Customer Success Story
Published September 28, 2026 · Updated September 28, 2026
Opt Health Builds a Fully White-Label Care Experience on Healthie
Opt Health is a longevity medicine startup clinic that built a fully white-labeled care experience on Healthie's API-first infrastructure, syncing data in real time between its own front end and Healthie as the clinical system of record underneath. With scheduling, eRx, charting, and intake forms handled through Healthie, Opt went live in 5 weeks and saved an estimated $100K–$250K annually in development costs.
$100K–$250K
Annual development cost savings
Engineering shifted from EHR maintenance to product development.
5 Weeks
Time to go live
From onboarding to live deployment on Healthie
At a Glance
As Opt Health scaled, they outgrew a legacy EHR with an outdated API and found themselves stitching together third-party tools and in-house builds just to keep core clinical workflows running. Switching to Healthie as its clinical system of record, Opt built a fully white-labeled front end on Healthie's GraphQL API, syncing scheduling, eRx, charting, and intake forms in real time. The result: a 5-week go-live, an estimated $100K–$250K in annual savings, and an engineering team that now builds on Healthie's foundation rather than maintaining it. With that foundation in place, they experience faster deployment of new capabilities and limitless scalability.
“Speed of development is the biggest ROI. Our engineering team can focus on innovation instead of building and maintaining foundational EHR features.”
The Challenge
Why does pediatric behavioral health need different tooling?
As Opt Health scaled, managing provider schedules, availability, and patient workflows became increasingly difficult. The team was on DrChrono, a legacy EHR whose outdated API made integrations cumbersome and slowed development to a crawl. Every new feature came with the decision to stitch together another third-party tool, or build it in-house.
Neither answer was good. Stitching tools together created fragility. Building in-house meant engineering hours poured into scheduling, charting, and intake forms, and other foundational infrastructure that wasn't advancing Opt's differentiated value.
“We really needed an EHR that could handle back-office admin and was developer-first, with robust documentation. ”
Inside the build
How Opt built its entire care experience on top of Healthie
When Opt moved to Healthie, the goal wasn't to use Healthie's interface, but to build entirely on top of it. Patients and providers interact exclusively with Opt's own front end. Healthie runs underneath as the clinical system of record, never surfaced directly to end users.
The foundation that made that possible is Healthie's extensively documented GraphQL API, which gave Opt's engineers full access to the same API Healthie uses to build its own product. From there, Opt built the integration layer that keeps the two systems in sync, pushing scheduling, eRx, charting, and intake form data back and forth in real time. "We're constantly pushing data back and forth between our platform and Healthie," said Getz.
Three capabilities do Opt’s heavy lifting:
- Healthie's GraphQL API: Full, backward-compatible access with extensive documentation and direct engineering support.
- White-label deployment: Every patient and provider screen is Opt's own, built directly on the API, with Healthie running as the compliant system of record underneath.
- Real-time data sync: Scheduling, eRx, charting, and intake form data flows continuously between Opt's front end and Healthie.
“Speed of development is the biggest ROI. Our engineering team can focus on innovation instead of building and maintaining foundational EHR features.”
BUILT ON HEALTHIE
What did they build on Healthie?
The specific Healthie capabilities behind that build, grouped by type:
Extensions
0
Healthie API
Gives developers full, backward-compatible access to Healthie's GraphQL API — the same API Healthie's own team uses to build its web and mobile apps.
Configurations
0
Full Web White-Label
Turns Healthie into a fully custom-branded platform on your own domain — no Healthie name or branding anywhere in the provider or client experience.
Integrations
0
E-Rx
Sends electronic prescriptions to any pharmacy directly from a client's profile, with Healthie managing the DoseSpot connection so no separate vendor account is required.
Results
What changed when Opt built on Healthie?
Engineering redirected from maintenance to differentiation
With core clinical infrastructure handled by Healthie, Opt's engineers stopped maintaining EHR plumbing and started building the product capabilities that set Opt apart.
$100K–$250K in estimated annual development cost savings
By adopting Healthie scheduling, charting, forms, and eRx, Opt avoided the in-house build and maintenance costs that would have otherwise consumed significant engineering budget.
Live in 5 weeks
Healthie's documentation, API design, and hands-on support from the Healthie engineering team allowed Opt to onboard and deploy quickly, without a long implementation runway.
A platform to keep building on
Opt plans to deepen its Healthie footprint with Programs for structured patient engagement, Chat to replace its current Zendesk workflow, and expanded scheduling configurations as the practice grows.