ONC certification standards face a patient safety warning as health IT deregulation advances
Health information technology sits inside nearly every modern care setting, but the systems that route orders, display labs, trigger alerts, and document decisions are not neutral infrastructure. When certification rules weaken, the risks do not stay abstract. They move directly to the bedside, where a missed alert, a mislabeled medication list, or a faulty workflow can alter care in seconds.
A Perspective published in Journal of the American Medical Informatics Association argues that the Office of the National Coordinator for Health Information Technology should retain safety-critical certification criteria rather than relax them. The authors frame the issue as a public safety problem, not an administrative one. Their central warning is blunt: future American patients could face avoidable harm if essential oversight is stripped away.
Why certification criteria matter in daily clinical practice
Health IT certification exists to keep software from becoming a hidden source of clinical injury. In practice, certification criteria help ensure that electronic systems support safe prescribing, accurate information exchange, reliable decision support, and predictable user interaction. When those controls are treated as optional, hospitals and clinicians may inherit products that work well enough for billing or convenience but poorly enough for safe care.
The perspective emphasizes that deregulatory actions are built on faulty premises. That argument reflects a fundamental point in medical informatics: software failures are not rare edge cases when a product is deployed across thousands of clinicians, emergency departments, operating rooms, and inpatient units. A design flaw can spread rapidly through repeated use, and once embedded in workflow, it can become difficult to detect and harder to reverse.
One alert failure can reach many patients.
The authors also stress that public safety regulation deserves a different standard from ordinary market rules. Health IT is not a consumer app, and the consequences of malfunction are not limited to inconvenience or lost productivity. A poorly designed interface can contribute to medication errors, delayed diagnosis, incorrect data display, or unsafe decision-making under time pressure. In those settings, the software is part of the clinical environment itself.
Faulty assumptions can turn deregulation into downstream harm
The Perspective links deregulation to serious adverse patient outcomes, although it does not quantify those outcomes in a trial or observational dataset. Its force comes from clinical plausibility and from the known role of health IT in shaping every step of care delivery. A platform that reduces required safeguards may invite variability in performance across vendors and sites, leaving clinicians to absorb the consequences when systems behave inconsistently.
From a pathophysiologic and operational standpoint, the danger is easy to understand. Patient harm often emerges when information is fragmented, delayed, or misrepresented at the exact moment a clinical decision is made. An ordering pathway that omits a safeguard, or a medication display that obscures a dose change, can translate directly into preventable injury. In that sense, certification criteria function as a structural defense layer, much like sterile technique or equipment calibration in other areas of medicine.
The perspective also warns against setting a dangerous precedent. If safety-critical requirements are relaxed for health IT, future policy decisions may drift toward treating core clinical software as if it were interchangeable with low-stakes commercial technology. That shift would make it easier for incentives tied to speed, cost, and market entry to outrun the obligations tied to patient protection.
Government oversight remains central when products can harm large populations
A key theme of the Perspective is the role of government in protecting the public from entities that may have incentives to produce harmful services or products. Health IT vendors operate in a complex market where commercial pressure, rapid deployment, and competitive feature sets can all push development faster than safety review. Certification standards are one of the few mechanisms that force a minimum level of scrutiny before software becomes embedded in clinical care.
This argument carries extra weight because health IT failures can scale. A defect in a single application may affect not one patient, but entire health systems using the same tool. Clinicians do not usually have full control over the design logic buried inside the products they are required to use. They depend on the regulator to preserve baseline safeguards, particularly when the software shapes diagnosis, treatment, and documentation across multiple care environments.
The authors’ position is not that innovation should stop. It is that innovation without enforceable safety criteria can create a pipeline of avoidable harm. In real-world medicine, a system may be faster, cheaper, or easier to deploy and still be unsafe. Certification exists to separate functional software from clinically trustworthy software.
A policy decision with direct bedside consequences
This Perspective places ONC policy in the same category as other patient protection measures that are easy to underestimate until a failure occurs. The article’s warning is direct: failing to retain safety-critical certification criteria could put all future American patients at risk. That sentence is not rhetorical excess; it reflects how deeply health IT is woven into contemporary care delivery.
For clinicians, the implications are immediate. Electronic systems guide medication reconciliation, order entry, test review, and communication across teams. If the regulatory floor drops, the clinical burden shifts back toward end users and institutions already managing staffing shortages, alert fatigue, and growing documentation demands. Safer software is not a luxury item in that environment. It is part of the infrastructure of safe practice.
The Perspective closes the policy debate with a simple principle: public safety regulations should be held to a higher standard because they exist to protect people who cannot evaluate hidden technical risk on their own. In health IT, the stakes are measured not in convenience or efficiency alone, but in patient outcomes, public trust, and the reliability of the systems clinicians use every day.