Most hardware founders approach FDA as a late-stage compliance exercise — something to "deal with" after the product is built. This misunderstanding is responsible for a significant fraction of medical device startup failures. The FDA doesn't just review the final device. It reviews the entire process by which it was designed, built, and validated.
Design History File: start it on day one
The Design History File (DHF) is the complete documented record of your product's development. It includes requirements, design outputs, verification and validation activities, design reviews, and risk analysis. The FDA expects to see a DHF that tells a coherent story — from initial concept through final release.
If you don't start building this on day one, you'll spend months recreating it from memory at submission time. That recreation is always incomplete, always inconsistent, and always visible to reviewers.
Risk management under ISO 14971
Medical device risk management is governed by ISO 14971. It requires you to identify hazards, estimate and evaluate risks, implement risk controls, and verify their effectiveness. This is not a checkbox at the end of development — it's a living document that should influence design decisions throughout.
Risk analysis shapes your architecture. A hazard that could cause patient harm demands a different design response than one causing minor inconvenience. Getting this analysis done early means you build the right controls in — rather than bolting them on after the fact.
Biocompatibility: materials matter
If any part of your device contacts the patient — skin, tissue, blood — biocompatibility testing under ISO 10993 is required. The testing strategy depends on the nature and duration of contact. The key is that material selection in CAD has downstream implications for testing timelines and cost.
Switching a housing material late in development because the originally specified polymer fails biocompatibility is an expensive and avoidable mistake.
Electrical safety: IEC 60601
Any electrically powered medical device needs to comply with IEC 60601. The specific standard and parts depend on the device type and its intended environment. Third-party testing for this standard typically takes 3–6 months and requires the product to be in near-final form. Build this into your development schedule from the start — not as an afterthought.
What we do differently for medical projects
- DHF structure established in week one — all engineering documents are DHF artifacts from the start
- Risk management integrated into design reviews, not conducted separately
- Material selection reviewed for biocompatibility early in detailed design
- IEC 60601 compliance mapped to architecture decisions before PCB layout
- Verification and validation protocols written in parallel with design, not after
Building a medical device and want a team that's navigated FDA and CE submissions before? Let's talk.