Medical Commodities: OpenLMIS Model for GS1

Updated for OpenLMIS 3.0. See previous versions of this page and Beta to 3.0 changes for historical information.

See Product Identification Terminology Reference for updated terminology around Products, their identification, classification and related concepts.

Introduction

OpenLMIS provides functionality for medical commodity logistics: ordering, shipping, receiving, and managing stock. In OpenLMIS 3.0, the model for storing and managing this data has been redesigned to align with the global GS1 standards. This new model has benefited from significant feedback and collaboration with representatives of GS1, USAID, BI&A LRM (Intellicog - Logical Reference Model).

This page documents the model as it exists in OpenLMIS 3.0; whereas the wiki sub-pages outline the direction of future development and should be considered working designs.

Our goal is to put the OpenLMIS community and code-base a step ahead in implementing best practices. This will provide long-term benefits including global alignment around analytics, end-to-end visibility, and shared value as the global community works to improve medical supply chains in an increasing number of countries.

Data Model

Modeling of medical commodities is central to OpenLMIS. Correctly modeling commodities enables administrators to:

• set up forms for requisitioning and re-supply

• managing their stock in inventory

• assess what their budget may support

• provide full visibility into a working supply chain

• enable trace-ability from production to consumption

Table of Contents

Model Diagram

The diagram below shows the domain objects and their relationships:

Open

Historical Note

In version 2 and earlier, Products were represented but a much simpler model shown below:

The Product model in version 2 and earlier was straightforward and could be reduced to two critical pieces of information:

• unique identification - both for the user as well as for connected systems

• a count of the number of dispensing units in a pack

Products had many optional fields and so by way of filling in some fields and not others we could define one product within the system as something more or less specific. It could be branded or generic such as the difference between Advil and Ibuprofen. It could define the primary package's dimensions, or even the carton's dimensions and how many could fit on a pallet. Defining these, or not, influenced how one reasoned about that particular product within the system, especially within inventory and fulfillment.

See previous versions of this page and Beta to 3.0 changes for historical information.

Working Documents

Warning: The links below do not represent the final design for OpenLMIS v3.0. They contain ideas for future implementation as well as notes and working drafts:

• Product Master within Orders

• Design within Inventory

• Working Notes on Products, Kits, Packaging