For IHN-CCO ABA participation and billing, an owner needs to understand InterCommunity Health Network CCO’s Medicaid requirements and know where to find the relevant Samaritan Health Plans resources. The 2026 authorization materials explicitly include ABA, including assessment codes. This guide explains how to evaluate participation, prepare for authorization and organize claim follow-up without borrowing rules from Samaritan’s Medicare or employer products.

Finding the IHN-CCO instructions among Samaritan’s resources

An owner looking for an IHN-CCO answer may arrive on a Samaritan page that also discusses Medicare and employer coverage. The product heading is what helps you tell which instructions apply to an Oregon Health Plan member.

Samaritan’s authorization page separates its materials by plan and links IHN-CCO’s own approval lists. That organization is helpful once your team recognizes it. A document with a familiar logo can still belong to a different product, and a saved download can lose the context that was obvious on the webpage.

A practical internal reference can include the document title, product and effective date alongside the link. This gives the next employee a way to check whether they are using the intended resource. It is especially useful when a practice works with several payers and the same administrator appears in more than one workflow.

Suppose a biller finds an old authorization note in the practice’s shared folder. Before treating it as an IHN-CCO rule, the team should establish where it came from and which service it addressed. A source link and effective date make that check much easier than an isolated note.

This guide focuses on the Medicaid payer relationship. It does not turn Samaritan’s Medicare instructions, employer-plan rules or pharmacy arrangements into ABA requirements. When a public page does not settle your specific question, Provider Relations or the appropriate authorization team needs the actual facts rather than a request to confirm a general assumption.

Planning participation before staffing a new service line

The network-joining page describes an initial consideration process followed by applicable credentialing and contracting work. It notes that review of a complete credentialing file can take up to 90 days and that contracting depends on credentialing approval. That is a planning consideration, not a guaranteed completion date or a promise that the practice will be accepted.

You may be making hiring and space decisions while this work is underway. It is tempting to convert an estimated administrative timeline directly into an opening date. A more realistic plan leaves room for questions, missing information and an outcome that differs from your initial expectation.

The details of the proposed practice matter. An organization adding an experienced clinician is not necessarily asking the same question as a new entity seeking its first agreement. The payer needs to understand the provider types, locations and services involved. The owner needs to understand which individual and organizational approvals will be required.

It is easy for “the application is complete” to become “the clinician is all set” as an update passes between staff. That phrase can conceal the unfinished work. An internal update that names the stage reached and the stage still pending is less likely to be interpreted as permission to book services.

This is also a good time to decide who will maintain the records after the initial application. A practice that carefully prepares its first roster but has no process for staffing changes can lose track of what the payer has on file. The source page provides update routes; your team still needs a person responsible for using the applicable one and retaining the response.

A small practice may only need a few records, provided they show exactly which approvals are complete and which questions remain. Families and staff both benefit when “ready” has a clear, supportable meaning.

Reading the IHN-CCO ABA entries in the 2026 lists

IHN-CCO’s 2026 prior-approval list names ABA services as requiring review. The coded companion list effective January 1, 2026 includes 97151 and 97152 along with treatment entries in its ABA section. An assessment should therefore not be assumed exempt simply because another plan handles assessment differently.

The coded document states that it is for in-network providers, is not exhaustive, and does not establish coverage or payment merely by listing a code. Out-of-network circumstances need their own review of applicable requirements and exceptions. Those qualifications matter as much as the row containing the code you were looking for.

After locating a code, your team still has a few questions to resolve. The proposed service still needs to fit the member’s benefits, provider arrangement and clinical circumstances. A missing code is not a reliable reason to conclude that no authorization is needed.

A useful authorization preparation discussion connects the clinician’s proposal with the administrative request. Does the named provider match the arrangement being used? Do the requested dates describe the intended service period? Does the submission include the information the plan says it needs for this request? These are questions a coordinator can help resolve without choosing the treatment.

The authorization list supplies no standard clinical schedule for everyone. Clinical need and appropriate care must be determined individually by qualified professionals, with applicable member rights and coverage rules considered.

If the plan asks for additional information, it helps to send the actual question to the person able to answer it. A coordinator can supply a missing administrative detail; a clinician needs to address a clinical rationale. When those roles are clear, a request is less likely to circulate through several people without anyone knowing what is needed.

