Versions Compared

Old Version 2

changes.mady.by.user Craig Appl

Saved on

compared with

New Version 3

changes.mady.by.user Craig Appl

Saved on

Key

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

...

This section defines the software products that can deliver the Enterprise and Functional Architectures cited above.

(WE WILL DO THIS LAST)

 

Expand
titleOriginal brainstorm notes that began this document
Focus on where the supply chain meets the patient and that will be the biggest impact for OpenHIE.
High Impact Interventions:
    - Recalls
    - End to End visibility
    - Sub-standard/falsified products (SGTIN - Serialized GTIN, every individual item is uniquely identified)
Components of the architecture:
    - Identification: Identify what products are available (as a service); use a standard identifier and a standard way to read that identifier (may be a barcode)
  •     - the service could send or receive or look up products based on standards (like GTIN with a Code 128 barcode reader device)
  •     - classifications can exist (commodity versus item; items can be grouped into commodity buckets)
  •     - some 
    - Report consumption (consumption over a period of time) on a regular schedule in the HMIS
    - Delivery of Shipments (ASN)
    - Inventory Report
  •      - For commodities
  • - For items
    (Out of OpenHIE - Dispensing Transactions against commodities)
    - Client Systems:
        - ERP
        - LMIS (OpenLMIS, mSupply, Logistimo)
    - Workflows
  •     - Start at point of service for a particular set of workflows
  •     - Show the sequence of the workflow and what data interchange makes that possible
  •     - Human/system workflows and start to tag standardized transactions to support those workflows
  •     - Reporting could happen partly into an HMIS and also into speciality supply chain reporting tools