Case studies
How clinics run on AI
What changes when the agents are staff, not features. What we built, what we measured, and what broke on the way.
Why we are the only EHR with MCPAn MCP server is not a feature you add to a record. It is a test of how the record was built: what it takes to pass, what it unlocks, and why the incumbents will find it hard.SPSpriggan teamRead
Why we built an EHR from the ground up for AIEvery EHR now has an AI button. Almost none were built so that AI could do the work. What changes when the agents are staff, not features.SPSpriggan teamRead What happens to a fax at 9:41 AMA three-page MRI report lands in a primary care clinic. Follow it from the machine to the chart, to the physician’s phone, and back out again.SPSpriggan teamRead One shared context: why every agent reads the same chartThe receptionist knows what the scribe heard. Billing knows what prior auth won. That only works if every agent works from one memory, not eight.SPSpriggan teamRead The front desk after the phone stops ringingWhat a receptionist actually does when the AI takes the calls, the reminders and the check-in. Less than you would fear, and more than you would guess.SPSpriggan teamRead MCP for clinics: bring the AI you already useSpriggan exposes every agent, record and workflow through an MCP server, so ChatGPT and Claude can run the clinic too. What that means and why we did it.SPSpriggan teamRead