Cited by 210Electronic Health Records SystemsPatient Safety and Medication ErrorsMedical Coding and Health Information

An analysis of electronic health record-related patient safety concerns

Open access
Meeks, Derek W, Smith, Michael W, Taylor, Lesley, Sittig, Dean F, Scott, Jean M, Singh, Hardeep·2014·Journal of the American Medical Informatics Association

Abstract

OBJECTIVE: A recent Institute of Medicine report called for attention to safety issues related to electronic health records (EHRs). We analyzed EHR-related safety concerns reported within a large, integrated healthcare system. METHODS: The Informatics Patient Safety Office of the Veterans Health Administration (VA) maintains a non-punitive, voluntary reporting system to collect and investigate EHR-related safety concerns (ie, adverse events, potential events, and near misses). We analyzed completed investigations using an eight-dimension sociotechnical conceptual model that accounted for both technical and non-technical dimensions of safety. Using the framework analysis approach to qualitative data, we identified emergent and recurring safety concerns common to multiple reports. RESULTS: We extracted 100 consecutive, unique, closed investigations between August 2009 and May 2013 from 344 reported incidents. Seventy-four involved unsafe technology and 25 involved unsafe use of technology. A majority (70%) involved two or more model dimensions. Most often, non-technical dimensions such as workflow, policies, and personnel interacted in a complex fashion with technical dimensions such as software/hardware, content, and user interface to produce safety concerns. Most (94%) safety concerns related to either unmet data-display needs in the EHR (ie, displayed information available to the end user failed to reduce uncertainty or led to increased potential for patient harm), software upgrades or modifications, data transmission between components of the EHR, or 'hidden dependencies' within the EHR. DISCUSSION: EHR-related safety concerns involving both unsafe technology and unsafe use of technology persist long after 'go-live' and despite the sophisticated EHR infrastructure represented in our data source. Currently, few healthcare institutions have reporting and analysis capabilities similar to the VA. CONCLUSIONS: Because EHR-related safety concerns have complex sociotechnical origins, institutions with long-standing as well as recent EHR implementations should build a robust infrastructure to monitor and learn from them.

AI snapshot

Written from the paper’s full text.

TL;DR

Analysis of 100 closed VA investigations of EHR-related safety concerns found that most involved unsafe technology and complex interactions across sociotechnical dimensions. Four recurring concern types accounted for 94% of incidents, showing that EHR safety concerns persist long after go-live even in a mature EHR system.

Key findings

  • Of 100 consecutive, unique, closed investigations from August 2009 to May 2013, 74 involved unsafe technology (phase 1), 25 involved unsafe use of technology (phase 2), and 1 involved lack of monitoring (phase 3); 70% involved two or more sociotechnical model dimensions.
  • Four concern types accounted for 94% of incidents: unmet display needs (n=36), software modifications/upgrades (n=24), system–system interface failures (n=17), and hidden dependencies in distributed systems (n=17).
  • The most commonly involved sociotechnical dimensions were hardware/software (76), clinical content (38), workflow/communication (35), human–computer interface (29), and people (20).
  • Incidents came from 55 unique VA facilities; IPS safety scores were low for 48 investigations, intermediate for 38, and high for 14.

Methods

  • Retrospective qualitative analysis of completed EHR-related safety investigations from the Veterans Health Administration Informatics Patient Safety Office, using 100 consecutive unique closed investigations extracted from 344 reported incidents.
  • Used framework analysis guided by Sittig and Singh’s eight-dimension sociotechnical model and three EHR safety phases; two authors independently indexed concerns, resolving discrepancies by consensus.
  • Coded narrative investigation reports in Atlas.ti V.6.2 and arranged data in Microsoft Excel; no inter-rater reliability was reported because the aim was descriptive.

