[v3.1] Stock Management: Lot Management
- Rachel Powers (Deactivated)
Goals/Scope
Lot management is being included in OpenLMIS v3.1, so the goal of this requirement page is to identify what vaccine-specific functionalities/features need to be added to support the vaccine module. The description of the 3.1 lot management requirement can be found here: Lot Management for Stock Management Service
Background
Vaccines vials can be separated from their original packaging, but many of them still contain their lot number (even if they no longer have their barcode). However, with a large number of vials that can come from multiple lots, it is not always the practice for facilities to log lot numbers of specific vials. In Mozambique, for instance, in case of a recall, the central level can disseminate the recall information to the facilities, and it is then up to the store room managers of the facilities to look through and find any vials from that recalled lot. It may often be the case that these vials from different lots are not recorded into the system with their lot information. In the Moz system it's not important for non-central users to add lot information into the system because they are not even tracking the lots of the vaccines that they receive from mixed-lot shipments.
More on this background can be found in Vidya's comment on SELV bar codes: SELV-306 - Getting issue details... STATUS
During the Moamba district distribution run, I made note of the following:
1. The cardboard boxes containing the vaccines have BOTH lot numbers and bar codes.
2. PCV is the only vaccine whose vials have both lot numbers and bar codes on the vials. One issue (you can see it in the picture attached) is that the lot numbers get smudged due to water exposure and people handing the vials.
3. All others (BCG, Measles, Tetanus, Polio, Penta) have only lot numbers on the vials. No idea about HPV.
Within the fridge, the boxes are stored as is or as single vials in a tray (see fridge picture, to the left are the vials in a tray and to the right are the boxes). This then creates a problem because the vials in the tray could come from more than one box, so how to keep track? Similarly, out of box of 100 vials, 20 vials could go to HC1, 10 to HC2, 30 to HC3 and so on. One option is to track the bar codes and lot numbers up to a delivery zone and leave it at that. In case of a recall, it gets traced to the delivery zone level, and the HCs within it are asked to check if they have those vials and to discard accordingly.
Assumptions
User Stories
| # | Title | User Story | Label | Importance | Notes |
|---|---|---|---|---|---|
| 1 |
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 the vaccine system, should users other than the central level be allowed to add lots? Or does everything need to be centralized? Vidya Sampath | ||
| 2 | How often does 3rd party vaccine product come into a facility's stock? What is the preferred way for this outside stock to be entered in the system? Vidya Sampath | ||
| 3 | Is it more important for all the lot information to be tracked, or more important for the central level to have ultimate control? Vidya Sampath |
Out of Scope
OpenLMIS: the global initiative for powerful LMIS software