Case 06 · Healthcare

Patient intake across three systems that didn't talk. Now it's one clean flow.

A regional clinic group running several sites, each on a different patient-records system inherited from past acquisitions.

Outcome · days, now next-day
  • Patient intake
  • Privacy-led
  • Insurance
  • Always on
Scroll

The issue

Where it hurt.

Front-desk staff at every site were retyping patient details between three records systems by hand, because none of the vendors talked to each other. Insurance approval took about four days on average — long enough that a chunk of booked appointments turned into no-shows, because patients didn't realise their coverage was confirmed. Their medical chief was blunt with us: she didn't want a vendor, she wanted a partner who'd treat patient data the way her staff did. We agreed to a privacy-led discovery before a line of code was written.

Discovery

What five days of looking found.

  1. 01

    Before anything else, every piece of patient data was mapped, along with how it would move — their privacy officer signed off on the flow before we wrote a line.

  2. 02

    Two weeks shadowing the busiest site filled in the picture: every hand-off between systems, every point where data got duplicated or lost.

  3. 03

    Then a run through every insurer — which supported instant approval, which needed someone working a portal, and which still ran on faxed forms. (A few still ran on faxed forms.)

How we worked

Side by side, not over tickets.

  1. 01

    Their privacy officer was in from day one and signed off on anything that touched patient data before it shipped.

  2. 02

    We had weekly sessions with the front-desk leads from each site — they shaped the workflow staff actually use, we handled the wiring underneath.

  3. 03

    The what-to-do-if-something-goes-wrong plan was written together with their compliance team before launch; their auditor later used it as the example for everyone else.

The build

What runs now.

  1. 01

    The system sits between the three records systems and a single patient record. Data moves one direction at a time per step, with every field change logged.

  2. 02

    Insurance approval runs automatically against the insurers that support it. The few fax-only ones get a different path: the form is generated and queued for the front desk to confirm.

  3. 03

    Every read and write is logged, and the review version hides names — an auditor can trace anything without ever seeing a patient.

  4. 04

    Patients confirm their details once, and it routes to the right system for their site and kicks off approval with the right insurer.

Outcome

What it's worth.

days, now next-day
  • Their privacy officer reused the plan we wrote together as the template for the rest of the clinic's vendors.
Saving
No-shows dropped from roughly one in seven to about one in twenty-five. The appointment slots that recovered were worth a solid six figures a year in visits.
Speed
Getting a patient fully through intake went from about a week to next-day. Insurance approval went from around four days to a matter of hours.
Reliability
Duplicated records between systems went from a noticeable share to almost none. No data-handling issues in the last review.

Where it is now

Live across every site, and we're still in it. Early discovery is underway on scheduling a little smarter from the no-show pattern, without hurting the patient experience.

Your next step

Your version of this story.

Thirty-minute call. We'll find three flows worth automating before we hang up. No deck. No "discovery proposal." Just the work.