An owner exploring Community Health Group Medi-Cal ABA participation should start with its network status. Community Health Group (CHG) listed ABA as closed on its joining-network page when checked August 30, 2026. Existing participants still need reliable referral, authorization and billing processes. This guide explains those processes and why a noncontracted submission route is not an invitation to join the network or an assurance of payment.

The closed-network notice belongs at the beginning of the conversation

An ABA owner in San Diego may hear the Community Health Group name often. Families, referral partners and clinicians may all be familiar with it. That familiarity can make participation sound like a routine application task, even when the current network position says otherwise.

CHG's joining-network page states that its ABA network is currently closed. The page limits its listed application opportunities to specified specialties with physical locations in San Diego County. This was the public position checked August 30, 2026; it is not a prediction about when the network may change.

If you're building a business plan, projected CHG revenue needs more support than a list of interested families. Interest in your practice and payer participation are different facts. You can investigate the opportunity respectfully without presenting an unconfirmed relationship to referral partners as settled.

An existing provider has a more specific question. The public notice does not explain every amendment, ownership change or additional-site request under an established agreement. Those circumstances need a review of the actual relationship. The office should not infer either that all changes are prohibited or that every change is already permitted.

A noncontracted provider may also encounter instructions for requesting a service or submitting a claim. Those instructions explain a transaction pathway; they do not erase the network notice. Whether a particular service can be provided and paid depends on the relevant circumstances and confirmation, not merely on finding a form that accepts the provider's name.

This distinction can feel awkward when a parent wants a simple yes or no. The office can still be helpful by explaining exactly what it knows and what it is checking. If the practice cannot currently offer the service under the family's coverage, an honest answer lets the family seek assistance from the plan instead of relying on an indefinite promise.

Your outward-facing information should reflect the same care. A payer logo or directory listing may be interpreted broadly by families. The owner needs a process for reviewing how participation is described and correcting information when the practice's actual arrangement changes.

Giving the referring clinician room to explain the concern

The CHG referral-resources page links an ABA referral packet separately from its general referral and non-specialty mental-health materials. Starting with that live collection helps staff identify the relevant document rather than choosing a similarly named file from an old email.

The linked ABA packet asks for the referring physician or licensed clinical psychologist's information and signature, the member and caregiver details, and a clearly explained referral reason. Its general request pages carry a July 2023 review date. The referral fields are useful to understand, but the packet's older billing language needs a separate check against current claim instructions before anyone relies on it.

The comments section matters because a checkbox rarely tells the whole story. A qualified referring professional needs to explain the concern in context. Office staff can identify an empty section or an inconsistent identifier, but they should not invent a clinical reason to make the document appear complete.

For example, a referral might identify a communication concern while the parent is most worried about a difficulty in everyday routines. That does not necessarily mean the records conflict. The clinician may need to understand how the concerns relate and what evaluation or support is appropriate. An administrative employee can help the right information reach that conversation without deciding the clinical conclusion.

DHCS's behavioral health treatment (BHT) guidance explains that eligible Medi-Cal members under 21 may receive medically necessary BHT regardless of an autism diagnosis. A form with ABA in its title should not become a reason to overlook that breadth. Clinical suitability and the required recommendation still need to be assessed by the appropriate professionals.

A family may already have reports from another provider or program. With appropriate permission and privacy safeguards, those records can contribute useful history. Their existence does not automatically establish a current request, and missing one office's preferred template does not justify assuming that the family has no meaningful clinical information.

The tone of intake makes a difference here. Staff can explain why a specific item is needed and offer a clear way to provide it. A request for a signature is easier to understand when the family knows whose recommendation the plan needs, rather than hearing that the paperwork is simply “wrong.”

Before the packet moves onward, the coordinator should know who can answer questions about it. A referring office, the treating clinician and the person submitting the request may have different roles. A clear contact for each role reduces the chance that a clarification request will circulate without anyone taking responsibility for the answer.

Contracted and noncontracted requests do not take the same path

The CHG service-authorization page directs contracted providers to submit required requests through the provider portal. It directs noncontracted providers to the referral and service-request form by fax, with a different status-inquiry route. The page also tells providers to consult the service-authorization list for the proposed service. These instructions should be read alongside the actual member and provider arrangement.

That is why an internal instruction such as “send CHG requests online” is incomplete. It may describe the usual work of one office without fitting every situation the practice encounters. Staff need to know what established the route for the case in front of them and when they should ask for clarification.

