Gegenereerde narrative: StructureDefinition logical-encounter Naam Markeringen Kard. Type Omschrijving & constraints logical-encounter 0..* Element Logical Model: Encounter Elementen gedefinieerd in ancestors:@id, <a href="http://hl7.org/fhir/R4/datatypes.html#Element" title="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.">extension #xD; sourceProfile 0..1 uri source Profile #xD; targetProfile 0..1 uri target Profile #xD; sourceProfileElementUrl 0..* uri Canonical URL of a source-side profile-specific extension or profile element preserved by this logical model. #xD; sourceProfileElementJson 0..* string Serialized source-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape. #xD; targetProfileElementUrl 0..* uri Canonical URL of a target-side profile-specific extension or profile element preserved by this logical model. #xD; targetProfileElementJson 0..* string Serialized target-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape. #xD; profileSpecificData 0..* Extension Profile-specific extension data carried explicitly by the logical model alongside the normalized R4 payload. #xD; identifier 0..* Identifier Encounter identifiers. #xD; status 1..1 code Current status of the encounter. #xD; class 1..1 Coding Classification of patient encounter. #xD; type 0..* CodeableConcept Encounter type concepts. #xD; subject 0..1 Reference(Patient) Patient or subject of the encounter. #xD; episodeOfCare 0..* Reference() Episodes of care associated with the encounter. #xD; participant 0..* logical-encounter-participant Participants involved in the encounter. #xD; period 0..1 Period Start and optional end of the encounter. #xD; reasonCode 0..* CodeableConcept Textual or coded deviating result carried as an encounter reason. #xD; reasonReferenceProblem 0..* Reference(Condition) Problem references that explain why the encounter took place. #xD; reasonReferenceProcedure 0..* Reference(Procedure) Procedure references that explain why the encounter took place. #xD; hospitalization 0..1 logical-encounter-hospitalization Admission and discharge context when supplied on the source encounter. #xD; serviceProvider 0..1 Reference(Organization) Service provider organization associated with the encounter. #xD; Documentatie voor dit formaat
Canonical intermediate logical model for Encounter translation. It is shaped to the R4 Encounter structure where practical, while keeping the Dutch STU3 zib encounter additions explicit.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Source profile used to populate this logical model.
Target profile intended for this logical model instance.
Canonical URL of a source-side profile-specific extension or profile element preserved by this logical model.
Serialized source-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.
Canonical URL of a target-side profile-specific extension or profile element preserved by this logical model.
Serialized target-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.
Profile-specific extension data carried explicitly by the logical model alongside the normalized R4 payload.
Episodes of care associated with the encounter.
Start and optional end of the encounter.
Textual or coded deviating result carried as an encounter reason.
Problem references that explain why the encounter took place.
Procedure references that explain why the encounter took place.
Admission and discharge context when supplied on the source encounter.
Service provider organization associated with the encounter.