Parties
Identify patient, provider, and any third-party facilitators; include legal names, licensure state for provider, and contact information for notices.
A signed remote consultation agreement clarifies consent, reduces administrative disputes, and supports legal enforceability. Electronic execution is permitted under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, while also documenting patient consent and HIPAA compliance steps for health information protection.
Primary users include clinicians, clinic administrators, and patient intake staff who need documented remote-consent and service terms before telehealth visits.
Use this agreement to ensure clinical, privacy, and billing requirements are documented in advance and to provide a retrievable record of patient consent.
Identify patient, provider, and any third-party facilitators; include legal names, licensure state for provider, and contact information for notices.
Specify permitted consultation types, limitations (no surgical procedures), follow-up requirements, and conditions necessitating in-person referral to avoid scope ambiguity.
Describe approved platforms, minimum device or connectivity requirements, and procedures for technical failures or platform outages during the encounter.
Detail how PHI is protected, whether a Business Associate Agreement exists, data transmission safeguards, and patient responsibilities for privacy at their location.
Include informed consent language for telehealth, disclosure of risks and benefits, and how the patient may withdraw consent or request records.
State visit fees, cancellation and no-show policies, insurance billing practices, and any patient financial responsibility for telehealth services.
| Field | Configuration |
|---|---|
| Authentication Level | Email or SMS code; KBA for higher risk |
| Record Retention | Retain signed PDF + audit trail in EHR |
| Notifications | Automated email confirmations to patient and clinic |
| Audit Trail | Capture IP, timestamp, and action log |
Use a platform that supports secure transmission, audit trails, and any required compliance features such as a HIPAA BAA when handling PHI.
Confirm platform compatibility with existing systems (EHR, billing) and ensure BAAs and access controls are in place before collecting or storing patient records.
Effective on the date entered; governs service authorization.
E-signatures typically completed within 24 hours for scheduled visits.
Patient may withdraw consent per policy; implement acknowledgment procedures.
Signed records should be accessible in the EHR immediately after signing.
Allow 1–3 business days for administrative reviews or billing linkage.
Legal and clinical teams finalize consent language before deployment.
Front-desk or portal collects patient identifiers and prepares document.
Patient signs electronically prior to or during the telehealth visit.
Signed copy and audit trail archived per retention policy.
A rural clinic implements a telehealth consent form for chronic care follow-ups to enable remote visits.
A dermatology practice uses a remote consultation agreement for image-based consults and triage.
| Criteria | Electronic | Paper |
|---|---|---|
| Legal Validity | esign/ueta | handwritten |
| Typical Turnaround | under 24 hours | days to weeks |
| Authentication | email/sms/kba | id in person |
| Record Copy | digital audit trail | physical file |
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Free trial available | Free trial available | Free trial available | Free trial available |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |