Designing Outpatient Lab Booking UX When Hospital and Community Networks Don’t Share a Queue

Primary CTA: https://www.tsbhealthcare.com/patient-access-platform/

If you have ever shipped a calendar widget and called it “patient access, British Columbia’s laboratory landscape will humble you.

Patients arrive with a requisition — a clinical order — and an administrative question the EHR rarely answers politely: which collection site can see me, and when? In BC that question splits across hospital / public outpatient laboratory booking and independent community lab schedulers. The assays may look similar on a panel list. The queues do not.

The product boundary that keeps you honest

LabOnlineBooking.ca (built by TSB HealthCare) is a scheduling surface for participating public and hospital outpatient labs. It is explicitly not a testing facility. That sentence is a UX requirement, not a footnote. The moment a booking product implies it “does bloodwork,” support tickets turn into clinical expectations the software cannot meet.

A patient access platform — overview at TSB’s patient access platform — owns finding, booking, arrival, and flow. The laboratory information system still owns specimens and results. Cross that line in copy or UI and you have created harm, not convenience.

Two schedulers, zero shared state

Community networks such as LifeLabs publish availability on their own properties (appointments.lifelabs.com). They are independent. Designing as if a deep link could “hand off” a slot between networks invents a partnership that does not exist.

Product implication: wayfinding beats unification cosplay. Help users identify the correct lane early — hospital outpatient vs community — instead of promising a mega-calendar that fabricates interoperability.

UX patterns that survive real outpatient volume

1. Service-aware slots
   
   Routine draws, fasting draws, drop-offs, and kit pick-ups are different durations and prep rules. A single generic “appointment” type trains patients to book the wrong chair.

2. Requisition-up-front without becoming an EMR
   
   Capture enough order metadata to route the visit. Do not invite free-text clinical narratives into a public form.

3. Multi-site search as the default
   
   Nearest kilometre ≠ soonest capacity. Cross-location search is the productivity feature patients actually feel.

4. Arrival is part of booking
   
   Self check-in and one fair queue (booked + walk-in where policy allows) close the loop the calendar opened. Booking without arrival design just moves the line indoors.

5. Disclosure in the empty states
   
   When a site has no capacity, say so. Offer other participating outpatient sites. Do not silently pivot users into an unrelated community network without labelling the jump.

What “scale” means when you refuse vanity metrics

Operated by TSB HealthCare since 2018 across four BC health organizations. Current footprint: 69 active outpatient sites, 820,105 distinct patients, 4.01M appointments booked, 16,958 bookings in the week of 14–19 Sep, 8.5 years in production. Those numbers describe scheduling throughput and network breadth. They are not clinical quality scores, and they are not a substitute for invented compliance claims nobody asked you to publish in a blog post.

For engineers and PMs, the interesting productivity story is quieter: fewer abandoned phone lines, fewer no-shows recovered into open chairs, fewer patients who drove to the wrong building because the UI collapsed two ecosystems into one button.

A short checklist before you ship “lab booking”

• [ ] Copy states you schedule visits; you do not perform tests
• [ ] Hospital outpatient and community paths are labelled as separate
• [ ] Slot types mirror real collection work, not marketing personas
• [ ] No PHI in analytics demos or screenshot fixtures
• [ ] Primary CTA lands on a page that explains access architecture, not a fake partnership

If you are mapping a similar outpatient problem outside BC, start with lane discovery. The calendar is the easy part. The hard part is refusing to pretend every laboratory shares a queue.

Further reading / CTA: Patient access platform — TSB HealthCare