In a fictional example, a clinician joins your organization after working for another contracted group. The clinician may remember the portal well, but the new practice still needs its own participation and access questions resolved. Familiarity with a previous employer's workflow does not prove that the new entity can use the same arrangement.

The request itself needs to remain connected to the clinical recommendation. A service description, code and quantity should tell a consistent story. If the coordinator cannot reconcile the requested amount with the clinician's plan, the disagreement needs an answer before the office sends competing versions.

Sending a request, confirming receipt and receiving a decision are separate events. A transmission record may help investigate delivery, but it does not establish approval. Keeping the submission details and subsequent responses together allows staff to investigate a missing decision without immediately creating another request.

The CHG packet specifically cautions against resubmitting a referral unless instructed. A team that cannot locate its earlier submission should therefore investigate the receipt and status rather than reflexively sending a duplicate. That caution is not a reason to ignore a delay; it is a reason to follow up through the appropriate route with enough information to identify the existing case.

Urgency needs to be evaluated under the current plan requirements, with appropriate clinical input. An approaching appointment or a late administrative discovery can be stressful without establishing that standard. The practice should seek timely clarification while preserving accurate descriptions of the circumstances.

After the decision, the office has another handoff to complete. The staff scheduling care need the applicable dates and service scope, and the biller needs the information relevant to the eventual claim. Neither should have to infer those details from a brief message that the request was handled.

CHG billing setup needs the clearinghouse, not just the payer name

The CHG claim-submission page lists payer identifiers by clearinghouse and transaction context. It also asks a first-time submitter to provide W-9 and NPI information. A single payer ID copied from another practice's software may therefore be an unreliable starting point for your own configuration.

During setup, you might ask the biller to show you the entry that applies to your clearinghouse and claim type. That brief conversation can uncover a number copied from a different configuration. Keeping the source with the setup record also gives a future employee a way to check it without retracing the entire implementation.

The first submission can reveal a missing connection. Perhaps the clearinghouse has accepted the file, but the practice has not yet established that the payer received an identifiable claim. Perhaps correspondence is directed to an old business address. Those possibilities require different follow-up, so the acknowledgment and provider-enrollment records matter.

Older instructions can add confusion. The general pages in the currently linked ABA packet include legacy billing language and a stated filing interval. This article does not treat that packet as a complete current claims manual. Before relying on a deadline, form version or required identifier, the practice should reconcile the current claim instructions and applicable agreement with the specific transaction.

There is no benefit in collecting or transmitting extra sensitive information simply because it appeared on an old list. Your billing and privacy reviewers should determine what the current process actually requires and the appropriate channel for sending it. Accuracy and appropriate disclosure belong together.

When a claim is rejected, the actual response is more useful than an assumption about why CHG did not pay. If several affected claims share one configuration, that pattern can guide investigation. It is not evidence that the services were wrong or that a clinician should alter accurate notes.

A denied or underpaid claim may instead require a correction, supporting documentation or a formal dispute. Staff need to distinguish those possibilities and identify the applicable requirements. Calling for an explanation can be helpful, but it should not be assumed to preserve a formal deadline.

Payment completes only part of the accounting task. The remittance needs to be matched to the account, with adjustments and remaining balances understood. A deposit that looks reasonable in total may still include a claim requiring attention. An owner needs enough visibility to ask about those exceptions without personally working every account.

Growing without asking one employee to remember everything

Early on, the owner may personally answer every referral question. Later, one coordinator may become the person who knows which request went where and which family is waiting for a call. That knowledge is valuable, but it becomes fragile when no one else can locate the underlying information.

A practical handoff contains the question being resolved, the evidence already available and the person responsible for the next response. It does not need to include every clinical detail. Role-appropriate access lets a colleague continue the administrative work while respecting the boundaries around the member's information.

This is especially helpful for CHG because network status, request routing and billing setup can each be unsettled for different reasons. A single “pending insurance” label hides those differences. Staff can communicate more accurately when the record says which question is pending and which parts are already confirmed.

An owner reviewing recurring delays can then look for causes rather than blame. Several requests awaiting the same missing signature may call for a better referring-office handoff. A cluster of rejected claims may call for configuration review. Families repeatedly calling for updates may indicate that no one has been assigned to communicate a status the office already knows.

For a family calling again, the difference may be small but meaningful: the colleague who answers can explain the open question without making them start over. Clearer records cannot guarantee a payer decision or a clinical result. They can help the office take better care of its own responsibilities while the family waits for an answer.

Related resources

Sources