Home / Insights / Business Operations and Integration
Business Operations and Integration
Building a Remote Patient Monitoring System: Components, Integration and Compliance
Remote patient monitoring lets care teams track patients’ vital signs at home and intervene earlier. This guide covers the components of an RPM platform, alert design, EHR integration, US reimbursement basics, privacy and regulatory considerations, and how to roll one out.
TopicsBusiness Operations and IntegrationMobile App DevelopmentArchitecture and Modernization
Key takeaways
- RPM collects physiological data — blood pressure, glucose, weight, oxygen saturation, heart rate — from patients at home and sends it to care teams.
- A platform needs device connectivity, a secure data pipeline, patient apps, clinician dashboards, alerting and EHR integration.
- Alert design decides success: thresholds per patient, escalation rules and workload management prevent alarm fatigue.
- In the US, Medicare and other payers reimburse RPM through specific CPT codes; new codes from January 2026 cover shorter monitoring periods and management time.
- Privacy and security obligations apply, and some software functions may be regulated as medical devices.
On this page
Remote patient monitoring (RPM) has moved from pilot projects to a mainstream part of chronic care management. Patients with hypertension, diabetes, heart failure or COPD use connected devices at home; their readings reach care teams, who can spot deterioration earlier and adjust treatment without waiting for the next visit.
This guide covers what it takes to build or extend an RPM platform. It is not clinical, legal or billing advice.
Core components
| Component | Purpose | Key decisions |
|---|---|---|
| — | — | — |
| Devices | Blood pressure cuffs, glucometers, scales, pulse oximeters, wearables | Validated devices; cellular versus Bluetooth; supply and logistics |
| Connectivity | Transmits readings to the platform | Cellular hubs for low-tech users; phone apps for others |
| Data pipeline | Ingests, validates and stores readings | Time zones, duplicates, device errors, data provenance |
| Patient app or portal | Shows readings, reminders, education and messages | Accessibility, languages, low digital literacy |
| Clinician dashboard | Patient lists, trends, alerts and actions | Prioritisation, workload, documentation |
| Alerting and escalation | Notifies the right person when readings cross thresholds | Per-patient thresholds, escalation paths, hours of coverage |
| EHR integration | Sends readings and notes to the record | FHIR or vendor interfaces; avoid double entry |
| Billing and reporting | Tracks days with data and time spent for reimbursement | Accurate, auditable logs |
Most RPM projects succeed or fail on workflow design, not device technology.
Designing alerts clinicians trust
- Personalised thresholds set by the care team for each patient, rather than universal values.
- Trend-based alerts that detect gradual deterioration, not only single readings.
- Tiered escalation: care coordinator first, then nurse, then physician, with clear response times.
- Missing-data alerts when patients stop measuring.
- Workload views: dashboards that sort patients by urgency so teams handle the most important first.
- Clear patient guidance on what to do in emergencies — RPM is not an emergency service.
EHR integration
Readings and care notes should appear in the patient’s record without manual copying. FHIR Observation resources are a natural fit for vital signs; EHR vendor app frameworks can embed RPM dashboards in clinicians’ workflow. Our guide to AI in EHR systems discusses integration patterns in more detail.
US reimbursement basics
In the US, remote physiologic monitoring is billed using CPT codes covering device set-up and education, device supply with daily recordings, and clinical staff or physician management time — historically 99453, 99454, 99457 and 99458, along with 99091. The AMA’s CPT Editorial Panel approved additional codes effective January 2026 for months with 2 to 15 days of data and for 10 to 19 minutes of management time, reflecting shorter monitoring periods. Payer rules, documentation requirements and eligible devices change, so confirm current requirements with billing specialists.
The platform should record days with data, time spent by staff and the activities performed, in a form that supports audit.
Privacy, security and regulation
- Privacy: RPM data is protected health information under HIPAA for covered entities and their business associates; see our guide to HIPAA-compliant AI for data-flow principles.
- Security: encrypt data from device to platform, secure device identities, manage patient authentication and log access.
- Device regulation: monitoring devices are usually regulated medical devices; software that analyses readings to diagnose or recommend treatment may also be regulated, depending on its functions.
- Consent: obtain patient consent for monitoring and explain how data is used and who sees it.
Phased rollout
| Phase | Focus | Success measures |
|---|---|---|
| — | — | — |
| 1. Pilot | One condition, one clinic, a few dozen patients | Enrolment, adherence (days with readings), alert volume per clinician |
| 2. Workflow refinement | Thresholds, escalation, documentation, EHR integration | Response times, staff time per patient, clinician satisfaction |
| 3. Scale | More conditions and sites; logistics for devices | Clinical outcomes, admissions, patient satisfaction, sustainable workload |
Measure adherence closely: monitoring only helps if patients take readings.
Frequently asked questions
Should we build our own RPM platform?
If RPM is central to your service or you need deep integration and custom workflows, building or extending makes sense. For standard programmes, established platforms may be faster.
Which devices should we choose?
Validated, easy-to-use devices with reliable connectivity. Cellular-connected devices often improve adherence for older or less tech-savvy patients.
How do we avoid overwhelming clinicians?
Personalised thresholds, trend-based alerts, tiered escalation and dashboards that prioritise patients.
Can AI help?
Yes, for prioritising patients, detecting trends and summarising data for clinicians — with clinical oversight and attention to regulatory boundaries.
Sources and methodology
Facts in this article were checked against the sources below on 6 November 2026. Directory data (ratings, review counts, rate bands and team sizes) changes over time and is shown as published on the date accessed. Illustrative examples are labelled as such and are not quotes.
- Cozen O’Connor (Health Law): AMA CPT Editorial Panel approves new codes covering remote patient monitoring services — accessed 6 November 2026. Existing RPM codes; new codes for 2–15 days of data and 10–19 minutes of management, effective January 2026
Related reading
Continue your research
Building or extending a remote monitoring service?
Share your care model and target patients. We will help you design devices, data flows, dashboards and integrations that clinicians will use.