| Target release | Release name or number |
|---|---|
| Epic | Interface - Product List sync |
| Document status | |
| Priority | |
| eLMIS Status | Not implemented |
| OpenLMIS Status | Not implemented |
| PATH | |
| OpenLMIS | Mary Jo Kochendorfer (Deactivated) |
| JSI |
|
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. |
Product lists and prices in OpenLMIS are updated in line with updates to product lists and prices in the ERP, so that this does not cause problems during import of orders from OpenLMIS to ERP and facilitates other future interoperability between OpenLMIS and the ERP.
Status in eLMIS: Not in eLMIS currently.
Status in OpenLMIS: Not in OpenLMIS currently
Priority: High priority for Tanzania especially for MSD
Notes: zambia
Status in eLMIS: Not in eLMIS currently.
Status in OpenLMIS: Not in OpenLMIS currently
Priority: High priority for Zambia especially for MSL/LMU
The PMU staff act as eLMIS administrators and configure eLMIS. Zonal level PMU staff are active in configuration of product lists and national advisors do other configuration.
Product meta-data are entered manually into eLMIS (with descriptions matching those on paper R&R forms). Products are entered into the ERP in parallel and by other MSD staff. This can result in mismatching, which throws up errors when requisitions are being imported from eLMIS to the ERP, which then need to be resolved manually.
Products in both eLMIS and in the ERP are generally the generic commodity as opposed to branded trade items. Kits are generally listed as one product as opposed to the constituent parts. The same item under different programs (for example cotrimoxazole under ILS and under ARV&OI) is coded and treated as separate items.
Prices are normally changed once per year, at the start of the financial year (i.e., 1 July). The system stores old prices as well as new prices and uses the appropriate prices for any particular time period.
Imports of R&Rs/orders currently return errors when product lists do not match. If prices do not match, this means that eLMIS does [not] give accurate cost information to R&R submitters and approvers.
Product prices are normally changed at the start of each financial year. New products can be created at any time.
See also sect ions of the document “System requirements specifications for eLMIS interface with mSupply” which discuss import of product lists.
Additional Notes : Zambia
MACS is the ERP in use by Medical Stores Limited in Zambia. MACS is for internal MSL use only. MACS covers internal management of MSL including MSL procurement, stock management and storage and distribution. For any functionality which involves interfaces with health facilities, districts or the Ministry, MSL requires that that functionality be in eLMIS.
Product meta-data are entered manually into eLMIS (with descriptions matching those on paper R&R forms). Products are entered into the ERP in parallel, and by other MSL staff. This can result in mismatching, which throws up errors when requisitions are being imported from eLMIS to the ERP, which then need to be resolved manually. New products can be created at any time.
While some non-vaccine items do require cold chain conditions, they are not given any special configuration treatment.
| 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:
Include any business process mapping, mockups, diagrams or visual designs relating to these requirements. Describes the tasks and the personas who perform those activities. The diagram provides the context for the user stories and serves as a focal point for achieving clarity and agreement among stakeholders. Looks like a standard flow chart.
Identify initial dependencies that are on the critical path for this functionality and may affect the delivery time and serving of business goals. Include links to stories.
| Description | Link |
|---|---|
| Name of story or release | Link to JIRA |
Initial communication between stakeholders and the development team to help understand scope and estimates.
Below is a list of questions to be addressed as a result of this requirements document:
| # | Question | Outcome | Status |
|---|---|---|---|
| 1 | Will product list updates always go through a manual validation and update process? | Communicate the decision reached | Open, In Progress, Closed, and date of closure |
| 2 | Was this background detail confirmed as not a gap in OpenLMIS: "Prices are normally changed once per year, at the start of the financial year (i.e., 1 July). The system stores old prices as well as new prices and uses the appropriate prices for any particular time period"? | ||
| 3 | Need for adding in "System requirements specifications for eLMIS interface with mSupply" on import of product lists. | ||
| 4 | Is there a desire to have this done automatically? |