Order and Appointment Lifecycle

The Walk-In Phlebotomy orders are composed of two different lifecycles, the Order lifecycle and the appointment lifecycle, detailed in the following sections.

​

Order Lifecycle

As discussed in Lab Test Lifecycle - Statuses, each lab testing modality has the following format

[HIGH-LEVEL STATUS].[TEST MODALITY].[LOW-LEVEL STATUS]

For each modality, there can be multiple low-level status, for Walk-In Phlebotomy the possible low-level status are:

• ordered: Vital received the order, stored it into our system, and started processing it asynchronously.
• requisition_created: An order requisition form was validated and created with the partner laboratory, making the order available to be carried out.
• appointment_pending: An appointment was placed in Vital’s system for the order, but doesn’t have a scheduled date.
• appointment_scheduled: An appointment was scheduled or rescheduled for the order.
• appointment_cancelled: The appointment was cancelled, by either the patient, Vital or you.
• partial_results: The laboratory has started making partial results available.
• completed: The laboratory processed the blood sample and final results are available.
• cancelled: The order was cancelled by either the patient, Vital or you.

The Finite State Machine that defines the possible transitions for the low-level statuses described above is illustrated in the following diagram.

​

Appointment Lifecycle

The appointment lifecycle is separate from the order lifecyle, and it corresponds to a single appointment. The possible status are defined as follows:

• pending: An appointment was placed in the system, and is pending updates from the phlebotomy service.
• scheduled: An appointment was scheduled or rescheduled.

The Finite State Machine that defines the possible transitions for the appointment statuses described above is illustrated in the following diagram.

The events are related to a single appointment. An order can have multiple existing appointments in Vital system, although only one appointment will be considered active and returned when using the GET Appointment endpoint.