Limitations

  • The paper states all incidents involved the same EHR within a single, albeit very large, healthcare system; findings may not generalize to institutions with different organizational characteristics, EHR infrastructure, or reporting mechanisms.
  • The paper states the data ranged from unsafe conditions to patient harm, did not analyze additional patient outcome data, and that reporting captures fewer than 10% of medical errors, so prevalence rates cannot be calculated.
  • The paper notes self-reported data may be limited by recall bias or reporter knowledge; evident from the text, the retrospective voluntary reporting system and exclusion of duplicate or comingled-record concerns may underrepresent the full universe of EHR-related safety concerns.

Model-written summary. Check it against the paper before relying on it.

Integrity signals

Registry

Crossref · 10.1136/amiajnl-2013-002578

Cites

60 of 60 references verified0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Claims the paper makes

0 of 50 cited sources checked · 0 supported · 0 flagged

  • Findingown data

    Hidden dependency incidents spanned both phase 1 (11 incidents) and phase 2 (6 incidents) of EHR safety.

    “These incidents also spanned both phase 1 (11 incidents) and phase 2 (6 incidents) of EHR safety.”
    Quote in the paperNot a substantial claim
  • Findingown data

    Across the 36 unmet display concerns, contributory dimensions were hardware/software (22), human-computer interface (22), workflow/communication (10), clinical content (9), people (9), organizational policies and procedures (2), and system measurement and monitoring (1).

    “Across the 36 concerns within this concern type, the contributory dimensions were hardware and software (22 incidents), human–computer interface (22 incidents), workflow and communication (10 incidents), clinical content (9 incidents), people (9 incidents), organizational policies and procedures (2 incidents), and system measurement and monitoring (1 incident).”
    Quote in the paperNot a substantial claim
  • Findingown data

    Phase 2 concerns most commonly involved people, clinical content, workflow and communication, and human-computer interface.

    “One-quarter were classified as phase 2 (ie, unsafe EHR use) and most commonly involved the dimensions of people, clinical content, workflow and communication, and human–computer interface.”
    Quote in the paperNot a substantial claim
  • Findingown data

    A pharmacist made a data entry error while approving the order for a larger-than-usual amount of diuretic.

    “First, a pharmacist made a data entry error while approving the order for a larger-than-usual amount of diuretic.”
    Quote in the paperNot a substantial claim
  • Findingown data

    All four types of safety concerns affected, or had the potential to affect, multiple patients.

    “All four types of safety concerns affected, or had the potential to affect, multiple patients, although we did not further analyze outcome data except as noted below.”
    Quote in the paperNot a substantial claim
  • May combine two claims. 26
  • Classified as probably not a substantial claim. 20
  • May combine two claims.

    Findingown data

    Four broad types of safety concerns were prominent: unmet data display needs within the EHR; problems with software modifications or upgrades; concerns related to system-system interfaces; and hidden dependencies within the EHR.

    “Although the reports documented a variety of EHR-related safety incidents, four broad types of safety concerns were prominent: unmet data display needs within the EHR; problems with software modifications or upgrades; concerns related to system–system interfaces; and hidden dependencies within the EHR.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingreasoning

    Since the printers were installed and configured before recruitment of the current staff, the configuration error was not immediately recognized.

    “Since these printers were installed and configured before recruitment of the current staff, the configuration error was not immediately recognized.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingcitation

    Another concern involved legacy software that needed an upgrade or maintenance, but support staff did not have sufficient knowledge of these systems.

    “Another concern involved ‘legacy’ software (ie, an older system that has not evolved despite newer technologies50) that needed an upgrade or maintenance, but support staff did not have sufficient knowledge of these systems.”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites [50] Brodie ML Stonebraker M . Migrating legacy systems: gateways, interfaces & the incremental approach. Morgan Kaufmann Publishers Inc., 1995.

      Not checked in the free run.

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingown data

    The selected incidents were reported from 55 unique VA facilities.

    “The selected incidents were reported from 55 unique VA facilities.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data

    Four types of safety concerns emerged: unmet display needs, software modifications or upgrades, data transmission at system-system interfaces, and hidden dependencies in distributed systems.

    “We classified these concerns into four types: unmet display needs in the EHR, safety concerns with software modifications or upgrades, concerns related to data transmission at system–system interfaces, and concerns of ‘hidden dependencies’ in distributed systems (ie, when one EHR component unexpectedly or unknowingly is affected by the state or condition of another).”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data

    Incidents frequently reflected more than one sociotechnical dimension: 40 incidents had two dimensions, 23 had three, and seven had four.

    “A majority (70%) involved two or more model dimensions.”
    • Also stated in: § Results · plain
      “Incidents frequently reflected occurrence of more than one sociotechnical dimension: 40 incidents were classified with two sociotechnical dimensions, 23 incidents had three, and seven involved four dimensions.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Findingown data

    Incidents in the hidden dependencies category were largely dependent on multiple interactions between these dimensions, and only one incident was coded with a single dimension.

    “Incidents in this category were also noted to be largely dependent on multiple interactions between these dimensions, and only one incident was coded with a single dimension.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data

    Patient context-related concerns were caused by network failures, conflicts created by non-EHR software, and EHR upgrades that were not compliant with context protocols.

    “Patient context-related concerns were caused by network failures, conflicts created by non-EHR software, and EHR upgrades that were not compliant with context protocols.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data

    The software modification concern type was most often associated with phase 1 (21 incidents); three were phase 2, and none were phase 3.

    “This concern type was most often associated with phase 1 EHR safety (21 incidents). Three concerns were classified as phase 2, and none were phase 3.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data

    System-system interface concerns involved interactions from multiple sociotechnical dimensions: hardware and software (17 incidents), workflow (6 incidents), and content (5 incidents).

    “As highlighted in this example, the system–system interface concern involved interactions from multiple sociotechnical dimensions: hardware and software (17 incidents), workflow (6 incidents), and content (5 incidents).”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data

    The concerns of hidden dependencies primarily involved the dimensions of hardware and software (14 of 17 incidents), workflow (14 incidents), clinical content (9 incidents), and people (5 incidents).

    “The concerns of hidden dependencies primarily involved the dimensions of hardware and software (14 of 17 incidents), workflow (14 incidents), clinical content (9 incidents), and people (5 incidents).”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingnone given

    A dose error warning appeared on order entry, and this particular warning was known to have a high false positive rate.

    “Although a dose error warning appeared on order entry, this particular warning was known to have a high false positive rate.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Findingown data

    On IPS-assessed safety scores, 48 investigations were scored low, 38 intermediate, and 14 high.

    “On the IPS-assessed safety scores, 48 investigations were scored low, 38 intermediate, and 14 were scored high.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Findingreasoning

    The nurse, unaware of the discrepancy between the prescribed amount and the amount approved by the pharmacist, administered the larger dose.

    “The nurse, unaware of the discrepancy between the prescribed amount and the amount approved by the pharmacist, administered the larger dose.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Premisecitation

    The authors previously developed a sociotechnical model that proposes eight interdependent dimensions essential to understand EHR-related safety.

    “For instance, we previously developed a sociotechnical model that proposes eight interdependent dimensions that are essential to understand EHR-related safety (table 1; Sittig and Singh model).24 34”
    Quote in the paperNot a substantial claim0 of 2 sources checked
    • cites [24] source

      Not checked in the free run.

    • cites [34] source

      Not checked in the free run.

  • Classified as probably not a substantial claim.

    Premisecitation

    The sociotechnical model accounts for complexities of technology, users, workflow, and larger external or organizational policies and context in assessment of EHR-related safety concerns.

    “The model accounts for the complexities of technology, its users, the involved workflow, and the larger external or organizational policies and context in assessment of EHR-related safety concerns.35 36”
    Quote in the paperSubstantial claim0 of 2 sources checked
    • cites [35] source

      Not checked in the free run.

    • cites [36] source

      Not checked in the free run.

  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Premisecitation

    Investments in health information technology can enhance the safety and efficiency of patient care and enable knowledge discovery.

    “Investments in health information technology (HIT) can enhance the safety and efficiency of patient care and enable knowledge discovery.1”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites [1] Institute of Medicine (IOM). Crossing the quality chasm a new health system for the 21st century. The National Academy Press, 2001.

      Not checked in the free run.

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Study design and conductown data

    Members of the multidisciplinary project team provided guidance on the content of the themes.

    “Members of our multidisciplinary project team, whose areas of expertise included clinical medicine, patient safety, informatics, human factors, and information technology, provided guidance on the content of the themes.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Interpretationreasoning

    As compared with system-system interfaces, hidden dependencies are unknown, and therefore potential points of failure and possible safety concerns may not be readily identified.

    “As compared with system–system interfaces, hidden dependencies are unknown, and therefore potential points of failure and possible safety concerns may not be readily identified.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Interpretationreasoning

    This example demonstrates how a complex interaction of a technical dimension with non-technical dimensions can potentially develop into a safety concern.

    “This example demonstrates how a complex interaction of a technical dimension with non-technical dimensions can potentially develop into a safety concern.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Interpretationreasoning

    As a result of the poor fit, displayed information available to the end user failed to reduce uncertainty or led to increased potential for patient harm.

    “As a result of this poor fit, the displayed information available to the end user failed to reduce uncertainty or led to increased potential for patient harm.”
    Quote in the paperSubstantial claim
  • Classified as probably not a substantial claim. May combine two claims.

    Study design and conductreasoning

    Given the rich nature of the qualitative data, 100 investigations was believed to be both valuable and feasible.

    “Given the rich nature of the qualitative data, we believed this number was both valuable and feasible.”
    Quote in the paperSubstantial claim
  • Classified as probably not a substantial claim. May combine two claims.

    Study design and conductreasoning

    The authors do not report inter-rater reliability because the aim was to describe the nature and context of common EHR-related safety concerns, not solely classification according to the sociotechnical models.

    “We do not report inter-rater reliability because the aim of the study was to describe the nature and context of common EHR-related safety concerns, not solely classification according to the sociotechnical models.47 49”
    Quote in the paperSubstantial claim0 of 2 sources checked
    • cites [47] source

      Not checked in the free run.

    • cites [49] Reliability. In: Given LM . ed. The SAGE Encyclopedia of Qualitative Research Methods. 2nd ed. Thousand Oaks, CA: SAGE Publications; 2008:753–4. source

      Not checked in the free run.

  • Classified as probably not a substantial claim.

    Interpretationreasoning

    A completed investigation provides additional contextual details pertinent to the incident under study compared with traditional event reports.

    “Thus, a completed investigation provides additional contextual details pertinent to the incident under study as compared with traditional event reports.”
    Quote in the paperSubstantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Study design and conductown data

    Two coding authors independently indexed each safety concern after reviewing the IPS investigation results, and discrepancies in coding were resolved by consensus.

    “The two coding authors (ie, a physician with informatics training and a human factors engineer) independently indexed each safety concern after reviewing the results of the IPS investigation. Discrepancies in coding were then resolved by consensus.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Premisecitation

    Known safety concerns related to erroneous editing or merging of patient records resulting in comingled or overlaid records were excluded because they are not routinely analyzed by IPS and are handled primarily by a separate office in the VA.

    “Although these are known safety concerns,43 they were excluded because they are not routinely analyzed by IPS and are handled primarily by a separate office in the VA.”
    Quote in the paperSubstantial claim0 of 1 sources checked
    • cites [43] source

      Not checked in the free run.

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Study design and conductown data

    Two authors independently reviewed and summarized the investigation reports to become familiar with the data.

    “First, two authors (DWM and MWS) independently reviewed and summarized the investigation reports to become familiar with the data, but at this secondary stage of analysis, we made no further effort to replicate the safety concern or investigation, determine additional causes, or offer additional solutions.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Interpretationreasoning

    Despite capturing a low percentage of errors, the authors were able to gain insight about non-technical aspects of EHR-related safety concerns that may not be routinely considered in technology-focused investigations.

    “Despite capturing a low percentage of errors, we were able to gain insight about non-technical aspects of EHR-related safety concerns that may not be routinely considered in technology-focused investigations.”
    Quote in the paperSubstantial claim
  • May combine two claims.

    Study design and conductreasoning

    The findings may not represent all types of EHR-related safety concerns and might not be generalizable to other institutions with different organizational characteristics, EHR infrastructure, or patient safety reporting mechanisms.

    “Nevertheless, our findings may not represent all types of EHR-related safety concerns and might not be generalizable to other institutions with different organizational characteristics, EHR infrastructure, or patient safety reporting mechanisms.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S2 (checkable).

    Interpretationreasoning

    The findings underscore the importance of continuing the process of detecting and addressing safety concerns long after EHR implementation and 'go-live' has occurred.

    “Our findings underscore the importance of continuing the process of detecting and addressing safety concerns long after EHR implementation and ‘go-live’ has occurred.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Study design and conductnone given

    The circumstances or implications of unsafe conditions or near misses may be different from adverse events that result in patient harm.

    “Although the analysis of unsafe conditions or near misses is useful to illustrate concerns in EHR-enabled care, we acknowledge that their circumstances or implications may be different from adverse events that result in patient harm.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Premisecitation

    In general, fewer than 10% of medical errors are captured through reporting, and such data do not allow calculation of prevalence rates.

    “In general, fewer than 10% of medical errors are captured through reporting, and such data do not allow us to calculate prevalence rates.56 59 60”
    Quote in the paperNot a substantial claim0 of 3 sources checked
    • cites [56] source

      Not checked in the free run.

    • cites [59] Sari AB-A Trevor AS Alison C . Sensitivity of routine system for reporting patient safety incidents in an NHS hospital: retrospective patient case note review. BMJ 2007;334. source

      Not checked in the free run.

    • cites [60] source

      Not checked in the free run.

  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Study design and conductown data

    The data used for the analysis were composed of safety concerns that ranged from unsafe conditions to patient harm.

    “The data used for our analysis were composed of safety concerns that ranged from unsafe conditions to patient harm.”
    Quote in the paperNot a substantial claim
  • Probably not a substantial claim: may not pass S3 (load-bearing).

    Study design and conductown data

    The authors did not analyze additional data on patient outcomes as a result of these concerns.

    “All four emergent safety concerns affected, or had the potential to affect, multiple patients, but we did not analyze additional data on patient outcomes as a result of these concerns.”
    Quote in the paperNot a substantial claim
  • May combine two claims.

    Study design and conductcitation

    Additional strengths of the study include the nationwide distribution of the sample of EHR-related safety incidents and the relatively sophisticated implementation and use of the EHR across the VA healthcare system.

    “Additional strengths of our study include the nationwide distribution of our sample of EHR-related safety incidents and the relatively sophisticated implementation and use of the EHR across the VA healthcare system.39”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites [39] Spetz J Burgess JF Phibbs CS . What determines successful implementation of inpatient information technology systems? Am J Manag Care 2012;18:157–62.

      Not checked in the free run.

  • Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.

    Premisecitation

    As an early adopter of EHRs, the VA has evolved into a 'learning system' that dedicates resources to investigating safety concerns and making EHR-related safety improvements decades after first launch.

    “As an early adopter of EHRs, the VA has evolved into a ‘learning system’ that dedicates resources to investigating safety concerns and making EHR-related safety improvements decades after first launch.42”
    Quote in the paperNot a substantial claim0 of 1 sources checked
    • cites [42] Taylor L Wood SD Chapman R . Analysis and Mitigation of Reported Informatics Patient Safety Adverse Events at the Veterans Health Administration. Human Factors and Ergonomics Society, 2012. source

      Not checked in the free run.

  • May combine two claims.

    Study design and conductown data

    The case descriptions were rich (2-4 single-spaced pages), spanned a period of 3 years, and represented a continuum of care from home-based primary care to large, urban medical centers.

    “Although the sample size is smaller than that of some other studies, the case descriptions were rich (ie, 2–4 single-spaced pages), spanned a period of 3 years, and represented a continuum of care from home-based primary care to large, urban medical centers.”
    Quote in the paperSubstantial claim
  • Classified as probably not a substantial claim. May combine two claims.

    Interpretationreasoning

    Technology-based solutions alone will only partially mitigate EHR-related safety concerns, and interventions to improve EHR-related safety should encompass the people, organizations, systems, and policies that influence how EHRs are used.

    “Our study suggests that technology-based solutions alone will only partially mitigate concerns and that interventions to improve EHR-related safety should encompass the people, organizations, systems, and policies that influence how EHRs are used.”
    Quote in the paperSubstantial claim
  • Classified as probably not a substantial claim. May combine two claims.

    Interpretationreasoning

    Safety concerns identified had complex sociotechnical origins and would need multifaceted strategies for improvement.

    “Safety concerns we identified had complex sociotechnical origins and would need multifaceted strategies for improvement.”
    Quote in the paperSubstantial claim
