Joint NPP for an OHCA

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

The notice scope needs reasonable specificity

Under 45 CFR 164.520, the joint notice describes participating entities or classes and service sites or classes. If applicable, it states that participants share PHI as needed for treatment, payment, or health care operations related to the arrangement. Preserve the OHCA basis and participant agreement.

Document why the arrangement qualifies, which entities participate, which sites are included, and which PHI is created or received through participation. Use class descriptions only when a reader can reasonably understand coverage. Maintain signed terms, effective dates, contacts, and the version each participant follows.

Describe applicable treatment, payment, and operations sharing accurately. Avoid implying that the joint notice creates authority beyond the Privacy Rule or other applicable law. Keep Part 2 records and duties under their separately reviewed requirements.

Participation does not erase separate duties

Map which entity and site each notice covers, who delivers it, how revisions are approved, which PHI arises through participation, and how complaints and contacts route. The joint-notice permission does not remove the separate obligations and rights tied to records subject to Part 2.

Create a participant and site register with ownership for first-service delivery, emergency delivery, posting, websites, paper copies, acknowledgment effort, complaints, individual rights, and record retention. One valid delivery can satisfy distribution for the entities covered by the notice, but evidence must show that the individual, encounter, version, and participant were within scope.

Govern arrivals, departures, and revisions

Before a new participant relies on joint delivery, update the agreement, scope, notice, registers, systems, sites, and channels as required. For departures, preserve historical coverage and establish the correct later notice. Do not let an acquisition automatically inherit inclusion.

Set approval and release rules for material revisions. Test every participant website, physical site, intake path, complaint route, and vendor. Preserve prior versions and effective periods.

Example across participating sites

A joint notice covers nine sites. Eight are listed directly or through a valid class description; one newly acquired site has no documented inclusion. Scope coverage is 8 of 9 sites. The new site needs a valid notice route before relying on joint delivery.

The acquired site can use its own correct notice while the arrangement reviews inclusion. Once properly added, test delivery and posting before moving it into the joint numerator. Historical deliveries remain tied to the notice actually in effect.

Joint-notice checklist

• Document OHCA basis, participant agreement, entities, sites, and PHI scope.
• Describe applicable sharing accurately and preserve Part 2 boundaries.
• Assign delivery, posting, website, paper, complaint, and rights roles.
• Link delivery evidence to participant, encounter, person, and version.
• Control acquisitions, departures, revisions, and effective dates.
• Test all sites, web properties, channels, contacts, and vendors.
• Preserve participant registers, prior versions, and scope decisions.

Owner controls

HHS guidance summarizes the joint-notice option. Maintain participant and site registers, signed terms, delivery evidence, complaint routing, current contacts, version approval, acquisition and departure workflow, and periodic scope tests.

Monitor scope coverage, participant attestations, delivery evidence, stale contacts, and sites using the wrong version. Audit from the register to operations and from actual deliveries back to valid joint scope. Re-test after organizational and legal changes.

Define governance for disputes among participants. The agreement should identify who interprets scope, approves revisions, receives complaints, coordinates individual rights, retains delivery evidence, and manages incidents involving shared PHI. A central office can coordinate while each covered entity still understands the duties that remain its own. Maintain escalation when a participant's state law, Part 2 role, or separate notice creates a conflicting requirement.

Audit encounters that cross participants. Verify the person received a valid joint notice once through an in-scope participant and that later sites can retrieve the evidence. Avoid repeated delivery solely because systems cannot share proof, but do not assume another entity delivered it without evidence. Review departures so historical records remain tied to the former arrangement and later services use the correct notice. Keep complaint and contact information current across every public format.

Maintain a controlled exception register for participants, sites, or services outside the joint scope. Staff need a simple way to identify when a separate notice and delivery record are required. Test mergers, new service lines, temporary locations, and contracted relationships before treating them as covered by the arrangement. If the legal or operational facts are uncertain, use an escalation state rather than expanding the notice by assumption. Reconcile the participant register to real scheduling, billing, and site records often enough to catch organizational drift.