To protect privacy when collecting ABA client experience, map the purpose, authority, audience, channel, setting, minimum fields, access, retention, recording, and vendor route. Offer a private client-selected response method, limit collection and reuse, and separate urgent disclosures. Prevent retaliation and unnecessary exposure, test controls, document incidents, and verify the applicable privacy and record rules for the organization.

Define purpose and authority

Record why experience data is collected, which decision it informs, entity and role status, applicable consent or authorization, client choice, permitted uses, required disclosures, and who may interpret or act on the result.

Collect the minimum useful fields

Use only identifiers, context, question, response, source, time, access status, missingness, and follow-up data needed for the purpose. Avoid open narrative that invites unrelated health, family, employment, or location details.

Protect the collection setting

Offer private space, headphones or visual privacy, a secure device, confidential interpreter or support, discreet timing, a way to exclude another person, and a route that avoids the staff member or partner involved in the concern.

Map technical and vendor controls

Document role-based access, authentication, approved devices, storage, transmission, audit trail, backup, export, retention, deletion, incident response, vendor role, required agreements, subcontractors, and any secondary use or model-training restriction.

Separate urgent information

Tell Theo how immediate danger, abuse or neglect, medical emergency, privacy incident, and routine dissatisfaction are routed. Collect only what the authorized responder needs and continue protecting unrelated feedback.

Test and review privacy

Run access tests, sample logs, remove departed users, verify deletion and retention, inspect misdirected notifications, rehearse incident routing, record client complaints, and reassess when the measure, vendor, site, channel, or purpose changes.

Design privacy from the client's point of view

Walk Theo through each route from invitation to follow-up. Check what appears on a lock screen, who can overhear the prompt, whether a shared portal reveals participation, where an interpreter sits, what a staff member can infer, and which people receive an alert. Ask which route feels private enough for favorable, critical, uncertain, and sensitive reports. Record his choice without promising anonymity when the workflow cannot provide it. Explain the actual audience, exceptions, retention, and response process in language Theo can use to decide.

Limit secondary use and copied data

Experience responses often spread into email, chat, dashboards, exports, meeting notes, vendor tools, and improvement reports. For every copy, document the purpose, minimum fields, authorized roles, source version, retention, correction route, and deletion or archival rule. Use de-identified or aggregated material only after the responsible authority confirms that the method and intended use are appropriate. Preserve a path from a corrected source response to each active derivative. Block model training, marketing, testimonials, research, or unrelated performance evaluation unless the required authority and transparent client choice are established.

Test privacy failure responses

Use fictional scenarios for a misdirected notification, shared-screen exposure, excessive access, copied narrative, lost device, vendor incident, and a client who wants another route. Confirm that staff can protect immediate interests, preserve evidence, contact the right privacy or security owner, and continue necessary care through an approved method. Record elapsed time and unresolved dependencies. The exercise tests routing and recovery; it never substitutes for the applicable incident, breach, reporting, or legal analysis.

Build Theo's experience-data privacy plan

Create one versioned experience-data privacy plan for the clinic and remote feedback. Include the construct, decision, direct client communication, source-labeled proxy evidence, consent and assent when applicable, privacy, AAC and supports, authority, method, readiness, timing, missingness, burden, versions, corrections, actions, owners, effective dates, and review triggers. Define raw units and denominators before use.

Keep Theo's operational record decision-ready

For Theo, record candidate or deployed method, source, version, question, response options, access setup, collector, setting, period, eligible events, raw responses, help, withdrawal, missing reason, privacy route, correction, uncertainty, qualified interpretation, action, implementation, client communication, confirmation, and closure. Restrict sensitive content to approved roles and systems.

Work through Theo's example

Theo reviews ten feedback routes. Eight pass the purpose, access, privacy, retention, and incident-routing gates. He chooses one private route and one backup from those eight. Report 8/10 route readiness and two selected options. The two failed routes stay blocked until their owners repair them. Preserve all mature items, readiness states, responses, failures, raw counts, denominators, missing categories, versions, actions, and open work. This fictional example demonstrates one operational control and supplies no universal threshold, validation finding, legal conclusion, causal result, or outcome guarantee.

Use Theo's evidence for a bounded decision

Before collecting more data, identify the decision and authorized owner. Possible actions include clarify, restore access, retrain, revise, correct, pause, investigate, replace, retire, or close. For Theo, document interim protection, evidence needed, due date, implementation test, client-facing explanation, disagreement route, next review, and criteria for reopening.

Review Theo's results without hiding failures

For Theo, show raw counts beside percentages and keep inaccessible, missing, unfavorable, corrected, overdue, and reopened items visible. Segment by method, version, setting, collector, access route, and period when useful and privacy-safe. Compare cohorts only when definitions and maturity rules match, and explain material changes before interpreting a trend.

Address Theo's main operational risk

A secure platform cannot protect privacy when the wrong people can hear the question or view the response. Theo's plan covers the physical and social setting as well as technology. Review construct fit, direct client access, privacy, partner influence, burden, missingness, versions, corrections, and decision response separately. A completed form or precise score cannot compensate for a measure that asks the wrong question or leads nowhere.

Choose Theo's next action

Privacy owners repair an access list and an unclear retention rule, Theo retests both routes, and the approved options remain limited to the stated purpose. Preserve original evidence, client corrections, and disagreement. Record the qualified owner, affected measures and plan versions, interim safeguards, downstream systems, due date, validation evidence, client communication, current status, and next governance check.

Apply current professional sources to Theo's workflow

For Theo's workflow, the BACB ethics hub identifies the current Ethics Code, which addresses understandable communication, client involvement, consent and assent when applicable, confidentiality, assessment, 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 research, clinical expertise, client values, and context.

Use measurement evidence for Theo

For Theo's process, the treatment-integrity practitioner guide, Essig review, impact study, and reporting review support explicit procedures, representative evidence, observer controls, and cautious interpretation. They create no universal experience threshold or validation method. Breaux and Smith offer assent-focused guidance in an evolving evidence base. ASHA supports continuous AAC access.

Close Theo's operations review

Review the experience-data privacy plan with Theo, the responsible clinician, operational owners, privacy and access roles, and the specialists named in the manifest. Verify that the method remains understandable, accessible, private, proportionate, version-controlled, and actionable. Preserve history, supports, limits, and open gaps. Keep this page draft and noindex until required reviews are complete.

Related resources

Sources