Case study · Medical · Diagnosis phase
The systems were fine. Everything between them was being done by hand.
A specialist physician practice with eighteen years of accumulated case records, a capable EHR, and a team that was still retyping the same information into three places. The practice is not named here.
What stage this is at
This is a write-up of the diagnosis, not of a finished build. The audit was delivered and the phased plan is with the practice; the build is gated on their go-ahead and has not begun. It is published because the diagnosis is the part most people have never seen, and it is exactly what the Workflow Audit produces. There are no outcome numbers on this page because there are no outcomes yet.
What the audit found
The practice was not disorganised, which is the usual assumption and the usual mistake. The EHR handled scheduling, records and reporting well. The billing software was genuinely good. The case log carried eighteen years of hard-won structure. The cost was in the gaps between those systems, where a person was doing the joining.
Referrals logged and chased from memory
Every referral entered by hand, one at a time, and followed up when somebody remembered. No single list of what was outstanding, so the chase depended on whoever was paying attention that week.
Email as the coordination layer
Messages scattered across departments, so the workaround had become copying everyone on everything. Things still slipped. The clearest example was a week lost because the one person who needed to see a message was the one person not copied.
No single at-a-glance view
Status lived in people’s heads and in a spreadsheet that had to be re-typed from what the EHR already knew. The same fact was being entered two and three times.
Reporting quietly wrong
The same physician’s name spelled four different ways across records, so any report grouping by provider was subtly incorrect. Nobody had noticed because the numbers looked plausible.
The last one is worth dwelling on. A data hygiene problem that nobody can see is more dangerous than a workflow problem everybody complains about, because decisions get made on the bad numbers with full confidence.
What was safe to automate, and what was not
Safe, and worth doing first
- +Routing incoming email to the right person automatically, so nothing depends on remembering to copy someone
- +Logging a referral in one action instead of by hand
- +Generating the weekly list of what is outstanding and who to chase
- +Producing a summary for a scheduled review, from records that already exist
- +Normalising provider names so reporting stops being wrong
Off the table entirely
- −Anything patient-facing. No AI talking to patients, in any channel
- −Anything clinical. No triage, no prioritisation by medical urgency, no interpretation of records
- −Any decision a clinician is professionally accountable for
- −Moving patient information anywhere it was not already held
The dividing line was simple enough to state in one sentence to the practice: the AI works in the back office only, sorting and summarising and reminding. Never patients, never clinical decisions. A boundary a physician can repeat from memory is a boundary that survives contact with a busy week.
The finding that changed the plan
They could build the first phase without signing anything new.
The default assumption going into a project like this is that new capability means new vendors, new agreements, and a legal review that adds months. Checking rather than assuming turned up something better: the practice had held a suitable agreement with their existing platform provider since 2018, and the entire first phase could be built inside it.
That single finding reshaped the sequencing. The work that required no new paperwork, no new system for staff to learn, and no patient data moving anywhere new became phase one. The work that would require a separate agreement, covering the more advanced querying, was pushed to a later phase to be scoped only once the earlier work had proved itself.
This is the sort of thing an audit is for. It is not a technical insight and it is not clever. It is just the result of reading the existing agreements before designing the system rather than after, and it removed the slowest step from the project.
The plan that came out of it
Three phases, each one gated on the last having earned its place. The practice can stop after any of them and still be better off than before.
A single team inbox that routes messages to the right person automatically, plus a referral tracker with one-action logging and a weekly chase list. Ends the manual logging and the missed hand-offs. Built entirely inside what the practice already runs and already has covered.
The spreadsheet view rebuilt as a proper app, organised by referrer and by status, with one-click summaries for scheduled reviews and a scorecard showing which referral sources actually send work. Provider names locked to a fixed list so reporting is finally trustworthy.
Plain-English querying across cases, and a link to the EHR so an update in one place appears in the other and the duplicate entry ends. Scoped last deliberately: what is possible depends entirely on what the vendor opens up, and that gets confirmed before anything is promised.
What this shows about the diagnosis phase
The answer is usually smaller than the pitch
Nothing in phase one is technically impressive. A routing inbox and a tracker are not the future of medicine. They are what would actually give this practice its week back, and an audit that recommended something grander would have been serving me rather than them.
Read the agreements before designing the system
The most valuable finding was that they could build inside what they already had. That came from reading paperwork, not from technical work, and it removed months from the timeline.
Name what you will not automate, early and plainly
Stating the boundary in one memorable sentence did more for confidence than any capability demonstration. In regulated work, the limits are the product.
Find the errors nobody is complaining about
The provider-name inconsistency was not on anyone’s list of problems. It was quietly corrupting every report. Those are the findings worth paying for, because by definition nobody was going to ask for them.
This is what the audit produces.
A map of where the manual work is, a clear line around what should stay human, a compliance answer, and a phased plan you can stop after at any point.
Questions people ask
Is this a finished project?
No. This is the diagnosis. The audit was delivered and the phased plan is with the practice, but the build is gated on their go-ahead and has not begun. It is published because the diagnosis is the part most people have never seen, and it is exactly what the Workflow Audit produces.
Why are there no outcome numbers?
Because nothing has been built yet, so there are no outcomes to report. A page claiming results at this stage would be describing a projection.
What was ruled out, and why?
Anything patient-facing, anything clinical, any decision a clinician is professionally accountable for, and moving patient information anywhere it was not already held. Those were off the table from the start rather than negotiated away later, because automating a clinical judgment is not a feature, it is a liability.
Did the practice have to buy new software?
No, and that was the most useful finding in the audit. The assumption going in was that new capability means new vendors, new agreements, and a legal review that adds months. Checking rather than assuming turned up a suitable agreement the practice had already held with its existing platform provider since 2018, and the entire first phase could be built inside it.
What does an audit like this cost?
The Workflow Audit is $2,500 and takes about two weeks. If you go on to a build within ninety days, the full fee comes off the build price.