Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Target releaseTBD
Epic
Document status
DRAFT
Document owner
Technical Lead


Goals/Scope

For facility lists in OpenLMIS to be updated in line with updates to facility lists in the ERP so that there are not problems importing orders from OpenLMIS to the ERP and to facilitate 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

Background

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 in Tanzania, however it is currently not interoperable with MSD ERP.  Even when the EPR starts drawing its facility list from the health facility registry, 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:

Assumptions

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.

User Stories

#TitleUser StoryLabelImportanceNotes
1Facility 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 ERPMust 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."

2Facility list update reviewAs 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 ERPMust have

Diagrams


Dependencies

DescriptionLink


Open Questions

Below is a list of questions to be addressed as a result of this requirements document:

#QuestionOutcomeStatus
1Should facility list updates always go through a manual validation and update process?

2Need for adding in "System requirements specifications for eLMIS interface with mSupply" on import of facility lists.

Out of Scope

  • No labels