CMBHS: Texas's Behavioral Health Data System Explained for Providers

In this article▾

1. What is CMBHS?
2. Which Texas providers need to use CMBHS?
3. What does CMBHS do in day-to-day operations?
4. How to get access to CMBHS
5. Location setup: a small configuration issue with large consequences
6. Can CMBHS coexist with your EHR?
7. CMBHS batch errors: how to find and resolve them
8. Common CMBHS problems and what to check first
9. How CMBHS affects SUD documentation and billing
10. CMBHS access, training, and support
11. Frequently asked questions
12. The bottom line

CMBHS (Clinical Management for Behavioral Health Services) is a Texas Health and Human Services Commission (HHSC) system used by contracted behavioral health and substance use disorder (SUD) providers to document services, submit required data, and, for certain provider types, manage authorizations and claims. Some organizations use CMBHS as their electronic health record (EHR), while others use it primarily to satisfy state reporting and documentation requirements.

The critical point for Texas practice administrators is that CMBHS requirements depend on your provider type and HHSC contract. It is not a universal requirement for every private therapist or behavioral health practice in Texas. HHSC directs providers to their contract manager when they need to confirm whether CMBHS use is required. Read HHSC's official CMBHS overview.

For organizations that must use the system, the work goes beyond creating a login. Administrators need to configure locations, assign staff access, keep clinical and service records consistent, and monitor data exchanges and errors.

This guide explains how CMBHS works, which organizations may need it, how it interacts with an existing EHR, and how to troubleshoot common operational problems.

What is CMBHS?

CMBHS is a web-based data management system and electronic health record developed by HHSC's Behavioral Health Services. It supports documentation for community-based mental health and substance use treatment programs across Texas. The help system is still hosted on a dshs.state.tx.us address, which is a legacy of the agency reorganization rather than a sign that DSHS runs it today.

According to HHSC's CMBHS application overview, the system supports functions such as:

• Screening and assessment.
• Diagnosis and level-of-care determination.
• Admission and discharge documentation.
• Treatment plans and progress notes.
• Service authorizations.
• Financial eligibility and Medicaid eligibility verification for applicable workflows.
• Claims processing for certain provider and service types.
• Occupancy management and reporting.
• Data collection for state oversight, compliance monitoring, and reporting.

Different organizations have access to different functions. A provider that uses CMBHS to document SUD treatment may have a different workflow from a local mental health authority (LMHA) transmitting required service data or a Medicaid provider using the system for specified mental health services.

CMBHS is therefore more than a claims portal, but it is not necessarily every organization's primary EHR.

Which Texas providers need to use CMBHS?

HHSC identifies providers contracted to deliver state behavioral health or SUD services as the system's primary users. Certain other provider types may qualify for access when they need to complete assessments or submit information for care coordination.

Whether your organization must use CMBHS is determined by the applicable contract and program requirements, not simply by the fact that you provide behavioral health services in Texas.

HHSC's official CMBHS provider resource page explains access requirements and directs providers to the appropriate process.

Before changing your workflow, confirm your obligation with your HHSC contract manager or program contact. A generic statement that CMBHS is mandatory for every Texas behavioral health practice would be inaccurate.

What does CMBHS do in day-to-day operations?

CMBHS combines clinical documentation with administrative and program functions. For administrators, its impact is easiest to understand across four workflows.

1. Clinical documentation

Depending on the provider's program and permissions, staff may use CMBHS to document assessments, admissions, treatment plans, progress notes, service delivery, and discharges.

The system also applies program-specific rules to certain forms and workflows. For example, the CMBHS help documentation describes treatment plans tied to the client's identified problems, goals, interventions, and objectives.

Operationally, this means staff need to understand both the clinical information being documented and the fields or rules required by the applicable program.

2. Service and authorization management

CMBHS includes administrative functions for managing service authorizations, referrals, assignments, and other program activities. Some workflows depend on the client's assigned location and the services available at that location.

If the expected service, location, or authorization information is missing, staff may be unable to complete the relevant workflow or may need to correct the underlying record.

3. Claims and payment-related functions

CMBHS supports claims and payment functions for certain provider and service types. Its business-office tools include claims-related workflows and documentation of client payments.

Do not assume that every claim for a Texas Medicaid member belongs in CMBHS. The correct route depends on the service, funding source, provider type, and applicable contract or payer instructions. Getting that routing wrong produces the same symptoms as a coding error, which is why it is worth ruling out first; see the behavioral health revenue cycle guide.

4. State reporting and oversight

CMBHS provides HHSC with data used for program oversight, compliance monitoring, policy development, and state and federal reporting. HHSC is Texas's state substance abuse agency for these purposes, which is why the data obligation sits alongside the clinical one.

