Telehealth resources
A working reference for multi-state telehealth review.
Telehealth operators face review questions that repeat across states even when the underlying rules differ: consent to asynchronous care, provider-patient relationship establishment, and documentation of clinical judgment. This hub collects the areas we see reviewed most often.
- Format
- Reference material
- Updated
- Reviewed quarterly
This page describes operational patterns commonly reviewed under the ScriptClear standards. It does not state the law of any specific state and is not legal advice.
- Purpose
- Practical operator guidance
- Written by
- The ScriptClear standards team
- Not legal advice
- Informational only
- Updated
- Reviewed quarterly
Frequently reviewed
Areas reviewers return to most often.
- Whether the patient is told, before treatment, whether their visit is synchronous or asynchronous
- Whether the intake questionnaire is specific enough to the requested treatment to support a clinical decision
- Whether a provider's review of the intake is documented, timestamped and attributable to a specific licensed individual
- Whether escalation paths exist for answers that suggest the treatment may not be appropriate
- Whether the platform states which states it is prepared to serve, and whether that list matches where it actually accepts patients
- Whether prescribing decisions reference the intake responses actually collected, rather than a generic protocol applied uniformly
Documentation
What documentation expectations typically look like.
Reviewers are less interested in the existence of a policy than in evidence that the policy was actually followed for real patient encounters.
- 1
Policy
A written description of how the asynchronous or synchronous visit is conducted.
- 2
Evidence of use
Sampled encounters showing the policy applied — intake responses, provider notes, timestamps.
- 3
Provider attribution
A named, licensed individual associated with each clinical decision, not a shared or generic account.
- 4
Escalation record
A record of what happens when an answer falls outside the standard protocol.
Worked example
A worked example of a review question.
Question a reviewer might ask: 'Show three intake submissions from the last quarter where the patient reported a condition or medication that could interact with the requested treatment, and show what the platform did in response.' A strong answer produces the specific submissions, the provider's documented response, and — where the platform proceeded anyway — a documented clinical rationale. A weak answer produces a generic policy document with no linked patient evidence.
FAQ
Questions we hear often
- Does this page state which states allow which telehealth practices?
- No. State-specific legal detail is outside this page's scope; it describes operational patterns reviewed under the ScriptClear standards, not state law.
- Is asynchronous care automatically non-compliant?
- No. Many jurisdictions permit asynchronous care under certain conditions. This page does not make a legal determination for any state.
- How does this differ from the telehealth industry page?
- The industry page frames why and how ScriptClear certifies telehealth operators. This page is a working reference for the review questions themselves.
Not sure where your organization stands? Start with a preliminary eligibility check.
Compliance should be clear, not complicated
See how telehealth scope is defined.
Visit the telehealth industry page for how certification scope is set for asynchronous and multi-state operators.
Know where you stand. Fix what matters. Stay ready.