top of page

Your wearable isn't failing on sensors. It's failing on the patient.

Writer: drmarthahall
drmarthahall
Oct 22
3 min read

Short answer: Most wearable problems in clinical trials are not sensor problems. They are wear problems: the device is uncomfortable, hard to put on, or doesn't fit the participant's life, so it comes off and your data goes with it.



Why do trial participants stop wearing their devices?

I've spent my career at the point where the body meets the product. I started as a childrenswear designer and patternmaker, then earned a PhD in biomechanics. That path taught me something sponsors often learn too late: a sensor only measures what it touches, for as long as someone is willing to keep it on.


When I review a trial wearable, the reasons it comes off are almost always the same:

  • Discomfort that builds over days. A strap that feels fine in a 20-minute site visit can irritate, chafe, or itch by day four at home.

  • Fit that ignores real bodies. One size rarely fits a population that spans ages, body shapes, and mobility limits.

  • Friction in daily routines. Charging, showering, sleeping and dressing all create moments when the device comes off and doesn't go back on.

  • Stigma. If a device looks medical, some participants hide it or skip it in public.

  • Hands and dexterity. Small clasps and buttons defeat participants with arthritis, neuropathy or tremor, the very people many trials are trying to study.

None of these show up on a spec sheet. All of them show up as missing data.



What does poor wear time cost a sponsor?

Missing wear time is not just an inconvenience. It weakens the endpoint you are counting on. Gaps can bias results toward participants who find the device easy to wear, and they can force larger enrollment to reach the same statistical power.

Regulators are paying attention. FDA's final guidance on digital health technologies for remote data acquisition, issued in December 2023, asks sponsors to show a DHT is fit for purpose, to evaluate its usability, and to plan for missing data in the statistical analysis plan. Usability is now part of the evidence, not a nice-to-have.



TechStyle Labs 5F Framework checklist for wearable design: Fit, Function, Fabric, Fastener and Fashion


How do you design a trial wearable people actually wear?

Start with the participant, not the sensor. In my work I use the 5F Framework, a checklist for wearable design:

  1. Fit: Does it stay in the right place on every body in your population, including on day 30?

  2. Function: Does it capture the signal you need without asking the participant to do extra work?

  3. Fabric: Do the materials breathe, flex and stay comfortable against skin for the full wear period?

  4. Fastener: Can someone with limited hand strength put it on and take it off alone?

  5. Fashion: Would the participant be comfortable wearing it in public?

Then test it early with people who match your population, in the conditions they live in. A short wear study before your protocol locks costs far less than a mid-trial amendment or a rescue enrollment.


Where should sponsors start?

If you have a wearable in an upcoming study, ask three questions now:

  • Have real participants worn this device for the full planned wear period?

  • Do we know why people take it off, and when?

  • Is our missing-data plan built on observed wear behavior or on assumptions?

If any answer is "not yet," that is where design can protect your data.


FAQ

What is wearable adherence in a clinical trial? It is how consistently participants wear a device as the protocol requires, usually measured as daily wear time or the share of valid days.


Can design really improve wear time? Yes. Comfort, fit, easy fastening and a less medical look remove the most common reasons people take devices off.


When should we test usability? Before the protocol locks, with participants who match your study population, for the full intended wear period.



TechStyle Labs helps biopharma and CRO teams design and test wearables participants keep wearing. Discuss a pilot program.

 
 
 
bottom of page