Consolidated CDA (C-CDA)
3.0.0 - STU United States of America flag

Consolidated CDA (C-CDA), published by Health Level Seven. This guide is not an authorized publication; it is the continuous build for version 3.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/CDA-ccda/ and changes regularly. See the Directory of published versions

Logical Model: Notes Section

Official URL: http://hl7.org/cda/us/ccda/StructureDefinition/NotesSection Version: 3.0.0
Draft as of 2024-05-07 Computable Name: NotesSection
Other Identifiers: urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#urn:hl7ii:2.16.840.1.113883.10.20.22.2.65:2016-11-01

The Notes Section allow for inclusion of clinical documentation which does not fit precisely within any other C-CDA section. Multiple Notes sections may be included in a document provided they each include different types of note content as indicated by a different section.code. The Notes Section SHOULD NOT be used in place of a more specific C-CDA section. For example, notes about procedure should be placed within the Procedures Section, not a Notes Section. When a Notes Section is present, Note Activity entries contain structured information about the note information allowing it to be more machine processable.

Usage:

  • This Logical Model is not used by any profiles in this Implementation Guide

Formal Views of Template Content

Description of Template, Differentials, Snapshots and how the different presentations work.

This structure is derived from Section

NameFlagsCard.TypeDescription & Constraintsdoco
.. Section C 1..1 Section XML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @nullFlavor, realmCode, typeId, templateId, @ID, @classCode, @moodCode, id, code, title, text, confidentialityCode, languageCode, subject, author, informant, entry, component
Base for all types and resources
Instances of this type are validated by templateId
Logical Container: ClinicalDocument (CDA Class)
shall-note-activity: If section/@nullFlavor is not present, SHALL contain at least one Note Activity
... Slices for templateId 1..* II Slice: Unordered, Open by value:root, value:extension
.... templateId:section 1..1 II
..... @root 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.10.20.22.2.65
..... @extension 1..1 st Required Pattern: 2016-11-01
... code 1..1 CE Binding: Note Types . (preferred)
.... @code 1..1 cs
.... @codeSystem 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.6.1
... title 1..1 ST This title should reflect the kind of notes included in this section, corresponding to the code.
... Slices for entry 0..* Entry Slice: Unordered, Open by profile:act
.... entry:note 0..* Entry If section/@nullFlavor is not present:
..... act 1..1 NoteActivity Base for all types and resources

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Section.codepreferredNoteTypes .
http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.68

Constraints

IdGradePath(s)DetailsRequirements
shall-note-activityerrorSectionIf section/@nullFlavor is not present, SHALL contain at least one Note Activity
: nullFlavor.exists() or entry.where(act.hasTemplateIdOf('http://hl7.org/cda/us/ccda/StructureDefinition/NoteActivity')).exists()
NameFlagsCard.TypeDescription & Constraintsdoco
.. Section C 1..1 Section XML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @nullFlavor, realmCode, typeId, templateId, @ID, @classCode, @moodCode, id, code, title, text, confidentialityCode, languageCode, subject, author, informant, entry, component
Base for all types and resources
Instances of this type are validated by templateId
Logical Container: ClinicalDocument (CDA Class)
shall-note-activity: If section/@nullFlavor is not present, SHALL contain at least one Note Activity
... Slices for templateId 1..* II Slice: Unordered, Open by value:root, value:extension
.... templateId:section 1..1 II
..... @root 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.10.20.22.2.65
..... @extension 1..1 st Required Pattern: 2016-11-01
... code 1..1 CE Binding: Note Types . (preferred)
.... @code 1..1 cs
.... @codeSystem 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.6.1
... title 1..1 ST This title should reflect the kind of notes included in this section, corresponding to the code.
... Slices for entry 0..* Entry Slice: Unordered, Open by profile:act
.... entry:note 0..* Entry If section/@nullFlavor is not present:
..... act C 1..1 NoteActivity Base for all types and resources
should-text-ref-value: SHOULD contain text/reference/@value

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
Section.codepreferredNoteTypes .
http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.68

Constraints

