Document Standards

Section 7 of 12
58% complete

CDA (Clinical Document Architecture)

Part of: HL7 V3 family Purpose: Structure for clinical documents Format: XML-based

When and Where CDA is Used

Primary Use Cases:

  • Discharge summaries
  • Progress notes
  • Procedure notes
  • Consultation reports
  • Imaging reports
  • Continuity of care documents
  • Hospital-to-hospital transfers
  • Care transitions

Typical Settings:

  • Hospitals and health systems
  • Health information exchanges
  • Physician practices
  • Long-term care facilities

CDA Structure

Core Components:

  • Header: Administrative metadata (patient, providers, document info)
  • Body: Clinical content

Levels:

  • Level 1: Unstructured (narrative text only)
  • Level 2: Structured headings with narrative
  • Level 3: Fully structured with coded entries

CDA Header Example:

<ClinicalDocument xmlns="urn:hl7-org:v3">
  <typeId root="2.16.840.1.113883.1.3" extension="POCD_HD000040"/>
  <templateId root="2.16.840.1.113883.10.20.22.1.1"/>
  <id root="2.16.840.1.113883.19.5" extension="c266"/>

  <code code="34133-9" displayName="Summarization of Episode Note"
        codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC"/>

  <title>Discharge Summary</title>
  <effectiveTime value="20231119120000-0500"/>

  <confidentialityCode code="N" codeSystem="2.16.840.1.113883.5.25"/>

  <recordTarget>
    <patientRole>
      <id extension="123456" root="2.16.840.1.113883.19.5"/>
      <addr use="HP">
        <streetAddressLine>123 Main Street</streetAddressLine>
        <city>Anytown</city>
        <state>CA</state>
        <postalCode>12345</postalCode>
      </addr>
      <telecom value="tel:555-555-1234" use="HP"/>
      <patient>
        <name use="L">
          <given>John</given>
          <family>Doe</family>
        </name>
        <administrativeGenderCode code="M" codeSystem="2.16.840.1.113883.5.1"/>
        <birthTime value="19800115"/>
      </patient>
    </patientRole>
  </recordTarget>

  <author>
    <time value="20231119120000-0500"/>
    <assignedAuthor>
      <id extension="99999" root="2.16.840.1.113883.19.5"/>
      <addr>
        <streetAddressLine>456 Hospital Drive</streetAddressLine>
        <city>Anytown</city>
        <state>CA</state>
        <postalCode>12345</postalCode>
      </addr>
      <telecom value="tel:555-555-5000" use="WP"/>
      <assignedPerson>
        <name>
          <given>Jane</given>
          <family>Provider</family>
          <suffix>MD</suffix>
        </name>
      </assignedPerson>
    </assignedAuthor>
  </author>

  <custodian>
    <assignedCustodian>
      <representedCustodianOrganization>
        <id root="2.16.840.1.113883.19.5"/>
        <name>General Hospital</name>
      </representedCustodianOrganization>
    </assignedCustodian>
  </custodian>
</ClinicalDocument>

CDA Body - Structured Content:

<component>
  <structuredBody>
    <component>
      <section>
        <templateId root="2.16.840.1.113883.10.20.22.2.5.1"/>
        <code code="11450-4" displayName="Problem List"
              codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC"/>
        <title>Active Problems</title>
        <text>
          <list>
            <item>Type 2 Diabetes Mellitus</item>
            <item>Hypertension</item>
          </list>
        </text>
        <entry>
          <act classCode="ACT" moodCode="EVN">
            <templateId root="2.16.840.1.113883.10.20.22.4.3"/>
            <id root="2.16.840.1.113883.19.5" extension="prob1"/>
            <code code="CONC" codeSystem="2.16.840.1.113883.5.6"/>
            <statusCode code="active"/>
            <effectiveTime>
              <low value="20200115"/>
            </effectiveTime>
            <entryRelationship typeCode="SUBJ">
              <observation classCode="OBS" moodCode="EVN">
                <templateId root="2.16.840.1.113883.10.20.22.4.4"/>
                <id root="2.16.840.1.113883.19.5" extension="obs1"/>
                <code code="55607006" displayName="Problem"
                      codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT"/>
                <statusCode code="completed"/>
                <effectiveTime>
                  <low value="20200115"/>
                </effectiveTime>
                <value xsi:type="CD" code="44054006"
                       displayName="Type 2 Diabetes Mellitus"
                       codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT"/>
              </observation>
            </entryRelationship>
          </act>
        </entry>
      </section>
    </component>
  </structuredBody>
</component>

C-CDA (Consolidated Clinical Document Architecture)

Status: US standard for clinical documents Based on: CDA R2 Versions: R1.1, R2.1 (current)

C-CDA Document Types

Common Templates:

  • Continuity of Care Document (CCD): Comprehensive summary
  • Discharge Summary: Hospital discharge information
  • Progress Note: Clinical visit documentation
  • Consultation Note: Specialist consultation
  • History and Physical: Initial evaluation
  • Care Plan: Treatment plan and goals
  • Referral Note: Referral to another provider
  • Transfer Summary: Facility transfer document

C-CDA Sections

Required/Common Sections:

  • Allergies and Intolerances
  • Medications
  • Problem List
  • Procedures
  • Results (Lab/Imaging)
  • Vital Signs
  • Immunizations
  • Social History
  • Family History
  • Functional Status
  • Care Plan
  • Reason for Visit
  • Chief Complaint

Implementation Considerations

Advantages:

  • Rich clinical content
  • Standardized sections
  • Human-readable (XML + narrative)
  • Wide EHR vendor support
  • ONC certification requirement

Challenges:

  • XML complexity
  • Large file sizes
  • Parsing difficulties
  • Version compatibility
  • Implementation variability (“optionality”)

Best Practices:

  • Validate against published schemas
  • Use C-CDA validators (NIST, ONC tools)
  • Include both coded and narrative content
  • Follow US Core Data for Interoperability (USCDI)
  • Test with trading partners
  • Document local implementation choices

Direct Secure Messaging

Purpose: Secure, encrypted email-like messaging for healthcare Status: Widely adopted in US

When and Where Direct is Used

Primary Use Cases:

  • Provider-to-provider referrals
  • Lab results delivery
  • Hospital discharge summaries to PCPs
  • Transitions of care documentation
  • Care coordination
  • Public health reporting

Typical Settings:

  • Physician offices
  • Hospitals
  • Health information exchanges
  • Labs and imaging centers

Direct Architecture

Components:

  • Direct Address: Email-like address ([email protected])
  • HISP (Health Information Service Provider): Manages direct addresses
  • Direct Certificate: X.509 digital certificate for encryption
  • Direct Trust: Certificate management and validation

Message Flow:

Sender EHR
  ↓ Create C-CDA or other document
  ↓ Encrypt with recipient's public key
HISP (Sender's)
  ↓ Validate certificate
  ↓ Send via SMTP/IMAP
HISP (Recipient's)
  ↓ Validate certificate
  ↓ Decrypt with recipient's private key
Recipient EHR
  ↓ Process document

Security Features:

  • S/MIME encryption (AES-128 or stronger)
  • Digital signatures
  • Certificate-based authentication
  • Transport Layer Security (TLS)

Implementation Considerations

Advantages:

  • Familiar email-like interface
  • Strong encryption
  • Low cost
  • Wide adoption
  • Works across different EHR vendors

Challenges:

  • Limited acknowledgment/tracking
  • No guaranteed delivery
  • Manual workflow in many systems
  • Certificate management overhead
  • Trust framework complexity

Quiz: Document Standards

Question 1 of 5

What are the two core components of a CDA document?