Abstract
Introduction
The delivery of healthcare to patients utilizing technology can be defined in many ways. The industry in which healthcare technologies contribute to providing such care is one of the largest economies globally. Digital health is commonly used globally and encompasses many technologies, industries and academic and scientific disciplines. The World Health Organization (WHO) defines digital health as using digital technologies to improve health outcomes, efficiency and equity. 1 An extension of this term provides the concept of digital health intervention (DHI), a discrete function of digital health technology that offers a health objective. 2 These concepts are recognized globally and enable a better understanding of industry trends, advances in clinical practice and supporting research on enhancing clinical decision-support (CDS) systems.
To better understand the objectives of this study, we provide a clear and concise definition of the terms used and the associated problem statements under investigation. We also offer a summary of the medical device regulatory industry and regulation to aid in understanding the impact and challenges faced.
Purpose and scope of the document
This deliverable aims to review and categorize DHI use cases and applications. The literature review will provide a classification scheme for further insight into this research project.
Structure of this document
The remainder of this document is organized as follows.
Section “Digital health interventions as medical devices” introduces DHIs as medical devices, including terminologies essential to understanding the analysis undertaken, data analyzed and results. Section “Method” provides the method of analysis for the literature review.
Section “Results” details the analysis results and Section “Discussion” provides discussion and commentary on the findings. The classification of DHIs and use cases presented in graphical form and analysis is comprehensive.
Digital health interventions as medical devices
DHIs that provide a function of general wellness and lifestyle improvements are not typically subject to stringent regulatory requirements to place these products onto the market for general use. Those DHIs that function with specific medical purposes, such as diagnosing, treating or managing disease, are medical devices. 3 Before being placed on the market and used, these products must meet stringent regulatory requirements to ensure their safety and security.
The International Medical Device Regulators Forum (IMDRF) promotes regulatory convergence in the global medical device industry. 3 Many of the strategic aims of the IMDRF are to guide its members in efficient and effective regulatory processes. These strategies provide a consistent approach to regulatory requirements regardless of the country where the products are placed. The European Union (EU) regulates medical devices through the Medical Device Regulation (MDR). There are two regulations, EU MDR 2017/745 and EU MDR 2017/746. These regulations cover medical devices (MD) and in vitro diagnostic devices (IVD). The main difference between these two device types is that the medical devices are used to diagnose, prevent, monitor, treat, or alleviate disease or injury. IVDs are used to perform tests on samples taken from the human body to provide information about a person's health status.
DHIs that diagnose, monitor, treat, or alleviate disease or injury are medical devices. Similarly, testing on samples taken from the human body for health status is an IVD. The definition of a medical device leads to the description of use cases of diagnosis, monitoring and treatment, which are fundamental to this study.
Meeting the regulatory requirements and complying with legislation requires a consistent approach to development by the manufacturer of such medical devices. One characteristic of the regulatory requirements is the concept of harmonized standards. These international standards consider relevant parts of medical device requirements pertinent to the subject under consideration. For example, safety, quality and risk management, usability/human factors, software design and development lifecycle, information security and cybersecurity. These terms may be considered domains to understand their role in certification and meeting legislative requirements.
Any medical device manufacturer's objective is to place products on the market that are safe to use. The safety of the medical device is underpinned by the security of design (vulnerabilities are known and risks mitigated). The domain of usability and alignment with standards in this area ensures the product is developed with human behavior, abilities and limitations incorporated into the design. We define the terms to provide a shared understanding of our research question approach.
Safety = Freedom from unacceptable risk
4
Security = Resistance to intentional or unauthorized act(s) designed to cause harm or damage to a system
5
Usability = Human factors engineering application of knowledge about human behavior, abilities, limitations and other characteristics to the design of medical devices (including software), systems and tasks to achieve adequate usability.
6
Achieving adequate USABILITY can result in acceptable RISK related to use Risk = A combination of the probability of occurrence of harm and the severity of that harm
4
Harm = The injury or damage to the health of people or damage to property or the environment
4
Complying with the medical device regulations requires meeting the legislative requirements with supporting evidence. The evidence is reviewed independently by organizations (notified bodies) with devolved powers provided by the medical device regulators. Assurance activities throughout the development lifecycle of the DHI, from early-stage prototype to final marketable product, utilize this evidence-based approach to compliance.
The risk posed to patients and users by the functionality of these products is classified from low to high. In some regulatory markets, the classification is Class I to III, with I being the lowest risk. In Europe, the classification is Class I, IIa, IIb and III, with Class I being the lowest risk.
The higher the risk classification, the greater the regulatory burden on the manufacturer to provide assurance evidence when placing a safe product on the market.
Software as a medical device utilizes additional classifications of Class A, B and C if the manufacturer adopts one of the harmonized international standards aligned to the software development lifecycle (IEC 62304 Medical device software—Software life cycle processes). 7
With all classes from market placement to software development, the effort to evidence regulatory compliance depends on risk. Higher risk naturally requires additional evidence and greater scrutiny from an assurance perspective.
Medical device registration
Once compliance and certification are achieved, the medical device can be placed on the market. This involves registration using Global Medical Device Nomenclature (GMDN) or European Medical Device Nomenclature (EMDN) codes. These codes are intended to reflect the medical purpose of the device and provide uniform classification and designation of medical devices.
GMDN and EMDN nomenclatures are similar; they are used to register products in the market. They are focused on product identification or categorization after completing the compliance activities. The classification schemes indicate that the intended purpose is incorporated into the coding structure. However, this is not consistently applied to software products such as medical devices and has only post-market certification objectives for safety incident reporting. 8 One challenge we face is the disconnect between medical device class, product classification, and further software development classes that may or may not be applied to the device's development. 9 Classification consistency can directly impact regulatory efforts at many other points in the device's lifecycle, including premarket assurance activities. Knowing the category of product that applies to the manufacturer, and an indication of its intended use, provides an opportunity to standardize assurance approaches for similar products. This benefits regulatory certification and compliance processes positively by creating efficiency, standardization and improvement in the classification schema. These are opportunities to meet the challenges regulators currently face. 10
Artificial intelligence and clinical effectiveness
Artificial intelligence (AI) in digital health involves using complex dynamic algorithms to analyze data. Through AI, DHIs can improve diagnosis and accuracy, predict patient outcomes, personalize treatment plans and improve healthcare delivery. This technology can process vast amounts of data quickly, identify patterns and provide insights that might need to be noticed by human analysis alone. For this study, we use the term machine learning (ML) as a type of AI methodology. 11
We know that medical device product development utilizes product and software risk classes, which help to define the strength of evidence required to demonstrate safety. Current regulatory methods are not standardized, leading to variations in the application of assurance and validation techniques. 12 This problem is linked to the efforts made regarding medical device product nomenclatures (e.g. GMDN and EMDN).
In addition to the technical verification, validating such devices’ clinical effectiveness and appropriateness will require testing them against datasets representing the targeted population. However, this task is challenging, as datasets cannot be shared with manufacturers due to privacy concerns. 13 Even when sharing is possible, the process may take several months. The problem is exacerbated by (a) the fact that datasets need to be produced specifically for each application, depending on its scope, and (b) the increasing volume of DHIs requiring validation. If a manufacturer has access to their datasets, it is easier to perform validation by a third party (e.g. a regulator) with a common dataset. Understanding aspects of the application training is crucial to provide safety assurance of acceptable use of such applications. This may include considering such problems as clinical relevance and specificity of data, the pedigree of data and their evidence base, alignment with the guidelines, data quality (e.g. accuracy and timeliness) and potential biases. This also has implications in the certification process, as each application is often non-standardized, and the stakeholders need more guidance on how to approach assurance, frequently resorting to their internal policy, which needs more EU, professional and international guidance. As a result, this wave of innovation cannot be effectively harnessed, with applications being deployed to patients. It may deprive patients of healthcare improvements and extension of optimum outcomes.
Method
Search strategy details and study criteria
The full search terms used are provided below:
Records must be published in English to be included in the review. The Engineering Village databases, including Compendex and Inspec, PubMed biomedical and life sciences literature, and OVID Embase scientific, medical and healthcare databases, will be used to include articles from the past five years to the present. This will be extended to 10 years if unsatisfactory results are found (low volume of records returned compared to other reviews in this field).
Screening process
Criteria for study inclusion/exclusion
Records must be relevant to the research question for inclusion and selection—articles discussing DHIs and their use cases are critical. We were particularly interested in ontologies recorded in the research literature. Study titles and abstracts have been reviewed, and screening has been performed by the independent reviewer(s). Following this initial screening, a further review of the full articles has been completed. A pictorial representation of the review and selection process has been provided in the review using the PRISMA flow diagram, shown in Figure 1.

