1. DATIM4U

2. DATIM4U Session Outline
Topic
1. DATIM4U - The Big Picture
2. Experience from the Pilot Country
3. Process Flow, Functionality, Customization
4. Considerations for Implementation
5. Architecture

3. Learning Objectives
This session is meant to inform you about DATIM4U and the Interoperability environment so that you can:
Understand what it is and what it does
Assess its relevance to you
Decide if DATIM4U is worth further discussion with MoH and/or within your USG country team
Take next steps in a cost/benefit determination

4. Key Features
DATIM 4U allows Country Teams/OUs to collect and analyze data in addition to that available in DATIM (aka custom indicators)
DATIM4U is a platform for data exchange with MoH (more on this shortly)
DATIM4U simplifies the data synchronization required to operate an in-country M&E system (data exchange OUs)
DATIM4U provides OUs who opt for it to have full system control and data stewardship

5. Which Approach is Right 4U?
Centralized Web-based Interface
Locally-implemented System
Allows customization addressing country- specific data needs
OGAC assumes full system management burden
OGAC ensures data entry tools support requirement changes
Provides a pathway for eventual integration with MoH
DATIM4U
Does not address additional country-specific data needs
OGAC still ensures data entry tools support requirement changes
Does not integrate with local MoH
Country Team assumes full system management burden
9/17/2018

6. Key Features
Preconfigured with the data entry forms needed to collect MER Indicators
Data entry forms can be extended locally to add Indicators as needed.
Automatically synchronizes local changes with DATIM Global including:
PEPFAR site lists/Org Hierarchies
Implementing Mechanisms
Updated versions of indicators and disaggregates.
Incorporates Open HIE Interoperability standards and profiles
9/17/2018

7. DATIM4U – The Long Game Goal is to ‘collect once, reuse frequently’
One virtual HIV system
uniform visibility and consistent numbers
But - different organizations have different needs
PEPFAR and MoH have overlapping, non-identical reporting needs
This requires a ‘configurable/extensible’ solution
DATIM4U is the first piece of a ‘distributed architecture’ solution addressing this need

8. Map of InterConfiguration Exchanges

9. DATIM4U – The Long Game
The previous diagram identifies the following trading partners:
MoH, IPs, OUs and DATIM Global
Data can be exchanged between:
MoH and OUs; MoH and DATIM Global
IPs and MoH; IPs and OUs; IPs and Global
OUs and Global
DATIM4U supports OU–to-Global but the other configurations are planned
Each configuration shares a common core

10. DATIM4U Common Core: OpenHIE

11. PEPFAR worked with OHIE to Extend the Core
OpenHIE now supports Interoperability between full-scale HIEs
DATIM Global is now a fully configured IHE standards compliant HIE
So is DATIM4U
So are a significant number of Ministries

12. DATIM4U – The Long Game This means that:
PEPFAR can currently synchronize changes in hierarchies and facilities between trading partner HIEs
PEPFAR could added HCWs to the HIE registries via IHE-compliant systems like iHRIS
There HCWs could be associated with facilities in DATIM
And changes can be synchronized with MoH
Or any HIE that implements the Extended OHIE Common Core

13. DATIM4U
2. Experience and Thoughts from the Pilot Country

14. Benefits
The opportunity for additional data gathering and tracking of indicators not reported to OGAC or dropped MER indicators of interest to the in-country team
The possibility of collecting OGAC data requirements that are not in the National systems e.g. KP, PP, additional disaggs etc. hence eliminating administrative responsibility for multiple systems
Possibility of MoH DHIS2 direct data exchange with DATIM4U
Allowing data synchronization between DATIM4U and DATIM Global and the local instance (DATIM4U)
The ability for more routine data collection and cleaning and ability for data review by USG and IPs before final submission
Pre-built functionalities for enhances data collection and reporting

