Why RPM and CCM Data Needs a System of Action, Not Just a Record

First Analysis recently put out a report built around a simple distinction: electronic health records are systems of record. They document what happened during a visit, what medications a patient is on, and what the lab results showed. That's the job they were built for, and they do it well.

What the report argues — and what anyone working in chronic care management already knows — is that healthcare doesn't have enough systems of action: tools that take what's been recorded, or what's coming in continuously, and turn it into something a care team actually does. That's the territory remote care programs like remote patient monitoring (RPM), chronic care management (CCM), and advanced primary care management (APCM) are built around.

Between visits, a patient with hypertension and diabetes generates a steady stream of information: daily blood pressure readings from a cellular-connected monitor, step counts and sleep data from a wearable, notes from a monthly care management call, and updates they report themselves about how they're feeling or whether they took their medication.

Some of that gets routed into the EHR. Some of it doesn't make it that far at all. Either way, the volume keeps growing — more devices, more monitoring programs, more touchpoints — and most of it sits there unreviewed. A blood pressure reading that's been climbing for two weeks looks identical in the chart to a single normal reading, unless someone is actually looking at the trend and flagging it.

This is the same problem First Analysis describes for clinical data exchange more broadly, just playing out in the data that's generated continuously rather than at a single encounter. The report points out that the highest-risk patients — the ones with the most chronic conditions, the most care transitions, the most complexity — are often in the settings least equipped to use their data well. The same is true for between-visit data. The patients who'd benefit most from someone catching a concerning trend early are often the ones least likely to have anyone looking.

What Reviewing the Data Actually Looks Like

Here's what that looks like with real numbers behind it. Prevounce recently completed a retrospective cohort analysis of 655 patients enrolled in an RPM program for hypertension, paired with structured virtual care management. Patients used cellular-connected blood pressure monitors to transmit daily readings. Care managers reviewed those readings and checked in with patients, adjusting lifestyle and adherence guidance based on what the trends showed.

Over nine months, the program produced an overall 6.3% reduction in systolic blood pressure and a 7.4% reduction in diastolic blood pressure. Patients who started with stage 2 hypertension — the highest-risk group — saw the largest improvements, with reductions of 9.1% and 9.7% respectively.

Two findings from the study are worth calling out specifically. The patients with the most room to improve saw the most improvement — exactly what you'd expect from a program built to prioritize by risk rather than treat every patient the same. And the results held up even for patients who transmitted readings on a more moderate schedule, 2 to 15 days a month, coming close to matching the patients who transmitted daily. What drove the outcomes was a care manager consistently reviewing the data and following up on what they saw, regardless of how often the patient transmitted readings.

Built to Sit in Front of the EHR

Prevounce isn't trying to replace the EHR, and there's no reason to. The EHR remains the system of record. Prevounce sits in front of it, taking in RPM data, care management activity, and patient-reported information, and turning it into something the care team can act on before it's just another data point. Prevounce is the system of action.

Part of what makes that possible is having all of the data in one place. Without that, a care team is checking a blood pressure monitor's portal, a separate wearable app, and CCM call notes as three different workflows, each on its own schedule. Prevounce pulls those streams together, so a care team can ask "what does this patient need right now" instead of hunting across three different places to find out.

A blood pressure reading outside a clinical threshold becomes a task for a care manager to follow up on. Two weeks of trending readings becomes a prompt to revisit the treatment plan right away, instead of sitting in a chart until someone happens to notice. A patient who's gone quiet — no readings transmitted in days — becomes an outreach call. AI-powered insights add another layer, surfacing patterns a care team might not catch through pre-configured alerts or tasks. Vitals data and care notes can still ultimately feed into the EHR and satisfy documentation requirements, but the review and the follow-up happen before that, while there's still time to do something useful with it.

This also answers a question we hear often: Why not just use the EHR for this? The EHR documents what happened. It doesn't tell anyone what to do next with the steady stream of data coming in between visits. That's not what it was built for, and asking it to do that job isn't realistic. RPM, CCM, and APCM exist because chronic disease management is a 365-day job, and the results above are what that job looks like when the right infrastructure is behind it.

The Practices That Will Pull Ahead

Between-visit data isn't going away, and the volume only grows from here — more connected devices, more programs, more ways for patients to generate information outside the clinic. The practices that build a system to review it, prioritize it, and turn it into action are the ones who'll actually improve outcomes and manage risk with it. Everyone else is just accumulating more data they don't have time to use.

For organizations operating under shared savings arrangements, that distinction has direct financial weight too. We've written more about how this plays out for ACOs and value-based care organizations in "Remote Care Management for ACOs: How Prevounce Supports Shared Savings and Quality Performance."

If you want to see how this works for your organization, book a consultation.