Lab Orders and Results exchange between OpenMRS and OpenELIS

The Lab Order workflow between OpenELIS and OpenMRS will use the OpenMRS FHIR Workflow Module and suggested Communication Patterns to implement the ordering of lab tests from OpenMRS to OpenELIS and the returning the results to OpenMRS.

The current communication workflow uses HL7 V2.5.1 messages as documented here: (Result Reporting ). This functionality is implemented in openmrs-module-labintegration, an OpenMRS module made for an implementation of OpenMRS deployed in Haiti called iSantePlus.

Communication Overview

Open

Intergration Between iSantéPlus and OPenELIS

iSantéPlus

1. Install iSantePlus using one of the following approaches:

2. Docker: GitHub - IsantePlus/isanteplus-docker: Dockerized iSantePlus EMR

3. Apache Tomcat WAR: SOP iSantePlus Installation.docx

4. Install the OpenMRS FHIR module using the following omod file: openmrs-module-fhir2.omod

5. Install the iSantePlus Lab on FHIR module using the following omod file: labonfhir-1.0.0-SNAPSHOT.omod

6. Restart iSantePlus

Start up the OpenELIS Update Task in System Administration → Advanced Administration → Scheduler → Manage Scheduler

Open

OpenELIS Global 2.x

1. Install OpenELIS Global 2.x using the instructions HERE

2. Navigate to the "results reporting" configuration: https://IPforyourserver:8443/OpenELIS-Global/ResultReportingConfiguration

3. Move the radio button for Result Reporting to "Enable" and enter in the URL for the OpenMRS connection like in the example below.

4. Please note, the Test URL button may not respond to the FHIR module, so please disregard any errors if you click it.

5. Click Save at the bottom of the page.

FHIR Based Intergration Between Openmrs 3.x and OPenELIS 2.6

Openmrs 3.x

1. Setup OpenRMS 3.x on top an instance of the Refference Application see more

2. Load the Following Modules

   • FHIR2 module version >= 1.4.0

   • Lab on FHIR module

   • Order Entry Ui Module

   • Order Entry Owa

3. Configure the required settings .

   • labonfhir.openElisUrl ,The URL for the FHIR server where OpenELIS polls the Orders From.

   • labonfhir.openElisUserUuid ,UUID for the service user that represents OpenELIS

   see more on Configuring the above Modules.

   Note: The Lab test Concept should be of class Test ,and should be mapped to a Loinc code that matches a the Test Loinc Code in OpenELIS

4. Go to the Reff App (2.x) Patient Dashbord ,Go to Prescribed Medication Widget.

   See more on Creating Orders using the Order Entry Owa.

5. If the Lab on FHIR module is rightly configured ,it will generate the lab FHIR Bundle and push to the remote Fhir Server for OpenELIS to poll the orders

6. Start the OpenELIS Pull Task ,to start polling for Lab Results via the Sheduler Interface
   System Administration → Advanced Administration → Scheduler → Manage Scheduler

   ![screen1](img/omrsoe1.png)

7. To view the lab Results , Ensure you have the patient-test-results-app. Go to the Patient DashBoard in 3.x ui and click Test Results.

OpenELIS Global 2.6.x

The FHIR based Lab Workflow is supported in OpenELIS 2.6 .

1. Start an instance of OpenELIS with the following configuration properties set in the properties file.

2. org.openelisglobal.fhirstore.uri=<localFhirServerUrl> . This is the Fhir Server that runs paralel with OPenELIS

3. org.openelisglobal.remote.source.uri=<remoreFhirServerUr>. This is the Fhir server that the Lab on FHIR module points to ie via the labonfhir.openElisUrl

4. org.openelisglobal.remote.source.updateStatus=true

5. org.openelisglobal.remote.source.identifier=Practitioner/<userUuuid> .This is the UUID of the user who created the Order ie labonfhir.openElisUserUuid

6. org.openelisglobal.task.useBasedOn=true

7. org.openelisglobal.fhir.subscriber=h<remoreFhirServerUrl> .

8. org.openelisglobal.fhir.subscriber.resources=Task,Patient,ServiceRequest,DiagnosticReport,Observation,Specimen,Practitioner,Encounter

9. Ensure OpenELIS has the test that maps to the same LOINC code as the test Concept in OpenMRS. This can be added via theAdmin page → Test Management → Add Tests

10. Configure OpenELIS to accept electronic order. Admin → Order Entry Configuration → external orders

11. Search for the Electronic Order ieOrder → Electronic Orders and then Complete the Order Note that the user should have the right Lab Unit Priviledges to complete the Order

12. After Results are captured and Validated , OpenELIS sends back the results to OpenMRS as a Diagnostic Report with an Observation

Required FHIR Resources

Task

more info

The Task resource is created along with the corresponding ServiceRequest resource when a clinician creates a TestOrder and decides to send it to OpenELIS.

This resource is used to track the status of the lab order request from initiation to completion, and as a container for all other resources related to the given order.

Example Task:

ServiceRequest

more info

The ServiceRequest resource represents the TestOrder placed in OpenMRS. It is referenced from the Task with the Task.basedOn element, and sent to OpenELIS with the Task to initiate the processing of the order.

Example Service Request:

DiagnosticReport

more info

The DiagnosticReport resource is the container for the results of an Order, and holds these results in the DiagnosticReport.result element as references to Observation resources.

Example Diagnostic Report

Observation

more info

The Observation resource contains the results of the Lab Order request.

Example Observation:

Patient

more info

The Patient resource contains vital information for OpenELIS to fullfill the lab order request, and is referenced by the Task.

Example Patient:

Relevant FHIR Docs

• Using Tasks in a RESTful Context

• Workflow Module

• Diagnostic Module

• Example: Workflow states for a lab order for a blood test

• Option G: POST of Task to fulfiller's system

Relevant OpenMRS Talk Posts

The handling and mapping of lab order status for the lab workflow