Home / How It Works
How It Works: One Document, Start to Finished
This page walks a single document through the path — from arrival to the moment the work it represents is finished and on the record. The example is a patient referral arriving by fax, but the same five stages apply to intake packets, claims, and clinical documents.
Intake: arrival is a system event, not a favour
The referral lands in the fax queue at 8:12 a.m. In a manual process it would wait in a tray until someone collected it and keyed it into the scheduling system. In the path, arrival is intake: the document is captured the moment it lands, given an identity, and queued alongside portal submissions, uploads, scans, and email attachments — every arrival enters the same way.
Nothing waits on a person noticing it, and nothing is lost between the fax machine and the desk. From here on, its location and status are always known.
Classification & extraction: the document is read
Next, the processing engine — MaxxOwl™ SI on the MaxxLogix platform — reads the document. Classification comes first: this is a referral, not an intake form or a claim attachment. The engine decides from the document's layout, language, and content — not from which tray it landed in.
Extraction follows: patient, referring provider, requested service, dates, and authorisation details are lifted out as structured data. Multi-page faxes and uneven scans are handled as part of the read, and every value carries a confidence level the next stage puts to work.
Validation: data is checked before it is trusted
Extracted data is only useful if it can be trusted, so the path checks it first. Required fields must be present — a referral without a requested service does not pass. Formats are normalised. The referral is matched to the right patient record, so it joins an existing history instead of starting a duplicate.
Anything that fails a check becomes an exception: a missing authorisation, an illegible page. It leaves the straight-through path and is routed to a person together with the document, the extracted data, and the specific reason it was flagged — while everything that passed keeps moving.
Workflow: work moves by rule, not by inbox
The validated referral moves into workflow. Routing follows your rules — by service, by location, by urgency — and the referral becomes a task in the scheduling queue, not a thread in someone's email. Schedulers work in Outcome Workspace™, where the document and its data sit side by side and each action is recorded with a name and a timestamp.
If a step stalls, the workflow knows. Reminders and escalations are part of the route itself, so a referral that is waiting too long surfaces on its own instead of being discovered by chance.
Outcome: the finish is recorded, not assumed
When the appointment is arranged, the path closes. The referral's outcome — what got done with it — is written to the record: who handled it, what was matched, how long each stage took, and what needed human judgement along the way. The whole handling sits inside HIPAA-compliant document management, hosted on AWS under a signed AWS BAA, with a BAA available.
That record is the point. It is what Outcome Analytics™ reports on: referral volumes, exception rates, stage-by-stage cycle times, and the outcomes each process produces. Improvement stops being a guess, because the path keeps its own evidence.
The other front door: forms and portals
Not everything arrives as a document. Patient intake submitted through a form or a portal — MaxxLaunch™ on the MaxxLogix platform — arrives as structured data already, and joins the same path at the validation stage. From there the loop treats both doors identically: checked, routed, worked, and recorded. Documents and data, one path.
Same path, every healthcare document
Every document type your operation runs on walks the same five stages — intake packets, referrals, claims and their attachments, eligibility records, clinical correspondence. The rules and routings change from process to process; the path doesn't. That consistency makes the outcomes comparable — and makes a platform different from a pile of point tools.
Put your documents through the path
The stages above run on MaxxLogix — Outcome Cloud™, MaxxOwl™ SI, Outcome Workspace™, and the rest of the platform, with capacity published in SI Units and no surprise overages. See it at maxxlogix.com.
Visit MaxxLogix