Part 2 fundraising opt-out statement

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

The statement is conditional on intended activity

42 CFR 2.22 requires the separate fundraising statement when the program intends to engage in the activity. An organization with no such activity should avoid generic copy that implies a workflow it does not operate.

Before adding the statement, document the program, intended fundraising purpose, records or data elements, internal and external users, patient population, channels, campaigns, vendors, consent or other authority analysis, HIPAA interaction, state law, and responsible owner. Distinguish true fundraising from treatment, payment, operations, grants, patient education, community outreach, and ordinary marketing through qualified review.

Design the activity and notice together

Define which patients and information could enter the workflow, how source and Part 2 status remain protected, and which approved system creates the audience. Avoid exporting a broad patient list and filtering later. Use the minimum approved data at each stage, role-based access, secure transfer, event logging, vendor limits, and return or destruction terms.

The notice statement should tell patients about the activity and clear opt-out opportunity without revealing participation through an unsafe communication. Align the exact statement, contact route, preference language, campaign footer, scripts, and confirmation. Keep fundraising choice separate from treatment consent, TPO consent, marketing preference, and notice acknowledgment.

The election must work

Offer a route that is easy to find and use. Capture patient identity, communication scope, request time, effective time, channels, campaigns, vendor synchronization, confirmation, and changes. Avoid requiring a reason or creating adverse service consequences.

Accept opt-out through practical phone, writing, email, portal, or communication channel under approved policy. Preserve the original receipt when the request reaches general intake. Ask only for facts needed to identify the patient and preference. Provide language, disability, representative, and safe-contact support without requiring a detailed reason.

Define whether the election covers all fundraising, specific channels, or another permitted scope, and explain the result. Record request, verification where needed, supported scope, effective time, source-of-truth state, downstream acknowledgments, and patient communication. Do not overwrite prior preferences.

Suppress before every release

Reconcile the current campaign cohort against active opt-outs at a defined cutoff and again immediately before send when feasible. Test internal tools, CRM, email, mail, phone, events, development platforms, agencies, and print vendors. Preserve cohort size, preference snapshot, excluded records, vendor input, accepted records, sends, failures, and post-send findings.

Use a campaign hold when suppression totals do not reconcile. An invoice or vendor assurance cannot replace patient-level evidence. During vendor change, retrieve preferences and event history before access ends. Apply opt-outs to copied or offline lists and destroy unneeded files under approved controls.

Protect the patient after an error

Route a fundraising communication sent after opt-out to privacy, complaint, consent, incident, vendor, and corrective-action review as appropriate. Stop remaining sends, preserve evidence, identify affected campaigns and people, correct the source and copies, and communicate carefully through a safe channel. Do not expose program status while apologizing.

Example with suppression readiness

A campaign has 1,100 eligible records and 84 active opt-outs. Seventy-nine are suppressed before release; five remain in a stale vendor file. Suppression readiness is 79 of 84 opt-out records. Hold the campaign until all five are resolved.

The program replaces the vendor file, confirms all 84 suppressions, and checks for other copied lists. It records the failed readiness result and later 84-of-84 retest. The campaign proceeds only after source, vendor, and sample outputs reconcile.

Fundraising checklist

• Confirm the program truly intends an approved fundraising activity.
• Map records, authority, channels, vendors, and safe communication.
• Publish a clear opt-out route without adverse service consequences.
• Preserve request, scope, effective time, and confirmation.
• Reconcile preferences across every internal and vendor channel.
• Hold campaigns when suppression evidence does not balance.
• Investigate errors and protect the patient during correction.

Owner controls

The 2024 final rule supplies the regulatory history. Use approved notice language, consent analysis, preference center, vendor terms, pre-send suppression test, confirmation, complaint route, and post-campaign audit.

Monitor active opt-outs, propagation age, campaign reconciliation, stale lists, vendor evidence, post-opt-out sends, complaints, and correction age. Audit from campaign recipients back to eligibility and preference, then from every opt-out into all downstream systems. Retest after vendor, campaign, consent, notice, or platform changes.

Use de-identified campaign performance where practical so routine reporting does not create another broad list of Part 2 patients. Restrict access to recipient-level evidence and retain it only under the approved schedule.