Two programs with the same weak points
Remote patient monitoring program support covers two related services. Remote patient monitoring (RPM) collects physiologic data, such as blood pressure, weight, pulse oximetry or blood glucose, from a connected device in the patient’s home. Remote therapeutic monitoring (RTM) collects non-physiologic data about a therapy, such as adherence and response, most often for respiratory and musculoskeletal conditions.
The clinical uses differ. The operational failures are the same. Devices sit in the box. Patients stop taking readings after the second week. Readings arrive and nobody is assigned to look. The month ends and no one can show how many days of data came in or how much time was spent.
Gateway addresses those points for practices in Greater St. Louis and the Metro East: onboarding, instructions, the review process and the records.
Onboarding patients and devices
Onboarding works when it runs in the same order every time.
- The clinician orders monitoring for a specific patient and purpose, and the practice confirms eligibility and payer requirements.
- Consent is obtained and documented.
- A device is selected and delivered. Our page on remote monitoring devices covers compatibility, setup, support and replacement.
- The patient or caregiver is shown how to use it, and the setup and education are recorded with a date.
- The first readings are checked to confirm the device is transmitting.
We track each patient through those steps, so a device shipped is not mistaken for a patient onboarded.
Patient instructions that hold up at home
Instructions written for a clinic visit rarely survive a kitchen table. We help the practice prepare plain-language instructions that answer what patients ask:
- When and how often to take a reading
- What to do if the device does not turn on or connect, and who to call about it
- Who to call about symptoms, which is the practice and not the device help line
- Whether a family member or caregiver can help
- That readings are reviewed on the practice’s schedule and are not watched around the clock
The last point is a safety matter. Patients need to hear that monitoring is not an emergency service and that an emergency means calling 911. Our patient guide to what to expect from remote monitoring at home can be shared at enrollment.
A clear process for clinical review
Data without an assigned reviewer is a liability. The practice defines the review process, and we help write it down and run its administrative parts.
The clinician sets each patient’s parameters and what counts as out of range. The practice names who reviews readings, how often, and what happens when a reading falls outside the parameters. We organize the queue: flagged readings routed to the practice’s clinical staff under its protocol, patients with missing readings listed for outreach, and documentation tasks kept open until done. Gateway does not interpret readings, advise patients on symptoms or change treatment.
Counting days and minutes
Monitoring codes turn on two kinds of counts. Device and data codes depend on how many days of readings arrive in a period. Management codes depend on time spent in a calendar month, usually including direct communication with the patient or caregiver. The thresholds vary by code and have been revised, so the practice confirms them for each date of service.
The records are the same either way: days with readings per patient per period, a dated log of management time by person and activity, and the date of setup and education. A month-end list shows the practice which patients met which requirements.
Time counted for monitoring is kept apart from time logged for chronic care management. AI-assisted follow-up can surface patients who are falling short on readings early enough for staff to call them.
What stays with the practice
Monitoring services carry eligibility, consent, supervision, documentation and billing requirements that vary by service and payer. The practice confirms them and keeps:
- The order for monitoring and each patient’s parameters
- Review of readings and every clinical response
- Supervision of the staff who do monitoring work
- Medical necessity, final coding decisions and responsibility for claims
How an engagement starts
Contact us through the practice support inquiry form or at 314-325-0126. We will ask what the practice wants to monitor, for which patients, with which devices and who would review the data.
The RPM program startup questions guide lists the decisions worth making first. If the review process is not yet defined, that is where we begin, before any device is ordered.
Common questions
What happens when a patient stops sending readings?
The patient appears on a missing-readings list, and outreach follows the practice’s rules: a call to check on the device, the routine and whether the patient still wants to take part. Device problems go to support or replacement. If the patient has lost interest or the monitoring is no longer useful, the clinician decides whether to end it.
Who owns the devices, and what happens when one breaks?
It depends on the arrangement the practice chooses: purchase, lease or a vendor-supplied program. Each handles replacement, returns and cleaning differently. We track which device each patient has, when it was issued and its status, and coordinate replacement with the supplier.
Is RTM run the same way as RPM?
Operationally, much of it is: an order, consent, onboarding, instructions, review and records. The differences lie in what is collected, which clinicians may order and bill it, and how data may be reported, including patient-entered information in some cases. Those rules are specific, and the practice confirms them before enrolling patients.
Which patients should we start with?
The clinician chooses. As a practical matter, programs go more smoothly when the first patients have a clear clinical reason for monitoring, a working phone, and either comfort with the device or a caregiver who can help. Starting small lets the practice test its review process before the number of readings grows.