![Gregory Schmidt, MD artwork](https://is4-ssl.mzstatic.com/image/thumb/Podcasts113/v4/53/b9/16/53b916f0-0f67-7acc-bd16-79a479f81f18/mza_1419307521266447922.jpg/100x100bb.jpg)
Manage auto-populated #EHR data separately
Gregory Schmidt, MD
English - November 24, 2018 19:17 - 18 minutes - 14.6 MBScience Technology design healthcaresystemdesign healtheconomics internalmedicine userinterface userinterfacedesign Homepage Download Apple Podcasts Google Podcasts Overcast Castro Pocket Casts RSS feed
Previous Episode: 5 ways to improve 'required fields' in #EHRs
Next Episode: Is this true? Problems with the Past Medical History
‘Auto-populated data’ should be stored different from ‘Original data’ in electronic health records http://www.gregoryschmidt.ca/writing/auto-populate-ehr-data-vs1 ----- Summary The auto-population of data fields is a key benefit of electronic medical records over paper. However, there are two issues that need to be addressed in order to minimize error and reduce the chance that garbage data is created. First, a system is needed where users have an opportunity to confirm if the auto-populated data remains ‘true’ or has changed. Second, the auto-populated data must be stored in a way where it is tagged different from original data. But first, a comment on the benefit of auto-populated data fields.