Interface - Facility edition
Merge with Interface - Interface with eLMIS Facility Edition
Goals/Scope
Facilities want to export R&R data from their facility electronic systems into OpenLMIS, to increase accuracy, consistency and reduce administrative burdens.
Status in eLMIS: Not in eLMIS currently.
Status in OpenLMIS: APIs available for client applications to call. Can initiate and submit requisitions. Search SOH.
Priority: Will increase in priority as more facilities use electronic systems.
Additional Notes (Zambia)
Status in eLMIS: in eLMIS currently.
Status in OpenLMIS: Not in OpenLMIS currently
Priority: high priority for zambia
Background
There are a range of general hospital administration systems in use in Tanzania by different hospitals, many of which have some functionality related to management of stocks and supplies and dispensing. Systems in widespread use include GOT HOMIS and AfyaPro. Many hospitals also have parallel laboratory systems such as Labnet and DAISA.
The National AIDS Control Programme (NACP) CTC2 Pharmacy module is an MS Access based system in use in many facilities to manage dispensing and stocks of ARV and OI drugs, linked to the NACP CTC2 database. The NACP CTC2 database itself is in use in more than 900 facilities, but not all of those use the CTC2 pharmacy module.
Facilities generally need to have combined/integrated systems which include stock management together with dispensing, insurance and cash payments management as well as medical records and other features. These systems should be programmed to produce R&Rs as an output, and some already do. Once the R&Rs are produced by these systems, they should then be automatically transferable into OpenLMIS rather than printing from the facility system and entering into OpenLMIS.
Additionally it may be useful for facility systems to export stock status information into OpenLMIS more frequently than the R&R period. This would replace some of the functionality of ILS Gateway in Tanzania.
Additional notes Zambia
Reporting facilities have FE(Facility edition) of eLMIS and therefore send R&R on a monthly basis but also are able to do an emergency requisitions. FE is programmed to produce R&Rs as an output. The system is linked directly to CE (central edition) by form of internet communication. Once the R&Rs are produced by FEs, they should then be automatically transferable into OpenLMIS rather than printing from the facility system and entering into OpenLMIS.
Additionally it may be useful for facility systems to export stock status information into OpenLMIS more frequently than the R&R period just as outlined for Tanzania.
Assumptions
User Stories
# | Title | User Story | Label | Importance | Notes |
---|---|---|---|---|---|
1 | Export R&R from facility system into OpenLMIS | As a facility user I want to export an R&R from my facility system into OpenLMIS to increase accuracy, consistency and reduce administrative burdens. | Tanzania point of care systems / Zambia Facility system | Must have | If the “non-ordering satellite facilities requirements” (defined separately) are implemented, the second bullet below is possible, otherwise only the first bullet below is possible:
In both cases, after authorisation of the quarterly R&R, the R&R would go through approvals in the normal way. |
2 | Export stock status from facility system into OpenLMIS | As a facility user I want to export stock status (stock on hand of each commodity) from facility system into OpenLMIS at any time (more frequently than at R&R time), so that this stock status can be visible to district, zonal and national level users. | Tanzania facility system /Zambia facility system | Nice to have |
Diagrams
Dependencies
Description | Link |
---|---|
Open Questions
Below is a list of questions to be addressed as a result of this requirements document:
# | Question | Outcome | Status |
---|---|---|---|
1 | For Tanzania user stories: review the users, "so thats" added, review the label, and review the priority level. | ||
2 | Ashraf and Alpha Nsaghurwe (Unlicensed) does Facility edition first initiate/call eLMIS and then push the data? What is the error handling if Facility edition trieds to create two regular requisitions within one period? Can we get more information about the order of processing between between the two systems? |
Out of Scope
Gap Estimation Notes 4/12/2018
- Attendees: Mary Jo, Matt, Josh, Peter, Ashraf, Muhammad, Peter, Craig, Brandon, Elias
- History of 'facility edition' provided by Ashraf.
- Facility edition is a separate application. It is used in Zambia, and other countries has expressed interest. It is built with a different toolset and is currently being migrated to a web based platform (in VueJS). It includes features like patient records for HIV/ARV regimens, and bin card/stock card workflows. There is a server in each facility, and thin clients that connect to it.
- At the end of the month, the facility edition syncs with the Central Edition (eLMIS/OpenLMIS). It is a metadata sync, and it creates a requisition.
.
OpenLMIS: the global initiative for powerful LMIS software