Part 2 200-mile multiple-enrollment radius

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) allows disclosure to a central registry or to a withdrawal-management or maintenance-treatment program not more than 200 miles away. Paragraph (a)(3)(ii) also lets consent authorize any such program established within 200 miles without naming each one. The text does not apply the same distance phrase to the central registry itself.

Apply the distance to the right recipient

Section 2.34(a) refers to a central registry or an applicable program not more than 200 miles away. Identify recipient type before applying the radius. Do not assume the central registry itself must sit within the same distance.

Define the measurement method

Record the two locations, authoritative addresses, geocoding source, straight-line or route interpretation adopted with counsel, calculation time, boundary handling, reviewer, and result. Recheck moved or newly established sites.

Distance clears one gate

The HHS Part 2 fact sheet confirms the current rule context. Distance does not establish program type, consent, treatment trigger, permitted data, purpose, secure transmission, enrollment status, clinical need, or payment.

Classify the recipient before measuring

Determine whether the destination is a central registry or a withdrawal-management or maintenance-treatment program. Record legal or operating name, program type, site, address, status, directory source, and reviewer. A general treatment provider, pharmacy, prescriber, payer, HIE, or vendor does not become a qualifying program because it sits nearby.

Apply the radius only where section 2.34 uses it. Do not reject a central registry merely because its office is farther away, and do not let central-registry status excuse distance for a direct program recipient.

Use an approved distance method

Preserve the sending and receiving locations, authoritative addresses, geocoding source, coordinates, calculation tool, measurement interpretation, calculation date, result, reviewer, and boundary handling. Counsel should approve whether the implementation uses straight-line or another method because the regulation supplies a distance but not an operational formula.

Avoid ZIP centroids, marketing service areas, state borders, estimated drive time, or vendor defaults unless the approved interpretation and evidence support them. Recalculate moved, merged, renamed, or newly opened locations.

Apply the radius to consent

For a known program, section 2.34 requires its name and address in consent. For the unnamed-program option, the patient may authorize any withdrawal-management or maintenance-treatment program established within 200 miles. Preserve the signed language, program eligibility, location facts, and measurement used at release.

A generic “nearby providers” or national network designation cannot substitute for the rule's program and distance boundaries. Material address or ownership changes may require renewed consent or qualified review.

Keep the other gates visible

Distance does not prove a treatment trigger, current consent, allowed data, purpose, patient identity, recipient authentication, or secure transmission. Use one decision record showing all gates. Route a recipient outside the radius to another supported Part 2 pathway rather than stretching the calculation.

Other state registry, controlled-substance, pharmacy, and cross-border rules may add requirements. The HHS fact sheet gives rule context but does not resolve measurement or jurisdiction.

Monitor and audit boundary decisions

Version the location directory and retain historical effective dates. Flag recipients near 200 miles for independent review and preserve the exact calculation. Recheck when data quality, geocoding, sites, or legal interpretation changes.

Audit the denominator of direct program recipients, including approved, rejected, and held cases. Investigate distances without source addresses, repeated manual overrides, stale locations, central registries incorrectly measured, and programs whose type is unsupported.

If a corrected address or method changes the result, hold future disclosures, review prior affected events, update the directory and consent workflow, and document whether a patient-facing correction or other remediation is required.

Example

Twelve program recipients are reviewed. Nine have verified type, source and destination addresses, approved distance method, result, consent, and reviewer; three rely on ZIP centroids. Radius evidence is complete for 9 of 12 recipients.

Two-hundred-mile checklist

• classify central registry versus qualifying treatment-program recipient first;
• retain authoritative sites, addresses, coordinates, method, tool, date, and reviewer;
• use a qualified interpretation for measurement and boundary handling;
• match known-recipient or unnamed-program consent to the actual program and location;
• keep event, consent, data, purpose, authentication, and security as separate gates; and
• independently review boundary cases and audit stale locations and overrides.

The 200-mile limit is a recipient boundary, not a proxy for clinical need or a general regional sharing permission.