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

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

INSERT DIAGRAM

• Changes to diagram include:
  • Infrastructure
    • Addition of a Product Registry
    • Addition of Supply Chain Management Registry (name?)
  • Point of Service
    • Warehouse Management System (WMS)
    • Enterprise Resource Planning (ERP) System
    • Inventory Control System
    • Shipping/Third Party Logisticians (3PL)

Descriptions

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

• Product Registry - The product registry is responsible for standardizing and serving a list of commodities and items that are available within the system. At minimum, it provides a list of available commodities that are available for distribution, consumption and disbursement within the system. In more advanced cases, the product registry is able to serve detailed information on each item that is available within the system including lot and serial number information collected as GTIN and SGTINs. The information in the product registry supports numerous transactions in the health, supply chain and reporting workflows.
• Supply Chain Management Registry - The supply chain management registry is responsible for storing and serving inventory reports, consumption reports and shipment notifications. This registry provides visibility into the current inventory levels at each location, their consumption over time and anticipated movements throughout the system.
• Warehouse Management System (WMS) - The warehouse management system is a point of service system that is used at large warehouses to track the products that are available for order, pick, pack and shipping. WMS are different from inventory control systems because they handle much larger product volumes than expected at the end nodes in the system.
• Enterprise Resource Planning (ERP) System - The enterprise resource planning system is a point of service system that is responsible for planning the supply chain needs over a period of time. ERP systems often operate at large warehouses, district and national levels and forecast supply and demand within their catchment area. ERP systems are often linked with WMS at large warehouses.
• Inventory Control System - The inventory control system is a point of service system that is run at the location where commodities are dispensed to the patient populations. These systems often function within a dispensary, keep track of the individual transactions and support compiling inventory reports and consumption reports. These systems are often the final destination for commodities before they are distributed to the patient. 
• Shipping/Third Party Logisticians (3PL) - Third party logistics companies is a catch all term for point of service organizations that are responsible for transporting commodities between points in the supply chain. These operators receive notification of a shipment that needs to be picked up, they arrange the transportation, pick the shipment and deliver it the the appropriate place. The recipient is responsible for verifying the shipment once received.

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

• Identify Products that are available in the system
  • Commodity level - What types of products should be available?
  • Item Level - Of those commodities, which specific items are available?
    • Trade name
    • Lot/Batch (GTIN)
    • Serial Numbers (SGTIN)
• Validate that a product in the system is not sub-standard or falsified
• Track Inventory Available Across the Network
  • (Inventory is a snapshot at a point in time)
  • Receive Inventory Reports from Point of Service Systems
  • Provide this information to decision makers
• Track Consumption Across the Network
  • (Consumption is a snapshot of disbursements and wastage over a period of time)
  • Receive Consumption Reports
  • Provide this information to decision makers
• Shipment Notifications
  • Act as a clearinghouse for 3PL Pick-up Planning
  • Receive and Forward Advanced Shipment Notifications from Source to Recipient
  • Receive Proof of Delivery

Out of Scope Functions

• Disbursement level transactions at the point of service health facility

Workflows

• General Point of Service to HIE Workflows
  • Query by Commodity Name/Type/Identifier
  • Query by GTIN
  • Query by SGTIN
  • Submit Inventory Report
  • Query Inventory Report by Location
  • Submit Consumption Report
  • Query Consumption Report by Location
  • Submit 3PL Pick-up Request
  • Query 3PL Pick-up Request by Location
  • Submit 3PL Picked Up Action
  • Query 3PL Picked Up Actions by Location
  • Submit Advanced Shipment Notification
  • Query Advanced Shipment Notification by Location
  • Submit Proof of Delivery by Location
  • Query Proof of Delivery by Location
• Health Related Point of Service Workflows
  • Product Verification (ensuring product is not sub-standard or falsified)
    • Immunization
    • General Medicine
    • Consumer facing 
  • Recall Products - Central Authority to Point of Service
    
    • Identify the current inventory of that product throughout the system
    • Estimate the recall
    • Contact the organizations
    • Arrange Shipment

Solution Architecture

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

(WE WILL DO THIS LAST)