To verify a written ABA authorization decision before service release, match the decision to the member, payer, product, request, provider, service, code, modifier, unit basis, quantity, date span, setting, and conditions. Capture approved, denied, partial, and unclear lines separately. Reconcile the letter, portal, and call evidence, then assign clinical, scheduling, authorization, and billing decisions to their qualified owners. Release only the verified scope.

Define Juno's written authorization decision verification

Juno begins with the actual payer decision artifact and the request version it answers. She treats a portal banner, call statement, fax, and letter as separate evidence until their fields agree or the payer resolves the conflict. The decision-to-release comparison preserves authorization identity, clinical authorship, client access, payer evidence, dates, unit basis, open work, and downstream controls.

Build the fields Juno needs

The record captures decision ID, member, payer legal entity, product, request and submission version, requesting and servicing provider, group, service, code and modifier, unit definition and amount, frequency, effective dates, setting and modality, conditions, approved and adverse lines, authorization number, decision and notice dates, source artifacts, portal as-of time, representative and call reference, conflict state, clinical review, access needs, release owner, holds, test record, and closure. Structured fields make decisions, authorization lines, dates, units, appointments, services, exceptions, and owners searchable. Narrative preserves clinical reasoning, client perspective, source conflicts, uncertainty, corrections, and limits.

Keep clinical authorization service and financial states distinct

Juno separates client choice, clinical recommendation, payer decision, authorization configuration, scheduling, rendered service, documentation, charge, claim, adjudication, payment, appeal, and closure. Software can compare sourced fields and enforce gates. Qualified people retain their actual decision authority.

Apply Juno's workflow

Juno transcribes every material field into a comparison table, has a second person verify the transcription, and keeps each unclear line on hold. The clinician reviews care implications. Scheduling and billing owners receive only the configuration that passed verification.

Verify partial approval at the service-line level

A decision can approve one service, reduce another, omit a requested setting, or use dates that differ from the packet. Juno gives each combination its own state. A favorable headline never turns an omitted or adverse component into approval.

Record the calculation evidence and downstream effect

Juno tests one representative future visit against the verified line. The test uses the actual provider, location, service, date, planned duration, and unit conversion. It also checks whether the current clinical plan still supports that visit. A passed test confirms only that configuration. Other providers, locations, services, or dates keep their own gates. When the payer later issues a corrected decision, Juno creates a new version, shows what changed, and reopens every affected schedule or claim control.

Protect urgent action and current authority

Juno routes imminent danger, medical emergency, urgent clinical need, suspected abuse or neglect, privacy incidents, and other time-sensitive duties through current authorized paths. A payer workflow never delays emergency action. Changes to the member, product, provider, service, plan, setting, decision, date, unit, or source reopen affected gates.

Work through Juno's fictional example

Juno locks 30 written decisions. Twenty-four match the request and contain verified lines, dates, units, providers, settings, conditions, artifacts, clinical review, and release evidence. One uses the wrong request, one drops a partial denial, one misreads the unit basis, one misses a provider limit, and two retain unresolved source conflicts. Four repair. Two remain open. This synthetic example tests workflow and denominator logic. It supplies no clinical, payer, authorization, privacy, coverage, claim, payment, or legal conclusion for a real person or plan.

Calculate Juno's measures honestly

Initial decision integrity is 24 of 30, or 80.0%. Twenty-eight decisions validate, or 93.3%. Decisions, request versions, service lines, providers, settings, dates, and release tests retain separate units.

Address the main written authorization decision verification risk

A single approval flag can expose clients and staff to service disruption or unsupported claims when a material line, date, provider, setting, or condition differs from the request.

Test Juno's artifact against hard cases

Juno tests full approval, partial approval, unit reduction, omitted line, provider restriction, setting restriction, corrected notice, portal lag, conflicting call, and changed clinical plan. Each case retains its source, affected person, current state, qualified owner, clock, communication, decision, validation, and next action.

Close the exact state with open work visible

Juno confirms source scope, clinical ownership, client access, authorization line, downstream controls, and unresolved work. The written authorization decision verification remains draft until every named reviewer finishes. Open items retain an owner, age, safeguard, deadline, and escalation route.

Keep clinical decisions and authorization states separate

Juno 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. These sources do not create payer approval, coverage, or payment.

Treat prior authorization as a coverage process

The HealthCare.gov preauthorization glossary describes preauthorization as a plan decision made before certain nonemergency services and explains that it is not a promise the plan will cover cost. Juno therefore keeps authorization, eligibility, benefits, clinical recommendation, service, claim acceptance, adjudication, and payment as separate states.

Use the CMS interoperability rule within its payer scope

The CMS-0057-F fact sheet applies its Prior Authorization API requirements to listed impacted payer classes for medical items and services excluding drugs, generally beginning January 1, 2027. It says the response communicates approval and the end date or circumstance, denial and reason, or a request for more information. Juno treats that as scoped federal process context, not proof that a payer endpoint, authorization, or ABA service is supported.

Use a state program only as a scoped field example

The current Texas Medicaid prior-authorization chapter states that prior authorization is not a guarantee of payment and, for its specified claims, identifies authorization number, NPI, procedure code, dates, required modifiers, and units from the authorization letter. Its claims-filing chapter supplies program-specific claim routes. Juno uses those fields as a concrete Texas example and verifies every other payer independently.

Separate code and provider identifiers from authority

The CMS coding overview explains that a code's existence does not determine coverage or payment. The current CMS NPI fact sheet says an NPI identifies a provider and does not validate licensure or credentialing, enroll a provider, or guarantee payment. Juno keeps code, NPI, licensure, competence, enrollment, contract, roster, authorization, and payment distinct.

Control authorization information by purpose

Juno applies HHS treatment, payment, and healthcare-operations guidance and minimum-necessary guidance only after confirming the entity, relationship, purpose, and applicable exception. Role-limited configurations and audit samples use the information needed for their task while preserving full source evidence in the authorized record.

Keep compliance and access controls visible

Juno uses the OIG General Compliance Program Guidance as voluntary, nonbinding orientation for risk assessment, auditing, reporting, incentives, and corrective action. The DOJ Title III overview applies within its public-accommodation scope. The ASHA AAC Practice Portal says AAC users should always have their communication tools or devices. Scheduling, notices, choices, and continuity preserve usable access.

Related resources

Sources