To plan a privacy-preference goal in ABA, identify a privacy choice the client wants to express and distinguish that preference from controlling legal, clinical, safety, payer, and organizational duties. Define people, place, channel, content, timing, and exceptions. Teach accessible messages and partner action. Measure preference access, honored requests, delays, disclosures, corrections, burden, and client experience.

Specify the privacy choice

Record who may be present, where conversation occurs, channel, content, timing, visibility, recording, follow-up, and how Elena communicates a change.

Tie the preference to an event that partners can recognize. Elena may want scheduling details sent by portal, treatment questions discussed away from a waiting room, a family member absent for one topic, the camera off during part of telehealth, or a report delivered to a private device. Record the people, information, place, channel, timing, and duration. Avoid promising secrecy when the organization cannot lawfully or operationally provide it.

Ask how Elena wants to revise the preference and whether a standing choice should be confirmed at certain transitions. Preserve AAC, language access, enough time, and a private route to object. If another person has authorized access, record that authority separately from Elena's current preference and route any conflict to the proper owner.

Map controlling duties

Route confidentiality, personal-representative, disclosure, mandated-reporting, emergency, record-access, payer, employment, and legal questions to authorized roles.

The clinical team should distinguish ordinary privacy practices from decisions controlled by law, contract, payer rules, safety duties, records policy, employment needs, or another authority. Name the qualified privacy or legal owner when the answer is uncertain. Record the minimum information and people required for the applicable purpose rather than using a broad exception to override every part of Elena's request.

Explain the decision accessibly. If the requested channel is insecure or a specific person must receive information, describe the reason, available alternatives, and complaint or review route. Preserve the parts of Elena's preference that remain possible and set an expiration or review point for any temporary exception.

Record the preference at event level

Write the preference so a partner can act on it in the moment. Name the conversation or task, the people who may participate, the accepted place or channel, the information covered, and the point when Elena may change her mind. Store the preference where affected staff can find it while limiting access to people who need it for their role. A broad label such as "prefers privacy" gives too little direction for reliable implementation.

Handle exceptions visibly

When a qualified owner determines that a safety, legal, payer, or operational duty changes the requested route, record the controlling source, the smallest necessary departure, the person who authorized it, and what Elena was told. Keep the exception separate from ordinary preference performance. Repeated exceptions can reveal a system design problem even when each individual action has a documented basis.

Build accessible messages

Include private, move, stop, different person, different channel, less detail, repeat later, correction, complaint, and help in Elena's accepted forms.

Make these messages available where disclosure risks occur, including reception, transport, community, telehealth, group spaces, and electronic communication. Partners should pause before continuing, move or change channels when feasible, acknowledge the request, and route any exception without debating Elena in public. Teach a backup route for a device, portal, or staff failure.

Measure privacy response

Report ready settings, eligible messages, partner acknowledgment, honored preferences, latency, disclosures, exceptions, corrective action, burden, and Elena's account.

Use separate denominators for planned events, private settings or channels ready, messages accessible, preferences communicated, partner responses honored, exceptions reviewed, and corrective actions completed. Keep disclosures and near misses visible even when later corrected. Close an event after Elena receives the explanation or repair, active instructions reflect the current preference, and any privacy review remains linked to its qualified owner.

Build Elena's privacy-preference plan

Create one versioned privacy-preference plan for the clinic conversations. Include the request or choice, direct communication, consent and assent when applicable, privacy, AAC and retained supports, authority, source evidence, system and partner duties, eligible opportunities, client and partner measures, experience, burden, decisions, owners, dates, and review triggers.

Work through Elena's example

Across eight planned conversations, Elena's requested location or secure channel is ready in six. She communicates a privacy preference in 4 of 4 eligible moments, and staff honor 3 of 4. Report 6/8 system readiness, 4/4 messages, and 3/4 response. The missed response receives privacy review. Keep every opportunity, readiness state, client action, partner response, system failure, numerator, denominator, exclusion, support, and experience measure visible. This fictional example supplies no universal goal, dose, independence standard, legal conclusion, payer result, or outcome guarantee.

Address Elena's main fit risk

A client goal cannot compensate for staff discussing information in the wrong place or channel. Elena's plan makes privacy readiness an organizational measure. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.

Choose Elena's next action

The privacy owner reviews the missed event, staff correct the channel rule, and Elena confirms whether the repair addresses her concern. Record the qualified owner, authority, affected setting, interim support, evidence needed, due date, client communication, correction route, disposition, and next review.

Verify the repair in the setting where the miss occurred. Confirm that staff can find the current preference, the private location or secure channel is ready, and the exception route reaches the privacy owner without further disclosure. If information already reached an unintended person, preserve the incident record and follow the applicable response process. Close the preference item only after Elena receives an accessible update, affected instructions agree, and she can still change or escalate the request.

Apply current professional sources to Elena's plan

For Elena's plan, the BACB ethics hub identifies the current Ethics Code, which addresses understandable communication, client involvement, consent and assent when applicable, confidentiality, assessment, medical needs, risk, documentation, and evaluation for covered people. BACB has no separate organizational jurisdiction. The BCBA outline is examination content and supplies no practice authority. The CASP public summary gives high-level context for ABA treatment of autistic people. An evidence-based ABA framework supports integrating research, clinical expertise, client values, and context.

Use implementation and access evidence for Elena

In Elena's plan, the treatment-integrity practitioner guide, Essig review, impact study, and reporting review support explicit procedures, representative implementation evidence, and cautious interpretation. They create no universal response threshold. Breaux and Smith offer assent-focused practice guidance while describing an evolving evidence base. ASHA supports continuous access to AAC tools or devices.

Close Elena's review

Review the privacy-preference plan with Elena, the responsible clinician, affected partners, and the specialists named in the manifest. Preserve direct communication, ordinary supports, disagreement, system duties, versions, decisions, limits, and open gaps. Keep this page draft and noindex until all required reviews are complete.

Related resources

Sources