Remote patient monitoring (RPM) after discharge means a hospital sends selected patients home with connected devices (blood pressure cuff, pulse oximeter, weighing scale, glucometer or a wearable), receives their readings daily, and has a nurse-led team act on readings that cross agreed limits. Done well, it catches deterioration early, so a patient gets a call, a medicine change or an OPD visit instead of an emergency readmission.
Done badly, it produces a stream of numbers nobody looks at. The difference is not the device. It is patient selection, alert rules, staffing and how readings reach the patient record.
This guide covers who benefits, how a programme is built, what the evidence actually shows, the 2026 US billing changes, the oversight concerns raised by US regulators, and how Indian hospitals can run RPM without a dedicated reimbursement code.
Who benefits most from post-discharge monitoring
RPM works best when there is a measurable sign that changes before a patient becomes seriously unwell, and a clear action the team can take. Good candidates include:
- Heart failure: daily weight, blood pressure and heart rate. Weight gain over a few days often precedes fluid overload.
- COPD: SpO2, heart rate and symptoms.
- Post-surgical recovery: temperature, heart rate, wound photos and pain scores in the first one to two weeks.
- Hypertension and diabetes after an admission: blood pressure and glucose while medicines are being adjusted.
- Elderly patients with multiple conditions: a combination of vitals and simple symptom check-ins.
Patients who are poor candidates include those who cannot use devices and have no caregiver to help, and those whose risk is not visible in vital signs.
What the evidence shows
The best-known randomised trial of structured remote management is TIM-HF2, published in The Lancet in 2018. It enrolled 1,571 heart failure patients in Germany who had a recent heart failure admission. According to the trial abstract on PubMed, patients in the remote management group lost 17.8 days a year to unplanned cardiovascular admissions or death, compared with 24.2 days in usual care. The reduction was driven mainly by lower mortality.
Three details from TIM-HF2 matter for anyone designing a programme:
- It was structured. A telemedical centre staffed around the clock reviewed data daily and acted on it.
- It selected patients. Enrolment targeted patients with a recent admission, not everyone with heart failure.
- Benefits faded after it stopped. A follow-up found no significant difference in the year after the intervention ended.
How a post-discharge RPM programme works
| Step | What happens | Who owns it |
|---|---|---|
| Enrolment | Eligible patient identified before discharge, consent taken | Ward team, RPM coordinator |
| Setup | Device paired, patient and caregiver trained | RPM nurse or technician |
| Daily readings | Patient takes readings; data syncs via app or gateway | Patient, caregiver |
| Triage | Readings outside limits flagged to a worklist | Software, RPM nurse |
| Action | Call, medicine change, OPD visit or emergency advice | RPM nurse, doctor |
| Review | Weekly summary to treating doctor | RPM team |
| Graduation | Monitoring ends after a set period or stability | Treating doctor |
Most programmes run for 30 to 90 days after discharge, which covers the period when readmission risk is highest.
Alert rules: the part that makes or breaks it
Alert thresholds should be set per condition and, where sensible, per patient. For heart failure, many programmes use weight gain over one day and over several days, plus blood pressure and heart rate limits. Every alert needs a defined response time and a named person.
Getting data into the record
Readings should land in the patient's record in your HMS or EMR, not just in a vendor portal. That way, the doctor sees home blood pressure trends during the OPD visit, and the readmission team sees the history if the patient comes back. Standards such as FHIR R4 Observation resources make this cleaner; our HL7 FHIR integration guide covers the basics.
The US payment picture in 2026
In the US, RPM is paid through specific CPT codes in the Medicare Physician Fee Schedule. The CY 2026 final rule, issued on October 31, 2025, added two new codes for shorter monitoring and less management time, as summarised in Physicians Practice:
- 99445: device supply with data transmitted on 2 to 15 days in a 30-day period. Previously, the device code required at least 16 days.
- 99470: the first 10 minutes of treatment management in a month, where the older code required 20 minutes.
This matters for post-discharge programmes because many patients do not transmit every day, and some need only brief monitoring. Billing rules (one device code per patient per 30 days, one billing practitioner) still apply, and rates vary by locality, so check the CMS fee schedule before building a business case.
The oversight warning
In September 2024, the HHS Office of Inspector General reported that Medicare RPM use grew from about 55,000 enrollees in 2019 to more than 570,000 in 2022, and that about 43% of enrollees did not receive all three components of RPM (education and setup, device supply, and treatment management), as reported by Healthcare Dive. OIG asked CMS to strengthen oversight.
The lesson applies everywhere: programmes built to bill rather than to act on data attract scrutiny and deliver little.
Remote monitoring in India
India has no dedicated public or insurance code for RPM, so programmes are funded in other ways:
- Bundled post-discharge packages. Hospitals offer 30 or 60 day monitoring as a paid add-on at discharge, especially after cardiac procedures and major surgery.
- Chronic care subscriptions. Monthly plans for diabetes, hypertension or heart failure, combined with teleconsultations.
- Corporate and insurer wellness programmes. Some insurers and employers fund monitoring for high-risk members.
- Readmission reduction as the business case. For hospitals, fewer emergency readmissions frees beds and improves outcomes and reputation.
Remote consultations sit under the Telemedicine Practice Guidelines issued in 2020. Monitoring data is personal health data under the DPDP Act 2023 and DPDP Rules 2025, so consent, purpose limitation and secure storage are required; see our DPDP Act checklist for hospitals.
India also has a strong home-grown monitoring industry. Contactless under-mattress monitors, for example, are already used in a number of Indian hospital wards, and the same kind of device can be used at home during recovery. And WhatsApp, which most Indian patients already use, is a practical channel for reminders, symptom check-ins and escalation messages; see our guide to WhatsApp automation for hospitals.
Choosing devices and a platform
Device choice is less important than reliability and ease of use, but a few practical points save trouble later:
- Validated devices. Use blood pressure monitors, oximeters and scales with recognised clinical validation, not consumer gadgets of unknown accuracy.
- Connectivity that suits your patients. Bluetooth-to-smartphone works for patients comfortable with apps. For elderly patients, devices with built-in cellular connectivity or a small home gateway avoid pairing problems.
- Simple patient experience. One app, large buttons, reminders in the patient's language, and a clear "call us" option.
- Clinician worklist, not a raw feed. The platform should sort patients by urgency, show trends, and record who acted on each alert and when.
- Open data access. Insist on an API or standards-based export so readings can flow into your HMS. Avoid platforms that lock data inside their portal.
- Device logistics. Plan how devices are issued, cleaned, returned and tracked. Lost devices quietly erode the budget.
Staffing the programme
A small programme for 50 to 100 active patients usually needs:
- An RPM nurse coordinator per shift to review worklists and call patients.
- A named doctor per specialty for escalation and medicine changes.
- A device technician or trained coordinator to set up devices before discharge.
- Clear hours. Many programmes review readings during the day and give patients emergency instructions for nights, unless they run a 24/7 hub.
How to start in 90 days
- Pick one condition. Heart failure after admission is the best-evidenced choice.
- Write the protocol. Eligibility, readings, frequency, thresholds, actions, response times and programme length.
- Choose devices and a platform. Validated devices, a simple patient app or cellular gateway, and a clinician worklist.
- Integrate with the HMS. Readings and notes go into the patient record; enrolment is triggered at discharge.
- Train ward staff. Enrolment and device setup must happen before the patient leaves.
- Launch with 20 to 30 patients. Review alert volume weekly and tune thresholds.
- Measure outcomes. 30-day readmissions, emergency visits, alert response times, adherence and patient satisfaction, compared with similar patients not enrolled.
| Metric | Target direction |
|---|---|
| Patients transmitting at least 4 days a week | Higher |
| Median alert response time | Lower |
| 30-day readmissions vs comparison group | Lower |
| Alerts per patient per week | Stable, not rising |
| Patient drop-out rate | Lower |
Common mistakes
- Enrolling everyone. Low-risk patients add workload without benefit.
- Data with no owner. If no named nurse reviews readings daily, the programme is unsafe.
- Vendor portal only. Doctors will not log into another system during OPD.
- No end date. Define when patients graduate, or the caseload grows without limit.
- Ignoring caregivers. Many elderly patients need a family member to take readings.
Where Algon fits
At Algon, we connect monitoring devices and platforms to the hospital management system, build clinician worklists and alert rules, and set up patient messaging through patient engagement channels. Where a hospital already has a monitoring vendor, healthcare integration work brings the readings into the record.
Conclusion
Remote patient monitoring after discharge works when it is a structured clinical service: carefully selected patients, a small set of meaningful readings, tuned alert rules, a named team that acts every day, and data that lands in the patient record. The US has made billing more flexible in 2026 while regulators watch for programmes that bill without delivering. In India, the model is funded through packages and subscriptions, and the business case rests on fewer readmissions. Start with one condition, measure honestly, and grow from there.
Frequently asked questions
What is remote patient monitoring after discharge?
It is a programme where patients go home with connected devices such as a blood pressure cuff, scale or pulse oximeter, send readings daily, and a nurse-led team acts on readings that cross agreed limits to prevent deterioration and readmission.
Does remote patient monitoring reduce readmissions?
Structured programmes can help. The TIM-HF2 trial of 1,571 heart failure patients found fewer days lost to unplanned cardiovascular admissions or death (17.8 vs 24.2 days a year), mainly through lower mortality. Results depend on daily review and clear actions.
What are the new RPM CPT codes for 2026?
The CY 2026 Medicare Physician Fee Schedule added 99445 for device supply with 2 to 15 days of data in 30 days, and 99470 for the first 10 minutes of monthly treatment management. Check CMS rates for your locality.
Is remote patient monitoring reimbursed in India?
There is no dedicated RPM code in India. Hospitals usually fund it through post-discharge packages, chronic care subscriptions, corporate or insurer wellness programmes, or as part of their readmission reduction strategy.
Which patients should be enrolled in RPM?
Patients with conditions where vital signs change before deterioration and where the team can act, such as heart failure, COPD, early post-surgical recovery, and hypertension or diabetes after an admission.
How many staff does an RPM programme need?
For 50 to 100 active patients, typically one nurse coordinator per shift reviewing worklists, a named doctor per specialty for escalation, and trained staff to set up devices before discharge.
