Heart Rate Monitoring Apps: Information for Engineers and Researchers About the New European Medical Devices Regulation 2017/745
Bibliographic record
Abstract
Background: After years in the making, on April 5, 2017, the European Parliament and Council finally adopted Regulation (EU) 2017/745, the new Medical Devices Regulation (MDR), repealing the existing Medical Device Directive (MDD) 93/42/EEC. Though long anticipated, this shift in policy will have strong and lasting effects in the medical devices industry. Objective: This paper focuses specifically on the classification of software as a potential medical device under MDD and MDR and examines whether or not the regulatory framework for health apps has changed substantially and what, if any, impact is to expected. A particular emphasis will be on the issue of classification uncertainty raised by borderline cases such as heart rate monitoring and well-being apps. The paper primarily targets researchers and engineers unfamiliar with regulatory requirements for medical devices and aims to provide a concise, yet accurate, overview of the European regulatory framework. This is of particular relevance as with the exponential growth of fitness and health-related apps, the lines between toys, lifestyle products, and medical devices have increasingly blurred. Methods: The recently published European Medical Device Regulation is analyzed and compared to the preceding MDD. Results: The previous regulatory framework already provided for the possibility of apps to fall under the definition of medical devices, in which case classification rules for active medical devices applied. However, while applicability of the new regulatory framework still hinges on whether the intended purpose is medical or not, the threshold for classifying as a medical device has been considerably lowered due to a broader interpretation of what constitutes a medical purpose. Conclusions: The adoption of the new European regulation on medical devices entails the risk that manufacturers previously unaffected by the medical devices regulatory framework may now unwillingly and unwittingly find themselves in the arena of medical device manufacturing.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.050 | 0.143 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.009 | 0.008 |
| Science and technology studies | 0.002 | 0.002 |
| Scholarly communication | 0.010 | 0.014 |
| Open science | 0.002 | 0.004 |
| Research integrity | 0.014 | 0.007 |
| Insufficient payload (model declined to judge) | 0.023 | 0.019 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".