39 of 39
  • The paper relies on this without support.

    Currently, few healthcare institutions have reporting and analysis capabilities similar to the VA.

    “Currently, few healthcare institutions have reporting and analysis capabilities similar to the VA.”
  • The paper relies on this without support.

    Few healthcare systems have robust reporting and analytic infrastructure similar to the VA's Informatics Patient Safety Office.

    “However, few healthcare systems have robust reporting and analytic infrastructure similar to the VA's IPS.”
2 of 2

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Cites

Flagged first, then by citations

Research works printed but not linked: 1

  1. Institute of Medicine (IOM). Health IT and Patient Safety: Building Safer Systems for Safer Care. Washington, DC: The National Academies Press, 2012.

Cited by

Sorted by citations

Authors
Meeks, D. W., Smith, M. W., Taylor, L., Sittig, D. F., Scott, J. M., & Singh, H.
Affiliations
  • Michael E. DeBakey VA Medical Center (US)
  • United States Department of Veterans Affairs (US)
  • Memorial Hermann (US)
Corresponding author
Singh, Hardeep
Venue
Journal of the American Medical Informatics Association
Published
2014-11
Volume
21
Issue
6
Pages
1053-1059
ISSN
  • 1067-5027 (ISSN-L)
  • 1527-974X
OpenAlex
W2148595420
Cited by
207
References
60
Citations by year
2026: 6 · 2025: 9 · 2024: 16 · 2023: 13 · 2022: 14 · 2021: 15 · 2020: 10 · 2019: 24 · 2018: 22 · 2017: 25 · 2016: 30 · 2015: 20 · 2014: 2
FWCI
46.82
Type
journal article
Language
en
Open access
Licence
cc-by-nc-nd
Locations
  • Journal of the American Medical Informatics Association (publishedVersion, cc-by-nc-nd)
  • Europe PMC (PubMed Central) (publishedVersion, cc-by-nc)
  • PubMed Central (publishedVersion, cc-by-nc)
  • PubMed (publishedVersion)
