Part 2 vital-statistics disclosure route

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

Current rule checkpoint

Live 42 CFR 2.15(b)(1) leaves Part 2 restrictions inapplicable to patient-identifying cause-of-death information disclosed under laws requiring collection of death or other vital statistics. The disclosure remains bounded by the actual collection law, required fields, recipient, and purpose. The HHS fact sheet identifies February 16, 2026 as the compliance date for the amended framework.

Mandatory fields come from the governing source

The current Part 2 provision points to laws requiring vital-statistics collection. Use the current jurisdictional form, instructions, data dictionary, certifier rules, electronic system, amendments, rejection process, and retention requirements.

Report only the required cause-of-death information

Map each requested field to the legal collection requirement and responsible professional. Preserve clinical authorship and source. Avoid filling uncertain clinical conclusions from administrative assumptions or extending the submission to unrelated records.

Operational controls protect accuracy

Verify decedent identity, case number, certifier, recipient, access, secure submission, time, acknowledgment, rejection, correction, audit log, and completion. Route conflicts or expanded requests to privacy counsel and the qualified medical role.

Build from the current jurisdictional requirement

Identify place of death, residence, reporting jurisdiction, responsible facility or professional, current statute and regulation, official form or electronic system, data dictionary, instructions, submission deadline, amendment rules, and retention duty. Record version and effective date so an obsolete local form cannot become the source of truth.

Verify which entity and individual must report or certify. The funeral director, attending clinician, medical examiner, coroner, registrar, hospital, facility, or program may have different responsibilities. Authentication and role verification should occur before protected facts are shared.

Map and validate each field

Create a field-level crosswalk from legal requirement to source record and accountable professional. Check decedent identifiers, dates, location, certifier, cause and manner of death, contributing conditions, interval, injury details, and other required fields. Use the jurisdiction's definitions rather than local shorthand.

Separate known fact, clinical opinion, pending test, and unknown. Do not infer a cause from diagnosis, medication, program participation, or administrative coding. Route medical conclusions to the authorized certifier and preserve the original source and later correction.

Limit the submission to the reporting route

Send only the fields, attachments, and explanation supported by the vital-statistics law and official process. Review comments, free text, scanned records, metadata, hidden fields, and other patients' information. A request for an entire SUD record or a secondary investigative use requires separate analysis.

Use an authenticated portal or approved secure method. Restrict user access, verify recipient, log submission, preserve acknowledgment, and monitor rejection or correction messages. Avoid putting identifying SUD detail into support tickets or email subject lines.

Reconcile rejection, amendment, and audit history

Assign owners for rejected fields, contradictory sources, late reports, amended cause findings, duplicate cases, and reopened inquiries. Preserve each submitted version, reason for change, approver, transmission, acknowledgment, and effective status rather than overwriting the original.

Audit a sample for current legal source, field accuracy, certifier authority, minimum scope, timeliness, secure delivery, acknowledgment, and correction. Fix both the record and the form, mapping, or training that caused the error.

Prepare for system and deadline failures

Document the approved fallback for portal outage, rejected credentials, unavailable certifier, late laboratory result, contradictory identity, duplicate case, and approaching statutory deadline. The fallback should name who may submit, which secure channel is allowed, how the registrar is contacted, and how the electronic record is reconciled later.

Do not move identifying SUD information into ordinary email, consumer file sharing, or an unrestricted support ticket to solve a technical problem. Use minimum information when obtaining technical help and record any emergency method.

Reviewers can ask whether the form and data dictionary were current, each field came from an authoritative source, the proper certifier approved the medical conclusion, the official system accepted it, and every correction reached the registrar. Preserve evidence for each answer.

Example

Ten vital-statistics submissions are sampled. Eight have legal source, current form, required fields, certifier, recipient, acknowledgment, and correction evidence; two use an obsolete field list. Readiness is 8 of 10 submissions.

Vital-statistics checklist

• identify the governing jurisdiction, current law, form, instructions, and deadline;
• verify reporting entity, certifier, registrar, and recipient roles;
• map each required field to an authoritative source and accountable professional;
• exclude unrelated records, unsupported conclusions, and excess attachments;
• secure, log, acknowledge, reject, correct, and version every submission; and
• start a separate review for expanded investigative or record requests.

The exemption follows the legally required vital-statistics route. It does not create a general post-death disclosure permission.