By Eric Andrew Kristof, RN, CAHIMS | Healthcare IT Professional | HIMSS Arkansas Chapter Member
About This Series: The HIMSS Word of the Day is a running blog series drawing from the HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025) — the authoritative reference for healthcare IT professionals and the primary study resource for CAHIMS and CPHIMS certification. Each post paraphrases the term in plain language, grounds it in real-world healthcare IT context, and adds a bedside nursing perspective you won’t find in a textbook.
📖 The Term: Consolidated Clinical Document Architecture (C-CDA)
Source: HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025)
🔍 Plain-Language Definition
C-CDA is the U.S. standard for structuring clinical documents, such as discharge summaries, referral notes, and continuity of care summaries, so that they can be exchanged between organizations and read by both people and computers.
The HIMSS Dictionary explains that C-CDA came out of a joint effort by HL7, Integrating the Healthcare Enterprise (IHE), the Health Story Project, and ONC. Its purpose was to resolve conflicts among the many separate CDA implementation guides that different standards organizations had published. C-CDA defines a shared library of templates and specifies how to use them for particular document types. The Continuity of Care Document (CCD) is one example of a C-CDA document.
Each C-CDA document combines a header, which identifies the patient, author, and encounter, with a body made up of sections. Most sections include both readable narrative text and coded entries. Commonly used document types include:
| Document Type | Typical Use |
|---|---|
| Continuity of Care Document (CCD) | A snapshot summary of problems, medications, allergies, results, and other key information |
| Discharge Summary | Hospital course and discharge instructions sent at the end of an inpatient stay |
| Transfer Summary | Information sent when a patient moves to another facility, such as a skilled nursing facility |
| Referral Note | The reason for referral and relevant history sent to a specialist |
| Consultation Note | A specialist’s findings and recommendations returned to the referring provider |
| Progress Note and History and Physical | Encounter documentation shared with other providers |
| Care Plan | Goals, interventions, and health concerns shared across the care team |
⚠️ Exam Alert: Keep the layers straight. CDA is the base HL7 standard for clinical documents. C-CDA is the consolidated U.S. implementation guide built on CDA. The CCD is one document type within C-CDA. The CCR (Continuity of Care Record) was an earlier, separate standard from ASTM. USCDI defines the data that must be exchangeable, and FHIR provides resource-based APIs that complement documents rather than replacing them overnight.
🌐 Why It Matters: Real-World Healthcare IT Context
C-CDA became the backbone of U.S. document exchange through Meaningful Use. Stage 2 required certified EHRs to produce and receive summary of care documents in C-CDA format at transitions of care, and ONC’s certification criteria continue to rely on it. HL7 has updated the guide repeatedly, and it now publishes C-CDA in numbered editions aligned with newer versions of USCDI.
Much of the record exchange that happens through health information exchanges and national networks still moves as C-CDA documents. When an emergency department queries for outside records or a hospital sends a discharge summary to a nursing facility, a C-CDA is frequently what arrives.
Documents have strengths and weaknesses. A C-CDA is a complete, signed snapshot that carries clinical context and can be displayed as readable text. It can also be long, repetitive, and hard to navigate, especially when systems include every available section and years of history in every summary.
Common problems with C-CDA exchange:
- Documents so long that important information is buried in pages of history
- Narrative text that does not match the coded entries underneath it
- Free-text or local codes where standard terminologies are expected
- Duplicate documents arriving from multiple sources for the same visit
- Incoming documents stored as attachments instead of being reconciled into the chart
Characteristics of effective C-CDA use:
- Document templates that include what the receiving setting actually needs
- Coded data using standards such as SNOMED CT, LOINC, and RxNorm
- Reconciliation tools that let clinicians import outside problems, medications, and allergies
- Clear workflows that identify who reviews incoming documents and when
- Testing with exchange partners to confirm documents display and parse correctly
🏥 The Nurse’s Perspective: Clinical, Bedside, & Workflow
C-CDA documents are often the first thing a nurse reads about a patient arriving from somewhere else.
At the Bedside
A nurse admitting a patient from another hospital, receiving a resident at a nursing facility, or preparing for a clinic visit after a hospitalization is often working from a C-CDA. A well-built summary gives a clear picture of active problems, current medications, allergies, recent results, and the plan of care.
A poorly built one can be dozens of pages long, listing every historical diagnosis and medication ever recorded. Nurses learn to look for the sections that matter most, but time spent searching is time not spent with the patient.
In Clinical Workflow
The highest-value nursing task tied to C-CDA is reconciliation. Incoming medication lists and allergies must be compared with what the patient reports and what the receiving team orders. EHR reconciliation tools let nurses and prescribers import coded items from outside documents rather than retyping them, which reduces transcription errors.
Outgoing documents matter just as much. The discharge summary or transfer summary a hospital sends depends on accurate, current nursing and medical documentation. Discharge instructions, recent vital signs, wound care details, and functional status all shape what the next setting can safely do on the first day.
In EHR Implementation (Go-Live Perspective)
During an Epic implementation, teams configure which C-CDA document types the organization sends, what sections each includes, when they are generated, and where incoming documents appear. Those choices determine how useful the documents are to exchange partners and how much reconciliation work lands on receiving clinicians.
End-user support analysts frequently field questions such as where outside documents appear in the chart, how to import an outside medication list, or why a discharge summary did not reach a nursing facility. Knowing whether the issue is document generation, routing, or display helps send each question to the right interoperability analyst.
🎓 CAHIMS / CPHIMS & HIMSS Perspective
CAHIMS Exam Domain Mapping
C-CDA is a frequently tested HL7 standard on the CAHIMS exam:
| CAHIMS Domain | How C-CDA Appears |
|---|---|
| Healthcare & Technology Environments | HL7 and IHE as standards bodies; Meaningful Use and certification requirements; relationship to USCDI |
| Clinical Informatics | Transitions of care; medication and allergy reconciliation; clinical summaries |
| Healthcare Information & Systems Management | Document generation and routing; CDA versus C-CDA versus FHIR; terminology standards within documents |
| Management & Leadership | Exchange partner agreements; interoperability strategy; workflow design for incoming documents |
Key Terms to Know Alongside C-CDA
- CDA (Clinical Document Architecture) — the base HL7 standard for structured clinical documents
- CCD (Continuity of Care Document) — a C-CDA document type that summarizes a patient’s key health information
- HL7 FHIR — the resource-based API standard that complements document exchange
- USCDI — the federal list of data classes and elements that exchanged documents and APIs must support
- Transitions of Care — the movement of patients between settings, where summaries are most needed
- Medication Reconciliation — the process of comparing medication lists to identify and resolve discrepancies
HIMSS Organizational Position
HIMSS supports standards-based exchange across care settings through its interoperability policy work and its Continuity of Care Maturity Model, which addresses how organizations share and use information as patients move between providers. Members can find related guidance through the HIMSS Resource Center.
🔗 Explore Further: External References
- HL7 International — C-CDA Implementation Guide (Product Brief) https://www.hl7.org/implement/standards/product_brief.cfm?product_id=492
- HL7 International — CDA Release 2 (Product Brief) https://www.hl7.org/implement/standards/product_brief.cfm?product_id=7
- ONC — Health IT Certification Program https://healthit.gov/certification-health-it/about-onc-health-it-certification-program/
- ONC — U.S. Core Data for Interoperability (USCDI) https://isp.healthit.gov/united-states-core-data-interoperability-uscdi
- ONC — What Is HIE? https://healthit.gov/health-it-basics/hie/
- IHE International https://www.ihe.net/
Term source: HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025). All definitions in this series are paraphrased for editorial purposes. Readers are encouraged to consult the primary source for exact language.
Eric Andrew Kristof, RN, CAHIMS is a Healthcare IT professional and HIMSS Arkansas Chapter member based in Hot Springs Village, AR, with hands-on Epic Go-Live experience and a diverse healthcare and IT background. He writes at kristof.org at the intersection of clinical care and healthcare technology.
Leave a Reply