PRISMA diagram.
Data extraction, collection and analysis
Data was extracted using a standardized form developed by the research team and piloted on five studies. The following data were systematically extracted: study characteristics (author, year, country, study type), DHI characteristics (type, technology used, terminology/standards), use cases and intended purposes, stakeholder involvement, patient/clinical outcomes, safety, security and usability concerns, regulatory considerations.
The taxonomy was developed through an iterative process: initial categorization based on regulatory definitions, thematic analysis of extracted use cases, stakeholder mapping based on identified roles, relationship mapping between categories and expert review and refinement.
A narrative synthesis approach was employed, supplemented by: frequency analysis of use case categories, stakeholder role mapping, thematic analysis of safety/security concerns, development of visual taxonomy representations, cross-referencing with existing regulatory frameworks (GMDN, EMDN, medical device regulations).
Records from all three databases were extracted in raw format, imported into a recognized reference manager tool, checked for duplicates and then exported into a Microsoft Excel spreadsheet pro forma. Each record was downloaded and reviewed based on the initial inclusion criteria of the DHI subject theme. This provided a set of excluded and included records from which a more detailed review was undertaken. The analysis was completed, and the pro forma contents are highlighted in Table 1.
Data collection definitions.
Results
Paper identification
Using the search method discussed, 1776 papers were identified. Of these, 1735 papers were excluded and 41 were included for review. Duplicates were removed when the three database sources were combined.
The records were found to vary between the following types of articles:
Interrater reliability study (1), journal articles (21), mixed methods study (1), narrative review (1), pre-post study (1), qualitative study (1), scoping review (4) and systematic review (11).
PRISMA paper extraction
The PRISMA flow diagram below, in Figure 1, shows the results of the systematic review:
Publication of articles over time
From the records identified, papers reviewed were published between 2019 and 2024. Articles published in 2019 = 3, 2020 = 7, 2021 = 7, 2022 = 12, 2023 = 10 and 2024 = 2.
Country of study
The records used for this review originate from 22 countries, as outlined in Figure 2. The United States provided the most articles, followed by the UK, Spain and Germany, which each provided three.