15. Key considerations
Need to have a team with capacity and that is dedicated to support DATIM4U.
Agree on system administration roles and levels of access to the system providing guidance on the role of M&E agents;
Need to determine the data needs and systems requirements.
Need to discuss and agree on the mode of Data entry into DATIM4U .i.e direct exchange Vs manual data
Need to know that the more extra indicators are added the more complicated to
Need to have BUDGET to support these activities

16. Challenges Change in indicator reporting requirements
For some users, there were difficulties with accounts (log in and access to some data sets e.g. interagency datasets)
Some users did not know the difference between DATIM Global and DATIM4U and associated log in
There was need for routine interaction between OU and HQ leads which mean use of media such as skype and GoToMeeting. These are not allowed on the state systems leading to challenges keeping up. Sometimes personal tools were used to undertake these coordination, follow up and supportive interactions.

17. Challenges continued
Limited access to the backend and system configuration apps by the country team. This is more with non-USG staff and yet they are more technically grounded to support the system in-country.
No access to apps like genie.

18. DATIM4U
3. Process Flow, Functionality,
Customization

19. DATIM4U at a glance
To the average user, DATIM4U will not seem any different from DATIM
Has similar login page
Includes most of the DHIS2 apps used on DATIM: Data entry, Pivot, Data approval, User Administration, Etc.
Includes country’s org hierarchy, has same MER datasets available in DATIM
But…
Has some distinct apps, including DATIM4U-specific Data submission app
Includes favorite synchronization service
And DATIM4U management team will have the additional responsibilities!

20. Process flow
DATIM4U includes MER data sets (Targets and Results), and data entry and import/export apps
Same workflow as in production:
Dedupe
Data approval
Quarterly data submission
And automated process for Resubmissions
Results/status message of data submission issues will be displayed, allowing follow-up actions to be taken

21. Mechanism import
DATIM4U uses same service for importing mechanisms as DATIM
Changes in FACTS info show up in DATIM4U after 7PM EST daily, same as in production
Funding mechanism code lists are the same on DATIM and DATIM4U, if you import data into DATIM4U you can use either UID or CODE

22. Synchronization of Favorites
Publicly shared favorites created on DATIM that are applicable to DATIM4U are synchronized from DATIM to DATIM4U daily

23. Data Submission App - key features
Access to the app is managed by assigning role to users who should be able to submit data;
Also has read-only role, for users who can see transaction history, but not initiate submission;
Submission is a two step process: select type (results or targets) and click Export;
Site updates are sent prior to data;
Data approval is validated, to ensure all mechanisms are approved;
Process has been optimized and submission takes minutes

24. Data submission app

25. Data Re-submission
For data entry countries, data cleaning requires updating all data relevant data values via UI;
For import countries, prior to re-submission, deletion file is required to process re-import;
For DATIM4U, you are not bound by PEPFAR opening date, and can start cleaning early (bound only by submission). Submission is a seamless process: DATIM4U has built in feature to delete previously submitted data and submit updated data without extra steps

26. User Accounts in DATIM4U
User accounts will be newly created
DATIM
The country's Agency and Inter-Agency users will continue to have 'read only' access to DATIM
Partner's DATIM accounts will be deactivated
User Support
While ZenDesk and the DATIM Support app will be available to USG users, support for DATIM4U partners will be managed by the in-country team

27. DATIM is the PEPFAR’s Official Source of Data
It is important to remember that DATIM is the official source of data for PEPFAR, regardless of what is in DATIM4U
the country is responsible for ensuring the data in DATIM is correct
The country team will need to know how to facilitate proper data cleaning within its DATIM4U environment to accommodate data modifications

28. System Configuration
The Country will be responsible to configure the DATIM4U reporting periods to remain in alignment with PEPFAR's calendar and reporting timelines.  
Configure the open and close dates for data entry periods
Approval app
Deduplication
This involves configuring the ‘expiry dates’ for the applicable datasets (forms) and DHIS2’s internal ‘datastore’ for the Deduplication App

