class: appointmentRequest

public class: appointmentRequest
Author:
Project: Phase: 1.0; Status: Proposed; Version: 1.0; Complexity: 1
Dates: Created: 16/12/2005 16:26:14; Modified: 09/02/2006 13:15:53;
Flags: Active: false; IsRoot: false; IsLeaf: false;
Extension Points:
UUID: {D14A7765-95B7-4498-981A-DDC483EC576E}
The appointment Request infromation is administrative.
 

Goto: Custom Properties, Fields

Extends: initialisedRequest

See also: initialisedRequest, additionalRequirement, activeAppointment, structuredReferralLetter

Appears in: Communication Description, Communication Description, Choose and Book Referral Status

Connections
 
Custom Properties
 
appointmentRequest Attributes
Attribute Details
public int
  assessmentOutcome
Range:0 to 1
Notes: Coded outcome of a clinical assessment.

The following are examples of values, this will be an external list of values maintained by Choose and Book.
Advise Referrer
Refer to Secondary Care
Resolved, Patient Request
Resolved, Treated During Assessment
Treat in Tier Two
Refer On
Refer On, Outside Choose and Book
public int
  breachOffset
Range:0 to 1
Notes: Number of days past lead time for referral letter.

Although the breachOffset is administrative information, it is unlikely that an application would wish to allow a patient to view this.
public date
  dueByDate
Range:0 to 1
Notes: Date by which the patient should be seen by the specialist.
public int
  requestedAction
Notes: A code describing the action requested within the referral.

The Coded with Code System datatype flavour is used to carry this information as follows:
- The code attribute will contain a value from the list of codes in the ServiceTypeRequested vocabulary;
- The codeSystem attribute will contain the OID referenced in the ServiceTypeRequested vocabulary.

Requested action can be specified in the user interace or in the structured referral. Hence the field appears twice in the model. If both methods are used it is not clear whether the values are overridden or stored separately.