Wearable medical devices are body-worn electronic products that sense, monitor, or deliver therapy while a person goes about daily life. Regulated as medical devices when intended for diagnosis, monitoring, or treatment, they combine sensors, embedded software, and wireless links and must meet safety, biocompatibility, and software standards set by the FDA and EU MDR.
What is a wearable medical device?
A wearable medical device is worn on or attached to the body to measure a physiological signal, monitor a condition, or apply a therapy, and it carries a medical intended use. Common forms include continuous glucose monitors, single-lead ECG patches, wearable cardioverter defibrillators, pulse oximeters, and neurostimulation wearables.
The regulatory line sits at intended use. A body-worn product that only encourages healthy habits can fall under the FDA general wellness policy, revised in January 2026 to give non-invasive consumer wearables more room. Once a product claims to diagnose, monitor a disease, or drive clinical management, it becomes a wearable medical device and enters the full design-control pathway.
Why wearable medical devices matter in medical device development
The stakes are higher than for a consumer gadget. A missed arrhythmia, a false low-glucose alarm, or a battery failure during therapy can cause direct patient harm, so these products sit under formal risk management and surveillance.
Wearables also live in an uncontrolled setting: the home, the gym, a commute. They run unattended, are operated by lay users, and face sweat, motion, temperature swings, and unreliable connectivity. That drives regulatory scrutiny and audit exposure. Getting the classification wrong or shipping without the right verification evidence can stall a submission or force a costly late redesign.
How a wearable medical device works
A wearable medical device combines several engineering domains in one small, body-worn system:
- Sensing. Optical (PPG), electrical (ECG or EMG), electrochemical, motion, or temperature sensors capture the raw signal at the skin.
- Signal conditioning and processing. Analog front ends and embedded firmware filter noise, reject motion artifacts, and convert raw data into a usable measurement.
- Embedded software. Firmware and any companion algorithm are developed under IEC 62304 for the software lifecycle. The current edition is IEC 62304:2006 with Amendment 1:2015; a second edition is anticipated around August 2026 but is not yet published.
- Power and thermal design. Small batteries must deliver days of operation without overheating against the skin, which ties into electrical safety testing.
- Connectivity. Bluetooth Low Energy or cellular links push data to a phone or cloud, raising electromagnetic compatibility and wireless coexistence obligations under IEC 60601-1-2.
- Skin interface. Adhesives and housings in prolonged skin contact require biological evaluation under ISO 10993-1:2018.
Governing standards run across the whole design. Basic safety and essential performance follow IEC 60601-1, with the home healthcare collateral IEC 60601-1-11:2015 (Amendment 1:2020) applying to body-worn products used outside a clinic. Risk management follows ISO 14971, usability IEC 62366-1, and the quality system ISO 13485. In the U.S., FDA 21 CFR Part 820 has operated as the Quality Management System Regulation aligned with ISO 13485:2016 since February 2026; the EU route runs through EU MDR 2017/745. Connected wearables add cybersecurity work under IEC 81001-5-1.
Common challenges and best practices
The first trap is the wellness boundary. Teams build a sensor-rich wearable, then add a claim that quietly turns it into a regulated device. Lock the intended use and claims early, because they set the entire compliance path.
Signal quality is the next hurdle. A reading accurate on a lab bench can drift once the user is walking, sweating, or sleeping on the sensor. Good programs validate performance across skin tones, activity levels, and real wear conditions, not just ideal ones.
Skin contact over days introduces irritation and sensitization risk, so biocompatibility testing should reflect actual wear duration, not a short-contact assumption. Battery and thermal safety also matter early, since a warm device against skin is both a comfort and a safety concern.
For connected wearables, treat cybersecurity as a design input, not a late add-on: threat modeling, secure updates, and data protection belong in the architecture. Finally, design for a lay user. Human factors work under IEC 62366-1 catches confusing alarms and misuse before they reach a patient.
How SJML helps with wearable medical devices
SJML develops wearable and body-worn devices end to end, from user-needs analysis and electromechanical architecture through embedded software, verification, and design transfer. Electronics, embedded systems, medical PCBA, and sensor integration are handled in-house, with risk management to ISO 14971 and usability engineering to IEC 62366 built into the process. In-house labs support electrical safety and IEC 60601 testing, EMC, and reliability testing. On the compliance side, SJML supports FDA and EU MDR pathways, IEC 62304 software lifecycle work, and cybersecurity risk assessment, so a wearable program can move from concept to market under one roof.
Talk to SJML’s engineering team →
Frequently asked questions
Usually not by default. A general fitness smartwatch that tracks steps or heart rate for wellness falls outside medical device regulation. It becomes a wearable medical device only when a specific function is intended to diagnose or monitor a condition, such as an FDA-cleared ECG or irregular-rhythm feature. The medical claim, not the hardware, triggers regulation.
Core standards include ISO 13485 for the quality system, ISO 14971 for risk management, IEC 60601-1 with the home healthcare collateral IEC 60601-1-11 for electrical safety, IEC 62304 for software, IEC 62366-1 for usability, and ISO 10993-1 for skin biocompatibility. Connected devices add IEC 81001-5-1 for cybersecurity. EU market access runs through the EU MDR 2017/745.
Classification depends on intended use and risk, not form factor. Under EU MDR and FDA rules, a low-risk monitoring wearable may sit in a lower class, while a device that delivers therapy or drives treatment decisions sits higher. A non-invasive product marketed solely for general wellness may not be regulated as a device at all under current FDA policy.
Yes, when they connect to phones, networks, or the cloud. Regulators expect security to be designed in, covering threat modeling, secure software updates, and protection of health data. IEC 81001-5-1 provides the framework for security in the software lifecycle, and both the FDA and the EU MDR require cybersecurity evidence in the submission for connected devices.
Related terms
- Software as a Medical Device (SaMD)
- IEC 62304
- Biocompatibility
- Remote Patient Monitoring
- Usability Engineering (IEC 62366-1)
