Part 2 relevant-facts-only minor safety disclosure

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.14(c) limits this minor-safety route to facts relevant to reducing the substantial threat to life or physical well-being identified by the program director. The rule names a parent, guardian, or other person authorized under state law as the recipient. The HHS fact sheet identifies February 16, 2026 as the compliance date for the amended framework.

Risk reduction defines the scope

Current 42 CFR 2.14 permits facts relevant to reducing the threat. Identify the threat, person at risk, recipient, protective action, information element, reason it helps, timing, method, and decision owner before sharing when circumstances allow.

Clinical history needs a fact-level rationale

A current medication, allergy, location, access need, communication method, recent event, warning sign, or safety instruction may support the response. Older notes, unrelated diagnoses, family history, billing data, and complete assessments require separate justification.

Document emergency judgment without slowing care

Use a rapid disclosure tool that captures the required findings, recipient authority, facts shared, reason, time, responder, method, instructions, confirmation, and follow-up. Preserve the original record and any corrections.

Build the scope from the protective action backward

Define the threat, person at risk, authorized recipient, action expected, and time available. For each proposed fact, ask what the recipient will do differently because they know it and how that action could reduce the threat. Exclude information with no clear connection.

A location, immediate warning sign, relevant medication or allergy, access to means, communication need, recent event, supervision instruction, or crisis contact may be relevant in one situation. A full assessment, historical diagnosis, unrelated treatment episode, family narrative, billing record, or broad progress-note set usually requires a more specific justification than convenience.

Use a rapid fact-selection process

List proposed facts in a restricted worksheet or response note with columns for source, accuracy check, protective purpose, recipient, and include or exclude decision. Have the director or authorized response lead confirm the final set when circumstances permit. Avoid copying entire notes simply because they contain one relevant sentence.

Verify recipient identity and authority, choose a secure and usable channel, state the requested action clearly, use accessible language, and confirm receipt. Separate verified facts from uncertainty and correct material errors promptly.

Record what was shared and what happened

The disclosure log should capture both paragraph (c) findings, recipient authority, exact facts communicated, omitted attachments, reason for each fact, date and time, method, sender, instructions, confirmation, response, and follow-up. Preserve the original clinical and operational records.

If the recipient asks for more, start a new authority and relevance review. Reassess when the threat, recipient, facts, or protective plan changes. After the event, evaluate whether the selected information helped, whether excess information escaped, and which workflow or training changes are needed.

Do not rely on a broad record with a warning label

Marking a chart “confidential,” adding a cover sheet, or asking the recipient to ignore unrelated pages does not narrow what was disclosed. Extract or communicate the selected facts in a controlled format. Check attachments, metadata, hidden spreadsheet columns, message history, portal access, and auto-generated summaries before delivery.

When a complete document is believed necessary, identify the protective purpose of each substantive portion and obtain privacy and legal review when circumstances allow. Preserve the reason a narrower summary could not meet the need.

The response team can ask which fact changes the recipient's action, whether it is accurate and current, whether a less revealing fact works, which uncertainty must be stated, how receipt will be confirmed, and when the information should stop being used. These questions make minimum scope practical during a time-sensitive event.

Example

Twelve fact sets are reviewed. Nine tie every disclosed element to the threat and protective action and preserve recipient, authority, timing, and follow-up; three attach the full assessment. Scope readiness is 9 of 12 sets.

Relevant-facts checklist

• define the substantial threat, person at risk, recipient, and protective action;
• connect each proposed fact to how it could reduce that threat;
• exclude unrelated history, diagnoses, billing data, and bulk records;
• verify accuracy, recipient authority, secure delivery, and receipt;
• log exact facts, rationale, instructions, response, and follow-up; and
• conduct a fresh review for every added request or changed situation.

Relevant scope depends on the live safety facts. A standard packet, complete chart, or standing family-access setting cannot replace a fact-level decision.