| Page Properties | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Note |
|---|
There are two different approaches for Product List Sync: this standards-based approach (this wiki page) or Interface - Product list sync (direct integration approach) if there is no product registry standard. Regardless of the approach, achieving product syncing is a high priority. The choice of approach may be influenced by an external project (a potential USAID Product Registry project). That project would create a new standard so these integrations and connectors could be built in a standards-based way. |
...
| Title | User Story | Label | Importance | Notes | JIRA Tickets | |
|---|---|---|---|---|---|---|
| 1 | Product list update from ERP | As an administrator I want product lists in OpenLMIS updated in line with updates to product lists in the MSD E9 ERP so that I don't have errors with other OpenLMIS-MSD E9 ERP data exchanges. | MSD Epicor 9 ERP | Must have | ||
| 2 | Product list update review | As an administrator I want to be able to manually review product list changes and add additional information or configurations which are not available in the MSD E9 ERP. | MSD Epicor 9 ERP | Must have | ||
| 3 | Price list update from ERP | As an administrator I want prices in OpenLMIS updated in line with updates to prices lists in the MSD E9 ERP so that R&R submitters and approvers have accurate cost information. | MSD Epicor 9 ERP | Must have | ||
| 4 | Product list update from ERP | As an administrator I want product lists in OpenLMIS updated in line with updates to product lists in the MSL MACS ERP so that I don't have errors with other OpenLMIS-MSL MACS ERP data exchanges. | MSL MACS ERP | Must have | ||
| 5 | Product list update review | As an administrator I want prices in OpenLMIS updated in line with updates to prices lists in the MSL MACS ERP so that R&R submitters and approvers have accurate cost information. | MSD MACS ERP | Must have | ||
| 6 |
Additional User Stories still needed here:
- OpenLMIS connector to standards-based Product Registry
- 3 ERP Connectors from the Product Registry to ERPs for TZ and Zambia
- 1 DHIS2 Connector from the Product Registry to DHIS2
- 1 ILS Gateway connector from Product Registry to ILS Gateway
Diagrams
Dependencies
| Description | Link |
|---|---|
...
- Price schedules is a different thing than the ERP price (in user story #2).
- Different facility types get a different price.
- History (from Josh)
- Historically, the IT implementers who owned these systems had control over the product list.
- There has been lots of discussion around making this a more robust model, including GS1, the BI&A Logical Reference Model (USAID), and much more.
- Lots of pain points updating the ERP and the keeping all product lists in sync.
- New model draws from 2 sources: (1) GS1 -- understanding trading partners and products that are made by and defined by specific manufacturers; (2) the classification sources such as UNSPSC and GPC – who are putting out product master lists to extend some of those.
- In the new world, there are 2 owners and none of them are the IT implementers.
- Do ERPs have this information in them?
- Some have a GTIN identifier they can store.
- We don't know of any ERPs that support this – this is a problem.
- There is also an idea to create a Product Registry in the OpenHIE group and to make a reference implementation.
- Craig: Why isn't the one National ERP the one the has the master list, and other systems can consume this?
- Josh: The ERP does not own the data, the supplier actually does. The identifiers come from the manufacturer (through GS1 GTINs).
- Josh: We should assume there is master data that feeds from another system into both the ERP and OpenLMIS.
- Elias: Some countries have already implemented a Product Registry.
- Josh: So we should be pre-assuming the data is synced.
- What is the work in this epic?
- Hopefully the product registry will be funded as a separate project.
- The work to modify OpenLMIS to subscribe to a product registry is not in this Gap project.
- Mary Jo: I think this work does include the ability to subscribe to an external product registry. Plus we would need to estimate the connectors, so implementations can be successful until all systems match the standards.
- Ashraf: Only about 10% of products are supplied by USAID GHSC-PSM. Locally-procured products do not have GTINs/GS1. Most products will not be GS1 compliant.
- Josh: That is fine, and that is planned for. The Product Registry will have the ability to handle those products too.
- What connectors do we need to estimate?
- To the 3 ERPs and 1 connector to DHIS2.
- Issues:
- Hard to test ILS Gateway!
- Or do we replace or rebuilt it with another tool!
Option 1: With no product registry
(make 3 connectors from OpenLMIS to ERPs, 1 to DHIS2, 1 to ILS Gateway)
Dependency: ETL tool and Business Analysis
...