Planned Encounter - Definitions - Consolidated CDA (C-CDA) v3.0.0

This page is part of the CCDA: Consolidated CDA Release (v3.0.0: CCDA 3.0) generated with FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions

Logical Model: PlannedEncounter - Detailed Descriptions

Draft as of 2024-05-18

Definitions for the PlannedEncounter logical model.

Differential Elements Table
Key Elements Table
Snapshot Elements Table

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

0. Encounter
Logical Container	ClinicalDocument (CDA Class)
Validation	Instance of this type are validated by templateId
XML Format	In the XML format, this property has the namespace `urn:hl7-org:v3`.
Invariants	should-text-ref-value: SHOULD contain text/reference/@value (`text.reference.value.exists()`) should-code: SHOULD contain code (`code.exists()`) should-effectiveTime: SHOULD contain effectiveTime (`effectiveTime.exists()`) should-author: SHOULD contain author (`author.exists()`)
2. Encounter.templateId
Control	1..?
Slicing	This element introduces a set of slices on `Encounter.templateId`. The slices areUnordered and Open, and can be differentiated using the following discriminators: value @ root value @ extension
4. Encounter.templateId:planned-enc
Slice Name	planned-enc
Control	1..1
6. Encounter.templateId:planned-enc.root
Control	1..?
Pattern Value	`2.16.840.1.113883.10.20.22.4.40`
8. Encounter.templateId:planned-enc.extension
Control	1..?
Pattern Value	`2014-06-09`
10. Encounter.classCode
Comments	SHALL contain exactly one [1..1] @classCode="ENC" (CodeSystem: HL7ActClass urn:oid:2.16.840.1.113883.5.6 STATIC) (CONF:1098-8564).
12. Encounter.moodCode
Comments	SHALL contain exactly one [1..1] @moodCode, which SHALL be selected from ValueSet Planned moodCode (Act/Encounter/Procedure) urn:oid:2.16.840.1.113883.11.20.9.23 STATIC 2014-09-01 (CONF:1098-8565).
Binding	The codes SHALL be taken from Planned moodCode (Act/Encounter/Procedure) (required to `http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.23`)
14. Encounter.id
Comments	SHALL contain at least one [1..*] id (CONF:1098-8567).
Control	1..?
16. Encounter.code
Short	Records the type of encounter ordered or recommended.
Comments	SHOULD contain zero or one [0..1] code, which SHOULD be selected from ValueSet Encounter Planned urn:oid:2.16.840.1.113883.11.20.9.52 DYNAMIC (CONF:1098-31032).
Binding	The codes SHOULD be taken from Encounter Planned (preferred to `http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.52`)
18. Encounter.text
Short	SHOULD reference the portion of section narrative text corresponding to this entry
20. Encounter.text.reference
Invariants	value-starts-octothorpe: If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative (`value.exists() implies value.startsWith('#')`)
22. Encounter.statusCode
Comments	SHALL contain exactly one [1..1] statusCode (CONF:1098-30439).
Control	1..?
24. Encounter.statusCode.code
Comments	This statusCode SHALL contain exactly one [1..1] @code="active" Active (CodeSystem: HL7ActStatus urn:oid:2.16.840.1.113883.5.14) (CONF:1098-31880).
Control	1..?
Fixed Value	`active`
26. Encounter.effectiveTime
Comments	SHOULD contain zero or one [0..1] effectiveTime (CONF:1098-30440).
28. Encounter.performer
Short	Performers represent clinicians who are responsible for assessing and treating the patient.
Comments	MAY contain zero or more [0..*] performer (CONF:1098-30442) such that it
30. Encounter.performer.assignedEntity
Comments	SHALL contain exactly one [1..1] assignedEntity (CONF:1098-31874).
32. Encounter.author
Short	The author in a planned encounter represents the clinician who is requesting or planning the encounter.
Comments	SHOULD contain zero or more [0..*] Author Participation (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.119) (CONF:1098-32045).
Type	http://hl7.org/cda/stds/core/StructureDefinition/Author(Author Participation)
34. Encounter.participant
Short	This location participation captures where the planned or ordered encounter may take place.
Slicing	This element introduces a set of slices on `Encounter.participant`. The slices areUnordered and Open, and can be differentiated using the following discriminators: value @ typeCode
36. Encounter.participant:location
Slice Name	location
Comments	MAY contain zero or more [0..*] participant (CONF:1098-30443) such that it
Control	0..*
38. Encounter.participant:location.typeCode
Comments	SHALL contain exactly one [1..1] @typeCode="LOC" Location (CodeSystem: HL7ParticipationType urn:oid:2.16.840.1.113883.5.90) (CONF:1098-31875).
Fixed Value	`LOC`
40. Encounter.participant:location.participantRole
Comments	SHALL contain exactly one [1..1] Service Delivery Location (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.32) (CONF:1098-31876).
Type	http://hl7.org/cda/stds/core/StructureDefinition/ParticipantRole(Service Delivery Location)
42. Encounter.entryRelationship
Short	The following entryRelationship captures the reason for the planned or ordered encounter
Slicing	This element introduces a set of slices on `Encounter.entryRelationship`. The slices areUnordered and Open, and can be differentiated using the following discriminators: profile @ observation
44. Encounter.entryRelationship:priorityPreference
Slice Name	priorityPreference
Short	The following entryRelationship represents the priority that a patient or a provider places on the encounter.
Comments	MAY contain zero or one [0..1] entryRelationship (CONF:1098-31033) such that it
Control	0..1
46. Encounter.entryRelationship:priorityPreference.typeCode
Comments	SHALL contain exactly one [1..1] @typeCode="REFR" Refers to (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002) (CONF:1098-31034).
Fixed Value	`REFR`
48. Encounter.entryRelationship:priorityPreference.observation
Comments	SHALL contain exactly one [1..1] Priority Preference (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.143) (CONF:1098-31035).
Control	1..?
Type	http://hl7.org/cda/stds/core/StructureDefinition/Observation(Priority Preference)
50. Encounter.entryRelationship:indication
Slice Name	indication
Comments	MAY contain zero or more [0..*] entryRelationship (CONF:1098-31877) such that it
Control	0..*
52. Encounter.entryRelationship:indication.typeCode
Comments	SHALL contain exactly one [1..1] @typeCode="RSON" Has Reason (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002) (CONF:1098-31878).
Fixed Value	`RSON`
54. Encounter.entryRelationship:indication.observation
Comments	SHALL contain exactly one [1..1] Indication (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.4.19:2014-06-09) (CONF:1098-31879).
Control	1..?
Type	http://hl7.org/cda/stds/core/StructureDefinition/Observation(Indication)

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

