TB Monthly Configuration Guide

Introduction

The electronic monthly report form for TBL medicines was designed to provide logistics information for supply chain managers . It shall monitor the flow of medicines from the district to health service delivery points (SDPs) that distribute medicines to end users. The form shall help supply chain officers easily determine which facilities are under stocked or overstocked, review trends in consumption on a product-by-product basis, identify facilities with potential TB and Leprosy medicines management problems, and plan redistributions and deliveries to facilities.

Requirements

  • Access to the application's administrative panel.

Configuration steps

  1. Create new “TB Monthly” program in “Programs” page.

Zrzut ekranu 2024-05-09 094635.png

 

  1. Create new “TB Monthly” requisition template in the “Requisition Templates” administration sub-modal. Add previously created program and assign any facility types.

Zrzut ekranu 2024-05-09 094552.png

 

  1. After redirecting to the “Configure Template” page, navigate to the “Template Settings” tab and select the “Enable Patient(s) Tab” checkbox.

 

  1. Navigate to the “Template Columns” tab. Leave the "Display" checkbox checked next to the following columns:

  • Skip

  • Product code

  • Product

  • Stock on hand

  • Remarks

  • Total received quantity

  • Total losses and adjustments

  • Unit/unit of issue

  • No of Patients on Treatment next month (C)

  • Total Requirement (E) E = C * D

  • Total Quantity Needed by HF (F) F = E * 2

  • Quantity to issue (G) G = F - A

  • Quantity to issue (converted to unit of measure) G/U

  • Individual Monthly Requirement (D)

 

  1. Change the names of the following fields in the "Label" column:

  • Product code -> MSD Code (not required)

  • Product -> Medicine Name (not required)

  • Stock on hand -> Stock on hand (A)

  • Total received quantity -> Quantity Issued

  • Total losses and adjustments -> Loss & Adjustments (B)

  • Unit/unit of issue -> Unit of measure (U)

 

  1. Change the definition of the "Quantity Issued" in the "Definition" column:

  • Total quantity received in the reporting period. This is quantified in dispensing units. -> Quantity Issued

 

  1. Set the following order of columns by using the move option (first column of the template table) and save the template then:

  • Skip

  • MSD Code

  • Medicine Name

  • Unit of Measure (U)

  • Stock on Hand (A)

  • Loss & Adjustments (B)

  • No of Patients on Treatment next month (C)

  • Individual Monthly Requirement (D)

  • Total Requirement (E) E = C * D

  • Total Quantity Needed by HF (F) F ß= E * 2

  • Quantity to Issue (G) G = F - A

  • Quantity to issue (converted to unit of measure) G/U

  • Quantity Issued

  • Remarks

  • <other inactive columns>

 

  1. Assign the “TB Monthly” program to all facilities that will be using TB Monthly. This can be done under “Edit Facility” page.

 

  1. Assign the “TB Monthly” program to requisition groups. If needed create new one.

 

  1. Add the following medicines in the “Products” administration page (if not existing yet). Make sure to add TB Monthly program into medicine’s settings.

Product Code

Product Name

Individual Monthly Requirement

10010510AE

Rifampicin + Isoniazid + Pyrazinamide + Ethambutol Hydrochloride (RHZE) Tablet 150/75/400/275 mg

112

10010508AE

Rifampicin + Isoniazid (RH) Tablet 150 + 75 mg/mg

112

10010110AE

MB BLISTER ADULT Tablet - -

1

10010515AE

Rifampicin+INH+Pyraz (RHZ) Tablet 75+50+150 mg

112

10010233AE

Ethambutol Tablet 100 mg

84

10010514AE

Rifampicin+INH (RH) Tablet 75+50 mg

112

10010113AE

MB BLISTER CHILD Tablet - -

1

10010114AE

ISONIAZID BP 100MG TABLETS Tablet 100 mg

56

10010315AE

Isoniazid Tablet 300 mg

28

 

  1. Assign TB Monthly program to the requisition user roles.

 

Additional notes:

  1. Dependency of the “No of Patients on Treatment next month (C)” for medicines, with values entered in” Patient(s)” tab

 

 

  1. The TB Monthly form is not converted to an order, the flow ends on the approval stage.

Functional Documentation

https://openlmis.atlassian.net/wiki/spaces/OP/pages/2526347364

OpenLMIS: the global initiative for powerful LMIS software