Versions Compared

Old Version 11

changes.mady.by.user Brandon Bowersox-Johnson

Saved on

compared with

New Version 12

changes.mady.by.user Josh Zamor

Saved on

Key

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

...

  • Capacity Building
    • Introduction/education on Supply Chain for Health Domain Professionals
      • Include educational materials on GS1 standards and how it applies; OpenLMIS v3 Commodity Model; why move from a flat Product List to a GS1 Commodity Model.
      • Terminology for product identification.
      • User personas and user stories.
  • Value Statement / 'why'
    • Documented the value of Supply Chain interoperability in the OpenHIE context. Make sure we remember the 'why' within the health context, for the health workers who use these systems and how it benefits patients.
    • Final October 2018 Document: Value Statement for an Integrated Health and Supply Chain
  • Facility Registry alignment
    • Include supply chain concepts into OHIE Facility Registry: GLNs, including all facilities that can hold stock (warehouses not just SDPs), hierarchies (perhaps multiple), connecting supply chains (facility X is supplied for Family Planning products from warehouse Y, for vaccines from warehouse Z), etc.
  • LMIS-HMIS Interoperability
    • OpenLMIS (gap project) is scoping interoperability and will share requirements with OHIE-SC (this will become an OHIE-SC workflow)
    • Discuss: (1) KPIs that add value; (2) architecture of how data is exchanged; (3) metadata alignment; (4) use cases/workflows; (5) capability statements.
    • Loop in work underway in countries: Malawi, Angola, and Tanzania.
  • Product Registry / Product Master Data "source of truth"/ Product Catalog Management
    • Define stakeholders and define the problem
    • Provide working definition of a Product Registry and of the value of a Product Registry at multiple levelsa definition for OpenHIE that fits with their "registries" concept, also provide working definitions for processes and tools that can assist in the creation of a "source of truth" through Master Data Management to create a "Product Master" and/or using a Product Catalog Management tool.  This should also include how these tools fit within standard industry tools such as a Product Information Management (PIM).
    • Provide workflows on how multiple levels (e.g. Global vs national) of product management processes/tools work.
    • Encourage / offer guidance on using standards such as GS1, standard barcoding, etc
  • Identify Next Steps - what work needs to be done to develop working reference software?