ABA practice incident intake and initial triage turns a report, alert, observation, system signal, or third-party notice into a controlled response. It preserves the earliest known facts and time, addresses immediate danger, identifies affected people and services, assigns a qualified triage owner, opens potentially applicable reporting routes, protects communication access, and keeps suspected, confirmed, duplicate, false-positive, referred, and unresolved states distinct.

Define the intake and triage boundary

Aaliyah accepts signals through staff, client, family, vendor, system, facility, payer, and external-authority channels. The intake form never asks the reporter to prove severity or choose a legal category. Staff capture the report in the person's own words, mark observations and interpretations separately, and route emergency action immediately. The incident-intake and triage record has a named owner, scope, current sources, qualified decision boundaries, version, role-limited access, evidence location, exception route, change triggers, and retention state.

Record the signal, clocks, people, risk, route, and owner

The working record captures incident ID, received and discovery times, reporter and channel, exact report, affected people and services, location, immediate danger, emergency action, injury or health concern, communication access, system or facility condition, privacy or security indicator, workforce indicator, payer or licensing indicator, evidence offered, duplicate link, triage owner, initial state, route screen, next action, update time, access restriction, correction, and audit trail. Each field supports protection, a decision, communication, measurement, or later trace. Narrative is used for context and uncertainty; structured states support queues, clocks, ownership, and reconciliation.

Use the intake record without delaying protection

Aaliyah uses a two-stage screen. The first stage protects people, summons emergency or medical help when needed, and preserves evidence. The second stage assigns provisional categories and qualified owners. An alert can close as a documented false positive after review; a confirmed event keeps the original alert and every state change.

Protect people while classification continues

Aaliyah lets emergency, medical, crisis, protective, and immediate containment actions proceed under the applicable route. Routine approvals never delay urgent help. Temporary service or system controls stay scoped to the observed condition and retain access, communication, clinical, workforce, privacy, and continuity review.

Keep facts, hypotheses, decisions, and actions distinct

Aaliyah labels each entry as a reported fact, direct observation, system result, hypothesis, qualified decision, assigned action, or later correction. Authorship and time remain visible. This structure allows a fast response while showing what remains uncertain.

Validate intake against source signals and outcomes

She seeds phone calls, AAC messages, after-hours emails, automated alerts, vendor reports, injuries, privacy concerns, and duplicates. Reviewers compare source timestamps with the intake record, test emergency bypasses, inspect routing, and confirm that every unresolved signal has an owner and next review.

Reconcile the incident across operating systems

Aaliyah compares the incident record with clinical documentation, schedules, staffing, access, communications, facilities, vendors, billing, payer evidence, HR systems, privacy and security cases, insurance files, and corrective actions as authorized. Differences receive owners, effects, and resolution states.

Protect direct communication, access, and dissent

Aaliyah gives affected people a direct, usable communication route whenever possible, keeps AAC and other supports available, allows time to respond, and records questions, corrections, refusal, pause, distress, or withdrawal. Confidentiality limits and required external routes are explained in accessible language.

Work through Aaliyah's fictional example

Aaliyah locks 30 incident signals received during a month. Twenty-three have original report, received time, immediate-risk screen, affected people, access support, evidence, state, owner, route screen, and next action. One AAC report loses detail, one alert lacks a discovery time, two emergency screens are late, one duplicate is counted twice, and three signals lack owners. Five signals are repaired. Two remain open. The scenario is synthetic. It tests scope, authority, access, evidence, clocks, response, and denominator logic without establishing clinical quality, legal compliance, reportability, coverage, causation, safety, satisfaction, or outcome.

Calculate the example measures

Initial intake integrity is 23 of 30, or 76.7%. Twenty-eight validate, or 93.3%. Signals, incidents, people, routes, actions, duplicates, false positives, and open records retain separate counts.

Preserve the original signal while urgent action proceeds

A polished form can delay urgent action or erase the first account. Aaliyah lets protection proceed while preserving the original signal, clock, and later corrections.

Test AAC reports, duplicates, missing clocks, and late screens

Aaliyah tests injury, medical emergency, privacy signal, blocked cyberattack, medication concern, facility hazard, anonymous report, AAC, interpreter, vendor notice, duplicate, and false positive. Each case states the event or signal, affected people and services, immediate protection, source, owner, evidence, communication, open route, decision, correction, validation result, and next review.

Close review with unresolved work visible

Aaliyah confirms scope, sources, authority, access, evidence, safeguards, reporting routes, communications, decisions, recovery, corrections, and fresh validation. The incident intake and initial triage stays draft until every named reviewer finishes. Open work retains its owner, age, effect, and next action.

Place incident intake within organizational guidance

Aaliyah uses the CASP Organizational Guidelines public overview for high-level business, clinical-operations, and risk-management context. CASP sells the detailed guidelines. The page presents an editorial incident intake and initial triage; the public overview does not prescribe this artifact, its fields, or its decision rights. The OIG General Compliance Program Guidance is voluntary and nonbinding. It supports reporting, investigation, correction, auditing, monitoring, and oversight concepts while actual duties come from the governing source.

Keep professional authority clear during response

The current BACB Ethics Code applies to BCBA and BCaBA certificants and people who completed an application for either credential. It addresses competence, client and stakeholder involvement, consent and assent when applicable, documentation, risk, delegation, evaluation, continuity, and reporting within scope. BACB has no separate jurisdiction over organizations or corporations. Aaliyah therefore maps covered professional duties separately from entity, owner, payer, regulator, and software roles.

Separate workplace recording and urgent reports

OSHA's recordkeeping page distinguishes recording, reporting, and electronic submission. Its fatality and severe-injury page describes federal reporting routes and clocks for covered work-related events. Aaliyah verifies event, employer, establishment, state-plan, and exception scope. Emergency response, clinical records, workers' compensation, insurance, licensing, and other reports keep their own routes.

Route privacy and security events through current sources

For HIPAA covered entities and business associates as applicable, current 45 CFR 164.308 includes security-incident procedures. HHS's Breach Notification Rule guidance explains the unsecured-PHI breach presumption, exceptions, low-probability assessment, and recipient-specific notice paths. Aaliyah keeps alerts, security incidents, impermissible uses or disclosures, breaches, business-associate notices, and non-HIPAA events distinct.

Use cybersecurity guidance within its scope

NIST SP 800-61 Revision 3, finalized in April 2025, integrates cybersecurity incident response across the six Cybersecurity Framework 2.0 functions. It is general guidance and does not replace HIPAA, state law, contracts, payer duties, clinical authority, or emergency action. Aaliyah adapts its preparation, detection, response, recovery, learning, and evidence concepts only where they fit the practice's systems and obligations.

Preserve usable communication throughout response

The DOJ effective-communication guidance addresses covered entities' communication with people who have communication disabilities, subject to the law's scope and standards. The ASHA AAC portal says AAC users should always have access to their communication tools or devices. Aaliyah provides accessible intake, updates, interviews, safeguards, emergency messages, corrections, and recovery communication while keeping needed AAC available.

Related resources

Sources