Audit-Ready Remote Patient Monitoring Software Development

Remote monitoring that clinicians trust, patients keep using and auditors can follow.

The program launched with a box of blood pressure cuffs and a vendor dashboard. Within a quarter, readings were arriving faster than anyone could read them, patients had stopped transmitting without anyone noticing, nurses were typing the same values into the chart by hand, and finance asked how many claims could be defended if a payer questioned them. Each tool did what it was built to do. Nobody had designed the program around who responds, who goes quiet and what has to be on record.

Our remote patient monitoring software development services cover the full remote patient monitoring platform for health systems, home health and post-acute operators, and the digital health and device companies that sell to them. We build device and data ingestion, alert rules and triage queues, patient apps and onboarding, clinician workspaces connected to the EHR, documentation and billing rules, and the analytics on top. Where AI helps, for example by drafting a note, a clinician approves it before it enters the record.

Most remote patient monitoring software development engagements begin with a program audit that looks at which patients and conditions are in scope, which devices and systems already exist and which billing and regulatory rules apply, so you see the risks before you commit to a build. Tell us your patient population, your devices and your EHR, and we will return a written scope with the integration and billing questions that will set your timeline.

‍

Scope your project

Tell us what you need and where it has to run, and we will come back with the right approach and the risks before the estimate.

No obligation. Your details stay private.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
570,000+

Medicare enrollees received remote patient monitoring in 2022, up from about 55,000 in 2019, according to the HHS Office of Inspector General. Monitoring is no longer a pilot. It is a billed benefit under review.

43%

of those enrollees did not receive all three components of the service, which are education and device setup, the device itself and treatment management, according to the same Inspector General report. That is the gap a platform that records each step is built to close.

700+

projects delivered for more than 140 clients, with healthcare as the focus of our work.

What remote patient monitoring software includes, and where a monitoring program stops

Remote patient monitoring software development is the design and build of the platform that collects health readings from patients outside the clinic, routes them to the right clinician, and keeps a record of each action needed for care and for billing.

The terms get blurred. Remote patient monitoring software is the system itself: device connections, a patient app, alert rules, a clinician worklist and documentation. An RPM program is the clinical service run on top of it, with enrolled patients, protocols, staff and a payer. A monitoring device is one component, and some are regulated as medical devices. Telemedicine is the live visit a reading may trigger. A custom build covers the software that ties these together, with the integration, alerting and documentation work that makes them usable as one workflow.

The test for a leader is whether the right reading reaches the right clinician in time, and whether the record shows what happened next. A vendor dashboard will plot a blood pressure trend. It will not tell you who owns an alert, which patient stopped transmitting, or whether the order, setup and clinician time behind a claim were captured. Work that reaches beyond monitoring, into clinical records and the wider platform underneath, sits with our healthcare software development practice. Buyers searching for remote patient monitoring solutions or RPM software development are usually asking for this software layer.

Why remote patient monitoring software gets launched but overwhelms staff, loses patients and invites audit

These are the six failure points clinical and operations leaders describe once remote patient monitoring software moves from a pilot to a full patient population. None of them is fixed by a better chart.

  • Nobody owns the alert. Readings arrive around the clock, thresholds are set once and never tuned, and nurses learn to dismiss what they cannot act on. When a real deterioration is buried in the noise, the program has failed at the one job it exists to do. Deciding who answers which alert, and by when, is a design task and not a settings screen.
  • Patients stop transmitting. Cuffs stay in their boxes, batteries die, Bluetooth pairing breaks after a phone upgrade, and a patient who struggles with the app simply stops. A quiet patient is a clinical risk and a revenue gap at once, and most programs notice only weeks later.
  • Device logistics break before the software does. Kits have to be shipped, paired, replaced and returned, and every step needs an owner. Without a designed workflow, nursing staff end up doing it by phone. Long term condition programs feel this most, which is where our disease management software work begins.
  • Documentation gaps invite audit. A claim needs an order, a record of education and device setup, enough days of readings and documented clinician time. When those facts sit in four systems, nobody can assemble them for a reviewer, and the program carries the exposure whether or not the care was good.
  • Billing rules keep moving. New billing codes took effect in 2026 for shorter periods of device data and shorter amounts of management time, and further changes are under proposal for 2027. A platform that hard codes today's rules becomes a rework project every year.
  • Packaged vendors lock the devices, the data and the price. Many packaged platforms work only with the devices they sell, charge per patient per month and make it hard to take your readings elsewhere. That suits a small pilot. It becomes expensive and restrictive as the program grows.
