To plan a personal-information sharing goal in ABA, choose a real decision the person wants to manage. Classify the information, authority, recipient, purpose, minimum useful content, channel, retention, and limits on reversal. Preserve refusal and help. Practice with fictional data when possible, and measure source readiness, safe decisions, partner response, disclosures, corrections, burden, and experience.

Classify the information

Separate contact, identity, health, financial, location, credential, account, employment, school, relationship, image, and other sensitive information.

Identify the exact field before teaching a rule. An email address, Social Security number, insurance identifier, treatment record, pay statement, location, photograph, password, and emergency contact carry different risks and may have different legitimate recipients. Record whether the information belongs only to Farid or also reveals another person. Use redacted examples during instruction.

Discuss what can be changed after disclosure. A phone number can be replaced, while a biometric, image, health history, or identity document may be difficult to retract. The level of verification, secure channel, and help needed should match the actual information and purpose.

Verify recipient and purpose

Record who asks, their authority, why the data is needed, required and optional fields, secure channel, retention, onward sharing, and correction route.

Teach Farid to verify through an independently obtained route rather than a link or phone number supplied in a suspicious message. For a real employer, school, payer, clinic, bank, or government request, identify the authorized office, current form, deadline, and minimum required fields. Separate mandatory information from optional demographic, marketing, or convenience fields.

Explain how the recipient will use, retain, correct, and share the data when that information is available. If the request concerns consent, privacy rights, legal process, account security, or financial risk, route the decision to the appropriate qualified owner. The ABA plan supports an accessible decision process; it does not create authority over another organization's requirements.

Teach a safe decision set

Include share the minimum, decline, ask why, verify independently, use another channel, ask a trusted qualified person, report concern, and stop.

Practice choosing among these actions rather than scoring disclosure itself as success. Farid can pause, seek help, or ask for a paper or secure-portal route. Preserve AAC, language support, privacy, and the option to refuse an optional request. Teach partners to answer questions without taking over the decision or entering real sensitive information during practice.

Build a rapid response for mistakes. Record who Farid contacts after sending information to the wrong recipient, suspected phishing, account compromise, lost device, or inaccurate submission. The right action may involve the organization's security, privacy, financial, employment, legal, or public authority. Immediate routing matters more than proving why the error occurred.

Use a disclosure worksheet

For each real request, record the requester, independently verified contact route, stated purpose, required fields, optional fields, authority, transmission method, retention statement, and help contact. Mark which facts Farid supplied, declined, or left pending. This makes the decision reproducible and prevents a general lesson about "safe sharing" from becoming permission for a partner to decide on his behalf.

Plan for hard-to-reverse sharing

Account numbers, identity documents, health records, location, images, and login credentials can create consequences after transmission. Before a real disclosure, confirm whether Farid can correct, revoke, replace, or limit the information and who handles an error. Use fictional values for practice. A suspected scam, account compromise, identity theft, or unlawful request belongs with the appropriate security, financial, employer, legal, or public authority.

Measure decisions without exposure

Use fictional or redacted data. Report ready scenarios, decisions, help use, unsafe prompts, actual disclosures, partner response, errors, burden, and Farid's experience.

Track scenarios with enough source information, verification attempts, minimum-field decisions, help requests, partner responses, real disclosures, suspected errors, and corrective routes used. Keep system readiness separate from Farid's action. Review whether partners protected privacy, whether the practice itself created risk, and whether Farid can reach the current help contact when a real request changes.

Build Farid's personal-information sharing plan

Create one versioned personal-information sharing plan for the internship onboarding. 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 Farid's example

Farid reviews ten fictional onboarding requests. The privacy rule, recipient, and purpose are clear in eight. He makes the selected share, decline, or ask-for-help decision in 7 of 8 ready scenarios and seeks help in both uncertain scenarios. Report 8/10 readiness, 7/8 decisions, and 2/2 help use. 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 Farid's main fit risk

A blanket rule against sharing fails when a legitimate recipient needs limited information. Farid's plan teaches a source-based decision and secure help route. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.

Choose Farid's next action

The internship clarifies two ambiguous requests, Farid updates his help contact, and the team repeats practice with fictional data. Record the qualified owner, authority, affected setting, interim support, evidence needed, due date, client communication, correction route, disposition, and next review.

Before real onboarding, verify the current form and secure submission route independently. Farid should know which fields are required, which are optional, who can correct an error, and where to report a suspicious request. After submission, retain only the minimum training record needed and avoid copying his real sensitive values into ABA data. Recheck the plan when the employer, portal, help contact, or requested information changes.

Apply current professional sources to Farid's plan

For Farid'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 Farid

In Farid'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 Farid's review

Review the personal-information sharing plan with Farid, 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