Wearable Devices and Health Apps
❌ The myth: If my wearable device or health app collects data through a smartphone, smartwatch, or fitness tracker, the entire system including the consumer hardware needs CE marking as a medical device
✅ The reality: The regulatory requirements depend entirely on the intended purpose of the software, not the hardware collecting the data. Under the EU MDR, when sensors or data collection components are integrated into finished consumer products (smartphones, tablets, smartwatches, fitness trackers), the consumer hardware itself doesn’t require separate medical device registration or CE marking.
However, if software uses this collected data for medical purposes such as diagnosis, monitoring, prediction, prognosis, or treatment of disease, that software as a medical device (SaMD) must comply with full MDR requirements and bear CE marking before being placed on the EU market.
Critical compliance requirements for SaMD:
- The software must be validated against the specific data collection components and consumer devices it relies on to ensure safety, effectiveness, and fitness for intended purpose
- Validation rigour must match the risk classification: Class IIb or III SaMD used for diagnosing life-threatening conditions requires extensive validation of sensors such as cameras, accelerometers, or photoplethysmography sensors
- The SaMD manufacturer must demonstrate that the combination of software and hardware sensor delivers clinically accurate and reliable results
- Technical documentation must include validation studies showing performance across different hardware configurations if the SaMD is compatible with multiple consumer devices
The regulatory boundary:
The distinction lies in the intended medical purpose, not the technology. A wellness app that displays heart rate, step counts, or sleep patterns for general fitness purposes isn’t classified as a medical device. However, software that diagnoses atrial fibrillation, monitors glucose levels for diabetes management, or detects sleep apnoea using the same smartwatch sensors requires full MDR compliance, risk classification, conformity assessment, and CE marking.
Practical implications:
Manufacturers developing health apps must carefully define their intended purpose and claims. Adding diagnostic or monitoring claims transforms a wellness product into a regulated medical device with substantial compliance obligations. This includes technical documentation, clinical evaluation, post-market surveillance, and potentially Notified Body involvement for higher risk classifications.
→ It’s the software’s intended medical purpose and clinical claims, not the consumer hardware platform, that determines MDR applicability
Bottom line: Consumer hardware remains unregulated, but medical software using that hardware faces full regulatory requirements. Understanding this distinction is crucial for product development strategy, go-to-market timelines, and compliance budgets. The same wearable technology can support both unregulated wellness features and regulated medical functions, but clear separation and appropriate validation are essential.