StructureDefinition-2.16.840.1.113883.10.20.22.4.40

Sourcehl7.cda.us.ccda#current:Consolidated CDA Release 2.1 StructureDefinition Publication (v5.0.0)
resourceTypeStructureDefinition
id2.16.840.1.113883.10.20.22.4.40
canonicalhttp://hl7.org/cda/us/ccda/StructureDefinition/2.16.840.1.113883.10.20.22.4.40
version2.1
statusactive
publisherHealth Level Seven
namePlannedEncounter
titlePlanned Encounter
date2023-08-24T14:33:15+00:00
descriptionThis template represents a planned or ordered encounter. The type of encounter (e.g., comprehensive outpatient visit) is represented. Clinicians participating in the encounter and the location of the planned encounter may be captured. The priority that the patient and providers place on the encounter may be represented.
jurisdictionsus
fhirVersion5.0.0
kindlogical
abstractfalse
sdTtypehttp://hl7.org/cda/stds/core/StructureDefinition/Encounter
derivationconstraint
basehttp://hl7.org/cda/stds/core/StructureDefinition/Encounter
Usages
Name Flags Card. Type Description & Constraints doco
. . Encounter CDAR2.Encounter XML Namespace: urn:hl7-org:v3
This logical model cannot be the target of a reference
. . . classCode 1..1 Fixed Value: ENC
. . . moodCode 1..1 Binding: Planned moodCode (Act/Encounter/Procedure) ( required )
. . . Slices for templateId 1 .. Slice: Unordered, Open by value:root, value:extension
. . . . templateId:primary 1..1
. . . . . root 1..1 Required Pattern: 2.16.840.1.113883.10.20.22.4.40
. . . . . extension 1..1 Required Pattern: 2014-06-09
. . . id 1..*
. . . code 0..1 Records the type of encounter ordered or recommended.
Binding: Encounter Planned ( preferred )
. . . statusCode 1..1
. . . . code 1..1 Fixed Value: active
. . . effectiveTime 0..1
. . . Slices for performer Performers represent clinicians who are responsible for assessing and treating the patient.
Slice: Unordered, Open by value:Encounter.assignedEntity
. . . . performer:performer 0..*
. . . . . assignedEntity 1..1
. . . author 0..* http://hl7.org/cda/stds/core/StructureDefinition/Author The author in a planned encounter represents the clinician who is requesting or planning the encounter.
. . . Slices for participant This location participation captures where the planned or ordered encounter may take place.
Slice: Unordered, Open by value:typeCode, value:participantRole
. . . . participant:location 0..*
. . . . . typeCode 1..1 Fixed Value: LOC
. . . . . participantRole 1..1 http://hl7.org/cda/stds/core/StructureDefinition/ParticipantRole
. . . Slices for entryRelationship The following entryRelationship captures the reason for the planned or ordered encounter
Slice: Unordered, Open by profile:observation
. . . . entryRelationship:priorityPreference 0..1 The following entryRelationship represents the priority that a patient or a provider places on the encounter.
. . . . . typeCode 1..1 Fixed Value: REFR
. . . . . observation 1..1 http://hl7.org/cda/stds/core/StructureDefinition/Observation
. . . . entryRelationship:indication 0..*
. . . . . typeCode 1..1 Fixed Value: RSON
. . . . . observation 1..1 http://hl7.org/cda/stds/core/StructureDefinition/Observation

doco Documentation for this format

Produced 08 Sep 2023