Part 2 discretionary restriction decision

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.26(a)(2) says a Part 2 program generally is not required to agree to a requested TPO restriction. Paragraph (a)(6) creates the important exception: the program must agree when every paid-in-full health-plan condition is met. Discretion begins only after the request has been permitted, understood, and screened for that mandatory route.

Start with the exception to discretion

Under 42 CFR 2.26(a)(2) and (6), most requests may be accepted or declined, while a qualifying health-plan restriction is mandatory. Intake should ask about recipient, payment or operations purpose, required-by-law status, item or service, payer involvement, and payment in full.

Use decision criteria that can be explained

Document clinical continuity, system capability, downstream recipients, emergency access, legal requirements, other Part 2 permissions, operational feasibility, alternatives, and the patient's stated concern. Apply approved criteria consistently and route legal questions.

Record the exact outcome

The HHS Part 2 fact sheet describes the restriction right at a high level. The practice record should state agreed, partly agreed, declined, or mandatory; define scope and effective time; give the patient an understandable response; and preserve escalation or complaint routes.

Screen the mandatory path before applying discretion

Confirm requester authority, recipient, purpose, required-by-law status, item or service, record scope, payer involvement, charge, adjustments, payment source, full-payment status, refunds, reversals, and timing. If the recipient is a health plan, the purpose is payment or operations, disclosure is not otherwise required by law, and the record pertains solely to a fully paid item or service, route the request as mandatory.

Do not place the burden on the patient to recite every regulatory element. Billing, privacy, and counsel should resolve facts the program controls.

Use approved decision criteria

For a discretionary request, assess the patient's concern, records and purposes, clinical continuity, care coordination, billing and payer dependencies, existing consents, system capability, downstream recipients, emergency treatment, required disclosures, other Part 2 permissions, vendor behavior, operational risk, and available narrower safeguards. Apply the same criteria across comparable cases.

Avoid reasons based on diagnosis, treatment choice, payment source, complaint history, or inconvenience alone. Document case-specific facts rather than a stock “cannot accommodate” response.

Consider a precise alternative

If the exact request cannot be administered safely, consider whether a narrower record set, recipient, purpose, date range, route, or duration would address the concern. Explain the alternative and record whether the patient accepts it. Do not convert a rejected request into a different restriction without agreement.

Partial agreement creates an enforceable operating duty for the accepted scope. Define it clearly enough that clinical, billing, privacy, records, technical, and vendor teams can implement and test it.

Record and communicate the decision

Use statuses such as mandatory, agreed, partly agreed, declined, pending facts, or withdrawn. Preserve the request, identity and authority, mandatory-path screen, facts, criteria, rationale, decision-maker, scope, effective time, patient response, complaint or review route, implementation owner, and closure.

Communicate in accessible language. Distinguish what the program will control from what a downstream recipient or separate entity controls. The HHS fact sheet confirms the current restriction-right framework but does not replace the provision-specific decision.

Implement or close deliberately

For accepted scope, configure controls, notify affected roles, test automated and manual routes, and retain evidence before marking complete. For declined scope, verify no accidental restriction remains and preserve the patient response. Reopen the decision when payment, law, clinical need, systems, recipients, or other material facts change.

Audit decisions for mandatory screening, consistency, explanation, partial alternatives, timely communication, implementation, complaints, and overrides. Correct criteria or training when similar cases receive unexplained different results.

Example

Eleven decisions are audited. Eight classify mandatory versus discretionary, state rationale, give notice, assign implementation where accepted, and close the request; three record only 'cannot accommodate.' Completeness is 8 of 11 decisions.

Discretionary-decision checklist

• verify every paid-in-full health-plan element before applying discretion;
• document the patient's concern, requested scope, facts, systems, and dependencies;
• use consistent approved criteria and avoid generic or discriminatory reasons;
• offer and document a precise alternative when it addresses the concern;
• communicate outcome, rationale, effective scope, complaint route, and ownership; and
• implement accepted portions, remove accidental controls, retest changes, and audit consistency.

Discretion is a governed decision, not a reason to ignore the request. The mandatory paragraph (a)(6) route must remain separate and visible.