Healthcare Wearables: Compliance, Battery, and Skin Adhesion
The trifecta that decides whether a healthcare wearable ships on time, on budget, and stays on the patient. Compliance, battery life, and the often-overlooked third pillar.
Healthcare wearables look like consumer products from the outside. From the inside, they are closer to medical devices than fitness trackers — and the teams that succeed are the ones that recognize this on day one rather than at month nine.
Three forces decide whether the product ships: compliance, battery, and adhesion. Most teams underestimate at least two of them.
Compliance is a roadmap, not a gate
Healthcare regulation is not a single hurdle at the end. It is a parallel workstream that starts on day one and runs alongside engineering for the life of the product.
The minimum the team needs to internalize:
- Classification. Is this a medical device under FDA, EU MDR, India CDSCO, or another regime? Class I, II, III? The classification determines the regulatory path and almost every downstream decision. Get a regulatory consultant on day one.
- Quality management system. Companies shipping medical devices need an ISO 13485 or equivalent QMS. This is not a document — it is a way of working with traceable design decisions, controlled documents, and verifiable change management.
- Software lifecycle. IEC 62304 governs medical device software. It dictates how requirements traceable to risk analysis flow through to design, implementation, verification, and release.
- Cybersecurity. FDA’s premarket cybersecurity guidance is now a hard expectation. Threat modeling, SBOM, vulnerability handling, and update strategy are all submission inputs.
- Privacy regulation. HIPAA in the US, GDPR in EU, DPDP in India — depending on what data the device handles and where the patient is.
The mistake that costs years: building the device first and “adding compliance later.” Medical-grade design is structural, not cosmetic. Retrofitting a non-compliant codebase is more expensive than rewriting it.
Battery life is non-negotiable
Patients do not charge medical devices. They lose them, leave them in pockets, and stop wearing them at the first inconvenience. A wearable that needs daily charging is a wearable that gets returned.
The targets that work:
- Continuous-monitoring wearables: 7+ days of battery between charges, more if the device targets older patients or chronic-care use cases.
- Disposable / single-use wearables: 3-14 days of total operation, then the device is replaced.
- Episodic-use wearables (rehab, episodic monitoring): days of standby, hours of active use per session.
Hitting these targets requires:
- Aggressive sleep modes. The MCU is asleep 99% of the time, waking only on sensor events.
- Sensor frontends with low-power options. Modern AFE chips for ECG, PPG, and biopotential signals support sleep states with single-microamp current. Use them.
- Radio discipline. BLE in connected mode with a long connection interval (1-2 seconds) is the typical pattern. Continuous streaming is rare and almost always wrong for wearable form factors.
- Edge processing. Compute the metric on the device, ship the metric. Streaming raw signals over BLE is what kills consumer fitness tracker batteries; it kills medical wearables faster.
A power model that predicts battery life within 10% of measured is a hard requirement. Surprises here delay clinical trials.
Skin adhesion is the silent killer
The most reliable, beautifully-engineered wearable is useless if patients stop wearing it. Adhesion is where engineering, materials science, and human factors collide — and most engineering teams have no expertise in any of those.
The variables that matter:
- Wear duration. Three days, seven days, longer? The adhesive has to hold without causing skin breakdown.
- Body location. Chest, wrist, upper arm, abdomen — each has different skin chemistry, motion, hair, and sweat patterns. An adhesive that works on the upper arm fails on the chest.
- Patient population. Pediatric skin is fragile. Elderly skin is fragile differently. Athletes sweat. Bedridden patients have shear forces on the adhesive from sheets. Each population shifts the design.
- Environmental conditions. Showers, swimming, exercise, climate. The label has to set realistic expectations.
Investments that pay back:
- Engage an adhesive supplier early. 3M, Avery Dennison, and several specialists have applications engineers who will help you select and test materials. Their input is free and saves months.
- Run human studies on adhesion specifically. Not as part of the clinical trial — a separate, faster study with the actual target population, on the actual body location, for the actual wear duration.
- Design for replacement. Most successful long-wear wearables separate the electronics module from the disposable adhesive layer. The electronics outlive many adhesive cycles.
- Account for adhesive cost in the BOM. Quality medical adhesives are not cheap. Building a product around a budget adhesive that fails wear-time is a false economy.
Putting it together
A healthcare wearable program that holds up has these characteristics by month three:
- A regulatory pathway documented and signed off, with a target submission date.
- A QMS in place — even if early-stage, even if just enough.
- A power model that predicts battery life on the actual hardware.
- An adhesive partner selected and a wear-time study scoped.
- Risk analysis covering hazards, mitigations, and residual risks, traceable to design choices.
- A cybersecurity plan covering identity, updates, and data handling.
Programs that have all six tend to ship. Programs that skip two or more tend to drift into a 24-month timeline that turns into 36.
If you are building a healthcare wearable and the regulatory and technical workstreams feel like they are racing each other, we have shipped this combination.
Keep reading
-
Connectivity
Choosing IoT Connectivity: Wi-Fi, BLE, LoRaWAN, NB-IoT, or Cellular
A practical decision guide for picking the right wireless stack for your connected product, based on power, range, throughput, cost per device, and operational reality.
Read -
Embedded
ESP32 vs STM32: When to Pick Each for Your IoT Product
A side-by-side look at when ESP32 wins, when STM32 wins, and the small set of cases where neither is the right answer.
Read -
Embedded
Designing OTA Firmware Updates That Don't Brick Devices
The patterns we use to ship firmware over the air to devices in the field — A/B partitions, rollback, signed images, staged rollouts, and the failure modes that bite if you skip them.
Read