Remote patient monitoring (RPM) is usually discussed in two registers: the devices — blood-pressure cuffs, glucometers, pulse oximeters, connected scales — and the reimbursement rules that govern when monitoring is billable. Both matter. But there is a third layer that determines whether RPM actually improves care rather than just generating numbers: the data-standards and integration layer. This explainer focuses there.
What RPM is, briefly
RPM uses connected devices to collect physiologic data from a patient at home — vital signs, weight, blood glucose — and transmit it to the care team for review between visits. Medicare established reimbursement for RPM through the Physician Fee Schedule, and a recurring requirement in those rules is instructive for our purposes: to be billable, readings generally must come from an FDA-cleared device and be transmitted automatically, not manually keyed in. That requirement is fundamentally about data integrity.
Why automatic transmission is a standards question
The insistence on device-transmitted (rather than patient-entered) data exists because manually entered readings are easy to mistype, misremember, or fabricate. Automatic transmission preserves a clean chain from measurement to record. But “automatic” only works if the device, the RPM platform, and the EHR can speak compatibly — which is a standards-and-integration problem, not merely a hardware one.
Coding the readings
A home blood-pressure reading is only useful if the receiving system knows it is a blood pressure, in the right units, for the right patient, at the right time. The same coding discipline that applies to in-hospital device data — LOINC for the observations, reliable patient association, a structured record (a FHIR Observation, for instance) — applies to home-collected data. RPM does not get a pass on data quality because the device is in a living room.
The trust problem
Clinicians act on RPM data only if they trust it. Trust depends on knowing the reading came from a validated device, was associated with the correct patient, and arrived uncorrupted. Every one of those assurances rests on standards and integration done well. A flood of poorly governed home readings is not an asset; it is noise and liability.
The convener’s framing
RPM sits at the seam between the home, the device industry, the EHR, and reimbursement policy — a genuinely multi-stakeholder space. Evaluating it well requires looking past the device marketing to the data path underneath. AzHeC’s role is to help Arizona stakeholders ask the right questions about that path. See our Connected Devices work area and the glossary for related coverage.