THIS DOCUMENT IS STILL IN DRAFT FORM AND HAS NOT BEEN REVIEWED BY THE COMMUNITY

This document serves as a place to brainstorm changes to the OpenHIE Architecture to support standardized supply chain information collection and dissemination. There are three types of architectures presented on this page, the Enterprise Architecture, Functional Architecture and Solution Architecture.


Enterprise Architecture - What pervasive digital infrastructure do we need so that our system will act like a system? 
Functional Architecture - What things do we need to do; what workflows do we need to support? 
Solution Architecture - What software products will operationalize these workflows within the context of the enterprise infrastructure?

Enterprise Architecture

The Enterprise Architecture identifies the pervasive digital infrastructure that the system will need.



Descriptions

This section contains a textual description of each item added to the diagram above:

Functional Architecture

The functional architecture focuses on identifying the functions required in the supply chain as well as the workflows that deliver those functions.

Functions

Out of Scope Functions

Workflows

This section defines high level workflows that should be considered within this functional architecture.

Solution Architecture

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

(WE WILL DO THIS LAST)


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