Why Do Practices Leave Collaborative Care Revenue on the Table, and What Does It Take to Actually Bill 99492 to 99494?

How to Actually Capture the CoCM Codes You Have Already Earned

The goal is simple: every minute your care manager already spends gets logged to the right patient and the right month, and the correct code goes out at month end without a compliance scare. Here is what does that, move by move.

1. Stand Up a Per-Patient, Per-Month Time Ledger

CoCM lives or dies on one number: behavioral care manager minutes for each enrolled patient in each calendar month. Before you bill anything, you need a place where those minutes land as the work happens, not reconstructed from memory at month end. The initial month code covers the first block of minutes, subsequent months cover their own, and the add-on stacks in thirty-minute increments. You cannot bill a threshold you never counted, so the ledger comes first, per patient, per month, every month.

2. Keep the Enrollment Registry Current

The care manager works a registry of enrolled patients, and the registry is what tells you who is even eligible to bill this month. Patients enroll, graduate, drop off, and return, and if the registry drifts, you either miss minutes for active patients or log time against someone who left the program. Keeping the registry clean, who is enrolled, when they started, where they are in treatment, is the difference between a defensible month-end claim and a guess.

3. Assemble the Right Code Against the Minute Thresholds

At month end, the minutes decide the code. The first calendar month of care manager activity is coded one way and only once, subsequent months another way, and the additional thirty-minute code stacks on top when the time supports it. Get the initial-versus-subsequent choice wrong, or claim an add-on the minutes do not support, and you have either left money uncollected or invited a takeback. Month-end assembly is a checklist, not a judgment call, once the ledger is honest.

4. Reconcile So Codes Do Not Collide in the Same Month

The rules that scare practices into billing nothing are the collision rules. The general behavioral health integration code and the collaborative care codes are not meant to be reported by the same professional for the same patient in the same month, and the American Psychiatric Association and AAFP both spell out how these services fit together. A monthly reconciliation that checks each patient for exactly one clean billing path is what turns compliance risk from a reason to avoid billing into a box you have already checked.

5. Hand CoCM Billing to a Dedicated Team

Practices that finally get paid for collaborative care do it by handing the billing administration to a dedicated team: remote specialists who own the time ledger, keep the registry current, assemble the month-end codes, and run the collision check, live in 1 to 2 weeks. The psychiatrist consults and the care manager treats, while someone whose whole job it is captures the revenue the program already earned. Below is what it sounds like when nobody owns this yet, in practice teams’ own words.

Why This Keeps Happening

If the clinical work is already happening, why does the revenue never show up? Because collaborative care billing is unlike almost anything else your practice bills. It is not tied to a single visit you can code from a note; it is tied to accumulated behavioral care manager minutes across an entire calendar month, for each enrolled patient, consulted on by the psychiatrist and directed by the treating physician. The American Psychiatric Association and AAFP both describe CoCM as a monthly, time-based service with an initial-month code and separate subsequent-month codes. Nothing in a normal encounter workflow captures a running monthly minute total, so the number that makes the claim billable is exactly the number nobody is keeping.

The second half is the collision rules, and they do real damage by making inaction feel safe. The general behavioral health integration code and the collaborative care codes are not meant to be reported by the same professional for the same patient in the same month, the initial-month code is billed only once, and the add-on stacks in thirty-minute blocks up to a monthly limit. Each rule is manageable on its own, but stacked together with no one assigned to them, they read as risk, and the practical response is to bill nothing. That is the gap a disciplined AI medical coding workflow with human oversight is built to close, by turning the rules into a checklist instead of a fear.

And the cost is not just uncollected codes; it is the program itself. When collaborative care shows no revenue, it reads to leadership as a cost center, and a cost center is what gets cut when a quarter tightens. The clinical results can be strong, the patients genuinely better, and the program still ends up on the chopping block because the billing that would have proven its value was never captured. A program that works but bills nothing is more fragile than one that works and gets paid, and the difference is entirely in who owns the ledger.

Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:

The Solution

