To separate ABA interruption suspension discontinuation discharge transfer and closure, classify the event before changing schedules or access. An interruption pauses expected service. A suspension is a temporary hold under a defined authority. Discontinuation ends a service relationship or service. Discharge is a setting-specific label that may combine clinical and administrative meanings. Transfer changes responsibility through an accepted handoff. Closure reconciles remaining operational work. Each state needs its own trigger, decision owner, date, client route, and evidence.
Define Marek's service-state classification
Marek keeps words from doing hidden work. The map records whether the change comes from the client, qualified clinician, payer, employer, regulator, contract, capacity condition, or receiving provider and what that source can actually decide. The service-state decision map names the client, trigger, state, authority, communication, access, safety, plan, dates, owners, open work, evidence, validation, and review status.
Build the fields Marek needs
The working record captures event and case ID, original report, trigger, candidate states, client and authority, communication and access, immediate safety route, clinical recommendation, coverage action, organizational decision, workforce action, privacy or record event, governing source, decision owner, start and expected end, last service, plan due date, interim service, hold conditions, appeal or review, referral, receiving acceptance, record transfer, operational tasks, reclassification trigger, final state, evidence, and closure. Structured fields keep clients, states, dates, decisions, referrals, tasks, and evidence searchable. Narrative preserves clinical reasoning, client perspective, uncertainty, dissent, and context while original records, communications, plans, corrections, and audit history remain attributable.
Keep each authority in its own lane
Marek separates client choice, representative authority, qualified clinical recommendation, payer coverage, organizational capacity, employment action, privacy, record access, billing, reporting, and legal review. Software and coordinators can route evidence and enforce holds; they cannot author clinical rationale or infer that one state decides every other state.
Apply Marek's workflow
Marek defines observable start and end events. A canceled week becomes an interruption only when expected services, cause, communication, and restoration path are known. A transfer requires receiving acceptance and an effective responsibility date, while sending records alone remains a record event.
Allow parallel states without merging them
Coverage may end while clinical recommendation continues. Employment may end while the organization retains the service relationship. The client may request a transfer while records and claims remain open. Marek links parallel state records and identifies the controlling source for each.
Control urgent action and changed facts
Marek routes immediate danger, medical emergency, suspected abuse or neglect, privacy incident, and other time-sensitive duties through current authorized paths. A changed client state, preference, risk, role, payer action, setting, recipient, record, or source reopens affected tasks. Interim action records authority, scope, start, expiry, communication, and reassessment.
Work through Marek's fictional example
Marek locks 33 service events. Twenty-five are classified with trigger, authority, state, dates, client route, continuity, and end evidence. One payer denial is mislabeled clinical discharge, one record transfer is called responsibility transfer, two interruptions have no restoration event, one client request is missing, and three cases need parallel states. Five repair. Three remain open. This synthetic example tests workflow and denominator logic. It supplies no clinical, privacy, payer, licensing, notice, reporting, employment, contract, record-access, or legal conclusion for a real person or organization.
Calculate Marek's measures honestly
Initial classification integrity is 25 of 33, or 75.8%. Thirty events validate, or 90.9%. Events, states, clients, services, plans, dates, and closures retain separate units.
Address the main service-state classification risk
Ambiguous state labels can turn a temporary gap into an unintended service end or let an administrative close erase clinical and client obligations.
Test Marek's artifact against hard cases
Marek tests missed week, staffing hold, clinician leave, client request, payer denial, goal completion, provider transfer, facility closure, and chart close. Each case records client choice, access, state, authority, safety, plan, referral, records, payer work, task, validation, and next review.
Close with continuity and open work visible
Marek confirms accessible client communication, clinical and payer boundaries, current safety, interim care, plan delivery, accepted ownership, referral and transfer status, records, operational tasks, validation, and residual uncertainty. The service-state classification remains draft until every named reviewer finishes. Open work retains an owner, age, affected people, interim safeguard, and next action.
Place Marek's continuity work inside accountable operations
Marek uses the CASP Organizational Guidelines public overview for high-level business, clinical-operations, and risk-management context. The ABA Practice Guidelines Version 3.0 public summary concerns ABA behavioral health treatment for people diagnosed with autism and places planning, implementation, and evaluation within standards of care. CASP licenses the details. This service-state classification is an editorial model, not a CASP protocol.
Apply the behavior-analyst continuity standards within their scope
Marek uses the current BACB Ethics Code, which applies to BCBA and BCaBA certificants and people who completed an application. Standards 3.14, 3.15, and 3.16 separately address interruption planning and continuity efforts, discontinuation circumstances and written planning, and transition plans with target dates, activities, responsible parties, review, and relevant collaboration. BACB has no separate organization or corporation jurisdiction.
Use treatment disclosure routes without assuming transfer
Marek uses current 45 CFR 164.506 for specified treatment, payment, and healthcare-operations uses and disclosures after confirming entity status and conditions. A treatment disclosure can support continuity, yet it does not transfer clinical responsibility, create licensure or payer status, require a recipient to accept the case, or replace consent to the service under other law.
Preserve individual record-access rights
Marek uses HHS right-of-access guidance and current 45 CFR 164.524 for requests by an individual or personal representative to inspect or obtain PHI in a designated record set, subject to rule-specific exclusions, form, timing, fee, and denial provisions. Provider-to-provider disclosure and individual access are different routes, and service end does not erase applicable record rights.
Verify who may direct the transition
Marek uses HHS personal-representative guidance, which says applicable law determines authority and scope and describes minor-specific and endangerment rules. Separate HHS family-involvement guidance describes conditions for directly relevant disclosure to involved people. A family label, emergency contact, or receipt of information does not itself create decision authority.
Keep communication and AAC available through service changes
Marek uses the ASHA AAC Practice Portal, which says AAC users should always have access to their communication tools or devices. Transition planning preserves the person's system, positioning, vocabulary, wait time, partner response, charging, and backup. Practice-owned property is reconciled without removing the person's own communication or access support.
Use coordination measurement as orientation rather than a mandate
Marek uses the AHRQ Care Coordination Measures Atlas Update as a broad, dated measurement framework. The Atlas was updated in 2014, notes that no consensus definition had fully evolved, and includes patient or family, professional, and system perspectives. It is not a current ABA rule, legal standard, transition protocol, or proof of causal benefit.
Related resources
- Write an ABA Service-Interruption Plan for the Service Agreement.
- Build an ABA Service-Interruption, Transition, Discontinuation, and Closure System.
- Respond When an ABA Clinician, Site, Vendor, or Critical System Becomes Unavailable.
- Audit an ABA Service-Interruption, Transition, Discontinuation, and Closure System.
Sources
- Council of Autism Service Providers, Organizational Guidelines public overview.
- Council of Autism Service Providers, ABA Practice Guidelines Version 3.0 public summary.
- Behavior Analyst Certification Board, Ethics Code for Behavior Analysts.
- Electronic Code of Federal Regulations, 45 CFR 164.506, Uses and disclosures for treatment, payment, or health care operations.
- U.S. Department of Health and Human Services, Individuals' Right under HIPAA to Access their Health Information.
- Electronic Code of Federal Regulations, 45 CFR 164.524, Access of individuals to protected health information.
- U.S. Department of Health and Human Services, Personal Representatives.
- U.S. Department of Health and Human Services, Communication with family, friends, and others involved in care.
- American Speech-Language-Hearing Association, Augmentative and Alternative Communication.
- Agency for Healthcare Research and Quality, Care Coordination Measures Atlas Update.