The stack index · September 8, 2026
The telehealth stack: every layer of the business, indexed.
A telehealth company is nine layers of assembly: an entity structure, a clinician supply, the software, a pharmacy relationship, payments, labs, a compliance function, a marketing machine, and the operations running it all. This page indexes all nine, linking each layer's deep-dive guides, verified vendor directories, and working tools where they exist, so you can walk the whole journey (or hand it to your diligence checklist) from one place.
Published by EmbedCare, which operates several of these layers as a platform and says so. The directories linked below profile vendors, competitors included, from their own public claims and the dated public record; nothing is ranked, no vendor paid to appear, and inclusion implies no relationship with EmbedCare in either direction. Each directory carries its own verification date. Corrections: anthony@embedcare.com.
Entity & legal structure
In corporate-practice-of-medicine states the business splits in two: a clinician-owned professional entity that practices, and a management company that runs everything else. The structure is built per state, and the strictest state you plan to serve sets the bar.
The diligence question: Does your corporate structure survive your strictest state?
Clinician supply
An operated medical group, a staffing network, or your own hires; oversight and collaboration requirements vary by state and by clinician type, and the model you pick decides who carries licensure coverage.
The diligence question: Who supplies the clinicians, and what happens when one says no?
Software
Eight products wearing one brand: storefront, intake engine, clinical record, prescribing rails, pharmacy routing, billing, patient communications, and the compliance glue between them. Most failures happen at the seams, not inside the layers.
The diligence question: Who holds the seams between the eight software layers?
Pharmacy
First the chassis question (503A patient-specific compounding versus 503B outsourcing facilities), then the counterparty: state licensure coverage, testing documentation, and integration quality. Supply resilience is a design decision, not a hope.
The diligence question: What is your plan for the day a pharmacy drops a state?
Payments
Selling medicine is what changes this layer: pharmacy merchant categories sit in the card networks' high-integrity-risk registration programs, several mainstream processors restrict prescription-product models in their own terms, and a specialist lane underwrites them. Consult-only telemedicine is a different, easier case, and the directory separates the two. Getting this layer wrong is how running businesses lose their revenue overnight.
The diligence question: Does your processor know exactly what you sell?
Labs & diagnostics
Ordering rails, at-home kit platforms, collection devices, and phlebotomy networks, wherever a care line needs bloodwork. This is the fastest-consolidating vendor layer we track, so verify ownership as well as claims.
The diligence question: Who owns the result when it comes back abnormal?
Compliance
Certification, claims discipline, state rules, and the paper trail that certification and underwriting reviews ask for. Retrofitted after launch it costs multiples of what it costs designed in.
The diligence question: Would your website pass the read a certification analyst gives it?
Marketing
Certification-gated ad platforms, HIPAA-constrained pixels, and the owned audience that outlasts both. The claims you make and the pixels you run are compliance decisions wearing growth clothes.
The diligence question: Which claims can you make, and which pixels can you legally run?
Operations
The org you actually need at each stage and the numbers it should watch: who to hire when, which metrics move first, and what the honest benchmarks are.
The diligence question: Which metric would tell you first that the model is not working?
The whole journey, in one pass
For readers who want the narrative instead of the map: the walkthroughs and cross-cutting references that span all nine layers.
Layers are rentable. Seams are not.
Two observations from mapping this category all year. First, the expensive layers are rentable now: clinicians, pharmacy, software, and much of compliance can be assembled from the vendors in these directories or arrive together on an operated platform. That is why the entity, the audience, and the operating discipline are where founders actually differentiate; those three cannot be rented.
Second, every layer has a vendor category, but the seams between layers do not. What happens to the subscription when a clinician declines, to the shipment when a card fails, to the record when a patient cancels: whoever holds those seams (you, an assembled vendor set, or one operated platform) holds the launch timeline and the patient experience. Use this index as the diligence checklist for any launch pitch, ours included: make every vendor and every plan name which layers it covers, which it leaves you, and who holds the seams between them.
The telehealth stack: FAQ
What is the telehealth stack?
Two stacks wearing one brand. The business stack is nine layers of assembly: an entity and legal structure, a clinician supply, the software, a pharmacy relationship, payments, labs where care lines need them, a compliance function, a marketing machine, and operations. Inside the software layer sits a second stack of eight products: storefront, intake engine, clinical record, prescribing rails, pharmacy routing, billing, patient communications, and the compliance glue. This index maps the nine business layers; the tech stack guide walks the eight software layers.
What are the nine layers of a telehealth business?
In rough assembly order: entity and legal structure, clinician supply, software, pharmacy, payments, labs and diagnostics, compliance, marketing, and operations. Every launch plan and every vendor pitch covers some subset of these; the useful diligence move is making each one name which layers it covers, which it leaves to you, and who holds the seams between them.
Do I have to build all nine layers before launching?
You have to account for all nine; you do not have to build them. Three honest paths exist: build from scratch (maximum control, slowest), assemble from vendors and healthcare APIs (faster, and you own the integration seams), or launch on an operated platform where the layers arrive already built and your team spends on brand and audience. The directories and guides under each layer here are the diligence material for whichever path you take.
Is this index neutral?
It is published by EmbedCare, which operates several of these layers as a platform and competes with some of the vendors profiled, so read it knowing that. The mitigations: the directories profile vendors from their own public claims and the dated public record, competitors are included, nothing is ranked, and nobody paid for placement. Every directory states its verification date and re-verification triggers, and corrections are welcome by email.
This index is orientation and diligence material, not legal advice and not a recommendation of any vendor; every linked directory states where its facts come from, and you should confirm claims directly before relying on them.
This index is also a map of what EmbedCare operates. Get the partner overview and see which of the nine layers you can stop shopping for.
One email, no sequence. A human follows up with your program scoped.
Nine layers to assemble, or one platform to launch on.
EmbedCare runs the stack under your brand, with licensed clinicians making every prescribing decision.