# HIPAA Release and Authorization Forms Explained > A plain-English explainer on HIPAA release and authorization forms: what they are, the required elements of a valid HIPAA authorization, the difference between consent and authorization, when each is needed, and where to find official sources. We explain rather than provide a fillable legal form. General information, not legal advice. Source: https://playciso.com/blog/hipaa-release-form-explained · Published: 2026-10-23 · Publisher: PlayCISO (https://playciso.com) --- A HIPAA release form — more precisely, a HIPAA authorization — is a written permission signed by a patient that allows a covered entity to use or disclose their protected health information for a purpose the Privacy Rule does not otherwise permit. This article explains what these forms are and how they work, and points you to official sources. It is general information, not legal advice, and it deliberately does not provide a fillable legal form. ## What a HIPAA release actually is Under the HIPAA Privacy Rule, protected health information (PHI) can flow freely for a few core purposes — treatment, payment and routine healthcare operations — without the patient signing anything specific each time. A HIPAA authorization is the document you need when information needs to leave that normal flow: sending records to an employer, an attorney, a school, a life insurer, a family member, or using PHI for marketing or research. It converts an otherwise-impermissible disclosure into a permitted one, on the strength of the individual's explicit, informed permission. People call it a "release form," a "medical records release," or a "consent form," but the legally meaningful object is the authorization, and it has specific content requirements. ## The required elements of a valid authorization The Privacy Rule is prescriptive about what a valid authorization must contain. If any required element is missing, the authorization can be invalid — and a disclosure made on an invalid authorization can itself be a violation. The required pieces fall into two groups. - Core elements. A specific and meaningful description of the information to be used or disclosed; the name or class of person(s) authorised to make the disclosure; the name or class of person(s) or entities who may receive it; a description of each purpose; an expiration date or expiration event; and the individual's signature and date (or a personal representative's signature, with a description of their authority). - Required statements. A statement of the individual's right to revoke the authorization and how to do so; a statement that the covered entity generally may not condition treatment, payment, enrollment or eligibility on signing (with narrow exceptions); and a statement that information disclosed under the authorization may be subject to re-disclosure by the recipient and no longer protected by HIPAA. On top of that, an authorization must be written in plain language, and the individual must be given a copy. Because the "specific and meaningful description" and the expiration have to fit the actual disclosure, a generic internet template rarely satisfies the rule on its own. ## Consent versus authorization — a distinction that matters These two words are used loosely in everyday speech but mean different things under HIPAA. A general **consent** — the sort of form you sign at intake agreeing to treatment — is not what the Privacy Rule means by authorization, and HIPAA does not require a signed consent for a provider to use PHI for treatment, payment and operations. An **authorization** is the formal, element-specific document the rule _does_ require for the non-routine uses: releasing records to a third party, most marketing, any sale of PHI, and most research. The practical rule of thumb: if information is moving for routine care, a signed HIPAA authorization usually is not required; if it is moving for anything outside treatment, payment and operations, a valid authorization almost certainly is. State laws and rules for especially sensitive records (for example, certain mental-health or substance-use records) can add further requirements on top. ## Revocation and expiration An authorization is not permanent. The individual generally has the right to revoke it at any time in writing, and the form must explain that right. Revocation stops future disclosures but does not reverse actions already taken in reliance on the authorization. Every authorization must also carry an expiration date or event, so it ends on its own terms unless it was written to run until a stated event, such as the conclusion of a specific legal matter. ## Where to go for official sources There is no single universal government form, because the right document depends on the organisation, the specific disclosure and applicable state law. The authoritative source for the requirements is the US Department of Health and Human Services (HHS) Office for Civil Rights, which publishes the Privacy Rule and detailed guidance on authorizations and on an individual's right to access their own records. Most covered entities build their own authorization forms to satisfy the required elements, usually with legal review, and many electronic health record and patient-portal platforms ship compliant templates. If you are evaluating such a platform as a vendor, confirm it handles authorizations correctly and that the vendor will sign a business associate agreement — the kind of question a [vendor risk scorecard](/tools/vendor-risk-scorecard) is built to surface. For the broader rules these forms sit within, see our explainer on [HIPAA compliance](/blog/hipaa-compliance-explained), and note that the [HITECH Act](/blog/hitech-act-explained) strengthened individuals' access and breach-notification rights that interact with these disclosures. ## Frequently asked questions **What is a HIPAA release form?** A signed, written authorization that lets a covered entity use or disclose a patient's PHI for a purpose the Privacy Rule does not otherwise permit, such as sending records to a third party. **What must a valid authorization include?** Core elements (specific description of the information, who discloses, who receives, purpose, expiration, signature and date) and required statements (right to revoke, no conditioning on signing, and re-disclosure risk), in plain language, with a copy to the individual. **How is consent different from authorization?** Consent is broad and often not required for routine treatment, payment and operations; authorization is a specific, required document for non-routine disclosures like releases to third parties, marketing and research. **Where do I get an official template?** From HHS Office for Civil Rights guidance plus your own legally reviewed form; there is no single universal government form, and we do not provide a fillable one here. **Can a patient revoke it?** Yes, generally in writing at any time; revocation stops future disclosures but not those already made, and every authorization also has an expiration date or event.