OpenMRS Interoperability and Integration Updates

• OEG integration in progress: Define exact extent of the work needed. Mekom to outline a timeline and project manage.

• Testing of OpenMRS Distro HIS in progress.

  • ERPNext processes confirmed to be working.

  • Documenting how Implementers can adopt OpenMRS Distro HIS-> to be reviewed by @Stephen Senkomago Musoke

    • Investigate how OpenMRS Distro HIS can be adopted

      • Direct inheritance from Ozone.

      • Inheritance of OpenMRS Distro HIS.

        • @Stephen Senkomago Musoke to try both options.

• Deployment of dev-his.openmrs.org server in progress: Mekom and OpenMRS devops to meet tomorrow.

• FHIR specs for ERP processes progressed. Almost ready to be shared.

• @Stephen Senkomago Musoke is looking into trying Superset within Ozone.

  • Mamba ETL flattened encounters tables must be forwarded to the PostgreSQL analytics table (from Ozone Analytics) as to be available as 1 single datasource in Superset.

    • Not so straightforward as the table columns is dynamic.

    • Need to find a way to identify a source data model and create the corresponding target database

    • → Set to the agenda next week. Invite @Wyclif Luyima @Emmanuel Nyachoke @Arthur D. Mugume @Laureen Omare .

• OEG integration in progress: See Slack conversation between Mekom and UW.

• Testing of OpenMRS Distro HIS in progress.

  • No demo patients created when running start-demo.sh. Further testing needed. Might need some documentation improvement → @Stephen Senkomago Musoke confirms that demo patient are created.

  • Testing of the actual integration between OpenMRS and ERPNext in progress. Should be done by mid-week by @Stephen Senkomago Musoke .

    • Create patient in OpenMRS

    • Create an order for that patient

    • See the patient in ERPNext

    • See the quotation opened in ERPNext

  • Documenting how Implementers can adopt OpenMRS Distro HIS → redirect to Ozone docs here: https://docs.ozone-his.com/create-distro/

    • Example of Ozone LIME: https://github.com/MSF-OCG/LIME-EMR

    • Example of KenyaHMIS: https://github.com/palladiumkenya/kenyahmis/tree/main

    • Investigate how OpenMRS Distro HIS can be adopted

      • Direct inheritance from Ozone.

      • Inheritance of OpenMRS Distro HIS.

• Deployment of dev-his.openmrs.org server in progress: host is ready on OpenMRS infrastructure. Next step is to actually deploy OpenMRS Distro HIS (need to identify how can do so).

• No progress on FHIR specs for ERP processes. @Romain Buisson will provide updates in next call.

• @Stephen Senkomago Musoke is looking into trying Superset within Ozone.

  • Discuss how we could leverage on Mamba ETL flattening in Ozone Analytics.

  • Superset alone (in Ozone FOSS) is decommissioned for now in favor of running it with Ozone Analytics.

  • Needs to find ways to have Mamba ETL tables available in Superset as part of Distro HIS (via Ozone Analytics?)

     

• Testing of OpenMRS Distro HIS in progress.

  • Process of raising issues:

    • Reach out on Slack first if issue is unsure, or needs some bits of troubleshooting first. or missing documentation.

    • Identify the priority.

    • Then create the JIRA ticket.

    • Document the ticket number on the Slack thread.

  • Conflicting names of containers when running multiple Ozone distros side-by-side

    • Provide a better default for Docker Compose project name (maybe to be the project name)

    • Provide the ability to override it at start time.

    • Ticket:

  • start.sh script not documented (only start-demo.sh). @Stephen Senkomago Musoke will update the documentation.

  • No demo patients created when running start-demo.sh. Further testing needed. Might need some documentation improvement.

  • Next testing steps: try the actual integration between OpenMRS and ERPNext:

    • Create patient in OpenMRS

    • Create an order for that patient

    • See the patient in ERPNext

    • See the quotation opened in ERPNext

  • Documenting how Implementers can adopt OpenMRS Distro HIS → redirect to Ozone docs here:

    • Example of Ozone LIME:

    • Example of KenyaHMIS:

• Deployment of dev-his.openmrs.org server in progress: host is ready on OpenMRS infrastructure. Next step is to actually deploy OpenMRS Distro HIS (need to identify how can do so).

   

• Goals for distro HIS (timeline ~Sep 2024)

  • dev-his.openmrs.org available

    • integrates with ERPNext

    • (integrates with OEG)

  • documentation available for implementers to leverage on it.

OpenMRS Distro HIS repo started and initialized.

Will start OpenMRS + ERPNext with default integrations. Needs testing + doc.

The presentation of OpenMRS distro HIS in the TAC call went well.

Some discussion ongoing on Talk:

Next step:

• Create GH the repository: openmrs-distro-his. → Mekom

• Create the Jira project: OpenMRS Distro HIS [HIS] → Mekom

• Initialize the repo using the Ozone Maven Archetype → UCSF to create the ticket, Mekom to work on it.

  • Adjust the Group ID to be org.openmrs

  • Artifact ID to openmrs-distro-his

  • Remove Ozone white labelling to keep the default Ref App theme.

  • Update the O3 Ref App dependency to point to latest next version of O3 (in the pom + Docker images)

  • Enable EPRNext integration

  • Disable other integrations (Lab integration should be enabled when OpenElis Global integration is ready)

  • Disable “embedded ERP” features:

    • Billing & Stock OMODs dependencies

    • Billing & Stock ESMs

• QA/testing of the new distribution.

• Start a dev server for OpenMRS Distro HIS: dev.his.openmrs.org (test.his.openmrs.org / demo.his.openmrs.org, alternatively dev-his...)

• Documentation:

  • OpenMRS Atlassian doc:

    • The repository

    • Vision/strategy

    • The specific configuration (components enabled…)

    • Use cases to cover / patient flows

    • Adoption of OpenMRS Distro HIS:

      • How to use that distribution and replace O3 Ref App with your own EMR distro.

Next call:

• What about analytics?