Telehealth Expansion Requirements in Connecticut: 2026 Guide

Connecticut expansion generally requires each clinician to have Connecticut authority to practice; an out-of-state license alone is not enough to assume telehealth access. The Connecticut Department of Public Health administers relevant professional licenses, while Conn. Gen. Stat. § 19a-906 supplies the central telehealth framework. The former temporary out-of-state authorization mechanism in § 19a-906a was repealed in 2024.

Connecticut telehealth requirements at a glance

Do I need a Connecticut license to treat Connecticut patients by telehealth?

Yes. Connecticut expansion should be handled provider by provider through the Connecticut Department of Public Health, rather than by relying on a clinician’s home-state license. DPH administers physician, APRN, and physician-assistant licensing, and the applicable authorization depends on the clinician’s profession.

An eligible physician may use the Interstate Medical Licensure Compact as an expedited route toward a Connecticut physician license. The compact is not a telehealth-only registration and does not eliminate the need for Connecticut licensure. A PA’s supervision and delegation requirements also need review before activation. For APRNs, Connecticut’s experience-based autonomy rule is especially important: DPH states that an APRN may practice without a collaborative agreement after at least three years and 2,000 qualifying hours, followed by written notice to DPH, under Conn. Gen. Stat. § 20-87a(3).

Operators comparing several jurisdictions can use the state-by-state telehealth licensing requirements hub to keep Connecticut’s provider review separate from first-time launch tasks.

Can an out-of-state doctor provide telehealth to Connecticut patients?

Not solely because the doctor holds an out-of-state license. The reviewed Connecticut sources do not establish a current general registration or permit allowing an unlicensed out-of-state clinician to practice broadly through telehealth.

Public Act No. 24-110, approved June 4, 2024, repealed § 19a-906a, the former temporary mechanism under which the DPH commissioner could authorize certain out-of-state telehealth providers by order. Older expansion checklists that describe that process as an available general Connecticut telehealth registration are therefore outdated. Confirm any other claimed statutory authorization with DPH before scheduling Connecticut patients.

What standard applies to telehealth practice in Connecticut?

Connecticut requires telehealth care to conform to the professional standard of care applicable to the provider and expected for comparable in-person care under Conn. Gen. Stat. § 19a-906. The statute covers multiple licensed professional categories, including physicians, APRNs, and PAs.

This matters when an operator imports protocols, triage rules, escalation paths, or documentation templates from another state. The platform can support workflows, but independently licensed clinicians remain responsible for clinical judgment within their Connecticut authority. Review the planned modality and provider category against the current text of § 19a-906 before launch.

Does Connecticut require telehealth consent?

Connecticut has no specific consent script, signature method, or timing requirement confirmed by the reviewed official sources; confirm the current rule with the Connecticut Department of Public Health. The research packet identifies consent as unresolved rather than supplying a reliable subsection of § 19a-906 or a board rule.

Do not copy a consent workflow from another state and label it Connecticut-compliant without current review. Treat the consent language, collection method, record retention, and provider-specific requirements as an open launch item.

Can a Connecticut practitioner-patient relationship be formed entirely by telehealth?

Connecticut has no fully resolved telehealth-specific rule in the reviewed sources confirming when every practitioner-patient relationship may be established entirely by telehealth; confirm the current rule with the Connecticut Department of Public Health and the applicable professional authority.

Conn. Gen. Stat. § 20-631 and related Chapter 400j provisions define a provider-patient relationship in prescribing-related contexts using elements that include a medical complaint, medical history, physical examination, and a logical connection between those facts and the prescribed drug or device. The exact application can vary by profession, service, and medication category, so the clinical workflow should receive qualified review.

What are Connecticut’s telehealth prescribing rules?

Connecticut requires a bona fide practitioner-patient relationship and medical evaluation before prescribing controlled substances under Conn. Agencies Regs. § 21a-326-1(c)–(d). The regulation addresses prescribing outside a bona fide relationship or without medically evaluating the need for a controlled substance as outside the course of professional practice.

That rule should not be expanded into a blanket statement about every prescription, clinician type, or telehealth modality. For non-controlled prescribing, the reviewed sources do not provide a complete current rule. Build a Connecticut-specific review for relationship formation, evaluation, documentation, clinician scope, and medication category.

Can a telehealth company use an MSO structure in Connecticut?

Connecticut requires separate analysis of clinical ownership, control, and administrative services before an operator adopts an MSO structure. Conn. Gen. Stat. § 20-9(a), § 19a-19, § 33-182a, § 34-243, and Chapter 594b are relevant corporate-practice, professional-entity, medical-foundation, and management-services authorities.

Chapter 594b addresses administrative services such as accounting, payroll, billing, human resources, and information technology. That does not create a universal safe-harbor checklist for every investor, professional entity, fee arrangement, or contract. Keep clinical decision-making with the appropriately licensed professional entity and obtain transaction-specific legal review for ownership, control, fee-splitting, and management terms.

