PEPFAR's annual planning process is done either at the country (COP) or regional level (ROP).
PEPFAR's programs are implemented through implementing partners who apply for funding based on PEPFAR's published Requests for Applications.
Since 2010, PEPFAR COPs have grouped implementing partners according to an organizational type. We have retroactively applied these classifications to earlier years in the database as well.
Also called "Strategic Areas", these are general areas of HIV programming. Each program area has several corresponding budget codes.
Specific areas of HIV programming. Budget Codes are the lowest level of spending data available.
Expenditure Program Areas track general areas of PEPFAR expenditure.
Expenditure Sub-Program Areas track more specific PEPFAR expenditures.
Object classes provide highly specific ways that implementing partners are spending PEPFAR funds on programming.
Cross-cutting attributions are areas of PEPFAR programming that contribute across several program areas. They contain limited indicative information related to aspects such as human resources, health infrastructure, or key populations programming. However, they represent only a small proportion of the total funds that PEPFAR allocates through the COP process. Additionally, they have changed significantly over the years. As such, analysis and interpretation of these data should be approached carefully. Learn more
Beneficiary Expenditure data identify how PEPFAR programming is targeted at reaching different populations.
Sub-Beneficiary Expenditure data highlight more specific populations targeted for HIV prevention and treatment interventions.
PEPFAR sets targets using the Monitoring, Evaluation, and Reporting (MER) System - documentation for which can be found on PEPFAR's website at https://www.pepfar.gov/reports/guidance/. As with most data on this website, the targets here have been extracted from the COP documents. Targets are for the fiscal year following each COP year, such that selecting 2016 will access targets for FY2017. This feature is currently experimental and should be used for exploratory purposes only at present.
Years of mechanism: 2014 2015 2016 2017 2018
NOTE: The following is taken from summaries released by PEPFAR on the PEPFAR Data Dashboard. They are incomplete summary paragraphs only and do not contain the full mechanism details. When the full narratives are released, we will update the mechanism pages accordingly.
TB is the most common cause of death among PLHIV in Zimbabwe. In 2011, 76% of registered TB patients with known HIV status were HIV-positive. Despite this, TB and HIV services are in most cases not fully integrated; only 44% HIV infected TB patients receive ART
The project goal is reduce morbidity and mortality among TB/HIV co-infected persons in 9 urban municipalities of Zimbabwe.
The objectives of the implementing mechanism:
• scale up decentralization of TB and HIV diagnostic and treatment services to primary health care clinics in urban areas;
• facilitate integration of HIV diagnostic and care services, including ART, into management of TB suspects, patients and their family members
• facilitate integration of TB diagnostic and treatment services into management of HIV in PLHIV and their family members
• strengthen TB infection control measures in health facilities in urban areas; and
• strengthen recording and reporting of TB, TB/HIV and HIV prevention and care activities
M&E is conducted as an integral part of the NTP M&E system using standard recording and reporting and training tools developed with TBCARE support, support supervision and joint data quality assessment.
Since COP2014, PEPFAR no longer produces narratives for every mechanism it funds. However, PEPFAR has now included performance targets or indicator information for each mechanism based on the Monitoring, Evaluation, and Reporting (MER) system. The MER guidance is available on PEPFAR's website https://www.pepfar.gov/reports/guidance/. Note that COP years 2014-2015 were under a previous version of the MER system and the indicators and definitions may have changed as of the new 2.0 guidance.
This mechanism has no published performance targets or indicators.
