Prioritizing product features for a digital health startup requires balancing the speed pressure of a startup with the safety, regulatory, and clinical workflow constraints of the healthcare industry — where a poorly prioritized feature can harm users or violate compliance requirements.
According to Lenny Rachitsky on Lenny's Podcast, digital health is one of the most complex product domains because the person who pays for the product (insurer, employer), the person who prescribes it (clinician), and the person who uses it (patient) are three completely different stakeholders — each with distinct needs.
According to Gibson Biddle on Lenny's Podcast, in highly regulated industries the product strategy question shifts from 'what delights users' to 'what delights users within the constraints of compliance' — and the constraints often become the moat.
According to Chandra Janakiraman on Lenny's Podcast, the best digital health products don't try to replace clinical workflows — they enhance them. The PM's job is to find where the digital product creates leverage for the clinician, not friction.
The Unique Challenges of Digital Health Feature Prioritization
Digital Health Product: A software application designed to help individuals manage health, support clinical care delivery, or improve health system efficiency — subject to varying levels of FDA oversight depending on clinical risk.
Digital health startups must navigate:
- FDA Software as a Medical Device (SaMD) classification: Features that diagnose, treat, or monitor clinical conditions require FDA clearance (510k) or approval
- HIPAA compliance: Any feature handling Protected Health Information (PHI) requires privacy and security reviews before shipping
- Clinical validation: Health outcomes claims require evidence — often from IRB-approved studies
- Clinician adoption: EHR integration, workflow fit, and billing code support often determine clinical adoption more than product quality
- Patient safety guardrails: Features that could cause patient harm through incorrect information or missed alerts are zero-tolerance
The Digital Health Feature Prioritization Matrix
Score each feature across five dimensions:
1. Patient Impact Score (1-5): Direct improvement in health outcomes, quality of life, or safety
2. Regulatory Risk Score (1-5 inverse): Features requiring FDA clearance score lower; features below FDA threshold score higher
3. Clinician Workflow Fit (1-5): Does this slot naturally into clinical workflows, or does it require behavior change?
4. Payer/Employer Value (1-5): Does this generate CPT billing codes, reduce hospitalizations, or improve HEDIS measures?
5. Engineering Cost (1-5 inverse): Time and complexity to build
Priority Score = (Patient Impact × Clinician Fit × Payer Value) / (Regulatory Risk × Engineering Cost)
Prioritization Rules for Digital Health
Rule 1: Patient Safety Is a Hard Override
Any feature that could cause harm through incorrect clinical information, missed alerts, or poor dosage guidance is categorically deprioritized until it has been clinically validated and reviewed by a licensed clinician or medical officer.
Rule 2: Separate SaMD from Wellness Features
Keep a clear line between features that make clinical claims (SaMD, requiring FDA path) and wellness features (not making clinical claims). Mixing them accidentally extends FDA review timelines.
Rule 3: EHR Integration Unlocks Clinician Adoption
A feature that requires clinicians to leave their EHR to use your product will have 10× lower adoption than one embedded in the EHR workflow. EHR integrations (Epic, Cerner) are high-effort but disproportionately high-value.
Rule 4: Prioritize Reimbursable Features
Features that map to CPT codes (Remote Patient Monitoring, Chronic Care Management, Digital Therapeutics) generate immediate revenue for health systems — and health systems adopt products that fit their billing model.
Step-by-Step Prioritization Process for Digital Health
- Classify every candidate feature as: Patient Safety (P0), Clinical Workflow, Consumer Health, or Operational
- Complete the FDA risk assessment for clinical features — consult regulatory counsel for anything that might be SaMD
- Score features using the 5-dimension matrix above
- Apply HIPAA impact assessment — any feature touching PHI adds 2-4 weeks for privacy review
- Validate with clinical advisors — at least 2 clinicians in the target specialty should evaluate clinical workflow fit before committing
- Run prioritization review with regulatory, clinical, and product — digital health feature decisions require multi-disciplinary sign-off
Common Pitfalls to Avoid
- Making clinical claims in consumer features: "This app monitors your heart health" may trigger SaMD classification
- Skipping HIPAA review on new data types: Adding a new PHI field later costs more than designing for compliance upfront
- Building without clinician input: Features built without clinician validation often fail to get adopted regardless of technical quality
- Underestimating EHR integration cost: Native EHR integration often takes 3-6× longer than in-app integrations
Success Metrics for Digital Health Feature Prioritization
- Feature adoption rate among clinicians is >40% within 90 days of launch
- No FDA regulatory flags triggered by post-launch feature review
- Patient-reported outcome improvement tracked for health impact features
- EHR-integrated features show 5× higher daily active use than standalone features
For more, visit PM interview prep and daily PM challenges.
Learn more about regulated industry PM work at Lenny's Newsletter.
Frequently Asked Questions
How do you prioritize features for a digital health startup?
Use a 5-dimension matrix: Patient Impact, Regulatory Risk (inverse), Clinician Workflow Fit, Payer Value, and Engineering Cost. Apply patient safety as a hard override — features that could cause harm are deprioritized until clinically validated.
What is Software as a Medical Device (SaMD) and why does it affect prioritization?
SaMD is software that performs a medical function without being part of a hardware medical device. Features that diagnose, treat, or monitor clinical conditions may be SaMD and require FDA clearance — adding 6-24 months to the roadmap, affecting prioritization significantly.
How does HIPAA affect digital health product feature development?
Any feature that creates, receives, transmits, or maintains Protected Health Information (PHI) requires HIPAA privacy and security compliance review before shipping — typically adding 2-4 weeks and specialized legal review to the development cycle.
What makes clinicians adopt digital health products?
Clinicians adopt products that fit their existing workflow (ideally EHR-integrated), map to billable CPT codes, reduce documentation burden, and are backed by clinical evidence. Features requiring behavior change outside the EHR have significantly lower adoption.
How do you balance innovation speed with regulatory compliance in digital health?
Separate your product into two tracks: an innovation track for consumer wellness features (below FDA threshold, fast iteration) and a clinical track for SaMD features (rigorous regulatory process, slower but defensible). Keeping these separate prevents regulatory complexity from blocking consumer iteration.