Joint NPP covered-entity scope description

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

Reasonable specificity is the standard

45 CFR 164.520 permits entity descriptions or class descriptions. A class can support a changing organization, while vague labels such as “our partners” make scope difficult to understand and operate.

Choose a description that an ordinary reader and staff member can apply. A named list offers specificity but requires prompt revision. A class can remain current as participants change if it uses objective, understandable criteria. Terms such as affiliated, partner, network, or related should be defined by covered-entity and OHCA facts rather than brand familiarity.

Build the public description from verified records

Start with the executed participant agreement and OHCA analysis. For each entity, document legal and assumed names, covered-entity type, qualifying arrangement, included sites, service role, PHI scope, participation dates, current notice, state or Part 2 constraints, and public contact. Group entities only when a class description accurately covers the shared facts.

Compare the proposed language with corporate, licensing, enrollment, contracting, site, and privacy records. Contractors, management companies, landlords, software vendors, billing companies, and referral partners may work closely with participants without becoming covered entities in the joint notice. Record exclusions and the reason staff might otherwise confuse them.

Connect public language to a controlled register

Keep legal names, assumed names, entity type, OHCA role, sites, participation dates, notices, acquisition or divestiture status, and accountable contact. The public notice can describe a class while the internal register proves which entities met it at a given time.

Version the register and public description together. Record the exact participant population and class criteria for each effective period. When a reader asks whether an entity was covered during an earlier service, staff should be able to use the historical register rather than today's roster.

Test the description with realistic names

Give reviewers legal names, brands, locations, departments, contractors, and recently acquired or departed entities and ask them to decide whether each falls within the notice. Record uncertainty and inconsistent answers. If trained staff cannot apply the class, revise it or add an accessible current participant list with appropriate governance.

Check every format and language. Confirm that websites, paper copies, portals, site displays, intake packets, and accessible notices use the same scope wording and point to a monitored source. Avoid links that require authentication or expose a changing roster without an archive.

Manage organizational change before public release

For acquisitions or new entities, complete covered-entity, OHCA, agreement, site, PHI-flow, training, and notice-delivery review before inclusion. For closure or divestiture, set the end date, update the current notice and register, preserve historical evidence, and determine which notice applies to continuing services or records.

Renaming does not automatically change legal scope, while a legal conversion or service change may. Track both legal and public names with effective periods. Route uncertain entities to qualified review rather than stretching an existing class to avoid a revision.

Example with entity mapping

A notice uses three entity classes covering 18 entities. Seventeen map clearly; one management company lacks covered-entity and OHCA evidence. Entity-scope completeness is 17 of 18 entities. Remove or clarify the uncertain record before release.

The team excludes the management company from the participant register and explains its operational role separately where needed. It searches existing notice formats for wording that implied inclusion and corrects those versions. A follow-up test confirms that staff can distinguish the company from the covered participants.

Entity-scope checklist

• Verify each organization's covered-entity and OHCA basis.
• Use named entities or objective, understandable class criteria.
• Link public language to a dated participant register.
• Distinguish participants from contractors and business associates.
• Test legal names, brands, acquisitions, departures, and edge cases.
• Align all formats, languages, sites, and request routes.
• Preserve historical scope and govern every roster change.

Owner controls

Use the HHS notice guidance with the operative rule. Test the description against new entities, renamed entities, acquisitions, closures, contractors, and business associates. A contract relationship alone does not place an organization inside the joint notice.

Monitor entities mapped, class tests passed, scope questions, unapproved additions, format parity, stale registers, and organizational changes. Audit from the public class into participant evidence and from actual entities or encounters back to valid scope. Retain each register version and correction record.

Assign every uncertainty a temporary public and operational instruction so staff do not expand scope by assumption while qualified review is pending.