For providers, that makes data quality an operational responsibility. Missing records, incorrect locations, inconsistent service dates, or unresolved batch errors may affect more than an individual screen or claim. They can also affect the information available for program reporting.

Explore the official CMBHS online help system.

How to get access to CMBHS

The access process depends on the organization and provider type. For organizations required to use CMBHS, HHSC's help documentation describes a local CMBHS Security Administrator who manages user setup and ongoing access.

Step 1: Confirm your organization's eligibility and requirements

Check the applicable HHSC contract, program instructions, or provider enrollment requirements. If you are unsure whether your organization needs access, contact your HHSC contract manager.

Step 2: Designate a local Security Administrator

HHSC's CMBHS access guide instructs organizations required to use CMBHS to designate a local Security Administrator.

The administrator helps establish the organization's access and sets up accounts for staff and contractors.

Step 3: Complete the relevant access documentation

Some provider types need to submit Form 5007, the CMBHS Access Request and User Agreement. HHSC's instructions are to download the form, complete it, print, sign and submit it to the Mental Health Contracts Unit at MHContracts@hhsc.state.tx.us. A separate HHS Enterprise Acceptable Use Agreement applies to all users of HHS systems and is not the same document. Other provider categories have additional prerequisites.

For Medicaid mental health targeted case management and rehabilitative service providers, HHSC describes prerequisites that include Texas Medicaid & Healthcare Partnership (TMHP) enrollment and an executed contract with a Medicaid managed care organization.

Use the current HHSC CMBHS page to find the applicable form and instructions rather than assuming the same process applies to every provider type.

Step 4: Set up individual staff accounts

Provider staff and contractors obtain access through their organization's local Security Administrator. HHSC's help documentation explains that accounts are established through the system's identity-management process.

Use individual accounts and assign access based on job responsibilities. When a staff member leaves or no longer needs access, follow the organization's access-termination procedure.

Step 5: Complete training and test the workflow

HHSC recommends training in addition to using the online help system. New staff should understand how to navigate the relevant workspace, select the correct location, document services, and resolve common errors.

The CMBHS help documentation gives 1-866-806-7806 for both the CMBHS Help Desk and the CMBHS Help Line. A prospective local Security Administrator calls that number to begin the set-up process for their organization. Training questions go to cmbhstrainingteam@hhs.texas.gov. Confirm current hours and contact details on the official HHSC CMBHS page.

Location setup: a small configuration issue with large consequences

Location configuration is one of the most important administrative tasks in CMBHS.

The system uses service locations to organize client records and support specific functions. HHSC's online help warns that users must be in the correct virtual service location when documenting a client's record. If the user lacks access to a location, or the client does not have a service associated with that location, certain functions may not be available.

HHSC's location-management guide describes how administrators create and maintain location records.

Before adding a location

The local Security Administrator should gather:

• The location's full address and phone number.
• Contact-person information.
• The services offered at the location.
• The appropriate location name, consistent with the organization's naming convention.
• Applicable identifiers required for the provider type.
• The correct location type and other program-specific configuration details.

Some information may be maintained by HHSC, while other fields are managed by the provider's local administrator.

Verify the location before documenting services

Use this operational checklist when opening a new site or reviewing an existing one:

• Confirm the correct organization and location record.
• Verify the physical address and contact information.
• Confirm the services offered and the location type.
• Verify the identifiers required for the provider and service location.
• Check that the relevant staff have access to the location.
• Confirm that the client and service are associated with the correct location.
• Test the documentation workflow before relying on it for routine operations.

For SUD providers, CMBHS help identifies three identifiers: the National Provider Identifier (NPI) from NPPES, entered at both the parent-entity and service-location level; the Texas Provider Identifier (TPI), issued by Texas Medicaid to identify individual service locations for billing; and, for SUD locations, a site number assigned by SAMHSA to individual service locations. Check the current instructions for the identifiers applicable to your organization.

Multi-location organizations: common failure points

When a provider operates several sites, a location error can be mistaken for a clinical or billing issue.

For example, a staff member may be logged into Location A while attempting to document a service delivered at Location B. The client record or relevant service may not be available in the expected workflow, or the resulting record may be associated with the wrong location.

To reduce this risk:

1. Standardize location names.
2. Train staff to verify the active location before entering or updating records.
3. Assign one administrator responsibility for location setup and changes.
4. Review location access whenever staff move between sites.
5. Test the workflow when opening a new site or adding services.

If the record is unavailable, check the active location and the client's service-location association before assuming the record is missing.

Can CMBHS coexist with your EHR?

Yes, but the appropriate workflow depends on what your organization is required to document in CMBHS and what your EHR can exchange with the state system.

HHSC explains that some providers use CMBHS as their EHR and claims payment system, while others mainly use it to transmit required data to the state. Its help system also describes data downloads and web-service access for eligible users.

