Consolidated CDA (C-CDA)
4.0.0-ballot - STU4 Ballot 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 4.0.0-ballot 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: NotesSection - Detailed Descriptions

Draft as of 2024-12-19

Definitions for the NotesSection logical model.

Guidance on how to interpret the contents of this table can be found here

0. Section
Logical ContainerClinicalDocument (CDA Class)
ValidationInstance of this type are validated by templateId
XML FormatIn the XML format, this property has the namespace urn:hl7-org:v3.
Invariantsshall-note-activity: If 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())
2. Section.templateId
Control1..?
SlicingThis element introduces a set of slices on Section.templateId. The slices areUnordered and Open, and can be differentiated using the following discriminators:
  • value @ root
  • value @ extension
  • 4. Section.templateId:section
    Slice Namesection
    Control1..1
    6. Section.templateId:section.root
    Control1..?
    Pattern Value2.16.840.1.113883.10.20.22.2.65
    8. Section.templateId:section.extension
    Control1..?
    Pattern Value2016-11-01
    10. Section.code
    Comments

    SHALL contain exactly one [1..1] code, which SHOULD be selected from ValueSet Note Types urn:oid:2.16.840.1.113883.11.20.9.68 DYNAMIC (CONF:3250-16892).

    Control1..?
    BindingThe codes SHOULD be taken from Note Types .
    (preferred to http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.68)
    12. Section.code.code
    Control1..?
    14. Section.code.codeSystem
    Control1..?
    Pattern Value2.16.840.1.113883.6.1
    16. Section.title
    ShortThis title should reflect the kind of notes included in this section, corresponding to the code.
    Control1..?
    18. Section.text
    ShortThe 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.
    Control1..?
    20. Section.entry
    Comments

    SHALL contain at least one [1..*] entry (CONF:3250-16904) such that it

    SlicingThis element introduces a set of slices on Section.entry. The slices areUnordered and Open, and can be differentiated using the following discriminators:
    • profile @ act
    • 22. Section.entry:note
      Slice Namenote
      ShortIf section/@nullFlavor is not present:
      Control0..*
      24. Section.entry:note.act
      Comments

      SHALL contain exactly one [1..1] Note Activity (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.4.202:2016-11-01) (CONF:3250-16905).

      Control1..?
      Typehttp://hl7.org/cda/stds/core/StructureDefinition/Act(Note Activity)