Skip to content

borghei/Claude-Skills / ra-qm-team/quality-manager-qms-iso13485

quality-manager-qms-iso13485

Verified

ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support.

references/advanced-integration.md

View on GitHub
# Advanced Integration: QMSR, Digital QMS & Cross-Framework

Deep-dive reference for FDA QMSR alignment, digital/electronic QMS (21 CFR Part 11 / EU Annex 11), remote audits, ISO 42001 AI integration, software/cloud supplier qualification, and cybersecurity-driven CAPA. Read this when modernizing the QMS, preparing for the FDA QMSR transition, or integrating AI/security frameworks.

---

## ISO 13485:2016 Alignment with FDA QMSR

### QMSR Transition Impact on ISO 13485 QMS

With the FDA's QMSR (effective February 2, 2026) incorporating ISO 13485:2016 by reference, organizations already ISO 13485 certified gain significant advantages:

| Area | Pre-QMSR (Dual System) | Post-QMSR (Unified) |
|------|----------------------|---------------------|
| Quality Manual | Separate FDA QSR and ISO 13485 references | Single Quality Manual referencing ISO 13485 |
| Design controls | 820.30 + ISO 13485 Clause 7.3 (mapped) | ISO 13485 Clause 7.3 (primary) |
| CAPA | 820.100 + ISO 13485 Clause 8.5 | ISO 13485 Clause 8.5 (primary) |
| Document control | 820.40 + ISO 13485 Clause 4.2 | ISO 13485 Clause 4.2 (primary) |
| Purchasing | 820.50 + ISO 13485 Clause 7.4 | ISO 13485 Clause 7.4 (primary) |
| Audits | Separate FDA and ISO audit tracks | Single audit satisfying both |

### FDA-Retained Requirements Beyond ISO 13485

Even under QMSR, certain FDA-specific requirements remain. The QMS must address:

| FDA Requirement | CFR Reference | ISO 13485 Gap | Action |
|----------------|---------------|---------------|--------|
| Complaint handling (medical device reports) | 21 CFR 820.198 | Clause 8.2.2 covers complaints but not FDA MDR reporting specifics | Add FDA MDR reporting procedure to complaint handling SOP |
| Corrections and removals | 21 CFR 806 | No direct equivalent | Maintain separate procedure for FDA reporting of corrections/removals |
| Unique Device Identification | 21 CFR 830 | No UDI clause in ISO 13485 | Add UDI procedures to labeling/identification processes |
| Electronic records and signatures | 21 CFR Part 11 | No electronic signature requirements | Implement Part 11 compliance for electronic QMS |

### QMSR Gap Analysis Checklist

- [ ] Map all existing QSR SOPs to ISO 13485 clause numbers
- [ ] Identify FDA-retained requirements not covered by ISO 13485
- [ ] Update Quality Manual scope and references
- [ ] Retrain staff on ISO 13485 terminology (e.g., "design output" terminology alignment)
- [ ] Update supplier quality agreements to reference QMSR
- [ ] Revise internal audit checklist to combined ISO 13485 + FDA requirements
- [ ] Verify complaint handling addresses both ISO 13485 Clause 8.2.2 and 21 CFR 820.198
- [ ] Conduct mock audit against QMSR requirements

---

## Digital QMS Implementation

### Electronic Document Management System (eDMS) Requirements

| Requirement | Implementation | Regulatory Basis |
|-------------|---------------|------------------|
| Document version control | Automatic versioning with audit trail | ISO 13485 Clause 4.2.3 |
| Electronic approval workflows | Role-based approval routing with e-signatures | 21 CFR Part 11, Annex 11 |
| Access controls | Role-based permissions, segregation of duties | ISO 13485 Clause 4.2.3(c) |
| Audit trail | Immutable record of all changes with timestamp, user, reason | 21 CFR Part 11 §11.10(e) |
| Backup and recovery | Regular backups with tested restore procedures | ISO 13485 Clause 4.2.4 |
| Training records integration | Link document access to training completion | ISO 13485 Clause 6.2 |
| Obsolete document control | Automatic removal from use with archival | ISO 13485 Clause 4.2.3(e) |

### Electronic Signatures

