Develop FHIR HL7 adapter

[fhauptmann]

In addition to Package A, the contractor is required to develop an FHIR HL7 (Fast Healthcare Interoperability Resources) adapter in SORMAS with the FHIR Argonaut Profile. Argonaut defines a minimum scope of "mandatory fields" and "target fields" (code must be in LOINC format). (Http://www.fhir.org/guides/argonaut/r2/StructureDefinition-argo-immun ization.html).
A mapping between the SORMAS data schema and FHIR must be defined in order to exchange data with a DHIS2 system for IDSR-based case monitoring with the DHIS2 FHIR adapter (https://demos.dhis2.org/fhir-demo).
The particular systems provide all available patient and case-related fields. The other system takes over what makes sense. It is important to ensure that the necessary subset of patient and case fields match, so that data can meaningfully be exchanged.
The FHIR adapter must be able to map IDs for each business unit. SORMAS should save the case number of DHIS2 (Business ID - returned at creation). DHIS2 needs to save the Case ID of SORMAS.
Implementation of HAPI FHIR library: http://hapifhir.io/ should be used.

For Package B, it makes sense for the contractor to use the Open Health Information Mediator (OpenHIM) as a middleware component to facilitate interoperability between SORMAS and DHIS2. OpenHIM provides secure communication and data governance, as well as support for routing, orchestrating and translating requests that flow between systems (http://openhim.org/).