To request concurrent ABA services without double counting, map every overlapping interval by participant, provider, service, clinical purpose, setting, exact start and end, payer rule, documentation, and requested unit. Verify that each service independently meets its current requirements and that no person's or provider's time is used incompatibly. Preserve denied combinations, partial overlaps, absences, corrections, and payer-specific concurrency decisions.

Define Talia's concurrent ABA services request

Talia starts with a timeline rather than totals. She can see who was actively delivering which service to whom, which activities were distinct, and where one person's time appears twice. The minute-level concurrency map preserves person-specific evidence, source scope, qualified authority, calculations, versions, and open work.

Build the fields Talia needs

The record captures concurrency case ID, member payer product and authorization, date and setting, each participant, each provider and role, service and clinical purpose, exact interval, direct or indirect state, group or individual state, protocol and plan, payer concurrency source, permitted combination, modifier when supported, documentation for each service, unit calculation, provider conflict, participant absence, partial overlap, correction, reviewer, and validation. Structured fields make repeated values and release gates testable. Narrative retains clinical reasoning, client perspective, alternatives, uncertainty, disagreement, and source limits.

Protect the concurrent ABA services boundary

Concurrent authorization never means every simultaneous combination is clinically appropriate, code-compliant, covered, payable, or feasible. The ABA Coding Coalition FAQ describes several stakeholder examples and restrictions, but licensed CPT, payer policy, contracts, law, provider authority, and actual service evidence control.

Apply Talia's workflow

Talia draws a lane for each participant and provider, adds exact intervals, and labels direct activity and purpose. She tests the combination under the current rule, checks whether one provider is claiming incompatible work, and calculates only supported minutes. Scheduling uses the approved configuration and stops when staff, participant, setting, or service changes.

Calculate time and units from supported service

Talia begins with qualified clinical design and current payer rules. Each line shows eligible dates, frequency, duration, actual participant and provider configuration, unit basis, exclusions, rounding, and total. The worksheet never creates a service, expands scope, or converts administrative and unsupported time into clinical units.

Keep access and choice in the release gate

Talia confirms accessible information, AAC and language supports, consent and assent when applicable, privacy, safe participation, and a usable pause or withdrawal response. Disability or communication needs trigger accommodation work and clinical review rather than an adverse fit assumption.

Work through Talia's fictional example

Talia locks 32 fictional concurrency cases. Twenty-five map participants, providers, services, intervals, rules, documentation, and units. One double counts a QHP, two use scheduled rather than actual overlap, one bills an absent participant, one mixes group and individual evidence, and two await payer interpretation. Five repair. Two remain held. This synthetic example tests workflow and denominator logic. It supplies no coding, clinical, payer, legal, privacy, coverage, claim, or payment conclusion for a real person.

Calculate Talia's measures honestly

Initial case readiness is 25 of 32, or 78.1%. Thirty cases validate, or 93.8%. Cases, participants, providers, services, intervals, units, and payer decisions retain separate units.

Address the main concurrent ABA services risk

Totals can conceal duplicate person-time, impossible provider assignments, absent participants, or unsupported code combinations that become visible only on a shared timeline.

Test Talia's request against hard cases

Talia tests technician plus QHP, two technicians, individual plus group, caregiver guidance during direct care, QHP treating and directing, partial overlap, late arrival, early departure, absent participant, and corrected time. Each test retains its source, participants, exact interval when relevant, expected safeguard, observed result, correction owner, retest, and final disposition.

Run Talia's release test

Talia selects three proposed combinations and rebuilds them on a minute-level lane diagram. A reviewer must account for every provider and participant, explain each service purpose, locate supporting documentation, and reproduce units after partial overlap. The test removes one participant and delays one provider to confirm that scheduled concurrency never survives as actual service. Any impossible assignment, duplicated minute, or unsupported combination remains held for qualified review.

Close the service-specific state with open work visible

Talia confirms the clinical source, current licensed and payer rules, provider authority, access, schedule, unit math, documentation, and unresolved work. The concurrent ABA services request remains draft until every named reviewer finishes. Open items keep an owner, age, safeguard, deadline, and escalation route.

Keep service design under qualified clinical authority

Talia uses the CASP ABA Practice Guidelines Version 3.0 public summary for high-level autism-treatment context and the current BACB Ethics Code for covered behavior analysts' competence, client involvement, consent and assent when applicable, assessment, intervention, risk, documentation, and billing duties. Organizational ownership, payer rules, and software do not create clinical authority.

Use licensed code materials for the requested period

The AMA CPT overview identifies the medical code set, and the AMA licensing FAQ explains its licensing boundaries. This page paraphrases service concepts and never reproduces a proprietary descriptor. Talia verifies the licensed code set, guidelines, effective date, and payer implementation before using any identifier or unit rule.

Treat stakeholder coding guidance as secondary

The ABA Coding Coalition FAQ offers public stakeholder education on assessment, direct treatment, protocol modification, caregiver guidance, groups, concurrency, direct and indirect activity, and payer variation. The Coalition is not the AMA or a payer. Talia uses it to frame questions, then checks licensed materials and governing payer sources.

Keep coding edits within their actual scope

The CMS coding overview explains that a code's existence does not determine coverage or payment. The CMS Medicaid NCCI FAQ addresses Medicaid correct-coding edits rather than medical necessity, prior authorization, or coverage. Talia records the program, product, service, edit version, date, and result because state programs may add more restrictive edits and private payer implementation needs separate verification.

Separate preauthorization from payment

The HealthCare.gov preauthorization glossary says preauthorization may be required and is not a promise that the plan will cover cost. Talia keeps clinical recommendation, authorization, provider eligibility, documentation, clean-claim status, adjudication, and payment as separate states.

Use the CMS process rule within its scope

The CMS-0057-F fact sheet applies to named impacted payer classes and medical items and services excluding drugs. It creates no universal ABA packet or service rule. Talia uses the current Nevada Medicaid FA-11E form and instructions only as one program's request-structure example, then verifies the actual member route independently.

Control information and preserve access

Talia applies HHS treatment, payment, and healthcare-operations guidance only within its entity, relationship, and purpose conditions. The DOJ Title III overview addresses public-access duties within its scope. The ASHA AAC Practice Portal says AAC users should always have their tools or devices. Authorization design preserves communication, privacy, and accessibility.

Related resources

Sources