Already decided to make a site level tool available: work was underway with U of Oslo to: â¦. Add Implementing Partner
Introducing PEPFAR’s new information system
*
◦ Initially launched in 2003 ◦ The largest effort by any nation to combat a single disease ◦ Funded at $15 billion for the first five years ◦ During its first phase, PEPFAR supported 2/7/10 Treatment of more than 2 million people, Prevention of 7 million infections Care for more than 10 million people
Assumption until now was program needed site level data, but program didn't need to collect/maintain it (partners did) MoH knew they needed site level data - and they collected it – creating demand for DHIS2 Newly appointed U.S. Global Coordinator, Amb Birx, agrees with MoH…more on this in a moment…but first:
PROMIS STATISTICS
SAPR 2010
APR 2010
SAPR 2011
APR 2011
SAPR 2012
Prime Partners
54
59
78
127
131
Mechanisms
64
78
112
279
294
Indicators Reported
29
34
34
39
41
Districts Reporting
139
139
141
142
143
Facilities Reporting
3,661
4,426
4,621
5,204
5,404
118
395
456
556
598
87,461
145,988
139,624
226,628
214,623
PROMIS Users Individual Results Reported
This also happens simultaneously in 35 other countries – on a twice-yearly basis at a cost of tens of millions of dollars
Deadline for data is 30 days after the close of the reporting period – twice a year
And all the data are aggregated in Washington within 45 days of the close of the reporting period
This is undoubtedly the most extensive data capture and reporting activity ever undertaken in Low & Middle Income Countries (LMIC)
Ambassador Birx decided PEPFAR would immediately move from a 'cast the net broadly' approach to ‘targeted epidemic control’…this requires knowing specifically where the epidemic is. To achieve this goal, we need data at appropriate levels of granularity: from facility and community level reporting through national and global roll up DHIS2 fit the need
Immediate Mandate: Site level data collection and reporting - beginning now (COP'15)
Already decided to make a site level tool available: work was underway with U of Oslo to: ◦
Add Implementing Partner attribution (mechanisms)
◦
An aside: The Importance of the ‘attribution’ feature to NGOs
◦
Support ‘submit/accept’ work flow from IPs thru to HQ
◦
Designed for use by Implementing Partners and Country Teams
◦
Provides graphical Dashboard and reports needed to support targeting epidemic response
◦
Integrates with MoH and USG Agencies M&E systems
Created PEPFAR Site Lists (Org Hierarchies)
Provided ToT training (December 1-14, 2014)
Built a support network
A word on a ‘reasonable’ timelines
◦ Covers over 50 countries ◦ 65,000 listed facilities/community sites
◦ Trained 200 DATIM Trainers from 24 countries ◦ They will train their Country Teams and Implementing Partners between now and March ◦ Dar Training – ended yesterday! ◦ Trained 30 HISP Network DHIS2 experts in DATIM support and data exchange
This site list can provide the basis for a common site identifier across the NGO community, as discussed later.
Lessons learned from Rwanda pilot 1. Pilot proved to be Essential! 2. Overwhelming burden of administrative tasks (mechanism management, user accounts, site lists)
3. Need for detailed Tech Support SOPs and SLAs
Key Takeaway:
Distributed Admin + Trouble Tickets
◦ User Management ◦ Site management ◦ Mechanism chron file - FACTS Info synch
Creating an M&E Community Support via common shared resources (like the PEPFAR Corner) Making this work central to a comprehensive Information System Strategy
HIS Strategy:
1. Begin to move M&E reporting through host government systems 2. Begin to derive M&E data from patient-centric data systems 3. Assist in defining an Enterprise approach for use in host government system implementation decisions 4. Ensure systems implement data exchange standards needed for system interoperability 5. Link implemented systems to evolve a Health Information Exchange (HIE) infrastructure 6. Work with broader international communities to move towards a shared HIE capability
OpenHIE is standards-based interoperability DHIS2is a fully compliant OpenHIE certified Facility Registry which can share common facility information with any other OpenHIE compliant applications A common Indicator registry is next up on the OpenHIE task list. This should be of great value to all.