Clinical and administrative staff discussing hospital call handling and patient communication workflows (placeholder image, to be replaced)

The systems our remote patient monitoring software development services build and integrate

Six kinds of system, built to fit the EHR, device and billing setup you already run rather than replacing it. Some organizations need all six over time. Most start with the part that loses the most patients or carries the most audit risk.

Around those six sit the modules specific programs ask for: multilingual patient content, caregiver access, hospital at home workflows, and cohort programs for conditions such as heart failure, hypertension and diabetes. Each one reads from the same patient record and the same alert rules.

What drives the cost of remote patient monitoring software development?

Five things move the number: how many device types and patients the platform supports, how many EHR and billing integrations it needs, how deep the alert logic goes, how much of the billing documentation it automates, and which regulatory scope applies. Integration is the piece leaders most often underprice, so we cost it as a separate line. Start with a rough range from the calculator, then walk us through your program and we will turn that range into a real estimate.

‍

How we find where your monitoring program loses patients and alerts before we build

Before any remote patient monitoring software development begins, we run a program audit that answers four questions, in order, because each one changes the build rather than the backlog. Most of the answers come from your own enrollment and alert data and from sitting with a nurse lead and a billing lead through a working week.

What does AI change in remote patient monitoring software development, and what must it never do?

Less than the marketing suggests, and more than a skeptic expects. The clearest wins are noise and time. AI can group duplicate alerts from the same patient, score a trend so a nurse sees the patients drifting before they cross a threshold, flag a drop in adherence, and draft a visit summary for a clinician to edit and approve. The second win is design time: drafting test scenarios and documentation for your team to review.

What AI should not do in monitoring is decide. It does not diagnose, change a medication, set or quietly change an alert threshold, or close an alert. Anything that reaches a patient or the chart is approved by a clinician first. Where AI runs in the live product, we deploy it inside your compliance boundary and keep it as an assistant to the worklist. For the wider question of where AI belongs in your organization, our healthcare AI consulting team starts from your data and your governance.

The same discipline applies to how we build. Three commitments are written into every engagement. We stay model neutral, choosing the right tool for each task rather than tying your platform to one AI vendor. A named engineer reviews every AI assisted change before it merges and answers for it as for code they wrote themselves. And we never train models on your code or your data. During development, real patient data stays away from any model, and the readings AI tests against are synthetic.

The tooling behind a Cabot remote patient monitoring software development engagement

A monitoring platform succeeds or fails on its connections, and RPM device integration is the first of them, so we pick the stack around your EHR, your devices and your hosting rather than around our preferences. Where your IT team has standardized on a cloud or a language, we build in it. Exchange standards, including SMART on FHIR, shape the integration layer. The table below shows, stage by stage, what AI handles, what a person keeps and which tools are involved.

What we work in:

Apps and device connectivity

React Native
Swift
Kotlin
Bluetooth LE
MQTT
Apple HealthKit

Integration and standards

FHIR R4
HL7 v2
SMART on FHIR
OAuth 2.0 and OpenID Connect
REST APIs
Webhooks

Platform, security and quality

AWS
Azure
Terraform
Playwright
SonarQube
OpenTelemetry

What AI does at each stage of remote patient monitoring software development, and what it never does

Every stage produces something you can review, and every stage has a person who signs it off. AI output does not enter your codebase, your data or your patients' messages until someone named has accepted it.

