UNDP Jobs – 107605- Provision of technical expertise in development of

Scope of Work

The scope will cover the development of a National Dashboard for laboratory tests done in Zimbabwe

Detailed Scope of Work

Device Management

The dashboard system should maintain information of individual devices that are used in diagnosis testing. The device management allows for all tests to be linked to a device over time. Users with authority may create, modify or delete devices.

1. The system maintains list of device profiles
2. The device profile consists of all or some of the following, but not limited to
3. A unique identifier  (System generated)
   1. Asset number (MOHCC generated)
   2. Serial number
   3. Device name
   4. Device model

Health Facility Profile Management

Health Facilities are either Laboratories, Hospitals or Health Centers that offer laboratory testing either using conventional machines or using point of care machines or bedside testing. The dashboard system keeps a record of all providers that have the ability to offer afore mentioned services.

1. The system maintains list of Health facility profiles
2. A health facility may be a clinic, a hospital, a health center or another laboratory, etc.
3. The provider profile consists of, but not limited to, the following
   1. A unique health facility identifier (Generated by MOHCC)
   2. Health facility name
   3. District
   4. Province
   5. Geo coordinates
   6. Physical address
   7. Telephone number
   8. Email address
   9. Contact person(s)

1. The system allows authorized users to manage health facility profiles.

Test Catalog Management

The dashboard system manages all the tests and procedures that are carried out by the health facility on a device by device basis. The LIS should allow for tests to be added, deleted or modified from the Test Catalog.

1. The system maintains one or more catalogs of all the offered testing services, i.e. tests.
2. Tests may be grouped in one or more categories and sub-categories in a catalog
3. A catalog test entry consists of, but not limited to, the following:
   1. A unique test identifier/code
   2. Test name
   3. Category name
   4. Subcategory name
4. The system allows authorized users to assign one or more test catalogs to health facility or device
5. The system allows authorized users to manage the test catalogs
6. The system allows authorized users to import the test catalogs.

Scheduling Management

The system should allow users to configure scheduled events which will run at set intervals or triggered by particular events.

The triggers may include, but are not limited to

1. Scheduled emailing of reports to set users
2. Email notification upon a particular event such as QC failure or equipment error threshold
3. Add request and sample received and accepted to specific test schedule
4. Non-reporting over a set period of time

Report Management

The dashboard system will generate reports in electronic format to authorized users. These reports will be stored or generated ad hoc and will allow the user to view tests done, tests ordered, Quality control, rejections, TAT, etc.

The users will be able to define the types of reports they need following the WHEN, WHAT, WHERE approach. The approach allows the users to specify the data to show (WHAT), for which facility (WHERE) and for which period (WHEN). Examples of reports that the system should be able to produce are

1. Facility reporting summary Report

1. The report will show a list of devices with the following information
   1. Instrument name
   2. Instrument identifier (S/N, etc.)
   3. Last test date
2. The system should allow the user to filter the list by
   1. Facility
   2. District
   3. Province
   4. Device category
   5. Date filters such as reported in the last X days, performed tests in the last X days, not reported in the last X Days

1. The system should allow user to export the list to , but not limited, the following formats
   1. CSV
   2. XML
   3. PDF
   4. JSON

2. Facility list

1. The report should list all facilities in the system indicating
   1. Facility name, district, province
   2. Instrument available at the facility
   3. Date when each device last send data
   4. Date when device last performed a test
   5. Reports can be either displayed (viewed on a monitor) or printed
2. The system should allow the user to filter the list by
   1. District
   2. Province
   3. Instrument category
   4. Date filters such as reported in the last X days, performed tests in the last X days, not reported in the last X Days
3. The system should allow user to export the list to , but not limited, the following formats
   1. CSV
   2. XML
   3. PDF
   4. JSON

3. Suppression rate report

The aim of the report is to allow the user to evaluate a proportion of HIV positive patients achieving viral suppression. The system should therefore enable the following

1. Determine the viral suppression target
2. Specify age stratification categories
3. Specify gender stratification categories
4. Specify other stratifications (case information) e.g. pregnancy, breastfeeding, drug regimen
5. Specify location stratification categories
6. Categorize by submitting clinic

4. Rejection rate report

The aim of the report is to allow the user to evaluate the proportion of samples received that were rejected. The reports should

1. Show number of samples received during a specific period
2. Show number of samples rejected during a specific period
3. Percentage of samples rejected (a/b X 100%)
4. Categorize rejections by rejection reason
5. Categorize by facility, district or province

5. Invalid result rate report

The aim of the report is to allow the user to evaluate the proportion of samples tested and had invalid results. The reports should

1. Show number of samples received
2. Show number of samples tested
3. Show number of samples with invalid results
4. Percentage of samples with invalid results
5. Invalid results by device
6. Categorize by facility, district or province

6. Invalid result rate report

The aim of the report is to allow the user to evaluate the proportion of samples tested and those which failed. The reports should

