Joint NPP participant agreement

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

Agreement follows the OHCA scope

45 CFR 164.520 ties the obligation to PHI created or received as part of each entity's OHCA participation. Verify the OHCA basis, participant, service sites, PHI flows, notice version, effective period, and responsible signatory.

Create a participant register with legal name, assumed name, covered-entity status, OHCA role, included service sites, PHI scope, participation start and end, agreement version, notice version, signatory authority, and accountable contacts. Link the public class or entity description to this controlled register. A shared brand, ownership relationship, lease, referral pattern, or contract alone does not establish inclusion.

Define what each participant agrees to follow

Attach or identify the exact joint notice and effective period. Specify that the participant will abide by its terms for PHI created or received through the stated participation. Describe how more protective participant, state, Part 2, or program requirements are handled. Keep PHI outside the arrangement under the participant's applicable notice and controls.

Use a responsibility matrix for notice approval, public posting, first-service and emergency delivery, acknowledgment effort, paper requests, websites, complaints, rights requests, contact information, incident coordination, record retention, translation, accessibility, and training. A central coordinator can perform shared work while each participant understands the duties and evidence that remain its own.

Each participant retains operational duties

Define who maintains the notice, approves revisions, provides copies, receives complaints, handles rights requests, coordinates incidents, archives versions, and reports withdrawal or scope change. The joint format should leave clear ownership rather than create a shared inbox with no accountable party.

Create service-level handoffs between participant and central teams. Preserve the original receipt time for complaints and rights requests, confirm accepted ownership, limit shared information to what is needed, and explain who communicates with the individual. Incidents affecting several participants need a coordinated lead, evidence preservation, scope analysis, and participant-specific decisions.

Govern entry, change, and exit

Before adding a participant, complete OHCA and covered-entity review, execute the agreement, map sites and data, train staff, deploy the correct notice, and test delivery and routing. Do not list an anticipated participant before the required facts and effective date are supported.

For acquisitions, renaming, new sites, service changes, and mergers, determine whether the existing class language and agreement still apply. When a participant exits, set the end date, update public and internal registers, preserve historical delivery and rights evidence, route later services to the correct notice, and resolve continuing access to shared PHI.

Audit from both directions

Sample the register into real sites, deliveries, websites, and request workflows. Then select encounters or notices and trace them back to a valid participant, site, agreement, effective period, and PHI scope. This reveals entities listed without evidence and in-scope entities operating outside the current notice.

Example with participant evidence

Seven covered entities appear in the joint notice. Six have current agreement and scope evidence; one acquisition has only a draft signature page. Participant readiness is 6 of 7 entities. Hold the acquired entity outside the published scope until its status is resolved.

The coordinator completes the acquired entity's OHCA analysis, signatory review, site map, training, and delivery tests before setting an effective date. If the entity cannot meet the criteria, it retains its separate notice pathway. The original gap remains documented in the release record.

Participant-agreement checklist

• Verify covered-entity and OHCA status before inclusion.
• Define participant, site, PHI, notice, and effective-period scope.
• Execute the agreement through an authorized signatory.
• Assign delivery, rights, complaint, incident, and archive duties.
• Preserve participant-specific state and Part 2 requirements.
• Govern additions, changes, withdrawals, and historical evidence.
• Audit the register against real operations and deliveries.

Owner controls

The HHS notice guidance offers general notice orientation. Maintain OHCA analysis, executed agreement, participant register, scope dates, revision approvals, delivery responsibilities, complaints, rights routing, and exit procedures.

Monitor participants current, agreements complete, sites mapped, notice versions aligned, handoffs accepted, scope exceptions, and exit actions. Retest after organizational, site, service, data, legal, or vendor changes. Retain prior registers and agreements so historical questions can be reconstructed.

Require periodic participant certification backed by evidence. Each entity should confirm its current sites, notice copies, delivery process, contacts, rights and complaint routes, Part 2 or state constraints, incident lead, and retained records. The coordinator reviews contradictions against central systems and opens corrective actions rather than treating a signed certification as conclusive.