Converge Appointment and Queue on One Encounter

Picture a patient who booked an appointment and takes a waiting-room ticket when they arrive. That is two front-of-house paths for the same visit, and a lesser system would happily open two separate visit records and split the patient’s day in half. Veona does not: both the appointment check-in and the queue token resolve to the same single encounter (the one record of this visit). One patient, one visit, one place everything attaches.

Who / when: the Front Desk drives both halves — checking the appointment in and issuing the queue token — usually within moments of each other when the patient arrives. This page shows that the two actions converge rather than collide.

We will follow Amina Bello, who booked a follow-up and then took a ticket at the door.

1. Front Desk — check Amina’s appointment in at Appointments → Schedule by pressing “Check in” on her row. This opens an “Appointment-origin / Outpatient” encounter and back-links it to the appointment (the full walk-through is in Check In an Appointment Into an Encounter).
2. Front Desk — now issue her queue token at Queue → Board: press “Issue token”, look Amina up by UHID (Unique Health ID, the permanent VNA-… number), pick the lane and confirm.
3. Front Desk — here is the convergence: instead of opening a new visit, the queue token resolves to the encounter that check-in already opened and links to it. Amina ends up with one encounter, not two — the appointment and the ticket both point at it.
4. Front Desk — confirm it if you like: Amina shows a single open visit, with both her appointment and her active queue token referencing it. There is no parallel, duplicate encounter to reconcile later.

Note

The rule is simply one patient, one open visit. Whichever front-of-house path runs first opens the canonical encounter; the other path finds it and joins it. This is the same single encounter the nurse, the physician and the bill all work against — see Open an Encounter at Registration for where that one visit record comes from.

Caution

This is why you never need to manually merge a “queue visit” with an “appointment visit” — they were never separate. If you ever see a patient appearing to have two open encounters for one day, that is worth raising, because Veona is built to converge them, not split them.

What happens next

With both paths on the one encounter, Amina flows cleanly: the nurse records vitals against it, the physician charts and orders into it, charges accrue to it, and the queue token drains as she is served (see Issue, Serve and Drain a Queue Ticket). When the doctor presses “Complete”, this single encounter closes — satisfying both the appointment she booked and the ticket she drew.

Follow the trail

• Previous: Check In an Appointment Into an Encounter · Link a Queue Ticket to an Open Encounter
• Related: Open an Encounter at Registration · Issue, Serve and Drain a Queue Ticket · A Patient’s First Visit, End to End