Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Workflow in eLMIS (screenshots from Chris in the comments below):

The requisition split happens when the requisition has been approved by the district. This is the workflow:

  • Step 1: Requisition is submitted and authorized with requested quantities for products (typically the calculated order qty = the requested quantity but it can be different)- user either enters same amount from calculated order quantity into the requested quantity, or different amount into requested quantity. Total cost and packs to ship are updated based on requested quantity. If requested quantity is null then total cost and packs to ship are calculated based on calculated order quantity. The following screenshots show initiating a requisition, entering the same and different amounts in the requested quantity, and the product information to show how pack size is defined. The total cost is zero in these requisitions because Zambia does not have a price per pack in the product details.

Image Added

Image Added

Image Added

Image Added

Image Added


Image Added

Image Added



    • Step 2: District supervisor reviews quantities and can edit the approved quantity. If approved quantity is edited (different than requested quantity) then approved quantity is used to calculate packs to ship and total cost.
  • Image Added
  • Image Added
  •  
    • Step 3: District supervisor approves requisition. Requisition status is In_Approval.
  • (Can the approved quantity be edited?)
    • The supervisor can see the calculated order quantity, requested quantity, and make edits to approved quantities as needed. Total cost and packs to ship should update as approved quantities are changed.


Image Added

Image Added

    • Step 4: Requisition is split (One for standard program, and one for CHAZ)
      • Standard program requisition shows requested qty amounts as zero, approved qty as zero, and packs to ship as zero for the amounts supplied by CHAZ 


Image Added Per the screenshot from Ashraf the view shows approved quantity, requested quantity, packs to ship as they were entered, nothing is zeroed out.

  • CHAZ requisition shows requested qty amounts as zero, but packs to ship displays so that CHAZ knows how much to supply requisition where CHAZ can edit the approved quantity, and then approves the requisition.

Image Added Ashraf or Chris Opit (Unlicensed) can you provide screenshots that show each of the columns approved quantity, requested quantity, and packs to ship for a CHAZ requisition?(Is requested qty only hidden from CHAZ? Is there any trace back to what was originally requested?)

  • Step 5: Customer service center reviews CHAZ requisition and is allowed to edit approved qty, they complete final approval. Standard program requisition goes through normal approval workflow. 
    • Step 6: CHAZ can log in to see status of requisition (what else happens here? if requisition is not approved they can contact whoever is necessary to move the approval along)  This was removed because it is part of step 4.
    • Step 7: Warehouse converts the requisition to an order, the CHAZ requisition is converted to a csv file and then sent to dropbox. Then uploaded into their system automatically.
    • Step 8: CHAZ can log in to see the approved requisition and packs to ship (compare what is uploaded in their system to eLMIS?)   This was removed because it is part of step 4.
    • Outside of eLMIS - Step 9: CHAZ determines how much they will fulfill and fulfills the order
    • Step 10: Released Requisition can be viewed and shows the standard program and CHAZ requisition as one requisition, with comments on products that were supplied by CHAZ.

Image Added

Discussed changes to the workflow based on this feature:

...

  • After Chaz has supplied the facility, we don't know how much was really supplied by the facility (Chris Opit (Unlicensed) is this actually a true statement? If the Proof of Delivery has the actual fullfilled quantity, is that input into eLMIS?) Fulfillment by supply partners is out of scope for this feature.
  • What is the benefit or purpose of zeroing out the requested quantity? Are there any concerns with doing this in OpenLMIS (reporting impact or other problems?) Does understanding what has been requested vs what was actually fulfilled help determine whether the facility is overstocked, stocked out, stocked according to plan, etc?
  • What happens if a requisition is rejected? 

...

Potential development tasks/tickets: (Chongsun Ahn (Unlicensed)Nikodem Graczewski (Unlicensed) this is not a complete list, so please add any other ideas)

  •  Split requisition after first approval Supply Partner model
  •  Administrator configuration screens to configure product lists and supply partners (
    Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-51425353
    )
  •  Determine if there are edge case scenarios that must be supported (for deleting, rejecting, editing approved quantities at each approval step)
  •  Zeroing out requested quantities
  •  CHAZ logging in to edit requisition? edit order? (and authorization to do so)
  •  Administrator configuration screens to configure product lists and supply partners  and related tickets)
  •  CHAZ or other supplier needs access to log in to view their requisition, edit approved quantities, convert to order (Joanna Szymańska (Deactivated) this is not a dev ticket, but should be a testing scenario)
  •  Split requisition after approval (
    Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-5353
     and related tickets)
    5142
    )
    •  Identifier (comment? remark? other?) for each orderable of who supplied?
    •  When requisition is split, and after its approved, the order no is different than the "standard' order no.
  •  Determine if there are edge case scenarios that must be supported (for deleting, rejecting, editing approved quantities at each approval step)
  •  
  •  


    QuestionAnswer
    Why is there approved quantity for CHAZ requisitions?CHAZ just looks at the packs to ship, they don't modify the requisitions.

...

  • They have access/rights to edit approved quantities in their requisitions.
    Does CHAZ approve the requisitions in the eLMIS?They don't, the requisition is converted to a CSV and dropped in the Dropbox.
    Is the process of converting requisition to a CSV automatic in eLMIS?Yes, it is.
    Would it be useful if CHAZ could see the requisition screen and approve specific quantity?

    Yes, the district supervisor might not know what is in the warehouses. Based on screenshots provided by Ashraf this can happen and does already in eLMIS.

    Is there a view for supervisor to display the combined requisition?No, there isn't. The original requisition has requested quantities set to 0 for products supplied by partners and a comment is added to the line item to indicate that.
    Is there a scenario when CHAZ has no supply?

    There might be, but CHAZ is responsible for making sure they can fulfill orders.

    Is the warehouse actually approving? Could they reject?Possible, but rare, warehouse team can change the values in the WMS though (provide X instead of Y quantity).
    Should CHAZ be able to fulfill order through OpenLMIS?

    Not the original goal, but would be really useful.

    If CHAZ could log in to the OpenLMIS, would

...

  • they do it?They actually do for eLMIS. They log in and can edit approved quantities.


Other important notes:

  • Supply partners do not have duplicate product lists, each supply partner has their own discrete list of products they supply to designated health facilities. There aren't scenarios where a product is supplied by more than one partner for the same facility.

...