Part 2 unnamed-program 200-mile consent option

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.34(a)(3)(ii) permits written consent to authorize disclosure to any withdrawal-management or maintenance-treatment program established within 200 miles of the disclosing program. This class option is distinct from paragraph (a)(3)(i), which requires the name and address of each central registry and each known program. The geographic wording does not authorize disclosure to every health care organization within the radius.

Define the class precisely

Current § 2.34(a)(3)(ii) permits the geographic program class. The consent should make the covered class understandable and connect it to the multiple-enrollment purpose. Do not expand it to every provider, pharmacy, plan, registry, or service in the area.

Resolve membership at release time

For each recipient, verify program type, establishment and address, distance, current operation, secure route, disclosure trigger, patient and consent match, permitted fields, and purpose. Preserve the source and calculation used on that date.

Keep general consent rules active

The written consent must still satisfy 42 CFR 2.31. A geographic class does not repair missing patient identity, authorized discloser, meaningful information, purpose, revocation, expiration, signature authority, or date.

Decide whether the class option fits

Use the unnamed class when a qualifying program may need to receive the narrow multiple-enrollment disclosure but is not known when consent is signed. If the recipient is already known, list its name and address through the known-recipient route. Keep central registries named because the 200-mile class refers to withdrawal-management and maintenance-treatment programs.

Document why the class option is operationally needed. Convenience alone should not turn a specific, foreseeable recipient into an unnamed one.

Verify each recipient at release

Confirm that the destination is an operating withdrawal-management or maintenance-treatment program, that its relevant site is established within 200 miles, and that the signed language covers it. Preserve authoritative name, address, program type, site, directory source, distance method, calculation, date, reviewer, and secure routing identifiers.

A nearby pharmacy, prescriber, payer, hospital, vendor, HIE, or general SUD provider does not qualify merely because it may participate in care. Escalate uncertain program classification and boundary cases.

Match the class to a complete consent

The consent must also satisfy 42 CFR 2.31. Validate the patient, authorized discloser, meaningful records, purpose, recipient designation, revocation, expiration, signature, date, and representative authority. Preserve the exact language the patient saw and any accessibility or interpreter support.

Avoid vague phrases such as “nearby providers” or “regional partners.” The form should identify the qualifying program class and the 200-mile boundary in language the patient can understand.

Run the full disclosure gate

At release, verify the listed treatment event, patient match, current consent, recipient class, distance, permitted identifying and medication fields, multiple-enrollment purpose, secure transmission, and approval. The geographic class solves only one recipient-designation issue.

If the recipient has moved, merged, changed type, or opened a different site, recalculate and decide whether the consent still applies. Hold the disclosure when evidence is missing rather than relying on a directory search radius.

Audit class-based releases

Review approved, rejected, held, corrected, and retried releases. Look for known programs routed through the unnamed option, programs outside the radius, unsupported provider types, stale addresses, inconsistent distance methods, expired consent, or payloads broader than section 2.34 permits.

Keep historical location and consent versions so reviewers can reproduce the decision as of the disclosure date.

If a program later becomes known, update the recipient directory and future consent workflow without altering the earlier signed form. Review whether open release requests still fit the class and preserve the reasoning for either continuing or seeking a new consent.

Example

Fifteen releases rely on the unnamed class. Twelve verify recipient type, establishment, distance, trigger, consent, limited payload, and evidence; three use a provider directory radius alone. Release readiness is 12 of 15 releases.

Unnamed-program consent checklist

• determine whether the recipient was genuinely unknown when consent was signed;
• keep central registries and known programs on the named-recipient path;
• verify program type, operating site, address, and establishment within 200 miles;
• preserve complete section 2.31 consent and the exact class language;
• recheck trigger, payload, purpose, route, distance, and consent at release; and
• audit class use, recipient changes, boundary decisions, holds, and corrections.

The class is a bounded consent option, not a regional permission for general information sharing.