What telehealth barriers in older veterans reveal about remote trial design
Remote-first research design tends to be evaluated against a fairly simple question: does the participant have a smartphone and a broadband connection? A recent ethnographic study conducted ahead of a telepharmacy trial for older veterans makes the case that this question, while necessary, badly understates what actually determines whether a remote or telehealth-based study design genuinely works for an older population.
What "digital ageism" actually looks like in practice
The term describes something more specific than a simple access gap. It's the pattern of a digital system being designed around assumptions, comfort with touchscreens, familiarity with app navigation conventions, willingness to trust a device with medical information, that don't hold for a meaningful share of older participants, even ones who technically have the required hardware and connection.
The formative work behind the telepharmacy trial documented barriers well beyond device ownership: uncertainty about whether a video call was actually secure, difficulty navigating multi-step app interfaces designed around conventions younger users take for granted, and a reluctance to ask for help repeatedly with the same technical step for fear of being a burden. None of these show up in a simple broadband-access checklist, and all of them can quietly suppress participation or retention in a study that assumes digital fluency by default.
Why this matters for study design specifically, not just outreach
It's tempting to treat this as a recruitment materials problem, better instructions, clearer onboarding video. Those help, but the underlying issue is structural: a study interface built around assumptions that don't match a meaningful part of the eligible population isn't fully accessible to that population no matter how good the instructions describing it are.
A few design implications follow directly from this:
- Assume variable digital fluency, not a binary "has device or doesn't." A participant with a smartphone can still find a multi-step consent or ePRO flow genuinely difficult to complete unassisted.
- Build in a live-human fallback that doesn't feel like failure. A participant who has to call a coordinator because they got stuck in an app shouldn't experience that as a personal shortcoming; the system should be designed expecting it to happen regularly for some participants.
- Test interfaces with the actual target population, not a digitally fluent proxy. A design team that's comfortable with technology will systematically underestimate friction points that are obvious to someone encountering the interface for the first time with less confidence.
- Repeat instructions across formats. Written, verbal, and video instructions for the same step catch different comprehension gaps; relying on just one format assumes a level of digital literacy the population may not uniformly have.
What the access checklist misses, row by row
A standard digital-access checklist and what the formative ethnographic work actually documented point in noticeably different directions.
| Standard access checklist asks | What the ethnographic work actually found mattered |
|---|---|
| Does the participant own a smartphone? | Ownership doesn't predict comfort navigating a multi-step flow unassisted |
| Is broadband available at their address? | A working connection doesn't resolve uncertainty about whether a video call is genuinely secure |
| Can they receive a text message? | Receiving isn't the same as confidently acting on a prompt embedded in an unfamiliar interface |
| Have they used a similar app before? | Prior app use elsewhere doesn't transfer if this study's interface uses unfamiliar conventions |
| Do they have someone to help if needed? | A reluctance to repeatedly ask for help, out of not wanting to be a burden, can suppress use even when help is genuinely available |
Every row on the left is checkable with a single yes-or-no question at screening. Every row on the right requires actually watching someone try to use the interface, which is exactly why a checklist-only approach to digital access assessment systematically misses the barriers that turn out to matter most.
A composite scenario that shows how this plays out
Consider a participant who owns a smartphone, has reliable broadband, and answers yes to every item on a standard access checklist at screening. Weeks into the study, this participant is quietly falling behind on ePRO completion, not because the app has crashed or the connection has failed, but because each entry requires navigating a multi-step flow that assumes a level of interface familiarity they don't have, and they've stopped asking the study coordinator for help after the second or third time, not wanting to seem like they're struggling.
Nothing about this shows up as a technical fault. From the study's side, it looks like ordinary declining engagement, the kind that might get attributed to waning motivation rather than an interface barrier the access checklist was never designed to catch. The participant hasn't withdrawn, hasn't complained, and technically passed every access criterion at enrolment. They've simply been quietly filtered out of full participation by a design that assumed access equals fluency.
The broader research-quality argument
There's a data-quality case here that goes beyond inclusion for its own sake. If a study's digital design quietly filters out less digitally confident older participants, either through non-enrolment or higher dropout, the resulting evidence base skews toward a specific, more digitally comfortable subset of the population the study was meant to represent. For research on a condition where older participants are a core population, not an edge case, that's a validity problem, not just an equity one.
What a genuinely accessible remote design looks like
None of this argues against remote-first design. It argues for building it properly. A remote or hybrid study that offers assisted digital options, phone-based alternatives to app-only steps, and interfaces genuinely tested with the population it's meant to serve captures the reach benefits of remote-first research without quietly excluding the participants a fully digital-only design would lose.
The lesson from work like this isn't that older participants can't take part in digital-first research. It's that whether they can depends entirely on whether the design accounted for them as a genuine part of the target population, rather than an accessibility feature added on afterward.