/
OpenMRS Interoperability and Integration Updates

OpenMRS Interoperability and Integration Updates

Focus on OpenMRS interoperability & integrations at facility-level

Mondays at 9 AM EST, 4 PM EAT - Link: meet.google.com/ksh-mdae-rtw

Represented organizations: UCSF, UgandaEMR, Palladium, Mekom, MSF/Madiro

Examples: Laboratory, billing, stock management, etc.

Objectives

  • Share knowledge and use cases about data exchange use cases

  • Align on practices, tools, and architectures

Deliverables

  • Map ecosystem of existing solutions and challenges to address them as a group

  • Framework for integration

  • Sets of routes

  • Documentation about how to integrate OpenMRS with other health systems

Calls and notes

Call cancelled, low attendance

Wei (UCL), Siddharth, Romain, Eudson, Michael

Wei (UCL), Siddharth, Romain, Eudson, Michael

  • Orthanc integration

    • Flows:

      • Order made in OpenMRS (radiology order planned in next 2 months) to be sent to Orthanc

      • Periodic sync from Orthanc to OpenMRS

      • Orthanc ID to be added to OpenMRS for mapping

    • Questions:

      • How to map/merge patients coming from Orthanc to OpenMRS ID? → For now, direct 1:1 mapping between the 2 systems (No CR)

      • SSO for login and privilege integration - Orthanc authentication Documentation and repo

    • Priority:

      • Link to patient/study in Orthanc in OpenMRS patient file

      • Later on, we can imagine a preview or iframe in OpenMRS with imagery

    • Next:

  • Deployment of dev-his.openmrs.org

    • Done, needs to fix the app switcher config. Fixing in progress.

    • Update on the README to point to direct access to apps by URL.

    • Next:

      • Enable SSO.

      • Enable Ozone Analytics

  • Stock & Price visible in O3 upon ordering.

    • openmrs-module-fhirproxy is now done.

    • fhir-odoo API is now done.

    • Need to implement the FHIR endpoints in Billing & Inventory OpenMRS modules. @Amos Laboso to reach out to Mekom regarding coding those FHIR endpoints.

    • UI implementation is happening ( @Usama Idriss Kakumba assigned to https://openmrs.atlassian.net/browse/O3-4009 ).

    • Testing currently in progress: finding some issues: initial development of OpenMRS module FHIR proxy done against 2.4.x and appears not compatible with 2.6.x, currently being looked at.

  • LIMS integration

  • Deployment of dev-his.openmrs.org

    • Done, needs to fix the app switcher config.

      • @Emmanuel Nyachoke to fix it this week.

    • Demoed at the conference multiple times.

  • Stock & Price visible in O3 upon ordering.

    • openmrs-module-fhirproxy is now done.

    • fhir-odoo API is now done.

    • Need to implement the FHIR endpoints in Billing & Inventory OpenMRS modules. @Amos Laboso to reach out to Mekom regarding coding those FHIR endpoints.

    • UI implementation is happening ( @Usama Idriss Kakumba assigned to https://openmrs.atlassian.net/browse/O3-4009 ).

  • Ozone Analytics

  • LIMS integration

    • OEG integration work is halted until the missing features are implemented.

    • Will touch base weekly to assess the progress and resume work when a number of the features are fixed.

    • Enable SENAITE as the default LIMS option currently in progress (PR in review and a bug reported) https://openmrs.atlassian.net/browse/HIS-15

  • Deployment of dev-his.openmrs.org

    • Work necessary in Ozone to build bundled Docker images is now done and currently being deployed (on the Ozone side).

    • Deployment of OpenMRS Distro HIS should be done through a Bamboo job - done by today or tomorrow.

  • FHIR API for Odoo

    ERP FHIR facade (1).jpg
    • Work has started.

      • Odoo Java Client: we will be using the Odoo Java API project as a Java client for Odoo XML RPC API → https://mekomsolutions.atlassian.net/browse/OZ-688 is not necessary anymore.

      • OpenMRS module FHIR Proxy work is started. Will get more updates after the Ozone internal call.

      • HAPI FHIR server work started today. Will get more updates after the Ozone internal call.

  • MambaETL

  • Ozone Analytics

    • Open sourcing of Ozone Analytics will be started by @Kakumirizi Daud this week.

Links and references

Archives