An ABA appointment status taxonomy gives each visit one current operational state with defined entry criteria, decision authority, timestamp, allowed transitions, and downstream meaning. It distinguishes planned, held, released, in service, completed, canceled, and unresolved work while preserving clinical, payer, and financial facts in separate fields. The taxonomy supports accurate schedules without pretending one status proves service, claim acceptance, or payment.
Define the core states
A practical sequence may include proposed, held, released, confirmed, in service, completed, canceled, and unresolved. Add changed or rescheduled as linked events rather than overwriting the original visit. Define exactly when each state begins and which role may set it.
Create a state contract
Document every state in a table:
| State field | Required definition |
|---|---|
| Entry event | Observable fact or authorized decision |
| Owner | Role allowed to set or approve the state |
| Required evidence | Fields, source, date, version |
| Allowed transitions | Valid next states and triggers |
| Downstream effect | Scheduling, notice, time, charge or hold action |
| Exit or correction | Completion event and preserved history |
Use one current operational state and retain the full event history. Avoid state names whose meaning changes by team.
Keep reasons and facts separate
A status answers what happened operationally. A reason records the observed condition or authorized decision. Store client request, staff issue, access failure, payer hold, clinical change, site problem, or weather as separate attributes with source and time.
Represent changes with linked visits
A reschedule should end or change the original visit under its authorized state and create a replacement with a new identifier. A makeup links to the original loss. An early end preserves scheduled and actual times. This keeps service-loss and recovery reporting honest.
Do not reuse one appointment row until it looks successful. Historical schedules, notices, staff time, clinical records, authorization use, and claims depend on the version that actually governed each event.
Avoid overloaded green checks
HealthCare.gov warns that preauthorization does not promise cost coverage. A released visit still needs current clinical, provider, location, access, and schedule evidence. Completion should reflect actual service, while documentation, charge, claim, adjudication, and payment retain distinct states.
Separate confirmation from consent and readiness
A family confirmation can mean receipt, acceptance of the time, or intent to attend, depending on the process. Define the event. It does not replace required consent, assent when applicable, clinical approval, payer state, qualified staff, supervision, or access support.
Likewise, staff acknowledgment means the assignment was received. Assignment release should require the full configuration. Keep each acknowledgment and decision attributable to the person or role that made it.
Assign decision rights
The BACB Ethics Code addresses clinical accountability, client involvement, risk, documentation, and billing for covered professionals. Operations maintains appointment state. Qualified roles own clinical, payer, privacy, access, workforce, and financial decisions within their scope.
Design corrections as events
When a state is wrong, append a correction with original state, corrected state, author, time, reason, source, and downstream impact. Preserve the original timestamp and do not make a late correction appear to have occurred earlier.
Reconcile notifications, staff assignments, timekeeping, documentation, authorization, charges, and claims that relied on the wrong state. A corrected calendar badge is only the first step.
Represent compound events without inventing hybrid states
One appointment may be confirmed, then delayed, shortened after qualified review, completed, and later corrected. Store those as timed events and facts linked to one visit rather than creating a status such as "confirmed-late-partial-corrected." Keep the current operational state easy to use while preserving the history needed for clinical, payer, payroll, family communication, and audit work.
Define precedence when events arrive out of order. A mobile update may post after an office correction, or an interface may resend an earlier event. Use event identity, source, effective time, recorded time, authority, and correction links to decide what the current view displays. Never erase a valid earlier event simply because the display needs one label. If sources conflict, hold the affected downstream action and route the discrepancy to its owner.
A fictional day
Elm River ABA starts with 30 released visits. Twenty-four complete, two client-cancel, one practice-cancels, one ends early, one is held before start, and one remains unresolved at close. Status completeness is 29 of 30, or 96.7%. The unresolved visit retains owner, age, and next action.
Keep the categories mathematically distinct
The 24 completed and five other resolved states total 29. The unresolved visit stays in the original 30-visit cohort. If ended early is also classified as completed, the taxonomy must specify whether it is a completion subtype or mutually exclusive outcome so it is not counted twice.
Report delivered service minutes and final reconciliation separately. Status completeness shows whether each visit has an accountable operational state, not whether the intended service or downstream work was complete.
Test transitions
Reject impossible moves such as proposed directly to paid, or canceled back to completed without a correction record. Audit timestamps, authorship, reason codes, linked replacement visits, and downstream consistency. Preserve the prior state, new state, source, author, and correction reason.
Test the taxonomy in real failure cases
Run scenarios for duplicate visits, late arrivals, no-shows, staff callouts, client-requested changes, inaccessible communication, system outage, completed visits with late documentation, payer rejection, and correction after claim submission. Confirm each role sees the right next action.
Review unmapped events monthly. Add a state only when it represents a genuinely different operational condition. Too many states make use inconsistent, while too few hide responsible work.
Measure whether people understand the states
Sample schedulers, clinicians, supervisors, billers, and managers with the same visit scenario. Record where they choose different states or next actions. Revise definitions, examples, permissions, or training when disagreement reveals ambiguity.
Owner taxonomy questions
- Does each state have explicit entry, exit, allowed predecessor, owner, evidence, and downstream effect?
- Are status, reason, clinical conclusion, payer state, confirmation, and payment kept in separate fields?
- Can compound events be reconstructed from an immutable, ordered history?
- Are invalid transitions blocked or sent to a correction queue?
- Do client-facing and staff-facing labels use understandable language without implying unsupported facts?
- Has the taxonomy been tested during outages, late-arriving events, duplicate messages, and corrections?
A useful taxonomy supports action during the day and reconstruction afterward. If a state cannot answer what happens next, it belongs in the design review.
A correction without erased history
An appointment is marked canceled by family at 9:05 a.m., then the family reaches the office at 9:12 and explains that staff sent the wrong location. The visit cannot simply be changed to practice canceled with the earlier event deleted. The record retains the original entry, source, time, and message; adds the correction request and evidence; authorizes the corrected reason through the defined role; and updates the current operational view.
Reports using the 9:10 snapshot keep the earlier value with a correction flag. Mature reporting uses the corrected classification and identifies that a prior version changed. The linked communication and data-quality work remains open. This preserves accountability for the inaccurate message without suggesting the family caused the final outcome or making historical dashboards impossible to reproduce.
Related resources
- ABA Late Arrival Response Workflow
- ABA Scheduling KPI Dictionary
- ABA No-Show Response and Outreach Workflow
- ABA Scheduling Ownership and RACI Matrix
