Part 2 peer-program enrollment verification

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(e) applies when a withdrawal-management or maintenance-treatment program receives information under paragraph (a) and determines that the patient is already enrolled. The receiving program may communicate with the program that made the disclosure as necessary to verify that no error occurred and to prevent or eliminate multiple enrollment. It is a purpose-limited follow-up, not general record access.

Confirm the prerequisite state

Current 42 CFR 2.34(e) starts after the receiving program obtained a disclosure under § 2.34 and determined existing enrollment. Preserve program types, original event, consent, patient match, source, recipient, determination, time, and responsible reviewer.

Keep communication necessary

Define the questions and fields needed to verify error and resolve duplicate enrollment. Record participants, program contact information, enrollment facts, medication details only when supported by the applicable paragraph, corrections, decision, and closure. Avoid full-record exchange.

Maintain the consent and purpose chain

The original disclosure depends on consent consistent with 42 CFR 2.31. Peer verification does not create a new general care, payer, analytics, research, employment, or law-enforcement route. Use separate verified authority for another purpose.

Confirm the pathway prerequisites

Document that the recipient is the qualifying withdrawal-management or maintenance-treatment program, that it received the information under section 2.34(a), and that it determined an existing enrollment. Link the patient, sender, recipient, original treatment event, consent, distance where applicable, limited payload, receipt, match evidence, and decision.

Do not use paragraph (e) after a general referral, payer notice, PDMP query, or unrelated record exchange. Route those facts through their own authority analysis.

Verify the patient and enrollment states

Use approved identity matching and authoritative enrollment sources at both programs. Preserve identifiers used, possible-match handling, program type, acceptance, interruption, resumption, termination, medication or dosage state where relevant, effective dates, record versions, and responsible roles.

Avoid treatment changes based on a weak demographic match. Escalate duplicates, aliases, changed identities, delayed documentation, and conflicting effective dates.

Limit the communication to necessity

Define the questions and fields needed to determine whether an error occurred and to prevent or eliminate the duplicate enrollment. Authenticate contacts and secure the channel. Record participants, purpose, facts exchanged, source, corrections, decision, and closure.

Do not attach full intake records, counseling notes, diagnoses, payer data, unrelated medications, or broad histories. Use separate verified authority if additional information is necessary for another purpose.

Protect continuity and clinical safety

The privacy pathway does not decide which program continues treatment or which medication plan is appropriate. Qualified clinical and program leaders should address immediate safety, continuity, medication reconciliation, patient communication, handoff, and applicable program or state requirements. Avoid abrupt termination while facts remain unresolved.

Assign an owner and urgency based on patient risk. Keep privacy, clinical, and operational decisions linked without allowing one role to exceed its scope.

Correct and reconcile both sides

When the match or enrollment information is wrong, correct the source program, receiving program, and any related registry or message as appropriate. Link original and corrected records, notify authorized recipients, obtain acknowledgment, and verify that automation will not resend the stale state.

Audit positive matches, false matches, resolved and open conflicts, full-record attachments, repeated contacts, corrections, patient-impact events, and downtime communication. Include blocked and abandoned cases in the denominator.

Set a resolution record that both programs can understand: the verified patient, enrollment states and dates, issue found, facts exchanged, clinical and operational owners, final decision, patient communication, corrections, acknowledgments, and remaining follow-up. Avoid vague closure such as “handled by phone.” If the programs disagree, preserve each source and escalate rather than forcing one system to mirror an unsupported conclusion. Review recurring conflicts for intake, termination, timing, identity, or interface defects that can be fixed upstream.

Example

Fourteen peer contacts follow positive enrollment determinations. Twelve preserve the original qualifying disclosure, consent, match evidence, necessary questions, participants, correction, resolution, and closure; two attach full intake records. Compliance is 12 of 14 contacts.

Peer-verification checklist

• prove the qualifying paragraph (a) disclosure and receiving program type;
• verify patient identity and enrollment state at both programs;
• limit authenticated communication to checking error and resolving enrollment;
• separate privacy authority from clinical continuity and medication decisions;
• correct source, recipient, registry, and automated state where necessary; and
• audit open, resolved, false-match, repeated, corrected, and patient-impact cases.

Peer communication should produce a verified enrollment resolution with the least additional Part 2 information needed for that purpose.