|
Note: This solution is an alternative option to using global standards in Interface - Facility Lists using Global Standards w/ mCSD. It creates atleast 3 connectors to 3 specific systems: EPICOR 9, MACS, mSupply as well as DHIS2. It would require new connectors for each new IT system used in country that needed to agree on Locations. |
For facility lists in OpenLMIS to be updated in line with updates to facility lists in the ERP (and other systems) so that there are not problems importing orders from OpenLMIS to the ERP and to facilitate future interoperability between OpenLMIS and the ERP. If a country has a facility registry, that would be another potential implementation. There are issues around who is the source for the facility lists, if the ERP then the ERP would be the appropriate system for the interface.
Status in eLMIS: Not in eLMIS currently.
Status in OpenLMIS: Not in OpenLMIS currently
Priority: High priority for Tanzania especially for MSD
Configuration of facilities and facility requisition groups
Facility meta-data is entered in parallel into eLMIS and into the ERP.
When a facility is registered, it is give:n a facility type (dispensary, health centre, hospital, etc.), it is assigned one or more programs (ILS, ARV&OI, TB&L, Lab), the district where it is located is recorded, and it is assigned to a “facility requisition group” (FRG).
An FRG in Tanzania can either be a specified district group for lower level facilities or a specified zonal group for hospitals. For example the FRGs are lower level facilities in district A, lower level facilities in district B, hospitals in zone X, hospitals in zone Y etc.
There is a national health facility registry (HFR) in Tanzania, however it is currently not interoperable with MSD ERP. Even when the ERP starts drawing its facility list from the health facility registry (HFR), there may be some human steps involved in verifying the facility by MSD. Once it goes “live” in the ERP, it should also go live in OpenLMIS so that the facility lists are always in sync.
See also sections of the document “System requirements specifications for eLMIS interface with mSupply” which discuss import of facility lists. (see open questions)
Side Note:
In the past, Tanzania used to divide the groups up more, in order to allow for different schedules for lower level facilities in the same district, but now Tanzania follows a system where all lower level facilities in a district operate on the same ordering schedule.
Josh: This feature should be addressed by this epic in JIRA: .
# | Title | User Story | Label | Importance | Notes |
---|---|---|---|---|---|
1 | Facility list update from ERP | As an administrator I want facility lists in OpenLMIS to be updated in line with updates to facility lists in the MSD ERP so that there are not errors during other OpenLMIS-MSD ERP data exchanges. | MSD ERP | Must have | Per Tanzania gap analysis document: This will involve an automated import into OpenLMIS, followed by an OpenLMIS administrator manually going through the changes and adding any additional information/configuration which is not available in the ERP." |
2 | Facility list update review | As an administrator I want to be able to manually review facility list changes and add additional information or configurations which are not available in the MSD ERP. | MSD ERP | Must have | |
DHIS2 | |||||
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 | Should facility list updates always go through a manual validation and update process? | ||
2 | Need for adding in "System requirements specifications for eLMIS interface with mSupply" on import of facility lists. | Communicate the decision reached | Open, In Progress, Closed, and date of closure |