Build stage What AI does What stays human Tools used
Program audit and scoping Summarizes enrollment exports, alert logs and interview notes into the decisions they contain, and drafts acceptance criteria from a written intent. Sitting with nurse, billing and IT leads, choosing the patients and conditions in scope, setting the alert protocol, and committing to scope. Claude, Jira AI
Device, integration and app build Drafts device payload mappings, FHIR resource transformations and repetitive code, following patterns already in your repository. The data model, the integration design, and every decision about which readings cross which boundary. GitHub Copilot, Claude Code, Cursor
Code review Flags a first round of problems such as unhandled errors, gaps in input validation and common security mistakes. Approving the merge. One named engineer accepts each change and remains answerable for it. GitHub Copilot, SonarQube
Test Writes test cases against synthetic patients and devices, including dropped connections, duplicate readings, clock drift, out of range values and replaced phones. Choosing what must be tested, which failure would harm a patient, and whether the suite proves it. Playwright, GitHub Copilot
Release and operate Drafts release notes and groups production errors, such as failed device syncs or undelivered alerts, by likely cause. The go or no go call, the order clinics and cohorts go live in, and how alert data shapes the next increment. GitHub Actions, Grafana

How Cabot remote patient monitoring software development differs from a packaged monitoring platform

Packaged platforms work well when your program looks like the one the product was designed around. In a build versus buy remote patient monitoring decision, these six dimensions are where the difference shows when it does not.

Dimension Packaged platform Cabot
Which devices you can use Often works with the devices the vendor sells or has certified, so a new device type means a vendor project or a separate kit. Device agnostic ingestion, so you choose devices by clinical need and can add a type without replacing the platform.
How deeply it connects to your EHR Supports the integrations on its list, often as a summary view or an export, so staff still chart twice. Integration is scoped against what your EHR exposes, and the first release returns readings and follow up work to the patient's chart.
Who owns the alert logic Ships a rules model with settings, and changes beyond them depend on the vendor's roadmap. Alert rules and escalation ladders are designed with your clinicians and held in configuration your team can review and change.
How billing rule changes are handled The vendor updates the product on its own schedule, and your documentation follows whatever the release supports. Billing rules are held as configuration, so a payer or code change becomes a reviewed update and not a rebuild.
What it costs as the program grows Often priced per patient per month, so cost rises with every patient and clinic you add. A build cost you can plan, with run costs that follow your infrastructure rather than your census.
Who owns the data and the roadmap The vendor holds the readings and sets the roadmap, and exporting your own data can become a project. You own the code, the data and the consent record, and the roadmap follows your own measures.

Who commissions remote patient monitoring software development, and where each one breaks

Three kinds of organization bring us this work. Each breaks in a different place, so here is what we understand about each.

‍

How patient readings, access and billing records stay protected and compliant

We treat security as a condition of finishing a feature, not a review scheduled at the end. Each user sees only the patients assigned to them, sign-in runs through single sign-on with multi-factor authentication, patient data is encrypted in transit and at rest, credentials live in a managed vault instead of in configuration files, and every access to a patient record is logged, starting with the first working version. Device credentials are issued per device and can be revoked, so a lost cuff does not become an open door.

Which rules apply depends on who runs the program and what the software does. A provider or plan using the platform to deliver care is generally a HIPAA covered entity, and we build under a business associate agreement. Whether a component is regulated as a medical device depends on its intended use, and one that qualifies brings FDA expectations, including the cybersecurity requirements for cyber devices in section 524B of the Federal Food, Drug, and Cosmetic Act. Billing follows CMS remote monitoring rules, which changed in 2026, and state telehealth and consent rules differ by state. Your counsel and regulatory advisers confirm what applies, and we keep the evidence trail that review needs. Our compliance practice covers the wider program.

Role-based access control
SSO and MFA
Encryption in transit and at rest
Audit log of every record access
Per-device credentials
Consent captured per patient

What happens, stage by stage, in remote patient monitoring software development with Cabot

The work runs in three stages, and each one closes with a choice that is yours to make. Many organizations commission the program audit on its own first, which lets them see how we work before they sign up for a build.

‍

Who delivers your remote patient monitoring software development, and what each person answers for

Every role has a clear owner from day one. The tech lead answers for the architecture, the data model and the decision to merge each change. An integration engineer looks after every connection into and out of your EHR, device data sources and billing systems. A solution architect for clinical workflow answers for the alert rules and escalation design, agreed with your clinical leaders. Engineers carry their own pieces of work from start to finish. The quality lead answers for the test suite and for what it demonstrates. The delivery lead runs the schedule and keeps clinical and operations leaders informed between demos. For any decision, you know the person responsible and how to reach them.

