Skip to content
Patient using a blood pressure monitor beside a cellular gateway and tablet showing a doctor
Julia SamaraJanuary 8, 202418 min read

How to Choose Connectivity for Remote Patient Monitoring

A remote patient monitoring (RPM) program may use identical medical devices across hundreds of patient homes, but those devices will operate under very different conditions. Home broadband, cellular coverage, building construction, and the amount of technical assistance patients need can all affect data delivery. Healthcare organizations choosing connectivity must account for those differences, as well as how interruptions are handled and what it takes to keep a distributed monitoring program running..

 

Table of Contents

  1. Why Is Connectivity More Complicated in Patient Homes?
  2. Should RPM Devices Use Wi-Fi or Cellular?
  3. When Does an RPM Program Need More Than One Cellular Network?
  4. What Happens When an RPM Device Loses Connectivity?
  5. What Should an RPM Pilot Demonstrate Before Wider Deployment?
  6. How Can Healthcare Teams Manage Connectivity Problems Remotely?
  7. How to Evaluate Connectivity Options for an RPM Program

 

 

1. Why Is Connectivity More Complicated in Patient Homes?

A medical device manufacturer can control the equipment, software, and much of the initial configuration. Once the devices reach patients, the operating environment is largely outside the manufacturer's or healthcare provider's control.

Some patients have reliable broadband and are comfortable connecting new equipment to their home networks. Others depend on shared household connections, have limited internet options, or need assistance with even basic device setup.

Conditions can also vary between homes in the same neighborhood. A cellular signal that works adequately near a window may be unreliable in an interior room. A Wi-Fi device may operate without difficulty for months, then lose access after the household changes internet providers or replaces its router.

When a device stops transmitting, staff may need to contact the patient, determine whether the equipment is still being used, investigate the connection, or arrange a replacement. What takes a few minutes to resolve during a closely managed pilot may require several calls when patients and suppliers are in different locations.

The frequency of these incidents becomes significant as an RPM program expands. A connectivity arrangement that requires regular patient assistance may be manageable for a small group but difficult to maintain across hundreds or thousands of homes.

 

2. Should RPM Devices Use Wi-Fi or Cellular?

Wi-Fi is often a reasonable choice when patients already have dependable broadband. It avoids a separate cellular subscription and can work well for monitoring equipment that stays in one location.

The complication is how that connection is established and maintained after the equipment reaches the patient.

Using the patient's home internet connection

Consider a blood pressure monitor that connects directly to Wi-Fi.

The patient may need to select a network, enter a password, and complete setup through a mobile application. If someone assists with installation, this may take only a few minutes.

Several months later, the household replaces its router. The medical device is still working, but its connection details are no longer valid. Measurements may continue to be taken without reaching the monitoring platform.

The support team has limited visibility into the patient's network and may need to guide the patient through reconnecting the equipment. That process is straightforward for some people and considerably more difficult for others.

Wi-Fi also depends on the quality of the connection where the device is used. Broadband service may be reliable, while wireless coverage is weak in a bedroom or another part of the home.

These issues are manageable when patients have suitable internet access and the program provides a practical way to resolve setup problems. They become more consequential when equipment is shipped directly to patients who are expected to complete installation independently.

Cellular connectivity without home network setup

A cellular-connected device or gateway can be provisioned before shipment, removing the need to configure access to the patient's router.

With compatible equipment and an active connectivity service, installation may require little more than powering on the device and completing its normal setup. Activation, coverage, and any required registration with the monitoring platform still need to be accounted for.

For organizations distributing equipment across a broad patient population, this can make onboarding more consistent. Patients do not need to know their Wi-Fi passwords, and changes to their home internet service generally do not affect the cellular connection.

The trade-off is dependence on cellular coverage at the installation location.

A carrier may provide adequate service throughout a neighborhood but have difficulty reaching an interior room or basement. Building materials and surrounding structures can affect reception, and a device may need to be placed differently to establish a usable connection.

Cellular service also carries a recurring expense. Whether that additional cost is justified depends partly on how much installation and troubleshooting work it replaces.

One cellular connection for several medical devices

An RPM kit may include a blood pressure monitor, digital scale, and pulse oximeter. Instead of giving each device its own internet connection, the manufacturer can configure them to send measurements over Bluetooth to a cellular gateway.

For the patient, the arrangement may require little setup if the equipment has been paired before shipment. From the provider's side, there is one cellular connection to activate and manage for the kit, rather than a separate connection for every medical device.

The gateway introduces a shared point of failure, however. If it loses power or stops communicating with the medical devices, readings from several sources may stop reaching the platform. Its location in the home also matters because Bluetooth has a limited range.