Making the portal response useful to the people scheduling care

Samaritan directs providers to Provider Connect for electronic authorization requests and tracking in its current authorization instructions. The same page cautions that retrospective medical-necessity review is limited to specified exceptions. Planning to resolve authorization only after services have been delivered is therefore not a sound routine workflow.

Portal access itself is an operational task. The employee responsible for follow-up needs the correct authorized access, a way to recognize the right member and a place to record the response. Shared passwords or screenshots passed around without context are not a substitute for appropriate access controls.

Imagine that a request has been submitted and the scheduler sees an open slot next week. The submission date does not answer whether that appointment can proceed under the requested arrangement. The team needs to distinguish a received request from a completed decision, then read what was actually authorized.

When a decision arrives, a short handoff can connect it to the schedule without asking the scheduler to interpret clinical policy. The authorization lead can identify the relevant service period and approved details, flag an unresolved question and refer any clinical issue to the clinician. The original decision should remain available to the staff who legitimately need it.

If approval differs from the request, the practice should not quietly change its records to make the two appear consistent. It needs to understand the decision and discuss the appropriate response through the applicable clinical and plan channels. The family should receive an explanation they can understand, including any relevant notice and review options.

Continuation requests deserve time for the same work. The appropriate submission timing should be confirmed for the specific service rather than copied from another payer’s calendar. Starting the internal preparation early enough to identify missing information is an organizational choice; it is not a substitute for the payer’s actual rules.

Why the clearinghouse matters when you bill IHN-CCO

Samaritan’s billing instructions publish different identifiers for different electronic routes: Office Ally uses SAMHP for all plans, while Trizetto lists INCHN for IHN-CCO. The right identifier depends on the submission channel. Copying a code from another practice’s instructions without knowing its clearinghouse can send your team down the wrong path.

The setup conversation should therefore include the billing vendor, not only the person reading the payer webpage. You want to know how the vendor has configured this particular product and how submission responses will be available to your staff. A verbal assurance that it “supports Samaritan” leaves the important product and routing questions unanswered.

A claim that disappears from the work queue deserves investigation before another copy is sent. The team can determine whether it was rejected before payer processing, received but pending, or processed with an explanation that needs action. This helps avoid treating every unpaid item as a denial.

Corrected claims have their own technical requirements. Samaritan’s page describes replacement claim frequency code 7 and a reference to the original claim number. Those are instructions for a correction workflow, not permission to change an accurate record in pursuit of payment. The billing specialist should confirm the required transaction details for the actual claim.

For example, if a rendering-provider field was entered incorrectly, the team needs to compare it with the clinical and participation records before submitting a correction. If the original field was accurate but the payer’s record is different, the next step may be to resolve that discrepancy rather than substitute another person’s identifier.

An owner does not need to troubleshoot every electronic transaction personally. You do need enough visibility to distinguish a recurring configuration problem from an isolated case. That distinction can influence whether the practice needs vendor help, staff training or a payer conversation.

Building confidence without promising an outcome

Families usually want to know whether your practice can help and when they will hear from you. They should not have to understand every stage of credentialing, authorization and claim processing to get an honest answer.

A helpful update names the current issue in ordinary language. The practice may be checking participation for a new clinician, waiting for a decision on an assessment request, or asking the plan to clarify a notice. The owner can set expectations for the team’s follow-up even when the payer’s decision is outside the practice’s control.

After several IHN-CCO cases, review where your staff repeatedly need help. One recurring problem might be locating the product-specific document; another might be a response that reaches billing but never reaches scheduling. Each problem calls for a different improvement.

A brief discussion of a real administrative sequence, using appropriately protected information, is often more useful than adding another generic procedure. The team can see where information was lost and agree how the next handoff should work. An agreed change can be tried on the next case and discussed with the staff doing the work.

The resulting process should support thoughtful care rather than pressure clinicians to shape treatment around administrative convenience. This article offers a way to understand the payer relationship; it does not establish coverage, clinical appropriateness, billing eligibility or a particular reimbursement outcome. Those decisions still depend on current requirements and the facts of the case.

Related resources

Sources