Remote Patient Monitoring for Chronic Disease Management vs. Vitals
As the Remote Patient Monitoring (RPM) market has evolved over the past five years, two primary types of RPM have emerged: RPM solutions for chronic disease management and those designed for tracking vitals and post-discharge monitoring. While there is some overlap, the different types differ based on goals, duration, and the types of devices used.
Remote Patient Monitoring for Chronic Disease Management
RPM for chronic disease management is designed to support patients with long-term health conditions, such as diabetes, hypertension, and respiratory conditions like COPD. These solutions typically focus on collecting data that is relevant to managing these conditions, such as blood glucose levels, blood pressure, weight, and pulse oximetry readings.
Goals: The goals of RPM for chronic disease management are to improve patient outcomes, reduce healthcare costs, and increase patient engagement in their own care.
Duration: RPM for chronic disease management is typically an ongoing process, with patients using the technology to monitor their health on a regular basis over a long period of time. After all, patients live with their chronic conditions 365 days a year, not just the three or four days per year they visit their doctor in person.
Devices: RPM for chronic disease management may include devices such as blood glucose meters, continuous glucose monitors (CGMs), blood pressure cuffs, weight scales, and pulse oximeters.
RPM for Post-Discharge Vitals Monitoring
RPM for vitals and post-discharge monitoring, on the other hand, is designed to track patient health status following a hospitalization or medical procedure. These solutions typically focus on collecting data such as heart rate, blood oxygen levels, and respiratory rate.
Goals: The goals of RPM for vitals and post-discharge monitoring are typically to prevent readmissions, ensure patient safety, and support patients as they recover from a medical procedure.
Duration: RPM for vitals and post-discharge monitoring is typically a shorter-term solution that is used for a specified period of time following a hospitalization or medical procedure.
Devices: RPM for vitals and post-discharge monitoring may include devices such as pulse oximeters, ECG monitors, and respiratory monitors.
Considering RPM? What to Look for in a Solutions Provider
Overall, while both types of RPM solutions involve the remote monitoring of patient health data, they differ in terms of their goals, duration, and the types of devices used.
When you are considering RPM, it’s important to ask these questions as you embark on your vendor search:
-
Is my organization doing this for chronic disease management or vitals monitoring?
-
How important is it to my clinicians to have a solution that integrates with our EHR so they can see patient-generated data in the context of other clinically relevant information?
-
What clinical use cases does the solution or solutions need to be able to support?
Rimidi’s Clinical Management Platform for Chronic Disease Management
Rimidi’s Clinical Management Platform combines patient-generated health data from connected devices or patient reported outcomes measures with clinical data from the EHR to drive patient-specific clinical insights and actions through embedded clinical decision support cards.
Rimidi’s Disease Views are problem-oriented screens providing a set of relevant clinical data along with guideline-based risk score(s) specific to a disease and a patient. Current disease views include diabetes, cardiovascular (hypertension), heart failure, obesity, Nonalcoholic Fatty Liver Disease (NAFLD/NASH), and respiratory.
Today, Rimidi works with a variety of providers across the US – from large academic medical centers to smaller physician clinics and Federally Qualified Healthcare Centers. Whether you are seeking to capture billable Remote Patient Monitoring or Chronic Care Management activity or want a better way to manage chronic diseases by including RPM and care management, Rimidi can help meet your needs.
