Industries
Design controls and a traced design history for medical devices
A device team can keep user needs, design inputs, design outputs, verification and validation in one traced OpenV project, with hazards linked to the design items that control them. A baseline at each design review freezes what was reviewed. OpenV has no electronic signatures, so on its own it does not meet 21 CFR Part 11, and approvals that need a signature are signed in your quality system.
Updated by Desktop Machine Shop, the makers of OpenV.
What these teams keep
Design controls under ISO 13485 and the FDA quality system regulation ask for user needs, design inputs derived from them, design outputs that meet the inputs, verification that outputs meet inputs, and validation that the device meets the user needs. ISO 14971 asks for hazards, the risk controls for each, and evidence the controls work. IEC 62304 asks the same traceability of software requirements.
Where it goes in OpenV
- User needs, requirements (design inputs), design items (design outputs), hazards and test cases are separate artifact types with typed links between them.
- A test case verifies a requirement or validates a user need, and the two links are different. The gap list reports a need no requirement answers.
- A hazard is mitigated by design items, and the tests of those items are the evidence the control works.
- Test runs keep each result with the version of the test case that was run and its evidence files, each with a SHA-256 digest.
- A baseline at each design review, and a comparison between any two.
- A PDF or Word document from a baseline, with the sections and fields you choose, for the design history file.
A first project
Model one function of the device end to end: a user need, the design inputs under it, a design output, a hazard and its control, one verification test and one validation test. Capture a baseline, change a requirement, and compare. The comparison and the flagged links show what a change costs in rework.
What OpenV does not do
- No certification, no tool qualification kit and no claim of compliance with any standard named on this page. OpenV holds the record; your process and your assessor decide whether it is enough.
- No risk estimation: probability, severity and risk acceptability are fields you define, and OpenV does not compute a risk level or draw a risk matrix.
- No electronic signatures, so 21 CFR Part 11 and similar rules are not met by OpenV alone.
- No software safety classification logic for IEC 62304; the class is an attribute you set.
- No electronic signatures, and no separate approver role: any project editor can approve, including their own change.
- OpenV is in alpha: screens still change between releases, though data, exports and the API stay compatible across stable releases.