| Signature Type | Use Case | Technical Requirement |
|---------------|----------|----------------------|
| Electronic signature | Document approval, batch release, CAPA closure | Linked to individual, date/time stamped, meaning included |
| Digital signature | High-assurance: design reviews, regulatory submissions | PKI-based, certificate authority, tamper-evident |
| Biometric signature | Optional for high-security processes | Fingerprint or similar biometric linked to identity |

### Audit Trail Requirements

| Element | Description | Example |
|---------|-------------|---------|
| Who | User identity (not shared accounts) | jane.smith@company.com |
| What | Action performed | "Approved SOP-02-001 Rev 3" |
| When | Date and time (UTC or with timezone) | 2026-03-09T14:30:00Z |
| Why | Reason for change (required for modifications) | "Updated per CAPA-2026-003 findings" |
| Previous value | Old content (for modifications) | Automatic diff/version comparison |

---

## Cross-Reference: 21 CFR Part 11 / Annex 11

### 21 CFR Part 11 Requirements for Electronic Records

| Requirement | Section | QMS Implementation |
|-------------|---------|-------------------|
| Validation | §11.10(a) | Validate eQMS software per GAMP 5 methodology |
| Audit trail | §11.10(e) | Computer-generated, timestamped, immutable audit trail |
| System access controls | §11.10(d) | Unique user IDs, passwords, role-based access |
| Authority checks | §11.10(g) | Only authorized individuals can use specific functions |
| Device checks | §11.10(h) | Verify source of data input |
| Personnel qualification | §11.10(i) | Training on system use and Part 11 requirements |
| Electronic signatures | §11.50, §11.100 | Unique to individual, not reusable, linked to records |
| Open vs. closed systems | §11.30 vs. §11.10 | Determine system type; open systems need encryption |

### Annex 11 (EU GMP) Requirements

| Requirement | Section | QMS Implementation |
|-------------|---------|-------------------|
| Risk management | §1 | Apply risk-based approach to computerized system validation |
| Personnel | §2 | Designated system owner and trained users |
| Supplier assessment | §3 | Assess eQMS vendor quality and compliance capability |
| Validation | §4-5 | IQ/OQ/PQ for eQMS, validation plan and report |
| Data | §6-9 | Data integrity, accuracy checks, data storage |
| Printouts | §8 | Ability to generate clear, legible copies of electronic records |
| Audit trail | §9 | Record of all GMP-relevant changes |
| Change and configuration management | §10-11 | Controlled change process for system modifications |
| Security | §12 | Physical and logical security controls |
| Incident management | §13 | Procedure for reporting and managing system incidents |
| Electronic signatures | §14 | Equivalent legal standing to handwritten signatures |
| Batch release | §15 | Electronic batch release with appropriate controls |
| Business continuity | §16 | Contingency procedures for system unavailability |
| Archiving | §17 | Long-term accessibility and readability of archived data |

---

## Remote Audit Considerations (Post-COVID)

### Remote Audit Methodology

| Audit Element | On-Site Approach | Remote Equivalent |
|-------------|-----------------|-------------------|
| Document review | Physical review of controlled copies | Screen-sharing of eDMS, live navigation |
| Record sampling | Pull physical records from files | Live database queries via screen-share |
| Process observation | Walk the production floor | Live video tour, camera-equipped devices |
| Personnel interviews | Face-to-face | Video conference with individual sessions |
| Equipment verification | Physical inspection | Live video with zoom capability |
| Evidence collection | Photocopies, photographs | Screenshots, screen recordings, exported PDFs |

### Remote Audit Best Practices

| Practice | Description |
|----------|-------------|
| Pre-audit documentation | Share document packages 2 weeks before audit via secure portal |
| Technology testing | Test video conferencing, screen-sharing, and secure file transfer before audit |
| Audit plan adaptation | Allow 20-30% more time for remote activities vs. on-site |
| Secure communication | Use encrypted channels for all audit communications and evidence transfer |
| Real-time evidence | Prefer live demonstrations over pre-recorded material |
| Breakout rooms | Use separate video sessions for confidential interviews |
| Audit trail of the audit | Record audit sessions (with agreement) for reference |

### Hybrid Audit Model

| Activity | Recommended Mode | Rationale |
|----------|-----------------|-----------|
| Opening/closing meetings | Remote | Efficient, schedule-friendly |
| Document and record review | Remote | Full eDMS access, efficient sampling |
| Process observation (manufacturing) | On-site | Cannot verify physical processes remotely |
| Cleanroom/controlled environment | On-site | Environmental conditions require physical presence |
| Software system review | Remote | Screen-sharing is equivalent or better |
| Management interview | Either | Remote is acceptable |
| Supplier audit (critical) | On-site | Physical verification essential |

