2020-01-13 Aggregate/Batch Requisition Requirements
Date
Jan 13, 2020
Participants
@Felimone Amone Junior
@Matthew Kumbuyo (Deactivated)
@Chongsun Ahn (Unlicensed)
@Christine Lenihan
@Ben Leibert
Notes
SELV’s current workflow involves having facilities submit requisitions to their districts which, in turn, create and submit new (aggregated) requisition to their overlying province. Because OpenLMIS already supports batch requisitions, however, we’ve been thinking of instead using them within Mozambique.
Mozambique’s version of batch requisitions would differ from the Core’s however. Rather than allowing users to manually choose up to 10 requisitions to batch-approve, Mozambique’s version of the system would automatically present aggregated totals for every facility in any given district. District users would review/approve these aggregated values per district, as would provincial users. (This comports with second screenshot on the related meeting page.
Provincial users may want to approve entire province at once, and the current mockups support this. Seeing the requests for every district within a province is fine - there's no need to subdivide the districts for individual review.
Our minimum requirement is be able to simultaneously see/approve the set of requisitions for a district. Being able to review/approve multiple districts at a time would be nice but isn't strictly necessary.
There are 12 - 15 facilities in most districts. Meanwhile, the largest district only has about 15 facilities.
Even accounting for the changes described at out last meeting, it seems as though batch requisitions will likely meet our short and longterm requirements with significantly less developmental effort than would be required to implement aggregate requisitions. This is good given that the Core team is unsure that aggregate requisitions belong within the product. Requisitions have always been associated with specific facilities, and there’s a lot of uncertainty about what the hypothetical design of aggregate requisitions would look like.
Although SELV doesn’t currently include cost values, we should include them within our implementation of the batch approval screens.
