IndustriesHealthcare

Two hours of admin for every hour of care

Clinicians did not train for data entry, and the documentation load is now the single largest predictor of burnout. The work is real, it is required, and almost none of it needs a clinical licence to complete.

13 hrs

of physician and staff time per week spent on prior authorisation

AMA

93%

of physicians say prior authorisation delays patient care

AMA

7.3 hrs

of a physician's week goes to administrative tasks alone

AMA, 2024 workweek data

43%

of physicians still reporting burnout symptoms

AMA, 2024

Where the time and revenue actually go

These are the specific, measured problems in healthcare and providers. Not generic digital transformation.

01

Documentation follows clinicians home

Roughly two hours go into the record and administrative tasks for every hour of direct clinical time. In the 2024 figures a physician's week runs to about 57.8 hours, of which 27.2 are direct patient care and the remainder is documentation, orders, results and paperwork.

02

Prior authorisation is a full working day, every week

Physicians complete around 40 prior authorisations a week, consuming roughly 13 hours of physician and staff time. Almost none of that is clinical judgement. It is assembling documents that already exist, into a format a specific payer will accept.

03

The delay reaches the patient

93 percent of physicians report that prior authorisation delays care and 89 percent say it contributes to burnout. More than a quarter report it having caused a serious adverse event for a patient in their care. This is an administrative process with clinical consequences.

04

Referral triage is manual and inconsistent

Incoming referrals arrive by fax, portal, email and phone, in no fixed format, and someone has to read each one, work out urgency, check whether the records are complete, and route it. The same referral gets triaged differently depending on who opens it.

05

The schedule leaks in both directions

Slots go unfilled while a waiting list exists, because nobody has time to work the list when a cancellation lands. Meanwhile patients who could have been seen sooner wait, and the clinic absorbs the cost of the empty room.

06

Patients ask the same operational questions constantly

Where is my referral, has my result come back, what do I need to bring, is my prescription ready. None of these need a clinician, all of them arrive on a phone line staffed by people who are also checking patients in.

07

The information is present but not connected

The answer to most administrative questions already exists across the record, the practice management system, the imaging system and the payer portal. It is not missing. It is simply that no one system can see all four at once, so a human becomes the integration layer.

What we build for healthcare teams

01

Prior authorisation packet assembly

Pulls the relevant notes, results and prior treatment history from the record, assembles them against the specific payer's requirements, and presents a complete packet for clinician review before anything is submitted.

02

Documentation support grounded in the record

Draft summaries, letters and referral responses built only from what is in the chart, with every clinical assertion linked to the note it came from, so review is verification rather than rewriting.

03

Referral intake and triage

Reads referrals arriving in any format, extracts the structured detail, flags missing records, applies your triage criteria consistently, and routes with a recommended urgency for a human to confirm.

04

Waiting list and cancellation matching

When a slot opens, the system finds the patients who fit it clinically and logistically and offers it, instead of the slot going unused because nobody had time to work the list.

05

Patient operational questions, answered from live systems

Status of a referral, result or prescription, answered from the actual systems rather than from a queue, with anything clinical escalated rather than attempted.

Two workflows, end to end

Illustrative composites, drawn from how these workflows actually run in each industry. Not named client engagements.

01Getting the authorisation through
The situation

A specialist orders an MRI. The payer requires documented conservative treatment before it will authorise the scan.

What usually happens

A staff member searches the chart for prior physical therapy notes, imaging and medication history, copies them into the payer portal, waits on hold to clarify a field, and submits. If it is denied for insufficient documentation the cycle repeats. Total elapsed time is measured in days and the patient waits through all of it.

What our system does

The system reads the payer's specific criteria for that procedure and plan, retrieves the conservative treatment history, the relevant imaging and the clinical rationale from the record, and assembles a complete packet with each element linked to its source note. The ordering clinician reviews and approves. If a required element genuinely does not exist in the record, it says so up front rather than submitting an incomplete packet and waiting for a denial.

Steps the system took
01Payer and procedure specific criteria retrieved
02Supporting history assembled from the record, each item cited
03Gaps flagged before submission rather than after denial
04Clinician reviews and approves the packet
05Submission and status tracked, with the result written back
02Getting the schedule to fill itself
The situation

A patient cancels a Thursday afternoon appointment at 4pm on Wednesday, and there is a six week waiting list.

What usually happens

The slot stays empty. Working the waiting list means calling people in order until someone answers and can rearrange their day at short notice, and the front desk is checking in patients until closing.

What our system does

The system identifies which waiting list patients match that slot on clinical need, appointment type and travel distance, offers it to them in priority order by their preferred channel, and confirms the first acceptance. It updates the practice management system, cancels the outstanding reminders for the original booking and notifies the clinician of the change. Anything clinically ambiguous goes to a human rather than being decided automatically.

Steps the system took
01Waiting list matched on clinical and logistical fit
02Offer sent by the patient's preferred channel, in priority order
03First confirmed acceptance takes the slot
04Practice management system and reminders updated
05Clinically ambiguous cases routed to a human instead

Wired into the healthcare stack you already run

Records and practice

  • Epic
  • Cerner
  • athenahealth
  • eClinicalWorks
  • NextGen

Scheduling and intake

  • Phreesia
  • Luma Health
  • Klara
  • Zocdoc
  • Twilio

Revenue and payers

  • Availity
  • Waystar
  • Change Healthcare
  • Payer portals
  • Clearinghouses

Documents and comms

  • Fax gateways
  • DocuSign
  • SharePoint
  • Secure messaging
  • HL7 and FHIR

Start with one healthcare workflow

A 30 minute audit, no sales pitch. We map where automation can cut manual work and create measurable ROI across the tools you already use.