AI for healthcare
Patterns, no client yetPractices and clinics where the front desk, the phone, and the documentation load are eating the day.
In a practice, almost nothing that slows the day down is clinical. It is the phone at 4pm, the intake form somebody rekeys, the no-show nobody called, and the documentation that follows a clinician home. Those are administrative patterns, and they are the only ones this page is about.
No client yet
We have not built for a practice
Admin only
Nothing clinical, ever
Start here
A workshop, not a pitch
Where the time goes
We have not built a system inside a practice, so this is a read on the administrative patterns rather than a claim about your clinic. Everything below is front-office work. None of it is clinical.
One person is checking in a patient, and the phone is ringing, and the person on the phone wants to reschedule. Whoever is in front of you loses, or the caller does. There is no version of this staffing problem where somebody is not being underserved.
One desk, two patients, every time
The patient filled it out. Somebody reads it and types it into the system. It is pure transcription, it happens for every patient, and it is the kind of work where accuracy matters and attention runs out by mid-afternoon.
Filled out once, typed again
The reminder went out and it was a generic text nobody read. A real confirmation call would have caught the conflict two days out and moved the slot to somebody on the waitlist. That call takes a person, and the person was on the desk.
An empty slot is a whole appointment
The visit ends and the note is not written. It gets written that evening, from memory, which is worse for the note and worse for the clinician. This is the most discussed administrative problem in the category and it is genuinely a hard one.
The note gets written from memory, at night
It was sent. Whether it was received, scheduled, or seen is somebody's job to chase, and chasing is manual, so it does not happen consistently. The loop stays open and nobody knows which ones did.
The loop closes only if somebody chases
Every idea above touches patient information, so every idea runs into a real question about what is allowed to move where. This is a legitimate reason most practices have not automated anything, and it is not a reason to automate carelessly.
Patient data changes what is allowed
The machine
The administrative machine around the clinical work. We are only describing this outer ring.
01
02
03
04
The split
The line here is not subtle and it does not move: nothing we would build touches clinical judgment. No diagnosis, no triage, no advice about a symptom. If a caller starts describing how they feel, the system's only correct behavior is to stop and hand the call to a person. Everything on this page is front-office administration, and a vendor who blurs that line in a sales conversation is telling you something about how they build.
What we build
01
The scheduling calls answered so the desk can face the person in the room: book, reschedule, cancel, directions, hours. Anything clinical routes to a human immediately and without negotiation.
02
The completed form becomes a structured record rather than a transcription job. The patient filled it out once. Typing it in again is a task, not work.
03
Not a broadcast reminder nobody reads. A confirmation that gets a real answer two days out, so a conflict becomes a reschedule and an open slot instead of an empty room.
04
A slot opens at 9am and it is worth something for about two hours. Working the list against that window is mechanical, time-sensitive, and exactly the kind of thing that does not happen when the desk is busy.
05
The administrative scaffolding of a note drafted for review. The clinician edits and signs. The note is theirs, the judgment is theirs, and it is never anything else.
06
Sent, received, scheduled, seen. The open ones surfaced as a list somebody can work, so closing the loop stops depending on whether anybody remembered to chase it.
Under the hood
Practice management and records
Patient communication
Phones
Your records system is the system of record and nothing about that should change. What we would need to work out first, before anybody commits to anything, is what is allowed to move where. In this category that is the first question and not a footnote, and if the answer is that a workflow cannot be built compliantly, then it cannot be built.
Principles
We ran a live system for a Medicare insurance brokerage, which is an insurance business with a healthcare-shaped vocabulary. It is not a clinic and we are not going to blur the two to look more experienced than we are. That system is described on the insurance page, where it belongs.
No diagnosis, no triage, no symptom advice, not at any confidence level. The systems on this page are front-office administration. This is a design boundary we would put in writing before a build starts, and one that would show up as a test.
What patient information is allowed to move and where is the first question, and it constrains what can be built at all. Any workflow that only works by moving data somewhere it should not go is a workflow we would tell you not to build.
Most administrative pain in a practice comes from one person being asked to serve the patient in front of them and the one on the phone at the same time. The highest-value thing to fix is usually whichever of those two you are currently choosing to underserve.
Same approach, different language
Insurance
Medicare brokers, independent agencies, and the licensed agents who live and die by enrollment windows.
Live system →Professional services
Agencies, consultancies, and expert firms where the product is judgment and the constraint is the founder's calendar.
We speak the language →Legal
Small and mid-sized firms where the partners are the product and the admin load is uncapped.
Patterns, no client yet →Questions
No. We ran a live system for a Medicare insurance brokerage, which is an insurance business, not a clinical one, and we are not going to present it as healthcare experience. If you want to see systems we actually shipped, the construction and insurance pages have them with client names and real numbers attached.
No. Not diagnosis, not triage, not advice about a symptom, at any confidence level. Everything on this page is front-office administration: phones, scheduling, intake transcription, referral tracking, and drafting the administrative parts of documentation for a clinician to sign. If a caller starts describing symptoms, the only correct behavior is to route to a person, and that would be built as a hard rule with a test behind it.
It is the first question rather than a footnote, and it constrains what can be built at all. What patient information is allowed to move, where it is allowed to go, and which vendors are permitted in the path are decisions for your compliance people, not for us. Our honest position is that if a workflow only works by moving data somewhere it should not go, then that workflow does not get built. We are not going to give you a regulatory opinion in a sales conversation.
For scheduling, rescheduling, hours, and directions, which is a large share of the volume and none of it clinical. The value is that the front desk can face the person standing in front of them instead of choosing between two patients every ten minutes. The moment a call becomes clinical, it goes to a person.
Ambient documentation is the most active area in this category and there are specialists doing it well. We would not claim to be one. What we would build is the administrative scaffolding around a note, always drafted for a clinician to review and sign, never as an authority. If documentation is your main problem, a dedicated scribe vendor is probably a better answer than us, and we would tell you that on the call.
A readiness workshop. One session mapping one real workflow end to end, and you leave with the map and a dated plan whether or not you ever build anything with us. In a category where we have no case study and the compliance constraints are real, paying us to guess would be a bad trade for you.
You do, from day one. The code is in your repository, the knowledge base is in your cloud, and the accounts are in your name. In a category where the data is this sensitive, a vendor holding the keys to your systems should be a hard no.
Read next
Explainer
What an AI-legible business actually looks like, the five-point readiness checklist to score your own operation, why one person is usually compensating for every broken handoff, and the 90-day path from messy to legible.
Explainer
What does an AI consultant actually do? A plain-English breakdown of the real work behind operational AI consulting, from diagnosis to system design to ongoing results.
Operations
How to reduce admin overhead without adding staff by redesigning intake, follow-up, and reporting workflows into systems that run without constant manual attention.
Where to start
Find the bottleneck, price the fix, build the system, then keep compounding it. The four engagements are how you buy it, and you can start on any rung.
See the four engagements →Get started
Book a 30 minute call. We find the one place your work waits on you, and you get a straight answer about whether AI is the fix. No pitch, no deck.