​​eSaude Double Data Entry Module
​​Lead: FGH
​​
​​Overview
​​
​​Patient safety is top priority.  Improving data quality is crucial for providing better quality of care for patients.  During data entry process (from paper to electronic health records), errors occur that might lead to adverse incidents and duplicate orders of tests.  There is a need to create Double Data Entry Module.  The main goal is to identify percentage of errors made in data entry process by the same data entry clerk to perform both data entries on the same encounter form so that implementations can conduct data entry training on areas that have high data entry error rates.
​​
​​The proposed workflow is to enforce based on a configurable frequency the form being entered to be entered twice. The outcome of double data entry is recorded and later on data collected can be used to calculate the rough estimate of percentage error.
​​ 
​​
​​Requirements
​​
  • ​​This module is applicable for paper form data entry (not POC) in OpenMRS 1.11.6.
  • ​​There is a configuration page for implementation to setup which encounter forms should be included as well as the frequency for double data entry.  For example, implementation can set up Adult HIV Follow-up Form with frequency of 1 in every 10 forms so the data entry clerk will be prompted to do double data entry on every 10 Adult HIV Follow-up Form.
  • ​​After double data entry is completed, it will highlight the field values that are not matched so corrections can be made immediately.  If third entry still doesn’t match, it will save the third entry in obs table.
  • ​​The error count/rate is calculated between the first entry and the truth stores in obs table.
  • ​​Comparison doesn’t include free text field.  Comparison applies to non-freetext observations.
  • ​​If exact matches for both entries, it saves the data to relevant tables.
  • ​​Create user manual
​​
​​First Version
​​
​​Double entry for the whole form.  Reports allow manager to search the discrepancy count/rate by date range, location, form id, user, and provider.
​​
​​Set of data to collect for discrepancies
  • ​​Form ID
  • ​​Question Concept
  • ​​Discrepant Initial Answer
  • ​​True Answer
  • ​​Data Clerk
  • ​​Provider
  • ​​Location
  • ​​Timestamp
​​ 
​​Configurations
  • ​​Forms
  • ​​Frequency of double entry per form
  • ​​Participating data entry clerks (the default is all data entry clerk if not being specified.)
​​
​​UI Mockup
​​
​​
​​