29. Many Ways to Customize DATIM4U
MoH HMIS
IL (Interoperability Layer)
Indicator Mapping
DATIM4U
Partner HMIS …
Custom reporting cycles
File import
Manual data entry
Custom indicators/forms
Mobile data collection

30. DATIM4U
4. General Considerations

31. Questions to Ask When Considering D4U…
Why do we want DATIM4U?
What would the impact be?
What do we need to have in place?

32. Question 1 - Why do we want DATIM4U?
Adding custom indicators
Allowing for monthly data collection
Increase control
Enhanced data compilation & submission processes
Enhancing ability for data analysis
Incorporate additional DHIS2 apps and features
Build interoperability with external systems
MFL, MoH HMIS, EMR, Partner Systems

33. Question 2 - General Impact
How would envisioned customizations impact our current processes, general usage and overall management?
Customizing for improved data analytics
Customizing by creating your own indicators and data entry forms
Customizing to populate your PEPFAR indicator results from other sources
etc…

34. Question 2 - Impact on Process
Web Form Entry
DATIM
Manual Entry
DATIM4U
File Import
External Data Source
External Data Source
External Data Source
Data Collection
Data Validation/Correction
Data Approval
Submission

35. Question 3 - What do we need to have in place?
Understand the additional responsibilities and roles needed to manage and maintain DATIM4U
Consider the availability of people and the needed skill sets and experience
System and Data Governance structures
Available funding …

36. Trade-offs
Operation and maintenance of DATIM4U is a complex technical undertaking that can have significant cost implications. Each OU should determine if, and when, moving to DATIM4U makes sense for you.
There is a lot that can be done, but there is also a lot that goes into making these systems successful

37. DATIM4U
5. Architecture

38. DATIM4U Architecture Main component is DATIM…
Country specific DHIS2 system
Based on DATIM
Datasets are managed by PEPFAR team
With Open Health Information Exchange (OpenHIE)
Framework made up of open-source components interacting to bring together information from various systems
Leverages health information standards
And is extendible to include additional OHIE components as needed

39. OpenHIE Architecture

40. DATIM4U and DATIM Global
Targets & Results (ADX)
IL (Interoperability Layer)
IL (Interoperability Layer)
OU Hierarchy (CSD)
DATIM4U
DATIM
Dev Team
FACTS Info (Mechanisms)

41. OpenHIE and DATIM4U System Components
IL (Interoperability Layer) – OpenHIM - orchestration of communication
ILR (Interlinked registry) – OpenInfoMan - supports metadata exchange transactions
HMIS (Health Management Information System)  - DHIS2
FR (Facility Registry) – also DHIS2
Data Sources
Mechanisms (partners) are managed by the FACTS Info system, managed by ILR
DATIM4U implementers manage their country’s site data

42. OpenHIM

43. OpenHIM Currently supports Ubuntu Open source Developed in node.js
Standalone mediators provide micro services, that can process transactions
Flexible and configurable, however addition of new mediators requires understanding of OpenHIM and knowledge of node.js
There is a library of standard based mediators for various tasks

44. OpenInfoMan

45. OpenInfoMan Care Service Delivery (CSD) profile implementation;
Uses XQuery and RESTXQ;
Open source;
Runs on Ubuntu;

46. ADX – Aggregate Data Exchange format

47. ADX XML based (SDMX to be more specific) format;
Standard, developed by IHE
Supports aggregate data representation;
Supported as import and export format in DHIS2;

48. ADX workflow

49. Summary

50. Summary In today’s session we discussed DATIM4U - The Big Picture
Experience from the Pilot Country
Process Flow, Functionality, Customization
Considerations for Implementation
Architecture

51. Next Steps…
If the DATIM4U advantages look as if they address some of your current challenges, then:
Initiate an assessment to determine whether this course of action makes sense
You may refer to DATIM Support Resources page to find our DATIM4U assessment forms
Contact SGAC through DATIM Support indicating your interest

52. Questions?

53. Thank You!