To configure Oregon Health Plan ABA telehealth and CCO controls, identify whether OHA fee for service or a coordinated care organization controls the service. Then verify current ABA coverage, provider scope, client choice, modality, member and practitioner locations, clinical fit, communication access, authorization, documentation, and billing. OHP's broad telehealth access message does not establish one claim configuration for every ABA service.

Define an Oregon telehealth release

Tamsin treats telehealth as a service-date configuration, not a reusable label. One row identifies the member, payer and product, covered 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.

Read the current Oregon Health Plan authority

OHP's current telehealth page says members may receive many services through video, phone, or online methods and can ask a CCO for access help. It is member-facing coverage orientation. Tamsin obtains the service-level code, modality, provider, authorization, and billing evidence before treating a session as payable.

Separate program coverage from payer routing

OHA's billing page says to bill a member's CCO when enrolled in one and bill OHA for an open-card member. It also requires current service coverage, provider scope, and records. The CCO page identifies current plans, while behavioral-health policy resources supply the program layer. Tamsin versions FFS and each CCO separately.

Use one release gate for every required fact

Tamsin requires member eligibility and CCO; current ABA coverage; provider enrollment, scope and plan participation; member and practitioner locations; supported modality; client choice; consent and assent when applicable; clinical fit; access; authorization; note; FFS or CCO claim rule; and emergency plan. A single failed gate holds the session or claim at the point affected. The register shows the source, owner, checked time, effective period, exception path, and next action rather than collapsing all facts into a green telehealth checkbox.

Keep the clinical decision with a qualified clinician

Tamsin routes case-specific modality, risk, treatment, supervision, and clinical-fit decisions to an appropriately qualified clinician. Operations can verify evidence, schedule, and surface conflicts. Software can check fields. Neither operations nor software changes a goal, dosage, risk control, or treatment rationale to satisfy a payer rule.

Verify location at every encounter

The member and practitioner locations can change between sessions. Tamsin asks for the physical location at check-in and records the practitioner location from the responsible professional. Those facts drive licensure, program, payer, emergency, privacy, place-of-service, and out-of-state analysis. A home address, office profile, device location, or prior visit cannot silently substitute.

Preserve choice, consent, assent and communication

Tamsin gives the person an understandable choice when the governing source allows it and records required consent from the person legally authorized to provide it. Assent is monitored when applicable. Speech, AAC, sign, gesture, writing, interpreters, captions, and other effective forms remain available. A person can request a pause or another supported setting without losing basic communication access.

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. Tamsin identifies which components need direct observation or in-person care and when to switch. Telehealth convenience, staffing pressure, distance, or payer approval cannot supply evidence that the modality fits.

Build technical and emergency readiness

Tamsin 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 do not continue through a connection failure that prevents safe or meaningful care.

Match authorization and documentation

Tamsin compares the authorized service, provider, setting, modality, dates, units, and any 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. It represents what happened rather than what the template expected.

Release the claim from completed evidence

Tamsin 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 cannot create coverage or fix a missing note. Claim acceptance, clean-claim status, adjudication, remittance, and payment remain later states.

Work through Tamsin's fictional cohort

Tamsin locks 23 fictional Eugene encounters across open-card and CCO members. Fifteen initially contain member route, coverage, provider scope, plan status, both locations, modality, choice, clinical fit, access, authorization, note, claim instruction, and emergency plan. One open-card claim goes to a CCO, two CCO sessions use OHA fee-for-service fields, one phone session lacks code support, one authorization names video, one provider scope is unclear, and two notes omit member location. 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 Tamsin's measures

OHP telehealth readiness is 15 of 23, or 65.2%. Twenty-one encounters reach release or accountable hold, or 21 of 23, or 91.3%. Report holds by coverage, authority, location, choice, consent, assent, access, clinical fit, technology, authorization, documentation, claim, and emergency reason. Preserve counts alongside percentages and age every unresolved item from its defined start event.

Address the main Oregon failure mode

Oregon's broad access message includes several modalities, while payment remains service and payer specific. Tamsin treats modality, code, benefit, authorization, provider, and receiver as independent fields. A member's ability to request phone care is not a claim-release instruction. For each CCO, she stores the manual source and the plan-confirmation date.

Test Tamsin's controls

Tamsin tests open-card video, CCO video, phone modality, online interaction, provider scope, authorization mismatch, member location, access support, and emergency fallback. Each scenario records the starting facts, expected action, source, observed result, owner, correction, retest, and disposition. A platform connection passes only a connection test. It cannot prove coverage, clinical fit, authorization, documentation, or payment.

Run independent acceptance

Tamsin gives an independent reviewer the locked cohort, sources, member and practitioner 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 OHP ABA telehealth and CCO release register

Tamsin 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, and next review. This Oregon page remains draft and noindex until every named expert review finishes.

Related resources

Sources