You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Work in progress

This is page is a work in progress. This info bubble will be removed once the TWG feels it is complete.

This page presents real world integration experiences that the team has collated. This information serves as background to help others understand some of the values and workflows created by this TWG.

Bidirectional OpenMRS → CommCare Integration

Dimagi built a point-to-point connection between CommCare and OpenMRS using the existing APIs. OpenMRS is the source of truth for this integration. The workflow focuses on exporting a list of people for community follow-up and entering them in to CommCare. Information collected in CommCare gets sent to OpenMRS as encounters and observations. CommCare is not responsible for creating new patients as part of this workflow.

Referral Workflow

Referrals are when a patient is referred from a community to a central health facility or visa versa so that they can receive care that that team can provide. Referrals are a package of information sent from the CHIS to the EMR in this instance.

Generic Steps:

  • User collects a form in the mobile app
  • Mobile app syncs to the central system
  • Central system identifies that there is a referral that needs to go to the third party system
  • Central system creates the referral package by mapping incoming form submission fields to the output(s)
  • Central system sends the package(s) to the third party system
    • Note: This may require creating multiple entities in the third party system and the Central data repository is responsible for orchestrating that. For example, you first need to create the patient, then the encounter, then the observations with the ability to roll back changes.
  • Third party system receives the package and confirms that it was received
  • Third party system parses each package and stores them in the system
  • Third party system may trigger internal events based on this changing information

CommCare ↔ OpenHIM

CommCare is importing data from a DHIS2 server through an OpenHIM mediator.

Point-to-Point ↔ DHIS2 connection for Aggregate and Tracker

CommCare is responsible for collecting and sending individual transactions to DHIS2 tracker. There is also a general pattern used to send regular reports from a central system to DHIS2.

Unidirectional OpenSRP → OpenMRS Integration


Bidirectional OpenSRP/CHT ↔ RapidPro Integration


Bidirectional Referrals OpenSRP CHW App ↔ OpenSRP Facility Based App


CHT ↔ EMR (Mali)


CHT Trace Reports for Lost to Follow-up and Contact Tracing

  • No labels