Office of HIV/AIDS High Frequency Reporting Guidance

Transcript

1. High Frequency Reporting Guidance Overview 5/17/2019
2. The current PEPFAR quarterly reporting cycle does not allow OHA/HQ or Implementing Partners to have the data they need to diagnose and take effective action in order to course correct in a timely way
3. Solutions Fully implement routine data use for decision making at the partner level Implement collection of key indicators to measure performance Increase the frequency at which the data are collected, analyzed, and acted upon Engage with USAID mission and HQ teams on performance analysis
4. HFR GUIDANCE
5. Reporting Frequency Before Quarterly reporting to DATIM Now Weekly reporting to mission and HQ Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
6. Reporting Frequency monthly reporting* results broken out by week* Now Weekly reporting to mission and HQ Q1 Q2 Q3 Q4 * MMD collected and reported monthly
7. Indicators HIV testing volume HTS_TST New enrollments on treatment TX_NEW VMMC services completed VMMC_CIRC Multi-month dispensing HIV positive testing volume HTS_TST_POS Current cohort on treatment TX_CURR Newly initiated on PrEP PrEP_NEW
8. HIV testing volume HTS_TST New enrollments on treatment TX_NEW VMMC services completed VMMC_CIRC Multi-month dispensing HIV positive testing volume HTS_TST_POS Current cohort on treatment TX_CURR Newly initiated on PrEP PrEP_NEW total disaggregated # of patients receiving 2, 3, 4 or 5, or 6 month ART dispensing Level of Reporting age/sex not required
9. Level of Reporting reporting to occur at level of entry into DATIM facility community
10. Structure Loose but Strict kind of agnostic to format must meet required element
11. Structure Mechanism ID Partner Name Operating Unit Facility/Community Name Facility/Community UID Collection Period Start Date Indicator Name Unique column Header Names No Merged Cells Zeros Rather Than Blank Cells Only One Data Table Per Tab Include a Data Dictionary Consistent Structure Avoid Calculations Dates in ISO 8601 Code Format YYYY-MM-DD populated directly from DATIM collection/reporting template submission formatting REQUIRED ELEMENTS
12. Structure EXAMPLE flat file output from MIS is the ideal format all elements included as columns in one long table
13. Structure EXAMPLE example collection/reporting template with a tab for each site each site on its own tab site UIDs pulled from DATIM ISO 8601 code formatted date data dictionary & country/mechanism info tabs despite the headers being over 3 lines, unique column names for use in row 4
14. example collection/reporting template with a tab for each indicator Structure EXAMPLE each indicator on its own tab each week is its own column data dictionary & country/mechanism info tabs indicator also included in table, not just tab name
15. Landscape review of current MIS and resolve issues, eg site lists, indicator names Document a timeline for alignment and data reporting calendar Produce a dataset of weekly reporting each month based on the HFR requirements & submit to OHA based on reporting calendar Integrate USAID staff (mission and HQ) in your routine analysis of these data Process
16. oha_hfr@usaid.gov Support
17. Notes and Attribution • Prepared for the OHA Implementing Partners High Frequency Reporting Meeting (DC), May 17, 2019 • Image Sourced from the Noun Project ◦ Alarm Clock by Rakhmat Setiawan ◦ Traffic Light by andriwidodo ◦ frequency by Ahock ◦ collaborate by Iconographer ◦ Clipboard by Grafix Point ◦ Puzzle by indra anis ◦ Binoculars by naim ◦ Calendar by MRK ◦ Data by Creative Mahira ◦ collaborate by Iconographer ◦ support by Icon Island