Our strength is concentrated in four areas. The first is device and data ingestion, where these programs most often lose credibility. The second is EHR integration through FHIR and HL7, so nobody keys a reading twice. The third is alert design and clinician worklists that hold up under volume. The fourth is documentation and billing rules that can change without a rebuild. Where a packaged product would serve you better than a build, we say so.

Your team and ours work inside an overlap window agreed in writing at the start, and anything that needs your decision is saved for it. Design decisions live in your repository as short written records, so a change of engineer does not cost you weeks. If the scope grows, we add engineers to the same team rather than standing up a second one.

Why health system leaders choose Cabot for audit-ready remote patient monitoring software development

A monitoring program only pays for itself if the right alert reaches the right clinician and the record stands up to review. These are the reasons leaders give for choosing Cabot as their remote patient monitoring software development company.

Where to go next, depending on your situation

This page covers the monitoring platform and the connections around it. If one of these describes you better, start there instead.

‍

Our Clients

Client Success Stories

See all Cabot case studies

Questions health system and digital health leaders ask about remote patient monitoring software development

  1. What do remote patient monitoring solutions include beyond the devices?
    A device kit is the visible part, and it is the smallest part of the work. A working solution also needs connectivity and pairing support, a patient app or a phone path, alert rules and a clinician worklist, a connection to the EHR, documentation for billing and the staff and protocol that respond. Software ties those parts together, and where it is missing, nurses fill the gaps by hand.
    ‍
  2. How much does remote patient monitoring software development cost?
    Price follows scope, meaning the number of device types, the size of the patient population, the integrations required and the depth of the alert logic and documentation. A per patient fee tells you little about what a build will cost. Our cost calculator gives you a first range in a few minutes, and we then price it against your program before anything is committed.
    ‍
  3. How long does remote patient monitoring software development take?
    The first patient group is the fastest part to reach. The full timeline is set less by the build than by access: which EHR interfaces exist, who owns the test environment, and how long device selection and clinical and compliance review take. We establish all three during the audit, so the timeline you receive reflects them rather than a generic estimate.
    ‍
  4. Can the platform connect to our devices and our EHR?
    Yes. We connect to Bluetooth and cellular devices through the vendors' published interfaces or gateways, and to EHRs through FHIR R4, HL7 v2 and SMART on FHIR where the vendor supports them. What each system exposes decides the work, so we confirm it during the audit and plan for disconnected devices from the start.
    ‍
  5. How does billing documentation work after the 2026 remote patient monitoring code changes?
    Medicare added two codes for 2026: 99445 for device supply over 2 to 15 days of readings in a 30 day period, and 99470 for the first 10 minutes of treatment management. They sit alongside 99453, 99454, 99457 and 99458. Whatever the code, a claim needs an order, setup, readings and clinician time on record, so we capture each as it happens and hold the rules as configuration. Rules change, so check the current CMS rule with your compliance lead before relying on any code or threshold.
    ‍
  6. Does remote patient monitoring software need FDA clearance?
    Not always. It depends on intended use. Software that only transmits, stores or displays readings is often treated differently from software that analyzes readings to diagnose or to drive treatment, and the answer can change when a feature is added. The devices that take the readings are usually cleared on their own. We scope this early, flag which components may be regulated and design cybersecurity to the expectations that apply. Your regulatory adviser makes the determination.
    ‍
  7. Should we choose custom remote patient monitoring software development or a packaged platform?
    For remote patient monitoring software development, buy when a packaged platform fits your devices, EHR and billing setup with light configuration, because it will be faster and cheaper. Build or extend when your devices, integrations or alert logic fall outside what products support, or when per patient fees will grow faster than your budget and you need to own the data and the roadmap. We tell you which applies after the audit, including when the answer is to buy.
    ‍
  8. Can AI be used in remote patient monitoring software, and what must a clinician still approve?
    Yes, for sorting and drafting, never for deciding. AI can group duplicate alerts, score a trend and draft a visit summary. A clinician sees the reason behind any flag and can override it, and AI never changes a threshold or closes an alert. We never train models on your data, and we stay model neutral.