Part 2 NPP required header

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

The rule controls the content

42 CFR 2.22 supplies the required header structure. Treat it as controlled notice text. Confirm program name, contact name or title, phone, email, prominence, and copy routes across every format.

Create one approved source block for each program or valid combined-notice scope. Record the controlling rule, exact wording, program identity, contact name or title, telephone and email, paper and electronic copy routes, effective date, reviewer, translation owner, accessibility owner, and version. Derivative templates should import or compare against that source rather than retyping the header.

Make every promise in the header operational

Test the named contact by phone and email, including voicemail, after-hours handling, interpreter support, relay service, safe callbacks, spam filtering, and staff absence. Confirm that paper and electronic copy requests reach an owner who can select the current program notice and deliver the requested format. A current address printed in the notice is not enough if the team cannot recognize a Part 2 question.

Train the contact to distinguish general questions, notice-copy requests, consent or revocation, accounting, complaint, proceeding-related concerns, and possible incidents. Preserve the original receipt and route the matter without asking the patient to repeat sensitive details across departments.

Prominence and access require testing

Check mobile, portal, email, PDF, print, large-print, screen-reader, and translated versions. The header should appear before dense terms and remain understandable without exposing that a person receives SUD services in a public setting.

Review visual and reading-order prominence at the point of use. PDF conversion, print scaling, mobile reflow, portal modals, banners, branding, and translation expansion can move or obscure the block. Confirm headings, sequence, link labels, contrast, zoom, tagging, audio or alternate-format equivalence, and complete contact information.

Protect the patient's context. Public website and physical availability should follow approved privacy-preserving design so asking for or reading the notice does not reveal program participation. Return calls and messages should use the safe route and wording selected through program policy. Do not expose a Part 2 question in a shared voicemail or notification preview.

Release and compare every active format

Use a format inventory with language, medium, location, source version, checksum or comparison result, deployment time, owner, and test. Search websites, portals, email templates, intake packets, print rooms, shared drives, vendor builders, translation memory, and local site stock for old headers. Archive historical copies with effective periods while keeping them out of current production routes.

After release, sample actual admission delivery, paper and electronic copy requests, public availability, and screen-reader output. If an obsolete contact or header circulated, identify the affected format and period, provide corrected notice where the reviewed process requires it, and preserve remediation.

Example across formats

A program maintains six notice formats. Five contain the current header and working contact; one translated PDF has an old email address. Header readiness is 5 of 6 formats. The translated version stays out of release until corrected.

The program updates the translation through qualified review, searches every public and stored copy for the old address, and tests the email from receipt through response. It preserves the failed baseline and the corrected artifact, then confirms that the old version is archived rather than publicly discoverable.

Part 2 header checklist

• Maintain one approved source block with current legal mapping.
• Identify the program, contact, phone, email, and copy routes.
• Test contact coverage, language access, disability access, and safe replies.
• Verify prominence and reading order in every format.
• Protect patients from exposure through public display or messaging.
• Compare translations, portals, PDFs, print, and vendor outputs.
• Archive prior versions and assess any defective distribution.

Owner controls

The 2024 final rule is the source history for the current rule. Maintain one approved header block, program identity, contact coverage, translation review, accessibility test, format inventory, version comparison, and release record.

Monitor active-format parity, contact-route availability, copy requests, old versions found, accessibility defects, translation lag, and unresolved remediation. Audit from delivered notices into the approved header and from every public route back to the current source. Retest after contact, program, design, vendor, legal, or notice changes.

Include the header in admission and downtime drills. Staff should be able to retrieve the current version, provide the requested format, explain the contact route, and document delivery without exposing program status. Reconcile manual copies after systems return and destroy obsolete emergency stock through approved controls.