Part 2 intermediary participant designation

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

The intermediary must be named

42 CFR 2.31 separates the intermediary name from participant identification. A network name alone cannot silently stand for every current and future participant. Decide whether the consent names members or uses the limited general designation.

Explain the intermediary's role, participant choices, treating-provider limitation, disclosure-list right, consent scope, and revocation in patient-facing language. The patient should know whether named participants are fixed on the form or a supported general designation can reach qualifying treating providers. Avoid interface language that presents all network members as one recipient.

Maintain an intermediary and participant register

Record intermediary legal and public name, systems, active dates, privacy contact, member roster, participant identifiers, participant type, relationship data source, service dates, consent mappings, event logs, export capability, and last review. Preserve roster and relationship history for the life of applicable consent and rights requests.

Participant entry should require qualified organization and role review. Network enrollment, directory presence, contract execution, or technical connectivity alone does not establish the patient-specific treating-provider relationship required for the general designation.

Give patients a usable way to ask which participants received their records, and route that request to an owner who can assemble the response. The supporting system should reconcile participant identifiers across renamed practices, merged organizations, and replaced platforms. Periodic test requests can expose missing events or stale relationships before a real patient depends on the list.

Treating-provider relationship is a gate

For a general designation, verify the relevant participant's relationship to the patient before disclosure. Define relationship evidence, effective dates, episode status, participant changes, record scope, consent status, and how a patient can request the intermediary's disclosure list.

Use current clinical and operational evidence such as accepted referral, scheduled or completed treatment, established care episode, or another approved relationship fact. Define when the relationship begins and ends and how retroactive corrections, transfers, provider departure, inactive episodes, and merged identities are handled. A historical directory or payer listing is weak evidence of current treatment.

Link the relationship decision to patient, participant, consent, purpose, record scope, disclosure event, reviewer, and source. Preserve the original evidence so the program can answer the intermediary-list right across the three-year period.

Gate every disclosure through the full consent

Confirm intermediary identity, named or general participant route, treating relationship where required, patient, record description, purpose, expiration, signer authority, revocation, and actual recipient. Carry Part 2 provenance and restrictions through the intermediary. An eligible participant still cannot receive records beyond the consent's meaningful scope or purpose.

Use technical rules that block participants without current evidence and require review for unknown or conflicting states. Test new participants, departed providers, changed organizations, proxy access, bulk exchange, emergency paths, and downtime. Keep manual exceptions restricted and auditable.

Support rights and revocation

Maintain complete disclosure events so the intermediary can produce the required list. Record recipient, amount and kind of records, purpose, time, consent, relationship evidence, source, and correction history as applicable. Test export before vendor change or platform retirement.

Propagate consent revocation to the intermediary, participants, scheduled exchange, and downstream access as current rules require. Preserve earlier supported disclosures. Hold unresolved identity or propagation cases with an owner instead of treating a central revoked flag as complete.

Example with participant checks

Twelve participant disclosures reach review. Ten have current treating-provider evidence; two have only historical directory entries. Participant eligibility is 10 of 12 disclosures.

The intermediary blocks both releases, seeks current relationship evidence through the approved workflow, and reviews whether the directory rule affected prior disclosures. One participant qualifies after a documented care event; the other remains ineligible. The result and correction remain visible in the audit log.

Intermediary-designation checklist

• Name the intermediary and identify the participant structure.
• Explain named members, general designation, and patient rights clearly.
• Maintain dated participant, relationship, consent, and event registers.
• Verify current treating-provider evidence where required.
• Apply every other consent and record-scope condition.
• Produce disclosure-list data and preserve migration exports.
• Propagate revocation and hold unresolved relationships.

Owner controls

The 2024 final rule explains the intermediary alignment. Maintain the intermediary register, participant roster, relationship evidence, consent language, release checks, list-of-disclosures support, revocation handling, and audits.

Monitor participant eligibility, relationship age, disclosures blocked, unknown states, consent and revocation propagation, list-source coverage, roster changes, and corrections. Audit from every intermediary disclosure back to current relationship and consent, then from active participants into sampled event evidence.