RPM, RTM & Remote Services: Where Coding Meets Workflow

Remote monitoring programs can expand access to care, support ongoing treatment, and help providers stay connected with patients between visits. But for healthcare organizations, a common challenge is ensuring that the services being delivered are supported by the documentation and workflows necessary for accurate billing.

A patient may be using a monitoring device, clinical staff may be reviewing information, and the provider may be making treatment decisions. Yet those activities do not automatically establish that every requirement for a separately billable remote monitoring service has been met.

As organizations evaluate existing programs and prepare for potential Medicare changes in 2027, understanding where coding meets workflow is increasingly important.

RPM and RTM are not interchangeable.

Remote physiologic monitoring (RPM) generally involves collecting physiologic data, such as blood pressure or weight, through connected medical devices.

Remote therapeutic monitoring (RTM) involves nonphysiologic data associated with therapeutic care, including certain respiratory and musculoskeletal monitoring services.

Although both support care outside traditional office visits, their coding requirements differ. Understanding which service is being provided is essential to determining what documentation and billing requirements apply.

Medicare is considering changes for 2027.

The CY 2027 Medicare Physician Fee Schedule (PFS) proposed rule addresses several aspects of remote monitoring, including initiating visits, established-patient requirements for RTM, and clinical staffing arrangements.

CMS is also evaluating payment valuation and potential changes to remote monitoring reimbursement, including possible new HCPCS G-codes.

These provisions remain proposals. Organizations should monitor the final rule before changing existing coding or billing practices based on proposed requirements.

Documentation must reflect the services performed.

Depending on the codes reported, documentation may need to support device setup, patient education, monitoring activity, treatment management time, and required interactive communication.

Importantly, collecting monitoring data and providing treatment management are distinct activities. Documentation supporting one service does not automatically establish that another service’s billing requirements have been satisfied.

Strong workflows support accurate reimbursement.

Organizations should consider whether staff responsibilities are clearly defined, required activities are consistently documented, and billing processes distinguish between RPM and RTM.

Education should include clinicians, clinical support staff, coders, and billing personnel involved in these services.

A focused review of existing practices can reveal opportunities to strengthen documentation, reduce billing uncertainty, and prepare for future policy changes.

BCA, Inc. helps healthcare organizations take that next step through auditing, targeted education, and consulting. By evaluating remote monitoring documentation, coding practices, and operational workflows, BCA can help identify potential gaps and develop practical improvements that support accurate, defendable billing.

Because successful remote monitoring requires more than the right technology or CPT code. It requires processes that consistently support the services being reported.

Schedule a consultation with one of our experts.