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: ActivitiesSection - Detailed Descriptions

Draft as of 2024-12-19

Definitions for the ActivitiesSection 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.
Invariantsshould-intervention-act: SHOULD contain Intervention Act (entry.where(act.hasTemplateIdOf('http://hl7.org/cda/us/ccda/StructureDefinition/InterventionAct')))
should-planned-intervention-act: SHOULD contain Planned Intervention Act (entry.where(act.hasTemplateIdOf('http://hl7.org/cda/us/ccda/StructureDefinition/PlannedInterventionAct')))
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.21.2.3
    8. Section.templateId:section.extension
    Control1..?
    Pattern Value2015-08-01
    10. Section.code
    ShortInterventions Narrative
    Control1..?
    12. Section.code.code
    Control1..?
    Pattern Value62387-6
    14. Section.code.codeSystem
    Control1..?
    Pattern Value2.16.840.1.113883.6.1
    16. Section.title
    Control1..?
    18. Section.text
    Control1..?
    20. Section.entry
    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:intervention
      Slice Nameintervention
      Comments

      SHOULD contain zero or more [0..*] entry (CONF:1198-30996) such that it

      Control0..*
      24. Section.entry:intervention.act
      Comments

      The entry, if present, SHALL contain exactly one [1..1] Intervention Act (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.4.131:2015-08-01) (CONF:1198-30997).

      Control1..?
      Typehttp://hl7.org/cda/stds/core/StructureDefinition/Act(Intervention Act)
      26. Section.entry:plannedIntervention
      Slice NameplannedIntervention
      Comments

      SHOULD contain zero or more [0..*] entry (CONF:1198-32730) such that it

      Control0..*
      28. Section.entry:plannedIntervention.act
      Comments

      The entry, if present, SHALL contain exactly one [1..1] Planned Intervention Act (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.4.146:2015-08-01) (CONF:1198-32731).

      Control1..?
      Typehttp://hl7.org/cda/stds/core/StructureDefinition/Act(Planned Intervention Act)
      30. Section.entry:handoffCommParticipants
      Slice NamehandoffCommParticipants
      Comments

      MAY contain zero or more [0..*] entry (CONF:1198-32402) such that it

      Control0..*
      32. Section.entry:handoffCommParticipants.act
      Comments

      The entry, if present, SHALL contain exactly one [1..1] Intervention Act (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.4.141) (CONF:1198-32403).

      Control1..?
      Typehttp://hl7.org/cda/stds/core/StructureDefinition/Act(Handoff Communication Participants)