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.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

Source profile used to populate this logical model.

Target profile intended for this logical model instance.

Encounter identifiers.

Current status of the encounter.

Prior encounter status periods.

Classification of patient encounter.

Prior encounter class periods.

Encounter type concepts.

Specific service provided during the encounter.

Encounter priority.

Patient or subject of the encounter.

Requests fulfilled by the encounter.

Episodes of care associated with the encounter.

Appointments that scheduled the encounter.

Participants involved in the encounter.

Start and optional end of the encounter.

Encounter duration.

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.

Diagnoses associated with the encounter.

Accounts used for billing the encounter.

Admission and discharge context when supplied on the source encounter.

Locations involved in the encounter.

Service provider organization associated with the encounter.

Parent encounter.

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.

Source profile used to populate this logical model.

Target profile intended for this logical model instance.

Encounter identifiers.

Current status of the encounter.

Prior encounter status periods.

Classification of patient encounter.

Prior encounter class periods.

Encounter type concepts.

Specific service provided during the encounter.

Encounter priority.

Patient or subject of the encounter.

Requests fulfilled by the encounter.

Episodes of care associated with the encounter.

Appointments that scheduled the encounter.

Participants involved in the encounter.

Start and optional end of the encounter.

Encounter duration.

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.

Diagnoses associated with the encounter.

Accounts used for billing the encounter.

Admission and discharge context when supplied on the source encounter.

Locations involved in the encounter.

Service provider organization associated with the encounter.

Parent encounter.

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.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

Source profile used to populate this logical model.

Target profile intended for this logical model instance.

Encounter identifiers.

Current status of the encounter.

Prior encounter status periods.

Classification of patient encounter.

Prior encounter class periods.

Encounter type concepts.

Specific service provided during the encounter.

Encounter priority.

Patient or subject of the encounter.

Requests fulfilled by the encounter.

Episodes of care associated with the encounter.

Appointments that scheduled the encounter.

Participants involved in the encounter.

Start and optional end of the encounter.

Encounter duration.

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.

Diagnoses associated with the encounter.

Accounts used for billing the encounter.

Admission and discharge context when supplied on the source encounter.

Locations involved in the encounter.

Service provider organization associated with the encounter.

Parent encounter.