| name | telemedicine-consent |
| title | Telemedicine Consent and Policy Document |
| description | Drafts dual-purpose telemedicine consent and policy documents covering informed consent, HIPAA privacy architecture, prescribing limitations, clinical scope boundaries, and patient acknowledgment sections. Addresses federal and state telehealth regulations, DEA controlled substance rules, and Interstate Medical Licensure Compact requirements. Use when drafting telehealth consent forms, telemedicine informed consent, remote patient monitoring agreements, virtual care policies, RPM consent documents, or store-and-forward authorization forms. |
| author | CaseMark |
| author_url | https://github.com/CaseMark/skills/tree/main/skills/legal/telemedicine-consent |
| license | Apache-2.0 |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | us |
| practice | healthcare |
| language | en |
| tags | ["agreement","drafting","regulatory"] |
Telemedicine Consent and Policy Document
Why This Skill Exists
Telemedicine consent documents fail for two reasons: they omit jurisdiction-specific prescribing and licensure requirements (creating regulatory exposure), or they use boilerplate language that fails informed consent standards because patients don't understand the real limitations of remote care. A consent form that doesn't explain why a provider can't palpate an abdomen over video is legally insufficient. A policy that ignores DEA telehealth prescribing rules invites enforcement action.
This skill produces a dual-purpose document — informed consent instrument and operational policy framework — that satisfies HIPAA privacy requirements, state telehealth regulations, and DEA prescribing rules while remaining accessible to patients at varying health literacy levels.
Checkpoint A: Pre-Draft Intake (Mandatory)
Gather before drafting unless user says "use defaults":
- Provider identity — legal entity name, professional designations, state licensure details
- Jurisdiction — state(s) where patients are physically located during consultations
- Modalities — synchronous video, asynchronous store-and-forward, RPM devices, mHealth apps
- Prescribing scope — whether controlled substances will be prescribed; if so, which schedules
- Billing model — insurance-based, self-pay, or hybrid
- Existing policies — institutional consent forms, privacy notices, credentialing requirements
- Technology platform — vendor names, encryption standards, BAA status
Defaults if user doesn't respond: synchronous video only; no controlled substance prescribing; insurance-based billing; standard HIPAA safeguards; single-state practice. Label all defaults clearly.
Step 1: Draft Consent and Telemedicine Explanation
| Element | Requirements |
|---|
| Patient ID | Full legal name, DOB |
| Provider ID | Legal entity, designations, license number |
| Modalities | Enumerate each modality in use with plain-language definition |
| Benefits | Access, convenience, scheduling flexibility, reduced travel |
| Limitations | No physical exam, limited emergency response, technology dependency |
Use plain language — explain telemedicine without jargon while maintaining legal sufficiency for informed consent.
