Page Comparison

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 module” vs. “leverage full “dedicated ERP like ODOO”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