Change record: HL7 publishes C-CDA 5.0.0

What changed

C-CDA 5.0.0 updates the U.S. clinical-document template set while remaining based on CDA R2 rather than becoming a FHIR-resource specification.

This entry preserves the event separately from maintained provider and capability conclusions. A rule, announcement, release, enforcement record, or market transaction can be material before enough evidence exists to revise a company classification or comparison.

Operating consequence

Enterprise exchange programs need explicit document-ingestion, validation, reconciliation, and extraction evidence in addition to FHIR API capability.

Teams should identify which records, populations, systems, transactions, jurisdictions, products, or decisions fall within the change. Then assign an accountable owner, response date, evidence requirement, and disposition. Broad reassessment is not always necessary, but a material event deserves a documented decision.

Capabilities to revisit

C-CDA Document Exchange

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for C-CDA document exchange.

HL7 V2 Interface Integration

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for HL7 v2 interface integration.

Data Quality, Lineage, And Provenance

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for data quality, lineage, and provenance.

Terminology Normalization And Value-Set Management

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for terminology normalization and value-set management.

Questions for operating teams

• Which exact population and effective date does the source establish?
• Does the change alter authority, policy, content, workflow, integration, evidence, or only market positioning?
• What customer-controlled interpretation, configuration, or process remains outside a provider's responsibility?
• What test case would show whether the operational consequence has reached production?
• What record will close, defer, or supersede this review?

Evidence boundary

The source class is Standards development organization publication. It establishes only the statements supported by the linked record and does not, by itself, establish implementation depth, market-wide availability, transaction-specific applicability, independent efficacy, or a universal buyer conclusion.