Skip to main content

Building a Data-Driven Culture in Behavioral Health Organizations

Jeremy Bloom, Co-founder · · Updated

“Data-driven” is a vague compliment until it names the record the program is already required to keep and the decision that record is for. Behavioral health programs generate assessments, encounters, credentials, and, where they hold grants, spending against an award. The useful shift is to read those records while the work is still open, and to say what is missing.

Duties that are already measurement

An opioid treatment program must maintain current quality assurance and quality control plans that include, among other things, annual reviews of program policies and procedures and ongoing assessment of patient outcomes [1]. It must also maintain a current diversion control plan as part of its quality assurance program that contains specific measures to reduce the possibility of diversion of dispensed MOUD, and that assigns specific responsibility to the program’s providers and administrative staff for carrying out the diversion control measures and functions the plan describes [1]. “Ongoing assessment” is not a promise that every field is filled. It is a duty to look at outcomes on a continuing basis and to be able to show the review [1].

Programs that use The ASAM Criteria are told to reassess. The FAQ says Levels 2.1, 2.5, 3.1, and 3.5 recommend monthly formal reassessments, and that if a patient reveals new information that impacts their treatment needs, the treatment plan should be updated with consideration for that new information [2]. A report of who is past that interval is a direct reading of that recommendation. It is not a new metric invented for a slide.

Accreditation manuals add their own performance-measurement expectations. Those expectations are the standard in the manual you are surveyed under. This post does not assign a section number to a manual it is not quoting. Bring the manual to the quality meeting.

What a useful view contains

A program director can look at one place for the counts they manage: who is in the program, which reassessments are late against the rule they adopted, which licenses end soon, and which grant is near its budget. The view is current only for the fields staff have entered. Late entry means a late view. Say that out loud so nobody treats a blank as a zero.

Cross-reading is the point of putting the fields next to each other. A housing problem recorded on the assessment does not appear in a finance-only report unless someone placed it there. The FAQ does not name housing as an assessment field or say that a housing problem by itself sets the level of care [2].

Alerts are reminders of dates the rule or the contract already set: a license end date, a reassessment month, and the annual review of program policies and procedures in § 8.12(c) [1]. They do not create the duty.

What not to claim

Do not tell a board or a staff meeting that outcome reports are complete because a screen refreshed. Completeness is an audit of the required fields, not a property of the software. Do not describe results from organizations as if a vendor had customers to survey. The evidence for a measure is the record and the standard it is tied to [1, 2].

Leaders still have to use the view in the meeting: name the late reassessments, assign the review, and check it the next time. Training staff to read the count is part of the work. Buying a chart is not a culture.

Sources

  1. 42 CFR 8.12, federal opioid use disorder treatment standards, including quality assurance, Office of the Federal Register, eCFR. Accessed September 28, 2026.
  2. The ASAM Criteria frequently asked questions, American Society of Addiction Medicine. Accessed September 28, 2026.

On Encore OS, leaders set goals, keep scorecards and run structured meetings in the same system as the rest of the organization’s work.

Explore the platform