---

## Cross-Reference: ISO 42001 for AI-Enabled Medical Devices

### ISO 42001 (AI Management System) Integration with ISO 13485

For medical device organizations developing AI-enabled products, ISO 42001:2023 provides an AI management system framework:

| ISO 42001 Clause | ISO 13485 Integration Point | Combined Requirement |
|-----------------|---------------------------|---------------------|
| 4. Context of the organization | Clause 4.1 (General requirements) | Extend QMS scope to include AI-specific processes |
| 5. Leadership | Clause 5 (Management responsibility) | AI governance within quality policy and objectives |
| 6. Planning (AI risk assessment) | Clause 7.1 (Risk management planning) | Extend ISO 14971 risk management to AI-specific risks |
| 7. Support (AI competence) | Clause 6.2 (Human resources) | Add AI/ML competency requirements to training matrix |
| 8. Operation (AI lifecycle) | Clause 7.3 (Design and development) | Integrate AI development lifecycle into design controls |
| 9. Performance evaluation | Clause 8 (Measurement, analysis) | Add AI performance metrics to quality monitoring |
| 10. Improvement | Clause 8.5 (CAPA) | Include AI-related incidents in CAPA scope |

### AI Lifecycle Integration with Design Controls

```
ISO 13485 Design Control (Cl. 7.3)     ISO 42001 AI Lifecycle
─────────────────────────────────       ─────────────────────
Design Input (7.3.3)                    AI System Requirements
    ↓                                       ↓
Design Output (7.3.4)                   Data Collection & Preparation
    ↓                                   Model Architecture & Training
    ↓                                       ↓
Design Review (7.3.5)                   AI Model Validation Review
    ↓                                       ↓
Design Verification (7.3.6)            Model Verification (accuracy, bias)
    ↓                                       ↓
Design Validation (7.3.7)             Clinical Validation (real-world performance)
    ↓                                       ↓
Design Transfer (7.3.8)               Model Deployment & Monitoring
    ↓                                       ↓
Design Changes (7.3.9)                Model Retraining & Update Control
```

---

## Supplier Qualification for Software/Cloud Providers

### Cloud Service Provider Qualification

| Qualification Criterion | Assessment Method | Minimum Requirement |
|------------------------|-------------------|---------------------|
| Information security | ISO 27001 certificate or SOC 2 Type II report | Current certification for relevant scope |
| Data residency | Contractual agreement + architecture review | Data stored in jurisdictions compliant with regulations |
| Availability SLA | Service agreement review | 99.9% uptime minimum for critical systems |
| Backup and recovery | Architecture review + test results | RPO < 4 hours, RTO < 8 hours for critical systems |
| Incident notification | Contract clause review | Notification within 24 hours of security incident |
| Audit rights | Contract clause | Right to audit or receive audit reports |
| Regulatory compliance | Vendor compliance documentation | GxP-qualified environments (if applicable) |
| Exit strategy | Data portability assessment | Documented data export capability in standard formats |

### Software Supplier Assessment

| Assessment Area | Category A (Critical) | Category B (Major) | Category C (Minor) |
|----------------|----------------------|--------------------|--------------------|
| Quality system | ISO 13485 or ISO 9001 required | ISO 9001 preferred | Documented processes |
| Development process | IEC 62304 compliance evidence | SDLC documentation | Basic version control |
| Cybersecurity | IEC 81001-5-1 compliance | Security testing evidence | Basic security practices |
| Change management | Formal change control with notification | Release notes and notification | Version tracking |
| Validation support | IQ/OQ/PQ documentation provided | Functional test documentation | User documentation |
| Incident handling | SLA-based response with root cause | Defined support process | Best-effort support |

---

## CAPA Integration with Cybersecurity Incidents

### Cybersecurity Incident as CAPA Trigger

