PLATFORM · BACK OFFICE

The back-office engine behind every booking

Every patient-facing workflow — online, inbound, outbound, walk-in — feeds the same intake, routing, and task-assignment layer, so staff work from one queue instead of five systems.

OCR-driven intake Auto vs. manual routing One system of record
THE FULL PATH

From referral to confirmed appointment

Referral In fax · eReferral · upload AI Extraction & Urgency Check Routing Engine Auto-Eligible no-gap slot optimizer Manual-Only staff task queue EHR/RIS Write-Back
STAT, MSK, and high-risk studies route to a staff task queue; everything else books automatically and falls back to manual review after 48 hours if unbooked.
WHAT'S INCLUDED

Where every channel actually meets

Requisition intake & OCR

Faxed and eReferral orders are ingested automatically; Canadian-hosted, PHIPA/PIPEDA-aligned OCR extracts the clinical detail needed to route them.

Rules-based routing, not guesswork

Urgency and procedure classification decide the path: auto-eligible studies book themselves, STAT, MSK, and high-risk BMD studies go to a person, and anything unbooked after 48 hours falls back to manual review.

A task pool, not a shared inbox

Staff pull from an assignment model with clear administrator and staff role boundaries, instead of hunting through a folder of PDFs.

One write, everywhere it matters

Confirmed bookings write back to your EHR/RIS and stay in sync with the EMR and PACS your team already runs — no duplicate entry, no reconciling two calendars.

DOCUMENT MANAGEMENT

Every fax and referral, processed the same way

Clinic fax lines route directly into Ruby alongside anything staff upload manually, so every document — regardless of source — lands in one place with full visibility into what’s been processed and what hasn’t.

One dashboard, every location

Requisitions, clinical documents, and admin paperwork all land in the same Documents Dashboard — grouped by site, with a status indicator and the age of the oldest unresolved item on every location card, so a site falling behind is visible at a glance, not discovered later.

~5 min

Saved per document processed

OCR-based intake extraction removes the manual data entry staff would otherwise do for every requisition or referral received.

VERIFIABLE EXTRACTION

See exactly what Ruby read off the page

Every document shows a confidence badge — High, Medium, or Low — next to what Ruby extracted, so staff are confirming a reading instead of re-entering one from scratch. A flag on a mismatched field means exactly that: something on the page didn't match what's on file, shown side by side so it's a 10-second check instead of a search.

Requisition_Ultrasound.pdf HIGH confidence
EXTRACTED FIELDS
PatientJ. Rivera
DOB · Age1990-07-22 · 36Y
Phone(519) 555-0171
ProcedurePelvic Ultrasound

Three ways to turn a requisition into a booking

Book in Ruby finds the next available slot automatically across every location that offers the procedure, the same way your EHR/RIS's own scheduling wizard would. Book Manually keeps staff in your EHR/RIS's own calendar while Ruby attaches the requisition automatically. A third option links a requisition back to an appointment already booked directly in your EHR/RIS — no re-entry, whichever order the work happens in.

Procedures Ruby can't confidently match get flagged, not guessed

When a procedure named on a requisition doesn't correspond to anything in your EHR/RIS's procedure list, it's shown as Unmatched From Requisition for a person to resolve — the same caution applied to low-confidence extractions and version-code mismatches.

Tags, notes, and triage built for a shared queue

Any clinic can create its own tags for the categories it tracks; internal notes give every document a timestamped record of what's been tried and what's still needed; and a Stat / Urgent / Routine priority keeps the most clinically urgent items visible first.

MANAGEMENT VISIBILITY

Built for the person accountable for the backlog, too

Pipeline health, at a glance

An intake summary bar tracks documents in flight by category — requisitions, clinical, administrative, junk, unmatched — with an all-clear banner when active items are within SLA, and a dedicated count for anything stuck in an extraction error.

Staff workload, not just document status

A load board shows what's assigned to each staff member, who's idle with a backlog, and who has capacity to take on more — so work gets rebalanced before a queue backs up on one person.

A canonical referring-physician record

Every referring physician is tracked clinic-wide with requisition volume and last-seen date — de-duplicated from the free-text name on any single requisition, so reporting and routing both work off one clean record.

See the orchestration layer with your own referral volume

Bring a week of real requisitions — we'll walk through exactly how Ruby would route them.