Digital Therapeutics Regulatory Framework: FDA Pathways and Evidence Requirements
"Digital therapeutics" is an industry term generally used for software-based interventions intended to prevent, manage, or treat disease. FDA does not maintain a separate DTx pathway; these products are regulated under the existing medical device framework for software functions when they meet the device definition. Depending on the intended use and available predicate history, the relevant pathway may be 510(k), De Novo, or, for higher-risk products, PMA. Evidence expectations depend on the device's intended use, risk, and claims.
Key Takeaways
Key Takeaways
- DTx are regulated as SaMD under the existing FDA device framework — there is no distinct DTx regulatory pathway.
- Novel software therapeutics often use De Novo when no predicate exists, and later products in the same classification may be eligible for 510(k), but pathway selection remains device-specific.
- FDA requires clinical trial evidence (typically RCTs) demonstrating therapeutic benefit, with evidence rigor scaled to risk profile and intended use claims.
- Patient engagement is a unique regulatory factor for DTx — effectiveness depends on adherence, which may differ between clinical trial and real-world settings.
Defining Digital Therapeutics
The Digital Therapeutics Alliance (DTA), an industry association, published a definition framework that has become the standard industry reference. Under the DTA framework:
Digital Therapeutics (DTx): Software-based interventions that deliver evidence-based therapeutic interventions to patients. DTx are used to prevent, manage, or treat a medical disorder or disease. They incorporate design, clinical evidence, usability, and data security as part of product development and regulatory clearance.
This definition distinguishes DTx from:
- Digital health: Broad category encompassing all health-related technology (telemedicine, EHR, wearables, wellness apps)
- Digital medicine: Measurement and intervention tools that are evidence-based but may not deliver treatment directly (e.g., medication adherence sensors)
- Digital wellness: Applications promoting general health without treating specific medical conditions (fitness trackers, meditation apps)
Key Characteristics of DTx
| Characteristic | Requirement |
|---|---|
| Evidence-based therapeutic intervention | Clinical trial evidence supporting efficacy |
| Treats, manages, or prevents a specific condition | Clear medical indication |
| Regulatory clearance or approval | FDA clearance/approval as a medical device |
| Real-world outcome data | Ongoing evidence collection |
| Quality and safety claims in labeling | Subject to regulatory enforcement |
| Professional oversight (prescription DTx) | Prescribed or ordered by healthcare provider |
Prescription vs Non-Prescription DTx
Prescription Digital Therapeutics (PDTs): Require authorization by a licensed healthcare provider, analogous to prescription drugs. The patient accesses the DTx through a prescription workflow, and the healthcare provider monitors treatment. FDA regulates these as prescription-use medical devices under 21 CFR 801.109.
Non-Prescription DTx: Available to patients without a healthcare provider's order. These may still be regulated as medical devices if they make diagnostic or therapeutic claims, but the distribution model does not require a prescription. FDA regulates these as over-the-counter (OTC) devices.
FDA Regulatory Framework for DTx
FDA does not have a distinct regulatory pathway for digital therapeutics. DTx are regulated as Software as a Medical Device (SaMD) under the existing device classification and premarket review framework. The applicable regulations, guidance documents, and review processes are the same as those for any other SaMD.
Applicable FDA Regulatory Framework
| Regulatory Element | Application to DTx |
|---|---|
| Device definition | Section 201(h) FD&C Act |
| Classification | Section 513 FD&C Act (Class I, II, or III) |
| Premarket review | 510(k), De Novo, or PMA |
| Quality system | 21 CFR Part 820 (QSR) |
| Labeling | 21 CFR Part 801 |
| Medical device reporting | 21 CFR Part 803 |
| Registration and listing | 21 CFR Part 807 |
| Software documentation | "Content of Premarket Submissions for Device Software Functions" (2023) |
| Cybersecurity | "Cybersecurity in Medical Devices" (2023) |
Primary Regulatory Pathways
De Novo Classification Request: Often used for novel software therapeutics that do not have a suitable predicate device. If FDA grants a De Novo request, that classification can later serve as the predicate basis for eligible 510(k) submissions.
510(k) Premarket Notification: Available when a legally marketed predicate device (typically a prior De Novo decision) exists with substantially equivalent intended use and technological characteristics.
PMA Premarket Approval: Required for Class III software devices. Whether a software therapeutic would require PMA depends on its classification and risk profile, not on the "DTx" label alone.
Clinical Evidence Requirements
FDA's Expectations for DTx Clinical Evidence
FDA evaluates DTx clinical evidence requirements based on the IMDRF SaMD clinical evaluation framework and the specific intended use claims. The level of evidence required depends on:
- Risk classification: Higher-risk DTx require more rigorous clinical evidence
- Nature of the therapeutic claim: Treatment claims require stronger evidence than management or informational claims
- Patient population: Vulnerable populations (pediatric, psychiatric) may require additional evidence
- Comparator: Claims of superiority or equivalence to existing treatments require comparative data
Evidence Hierarchy for DTx
| Claim Type | Typical Evidence Required | Study Design |
|---|---|---|
| Treatment of disease/disorder | Randomized controlled trial (RCT) | Parallel-group, active or sham control |
| Adjunct to standard of care | RCT demonstrating added benefit | DTx + SOC vs SOC alone |
| Symptom management | RCT or well-designed observational study | May accept patient-reported outcomes |
| Prevention | RCT with adequate follow-up | Prospective, may require large sample |
| Monitoring/tracking | Performance testing, clinical validation | May not require RCT |
Clinical Trial Design Considerations for DTx
Control Group Selection:
DTx clinical trials face unique challenges in control group design. Unlike drug trials where a placebo pill is physically identical to the active treatment, DTx interventions are interactive software experiences that are difficult to blind.
Common control strategies:
| Control Type | Description | Advantages | Limitations |
|---|---|---|---|
| Waitlist control | Control group receives DTx after study period | Simple, ethical | No blinding, nocebo/placebo effects uncontrolled |
| Sham DTx | Control group receives similar app without active therapeutic content | Better blinding | Difficult to create convincing sham, expensive |
| Active comparator | Control group receives standard of care (e.g., in-person CBT) | Clinically relevant | Non-inferiority design may require large sample |
| Treatment as usual (TAU) | Both groups continue standard care; intervention group adds DTx | Pragmatic | Unblinded, contamination risk |
Endpoints:
DTx trials typically use patient-reported outcome (PRO) measures as primary endpoints. FDA's guidance "Patient-Reported Outcome Measures: Use in Medical Product Development to Support Labeling Claims" (December 2009) applies. Key considerations:
- The PRO instrument must be validated for the target condition
- Clinically meaningful change thresholds must be pre-specified
- Electronic data capture (ePRO) is standard for DTx trials
- Engagement metrics (app usage, session completion) are typically secondary endpoints
Engagement and Adherence:
DTx are unique among medical devices in that therapeutic effect depends on patient engagement with the software. FDA evaluates:
- How the DTx maintains patient engagement
- What happens when patients do not complete the prescribed course
- Whether efficacy results apply to per-protocol or intent-to-treat populations
- How the DTx addresses non-adherence within the product design
Post-Market Evidence Requirements
FDA may impose post-market requirements through Special Controls (for Class II devices) or post-approval studies (for PMAs). For DTx, common post-market requirements include:
- Real-world evidence (RWE) collection on therapeutic outcomes
- Software performance monitoring (algorithm accuracy, uptime)
- Adverse event reporting under 21 CFR Part 803
- Periodic reporting on patient engagement metrics
The De Novo Process for DTx
The De Novo classification request is the primary pathway for novel DTx and merits detailed discussion.
De Novo Submission Components for DTx
| Section | Content |
|---|---|
| Device description | Software architecture, therapeutic mechanism, user interaction model |
| Intended use / Indications for use | Target condition, patient population, use environment, prescription/OTC |
| Classification recommendation | Proposed class (typically Class II) and rationale |
| Special controls | Proposed special controls (performance testing, labeling, post-market) |
| Non-clinical testing | Software verification and validation, cybersecurity testing, human factors |
| Clinical evidence | RCT data demonstrating therapeutic benefit |
| Labeling | Proposed labeling including contraindications, warnings, directions for use |
| Software documentation | Per "Content of Premarket Submissions for Device Software Functions" |
| Cybersecurity | Per "Cybersecurity in Medical Devices" guidance |
Special Controls for DTx
When FDA grants a De Novo classification, it issues a De Novo order that includes Special Controls. These become binding requirements for the product and serve as the predicate standard for future 510(k) submissions. Typical DTx Special Controls include:
Clinical Performance Testing:
- Clinical study demonstrating safety and effectiveness in the intended population
- Pre-specified primary endpoint using a validated PRO measure
- Adequate sample size and study duration
Software Requirements:
- Software verification and validation per FDA's software guidance
- Cybersecurity documentation and SBOM
- Software update and maintenance procedures
Labeling Requirements:
- Prescription use statement (for PDTs)
- Contraindications and warnings based on clinical trial exclusion criteria
- Description of the therapeutic mechanism
- Summary of clinical evidence
- Patient/caregiver instructions for use
Human Factors:
- Usability testing demonstrating that the intended user population can use the DTx safely and effectively
- Accessibility considerations
De Novo Review Milestones
| Phase | Timing | Activity |
|---|---|---|
| FDA acceptance review | 15 calendar days | FDA determines whether the request is administratively complete |
| FDA substantive review | 150 FDA review days | Technical review, including any Additional Information cycle |
| De Novo decision | - | Grant, decline, or withdrawal |
Enforcement Discretion and the Digital Health Policy
FDA has exercised enforcement discretion for certain low-risk digital health products, meaning the agency has chosen not to enforce device regulatory requirements even though the products technically meet the device definition.
COVID-19 Enforcement Discretion
During the COVID-19 public health emergency, FDA issued multiple enforcement discretion policies relevant to DTx:
- "Enforcement Policy for Digital Health Devices for Treating Psychiatric Disorders During the Coronavirus Disease 2019 (COVID-19) Public Health Emergency" (April 2020): Allowed certain DTx for psychiatric conditions to be marketed without FDA clearance during the emergency
- This enforcement discretion was time-limited and ended when the public health emergency declaration was terminated
General Enforcement Discretion Policy
FDA's guidance "Policy for Device Software Functions and Mobile Medical Applications" describes categories of device software functions for which FDA intends to exercise enforcement discretion. These include software that:
- Helps patients self-manage their disease or condition without providing specific treatment or treatment suggestions
- Provides simple tools to organize and track health information
- Provides access to peer-reviewed literature or clinical practice guidelines
Enforcement discretion is a policy decision, not a legal determination. Products subject to enforcement discretion are still technically medical devices and could be subject to FDA oversight if the agency changes its policy.
Reimbursement Considerations
While reimbursement is not a regulatory requirement, it is a critical commercial consideration that influences regulatory strategy for DTx.
Current Reimbursement Landscape
| Payer Type | Reimbursement Status | Mechanism |
|---|---|---|
| Medicare | Limited coverage, case-by-case | HCPCS codes, CMS coverage determinations |
| Commercial insurers | Selective coverage, growing | Pharmacy benefit, medical benefit, or carve-out |
| Employers | Direct contracting | Self-insured employer benefit programs |
| Medicaid | State-by-state | Varies by state Medicaid program |
CPT and HCPCS Codes for DTx
The American Medical Association (AMA) established CPT codes for remote therapeutic monitoring (RTM) in 2022:
- CPT 98975: Remote therapeutic monitoring, initial setup and patient education
- CPT 98976: Remote therapeutic monitoring, device supply (respiratory system)
- CPT 98977: Remote therapeutic monitoring, device supply (musculoskeletal system)
- CPT 98980: Remote therapeutic monitoring treatment management services, first 20 minutes
- CPT 98981: Remote therapeutic monitoring treatment management services, each additional 20 minutes
Additionally, CMS created HCPCS codes for specific DTx products on a case-by-case basis. The coverage landscape remains fragmented, and DTx manufacturers typically need to negotiate coverage with individual payers.
Regulatory Strategy Implications
Reimbursement considerations can influence regulatory strategy in several ways:
- Prescription vs OTC designation: Prescription DTx have more established reimbursement pathways through pharmacy and medical benefits
- Clinical trial design: Payers may require specific outcomes data (e.g., healthcare utilization reduction, medication reduction) beyond what FDA requires
- Comparative effectiveness: Payers often want evidence comparing DTx to standard of care, not just placebo
- Health economics data: Cost-effectiveness analyses are increasingly expected by payers, even though FDA does not require them
Challenges and Emerging Issues
Therapeutic Mechanism Validation
Unlike drugs with defined pharmacological mechanisms, DTx therapeutic mechanisms (cognitive behavioral therapy, psychoeducation, biofeedback) can be difficult to isolate and validate. FDA expects manufacturers to articulate the therapeutic mechanism and provide evidence that the software-delivered intervention produces the claimed therapeutic effect.
Patient Engagement as a Regulatory Factor
DTx effectiveness depends on patient engagement. A DTx that works well in a clinical trial with monitored adherence may perform differently in real-world use where patients may not complete sessions, may use the product inconsistently, or may stop using it entirely. FDA may consider engagement design and real-world adherence data as part of the regulatory review.
Software Updates and the PCCP Framework
DTx, like all SaMD, may need frequent software updates. The Predetermined Change Control Plan (PCCP) framework allows DTx manufacturers to describe planned modifications in their premarket submissions. For DTx, relevant PCCP-covered changes might include:
- Updates to therapeutic content (e.g., adding new CBT modules)
- Algorithm modifications that adjust treatment personalization
- User interface changes that improve engagement
- Expansion to additional device platforms
Changes outside the authorized PCCP scope require a new premarket submission.
Key Regulatory References
| Document | Source | Year |
|---|---|---|
| Digital Therapeutics Definition and Core Principles | Digital Therapeutics Alliance | 2019 |
| Policy for Device Software Functions and Mobile Medical Applications | FDA | 2019 (updated 2022) |
| Patient-Reported Outcome Measures: Use in Medical Product Development | FDA | 2009 |
| Content of Premarket Submissions for Device Software Functions | FDA | 2023 |
| Cybersecurity in Medical Devices | FDA | 2023 |
| Marketing Submission Recommendations for a PCCP for AI-Enabled Device Software Functions | FDA | 2025 |
| De Novo Classification Process (Evaluation of Automatic Class III Designation) | FDA | 2021 |
| IMDRF SaMD Key Definitions (N10) | IMDRF | 2013 |
| IMDRF SaMD Risk Categorization (N12) | IMDRF | 2014 |
References
Sources
- Digital Therapeutics Alliance: Digital Therapeutics Definition and Core Principles
- Policy for Device Software Functions and Mobile Medical Applications | FDA
- Patient-Reported Outcome Measures: Use in Medical Product Development to Support Labeling Claims | FDA
- Content of Premarket Submissions for Device Software Functions | FDA
- Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions | FDA
- Marketing Submission Recommendations for a Predetermined Change Control Plan for Artificial Intelligence-Enabled Device Software Functions | FDA
- De Novo Classification Process (Evaluation of Automatic Class III Designation) | FDA
- Software as a Medical Device (SaMD): Key Definitions | IMDRF
- Software as a Medical Device: Possible Framework for Risk Categorization and Corresponding Considerations | IMDRF