Wiki Spaces

Documentation
Projects
Resources

Get Help from Others

Q&A: Ask OpenMRS
Discussion: OpenMRS Talk
Real-Time: IRC Chat | Slack

Documentation

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update link to go to OpenMRS Add-ons index instead

...

simplelabentry.testFailureConcepts

What this does: TBD TBD - need to clarify whether this is actually used by the module.

How you should enter it:: This should be a comma-separated string of entries in the form (labTestSetConceptId).(testFailureConceptId)

simplelabentry.conceptsInLabSetsThatAreNotTests

What this does: TBD

How you should enter it:: As a comma-separated string of concept ids

simplelabentry.labOrderType</property>

What this does: Within the "Lab Order Entry" section, when a new Order is placed for a Lab Test, the Order Type that is created is determined from this property. So, this property should be configured with the Order Type that refers to a Lab Test order.

How you should enter it:: An Order Type ID

simplelabentry.labTestEncounterType

What this does: This should be the EncounterTypeId of the EncounterType that represents a Lab Test

How you should enter it:: An Encounter Type ID

simplelabentry.patientIdentifierType

What this does: The system supports a single primary identifier type for searching for patients, and also that is displayed on the entry screens for each patient. You should enter here the PatientIdentifierType that you would like the system to use for listing, searching, and creating patients

How you should enter it:: A Patient Identifier Type ID

Overview

TBD

Installation and Configuration

The module requires the following global properties to be set before it can be used:

simplelabentry.supportedTests

What this does: This determines what Lab Tests may be ordered and entered within the module. This supports panels of tests (eg. Hematology, which includes multiple tests such as Hemoglobin, Hematocrit, etc.), or single Tests (eg. HIV Rapid Test Result). Examples of what this looks like are included in the Usage section below.

How you should enter it:: A comma-separated string of concept ids. Each concept id may either refer to a Concept of type "LabSet", in which case all of the Concepts of type "Test" within this set will be entered together, or may refer to a Concept of type "Test", which will allow for single test result entry.

simplelabentry.testFailureConcepts

What this does: TBD

How you should enter it:: This should be a comma-separated string of entries in the form (labTestSetConceptId).(testFailureConceptId)

simplelabentry.conceptsInLabSetsThatAreNotTests

What this does: TBD In the event that you have the "supportedTests" property configured to point at a Concept Set, and within that Concept Set you have a Concept of type "Test" which you do _not_ want to include for entry, you can specify that in this property here.

How you should enter it:: As a comma-separated string of concept ids

simplelabentry.

...

labOrderType

What this does: Within the "Lab Order Entry" section, when a new Order is placed for a Lab Test, the Order Type that is created is determined from this property. So, this property should be configured with the Order Type that refers to a Lab Test order. From the Administration page, go to  Orders > Manage Order Types to list or add Order Types. 

How you should enter it:: An Order Type ID

simplelabentry.labTestEncounterType

What this does: This should be the EncounterTypeId of the EncounterType that represents a Lab Test. From the Administration page, go to  Encounters > Manage Encounter Types to list or add Order Types.

How you should enter it:: An Encounter Type ID

simplelabentry.patientIdentifierType

What this does: The system supports a primary identifier type to use when searching for patients, and also a single type which is displayed on the entry and view screens for each patient. You should enter here the PatientIdentifierType that you would like the system to use for this purpose here. From the Administration page, go to Patients > Manage Identifier Types to list or add Patient Identifier Types.

How you should enter it:: A Patient Identifier Type ID

...

What this does: The system supports additional identifier types that can be used when for searching for patients. These should be entered here.  From the Administration page, go to Patients > Manage Identifier Types to list or add Patient Identifier Types.

How you should enter it:: A comma delimited set of patient identifier type IDs.

...

What this does: Used to display the patient's current state in the configured program workflow when viewing patient entries in the lab order and result entry interfaces, as well as when searching for patients. This is used in conjunction with the "workflowToDisplay" property. From the Administration page, go to Patients > ManagePrograms to list or add Programs.

How you should enter it:: This The name of the program, not the id. For example - "HIV PROGRAM"

...

What this does: Used to display the patient's current state in the configured program workflow when viewing patient entries in the lab order and result entry interfaces, as well as when searching for patients. This is used in conjunction with the "programToDisplay" property. From the Administration page, go to Patients > ManagePrograms. Click on the program to see workflows.

How you should enter it:: This name of the workflow, not the id. For example - "ANTIRETROVIRAL TREATMENT GROUP"

...

What this does: Allows you to configure what Concept in your dictionary refers to "CD4 Count". This is needed for the CD4 Count Report that the module provides. Again, this is specific to Rwanda needs and is a good candidate for refactoring out in a more generic way, but currently is required by the module. Go to the Concept Dictionary to find or create a CD4 concept.

How you should enter it:: The local conceptId of the CD4 concept

...

The module is written to support a particular workflow, namely one in which first an Order is entered for one or more lab tests, and later results are entered for these ordered tests. There is also an administrative interface for managing all lab orders and results, as needed, outside of this particular workflow, as well as some pre-built reports. These are described in more detail below.

Lab Order Entry

TBD.  Instructions and screenshots here

Lab Result Entry

TBD.  Instructions and screenshots here

Lab Data Management / Administration

TBD.  Instructions and screenshots here

Reports

TBD.  Instructions and screenshots here

Download

...

\* \[Download from the OpenMRS module repository\|http://modules.openmrs.org/modules/view.jsp?module=simplelabentry\]

Release Notes

TBD