Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleFollow-up call Sep 30, 2024

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

      Jira Legacy
      serverSystem Jira
      serverIddd5f38d5-f8f4-3f41-9551-b59f4841491c
      keyO3-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.

Expand
titleFollow-up call Sep 23, 2024
  • LIMS integration

  • Deployment of dev-his.openmrs.org

    • Done, needs to fix the app switcher config.

    • 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

      Jira Legacy
      serverSystem Jira
      serverIddd5f38d5-f8f4-3f41-9551-b59f4841491c
      keyO3-4009
      ).

  • Ozone Analytics

Expand
titleFollow-up call Sep 2, 2024
  • 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)

      Jira Legacy
      serverSystem Jira
      serverIddd5f38d5-f8f4-3f41-9551-b59f4841491c
      keyHIS-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).jpgImage Added
    • 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.

Expand
titleFollow-up call Aug 26, 2024
  • 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.

    • Will enable SENAITE as the default LIMS option for now.

      Jira Legacy
      serverSystem Jira
      serverIddd5f38d5-f8f4-3f41-9551-b59f4841491c
      keyHIS-15

  • Deployment of dev-his.openmrs.org

    • Delayed few days: init. estimate on end of last week. Looking at mid this week now. (technical work is done so that child distributions can build those Docker-embedded images).

    • Unable to reach out to Rafal. Scott has not answered regarding if a Bamboo job already exists or not.

  • FHIR API for Odoo

  • MambaETL

    • Technical architecture call on Thursday

      • Simplicity of deployment (OMODs and/or SQL script)

      • Ability to dynamically flatten encounters and transpose questions as columns

      • Concerns over:

        • Change Data Capture done through monitoring some specific database fields (date_changed, date_voided…) instead of default mechanisms (binlog…)

        • Performance concerns (due to a lot of indexing) for 10M records databases.

        • Little to no testing.

  • Ozone Analytics

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

Expand
titleFollow-up call Aug 19, 2024
  • OEG integration

    • Project updates shared by Suruchi: integration work is being delayed (+1 week already) by low responsiveness from OEG devs. Attempting to setup weekly calls.

    • Eudson advises to not implement any workaround and rather wait for OEG folks to answer.

  • Deployment of dev-his.openmrs.org

    • Development work needed to deploy embedded distro Docker images is well advanced. Est. done by mid-week.

    • Then reaching out to Rafal in OpenMRS community to deploy via Bamboo.

    • Q: Emmanuel Nyachoke where to deploy the OpenMRS Distro HIS-embedded Docker images?

  • FHIR API for ERPNext (or Odoo)

    • From Slack message Odoo might be a better fit for the default ERP system in Ozone and OpenMRS distro HIS.

    • Work needed to have ERPNext expose a FHIR API still needs to be documented as an example. Current work could be pushed and documented so to be picked up and resumed by other group.

    • ChargeItemDefinition and InventoryItem exposed in Billing & Pharmacy modules needs to start. Mekom will provide guidance. Need to use the https://github.com/ozone-his/fhir-structures-backport-r4/ library.

  • MambaETL + Oz Analytics

    • Plan a call this week between UCSF and Mekom to look at Mamba ETL in terms of incremental updates.

  • DHIS2 / DHIS Tracker integration:

    • Integration with Tracker. Advises to look at the Ethiori REDCap integration.

    • Integration DHIS2 (analytics). Advises to look at the Ozone Analytics when integrated data analytics.

Expand
titleFollow-up call Aug 12, 2024

OEG integration:

Deployment of dev-his.openmrs.org.

FHIR API for ERPNext:

  • Architecture still in progress. Leaning towards running HAPI FHIR to transform and expose FHIR objects from the ERPNext database.

    • Architecture will be defined this week and implementation started the week after.

Expand
titleFollow-up call Jul 29, 2024
  • Analytics in OpenMRS Distro HIS: Ozone Analytics + Mamba ETL

    • 3 tickets to be worked on:

      • Jira Legacy
        serverSystem Jira
        serverIddd5f38d5-f8f4-3f41-9551-b59f4841491c
        keyHIS-11

      • Jira Legacy
        serverSystem Jira
        serverIddd5f38d5-f8f4-3f41-9551-b59f4841491c
        keyHIS-10

      • Jira Legacy
        serverSystem Jira
        serverIddd5f38d5-f8f4-3f41-9551-b59f4841491c
        keyHIS-9

    • Planned a demo session of Mamba ETL w/ support of incremental changes lead by UCSF. (to be scheduled to next week)

  • OEG integration in progress:

  • Deployment of dev-his.openmrs.org server:

    • Will be looked at tomorrow.

  • FHIR specs for ERP Processes completed. Link: https://docs.google.com/document/d/1uvJwYCGZg_wnt5eMCFLBIJoWU4CQaUWSKENvHrR-MEg/edit?usp=sharing

    • Designs for Price + Stock upon ordering will be added in Zeplin today.

      • Need some architecture call with Wyclif regarding exposing the FHIR API of the ERP (and authenticating to it)

  • SSO: Should be configurable to be enabled by implementers.

  • Custom systems integration:

    • Ethiori being integrated with a custom LIMS. → good progress done in Ethiori hackathon.

    • Used as an example to add more integrations.

  • Enabling SENAITE in OpenMRS distro HIS:

    • Stephen Senkomago Musoke starting evaluation of SENAITE integration.

      • Patients are synced

      • Lab orders not tested as unable create orders with admin users. Reached out on the #ozone channel.

      • Mekom reported some issues with the Lab order basket (unable to revise order).

  • DHIS2 integration by Michael Bontyes . Interested in looking UgandaEMR existing DHIS2 integration.

    • MSF scope: Initialize a new OpenMRS instance with DHIS2 patients (w/ DHIS2 ID + demographics)

      • Using OpenFn to send the new patients and data points.

      • Business logic available on GitHub.