Country of study.
Included studies and research focus (digital health intervention)
From the included studies, we present in Table 2 the DHI-led research focus, technology in use, terminology of the use case, or standards in use, and documented level of concern from the study. Where possible, the technology and terminology of the use case have been reported in full. Missing data items not presented in the study are explained as N/A (not available). An examination of this in full is presented in Appendix.
Results—digital health intervention, research focus and level of concern.
Technology distribution analysis shows mobile health technologies are reported in 25 studies, AI software in 8, web-based solutions in 10 and Internet of Things in 4 studies. Primary concerns are the safety of the DHI (14 studies), usability (5 studies) and accuracy (4 studies).
Stakeholder mapping
We considered all stakeholders involved in using each DHI within the studies reviewed. The roles within each stakeholder grouping are presented in Table 3 and are organized to highlight the commonalities among users as presented in the literature. The stakeholders identified in Table 3 provide context when examining the relationships between the four primary stakeholder groups—Manufacturer, Regulator, Patient and Healthcare Professional (incorporating Health Organization, Administrator, Care Giver and Local Authorities).
Stakeholder relationship mapping.
The Manufacturer to Regulator relationship provides context regarding the requirements for regulatory compliance and the demonstration of the DHI's safety. Regulators provide approval of DHI compliance based on evidence to permit products to be placed on the market and monitored for their use. Both stakeholders work within harmonized standards and legislative requirements to demonstrate the compliance of the DHI. At such a time when the DHI is placed onto the market for use, this enables a feedback loop of post-market surveillance to be implemented to provide a mechanism for safety incidents to be reported as and when they occur and assessed periodically.
The relationship between the Manufacturer to Healthcare Professional and others encompasses several distinct actions. Clinical requirements, workflow integration considerations and usability feedback are all provided to the manufacturer during DHI development. A manufacturer may provide training, support and guidance to implement and use the DHIs within the setting in which they are used. Healthcare professionals and others generate real-world evidence-based information on usage, clinical outcomes and safety reports to inform future developments or safety incident analysis.
The relationship between Healthcare Professionals and other patients can be summarized in several ways. The prescribing, recommendation and integration of DHIs into the patient care pathways is a key action. Patients can receive education and guidance on the use and interpretation of outputs from the DHIs. Clinical oversight concerns outcome assessment, management of treatment plans and often professional endorsement.
The Patient to Manufacturer relationship includes direct feedback from a DHI user through forums, app stores and customer support. Patient groups can provide usability feedback during the development of a DHI in prototyping stages. Manufacturers utilize the data collected for regulatory post-market surveillance activities. Finally, safety reporting allows a patient to report adverse DHI events to manufacturers directly.
The Patient to Regulator relationship also includes the reporting of adverse events concerning the use of the DHI within the context of market analysis, incident detection and learning. Clinical trials often incorporate patient feedback through clinical studies for regulatory approval and certification of the DHI. Regulators usually seek public feedback (patient advocacy groups) and consultation on standards, subjects of interest, influencing policy and safety awareness as part of more proactive safety measures.
The Healthcare Professional and others-Regulator relationship concerns the provision of and action of clinical studies for regulatory evidence. Professional and implementation guidance, new use cases and learning from safety incidents are also key actions within this context.
Whilst individual relationships are common, there are multi-stakeholder interactions that impact the quality and safety ecosystem of DHIs, evidence generation, innovation and development lifecycle. This stakeholder mapping demonstrates that the safety of DHIs requires technical innovation and the effective interaction of these relationships throughout the product lifecycle.
Use case, common functions and distribution analysis
The use cases defined in each study were grouped into the standard functions of Diagnosis, Therapeutics, Detection/Measurement and Classification. The classification of DHI from the WHO framework was aligned with each study, together with the technology utilized and the standard functions of the DHI. The use case analysis can be seen in Figures 3 to 6. Figure 3 shows the WHO DHI classification distribution and highlights the eight categories with counts in the literature from the scoping review. Use Case, Common Functions and relationship analysis can be shown in Figure 4. The Use case distribution analysis in Figure 4 reported eight use case patterns, with multi-function DHIs the most common reported in literature at 31%. The Relationship analysis displayed in Figure 5, across the use cases and WHO classification categories, reveals clear patterns indicating that CDS and multi-functional DHIs are the most common. Healthcare Provider Decision Support + multi-function DHI accounts for the most significant percentage of studies examined, at 35.7%. The Technology distribution analysis shown in Figure 6, considers the reported DHI, with most involved mobile health (mHealth) in 31% of the studies analyzed. The functions represented in literature are common legislative terms within medical device regulations and standards.