IdGradePath(s)DetailsRequirements
shall-note-activityerrorSectionIf section/@nullFlavor is not present, SHALL contain at least one Note Activity
: nullFlavor.exists() or entry.where(act.hasTemplateIdOf('http://hl7.org/cda/us/ccda/StructureDefinition/NoteActivity')).exists()
should-text-ref-valuewarningSection.entry:note.actSHOULD contain text/reference/@value
: text.reference.value.exists()
NameFlagsCard.TypeDescription & Constraintsdoco
.. Section C 1..1 Section XML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @nullFlavor, realmCode, typeId, templateId, @ID, @classCode, @moodCode, id, code, title, text, confidentialityCode, languageCode, subject, author, informant, entry, component
Base for all types and resources
Instances of this type are validated by templateId
Logical Container: ClinicalDocument (CDA Class)
shall-note-activity: If section/@nullFlavor is not present, SHALL contain at least one Note Activity
... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
... realmCode 0..* CS
... typeId 0..1 II
.... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
.... @assigningAuthorityName 0..1 st
.... @displayable 0..1 bl
.... @root 1..1 oid, uuid, ruid Fixed Value: 2.16.840.1.113883.1.3
.... @extension 1..1 st
.... templateId:section 1..1 II
..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
..... @assigningAuthorityName 0..1 st
..... @displayable 0..1 bl
..... @root 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.10.20.22.2.65
..... @extension 1..1 st Required Pattern: 2016-11-01
... @ID 0..1 xs:ID
... @classCode 0..1 cs Binding: ActClassRecordOrganizer (required)
Fixed Value: DOCSECT
... @moodCode 0..1 cs Binding: CDAActMood (required)
Fixed Value: EVN
... id 0..1 II
... code 1..1 CE Binding: Note Types . (preferred)
.... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
.... @code 1..1 cs
.... @codeSystem 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.6.1
.... @codeSystemName 0..1 st
.... @codeSystemVersion 0..1 st
.... @displayName 0..1 st
.... @sdtcValueSet 0..1 oid XML Namespace: urn:hl7-org:sdtc
XML: valueSet (urn:hl7-org:sdtc)
.... @sdtcValueSetVersion 0..1 st XML Namespace: urn:hl7-org:sdtc
XML: valueSetVersion (urn:hl7-org:sdtc)
.... originalText 0..1 ED
.... translation 0..* CD
... title 1..1 ST This title should reflect the kind of notes included in this section, corresponding to the code.
... text 1..1 xhtml The narrative SHOULD contain human-readable representations using standard CDA narrative markup of each note to ensure widest compatibility with receivers. While allowed by CDA, the use of renderMultiMedia elements, which contain a referencedObject attribute pointing to an observationMedia or regionOfInterest element in the discrete entries, is discouraged in Note Sections because rendering support for these elements is not widespread.
... confidentialityCode 0..1 CE
... languageCode 0..1 CS Binding: AllLanguages (required)
... subject 0..1 Subject
... author 0..* Author
... informant 0..* Informant
... Slices for entry 0..* Entry Slice: Unordered, Open by profile:act
.... entry:note 0..* Entry If section/@nullFlavor is not present:
..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
..... realmCode 0..* CS
..... typeId 0..1 II
...... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
...... @assigningAuthorityName 0..1 st
...... @displayable 0..1 bl
...... @root 1..1 oid, uuid, ruid Fixed Value: 2.16.840.1.113883.1.3
...... @extension 1..1 st
..... templateId 0..* II
..... @typeCode 0..1 cs Binding: x_ActRelationshipEntry (required)
..... @contextConductionInd 0..1 bl Fixed Value: true
..... act C 1..1 NoteActivity Base for all types and resources
should-text-ref-value: SHOULD contain text/reference/@value
..... encounter 0..1 Encounter
..... observation 0..1 Observation
..... observationMedia 0..1 ObservationMedia
..... organizer 0..1 Organizer
..... procedure 0..1 Procedure
..... regionOfInterest 0..1 RegionOfInterest
..... substanceAdministration 0..1 SubstanceAdministration
..... supply 0..1 Supply
... component 0..* InfrastructureRoot
.... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
.... realmCode 0..* CS
.... typeId 0..1 II
..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
..... @assigningAuthorityName 0..1 st
..... @displayable 0..1 bl
..... @root 1..1 oid, uuid, ruid Fixed Value: 2.16.840.1.113883.1.3
..... @extension 1..1 st
.... templateId 0..* II
.... @typeCode 0..1 cs Fixed Value: COMP
.... @contextConductionInd 0..1 bl Fixed Value: true
.... section 1..1 Section

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / CodeURI
Section.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor
Section.typeId.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor
Section.templateId:section.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor
Section.classCoderequiredFixed Value: DOCSECT
http://terminology.hl7.org/ValueSet/v3-ActClassRecordOrganizer
Section.moodCoderequiredFixed Value: EVN
http://hl7.org/cda/stds/core/ValueSet/CDAActMood
Section.codepreferredNoteTypes .
http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.68
Section.code.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor
Section.languageCoderequiredAllLanguages
http://hl7.org/fhir/ValueSet/all-languages
from the FHIR Standard
Section.entry:note.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor
Section.entry:note.typeId.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor
Section.entry:note.typeCoderequiredXActRelationshipEntry
http://terminology.hl7.org/ValueSet/v3-xActRelationshipEntry
Section.component.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor
Section.component.typeId.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor

Constraints

