Healthcare workflow automation
Healthcare automation pays off fastest in the back office: logging referrals, sorting shared inboxes and chasing what is outstanding, so nothing depends on who remembered to copy whom. I build it inside the Google Workspace your practice already owns. It never talks to patients and never makes a clinical decision.
By Jimmy Hackett, founder of Playground Giants · Updated September 27, 2026
Most practices do not need another vendor to stop referrals slipping. They need the mail they already get to land in one log, and a list of what nobody has chased yet.
Copies of mail from your intake and records inboxes land in one account you own. Referrals, records requests and surgery mail are logged as they arrive, one row per email thread.
Once your team writes down who handles what, each kind of message goes to that person automatically, so nothing depends on remembering to copy someone.
Referrals with no appointment get a nudge, and a sender who keeps asking is escalated to a person.
New steps run in shadow mode first, writing to a copy of your log. They act for real only after your team approves them.
Your EHR is usually fine. The cost is in the gaps around it, where a person retypes what the EHR already knows.
Where your EHR vendor offers a standard API such as FHIR, a later phase can read new patients so they appear on the log without being typed twice. It is scoped only after the earlier phases have earned it.
I read your existing agreements before designing anything. Often the first phase fits inside a business associate agreement you already have, which removes the slowest step from the project.
If your site needs rebuilding, new-patient inquiries can land in the same place as your referrals, instead of in another inbox.
The accounts, the log and the scripts are yours. If you replace me, your team keeps operating.
Running today
Phase one has run unattended in the practice's own Google Workspace since September 22, 2026, logging referrals, records requests and surgery mail as they arrive. It uses no AI: plain rules the practice can read, with no calls to any outside service. Phase two, the follow-ups, was installed in shadow mode on September 25, 2026 and writes only to copies of the practice's log until they approve it.
The practice is not named, and there are no outcome numbers yet because nothing has been measured. The case study shows what the audit found and why the work was ordered the way it was.
Read the full case studyWith a two week Workflow Audit. I map how referrals and mail move through your practice today, mark what is safe to automate and what has to stay with a person, check it against the agreements you already hold, and price the build in phases. It is a $2,500 fixed fee, credited in full if you build within ninety days, and the plan is yours either way.
The stages after that are on the packages page.
Taking the repetitive work between your systems off your staff: logging referrals, sorting shared inboxes, chasing what is outstanding, and keeping one list everyone can see. It is back-office work only. It does not talk to patients and it does not make clinical decisions.
Only where it helps, and never for a clinical call. Often the first phase needs none: plain rules the practice can read are enough to stop referrals slipping. Where a later phase adds a model, its only job is to pull facts out of an email, and a person or a written rule decides what happens next.
It is built to work inside the agreements you already hold. Before anything is designed, I read them. Often the first phase can run inside a platform your practice already has a business associate agreement with, such as its Google Workspace, so patient information does not move anywhere new. I sign a business associate agreement with the practice before touching real mail.
No. New steps start in shadow mode: the system writes what it would do into a copy of your log, and your team compares it with what actually happened. It only starts acting for real when you approve it.
Usually not. The system is built on accounts you already own, and the log is a sheet in your own Workspace. If your EHR vendor offers an API, a later phase can read new patients from it so nothing is typed twice. That is scoped once the earlier phases have proved themselves.
Anything patient-facing, anything clinical, any decision a clinician is professionally accountable for, and moving patient information anywhere it was not already held.
Nearly every engagement starts with the Workflow Audit: two weeks, a $2,500 fixed fee, and a written plan that is yours either way. If you go ahead with a build within ninety days, the full fee comes off the build price.
Fifteen minutes is enough for me to tell you whether there is anything worth building. If there is not, I will say so.