Consolidated CDA (C-CDA)
5.0.0-ballot - STU5 Ballot 1 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 5.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: Care Plan Act

Official URL: http://hl7.org/cda/us/ccda/StructureDefinition/CarePlanAct Version: 5.0.0-ballot
Draft as of 2025-12-12 Computable Name: CarePlanAct
Other Identifiers: urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#urn:hl7ii:2.16.840.1.113883.10.20.22.4.518:2026-05-01

The Care Plan Act represents a snapshot in time of a dynamic, consensus-driven plan that has captured a patient's and care team members' prioritized concerns, goals, and planned interventions. It reflects the state of the care plan as managed within a source system and may be exchanged to support care coordination across systems and settings.

The Care Plan Act identifies the authoring individual or organization (act.author), which aligns with the FHIR CarePlan.contributor, and records the set of health concerns or conditions being addressed.

To meet USCDI requirements, at least one entryRelationship:addresses element referencing an Indication, Problem Observation, or Observation is required.

The Care Plan Act may integrate multiple condition- or discipline-specific plans of care and serves to align activities and responsibilities among participants. Supporting entryRelationship templates such as Goal, Intervention Act, Planned Intervention Act, and Act are available for systems capable of representing structured care plans, but their use is optional and not required for USCDI compliance.

This entry conveys an instance of the evolving Care Plan at a specific point in time and does not represent a dynamically updated plan.

Templates Used

Although open templates may contain any valid CDA content, the following templates are specifically called out by this template:

Optional EntryRelationships: Act, EntryReference, GoalObservation, Indication, InterventionAct, Observation, PlannedInterventionAct, ProblemObservation

Usages:

You can also check for usages in the FHIR IG Statistics

