C.20 - EHDS refined base model for Appointment

Appointment identifier

The overall status of the Appointment. Each of the participants has their own participation status which indicates their involvement in the process, however this status indicates the shared status.

HL7 Appointment status

Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations.

HL7 Encounter class

The specific service that is to be performed during this appointment

SNOMED CT

The specialty of a practitioner that would be required to perform the service requested in this appointment

SNOMED CT

The type of appointment or patient that has been booked in the slot, e.g. Routine, check-up, walk-in, routine, emenrgency etc.

TBD

The reason that this appointment is being scheduled.

SNOMED CT

The priority of the appointment. Can be used to make informed decisions if needing to re-prioritize appointments.

HL7 Act priority

The brief description of the appointment as would be shown on a subject line in a meeting request, or appointment list.

Additional information to support the appointment provided when making the appointment.

Date/Time that the appointment is to take place.

Date/Time that the appointment is to conclude.

A set of date ranges (potentially including times) that the appointment is preferred to be scheduled within.

The slots from the participants' schedules that will be filled by the appointment.

Patient facing information about the Appointment (e.g. fast from 8pm night before).

Additional notes/comments about the appointment.

The patient or group associated with the appointment, if they are to be present (usually) then they should also be included in the participant backbone element.

List of participants involved in the appointment.

List of participants involved in the appointment.

HL7 Participant Type

The individual, device, location, or service participating in the appointment.

Whether this participant is required to be present at the meeting.

C.20 - EHDS refined base model for Appointment

Appointment identifier

The overall status of the Appointment. Each of the participants has their own participation status which indicates their involvement in the process, however this status indicates the shared status.

HL7 Appointment status

Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations.

HL7 Encounter class

The specific service that is to be performed during this appointment

SNOMED CT

The specialty of a practitioner that would be required to perform the service requested in this appointment

SNOMED CT

The type of appointment or patient that has been booked in the slot, e.g. Routine, check-up, walk-in, routine, emenrgency etc.

TBD

The reason that this appointment is being scheduled.

SNOMED CT

The priority of the appointment. Can be used to make informed decisions if needing to re-prioritize appointments.

HL7 Act priority

The brief description of the appointment as would be shown on a subject line in a meeting request, or appointment list.

Additional information to support the appointment provided when making the appointment.

Date/Time that the appointment is to take place.

Date/Time that the appointment is to conclude.

A set of date ranges (potentially including times) that the appointment is preferred to be scheduled within.

The slots from the participants' schedules that will be filled by the appointment.

Patient facing information about the Appointment (e.g. fast from 8pm night before).

Additional notes/comments about the appointment.

The patient or group associated with the appointment, if they are to be present (usually) then they should also be included in the participant backbone element.

List of participants involved in the appointment.

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 managable, 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.

List of participants involved in the appointment.

HL7 Participant Type

The individual, device, location, or service participating in the appointment.

Whether this participant is required to be present at the meeting.

C.20 - EHDS refined base model for Appointment

Appointment identifier

The overall status of the Appointment. Each of the participants has their own participation status which indicates their involvement in the process, however this status indicates the shared status.

HL7 Appointment status

Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations.

HL7 Encounter class

The specific service that is to be performed during this appointment

SNOMED CT

The specialty of a practitioner that would be required to perform the service requested in this appointment

SNOMED CT

The type of appointment or patient that has been booked in the slot, e.g. Routine, check-up, walk-in, routine, emenrgency etc.

TBD

The reason that this appointment is being scheduled.

SNOMED CT

The priority of the appointment. Can be used to make informed decisions if needing to re-prioritize appointments.

HL7 Act priority

The brief description of the appointment as would be shown on a subject line in a meeting request, or appointment list.

Additional information to support the appointment provided when making the appointment.

Date/Time that the appointment is to take place.

Date/Time that the appointment is to conclude.

A set of date ranges (potentially including times) that the appointment is preferred to be scheduled within.

The slots from the participants' schedules that will be filled by the appointment.

Patient facing information about the Appointment (e.g. fast from 8pm night before).

Additional notes/comments about the appointment.

The patient or group associated with the appointment, if they are to be present (usually) then they should also be included in the participant backbone element.

List of participants involved in the appointment.

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 managable, 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 managable, 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.

List of participants involved in the appointment.

HL7 Participant Type

The individual, device, location, or service participating in the appointment.

Whether this participant is required to be present at the meeting.