Document Title
Use an explicit title such as 'Revocation of HIPAA Authorization' and include a revision or effective date to clearly link the revocation to prior authorizations.
Revoking a HIPAA authorization restores patient control over future disclosures of PHI, limits ongoing data sharing, and reduces exposure of sensitive records. Timely revocations help covered entities update access controls and ensure disclosures occur only under lawful exceptions or prior reliance.
This form is used by patients or their authorized representatives to stop future disclosures of protected health information.
Use an explicit title such as 'Revocation of HIPAA Authorization' and include a revision or effective date to clearly link the revocation to prior authorizations.
Provide the patient's full legal name, date of birth, and any patient identification number used by the health system; mismatches can delay processing or trigger verification.
Reference the original authorization by date, recipient(s), and description of PHI disclosed so the covered entity can identify which consent is being withdrawn without ambiguity.
Clearly state whether the revocation applies to all disclosures or specific recipients, list the affected recipients, and provide the effective revocation date in MM/DD/YYYY format.
Include signature of the patient or authorized representative, printed name, relationship to patient, and date. Electronic signatures are valid if executed under ESIGN/UETA and recorded.
Provide a daytime phone number, email, and mailing address so the provider can confirm receipt, request clarification, or follow up about prior disclosures.
| Field | Configuration |
|---|---|
| Authentication | Use email link plus optional SMS code for verification. |
| Signature Type | Enable ESIGN-compliant electronic signature capture. |
| Routing | Auto-notify privacy officer and BAA contacts. |
| Retention | Archive signed revocations in secure storage for HIPAA retention. |
| Requirement | Standard Rule | Notable Variation |
|---|---|---|
| Notarization | varies by state | |
| Witnesses | varies (some forms) | |
| Formality | written | written required |
| Electronic Validity | yes (esign/ueta) |
| 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 | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
The clinic standardized revocations into its intake workflows to stop future disclosures quickly and securely.
A small healthcare-adjacent provider used online revocation forms to centralize requests and reduce phone inquiries.
Use MM/DD/YYYY; affects future disclosures only.
Does not undo disclosures already made in reliance before receipt.
Request written receipt from provider within a reasonable time.
Update access lists and notify BAAs promptly.
Keep records per HIPAA retention rules.
Patient signs and sends revocation to the provider.
Provider confirms receipt and logs the revocation.
Provider notifies business associates and prior recipients where applicable.
Access controls and disclosure logs are adjusted to reflect the revocation.
Ensure the platform supports HIPAA safeguards, BAAs, and reliable audit trails before using it to accept revocations electronically.