Changes since version 4.0.0:

  • New Content

    • Formal Views of Template Content

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

    This structure is derived from Act

    NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
    .. Act C 1..1 Act XML Namespace: urn:hl7-org:v3
    Base for all types and resources
    Instance of this type are validated by templateId
    Logical Container: ClinicalDocument (CDA Class)
    Constraints: should-text-ref-value
    ... Slices for templateId 1..* II Slice: Unordered, Open by value:root, value:extension
    .... templateId:care-plan-act 1..1 II
    ..... @root 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.10.20.22.4.518
    ..... @extension 1..1 st Required Pattern: 2026-05-01
    ... @moodCode 1..1 cs CarePlan.intent
    Binding: Care Plan Mood Codes . (required)
    ... code 1..1 CD Plan of care note
    .... @code 1..1 cs Required Pattern: 18776-5
    .... @codeSystem 1..1 oid, uuid, ruid LOINC
    Required Pattern: 2.16.840.1.113883.6.1
    .... translation 0..* CD Binding: CarePlanCategory (preferred)
    .... reference C 0..1 TEL Constraints: value-starts-octothorpe
    ... statusCode 1..1 CS CarePlan.status
    ... author 0..* AuthorParticipation CarePlan.contributor
    ... Slices for entryRelationship 0..* EntryRelationship Entries can be embedded directly or referenced via EntryReference. Use the @typeCode attribute to distinguish the type of relationship.
    Slice: Unordered, Open by value:typeCode
    .... entryRelationship:addresses C 0..* EntryRelationship 𝗨𝗦𝗖𝗗𝗜: CarePlan.addresses
    Constraints: act-or-observation
    ..... @typeCode 1..1 cs Required Pattern: RSON
    ..... act 0..1 EntryReference, Act References an Indication, Problem Observation, or other Problem described elsewhere in the document.
    ..... observation 0..1 Indication, ProblemObservation, Observation Directly-embedded Problem or Indication observation. Use EntryReference to reference an existing problem observation or indication described elsewhere in the document.
    .... entryRelationship:goal C 0..* EntryRelationship Desired outcome of the plan (CarePlan.goal). Can embed a Goal Observation directly or use the EntryReference template to reference a Goal Observation described elsewhere in the document.
    Constraints: act-or-observation
    ..... @typeCode 1..1 cs Required Pattern: GEVL
    ..... act C 0..1 EntryReference Use to reference a Goal Observation elsewhere
    Constraints: entry-ref-goal
    ..... observation 0..1 GoalObservation Use to embed a Goal Observation directly
    .... entryRelationship:supportingInfo 0..* EntryRelationship Information considered as part of the plan (CarePlan.supportingInfo)
    ..... @typeCode 1..1 cs Required Pattern: SPRT
    .... entryRelationship:activity 0..* EntryRelationship Activity to occur as part of plan (CarePlan.activity). Common examples include the Intervention Act and Planned Intervention Act, but any entry may be considered an activity of the care plan.
    ..... @typeCode 1..1 cs Required Pattern: COMP
    ..... act 0..1 InterventionAct, PlannedInterventionAct, Act A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... encounter 0..1 Encounter A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... observation 0..1 Observation A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... supply 0..1 Supply A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.

    doco Documentation for this format

    Terminology Bindings (Differential)

    Path Status Usage ValueSet Version Source
    Act.moodCode Base required Care Plan Mood Codes . 📦20251123 VSAC v0.24
    Act.code.translation Base preferred Care Plan Category 📦5.0.0 FHIR Std.

    Constraints

    Id Grade Path(s) Description Expression
    act-or-observation error Act.entryRelationship:addresses, Act.entryRelationship:goal Either act or observation SHALL be present but not both. act.exists() or observation.exists()
    entry-ref-goal error Act.entryRelationship:goal.act This entryReference template **SHALL** reference an instance of a Goal Observation template. %resource.descendants().ofType(CDA.Observation).where(templateId.exists($this.root = '2.16.840.1.113883.10.20.22.4.121' and $this.extension = '2022-06-01') and id.exists($this.root = %context.id.first().root and $this.extension ~ %context.id.first().extension))
    should-text-ref-value warning Act SHOULD contain text/reference/@value text.reference.value.exists()
    value-starts-octothorpe error Act.text.reference If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative value.exists() implies value.startsWith('#')
    NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
    .. Act C 1..1 Act XML Namespace: urn:hl7-org:v3
    Base for all types and resources
    Instance of this type are validated by templateId
    Logical Container: ClinicalDocument (CDA Class)
    Constraints: should-text-ref-value
    ... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ... realmCode 0..* CS
    ... typeId C 0..1 II Constraints: II-1
    .... @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:care-plan-act 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.4.518
    ..... @extension 1..1 st Required Pattern: 2026-05-01
    ... @classCode 1..1 cs Binding: XActClassDocumentEntryAct (2.0.0) (required)
    ... @moodCode 1..1 cs CarePlan.intent
    Binding: Care Plan Mood Codes . (required)
    ... @negationInd 0..1 bl
    ... id 0..* II
    ... code 1..1 CD Plan of care note
    Binding: v3 Code System ActCode (example)
    .... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    .... @code 1..1 cs Required Pattern: 18776-5
    .... @codeSystem 1..1 oid, uuid, ruid LOINC
    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
    .... qualifier 0..* CR
    .... translation 0..* CD Binding: CarePlanCategory (preferred)
    ... text C 0..1 ED SHOULD reference the portion of section narrative text corresponding to this entry
    .... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    .... @compression 0..1 cs Binding: CDACompressionAlgorithm (required)
    .... @integrityCheck 0..1 bin
    .... @integrityCheckAlgorithm 0..1 cs Binding: IntegrityCheckAlgorithm (2.0.0) (required)
    .... @language 0..1 cs
    .... @mediaType 0..1 cs Binding: MediaType (example)
    .... @representation 0..1 cs Binding: CDABinaryDataEncoding (required)
    .... xmlText 0..1 st Allows for mixed text content. If @representation='B64', this SHALL be a base64binary string.
    .... reference C 0..1 TEL Constraints: value-starts-octothorpe
    .... thumbnail C 0..1 ED Constraints: ED-1
    ... statusCode 1..1 CS CarePlan.status
    Binding: ActStatus (required)
    ... effectiveTime 0..1 IVL_TS
    ... priorityCode 0..1 CE Binding: ActPriority (example)
    ... languageCode 0..1 CS Binding: AllLanguages (required)
    ... subject 0..1 Subject
    ... specimen 0..* Specimen
    ... performer 0..* Performer2
    ... author 0..* AuthorParticipation CarePlan.contributor
    ... informant 0..* Informant
    ... participant 0..* Participant2
    ... Slices for entryRelationship 0..* EntryRelationship Entries can be embedded directly or referenced via EntryReference. Use the @typeCode attribute to distinguish the type of relationship.
    Slice: Unordered, Open by value:typeCode
    .... entryRelationship:addresses C 0..* EntryRelationship 𝗨𝗦𝗖𝗗𝗜: CarePlan.addresses
    Constraints: act-or-observation
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: RSON
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act 0..1 EntryReference, Act References an Indication, Problem Observation, or other Problem described elsewhere in the document.
    ..... encounter 0..1 Encounter
    ..... observation 0..1 Indication, ProblemObservation, Observation Directly-embedded Problem or Indication observation. Use EntryReference to reference an existing problem observation or indication described elsewhere in the document.
    ..... observationMedia 0..1 ObservationMedia
    ..... organizer 0..1 Organizer
    ..... procedure 0..1 Procedure
    ..... regionOfInterest 0..1 RegionOfInterest
    ..... substanceAdministration 0..1 SubstanceAdministration
    ..... supply 0..1 Supply
    .... entryRelationship:goal C 0..* EntryRelationship Desired outcome of the plan (CarePlan.goal). Can embed a Goal Observation directly or use the EntryReference template to reference a Goal Observation described elsewhere in the document.
    Constraints: act-or-observation
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: GEVL
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act C 0..1 EntryReference Use to reference a Goal Observation elsewhere
    Constraints: entry-ref-goal
    ..... encounter 0..1 Encounter
    ..... observation 0..1 GoalObservation Use to embed a Goal Observation directly
    ..... observationMedia 0..1 ObservationMedia
    ..... organizer 0..1 Organizer
    ..... procedure 0..1 Procedure
    ..... regionOfInterest 0..1 RegionOfInterest
    ..... substanceAdministration 0..1 SubstanceAdministration
    ..... supply 0..1 Supply
    .... entryRelationship:supportingInfo 0..* EntryRelationship Information considered as part of the plan (CarePlan.supportingInfo)
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: SPRT
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act 0..1 Act
    ..... 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
    .... entryRelationship:activity 0..* EntryRelationship Activity to occur as part of plan (CarePlan.activity). Common examples include the Intervention Act and Planned Intervention Act, but any entry may be considered an activity of the care plan.
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: COMP
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act 0..1 InterventionAct, PlannedInterventionAct, Act A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... encounter 0..1 Encounter A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... observation 0..1 Observation A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... observationMedia 0..1 ObservationMedia
    ..... organizer 0..1 Organizer
    ..... procedure 0..1 Procedure
    ..... regionOfInterest 0..1 RegionOfInterest
    ..... substanceAdministration 0..1 SubstanceAdministration
    ..... supply 0..1 Supply A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ... reference 0..* Reference
    ... precondition 0..* Precondition
    ... sdtcPrecondition2 0..* Precondition2 XML Namespace: urn:hl7-org:sdtc
    XML: precondition2 (urn:hl7-org:sdtc)
    ... sdtcInFulfillmentOf1 0..* InFulfillmentOf1 XML Namespace: urn:hl7-org:sdtc
    XML: inFulfillmentOf1 (urn:hl7-org:sdtc)

    doco Documentation for this format

    Terminology Bindings

    Path Status Usage ValueSet Version Source
    Act.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.templateId:care-plan-act.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.classCode Base required x_ActClassDocumentEntryAct 📍2.0.0 THO v5.2
    Act.moodCode Base required Care Plan Mood Codes . 📦20251123 VSAC v0.24
    Act.code Base example v3 Code System ActCode 📦3.0.0 THO v7.0
    Act.code.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.code.translation Base preferred Care Plan Category 📦5.0.0 FHIR Std.
    Act.text.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.text.compression Base required CDACompressionAlgorithm 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.text.integrityCheckAlgorithm Base required IntegrityCheckAlgorithm 📍2.0.0 THO v5.2
    Act.text.mediaType Base example MediaType 📦3.0.0 THO v7.0
    Act.text.representation Base required CDABinaryDataEncoding 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.statusCode Base required ActStatus 📦3.0.0 THO v7.0
    Act.priorityCode Base example ActPriority 📦3.0.0 THO v7.0
    Act.languageCode Base required All Languages 📦5.0.0 FHIR Std.
    Act.entryRelationship:addresses.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:addresses.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:addresses.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0
    Act.entryRelationship:goal.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:goal.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:goal.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0
    Act.entryRelationship:supportingInfo.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:supportingInfo.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:supportingInfo.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0
    Act.entryRelationship:activity.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:activity.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:activity.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0

    Constraints

    Id Grade Path(s) Description Expression
    ED-1 error Act.text.thumbnail Thumbnails cannot contain their own thumbnails thumbnail.empty()
    II-1 error Act.typeId, Act.entryRelationship:addresses.typeId, Act.entryRelationship:goal.typeId, Act.entryRelationship:supportingInfo.typeId, Act.entryRelationship:activity.typeId An II instance must have either a root or an nullFlavor. root.exists() or nullFlavor.exists()
    act-or-observation error Act.entryRelationship:addresses, Act.entryRelationship:goal Either act or observation SHALL be present but not both. act.exists() or observation.exists()
    entry-ref-goal error Act.entryRelationship:goal.act This entryReference template **SHALL** reference an instance of a Goal Observation template. %resource.descendants().ofType(CDA.Observation).where(templateId.exists($this.root = '2.16.840.1.113883.10.20.22.4.121' and $this.extension = '2022-06-01') and id.exists($this.root = %context.id.first().root and $this.extension ~ %context.id.first().extension))
    should-text-ref-value warning Act SHOULD contain text/reference/@value text.reference.value.exists()
    value-starts-octothorpe error Act.text.reference If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative value.exists() implies value.startsWith('#')
    NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
    .. Act C 1..1 Act XML Namespace: urn:hl7-org:v3
    Base for all types and resources
    Instance of this type are validated by templateId
    Logical Container: ClinicalDocument (CDA Class)
    Constraints: should-text-ref-value
    ... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ... realmCode 0..* CS
    ... typeId C 0..1 II Constraints: II-1
    .... @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:care-plan-act 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.4.518
    ..... @extension 1..1 st Required Pattern: 2026-05-01
    ... @classCode 1..1 cs Binding: XActClassDocumentEntryAct (2.0.0) (required)
    ... @moodCode 1..1 cs CarePlan.intent
    Binding: Care Plan Mood Codes . (required)
    ... @negationInd 0..1 bl
    ... id 0..* II
    ... code 1..1 CD Plan of care note
    Binding: v3 Code System ActCode (example)
    .... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    .... @code 1..1 cs Required Pattern: 18776-5
    .... @codeSystem 1..1 oid, uuid, ruid LOINC
    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
    .... qualifier 0..* CR
    .... translation 0..* CD Binding: CarePlanCategory (preferred)
    ... text C 0..1 ED SHOULD reference the portion of section narrative text corresponding to this entry
    .... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    .... @compression 0..1 cs Binding: CDACompressionAlgorithm (required)
    .... @integrityCheck 0..1 bin
    .... @integrityCheckAlgorithm 0..1 cs Binding: IntegrityCheckAlgorithm (2.0.0) (required)
    .... @language 0..1 cs
    .... @mediaType 0..1 cs Binding: MediaType (example)
    .... @representation 0..1 cs Binding: CDABinaryDataEncoding (required)
    .... xmlText 0..1 st Allows for mixed text content. If @representation='B64', this SHALL be a base64binary string.
    .... reference C 0..1 TEL Constraints: value-starts-octothorpe
    .... thumbnail C 0..1 ED Constraints: ED-1
    ... statusCode 1..1 CS CarePlan.status
    Binding: ActStatus (required)
    ... effectiveTime 0..1 IVL_TS
    ... priorityCode 0..1 CE Binding: ActPriority (example)
    ... languageCode 0..1 CS Binding: AllLanguages (required)
    ... subject 0..1 Subject
    ... specimen 0..* Specimen
    ... performer 0..* Performer2
    ... author 0..* AuthorParticipation CarePlan.contributor
    ... informant 0..* Informant
    ... participant 0..* Participant2
    ... Slices for entryRelationship 0..* EntryRelationship Entries can be embedded directly or referenced via EntryReference. Use the @typeCode attribute to distinguish the type of relationship.
    Slice: Unordered, Open by value:typeCode
    .... entryRelationship:addresses C 0..* EntryRelationship 𝗨𝗦𝗖𝗗𝗜: CarePlan.addresses
    Constraints: act-or-observation
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: RSON
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act 0..1 EntryReference, Act References an Indication, Problem Observation, or other Problem described elsewhere in the document.
    ..... encounter 0..1 Encounter
    ..... observation 0..1 Indication, ProblemObservation, Observation Directly-embedded Problem or Indication observation. Use EntryReference to reference an existing problem observation or indication described elsewhere in the document.
    ..... observationMedia 0..1 ObservationMedia
    ..... organizer 0..1 Organizer
    ..... procedure 0..1 Procedure
    ..... regionOfInterest 0..1 RegionOfInterest
    ..... substanceAdministration 0..1 SubstanceAdministration
    ..... supply 0..1 Supply
    .... entryRelationship:goal C 0..* EntryRelationship Desired outcome of the plan (CarePlan.goal). Can embed a Goal Observation directly or use the EntryReference template to reference a Goal Observation described elsewhere in the document.
    Constraints: act-or-observation
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: GEVL
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act C 0..1 EntryReference Use to reference a Goal Observation elsewhere
    Constraints: entry-ref-goal
    ..... encounter 0..1 Encounter
    ..... observation 0..1 GoalObservation Use to embed a Goal Observation directly
    ..... observationMedia 0..1 ObservationMedia
    ..... organizer 0..1 Organizer
    ..... procedure 0..1 Procedure
    ..... regionOfInterest 0..1 RegionOfInterest
    ..... substanceAdministration 0..1 SubstanceAdministration
    ..... supply 0..1 Supply
    .... entryRelationship:supportingInfo 0..* EntryRelationship Information considered as part of the plan (CarePlan.supportingInfo)
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: SPRT
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act 0..1 Act
    ..... 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
    .... entryRelationship:activity 0..* EntryRelationship Activity to occur as part of plan (CarePlan.activity). Common examples include the Intervention Act and Planned Intervention Act, but any entry may be considered an activity of the care plan.
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: COMP
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act 0..1 InterventionAct, PlannedInterventionAct, Act A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... encounter 0..1 Encounter A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... observation 0..1 Observation A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... observationMedia 0..1 ObservationMedia
    ..... organizer 0..1 Organizer
    ..... procedure 0..1 Procedure
    ..... regionOfInterest 0..1 RegionOfInterest
    ..... substanceAdministration 0..1 SubstanceAdministration
    ..... supply 0..1 Supply A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ... reference 0..* Reference
    ... precondition 0..* Precondition
    ... sdtcPrecondition2 0..* Precondition2 XML Namespace: urn:hl7-org:sdtc
    XML: precondition2 (urn:hl7-org:sdtc)
    ... sdtcInFulfillmentOf1 0..* InFulfillmentOf1 XML Namespace: urn:hl7-org:sdtc
    XML: inFulfillmentOf1 (urn:hl7-org:sdtc)

    doco Documentation for this format

    Terminology Bindings

    Path Status Usage ValueSet Version Source
    Act.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.templateId:care-plan-act.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.classCode Base required x_ActClassDocumentEntryAct 📍2.0.0 THO v5.2
    Act.moodCode Base required Care Plan Mood Codes . 📦20251123 VSAC v0.24
    Act.code Base example v3 Code System ActCode 📦3.0.0 THO v7.0
    Act.code.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.code.translation Base preferred Care Plan Category 📦5.0.0 FHIR Std.
    Act.text.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.text.compression Base required CDACompressionAlgorithm 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.text.integrityCheckAlgorithm Base required IntegrityCheckAlgorithm 📍2.0.0 THO v5.2
    Act.text.mediaType Base example MediaType 📦3.0.0 THO v7.0
    Act.text.representation Base required CDABinaryDataEncoding 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.statusCode Base required ActStatus 📦3.0.0 THO v7.0
    Act.priorityCode Base example ActPriority 📦3.0.0 THO v7.0
    Act.languageCode Base required All Languages 📦5.0.0 FHIR Std.
    Act.entryRelationship:addresses.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:addresses.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:addresses.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0
    Act.entryRelationship:goal.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:goal.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:goal.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0
    Act.entryRelationship:supportingInfo.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:supportingInfo.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:supportingInfo.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0
    Act.entryRelationship:activity.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:activity.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:activity.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0

    Constraints

    Id Grade Path(s) Description Expression
    ED-1 error Act.text.thumbnail Thumbnails cannot contain their own thumbnails thumbnail.empty()
    II-1 error Act.typeId, Act.entryRelationship:addresses.typeId, Act.entryRelationship:goal.typeId, Act.entryRelationship:supportingInfo.typeId, Act.entryRelationship:activity.typeId An II instance must have either a root or an nullFlavor. root.exists() or nullFlavor.exists()
    act-or-observation error Act.entryRelationship:addresses, Act.entryRelationship:goal Either act or observation SHALL be present but not both. act.exists() or observation.exists()
    entry-ref-goal error Act.entryRelationship:goal.act This entryReference template **SHALL** reference an instance of a Goal Observation template. %resource.descendants().ofType(CDA.Observation).where(templateId.exists($this.root = '2.16.840.1.113883.10.20.22.4.121' and $this.extension = '2022-06-01') and id.exists($this.root = %context.id.first().root and $this.extension ~ %context.id.first().extension))
    should-text-ref-value warning Act SHOULD contain text/reference/@value text.reference.value.exists()
    value-starts-octothorpe error Act.text.reference If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative value.exists() implies value.startsWith('#')

    Differential View

    This structure is derived from Act

    NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
    .. Act C 1..1 Act XML Namespace: urn:hl7-org:v3
    Base for all types and resources
    Instance of this type are validated by templateId
    Logical Container: ClinicalDocument (CDA Class)
    Constraints: should-text-ref-value
    ... Slices for templateId 1..* II Slice: Unordered, Open by value:root, value:extension
    .... templateId:care-plan-act 1..1 II
    ..... @root 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.10.20.22.4.518
    ..... @extension 1..1 st Required Pattern: 2026-05-01
    ... @moodCode 1..1 cs CarePlan.intent
    Binding: Care Plan Mood Codes . (required)
    ... code 1..1 CD Plan of care note
    .... @code 1..1 cs Required Pattern: 18776-5
    .... @codeSystem 1..1 oid, uuid, ruid LOINC
    Required Pattern: 2.16.840.1.113883.6.1
    .... translation 0..* CD Binding: CarePlanCategory (preferred)
    .... reference C 0..1 TEL Constraints: value-starts-octothorpe
    ... statusCode 1..1 CS CarePlan.status
    ... author 0..* AuthorParticipation CarePlan.contributor
    ... Slices for entryRelationship 0..* EntryRelationship Entries can be embedded directly or referenced via EntryReference. Use the @typeCode attribute to distinguish the type of relationship.
    Slice: Unordered, Open by value:typeCode
    .... entryRelationship:addresses C 0..* EntryRelationship 𝗨𝗦𝗖𝗗𝗜: CarePlan.addresses
    Constraints: act-or-observation
    ..... @typeCode 1..1 cs Required Pattern: RSON
    ..... act 0..1 EntryReference, Act References an Indication, Problem Observation, or other Problem described elsewhere in the document.
    ..... observation 0..1 Indication, ProblemObservation, Observation Directly-embedded Problem or Indication observation. Use EntryReference to reference an existing problem observation or indication described elsewhere in the document.
    .... entryRelationship:goal C 0..* EntryRelationship Desired outcome of the plan (CarePlan.goal). Can embed a Goal Observation directly or use the EntryReference template to reference a Goal Observation described elsewhere in the document.
    Constraints: act-or-observation
    ..... @typeCode 1..1 cs Required Pattern: GEVL
    ..... act C 0..1 EntryReference Use to reference a Goal Observation elsewhere
    Constraints: entry-ref-goal
    ..... observation 0..1 GoalObservation Use to embed a Goal Observation directly
    .... entryRelationship:supportingInfo 0..* EntryRelationship Information considered as part of the plan (CarePlan.supportingInfo)
    ..... @typeCode 1..1 cs Required Pattern: SPRT
    .... entryRelationship:activity 0..* EntryRelationship Activity to occur as part of plan (CarePlan.activity). Common examples include the Intervention Act and Planned Intervention Act, but any entry may be considered an activity of the care plan.
    ..... @typeCode 1..1 cs Required Pattern: COMP
    ..... act 0..1 InterventionAct, PlannedInterventionAct, Act A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... encounter 0..1 Encounter A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... observation 0..1 Observation A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... supply 0..1 Supply A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.

    doco Documentation for this format

    Terminology Bindings (Differential)

    Path Status Usage ValueSet Version Source
    Act.moodCode Base required Care Plan Mood Codes . 📦20251123 VSAC v0.24
    Act.code.translation Base preferred Care Plan Category 📦5.0.0 FHIR Std.

    Constraints

    Id Grade Path(s) Description Expression
    act-or-observation error Act.entryRelationship:addresses, Act.entryRelationship:goal Either act or observation SHALL be present but not both. act.exists() or observation.exists()
    entry-ref-goal error Act.entryRelationship:goal.act This entryReference template **SHALL** reference an instance of a Goal Observation template. %resource.descendants().ofType(CDA.Observation).where(templateId.exists($this.root = '2.16.840.1.113883.10.20.22.4.121' and $this.extension = '2022-06-01') and id.exists($this.root = %context.id.first().root and $this.extension ~ %context.id.first().extension))
    should-text-ref-value warning Act SHOULD contain text/reference/@value text.reference.value.exists()
    value-starts-octothorpe error Act.text.reference If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative value.exists() implies value.startsWith('#')

    Key Elements View

    NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
    .. Act C 1..1 Act XML Namespace: urn:hl7-org:v3
    Base for all types and resources
    Instance of this type are validated by templateId
    Logical Container: ClinicalDocument (CDA Class)
    Constraints: should-text-ref-value
    ... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ... realmCode 0..* CS
    ... typeId C 0..1 II Constraints: II-1
    .... @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:care-plan-act 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.4.518
    ..... @extension 1..1 st Required Pattern: 2026-05-01
    ... @classCode 1..1 cs Binding: XActClassDocumentEntryAct (2.0.0) (required)
    ... @moodCode 1..1 cs CarePlan.intent
    Binding: Care Plan Mood Codes . (required)
    ... @negationInd 0..1 bl
    ... id 0..* II
    ... code 1..1 CD Plan of care note
    Binding: v3 Code System ActCode (example)
    .... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    .... @code 1..1 cs Required Pattern: 18776-5
    .... @codeSystem 1..1 oid, uuid, ruid LOINC
    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
    .... qualifier 0..* CR
    .... translation 0..* CD Binding: CarePlanCategory (preferred)
    ... text C 0..1 ED SHOULD reference the portion of section narrative text corresponding to this entry
    .... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    .... @compression 0..1 cs Binding: CDACompressionAlgorithm (required)
    .... @integrityCheck 0..1 bin
    .... @integrityCheckAlgorithm 0..1 cs Binding: IntegrityCheckAlgorithm (2.0.0) (required)
    .... @language 0..1 cs
    .... @mediaType 0..1 cs Binding: MediaType (example)
    .... @representation 0..1 cs Binding: CDABinaryDataEncoding (required)
    .... xmlText 0..1 st Allows for mixed text content. If @representation='B64', this SHALL be a base64binary string.
    .... reference C 0..1 TEL Constraints: value-starts-octothorpe
    .... thumbnail C 0..1 ED Constraints: ED-1
    ... statusCode 1..1 CS CarePlan.status
    Binding: ActStatus (required)
    ... effectiveTime 0..1 IVL_TS
    ... priorityCode 0..1 CE Binding: ActPriority (example)
    ... languageCode 0..1 CS Binding: AllLanguages (required)
    ... subject 0..1 Subject
    ... specimen 0..* Specimen
    ... performer 0..* Performer2
    ... author 0..* AuthorParticipation CarePlan.contributor
    ... informant 0..* Informant
    ... participant 0..* Participant2
    ... Slices for entryRelationship 0..* EntryRelationship Entries can be embedded directly or referenced via EntryReference. Use the @typeCode attribute to distinguish the type of relationship.
    Slice: Unordered, Open by value:typeCode
    .... entryRelationship:addresses C 0..* EntryRelationship 𝗨𝗦𝗖𝗗𝗜: CarePlan.addresses
    Constraints: act-or-observation
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: RSON
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act 0..1 EntryReference, Act References an Indication, Problem Observation, or other Problem described elsewhere in the document.
    ..... encounter 0..1 Encounter
    ..... observation 0..1 Indication, ProblemObservation, Observation Directly-embedded Problem or Indication observation. Use EntryReference to reference an existing problem observation or indication described elsewhere in the document.
    ..... observationMedia 0..1 ObservationMedia
    ..... organizer 0..1 Organizer
    ..... procedure 0..1 Procedure
    ..... regionOfInterest 0..1 RegionOfInterest
    ..... substanceAdministration 0..1 SubstanceAdministration
    ..... supply 0..1 Supply
    .... entryRelationship:goal C 0..* EntryRelationship Desired outcome of the plan (CarePlan.goal). Can embed a Goal Observation directly or use the EntryReference template to reference a Goal Observation described elsewhere in the document.
    Constraints: act-or-observation
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: GEVL
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act C 0..1 EntryReference Use to reference a Goal Observation elsewhere
    Constraints: entry-ref-goal
    ..... encounter 0..1 Encounter
    ..... observation 0..1 GoalObservation Use to embed a Goal Observation directly
    ..... observationMedia 0..1 ObservationMedia
    ..... organizer 0..1 Organizer
    ..... procedure 0..1 Procedure
    ..... regionOfInterest 0..1 RegionOfInterest
    ..... substanceAdministration 0..1 SubstanceAdministration
    ..... supply 0..1 Supply
    .... entryRelationship:supportingInfo 0..* EntryRelationship Information considered as part of the plan (CarePlan.supportingInfo)
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: SPRT
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act 0..1 Act
    ..... 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
    .... entryRelationship:activity 0..* EntryRelationship Activity to occur as part of plan (CarePlan.activity). Common examples include the Intervention Act and Planned Intervention Act, but any entry may be considered an activity of the care plan.
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: COMP
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act 0..1 InterventionAct, PlannedInterventionAct, Act A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... encounter 0..1 Encounter A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... observation 0..1 Observation A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... observationMedia 0..1 ObservationMedia
    ..... organizer 0..1 Organizer
    ..... procedure 0..1 Procedure
    ..... regionOfInterest 0..1 RegionOfInterest
    ..... substanceAdministration 0..1 SubstanceAdministration
    ..... supply 0..1 Supply A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ... reference 0..* Reference
    ... precondition 0..* Precondition
    ... sdtcPrecondition2 0..* Precondition2 XML Namespace: urn:hl7-org:sdtc
    XML: precondition2 (urn:hl7-org:sdtc)
    ... sdtcInFulfillmentOf1 0..* InFulfillmentOf1 XML Namespace: urn:hl7-org:sdtc
    XML: inFulfillmentOf1 (urn:hl7-org:sdtc)

    doco Documentation for this format

    Terminology Bindings

    Path Status Usage ValueSet Version Source
    Act.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.templateId:care-plan-act.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.classCode Base required x_ActClassDocumentEntryAct 📍2.0.0 THO v5.2
    Act.moodCode Base required Care Plan Mood Codes . 📦20251123 VSAC v0.24
    Act.code Base example v3 Code System ActCode 📦3.0.0 THO v7.0
    Act.code.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.code.translation Base preferred Care Plan Category 📦5.0.0 FHIR Std.
    Act.text.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.text.compression Base required CDACompressionAlgorithm 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.text.integrityCheckAlgorithm Base required IntegrityCheckAlgorithm 📍2.0.0 THO v5.2
    Act.text.mediaType Base example MediaType 📦3.0.0 THO v7.0
    Act.text.representation Base required CDABinaryDataEncoding 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.statusCode Base required ActStatus 📦3.0.0 THO v7.0
    Act.priorityCode Base example ActPriority 📦3.0.0 THO v7.0
    Act.languageCode Base required All Languages 📦5.0.0 FHIR Std.
    Act.entryRelationship:addresses.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:addresses.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:addresses.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0
    Act.entryRelationship:goal.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:goal.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:goal.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0
    Act.entryRelationship:supportingInfo.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:supportingInfo.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:supportingInfo.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0
    Act.entryRelationship:activity.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:activity.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:activity.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0

    Constraints

    Id Grade Path(s) Description Expression
    ED-1 error Act.text.thumbnail Thumbnails cannot contain their own thumbnails thumbnail.empty()
    II-1 error Act.typeId, Act.entryRelationship:addresses.typeId, Act.entryRelationship:goal.typeId, Act.entryRelationship:supportingInfo.typeId, Act.entryRelationship:activity.typeId An II instance must have either a root or an nullFlavor. root.exists() or nullFlavor.exists()
    act-or-observation error Act.entryRelationship:addresses, Act.entryRelationship:goal Either act or observation SHALL be present but not both. act.exists() or observation.exists()
    entry-ref-goal error Act.entryRelationship:goal.act This entryReference template **SHALL** reference an instance of a Goal Observation template. %resource.descendants().ofType(CDA.Observation).where(templateId.exists($this.root = '2.16.840.1.113883.10.20.22.4.121' and $this.extension = '2022-06-01') and id.exists($this.root = %context.id.first().root and $this.extension ~ %context.id.first().extension))
    should-text-ref-value warning Act SHOULD contain text/reference/@value text.reference.value.exists()
    value-starts-octothorpe error Act.text.reference If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative value.exists() implies value.startsWith('#')

    Snapshot View

    NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
    .. Act C 1..1 Act XML Namespace: urn:hl7-org:v3
    Base for all types and resources
    Instance of this type are validated by templateId
    Logical Container: ClinicalDocument (CDA Class)
    Constraints: should-text-ref-value
    ... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ... realmCode 0..* CS
    ... typeId C 0..1 II Constraints: II-1
    .... @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:care-plan-act 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.4.518
    ..... @extension 1..1 st Required Pattern: 2026-05-01
    ... @classCode 1..1 cs Binding: XActClassDocumentEntryAct (2.0.0) (required)
    ... @moodCode 1..1 cs CarePlan.intent
    Binding: Care Plan Mood Codes . (required)
    ... @negationInd 0..1 bl
    ... id 0..* II
    ... code 1..1 CD Plan of care note
    Binding: v3 Code System ActCode (example)
    .... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    .... @code 1..1 cs Required Pattern: 18776-5
    .... @codeSystem 1..1 oid, uuid, ruid LOINC
    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
    .... qualifier 0..* CR
    .... translation 0..* CD Binding: CarePlanCategory (preferred)
    ... text C 0..1 ED SHOULD reference the portion of section narrative text corresponding to this entry
    .... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    .... @compression 0..1 cs Binding: CDACompressionAlgorithm (required)
    .... @integrityCheck 0..1 bin
    .... @integrityCheckAlgorithm 0..1 cs Binding: IntegrityCheckAlgorithm (2.0.0) (required)
    .... @language 0..1 cs
    .... @mediaType 0..1 cs Binding: MediaType (example)
    .... @representation 0..1 cs Binding: CDABinaryDataEncoding (required)
    .... xmlText 0..1 st Allows for mixed text content. If @representation='B64', this SHALL be a base64binary string.
    .... reference C 0..1 TEL Constraints: value-starts-octothorpe
    .... thumbnail C 0..1 ED Constraints: ED-1
    ... statusCode 1..1 CS CarePlan.status
    Binding: ActStatus (required)
    ... effectiveTime 0..1 IVL_TS
    ... priorityCode 0..1 CE Binding: ActPriority (example)
    ... languageCode 0..1 CS Binding: AllLanguages (required)
    ... subject 0..1 Subject
    ... specimen 0..* Specimen
    ... performer 0..* Performer2
    ... author 0..* AuthorParticipation CarePlan.contributor
    ... informant 0..* Informant
    ... participant 0..* Participant2
    ... Slices for entryRelationship 0..* EntryRelationship Entries can be embedded directly or referenced via EntryReference. Use the @typeCode attribute to distinguish the type of relationship.
    Slice: Unordered, Open by value:typeCode
    .... entryRelationship:addresses C 0..* EntryRelationship 𝗨𝗦𝗖𝗗𝗜: CarePlan.addresses
    Constraints: act-or-observation
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: RSON
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act 0..1 EntryReference, Act References an Indication, Problem Observation, or other Problem described elsewhere in the document.
    ..... encounter 0..1 Encounter
    ..... observation 0..1 Indication, ProblemObservation, Observation Directly-embedded Problem or Indication observation. Use EntryReference to reference an existing problem observation or indication described elsewhere in the document.
    ..... observationMedia 0..1 ObservationMedia
    ..... organizer 0..1 Organizer
    ..... procedure 0..1 Procedure
    ..... regionOfInterest 0..1 RegionOfInterest
    ..... substanceAdministration 0..1 SubstanceAdministration
    ..... supply 0..1 Supply
    .... entryRelationship:goal C 0..* EntryRelationship Desired outcome of the plan (CarePlan.goal). Can embed a Goal Observation directly or use the EntryReference template to reference a Goal Observation described elsewhere in the document.
    Constraints: act-or-observation
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: GEVL
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act C 0..1 EntryReference Use to reference a Goal Observation elsewhere
    Constraints: entry-ref-goal
    ..... encounter 0..1 Encounter
    ..... observation 0..1 GoalObservation Use to embed a Goal Observation directly
    ..... observationMedia 0..1 ObservationMedia
    ..... organizer 0..1 Organizer
    ..... procedure 0..1 Procedure
    ..... regionOfInterest 0..1 RegionOfInterest
    ..... substanceAdministration 0..1 SubstanceAdministration
    ..... supply 0..1 Supply
    .... entryRelationship:supportingInfo 0..* EntryRelationship Information considered as part of the plan (CarePlan.supportingInfo)
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: SPRT
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act 0..1 Act
    ..... 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
    .... entryRelationship:activity 0..* EntryRelationship Activity to occur as part of plan (CarePlan.activity). Common examples include the Intervention Act and Planned Intervention Act, but any entry may be considered an activity of the care plan.
    ..... @nullFlavor 0..1 cs Binding: CDANullFlavor (required)
    ..... realmCode 0..* CS
    ..... typeId C 0..1 II Constraints: II-1
    ...... @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 1..1 cs Binding: x_ActRelationshipEntryRelationship (required)
    Required Pattern: COMP
    ..... @inversionInd 0..1 bl
    ..... @contextConductionInd 0..1 bl
    ..... @negationInd 0..1 bl
    ..... sequenceNumber 0..1 INT
    ..... seperatableInd 0..1 BL
    ..... act 0..1 InterventionAct, PlannedInterventionAct, Act A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... encounter 0..1 Encounter A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... observation 0..1 Observation A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ..... observationMedia 0..1 ObservationMedia
    ..... organizer 0..1 Organizer
    ..... procedure 0..1 Procedure
    ..... regionOfInterest 0..1 RegionOfInterest
    ..... substanceAdministration 0..1 SubstanceAdministration
    ..... supply 0..1 Supply A care plan may have multiple COMP entryRelationships, but each entryRelationship may only have a single act/encounter/observation/supply or other clinical statement.
    ... reference 0..* Reference
    ... precondition 0..* Precondition
    ... sdtcPrecondition2 0..* Precondition2 XML Namespace: urn:hl7-org:sdtc
    XML: precondition2 (urn:hl7-org:sdtc)
    ... sdtcInFulfillmentOf1 0..* InFulfillmentOf1 XML Namespace: urn:hl7-org:sdtc
    XML: inFulfillmentOf1 (urn:hl7-org:sdtc)

    doco Documentation for this format

    Terminology Bindings

    Path Status Usage ValueSet Version Source
    Act.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.templateId:care-plan-act.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.classCode Base required x_ActClassDocumentEntryAct 📍2.0.0 THO v5.2
    Act.moodCode Base required Care Plan Mood Codes . 📦20251123 VSAC v0.24
    Act.code Base example v3 Code System ActCode 📦3.0.0 THO v7.0
    Act.code.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.code.translation Base preferred Care Plan Category 📦5.0.0 FHIR Std.
    Act.text.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.text.compression Base required CDACompressionAlgorithm 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.text.integrityCheckAlgorithm Base required IntegrityCheckAlgorithm 📍2.0.0 THO v5.2
    Act.text.mediaType Base example MediaType 📦3.0.0 THO v7.0
    Act.text.representation Base required CDABinaryDataEncoding 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.statusCode Base required ActStatus 📦3.0.0 THO v7.0
    Act.priorityCode Base example ActPriority 📦3.0.0 THO v7.0
    Act.languageCode Base required All Languages 📦5.0.0 FHIR Std.
    Act.entryRelationship:addresses.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:addresses.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:addresses.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0
    Act.entryRelationship:goal.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:goal.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:goal.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0
    Act.entryRelationship:supportingInfo.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:supportingInfo.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:supportingInfo.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0
    Act.entryRelationship:activity.​nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:activity.​typeId.nullFlavor Base required CDANullFlavor 📦2.0.2-sd Clinical Document Architecture v2.0
    Act.entryRelationship:activity.​typeCode Base required x_ActRelationshipEntryRelationship 📦3.0.0 THO v7.0

    Constraints

    Id Grade Path(s) Description Expression
    ED-1 error Act.text.thumbnail Thumbnails cannot contain their own thumbnails thumbnail.empty()
    II-1 error Act.typeId, Act.entryRelationship:addresses.typeId, Act.entryRelationship:goal.typeId, Act.entryRelationship:supportingInfo.typeId, Act.entryRelationship:activity.typeId An II instance must have either a root or an nullFlavor. root.exists() or nullFlavor.exists()
    act-or-observation error Act.entryRelationship:addresses, Act.entryRelationship:goal Either act or observation SHALL be present but not both. act.exists() or observation.exists()
    entry-ref-goal error Act.entryRelationship:goal.act This entryReference template **SHALL** reference an instance of a Goal Observation template. %resource.descendants().ofType(CDA.Observation).where(templateId.exists($this.root = '2.16.840.1.113883.10.20.22.4.121' and $this.extension = '2022-06-01') and id.exists($this.root = %context.id.first().root and $this.extension ~ %context.id.first().extension))
    should-text-ref-value warning Act SHOULD contain text/reference/@value text.reference.value.exists()
    value-starts-octothorpe error Act.text.reference If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative value.exists() implies value.startsWith('#')

     

    Other representations of profile: CSV, Excel