With the pull of a product list from PCMT->OpenLMIS making technical progress I wanted to re-surface what I’ve assumed is the proper partitioning of concerns: the mapping of a Product pulled from a product list into an OpenLMIS.
We’ve structured that in an ideal world a country runs PCMT as a National Product Catalog (NPC), and their OpenLMIS as their national public health LMIS, and therefore the proper positioning of product data would be:
- The NPC would be the authoritative source of product and item data.
- The LMIS would be the authoritative source of how that product data was used transactionally.
It doesn’t have to be so cut-and-dried, you could stick everything (but the actual transactions of course) in the NPC. However doing so could make it awkward for OpenLMIS:
- Mapping a Product to a Program - in OpenLMIS this is where we define things like if it’s a full-supply product, the display order on the LMIS form, etc.
- Mapping a Product to a Facility Type Approved Product (FTAP) - in OpenLMIS this is a bespoke concept, and it’s where OpenLMIS defines things such as the min and max supply levels as well as a reference price.
My preference is to leave Programs and FTAP’s in OpenLMIS - that keeps the definition of those things close to those operating the LMIS. That would mean that OpenLMIS would ideally have someway for the administrator to find new Products and ensure that their mapping to Programs and FTAPs was done (and correct).
Does this make sense to you?