PatientTrac Companion | Reimbursement Series

Patient using a mobile health application alongside connected clinical monitoring data
Patient-reported information can be clinically valuable, but Medicare RPM device billing depends on qualifying connected-device transmission.

The patient takes a reading on a drugstore blood-pressure cuff at the kitchen table. The display reads 132 over 84. She opens her recovery app and types the two numbers into a field, then taps "slightly dizzy." On the care team's screen, the entry looks exactly like device data.

That typed number is patient-reported data, but Medicare's remote physiologic monitoring codes pay only when a device sends the reading itself.

CMS describes remote patient monitoring as the collection of physiologic data—such as blood pressure, weight, or oxygen saturation—using a connected medical device that automatically transmits the data to the health care provider. Medicare policy has also clarified that RPM device data must be electronically collected and transmitted rather than self-reported. For 2026, the longer-duration CPT 99454 pathway remains tied to 16–30 days of device data, while a separate short-duration code, CPT 99445, addresses 2–15 days.

That rule binds every practice that bills RPM, regardless of the app in the patient's hand. A reading typed from a separate cuff breaks the chain the code requires, because no device transmitted it. The number can still be clinically useful. It cannot support an RPM device claim.

Many remote-care products blur this line in their marketing. A symptom diary gets described as monitoring, and monitoring gets described as billable. A practice that believes it and bills manual entries as RPM takes on the audit risk itself.

PatientTrac Companion as it stands today should be described plainly. Manual symptom, medication, and wellbeing entries support care documentation, ePRO programs, and care management. They do not by themselves create an RPM claim. A legitimate RPM pathway requires integration with qualifying connected devices such as blood-pressure cuffs, scales, and pulse oximeters, and that integration is Companion's next build, not a current feature.

Saying so costs a sales conversation or two. It also keeps every other claim Companion makes believable when a compliance officer reads it.

The patient at the kitchen table did everything asked of her. Whether her next reading counts as monitoring now depends on a cable, a Bluetooth pairing, and a decision the practice has not yet made.

Reimbursement information is provided for educational purposes and reflects publicly available guidance reviewed as of September 28, 2026. Coverage, coding, documentation requirements, medical necessity and payment vary by payer, locality, patient circumstances and service. PatientTrac supports clinical and documentation workflows and does not determine code selection or guarantee reimbursement. Qualified billing and clinical staff should verify current payer requirements.

Primary Sources

Sources reviewed September 28, 2026. Links should be rechecked at publication and during periodic reimbursement review.