Reporting requirement ≠ evaluation question

CCBHCs have no shortage of reporting requirements. That can make it easy for the evaluation function to become synonymous with producing reports.

They are not the same thing.

Reporting is an essential part of CCBHC accountability. Evaluation serves a different purpose. A strong evaluation function uses required data, operational data, qualitative information, and targeted analyses to answer questions the organization needs to understand.

Reporting starts with a specification

A reporting requirement usually tells you what needs to be submitted, how a measure is defined, which population is included, what period applies, and when the result is due.

The evaluator's responsibility is to make sure the organization can produce that information reliably. That requires attention to source data, workflows, technical specifications, validation, documentation, and deadlines.

But once the report is submitted, many important questions remain unanswered.

Evaluation starts with a question

Consider access.

A required measure may tell you how quickly people received an initial service. An evaluation question might ask why one site consistently performs better than another, whether access differs by referral source, whether staffing patterns are contributing to delays, or whether a new scheduling workflow improved timeliness without increasing no-shows.

Those are different questions. They may use some of the same data, but they require interpretation and context that a submission file was never designed to provide.

The same is true for outcomes. A CCBHC may successfully report an outcome measure while still needing to understand which clients are not completing reassessments, whether outcomes vary across service pathways, or whether an implementation change is associated with better engagement.

Do not build two disconnected systems

The answer is not to create a reporting system and then build a completely separate evaluation system.

The better approach is to design data infrastructure that can support both external accountability and internal learning.

If the organization is already collecting information for required measures, ask what additional fields, linkages, or workflow controls would make that information more useful internally. If leadership is tracking operational KPIs, make sure definitions and source data are governed with the same care used for external reporting.

This reduces duplicate work and makes it easier to move from a reported result to a meaningful analysis.

Some questions need more than quantitative data

Not every implementation problem can be understood from an EHR extract.

If a new workflow is not being used consistently, interviews or staff feedback may explain why. If clients are not completing follow-up assessments, the organization may need to understand burden, timing, engagement, or how the request is being introduced. If a community partnership is not producing referrals, referral counts alone will not explain whether the pathway is poorly understood or simply underused.

Evaluation gives the organization permission to ask the next question instead of treating the available metric as the only answer.

A useful evaluation agenda is selective

CCBHCs could evaluate almost everything. They should not.

Choose questions that matter to implementation, strategic priorities, quality, access, equity, outcomes, sustainability, or a known area of uncertainty. Some questions may need a formal evaluation design. Others can be answered through a focused analysis, chart review, workflow review, staff feedback, or a short quality-improvement cycle.

The method should fit the question.

The distinction matters for staffing too

If an organization defines evaluation only as completing required submissions, it will underestimate the capacity needed for the work.

A functioning CCBHC evaluation role may include measure governance, data validation, statistical analysis, dashboards, grant reporting, internal audits, quality-improvement support, evaluation design, interpretation for leadership, and coordination with clinical, operational, IT, and compliance teams.

Those activities are related, but they are not interchangeable.

SAMHSA's certification criteria make quality and other reporting a core CCBHC program area and require capacity to collect, report, and track encounter, outcome, and quality data. They also require a data-driven CQI approach. That creates an opportunity to build an evaluation function that does more than submit numbers.

Required reporting answers, “What do we have to report?”

Evaluation asks, “What do we need to understand?”

A mature CCBHC needs both.