Three integration paths. Direct API for partners with their own dev team, integrated
commerce stack via a platform partner for speed to market, or commercial terms for
operators who want to become a platform themselves. Same clinical infrastructure
behind your brand, different scope and timeline depending on the team you have today.
30 minutes with engineering. Sample payloads and timeline by the end of the call.
This page is for technical buyers and established operators. If you're new to telehealth
infrastructure entirely, start here for the
orientation walkthrough. Otherwise, read on. Everything below assumes familiarity with API
integration, EMR workflows, and pharmacy routing.
Where Beluga fits in your stack.
Telehealth is four layers: acquisition and marketing, intake and commerce, clinical care
and pharmacy, support and retention. Beluga owns clinical and pharmacy by default and can
reach into the adjacent layers if it helps. The diagram below shows what Beluga handles
and what your team typically keeps.
What's included at each layer.
Acquisition and marketing.
You own this layer end to end. Brand, paid acquisition, lifecycle marketing, content,
landing pages, and the customer relationship. Beluga is invisible at this layer. We do
not market to your patients, we do not own their email addresses, and we do not insert
ourselves into the channel.
Intake and commerce.
Patient portal, secure messaging, e-commerce, subscription billing, and CRM. You can
build this yourself, plug in a platform partner who has it pre integrated with Beluga,
or run Beluga's hosted intake under your subdomain while keeping your own commerce stack.
Three configurations, all using the same Beluga clinical layer behind them.
Clinical care and pharmacy.
The physician network, the EMR, the clinical workflows, the protocols, the questionnaires,
and the pharmacy rails. Beluga owns this layer end to end. Physicians are credentialed in
all 50 states plus DC. Workflows are designed so the clinical work happens where the evidence
says it should and the operational work runs in the background.
Support and retention.
Your team owns the customer relationship. Beluga provides the partner dashboard, the
pharmacy fulfillment tracking, the compliance flag feed, and a dedicated pod in Slack so
your support team has a direct line into clinical and operations when something stalls.
Three integration paths
Same Beluga clinical infrastructure behind your brand. The difference is who builds the patient facing
layer and how fast you get to production.
Direct API integration
For partners with their own dev team and tech stack. You build the patient portal, e-commerce,
and CRM layer. We provide the clinical API, documentation, and protocols. This is the longer of
our two integration paths, though a motivated dev team moves faster.
Best for: established brands and operators with technical
capacity, and brands switching from another provider who already have working infrastructure.
For partners who want speed to market without building from scratch. We work closely with a
small set of platform companies that provide a white label DTC telehealth stack with patient
portal, secure messaging, e-commerce, EMR, and CRM, pre integrated with Beluga. You handle
marketing and brand. This is the fastest route to launch. Specific platform partners are
introduced on the scoping call once we understand which fit is right.
Best for: first time founders and brands without a dev team.
Become a platform company yourself
For operators who want to build infrastructure that other brands can plug into. We support
that path with the same clinical API and additional commercial terms designed for downstream
resale. Talk to us about volume tiers, white labeling, and partner economics.
Best for: established operators, agencies, and multi brand
holding companies.
Smart pharmacy routing, in detail.
Pharmacy assignment is configured per medication, per partner, and per state. Inside the
clinical workflow engine, each medication has a default routing rule that maps to one or
more pharmacy partners. Partners can override the default at the medication level (route
this Rx to my pharmacy, route that one to yours, route the GLP-1s direct from
manufacturer) and at the state level (use this pharmacy for the states they cover, fall
back to ours for the rest).
When you bring your own pharmacy, the integration runs through Surescripts where the
pharmacy supports it, or through a partner specific API where it does not. Beluga
maintains those integrations so your pharmacy contract stays in your hands. You see the
underlying fulfillment cost in your dashboard, the pharmacy invoices you directly, and
Beluga charges you nothing additional for routing the prescription.
The point is that pharmacy is configuration, not lock in. Most partners start with one
setup and adjust over time as their medication mix changes. None of this requires a
redeployment or a contract renegotiation.
Beluga is credentialed nationally with commercial payers. For brands serving employer
plans, value-based care programs, chronic care management pipelines, or HEDIS gap
closure workflows, this unlocks revenue that compounder-only platforms cannot access.
HEDIS gap closure for Medicare Advantage and commercial plans
Chronic care management (CCM, RPM, PCM) pipelines
Health plans embedding telehealth into member care
Employer benefits platforms billing through commercial coverage
Visit-based fee structures, not PMPM, not capitation
Always-on monitoring of partner site copy for FTC and FDA claims compliance. State
specific rules enforced automatically in the clinical workflow. Compliance posture is
not a checklist. It runs in the background of every visit.
LegitScript certified
HIPAA, FDA, DEA, all 50 states plus DC
Mandatory video visits enforced where required
ISO 27001, SOC 2 posture, insurance carrier enrollment
Always-on monitoring of partner site copy
What you see when you log in.
Every Beluga partner sees the same dashboard our team sees. Live visit queue with status.
Pharmacy fulfillment tracking. Compliance flags and clinical escalations. Real-time API
health. Direct Slack into your pod. No upcharge, no separate SKU. You will know when
something is stuck before we do.
partner.belugahealth.com / dashboard
Company Portal
Live · last sync 14s ago
Avg doctor response
28 min
API uptime · 30d
99.97%
Pharmacy on-time · 7d
96.2%
Recent averages, shown as an example.
Visits by Status
ADMIN
158
Ready for admin action
ACTIVE
95
Ready for doctor action
PENDING
362
Awaiting patient response
HOLDING
315
Not yet ready for action
Resolved Outcomes · 7 days
Prescribed 49(92%)
Referred 1(2%)
Canceled 3(6%)
Recent visit · drill-down
visit_01HQXMK4T8
trtHolding
✓Consents Signed
✓Photos Approved
✓Prescription Sent
⬤Pharmacy: Delivered
⬤Lab: Completed
iLast update 4h ago
From kickoff to production.
Most partners are live within 14-60 days depending on your integration path — platform
partners at the fast end, direct API builds toward the longer end. We'll give you an exact
timeline once we understand your setup. Either way, your team's main lift is the front end
(direct API) or platform configuration (integrated commerce); Beluga handles clinical
operations, pharmacy, and compliance throughout.
Beluga uses analytics cookies to understand how this site is used.
Accept to help us improve. Reject to opt out. No advertising, no
third-party sharing. Read our
privacy policy.