ONC Drops 14 EHR Certification Requirements, Shifts AI Validation to Buyers
Federal rule removes source-attribution requirement for AI clinical recommendations. Health systems assume full responsibility for explainability and audit controls by January 2027.
ONC eliminates one-quarter of certification criteria
The Office of the National Coordinator for Health IT finalized HTI-5 on November 19, removing 14 of the 60 active certification criteria for electronic health records and revising seven more. The rule takes effect December 28, 2026, with most changes applying January 1, 2027.
ONC retained 39 criteria, including electronic prior authorization and real-time prescription benefits. It extended certain transitions-of-care deadlines to January 1, 2030.
The most consequential change for buyers: ONC removed the requirement that certified systems provide source attribution for AI recommendations. That means EHR vendors no longer must disclose the data, models, or evidence supporting clinical suggestions generated by artificial intelligence.
Vendor compliance costs may fall. Health-system risk does not. Procurement teams should update RFP requirements to mandate AI explainability, data provenance, model-performance reporting, and audit trails before any 2027 implementation. The burden of validating patient-safety controls now falls entirely on the buyer, not the certifying body.
Epic customers plan to consolidate AI vendors
A Black Book Research report found that 63% of Epic-based health systems plan to replace at least one standalone AI application with an EHR-native tool by 2028. Among organizations using other EHR platforms, the comparable figure was 34%.
The finding signals a consolidation threat to point-solution vendors in ambient documentation, clinical decision support, analytics, and workflow automation. Epic also announced that its November 2026 software version would support large-volume data transfers at up to five times faster speeds through dedicated reporting infrastructure.
Enterprise buyers should compare the total cost of standalone tools—including integration, support, security review, and clinician adoption—against native EHR modules. Consolidation reduces interface complexity but increases platform dependence and erodes negotiating leverage. Buyers should verify that throughput acceleration applies to their specific FHIR and reporting use cases, not just vendor benchmarks.
Shore Medical extends Oracle Health deployment across care settings
Shore Medical Center, a 196-bed nonprofit hospital in New Jersey, plans to implement Oracle Health's AI-powered EHR across the hospital and physician practices by December 2027. The deployment will cover inpatient care, outpatient rehabilitation, urgent care, primary care, and specialty practices.
The project includes Oracle Health's voice-first EHR, which surfaces laboratory results and medications through voice commands, plus an AI-powered patient portal for records access, appointments, and care-team communications.
The case supports a trend toward replacing fragmented clinical and ambulatory systems with one vendor platform. Buyers should evaluate migration complexity, implementation staffing, physician-practice standardization, and the maturity of voice and generative-AI features—not just the promise of workflow unification. No contract value was disclosed, so the announcement does not support a precise ROI calculation. Its concrete significance is scope: a 196-bed organization is extending an existing Oracle relationship across multiple care settings rather than adding another point tool.
HIPAA Privacy Rule changes create July 2027 compliance deadline
The HHS Office for Civil Rights published a final HIPAA Privacy Rule modification on November 19, 2026, intended to support care coordination and faster, lower-cost access to health information through applications. It takes effect January 19, 2027, with compliance required by July 19, 2027.
Health systems and covered entities need to inventory patient-access applications, revise privacy and security controls, and validate contracts with vendors that retrieve, transmit, or expose protected health information. The July 19, 2027 compliance date creates a near-term legal and implementation budget item. Organizations should expect spending on API governance, identity verification, consent management, audit logging, vendor assessments, and incident-response processes.
EHR vendors, health-information exchanges, payer platforms, patient-access APIs, and consumer health applications will compete on secure data access and authorization workflows. Vendors that already support standardized APIs and strong consent controls may have an implementation advantage.
What to watch
Funding and M&A activity during the week indicates continued consolidation. Knit Health announced $35 million from NEA to scale Med-BEAM, a model intended to predict clinical actions and care needs. Wolters Kluwer Health agreed to acquire AgileMD for up to $100 million, expanding its clinical decision-support portfolio. XpertDox announced $20 million in Series A funding for automated medical coding. Credo Health acquired Affineon Health and rebranded as Pajama.ai, targeting physician inbox and medical-record workflow management.
Enterprises should examine product-road-map continuity, data portability, licensing changes, and integration plans before committing to acquired platforms. The Wolters Kluwer-AgileMD deal is especially relevant because it combines clinical content and decision-support distribution with a point-of-care technology asset.
The combination of lighter certification requirements, embedded-EHR AI consolidation, and the July 2027 HIPAA compliance deadline creates a narrow window for health systems to shift governance and procurement processes. The question is not whether to adopt AI-powered workflows, but whether your organization can validate them without federal certification as a backstop.
Technology decisions, clearly explained.
Weekly analysis of the tools, platforms, and strategies that matter to B2B technology buyers. No fluff, no vendor spin.
