11 controls
0 frameworks share controls with it
International (IMDRF member regulators)
verified against its source document
Every control below is one this framework asks for. The right hand column counts how
many other frameworks in our corpus carry the same control, which is the difference between
doing this work once and doing it again for the next standard.
There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.
What you already have
Frameworks whose controls overlap this one, most first. If you run any of them, the
count is roughly what you have already evidenced.
No measured overlap with another framework in the corpus.
Every control
| Code | Control | Also in |
1 | Introduction and references | 0 |
P1 | Understand the intended use deeply and bring multi-disciplinary expertise across the life cycle | 0 |
P10 | Monitor deployed models and manage re-training risks | 0 |
P2 | Apply good software engineering, device design and security practice throughout | 0 |
P3 | Evaluate clinically with datasets representative of the intended patient population | 0 |
P4 | Keep training and test datasets independent | 0 |
P5 | Use reference standards that are fit for purpose | 0 |
P6 | Tailor model choice and design to the data and the intended use | 0 |
P7 | Assess the human-AI team in the intended use environment, not the device alone | 0 |
P8 | Test performance under clinically relevant conditions, independent of training data | 0 |
P9 | Give users clear, essential information | 0 |
Tell me when IMDRF N88 Good Machine Learning Practice for Medical Device Development: Guiding Principles (2025) files something new
One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.
What this page is
A control-level reference for IMDRF N88 Good Machine Learning Practice for Medical Device Development: Guiding Principles (2025), drawn from our framework corpus. Control codes and
titles are references to the standard, not reproductions of it. The overlap counts and the
auditor artefacts are our own work and are the part you will not find elsewhere.
Measure this against what you already run ·
All frameworks · Today's edition