To request QHP-led ABA group treatment, connect the group to every participant's individualized need and goals. Define the shared purpose, group composition, qualified professional, protocols, patient-present clinical activity, setting, access, AAC, safety, schedule, duration, requested units, attendance, person-specific documentation, and review criteria. Verify current licensed coding and payer rules rather than treating professional presence as sufficient.

Define Samir's QHP-led ABA group treatment request

Samir describes what the QHP will do with the participants and how the activity addresses each plan. He keeps group leadership, protocol evaluation or modification, staff direction, and indirect preparation distinguishable. The QHP group clinical-activity plan preserves person-specific evidence, source scope, qualified authority, calculations, versions, and open work.

Build the fields Samir needs

The record captures group design ID, participant and plan, individualized need goal and measure, shared clinical purpose, group rule and composition, QHP identity authority competence enrollment and roster, protocol and patient-present activity, other staff roles, setting modality and accessibility, consent assent privacy and safety, schedule duration dates and units, attendance and partial participation, individual data and note, indirect preparation, review decision, payer source, 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 QHP-led ABA group treatment boundary

The public stakeholder FAQ discusses QHP-led group treatment and patient-present protocol activity. It does not replace licensed CPT or payer requirements. QHP attendance alone cannot turn a technician group, staff training, case conference, or written-protocol work into this service.

Apply Samir's workflow

Samir verifies each participant's fit, defines the QHP activity, and maps time by participant and provider. He checks access, privacy, and safe exit before scheduling. Each participant receives a separate source record, note, and unit decision; shared group documentation supplements rather than replaces person-specific evidence.

Calculate time and units from supported service

Samir 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

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

Samir locks 21 fictional participant requests. Sixteen show individualized need, shared purpose, QHP activity, group composition, access, safety, attendance, notes, and units. One relies on QHP presence, one lacks an individual measure, one double counts staff time, one has no privacy plan, and one awaits payer confirmation. Three 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 Samir's measures honestly

Initial participant-request readiness is 16 of 21, or 76.2%. Nineteen validate, or 90.5%. Groups, participants, professionals, clinical intervals, protocols, observations, and units retain separate units.

Address the main QHP-led ABA group treatment risk

A QHP-led label can obscure an undefined group purpose, indirect work, missing participant evidence, or concurrent time that the payer route does not support.

Test Samir's request against hard cases

Samir tests QHP leads group, QHP observes technician group, protocol change, no change needed, absent member, partial attendance, telehealth group, privacy concern, individual crisis, and indirect preparation. Each test retains its source, participants, exact interval when relevant, expected safeguard, observed result, correction owner, retest, and final disposition.

Run Samir's release test

Samir gives the reviewer a timeline for the QHP and every participant. The reviewer must identify the group clinical activity, each individualized purpose, actual attendance, patient-present interval, and person-specific record. Written preparation and later data review remain visible outside the direct interval. The design fails when QHP presence is the only service description or when shared documentation cannot support each participant's request and outcome evidence under the current source.

Close the service-specific state with open work visible

Samir confirms the clinical source, current licensed and payer rules, provider authority, access, schedule, unit math, documentation, and unresolved work. The QHP-led ABA group treatment 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

Samir 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. Samir 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. Samir 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. Samir 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. Samir 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. Samir 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

Samir 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