QMS OS — 8-Scene Self-Service Tour
~5–10 minutes · arrow keys navigate · Esc resets · session69998f9c
FDA Guidance — Cardiovascular Devices: Updated Design Control Expectations Under 21 CFR 820.30 (Class II/III)
US Class IIClass III
FDA tightens design verification documentation requirements for cardiovascular devices, particularly software-as-medical-device (SaMD) elements. Effective immediately for new submissions; 120-day grace for in-flight submissions.
Citations:
21 CFR 820.3021 CFR 820.100ISO 13485:2016 §7.3
Scene 1 of 8
The Regulatory Intelligence Engine polls FDA, EU, ISO, Health Canada, TGA, and PMDA daily.
This morning it caught a HIGH-severity FDA cardiovascular guidance update — the kind of release that would normally trigger a fire-drill.
Watch what happens next →
3-Model Council weighs in
HIGH IMPACT — your design history files (DHF) for cardiovascular Class II/III devices need a verification matrix update within 120 days.
Confidence 92%Affects DHF, DMR, and risk-management file (ISO 14971). Three SOPs likely require revision: SOP-DC-001, SOP-DC-014, SOP-RM-002.
Confidence 89%Trigger CAPA. Recommend formal design review within 30 days, training rollout within 60 days, full verification matrix re-baseline within 120 days.
Confidence 91%Consensus
Severity confirmed: HIGH · estimated effort 64 h
- Open CAPA against design control SOPs
- Update DHF verification matrix for affected products
- Schedule cross-functional design review (RA + R&D + QE)
- Re-train design owners on new documentation expectations
Risk if ignored: Form 483 observation likely on next inspection; potential shipment hold for new submissions.
QMS OS Agent auto-drafts the response plan
Document updates
SOP-DC-001— Design Control — Verification Procedure (§ 4.2, 5.1.3) — highSOP-DC-014— Design Review Cadence (§ 3.0) — mediumSOP-RM-002— Risk Management File (§ 8.5.2) — medium
Training updates
- Design owners (R&D + RA) — Live workshop + LMS module (deadline 2026-07-02)
CAPA candidate
Update design control SOPs to revised FDA cardiovascular guidance
Root cause: SOP-DC-001 verification matrix predates 2026 cardiovascular guidance; documentation depth no longer meets FDA expectations.
Human reviewer approves
Separation of duties enforced — the initiator can never approve their own task.
Approved
- CAPA
CV-DC-2026-01created - 3 Issues opened (one per document update)
- Regulatory change →
response_in_progress
CAPA appears with FMEA cross-link
Update design control SOPs to revised FDA cardiovascular guidance
Ref CV-DC-2026-01 · severity HIGH ·
owner Director of Quality Engineering · due 2026-08-01
Revise SOP-DC-001/014/RM-002, update DHF verification matrix for active CV programs, retrain design owners, file revisions in DMR.
Linked FMEA: demo-fmea-001 · Issues: demo-issue-001, demo-issue-002, demo-issue-003
FMEA · Cardiovascular Implantable — Design FMEA
design · in_review11-Model Council Mode
Ask anything — get triangulated answers from 11 SOTA models in parallel.
Add a firmware regression matrix and document software-of-unknown-provenance (SOUP) rationale.
412 tok · 2150 ms · 4 citesMandatory: cybersecurity threat model + post-market surveillance plan keyed to UDI.
388 tok · 1980 ms · 5 citesUpdate design review minutes to include a verifiable, timestamped sign-off per design output.
401 tok · 2240 ms · 3 citesPre-submission Q-Sub recommended to confirm new evidence depth.
295 tok · 1620 ms · 2 citesAdd explicit traceability: URS → DI → V&V test → manufacturing acceptance criteria.
367 tok · 2410 ms · 4 citesRisk-management file update under ISO 14971:2019 §7 to capture residual risk re-evaluation.
332 tok · 2080 ms · 3 citesAdd usability engineering file (IEC 62366-1) — implant programmers fall under HF scope.
280 tok · 1850 ms · 3 citesDocument software-development life cycle conformance to IEC 62304 Class C.
318 tok · 1990 ms · 4 citesThree recent FDA Form 483 cite missing SOUP rationale — single highest enforcement signal.
425 tok · 3120 ms · 6 citesRecommend formal verification report deliverable per affected design output.
351 tok · 2680 ms · 4 citesConfirmed: matches latest FDA pre-submission feedback patterns logged in 2025-Q4.
309 tok · 2470 ms · 5 citesConsensus (87% agreement)
Submit a pre-submission Q-Sub confirming evidence depth before final 510(k); expand DHF with explicit firmware regression matrix and cybersecurity threat model.
- Firmware regression + SOUP documentation
- Cybersecurity threat model
- Bidirectional trace URS → V&V → manufacturing
- Risk-file refresh per ISO 14971:2019
FDA Warning Letter analytics
Top cited CFR sections
- 21 CFR 820.30 (Design Controls) — 187 citations
- 21 CFR 820.100 (Corrective & Preventive) — 154 citations
- 21 CFR 820.198 (Complaint Files) — 142 citations
- 21 CFR 820.50 (Purchasing Controls) — 118 citations
- 21 CFR 820.75 (Process Validation) — 94 citations
Ready to deploy?
From regulatory radar to a board-ready CAPA in one human-supervised loop. That's QMS OS.
Press Esc to restart the tour.