Attendees:
- Peter Alvarez (GS1)
Sean Lockhead (GS1)
- Chuck Biss (GS1)
Josh Zamor (VillageReach)
- Jake Watson (Deactivated) (VillageReach)
- Brian Taliesin (PATH)
- Mary Jo Kochendorfer (Deactivated) (VillageReach)
Call Recording: GS1 and OpenLMIS Discussion-20160728 1759-1.arf
Next steps for OpenLMIS:
- Discuss and decide on if we should use GPC or UNSPC.
- Discuss and determine how to exchange data.
NOTES:
Introductions, OpenLMIS is focused on providing donors (like USAID) visibility into the supply chain of health commodities after it is delivered to the central warehouse. Are goal is end-two-end visibility. Initially focused on managing the paper process and approvals initially, now moving towards improved stock management track and trace.
GS1 Team: Peter is focused on data structure for Heathcare. Sean manages the tech team and GDSN. Chuck focuses on barcodes.
Josh introducing the questions. Asked about GPC use in healthcare and logical model from USAID.
Peter: overall you are on the right track. The main decision is around choosing which standard to use, GPC or UNSPSC.
GPC (limited coverage, currently development is on hold, series of attributes associated with each product)
or
UNSPSC (no limitations in its development)
Once decided, then map either the GPC or UNSPSC to the GTINs / GLNs which the manufacturers are already using.
- Definition: The Global Location Number (GLN) is part of the GS1 systems of standards. It is a simple tool used to identify a location and can identify locations uniquely where required. This identifier is compliant with norm ISO/IEC 6523. The GS1 Identification Key is used to identify physical locations or legal entities.
- Definition: The GTIN is a globally unique 14-digit number used to identify trade items, products, or services. GTIN is also an umbrella term that refers to the entire family of UCC.EAN data structures. The entire family of data structures within the GTIN is: GTIN-12 (UPC)
Josh: Who pays?
Peter: Those generating the keys (usually manufacturers) pay to apply an identifier to your product. You pay if you want to generate a GTIN or GLN, that is when you become a member. Receivers don't need to be a member. Only if you want a GLN yourself.
Brian: Does the manufacturer have a single GLN (e.g., Pfizer) or one for each manufacturing location (e.g., Puurs, Belgium)
Peter: GLN are driven more by electronic commerce. Pfizer will have one for corporate and divisions, not all locations.
Team reviewed Josh's matrix:
Peter's comments: Master data for level one and two Transaction data. Some of the things noted get into tracability standards. Event based traceabilites helps when interacting with 3rd party system.
Brian would love performance management within deliveries (check in and check out) and using barcodes.
Peter outlined the three things to be most concerned with:
- Who (who am I and who are you)
- What (what information)
- Where (everything else, trace, events)
Josh: is there a preferred GDSN?
Peter: GDSN - the messages which are used in the exchange support our open standards. It is a messaging service (35 data pools over the world) which manufacturer publish in, and receipts subscribe to it. You need a relationship with one of the data pools. No database to log into, messaging service. I list all my stuff. Data sync service. Data pools are owned by countries or companies. Evaluate anyone of these. GDSN is one way of sharing data. Xml messaging peer to peer. Also, data recipients cannot dictate which data pool to use.
OpenLMIS will need to determine how to exchange data.
- Evaluate the GDSNs out there to determine if they do what we need.
- Back to USAID to determine and pay for the datapool arrangement