How to Review an ABA Incident Report

Start with the report's purpose and scope

An incident report usually records a provider's account of an unusual, harmful, or potentially harmful event. Its label, required fields, timing, confidentiality, distribution, and reporting consequences depend on provider policy, state rules, licensing, payer terms, insurance, and the setting. It is neither a medical diagnosis nor a final ruling about fault or cause.

The AHRQ patient-safety response primer describes reporting, investigation, communication, remediation, tracking, and system improvement as distinct parts of an event response. It is healthcare safety guidance rather than an ABA reporting rule. Ask which part this document serves and which later records or decisions are still expected.

Read the timeline as separate evidence entries

Review the report from the last known safe condition through discovery, response, handoff, and follow-up. Check the date, clock time, location, activity, people present, staffing assignment, equipment, communication access, health information available, observed change, words or messages used, immediate action, and resulting condition.

Label each statement as direct observation, client communication, family report, witness report, device record, clinical interpretation, medical direction, or later conclusion. Phrases such as “became upset,” “noncompliant,” or “appeared fine” need the observable events, speaker, time, and response behind them.

Know which record you are asking to see

For a HIPAA covered entity, the HHS access guidance generally gives an individual access to PHI in a designated record set, with stated exclusions, procedures, timing, fees, and denial rules. A provider's internal incident, quality, risk-management, or peer-review file does not automatically become accessible merely because it concerns the event. State law, contract, provider policy, or another rule may provide additional rights.

The HHS personal-representative guidance explains that applicable law determines who may exercise a person's HIPAA rights and how broad that authority is. A family relationship or emergency-contact label alone does not establish that authority. Ask for the precise accessible client records you need and ask separately what incident-review information the provider can share.

Turn missing details into answerable requests

List each discrepancy with the exact sentence or field, the proposed factual wording, the evidence supporting it, and why it matters for health, care, reporting, or prevention. Preserve the original report and add corrections through a dated process. Ask who decides whether the report changes and how a disagreement remains linked to later users.

Also request the event disposition: medical follow-up, clinical review, environmental review, privacy review, external reporting decision, corrective action, interim protection, return condition, and family communication. “Reviewed” is incomplete unless the owner, evidence, decision, and date are visible.

Use one decision register

Create a role-limited incident-report review register. Include report version and date, event identity, chronology, setting, participants, sources, direct observations, client communication, response, harm and follow-up, disputed text, missing evidence, requested correction, notifications, interim safeguards, corrective actions, owners, due dates, and dispositions. Preserve every original record and add later information as a dated, attributed entry.

Use the incident-report 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 incident-report 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

• Which document and version is this?
• Which statements are direct observations?
• What does the person say happened?
• Which health follow-up is documented?
• What evidence is missing or disputed?
• Which actions protect the next service?
• Who owns each open decision?

For every answer in the incident-report 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 for a later symptom, conflicting witness account, missing attachment, altered timestamp, inaccessible record, disputed authority, overdue correction, new safety concern, or another service scheduled before the response closes. 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 incident-report 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 incident-report 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

Rosa's family reviews 20 required incident-report fields at a defined checkpoint. Sixteen are supported by the report or linked evidence. The client message, exact medication time, second witness account, and current interim safeguard remain open. Completeness is 16 of 20, or 80%.

That ratio describes the locked review fields. It cannot establish medical recovery, truth of every entry, cause, fault, legal sufficiency, or prevention of recurrence.

Measure the named process

Lock the incident-report 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 Rosa's direct communication, the event sequence, source labels, health follow-up, disputed statements, interim protection, and open corrective work. 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.

An incident-report 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 incident-report review register when the first report arrives, after health information changes, after each correction response, before care resumes, and when every safety action reaches its acceptance test. 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 incident-report 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.