Whether this arrangement makes sense depends largely on the equipment included in the kit. A standalone monitor with integrated cellular connectivity avoids the separate gateway. Where multiple compatible devices are used, a shared gateway may reduce the number of cellular connections needed.

Consideration Wi-Fi Cellular
Patient's home broadband
Required
Not required
Initial setup
May require router access and passwords
Can be provisioned before shipment
Changes to home internet
May require reconnection
Generally unaffected
Coverage limitations
Wi-Fi reach and broadband availability
Cellular coverage, including indoor reception
Connectivity charges
Usually uses existing broadband
Separate cellular service expense
Support requirements
May involve the patient's home network, broadband provider, device, or monitoring application
May involve cellular coverage, SIM provisioning, device or gateway operation, and connectivity or platform providers

 

 Takeaway
 
A pre-provisioned cellular device can reduce the need for patients to configure and maintain a home network connection. Wi-Fi may still be suitable when broadband is dependable and installation support is available. 

 

CONNECTIVITY OPTION

Cellular Connectivity for Healthcare Applications

 
See how cellular connectivity supports remote patient monitoring and other connected healthcare applications.

 

3. When Does an RPM Program Need More Than One Cellular Network?

A single cellular carrier may provide sufficient coverage for an RPM program operating in a limited geographic area. The situation becomes less predictable when the same devices are distributed across several states or a mixture of urban, suburban, and rural communities.

Carrier coverage maps can indicate where service is expected, but they cannot fully account for reception inside individual homes.

For a program shipping standardized monitoring kits, this creates a practical problem. If a device cannot establish a usable connection at a patient's address, the organization may need to identify another carrier, send replacement equipment, or arrange a different way to transmit readings.

Handling a few exceptions may be relatively straightforward. Maintaining carrier-specific equipment and activation procedures across a large patient population introduces additional inventory and support work.

What multi-carrier connectivity offers

A Multi-Carrier SIM can provide access to several supported cellular networks through one connectivity arrangement.

Depending on the device and service configuration, equipment can automatically switch across networks when its current connection becomes unavailable or network-selection conditions require a change.

This reduces dependence on a single carrier's coverage footprint and may allow the same device configuration to serve more patient locations.

The availability of multiple networks does not guarantee service inside every building. A home may have poor reception from all supported carriers, and cellular network selection is not based on signal strength alone. 

Recovery may also take time. A network change does not guarantee that measurements will immediately resume reaching the monitoring platform.

For RPM operators, the practical question is how many locations the proposed connectivity service can accommodate without requiring individual carrier arrangements or replacement equipment.

When eSIM becomes relevant

Some device manufacturers and RPM providers also need flexibility over the longer service life of their equipment.

Devices may be supplied in several countries, or the organization may want to change connectivity providers without retrieving equipment from patients.

An appropriate eSIM implementation can support remote provisioning or changes to operator profiles, depending on the device, provisioning system, and service agreements.

That is different from providing access to multiple cellular networks through a Multi-Carrier SIM. Having an eSIM does not automatically mean that a device can move between carriers whenever coverage changes.

For a domestic RPM program with stable connectivity requirements, remote profile management may offer limited additional value. For a manufacturer distributing devices internationally or planning future provider changes, it may be an important purchasing consideration.

 

4. What Happens When an RPM Device Loses Connectivity?

A patient may continue taking measurements without knowing that the device has stopped sending them. The problem could remain unnoticed until someone checks the monitoring dashboard or the system flags missing readings.

Whether the data can be recovered depends on where the device stores measurements and what it does when the connection returns. A short delay may be acceptable for a scheduled daily reading, while other RPM programs have stricter delivery requirements. Those limits need to be established according to the clinical purpose of the monitoring service.

Conventional RPM equipment should not be treated as an emergency monitoring system unless it has been specifically intended and validated for that purpose.

What happens to readings during an interruption?

Consider a blood pressure monitor used for scheduled morning measurements. The patient takes a reading, but the home's internet connection is unavailable. The measurement itself is successful; the difficulty is getting it to the monitoring platform.

Some devices retain readings in their internal memory. Others use a gateway or companion application to store measurements until they can be uploaded. The amount of available storage, the way timestamps are recorded, and the handling of unsuccessful transmissions vary between products.

For the healthcare team, the distinction becomes important when a connection has been unavailable for several hours or longer. A device may eventually deliver every measurement collected during that period, or it may retain only a limited number of readings. Some systems may require the patient to repeat a measurement that was never stored successfully.

The monitoring platform also needs to preserve the original measurement time. Otherwise, a group of readings uploaded after a prolonged interruption could appear to have been collected together when the connection returned.

Recovery without patient assistance

A device may restore its network connection but still have readings waiting to be delivered. The application needs to resume communication, upload pending measurements, and confirm that the receiving system has accepted them.

