2019-02-21 Meeting notes - Stock Mgmt Source&Destination Lists

Date

Feb 21, 2019

Participants

• @Josh Zamor

• @Wesley Brown

Goals

• Level set on what we want with Stock Management Sources and Destinations

• Lay-out our options

Discussion topics

Notes

Stock Management Organization

Background:

• Introduced by Stock Management team to account to help with tracking sources and destinations of stock movements.

• An Organization is a predefined name. No other attributes.

• In issue and receive workflows, the user is given a list of either valid sources (where stock comes from in the receive process) or valid destinations (where stock has gone to in the issue process). These lists are separate from one-another and are defined by facility type and program (e.g. all District Warehouses have a source and destination list for the vaccine program).

• Tickets from original team:

  • Epic: OLMIS-623: Electronic version of a stock cardDone

  • Source lists: OLMIS-633: [API] Configure valid sources for ad hoc receiptsDone

  • Wiki page of meetings: https://openlmis.atlassian.net/wiki/x/gwCDBg

Problem:

• Stock Management configuration is half-done:

  • The source and destination lists have no UI, and can’t be managed by CSV upload (ref data seed tool)

  • New nor deactivated/removed facilities are not automatically added to the source or destination list. The configuration management is wholly separate and a new concept.

  • Organizations are a new concept, with no UI, and can’t be managed by CSV upload (ref data seed tool).

• Interoperability

  • Organizations as defined aren’t interoperable. We’d need to reconcile this new concept with one from an interoperability standard such as FHIR’s Organization or Location - likely the latter.

Solutions:

• Source and destination list configuration

  1. Add ability to manage lists via Ref Data seed tool

  2. Add UI screens

  3. Rip out source and destination lists?

• Organizations

  1. Rip out / ignore Organizations

  2. Add ability to manage via Ref Data seed tool

  3. Add UI screens

  4. Convert concept to FHIR Location for interoperability (DHIS2, GS1, etc)

  5. Redefine all stocking locations in Stock Management in terms of Locations (this also helps with being able to do sub-facility stock management).

• Facility Management

  • Do we want to make it easier to manage source and destination lists as facilities are added / deactivated?

Work plan options (WIP)

1. We define what we want, and slate a release for it

   1. Easiest solution to src/dest list

   2. Suss out does Angola want Orgs and what’s the lowest LOE

   3. If Orgs are needed, we might need to evaluate the more ideal solution for Locations

2. We define what we want, negotiate what upcoming implementation can tackle, they work on it?

3. Some mix? Other options?

Action items

Decisions