-
1. Introduction
-
2. Translating data into action: essential components of a TB recording and reporting system
-
3. Designing an optimal information system
-
4. Recommended process of development
-
5. Resource requirements
-
6. Measuring the impact of the information system
-
References
2.3 Reporting systems
Reports help users at different levels of TB programmes understand how the programme is progressing based on key indicators or metrics. Reports designed for different users will vary in the level of granularity needed. For example, reports designed for an NTP manager would ideally be high-level reports on key indicators for the country and perhaps for individual provinces. Reports for lower level managers in the health system generally require more detail. For example, district TB officers may want to see performance metrics for all of the towns in their district and may be interested in operational details that would be too much information for the NTP manager.
Quarterly reports
It may be most efficient to automate reports that are needed at a set frequency (e.g. quarterly) such that, for example, the Q1 report is auto-generated and available to view on April 1. (It is worth noting that treatment outcomes for the same quarter may only be available in the next one.) For systems in which data are entered offline or retrospectively, however, it is advisable to allow time for users to upload any data not yet entered into the system.
Day-to-day management
Reports for day-to-day management should be available on-demand, with users provided with a visual interface that they can use to generate reports, filter reports based on criteria such as date and location, and sort data as needed. As with other aspects of system development and design, report development is also an iterative process. More or different reports may be needed as programme staff learn more about their own programmes and identify new variables that could be important for assessing programme performance. Similarly, changes to protocol or new developments in TB control can necessitate modifications in the way data are presented. In time, the system can even provide recommendations automatically based on certain thresholds.
Privacy constraints
Regardless of whether a report is automated or generated on-demand, it is important that reports show data in an easily consumable way, but also with appropriate “privacy filters” and patient identifiers so that individual patients cannot be identified when moving to the consolidation and analysis of data. (Issues related to UPIs are explored in more detail in Section 3.2. of this field guide.) This is best done using dashboards with charts and graphs, as well as giving the option to download data in Excel, CSV or other formats for deeper analysis. Business intelligence tools, such as Pentaho, Microsoft BI and Tableau, among others, are often used to create powerful reporting and analytics dashboards. Dashboards can also be used to display geographical data, as described later in Section 3.