...

Status in OpenLMIS: Not implemented

Priority: High

Goal/scope

The goal is to enable OpenLMIS to split products within a requisition by supply partner, so that each partner only supplies the products they are configured by the administrator to supply.

Background

Requisition Splitting - Extension Scenario Analysis is the background of the OpenLMIS team's assessment of how to achieve this by extensible means.

Currently, the Zambia eLMIS team have built an enhancement which is able to split the products defined by a facility to different defined suppliers. The Ministry of Health relies on MSL for its supplies of products. However,  some other Organisations can also supplement with the supplies and that case referred to as a supply partner. Currently, CHAZ (churches Association of Zambia) has a number of facilities which they supply certain products. In this case, the facilities do the normal requisition process except the system splits out the products so that the intended supply partners are able to view and supply the product.  In that way the, two supply partners cannot supply the same product to the same facility. The supply partners will have to be defined in the system.

In Zambia, Chaz has been defined and apparently serves 59 facilities and 36 products under the ARV program. See picture below.
So when an R&R is sent from one of the defined facilities, the requisition goes through the normal process except it will be viewed by CHAZ if the products being requested are within the products that CHAZ supplies. If some products cannot be supplied by CHAZ, then part of the requisition goes to MSL for supply. In this case, CHAZ will only view what it can supply and MSL can only view what it can supply.  

Assumptions

• Requisition is split after first approval
• Once requisitions are split, they cannot be merged back together
• This feature has been broken out into two epics: 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-4842

   and 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-5642

User Stories

Diagrams

The following screenshots are from eLMIS Supply Partner configuration screens:
Accessing 
Image Modified

See process on adding supply partner
Image Modified

Defining a supply partner. Note the fields involved i.e Source program, Destination program, Supervisory node, Requisition group, Facilities, products and action.
Image Modified


Clicking on facility eg. '59  facilities' will bring the below screen. 

Image Modified   Image Modified

Clicking on product e.g '36 products' will bring screen below

   

Gap Estimation Notes

• Attendees: Josh, Mary Jo, Brandon
• We would build this in core product, not as extension mechanism.
• We would build admin screen to configure which products are supplied by an outside partners.
• This also might be partly supported by product registry.

...