Expand
titleFollow-up call Jul 22, 2024
  • Analytics in OpenMRS Distro HIS: Ozone Analytics + Mamba ETL

    • 3 tickets to be worked on:

      • Jira Legacy
        serverSystem Jira
        serverIddd5f38d5-f8f4-3f41-9551-b59f4841491c
        keyHIS-11

      • Jira Legacy
        serverSystem Jira
        serverIddd5f38d5-f8f4-3f41-9551-b59f4841491c
        keyHIS-10

      • Jira Legacy
        serverSystem Jira
        serverIddd5f38d5-f8f4-3f41-9551-b59f4841491c
        keyHIS-9

    • Planned a demo session of Mamba ETL w/ support of incremental changes lead by UCSF. (to be scheduled to next week)

  • OEG integration in progress:

  • Deployment of dev-his.openmrs.org server:

    • Will be looked at next week.

  • FHIR specs for ERP Processes completed. Link: https://docs.google.com/document/d/1uvJwYCGZg_wnt5eMCFLBIJoWU4CQaUWSKENvHrR-MEg/edit?usp=sharing

    • Designs for Price + Stock upon ordering will be added in Zeplin today.

      • Need some architecture call with Brandon regarding the ability for O3 to query multiple backends.

      • Need some architecture call with Wyclif regarding exposing the FHIR API of the ERP (and authenticating to it)

  • Custom systems integration:

    • Ethiori being integrated with a custom LIMS.

    • Used as an example to add more integrations.

    • The week after next, prepare a demo/call to run through the Ethiori LIMS integration compared to say, SENAITE integration).

  • Enabling SENAITE in OpenMRS distro HIS:

    • Stephen Senkomago Musoke starting evaluation of SENAITE integration. Will provide more updates on #ozone channel by EOD.

  • DHIS2 integration by Michael Bontyes . Interested in looking UgandaEMR existing DHIS2 integration.

Expand
titleFollow-up call Jul 15, 2024
  • Analytics in OpenMRS Distro HIS: Ozone Analytics + Mamba ETL

    • 3 tickets to be worked on:

      • Jira Legacy
        serverSystem Jira
        serverIddd5f38d5-f8f4-3f41-9551-b59f4841491c
        keyHIS-11

      • Jira Legacy
        serverSystem Jira
        serverIddd5f38d5-f8f4-3f41-9551-b59f4841491c
        keyHIS-10

      • Jira Legacy
        serverSystem Jira
        serverIddd5f38d5-f8f4-3f41-9551-b59f4841491c
        keyHIS-9

    • We can assume that MambaETL is supporting incremental changes.

  • OEG integration in progress: Exact extent of the work is identified. Mekom to outline a timeline and provide regular updates on this call.

  • Deployment of dev-his.openmrs.org server in progress: Mekom and OpenMRS devops have met: Need to modify Ozone so that it provides Docker images with the configs+binaries embedded in the image. Work should be started around next week.

  • FHIR specs for ERP Processes completed. Link: https://docs.google.com/document/d/1uvJwYCGZg_wnt5eMCFLBIJoWU4CQaUWSKENvHrR-MEg/edit?usp=sharing

    • Focus on the common parts of ERP processes:

      • Stock levels displayed upon ordering.

      • Product price displayed upon ordering.

    • Comparison between FHIR spec vs OpenMRS designs in progress. Done by Kevin.

Expand
titleFollow-up call Jul 8, 2024
Expand
titleFollow-up call Jul 1, 2024
  • 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

  • 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.

...

Expand
titleFollow-up call April 29, 2024

Gilbert Muthee Romain Buisson Michael Bontyes

  • Scope of the group: facility level

  • What is out of this group:

    • MPI/CR Integration squad

    • FHIR channel

    • Offline discussions

  • Recurrence of call? Weekly in May, then to revisit later.

  • Gilbert/UCSF use case:

    • Looking for a unified UI to integrate ERP data, but also looking to be able to switch from “integrated OpenMRS module” vs. “dedicated ERP” like Odoo - Context statement

    • Common features, no matter the approach and whatever the backend/flavour is (ex. OpenMRS ERP module vs. dedicated ERP system integration). For example:

      • Stock levels upon ordering + moving goods and commodities around

      • Billing features

  • Next:

    • Planning integration Hackathon/Workshop in collaboration with Mekom in ~3 weeks - preparing concept note for it (to be sorted out: Goals, type of devs needed)

      • Started: Identify the boundaries/cut-off point, scope, and features of both flavours (ex. what do users get using billing module vs dedicated?)

      • To be started prior to the workshop:

        • Paul A. to look into overlaps and identify what should live where - also by reviewing the OpenMRS data model

        • Prepare the re-architecture scope

        • Pick tools for dedicated ERP. Ex. Odoo vs. ERPNext. Lab would be later.

        • To consider on the long term: how feasible would be the transition from the “light”flavour to the “dedicated “flavour” - data migration + ERP configurations/metadata to consider.

        • Product Catalogue: where will be the source of truth for the products between OpenMRS and the ERP. Middleware example: OpenConceptLab or Odoo. Considering pulling products from higher levels, that can be consolidated with local products = cascade approach. Limit current scope to facility level for now.

      • Workshop scope:

        • Dev and re-achitecture work for that scope to be “optional” + FHIR for the ERP readiness (format and endpoints)

        • Documentation, guideline-style to facilitate other to reuse - A BA could help

        • Current User Stories for billing and Stock

      • Not in scope:

        • FHIR facade - would be a next step

...