| Incident Type | CAPA Required? | Response Actions |
|-------------|----------------|-----------------|
| Patient data breach | Yes — automatic | Contain → investigate → notify (GDPR 72h, HIPAA 60 days) → CAPA |
| Device vulnerability (exploitable) | Yes — automatic | Patch → verify → communicate → CAPA for root cause |
| Device vulnerability (not exploitable) | Evaluate | Risk assessment → mitigate if feasible → track |
| Malware on manufacturing system | Yes — automatic | Isolate → clean → verify product integrity → CAPA |
| Unauthorized access to QMS | Yes — automatic | Revoke access → assess impact → verify record integrity → CAPA |
| Supplier security incident | Evaluate | Assess impact on device/data → CAPA if product affected |

### Cybersecurity CAPA Process

```
Step 1: Incident Detection and Containment
        → Activate incident response plan
        → Contain threat and preserve evidence
        → Assess impact on product safety and quality

Step 2: Investigation (Root Cause Analysis)
        → Technical forensic analysis
        → 5 Whys + attack chain reconstruction
        → Identify QMS process failures that enabled the incident
        → Assess whether product quality was affected

Step 3: Corrective Actions
        → Technical: patch vulnerability, update security controls
        → Process: update SOPs, access controls, monitoring
        → People: security awareness training
        → Product: assess need for field safety corrective action (FSCA)

Step 4: Preventive Actions
        → Threat modeling review for similar attack vectors
        → Security control gap analysis
        → Supply chain security review (if applicable)
        → Update cybersecurity risk assessment

Step 5: Effectiveness Verification
        → Penetration testing to verify fix
        → Monitoring for recurrence (90-day window)
        → Review of updated security metrics
        → Close CAPA with evidence of effectiveness

Step 6: Regulatory Reporting (if required)
        → MDR vigilance report (if patient safety affected)
        → FDA MedWatch report (if applicable)
        → GDPR breach notification (if personal data involved)
        → NIS2 incident report (if essential entity)
```

> **Cross-references:** See `../information-security-manager-iso27001/SKILL.md` for ISO 27001 incident response procedures, `../fda-consultant-specialist/SKILL.md` for FDA QMSR alignment, and `../risk-management-specialist/SKILL.md` for cybersecurity risk integration with ISO 14971.

---

## ISO 13485 Enhanced — QMSR, Digital QMS & Cross-Framework Integration

### ISO 13485:2016 Alignment with FDA QMSR

With FDA's Quality Management System Regulation (QMSR) effective Feb 2026:

- **Direct Alignment:** FDA now recognizes ISO 13485:2016 as the quality system standard
- **Single QMS:** Organizations can maintain one QMS for both FDA and EU market access
- **Gap Analysis:** Identify differences between current QSR procedures and ISO 13485 requirements
- **Transition Plan:** Map QSR 21 CFR 820 sections to ISO 13485 clauses, update procedures
- **Cross-reference:** See `fda-consultant-specialist` for detailed FDA requirements

### Digital QMS Implementation

- **Electronic Document Control:** Validated electronic document management system (eDMS)
- **Electronic Signatures:** 21 CFR Part 11 / EU Annex 11 compliant e-signatures
- **Audit Trail:** Automated, timestamped, immutable record of all document changes
- **Cloud QMS Platforms:** Qualification requirements for SaaS QMS solutions (IQ/OQ/PQ)
- **Cross-reference:** See `quality-documentation-manager` for Part 11 compliance

### Remote Audit Considerations

- **Hybrid Audits:** Combination of on-site and remote activities (ISO 19011 guidance)
- **Technology Requirements:** Secure video conferencing, screen sharing, document access
- **Limitations:** Physical process observations may require on-site verification
- **Notified Body Acceptance:** Most NBs accept hybrid audits for surveillance and recertification

### AI-Enabled Medical Device QMS

- **ISO 42001 Integration:** For organizations developing AI-enabled medical devices
- **Data Governance:** Training data quality per ISO 42001 Annex A.7 within QMS
- **Model Lifecycle:** AI model versioning and change control within existing QMS processes
- **Cross-reference:** See `iso42001-ai-management` for AI management system requirements

### Supplier Qualification for Software/Cloud Providers

- **Cloud Service Providers:** Qualification checklist (SOC 2, ISO 27001, data residency, SLAs)
- **Open Source Software:** Risk assessment for OSS components (licensing, maintenance, vulnerabilities)
- **SaaS Tools:** Validation requirements for SaaS platforms used in QMS processes
- **SBOM Management:** Track software components across the supply chain
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall