Hypertension monitoring
BP cuffs feeding a managed monitoring program.
Custom RPM App Development
RPM Custom App
We build the full remote patient monitoring product (a patient app for enrollment and readings, and a clinician dashboard for review and billing) wired to devices and RPM CPT from the first sprint.
HIPAA-ReadyFHIR R4RPM CPT CodesAudit Logged
Trusted by global innovators
What is an RPM custom app?
An RPM custom app is remote patient monitoring software built for your program: a patient app that pairs devices and captures daily readings, and a clinician dashboard that triages data and records billable time. Agnotic Technologies builds both halves as one system, linked to your EHR through FHIR R4 and designed around the HIPAA Security Rule.
When the two halves come from different vendors, readings, review notes and claims stop matching. The dashboard tracks device days and management time against the CPT codes in force, including 99445 and 99470 added for 2026.
What it is
One product, two experiences
Custom RPM app development means building both sides of a remote monitoring program: the patient app that captures readings and the clinician dashboard that turns them into care and billing. The value is in the fit: one shared model, with no data lost between them.
We design the patient experience for adherence and the clinician experience for throughput, wire RPM CPT billing through both, and keep everything on a FHIR R4 record that also syncs to the EHR.
Patient app + clinician dashboard architecture
See how enrollment, device readings, the clinician worklist, and RPM CPT billing share one FHIR data layer.
What goes into a custom RPM app?
Two halves of one product (patient capture and clinician workflow) with billing wired through.
Patient app & enrollment
iOS/Android app for consented enrollment, device pairing, daily readings, reminders, and education, designed for older and lower-tech patients, not just power users.
Clinician dashboard
A prioritized worklist that surfaces out-of-range and non-adherent patients first, with review documentation, messaging, and escalation built for a monitoring team's real day.
RPM CPT billing
99453 setup, 99454 for 16 or more days of device data, 99445 for 2 to 15 days, and management time under 99470, 99457 and 99458, all tracked in-product with an audit trail.
Consent, PHI & audit
Explicit consent capture, PHI encryption in transit and at rest, and immutable access logs across both apps so the whole program is HIPAA-ready and audit-defensible.
Shared FHIR data model
Readings as FHIR R4 Observation shared by the patient app, dashboard, and EHR: one canonical record instead of two systems drifting apart.
Where it runs
Who uses a custom RPM app?
Diabetes RPM
Glucometer and CGM readings with clinician review.
Cardiac & CHF programs
Weight and vitals tracking to prevent readmissions.
Post-discharge monitoring
Structured 30-day monitoring after acute care.
Health system RPM lines
Enterprise RPM across multiple chronic conditions.
RPM service companies
White-label patient and clinician apps for RPM providers.
Where RPM programs win or lose
RPM revenue depends on adherence and documented minutes. We build both the patient side that drives adherence and the clinician side that captures the time.
2-in-1
Patient app + clinician dashboard
6
RPM CPT codes tracked, including 2026 additions
2 to 15
Device days billable under CPT 99445
Compliance-First Healthcare App Development Services Backed by Global Standards
15-Minute Scoping Call01
HIPAA
Health Insurance Portability and Accountability Act
Protect PHI with privacy-first architecture, encrypted storage and transmission, strict access controls, and traceable audit logs.
02
GDPR
General Data Protection Regulation
Implement lawful consent flows, data minimization, retention controls, and secure processing for sensitive health data.
03
FHIR
Fast Healthcare Interoperability Resources
Enable standardized health data exchange across apps, care teams, and systems through standards-based FHIR APIs.
04
HL7
Health Level Seven International
Support enterprise-grade interoperability with HL7-based integrations for records, events, and clinical messaging workflows.
05
HITRUST
Health Information Trust Alliance
Align security programs to healthcare-specific control and risk management practices trusted by providers and ecosystem partners.
06
HITECH
Health Information Technology for Economic and Clinical Health Act
Design with breach notification readiness, digital record safeguards, and operational controls that support regulated care programs.
07
SaMD
FDA Software as a Medical Device
Plan software quality, traceability, and documentation pathways for products that may require SaMD review and submission.
08
MDR (EU)
Medical Device Regulation (European Union)
Prepare EU market-ready processes for risk classification, evidence tracking, and lifecycle governance under MDR expectations.
09
SAMHSA
Substance Abuse and Mental Health Services Administration
Apply confidentiality controls and consent-aware sharing models for behavioral and mental health data experiences.
Standards & billing
Which standards does an RPM app follow?
CPTFHIRX12HIPAAICD-10
Our Process
How do we ship a custom RPM app?
We build patient and clinician experiences against a shared data model so the two halves never drift.
1.
Program & workflow design
We map enrollment, the monitoring team's day, and the RPM CPT model, then design the shared FHIR data layer both apps use.
One data model
2.
Patient app build
Enrollment, device pairing, readings, reminders, and consent, designed for accessibility and adherence.
Patient-friendly
3.
Clinician dashboard build
The worklist, review documentation, time tracking, and escalation the monitoring team lives in every day.
Workflow-first
4.
Billing, EHR & go-live
CPT claim generation, EHR write-back, and a phased rollout with monitoring on thresholds and adherence.
Revenue-ready
Facts and sources
Which rules shape RPM apps?
Short facts we design around, each linked to its primary source.
Medicare's remote physiologic monitoring codes include CPT 99453, 99454, 99457 and 99458, and the CY 2026 Physician Fee Schedule added 99445 and 99470 for shorter monitoring periods and shorter management time.
Source: Federal Register, November 5, 2025 (CY 2026 Physician Fee Schedule final rule, CMS-1832-F)The HIPAA Security Rule requires administrative, physical and technical safeguards for electronic protected health information.
Source: 45 CFR Part 164 Subpart C (eCFR)A HIPAA covered entity may share protected health information with a business associate, such as a software vendor, only under a business associate agreement that commits the vendor to safeguard it.
Source: 45 CFR 164.502(e) and 164.504(e) (eCFR)FDA's guidance on device software functions focuses oversight on software that meets the definition of a medical device and could put patient safety at risk if it does not work as intended.
Source: FDA, Policy for Device Software Functions and Mobile Medical Applications (2022)
Featured case study
Read Case StudyLera Health: compliant women's health platform
Related proof of compliant delivery: for Lera Health we built a patient experience and a privacy-first data layer end to end: the same two-sided, consent-driven discipline a custom RPM product depends on.
Why Partner With Us
Book a scoping callWhy build your RPM app with Agnotic?
We build the patient and clinician sides as one product, so the program actually runs.
Compliance-first by default
Consent, PHI encryption, and audit logging across both apps from sprint one.
Billing wired through
RPM CPT thresholds and time tracking built in so the program is reimbursable, not just functional.
Two-sided product depth
Patient and clinician experiences built together against one FHIR model, no integration gap between halves.
Accessible patient design
Enrollment and daily use designed for the patients RPM actually serves, driving adherence and revenue.
Build an RPM product that patients use and clinicians run
Patient app and clinician dashboard, delivered as one system
Frequently Asked Questions
Yes. Agnotic signs a business associate agreement before any PHI is shared, and we use synthetic readings in development and test environments.
Yes. A common first scope is one condition, one device class, the clinician worklist and time tracking, with EHR write-back and more devices in later releases.
AI tools help our engineers draft code and tests, but a person reviews every change, and it passes the same automated tests and security checks as any other code, including the tests on RPM CPT billing rules. Which tools may see your code or data is agreed with you at the start.
Cost depends on device classes, EHR integration depth and white-labeling. We scope against your conditions and device mix, then share a fixed estimate after discovery.
It depends on device classes, EHR write-back and billing scope. A first release usually covers patient capture, the clinician worklist, time tracking and claims for one device class. We give you a dated plan after discovery.
Buy when a generic RPM platform fits your program and you can accept its device list and billing assumptions. Build when you need a specific patient experience, unusual device support, white-labeling, or tight EHR integration: the patient-side UX and billing accuracy are where custom pays off.
Yes. The patient app pairs with BLE and cellular devices and normalizes readings to FHIR R4 Observation. The same record writes back to your EHR as Observation and DocumentReference and drives 837P claim generation, so devices, chart and billing share one data model.
We track 99453 setup, device supply under 99454 (16 or more days) or 99445 (2 to 15 days), and management time under 99470, 99457 and 99458, with a documented interaction log. Claims go out as 837P with the right modifiers and ICD-10 linkage, and your billing team confirms current fee schedule rules.
Adherence is a design problem. We build accessible enrollment, guided device pairing, reminders, and simple daily capture aimed at the older, lower-tech patients RPM often serves, because missed readings mean lost care and lower reimbursement.
Ready to build your custom RPM product?
Tell us your conditions and device mix. We'll return a plan for the patient app, clinician dashboard, and RPM CPT billing on a shared FHIR model.
contact@agnotic.com
Partnerships
contact@agnotic.com