1. Show number of samples tested
2. Show number of samples which failed
3. Percentage of failure
4. Failures by device
5. Failures by user

7. Current regimen report

The aim of the report is to allow the user to evaluate regimens being given to patients. The report should;

1. Indicate number of samples received
2. Number of samples tested by
3. Number of valid results
4. Number of patients achieving targets, e.g. positivity for Covid, VL suppression for HIV VL, TB resistance for TB, etc.
5. Categorize patients by different variable, e.g. regimen, reason for test, case information
6. Calculate suppression rate by regimen

8. Testing trends

The aim of the report is to give a view of the number of tests performed per given period. The reports should

1. Categorize tests by sample type
2. Categorize tests by facility level (rural health center, district etc.)
3. Categorize tests by submitting clinic

9. Testing reason report

Clinicians requests for tests due to various reasons. The report give an account of the various justification for viral load testing such as treatment failure, routine etc.

1. Categorize by reason for testing
2. Categorize by submitting clinic
3. Categorize by viral load result or result range or case

10. Turnaround time report

The aim of the report is to measure the amount of time between sample collection and results reporting. This will form basis for improving sample transportation, testing as well as results reporting.  The report should include

1. Number of samples by date collected, registered, received, tested, delivered results
2. Number of results report
3. Number of results reported within defined turnaround time
4. Percentage of results reported within defined turnaround time
5. Categorized by testing facility
6. Categorized by submitting  facility
7. Categorized by instrument

11. Health facility performance report

The aim of the report is to evaluate performance of different laboratories by;

1. Showing number of facilities serviced
2. Samples received
3. Repeat tests performed
4. QA test performed
5. Total tests performed

12. Visualization/GIS Reports

The consultant will be expected to develop visual maps, heat maps, charts, modern map technology

Communication with external systems

The dashboard system should have capability to communicate with other external systems by offering endpoints through Application Programming Interface (APIs).

User Account Management

User Access

1. The dashboard system provide online access to various laboratory personnel
2. Online access to the dashboard system is granted only through dedicated user accounts
3. The system maintains list of user accounts
4. A user account consists of the following components:

1. User Profile – contains user contact information
2. User Credentials – contains user authentication (identity confirmation) information
3. User Role – Defines user authorization and privileges

1. The system allows authorized users to manage user accounts.

User Profile

1. The user profile contain the following contact information
   1. Person full name including last (family), first (given) and middle names
   2. Gender
   3. Tile
   4. Department/organization
   5. The system allows authorized users to manage user profiles

User Credential

1. User credentials consist of the following information:
   1. A unique username and
   2. A unique password

1. The system stores user credentials in encrypted format for security purposesUser Role
2. A user role defines user authorization and should reflect the person’s title/job in the laboratory
3. Example user roles are:
   1. System Administrator – A type of IT operations personnel that configures the system, schedules job runs and backs up the system data
4. A user role represents a list of dashboard features to which the user has been granted access, i.e. privileges
5. Every user account is assigned a user role
6. The system allows authorized users to manage user roles
7. The system allows authorized users to manage user role privileges   

D.           Expected Outputs and Deliverables

1. Stable and working dashboard meeting the functional requirements outlined above
2. Documentation – Technical and User manuals
3. Activity reports and relevant annexes

Documentation

Documentation will include sufficient and detailed documentation for a general laboratory user as well as necessary details for the specialty laboratories as appropriate. The specific documentation guides shall be provided to cover the needs of the following users.

Installation and Administration

The installation guide shall be detailed enough to provide system’s administrators with all of the information necessary to install and bring the application live in a production environment. The documentation shall list all utilities and tools necessary for the proper administration of the system. These tools shall cover management and administration of the system database, the user interface, and any auxiliary programs integrated into the delivered system.

User Guide

Laboratory User documentation shall be sufficient and detailed enough to allow different levels of lab users to perform their functions without having to rely overly much on external support.

System Operator Documentation

This portion of the document is intended for those people who are running the system. It shall include direction for operating the various hardware components, operating the software and, recognizing and correcting problems.

This consists of, but not limited to, the following

1. Software and system operating direction

Hardware operating direction

Timelines for the deliverables/outputs

The work will be performed over a period of 90 working days spread over 3-4 months

E.      Institutional Arrangement

1. The IT LIMS Coordinator will review output and confirm acceptance, directly supervise the Contractor, to whom the consultant will be directly responsible, reporting to, seeking approval/acceptance of output
2. Progress report will be presented at the end of each milestone. There is an option for presenting the report virtually depending on circumstances.
3. The contractor is expected to liaise/interact/collaborate with IT LIMS Team through the IT Coordinator during performance of the work for technical guidance

F.      Duration of the Work

1. The work will be performed over a period of 40 working days spread.
2. MOHCC will is expected to review outputs, give comments, certify approval/acceptance of outputs, etc. with 2 weeks. 

G.     Duty Station

1. Training will be conducted at a venue to be determined by MOHCC

Source