Skip to content
Book a free consult
Interface sounds
Healthcare Practices Transformation concept 4 min read

Case study

AI Intake, Notes, and Billing Busywork Removal for a Physiotherapy Clinic

How a physiotherapy group turns paper intake, re-typed SOAP notes, and manual claim entry into one reviewed flow: the patient's own words become the record, and a clinician approves every step.

No client engagement behind this piece: this is how we would transform this category of product, with benchmark-sourced targets.

Who this is for

A typical multi-clinic physiotherapy group

Industry

Private healthcare (physiotherapy), 3 locations, ~25 staff

Legacy stack

Desktop practice management systemPaper and PDF intake formsManual claim entry into insurer portals

Engagement

Concept

A paper intake form and a cluttered clinic software window transforming into a calm patient-sentence bar with a structured record.
Contents

A physiotherapy clinic runs on hands-on hours: assessment, treatment, progress. Around every one of those hours sits a second, invisible shift. The front desk re-types paper intake forms into a desktop practice management system while the phone rings. Clinicians stay late writing SOAP notes from memory. Someone spends Friday afternoon keying claims into insurer portals, then re-keying the ones that bounce. And every new location the group opens adds another copy of the same busywork.

This is the transformation we would run for that group. It is presented as a concept, built on the same method we use in client engagements, so you can see exactly what the before, the after, and the path between them look like.

The busywork, quantified

Follow one new patient through the flow. She fills out a paper form on a clipboard in the waiting room: history, medications, injury, insurer, consent. The front desk re-types that form into the PMS, field by field, between phone calls. In the treatment room the physiotherapist asks her the same questions again, because the clipboard never made it that far, then spends ten minutes after the session writing the SOAP note from memory. At day’s end, someone reads that note, picks a billing code, and types the claim into the insurer’s portal by hand. One visit, one story: told twice, typed three times.

The clinic is not disorganized. It is faithful to how clinic software was designed: a person translates what the patient said into fields, one keystroke at a time. The clinical judgment, the treatment plan, the billing rules underneath are all still right. The waste lives entirely in the translation layer.

Before and after: the intake-to-billing flow

Drag the handle. The before is the recreated legacy intake screen; the after is the intelligent flow designed in its place.

The intelligent intake
"My right shoulder has been stiff since I painted the fence two weeks ago, and it clicks when I reach up."

Drafted from the patient's words · review and confirm

Intake
R shoulder · onset 2 wks
Insurance
Sun Life · EH-7743210
SOAP draft
S + O pre-filled for review
Claim line
PT-INIT-45 · Initial 45 min
Confirm Intake, note, and claim from one sentence
Their clinic software today
New Patient Visit Re-typing from the paper form
PatientInsuranceSOAP NoteScheduleBilling
SOAP note and claim still to type
Save draft Next tab

The sentence the patient says in the waiting room becomes the start of the record. The old form does not disappear; it becomes the review surface, where the clinician confirms what the system drafted instead of typing it from scratch.

What we built

The concept above is not a mockup exercise. It is the output of the same engagement steps we run in client work:

  • We map the intake-to-billing workflow first: it touches every patient at every location, and its time cost is easy to measure at the front desk.
  • We design the data path as private by design: patient information stays in the clinic’s environment, the AI reads through the same permissions staff already have, and processing runs with zero data retention.
  • We build the drafting layer as grounded: the structured intake, the SOAP note, and the claim line are drafted from the patient’s own words plus the clinic’s records and fee schedules, never from thin air, and every draft shows what it used.
  • We design the approval gates before the automation: the clinician confirms the note, the biller confirms the claim, every field visible and editable, with an undo and an audit trail.
  • We wire evals from day one: drafts are scored against real historical visits, and every correction a clinician makes becomes a test case.

How it works

The clinic visit loop: the patient's own words become a structured intake and a draft note, a clinician reviews it, and the claim is pre-filled and approved by a person.

The PMS stays the source of truth, which is what makes this safe for a clinic with real patients and real insurers. Before the visit, the patient describes the problem once, in their own words, on their phone or a clinic tablet. The system turns that into a structured intake, checks the policy details, and drafts the SOAP note the clinician refines in the treatment room. The confirmed note pre-fills the claim, and a person approves it before anything is sent. The AI never posts to the chart or to an insurer on its own.

Because patient information stays inside the clinic’s environment and processing runs with zero data retention, the design lines up with what PIPEDA expects of a private healthcare business: collect once, with consent, use it for the purpose the patient gave it, and let no copy wander.

Why this pays back

