Class: Appointment

Description of: Appointment

Class steward is Inter-Enterprise (ADT/Finance/Inter-Enterprise)
Interested committees Patient Administration
A planned patient encounter set for a specific time and place.

Attribute definitions for: Appointment

appointment_duration_qty ::

Amount of time allotted for the appointment. In cases of repeating appointments, this field describes the duration of one instance of the appointment.

|ARQ^9^00868^Appointment Duration| |SCH^9^00868^Appointment Duration|

appointment_timing_qt ::

The scheduled appointment’s timing and quantity as scheduled by the filler application.

|SCH^11^00884^Appointment Timing Quantity|

event_reason_cd ::

Code for the reason that the notification event was triggered. It may describe the cancel reason, the delete reason, the discontinue reason, the add reason, the block reason or others.

OpenIssue: Clarify definition. What is the relationship between the appointment and the notification event? It is difficult to distinguish the idea of the appointment reason and the event reason. Also, I see event reason and cancellation date. Don't seem consistent.

|SCH^6^00883^Event Reason|

expected_service_desc ::

Text providing the service(s) expected to be provided in the scheduled encounter.

expected_start_dttm ::

The scheduled date and time for the start of an appointment.

id ::

A unique identifier assigned to an appointment.

|ARQ^2^00861^Filler Appointment ID| |SCH^2^00861^Filler Appointment ID|

status_cd ::

Code describing the status of the appointment with respect to the filler application. Sample values: Booked, Started, Complete, Cancelled, Discontinue, Deleted, Overbook.

|AIG^14^00889^Filler Status Code| |AIL^12^00889^Filler Status Code| |AIP^12^00889^Filler Status Code| |AIS^10^00889^Filler Status Code| |SCH^25^00889^Filler Status Code|

urgency_cd ::

A code depicting the urgency for the patient to be seen by a healthcare provider.

Association definitions for: Appointment

has_as_a_contact (0,1) :: Contact_person :: is_a_contact_for (0,n)

is_child_of (0,1) :: Appointment :: is_parent_of (0,n)

is_entered_by (1,1) :: Entering_person :: enters (0,n)

is_parent_of (0,n) :: Appointment :: is_child_of (0,1)

is_booked_in (1,n) :: Schedule :: books (0,n)

is_requested_by (0,1) :: Appointment_request :: requests (0,n)

OpenIssue: Committee must revisit the multiplicities for this association.

reserves (0,n) :: Resource_slot :: is_reserved_by (0,n)

Links a schedule to its contents.

Rationale: This many-to-many association represents the over-booking of a resoruce slot Patient is just another resource and an appoinment can be booked without including the patient, i.e., a consult. It is not believed that this many-to-many will ever need to be resolved.

schedules (0,1) :: Patient_encounter :: is_scheduled_by (0,1)

OpenIssue: This may have to be changed after we figure out what tis "encounter" thing really is.