Healthie AI: What AI Scribe Does and What the API Costs
If you searched “Healthie AI,” you are probably deciding whether the AI Scribe add-on is worth another line on an already uncomfortable software bill. Healthie has shipped real AI, and unusually for vertical health software, the flagship feature is genuinely good at the thing that eats your evenings: charting.
What follows is what each piece does, where it stops, and what you can wire around it — written for a solo dietitian or a small virtual-health practice, not a digital health startup with engineers.
AI Scribe is the real product; the rest is a roadmap
Healthie brands its AI work Intelligence by Healthie, described as “a suite of purpose built AI driven tools for providers, administrators and developers, designed native to Healthie.” Treat the suite as one shipped feature and a list of intentions.
AI Scribe is the shipped one, and it is the reason this search term exists. It captures the session — in person via your device microphone, over the phone, or through Healthie’s Zoom telehealth integration — and returns a structured, editable chart note plus a full transcript. Healthie says the note lands within 10 to 15 seconds of the session ending. Critically for this audience, it follows your template: “Whether you use SOAP notes, ADIME, or a fully custom template, AI Scribe will follow the structure of the template and capture relevant details.” ADIME support is the tell that this was built for dietitians rather than retrofitted from a generic medical scribe. Healthie announced it at FNCE 2025 and has expanded it since.
You review, edit, and sign. It does not sign for you, which is correct.
Medical record summaries condense “large volumes of patient data into actionable insights” — useful when a new client arrives with 40 pages of prior records.
Patient messaging assistance suggests replies to incoming client messages.
Healthie Dev Assist is an AI tool for developers exploring the API. More on why that matters, and why it probably isn’t for you, below.
The remaining items Healthie lists — workflow automation “through natural language commands” and intelligent task management — read as roadmap language rather than features you can switch on today. Don’t buy a plan for them.
AI Scribe’s privacy answers are better than most
This audience has to ask, and Healthie’s answers are unusually specific, so they’re worth repeating precisely rather than paraphrasing into mush.
Raw audio is not kept: “Raw audio is not stored by Healthie. Only the generated transcript is retained — audio is processed and discarded.” Transcripts are retained for two years. And on the question everyone actually worries about: “Audio, video, and transcript data from sessions are never used to train AI models — neither Healthie’s own models nor those of any sub-processors.”
Healthie also tells you to get consent, and spells out what that consent should cover: that an AI tool is generating notes, how data is handled, and that session data isn’t used for training. That is your obligation, not Healthie’s — build the language into your intake paperwork before you turn Scribe on, not after.
AI Scribe is available on Plus plans and above as a paid subscription add-on. It is not included in your base seat.
The API is the part that will stop you
This is the section most articles about Healthie get wrong, and it’s the one that decides whether any of the automation below is available to you at all.
Healthie has an excellent, genuinely public GraphQL API documented at docs.gethealthie.com. The docs are thorough, there’s a sandbox, there’s an API Explorer, and there are community SDKs. Everything about the developer experience is above average for vertical health software.
The catch is commercial, not technical. Per Healthie’s own support documentation: “Our API is an available add-on for members on our Group and Enterprise Plans.” It is a paid add-on on top of a plan that already costs more than the solo tiers.
That matters because of where Healthie’s pricing sits. The Core and Essentials tiers, and the Plus plan at around $129/month — the plan a busy solo dietitian most likely occupies — do not include API access at any price. The Group plan starts around $149.99/month for one standard role, and only from there can you pay extra to add the API. Healthie has opened API and Dev Assist access to Group customers, which is a real loosening, but it is still a plan upgrade plus an add-on fee.
There’s no self-serve key either. Keys come through Healthie: the docs say “Contact us if you do not have one,” and sandbox access runs through hello@gethealthie.com.
So the honest verdict: Healthie’s API is excellent and you probably can’t reach it. If you’re a solo practitioner on Plus, the path to automation is a plan upgrade and an add-on conversation with sales, not an afternoon with an API key. Price that against what you’d actually automate before you upgrade — and read the section below on what works without it, because for most solo practices that’s the whole answer.
If you are on Group or Enterprise and do have the API add-on, you’ll be issued a key, and you paste it into Carly at carlyassistant.com/integrations as a bring-your-own-key connection. Carly doesn’t ship Healthie as a prebuilt connector; BYO-key is the supported route.
No, ChatGPT and Claude do not connect to Healthie
There is no native ChatGPT connector and no Claude connector for Healthie. Neither vendor lists one, and an EHR carrying PHI is close to the last category either would ship into a consumer connector directory.
There is one genuine near-miss worth naming honestly, because you may find it and misread it. Healthie Dev Assist is a real MCP server, published by Healthie, and it does work with Claude Desktop and Cursor. But it is a developer tool for exploring and querying the API — its own description is “AI-powered Healthie API exploration.” It runs locally, it requires an API key to touch real data, and that key requires the plan gate above. It is not a way for a dietitian to ask Claude about tomorrow’s clients.
There is no such thing as an MCP trigger. The protocol's own working group states plainly that clients find out about server-side changes by polling for them, and a real event mechanism remains unshipped.
The same limit applies to the assistants themselves, not just to MCP.
Scheduled work is available in ChatGPT and Claude Cowork, but their ordinary schedulers are clock-driven rather than generic listeners for changes in connected business apps. ChatGPT Workspace Agents add API-triggered runs, with another system responsible for detecting the event and making the call.
For a virtual practice, that limit bites in a specific place. “Every morning at 7, tell me who’s on today and who hasn’t returned their intake form” is achievable. “The moment a client no-shows, start the rebooking sequence” is not — unless you’re on the webhook path.
Healthie’s webhooks are the best thing in the API
If you do clear the plan gate, the webhooks are what you’re really buying, and they’re strong. Healthie’s event reference covers appointments (appointment.created, appointment.updated, appointment.deleted), forms (form_answer_group.created, form_answer_group.signed, requested_form_completion.created), messages (message.created), clients (patient.created, patient.updated), care plans, lab orders, and billing events including billing_item.created and claim_submission.created.
That is an event trigger — the capability ChatGPT’s scheduled tasks and Claude’s scheduled work both lack. Something changes in the chart, Healthie fires, and a workflow runs in the same minute instead of at tomorrow’s sweep.
Concretely: a requested_form_completion.created event fires when you send intake, and if no matching form_answer_group.signed arrives within 48 hours, a reminder goes out before the session rather than after you notice mid-appointment that you have nothing to work from. An appointment.deleted event fires on a late cancel and your waitlist gets offered the slot while it’s still fillable. A claim_submission.created event without a follow-up within its expected window surfaces on a list instead of quietly aging. In Carly, that trigger-and-branch scaffolding sits in the free Zapier-style workflow layer; the AI agents that read, draft, and judge start at $35/month.
Route PHI deliberately, though. A webhook payload identifying a client is PHI the moment it leaves Healthie, so anything downstream needs a BAA and needs to be somewhere you’re willing to defend in an audit. The safest pattern is to let the event carry only the resource ID and the event type — which is roughly what Healthie’s payload does — and keep the clinical detail inside Healthie rather than piping it into a general-purpose AI tool.
Your calendar is publishing client names
Healthie appointments frequently end up mirrored onto a Google or Outlook calendar so you can see work and life in one place. That convenience quietly carries client names and appointment types onto a calendar that may be shared with a partner, a virtual assistant, a biller, or a spouse.
For a dietitian that might be tolerable. For anyone working eating-disorder cases, bariatric follow-up, or fertility nutrition, a shared calendar reading “Intake — [name]” is a disclosure, and free/busy permissions apply to the whole calendar rather than the sensitive entries.
Carly’s Calendar Sync sits between calendars and rewrites entries as they cross: titles become “Busy” and attendees are stripped, so the shared view shows accurate blocked time and nothing else. Your own calendar keeps the real detail. The calendar-as-source-of-truth piece for healthcare goes further into how to structure this.
What a solo practice can automate today
None of this needs Healthie API access, which for most readers is the entire point:
- Morning brief from your calendar — today’s sessions, new clients, and gaps — pushed before you open the laptop.
- Inbox triage on the address Healthie confirmations, cancellations, and form notifications land in, so client replies surface and receipts don’t.
- Superbill and invoice follow-ups driven off dates rather than off remembering.
- Referral-source follow-up from your own list, drafted and queued rather than written between sessions.
- Recurring admin — CEU deadlines, license renewal, credentialing dates — as dated triggers instead of a note on the fridge.
That covers calendar, email, and tasks, which work regardless of what Healthie exposes. The AI tools for dietitians rundown covers the wider stack.
FAQ
What is Healthie AI Scribe? AI Scribe is Healthie’s ambient documentation tool. It captures a session in person, by phone, or through Healthie’s Zoom telehealth integration, and generates a structured, editable chart note plus a transcript within 10 to 15 seconds. It follows your template, including SOAP, ADIME, and custom charting templates built in Healthie.
How much does Healthie AI Scribe cost? It is a paid subscription add-on available on Plus plans and above. It is not included in the base plan price, so budget it separately from your seat.
Does Healthie use my session data to train AI? No. Healthie states that audio, video, and transcript data from sessions are never used to train AI models, including sub-processor models. Raw audio is discarded after processing and only the transcript is kept, for two years. You are still responsible for obtaining client consent to use an AI scribe.
Does Healthie have an API? Yes, a well-documented GraphQL API at docs.gethealthie.com, with webhooks and a sandbox. Access is a paid add-on restricted to Group and Enterprise plans, so Core, Essentials, and Plus subscribers cannot get a key. Keys are issued by Healthie rather than self-serve.
Can ChatGPT or Claude connect to Healthie? No. Neither ships a native Healthie connector. Healthie publishes an MCP server called Dev Assist that works with Claude Desktop and Cursor, but it is a developer tool for API exploration and still requires an API key from a Group or Enterprise plan.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