0. Encounter
Definition	Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type. Base definition for all types defined in FHIR type system.
Short	Base for all types and resources
Control	10..1*
Is Modifier	false
Logical Container	ClinicalDocument (CDA Class)
Validation	Instance of this type are validated by templateId
XML Format	In the XML format, this property has the namespace `urn:hl7-org:v3`.
Invariants	should-text-ref-value: SHOULD contain text/reference/@value (`text.reference.value.exists()`) should-code: SHOULD contain code (`code.exists()`) should-effectiveTime: SHOULD contain effectiveTime (`effectiveTime.exists()`) should-author: SHOULD contain author (`author.exists()`)
2. Encounter.templateId
Definition	When valued in an instance, this attribute signals the imposition of a set of template-defined constraints. The value of this attribute provides a unique identifier for the templates in question
Control	1..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/II
Slicing	This element introduces a set of slices on `Encounter.templateId`. The slices areUnordered and Open, and can be differentiated using the following discriminators: value @ root value @ extension
4. Encounter.templateId:planned-enc
Slice Name	planned-enc
Definition	When valued in an instance, this attribute signals the imposition of a set of template-defined constraints. The value of this attribute provides a unique identifier for the templates in question
Control	1..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/II
6. Encounter.templateId:planned-enc.root
Definition	A unique identifier that guarantees the global uniqueness of the instance identifier. The root alone may be the entire instance identifier.
Control	1..1
Type	string(oid: ISO Object Identifier, uuid: DCE Universal Unique Identifier, ruid: HL7 Reserved Identifier Scheme)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Root
Pattern Value	`2.16.840.1.113883.10.20.22.4.40`
8. Encounter.templateId:planned-enc.extension
Definition	A character string as a unique identifier within the scope of the identifier root.
Control	1..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Extension
Pattern Value	`2014-06-09`
10. Encounter.classCode
Comments	SHALL contain exactly one [1..1] @classCode="ENC" (CodeSystem: HL7ActClass urn:oid:2.16.840.1.113883.5.6 STATIC) (CONF:1098-8564).
Control	1..1
Binding	The codes SHALL be taken from CDAActClass (required to `http://hl7.org/cda/stds/core/ValueSet/CDAActClass`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Fixed Value	`ENC`
12. Encounter.moodCode
Comments	SHALL contain exactly one [1..1] @moodCode, which SHALL be selected from ValueSet Planned moodCode (Act/Encounter/Procedure) urn:oid:2.16.840.1.113883.11.20.9.23 STATIC 2014-09-01 (CONF:1098-8565).
Control	1..1
Binding	The codes SHALL be taken from Planned moodCode (Act/Encounter/Procedure) (required to `http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.23`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
14. Encounter.id
Definition	The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Short	Logical id of this artifact
Comments	SHALL contain at least one [1..*] id (CONF:1098-8567). Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
Control	10..*1
Type	http://hl7.org/cda/stds/core/StructureDefinition/IIid
Is Modifier	false
16. Encounter.code
Short	Records the type of encounter ordered or recommended.
Comments	SHOULD contain zero or one [0..1] code, which SHOULD be selected from ValueSet Encounter Planned urn:oid:2.16.840.1.113883.11.20.9.52 DYNAMIC (CONF:1098-31032).
Control	0..1
Binding	The codes SHOULD be taken from Encounter Planned (preferred to `http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.52`)
Type	http://hl7.org/cda/stds/core/StructureDefinition/CD
18. Encounter.text
Definition	A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Short	SHOULD reference the portion of section narrative text corresponding to this entryText summary of the resource, for human interpretation
Comments	Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
Control	0..1 This element is affected by the following invariants: dom-6
Type	http://hl7.org/cda/stds/core/StructureDefinition/EDNarrative
Is Modifier	false
Alternate Names	narrative, html, xhtml, display
Invariants	ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()))
20. Encounter.text.reference
Definition	A telecommunication address (TEL), such as a URL for HTTP or FTP, which will resolve to precisely the same binary data that could as well have been provided as inline data.
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/TEL
Label	Reference
Invariants	value-starts-octothorpe: If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative (`value.exists() implies value.startsWith('#')`)
22. Encounter.statusCode
Comments	SHALL contain exactly one [1..1] statusCode (CONF:1098-30439).
Control	1..1
Binding	The codes SHALL be taken from ActStatus (required to `http://terminology.hl7.org/ValueSet/v3-ActStatus`)
Type	http://hl7.org/cda/stds/core/StructureDefinition/CS
24. Encounter.statusCode.code
Definition	The plain code symbol defined by the code system. For example, "784.0" is the code symbol of the ICD-9 code "784.0" for headache.
Comments	This statusCode SHALL contain exactly one [1..1] @code="active" Active (CodeSystem: HL7ActStatus urn:oid:2.16.840.1.113883.5.14) (CONF:1098-31880).
Control	1..1
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Code
Fixed Value	`active`
26. Encounter.statusCode.codeSystem
Definition	Specifies the code system that defines the code.
Control	0..0
Type	string(oid: ISO Object Identifier, uuid: DCE Universal Unique Identifier, ruid: HL7 Reserved Identifier Scheme)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Code System
28. Encounter.statusCode.codeSystemName
Definition	The common name of the coding system.
Control	0..0
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Code System Name
30. Encounter.statusCode.codeSystemVersion
Definition	If applicable, a version descriptor defined specifically for the given code system.
Control	0..0
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Code System Version
32. Encounter.statusCode.displayName
Definition	A name or title for the code, under which the sending system shows the code value to its users.
Control	0..0
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Display Name
34. Encounter.statusCode.originalText
Definition	The text or phrase used as the basis for the coding.
Control	0..0
Type	http://hl7.org/cda/stds/core/StructureDefinition/ED
Label	Original Text
36. Encounter.statusCode.qualifier
Definition	Specifies additional codes that increase the specificity of the the primary code.
Control	0..0
Type	http://hl7.org/cda/stds/core/StructureDefinition/CR
Label	Qualifier
38. Encounter.statusCode.translation
Definition	A set of other concept descriptors that translate this concept descriptor into other code systems.
Control	0..0
Type	http://hl7.org/cda/stds/core/StructureDefinition/CD
XML Format	The type of this property is determined using the " `xsi:type`attribute.
Label	Translation
40. Encounter.effectiveTime
Comments	SHOULD contain zero or one [0..1] effectiveTime (CONF:1098-30440).
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/IVL-TS
42. Encounter.performer
Short	Performers represent clinicians who are responsible for assessing and treating the patient.
Comments	MAY contain zero or more [0..*] performer (CONF:1098-30442) such that it
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/Performer2
44. Encounter.performer.assignedEntity
Comments	SHALL contain exactly one [1..1] assignedEntity (CONF:1098-31874).
Control	1..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/AssignedEntity
46. Encounter.author
Definition	Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type.
Short	The author in a planned encounter represents the clinician who is requesting or planning the encounter.
Comments	SHOULD contain zero or more [0..*] Author Participation (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.119) (CONF:1098-32045).
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/Author(Author Participation)
Is Modifier	false
48. Encounter.participant
Definition	The list of people responsible for providing the service.
Short	This location participation captures where the planned or ordered encounter may take place.List of participants involved in the encounter
Comments	Any Patient or Group present in the participation.actor must also be the subject, though the subject may be absent from the participation.actor for cases where the patient (or group) is not present, such as during a case review conference.
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/Participant2BackboneElement
Is Modifier	false
Invariants	ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count())) enc-1: A type must be provided when no explicit actor is specified (actor.exists() or type.exists()) enc-2: A type cannot be provided for a patient or group participant (actor.exists(resolve() is Patient or resolve() is Group) implies type.exists().not())
Slicing	This element introduces a set of slices on `Encounter.participant`. The slices areUnordered and Open, and can be differentiated using the following discriminators: value @ typeCode
50. Encounter.participant:location
Slice Name	location
Definition	The list of people responsible for providing the service.
Short	List of participants involved in the encounter
Comments	MAY contain zero or more [0..*] participant (CONF:1098-30443) such that it Any Patient or Group present in the participation.actor must also be the subject, though the subject may be absent from the participation.actor for cases where the patient (or group) is not present, such as during a case review conference.
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/Participant2BackboneElement
Is Modifier	false
Invariants	ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count())) enc-1: A type must be provided when no explicit actor is specified (actor.exists() or type.exists()) enc-2: A type cannot be provided for a patient or group participant (actor.exists(resolve() is Patient or resolve() is Group) implies type.exists().not())
52. Encounter.participant:location.typeCode
Comments	SHALL contain exactly one [1..1] @typeCode="LOC" Location (CodeSystem: HL7ParticipationType urn:oid:2.16.840.1.113883.5.90) (CONF:1098-31875).
Control	1..1
Binding	The codes SHALL be taken from CDAParticipationType (required to `http://hl7.org/cda/stds/core/ValueSet/CDAParticipationType`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Fixed Value	`LOC`
54. Encounter.participant:location.participantRole
Definition	Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type.
Short	Base for all types and resources
Comments	SHALL contain exactly one [1..1] Service Delivery Location (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.32) (CONF:1098-31876).
Control	1..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/ParticipantRole(Service Delivery Location)
Is Modifier	false
Invariants	role-choice: playingDevice and playingEntity are mutually exclusive (`(playingDevice \| playingEntity).count() <= 1`) should-addr: SHOULD contain addr (`addr.exists()`) should-telecom: SHOULD contain telecom (`telecom.exists()`)
56. Encounter.entryRelationship
Short	The following entryRelationship captures the reason for the planned or ordered encounter
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/EntryRelationship
Slicing	This element introduces a set of slices on `Encounter.entryRelationship`. The slices areUnordered and Open, and can be differentiated using the following discriminators: profile @ observation
58. Encounter.entryRelationship:priorityPreference
Slice Name	priorityPreference
Short	The following entryRelationship represents the priority that a patient or a provider places on the encounter.
Comments	MAY contain zero or one [0..1] entryRelationship (CONF:1098-31033) such that it
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/EntryRelationship
60. Encounter.entryRelationship:priorityPreference.typeCode
Comments	SHALL contain exactly one [1..1] @typeCode="REFR" Refers to (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002) (CONF:1098-31034).
Control	1..1
Binding	The codes SHALL be taken from x_ActRelationshipEntryRelationship (required to `http://terminology.hl7.org/ValueSet/v3-xActRelationshipEntryRelationship`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Fixed Value	`REFR`
62. Encounter.entryRelationship:priorityPreference.observation
Definition	Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type.
Short	Base for all types and resources
Comments	SHALL contain exactly one [1..1] Priority Preference (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.143) (CONF:1098-31035).
Control	1..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Observation(Priority Preference)
Is Modifier	false
Invariants	should-text-ref-value: SHOULD contain text/reference/@value (`text.reference.value.exists()`) should-effectiveTime: SHOULD contain effectiveTime (`effectiveTime.exists()`) should-author: SHOULD contain author (`author.exists()`)
64. Encounter.entryRelationship:indication
Slice Name	indication
Comments	MAY contain zero or more [0..*] entryRelationship (CONF:1098-31877) such that it
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/EntryRelationship
66. Encounter.entryRelationship:indication.typeCode
Comments	SHALL contain exactly one [1..1] @typeCode="RSON" Has Reason (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002) (CONF:1098-31878).
Control	1..1
Binding	The codes SHALL be taken from x_ActRelationshipEntryRelationship (required to `http://terminology.hl7.org/ValueSet/v3-xActRelationshipEntryRelationship`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Fixed Value	`RSON`
68. Encounter.entryRelationship:indication.observation
Definition	Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type.
Short	Base for all types and resources
Comments	SHALL contain exactly one [1..1] Indication (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.4.19:2014-06-09) (CONF:1098-31879).
Control	1..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Observation(Indication)
Is Modifier	false
Invariants	should-text-ref-value: SHOULD contain text/reference/@value (`text.reference.value.exists()`) should-effectiveTime: SHOULD contain effectiveTime (`effectiveTime.exists()`) indication-value: If the ID element does not reference a problem recorded elsewhere in the document, then observation/value must be populated with a coded entry. (`value.exists() or (%resource.descendants().ofType(CDA.Observation).where(id.exists($this.root = %context.id.first().root and $this.extension ~ %context.id.first().extension) and value.exists()))`)

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

0. Encounter
Definition	Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type.
Short	Base for all types and resources
Control	1..1
Is Modifier	false
Logical Container	ClinicalDocument (CDA Class)
Validation	Instance of this type are validated by templateId
XML Format	In the XML format, this property has the namespace `urn:hl7-org:v3`.
Invariants	should-text-ref-value: SHOULD contain text/reference/@value (`text.reference.value.exists()`) should-code: SHOULD contain code (`code.exists()`) should-effectiveTime: SHOULD contain effectiveTime (`effectiveTime.exists()`) should-author: SHOULD contain author (`author.exists()`)
2. Encounter.nullFlavor
Definition	If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
Control	0..1
Binding	The codes SHALL be taken from CDANullFlavor (required to `http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Exceptional Value Detail
4. Encounter.realmCode
Definition	When valued in an instance, this attribute signals the imposition of realm-specific constraints. The value of this attribute identifies the realm in question
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/CS
6. Encounter.typeId
Definition	When valued in an instance, this attribute signals the imposition of constraints defined in an HL7-specified message type. This might be a common type (also known as CMET in the messaging communication environment), or content included within a wrapper. The value of this attribute provides a unique identifier for the type in question.
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/II
8. Encounter.typeId.nullFlavor
Definition	If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
Control	0..1
Binding	The codes SHALL be taken from CDANullFlavor (required to `http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Exceptional Value Detail
10. Encounter.typeId.assigningAuthorityName
Definition	A human readable name or mnemonic for the assigning authority. The Assigning Authority Name has no computational value. The purpose of a Assigning Authority Name is to assist an unaided human interpreter of an II value to interpret the authority. Note: no automated processing must depend on the assigning authority name to be present in any form.
Control	0..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Assigning Authority Name
12. Encounter.typeId.displayable
Definition	Specifies if the identifier is intended for human display and data entry (displayable = true) as opposed to pure machine interoperation (displayable = false).
Control	0..1
Type	boolean(bl: Boolean)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Displayable
14. Encounter.typeId.root
Definition	Identifies the type as an HL7 Registered model
Control	1..1
Type	string(oid: ISO Object Identifier, uuid: DCE Universal Unique Identifier, ruid: HL7 Reserved Identifier Scheme)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Root
Fixed Value	`2.16.840.1.113883.1.3`
16. Encounter.typeId.extension
Definition	A character string as a unique identifier within the scope of the identifier root.
Control	1..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Extension
18. Encounter.templateId
Definition	When valued in an instance, this attribute signals the imposition of a set of template-defined constraints. The value of this attribute provides a unique identifier for the templates in question
Control	1..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/II
Slicing	This element introduces a set of slices on `Encounter.templateId`. The slices areUnordered and Open, and can be differentiated using the following discriminators: value @ root value @ extension
20. Encounter.templateId:planned-enc
Slice Name	planned-enc
Definition	When valued in an instance, this attribute signals the imposition of a set of template-defined constraints. The value of this attribute provides a unique identifier for the templates in question
Control	1..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/II
22. Encounter.templateId:planned-enc.nullFlavor
Definition	If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
Control	0..1
Binding	The codes SHALL be taken from CDANullFlavor (required to `http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Exceptional Value Detail
24. Encounter.templateId:planned-enc.assigningAuthorityName
Definition	A human readable name or mnemonic for the assigning authority. The Assigning Authority Name has no computational value. The purpose of a Assigning Authority Name is to assist an unaided human interpreter of an II value to interpret the authority. Note: no automated processing must depend on the assigning authority name to be present in any form.
Control	0..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Assigning Authority Name
26. Encounter.templateId:planned-enc.displayable
Definition	Specifies if the identifier is intended for human display and data entry (displayable = true) as opposed to pure machine interoperation (displayable = false).
Control	0..1
Type	boolean(bl: Boolean)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Displayable
28. Encounter.templateId:planned-enc.root
Definition	A unique identifier that guarantees the global uniqueness of the instance identifier. The root alone may be the entire instance identifier.
Control	1..1
Type	string(oid: ISO Object Identifier, uuid: DCE Universal Unique Identifier, ruid: HL7 Reserved Identifier Scheme)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Root
Pattern Value	`2.16.840.1.113883.10.20.22.4.40`
30. Encounter.templateId:planned-enc.extension
Definition	A character string as a unique identifier within the scope of the identifier root.
Control	1..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Extension
Pattern Value	`2014-06-09`
32. Encounter.classCode
Comments	SHALL contain exactly one [1..1] @classCode="ENC" (CodeSystem: HL7ActClass urn:oid:2.16.840.1.113883.5.6 STATIC) (CONF:1098-8564).
Control	1..1
Binding	The codes SHALL be taken from CDAActClass (required to `http://hl7.org/cda/stds/core/ValueSet/CDAActClass`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Fixed Value	`ENC`
34. Encounter.moodCode
Comments	SHALL contain exactly one [1..1] @moodCode, which SHALL be selected from ValueSet Planned moodCode (Act/Encounter/Procedure) urn:oid:2.16.840.1.113883.11.20.9.23 STATIC 2014-09-01 (CONF:1098-8565).
Control	1..1
Binding	The codes SHALL be taken from Planned moodCode (Act/Encounter/Procedure) (required to `http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.23`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
36. Encounter.id
Comments	SHALL contain at least one [1..*] id (CONF:1098-8567).
Control	1..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/II
38. Encounter.code
Short	Records the type of encounter ordered or recommended.
Comments	SHOULD contain zero or one [0..1] code, which SHOULD be selected from ValueSet Encounter Planned urn:oid:2.16.840.1.113883.11.20.9.52 DYNAMIC (CONF:1098-31032).
Control	0..1
Binding	The codes SHOULD be taken from Encounter Planned (preferred to `http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.11.20.9.52`)
Type	http://hl7.org/cda/stds/core/StructureDefinition/CD
40. Encounter.text
Short	SHOULD reference the portion of section narrative text corresponding to this entry
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/ED
42. Encounter.text.nullFlavor
Definition	If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
Control	0..1
Binding	The codes SHALL be taken from CDANullFlavor (required to `http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Exceptional Value Detail
44. Encounter.text.compression
Definition	Indicates whether the raw byte data is compressed, and what compression algorithm was used.
Control	0..1
Binding	The codes SHALL be taken from CDACompressionAlgorithm (required to `http://hl7.org/cda/stds/core/ValueSet/CDACompressionAlgorithm`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Compression
46. Encounter.text.integrityCheck
Definition	The integrity check is a short binary value representing a cryptographically strong checksum that is calculated over the binary data. The purpose of this property, when communicated with a reference is for anyone to validate later whether the reference still resolved to the same data that the reference resolved to when the encapsulated data value with reference was created.
Control	0..1
Type	base64Binary(bin: Binary Data)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Integrity Check
48. Encounter.text.integrityCheckAlgorithm
Definition	Specifies the algorithm used to compute the integrityCheck value. The cryptographically strong checksum algorithm Secure Hash Algorithm-1 (SHA-1) is currently the industry standard. It has superseded the MD5 algorithm only a couple of years ago, when certain flaws in the security of MD5 were discovered. Currently the SHA-1 hash algorithm is the default choice for the integrity check algorithm. Note that SHA-256 is also entering widespread usage.
Control	0..1
Binding	The codes SHALL be taken from IntegrityCheckAlgorithm (2.0.0) (required to `http://terminology.hl7.org/ValueSet/v3-IntegrityCheckAlgorithm\|2.0.0`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Integrity Check Algorithm
50. Encounter.text.language
Definition	For character based information the language property specifies the human language of the text.
Control	0..1
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Language
52. Encounter.text.mediaType
Definition	Identifies the type of the encapsulated data and identifies a method to interpret or render the data.
Control	0..1
Binding	For example codes, see MediaType (example to `http://terminology.hl7.org/ValueSet/v3-MediaType`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Media Type
54. Encounter.text.representation
Control	0..1
Binding	The codes SHALL be taken from CDABinaryDataEncoding (required to `http://hl7.org/cda/stds/core/ValueSet/BinaryDataEncoding`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
56. Encounter.text.xmlText
Definition	Data that is primarily intended for human interpretation or for further machine processing is outside the scope of HL7. This includes unformatted or formatted written language, multimedia data, or structured information as defined by a different standard (e.g., XML-signatures.)
Short	Allows for mixed text content. If @representation='B64', this SHALL be a base64binary string.
Comments	This element is represented in XML as textual content. The actual name "xmlText" will not appear in a CDA instance.
Control	0..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as unadorned text.
58. Encounter.text.reference
Definition	A telecommunication address (TEL), such as a URL for HTTP or FTP, which will resolve to precisely the same binary data that could as well have been provided as inline data.
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/TEL
Label	Reference
Invariants	value-starts-octothorpe: If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative (`value.exists() implies value.startsWith('#')`)
60. Encounter.text.thumbnail
Definition	An abbreviated rendition of the full data. A thumbnail requires significantly fewer resources than the full data, while still maintaining some distinctive similarity with the full data. A thumbnail is typically used with by-reference encapsulated data. It allows a user to select data more efficiently before actually downloading through the reference.
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/ED
Label	Thumbnail
62. Encounter.statusCode
Comments	SHALL contain exactly one [1..1] statusCode (CONF:1098-30439).
Control	1..1
Binding	The codes SHALL be taken from ActStatus (required to `http://terminology.hl7.org/ValueSet/v3-ActStatus`)
Type	http://hl7.org/cda/stds/core/StructureDefinition/CS
64. Encounter.statusCode.nullFlavor
Definition	If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
Control	0..1
Binding	The codes SHALL be taken from CDANullFlavor (required to `http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Exceptional Value Detail
66. Encounter.statusCode.code
Definition	The plain code symbol defined by the code system. For example, "784.0" is the code symbol of the ICD-9 code "784.0" for headache.
Comments	This statusCode SHALL contain exactly one [1..1] @code="active" Active (CodeSystem: HL7ActStatus urn:oid:2.16.840.1.113883.5.14) (CONF:1098-31880).
Control	1..1
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Code
Fixed Value	`active`
68. Encounter.statusCode.codeSystem
Definition	Specifies the code system that defines the code.
Control	0..0
Type	string(oid: ISO Object Identifier, uuid: DCE Universal Unique Identifier, ruid: HL7 Reserved Identifier Scheme)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Code System
70. Encounter.statusCode.codeSystemName
Definition	The common name of the coding system.
Control	0..0
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Code System Name
72. Encounter.statusCode.codeSystemVersion
Definition	If applicable, a version descriptor defined specifically for the given code system.
Control	0..0
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Code System Version
74. Encounter.statusCode.displayName
Definition	A name or title for the code, under which the sending system shows the code value to its users.
Control	0..0
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Display Name
76. Encounter.statusCode.sdtcValueSet
Definition	The valueSet extension adds an attribute for elements with a CD dataType which indicates the particular value set constraining the coded concept.
Control	0..1
Type	string(oid: ISO Object Identifier)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.In the XML format, this property has the namespace `urn:hl7-org:sdtc`.In the XML format, this property has the actual name`valueSet`.
78. Encounter.statusCode.sdtcValueSetVersion
Definition	The valueSetVersion extension adds an attribute for elements with a CD dataType which indicates the version of the particular value set constraining the coded concept.
Control	0..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.In the XML format, this property has the namespace `urn:hl7-org:sdtc`.In the XML format, this property has the actual name`valueSetVersion`.
80. Encounter.statusCode.originalText
Definition	The text or phrase used as the basis for the coding.
Control	0..0
Type	http://hl7.org/cda/stds/core/StructureDefinition/ED
Label	Original Text
82. Encounter.statusCode.qualifier
Definition	Specifies additional codes that increase the specificity of the the primary code.
Control	0..0
Type	http://hl7.org/cda/stds/core/StructureDefinition/CR
Label	Qualifier
84. Encounter.statusCode.translation
Definition	A set of other concept descriptors that translate this concept descriptor into other code systems.
Control	0..0
Type	http://hl7.org/cda/stds/core/StructureDefinition/CD
XML Format	The type of this property is determined using the " `xsi:type`attribute.
Label	Translation
86. Encounter.effectiveTime
Comments	SHOULD contain zero or one [0..1] effectiveTime (CONF:1098-30440).
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/IVL-TS
88. Encounter.sdtcDischargeDispositionCode
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/CE
XML Format	In the XML format, this property has the namespace `urn:hl7-org:sdtc`.In the XML format, this property has the actual name`dischargeDispositionCode`.
90. Encounter.priorityCode
Control	0..1
Binding	For example codes, see ActPriority (example to `http://terminology.hl7.org/ValueSet/v3-ActPriority`)
Type	http://hl7.org/cda/stds/core/StructureDefinition/CE
92. Encounter.subject
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Subject
94. Encounter.specimen
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/Specimen
96. Encounter.performer
Short	Performers represent clinicians who are responsible for assessing and treating the patient.
Comments	MAY contain zero or more [0..*] performer (CONF:1098-30442) such that it
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/Performer2
98. Encounter.performer.nullFlavor
Definition	If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
Control	0..1
Binding	The codes SHALL be taken from CDANullFlavor (required to `http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Exceptional Value Detail
100. Encounter.performer.realmCode
Definition	When valued in an instance, this attribute signals the imposition of realm-specific constraints. The value of this attribute identifies the realm in question
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/CS
102. Encounter.performer.typeId
Definition	When valued in an instance, this attribute signals the imposition of constraints defined in an HL7-specified message type. This might be a common type (also known as CMET in the messaging communication environment), or content included within a wrapper. The value of this attribute provides a unique identifier for the type in question.
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/II
104. Encounter.performer.typeId.nullFlavor
Definition	If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
Control	0..1
Binding	The codes SHALL be taken from CDANullFlavor (required to `http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Exceptional Value Detail
106. Encounter.performer.typeId.assigningAuthorityName
Definition	A human readable name or mnemonic for the assigning authority. The Assigning Authority Name has no computational value. The purpose of a Assigning Authority Name is to assist an unaided human interpreter of an II value to interpret the authority. Note: no automated processing must depend on the assigning authority name to be present in any form.
Control	0..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Assigning Authority Name
108. Encounter.performer.typeId.displayable
Definition	Specifies if the identifier is intended for human display and data entry (displayable = true) as opposed to pure machine interoperation (displayable = false).
Control	0..1
Type	boolean(bl: Boolean)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Displayable
110. Encounter.performer.typeId.root
Definition	Identifies the type as an HL7 Registered model
Control	1..1
Type	string(oid: ISO Object Identifier, uuid: DCE Universal Unique Identifier, ruid: HL7 Reserved Identifier Scheme)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Root
Fixed Value	`2.16.840.1.113883.1.3`
112. Encounter.performer.typeId.extension
Definition	A character string as a unique identifier within the scope of the identifier root.
Control	1..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Extension
114. Encounter.performer.templateId
Definition	When valued in an instance, this attribute signals the imposition of a set of template-defined constraints. The value of this attribute provides a unique identifier for the templates in question
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/II
116. Encounter.performer.typeCode
Control	0..1
Binding	The codes SHALL be taken from ParticipationPhysicalPerformer (required to `http://terminology.hl7.org/ValueSet/v3-ParticipationPhysicalPerformer`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Fixed Value	`PRF`
118. Encounter.performer.sdtcFunctionCode
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/CE
XML Format	In the XML format, this property has the namespace `urn:hl7-org:sdtc`.In the XML format, this property has the actual name`functionCode`.
120. Encounter.performer.time
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/IVL-TS
122. Encounter.performer.modeCode
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/CE
124. Encounter.performer.assignedEntity
Comments	SHALL contain exactly one [1..1] assignedEntity (CONF:1098-31874).
Control	1..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/AssignedEntity
126. Encounter.author
Definition	Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type.
Short	The author in a planned encounter represents the clinician who is requesting or planning the encounter.
Comments	SHOULD contain zero or more [0..*] Author Participation (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.119) (CONF:1098-32045).
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/Author(Author Participation)
Is Modifier	false
128. Encounter.informant
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/Informant
130. Encounter.participant
Short	This location participation captures where the planned or ordered encounter may take place.
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/Participant2
Slicing	This element introduces a set of slices on `Encounter.participant`. The slices areUnordered and Open, and can be differentiated using the following discriminators: value @ typeCode
132. Encounter.participant:location
Slice Name	location
Comments	MAY contain zero or more [0..*] participant (CONF:1098-30443) such that it
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/Participant2
134. Encounter.participant:location.nullFlavor
Definition	If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
Control	0..1
Binding	The codes SHALL be taken from CDANullFlavor (required to `http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Exceptional Value Detail
136. Encounter.participant:location.realmCode
Definition	When valued in an instance, this attribute signals the imposition of realm-specific constraints. The value of this attribute identifies the realm in question
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/CS
138. Encounter.participant:location.typeId
Definition	When valued in an instance, this attribute signals the imposition of constraints defined in an HL7-specified message type. This might be a common type (also known as CMET in the messaging communication environment), or content included within a wrapper. The value of this attribute provides a unique identifier for the type in question.
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/II
140. Encounter.participant:location.typeId.nullFlavor
Definition	If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
Control	0..1
Binding	The codes SHALL be taken from CDANullFlavor (required to `http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Exceptional Value Detail
142. Encounter.participant:location.typeId.assigningAuthorityName
Definition	A human readable name or mnemonic for the assigning authority. The Assigning Authority Name has no computational value. The purpose of a Assigning Authority Name is to assist an unaided human interpreter of an II value to interpret the authority. Note: no automated processing must depend on the assigning authority name to be present in any form.
Control	0..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Assigning Authority Name
144. Encounter.participant:location.typeId.displayable
Definition	Specifies if the identifier is intended for human display and data entry (displayable = true) as opposed to pure machine interoperation (displayable = false).
Control	0..1
Type	boolean(bl: Boolean)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Displayable
146. Encounter.participant:location.typeId.root
Definition	Identifies the type as an HL7 Registered model
Control	1..1
Type	string(oid: ISO Object Identifier, uuid: DCE Universal Unique Identifier, ruid: HL7 Reserved Identifier Scheme)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Root
Fixed Value	`2.16.840.1.113883.1.3`
148. Encounter.participant:location.typeId.extension
Definition	A character string as a unique identifier within the scope of the identifier root.
Control	1..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Extension
150. Encounter.participant:location.templateId
Definition	When valued in an instance, this attribute signals the imposition of a set of template-defined constraints. The value of this attribute provides a unique identifier for the templates in question
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/II
152. Encounter.participant:location.typeCode
Comments	SHALL contain exactly one [1..1] @typeCode="LOC" Location (CodeSystem: HL7ParticipationType urn:oid:2.16.840.1.113883.5.90) (CONF:1098-31875).
Control	1..1
Binding	The codes SHALL be taken from CDAParticipationType (required to `http://hl7.org/cda/stds/core/ValueSet/CDAParticipationType`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Fixed Value	`LOC`
154. Encounter.participant:location.contextControlCode
Control	0..1
Binding	The codes SHALL be taken from CDAContextControl (required to `http://hl7.org/cda/stds/core/ValueSet/CDAContextControl`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Fixed Value	`OP`
156. Encounter.participant:location.sdtcFunctionCode
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/CE
XML Format	In the XML format, this property has the namespace `urn:hl7-org:sdtc`.In the XML format, this property has the actual name`functionCode`.
158. Encounter.participant:location.time
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/IVL-TS
160. Encounter.participant:location.awarenessCode
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/CE
162. Encounter.participant:location.participantRole
Definition	Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type.
Short	Base for all types and resources
Comments	SHALL contain exactly one [1..1] Service Delivery Location (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.32) (CONF:1098-31876).
Control	1..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/ParticipantRole(Service Delivery Location)
Is Modifier	false
Invariants	role-choice: playingDevice and playingEntity are mutually exclusive (`(playingDevice \| playingEntity).count() <= 1`) should-addr: SHOULD contain addr (`addr.exists()`) should-telecom: SHOULD contain telecom (`telecom.exists()`)
164. Encounter.entryRelationship
Short	The following entryRelationship captures the reason for the planned or ordered encounter
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/EntryRelationship
Slicing	This element introduces a set of slices on `Encounter.entryRelationship`. The slices areUnordered and Open, and can be differentiated using the following discriminators: profile @ observation
166. Encounter.entryRelationship:priorityPreference
Slice Name	priorityPreference
Short	The following entryRelationship represents the priority that a patient or a provider places on the encounter.
Comments	MAY contain zero or one [0..1] entryRelationship (CONF:1098-31033) such that it
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/EntryRelationship
168. Encounter.entryRelationship:priorityPreference.nullFlavor
Definition	If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
Control	0..1
Binding	The codes SHALL be taken from CDANullFlavor (required to `http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Exceptional Value Detail
170. Encounter.entryRelationship:priorityPreference.realmCode
Definition	When valued in an instance, this attribute signals the imposition of realm-specific constraints. The value of this attribute identifies the realm in question
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/CS
172. Encounter.entryRelationship:priorityPreference.typeId
Definition	When valued in an instance, this attribute signals the imposition of constraints defined in an HL7-specified message type. This might be a common type (also known as CMET in the messaging communication environment), or content included within a wrapper. The value of this attribute provides a unique identifier for the type in question.
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/II
174. Encounter.entryRelationship:priorityPreference.typeId.nullFlavor
Definition	If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
Control	0..1
Binding	The codes SHALL be taken from CDANullFlavor (required to `http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Exceptional Value Detail
176. Encounter.entryRelationship:priorityPreference.typeId.assigningAuthorityName
Definition	A human readable name or mnemonic for the assigning authority. The Assigning Authority Name has no computational value. The purpose of a Assigning Authority Name is to assist an unaided human interpreter of an II value to interpret the authority. Note: no automated processing must depend on the assigning authority name to be present in any form.
Control	0..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Assigning Authority Name
178. Encounter.entryRelationship:priorityPreference.typeId.displayable
Definition	Specifies if the identifier is intended for human display and data entry (displayable = true) as opposed to pure machine interoperation (displayable = false).
Control	0..1
Type	boolean(bl: Boolean)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Displayable
180. Encounter.entryRelationship:priorityPreference.typeId.root
Definition	Identifies the type as an HL7 Registered model
Control	1..1
Type	string(oid: ISO Object Identifier, uuid: DCE Universal Unique Identifier, ruid: HL7 Reserved Identifier Scheme)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Root
Fixed Value	`2.16.840.1.113883.1.3`
182. Encounter.entryRelationship:priorityPreference.typeId.extension
Definition	A character string as a unique identifier within the scope of the identifier root.
Control	1..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Extension
184. Encounter.entryRelationship:priorityPreference.templateId
Definition	When valued in an instance, this attribute signals the imposition of a set of template-defined constraints. The value of this attribute provides a unique identifier for the templates in question
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/II
186. Encounter.entryRelationship:priorityPreference.typeCode
Comments	SHALL contain exactly one [1..1] @typeCode="REFR" Refers to (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002) (CONF:1098-31034).
Control	1..1
Binding	The codes SHALL be taken from x_ActRelationshipEntryRelationship (required to `http://terminology.hl7.org/ValueSet/v3-xActRelationshipEntryRelationship`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Fixed Value	`REFR`
188. Encounter.entryRelationship:priorityPreference.inversionInd
Definition	The entryRelationship.inversionInd can be set to "true" to indicate that the relationship should be interpreted as if the roles of the source and target entries were reversed.
Control	0..1
Type	boolean(bl: Boolean)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
190. Encounter.entryRelationship:priorityPreference.contextConductionInd
Definition	The entryRelationship.contextConductionInd differs from the otherwise common use of this attribute in that in all other cases where this attribute is used, the value is fixed at "true", whereas here the value is defaulted to "true", and can be changed to "false" when referencing an entry in the same document. Setting the context conduction to false when referencing an entry in the same document keeps clear the fact that the referenced object retains its original context.
Control	0..1
Type	boolean(bl: Boolean)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Default Value	`true`
192. Encounter.entryRelationship:priorityPreference.negationInd
Control	0..1
Type	boolean(bl: Boolean)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
194. Encounter.entryRelationship:priorityPreference.sequenceNumber
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/INT
196. Encounter.entryRelationship:priorityPreference.seperatableInd
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/BL
198. Encounter.entryRelationship:priorityPreference.act
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Act
200. Encounter.entryRelationship:priorityPreference.encounter
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Encounter
202. Encounter.entryRelationship:priorityPreference.observation
Definition	Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type.
Short	Base for all types and resources
Comments	SHALL contain exactly one [1..1] Priority Preference (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.143) (CONF:1098-31035).
Control	1..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Observation(Priority Preference)
Is Modifier	false
Invariants	should-text-ref-value: SHOULD contain text/reference/@value (`text.reference.value.exists()`) should-effectiveTime: SHOULD contain effectiveTime (`effectiveTime.exists()`) should-author: SHOULD contain author (`author.exists()`)
204. Encounter.entryRelationship:priorityPreference.observationMedia
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/ObservationMedia
206. Encounter.entryRelationship:priorityPreference.organizer
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Organizer
208. Encounter.entryRelationship:priorityPreference.procedure
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Procedure
210. Encounter.entryRelationship:priorityPreference.regionOfInterest
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/RegionOfInterest
212. Encounter.entryRelationship:priorityPreference.substanceAdministration
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/SubstanceAdministration
214. Encounter.entryRelationship:priorityPreference.supply
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Supply
216. Encounter.entryRelationship:indication
Slice Name	indication
Comments	MAY contain zero or more [0..*] entryRelationship (CONF:1098-31877) such that it
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/EntryRelationship
218. Encounter.entryRelationship:indication.nullFlavor
Definition	If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
Control	0..1
Binding	The codes SHALL be taken from CDANullFlavor (required to `http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Exceptional Value Detail
220. Encounter.entryRelationship:indication.realmCode
Definition	When valued in an instance, this attribute signals the imposition of realm-specific constraints. The value of this attribute identifies the realm in question
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/CS
222. Encounter.entryRelationship:indication.typeId
Definition	When valued in an instance, this attribute signals the imposition of constraints defined in an HL7-specified message type. This might be a common type (also known as CMET in the messaging communication environment), or content included within a wrapper. The value of this attribute provides a unique identifier for the type in question.
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/II
224. Encounter.entryRelationship:indication.typeId.nullFlavor
Definition	If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
Control	0..1
Binding	The codes SHALL be taken from CDANullFlavor (required to `http://hl7.org/cda/stds/core/ValueSet/CDANullFlavor`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Exceptional Value Detail
226. Encounter.entryRelationship:indication.typeId.assigningAuthorityName
Definition	A human readable name or mnemonic for the assigning authority. The Assigning Authority Name has no computational value. The purpose of a Assigning Authority Name is to assist an unaided human interpreter of an II value to interpret the authority. Note: no automated processing must depend on the assigning authority name to be present in any form.
Control	0..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Assigning Authority Name
228. Encounter.entryRelationship:indication.typeId.displayable
Definition	Specifies if the identifier is intended for human display and data entry (displayable = true) as opposed to pure machine interoperation (displayable = false).
Control	0..1
Type	boolean(bl: Boolean)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Displayable
230. Encounter.entryRelationship:indication.typeId.root
Definition	Identifies the type as an HL7 Registered model
Control	1..1
Type	string(oid: ISO Object Identifier, uuid: DCE Universal Unique Identifier, ruid: HL7 Reserved Identifier Scheme)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Root
Fixed Value	`2.16.840.1.113883.1.3`
232. Encounter.entryRelationship:indication.typeId.extension
Definition	A character string as a unique identifier within the scope of the identifier root.
Control	1..1
Type	string(st: Character String)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Label	Extension
234. Encounter.entryRelationship:indication.templateId
Definition	When valued in an instance, this attribute signals the imposition of a set of template-defined constraints. The value of this attribute provides a unique identifier for the templates in question
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/II
236. Encounter.entryRelationship:indication.typeCode
Comments	SHALL contain exactly one [1..1] @typeCode="RSON" Has Reason (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002) (CONF:1098-31878).
Control	1..1
Binding	The codes SHALL be taken from x_ActRelationshipEntryRelationship (required to `http://terminology.hl7.org/ValueSet/v3-xActRelationshipEntryRelationship`)
Type	code(cs: Coded Simple Value)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Fixed Value	`RSON`
238. Encounter.entryRelationship:indication.inversionInd
Definition	The entryRelationship.inversionInd can be set to "true" to indicate that the relationship should be interpreted as if the roles of the source and target entries were reversed.
Control	0..1
Type	boolean(bl: Boolean)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
240. Encounter.entryRelationship:indication.contextConductionInd
Definition	The entryRelationship.contextConductionInd differs from the otherwise common use of this attribute in that in all other cases where this attribute is used, the value is fixed at "true", whereas here the value is defaulted to "true", and can be changed to "false" when referencing an entry in the same document. Setting the context conduction to false when referencing an entry in the same document keeps clear the fact that the referenced object retains its original context.
Control	0..1
Type	boolean(bl: Boolean)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
Default Value	`true`
242. Encounter.entryRelationship:indication.negationInd
Control	0..1
Type	boolean(bl: Boolean)
Primitive Value	This primitive element may be present, or absent, or replaced by an extension
XML Format	In the XML format, this property is represented as an attribute.
244. Encounter.entryRelationship:indication.sequenceNumber
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/INT
246. Encounter.entryRelationship:indication.seperatableInd
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/BL
248. Encounter.entryRelationship:indication.act
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Act
250. Encounter.entryRelationship:indication.encounter
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Encounter
252. Encounter.entryRelationship:indication.observation
Definition	Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type.
Short	Base for all types and resources
Comments	SHALL contain exactly one [1..1] Indication (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.4.19:2014-06-09) (CONF:1098-31879).
Control	1..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Observation(Indication)
Is Modifier	false
Invariants	should-text-ref-value: SHOULD contain text/reference/@value (`text.reference.value.exists()`) should-effectiveTime: SHOULD contain effectiveTime (`effectiveTime.exists()`) indication-value: If the ID element does not reference a problem recorded elsewhere in the document, then observation/value must be populated with a coded entry. (`value.exists() or (%resource.descendants().ofType(CDA.Observation).where(id.exists($this.root = %context.id.first().root and $this.extension ~ %context.id.first().extension) and value.exists()))`)
254. Encounter.entryRelationship:indication.observationMedia
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/ObservationMedia
256. Encounter.entryRelationship:indication.organizer
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Organizer
258. Encounter.entryRelationship:indication.procedure
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Procedure
260. Encounter.entryRelationship:indication.regionOfInterest
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/RegionOfInterest
262. Encounter.entryRelationship:indication.substanceAdministration
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/SubstanceAdministration
264. Encounter.entryRelationship:indication.supply
Control	0..1
Type	http://hl7.org/cda/stds/core/StructureDefinition/Supply
266. Encounter.reference
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/Reference
268. Encounter.precondition
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/Precondition
270. Encounter.sdtcPrecondition2
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/Precondition2
XML Format	In the XML format, this property has the namespace `urn:hl7-org:sdtc`.In the XML format, this property has the actual name`precondition2`.
272. Encounter.sdtcInFulfillmentOf1
Control	0..*
Type	http://hl7.org/cda/stds/core/StructureDefinition/InFulfillmentOf1
XML Format	In the XML format, this property has the namespace `urn:hl7-org:sdtc`.In the XML format, this property has the actual name`inFulfillmentOf1`.