Case study
Twelve Visits, One Report: Insurer and WSIB Progress Reporting Without the Sunday Afternoon
A physiotherapy clinic's insurer reporting is not documentation, it is aggregation: twelve visits of measurements and notes compressed into one structured report on a deadline set by somebody else. This is the transformation that assembles the trend from the record and leaves the clinical reasoning to the therapist.
No client engagement behind this piece: it is how this category of product would be transformed, with benchmark-sourced targets.
Who this is for
A typical multi-clinic physiotherapy group
Signed off by Clinic director, with the billing lead scoping
Industry
Private healthcare (physiotherapy and rehabilitation), 3 locations, about 25 staff, mixed extended health and WSIB caseload
Legacy stack
Engagement
Concept
Contents
A physiotherapist finishes at six and has three progress reports due. Each one means reopening twelve visit notes, finding which outcome measures were actually recorded and when, working out whether the numbers moved, and rewriting all of it into a template designed by an insurer who will read it for ninety seconds. The clinical thinking takes four minutes. The other twenty-five are archaeology.
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 the before, the after, and the path between them are all visible.
What does insurer reporting actually cost a clinic?
There is no published Canadian index of administrative time in physiotherapy, and this study is not going to manufacture one from a vendor blog. What exists is a measurement of the surrounding category: the CAQH Index 2025, published in February 2026 and built on data from more than 600 provider organizations and health plans representing 63% of insured lives, identifies roughly $21 billion still available from automating provider-to-payer transactions that remain manual or partly manual. That is US medical data. It sizes the shape of the problem and says nothing specific about an Ontario physiotherapy clinic, which is exactly how it is used here.
What is specific is the structure of the work. Progress reporting is not documentation, and this is the distinction most software gets wrong. Documentation captures what happened in one visit while it is happening. Reporting compresses many visits into a claim about direction, on a deadline the clinic did not set, in a format the clinic does not control. Those are different problems, and a tool built for the first does not solve the second.
Before and after: the report
Drag the handle. The before is twelve notes reopened one by one; the after is the assembled trend designed in its place.
Flagged at visit 8, not tonight
Range of motion required by this authorization, last recorded at visit 1. Still collectable.
Interpretation
Left for the therapist. The trend is a fact; whether it justifies more visits is a clinical claim.
The clinical thinking takes four minutes. The other twenty-five are archaeology.
The insurer’s template does not change and neither does the therapist’s judgment about whether the patient is progressing. What changes is that the twelve visits arrive already read, with the measures plotted and the gaps named.
What we built
The concept above is the output of the same engagement steps we run in client work, and two of them are decisions a competent peer could argue with.
- We make outcome measures structured at the point of capture, before touching the report at all. This is the unglamorous decision and it is the one that makes everything downstream possible. A clinic that records measures in free text can have prettier reports, but it cannot have trends, and a trend is what an insurer is buying.
- We run the completeness check continuously against the authorization rather than at report time. A missing required measure surfaces around visit eight, while the patient is still coming in, instead of on the evening the report is due, when the only options are submitting something incomplete or fabricating something plausible.
- We assemble the trend and stop before the interpretation. The system reports which measures moved and by how much; the therapist says what that means and whether more visits are warranted. This is the decision most likely to be argued with, because interpretation is the slowest part and a fluent auto-written narrative demos beautifully. It is also a clinical assertion to a third party with money attached.
- We refuse to auto-submit to any insurer portal, including where an API exists.
- We wire evals from day one against the clinic’s own historical reports, scored on whether the assembled measures and dates matched what the therapist actually reported, and every correction becomes a test case.
How it works
The practice management system stays the source of truth. Outcome measures are captured in structure at each visit rather than in prose. As visits accumulate, the trend assembles itself and a completeness check runs against what the specific authorization requires, flagging anything missing while it can still be collected. At report time the therapist reads an assembled picture, writes the interpretation and the recommendation, and submits. Nothing reaches an insurer without that review.
Because notes, measures and reports stay in Canadian infrastructure and processing runs with zero data retention, the design lines up with what PHIPA expects: a completed privacy impact assessment before deployment, an agreement naming the processor as an agent under section 17, and an audit log on every access to personal health information.
Why this pays back
The return lands on the clinician’s evening rather than on the front desk, which makes it a retention argument as much as an efficiency one. Break-even for the first slice is about thirty progress reports a month at a typical loaded clinical hourly cost, and the clinic should substitute its own number.
The limit worth stating before anyone signs: a clinic that does not currently record outcome measures consistently will spend the first slice changing clinical habits, not saving time, and will see the payback in the second block of visits rather than the first. That is a real cost paid by therapists in their treatment hour, and a clinic unwilling to change how measures are captured should not buy this. It cannot assemble a trend from notes that never held one.
The outcomes
Visits a single progress report compresses
12 notes, read again by hand One assembled trend, reviewed
12 to 11
Design targetRemaining savings from automating manual and partially manual administrative transactions
$21B2
Industry benchmarkBreak-even, in progress reports per month
About 303
Design targetReports late or missing a required outcome measure
Discovered at submission Flagged at visit 8
Caught 4 visits earlier4
Design targetTime to the first shippable slice
4-6 wk5
Design target1 Design target measured against the recreated legacy reporting flow shown in the before/after above, using a typical twelve-visit extended health authorization block.
2 CAQH Index 2025, published February 2026, built on data from more than 600 provider organizations and health plans representing 63% of insured lives. US medical data, quoted to size the category of provider-to-payer administrative work. There is no equivalent published index for Canadian physiotherapy, and this study does not invent one.
3 Design-target arithmetic, not a measured result. The first slice is a fixed fee; break-even is stated as the number of progress reports per month whose preparation time would cover it at the clinic's own loaded clinical hourly cost, which the clinic supplies.
4 Design target for the completeness check described in the how-it-works section: the required-fields gate runs continuously against the authorization, not once at report time.
5 Standard first-slice scope: one insurer template, one metric, evals and an approval gate included.
Frequently asked questions
Does this write the clinical reasoning for the report?
No. It assembles the trend: which outcome measures were recorded, on what dates, in which direction they moved, what treatment was delivered and what the authorization allows. The interpretation, whether the patient is progressing, whether more visits are warranted, whether function has returned enough to discharge, is written by the therapist. An insurer report is a clinical argument, and the person making it has to be the person who treated the patient.
What happens when outcome measures were never recorded properly?
It surfaces that instead of papering over it, which is uncomfortable and is the point. If the required measure was recorded once at intake and never again, the report cannot show a trend and the system says so rather than generating a plausible-sounding narrative around the gap. The completeness check runs continuously against the authorization, so a missing measure is flagged around visit eight, when it can still be collected, rather than at submission.
Every insurer wants a different template. Does that break it?
It is why the first slice is one insurer rather than all of them. The underlying clinical facts are the same; the templates differ in field names, ordering and which measures they accept. Each template becomes a mapping from the clinical record, so adding the next is hours of mapping rather than a rebuild, and templates nobody has mapped yet are still done the old way.
Does patient information leave the clinic?
No. Visit notes, measures and reports stay in Canadian infrastructure, the system reads the practice management system through the same permissions the therapist already has, processing runs with zero data retention, and nothing trains anyone's model. A privacy impact assessment is completed before deployment, and the agreement names the processor as an agent under section 17 of PHIPA.
What would this cost to try?
A fixed-fee first slice on the clinic's highest-volume insurer, which for most Ontario clinics is either WSIB or one extended health carrier. It ships in four to six weeks with its own metric, and break-even is stated in reports per month rather than in licences.
Go deeper on the method
Turn Your Clinic's Documents Into an Answer Engine
Stop searching, start asking. How a grounded assistant reads your own protocols, letters and policies and answers in plain language with the source attached, instead of handing your staff a folder to scroll through between patients.
Read articleHow Do You Know Your AI Works? A Plain Guide to Evals
A scribe that demos beautifully can still be wrong in ways nobody sees until it is in a chart. Evals are how a practice measures whether a tool actually works, before it goes live and every month after. A non-technical guide to doing it honestly.
Read articleMore transformations
Down the Hall, Never Booked: The Internal Referral Nobody in the Clinic Owns
A multidisciplinary clinic's cheapest appointment is the one a practitioner refers to a colleague thirty feet away, and it is the one most likely to evaporate. This is the transformation that catches the referral where it is made, carries only what the patient agreed to let travel, and escalates the ones that go quiet.
Untracked to 5 days
The Refill Line: Turning the Pharmacy's Loudest Conversation Into Something You Can Work in Batches
A community pharmacy answers the same question forty times a day, one interruption at a time, in the middle of dispensing. This is the transformation that lets the request arrive as structured intake instead of a phone call, keeps a pharmacist signing every fill, and measures the change at the counter rather than in a dashboard.
21.7%
Ontario pharmacy professionals naming workload as their top driver of burnout
Get the next transformation in your inbox.
When there is something worth your time, you will be first to know. No spam, unsubscribe anytime.