WHO DHI classification distribution.

Use case distribution.

Use case, common functions and relationship analysis.

Technology distribution analysis.
Intended use and patient/clinical outcome
To reaffirm the use case and standard functions, we examine the intended use and outcome (patient or clinical) for each DHI under review, shown in Table 4. The focus of the study, along with its objectives, accounts for the missing data. We can see from the results that the use cases of Therapeutic, Detection/Measurement, Diagnosis, and Classification are common. This is as expected. Similar patient/clinical outcomes have been removed as they duplicate the confirmed outcome.
Intended use and patient/clinical outcome.
Discussion
Quality improvement of DHIs
The benefits of utilizing complex algorithmic decision-making have been reported within the review, as well as in our introduction and research objectives. 14 Confirmation of manual processing of interventions being improved by these technologies. Quality improvements are noted, in particular, by the recommendation from the Canadian Association of Radiologists—Developers should define the healthcare needs addressed by their software (e.g. quality of radiological care, healthcare network integration, patient perspective, employee experience, efficiency and costs), the applicable clinical domain (e.g. mammography and chest radiograph) and task (e.g. breast density evaluation and pneumothorax detection) and describe the expected positive impact on these needs and patient outcomes. 15 These additional factors reported in the literature provide a compelling argument that DHIs incorporating AI and more innovative technologies improve interventions. The operational aspects of implementing DHIs require consideration of the intended purpose, and a lack of experience or understanding of potential complex CDS systems. 16 Frameworks focusing on the design principles of reusability, reliability, privacy, versatility and testability provide the infrastructure to develop high-quality mobile health applications. 17 These principles underpin safety requirements.
Classification of digital health interventions
Our findings align with and extend previous classification efforts. The WHO Digital Health Intervention Classification 1 provides a broad categorization framework but lacks the detailed use case specificity identified in our review. Similarly, the NICE Evidence Standards Framework 14 focuses on evidence requirements and lacks the taxonomic structure our study develops. Our identification of four primary use cases (Diagnosis, Detection/Measurement, Classification, Therapeutics) aligns with medical device regulatory categories. It provides more granular DHI-specific detail than existing frameworks like GMDN coding systems.
The stakeholder mapping (patients, healthcare professionals, manufacturers, regulators) reflects the multi-stakeholder nature of digital health ecosystems identified in previous work by [relevant citations]. Still, our study uniquely maps these relationships to specific use cases.
From the studies reviewed, we find helpful insight into the classification of DHIs, extended from workflow design and behavioral change intervention of mobile applications. 18 Within this are intervention descriptors, use case definitions and stakeholders. The hierarchy of digital technology is assessed to enhance tuberculosis control, 19 collaborates with the hierarchy of AI-based technologies in the previously discussed behavioral change study. The terminology used to assess DHIs utilized during the COVID-19 pandemic (Digital Health MeSH Descriptor Data 2024) also provides a consolidated yet not fully elaborated view of terms used that synergize with classification structures. 20
Terminologies and definitions are critical when defining any form of taxonomy or ontology. Our research has included many different DHIs using the following definitions:
Digital Health—Systematic application of information and communications technologies, computer science, and data to support informed decision-making by individuals, the health workforce and health systems to strengthen resilience to disease and improve health and wellness. 1
Digital Health Intervention—a discrete functionality of digital technology that is applied to achieve health objectives. 2
Health System Challenge—A generic need or gap that reduces the optimal implementation of health services. 2
Intended Use or Purpose—The use for which the device is intended according to the data supplied by the manufacturer. 3
Use Cases have been defined for Diagnosis, Detection/Measurement, Classification and Therapeutics. Stakeholders are categorized as Manufacturers, Healthcare Professionals, Patients and Regulators. Both categories are derived from this study.
The taxonomy mapping of the data available through our study is provided in Figure 7. This highlights the relationship to the broader term of digital health and follows international standards, industry guidelines and best practice.21–25

