The demo shows you an EHR. The build is everything an EHR leaves out.
Healthie describes itself in one line: "the leading headless EMR in digital health". That is accurate, and it is the opposite shape from MD Integrations, which powers the medicine and hands you the brand. Healthie powers the record and the back office and hands you the medicine.
For a clinic that already has clinicians, that is the right trade. For a brand that wants to launch a GLP-1 program and assumed the platform came with doctors and a pharmacy, it is the whole build.
Every claim below is read out of Healthie's own documentation and linked so you can check it. Nothing here is medical or legal advice.
What does Healthie own?
A lot.
The chart and the back office. Scheduling, intake forms and flows, charting, care plans, programs, a client portal on web and mobile, secure messaging and reporting. The EHR is ONC certified, and Healthie states that it is HIPAA, SOC 2, PIPEDA, GDPR and PCI compliant and will sign a BAA.
Video. Built-in one to one video on every plan. Group calls and recording go through Zoom for Healthcare, from the Plus plan up, with no Zoom account of your own.
Payments and packages. One-off and recurring packages charged to a card on file, with promo codes, a different first payment and billing cycles from weekly to yearly. Processing is Stripe, inside Healthie, on every plan.
The API. The same GraphQL API Healthie's own developers use, with webhooks, a sandbox and React SDKs, versioned by date.
What stays yours?
Find every sentence in the documentation that offers you a choice, or names a thing the platform does not do, because that is a thing you now own. Healthie has five that decide a telehealth build.
The clinicians. Healthie does not supply prescribers, and nothing on its pages claims to. The E-Rx application wants each prescriber's legal name, date of birth and NPI, and the NPI "must be for the individual, not an organizational/type 2 NPI". The onboarding guide describes a matching engine you build through the API "with your clinician network based on factors like State Licensure, Tags, and more". The medical entity they work under is the corporate practice of medicine question, and it is not on any Healthie page.
The pharmacy. E-prescribing is an add-on through DoseSpot on the Plus, Group and Enterprise plans, after a credential review that "typically takes 7-14 business days". A prescription goes to a Preferred Pharmacy the prescriber selects, and Healthie's visibility ends at a status line: "Pharmacy Verified: confirms that the pharmacy has received and reviewed the prescription order." There is no fulfilment network, no shipment tracking and no cold chain. Compounds can be prescribed. A missing ingredient can be entered as a free-text ingredient if it is not a controlled substance, and if you want it added to the database, "the approval to add a medication comes from Lexicomp directly and the turnaround time can vary", and "Neither Healthie nor Dosespot are able to speed up this process". Compounded drugs are not FDA approved, and the pharmacy that makes and ships them is a relationship you bring. Physical products in a package are the same: you "are still responsible for 'giving' the product (virtual or physical) to your client, as there is no associated drop-shipping or delivery of products at this time".
The payment relationship, a fork with one open path. "Pre-existing or personal Stripe accounts cannot be connected to Healthie." Of the account Healthie creates for you: "It is not possible to directly sign into the Stripe dashboard for your account." The alternative is in the same FAQ: "You can take payments outside of Healthie (using any payment processor) and then send in those payment records to Healthie if leveraging our API." So the real choice is Healthie's rails or your own checkout plus the API. On Healthie's rails there is no ACH and no purchase inside the mobile app. On your own rails you own underwriting, chargebacks, every subscription disclosure at checkout, and the integration.
The cancel button. That sentence is from Healthie's card payments FAQ, and the next one gives the reason: it "allows you to be fully aware of clients who wish to cancel services and to enforce any cancellation policies you have in place". For a dietitian's monthly package that is a feature. For a recurring program sold online to consumers it is a build item, because California's automatic renewal law requires that a customer who accepted an offer online can terminate it "exclusively online", and other jurisdictions have their own versions. Whether a staff-handled cancellation satisfies the law for your offer is a question for counsel. What is certain is that the self-serve path does not exist inside a Healthie package, so it is built outside it, on a subscription flow that already answers click-to-cancel, and it is yours.
Where intake sits, and what it can refuse. Intake flows "are automatically sent to your clients when they are added to your Healthie provider portal", and a package purchase is one of the doors a client comes in through, so the order of intake and payment is yours to set. Two capabilities decide whether that intake can stop anyone: conditional form questions and auto-scored forms are marked unavailable on the Group plan in Healthie's own comparison table and available on Enterprise. A GLP-1 intake that has to stop on a contraindication needs that logic, so on a Group plan it lives on your side of the API.
Who owns the integration after it goes live?
You do, and Healthie is unusually plain about the terms. Buying the API gets "5 hours of technical support each month with a dedicated Solutions Engineer", and to the question of developer forums or community resources the published answer is no. Real patient data "is not allowed in any form" in the sandbox, and "there is no mechanism to push data, configurations, or code directly from Staging into Production".
The part that is better than most: breaking changes only reach you when you change a request header. Thirteen breaking-change versions have shipped since the June 2024 baseline, the latest dated October 1, 2026, and a request with no version header still gets the baseline. The cost is on the same page of their docs: "Customers that request the latest version will need to update their API clients as we release new versions." An integration is a thing you staff. Here, at least, you choose the week.
Does their compliance cover you?
Healthie's HIPAA, SOC 2 and ONC statements are statements about Healthie. The word LegitScript does not appear on any of the Healthie pages cited below, and certification is granted to an applicant for the websites it controls, so your storefront is its own application, with its own checklist. Controlled substances are an Enterprise add-on to the E-Rx add-on, and what telehealth can prescribe after December 31, 2026 is not a Healthie question either.
Where do their own pages disagree?
Which plan gets the API. The marketing FAQ says Healthie makes its API available "to customers on our Enterprise plan". The help center says "Our API is an available add-on for members on our Enterprise and Group Plans", and the plan comparison lists it at additional cost on both.
How long E-Rx approval takes. The getting started article says DoseSpot review "typically takes 7-14 business days". The EPCS article says it "typically takes 24-48 hours", followed by identity proofing that "may take an additional 5+ business days". The product page says "Setup takes up to 2 weeks." Plan for the longest.
Whether patients get a receipt on each renewal. The subscription services article says the client receives "a confirmation email/receipt of their purchase after every transaction". The packages article, updated three years later, says the client receives "a receipt only after the initial transaction, and will not receive receipts for recurring charges". Test against the newer page.
Whether it is all in one. The FAQ says Healthie is "truly all-in-one" and that "no 3rd party accounts and logins are required". Prescribing opens the DoseSpot platform, group video is Zoom, and the white-label guide warns that third-party tools shown inside the platform, "such as e-prescribing tools", "may retain their own branding".
The version that counts is the one in your contract.
What to settle before you sign
- Whose checkout: Healthie's Stripe, with no dashboard and no self-serve cancel, or your own, with the API work that implies.
- Which plan, read off the comparison table rather than the FAQ: API access, conditional intake and EPCS each move the answer.
- Who the prescribers are, which states they hold, and who owns the matching logic.
- Which pharmacy, named, how it receives the prescription, and who sees the shipment.
- Who on your side owns the API version header, and when it moves.
Every one of those is something Healthie hands back to you. It is a strong record and a strong back office, honest about where it stops. The build is everything on the other side of that line.
If you want that seam mapped against your program before you commit, that is what a telehealth program fit review is for, and it is the same work behind our telehealth and GLP-1 website builds.
Common questions
Does Healthie provide clinicians or a physician network?
No. Healthie is an EHR and practice management platform, and nothing in its documentation offers prescribers. Its E-Rx application asks for each prescriber's own legal name, date of birth and NPI, and states that the NPI must be for the individual, not an organizational or type 2 NPI. Its onboarding guide describes a provider matching engine that you build through the API against your own clinician network, using state licensure and tags. The clinicians, their licence map and the medical entity they work under are all yours to arrange.
Does Healthie handle pharmacy fulfilment for a GLP-1 program?
No. Healthie's e-prescribing is an add-on through DoseSpot, available on the Plus, Group and Enterprise plans after a credential review. A prescription is sent to a preferred pharmacy the prescriber selects, and Healthie's visibility ends at a status such as 'Pharmacy Verified', which its documentation defines as the pharmacy having received and reviewed the order. There is no fulfilment network, shipment tracking or cold chain in the platform, and for physical products sold in a package Healthie states that you are still responsible for giving the product to the client because there is no drop-shipping or delivery of products at this time. Compounded drugs are not FDA approved, and the pharmacy that makes and ships them is a relationship you bring.
Can I use my own Stripe account with Healthie?
No. Healthie's card payments FAQ states that pre-existing or personal Stripe accounts cannot be connected, and that the Stripe account Healthie creates for you is only accessible through Healthie, with no direct sign in to the Stripe dashboard. The documented alternative is to take payments outside Healthie with any processor and send the payment records into Healthie through the API. That is the real fork: Healthie's rails, which have no ACH and no in-app purchase on mobile, or your own checkout plus integration work.
Can patients cancel a Healthie subscription package themselves?
Not inside Healthie. The card payments FAQ states that clients are not able to cancel a package they have purchased on their own, that they will need to contact you, and that this lets the business enforce its cancellation policies. For a recurring program sold online to consumers that is a build item rather than a feature, because California's automatic renewal law requires that a customer who accepted an offer online can terminate it online, and other jurisdictions have their own versions. Whether a staff-handled cancellation satisfies the law for your offer is a question for counsel. The self-serve path itself has to be built outside the package, or on your own checkout.
Does Healthie's API come with the Group plan or only Enterprise?
Healthie's own pages differ. The marketing FAQ says the API is made available to customers on the Enterprise plan. The help center says the API is an available add-on for members on the Enterprise and Group plans, and the Group versus Enterprise comparison lists API access at additional cost on both. Treat the help center and the comparison table as the operative answer, and get the plan and the add-on named in the contract rather than inferred from the FAQ.
If Healthie is HIPAA and SOC 2 compliant, is my telehealth storefront covered?
Only for what Healthie does. Healthie states it is HIPAA, SOC 2, PIPEDA, GDPR and PCI compliant, that its EHR is ONC certified and that it will sign a BAA. Those are statements about Healthie's platform. Your storefront, your advertising, your intake placement and any LegitScript certification are your own obligations, and the word LegitScript does not appear on any of the Healthie pages cited in this post. Healthie's audits answer questions about Healthie. Yours still get asked.
Sources
- Healthie FAQ, describing Healthie as the leading headless EMR, the all-in-one claim and the Enterprise plan API answer checked 2026-10-17
- Healthie, Building with Healthie, on the API, compliance statements, the BAA and ONC certification checked 2026-10-17
- Healthie, E-Prescribe product page, including the EPCS setup time and the plans the add-on is available on checked 2026-10-17
- Healthie pricing page, with the feature matrix and the integrations and add-ons list checked 2026-10-17
- Healthie help center, Healthie's API and SDKs, on plan availability, the sandbox, support hours and developer resources checked 2026-10-17
- Healthie help center, Group Plan versus Enterprise Plan, the feature comparison table checked 2026-10-17
- Healthie help center, Getting Started with E-Rx, on the DoseSpot application, approval time, the individual NPI and the preferred pharmacy checked 2026-10-17
- Healthie help center, Prescribing a Compounding Medication, on free-text compounds and Lexicomp approval checked 2026-10-17
- Healthie help center, Controlled Substances EPCS, on the Enterprise add-on, Experian identity proofing and two-factor sign off checked 2026-10-17
- Healthie help center, Stripe and Healthie, on the Healthie-created Stripe account and dashboard access checked 2026-10-17
- Healthie help center, FAQs on Card Payments, on connecting your own Stripe, outside payments through the API, package cancellation, ACH and mobile purchases checked 2026-10-17
- Healthie help center, Getting Started with Client Packages, on billing cycles, receipts on recurring charges and product delivery checked 2026-10-17
- Healthie help center, Subscription Services Within Healthie, on receipts after every transaction checked 2026-10-17
- Healthie help center, Working With Clients Asynchronously, on the sign-up doors including package purchase checked 2026-10-17
- Healthie help center, Getting Started with Intake Flows, on when intake flows are sent checked 2026-10-17
- Healthie help center, Create a custom onboarding flow with provider matchmaking, on building a matching engine against your own clinician network checked 2026-10-17
- Healthie help center, Full Web White-Label, including the note on third-party branding inside the platform checked 2026-10-17
- Healthie help center, Staging vs Production, on the absence of any push from sandbox to production checked 2026-10-17
- Healthie help center, Getting Started with Video Calls, on built-in one to one video, Zoom from the Plus plan and recording checked 2026-10-17
- Healthie API documentation, Versioning, the version history and the baseline header behaviour checked 2026-10-17
- Healthie, Platform Overview, stating the EHR is ONC certified checked 2026-10-17
- California Business and Professions Code 17602, termination of an online automatic renewal exclusively online checked 2026-10-12
Want this costed for your build?
Tell us what you already have and what is not working, and we will come back with the shape of the work and what drives the number.