The process differs between RPM products. Some recover automatically after a router restart or a temporary cellular outage. Others may require a device restart, reconnection through an application, or assistance from technical support.

For equipment deployed in patient homes, that difference has a direct effect on everyday operations. A brief network outage that resolves without intervention may go unnoticed. The same interruption becomes a support issue when a patient must follow several instructions before readings begin appearing again.

When missing data requires action

A brief interruption followed by successful transmission may require no intervention. A device that has not reported for an extended period presents a different situation.

The care team may not know whether the patient stopped taking measurements, the device lost power, or readings were collected but never delivered.

Programs therefore need defined reporting expectations and procedures for investigating missing information.

A connectivity failure is not itself a clinical alert. However, when the monitoring service depends on receiving measurements within a specified period, missing data may require staff to contact the patient or follow another established process.

The connectivity design should support those requirements without being treated as a substitute for clinical monitoring or escalation procedures.

 

 Takeaway
 
Restoring a network connection does not guarantee that missing measurements have been delivered. RPM systems need appropriate data storage, recovery behavior, and reporting procedures for the clinical program they support.

 

CONNECTIVITY SOLUTION

Planning Connectivity for an RPM Deployment?

 
Discuss your device setup, patient locations, and connectivity requirements with our team. We'll recommend the most suitable connectivity arrangement for your deployment.

 

5. What Should an RPM Pilot Demonstrate Before Wider Deployment?

A pilot can look successful when devices transmit readings reliably and the monitoring platform displays the expected information. Yet the amount of assistance provided during the pilot may conceal problems that will be difficult to manage in a larger program.

Consider a pilot involving twenty patients. Every participant receives help installing the equipment, and a small project team responds personally whenever something stops working.

The devices may perform well under those conditions. The same operating model becomes harder to sustain when equipment is mailed to two thousand patients across different regions.

Can patients get connected under normal deployment conditions?

A pilot in which technicians install every device can provide useful information about equipment performance, but it tells the organization little about what patients will experience when kits arrive by mail.

For at least some pilot participants, installation should follow the same process planned for the wider rollout. That includes the instructions supplied with the kit, any required activation steps, and the support channels patients will have available.

A blood pressure monitor might work reliably once connected to Wi-Fi, yet patients may repeatedly need assistance entering network credentials or reconnecting after a router change. A cellular device removes those particular steps but may encounter poor reception in certain homes. Both situations belong in the pilot record, along with the time and assistance needed to resolve them.

Are readings delivered within the program's requirements?

During the pilot, it is worth examining the timing of measurements that arrive late, not only whether they eventually reach the platform.

For a program collecting scheduled blood pressure or weight measurements, the reporting window may be fairly generous. Another RPM service might depend on receiving several updates throughout the day. In either case, the clinical team should already have established what counts as an acceptable delay.

The pilot results can then be assessed against those expectations. If delayed readings are common, the organization needs to establish whether the interruptions were brief, whether measurements arrived outside the agreed window, and whether any patient assistance was involved. A high overall delivery rate does not necessarily mean the system met the program's reporting requirements.

What will the support workload look like at scale?

Support records can reveal problems that are easily overlooked when attention is focused on device performance. A monitoring kit may have a high transmission success rate while still generating frequent calls about activation, equipment placement, or reconnection.

Suppose two patients in a twenty-person pilot encounter the same installation problem. Both cases are resolved quickly by the project team. That may seem insignificant while the pilot is small, but the same 10% incidence across two thousand patients would mean approximately two hundred cases requiring attention.

The estimate is not a forecast. The wider patient population may have different circumstances, and some problems may disappear after the installation process is improved. Still, recurring support incidents deserve investigation before the organization commits to a large shipment of equipment.

Some support issues are tied to particular locations or groups of patients. For example, several failed installations in the same rural area may indicate that the selected cellular carrier has insufficient coverage there. If calls are coming from patients in different locations but concern the same activation step, the problem is more likely to involve the setup process.

These details are worth separating in the pilot report. Otherwise, a high overall connection success rate may conceal difficulties that will continue when the program expands.

 

RELATED GUIDE

How to Know If Your IoT Connectivity Is Ready for a Full Deployment

 
For a broader look at what to check before moving beyond a pilot, including connectivity performance, recovery behavior, and rollout readiness.

 

6. How Can Healthcare Teams Manage Connectivity Problems Remotely?

An active cellular connection tells the RPM support team very little about whether a patient's measurements have reached the monitoring platform. The gateway may be online, but the medical device could have stopped communicating with it. The application might also be experiencing a transmission or processing problem.

