To build a traceable ABA requested-units calculation, begin with the qualified clinician's service design and the payer's current unit rules. Calculate each service line separately from eligible dates, frequency, duration, participant, provider, setting, modality, and unit conversion. Show exclusions, holidays, start assumptions, partial weeks, rounding, and totals. Reconcile the result to the plan, form, portal, and narrative before submission.

Define Ravi's traceable requested-units calculation

Ravi keeps the clinical recommendation upstream of the arithmetic. The worksheet translates an approved clinical design into a payer request; it never selects dosage, increases hours to use a benefit, or treats a code as proof of coverage. The requested-units worksheet preserves sources, versions, decision authority, corrections, validation, and open work.

Build the fields Ravi needs

The record captures calculation ID, plan version and clinician decision, payer product and source, service and code, participant and provider role, setting and modality, requested start and end, eligible weekdays, partial weeks, excluded dates, frequency, duration, unit size, rounding rule, units per event, event count, subtotal, adjustment, final units, cross-document values, reviewer, and validation. Structured fields support comparison and routing. Narrative retains clinical reasoning, context, client perspective, uncertainty, disagreement, corrections, and source limits.

Apply Ravi's workflow

Ravi creates one row per service line, expands the requested span into eligible dates, applies the planned cadence, and converts supported time using the current rule. He retains both time and units, shows each excluded day, and recalculates after any date, frequency, duration, code, or setting change. A second reviewer rebuilds selected rows from source inputs rather than checking only the total.

Make every total reproducible

In a fictional 12-week period, four planned three-hour visits per week would create 48 visits. Two ineligible holidays leave 46 visits. That is 138 hours and, under a hypothetical 15-minute unit basis, 552 units. A separate weekly one-hour caregiver service across 12 eligible weeks is 12 hours or 48 units. These lines never combine unless the payer explicitly uses the same service and unit basis.

Separate related operational and payer states

Ravi tracks source collection, clinical authorship, administrative assembly, review, approval, release, transmission, receipt, request-for-information, payer decision, authorization, service, claim, adjudication, and payment separately. Each state has its own evidence, owner, timestamp, and reopening rule.

Protect urgent care and current information

Ravi routes imminent danger, medical emergencies, suspected pain, urgent clinical needs, suspected abuse or neglect, privacy incidents, and other time-sensitive duties through current authorized paths. Packet work never delays emergency, medical, protective, or mandated action. Material new information reopens the affected review.

Work through Ravi's fictional example

Ravi locks 30 worksheets. Twenty-four reproduce from current clinical, calendar, and payer inputs. One uses calendar days instead of eligible dates, two omit holidays, one rounds every session upward, one mixes hours and units, and one carries an old plan frequency. Four repair. Two remain held. This synthetic example tests workflow and denominator logic. It supplies no payer, clinical, privacy, legal, coverage, claim, or payment conclusion for a real person.

Calculate Ravi's measures honestly

Initial calculation integrity is 24 of 30, or 80.0%. Twenty-eight worksheets validate, or 93.3%. Service lines, eligible dates, events, hours, units, exclusions, and totals retain separate units.

Address the main traceable requested-units calculation risk

Untraceable unit math can overstate or understate a request, obscure a clinical change, or make a later correction impossible to reproduce.

Test Ravi's artifact against hard cases

Ravi tests partial first week, partial last week, holiday, planned absence, leap day, daylight-saving change, mixed unit sizes, frequency change, telehealth line, and decimal duration. Every test records the starting state, expected safeguard, observed result, affected artifact, correction owner, retest, and final disposition.

Run Ravi's release test

Ravi tests the worksheet by changing one input at a time. Moving the start date changes eligible events, while changing a provider identifier leaves the clinical quantity unchanged unless a governing rule changes eligibility. He then rebuilds three sampled service lines from the plan and calendar. The released total must equal the sum of visible line subtotals, with every adjustment and rounding step named.

Close the packet state with open work visible

Ravi confirms the source set, qualified authorship, client access, validation evidence, released version, and unresolved work. The traceable requested-units calculation remains draft until every named reviewer finishes. Open items retain an owner, age, safeguard, deadline, and escalation route.

Keep clinical content with qualified authors

Ravi 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, documentation, and billing duties. Neither source creates a payer rule or authorizes administrative staff or software to make clinical decisions.

Keep prior authorization separate from payment

The HealthCare.gov preauthorization glossary explains that preauthorization may be required and is not a promise that a plan will cover cost. Ravi keeps benefit, network, prior authorization, clinical recommendation, service release, 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. Its process rules and API requirements do not supply one national ABA packet, code map, source hierarchy, or medical-necessity standard. Ravi verifies the member's actual payer, product, contract, route, and effective date.

Use payer forms as scoped examples

The current Nevada Medicaid FA-11E form and instructions illustrate program-specific fields, evidence, timing, signatures, and attachments. The Texas Medicaid prior-authorization chapter says authorization is not a guarantee of payment and supplies its own field and claim relationships. Ravi never generalizes either program to another payer.

Separate codes and identifiers from authority

The CMS coding overview explains that a code's existence does not determine coverage or payment. The CMS NPI fact sheet says an NPI identifies a provider and does not validate licensure or credentialing, enroll the provider, or guarantee payment. Ravi verifies every separate clinical, legal, payer, and operational gate.

Control information by purpose

Ravi applies HHS treatment, payment, and healthcare-operations guidance and minimum-necessary guidance only after confirming entity, relationship, purpose, and applicable exception. Packet access, exports, reviews, test cases, and transmissions use authorized information and retain source attribution.

Preserve access and communication

The DOJ Title III overview addresses equal opportunity, effective communication, and reasonable modifications within its scope. The ASHA AAC Practice Portal says AAC users should always have access to their communication tools or devices. Ravi keeps communication and accessibility evidence intact without treating an access need as poor fit.

Use compliance guidance as orientation

Ravi uses the OIG General Compliance Program Guidance as voluntary, nonbinding orientation for risk assessment, auditing, reporting, incentives, and corrective action. Current payer, program, record, coding, privacy, contract, and professional sources govern the packet.

Related resources

Sources