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 C-CDA document exchange 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
USCDI v6
USCDI v6 defines an expanded national set of health-data classes and elements intended to support interoperable exchange. Publication, regulatory adoption, and voluntary certification advancement are distinct status records. USCDI version determines the content baseline around which profiles, certification, mapping, and exchange programs are designed. Buyers should demand a version-aware roadmap and evidence for missing or newly added elements.
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.
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
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.
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.
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.
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 C-CDA document exchange 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
HL7 publishes C-CDA 5.0.0 — Enterprise exchange programs need explicit document-ingestion, validation, reconciliation, and extraction evidence in addition to FHIR API capability.