On this page

A HIPAA consent form is a patient's written permission for a covered entity to use and disclose their health information for treatment, payment and health care operations, and under the Privacy Rule it is optional: covered entities that ask for consent “have complete discretion to design a process that best suits their needs” (HHS). It is not a HIPAA authorization, which the rule requires for uses such as most marketing and which must contain the elements in 45 CFR 164.508(c). Curve Compliance, whose HIPAA intake forms, Curve Forms, keep privacy consent and marketing consent as separate checkboxes, checked each rule on eCFR and HHS on November 2, 2026.

Book a call. Collecting consent online? Curve Forms are hosted by Curve under the BAA Curve signs on every plan, and form answers are never sent to ad platforms. Curve's team does the setup, typically live in about a week. Book a call with Curve.

The rule's text is short: “A covered entity may obtain consent of the individual to use or disclose protected health information to carry out treatment, payment, or health care operations” (45 CFR 164.506(b)(1)). HHS's summary adds that obtaining consent “is optional under the Privacy Rule for all covered entities,” and that “The content of a consent form, and the process for obtaining consent, are at the discretion of the covered entity electing to seek consent” (HHS).

So HIPAA never makes you collect consent for treatment, payment or operations. The rule already permits those uses (45 CFR 164.506(a)); see HIPAA TPO. State law is a separate layer. HIPAA does not override a state privacy law that is more stringent (45 CFR 160.203(b)), so a state can require consent where HIPAA does not. Which state rules apply to your practice is a question to talk to your counsel about.

These documents are easy to mix up. Each does a different job:

DocumentRequired by HIPAA?What it coversRule
ConsentNo, optionalTreatment, payment and health care operations45 CFR 164.506(b); HHS FAQ
Authorization (often called a release form)Yes, for uses and disclosures the rule doesn't otherwise permitThe specific information, recipient and purpose named on it45 CFR 164.508
Notice of privacy practicesYes, for most covered entitiesHow the practice may use and disclose PHI, and patients' rights45 CFR 164.520
Notice acknowledgmentA good faith effort, for providers with a direct treatment relationshipThe patient confirms they received the notice45 CFR 164.520(c)(2)(ii)
Cookie bannerNot a HIPAA documentThe website's cookie and tracking choicesHHS tracking bulletin

HHS describes the authorization as “a detailed document that gives covered entities permission to use protected health information for specified purposes, which are generally other than treatment, payment, or health care operations, or to disclose protected health information to a third party specified by the individual” (HHS). The HIPAA release form checklist walks through its required elements, and the notice of privacy practices guide covers the notice.

Because HHS leaves the content to you, HIPAA sets no required list for consent. If you use a consent form, these are the parts the rule gives you reason to include, with the rule behind each:

Part of the formWhat it saysRule behind it
ScopePermission to use and disclose PHI for treatment, payment and health care operations164.506(b)(1)
LimitThat this consent does not stand in for an authorization where one is required164.506(b)(2)
NoticeWhere to find the notice of privacy practices, and a line acknowledging the patient received it164.520(c)(2)(ii)
RestrictionsThat the patient may ask the practice to restrict uses and disclosures for treatment, payment and operations, and that the practice need not agree, except a restriction on disclosures to a health plan for payment or health care operations, not otherwise required by law, about care paid for in full164.522(a)(1)
Who signsThe patient, or a personal representative, whom the rule treats as the patient164.502(g)(1)
Signature, date and how to withdrawYour choice: HHS leaves the design of the consent process to the covered entityHHS FAQ

Keep marketing out of it. An authorization “may not be combined with any other document to create a compound authorization,” apart from listed exceptions (45 CFR 164.508(b)(3)), so a marketing authorization can't be folded into a consent form.

The rule closes the gap itself. Consent “shall not be effective to permit a use or disclosure of protected health information when an authorization, under § 164.508, is required” (45 CFR 164.506(b)(2)). HHS puts it this way: “Where the Privacy Rule requires patient authorization, voluntary consent is not sufficient to permit a use or disclosure of protected health information unless it also satisfies the requirements of a valid authorization” (HHS). Three uses always need an authorization, apart from narrow exceptions:

Online intake adds two things a paper form doesn't have: the website around the form, and the tools that run on that page. For the website, a covered entity with a web site about its services “must prominently post its notice on the web site and make the notice available electronically through the web site” (45 CFR 164.520(c)(3)(i)); a link next to the consent checkbox keeps it in view. For the tools, HHS's tracking bulletin says “disclosures of PHI to tracking technology vendors for marketing purposes, without individuals' HIPAA-compliant authorizations, would constitute impermissible disclosures” (HHS). A consent checkbox does not change what a page's pixels send.

Curve Forms handle the form side. Forms are hosted by Curve under the BAA Curve signs on every plan, so submissions never pass through a third-party form tool, and each form can carry separate checkboxes for privacy consent and marketing consent. Form events such as a completed submission reach Meta, Google Ads and your other destinations server-side through your event mappings, while form answers, page titles and free text are never sent. See what makes an intake form HIPAA compliant and the patient intake form template.

HHS is direct: “Website banners that ask users to accept or reject a website's use of tracking technologies, such as cookies, do not constitute a valid HIPAA authorization.” Where no Privacy Rule permission applies, or the vendor is not a business associate, “the individuals' HIPAA-compliant authorizations are required before the PHI is disclosed to the vendor” (HHS). The same page notes that a federal court vacated part of the bulletin on June 20, 2024, the part about IP addresses on unauthenticated public pages about health conditions or providers. See cookie banners vs HIPAA authorization and consent management vs HIPAA authorization.

How Curve Compliance helps

Curve Compliance helps on both sides of an online consent flow. Curve Forms host the form under the BAA Curve signs on every plan, with separate privacy consent and marketing consent checkboxes, logic that shows or hides fields based on earlier answers, and a log of every view or export of submissions. On the tracking side, Curve replaces browser ad pixels with one script, sends conversions server-side and strips PHI before data reaches an ad platform. Curve also offers consent management for your website's cookie choices.

Curve is SOC 2 Type II and signs a BAA on every plan (Directory entry). Curve's team does the setup, typically live in about a week.

Sources, checked November 2, 2026: 45 CFR 164.506; 45 CFR 164.508; 45 CFR 164.502; 45 CFR 164.520; 45 CFR 164.522; 45 CFR 160.203; HHS, Summary of the HIPAA Privacy Rule; HHS, consent vs authorization; HHS, Use of Online Tracking Technologies.

Frequently Asked Questions

A patient's written permission for a provider to use and disclose their health information for treatment, payment and health care operations. HIPAA makes it optional (45 CFR 164.506(b)).

Usually it means a release form, which HIPAA calls an authorization: permission to share specific information with a named recipient for a stated purpose, with the elements in 45 CFR 164.508(c). See the HIPAA release form checklist.

Not by HIPAA. HHS says covered entities may obtain consent for treatment, payment and health care operations but are not required to (HHS), though a more stringent state law can still apply (45 CFR 160.203(b)).

Consent is optional permission for treatment, payment and health care operations, designed however the covered entity chooses. An authorization is required for uses the rule doesn't otherwise allow, and it must name the information, recipient, purpose and expiration (HHS; 45 CFR 164.508).

No. HHS says banners that ask users to accept or reject tracking technologies such as cookies are not a valid HIPAA authorization (HHS).

Keep them as separate choices. Where marketing needs a HIPAA authorization, it must meet 45 CFR 164.508, including the patient's signature and date, and the rule bars combining an authorization with another document outside its listed exceptions (164.508(b)(3)). For the consent choices on an intake form, Curve Forms has separate checkboxes for privacy consent and marketing consent.

HIPAA doesn't say, because it doesn't require consent at all; HHS leaves the content and process to the covered entity (HHS). An authorization is different: it must carry the patient's signature and date (45 CFR 164.508(c)(1)(vi)).

Talk to Curve Compliance

Book a call. Building an online intake or consent flow? Curve Forms host it under the BAA Curve signs on every plan, keep privacy consent and marketing consent separate, and never send form answers to ad platforms. Book a call with Curve.