IdGradePath(s)DetailsRequirements
shall-note-activityerrorSectionIf section/@nullFlavor is not present, SHALL contain at least one Note Activity
: nullFlavor.exists() or entry.where(act.hasTemplateIdOf('http://hl7.org/cda/us/ccda/StructureDefinition/NoteActivity')).exists()
should-text-ref-valuewarningSection.entry:note.actSHOULD contain text/reference/@value
: text.reference.value.exists()

This structure is derived from Section

Summary

Mandatory: 9 elements(1 nested mandatory element)

Structures

This structure refers to these other structures:

Slices

This structure defines the following Slices:

  • The element 2 is sliced based on the values of Section.templateId
  • The element 1 is sliced based on the value of Section.entry

Differential View

This structure is derived from Section

NameFlagsCard.TypeDescription & Constraintsdoco
.. Section C 1..1 Section XML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @nullFlavor, realmCode, typeId, templateId, @ID, @classCode, @moodCode, id, code, title, text, confidentialityCode, languageCode, subject, author, informant, entry, component
Base for all types and resources
Instances of this type are validated by templateId
Logical Container: ClinicalDocument (CDA Class)
shall-note-activity: If section/@nullFlavor is not present, SHALL contain at least one Note Activity
... Slices for templateId 1..* II Slice: Unordered, Open by value:root, value:extension
.... templateId:section 1..1 II
..... @root 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.10.20.22.2.65
..... @extension 1..1 st Required Pattern: 2016-11-01
... code 1..1 CE Binding: Note Types . (preferred)
.... @code 1..1 cs
.... @codeSystem 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.6.1
... title 1..1 ST This title should reflect the kind of notes included in this section, corresponding to the code.
... Slices for entry 0..* Entry Slice: Unordered, Open by profile:act
.... entry:note 0..* Entry If section/@nullFlavor is not present:
..... act 1..1 NoteActivity Base for all types and resources

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Section.codepreferredNoteTypes .
http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.68

Constraints

IdGradePath(s)DetailsRequirements
shall-note-activityerrorSectionIf section/@nullFlavor is not present, SHALL contain at least one Note Activity
: nullFlavor.exists() or entry.where(act.hasTemplateIdOf('http://hl7.org/cda/us/ccda/StructureDefinition/NoteActivity')).exists()

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Section C 1..1 Section XML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @nullFlavor, realmCode, typeId, templateId, @ID, @classCode, @moodCode, id, code, title, text, confidentialityCode, languageCode, subject, author, informant, entry, component
Base for all types and resources
Instances of this type are validated by templateId
Logical Container: ClinicalDocument (CDA Class)
shall-note-activity: If section/@nullFlavor is not present, SHALL contain at least one Note Activity
... Slices for templateId 1..* II Slice: Unordered, Open by value:root, value:extension
.... templateId:section 1..1 II
..... @root 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.10.20.22.2.65
..... @extension 1..1 st Required Pattern: 2016-11-01
... code 1..1 CE Binding: Note Types . (preferred)
.... @code 1..1 cs
.... @codeSystem 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.6.1
... title 1..1 ST This title should reflect the kind of notes included in this section, corresponding to the code.
... Slices for entry 0..* Entry Slice: Unordered, Open by profile:act
.... entry:note 0..* Entry If section/@nullFlavor is not present:
..... act C 1..1 NoteActivity Base for all types and resources
should-text-ref-value: SHOULD contain text/reference/@value

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
Section.codepreferredNoteTypes .
http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.68

Constraints

