Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

2014 Internship Project

This project is being considered as a potential project for 2014 Internships. If you are a potential intern and are interested in working on this project, please discuss it in detail with the mentor(s) listed here before submitting your internship proposal.

Primary mentor

Cosmin Ioan

Backup mentor

Mike Seaton

Assigned to

Stephen Po-Chedley

Abstract

Electronic medical records (EMR) systems are critical to evaluating and providing feedback to clinical programs, to monitoring the evolution and overall success of medical programs, and ensuring that patient data and operational reports are easily accessed. Thousands of programs use an open-source medical records system called OpenMRS throughout the world to help advance the quality of care provided. Like all electronic medical records systems, the ability to use OpenMRS is limited by the quality of data entered into the EMR. OpenMRS deployments have used a variety of external data checks to ensure that data from the EMR system is reliable relative to paper systems, but there has been no consistent tool and this data is not always retained in a systematic way.

This Google Summer of Code Project develops a Data Quality Module for OpenMRS that can be used both by the broader OpenMRS community. The basic module is meant to extract encounter information based on user-selected criteria (e.g. for a specific form, date range, etc.) and prompt the user to re-enter the information. Once the user enters the data, differences between the original record are highlighted and the user is prompted to confirm the differences and will have the option of providing notes about the inconsistencies.

Project Champions

 

Objectives

  •  Allow users to sample records based on user identified criteria
    • Sample based on encounter type, original enterer, location, and date range 
  • Prompt user to re-enter encounter information 
    • Highlight data that is inconsistent between the original and updated record 
    • Store this data for reporting purposes 
    • Allow user to provide information about inconsistencies (e.g. bad handwriting, missing data, updated data, etc.)

Extra Credit

  • Allow user to define a set of records within a given project
    • List a set of records to evaluate and allow user to click on individual records to evaluate 
      • Mark records as “evaluated,” “not done,” or “not evaluated” 
      • Save list so it can be revisited in multiple sessions 
    • May allow user to flag and separate data quality exercises (e.g. Recent HIV follow-up visit data quality)
    • Automatically sub-sample appropriately for statistical purposes (e.g. to select an appropriate random population for a given confidence interval or to produce a lot quality assurance assessment)
  • Generate reports based on given data quality project
    • Quality of data by user
    • Types of errors (e.g. user left record blank, user filled in data missing from paper record, user entered in a value with insufficient precision, paper record was difficult to read or changed, impossible to represent accurately in EMR, etc.)
    • Quality of data based on location
    • Quality of data for a user defined project, program, or encounter type
    • Quality of data based on observation
    • Statistical calculations for confidence intervals, sensitivity, LQAS, etc. 
  • Allow Users to update the original record automatically while assessing the original EMR data

Mockups

Resources

 

  • No labels