Most conversations about Remote Patient Monitoring (RPM) and Chronic Care Management (CCM)¹ start with devices and tech. These matter, of course. But across hundreds of programs, the biggest determinants of success are rarely the flashiest ones.
The programs that scale and sustain pair a best-in-class device and technology stack with something less visible: the operational discipline to make it work in the real world. Here are the six things the best ones consistently get right.
¹Throughout this piece, RPM and CCM refers to the full spectrum of connected care programs — including RTM, PCM, BHI, TCM, AWVs, and the growing range of reimbursable virtual care services that the strongest vendor partners support under one roof.
1. The program breaks the moment providers have to change how they work
RPM and CCM programs don't fail because providers stop caring. They fail because the program quietly becomes one more thing on an already impossible list — another login, another dashboard, another workflow that doesn't quite fit.
Every extra step is a failure point. And failure points compound.
The best programs don't ask providers to adapt to the technology. They adapt the technology to the provider. That means communicating through whatever channel the practice already uses — EHR messaging in athenahealth, eClinicalWorks, Epic, or any of the dozens of other platforms we work across, or a shared Slack channel, or a simple text thread, or a phone call. Whatever the practice already uses reliably. Forcing a new communication tool into a busy clinical environment is just building a new place for things to fall through the cracks.
But workflow fit is only half the equation. The other half is escalation design — and this is where most programs get it wrong in one of two directions.
Too loose: the care team flags every outlier reading and the provider's inbox fills with noise. After the third unnecessary alert, providers start ignoring all of them. You've trained them to tune out the program.
Too tight: real clinical signals don't get escalated because the thresholds are too conservative. A patient with three consecutive out-of-range blood pressure readings over seven days gets no follow-up. That's not just a missed care opportunity — it's a missed billable event and potentially a bad outcome.
The right calibration takes software that can evaluate patterns specific to each patient — not just generic thresholds — and a care team that does the clinical triage before escalating. Is this reading actually elevated, or did the patient just walk up a flight of stairs? Is this a device issue? Is this consistent with their history? That human layer between the data and the provider is what makes escalations meaningful instead of annoying.
When programs are calibrated correctly, practices should expect roughly 5–10 escalations per 100 enrolled patients per month. That's the signal-to-noise ratio that keeps providers engaged and trusting the program.
And here's what most practices don't realize: each of those escalations is a clinical and financial event. A well-managed escalation that results in a provider touching the patient — adjusting a medication, scheduling a visit, making a clinical decision — is generating an encounter that bills at the same level as a standard office visit, typically $87–$127 under Medicare depending on complexity. The program isn't just managing chronic disease between visits. It's creating visits that would otherwise never have happened — and capturing the revenue that comes with them.
That's a very different conversation than "here's another tool for your workflow."
BLOG: Why Most RPM & CCM Programs Fail at Enrollment (and How to Fix It)
2. Practices that treat enrollment as a launch project quietly fail
Every RPM and CCM program launches with momentum. The practice identifies eligible patients, the care team gets trained, devices ship, and enrollment begins. It feels like a project with a finish line.
There is no finish line.
Even in the best-run programs, patient panels erode naturally and continuously. Patients change providers. Insurance coverage shifts. Some patients achieve better health status and genuinely no longer need high-touch monitoring support — that's actually a win. Others pass away. Some simply decide the program isn't for them, regardless of the clinical benefit. In well-managed programs, that natural attrition runs 10–15% annually. In practices with higher-acuity or more transient patient populations, it can reach 20%.
Do the math on a practice that launches with 500 enrolled patients and never actively re-enrolls: by the end of year two, they could be running at 300–400 patients — or fewer — without a single obvious warning sign. RPM and CCM revenue doesn't show up as its own line item in most practice P&Ls. It gets absorbed into the broader revenue picture, where it's invisible against the noise of everything else moving up and down. Practices typically don't notice the erosion until they're down 30–50% from peak enrollment — and by then they've left months of revenue on the table.
This is why enrollment has to be a permanent operational function, not a launch project. New eligible patients appear every month. Re-enrollment opportunities exist for patients who previously declined. The pipeline never closes.
The enrollment method matters as much as the effort
Not all enrollment is equal, and practices should understand the real-world difference in conversion rates before designing their program.
Provider-led enrollment — a physician recommending the program directly to a patient during a visit — converts at 70–80%. That number isn't surprising when you think about it: the patient is already there, the relationship is established, and the clinical context makes participation feel natural. Some practices make program participation a standard part of their care model, presenting it not as an optional add-on but as part of how they manage chronic conditions at scale.
Remote enrollment — outreach via phone, text, and email conducted under the practice's brand, from the practice's caller ID, by a team the patient associates with their care — is achievable at 20%+ conversion when executed well. Lower than in-clinic, but highly scalable and capable of reaching patients who haven't been seen recently.
The best programs use both. 1bios can place staff directly in the clinic to handle in-person enrollment, and our remote team handles everything else — outreach, follow-up, consent, documentation. The physician focuses on the clinical recommendation. We handle the operational execution from there.
Benefits verification is where quiet revenue loss hides
Enrollment isn't just about getting patients to say yes. It's about making sure the patients you enroll are actually covered — and that the documentation supports billing when claims go out.
Payer rules for RPM and CCM are not static. Coverage requirements shift. Specific diagnosis codes get added or removed from covered indications. A plan that covered a patient last quarter may require additional or more specific documentation this quarter. Staying current across dozens of payers simultaneously is not something a practice can reasonably do on its own.
Our eligibility and benefits verification team does this continuously. When we identify a gap — a patient whose chart documentation doesn't align with a payer's current coding requirements, for example — we surface it to the provider so they can make the right clinical documentation decision before a claim goes out. We're not making coding calls. We're making sure nothing falls through the cracks that shouldn't.
The practices that get this right treat benefits verification not as a one-time enrollment checkbox but as an ongoing function that runs in parallel with care delivery. The ones that don't tend to find out the hard way — through denials, delayed payments, and revenue that was earned but never collected.
3. Vendors who get paid whether or not the program works have no reason to make it work
Here is the most common RPM and CCM vendor failure pattern we've watched play out across the industry:
A vendor sells a practice on the program. Enrollment kicks off with energy. The vendor sends invoices. The practice pays them — because the program is new, optimism is high, and nobody has done the math yet. Months pass. Enrollment stalls. Claims go out but reimbursement is inconsistent. Documentation is incomplete. Some enrolled patients turn out not to be covered. The vendor keeps sending invoices. The practice keeps paying — until suddenly they do the math and realize the program is generating far less revenue than it costs. The vendor, having collected fees throughout, moves on to the next customer.
This happens because the incentives were never aligned. The vendor got paid regardless of whether the program worked. So the program didn't work.
What aligned incentives actually look like
The 1bios model is built around a simple principle: we get paid on a per-billable, per-reimbursed code basis. Not per enrolled patient. Not per month of service. Per code that is fully documented, clinically substantiated, successfully billed, and actually reimbursed by the payer.
That means if a code isn't billable — because the documentation doesn't support it, the minutes weren't logged, the device measurement days weren't met, the patient consent wasn't captured — we don't get paid. If the code is billable but the claim gets denied because the patient changed insurance, the payer changed policy, or the diagnosis coding created friction, we don't get paid. If we fumble on benefits verification and enroll a patient who turns out not to be covered, that's our problem, not the practice's.
The 1bios model is designed so our financial success tracks directly with the practice's. We invoice in arrears and reconcile monthly — practices receive credits for any codes that don't ultimately get reimbursed. On a well-run program, that reconciliation typically represents 0–1% of total billing. The practice is never permanently out of pocket for a program failure that was ours to prevent — and on a program operating the way it should, there's almost nothing to reconcile.
This structure also explains why we maintain a dedicated team supporting the practice's billing function, why our documentation is audit-proof down to the exact minutes, seconds, device measurement days, and patient check-ins recorded each month, and why we don't require minimum commitments or long-term contracts. Minimum commitments and multi-year lock-ins are how vendors protect themselves from programs that don't perform. We don't need that protection because our incentives don't require it.
For practices that want to go further — startups building their billing function from scratch, or established practices that know their current RCM situation needs a reset — 1bios also offers full-service RCM execution as an add-on. But even in the standard model, the support is deep enough that most practices never need it.
Four questions every practice should ask any RPM or CCM vendor
Before signing with any vendor, a practice administrator should ask these four questions. The answers will tell you everything about whether the partnership is real or just a service contract dressed up as one:
- Am I charged if a code isn't billable for any reason?
- Am I charged if a code is billable but the claim isn't reimbursed?
- If I'm recouped by a payer due to a documentation error on your end, will you make me whole?
- Will you guarantee that 100% of clinical and billing documentation lives in my EHR system?
A vendor who answers no, no, yes, and yes — in that order — has real skin in the game. Any other combination of answers tells you who is carrying the risk.
If your vendor wins, whether or not the program works, it’s not a real partnership. It’s a service contract.
4. RCM isn't a billing department problem — it's a program design problem
The care was delivered. The documentation exists. The patient was monitored, supported, and engaged all month. And then the claim didn't get paid.
This is one of the most avoidable ways RPM and CCM programs leak revenue — and it happens constantly, because billing for these programs is genuinely different from standard office visit billing and most practice billing teams, whether in-house or outsourced, have never worked these codes before.
RPM and CCM codes operate on a monthly cadence with specific date-of-service rules that have to be applied correctly and consistently, month after month. The minutes have to be logged precisely. The measurement days have to meet threshold. The dates can't overlap or violate code-specific rules. A billing team that handles these codes the same way they handle a standard E&M visit will generate denials — not because the care wasn't delivered, but because the claim wasn't built correctly.
And then there's the denial side. Many practices either don't track denials systematically or don't appeal them when they should. Revenue that was fully earned just evaporates.
What a real RCM relationship looks like
1bios isn't a practice's RCM company — that relationship stays with whoever the practice already uses. But because we're at financial risk on every code, we staff a dedicated team that works directly with the practice's billing function from day one.
In the first 90 days especially, that's a high-touch relationship. We make sure the billing team understands how RPM and CCM codes work, what's coming each month, and how to submit claims correctly. When something goes wrong — a claim structured incorrectly, a denial for a reason that doesn't make sense — we troubleshoot it with them directly.
The documentation we produce for every patient makes this easier. Every month, the practice receives a complete, audit-proof health summary for each enrolled patient: time and date stamps for every device measurement, every virtual care session, every alert and how it was addressed, every inbound and outbound communication by channel, care plan updates, and clinical notes. When a payer questions a claim, the answer is already in the record.
For practices that want to go further — startups building their billing function from scratch, or established practices that know their current RCM situation needs a reset — 1bios also offers full-service RCM execution as an add-on. But even in the standard model, the support is deep enough that most practices never need it.
The feedback loop that keeps the program calibrated
The real operational value of a tight RCM relationship isn't just catching problems — it's feeding information back into the program before problems repeat.
When denial patterns emerge, we surface them. If a specific payer stops covering an add-on time code beyond a single unit per month, we adjust — and we accept that some of what we delivered won't get reimbursed, because that's our risk to carry, not the practice's. If a non-Medicare payer has an unusual rule where passing more than one chronic diagnosis code on a claim disqualifies the entire encounter — regardless of how clinically appropriate each diagnosis is — we identify it, document it, and make sure every future claim for that payer is structured accordingly. These aren't standard rules. They're random, payer-specific, and constantly evolving. Smoking them out proactively is part of what we staff for.
When those patterns feed back into operations — enrollment decisions, documentation workflows, code selection — the program gets sharper over time. Revenue that would have quietly leaked instead gets protected.
The program isn't working if the care is delivered but the claims aren't getting paid. Getting paid isn't a billing department problem. It's an operational discipline that has to be built into the program from the start.
5. Patients disengage when they feel monitored instead of cared for
Ask a patient what they remember about a bad RPM or CCM experience and they won't mention the device or the software. They'll tell you about the call.
The one where someone they'd never spoken to before called from an 800 number, asked for "Mr. Jonathan Winters" when everyone calls him John, read through a checklist of questions he'd answered identically the month before, and had no idea he'd seen his doctor five days ago and was already on a new medication. Or the one where they got a call when they'd specifically asked for a text. Or where nobody on the other end spoke their preferred language comfortably. Or where the caller represented themselves as "your monitoring company" instead of as an extension of the practice he's trusted for a decade.
That patient doesn't answer next month. And the month after that. And eventually he's just gone.
This is how low-relationship programs lose patients — not in a dramatic moment, but in a slow accumulation of interactions that felt generic, transactional, and disconnected from the care relationship that actually matters to them.
What high-relationship programs do differently
The operational differences are specific and replicable.
Same care manager, every month. Not a rotation. Not whoever is available. The same person, who knows that this patient likes to warm up with a few minutes of conversation before getting clinical, whose wife just had surgery, who has a dog named Biscuit, and who will tell you everything is fine even when it isn't unless you've built enough trust that they feel safe being honest. That relationship is built over months and it is genuinely irreplaceable.
Every touchpoint is structured to meet the interactive communication standards required for billing — but that's a baseline, not a ceiling. The goal is a call worth having, not a call worth billing.
Before every call, the care manager reviews an AI-generated summary of what matters most right now for that specific patient — not a generic care plan template, but a live snapshot that surfaces whether they're on a new medication or adjusted dose, whether their readings are trending up or down, what appointments are upcoming, what screenings are due, what was flagged last month and whether it was resolved. The call starts informed, not cold.
The call itself happens through whatever channel the patient prefers — phone, video, text — at a time they've agreed to, from the practice's number, in their preferred language, representing their doctor. Not "your monitoring company." Dr. Rivera's care team.
And when something matters — a reading that's been trending wrong, a medication question, a missed appointment — the patient hears something that changes everything: "I'm flagging this for Dr. Rivera right now. We're going to get this sorted out." That's not a script. That's a care relationship. And patients know the difference.
What the data shows
High-relationship programs — where continuity, personalization, and genuine engagement are built into operations — show patients staying on service for two, three, even more years on average, and still growing. We're tracking patient cohorts going back to 2020 and the retention curves on well-run programs haven't plateaued.
Low-relationship programs, where touchpoints are generic and care managers rotate, see patients cycling off in three to nine months.
The monthly talk-to-patient rate tells the same story: high-90s to 100% on high-relationship programs, 80% or lower on low-relationship ones. That gap compounds fast. A 20-point difference in whether patients actually pick up the phone, sustained over a year, is the difference between a program that builds and a program that quietly erodes.
Patient age, diagnosis mix, payer composition — all of these matter and explain some of the variance. But the directional difference holds even when you control for all of it. Relationship quality is an independent variable. It's not soft. It's operational infrastructure.
Patients don't stay engaged because they're managed. They stay engaged because they feel known.
BLOG: The Missing Piece in Remote Care Isn’t Data. It’s People.
6. Providers can't champion a program they can't see — and patients notice when they don't
A physician walks into an exam room with a patient they see two or three times a year. That patient has been enrolled in RPM for eight months. The care team has called them every month, reviewed hundreds of blood pressure readings, escalated twice, helped them get a medication adjustment, and updated their care plan. The provider has no idea any of this happened.
That's not hypothetical. It's the default state of most RPM and CCM programs — and it's one of the most expensive missed opportunities in chronic care.
When providers are disconnected from what's happening between visits, two things break. First, the patient loses the most powerful reinforcement available to any care program: their doctor acknowledging their effort. "I see your blood pressure readings have been much more consistent lately" is not a small thing to a patient who has been faithfully taking measurements every morning for six months. It's validation that the program matters, that someone important noticed, and that their effort is connected to their care. Second, the provider loses the ability to champion something they can't see — and providers who don't champion the program, even passively, are quietly contributing to patient churn without knowing it.
What visibility actually looks like in practice
Every month, 1bios places a complete health summary directly in the patient's EHR chart. Not a separate portal. Not a report that lives somewhere else. In the chart, where the provider already works.
But a month of daily device measurements, care team calls, texts, alerts, escalations, medication updates, and care plan changes is a lot of information. Nobody has time to read all of it before a visit. So alongside the full summary, we surface an AI-generated narrative of the top three things the provider needs to know about this patient right now — what's changed, what's been flagged, what deserves a mention during the visit. That's the minimum viable visibility that actually changes provider behavior at the point of care.
For escalations, we go further — directly into whatever communication channel the practice uses. EHR task, shared Slack channel, secure email, text. Whatever gets seen fastest gets used.
At minimum, every enrolled patient's chart carries a clear callout of their enrollment status. Even if nothing significant happened that month, the provider sees it, remembers the program exists, and has a natural opening: reinforce the value, acknowledge the effort, keep the patient engaged. Thirty seconds at the point of care does more for retention than almost anything else we can do remotely.
The reinforcement gap most providers don't know they have
Here's the honest truth: most providers still don't do this naturally, even when the infrastructure is right. Not because they don't care — they do — but because their default orientation is what's in front of them in the exam room, not what happened remotely over the past thirty days.
This is where a good vendor partner becomes genuinely annoying in the right way. We track unenrollment reasons across every practice. When "provider didn't reinforce the program" shows up as a pattern — and it does — we put that data in front of the practice directly, connected to patient churn numbers and lost RPM and CCM revenue. Not as a criticism. As a lever they didn't know they had.
The providers who internalize this shift — who start walking into exam rooms with three talking points about what their remote care team has been doing — see retention improve, patient trust deepen, and the program start to feel like what it actually is: an extension of their practice, not a side project nobody sees.
Conclusion
Most RPM and CCM conversations start in the wrong place. They start with the device, the platform, the reimbursement rates, the codes. Those things matter. But across hundreds of programs, the ones that scale and sustain aren't winning on technology. They're winning on operational discipline.
No workflow friction. Enrollment that never stops. A partner with real skin in the game. RCM treated as a feedback loop. Patients who feel known. Providers who can see and reinforce what's happening between visits. These aren't advanced ideas. They're blocking and tackling — done consistently, at scale, by a team built to do nothing else.
The challenge is that these six things are deeply interconnected. A practice that tries to assemble them across multiple vendors, or manage them in-house without dedicated infrastructure, almost never gets all six right simultaneously. The gaps between vendors are exactly where programs leak — where a patient falls through because enrollment and RCM aren't talking, or where a denial pattern never feeds back into operations because nobody owns the full loop. A truly turnkey partner doesn't just deliver the pieces. They own the connections between them.
The practices that get all six right don't just collect more reimbursement. They build something harder to replicate: a chronic care program that patients stay in, providers trust, and payers increasingly reward. As value-based care models mature and the industry moves beyond pure fee-for-service reimbursement, programs built on these foundations will be positioned to capture that upside too. That's a longer conversation — but it starts here.
If you're evaluating where your program stands on any of these dimensions, we're happy to have that conversation.
