What to Do When an ABA Incident Report Is Delayed or Missing

Protect care while the paperwork is unresolved

An ABA incident report delayed or missing should never delay emergency care, symptom monitoring, prescribed treatment, mandated reporting, or an immediate safety change. Create a family chronology with the event date, who called, what was said, symptoms, medical visits, photographs, messages, names, and unanswered questions. Label recollection and direct evidence separately.

Ask the provider for a short interim summary covering the known event, current safeguard, service status, medical or clinical contact, and the person responsible for updates. Preserve all versions rather than replacing an earlier account.

Request the records by name

Ask for the incident report if it is available under the applicable policy or law. Also name the client records needed for care: session note, treatment-plan change, medication administration record, injury assessment, restraint log, discharge instruction, communication record, authorization, or other relevant item. A broad request for “everything” can obscure which records are urgent.

For a HIPAA covered entity, HHS access guidance says the right generally covers PHI in designated record sets and requires action within 30 calendar days, with one possible extension of up to 30 days if the entity provides a timely written explanation and completion date. Faster state, payer, contract, or provider requirements may apply.

Keep internal review and client access distinct

An internal risk-management, quality, peer-review, attorney, or insurer file may have a different status from the clinical and billing records used to make decisions about the person. Ask the provider to identify the basis for any withholding or denial and any review or appeal route. Avoid assuming that the title “incident report” resolves access.

The HHS personal-representative guidance explains that applicable law determines whether someone may exercise another person's HIPAA rights. Confirm the requester's authority and scope, especially for adults, limited guardianship, foster care, custody changes, or minor-specific exceptions.

Escalate the exact unresolved obligation

Send a dated written request through the provider's stated channel. Record receipt, responsible office, required response date, extension, production, missing item, denial basis, and next step. Ask a supervisor, privacy officer, clinical leader, licensing authority, payer, insurer, or counsel only for the issue within that role.

The AHRQ event-response primer describes ongoing communication after patient-safety events. It does not give every family a universal right to an internal analysis. When case-specific legal help is needed, the USAGov directory points to affordable legal-aid resources.

Use one decision register

Create a role-limited delayed-record request register. Include event and urgent care needs, requested document, record category, requester authority, delivery channel, receipt date, governing source, ordinary deadline, extension, owner, interim summary, records received, missing elements, denial and review route, escalation, current safeguard, next service, and final disposition. Preserve every original record and add later information as a dated, attributed entry.

Use the delayed-record request 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 delayed-record request 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 record is needed and why?
• Is it part of the accessible client record?
• Who has authority to request it?
• Which clock applies?
• What interim information protects care?
• What basis supports a delay or denial?
• Which review or escalation route applies?

For every answer in the delayed-record request 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 symptoms change, the request lacks receipt evidence, the provider gives only a verbal promise, an extension arrives late, the wrong office owns the request, urgent client records remain absent, or care proceeds with an unverified safety fact. 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 delayed-record request 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 delayed-record request 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

Inez's family locks 16 request and safety tasks after an incident document is delayed. Twelve are complete. The provider's written access decision, one clinical note, the extension status, and the next-service safeguard remain open. Completion is 12 of 16, or 75%.

The ratio measures the chosen tasks. It does not determine whether an internal report is legally accessible, whether the provider met every applicable deadline, or what caused the event.

Measure the named process

Lock the delayed-record request 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 Inez's current health, accessible client records, requester authority, request receipt, applicable clock, withheld-item basis, interim safety, and escalation outcome. 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 delayed-record request 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 delayed-record request register after each request, at the stated response date, when an extension or denial arrives, before any affected service, and when the family receives or exhausts the applicable record route. 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 delayed-record request 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.