Explain permission before connecting the records

What we found in the news

An HHS fact sheet reviewed on January 30, 2026 (opens in a new tab) explained changes to federal protections for certain substance-use-disorder treatment records under 42 CFR Part 2. Its discussion of disclosures made with consent included:

“a clear explanation of the scope of the consent”

— HHS Office for Civil Rights

The fact sheet identified February 16, 2026 as the compliance date for applicable requirements. These are specific protections, with important distinctions and exceptions. They are not a general permission to share any health information. Our interest here is the everyday conversation around permission, rather than an interpretation for an individual case.

A form cannot carry the whole explanation

Picture a person being offered a connection between two services. They may welcome having less to repeat. They may also want to know exactly who will see the information, what it contains, and whether accepting one kind of support means accepting something else.

This is an illustrative situation, but the design question is concrete. Where can the person ask those questions? A busy reception counter, a screen filled with unfamiliar terms, or a hurried request for a signature may leave little room for understanding.

At genus, we want connection to preserve people's agency. That includes the ability to pause while someone explains a choice properly.

Start with the particular purpose

Explain the proposed exchange in terms of the task it supports. Naming an organization is helpful, but people may also need to understand which service or role is involved and why that information is relevant.

Avoid stretching a simple explanation into a promise that exceeds the actual rules or arrangement. Some uses require different treatment; some material has additional protections. Staff should know when to bring in a privacy professional rather than guessing from a familiar-looking form.

Use examples that do not expose someone else's records. A plain description of the proposed process can make a conversation easier without turning another person's experience into teaching material.

Offer a way to ask privately

Give people a suitable place and enough time to raise concerns. Ask what communication format helps them understand the explanation. A chosen supporter may contribute, while the person whose information is involved remains central to the discussion.

Do not use a request for clarification as evidence that someone is difficult or unwilling to participate. It may show that the service has not explained the choice well enough. A useful response might be to slow down, use a different format, or arrange a conversation with the right colleague.

Teams also need a clear route for questions about changing a choice, correcting information, or understanding what has already happened. The answer depends on the applicable arrangement; it should not depend on finding a particular employee by chance.

Keep the explanation connected to the actual process

When a service changes its partners or tools, review the explanation people receive. A reassuring leaflet can become misleading if the practical information route has changed behind it.

Ask the responsible team to check whether public descriptions, staff guidance, and the consent process still agree. Decide who maintains each part and how a colleague can raise a discrepancy. Keep the detailed privacy review with qualified professionals who understand the records and organizations involved.

A shared communications channel is not automatically a suitable place for sensitive information. Being convenient to reach does not establish permission to disclose.

What this means for participants and families

People should have a clear route to an explanation of their own choices. They should not need to reveal sensitive details in a public discussion to obtain basic information about a service's process. Families can help someone prepare questions without being assumed to hold permission for every exchange.

The genus connection

Today, genus content and pathways can make prepared explanations and questions available in configured experiences. Organizations can use reviewed resources to help people prepare for a conversation with the appropriate team.

That supporting role is different from interpreting consent or authorizing record disclosure. Public care-wall content is not a place to expose private treatment information. The organization must determine the appropriate audience, channel, permissions, and professional responsibilities for its setup. A useful resource should make the next conversation easier to find, while leaving the decision with the person and the responsible service.

One question for the team

Could someone explain back what they are agreeing to share, or have we only made it easy to finish the form?