Class steward is Inter-Enterprise (ADT/Finance/Inter-Enterprise)
A request for the booking of an appointment.
Rationale: Separates an appointment from a request for an appointment.
OpenIssue:
The reason that the appointment is to take place. Examples are: ROUTINE, WALKIN, CHECKUP, FOLLOWUP, EMERGENCY.
Rationale: Currently in 2.3
OpenIssue: It appears that this attribute has the potential to be used for two types of codes that should be mutually exclusive (local site specific code, and the other is a service code) combining an administrative reason with the thing to be performed
|ARQ^7^00866^Appointment Reason| |SCH^7^00866^Appointment Reason|
The type of appointment request. Examples are: NORMAL, TENTATIVE, COMPLETE.
Rationale: Currently in 2.3
OpenIssue:
|ARQ^8^00867^Appointment Type| |SCH^8^00867^Appointment Type|
Parameters and preferences regarding the selection of an appropriate resource for an appointment. The first component of this field is a code identifying the parameter or preference and the second component is the actual data value for that parameter.
Rationale: Currently in 2.3
OpenIssue: Proposed data type that accommodates parameter, value pairs where the pairs are drawn from a user defined table.
|APR^2^00909^Resource Selection Criteria|
Unique identifier for an appointment request.
Rationale: Separates appointment from its request.
OpenIssue:
|ARQ^1^00860^Placer Appointment ID| |SCH^1^00860^Placer Appointment ID|
Parameters and preferences regarding the selection of an appropriate location for the appointment.
Rationale: Currently in 2.3
OpenIssue: Proposed data type that accommodates parameter, value pairs where the pairs are drawn from a user defined table.
|APR^3^00910^Location Selection Criteria|
Uniquely identifies an individual occurrence (a child) of a parent repeating schedule appointment.
Rationale: Currently in 2.3
OpenIssue: Probably do not need this class, could make a recursive relationship on Appointment_request
|ARQ^3^00862^Occurrence Number| |SCH^3^00862^Occurrence Number|
The urgency of the request.
Rationale: Currently in 2.3
OpenIssue:
|ARQ^12^00871^Priority|
How long the appointment repetitions should continue, once they have begun.
Rationale: Currently in 2.3
OpenIssue:
|ARQ^14^00873^Repeating Interval Duration|
The interval between repeating appointments.
Rationale: Currently in 2.3
OpenIssue: May require a new data type or attribute group. Talk to CQ about the need for a repeating interval datatype
|ARQ^13^00872^Repeating Interval|
A code describing the cancel reason, the delete reason, the discontinue reason, the add reason, or any other code describing the reason for a specific request event.
Rationale: Currently in 2.3
OpenIssue:
|ARQ^6^00865^Request Event Reason|
The amount of time being requested for the appointment.
Rationale: Currently in 2.3
OpenIssue:
|ARQ^9^00868^Appointment Duration| |SCH^9^00868^Appointment Duration|
The date and time that the appointment is requested to begin in the form of a date/time range.
Rationale: Currently in 2.3
OpenIssue: Proposed new attribute type not currently supported. Needs to be proposed to CQ for the DT/AT work.
|ARQ^11^00870^Requested Start Date/Time Range|
Parameters and preferences regarding the selection of an appropriate time slot for an appointment.
Rationale: Currently in 2.3
OpenIssue: Proposed data type that accommodates parameter, value pairs where the pairs are drawn from a user defined table. Needs new attribute type mapping to DT:PV
|APR^1^00908^Time Selection Criteria|