Telehealth Company and Platform Directory

Telehealth platforms and companies operate across a fragmented landscape of direct-to-consumer services, enterprise health system deployments, and specialty-specific clinical networks. This directory page establishes the classification framework for understanding how telehealth organizations are structured, what regulatory categories they fall under, and how platform types differ in function and scope. Understanding these distinctions matters for clinicians, payers, health system administrators, and researchers evaluating the telehealth market.

Definition and scope

A telehealth company, in the context of US health services, is any organization that delivers clinical or health-adjacent services through electronic communications technology — including two-way video, asynchronous messaging, remote monitoring infrastructure, or mobile health applications. The scope of this directory category spans both technology vendors and clinical service organizations, which are not always distinct entities.

Regulatory framing begins at the federal level. The Centers for Medicare & Medicaid Services (CMS) defines covered telehealth services through specific Healthcare Common Procedure Coding System (HCPCS) and Current Procedural Terminology (CPT) codes, and distinguishes between telehealth, telephone-only services, and remote patient monitoring as separate billing categories (CMS Telehealth Services). The Health Resources and Services Administration (HRSA) maintains its own definitions through grant programs and the rural health telehealth policy framework (HRSA Telehealth Programs).

Platform companies operating in this space fall into four primary classification types:

1. Direct-to-consumer (DTC) platforms — services marketed to individual patients for on-demand or scheduled care without a referring provider
2. Business-to-business (B2B) enterprise platforms — technology infrastructure licensed to hospitals, health systems, or payer networks
3. Specialty-network platforms — organizations that aggregate credentialed specialists in a defined clinical domain (telestroke, telepsychiatry, teledermatology)
4. Remote patient monitoring (RPM) vendors — companies providing device hardware, data pipelines, and clinical alerting infrastructure

For a fuller breakdown of platform types by technology modality, see Telehealth Platform Types and Technologies.

How it works

Telehealth platforms operate through one of two foundational delivery architectures — synchronous or asynchronous — and most enterprise-grade platforms support both. Synchronous delivery involves real-time audio-video encounters between a patient and a licensed clinician. Asynchronous delivery, also called store-and-forward, allows patients to submit clinical data, images, or symptom histories that a provider reviews at a later time. The distinction between these models carries reimbursement and licensure implications at both federal and state levels. A detailed treatment of these differences is available at Synchronous vs Asynchronous Telehealth.

Platform architecture typically involves the following discrete components:

1. Patient-facing interface — web browser or mobile application through which patients schedule, initiate, or submit encounters
2. Provider-facing clinical workspace — dashboard integrating patient records, encounter queues, e-prescribing modules, and documentation tools
3. EHR integration layer — application programming interfaces (APIs) connecting the telehealth platform to a health system's electronic health record, often via HL7 FHIR standards (HL7 FHIR R4 specification)
4. Identity verification and consent module — captures informed consent and performs identity proofing consistent with HIPAA requirements under 45 CFR Parts 160 and 164
5. Billing and coding engine — generates claims using appropriate telehealth-specific CPT codes (such as 99201–99215 series for office or other outpatient services delivered via telehealth) and place-of-service code 02 for telehealth encounters

HIPAA compliance obligations apply to any platform handling protected health information (PHI), designating such platforms as business associates under 45 CFR §160.103 when they process PHI on behalf of a covered entity. Platforms must execute Business Associate Agreements (BAAs) with their clinical clients. For a detailed regulatory map, see Telehealth HIPAA Compliance Requirements.

Common scenarios

Telehealth companies appear across the care continuum in distinct operational configurations:

Direct-to-consumer urgent care platforms connect unattributed patients with on-call licensed clinicians for low-acuity conditions. These platforms typically operate under the medical license of a physician group or professional corporation that contracts with the platform technology company — a structure required in states with corporate practice of medicine (CPOM) statutes.

Employer-sponsored telehealth programs are contracted by self-insured employers as a health benefit, often at a per-member-per-month rate. These arrangements are structured through benefits administrators and typically exclude high-acuity or controlled-substance prescribing. See Employer-Sponsored Telehealth Programs for structural detail.

Hospital and health system telehealth programs deploy platform technology to extend existing provider relationships. These configurations commonly support Telehealth Chronic Disease Management, post-acute follow-up, and inpatient specialist consults (telestroke, telepsychiatry, tele-ICU).

Federally Qualified Health Centers (FQHCs) use telehealth to serve Section 330-designated populations, with specific reimbursement structures under the FQHC prospective payment system (CMS FQHC Center).

Decision boundaries

Distinguishing among telehealth companies requires applying at least three classification boundaries:

Clinical vs. non-clinical function — Platforms that host licensed clinical encounters are subject to medical practice regulation, HIPAA, and state telehealth laws. Platforms providing only scheduling, connectivity, or wellness content without clinical decision-making occupy a different regulatory tier and may not qualify as covered entities or business associates under HIPAA.

Multi-state licensure scope — Companies operating across state lines must comply with the licensure laws of the state where the patient is physically located at the time of service, not the location of the provider. The Interstate Medical Licensure Compact facilitates multi-state credentialing for eligible physicians, but compact participation varies by state and specialty.

Prescribing authority — Platforms that include prescribing functions — particularly for controlled substances — face a separate regulatory layer under the Ryan Haight Online Pharmacy Consumer Protection Act and Drug Enforcement Administration (DEA) telemedicine prescribing rules. Platforms must either require an in-person evaluation before prescribing Schedule II–V substances or operate under a DEA-registered special registration when that mechanism is active (DEA Telemedicine Prescribing Regulations).

Platforms claiming accreditation should be assessed against standards from the Utilization Review Accreditation Commission (URAC) telehealth accreditation program or the Joint Commission's telehealth certification pathway, both of which publish their standards criteria publicly.

References

• Centers for Medicare & Medicaid Services — Telehealth Services
• Health Resources and Services Administration — Telehealth Programs
• HL7 FHIR R4 Specification
• HIPAA Administrative Simplification — 45 CFR Parts 160 and 164 (HHS)
• CMS FQHC Center
• Drug Enforcement Administration — Telemedicine Regulations
• URAC Telehealth Accreditation
• The Joint Commission — Telehealth Certification