To configure Utah Medicaid ABA telehealth and authorization controls, use the current Autism Spectrum Disorder Services manual to classify the exact service. Verify synchronous audio-video delivery, clinical appropriateness, provider authority, member route, authorization, documentation, and billing. Utah covers remote parent training and certain supervision when clinically appropriate, while the manual excludes specified technician and group services from telehealth.

Define a Utah Medicaid telehealth release

Osric treats telehealth as a service-date configuration. One row identifies the member, program or plan, service, billing and rendering providers, supervisor when applicable, member and practitioner locations, modality, authorization, clinical decision, access supports, platform, note, claim rule, and emergency plan. The row receives a new version when any controlling fact changes.

Read the current Utah Medicaid ASD services authority

Utah Medicaid's ASD services page points to the current provider manual. Its telehealth section allows clinically appropriate remote supervision of an assistant behavior analyst or behavior technician and clinically appropriate parent training. It requires synchronous two-way video and audio, documentation of clinical appropriateness, and one member or one group at a time.

Separate program coverage from payer routing

The manual excludes technician-administered adaptive behavior treatment, technician-administered group treatment, and group protocol modification by a qualified professional from telehealth. Osric treats those exclusions as service-level rules. The manuals page controls current publication status, while PRISM guidance supports enrollment and claim operations without changing clinical coverage.

Use one release gate for every required fact

Osric requires current member route; exact covered service; synchronous modality; provider enrollment, license, role and supervision; one-member or one-group limit; both physical locations; choice; consent and assent when applicable; documented clinical appropriateness; authorization; access; complete note; current billing setup; and emergency plan. A failed gate holds the session or claim at the affected point. The register shows the source, owner, checked time, effective period, exception path, and next action. Clinical, legal, payer, technical, and claim facts retain separate owners and evidence.

Keep clinical decisions with qualified clinicians

Osric routes case-specific modality, risk, treatment, supervision, and clinical-fit decisions to an appropriately qualified clinician. Operations verifies evidence, coordinates scheduling, and surfaces conflicts. Software can check fields and deadlines. A payer coverage action remains separate from the treating clinician's recommendation.

Verify location at every encounter

The member and practitioner locations can change between sessions. Osric asks for the member's physical location at check-in and records the practitioner's physical location from the responsible professional. Those facts drive licensure, payer, emergency, privacy, and place-of-service analysis. Profiles and prior visits serve as reference data rather than the current encounter record.

Preserve choice, consent, assent, and communication

Osric gives the person an understandable modality choice when the governing source allows it and records required consent from the legally authorized person. Assent is monitored when applicable. Speech, AAC, sign, gesture, writing, interpreters, captions, and other effective forms remain available. The person has an accessible way to request a pause or another supported setting.

Decide whether the session can work remotely

A qualified clinician reviews the purpose, response forms, observation needs, prompting, caregiver role, safety, privacy, environment, technology, fatigue, and alternatives. Osric identifies which components need direct observation or in-person care and when to switch. Staffing pressure, distance, or payer approval supplies no clinical-fit conclusion.

Build technical and emergency readiness

Osric tests the approved platform, audio, video when required, device power, bandwidth, camera view, communication system, backup contact, privacy, and outage route. The record names the person's physical location, local emergency contact, responsible adult when applicable, nearest response route, and stop condition. Staff pause when a connection failure prevents safe or meaningful care.

Match authorization and documentation

Osric compares the authorized service, provider, setting, modality, dates, units, and stated conditions with the planned encounter. The note records actual locations, modality, start and stop time when required, participants, accessible communication, interventions, responses, interruptions, supervision, and clinically relevant outcome. The record describes the delivered session.

Release the claim from completed evidence

Osric derives code, units, modifier, place of service, rendering and billing identities, location, authorization reference, and payer route from verified records and current instructions. A telehealth flag supplies one field, while the completed source record supplies the claim evidence. Claim acceptance, adjudication, remittance, and payment remain later states.

Work through Osric's fictional cohort

Osric locks 18 fictional Salt Lake City sessions. Ten initially contain the correct service classification, synchronous platform, provider role, both locations, clinical rationale, authorization, access, note, claim fields, and emergency plan. One technician treatment is marked remote, one group protocol-modification session is remote, one asynchronous upload is treated as a session, two authorizations lack telehealth support, one note omits the clinical rationale, and two schedules overlap members. Six repair. Two remain held. The example is synthetic. It tests release and denominator logic and establishes no coverage, authorization, clinical, legal, privacy, licensure, claim, or payment conclusion for a real person or practice.

Calculate Osric's measures

Utah ABA telehealth readiness is 10 of 18, or 55.6%. Sixteen sessions reach release or accountable hold, or 16 of 18, or 88.9%. Report holds by coverage, authority, location, choice, consent, assent, access, clinical fit, technology, authorization, documentation, claim, and emergency reason. Preserve counts beside percentages and age every unresolved item from its defined start event. Every failed or pending item remains visible in its declared cohort.

Address the main Utah failure mode

A broad telehealth label can hide a service excluded by the ASD manual. Osric keeps code, service description, delivering role, supervision relationship, session grouping, modality, authorization, and documented rationale on the same versioned row. The schedule blocks overlapping one-to-one sessions before staff or claims are assigned. The released calendar shows the assigned supervisor.

Test Osric's controls

Osric tests parent training, remote supervision, technician treatment, group treatment, group protocol modification, asynchronous delivery, overlapping sessions, stale authorization, incomplete rationale, and failed connection. Each scenario records the starting facts, expected action, source, observed result, owner, correction, retest, and disposition. A successful connection proves technical access for that test. Coverage, clinical fit, authorization, documentation, and payment need their own acceptance evidence.

Run independent acceptance

Osric gives an independent reviewer the locked cohort, sources, locations, provider records, authorizations, clinical decisions, access plans, consent and assent evidence, platform results, notes, claims, and payer responses. The reviewer reproduces one release and one hold. A changed cohort, hidden failure, unsupported rule, or unexplained calculation fails acceptance.

Maintain the Utah Medicaid ABA telehealth service and authorization register

Osric reviews sources monthly and after program, plan, law, rule, manual, code, modifier, place-of-service, form, platform, authorization, contract, or contact changes. Each source keeps an owner, effective and checked dates, scope, supersession state, and next review. This Utah page remains draft and noindex until every named expert review finishes.

Related resources

Sources