Open and Classify an ABA Prior Authorization Request

Define Fari's prior-authorization request intake and classification

Fari creates the request before collecting a full packet. She records the narrow purpose, due work, client communication needs, safety concerns, current clinical owner, payer source, and exact event the practice is trying to schedule or bill. The authorization request state record preserves request identity, source authority, clinical authorship, client access, evidence states, owners, clocks, decisions, open work, and downstream controls.

Build the fields Fari needs

The record captures request ID, member and product, payer and administrator, service and setting, provider and location, request type and trigger, referral or order when applicable, assessment or treatment state, current clinical recommendation, benefit and network evidence, authorization requirement, submission route, urgency source, source dates, privacy route, client communication and AAC, state, owner, due date, hold reason, escalation, decision, effective span, appeal or reconsideration, scheduling release, service, claim, adjudication, payment, correction, and closure. Structured fields keep members, products, requests, services, sources, versions, submissions, decisions, units, and deadlines searchable. Narrative preserves clinical reasoning, client perspective, ambiguity, conflicts, corrections, and limits while original records and artifacts remain attributable.

Keep payer and clinical decisions with their proper owners

Fari separates client choices, clinical recommendation, consent and assent when applicable, benefit and network evidence, payer authorization, operational submission, privacy, coding, scheduling, service, claim, adjudication, and payment. Automation can compare sourced fields and block incomplete release. It cannot decide clinical content, payer coverage, appeal strategy, or lawful disclosure. Fari also links every request to its predecessor, replacement, appeal, or concurrent-review record so later staff can reconstruct the complete authorization path without merging distinct states.

Apply Fari's workflow

Fari assigns one state from a controlled list and records every transition with its evidence and time. She links related requests without merging them. A new assessment request, treatment request, extension, provider change, location change, appeal, and claim correction each keep their own lifecycle.

Use a state model that prevents premature release

The practice releases only the named next event. Assessment scheduling can have different prerequisites from treatment scheduling. An authorization approval can still leave provider, location, date, code, staffing, consent, or safety work open. Fari's state record blocks silent leaps from benefit confirmation to authorization or from authorization to payment.

Control urgency and changed facts

Fari routes imminent danger, medical emergency, urgent clinical need, suspected abuse or neglect, privacy incident, and other time-sensitive duties through current authorized paths. Payer, product, member, provider, location, service, code, date, source, clinical plan, urgency, route, or decision changes reopen affected gates. Interim action records authority, scope, client impact, expiry, communication, and reassessment.

Work through Fari's fictional example

Fari locks 30 request records. Twenty-four identify the member, product, event, service, owner, sources, state, open work, client route, and next decision. One merges two products, one treats benefits as authorization, two omit receipt evidence, one lacks AAC access, and one closes with an open decision. Four repair. Two remain open. This synthetic example tests workflow and denominator logic. It supplies no clinical, payer, coding, privacy, coverage, appeal, claim, payment, or legal conclusion for a real member or plan.

Calculate Fari's measures honestly

Initial request integrity is 24 of 30, or 80.0%. Twenty-eight records validate, or 93.3%. Members, products, requests, services, submissions, decisions, claims, and payments retain separate units.

Address the main prior-authorization request intake and classification risk

A single open or approved label can hide which payer product, service, provider, dates, evidence, and decision the status actually covers.

Test Fari's artifact against hard cases

Fari tests initial assessment, treatment start, concurrent request, provider change, location change, payer switch, returned request, partial approval, appeal, and claim hold. Each case retains the original evidence, affected person, current state, source, owner, clock, decision, communication, correction, and next action.

Close only after the named state is proven

Fari confirms request identity, source scope, clinical ownership, access, evidence, payer state, downstream controls, and unresolved work. The prior-authorization request intake and classification remains draft until every named reviewer finishes. Open items retain an owner, age, client impact, current safeguard, due date, and escalation route.

Keep clinical authorship and client participation in scope

Fari uses the CASP ABA Practice Guidelines Version 3.0 public summary only 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 payer coverage. Operations and software surface requirements while qualified clinicians retain clinical authorship.

Apply the current CMS rule to its actual payer classes

Fari uses the CMS-0057-F fact sheet and CMS FAQ for the rule's impacted payers, non-drug scope, operational provisions beginning in 2026, and APIs generally beginning January 1, 2027. Other commercial and employer plans fall outside its mandatory payer scope. A required API never proves that a specific endpoint is live, complete, current, or applicable to this request.

Keep authorization separate from a payment promise

Fari uses the HealthCare.gov preauthorization glossary, which explains that preauthorization may be required before certain services and is not a promise that the plan will cover the cost. Benefit, network, authorization, clinical appropriateness, scheduling, claim acceptance, clean-claim status, adjudication, patient responsibility, and payment stay separate.

Use and disclose information through the correct route

Fari uses HHS treatment, payment, and healthcare-operations guidance and minimum-necessary guidance only after confirming HIPAA entity, relationship, purpose, and exception scope. Payment and operations work generally require role-based minimum-necessary controls. The treatment exception for provider disclosures and requests is not blanket access for every authorization worker.

Use compliance guidance as orientation

Fari uses the OIG General Compliance Program Guidance as voluntary, nonbinding orientation for federal healthcare compliance, reporting, risk assessment, auditing, incentives, and corrective action. It does not validate a payer requirement, coding choice, clinical recommendation, authorization route, claim, or payment. Current product, contract, program, law, and professional sources control.

Make every authorization contact accessible

Fari uses the DOJ Title III overview for covered public-accommodation duties such as effective communication and reasonable modifications, subject to the law's scope and defenses. The ASHA AAC Practice Portal says AAC users should always have access to communication tools or devices. Contacts, forms, portals, decisions, and review options preserve usable language, communication, and disability access.

Related resources

• Verify the Member, Product, Benefit, Network, and ABA Authorization Route.
• Reconcile a Partial ABA Prior Authorization Approval.
• Determine Whether an ABA Assessment Requires Prior Authorization.
• Monitor ABA Prior Authorization Decision Deadlines and Escalations.

Sources

• Council of Autism Service Providers, ABA Practice Guidelines Version 3.0 public summary.
• Behavior Analyst Certification Board, Ethics Code for Behavior Analysts.
• Centers for Medicare and Medicaid Services, Interoperability and Prior Authorization Final Rule CMS-0057-F fact sheet.
• Centers for Medicare and Medicaid Services, Interoperability and Prior Authorization Frequently Asked Questions.
• HealthCare.gov, Preauthorization glossary.
• U.S. Department of Health and Human Services, Uses and Disclosures for Treatment, Payment, and Health Care Operations.
• U.S. Department of Health and Human Services, Minimum Necessary Requirement.
• U.S. Department of Health and Human Services Office of Inspector General, General Compliance Program Guidance.
• U.S. Department of Justice, Businesses That Are Open to the Public.
• American Speech-Language-Hearing Association, Augmentative and Alternative Communication.