Ryan Haight Act and Async Prescribing: A Telehealth Operator's Guide

What does the Ryan Haight framework require?

The fourth temporary extension rule explains the general prior in-person evaluation framework and its exceptions. The current extension is effective January 1 through December 31, 2026. It does not remove the need for legitimate medical purpose, appropriate authority or compliance with other applicable rules.

For an operator, the important step is to identify the actual pathway supporting each program. Do not use telehealth as a single undifferentiated category. The facts can include the medication, the prescriber, the patient location, prior encounters, encounter format and any specific exception being used.

Write those facts into the clinical operating design. The commercial team does not need to decide the law for each patient, but it does need to avoid building a promise that the approved clinical process cannot fulfill. The white-label telehealth overview explains the distinction between coordinating an experience and making medical decisions.

Why is asynchronous intake not the same as prescribing authority?

Asynchronous intake collects information before or between encounters. It can help organize history, documents and questions. That is different from establishing that a particular prescription may lawfully be issued. A form can be complete while the provider still needs an appropriate encounter, additional records or another step.

DEA's announcement describes the general extended pathway as audio-video for Schedule II–V controlled medications. It separately describes a narrower audio-only provision related to qualifying opioid-use-disorder treatment. That limited provision should not be generalized to every controlled drug or to TRT.

The product interface should reflect this distinction. Intake complete should mean the information was submitted, not that a prescription was approved. A clinician may determine that the person needs a different encounter format, further evaluation or care outside the program. These are valid outcomes of care, not errors to hide from the customer.

AI-assisted intake can support organization and workflow. It does not acquire a medical license, make the independent clinical decision or create prescribing authority that would otherwise be absent.

How should a program map its prescribing pathway?

Assign responsibility for maintaining each layer. The technical implementation should not invent clinical exceptions because a patient cannot complete a step. Instead, it should route the case to the appropriate team and show the customer a clear next action.

Test the negative cases as carefully as the successful one. A launch review should include an unsupported location, an expired credential, an incomplete encounter and a pharmacy clarification. The system should stop or route those cases without implying that payment guarantees treatment.

How do state rules affect a nationwide program?

HHS explains that authority to deliver care across state lines varies. The federal temporary extension is one layer of the analysis; it does not replace state professional and prescribing requirements. A clinician assignment must match the patient and program rather than simply selecting whoever is available.

TEHR connects brands with an independent clinical network with 50-state reach. Program availability, eligibility and appropriate care still vary. The brand should describe that reach without turning it into an assurance that every controlled medication is available to every patient in all states.

State expansion should therefore be program-specific. When adding a new category or clinician type, revisit the route rather than copying the configuration from an unrelated service. The CPOM review framework addresses the parallel ownership and control questions, which are distinct from an individual prescriber's authority.

What should an existing brand do when migrating patients?

Records can support continuity, but an imported chart is not itself a new prescription or a completed encounter with a new prescriber. Map the care relationship, prior evaluations, current orders and outstanding follow-up separately from the account and subscription data.

For each active patient group, identify the next expected clinical event and who is responsible for it. Some people may be waiting for an appointment, others for a pharmacy response, and others for a future review. A migration plan that moves all accounts on one date without understanding those states can create avoidable gaps.

Keep source provenance. A historical note should show its origin and date, and a prior prescription should not be displayed as though the receiving clinician created it. Reconcile active work before closing the old workflow. Use the patient migration checklist to coordinate records, patient communication and unresolved tasks.

Do not promise uninterrupted controlled-medication supply as a feature of the software move. The independent provider and pharmacy must determine what is appropriate within the applicable rules. The brand can promise a defined coordination process only when that process is actually staffed and supported.

How should a brand prepare for the end of 2026?

Do not assume the temporary extension will continue unchanged. Its stated end date is December 31, 2026. Build a review milestone before that date, identify who monitors official developments and decide how the team will translate a change into patient-facing operations.

Create a contingency inventory. Which programs currently depend on the temporary pathway? Which appointment types, notices, scripts, agreements and technical rules would need to change if the authority changes? Which patients have upcoming care events that might be affected? This is planning for uncertainty, not predicting a specific regulatory outcome.

A useful change process begins with the source document, then the clinical and legal interpretation, then the product configuration and communication. Avoid reversing that order by launching new copy as soon as a headline appears. If a new rule applies only to a subset of practitioners or circumstances, the interface must preserve that scope.

Keep historical decisions documented. When a rule changes, staff may still encounter records created under the earlier pathway. Clear dates help them distinguish a historical record from the rule governing a new encounter.

What should customer-facing copy and support scripts say?

Explain the sequence: submit information, complete the required evaluation, receive an independent clinical decision, and obtain any prescribed treatment through the appropriate pharmacy process. Do not collapse those steps into instant approval. A short journey can still be accurate.

Support staff should have separate instructions for scheduling, billing and clinical concerns. When someone asks whether a prescription will be renewed, the answer should route to the clinical team rather than promise a result. When the issue is a technical failure joining a video appointment, support can help restore access without deciding that the appointment is unnecessary.

Commercial disclosures should also explain what happens if medication is not prescribed, including the actual payment and refund terms. Those terms must reflect the offer rather than an assumption that every participant receives the same outcome.

Review the TEHR platform with these cases in mind. Ask to see how intake, appointment status, clinical decisions and pharmacy events remain distinct. For the business model, obtain a scoped quote that describes the supported services without promising clinical outcomes.

Which operational signals are worth monitoring?

Monitor completion and handoff failures rather than pressuring clinicians to approve more prescriptions. Useful measures include incomplete encounter requirements, routing mismatches, unresolved pharmacy questions, failed appointment connections and customers who do not understand the next step. Each reveals a process the operator can improve.

Keep a separate review for safety complaints and clinical concerns. They should reach the appropriate professionals, not be reduced to churn or conversion problems. An efficient business knows the difference between removing unnecessary administrative friction and removing a necessary clinical step.

Document changes to the workflow and the reason for them. This helps teams understand why a step exists and prevents a later redesign from accidentally deleting it. The goal is a reliable brand experience that supports independent care under the current rules.

What else should you know?