01
Finished firmware, an EU MDR or FDA submission in a few months
- Architecture, design, SOUP records, the threat model (a structured analysis of how the device could be attacked) and the SBOM are missing
What we do: The software file written from the existing code and records. Reviews and tests that left no record are not written after the fact, the gap analysis names the tests to run.
IEC 62304 documentation →02
Notified body findings on a product on the market
- The audit found gaps in the software records
What we do: A gap analysis in three weeks for an agreed scope, with findings in order of priority and a plan to close them.
IEC 62304 gap analysis →03
A supplier is leaving
- The knowledge of the code and the build sits with the outgoing supplier
What we do: A handover plan for the weeks the supplier is still available, then maintenance and the next release.
Legacy modernisation and takeover →04
A connected device without a cybersecurity file
- The FDA or the notified body asks for the threat model and the SBOM
What we do: Threat modelling, risk assessment, SBOM and security tests for the EU MDR and, for cyber devices, FD&C Act section 524B.
Medical device cybersecurity →05
An AI model that has to become a medical device
- The model works on research data and needs a product around it
What we do: Production inference, hospital integration and the records for the EU MDR, the EU AI Act and the FDA.
AI model to medical device →06
Code written with AI tools, heading for an audit
- Nobody can say what the code does or how it will pass
What we do: An assessment, a test baseline and a plan to bring the code under IEC 62304.
AI coding tools in regulated development →07
A submission is close and the V&V will not pass
- Requirements exist, but test protocols, executed records and the V&V report are missing
What we do: Verification against your requirements and risk controls, and validation against the intended use under your validation plan, usability evaluation included: protocols, executed records and reports, with anomalies handled.
Verification and validation →08
Firmware that is hard to change, or updates that fail in the field
- Every change is risky
- Firmware updates over Bluetooth Low Energy (BLE) hang now and then
What we do: The update failures traced to their root cause and fixed, the firmware restructured into testable modules and put under automated tests.
Embedded and firmware development →09
A first FDA 510(k) for a product built for the EU
- The file was written for the EU MDR, and the team has not worked with the FDA
What we do: Route and predicate, a gap analysis against the FDA expectations, a Pre-Submission where useful and the eSTAR submission.
Regulatory consulting →10
The team needs engineers now
- The roadmap is ahead of the hiring plan
What we do: Engineers who join your team inside your QMS, the first ones within two to three weeks of signature.
Team extension →11
A hospital choosing or integrating AI
- Many offers, and performance on your own patients is unknown
What we do: Use case selection, vendor evaluation, local validation and integration, independent of the vendors.
Clinical AI selection and integration →