Digital Therapeutics Program Lead Tools Guide: Evidence, Regulation, Engagement and a Step-by-Step Workflow
A Digital Therapeutics Program Lead guides the team that turns a clinically validated software intervention into a safe, regulated and widely used treatment. This guide covers the key tools, frameworks and standards, plus a clear workflow from clinical claim to post-market monitoring.
- What a Digital Therapeutics Program Lead does
- Tool landscape at a glance
- What makes a digital therapeutic different
- Regulatory and quality references
- Intervention design frameworks
- Evidence and study design tools
- Data capture and trial platforms
- Outcome measures
- Engineering tools
- Engagement and analytics tools
- Wearables and remote data
- Privacy and security references
- Programme management tools
- Step-by-step workflow
- FAQs
What a Digital Therapeutics Program Lead Does
This role combines programme management, clinical development and regulatory strategy. Typical responsibilities include:
- Defining the indication, intended use and clinical claims
- Coordinating clinical, regulatory, engineering, data science and commercial teams
- Planning clinical studies and evidence for regulators and payers
- Managing quality, risk, budget and timelines
- Overseeing vendors, such as research organisations and development partners
- Tracking engagement, outcomes and safety after launch
Tool Landscape at a Glance
SaMD and quality systems
Behaviour change models
Trials and outcomes
Apps and integrations
Analytics and messaging
Security and compliance
Chart: number of entries listed in each category of this guide. It is not a popularity ranking.
What Makes a Digital Therapeutic Different
- Clinical claim: it aims to prevent, manage or treat a medical condition, not only to support wellness.
- Evidence: claims are usually supported by clinical studies, often randomised controlled trials.
- Regulation: many products are regulated as software as a medical device (SaMD), depending on intended use and region.
- Engagement matters: a treatment only works if patients keep using it as intended.
- Ongoing change: updates to content or algorithms need change control and sometimes regulatory review.
Regulatory and Quality References
| Reference | Purpose |
|---|---|
| FDA digital health guidance | US expectations for software functions, premarket submissions and cybersecurity |
| EU MDR Rule 11 | Classification rule that applies to medical device software |
| IMDRF SaMD framework | International thinking on software as a medical device |
| ISO 13485 | Quality management system for medical devices |
| ISO 14971 | Risk management for medical devices |
| IEC 62304 | Software lifecycle processes |
| IEC 62366-1 | Usability engineering |
| DiGA fast-track (Germany) | Pathway for prescribable digital health applications reviewed by BfArM |
Intervention Design Frameworks
- COM-B and the Behaviour Change Wheel: understanding capability, opportunity and motivation behind behaviour.
- Behaviour Change Technique Taxonomy: a standard list of techniques for describing intervention content.
- Person-Based Approach: shaping the intervention with patients’ views and needs.
- MRC framework for complex interventions: guidance on developing, testing and evaluating interventions.
Include patients and clinicians in co-design so the programme fits real life and care pathways.
Evidence and Study Design Tools
| Resource | Purpose |
|---|---|
| CONSORT-EHEALTH | Reporting guidance for trials of web and mobile health interventions |
| SPIRIT | Checklist for writing clinical trial protocols |
| ClinicalTrials.gov | Registering studies and searching existing ones |
| NICE Evidence Standards Framework | UK framework describing evidence expected for digital health technologies |
| GRADE | Rating the certainty of a body of evidence |
Choose clinically meaningful endpoints, a suitable control (such as sham or standard care) and a pre-specified analysis plan.
Data Capture and Trial Platforms
| Tool | Typical use |
|---|---|
| REDCap | Flexible research data capture, widely used in academic studies |
| Medidata Rave | Electronic data capture for regulated clinical trials |
| Castor EDC | Cloud data capture for clinical research |
| OpenClinica | Electronic data capture and clinical data management |
Outcome Measures
- PROMIS: patient-reported measures across many health areas.
- PHQ-9 and GAD-7: short questionnaires for depression and anxiety symptoms.
- EQ-5D: a generic measure of health-related quality of life.
- System Usability Scale: quick measure of perceived usability.
- Engagement and adherence measures: sessions completed, retention and use as prescribed.
Check licence terms and validation status of each questionnaire for your population and language.
Engineering Tools
| Tool | Typical use |
|---|---|
| React Native | Cross-platform mobile apps |
| Flutter | Cross-platform apps from one codebase |
| Swift and Kotlin | Native iOS and Android development |
| Apple HealthKit | Reading health data on iOS with user permission |
| Android Health Connect | Sharing health data between Android apps |
| HL7 FHIR | Exchanging data with EHRs and clinical systems |
Keep requirements traceability and design controls in line with your quality system.
Engagement and Analytics Tools
- Amplitude and Mixpanel: product analytics for journeys, retention and feature use.
- Braze: customer messaging across push, email and in-app channels.
- OneSignal: push notification delivery.
- Metabase: dashboards and SQL reporting.
Confirm whether each tool can handle health data and whether a business associate agreement or equivalent contract is available. Avoid sensitive details in notifications.
Wearables and Remote Data
- Validic: aggregating data from many wearable and health devices.
- Garmin Health API: access to data from Garmin devices.
- Oura API: access to sleep and readiness data from Oura users.
- Bluetooth Low Energy: the standard wireless link used by many sensors.
Validate that consumer device data is accurate enough for your intended use before relying on it for clinical decisions.
Privacy and Security References
| Reference | Purpose |
|---|---|
| HIPAA | US privacy and security rules for protected health information |
| GDPR | EU data protection law |
| FTC Health Breach Notification Rule | US rule that can apply to health apps not covered by HIPAA |
| SOC 2 | Audit report on security and related controls |
| HITRUST | Certifiable security framework used in healthcare |
| ISO/IEC 27001 | Information security management standard |
| OWASP MASVS | Security verification standard for mobile apps |
Programme Management Tools
- Jira and Asana: task tracking across engineering and operations.
- Smartsheet: timelines, budgets and resource planning.
- Confluence: shared documentation and decisions.
- Greenlight Guru: design controls and quality records for medical devices.
Use stage gates with clear criteria, such as clinical readiness, regulatory readiness and commercial readiness, and keep a risk and issue log.
Step-by-Step Workflow
- Define indication and claim. Specify the condition, patients, intended use, endpoints and what the product claims to do.
- Design the intervention. Use a behaviour change model, co-design with patients and clinicians, and write clear content and rules.
- Set regulatory path and quality system. Determine SaMD classification, choose the market route and put design controls and risk management in place.
- Build the product. Develop a secure app with data capture, integrations and engagement features, with traceability and testing.
- Generate evidence. Run pilot and pivotal studies, register and pre-specify them, and report using CONSORT-EHEALTH.
- Submit and launch. Complete regulatory submissions, prepare payer and health-system evidence, and onboard clinicians and patients.
- Monitor and improve. Track engagement, outcomes and safety, run post-market surveillance and manage every update through change control.
Chart: the seven workflow steps shown with equal weight. Real effort varies by programme.
Checklist and Common Mistakes
- Claim: is the intended use clear and supported by evidence?
- Evidence: are endpoints meaningful and pre-specified?
- Engagement: will patients realistically use it as intended?
- Change control: are updates assessed for safety and regulatory impact?
Frequently Asked Questions
1. What does a Digital Therapeutics Program Lead do?
They lead the programme that develops, validates, regulates and launches a software-based treatment, coordinating clinical, regulatory, technical and commercial work.
2. How is a digital therapeutic different from a wellness app?
A digital therapeutic makes a medical claim, such as treating or managing a condition, and is supported by clinical evidence. Wellness apps generally do not make such claims.
3. Do digital therapeutics need regulatory approval?
Many do, as they may be regulated as software as a medical device. The route depends on intended use, claims and country, so regulatory advice is important.
4. What evidence is usually needed?
Regulators and payers often expect clinical studies with meaningful endpoints, commonly randomised controlled trials, along with usability, safety and real-world engagement data.
5. Why is engagement so important?
The therapeutic effect depends on patients using the programme as intended. Low engagement can weaken results, so teams track adherence and design for ongoing use.
Conclusion
A strong digital therapeutics programme links a clear clinical claim, a well-designed intervention, rigorous evidence, quality systems and privacy protection. Plan regulation early, measure engagement and outcomes and manage every change carefully. Always confirm current regulations, standards and product details in official sources.
