Administrative recording of a meeting between a patient and a practitioner/organisation, with references to clinical data.

Unique business identifier of the CareSet

Date of registration by the Author/Recorder (date of the last update). Enables CareSet history management through the pair Business Identifier - RecordedDate, which guarantees access to the latest version of the content

The health professional who takes responsibility for the recorded content

Registration status, the moment in the lifecycle. For example: final, corrected, cancelled, entered-in-error. ValueSet: VS_Encounter_Status

Classification of the type of Encounter. ValueSet: VS_Encounter_Class

Type of services/specialisation offered during the Encounter. ValueSet: VS_Encounter_ServiceType (see proposal VS_Be_ServiceType_Voorstel)

The person who is the subject of the healthcare the record (CareSet) refers to. Refers to BePatient

Reference to the EpisodeOfCare resource this Encounter is linked to. Refers to BeEpisodeOfCare

The request that initiated this Encounter. In this case it can only originate from BeCarePlan

Reference to the CareTeam resource recording which team is involved in the care during this Encounter. Refers to BeCareTeam

Reference to another Encounter this Encounter is part of. Refers to BeEncounter

Organisation responsible for this Encounter. Refers to BeOrganization

List of participants involved in the care during this Encounter. Refers to BePractitioner

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.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Period during which the Participant is involved in this Encounter

Role of the Participant involved in this Encounter

The effective start and end moments of this Encounter

Effective duration of the Encounter (excluding absences)

The list of Reasons that will be discussed during this Encounter. ValueSet: VS_Encounter_Reason

List of diagnoses relevant for this Encounter. Refers to BeProblem

Details about the admission of the patient to the care organisation

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.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The location the patient came from for the admission. Refers to BeOrganization

How the patient was admitted. ValueSet: VS_Encounter_Admission_AdmitSource

Is this a re-admission of the patient?

Destination of the patient after discharge. Refers to BeOrganization

Category of location after discharge of the patient. ValueSet: VS_Encounter_Admission_DischargeDisposition

Additional information related to the CareSet content in free text form

Administrative recording of a meeting between a patient and a practitioner/organisation, with references to clinical data.

Unique business identifier of the CareSet

Date of registration by the Author/Recorder (date of the last update). Enables CareSet history management through the pair Business Identifier - RecordedDate, which guarantees access to the latest version of the content

The health professional who takes responsibility for the recorded content

Registration status, the moment in the lifecycle. For example: final, corrected, cancelled, entered-in-error. ValueSet: VS_Encounter_Status

Classification of the type of Encounter. ValueSet: VS_Encounter_Class

Type of services/specialisation offered during the Encounter. ValueSet: VS_Encounter_ServiceType (see proposal VS_Be_ServiceType_Voorstel)

The person who is the subject of the healthcare the record (CareSet) refers to. Refers to BePatient

Reference to the EpisodeOfCare resource this Encounter is linked to. Refers to BeEpisodeOfCare

The request that initiated this Encounter. In this case it can only originate from BeCarePlan

Reference to the CareTeam resource recording which team is involved in the care during this Encounter. Refers to BeCareTeam

Reference to another Encounter this Encounter is part of. Refers to BeEncounter

Organisation responsible for this Encounter. Refers to BeOrganization

List of participants involved in the care during this Encounter. Refers to BePractitioner

Period during which the Participant is involved in this Encounter

Role of the Participant involved in this Encounter

The effective start and end moments of this Encounter

Effective duration of the Encounter (excluding absences)

The list of Reasons that will be discussed during this Encounter. ValueSet: VS_Encounter_Reason

List of diagnoses relevant for this Encounter. Refers to BeProblem

Details about the admission of the patient to the care organisation

The location the patient came from for the admission. Refers to BeOrganization

How the patient was admitted. ValueSet: VS_Encounter_Admission_AdmitSource

Is this a re-admission of the patient?

Destination of the patient after discharge. Refers to BeOrganization

Category of location after discharge of the patient. ValueSet: VS_Encounter_Admission_DischargeDisposition

Additional information related to the CareSet content in free text form

Administrative recording of a meeting between a patient and a practitioner/organisation, with references to clinical data.

Unique business identifier of the CareSet

Date of registration by the Author/Recorder (date of the last update). Enables CareSet history management through the pair Business Identifier - RecordedDate, which guarantees access to the latest version of the content

The health professional who takes responsibility for the recorded content

Registration status, the moment in the lifecycle. For example: final, corrected, cancelled, entered-in-error. ValueSet: VS_Encounter_Status

Classification of the type of Encounter. ValueSet: VS_Encounter_Class

Type of services/specialisation offered during the Encounter. ValueSet: VS_Encounter_ServiceType (see proposal VS_Be_ServiceType_Voorstel)

The person who is the subject of the healthcare the record (CareSet) refers to. Refers to BePatient

Reference to the EpisodeOfCare resource this Encounter is linked to. Refers to BeEpisodeOfCare

The request that initiated this Encounter. In this case it can only originate from BeCarePlan

Reference to the CareTeam resource recording which team is involved in the care during this Encounter. Refers to BeCareTeam

Reference to another Encounter this Encounter is part of. Refers to BeEncounter

Organisation responsible for this Encounter. Refers to BeOrganization

List of participants involved in the care during this Encounter. Refers to BePractitioner

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.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Period during which the Participant is involved in this Encounter

Role of the Participant involved in this Encounter

The effective start and end moments of this Encounter

Effective duration of the Encounter (excluding absences)

The list of Reasons that will be discussed during this Encounter. ValueSet: VS_Encounter_Reason

List of diagnoses relevant for this Encounter. Refers to BeProblem

Details about the admission of the patient to the care organisation

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.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The location the patient came from for the admission. Refers to BeOrganization

How the patient was admitted. ValueSet: VS_Encounter_Admission_AdmitSource

Is this a re-admission of the patient?

Destination of the patient after discharge. Refers to BeOrganization

Category of location after discharge of the patient. ValueSet: VS_Encounter_Admission_DischargeDisposition

Additional information related to the CareSet content in free text form