Operating Theory · Sep 10, 2026

Continuous traceability instead of reconstruction

The chain from clinical need to post-market observation should be current every day, not rebuilt in the weeks before a submission or an audit. Reconstruction is where the errors enter.

Under the pillar Consumer tech for medical grade devices

The claim

Traceability reconstructed after the fact is a description of what a team wishes it had done. Traceability maintained continuously is a description of what it did. Both produce a matrix; only one of them is evidence.

The chain has ten links: clinical need, product requirement, technical design, hazard, mitigation, verification test, validation evidence, regulatory claim, submission evidence, post-market observation. A break anywhere means a requirement with no test, a hazard with no mitigation, or a claim with nothing under it.

The regulatory traceability chainTen links maintained continuously: clinical need, product requirement, technical design, identified hazard, mitigation, verification test, validation evidence, regulatory claim, submission evidence, and post-market observation, with each link tied to the one before it.Clinical needwho is harmed today, and howProduct requirementwhat the device must doTechnical designhow it does itHazardwhat can go wrongMitigationwhat reduces the riskVerification testdoes it meet the requirementValidation evidencedoes it meet the needRegulatory claimwhat is asserted, and whereSubmission evidencewhat supports the assertionPost-market observationwhat the field reports back
Kept live by the system, reviewed and approved by qualified people.

What has to be true for it to work

The links have to be created by the work rather than typed in afterwards: a test that runs updates the verification link, a design change flags the hazards it touches, a complaint attaches to the requirement it concerns. If maintaining the chain is a separate job, it will fall behind, and a chain that is behind is worse than no chain because it is trusted.

The measure we intend to hold ourselves to: at any moment, without notice, the current state of every link should be producible. If preparing that takes a week, the theory failed.

Post-market is part of the chain, not an epilogue

Adverse events, complaints, and recalls are public for the whole industry, and they are the closest thing to ground truth about how devices fail in use. Reading them for a category before designing in it is cheap. Feeding your own back into the risk file is the part most teams do slowly.

Put this to work

Continuous traceability instead of reconstruction challenge record

Test the claim behind Continuous traceability instead of reconstruction against a real case and look for where it fails.

For
Clinical, operational, product, reimbursement, and implementation leaders.
What you keep
A continuous traceability instead of reconstruction challenge record you can review, revise, and send.
What counts as sound
  • Makes the claim testable
  • Includes contrary evidence
  • Preserves competing explanations
  • States uncertainty
  • Names what would change the conclusion

Clinical, regulatory, privacy, and release decisions remain with qualified people.

Nothing entered here is stored or sent. Review the prompt before sharing confidential, personal, patient, or privileged information.

Review the prompt

You can leave any field blank. The prompt will mark it as not provided.

If the record survives your review, send the question, evidence, unknowns, and requested next step.