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.An Unstructured Document (UD) document type can (1) include unstructured content, such as a graphic, directly in a text element with a mediaType attribute, or (2) reference a single document file, such as a word-processing document using a text/reference element.For guidance on how to handle multiple files, on the selection of media types for this IG, and on the identification of external files, see the examples that follow the constraints below.IHE's XDS-SD (Cross-Transaction Specifications and Content Specifications, Scanned Documents Module) profile addresses a similar, more restricted use case, specifically for scanned documents or documents electronically created from existing text sources, and limits content to PDF-A or text. This Unstructured Documents template is applicable not only for scanned documents in non-PDF formats, but also for clinical documents produced through word processing applications, etc.For conformance with both specifications, implementers need to ensure that their documents at a minimum conform with the SHALL constraints from either specification.
Contained By: | Contains: |
---|---|
none | none |
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-32944).
Heading: nonXMLBody
An Unstructured Document must include a nonXMLBody component with a single text
element. The text element can reference an external file using a reference element, or include unstructured
content directly with a mediaType attribute. The nonXMLBody/text element also has a "compression" attribute
that can be used to indicate that the unstructured content was compressed before being Base64Encoded. At a
minimum, a compression value of "DF" for the deflate compression algorithm (RFC 1951
[URL:http://www.ietf.org/rfc/rfc1951.txt]) must be supported although it is not required that content be
compressed.
If the text element does not contain a reference element with a value attribute, then it SHALL contain exactly one [1..1] @representation="B64" and exactly one [1..1] @mediaType (CONF:1198-7624).
The value of @mediaType, if present, SHALL be drawn from the value set 2.16.840.1.113883.11.20.7.1 SupportedFileFormats STATIC 2010-05-12 (CONF:1198-7623).