Adult ABA updates usually begin with the capable client's own instructions. The client can identify people involved in care or payment, allow relevant discussion, use a written authorization where needed, or direct certain records through an access request. Personal-representative authority is different and comes from applicable law. Record who may receive which information, for what purpose, through which channel, for how long, and how the client changes the choice.

Ask the adult in an accessible way

Offer names, roles, topics, channels, and duration in the person's communication form. The BACB Code addresses understandable communication, client involvement, confidentiality, and consent.

Use the right HIPAA pathway

For covered entities, HHS permits certain directly relevant sharing with involved people under specified conditions. Broader disclosure may need another route.

Separate support from representative authority

HHS personal-representative guidance explains that applicable law determines representative authority and scope. A supporter does not become the decision-maker merely by receiving updates.

Maintain a current preference record

The CASP summary supports individualized care. Record approved recipients, topics, channels, restrictions, expiration, changes, and the client's last confirmation. Stop routine sharing when the client revokes or the route expires, subject to any separate lawful duty.

Ask the adult client before building the contact list

Use an accessible conversation to ask who may receive scheduling, clinical, billing, emergency, and general updates. The answer may differ by topic. Record the client's preferred channels, times, language, AAC, privacy needs, and how the person changes the choice.

Do not make family involvement the default merely because it occurred during childhood. When the adult can make the decision, center that person's direction. If another person claims representative authority, verify the applicable law and scope. Limited authority may cover only particular decisions or information.

Use the correct disclosure pathway

For a HIPAA-covered provider, relevant information may sometimes be shared with family or another person involved in care when the regulatory conditions are met. That pathway does not create personal-representative authority. A HIPAA authorization is another mechanism and must meet its own requirements. Treatment, payment, operations, required-by-law, and other pathways have distinct scopes.

Ask the practice to document which route it is using, the recipient, information, purpose, and time period. Receiving information from a family member does not automatically authorize the provider to disclose information back.

Make preferences operational

Update the portal, phone tree, scheduling system, clinical handoff, billing contact, and emergency instructions without granting broader access than requested. Give frontline staff a clear current rule while keeping sensitive authority documents restricted. Remove obsolete contacts and test the selected channel.

Explain limits. Emergencies, required reporting, legal processes, or other duties may allow or require communication outside ordinary preferences. State those boundaries in understandable language without using rare exceptions to justify routine disclosure.

Work through an adult update plan

Rina wants her father to receive appointment changes and transportation questions but not clinical notes or billing information. She wants her partner to join quarterly planning meetings. The provider verifies Rina's choice, records separate contact purposes, and gives her an accessible route to revise them.

Over one month, five scheduling updates are due. Four reach the father through the requested channel; one goes only to Rina and causes a missed ride. Channel completion is 4 of 5 updates. The practice corrects the workflow without expanding the father's clinical access.

Review the preference record

Include the adult's decision, communication method, recipients, topics, channels, effective date, expiration if any, and revocation or change process. Distinguish personal representative, involved person, support person, emergency contact, and authorized recipient.

Recheck after a move, hospitalization, relationship change, safety concern, capacity or authority change, or direct client request. Close old permissions in every system. A respectful update process enables chosen support while preserving the adult client's privacy and control to the extent applicable.

Change or revoke an update preference

Tell the provider exactly which recipient, topic, channel, and effective date should change. Ask whether the current arrangement is a client preference, care-involvement decision, authorization, personal-representative record, or another pathway, because the method for changing it may differ. Preserve the prior state and the new request with dates.

Request confirmation across every relevant system. A portal may remove proxy access while a scheduling platform, phone tree, billing system, or staff contact list still sends updates. Name the systems the practice checked and the date of completion. Do not ask frontline clinicians to manually remember an exception that the organization can encode safely.

Plan for the period between request and verified implementation. Identify which communications should be held, which can continue directly to the client, and who handles urgent questions. If the change relates to safety or possible coercion, use the provider's protected or confidential communication and urgent-review routes as applicable.

An adult client can write: “Effective today, stop sending clinical and billing updates to this person. Scheduling messages may continue through this date only. Send all updates to my requested channel and confirm when portal, scheduling, clinical, and billing contacts have been changed. This request does not change any separate legal authority unless the applicable process says so.”

Test the result with the next due communication. Record successful delivery to the chosen recipient and any unwanted disclosure or failed access. Route a possible privacy incident to the responsible role. Close the change only after the client confirms the new route works and old permissions no longer operate beyond their lawful scope.

Protect confidential communication when risk is present

An adult client may need updates sent through a different address, phone, portal, or time because ordinary contact could create harm or unwanted disclosure. Ask the provider about its confidential or alternative communication process and the conditions that apply. Do not put the sensitive reason in a broadly visible scheduling note.

Create a safe verification method that does not reveal the request to the former recipient. Confirm how voicemail, caller identification, paper mail, billing statements, appointment reminders, and portal notifications behave. Test the new channel with low-risk information before relying on it for an urgent message.

If an unwanted disclosure occurs, preserve the message and route it promptly to the privacy contact while maintaining safe communication. The adult client should receive an understandable disposition and any protective change. Clinical, safety, or legal duties may require separate action, but they do not excuse leaving routine contact settings inaccurate.

Recheck the communication choice during annual paperwork without forcing the adult to name a family recipient. “No additional recipient” is a valid operational state when the client controls the choice. Staff should know how to route questions directly and accessibly to the client and record successful delivery. Ask the client whether the corrected message arrived privately and in usable form.

Related resources

Sources

Finni resources

Ready for the next step?

Find ABA care near you