Funders
  • U.S. Department of Veterans Affairs (14-274, CIN13-413, USA 14-274)
  • Office of Research and Development (CIN 13-413)
  • Health Services Research and Development (CIN 13‐413, CRE12-033, USA 14-274)
  • Agency for Healthcare Research and Quality (R01HS022087)
  • U.S. Public Health Service (T32HP10031)
  • Center for Innovations in Quality, Effectiveness and Safety (CIN 13–413, 13–413)
Topics
  • Health Sciences › Health Professions › Health Information Management › Electronic Health Records Systems
  • Health Sciences › Health Professions › Emergency Medical Services › Patient Safety and Medication Errors
  • Health Sciences › Health Professions › Health Information Management › Medical Coding and Health Information
Keywords
electronic health records, patient safety, socio-technical model, near misses, software upgrade, data transmission, hidden dependencies, workflow, EHR implementation, safety reporting, Veterans Health Administration
MeSH terms
Humans, Retrospective Studies, United States, United States Department of Veterans Affairs, Medical Errors, Workflow, Electronic Health Records, Patient Safety

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Claims read by deepseek-v4.1-flash under definition version 3 (extract-v3) on 2026-10-07.

Classified by jev-1.13-20260917 (gold-guideline-v0.2) on 2026-10-07.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review