RPM for Elderly Patients: Designing for Older Adults

How should RPM be designed for elderly patients?

RPM for elderly patients should be designed so that taking a reading needs no app, no pairing and no reading of small text. That means cellular devices that send data automatically, setup done with the patient and checked by teach-back, a defined role for caregivers, accessible screens and calls, and prompt human follow-up when readings stop.

Older adults are not one group. A 68-year-old who uses a smartphone daily and an 88-year-old with low vision and arthritis need different setups, so the service should record each patient's needs at enrollment and adjust devices, channels and contact plans to match.

Which devices suit older adults?

Devices that suit older adults send readings over their own cellular connection, have large displays and few buttons, and work the same way every time. Bluetooth devices that pair with the patient's phone add steps that can fail without the patient knowing.

• Connectivity: cellular-enabled devices, or a cellular hub that collects readings from nearby devices, avoid dependence on home Wi-Fi or a smartphone.
• Display: large digits, high contrast and a clear sign that the reading was sent, such as a check mark or a confirmation tone.
• Physical design: cuffs that are easy to put on with one hand, scales with a wide platform and low step, and buttons large enough for reduced dexterity.
• Sizing: blood pressure cuffs in the right size for the patient's arm, recorded at enrollment so replacements match.
• Power: long battery life with an alert to the care team, not just the patient, when the battery runs low.

On the software side, map each device model to its data path and its failure signals. The platform should know the difference between a device that sent no reading, a device that is offline and a device whose battery is low, because each needs a different follow-up.

Setup and training that sticks

Setup sticks when it happens with the patient, at their pace, and ends with the patient taking a reading on their own while someone watches. A box mailed with a leaflet leaves too much to chance for many older adults.

Offer setup in person or by video with a caregiver present if the patient wants one. Walk through each device, then ask the patient to show how they take a reading. This teach-back step finds problems, such as a cuff placed over clothing, before they become weeks of bad data.

Leave simple printed instructions with large text and photos of each step, plus a single phone number for help. Record in the platform who attended setup, which steps the patient completed and any adjustments made, so follow-up calls start from what actually happened.

Schedule a check-in call a few days after setup. Early questions are easier to solve before the patient loses confidence in the devices.

Plan for device replacement too. When a device fails or the patient moves into a care facility, the platform should support a swap without losing history: retire the old device record, pair the new one to the same patient and note the change on the reading timeline so clinicians do not mistake a device change for a clinical change.

How should caregivers and proxies get access?

Caregivers and proxies should get access through their own accounts with permissions the patient agrees to, never by sharing the patient's login. The platform needs to know who each person is, what they may see and do, and when that permission ends.

HIPAA allows sharing with people involved in care. Under 45 CFR 164.510(b), a covered entity may disclose information directly relevant to a family member's, relative's or close friend's involvement in the patient's care, and when the patient is present and has capacity, it may do so if the patient agrees or does not object when given the chance.

• Roles: separate a caregiver who receives reminders, a caregiver who can view readings and a legal representative with full access, and record the basis for each.
• Consent capture: record the patient's agreement, the date and the scope, and let the patient change it later.
• Notifications: let the patient choose whether a caregiver hears about missed readings, out-of-range readings or both.
• Audit: log every caregiver view and action under their own identity.
• End dates: support temporary access, for example during recovery, that expires automatically.

Caregiver involvement should not replace contact with the patient. Clinical conversations still happen with the patient whenever they are able, with the caregiver joining if the patient wants.

Designing for hearing, vision and dexterity

Designing for hearing, vision and dexterity means every patient-facing screen, message and call can be used by someone with reduced senses or grip. For many providers this is also a legal question, not just good design.

The HHS Section 504 rule at 45 CFR 84.84 adopts WCAG 2.1 Level AA for the web content and mobile apps of recipients of HHS federal financial assistance. An interim final rule published on 11 May 2026 moved compliance to 11 May 2027 for recipients with 15 or more employees and to 10 May 2028 for smaller ones.

• Vision: support system text size and zoom without breaking layout, use strong contrast, and never rely on color alone to show an out-of-range reading.
• Hearing: pair every sound with a visual cue, offer text and captions for video, and let patients choose text over calls.
• Dexterity: use large touch targets, avoid gestures that need precision, and keep forms to a few fields.
• Cognition: use plain words, one task per screen and consistent placement, and confirm each action clearly.
• Calls: set outbound calls to come from a recognizable number, speak slowly and confirm understanding before ending.

Test with older adults, including people who use screen readers or magnifiers. Automated accessibility checks catch some problems, but they cannot tell you whether an 85-year-old can find the help number.

How do you follow up when readings stop?

Follow up when readings stop by treating silence as an event: the platform flags a missed reading on the day it was due, sends a reminder through the patient's chosen channel, and creates a call task if the gap continues. When the cause is practical, a call finds it faster than repeated texts.

Practical causes include a dead battery, a device moved away from the hub, a hospital stay, a visiting relative's routine or a lost instruction sheet. Record the cause in a structured field so the program can see which problems recur and fix them at the source.

Billing rules give shorter periods a place. Under the CY 2026 Physician Fee Schedule final rule, CPT 99445 covers device supply for 2 to 15 days of readings in a 30-day period, alongside 99454 for 16 to 30 days, so a patient with fewer reading days can still be part of a billable program.

That should not change the clinical goal. Follow-up exists to keep the patient monitored as the care team intends, and the platform should report adherence against the clinician's plan, not only against billing thresholds.

Which privacy and safety risks are specific to older adults?

Older adults face particular risks from shared devices, scam messages and changes in capacity, so the service should plan for each. These are design questions as much as policy ones.

Shared phones and tablets mean messages can be read by others in the home. Keep message content minimal and show detail only after the patient signs in. Scam texts and calls that imitate health services are a concern, so tell patients exactly which number and sender name the service uses and never ask for passwords by message.

Capacity can change during a program. Give the care team a way to record a change, review caregiver roles and, where a legal representative is involved, update access based on documentation rather than a phone request.

An older-adult RPM design checklist

Use this checklist when designing a new RPM service for older adults or reviewing an existing one.

• 1. Enrollment: record vision, hearing, dexterity, preferred channel, language and caregiver details for each patient.
• 2. Devices: default to cellular devices or a cellular hub, with the cuff size and model recorded.
• 3. Setup: complete setup with teach-back, record the result and schedule an early check-in call.
• 4. Caregivers: give each caregiver their own account, role, consent record, notifications and audit trail.
• 5. Accessibility: meet WCAG 2.1 AA on patient screens, test with older users and pair every sound with a visual cue.
• 6. Silence handling: flag missed readings on the due day, remind through the chosen channel and escalate to a call.
• 7. Causes: capture the reason for each gap in a structured field and review the trends monthly.
• 8. Safety: keep messages minimal, publish the service's real contact details and handle capacity changes through documented steps.

How Agnotic can help

An RPM service for older adults needs devices that work without fuss and software that notices quickly when they do not. Agnotic Technologies builds custom RPM apps for clients with cellular device integration, enrollment records for each patient's needs, caregiver roles and consent, accessible patient screens and follow-up workflows that turn missed readings into tasks.

Agnotic does not run monitoring or staff a care program. It builds the software the client's clinical team specifies, tests it with older users before launch, and adjusts device integrations and screens as the program learns where patients struggle.

Sources

• Cornell LII: 45 CFR 164.510, uses and disclosures requiring an opportunity to agree or object
• Federal Register: Extension of compliance dates for the HHS Section 504 web and mobile accessibility rule
• CMS: CY 2026 Medicare Physician Fee Schedule final rule (CMS-1832-F) fact sheet