{"id":23469,"date":"2026-06-20T10:25:00","date_gmt":"2026-06-20T10:25:00","guid":{"rendered":"https:\/\/engineerbabu.com\/blog\/?p=23469"},"modified":"2026-06-19T10:40:48","modified_gmt":"2026-06-19T10:40:48","slug":"build-a-remote-patient-monitoring-platform","status":"publish","type":"post","link":"https:\/\/engineerbabu.com\/blog\/build-a-remote-patient-monitoring-platform\/","title":{"rendered":"How to Build a Remote Patient Monitoring Platform – IoT Devices, CMS Billing, Alert Engine, HIPAA Architecture 2026"},"content":{"rendered":"

Remote patient monitoring is the fastest-growing segment in digital health with a sustainable CMS reimbursement model that does not depend on venture capital. <\/span>EngineerBabu<\/span><\/a> built Somnoware, the remote monitoring platform for ResMed’s sleep therapy device network, subsequently acquired by ResMed<\/a>. We understand production-grade medical IoT at scale.<\/span><\/p>\n

2026 RPM billing codes:<\/b><\/p>\n\n\n\n\n\n\n\n\n\n
CPT Code<\/b><\/td>\nWhat It Covers<\/b><\/td>\n2026 Rate<\/b><\/td>\n<\/tr>\n
99453<\/span><\/td>\nDevice setup + patient education<\/span><\/td>\n~$22<\/span><\/td>\n<\/tr>\n
99454<\/span><\/td>\nDevice supply + 16+ days transmission<\/span><\/td>\n~$52\/month<\/span><\/td>\n<\/tr>\n
99445<\/span><\/td>\nDevice supply + 2\u201315 days transmission (2026 new)<\/span><\/td>\n~$26\/month<\/span><\/td>\n<\/tr>\n
99457<\/span><\/td>\nFirst 20 minutes clinical management<\/span><\/td>\n~$52\/month<\/span><\/td>\n<\/tr>\n
99470<\/span><\/td>\nFirst 10 minutes clinical management (2026 new)<\/span><\/td>\n~$26\/month<\/span><\/td>\n<\/tr>\n
99458<\/span><\/td>\nAdditional 20 minutes clinical management<\/span><\/td>\n~$42\/month<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\"\"<\/p>\n

Module 1 – FDA-Cleared Device Integration<\/b><\/h2>\n

RPM devices must be FDA-cleared. Consumer-grade fitness trackers do not qualify.<\/span><\/p>\n

Device categories and integration methods:<\/b><\/p>\n\n\n\n\n\n\n\n\n\n
Device<\/b><\/td>\nCommon Brands<\/b><\/td>\nIntegration<\/b><\/td>\n<\/tr>\n
Blood pressure monitors<\/span><\/td>\nOmron, Withings, A&D Medical<\/span><\/td>\nBluetooth LE + manufacturer SDK<\/span><\/td>\n<\/tr>\n
Continuous glucose monitors<\/span><\/td>\nDexcom G7, FreeStyle Libre 3<\/span><\/td>\nBluetooth LE + Dexcom\/Abbott API<\/span><\/td>\n<\/tr>\n
Weight scales<\/span><\/td>\nWithings, iHealth<\/span><\/td>\nWiFi + manufacturer cloud API<\/span><\/td>\n<\/tr>\n
Pulse oximeters<\/span><\/td>\nNonin, Masimo<\/span><\/td>\nBluetooth LE + SDK<\/span><\/td>\n<\/tr>\n
ECG patches<\/span><\/td>\niRhythm Zio, AliveCor<\/span><\/td>\nCellular + cloud API<\/span><\/td>\n<\/tr>\n
Spirometers<\/span><\/td>\nNuvoAir, Smart Respiratory<\/span><\/td>\nBluetooth LE + SDK<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The device abstraction layer:<\/b><\/p>\n

A standardised internal interface normalises data from every device regardless of manufacturer format. Adding a new device requires implementing one new adapter not modifying the core platform.<\/span><\/p>\n

Data model per reading:<\/b><\/p>\n\n\n\n\n\n\n\n\n\n\n
Field<\/b><\/td>\nNotes<\/b><\/td>\n<\/tr>\n
patient_id<\/span><\/td>\nPlatform patient identifier<\/span><\/td>\n<\/tr>\n
device_id<\/span><\/td>\nSpecific physical device (serial number)<\/span><\/td>\n<\/tr>\n
measurement_type<\/span><\/td>\nBlood pressure \/ glucose \/ weight \/ SpO2<\/span><\/td>\n<\/tr>\n
value(s)<\/span><\/td>\nSystolic + diastolic for BP, mg\/dL for glucose<\/span><\/td>\n<\/tr>\n
device_timestamp<\/span><\/td>\nUTC \u2014 device-reported<\/span><\/td>\n<\/tr>\n
transmission_timestamp<\/span><\/td>\nWhen reading reached the platform server<\/span><\/td>\n<\/tr>\n
quality_flag<\/span><\/td>\nManufacturer-reported quality indicator<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The timestamp distinction matters for billing, CMS counts days where data was transmitted, not measured. Both timestamps must be recorded.<\/span><\/p>\n

Module 2 – Real-Time Vital Signs Streaming and Alert Engine<\/b><\/h2>\n

The data pipeline:<\/b><\/p>\n

Device \u2192 Bluetooth \u2192 patient smartphone \u2192 device manufacturer cloud \u2192 <\/span>platform API<\/span><\/a> \u2192 time-series database \u2192 alert evaluation<\/span><\/p>\n

Time-series database choice:<\/b><\/p>\n\n\n\n\n\n\n
Option<\/b><\/td>\nWhen to Use<\/b><\/td>\n<\/tr>\n
PostgreSQL (TimescaleDB)<\/span><\/td>\n< 50,000 patients, simplicity preferred<\/span><\/td>\n<\/tr>\n
InfluxDB<\/span><\/td>\n50,000+ patients, high-frequency readings<\/span><\/td>\n<\/tr>\n
Amazon Timestream<\/span><\/td>\nAWS-native, managed, scales automatically<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Alert evaluation, every incoming reading is evaluated:<\/b><\/p>\n\n\n\n\n\n\n\n
Alert Type<\/b><\/td>\nExample<\/b><\/td>\nSeverity<\/b><\/td>\n<\/tr>\n
Absolute threshold<\/span><\/td>\nSystolic BP > 180 mmHg<\/span><\/td>\n\ud83d\udd34 Critical<\/span><\/td>\n<\/tr>\n
Trend alert<\/span><\/td>\nBP rising > 15 mmHg over 3 consecutive readings<\/span><\/td>\n\ud83d\udfe1 Warning<\/span><\/td>\n<\/tr>\n
Missed reading<\/span><\/td>\nNo reading in 24 hours<\/span><\/td>\n\ud83d\udfe1 Warning<\/span><\/td>\n<\/tr>\n
Device disconnection<\/span><\/td>\nDevice not synced in 48 hours<\/span><\/td>\n\u2139\ufe0f Info<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Alert fatigue prevention: four mechanisms:<\/b><\/p>\n

    \n
  1. Patient-specific thresholds:<\/b> A systolic of 160 is a crisis for a 35-year-old, normal for an 82-year-old. Each patient gets provider-set thresholds.<\/span><\/li>\n
  2. Alert suppression windows:<\/b> Expected post-meal glucose spikes do not generate alerts.<\/span><\/li>\n
  3. ML anomaly scoring:<\/b> Deviation from the patient’s personal baseline, not population averages.<\/span><\/li>\n
  4. Alert deduplication:<\/b> One alert for a sustained abnormal period, not one per reading.<\/span><\/li>\n<\/ol>\n

    \"\"<\/p>\n

    Module 3 – CMS Billing Compliance Automation<\/b><\/h2>\n

    The compliance tracking engine:<\/b><\/p>\n\n\n\n\n\n\n\n
    CPT Code<\/b><\/td>\nRequirement<\/b><\/td>\nPlatform Tracking<\/b><\/td>\n<\/tr>\n
    99445<\/span><\/td>\n2\u201315 transmission days<\/span><\/td>\nCount distinct calendar days with transmission<\/span><\/td>\n<\/tr>\n
    99454<\/span><\/td>\n16+ transmission days<\/span><\/td>\nSame count, determines 99445 vs 99454<\/span><\/td>\n<\/tr>\n
    99457<\/span><\/td>\n20 minutes clinical management + patient contact<\/span><\/td>\nTime-stamped log of interactions<\/span><\/td>\n<\/tr>\n
    99470<\/span><\/td>\n10 minutes clinical management<\/span><\/td>\nSame, determines 99470 vs 99457<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Mid-month compliance alerts (critical feature):<\/b><\/p>\n

    During the month not at month-end, the platform surfaces compliance gaps:<\/span><\/p>\n\n\n\n\n\n\n
    Alert<\/b><\/td>\nTiming<\/b><\/td>\nAction<\/b><\/td>\n<\/tr>\n
    Patient approaching 16-day threshold<\/span><\/td>\nWhen at 12 days<\/span><\/td>\nProvider prompts patient to take readings<\/span><\/td>\n<\/tr>\n
    Clinical time short of 20-minute threshold<\/span><\/td>\nWith 5 days left in month<\/span><\/td>\nProvider reviews and adds documented interaction<\/span><\/td>\n<\/tr>\n
    Patient not responsive<\/span><\/td>\n72 hours without reading<\/span><\/td>\nOutreach call from care coordinator<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    The billing automation workflow:<\/b><\/p>\n

    At month end, the platform automatically:<\/span><\/p>\n

      \n
    1. Calculates each patient’s transmission day count<\/span><\/li>\n
    2. Determines correct device supply code (99445 vs 99454)<\/span><\/li>\n
    3. Sums clinical management time per provider per patient<\/span><\/li>\n
    4. Determines correct clinical time code<\/span><\/li>\n
    5. Generates 837P claim files<\/span><\/li>\n
    6. Submits to clearinghouse<\/span><\/li>\n
    7. Tracks ERA responses and posts payments<\/span><\/li>\n<\/ol>\n

      Module 4 – Patient App and Engagement<\/b><\/h2>\n

      The patient <\/b>mobile app<\/b><\/a> (iOS + Android, Flutter):<\/b><\/p>\n\n\n\n\n\n\n\n\n
      Feature<\/b><\/td>\nDetails<\/b><\/td>\n<\/tr>\n
      Reading reminders<\/span><\/td>\nDaily notification at patient-selected time<\/span><\/td>\n<\/tr>\n
      Trend visualisation<\/span><\/td>\n“Your blood pressure over the last 30 days”<\/span><\/td>\n<\/tr>\n
      Goal tracking<\/span><\/td>\nProvider-set targets with patient progress<\/span><\/td>\n<\/tr>\n
      Secure messaging<\/span><\/td>\nHIPAA-compliant messaging to care coordinator<\/span><\/td>\n<\/tr>\n
      Education content<\/span><\/td>\nCondition-specific educational materials<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      The engagement cadence:<\/b><\/p>\n\n\n\n\n\n\n\n\n
      Day<\/b><\/td>\nAction<\/b><\/td>\n<\/tr>\n
      Enrolment<\/span><\/td>\nWelcome + device setup guide<\/span><\/td>\n<\/tr>\n
      Day 3<\/span><\/td>\nCheck-in: “How is the device working?”<\/span><\/td>\n<\/tr>\n
      Day 7<\/span><\/td>\nFirst week summary<\/span><\/td>\n<\/tr>\n
      Day 30<\/span><\/td>\nMonthly summary with trend comparison<\/span><\/td>\n<\/tr>\n
      No reading 24h<\/span><\/td>\nAutomated reminder<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      \"\"<\/p>\n

      Module 5 – Provider Dashboard and Care Coordinator Workflow<\/b><\/h2>\n

      The provider dashboard:<\/b><\/p>\n\n\n\n\n\n\n\n
      View<\/b><\/td>\nContents<\/b><\/td>\n<\/tr>\n
      Patient panel<\/span><\/td>\nAll RPM patients, current readings, alert status, compliance<\/span><\/td>\n<\/tr>\n
      Alert queue<\/span><\/td>\nPrioritised alerts requiring clinical review<\/span><\/td>\n<\/tr>\n
      Compliance tracker<\/span><\/td>\nPer-patient transmission days and clinical time<\/span><\/td>\n<\/tr>\n
      Month-end billing preview<\/span><\/td>\nProjected claims before month closes<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      The care coordinator workflow:<\/b><\/p>\n\n\n\n\n\n\n\n
      Trigger<\/b><\/td>\nAction<\/b><\/td>\n<\/tr>\n
      Critical alert<\/span><\/td>\nImmediate phone call to patient<\/span><\/td>\n<\/tr>\n
      Warning alert<\/span><\/td>\nSecure message within 4 hours<\/span><\/td>\n<\/tr>\n
      Low compliance<\/span><\/td>\nMotivational outreach and troubleshooting<\/span><\/td>\n<\/tr>\n
      Patient missed appointment<\/span><\/td>\nReschedule and document<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      Cost to Build a Remote Patient Monitoring Platform<\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
      Module<\/b><\/td>\nCost Range (USD)<\/b><\/td>\nNotes<\/b><\/td>\n<\/tr>\n
      Device integration layer (10 device types)<\/span><\/td>\n$10K \u2013 $20K<\/span><\/td>\n~$1K\u2013$2K per device adapter<\/span><\/td>\n<\/tr>\n
      Time-series database + data pipeline<\/span><\/td>\n$6K \u2013 $12K<\/span><\/td>\n<\/td>\n<\/tr>\n
      Real-time alert evaluation engine<\/span><\/td>\n$8K \u2013 $15K<\/span><\/td>\n<\/td>\n<\/tr>\n
      Alert fatigue prevention (ML baseline)<\/span><\/td>\n$8K \u2013 $15K<\/span><\/td>\n<\/td>\n<\/tr>\n
      CMS billing compliance engine<\/span><\/td>\n$10K \u2013 $18K<\/span><\/td>\nAll 2026 CPT codes<\/span><\/td>\n<\/tr>\n
      Claims generation + clearinghouse<\/span><\/td>\n$6K \u2013 $12K<\/span><\/td>\n837P EDI<\/span><\/td>\n<\/tr>\n
      Patient app (iOS + Android)<\/span><\/td>\n$10K \u2013 $18K<\/span><\/td>\nFlutter<\/span><\/td>\n<\/tr>\n
      Provider dashboard + care coordinator<\/span><\/td>\n$8K \u2013 $15K<\/span><\/td>\n<\/td>\n<\/tr>\n
      EHR integration (FHIR R4)<\/span><\/a><\/td>\n$6K \u2013 $12K<\/span><\/td>\n<\/td>\n<\/tr>\n
      AWS HIPAA + IoT security + VAPT<\/span><\/td>\n$8K \u2013 $15K<\/span><\/td>\n<\/td>\n<\/tr>\n
      Total<\/b><\/td>\n$80K \u2013 $152K<\/b><\/td>\nFull RPM platform<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      EngineerBabu built Somnoware, the <\/span><\/i>RPM platform<\/span><\/i><\/a> for ResMed’s sleep therapy device network, acquired by ResMed. Contact: <\/span><\/i>mayank@engineerbabu.com<\/span><\/i><\/a><\/p>\n

      Frequently Asked Questions<\/b><\/h2>\n
        \n
      • \n

        What is the 16-day rule in RPM billing and how does the platform track it?<\/b><\/h3>\n<\/li>\n<\/ul>\n

        CPT 99454 requires a minimum of 16 distinct calendar days of data transmission in a 30-day billing period. The 2026 update added CPT 99445 for 2 to 15 transmission days. The platform tracks transmission days automatically, counting any calendar day where at least one reading was received. At month-end, the platform selects the correct code based on the actual count. Mid-month alerts notify the care team when a patient is on track for 99445 instead of 99454, enabling proactive outreach to increase transmission frequency before the billing window closes.<\/span><\/p>\n

          \n
        • \n

          How did EngineerBabu’s Somnoware build inform this RPM architecture?<\/b><\/h3>\n<\/li>\n<\/ul>\n

          Somnoware was built for ResMed’s connected sleep therapy devices, CPAP and BiPAP machines that transmit usage data nightly. The core challenges were identical to a general RPM platform: device protocol normalisation across multiple device generations, alert engine design that surfaces clinically meaningful signals without alert fatigue, compliance tracking for billing purposes, and a patient app that drives engagement with patients who have chronic conditions. The acquisition by ResMed validated the platform’s clinical and technical quality. EngineerBabu applies these lessons, specifically the device abstraction layer architecture, the alert fatigue prevention model, and the compliance billing engine to new RPM builds.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

          Remote patient monitoring is the fastest-growing segment in digital health with a sustainable CMS reimbursement model that does not depend on venture capital. EngineerBabu built Somnoware, the remote monitoring platform for ResMed’s sleep therapy device network, subsequently acquired by ResMed. We understand production-grade medical IoT at scale. 2026 RPM billing codes: CPT Code What It […]<\/p>\n","protected":false},"author":1,"featured_media":23470,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1246],"tags":[],"class_list":["post-23469","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-healthtech"],"_links":{"self":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/23469","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/comments?post=23469"}],"version-history":[{"count":1,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/23469\/revisions"}],"predecessor-version":[{"id":23476,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/23469\/revisions\/23476"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/media\/23470"}],"wp:attachment":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/media?parent=23469"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/categories?post=23469"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/tags?post=23469"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}