Part 2 program-director payment-only consent

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

Current rule checkpoint

Live 42 CFR 2.15(a)(2) allows the Part 2 program director to exercise a qualifying patient's consent right solely to obtain payment from a third-party payer or health plan during a period of medically caused inability to take knowing or effective action. Current section 2.31 supplies the consent elements. The HHS fact sheet identifies February 16, 2026 as the amended framework's compliance date.

Every prerequisite needs evidence

The current rule ties director action to patient status, absence of adjudication, medical incapacity, limited duration, payment purpose, and eligible recipient. Record each fact, source, reviewer, date, director, consent, disclosure, and reassessment.

Payment necessity defines the information

Identify the payer or plan, claim or payment event, recipient endpoint, requested data, necessary information, service dates, amount, and narrower alternatives. Avoid complete-record releases when a smaller data set supports payment.

Recovery returns decision-making to the patient

Set a reassessment trigger and stop director-authorized disclosures when the patient can act. Inform the patient as appropriate, preserve the disclosure history, update access, and obtain the patient's own consent for later uses when required.

Use a director decision form with hard gates

Require confirmation that the patient is an adult, has no court adjudication governing health-care capacity, has a documented medical condition, cannot take knowing or effective action for the period, and needs a use or disclosure to obtain payment from a named payer or plan. Record the clinical source, communication supports attempted, onset, reassessment time, and director identity.

The form should block family, employer, legal, research, marketing, general operations, and other recipients or purposes. It should also prevent the director from using this route merely because obtaining the patient's signature is inconvenient or delayed.

Build the consent around the payment transaction

Specify patient, payer or plan, information, payment purpose, expiration tied to the incapacity or event, revocation process where applicable, required statements, director signature, and date. Record why each data element and attachment is needed. Prefer a claim-specific or episode-specific scope over a complete record.

Verify payer endpoint, member and product, service dates, claim, prior authorization or appeal relationship, transmission method, vendor access, and receipt. Distinguish obtaining payment from unrelated analytics, quality measurement, fraud investigation, litigation, or secondary use and obtain separate authority when needed.

Stop the route when its facts change

Reassess before recurring claims, attachments, appeals, and follow-up requests. When the patient recovers, stop future director-authorized disclosures, restore ordinary consent controls, explain prior disclosures when appropriate, and obtain patient consent for later covered actions.

If a court adjudication appears, a representative claims authority, the payer changes, or the purpose expands, pause and reclassify the route. Preserve the original authorization and disclosure log rather than editing it to fit new facts.

Review patterns and exceptions

Track how often directors act, duration, medical basis, payers, information volume, rejected claims, reassessment, and closure. High use in one location or payer may reveal a broken intake, accessibility, or billing process rather than genuine temporary incapacity.

Handle payer follow-up without expanding silently

A denial, attachment request, appeal, coordination inquiry, audit, or recovery demand may arrive after the original claim. Identify whether the new event still seeks payment for the same services, whether the patient remains unable to act, and whether the existing director consent covers the recipient, purpose, information, and time. Pause when any element differs.

Record the payer's question, exact response, added records, medical-incapacity update, director approval, transmission, and outcome. A request marked urgent or “required for payment” is evidence to evaluate, not automatic authority to send the complete file.

Staff can ask who verified the medical facts, why patient action is unavailable, which payer and claim are involved, what minimum data is needed, when the route ends, and who reviews an expansion. Make those fields mandatory before an export can be released.

Example

Ten director consents are sampled. Eight have every prerequisite, payment purpose, payer, data scope, disclosure log, reassessment, and closure evidence; two extend into utilization research. Readiness is 8 of 10 consents.

Director payment-consent checklist

• document every patient-status and medical-incapacity prerequisite;
• show why communication support cannot presently enable patient action;
• name the payer, payment event, necessary information, and secure endpoint;
• complete the consent elements and record director identity and time;
• stop and reclassify after recovery, adjudication, recipient, or purpose change; and
• audit frequency, duration, scope, vendors, reassessment, and closure.

Program-director authority under paragraph (a)(2) is payment-only and temporary. It cannot become a standing operational consent.