That means an existing EHR does not automatically remove the need to use CMBHS. Nor should administrators assume that every CMBHS function is available through a third-party integration.

Three common operating models

These are operational patterns, not a guarantee that every provider has access to all three options. Confirm the capabilities available for your organization and program.

If staff use both an EHR and CMBHS

Define which system is the source of truth for each data element and which fields must be entered or confirmed in CMBHS.

For example, your organization might maintain the full clinical record in its EHR while entering specific assessments, progress notes, or service data in CMBHS to satisfy program requirements. The exact arrangement must match the contract and program rules.

Create a workflow matrix that identifies:

• Which record is created in which system.
• Who is responsible for entering or transmitting it.
• The deadline for completion.
• Which fields must match across systems.
• How staff verify that the data reached CMBHS.
• How corrections and rejected transactions are handled.

Do not assume that data entered in the EHR has reached CMBHS unless the exchange has been confirmed.

What CMBHS data exchange can and cannot tell you

The CMBHS online help describes downloadable data in Excel formats and a web-service option for retrieving certain records. It also notes that downloaded data is not necessarily available on the same day it is entered.

For downloads, the documented workflow allows users to select a document type, location, date type, and date range. The guide specifies a maximum seven-day date range for the relevant download function. Web-service access has its own technical and security requirements.

These features can support reconciliation and reporting, but they should not be treated as a universal, real-time integration with every commercial EHR. The same caution applies to any state data obligation your programs carry, such as electronic visit verification where it applies to the service; confirm what is required for your contract rather than assuming CMBHS covers it.

Before choosing or changing an EHR, ask your vendor and HHSC contact:

• Can the required CMBHS data be exported or exchanged using a supported method?
• Which document types and fields are supported?
• How are invalid or incomplete transactions identified?
• How will staff know that data was accepted?
• What happens when an EHR field does not map to the corresponding CMBHS field?
• How are corrections transmitted?
• What audit trail is retained?
• What testing is required before changes go live?

CMBHS batch errors: how to find and resolve them

Some organizations transmit information to CMBHS in batches rather than entering every record manually. The system validates batched transactions against business rules.

According to the official CMBHS Data Functions help page, transactions with severe errors can remain in pending status and appear on the Batch Error Correction List (BECL).

The help documentation identifies contracted mental health providers, hospitals, and subcontracted providers sending batch transactions for a Local Behavioral Health Authority among the organizations that may use this process.

Where to find the Batch Error Correction List

The documented navigation path is:

Administrative Toolbar → Data → Batch Error Correction List

The list displays pending transactions that have severe errors. Providers that submit batches can use the list to make changes or delete transactions, as applicable to the workflow.

One important detail: the help documentation says the batch parser runs once each evening. Although the list refreshes when searched, it reflects the previous night's batch processing rather than a continuously updated validation result. It also states that transactions are deleted from the BECL after 120 days.

These details make routine monitoring important. A team that waits until the end of a reporting period may find that older errors are harder to investigate or no longer appear in the correction list.

A practical batch-error workflow

1. Check the latest processed batch. Review the BECL after the system has processed the relevant transactions. Do not assume a record sent moments ago will immediately appear in the list.

2. Identify the transaction and error. Capture the affected record, date, location, and available error information. Determine whether the issue relates to required fields, identifiers, dates, service information, or another business rule.

3. Compare the record with the source system. Check the original EHR or source data before changing a transaction. The goal is to correct the underlying information, not simply to make an error message disappear.

4. Correct or remove the transaction as appropriate. Follow the applicable CMBHS instructions and your organization's correction procedure. If you are unsure what a rule requires, consult the CMBHS help documentation or Help Line.

5. Confirm the outcome. After the next relevant processing cycle, verify that the correction was accepted or that the transaction has reached the intended status. Record unresolved errors for follow-up.

6. Keep a correction log. Track the date, error, responsible staff member, action taken, and final status. This helps identify repeated issues caused by a mapping rule, location setup, or training gap.

Why batch errors should be reviewed regularly

The BECL's 120-day retention detail is particularly important for organizations that depend on batch submissions. It is safer to make error review part of the daily or scheduled operational routine than to rely on the list as a permanent archive.

Keep separate source records and follow your organization's record-retention requirements. The BECL should not be your only evidence of what was transmitted or corrected.

Common CMBHS problems and what to check first

The goal is to diagnose the problem before repeating the action. Resubmitting a transaction without understanding why it failed may create duplicate work or leave the original error unresolved.

How CMBHS affects SUD documentation and billing

For Texas SUD treatment providers whose contracts require CMBHS, the system is part of the operational record of care. Clinical documentation, service information, eligibility, and program requirements may intersect with claims and payment workflows.

