How Families Can Participate in an ABA Safety Root-Cause Review

Understand what a systems review can do

A family ABA safety root-cause review can use the AHRQ root-cause analysis primer as a question framework. The primer describes a structured review that reconstructs an event, examines active and latent system problems, and seeks prevention rather than focusing only on individual mistakes. It also notes that root-cause analyses can produce weak or incompletely implemented actions. A family can ask for a system view without assuming the method proves one root cause.

This AHRQ primer addresses healthcare patient safety. It does not require a specific ABA provider to conduct or disclose a particular review. Accreditation, state law, facility rules, payer terms, insurance, privilege, contracts, and provider policy can change the process and access.

Offer evidence the provider may not have

Families can explain the person's ordinary communication, health, sensory needs, mobility, routines, response to unfamiliar people, equipment, prior similar events, successful supports, and changes after the event. The client may identify fear, pain, confusion, a blocked message, or a goal conflict that records miss.

Provide dates, observations, messages, photographs, medical instructions, and relevant records with clear source labels. State uncertainty. Avoid turning a sequence into causation simply because one event followed another.

Ask system questions across the event path

Work through planning, staffing, qualifications, supervision, handoff, communication, environment, equipment, scheduling, health information, policy, training, technology, vendor, emergency response, escalation, and leadership decisions. Ask which defenses existed, which were missing, which failed, and which worked.

The AHRQ event-response primer describes communication and system improvement as part of ongoing response. The AHRQ CANDOR resource offers hospital implementation material for communication and resolution. Use both as question frameworks rather than universal legal standards.

Test whether proposed actions reduce exposure

A broad retraining promise may leave the original system unchanged. Ask whether the action eliminates a hazard, adds a hard stop, simplifies a workflow, automates a reliable check, improves staffing or supervision, secures an environment, creates redundancy, or detects failure sooner. Require an owner, due date, affected locations, acceptance test, monitoring period, and response to failure.

Include possible unwanted effects, such as reduced AAC access, added restraint, burdensome family requirements, or loss of service. A correction should preserve the person's rights and ordinary supports while addressing the actual exposure.

Use one decision register

Create a role-limited family root-cause review register. Include review scope and authority, event chronology, client account, family evidence, ordinary conditions, active and latent factors, working hypotheses, confirmed findings, dissenting evidence, corrective options, action strength, unwanted effects, owners, due dates, acceptance tests, recurrence monitoring, communication, and disposition. Preserve every original record and add later information as a dated, attributed entry.

Use the family root-cause review register to distinguish direct observation, client communication, family report, staff report, clinical judgment, medical direction, device or system evidence, authority response, and interpretation. Give the person and authorized family member an accessible summary. ASHA says AAC users should always have access to their communication tools or devices.

The family root-cause review register uses the CASP organizational overview only for broad business, clinical-operations, and risk framing. For covered professionals, the BACB Ethics Code addresses competence, understandable communication, consent and assent when applicable, documentation, risk, and evaluation. Neither source assigns medical, legal, payer, insurer, facility, protective-services, or family authority.

Answer the questions that control the next step

• What is confirmed and by which source?
• What does the person say or show?
• Which system conditions shaped the event?
• Which explanations remain hypotheses?
• How strong is each proposed action?
• What unwanted effects could it create?
• How will implementation and effectiveness be tested?

For every answer in the family root-cause review register, record the source, version, date, responsible role, decision, rationale, next action, due date, interim safeguard, and acceptance evidence. Mark the item confirmed, open, disputed, inapplicable with a source, or decided by the authority. Preserve competing accounts rather than merging them into artificial certainty.

When case-specific legal advice is needed, the USAGov legal-aid directory can help locate affordable assistance. A provider policy, meeting note, software status, or family agreement cannot replace an authority's required decision.

Prepare for a second failure

Plan now in case the review narrows to one person's mistake, family evidence is mislabeled, a hypothesis becomes a fact, the client cannot participate, a proposed action removes access, the due date slips, or the same exposure appears elsewhere. Name who protects health and safety, who communicates with the person, which record is preserved, which accessible backup is available, which service pauses, and which medical, clinical, privacy, payer, insurer, facility, licensing, protective, legal, or emergency role must act.

While the family root-cause review register remains open, keep AAC, interpreters, mobility, bathroom use, food, water, prescribed care, rest, and emergency help available. Record the actual response, failed control, new evidence, notification, temporary safeguard, and condition for safe continuation. Avoid asking the person to reenact an event or enter an unverified condition to prove a correction.

One named owner remains accountable for each open family root-cause review register item, including work delegated elsewhere. The client and family should know whom to contact, what is happening next, and when another update is due.

A fictional family tracking example

Amara's family and the review team lock 22 evidence and action questions. Seventeen have a sourced answer. The equipment history, supervision handoff, client communication gap, cross-site exposure, and acceptance-test owner remain open. Review completeness is 17 of 22, or 77.3%.

The ratio describes answered questions. It cannot prove root cause, fault, privilege status, action effectiveness, or reduced future harm.

Measure the named process

Lock the family root-cause review register cohort and checkpoint before counting. Report verified or accepted items divided by every item due at that checkpoint. Keep missing, late, failed, disputed, and untested items in the denominator with their age and owner. Mark inapplicable only when the governing source and event facts support it.

Focus on Amara's account, the event sequence, ordinary supports, system conditions, competing explanations, access effects, action strength, acceptance tests, and recurrence evidence. Pair process counts with the person's direct report, health, safety, communication access, missed care, privacy, financial effects, travel, work or school disruption, and household effort. If direct report is unavailable, identify whose observation is used and preserve accessible opportunities for the person to participate.

A family root-cause review register percentage describes the named cohort and time window. It cannot prove causation, fault, compliance, medical recovery, clinical appropriateness, client agreement, or future safety. Show raw counts beside percentages and explain every exclusion.

Set the next review date

Review the family root-cause review register when the review scope is set, after each evidence interview, before findings are finalized, when actions are approved, at each due date, and through the defined recurrence window. At each checkpoint, verify current health and safety, the person's priorities, new facts, applicable sources, responsible roles, deadlines, interim safeguards, service effects, and unresolved consequences.

Close each family root-cause review register row with a concrete disposition such as received, corrected, amended, disagreement linked, medically reviewed, clinically decided, reported, declined by the authority, implemented, tested, failed and reopened, transferred, appealed, or completed with evidence. A meeting, apology, assigned task, sent form, or “closed” label alone does not show the issue was resolved.

Provide a plain-language summary of what happened, what was decided, what changed, what remains uncertain, who owns the next step, and when review continues.