What Connecticut business registration and fees should an expansion operator verify?

Connecticut DPH directs applicants to professional licensing, eLicense, and facility-license resources; the reviewed sources do not establish that every telehealth-only business needs a separate clinic or facility license solely because it serves patients remotely.

The DPH physician page lists a $565 initial application fee, a $575 renewal application fee, and a $565 reinstatement fee. The reviewed PA page states that the described PA application has no application fee. These are profession-specific figures, not a prediction of total expansion cost. Verify current fees and any facility requirements with DPH, and separately research business-entity registration with the Connecticut Secretary of State.

What Connecticut privacy rules apply beyond HIPAA?

Connecticut’s Data Privacy Act can apply to consumer-health-data controllers doing business in Connecticut or targeting Connecticut residents, even without the ordinary revenue or processing thresholds, under Conn. Gen. Stat. § 42-526 and related §§ 42-515–42-529e.

An expansion review should map HIPAA-covered data, Connecticut consumer health data, processor contracts, data sales, geofencing, advertising and analytics tools, and breach response. Conn. Gen. Stat. § 36a-701b addresses breach obligations involving personal information such as medical information and health-insurance identifiers. HIPAA exemptions in the Connecticut law do not mean HIPAA automatically resolves every state privacy issue.

What changed recently in Connecticut telehealth rules?

Public Act No. 24-110 was approved June 4, 2024, and repealed § 19a-906a. The practical consequence is that older guidance describing a general commissioner-order pathway for out-of-state telehealth providers should not be used as the current Connecticut expansion rule.

The 2024 telehealth materials also discuss revisions involving out-of-state telehealth-provider language and professional liability. The final codified statute, rather than a proposal or substitute bill, controls. As of October 10, 2026, unresolved consent, remote-relationship, facility, and MSO questions should remain explicit review items.

Connecticut telehealth clinic launch sequence

1. 1Map the service model. Identify patient locations, modalities, provider types, prescribing categories, and whether the operation has a Connecticut physical site.
2. 2Verify physician credentials with DPH. Confirm a Connecticut license or an eligible compact-based Connecticut physician license before activation.
3. 3Verify APRN credentials with DPH. Determine whether the APRN needs collaboration or qualifies for independent practice under Conn. Gen. Stat. § 20-87a(3).
4. 4Verify PA credentials and supervision. Review the Connecticut DPH PA requirements, including supervision and delegation questions applicable to the model.
5. 5Review § 19a-906. Match the planned service, provider category, and modality to the current Connecticut telehealth statute.
6. 6Resolve consent and relationship questions. Obtain qualified review of Connecticut DPH requirements, § 20-631, and any applicable professional-board interpretation.
7. 7Build prescribing controls. For controlled substances, document the bona fide relationship and medical evaluation process required by Conn. Agencies Regs. § 21a-326-1.
8. 8Review the clinical-business structure. Separate independent clinical decisions from platform, marketing, billing, payroll, and technology functions under the relevant Connecticut entity authorities.
9. 9Confirm DPH and facility requirements. Use DPH licensing and provider resources to verify professional, facility, and permit questions; separately address business-entity registration.
10. 10Map privacy and breach operations. Assign Connecticut consumer-health-data, processor, geofencing, and breach-response responsibilities across the operator and vendors.
11. 11Create a renewal and audit calendar. Track each clinician’s Connecticut status, professional documents, collaboration or supervision evidence, and workflow review dates.

MDLaunchr is the brand behind WhiteLabelClinic.com, a platform designed to help qualified businesses evaluate and coordinate the technology, operational, compliance, clinical-network, and fulfillment relationships involved in launching telehealth services. Discuss expansion readiness with MDLaunchr before treating Connecticut activation as a software-only change.

What should an operator document before Connecticut activation?

Use this final readiness checklist:

• Connecticut license status for every physician, APRN, and PA
• Compact pathway documentation for any physician using it
• APRN collaboration or independent-practice evidence
• PA supervision and delegation review
• Current § 19a-906 review for the planned service
• Consent and remote-relationship questions routed for qualified review
• Controlled-substance relationship and evaluation controls
• Clinical-entity and administrative-services analysis
• DPH, facility, and business-registration determinations
• Connecticut privacy, processor, geofencing, and breach mapping
• License renewal and credentialing ownership

Educational disclaimer: This article is general business and regulatory information for healthcare entrepreneurs. It is not legal advice, medical advice, licensing advice, or a substitute for review by Connecticut counsel, the Connecticut Department of Public Health, or the applicable professional authority. Requirements can change; verify current rules before launch.

Related reading: Telehealth Expansion Requirements in Colorado: 2026 Guide, Telehealth Expansion Requirements in California: 2026 Guide.