Embed Size (px)
Citation preview
TrainSMART for Decision Makers
TrainSMART for Decision Makers
Goal of this training:
To prepare I-TECH decision makers to rollout TrainSMART in their country project
TrainSMART for Decision Makers
Training Objectives:
At the end of this training, participants will be able to:
Explain the next steps required for TrainSMART rollout in their country project
Identify resources required for rolling out TrainSMART in their country project
Generate three types of reports in TrainSMART
TrainSMART Background
HRSA and PEPFAR require training data as a condition of our award
Several data collection systems attempted in different countries
I-TECH HQ addressed need for a uniform data collection system through creation of TrainSMART
Case Study
Adopting a training data management system in Nayar: the experience of the Nayar HIV/AIDS National Training Center (NHNTC)
Case Study Objectives
By the end of this session, you should be able to:
Describe the steps taken by Nayar to adopt a new training data management system
List the challenges that Nayar needs to overcome to implement TrainSMART
Case Study TrainSMART
Background
Nayar has 7 different training centers 6 regions.
Since 2005, each center has collected training data and mailed it to a central location, the NCU, for data entry (National Coordinating Unit).
Centers wanted to have better access to their data, the NCU didn’t want the responsibility of data entry, data cleaning, and ad hoc reporting for the Centers.
A nationwide meeting was held to discuss adoption of a new web-based database as a solution.
Case Study TrainSMART
What may have been some of the questions and concerns raised by the centers?
What questions and concerns might the NCU or I-TECH have raised?
Case Study TrainSMART
NHNTC agreed that a web-based database would resolve many of these challenges and opted to implement TrainSMART.
Each training center agreed to hire an administrative assistant or data entry clerk to enter the training data.
NHNTC partners were unwilling to adopt a system that would allow other centers to view or edit their data.
They did not want to lose the legacy data that had already been collected in the database at the NCU, but the data was flawed- many of the fields required for TrainSMART were blank.
Case Study TrainSMART
What are some possible strategies for addressing the concerns raised regarding access to other centers’ data and legacy data?
What might be some barriers to implementing those strategies?
Case Study TrainSMART
NHNTC decided to contract with the database developer to create a customization that allowed the administrator to set permissions at the level of the training organizer.
Legacy data was uploaded to TrainSMART and data quality issues were addressed by inserting “unknown” into all blank fields. The centers agreed to go back and correct essential fields in TrainSMART.
Case Study Key Issues
Setting Permissions
Roles related to data entry
Implications for human resources
How to handle legacy data
Existing data quality issues
TrainSMART Additional Considerations
Required resources Computer, Internet, Data entry person
Where will the site live (hosting) I-TECH servers or In-country servers
Who is responsible for site administration Initial setup, localization, ongoing administration
Customization Enhanced functionality
I-TECH approved developers or local developers
