An ABA practice incident notification and deadline register tracks every potentially applicable emergency, client, representative, workforce, privacy, security, payer, insurer, licensing, protective, professional, law-enforcement, and contractual communication route. Each row states the source, entity and event scope, trigger, discovery rule, clock, recipient, content, qualified owner, submission evidence, confirmation, update, correction, and final status without treating one deadline as universal.

Define each notification route and clock

Felix opens potential rows early and lets qualified owners decide applicability. Emergency action proceeds first. A 60-day outer ceiling under one federal rule never becomes permission to wait, and it never controls a state, contract, payer, insurer, licensing, workplace, or client-communication deadline. The notification-route and clock register has a named owner, scope, current sources, qualified decision boundaries, version, role-limited access, evidence location, exception route, change triggers, and retention state.

Record source, trigger, discovery, recipient, content, and confirmation

The working record captures incident and route IDs, potential recipient, source and version, entity and relationship, event scope, trigger question, discovery facts, clock start, deadline and timezone, extension rule, content and format, data minimization, decision owner, legal or clinical consultation, submission channel, attempt, sent time, delivery, confirmation, external reference, follow-up, supplemental notice, correction, status, failed route, escalation, and retained proof. 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.

Track every route separately through disposition

He records an applicability decision for every opened route and preserves the original discovery facts. A later transfer keeps the first clock. One coordinated message can satisfy several rows only when every source permits the same recipient, content, timing, and evidence. Failed delivery triggers the route's prescribed follow-up.

Protect people while classification continues

Felix 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

Felix 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 recipients, clocks, delivery, and escalation

Felix tests urgent, short, business-day, calendar-day, and outer-ceiling clocks; weekends; late discovery; vendor notice; state-plan variation; failed portal delivery; supplemental facts; and an event ultimately found outside a route's scope.

Reconcile the incident across operating systems

Felix 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

Felix 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 Felix's fictional example

Felix locks 32 notification routes. Twenty-four have source, scope, trigger, discovery, clock, owner, content, channel, submission, confirmation, and status. One clock resets at transfer, one route uses the wrong recipient, two sources are stale, one failed delivery lacks escalation, and three applicability decisions lack rationale. Six routes 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 notification-route integrity is 24 of 32, or 75.0%. Thirty validate, or 93.8%. Incidents, routes, recipients, clocks, messages, submissions, confirmations, and open rows remain separate.

Avoid one deadline for a multi-route incident

A single incident deadline can create false confidence. Felix tracks each route from its own source and discovery rule through confirmed disposition.

Test transfer, wrong recipients, failed delivery, and rationale

Felix tests emergency call, client update, OSHA route, privacy route, business-associate notice, payer notice, insurer notice, licensing route, protective report, failed portal, supplemental facts, and inapplicable route. 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

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

Place notification registers within organizational guidance

Felix 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 notification and deadline register; 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. Felix 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. Felix 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. Felix 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. Felix 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. Felix provides accessible intake, updates, interviews, safeguards, emergency messages, corrections, and recovery communication while keeping needed AAC available.

Related resources

Sources