This navigation tool is generated from the published PDF of the Consolidated Clinical Document Architecture (C-CDA) 2.1 (2.1.0.7, September 2022) and the C-CDA 2.1 Companion Guide (4.1.1, June 2023). For the latest information on C-CDA, or to access the Supplemental Implementation Guides, please refer to the HL7 C-CDA Page which remains the definitive source for the standards. CDA and C-CDA are copyright property of Health Level Seven (HL7) and subject to the terms of HL7's IP policy.
HL7 encourages users to sign up for an account, which is free!
Please sign up if you do not have an account. C-CDA Online Navigator last updated: August 2023.This document type was originally based on the Continuity of Care Document (CCD) Release 1.1 which itself was derived from HITSP C32 and CCD Release 1.0.
The Continuity of Care Document (CCD) represents a core data set of the most relevant administrative, demographic, and clinical information facts about a patient's healthcare, covering one or more healthcare encounters. It provides a means for one healthcare practitioner, system, or setting to aggregate all of the pertinent data about a patient and forward it to another to support the continuity of care.
The primary use case for the CCD is to provide a snapshot in time containing the germane clinical, demographic, and administrative data for a specific patient. The key characteristic of a CCD is that the ServiceEvent is constrained to "PCPR". This means it does not function to report new ServiceEvents associated with performing care. It reports on care that has already been provided. The CCD provides a historical tally of the care over a range of time and is not a record of new services delivered.
More specific use cases, such as a Discharge Summary, Transfer Summary, Referral Note, Consultation Note, or Progress Note, are available as alternative documents in this guide.
When asserting this templateId, all C-CDA 2.1 section and entry templates that had a previous version in C-CDA R1.1 SHALL include both the C-CDA 2.1 templateId and the C-CDA R1.1 templateId root without an extension. See C-CDA R2.1 Volume 1 - Design Considerations for additional detail (CONF:1198-32936).
Such assignedAuthors SHALL contain (exactly one [1..1] assignedPerson) or (exactly one [1..1] assignedAuthoringDevice and exactly one [1..1] representedOrganization) (CONF:1198-8456).
If assignedAuthor has an associated representedOrganization with no assignedPerson or assignedAuthoringDevice, then the value for ClinicalDocument/author/assignedAuthor/id/@NullFlavor SHALL be "NA" Not applicable 2.16.840.1.113883.5.1008 NullFlavor STATIC (CONF:1198-8457).
The main activity being described by a CCD is the provision of healthcare over a period of time. This is
shown by setting the value of serviceEvent/@classCode to "PCPR" (care provision) and indicating the duration
over which care was provided in serviceEvent/effectiveTime. Additional data from outside this duration may
also be included if it is relevant to care provided during that time range (e.g., reviewed during the stated
time range).
NOTE: Implementations originating a CCD should take care to discover what the episode of care
being summarized is. For example, when a patient fills out a form providing relevant health history, the
episode of care being documented might be from birth to the present.
Heading: documentationOf
The documentationOf relationship in a Continuity Care Document contains the
representation of providers who are wholly or partially responsible for the safety and well-being of a subject
of care.
If this assignedEntity is an assignedPerson, the assignedEntity/id SHOULD contain zero or one [0..1] @root="2.16.840.1.113883.4.6" National Provider Identifier (CONF:1198-32466).