genus perspective
Share the context that fits the role
A care team needs useful information, and each recipient has a different job to do. HHS guidance on communication with family and friends prompts a practical discussion about purpose, the person's wishes and sharing relevant context through the right channel.
What we found in the news
The U.S. Department of Health and Human Services' guidance for patients about communication with family and friends (opens in a new tab), reviewed in December 2022, explains circumstances in which covered providers may share information. Its linked patient guide refers to:
“only the information that the person involved needs to know”
— HHS Office for Civil Rights, A Patient's Guide, question 1
The guide describes specific HIPAA situations, including the person's agreement or lack of objection and professional judgment in defined circumstances. It is not a blanket permission to share a care record. Different settings and information can require different rules.
Why this matters to us
In an illustrative community program, a participant has agreed that a friend will help with transport. The driver needs the collection arrangement and relevant assistance information. A practitioner reviewing care may need different details. An activity facilitator has another role again.
Sending everyone the same long update is unlikely to make those distinctions clearer.
At genus, we are interested in useful connections that respect the person at their center. That begins with understanding why someone needs information and what they will do with it. Being helpful should not require a person to surrender every detail of their life to everyone involved.
Begin with the intended action
Before preparing an update, ask what the recipient is responsible for. Which information helps them carry out that responsibility? Which details belong elsewhere?
For the transport example, staff can use the organization's approved process to confirm what the friend needs and what the participant wants shared. A health history should not travel alongside a routine collection time simply because both were stored in one note.
Avoid making the opposite mistake, too: an update so vague that the authorized receiving person cannot do their job. Appropriate sharing requires judgment about purpose and relevant context, within the rules that apply.
When unsure, use the organization's privacy or professional advice route. This article offers communication questions for teams; it does not determine whether a particular disclosure is lawful. Staff should not have to improvise that decision from a blog post.
Separate the audiences when preparing an update
An internal staff record and an update for a chosen supporter can have different purposes. Review each for its intended reader.
Ask whether the wording distinguishes an observation from an assumption. A participant requesting a quieter room is a recorded request; an unsupported explanation of their motivation is something else. Sensitive interpretations can spread surprisingly far once they are copied into successive summaries.
Check the recipient and channel before sending. Familiar names can be selected incorrectly, and an old contact may no longer have the same role. A convenient channel is not automatically the approved channel.
The person receiving support may want to contribute to the everyday account being shared. Where appropriate, offer a chance to correct a detail or explain their preference. That does not replace the professional record; it helps the communication represent the situation more accurately.
Keep permission and access current
Relationships and responsibilities change. A friend may stop providing transport. A worker may leave a team. A person may want a different supporter involved.
Build a practical route for updating those arrangements. Staff need to know where to record a change and who can alter access. The person needs to know how to raise it.
Managers can review one routine communication journey with fictional information: who prepares the update, who checks it and how its audience is chosen. This can reveal an unnecessary copy or an unclear responsibility without exposing real records.
Avoid treating privacy as a reason to stop useful conversation altogether. The task is to establish an appropriate route for the information the recipient is entitled and needs to receive.
The genus connection
Today, genus partner and care-community experiences use configured access and workflows for different audiences. Staff can prepare and review information within the modules their organization uses.
Configuration needs to match the actual service arrangement. A community membership, message or sharing feature does not by itself establish consent, legal authority or the correct audience. Organizations remain responsible for those decisions and for reviewing access as roles change.
For us, the useful design question is whether the right person can find the context needed for the agreed next step, with appropriate boundaries around everything else.
One question to take away
For your next routine update, can you explain what each recipient needs it for?
Supporting references
- Family Members and Friends (opens reference preview; direct link opens in a new tab)
U.S. Department of Health and Human Services · 2022-12-23
HHS patient guidance last reviewed December 23, 2022. Describes circumstances for sharing with family/friends and links the patient guide. The date is the page's review date.
- A Patient's Guide: When Health Care Providers May Communicate About You with Your Family, Friends, or Others Involved in Your Care (opens reference preview; direct link opens in a new tab)
HHS Office for Civil Rights
Short quotation from question 1, page 1. The PDF does not state a publication date; it is linked from the HHS page reviewed in 2022. The article is operational commentary, not a legal determination.
