Lab results
Attach laboratory results to DHIS2 tracker cases, from HL7 v2 and FHIR sources.
A case is registered in a DHIS2 tracker program when a specimen is collected. The laboratory analyses the specimen and reports the result through its own systems, as an HL7 v2 ORU message or as a FHIR Observation. Zato receives the result, identifies the case by the specimen ID, and writes the result to the case in DHIS2.
This section describes each stage of the integration. The pages build on one another and are read in order.
Processing flow
The DHIS2 program
The integration assumes a tracker program with two program stages, in line with the DHIS2 laboratory interoperability reference implementation:
- A lab request stage, completed when the specimen is collected. It holds the specimen ID, which is the only value the laboratory and DHIS2 have in common.
- A lab result stage, which is repeatable. Each result is one event on this stage, and a corrected result updates the same event rather than adding a new one.
The services on the following pages look up the lab request event by its specimen ID, read the enrollment and organisation unit from it, and write the result to the lab result stage of the same enrollment.
Pages in this section
| Page | What it covers |
|---|---|
| Setup | The security definition, the REST connections and the configuration files |
| Write a result | Find the case by specimen ID and write the result event |
| Results over HL7 v2 | Receive ORU messages over MLLP and acknowledge them |
| Results from FHIR | Poll a FHIR server for new Observations |
| Held results | Results that arrive before their case exists |
| Weekly counts | Aggregate counts for a DHIS2 data set |
See also
| Feature | What it does |
|---|---|
| DHIS2 overview | All DHIS2 integration pages |
| HL7 v2 over MLLP | Channels that receive HL7 v2 messages |
| FHIR | Connections to FHIR servers |