Part 2 central-registry member-program exchange

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(c) addresses a member program's identified-patient inquiry. When the central registry determines that the patient is enrolled in another member program, it may give each program the other's name, address, and telephone number. The two programs may then communicate as necessary to verify that the patient is enrolled in both and to prevent or eliminate the multiple enrollment.

A positive match starts the exchange

Current § 2.34(c) begins with an identified-patient query from a member program and a registry determination of existing enrollment. Preserve the query, patient match method, member status, result, timestamp, and analyst or system decision.

Keep the first response to contact details

Map the outgoing fields to program name, address, and telephone number. Do not attach a chart, medication list, diagnosis, payer record, or counseling note to the reciprocal member notification under this paragraph.

Document necessary follow-up

The HHS Part 2 fact sheet does not expand this pathway. Record each program contact, purpose, participants, questions, correction, resolution, enrollment decision, and any separate authority used for additional information.

Verify the inquiry and match

Authenticate the inquiring program, confirm current member status, and identify the patient with an approved matching method. Preserve the submitted identifiers, match criteria, possible-match handling, registry result, timestamp, operator or system decision, and source record. Do not treat a weak similarity as a confirmed enrollment.

Use a controlled process for false positives, duplicate identities, changed names, and demographic corrections. A no-match response should avoid revealing whether an unverified person appears elsewhere.

Limit the reciprocal registry response

For a confirmed existing enrollment, return the name, address, and telephone number of the existing member program to the inquirer and the same contact fields for the inquiring program to the existing program. Keep charts, medication details, diagnoses, payer information, counseling notes, and intake attachments out of this first reciprocal contact exchange.

Map and test the response fields through the registry, interface, logs, notifications, and recipient display. Verify that hidden metadata and support tooling do not add patient content or broader records.

Conduct necessary program follow-up

The programs may communicate as necessary to verify the overlapping enrollment and prevent or eliminate it. Identify authorized contacts, authenticate the channel, state the purpose, ask only the questions needed, and record the verified facts, correction, clinical or operational decision, responsible roles, and resolution.

Do not assume which program should terminate or alter care. Clinical and program leaders should address continuity, medication safety, patient communication, and applicable requirements. The privacy pathway does not decide the treatment outcome.

Protect the patient's care and record

Avoid abrupt changes based on an unconfirmed match. Use escalation for urgent safety issues and coordinate a clear patient-facing explanation through appropriate staff. Correct each affected registry and program record when the match or enrollment state was wrong.

Retain the original query, registry response, reciprocal notices, follow-up communications, decisions, corrections, acknowledgments, and closure. Apply access and retention controls to this evidence.

Reconcile and audit the workflow

Track every positive match through resolution. Include unresolved, corrected, withdrawn, duplicate, and downtime cases in the denominator. Investigate contact-only responses that included extra records, programs communicating before authentication, missing reciprocal notice, open conflicts, repeat matches, and uncorrected registry states.

Test both human and automated paths after directory, interface, matching, or registry changes.

Define a time owner for every unresolved match and escalate cases that can affect medication or continuity decisions. Closure should identify the final enrollment state, the programs informed, outstanding patient communication, and any later correction still required.

Example

Thirteen positive-match exchanges are sampled. Eleven include verified member status, match evidence, reciprocal contact fields, limited follow-up, resolution, and audit trail; two attach intake records. Compliance is 11 of 13 exchanges.

Member-exchange checklist

• authenticate the inquiring member program and verify patient-match evidence;
• send only reciprocal program name, address, and telephone number initially;
• use authenticated contacts and limit follow-up to verifying and resolving enrollment;
• protect continuity and medication decisions through qualified clinical operations;
• correct registry and program records and preserve acknowledgments; and
• audit positive matches, unresolved cases, false matches, extra fields, and repeat conflicts.

The registry establishes contact between member programs. It does not supply a full clinical record or dictate the care decision.