IdGradePath(s)DetailsRequirements
shall-note-activityerrorSectionIf section/@nullFlavor is not present, SHALL contain at least one Note Activity
: nullFlavor.exists() or entry.where(act.hasTemplateIdOf('http://hl7.org/cda/us/ccda/StructureDefinition/NoteActivity')).exists()
should-text-ref-valuewarningSection.entry:note.actSHOULD contain text/reference/@value
: text.reference.value.exists()

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Section C 1..1 Section XML Namespace: urn:hl7-org:v3
Elements defined in Ancestors: @nullFlavor, realmCode, typeId, templateId, @ID, @classCode, @moodCode, id, code, title, text, confidentialityCode, languageCode, subject, author, informant, entry, component
Base for all types and resources
Instances of this type are validated by templateId
Logical Container: ClinicalDocument (CDA Class)
shall-note-activity: If section/@nullFlavor is not present, SHALL contain at least one Note Activity
... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
... realmCode 0..* CS
... typeId 0..1 II
.... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
.... @assigningAuthorityName 0..1 st
.... @displayable 0..1 bl
.... @root 1..1 oid, uuid, ruid Fixed Value: 2.16.840.1.113883.1.3
.... @extension 1..1 st
.... templateId:section 1..1 II
..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
..... @assigningAuthorityName 0..1 st
..... @displayable 0..1 bl
..... @root 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.10.20.22.2.65
..... @extension 1..1 st Required Pattern: 2016-11-01
... @ID 0..1 xs:ID
... @classCode 0..1 cs Binding: ActClassRecordOrganizer (required)
Fixed Value: DOCSECT
... @moodCode 0..1 cs Binding: CDAActMood (required)
Fixed Value: EVN
... id 0..1 II
... code 1..1 CE Binding: Note Types . (preferred)
.... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
.... @code 1..1 cs
.... @codeSystem 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.6.1
.... @codeSystemName 0..1 st
.... @codeSystemVersion 0..1 st
.... @displayName 0..1 st
.... @sdtcValueSet 0..1 oid XML Namespace: urn:hl7-org:sdtc
XML: valueSet (urn:hl7-org:sdtc)
.... @sdtcValueSetVersion 0..1 st XML Namespace: urn:hl7-org:sdtc
XML: valueSetVersion (urn:hl7-org:sdtc)
.... originalText 0..1 ED
.... translation 0..* CD
... title 1..1 ST This title should reflect the kind of notes included in this section, corresponding to the code.
... text 1..1 xhtml The narrative SHOULD contain human-readable representations using standard CDA narrative markup of each note to ensure widest compatibility with receivers. While allowed by CDA, the use of renderMultiMedia elements, which contain a referencedObject attribute pointing to an observationMedia or regionOfInterest element in the discrete entries, is discouraged in Note Sections because rendering support for these elements is not widespread.
... confidentialityCode 0..1 CE
... languageCode 0..1 CS Binding: AllLanguages (required)
... subject 0..1 Subject
... author 0..* Author
... informant 0..* Informant
... Slices for entry 0..* Entry Slice: Unordered, Open by profile:act
.... entry:note 0..* Entry If section/@nullFlavor is not present:
..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
..... realmCode 0..* CS
..... typeId 0..1 II
...... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
...... @assigningAuthorityName 0..1 st
...... @displayable 0..1 bl
...... @root 1..1 oid, uuid, ruid Fixed Value: 2.16.840.1.113883.1.3
...... @extension 1..1 st
..... templateId 0..* II
..... @typeCode 0..1 cs Binding: x_ActRelationshipEntry (required)
..... @contextConductionInd 0..1 bl Fixed Value: true
..... act C 1..1 NoteActivity Base for all types and resources
should-text-ref-value: SHOULD contain text/reference/@value
..... encounter 0..1 Encounter
..... observation 0..1 Observation
..... observationMedia 0..1 ObservationMedia
..... organizer 0..1 Organizer
..... procedure 0..1 Procedure
..... regionOfInterest 0..1 RegionOfInterest
..... substanceAdministration 0..1 SubstanceAdministration
..... supply 0..1 Supply
... component 0..* InfrastructureRoot
.... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
.... realmCode 0..* CS
.... typeId 0..1 II
..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
..... @assigningAuthorityName 0..1 st
..... @displayable 0..1 bl
..... @root 1..1 oid, uuid, ruid Fixed Value: 2.16.840.1.113883.1.3
..... @extension 1..1 st
.... templateId 0..* II
.... @typeCode 0..1 cs Fixed Value: COMP
.... @contextConductionInd 0..1 bl Fixed Value: true
.... section 1..1 Section

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / CodeURI
Section.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor
Section.typeId.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor
Section.templateId:section.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor
Section.classCoderequiredFixed Value: DOCSECT
http://terminology.hl7.org/ValueSet/v3-ActClassRecordOrganizer
Section.moodCoderequiredFixed Value: EVN
http://hl7.org/cda/stds/core/ValueSet/CDAActMood
Section.codepreferredNoteTypes .
http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.68
Section.code.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor
Section.languageCoderequiredAllLanguages
http://hl7.org/fhir/ValueSet/all-languages
from the FHIR Standard
Section.entry:note.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor
Section.entry:note.typeId.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor
Section.entry:note.typeCoderequiredXActRelationshipEntry
http://terminology.hl7.org/ValueSet/v3-xActRelationshipEntry
Section.component.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor
Section.component.typeId.nullFlavorrequiredCDANullFlavor
http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor

Constraints

IdGradePath(s)DetailsRequirements
shall-note-activityerrorSectionIf section/@nullFlavor is not present, SHALL contain at least one Note Activity
: nullFlavor.exists() or entry.where(act.hasTemplateIdOf('http://hl7.org/cda/us/ccda/StructureDefinition/NoteActivity')).exists()
should-text-ref-valuewarningSection.entry:note.actSHOULD contain text/reference/@value
: text.reference.value.exists()

This structure is derived from Section

Summary

Mandatory: 9 elements(1 nested mandatory element)

Structures

This structure refers to these other structures:

Slices

This structure defines the following Slices:

  • The element 2 is sliced based on the values of Section.templateId
  • The element 1 is sliced based on the value of Section.entry

 

Other representations of profile: CSV, Excel