IEC 62304
The software lifecycle for medical device software, from requirements through architecture to release and maintenance. It applies to the app on the phone and the algorithm in the cloud as squarely as to firmware on the wearable.
ALCOA++ in the Age of Digital Health Technologies (Part 5/8)
Can your audit trail reconstruct every DHT data transformation from source to submission? Are firmware, algorithms, and databases synchronised under one…
Read the article →Endpoints and Algorithms: How Firmware Can Break Your Study (Part 4/8)
Can a single firmware update, algorithm change or data-sync failure invalidate months of trial data? How did the FDA’s DHT guidances change who answers for endpoint traceability and version control?
Read the article →FDA’s Final Guidance on Cybersecurity in Medical Devices: Insights and a Comparison with EU Frameworks
What the FDA’s 2023 final guidance on cybersecurity in medical devices asks of manufacturers — security risk management within the quality system and the content of premarket submissions — and how it compares with the EU frameworks.
Read the article →Fit-for-Purpose or Bust: A Real-World Rubric for DHT Verification, Validation & Usability
What makes a DHT truly “fit-for-purpose” in a clinical trial context? How do verification and validation differ—and why does it matter? What role does…
Read the article →From Compliance Burden to Competitive Edge: How DHT Readiness Can Shorten the Path Through Review
Can building DHT compliance into trial design, rather than adding it later, mean fewer regulator questions and less rework? Is your compliance programme adding time to your timelines—or saving it?
Read the article →The DHT-Ready QMS: Integrating Device, Data, and Clinical Quality into One System (Part 2/8)
Does your QMS include design-history and validation records for every DHT you use? Are firmware, algorithms, and human-factors results governed under change…
Read the article →The Shockwave: What the FDA’s DHT Framework Really Means (Part 1/8)
Are your current DHTs validated for analytical, clinical, and usability accuracy? Who in your organisation owns responsibility for device version control?…
Read the article →“It’s Just a Phone”
Did you know a consumer smartphone can trigger four separate regulatory frameworks the moment it touches a clinical endpoint? Why do so many sponsors fail…
Read the article →A document appears here because it names IEC 62304 in its own text. Nothing is inferred: this is what we have actually written about it.