Part 2 paper-or-electronic notice copy right

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

The patient chooses the usable form

42 CFR 2.22 includes the copy right in the notice and electronic-notice provisions. Confirm the requested form and accessible needs. Avoid making portal enrollment or a new electronic agreement the only way to obtain a public notice.

Publish simple phone, email, office, mail, web, or portal instructions under program policy. Accept ordinary requests without requiring a diagnosis, reason, detailed treatment history, or new consent. Ask only for the program or notice needed, paper or electronic choice, language or accessible format, safe route, and delivery information required for that route.

Keep public access and patient privacy together

The notice is public, while a request can reveal that a person is connected with a Part 2 program. Use safe callback, email, portal, pickup, and mailing procedures. Avoid voicemail, envelope, sender name, notification preview, or public pickup practices that disclose SUD service context unnecessarily. Limit request-log access and collect only operational facts.

Provide a route for any person seeking the public notice, while applying qualified identity or authority checks to separate patient-right actions. Staff should recognize when a copy request becomes a complaint, accounting, consent question, revocation, or legal concern and preserve the original receipt during transfer.

Current version and delivery are separate controls

Map program, notice version, effective date, language, format, request time, owner, send time, delivery result, and fallback. Retain prior notices in the controlled archive while keeping them out of active public routes.

Use a notice registry with program, entity, language, format, effective period, accessibility review, public source, approved print file, checksum, owner, and archive location. When several program or historical notices may apply, use limited clarification and a trained selection rule. Do not choose the newest filename automatically.

Control central and local print stock, preassembled packets, shared drives, websites, portals, vendor builders, translations, and accessible variants. After revision, remove old production copies while preserving historical artifacts in a clearly labeled archive.

Follow the request to a supported outcome

Useful states include received, selection needed, paper prepared, electronic prepared, mailed, pickup available, transmitted, failed, returned, alternate format pending, replaced, and closed. Preserve the exact version, format, route, time, and final disposition. A generated email or print job is an attempt; known failure or returned mail needs a new action.

Electronic delivery needs accessible content and a route that the requester can open. Paper fulfillment needs current stock, safe address, chain of custody where applicable, returns, and replacement. A person who receives electronic notice can still request paper without withdrawing an electronic preference unless the person separately asks to change it.

Test every form from discovery through receipt

Mystery-shop web download, phone, email, office pickup, paper mail, large print, screen reader, translation, and alternate-format intake. Record discovery route, program selected, version, staff response, delivery, accessibility, privacy, and correction. Include downtime and staff-absence scenarios.

Example across request paths

A program tests paper pickup, mail, email, web download, large print, and screen-reader PDF. Five return the current notice; mail uses an old insert. Route readiness is 5 of 6 paths.

The owner quarantines the old insert, searches vendor and site inventory, assesses requests fulfilled during the affected period, and mails the corrected notice where appropriate. A follow-up test confirms version, safe envelope, fulfillment evidence, and return handling. The failed baseline remains documented.

Notice-copy checklist

• Offer understandable paper, electronic, language, and accessible choices.
• Avoid unnecessary identity, diagnosis, purpose, or portal requirements.
• Protect request and delivery routes from exposing program participation.
• Select from a controlled current-version registry.
• Record request, version, format, route, result, and fallback.
• Remove obsolete active copies while preserving the archive.
• Test every route after notice, contact, vendor, or system changes.

Owner controls

The 2024 final rule supports the current notice alignment. Use a version registry, request script, print controls, accessibility review, language access, link tests, delivery evidence, and exception queue.

Monitor route availability, requests fulfilled, correct-version delivery, safe communication, format needs, failures, returns, old stock, and unresolved cases. Audit from requests into delivery evidence and from delivered copies back to the approved source. Keep public-notice data separate from protected record-request data.

Maintain a continuity package with approved electronic and print sources, neutral packaging instructions, language and accessibility contacts, alternate fulfillment, and a restricted manual log. During outage, assign temporary ownership and reconcile every request after restoration. Refresh the package with each material revision so emergency readiness never becomes an obsolete-copy source.