CCBHC EHR Reporting Requirements: Configuring Your Netsmart Platform for Compliance, Clean Claims, and Quality Outcomes

Certified Community Behavioral Health Clinics (CCBHCs) offer enhanced reimbursement and the ability to broaden services. However, getting your Netsmart system properly configured is a challenge. If your Netsmart EHR isn’t fully CCBHC-ready, you face mounting denials, documentation burden, and manual reporting.

The solution isn’t as simple as implementing a new EHR. Properly configuring Netsmart’s myAvatar and/or myEvolv EHRs requires a thorough understanding of clinical documentation and workflows, PPS requirements, and the needs of state agencies. This is where The Joxel Group can help. We have spent more than a decade configuring Netsmart platforms and bring 10-plus years of myAvatar expertise and seven-plus years of myEvolv configuration experience.

In this guide, we’ll explore:

• How to configure Netsmart to meet CCBHC needs
• Common configuration gaps that cause compliance and revenue problems
• The Joxel Group’s proven approach to CCBHC implementation

The Core Problem: CCBHC Reporting Is Not “Just Another Report”

CCBHC data reporting goes far beyond generating a PDF. The program requires your EHR to collect, organize, and export highly structured encounter and outcome data in ways that are:

• Mappable to CCBHC service types, as every encounter must be coded to one of the nine distinct CCBHC service categories in formats states recognize for payment and oversight.
• Auditable at the patient and aggregate levels, as Medicaid and accreditation teams may pull records to validate service delivery, clinical outcomes, and care-coordination elements.
• Consistently reproducible year-over-year, because reliable trend analysis depends on standardized definitions and dependable capture.
• Ready for annual standardized data reporting, since certain data must be pulled and submitted to SAMHSA using a standardized data reporting template.

When the EHR falls short, clinics may experience:

• Billing errors and claim denials from improper encounter-level cost categorizations and service-type reporting
• Missed or delayed Quality Bonus Payment eligibility because outcome measures aren’t consistently captured or calculated
• Increased staff time spent reconciling free-text documentation into CCBHC-compatible spreadsheets

What CCBHC EHR Configuration Actually Requires

Meeting CCBHC expectations in Netsmart calls for precise, interconnected adjustments spanning clinical documentation, financial workflows, and regulatory reporting. These enhancements ensure accurate encounter-level cost categorizations, streamlined data submission, and adherence to evolving CCBHC quality and financial requirements.

1. Structured Clinical Data Capture for Quality Measures

CCBHCs must collect and report on specific quality metrics. Rather than rely on clinicians to pull reports at regular intervals, we recommend embedding required measures into clinical documentation through smart forms that capture the data in the moment. These may include, but are not limited to:

• Patient-centered mental health measures: PHQ-9, GAD-7, and C-SSRS
• Care coordination elements: Collaborative care activities and care-transition documentation
• CCBHC-defined service-type encounters: Ensuring each of the nine distinct CCBHC service types is defined, differentiated, and mapped to appropriate clinical workflows

These elements must be coded at the right levels so they can be rolled up into reports. For example, it’s not enough to document PHQ-9 and PHQ-9m scores within a note; your EHR needs to recognize this information so it can calculate outcomes and roll them up for reporting. Free-form documentation can make reporting nearly impossible, so your EHR needs a way to collect this information in a standardized fashion.

2. PPS-Aligned Billing and Revenue Cycle Configuration

The move to a Prospective Payment System (PPS) changes how CCBHCs track and report encounters and costs. Configuration should reflect these requirements:

• PPS encounter definitions: Encounter-level cost categorizations, such as complex or intensive, mapped to service delivery workflows
• Reporting requirements: Ability to generate reports aligned with evolving PPS guidelines
• Outlier payments: Encounter-level cost categorization aligned to clinical workflows
• Provider taxonomy: Dual NPI setup to report on NPI at the practitioner and clinic levels
• Quality bonus payments: Automated calculations for quality-based reimbursement

3. SAMHSA Data Reporting Template Readiness

CCBHCs are required to provide SAMHSA an annual data report using a standardized data reporting template. We recommend creating reports within Netsmart to streamline this process. This might include reports to track:

• Encounters and visits by service category
• Clinical outcomes tied to the above-mentioned quality measures

How The Joxel Group Approaches CCBHC EHR Configuration

At The Joxel Group, our approach is rooted in a simple but powerful philosophy: get to know your system, find what’s holding it back, and help you unlock its potential. Our approach consists of four steps:

• CCBHC EHR Assessment: Understand your organization’s unique goals and challenges. Identify gaps and areas of opportunity, prioritizing improvements to optimize outcomes.
• CCBHC EHR Optimization: Make targeted improvements to clinical documentation, revenue cycle, reporting, and other aspects of the EHR as necessary to meet your organization’s goals and streamline operations.
• Testing & Validation: Validate changes to confirm they’re performing as intended.
• Knowledge Transfer: Build your team’s confidence with comprehensive documentation and knowledge transfer, empowering them to navigate the system independently.

Real Outcomes: What Proper CCBHC Configuration Delivers

Clinics that partner with The Joxel Group for Netsmart’s myAvatar and/or myEvolv to align with CCBHC requirements see immediate and long-term gains across clinical, financial, and operational dimensions. Outcomes include:

• Smarter documentation: Smart forms and conditional logic streamline documentation so clinicians can enter data once and use it throughout your system, from quality measures and care-coordination dashboards to PPS categorization and cost reporting.
• Fewer claim denials: Aligning service-type definitions with clinical documentation helps ensure proper coding and claim submission.
• Timely CCBHC data submissions: Data is collected in the moment rather than backfilled.
• Faster return on investment: Targeted Netsmart optimization projects are often completed in a matter of weeks, typically 8 to 16.

Frequently Asked Questions

Can my current Netsmart EHR handle CCBHC reporting, or do I need a new one?

In most cases, Netsmart’s myAvatar and/or Netsmart’s myEvolv can be optimized to accommodate your organization’s CCBHC data collection, billing, and reporting needs. At The Joxel Group, we’ve spent years helping organizations configure Netsmart EHRs. We’ll conduct an assessment to identify gaps and make recommendations to help you decide next steps.

How long will my EHR configuration project take?

Timelines depend on the scope of configuration, but a typical CCBHC-focused project takes 8-16 weeks.

Will my team need extensive training afterward?

We provide the knowledge transfer your organization requires to operate with confidence. We also provide comprehensive documentation to make sure everyone is aligned.

Ready to optimize Netsmart’s myAvatar or Netsmart’s myEvolv EHRs to meet CCBHC requirements? Schedule a discovery call with The Joxel Group to learn how we can help you meet CCBHC documentation, billing, and data-reporting requirements with Netsmart.