---
title: What Happens After an Abnormal RPM Reading? | 1bios
description: Learn how remote patient monitoring teams review abnormal readings, contact patients, escalate concerns, document actions, and follow through.
---

[Blog: Expert Insights on RPM | 1bioshealth](https://www.1bioshealth.com/blog)

# [What Happens After an Abnormal RPM Reading? | 1bios](https://www.1bioshealth.com/blog/abnormal-remote-patient-monitoring-reading)

 Written by [Andy Scott](https://www.1bioshealth.com/blog/author/andy-scott) | Sep 29, 2026

A patient takes a blood pressure reading at home, and the result falls outside the range their care team is watching. **After an abnormal remote patient monitoring (RPM) reading, the designated team should review the result, assess urgency and patient context, contact the patient as appropriate, and follow a clinician-approved escalation pathway.** The response should be documented, with ownership of any follow-up clearly assigned.

For a physician practice, the operational question is who carries that work through each step. A device can transmit a measurement, but the program still needs people, clinical direction, and a reliable handoff process. That is the practical meaning of 1bios’s positioning: **You already have the patients. We bring the operation.**

 

[BOOK A MEETING](https://www.1bioshealth.com/book-intro)

 

## At a glance: What happens after an abnormal RPM reading?

 After an abnormal remote patient monitoring (RPM) reading, the designated team should assess urgency, review patient context, and follow a clinician-approved response pathway. The response may involve patient contact, verification of the measurement, clinical escalation, and assigned follow-up. Urgent situations may require immediate action rather than completion of every routine step.

1. **Review the reading and its timing.** Confirm the patient, measurement, time taken, and time received. Check relevant trends and existing care instructions.
2. **Assess urgency and patient context.** Consider reported symptoms, clinical history, and the approved monitoring parameters. A software flag alone does not establish a diagnosis.
3. **Contact the patient as appropriate.** Clarify symptoms and measurement circumstances. Repeat a measurement only when clinically appropriate, without delaying urgent care.
4. **Act or escalate under the approved protocol.** Route concerns to the appropriate clinician with the information needed to act. Use the designated backup pathway if the patient or clinician cannot be reached.
5. **Document what happened.** Record the assessment, contact attempts, instructions, and clinical decisions. Distinguish completed actions from planned work.
6. **Assign and confirm follow-up.** Name the person responsible for the next action. Keep unresolved concerns assigned rather than treating a sent message as a completed handoff.

 This is a recommended operational overview, not a patient-specific clinical protocol or a statement of 1bios service commitments. Response depends on clinical urgency and the program's defined review hours and escalation coverage. Automatic transmission does not mean continuous live observation. RPM is not a substitute for emergency care; patients with signs of a medical emergency should call 911 rather than wait for an RPM callback.

## What makes an RPM reading abnormal?

An abnormal reading is a measurement that falls outside the parameters established for clinical review or forms part of a concerning pattern. The significance depends on the measurement, the patient’s condition, their usual readings, and any symptoms. A software flag identifies something to assess; it does not establish a diagnosis or determine treatment by itself.

Practices should define who approves monitoring parameters and how changes are communicated to the team. The workflow should also address trends that warrant review even when an individual measurement does not trigger an alert. The [American Medical Association’s RPM implementation guidance](https://www.ama-assn.org/system/files/ama-remote-patient-monitoring-playbook.pdf) recommends establishing clinical intervention thresholds and protocols as part of workflow design.

## What should happen between the reading and the response?

A practical workflow connects the incoming measurement to a person responsible for reviewing it and a clear route for taking action. The steps below describe a recommended operational structure, rather than a universal response schedule. Urgent situations may require immediate escalation instead of progressing through every routine step.

| Workflow step | Responsible role to assign | Information or action needed | Evidence of completion |
| --- | --- | --- | --- |
| Reading received and routed | Designated monitoring team; technical support for delivery issues. | Confirm patient and device, measurement time, receipt time, and the assigned review queue. | Reading is available to the assigned reviewer; any delivery problem has an owner. |
| Urgency and context reviewed | Appropriately qualified clinical reviewer. | Review the value, relevant trends, available symptom information, and patient-specific instructions under the approved protocol. | Assessment and priority are documented, with the next action assigned. |
| Patient contacted | Authorized care team member following the clinical protocol. | Assess symptoms and measurement circumstances. Arrange a repeat reading only when clinically appropriate and without delaying urgent action. | Successful contact and findings are recorded, or unsuccessful attempts trigger the assigned backup pathway. |
| Clinical action or escalation | Authorized clinician or team member acting within scope and approved orders or protocols. | Provide permitted instructions or escalate the reading, symptoms, trend, and actions already taken to the appropriate clinician. | Clinical direction or escalation is recorded, including the decision needed and responsible recipient. |
| Handoff acknowledged | Sending team and designated receiving clinician or service. | Confirm receipt and responsibility for the next action. Use the backup route if the intended recipient is unavailable. | Acknowledgment and ownership are documented; a sent message alone does not complete the handoff. |
| Follow-up completed or remaining issue assigned | Named follow-up owner, with clinical oversight as appropriate. | Confirm the planned follow-up occurred and record its outcome. Keep outstanding actions assigned with an appropriate follow-up point. | The record shows completed follow-up, an acknowledged transfer of responsibility, or an unresolved issue with a named owner. |

Recommended operational structure, not a patient-specific clinical protocol or a statement of 1bios service commitments. Assign responsibilities according to professional scope, approved protocols, and the service agreement. Urgency may require immediate escalation rather than completion of every routine step. RPM is not a substitute for emergency care.

### Review the reading and its context

The reviewer should confirm which patient and device the reading belongs to, when it was taken, and when it reached the monitoring system. A delayed transmission should not be treated as though it describes the patient’s condition at the moment of review. Recent readings and existing care instructions provide additional context for deciding what needs attention.

This review also helps distinguish a measurement concern from a technical issue. An unusual value may require clinical assessment, while a missing transmission may require investigation of connectivity or device use. Neither should disappear from the workflow simply because the cause is initially unclear.

### Contact the patient and assess what is happening

Patient contact can establish whether symptoms are present and clarify the circumstances surrounding the measurement. Depending on the approved protocol, the conversation may address measurement technique, recent activity, medication use, or other relevant changes. [HHS guidance on remote patient monitoring](https://telehealth.hhs.gov/providers/best-practice-guides/telehealth-and-remote-patient-monitoring/getting-started) describes patient notification and clinical action as central parts of responding to out-of-range data.

A repeat measurement may help when it is clinically appropriate, but it should not become an automatic prerequisite for urgent action. For blood pressure, the [American Heart Association’s home-monitoring guidance](https://www.heart.org/en/health-topics/high-blood-pressure/understanding-blood-pressure-readings/monitoring-your-blood-pressure-at-home) explains the importance of measurement technique and distinguishes repeat-check situations from emergencies. Staff should follow the applicable clinical protocol rather than assume that every abnormal result is a device error.

### Take action or escalate to the appropriate clinician

The next step depends on the clinical assessment and the team member’s authorized role. It may involve reinforcing existing instructions, obtaining clinician review, arranging an appointment, or directing the patient to urgent or emergency care. Medication changes require an authorized clinician’s decision or a valid clinical order or protocol within the staff member’s scope.

An escalation should give the receiving clinician enough information to act. Include the reading and its timing, relevant trends, reported symptoms, contact attempts, actions already taken, and the decision needed. The workflow should specify how receipt is acknowledged and what happens if the designated clinician is unavailable.

### Document the response and assign follow-up

The record should explain what prompted review, what the team learned, and what happened next. Sending a message does not establish that a clinician reviewed it or that the patient received instructions. Any unfinished action needs an owner and a follow-up point appropriate to the situation.

A useful distinction is between an alert that has been reviewed and a clinical issue that has been resolved or transferred to an acknowledged care pathway. The patient may still need an appointment, another assessment, or confirmation of a treatment instruction. The documentation should make that status visible to the next person involved.

## How quickly should an abnormal RPM reading be reviewed?

The response pathway should reflect clinical urgency, patient-specific instructions, and the program’s actual review arrangements. Practices should define response expectations by priority and ensure staffing and escalation coverage support them. A single promised turnaround time does not adequately describe every abnormal-reading scenario.

Patients also need to understand when readings are reviewed and what to do outside those hours. Automatic transmission does not establish that a clinician is continuously watching the data. Enrollment materials should explain the program’s limits and give clear instructions for urgent concerns.

**Patients with signs of a medical emergency should call 911 rather than wait for an RPM callback.** For example, the American Heart Association advises emergency action for severely elevated blood pressure accompanied by specified concerning symptoms. A routine recheck or troubleshooting step should not delay emergency care.

## What if the patient or clinician cannot be reached?

An unanswered call leaves an unresolved assessment, not evidence that the patient is well. The workflow should specify how the team proceeds based on the reading, known context, and approved urgency criteria. Document the attempt and keep the next action assigned.

The same principle applies when the practice receives an escalation, but the intended clinician is unavailable. A shared inbox or voicemail needs an accountable backup process. Teams should agree on that route before relying on it for a patient concern.

| Situation | Operational next step under the approved protocol | Who owns the unresolved issue |
| --- | --- | --- |
| Patient does not answer | Document the contact attempt and assess the next action under the approved urgency criteria. Follow the designated unsuccessful-contact pathway; do not mark the concern resolved solely because a call was attempted. | Assigned clinical reviewer or outreach owner, with escalation to the designated clinician when required. |
| Contact information is incorrect | Use approved records and authorized contact routes to verify contact details. Keep the clinical concern assigned while the contact problem is investigated, and escalate according to urgency. | Assigned outreach owner coordinates verification; the clinical reviewer retains responsibility for the clinical next step until an acknowledged handoff. |
| Clinician does not acknowledge escalation | Use the designated backup clinician or escalation route. Record the pending decision and communication attempts; a sent message does not establish receipt or acceptance of responsibility. | Sending clinical team retains responsibility for pursuing the handoff until the receiving clinician or service acknowledges it. |
| Reading arrives late | Check when the measurement was taken and received. Assess its relevance to the patient's current condition under the clinical protocol, and investigate the transmission delay separately. | Clinical reviewer owns assessment and follow-up; designated technical support owns investigation of the delay. |
| Repeat reading is unavailable | Document why another measurement is unavailable. Determine the next action from the available reading, symptoms, and clinical context; do not delay urgent escalation while waiting for a repeat. | Assigned clinical reviewer, with the authorized clinician determining clinical action when needed. |
| Reading cannot be verified because of a device problem | Record the uncertainty and arrange appropriate device support. Use the approved clinical pathway to assess the patient despite the technical issue; do not assume an unverified reading is harmless. | Clinical reviewer owns the patient concern; technical support owns troubleshooting, with both tasks tracked until completed or handed off. |

Recommended operational responses, not a patient-specific clinical protocol or a statement of 1bios service commitments. Assign roles, backup routes, and response expectations under approved protocols and the service agreement. Actions depend on clinical urgency and available information; no universal retry count or response time applies to this table. RPM is not a substitute for emergency care.

## What does this look like in practice? An illustrative blood pressure example

Consider a patient whose transmitted blood pressure reading exceeds the practice’s review threshold. In this fictional example, the assigned clinical reviewer checks the measurement time and recent trend, then contacts the patient under the approved protocol. The initial assessment identifies no emergency features, and the reviewer determines that a repeat measurement is appropriate.

The reviewer confirms technique, and the repeat result remains outside the patient’s monitoring parameters. The team sends the responsible clinician both readings, the patient’s reported symptoms and relevant context, and the actions already taken. The clinician reviews the information and provides a patient-specific plan.

The assigned team member communicates that plan and confirms the patient understands the next step. The record identifies who will check that the requested follow-up occurred. If the patient cannot be reached or the clinician has not responded, the issue remains assigned and follows the backup pathway rather than being marked resolved.

## Who is responsible when an RPM partner is involved?

An RPM partner’s responsibilities depend on the agreement, approved protocols, and the qualifications of the people performing the work. Practices should explicitly assign data review, patient outreach, technical support, escalation, and documentation. Clinical decisions and oversight must remain with appropriately authorized professionals.

The operating model changes how those responsibilities are staffed and coordinated. With internal delivery, the practice organizes the workflow itself; with hybrid or managed delivery, some functions are assigned to a partner. Our comparison of [RPM operating models](https://www.1bioshealth.com/blog/rpm-monitoring-team-insource-vs-outsource) explores that broader build-versus-partner decision.

When evaluating an arrangement with 1bios, use the abnormal-reading pathway as a concrete discussion. Ask who receives the result, what information reaches the practice, and who follows up on an unresolved handoff. Confirm the agreed scope before describing coverage hours, response times, or escalation capabilities to patients.

## What should the team document after an abnormal reading?

The record should allow another authorized team member to understand the event without reconstructing it from scattered messages. It should distinguish completed actions from attempts and planned work. Practices can use the following as an operational documentation checklist.

- **Measurement:** Value, units, measurement time, receipt time, and relevant trend.
- **Assessment:** Reported symptoms, relevant patient context, and any verification performed.
- **Communication:** Who was contacted, when, through which channel, and whether contact succeeded.
- **Clinical direction:** Instructions or decisions, their source, and any escalation.
- **Follow-up:** Responsible person, planned next action, and current status.

Documentation supports continuity of care and may also support review of services for billing. An abnormal reading or an automated alert does not, by itself, establish a billable RPM service. [CMS describes RPM as distinct service components](https://www.cms.gov/medicare/coverage/telehealth/remote-patient-monitoring), so billing review must assess the work actually performed and the applicable requirements.

## How can a practice check whether its workflow is working?

Start by tracing a small sample of abnormal readings from receipt through their final documented status. Look for unanswered questions, repeated handoffs, and actions that were assigned but never confirmed. Review performance against the practice’s approved expectations rather than an invented industry benchmark.

Useful measures include:

- Time from receipt to review, separated by urgency and coverage period.
- Unacknowledged escalations and how long they remain outstanding.
- Unsuccessful patient contacts awaiting further action.
- Follow-up tasks completed within the assigned timeframe.
- Repeated technical or measurement problems generating avoidable work.

Review these measures alongside case context. A quickly dismissed alert is not necessarily a successfully managed concern. The operational aim is to make the next necessary action visible, assigned, and completed.

For 1bios, this is the conversation behind **“You already have the patients. We bring the operation.”** A practice evaluating RPM support should be able to examine responsibilities from the incoming reading through follow-up. Those responsibilities should be clear before the program begins enrolling patients.

 

[SCHEDULE A DEMO](https://www.1bioshealth.com/book-intro)

 

### Related articles

- [RPM Software vs. Fully Managed RPM: Which Model Fits Your Practice?](https://www.1bioshealth.com/blog/rpm-monitoring-team-insource-vs-outsource)
- [In-House vs. Outsourced Chronic Care Management: Costs and Tradeoffs](https://www.1bioshealth.com/blog/outsourced-ccm)
- [What Does a Billing-Ready CCM and RPM Workflow Look Like?](https://www.1bioshealth.com/blog/billing-ready-ccm-rpm-workflow)
- [Can RHTP Funding Support RPM and Care Coordination?](https://www.1bioshealth.com/blog/can-rhtp-funding-support-rpm-and-care-coordination)

## Frequently asked questions

Practices and patients need a shared understanding of what happens after a concerning reading. The answers below distinguish clinical review from automatic alerts and program coverage from emergency care. Individual instructions should come from the treating team.

### Does every abnormal RPM reading mean an emergency?

No, an abnormal reading does not automatically establish an emergency. Its significance depends on the measurement, symptoms, patient history, and clinical context. The team should use an approved assessment pathway rather than dismiss the result or treat every alert identically.

### Does an RPM alert automatically go to the physician?

Not necessarily, because routing depends on the program’s workflow. A designated clinical team may review the information and escalate it to the appropriate practitioner. The practice should confirm both the initial reviewer and the backup route for concerns requiring a clinician’s decision.

### Is remote patient monitoring watched 24/7?

Patients should not assume continuous live observation simply because a device transmits automatically. Review hours and escalation coverage depend on the program’s actual arrangements. Those limits should be explained clearly, along with instructions for urgent concerns outside review hours.

### Can RPM software decide to change a patient’s medication?

A software flag alone should not be treated as authorization to change medication. Treatment changes require an appropriately authorized clinician or a valid order or protocol applied within professional scope. Patients should follow their clinician’s instructions rather than change a dose because an app marks a result as abnormal.

### What happens if the patient does not answer the care team’s call?

The team should document the unsuccessful contact and follow the approved pathway for that situation. Next steps depend on urgency, available information, and the program’s escalation arrangements. An unanswered call should not automatically close the concern.

### Is a missing RPM reading the same as an abnormal reading?

No, an abnormal reading is an available measurement that raises a concern, while a missing reading means expected information has not arrived. Missing data may reflect device use, connectivity, or another issue that requires investigation. The team should not interpret an absence of data as evidence that the patient is stable.

[View full post](https://www.1bioshealth.com/blog/abnormal-remote-patient-monitoring-reading)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Andy Scott"
  },
  "dateModified" : "2026-09-29T12:46:06.854Z",
  "datePublished" : "2026-09-29T12:46:06Z",
  "headline" : "What Happens After an Abnormal Remote Patient Monitoring Reading?",
  "image" : {
    "@type" : "ImageObject",
    "height" : 1024,
    "url" : "https://6564142.fs1.hubspotusercontent-na2.net/hubfs/6564142/image%20%283%29.png",
    "width" : 1365
  },
  "mainEntityOfPage" : "https://www.1bioshealth.com/blog/abnormal-remote-patient-monitoring-reading",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60,
      "url" : "/hs/hsstatic/content_shared_assets/static-1.4092/img/default-amp-logo.png",
      "width" : 60
    },
    "name" : "1bioshealth Blog"
  }
}
```