For a clinic group the return shows up three times. The front desk stops being a transcription service and gets back to the patients on the phone. Clinicians finish notes in the room instead of after hours, which is the difference between a sustainable caseload and a burned-out one. And claims go out the same day with fewer bounces, because each claim is drafted from the confirmed note instead of retyped from it. Time-and-motion research on clinical documentation shows the stakes: when desk work eats nearly two hours for every hour of care, removing the re-typing is not a convenience, it is capacity.

The outcomes

Intake data entry per new patient

Paper form, re-typed into the PMS Patient's own words become the record

2x entry to zero re-typing1

Design target

Clinician desk work per hour of direct patient care

Nearly 2 hrs2

Industry benchmark

Time to the first shippable slice

4-6 wk3

Design target

1 Design target for the intelligent intake flow, measured against the recreated legacy flow shown in the before/after above.

2 Annals of Internal Medicine time-and-motion study (2016): for every hour of direct patient care, physicians spend nearly two additional hours on EHR and desk work.

3 Standard first-slice scope: one workflow, one metric, evals and an approval gate included.

Frequently asked questions

Does our patient data leave the clinic to make this work?

No. The system is designed so patient information stays in the clinic's environment: the AI reads the PMS through the same permissions staff already have, processing runs with zero data retention, and nothing is ever used to train anyone's model. That is the posture PIPEDA expects for personal health information, and it is designed in before the first feature, not patched on after.

What happens when the AI gets a clinical detail wrong?

Nothing enters the chart without review. The draft note appears with every line visible and editable, the clinician confirms or corrects it, and each correction is logged. Those corrections feed the evals, so accuracy is measured on the clinic's real visits, not on a demo script.

We already have practice management software. Does this replace it?

No. The PMS stays the source of truth. The intelligent layer sits on top of it: it drafts the intake, the note, and the claim from the patient's own words, and it writes into the PMS only through the reviewed confirm step. Bookings, records, and billing history stay exactly where they are.

What would trying this cost?

A scoped proof of value on the single busiest workflow, usually intake to note, priced as a fixed first slice. It ships in weeks with its own metric, so the decision to go further is made on a measured result, not a promise.

Go deeper on the method

A cluttered grid of controls condensing into a single intelligent input.
AI ProductUX

From Busywork to Brilliance, Rethinking Software as Intelligence

Most software still makes people do the work. Here is how we re-engineer click-heavy products into intelligent experiences that quietly do the work for you.

Read article
A cluttered maze of form fields and filters dissolving into a single intent box that yields a result.
AI ProductUX

The End of Forms: When You Say What You Need and the Product Builds It

Forms, filters, and clicks were a workaround for software that could not understand you. Generative, conversational interfaces let people state what they want and let the product assemble the screen, report, or action.

Read article
A secure boundary around your data, with AI working inside the boundary rather than sending data out.
StrategyTrust

Your Data Stays Yours: Adding AI Without Handing Over the Crown Jewels

The top reason teams stall on AI is fear of where their data goes. Here is how to add intelligence while your data stays in your environment, plus what to ask any AI vendor before you trust them.

Read article

More transformations

An unsorted grid of forty-one claim photos becoming a structured damage assessment where every line cites the photo it came from, with the coverage clause quoted and one uncertain line flagged.
Professional Services Concept

AI Claim Triage From Photos: First Notice of Loss to a Reviewed Assessment

How a property claims operation turns a folder of unsorted phone photos and a 62-page policy into a structured damage assessment: every line citing the photo it came from, the coverage clause quoted, uncertain lines flagged, and an adjuster approving before anything moves.

32.4 days

Average property claim, filing to finished repairs

A crowded RFQ inbox queueing on the left transforming into a priced, stock-checked quote with one flagged line and a rep approval button.
Wholesale & Distribution Concept

AI Quote Desk for a Wholesale Distributor: RFQ Inbox to Priced Quote in Minutes

How a parts distributor replaces the morning RFQ pile and the three-system price hunt with a copilot that extracts every line item, prices it from the company's own item master and contracts, checks stock, and drafts the reply, with a rep approving every quote before it leaves.

60-70%

Share of routine admin work generative AI can absorb

Get the next transformation in your inbox.

When we publish something worth your time, you will be first to know. No spam, unsubscribe anytime.

Your version of this

Run a clinic drowning in intake, notes, and billing? We will mapyour version of this transformation in a free consult.

We design and build every engagement ourselves. No juniors, no handoffs.

Free, no obligation Your data stays yours Reply within 1 business day