Finding the cause becomes more complicated when the equipment manufacturer, connectivity provider, and RPM platform vendor operate separate systems. Each may have records that explain part of the incident, but the healthcare organization needs a way to bring that information together.

For an RPM program with hundreds or thousands of devices in patients' homes, routine investigations cannot depend on patients repeatedly checking cables, restarting gateways, or contacting several support departments. The organization needs access to appropriate device and connectivity information, along with a clear process for assigning and escalating support cases.

What can be checked without contacting the patient?

The monitoring platform should generally provide a record of when measurements were received and when the device or gateway last communicated.

A device management platform might show whether a gateway is powered on, whether measurements are stored locally, or whether transmission attempts have failed.

A cellular connectivity provider may report connection activity, the network being used, or recent data consumption.

These records can narrow down the cause of missing readings before the patient is asked to troubleshoot equipment.

For example, an absence of cellular activity may suggest that a gateway has lost power or cannot establish service. Continued cellular traffic without corresponding measurements points toward a different set of possibilities.

A support team may also be able to identify whether a disruption affects one patient's equipment or several devices operating in the same area.

The available diagnostics vary between vendors. Healthcare organizations do not necessarily need direct access to every technical system, but the relevant information should be obtainable when an investigation requires it.

Who investigates when the cause is unclear?

An RPM program may involve a medical device manufacturer, monitoring platform vendor, connectivity provider, and healthcare organization.

Each has responsibility for a different part of the service.

The device supplier may need to establish whether measurements were collected and stored. The connectivity provider can investigate cellular network access. The platform vendor may examine whether data reached the application and was processed correctly.

Without an agreed process, support cases can move between vendors while the healthcare organization continues to receive incomplete information.

Contracts and operating procedures should identify who receives the initial report, which supplier investigates each type of failure, and how unresolved cases are escalated.

The same arrangements should cover device replacement, SIM activation, changes to connectivity service, and patients moving to locations where their existing connection may no longer work.

For a large RPM program, the ability to resolve problems remotely is important. Equally important is knowing who has the information and authority needed to act.

 

 Takeaway
 
For distributed RPM programs, remote diagnostics are only useful when support responsibilities are clear. Device, connectivity, and platform providers need an agreed process for investigating problems that cross system boundaries. 

 

7. How to Evaluate Connectivity Options for an RPM Program

Connectivity proposals are easier to compare when the requirements have been established before selecting a technology or provider.

An RPM program serving patients in one region may be able to use a single cellular carrier or existing home broadband connections. A program distributing equipment across several states may place greater value on multi-carrier access, pre-provisioned devices, and centralized support.

The appropriate arrangement also depends on the clinical reporting requirements and the amount of patient assistance the program can sustain.

Evaluation area What needs to be established
Patient environment
Where devices will be used, available broadband and cellular coverage, and any indoor reception limitations
Installation and onboarding
Whether patients can activate equipment independently and what assistance will be required
Data-delivery requirements
How quickly readings must arrive, what delays are acceptable, and how missing information is handled
Connectivity recovery
Whether devices preserve readings and reconnect without patient intervention
Remote support
What information is available to investigate failures and which supplier is responsible
Operating costs
Equipment, connectivity charges, onboarding, replacements, and ongoing technical support
Future flexibility
Whether connectivity arrangements can be changed as coverage needs, providers, or deployment locations change
Data protection
How information is protected during transmission and which parties are responsible for the relevant security controls

Security deserves attention when several suppliers handle different parts of the transmission process. An encrypted cellular connection, for example, does not establish that the complete RPM system meets the organization's data protection obligations. Device security, application controls, access permissions, and data handling responsibilities must be considered as part of the wider system.

When comparing proposals, healthcare organizations should ask providers to demonstrate how their systems meet the agreed requirements. Coverage claims alone cannot establish whether equipment will work reliably inside representative patient homes. Likewise, a successful data transmission during a demonstration says little about how the device will behave after a prolonged interruption.

Cost comparisons should reflect the expected operating life of the equipment. A lower connectivity charge may be offset by frequent support calls, manual activation, or replacement devices. A cellular gateway introduces hardware costs but may provide connectivity for several medical devices through one service plan.

The final arrangement does not necessarily need to be identical for every patient. Some programs may use cellular as the standard connection while supporting Wi-Fi where appropriate. Others may select different equipment for patients with limited coverage or more demanding reporting requirements.

The decision should account for how the system will be installed, what happens when communication fails, and how problems will be managed once the devices are distributed. Those operating conditions ultimately determine whether the selected connectivity arrangement is sustainable for the RPM program.

 

CONTINUE EXPLORING

See how cellular connectivity supports remote monitoring devices in patients' homes
 
Compare how single-IMSI and multi-IMSI SIMs differ in network access and deployment flexibility

 

RELATED ARTICLES