09 – Strengthening Information Systems and Linkages to Care

4.1 Plan

The first step to building (or buying) an optimal information system for TB management is to plan. Section 5 of this field guide outlines the resources needed to create and run these systems; it is important to ensure that those resources are in place or can be made available when needed as the system is developed and deployed, and enters maintenance phase. While Section 2 outlines the various features and characteristics of an optimal system, it must be understood that context and available resources will often determine what can and cannot be built (or bought). Some components may already be in place, while others will need to be built from scratch. Those components that are in place may not be functioning well and may require changes and enhancements. Multiple stakeholders should be consulted in the planning phase (see Table 2 below). Careful planning will enable systems to mature over time when resources are available and ensure that the minimum set of features needed for a TB programme to use the system effectively are available from the outset. Since this minimum will vary by country and context, programmes will need to decide on their priorities and plan accordingly.

Table 2. Inputs from different stakeholders when designing an information system

Stakeholder

Type of Input

NTP management Buy-in for the system, TB programme priorities, funding and timelines, ownership of data. If the system is being funded by private or donor sources, NTP agreement to take ownership of the system in some agreed timeframe
TB Technical Experts and M&E staff Data dictionary, content and content validation, programme workflows, indicators, reporting requirements
Lab Management (e.g. from NRL and other labs) Sample collection and test recording workflows, lab indicators and reporting, diagnostic device connectivity
Implementation teams Field constraints, e.g. terrain, network connectivity, power constraints, field team workflows and management structures
Software Developers Building or configuring the system. Must be aware of the system scope and requirements
NTP IT Staff Planning server hosting and (where needed) system handover processes
Field Staff, GPs, Lab Technicians Identifying pain points with current system, as the ones who use it every day. User interfaces and data workflows must make things easier for these users for the system to succeed.