Building a Psychiatric Collaborative Care Platform

The billing side of the Collaborative Care Model is genuinely well documented: codes, thresholds, the same-month exclusion rule. What’s harder to find written down anywhere is the platform architecture underneath it: how a behavioral health care manager, a consulting psychiatric provider who may never see the patient directly, and the billing practitioner all work from one coordinated system instead of three people comparing notes over email.

Epic-Approved Vendor · HIPAA and SOC 2 controls built into every build · 50+ healthcare solutions shipped.

The Three Roles and What Each One Needs From the System

The consultant’s view is structurally different from the other two roles, caseload-wide rather than patient-by-patient, which is the design requirement most platforms get wrong by building one generic patient-record view for all three roles.

The Registry: Beyond the 4-Part Sketch

Mindbowser’s published BHI/CoCM billing guide sketches the registry at a high level: screening scores, care manager notes, consultant reviews, and a time log. Building it means specifying what each of those actually is as a data model, not just a list of categories.

The Psychiatric Consultant’s Caseload Review Workflow

This is the workflow most general care-management platforms weren’t built for, because it’s specific to CoCM’s structure. The consultant doesn’t work through a patient list the way a treating clinician does. They review a caseload, typically weekly, looking at which patients are trending worse on their screening scores, which the care manager has flagged, and which need a documented recommendation without a direct visit.

Screening Score Trending, Not Just Point-in-Time Capture

A single PHQ-9 score tells a consultant almost nothing on its own. A score of 12 could mean a patient stabilizing from 18 or worsening from 6, and the clinical recommendation is close to opposite in each direction. A platform that only stores the current score, overwriting the prior value each time, structurally can’t support the trend-based judgment the consultant’s role actually requires.

The registry needs every screening event stored as its own record, not the latest value alone, which is also what makes the billing-defensibility argument work: a reviewer checking whether the consultant genuinely engaged with a patient’s trajectory needs the trend visible, not just a single number on the date of the claim.

This is a common mistake specifically because most general-purpose EHR modules treat a screening score the way they treat a vital sign, a single current value with prior readings buried in a history tab nobody clicks through during a fast caseload review. That pattern works fine for a value a clinician checks once and moves on from.

It fails for CoCM’s actual use case, where the consultant is deliberately scanning a whole caseload for who’s trending in the wrong direction, which requires the trend to be visually surfaced at the caseload-list level, not one click away for each patient individually.

A caseload review interface that makes the consultant open each patient’s chart to see whether their score improved or worsened isn’t a minor UX inconvenience; it’s a structural barrier to the actual clinical task CoCM asks that role to perform, and it’s the specific gap that separates a platform built for CoCM from a general care-management tool with a CoCM label added to it.

Time Aggregation Across Three Roles

The consultant-time attribution is the harder half of this calculation, and it’s worth being specific about why. A consultant reviewing a 20-patient caseload in a single 60-minute session isn’t spending 60 minutes on any one patient; they’re spending some fraction of that hour per patient depending on how much each case needed.

A platform that can’t capture that per-patient attribution defaults to one of two wrong shortcuts: crediting the full 60 minutes to every patient reviewed, which overstates billable time and creates real audit exposure, or crediting none of it because the time can’t be cleanly split, which understates the consultant’s actual contribution and leaves legitimate revenue uncaptured.

The correct approach requires the caseload review interface itself to log time per patient as the consultant works through the list, not a single session-level timer that has to be manually apportioned afterward.

Integrating With the Primary Care EHR

CoCM sits alongside a patient’s primary care relationship, not separate from it. The registry needs to pull the patient’s current condition list and share screening results back into the primary EHR, so the primary care team sees behavioral health status without logging into a separate system. ConnectHealth is the connectivity layer that makes this bidirectional flow work, whether the primary EHR is Epic, Cerner, or Athenahealth, keeping the registry and the primary chart in sync rather than requiring manual reconciliation between two systems that both claim to be current

Related read: Epic EHR Explained: What It Is, What It Costs, and Who It’s For

What Happens When a Patient Transitions Out of CoCM

A patient stabilizing may step down from CoCM to general BHI, or discharge from behavioral health coordination entirely. The same transition-tracking discipline this cluster’s other pieces describe for program switches applies here: the registry needs to close out CoCM’s active status cleanly, without losing the historical screening trend and consultant-review record that the patient’s chart has built up, since that history remains clinically relevant even after billing under CoCM’s specific codes stops.

The step-down case deserves specific handling because it’s clinically different from a simple program switch. A patient moving from CoCM to general BHI isn’t starting a new behavioral health relationship; they’re continuing one under a lighter-touch billing model, and the platform should reflect that continuity rather than treating it as closing one case and opening an unrelated one.

The screening trend that justified stepping down in the first place, several consecutive months of improving scores, is exactly the evidence a reviewer would want to see if the step-down decision were ever questioned, which means the registry’s value as a historical record actually increases at the moment of transition, not decreases. A platform that archives CoCM data somewhere inaccessible once a patient exits the program is discarding the specific evidence that makes the transition defensible.