Abstract

Electronic medical records (EMRs) allow for the creation of “fictional” and unknown patients within the EMR production environment. Surprisingly, there is sparse literature regarding the use cases for these patients or the challenges associated with their existence in the EMR. Here, we identified three classes of patients in regular use at our institution: true fictional patients with medical record numbers (MRNs) used to test EMR functions in the production environment, “confidential patients” used to store sensitive data, and “unknown” patients that are assigned temporary MRNs in emergency situations until additional information can be acquired. A further layer of complexity involving the merging of records for unknown patients once they are identified is also explored. Each class of patients, real or fictional, poses a variety of challenges from a clinical laboratory standpoint, which are often dealt with on a case-by-case basis. Here, we present a series of instructional cases adapted from actual patient safety events at our institution involving fictional, confidential, and unknown patient records. These illustrative cases highlight the utility of these fictional and unknown patients, as well as the challenges they pose on an institutional and individual level, including issues that arise from merging clinical data from temporary MRNs to identified patient charts. Lastly, we provide recommendations on how best to manage similar scenarios that may arise.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.