Customer story
An ISO 14971 risk model, built by an agent
- 13
- models created
- 17
- declared links

MedTech
Risk, requirements, design outputs, tests and revisions are linked in one model. Your design history file (DHF) exports when the auditor asks for it, instead of being assembled for weeks beforehand.
1 click
to export the certification file
1 day
for a change impact analysis, instead of 2 weeks of meetings and spreadsheets
Measured at our reference customer after a year in use. Your first scope measures them on your own programme. Reference customer: Exotec, with more than 1,000 users and 20 partner organisations in Koddex.
Today
Before every audit, the team assembles the DHF by hand from files that no longer agree.
With Koddex
User needs, design inputs, outputs and verification are linked in one model, and the DHF exports in one click.
ISO 13485, EU MDR and FDA design controls apply to every change.
User needs, design inputs, outputs and verification are linked, so the DHF is a view of your data instead of a separate project.
Risk analysis often lags behind the design.
Hazards, risks and controls live in the same model as the parts and tests.
Software and hardware are certified together.
IEC 62304 software items and hardware parts trace to the same requirements.
Several sites validate the same device.
Every site reads the same released configuration, each in its own scope.
With Koddex agents
Assign a design change to an agent. It checks which risk controls and verifications the change reopens and moves the review forward in the workflow.
Teams that work with Koddex agents spend up to 50% less time on repetitive engineering tasks.
An agent connected through MCP works on an ISO 14971 risk file
Customer story
Reference scenario
Customer story
Customer story
Customer story
Event
Booth E15, October 13 to 15. We run live demos on a real engineering project.
Bring one device and one design change. In the demo, we show in Koddex how a design change is traced and how the file exports.