Page Comparison

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:

    • Add EIP-OpenMRS-Orthanc routes in Ozone repo (new repo created: https://github.com/ozone-his/eip-openmrs-orthanc/tree/main )

• 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

    Jira Legacy
    server System Jira serverId dd5f38d5-f8f4-3f41-9551-b59f4841491c key 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.