So what does “someone whose whole job it is” look like for collaborative care? The specialist starts with the ledger the practice never kept: a per-patient, per-month record where behavioral care manager minutes land as the work happens, not as a month-end guess. They keep the enrollment registry current so every active patient’s time is counted and no graduated patient’s is, and they hold the running total that decides which code the month qualifies for. That daily discipline is exactly what dedicated behavioral health billing support is built to own, so the number that makes the claim billable actually exists when month end arrives.

Then comes the month-end assembly a practice keeps deferring. The specialist maps each patient’s minutes to the right code, initial month billed once, subsequent months coded separately, the thirty-minute add-on stacked only where the time supports it, and runs the collision check so the general integration code never lands in the same month as CoCM for the same professional. The psychiatrist keeps consulting and the care manager keeps treating, while the claim gets built correctly and defensibly by someone who does only this, across many programs, every month.

Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow assembles the month-end code against the minute thresholds and flags any collision; a person confirms the enrollment, the minutes, and the code choice before anything is submitted. Every security control that protects the behavioral health data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving mental health records through a billing workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team capture your CoCM revenue better than your own staff? Because keeping a per-patient monthly time ledger and assembling time-based behavioral codes is their entire day, not the thing they squeeze between clinical demands that always win. The people working your collaborative care billing are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US behavioral health integration and CoCM billing rules. They know the initial-versus-subsequent code logic, the add-on thresholds, and the collision rules cold, so the rules that scared your practice into billing nothing become a routine monthly checklist for them.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so the month-end ledger never falls behind because the one person who owned it was on vacation.

And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.

Put the routine and the people together, and a specific list of things simply stops happening.

How We Permanently Fix the Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented CoCM billing workflow: exactly how care manager minutes get logged per patient per month, how the registry stays current, which code each month qualifies for at which threshold, and the collision check that keeps the general integration code out of a CoCM month for the same professional, all written down and worked the same way every month. Before we bill a single month for a new program, we chart your enrolled panel and your minute-capture gaps so we can see where the revenue is actually leaking, and we build the workflow against that.

From there the workflow becomes a living playbook rather than tribal knowledge in one care manager’s head. It records how minutes are captured for each patient, how the registry is reconciled, the exact month-end code logic, and the collision rules as the APA and AAFP describe them, kept current as guidance changes. When your specialist is out, a trained backup works the same playbook the same way, so a month of billable collaborative care never quietly closes uncaptured because one person was away.

That is the difference between hoping leadership keeps funding a cost center and proving the program pays for itself, and it is what a dedicated medical billing and coding partner actually buys you. A care manager or biller leaving used to mean the ledger fell apart and the revenue vanished again. Under this model the workflow keeps running, the playbook stays, the backup steps in, and collaborative care stops being the program you have to defend and becomes the one that carries its own weight.

The Whole Thing in Four Sentences

Practices leave collaborative care revenue unbilled because 99492 to 99494 are time-based and month-based: they require logged behavioral care manager minutes per enrolled patient per calendar month, a correct initial-versus-subsequent code choice, and a collision check against the general integration code, and without someone owning that ledger the compliance risk feels bigger than the money. Asking the care manager to track her own minutes, deferring it to the billing team, or billing nothing to stay safe all fail the same way. The fix is a per-patient monthly time ledger, a current enrollment registry, correct month-end code assembly against the thresholds, and a monthly reconciliation. A primary care group running an integrated care program runs exactly this model with us today, names withheld, no patient data shown.

If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.

Ready to get paid for the program you already run? Try us risk free: two weeks, your real CoCM enrollment and minute capture, dedicated specialists building the ledger and assembling the month-end codes, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.

Written By

Dan Nandan

Founder and CEO, Staffingly, Inc. · Piscataway, NJ

Dan Nandan has spent 25+ years in IT consulting and healthcare BPO, was among the first in the US to build an RPO/BPO delivery network in India, and has been featured in Computerworld. He runs the operations and the dedicated virtual teams behind the workflows on this page; the team-voice answers above come from the remote specialists who work them every day.

Connect on LinkedIn

Where the Claims on This Page Come From