Define the operating boundary
A useful definition names the triggering event, required inputs, governing source, accountable owner, decision or action, exception path, evidence retained, and downstream handoff. Buyers should adapt those elements to their own population, jurisdictions, policies, systems, and control model before writing requirements.
The most important distinction is between a label and an operational capability. A provider may document operational monitoring and exception management while depending on customer-supplied policy, licensed content, third-party data, integration partners, manual review, or services. The demonstration should expose those dependencies rather than hiding them behind a completed interface.
What a demonstration should prove
- Begin with representative source records and a named policy, standard, or controlled rule.
- Show the normal path, an ambiguous case, missing data, an exception, an override, and a material source change.
- Identify who can change rules, who can approve or reject, and how accountability is preserved.
- Trace every output back to inputs, versions, timestamps, user actions, and governing evidence.
- Export the resulting record and reconcile it with downstream systems and retained obligations.
Authority and operating context
FHIR R4 4.0.1
FHIR R4 defines resources, RESTful interactions, data types, terminology bindings, conformance artifacts, security considerations, and exchange patterns. It includes the first normative FHIR content and remains the base for major U.S. implementation guides. Buyers must distinguish base R4 support from support for a named profile or implementation guide. FHIR R4 does not establish production connectivity, semantic quality, authorization design, or conformity for a particular product.
HTI-1 Final Rule
HTI-1 updates the ONC Health IT Certification Program, adopts USCDI v3 as the baseline from January 1, 2026, revises information-blocking provisions, adds algorithm-transparency requirements, and creates interoperability-focused reporting metrics. HTI-1 connects standards versions to certification and reporting obligations. Product roadmaps must distinguish the adopted baseline from newer voluntarily advanced specifications.
HTI-2 Final Rule
HTI-2 finalizes TEFCA-related definitions, establishes 45 CFR Part 172 provisions supporting TEFCA reliability, privacy, security, trust, and transparency, and leaves the TEFCA Manner Exception unchanged. The final rule makes regulatory status and formal network governance a first-class buying question. It also demonstrates why withdrawn proposals cannot be presented as current requirements.
HTI-3 Final Rule
HTI-3 adds a definition of reproductive health care for information-blocking regulations, revises the Privacy and Infeasibility Exceptions, and creates a Protecting Care Access Exception. Exchange technology must preserve policy context, purpose, restriction, decision, and evidence rather than assuming that technical availability alone determines whether information should be disclosed.
HTI-5 Proposed Rule
HTI-5 proposes changes to the ONC Certification Program, information-blocking regulations, and standards-based API foundations. Its provisions remain proposals as of the seed date. The proposal can inform scenario planning, but vendors and buyers must not describe proposed removals or new API provisions as settled current requirements.
CMS-9115-F
CMS-9115-F requires specified payers to maintain FHIR-based Patient Access APIs for claims, encounter, cost, and maintained clinical data, and establishes other interoperability and provider-notification provisions. The rule created a durable payer API market while leaving data scope, patient authorization, app privacy, testing, operations, and implementation-guide choices as material implementation decisions.
CMS-0057-F
CMS-0057-F expands Patient Access API content and requires Provider Access, Payer-to-Payer, and Prior Authorization APIs for impacted payers, with associated privacy, opt-in or opt-out, metrics, and operational provisions. The rule makes versioned FHIR implementation, bulk data, member permission, endpoint discovery, data lineage, and production operations central payer interoperability requirements.
TEFCA Common Agreement v2.1
The Common Agreement establishes the legal and governance foundation for nationwide exchange among QHINs, Participants, and Subparticipants, with operating detail supplied by the QTF and standard operating procedures. A TEFCA buying decision must identify the contracted path, participant role, exchange purpose, downstream obligations, technical services, and operating procedures rather than relying on a generic connectivity label.
QTF v2.1
The QTF defines technical and functional requirements for QHIN-to-QHIN exchange and works with the Common Agreement and operating procedures to support nationwide exchange. Organizations should distinguish QHIN-level technical duties from the services a QHIN exposes to Participants and the separate interfaces a participant uses internally.
SMART App Launch 2.2.0
SMART App Launch defines discovery, authorization, scopes, token exchange, and app-launch patterns for applications accessing FHIR APIs from within or outside an EHR workflow. A buyer needs evidence for the exact SMART version, supported launch contexts, scopes, client registration, user and system authorization, and operational token controls.
Bulk Data Access 3.0.0
The Bulk Data Access guide defines asynchronous export patterns for large FHIR datasets, including system-, patient-, and group-level workflows and associated authorization considerations. Bulk export adds job orchestration, file security, filtering, deletion, monitoring, performance, and downstream stewardship requirements that are not answered by a synchronous FHIR API demo.
C-CDA 5.0.0
C-CDA 5.0.0 consolidates U.S. clinical document templates and current guidance while remaining based on the underlying CDA R2 document standard. It uses FHIR tooling to represent templates but does not turn CDA documents into FHIR resources. Document exchange remains a large production reality alongside FHIR APIs. Buyers need version-aware parsing, generation, validation, provenance, and historical compatibility rather than a plan that assumes CDA has disappeared.
The Direct Standard Version 1.3
The Direct Standard specifies a secure, authenticated, scalable method for sending health information to known recipients using profiled internet messaging, public-key infrastructure, certificate discovery, trust, and delivery notifications. Direct remains a durable push-exchange path for referrals, transitions, notifications, and document delivery. Buyers should distinguish messaging capability, address discovery, trust participation, workflow integration, and delivery evidence.
Operating domains
Standards version and conformance control
Risk that organizations treat a standard as a timeless feature, combine incompatible versions or profiles, misstate certification or conformance, and release interfaces without reproducible evidence for the exact artifacts in use.
Patient identity and record linkage
Risk that records are missed, duplicated, or linked to the wrong person because demographic data, identifiers, algorithms, thresholds, human adjudication, and correction workflows do not align across sources and purposes.
Semantic integrity and terminology
Risk that data move successfully but lose or distort meaning because codes, units, value sets, local terms, context, negation, status, and version provenance are incomplete or transformed incorrectly.
Consent, privacy, purpose, and data segmentation
Risk that technically available information is exchanged without appropriate authority, purpose, restriction, segmentation, patient preference, or evidence—or withheld because policy and technology cannot express a lawful path.
Network coverage, routing, and discovery
Risk that a buyer mistakes network scale, participant counts, connector catalogs, or designation for a usable path to the needed organization, endpoint, data, exchange purpose, and response behavior.
Data quality, completeness, and provenance
Risk that exchanged information lacks source, time, status, authorship, context, completeness, or transformation history, preventing the receiving organization from evaluating whether and how to use it.
Security, authorization, and trust
Risk that exchange credentials, certificates, clients, users, systems, scopes, directories, and trust relationships are weakly governed, overbroad, stale, or poorly monitored across organizational boundaries.
Operational reliability and observability
Risk that interfaces and networks appear implemented but fail silently, degrade, duplicate, delay, or lose data because monitoring, ownership, replay, escalation, maintenance, and service evidence are incomplete.
Public-health and community exchange
Risk that provider, HIE, and public-health systems cannot exchange timely, complete, standardized, and actionable information across routine reporting, surveillance, registry, response, and bidirectional workflows.
Information access, blocking, and workflow use
Risk that organizations cannot deliver electronic health information in an authorized, timely, usable manner—or mistake technical delivery for satisfaction of access, exchange, use, clinical, or operational responsibilities.
Evidence and comparison limits
Official provider documentation can establish product positioning. Provider confirmation can clarify package or availability. Independent observation requires a disclosed scenario, environment, date, inputs, and reproducible result. None of those sources alone establishes buyer-specific legal, clinical, regulatory, quality, or operational fitness.
Buyer questions
- What exact outcome and evidence should operational monitoring and exception management produce?
- Which source, version, and customer facts govern the workflow?
- Which decisions remain human and who is accountable for them?
- What is native, configured, integrated, service-delivered, or planned?
- How does a changed source affect open and historical records?
Recent changes
CMS refreshes interoperability API frequently asked questions — Readiness records should be separated by API, implementation guide, source system, responsible party, test status, production status, and exception process.
ONC publishes national HIO public-health capability findings — Provider records should distinguish public-health connection from bidirectional production use, data quality, identity services, and operating support.
HHS reports more than one billion records exchanged through TEFCA — TEFCA has become a material exchange channel, but buyers still need organization-specific evidence for reach, exchange purpose, data quality, operating performance, and governance.
ASTP/ONC confirms HTI-2 final scope and withdrawn proposals — Compliance summaries and product roadmaps must remove broad proposed provisions that did not become final requirements and add TEFCA governance controls where applicable.
HTI-3 revises information-blocking exceptions — Exchange workflows need organization-specific policy, documentation, escalation, segmentation, and audit controls; technology alone cannot decide disclosure applicability.
HHS releases HTI-5 proposed rule — Organizations may use the proposal for scenarios, but should not record its provisions as binding requirements or treat vendor roadmaps as compliance evidence.
TEFCA RCE publishes QHIN Technical Framework 2.1 — QHINs, participants, subparticipants, and vendors need versioned impact assessment, coordinated testing, control mapping, and release evidence.