Taxonomy of digital health technologies.
Focusing on use cases, stakeholders and health system challenges, we examine the features in Figure 8, between these terms, to demonstrate the one-to-many and many-to-many relationships.

Use cases, stakeholders and DHI taxonomy.
Use case and intended purpose
The intended use or purpose of a medical device is a defined term used to describe the use of the product.26–28 The stakeholder analysis from this study provides four personas of technology users: patient, healthcare professional, manufacturer and regulator. These personas can be used in conjunction with their intended use and use case, as shown in Figure 8. This relationship and taxonomy are a precursor to the classification scheme.
Harmonization of ICF Body Structures and ICD-11 Anatomic Detail improves the quality of classification of DHIs. There is potential to align this classification scheme with the intended use/purpose and instructions for use statements for medical devices. 29 Using structured languages and natural language processing allows for automation in device classification and many parts of the regulatory certification process.
Medical device nomenclature and coding schemes
Medical device nomenclatures are key to product placement and post-market analysis. These coding structures can be linked to the taxonomy offered in this study by using the product term name and definition9,10 to align with the digital technology term used in this study. The quality of medical device coding post-certification (in use) is not consistent in both the terminology and post-market incident reporting. 30 Adverse event reporting is expected to be simpler to analyze due to the coding schemas offered to manufacturers. Efforts to consolidate coding schemas and provide improved clarity on intended use versus the type of medical device certified would be beneficial.
Policy and practical implications
As illustrated in Figure 8, the taxonomy developed has the potential to support more consistent DHI classification across regulatory legislation, standards and address the inconsistencies in medical device nomenclature frameworks. This provides the advantages of improving regulatory harmonization. From the software development lifecycle (focus of the scoping review), manufacturers could utilize the framework better to align DHI development with the requirements for regulatory and use case objectives. Healthcare professionals and included stakeholders could benefit from clarity in the classification to support the selection, implementation and adoption of DHIs into clinical workflows.
From the perspective of evidence generation to support regulatory requirements, the framework could guide stakeholders to the appropriate level of evidence for the DHI classification, based on risk and safety classification. Finally, from an interoperability perspective, standardization in classification would facilitate improvements in health system integration with extensions of functionality consistent with information exchange.
Limitations and further work
This scoping review provides a preliminary framework for classifying DHIs based on use cases, stakeholder involvement and regulatory considerations. While the proposed taxonomy offers a structured approach to understanding DHI complexity, several limitations should be acknowledged. This includes considerations on the interpretation of the results. While comprehensive, the search was limited to three databases and may have missed relevant studies in specialized repositories. The inclusion of English-only publications may have excluded relevant international perspectives. The scoping review focused on published literature and may have missed grey literature or unpublished findings. Temporal Limitations: The 5-year search window, while capturing recent developments, may have excluded foundational work in DHI classification. The diverse nature of the included studies (different methodologies, DHI types and outcomes) limited quantitative synthesis. The proposed taxonomy has not been externally validated with stakeholder groups. The classification system, derived from 41 studies primarily from high-income countries, may not fully represent the global DHI landscape. The framework requires validation with broader stakeholder groups and testing across different healthcare contexts before widespread implementation. The identification of four primary use cases (Diagnosis, Detection/Measurement, Classification, Therapeutics) and four stakeholder categories provides a foundation for future classification efforts. Still, the relationships between these categories need further empirical validation. The method of hazard assessment, analysis and use of ontologies shows promise for improving safety claims and evidence articulation in DHIs; additional research would establish the effectiveness across different DHI categories and regulatory contexts. Further research to develop the effectiveness of the proposed taxonomy through external validation, consideration of extending to other DHI areas such as social and community care, integration with regulatory frameworks and the development of assessment/assurance tools based on the classification taxonomy.
Conclusion
The scoping review has enabled a classification and taxonomy for DHIs to be developed. The development has incorporated use cases, stakeholders and regulatory considerations, which to date have not been published in literature, nor has the relationship between these terms been explored. The systematic analysis of 41 studies identified four primary use cases that align with medical device regulatory requirements and terminologies: Diagnosis (
The taxonomy offered in this scoping review addresses gaps in the classification of DHIs by the provision of the following:
Standard Use Case Categories: representing DHI functions that align with regulatory terminology and intended use Stakeholder Mapping: four groups identified (patients, healthcare professionals, manufacturers and regulators), including the relationships between each stakeholder Regulatory standards alignment: The review provides insight into a framework to connect medical device classification with use cases and health system challenges.
The scoping review shows that the most common category of DHIs is those that are multi-functional (31% of studies), from the literature. This confirms the evolution of health software towards more integrated care solutions and services. It should not be understated that the predominance of mobile health technologies represents an ever-growing emphasis on patient-centred care and accessible DHIs.
The practical implications for stakeholders are many. Manufacturers may use the taxonomy for guiding through often complex regulatory requirements, thereby enabling an efficient, effective and consistent pathway to market beyond safety claims being made. For Healthcare professionals, the increased clarity on DHI selection, implementation and alignment with clinical workflows provides an additional advantage from a quality, healthcare planning and improvement in patient outcomes perspective. Finally, regulators may utilize the taxonomy and classification alignment to support consistency in the classification and evidence-based assessment of DHIs.
The scoping review is not without limitations. External validation with additional stakeholders, consideration of other healthcare systems beyond the initial WHO classification scheme (for example, social and community care), before implementation. Further work will focus on the validation of the classification scheme and extending it into social and community care. This validation will enable the development of a more practical assessment-based tool and process based on the taxonomy. This research contributes to a broader objective of enhancing DHI innovation by providing a structured approach (harmonized and evidence-based) to the complexity of DHI use case development within a challenging regulatory environment.
