An MDSAP meeting note about device lifetime turned into a clause-specific ISO 13485 update, one that had to be checked against how the QM actually operates, not just what the clause says.
MDSAP notes as a trigger, not the whole task
A note from an MDSAP meeting flags where a gap might exist. Confirming it's an actual gap, and not just an ambiguity in the clause wording, means checking the current QM process directly.
- Tracing the change/record through every referencing document (manual, CAPA, recall record)
- Confirming consistency against ISO 13485 and the current QMS procedure
- Adding device lifetime to the IFUs as the concrete output of the review
Where the traceability gap shows up
A quality record (change control, recall, CAPA) that doesn't reconcile with its related documents creates a traceability gap during an audit, and an MDSAP note about device lifetime is exactly the kind of trigger that finding comes from.
What the update confirmed
Updating the relevant ISO 13485:2016 clause documentation confirmed current practice matched the documented requirement, closing the gap the MDSAP note had flagged.
The Real Takeaway
Clause-specific ISO 13485 work needs to be checked against the actual current process, not just the clause text.
That's the only way to confirm the requirement is genuinely met in practice.