That makes the quality and consistency of the underlying data important. An incorrect service date, an incomplete progress note, or a mismatch between the recorded service and the applicable program requirements may require correction before the associated administrative workflow can be completed.

Administrators should pay particular attention to:

• Admission and assessment: Confirm required assessments and program-specific documentation are completed.
• Level of care: Record the determination and supporting information required by the applicable program. Texas SUD programs commonly work from the ASAM Criteria; see ASAM levels of care for what each level covers.
• Treatment planning: Ensure plans and reviews are completed according to contract and program requirements.
• Service documentation: Confirm the correct client, service date, location, service type, and required narrative or fields.
• Authorization: Verify that required authorizations and related records are present.
• Claims and payment: Confirm that the service and claim workflow applies to the provider type and funding source.
• Discharge and follow-up: Track any program-required discharge records or follow-up contacts.

The specific requirements vary by program and contract. Use the current HHSC SUD provider guidance and your organization's contract rather than assuming every SUD service follows the same documentation sequence.

For related coding resources, see the guides to alcohol use disorder ICD-10 codes, substance use disorder ICD-10 codes and opioid use disorder ICD-10 codes. Diagnosis coding is one part of the record; it does not replace the other documentation and program requirements.

CMBHS access, training, and support

HHSC provides an online help system with instructions for clinical, administrative, business-office, and data functions. The help site is organized by task, so it is useful to search for a specific workflow rather than relying on a general overview.

Start with these official resources:

• HHSC CMBHS provider resource page: access requirements, forms, and contact information.
• CMBHS application overview: functions, intended users, and training information.
• CMBHS access and location help: accounts, security administration, and locations.
• CMBHS Data Functions: downloads, web-service data access, and batch errors.
• CMBHS Managing Locations: location setup and identifiers.

Because system instructions can change, verify current browser requirements, access procedures, contact details, and workflow rules on HHSC's official site before making operational changes.

Frequently asked questions

Is CMBHS mandatory for every behavioral health practice in Texas?

No. CMBHS requirements depend on the provider type, program, and HHSC contract. HHSC-contracted SUD and mental health providers are primary users, while certain other provider types may qualify or need access for specific services. Confirm your organization's requirements with its HHSC contract manager.

Is CMBHS an EHR or a billing system?

It can serve both functions for some providers. HHSC describes it as a web-based data management system and EHR that also supports administrative functions, including claims for certain provider and service types. Other organizations primarily use it to submit required data to the state.

Can a behavioral health practice keep its existing EHR?

Potentially, yes. Some organizations use another EHR alongside CMBHS, but they must still meet the documentation and data-submission requirements that apply to them. Confirm supported data-exchange options and define how staff will validate that required information reaches CMBHS.

How do I get a CMBHS account?

For organizations required to use CMBHS, a local CMBHS Security Administrator typically coordinates staff account setup. Some provider types must complete Form 5007 or satisfy additional enrollment and contract prerequisites. Follow the current instructions on the official HHSC CMBHS page.

What is the CMBHS Batch Error Correction List?

The BECL displays certain batched transactions with severe errors that remain in pending status. Authorized staff can review the affected transactions and make corrections or deletions as permitted. The official help documentation states that the batch parser runs once each evening and that transactions are removed from the BECL after 120 days.

Why is a client or service missing from a CMBHS workflow?

Check the active location, the client's association with that location, staff permissions, and the relevant service setup. CMBHS functionality can depend on location configuration and access rights. If the record should be available but is not, contact your local Security Administrator or the CMBHS Help Line.

Does CMBHS replace Medicaid enrollment or payer requirements?

No. CMBHS access does not automatically establish Medicaid enrollment, managed care contracting, authorization, or eligibility for reimbursement. Complete the enrollment and contracting steps required for the service and confirm the correct billing route.

The bottom line

CMBHS is an important part of Texas's public behavioral health infrastructure, but it is not a universal EHR mandate for every behavioral health practice. The requirements depend on the provider's program, contract, and service type.

For organizations that must use it, reliable operations start with correct location setup, role-based staff access, consistent clinical and service documentation, and regular monitoring of batch transactions. If you are also choosing software around it, the substance abuse billing software guide covers what to make a vendor demonstrate. If your organization also uses a separate EHR, define exactly how required data reaches CMBHS and how staff confirm that it has been accepted.

When a problem occurs, check the active location, source record, permissions, transmission status, and applicable business rules before repeating the action. Use HHSC's current instructions and your contract manager to resolve questions that cannot be answered from the help documentation.

Related: substance abuse billing software, ASAM levels of care, and the behavioral health revenue cycle guide. Other states run this differently; see California's DMC-ODS and Arizona's APEP.