1 / 12

COTE D’IVOIRE CASE STUDY

COTE D’IVOIRE CASE STUDY. Steven Yoon A. Salam Gueye Catherine Seyler Mike McKay Laurence E. Aka. No Infrastructure for Computer. No Infrastructure for Computer. Three years down the road. District User. National Data Repository. No Internet. No Infrastructure for Computer.

aricin
Download Presentation

COTE D’IVOIRE CASE STUDY

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. COTE D’IVOIRE CASE STUDY Steven YoonA. Salam Gueye Catherine Seyler Mike McKay Laurence E. Aka

  2. No Infrastructure for Computer

  3. No Infrastructure for Computer

  4. Three years down the road

  5. District User National Data Repository No Internet No Infrastructure for Computer

  6. LIST OF PRIORITIES • Patient Record Identification • National Data Repository • User Interface Improvement • Barriers to Success • Maintenance

  7. Patient Record Identification • Unique ID, • Facility ID (already exist) followed by Patient ID • GUID - not tied to anything; 32 characters long; need computer, can’t use in paper system • ID service as phones for requesting IDs – i.e. clinical trials • The golden rules of ID creation – P. Boucher, WHO/EIP/KMS/EHL • Deduplication, proposal for OGAC funding deduplication module? • IDs best if not just HIV – may wish to use this opportunity to develop health system ID

  8. National Data Repository • What architecture is desirable? • OpenMRS good for prototyping application • mySQL robust, scalable • opportunity to define nat’l standards – start with WHO minimum data set (HL7???) • may want to convene expert group to lay out nat’l data system; set of “virtual consultants” • Data transport: GPRS; transfer protocols – allow to transfer changes in dataset only • Governance including concept dictionary • Need flexibility: add new concepts without altering the data model

  9. User Interface Improvement • Touch screen interface • Takes a lot of work, • $500 for each touch screen setup (computer & monitor) • Malawi uses thin client system, one server per clinic, less than 100 Watts per installation • ASP version that runs in a browser – “kiosk mode” • Invenio computer – small PC that can be attached to a touch screen • Smart paper – as you check off boxes, gets entered into database • Voice recognition? Voice recording followed by data entry?

  10. Barriers to Success • Socio-Organizational • Standardizing on a single, national system may create barriers with people that desire a different system, e.g., NGOs • Financial particularly after PEPFAR • Medical Standards • Human Resources Very limited HR in the MOH M&E and HMIS teams • Possible resistance of staff to system – computer systems don’t necessarily make less work

  11. Maintenance • What is the long-term role of ACONDA – does role change as software requirements change • Developers – nat’l system requires sophisticated team, much higher level of effort, need to staff appropriately • Difference between providing a product and providing a service (nat’l system) • Need defined procedures • Source control – SVN – tracks changes in source code • Help desk/bug tracking – free tools available • ETR rollout – WAM technology in S. Africa may be useful to talk to (wametc@iafrica.com)

More Related