Part 2 first-service notice delivery

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

First service is a release gate

42 CFR 2.22 covers in-person and electronic service. Connect scheduling and service records to the notice workflow while keeping emergency treatment available. A missing signature should not be recast as a universal consent requirement.

Define first service for each program, service line, site, and channel. Scheduling, inquiry, screening, admission, assessment, treatment, telehealth connection, portal request, and claim event may occur at different times. Qualified Part 2 and operational owners should identify the trigger and supporting source record, including transfers, readmissions, new episodes, and services after organizational change.

Select the correct notice before the event

Map program, entity, service, jurisdiction, language, accessible format, joint-notice scope, and effective date to the approved notice. Preserve the version, patient or representative, route, send or provision time, result, owner, and fallback. Keep historical versions available for review while preventing them from current selection.

Align the Part 2 admission communication and the full patient notice without merging their timing or content. A patient may have received the confidentiality communication at admission and still need the full notice by first service. A signature documents only what the approved workflow says it documents.

Electronic first service has its own automation

When the first service is electronic, the rule also addresses automatic and contemporaneous electronic notice in response to the first request for service. Test the trigger, notice version, accessibility, email or portal result, and paper-copy route.

Map the sequence from first electronic request into automated delivery. Preserve request ID, patient or prospective patient, program, request time, notice version, generation time, route, response event, known failure, and fallback. Test web, app, portal, email, telehealth, API, chatbot, and vendor intake paths that can start a service request.

Make the notice available without requiring the patient to finish portal enrollment or sign a consent first. Support screen readers, mobile reflow, language, large print, and paper requests. A successful screen render should be reproducible through system logs or equivalent evidence.

Reconcile the complete first-service cohort

Run from service records into notice evidence and from notice deliveries back to qualifying service or request events. Include canceled-to-completed changes, same-day walk-ins, home and community visits, telehealth, transfers, downtime, and duplicate identities. Separate notice generated, attempted, delivered or provided, failed, retried, and supported final disposition.

Create an exception queue for wrong program, missing version, known electronic failure, returned mail, unsafe address, language or format unavailable, identity mismatch, and system outage. Assign next action and escalation. Keep timely delivery and eventual remediation as separate measures.

Use a distinct emergency branch

Emergency service proceeds through the current emergency timing rule and a prompt post-emergency notice task. Do not delay necessary treatment for notice or acknowledgment. Preserve the emergency context, practical opportunity, notice version, route, delivery, and unresolved state.

During downtime, use a restricted manual register and current controlled copies. Enter original event times after restoration and reconcile every record before closing the outage.

Example with a locked cohort

Forty-two patients have a first service during the week. Forty receive the current notice on time; two failed electronic deliveries enter paper fallback. Timely provision is 40 of 42 patients.

The program verifies safe paper routes, mails both current notices, and records one completed delivery and one return. Eventual supported completion becomes 41 of 42, while timely provision remains 40 of 42. The return stays open with an owner.

First-service checklist

• Define first service and first electronic request for each workflow.
• Select the current program, language, accessibility, and joint notice.
• Keep admission communication, full notice, and acknowledgment distinct.
• Automate contemporaneous electronic response with event evidence.
• Preserve paper-copy rights and failed-delivery fallback.
• Reconcile every service into a timely or exception disposition.
• Route emergencies and downtime through controlled branches.

Owner controls

The 2024 final rule explains the aligned timing. Use a first-service definition, notice-version mapping, automatic trigger, accessible formats, failure detection, emergency branch, delivery evidence, and exception aging.

Monitor cohort completeness, current-version accuracy, same-event timing, electronic response latency, known failures, paper fallback, emergency follow-up, and unresolved cases. Test after scheduling, intake, telehealth, EHR, portal, vendor, notice, or program changes. Protect the audit queue from exposing Part 2 status broadly.

When a service event or identity is corrected later, preserve the original timestamps and append the supported delivery decision. Do not rewrite the service date to make late provision appear timely. Report cohort adjustments, timely completion, and eventual remediation separately.