Skip to main content
AnyVet
Back to docs

Reference

Appointment Status Flow

The meaning of the main appointment and queue states used across booking, queue, and billing workflows.

Section: Reference
Updated: 2026-03-09
Tags: appointment, queue, reference

Appointment Status Flow

Appointments and same-day queue handling in AnyVet Smart are driven by status transitions. Understanding those states makes queue interpretation and operational decision-making much easier.

Default Status Flow

PENDING -> WAITING -> IN_PROGRESS -> WAITING_FOR_PAYMENT -> PAID -> DONE

Meaning of Each Status

StatusMeaningTypical usage point
PENDINGAppointment exists but has not entered active handling yetadvance bookings, immediate post-creation state
WAITINGPatient has arrived and is waiting for care or servicesame-day queue management
IN_PROGRESSClinical care or service work is actively happeningclinician or assigned operator is working
WAITING_FOR_PAYMENTCare or service is finished and the case is waiting for paymentfront desk billing handoff
PAIDPayment is completeimmediate post-payment state
DONEThe overall workflow is fully closedfinal operational closure

Operational Interpretation Tips

  • If WAITING accumulates, investigate front desk congestion or insufficient consultation capacity.
  • If a case stays too long in IN_PROGRESS, check for unfinished charting, incomplete closure, or a missed downstream action.
  • If many cases are in WAITING_FOR_PAYMENT, review the POS and billing handoff process.

Tip: Queue status is not just a label. It is also an ownership signal that helps the team know whether the next responsibility belongs to front desk, clinician, or cashier.

Common Misunderstandings

Payment completion does not always mean the operational workflow is fully closed. The team should define clearly when the case is considered truly DONE.

Status transitions can look different depending on role and screen

Not every user can directly change every status. Available actions differ by permission and by page context.

Warning: Skipping states arbitrarily can make reports, audit logs, and billing interpretation drift away from what really happened operationally.