QMS Audit Expert
ISO 13485 internal audit methodology for medical device quality management systems.
Table of Contents
Clarify First
Before planning or executing the audit, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the audit plan.
Audit Planning Workflow
Plan risk-based internal audit program:
- List all QMS processes requiring audit
- Assign risk level to each process (High/Medium/Low)
- Review previous audit findings and trends
- Determine audit frequency by risk level
- Assign qualified auditors (verify independence)
- Create annual audit schedule
- Communicate schedule to process owners
- Validation: All ISO 13485 clauses covered within cycle
Risk-Based Audit Frequency
| Risk Level |
Frequency |
Criteria |
| High |
Quarterly |
Design control, CAPA, production validation |
| Medium |
Semi-annual |
Purchasing, training, document control |
| Low |
Annual |
Infrastructure, management review (if stable) |
Audit Scope by Clause
| Clause |
Process |
Focus Areas |
| 4.2 |
Document Control |
Document approval, distribution, obsolete control |
| 5.6 |
Management Review |
Inputs complete, decisions documented, actions tracked |
| 6.2 |
Training |
Competency defined, records complete, effectiveness verified |
| 7.3 |
Design Control |
Inputs, reviews, V&V, transfer, changes |
| 7.4 |
Purchasing |
Supplier evaluation, incoming inspection |
| 7.5 |
Production |
Work instructions, process validation, DHR |
| 7.6 |
Calibration |
Equipment list, calibration status, out-of-tolerance |
| 8.2.2 |
Internal Audit |
Schedule compliance, auditor independence |
| 8.3 |
NC Product |
Identification, segregation, disposition |
| 8.5 |
CAPA |
Root cause, implementation, effectiveness |
Auditor Independence
Verify auditor independence before assignment:
Audit Execution
Conduct systematic internal audit:
- Prepare audit plan (scope, criteria, schedule)
- Review relevant documentation before audit
- Conduct opening meeting with auditee
- Collect evidence (records, interviews, observation)
- Classify findings (Major/Minor/Observation)
- Conduct closing meeting with preliminary findings
- Prepare audit report within 5 business days
- Validation: All scope items covered, findings supported by evidence
Evidence Collection
| Method |
Use For |
Documentation |
| Document review |
Procedures, records |
Document number, version, date |
| Interview |
Process understanding |
Interviewee name, role, summary |
| Observation |
Actual practice |
What, where, when observed |
| Record trace |
Process flow |
Record IDs, dates, linkage |
Audit Questions by Clause
Document Control (4.2):
- Show me the document master list
- How do you control obsolete documents?
- Show me evidence of document change approval
Design Control (7.3):
- Show me the Design History File for [product]
- Who participates in design reviews?
- Show me design input to output traceability
CAPA (8.5):
- Show me the CAPA log with open items
- How do you determine root cause?
- Show me effectiveness verification records
See references/iso13485-audit-guide.md for complete question sets.
Finding Documentation
Document each finding with:
Requirement: [Specific ISO 13485 clause or procedure]
Evidence: [What was observed, reviewed, or heard]
Gap: [How evidence fails to meet requirement]
Example:
Requirement: ISO 13485:2016 Clause 7.6 requires calibration
at specified intervals.
Evidence: Calibration records for pH meter (EQ-042) show
last calibration 2024-01-15. Calibration interval is
12 months. Today is 2025-03-20.
Gap: Equipment is 2 months overdue for calibration,
representing a gap in calibration program execution.
Nonconformity Management
Classify and manage audit findings:
- Evaluate finding against classification criteria
- Assign severity (Major/Minor/Observation)
- Document finding with objective evidence
- Communicate to process owner
- Initiate CAPA for Major/Minor findings
- Track to closure
- Verify effectiveness at follow-up
- Validation: Finding closed only after effective CAPA
Classification Criteria
| Category |
Definition |
CAPA Required |
Timeline |
| Major |
Systematic failure or absence of element |
Yes |
30 days |
| Minor |
Isolated lapse or partial implementation |
Recommended |
60 days |
| Observation |
Improvement opportunity |
Optional |
As appropriate |
Classification Decision
Is required element absent or failed?
├── Yes → Systematic (multiple instances)? → MAJOR
│ └── No → Could affect product safety? → MAJOR
│ └── No → MINOR
└── No → Deviation from procedure?
├── Yes → Recurring? → MAJOR
│ └── No → MINOR
└── No → Improvement opportunity? → OBSERVATION
CAPA Integration
| Finding Severity |
CAPA Depth |
Verification |
| Major |
Full root cause analysis (5-Why, Fishbone) |
Next audit or within 6 months |
| Minor |
Immediate cause identification |
Next scheduled audit |
| Observation |
Not required |
Noted at next audit |
See references/nonconformity-classification.md for detailed guidance.
External Audit Preparation
Prepare for certification body or regulatory audit:
- Complete all scheduled internal audits
- Verify all findings closed with effective CAPA
- Review documentation for currency and accuracy
- Conduct management review with audit as input
- Prepare facility and personnel
- Conduct mock audit (full scope)
- Brief personnel on audit protocol
- Validation: Mock audit findings addressed before external audit
Pre-Audit Readiness Checklist
Documentation:
Personnel:
Facility:
Mock Audit Protocol
- Use external auditor or qualified internal auditor
- Cover full scope of upcoming external audit
- Simulate actual audit conditions (timing, formality)
- Document findings as for real audit
- Address all Major and Minor findings before external audit
- Brief management on readiness status
Reference Documentation
ISO 13485 Audit Guide
references/iso13485-audit-guide.md contains:
- Clause-by-clause audit methodology
- Sample audit questions for each clause
- Evidence collection requirements
- Common nonconformities by clause
- Finding severity classification
Nonconformity Classification
references/nonconformity-classification.md contains:
- Severity classification criteria and decision tree
- Impact vs. occurrence matrix
- CAPA integration requirements
- Finding documentation templates
- Closure requirements by severity
Tools
Audit Schedule Optimizer
# Generate optimized audit schedule
python scripts/audit_schedule_optimizer.py --processes processes.json
# Interactive mode
python scripts/audit_schedule_optimizer.py --interactive
# JSON output for integration
python scripts/audit_schedule_optimizer.py --processes processes.json --output json
Generates risk-based audit schedule considering:
- Process risk level
- Previous findings
- Days since last audit
- Criticality scores
Output includes:
- Prioritized audit schedule
- Quarterly distribution
- Overdue audit alerts
- Resource recommendations
Sample Process Input
{
"processes": [
{
"name": "Design Control",
"iso_clause": "7.3",
"risk_level": "HIGH",
"last_audit_date": "2024-06-15",
"previous_findings": 2
},
{
"name": "Document Control",
"iso_clause": "4.2",
"risk_level": "MEDIUM",
"last_audit_date": "2024-09-01",
"previous_findings": 0
}
]
}
Audit Program Metrics
Track audit program effectiveness:
| Metric |
Target |
Measurement |
| Schedule compliance |
>90% |
Audits completed on time |
| Finding closure rate |
>95% |
Findings closed by due date |
| Repeat findings |
<10% |
Same finding in consecutive audits |
| CAPA effectiveness |
>90% |
Verified effective at follow-up |
| Auditor utilization |
4 days/month |
Audit days per qualified auditor |
Troubleshooting
| Problem |
Likely Cause |
Resolution |
| Schedule optimizer produces no audits for a process |
last_audit_date is recent and risk level is Low |
Low-risk processes are scheduled annually. If the last audit was within 365 days, no new audit is generated. Increase risk_level or criticality_score to trigger earlier scheduling. |
| Optimizer flags all processes as overdue |
Date format in processes.json is incorrect |
Use ISO 8601 format (YYYY-MM-DD) for last_audit_date. Invalid dates cause the tool to treat the last audit as missing. |
| Interactive mode does not accept input |
Terminal does not support stdin prompts |
Use file-based input with --processes processes.json instead of --interactive. |
| Audit schedule does not cover all ISO 13485 clauses |
Input process list is incomplete |
The optimizer schedules only the processes provided. Ensure all required clauses (4.2, 5.6, 6.2, 7.3, 7.4, 7.5, 7.6, 8.2.2, 8.3, 8.5) are represented in the input. |
| Finding classified as Minor but should be Major |
Classification was applied inconsistently |
Apply the decision tree: systematic failure or absent element = Major; isolated lapse = Minor. Consider whether the finding could affect product safety (auto-escalate to Major). |
| External auditor raises finding already closed internally |
CAPA effectiveness verification not completed before external audit |
Ensure all internal audit findings have completed CAPA with documented effectiveness verification before the external audit date. Close the loop, do not just complete the action. |
| Audit report rejected by process owner |
Findings not supported by objective evidence |
Every finding must reference specific evidence (document number, record ID, observation details). Rework findings using the Requirement-Evidence-Gap format documented in this skill. |
Success Criteria
- Annual audit schedule covers 100% of ISO 13485 clauses with risk-based frequency (quarterly for high-risk, semi-annual for medium, annual for low)
- Schedule compliance rate exceeds 90% (audits completed on time vs. planned)
- All Major findings result in full root cause analysis CAPA initiated within 30 days and verified effective within 6 months
- Finding closure rate exceeds 95% by due date, with no overdue Major findings at any point
- Repeat finding rate below 10% across consecutive audit cycles, demonstrating effective corrective actions
- Auditor independence verified and documented for every audit assignment (no self-auditing of own work area)
- Mock audit conducted before every external certification or surveillance audit with all Major and Minor findings resolved
Scope & Limitations
In Scope:
- ISO 13485:2016 internal audit planning, scheduling, and execution
- Risk-based audit frequency optimization
- Nonconformity classification (Major/Minor/Observation) with decision tree
- CAPA integration for audit findings
- External audit preparation and mock audit protocols
- Audit program metrics and effectiveness tracking
Out of Scope:
- External audit execution (this skill supports preparation for and response to external audits, not conducting them)
- Regulatory inspection management (FDA, Notified Body inspections have jurisdiction-specific protocols beyond internal audit scope)
- Detailed CAPA root cause analysis methodology (use capa-officer skill for 5-Why, Fishbone, FTA, FMEA)
- ISO 19011 auditor certification or training program administration
- Technical product testing or process validation
- QMSR-specific audit checklist generation (use quality-manager-qms-iso13485 for QMSR gap analysis)
Integration Points
| Skill |
Integration |
| quality-manager-qms-iso13485 |
Provides the QMS process framework that the audit program evaluates; audit results feed into management review inputs |
| capa-officer |
Major and Minor audit findings trigger CAPA initiation; CAPA effectiveness verification closes the audit finding loop |
| quality-documentation-manager |
Document control audit coverage (Clause 4.2) validates document numbering, approval workflows, and Part 11 compliance |
| quality-manager-qmr |
Audit program results are a required management review input (Clause 5.6.2); QMR oversees audit program effectiveness |
| risk-management-specialist |
Risk management process audit (Clause 7.1) verifies ISO 14971 implementation and risk file completeness |
Tool Reference
audit_schedule_optimizer.py
Generates risk-based audit schedules optimized by process risk, findings history, and time since last audit.
| Flag |
Required |
Description |
--processes |
Yes (or --interactive) |
Path to JSON file containing process definitions with name, iso_clause, risk_level (HIGH/MEDIUM/LOW), last_audit_date, previous_findings, and criticality_score |
--interactive |
No |
Launch interactive mode for guided process entry (alternative to file input) |
--output |
No |
Output format: json for structured output, omit for human-readable text |
1---2name: qms-audit-expert-23description: ISO 13485 internal audit expertise for medical device QMS. Use for audit planning and execution, nonconformity classification, CAPA verification, external audit preparation, or audit program management.4license: MIT + Commons Clause5---6# QMS Audit Expert
7
8ISO 13485 internal audit methodology for medical device quality management systems.
9
10---
11
12## Table of Contents
13
14- [Audit Planning Workflow](#audit-planning-workflow)
15- [Audit Execution](#audit-execution)
16- [Nonconformity Management](#nonconformity-management)
17- [External Audit Preparation](#external-audit-preparation)
18- [Reference Documentation](#reference-documentation)
19- [Tools](#tools)
20
21---
22
23## Clarify First
24
25Before planning or executing the audit, confirm these inputs. If any is unknown or vague, ASK — do not assume:
26
27- [ ] **Audit purpose** — internal scheduled audit, external/certification prep, or mock audit (sets the scope and formality)
28- [ ] **Processes/clauses in scope** — which ISO 13485 clauses (drives the checklist and frequency)
29- [ ] **Risk level and prior findings per process** — picks audit frequency and sample size
30
31Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the audit plan.
32
33## Audit Planning Workflow
34
35Plan risk-based internal audit program:
36
371. List all QMS processes requiring audit
382. Assign risk level to each process (High/Medium/Low)
393. Review previous audit findings and trends
404. Determine audit frequency by risk level
415. Assign qualified auditors (verify independence)
426. Create annual audit schedule
437. Communicate schedule to process owners
448. **Validation:** All ISO 13485 clauses covered within cycle
45
46### Risk-Based Audit Frequency
47
48| Risk Level | Frequency | Criteria |
49|------------|-----------|----------|
50| High | Quarterly | Design control, CAPA, production validation |
51| Medium | Semi-annual | Purchasing, training, document control |
52| Low | Annual | Infrastructure, management review (if stable) |
53
54### Audit Scope by Clause
55
56| Clause | Process | Focus Areas |
57|--------|---------|-------------|
58| 4.2 | Document Control | Document approval, distribution, obsolete control |
59| 5.6 | Management Review | Inputs complete, decisions documented, actions tracked |
60| 6.2 | Training | Competency defined, records complete, effectiveness verified |
61| 7.3 | Design Control | Inputs, reviews, V&V, transfer, changes |
62| 7.4 | Purchasing | Supplier evaluation, incoming inspection |
63| 7.5 | Production | Work instructions, process validation, DHR |
64| 7.6 | Calibration | Equipment list, calibration status, out-of-tolerance |
65| 8.2.2 | Internal Audit | Schedule compliance, auditor independence |
66| 8.3 | NC Product | Identification, segregation, disposition |
67| 8.5 | CAPA | Root cause, implementation, effectiveness |
68
69### Auditor Independence
70
71Verify auditor independence before assignment:
72
73- [ ] Auditor not responsible for area being audited
74- [ ] No direct reporting relationship to auditee
75- [ ] Not involved in recent activities under audit
76- [ ] Documented qualification for audit scope
77
78---
79
80## Audit Execution
81
82Conduct systematic internal audit:
83
841. Prepare audit plan (scope, criteria, schedule)
852. Review relevant documentation before audit
863. Conduct opening meeting with auditee
874. Collect evidence (records, interviews, observation)
885. Classify findings (Major/Minor/Observation)
896. Conduct closing meeting with preliminary findings
907. Prepare audit report within 5 business days
918. **Validation:** All scope items covered, findings supported by evidence
92
93### Evidence Collection
94
95| Method | Use For | Documentation |
96|--------|---------|---------------|
97| Document review | Procedures, records | Document number, version, date |
98| Interview | Process understanding | Interviewee name, role, summary |
99| Observation | Actual practice | What, where, when observed |
100| Record trace | Process flow | Record IDs, dates, linkage |
101
102### Audit Questions by Clause
103
104**Document Control (4.2):**
105- Show me the document master list
106- How do you control obsolete documents?
107- Show me evidence of document change approval
108
109**Design Control (7.3):**
110- Show me the Design History File for [product]
111- Who participates in design reviews?
112- Show me design input to output traceability
113
114**CAPA (8.5):**
115- Show me the CAPA log with open items
116- How do you determine root cause?
117- Show me effectiveness verification records
118
119See `references/iso13485-audit-guide.md` for complete question sets.
120
121### Finding Documentation
122
123Document each finding with:
124
125```
126Requirement: [Specific ISO 13485 clause or procedure]
127Evidence: [What was observed, reviewed, or heard]
128Gap: [How evidence fails to meet requirement]
129```
130
131**Example:**
132```
133Requirement: ISO 13485:2016 Clause 7.6 requires calibration
134at specified intervals.
135
136Evidence: Calibration records for pH meter (EQ-042) show
137last calibration 2024-01-15. Calibration interval is
13812 months. Today is 2025-03-20.
139
140Gap: Equipment is 2 months overdue for calibration,
141representing a gap in calibration program execution.
142```
143
144---
145
146## Nonconformity Management
147
148Classify and manage audit findings:
149
1501. Evaluate finding against classification criteria
1512. Assign severity (Major/Minor/Observation)
1523. Document finding with objective evidence
1534. Communicate to process owner
1545. Initiate CAPA for Major/Minor findings
1556. Track to closure
1567. Verify effectiveness at follow-up
1578. **Validation:** Finding closed only after effective CAPA
158
159### Classification Criteria
160
161| Category | Definition | CAPA Required | Timeline |
162|----------|------------|---------------|----------|
163| Major | Systematic failure or absence of element | Yes | 30 days |
164| Minor | Isolated lapse or partial implementation | Recommended | 60 days |
165| Observation | Improvement opportunity | Optional | As appropriate |
166
167### Classification Decision
168
169```
170Is required element absent or failed?
171├── Yes → Systematic (multiple instances)? → MAJOR
172│ └── No → Could affect product safety? → MAJOR
173│ └── No → MINOR
174└── No → Deviation from procedure?
175 ├── Yes → Recurring? → MAJOR
176 │ └── No → MINOR
177 └── No → Improvement opportunity? → OBSERVATION
178```
179
180### CAPA Integration
181
182| Finding Severity | CAPA Depth | Verification |
183|------------------|------------|--------------|
184| Major | Full root cause analysis (5-Why, Fishbone) | Next audit or within 6 months |
185| Minor | Immediate cause identification | Next scheduled audit |
186| Observation | Not required | Noted at next audit |
187
188See `references/nonconformity-classification.md` for detailed guidance.
189
190---
191
192## External Audit Preparation
193
194Prepare for certification body or regulatory audit:
195
1961. Complete all scheduled internal audits
1972. Verify all findings closed with effective CAPA
1983. Review documentation for currency and accuracy
1994. Conduct management review with audit as input
2005. Prepare facility and personnel
2016. Conduct mock audit (full scope)
2027. Brief personnel on audit protocol
2038. **Validation:** Mock audit findings addressed before external audit
204
205### Pre-Audit Readiness Checklist
206
207**Documentation:**
208- [ ] Quality Manual current
209- [ ] Procedures reflect actual practice
210- [ ] Records complete and retrievable
211- [ ] Previous audit findings closed
212
213**Personnel:**
214- [ ] Key personnel available during audit
215- [ ] Subject matter experts identified
216- [ ] Personnel briefed on audit protocol
217- [ ] Escorts assigned
218
219**Facility:**
220- [ ] Work areas organized
221- [ ] Documents at point of use current
222- [ ] Equipment calibration status visible
223- [ ] Nonconforming product segregated
224
225### Mock Audit Protocol
226
2271. Use external auditor or qualified internal auditor
2282. Cover full scope of upcoming external audit
2293. Simulate actual audit conditions (timing, formality)
2304. Document findings as for real audit
2315. Address all Major and Minor findings before external audit
2326. Brief management on readiness status
233
234---
235
236## Reference Documentation
237
238### ISO 13485 Audit Guide
239
240`references/iso13485-audit-guide.md` contains:
241
242- Clause-by-clause audit methodology
243- Sample audit questions for each clause
244- Evidence collection requirements
245- Common nonconformities by clause
246- Finding severity classification
247
248### Nonconformity Classification
249
250`references/nonconformity-classification.md` contains:
251
252- Severity classification criteria and decision tree
253- Impact vs. occurrence matrix
254- CAPA integration requirements
255- Finding documentation templates
256- Closure requirements by severity
257
258---
259
260## Tools
261
262### Audit Schedule Optimizer
263
264```bash
265# Generate optimized audit schedule
266python scripts/audit_schedule_optimizer.py --processes processes.json
267
268# Interactive mode
269python scripts/audit_schedule_optimizer.py --interactive
270
271# JSON output for integration
272python scripts/audit_schedule_optimizer.py --processes processes.json --output json
273```
274
275Generates risk-based audit schedule considering:
276- Process risk level
277- Previous findings
278- Days since last audit
279- Criticality scores
280
281**Output includes:**
282- Prioritized audit schedule
283- Quarterly distribution
284- Overdue audit alerts
285- Resource recommendations
286
287### Sample Process Input
288
289```json
290{
291 "processes": [
292 {
293 "name": "Design Control",
294 "iso_clause": "7.3",
295 "risk_level": "HIGH",
296 "last_audit_date": "2024-06-15",
297 "previous_findings": 2
298 },
299 {
300 "name": "Document Control",
301 "iso_clause": "4.2",
302 "risk_level": "MEDIUM",
303 "last_audit_date": "2024-09-01",
304 "previous_findings": 0
305 }
306 ]
307}
308```
309
310---
311
312## Audit Program Metrics
313
314Track audit program effectiveness:
315
316| Metric | Target | Measurement |
317|--------|--------|-------------|
318| Schedule compliance | >90% | Audits completed on time |
319| Finding closure rate | >95% | Findings closed by due date |
320| Repeat findings | <10% | Same finding in consecutive audits |
321| CAPA effectiveness | >90% | Verified effective at follow-up |
322| Auditor utilization | 4 days/month | Audit days per qualified auditor |
323
324---
325
326## Troubleshooting
327
328| Problem | Likely Cause | Resolution |
329|---------|-------------|------------|
330| Schedule optimizer produces no audits for a process | `last_audit_date` is recent and risk level is Low | Low-risk processes are scheduled annually. If the last audit was within 365 days, no new audit is generated. Increase `risk_level` or `criticality_score` to trigger earlier scheduling. |
331| Optimizer flags all processes as overdue | Date format in `processes.json` is incorrect | Use ISO 8601 format (`YYYY-MM-DD`) for `last_audit_date`. Invalid dates cause the tool to treat the last audit as missing. |
332| Interactive mode does not accept input | Terminal does not support stdin prompts | Use file-based input with `--processes processes.json` instead of `--interactive`. |
333| Audit schedule does not cover all ISO 13485 clauses | Input process list is incomplete | The optimizer schedules only the processes provided. Ensure all required clauses (4.2, 5.6, 6.2, 7.3, 7.4, 7.5, 7.6, 8.2.2, 8.3, 8.5) are represented in the input. |
334| Finding classified as Minor but should be Major | Classification was applied inconsistently | Apply the decision tree: systematic failure or absent element = Major; isolated lapse = Minor. Consider whether the finding could affect product safety (auto-escalate to Major). |
335| External auditor raises finding already closed internally | CAPA effectiveness verification not completed before external audit | Ensure all internal audit findings have completed CAPA with documented effectiveness verification before the external audit date. Close the loop, do not just complete the action. |
336| Audit report rejected by process owner | Findings not supported by objective evidence | Every finding must reference specific evidence (document number, record ID, observation details). Rework findings using the Requirement-Evidence-Gap format documented in this skill. |
337
338---
339
340## Success Criteria
341
342- Annual audit schedule covers 100% of ISO 13485 clauses with risk-based frequency (quarterly for high-risk, semi-annual for medium, annual for low)
343- Schedule compliance rate exceeds 90% (audits completed on time vs. planned)
344- All Major findings result in full root cause analysis CAPA initiated within 30 days and verified effective within 6 months
345- Finding closure rate exceeds 95% by due date, with no overdue Major findings at any point
346- Repeat finding rate below 10% across consecutive audit cycles, demonstrating effective corrective actions
347- Auditor independence verified and documented for every audit assignment (no self-auditing of own work area)
348- Mock audit conducted before every external certification or surveillance audit with all Major and Minor findings resolved
349
350---
351
352## Scope & Limitations
353
354**In Scope:**
355- ISO 13485:2016 internal audit planning, scheduling, and execution
356- Risk-based audit frequency optimization
357- Nonconformity classification (Major/Minor/Observation) with decision tree
358- CAPA integration for audit findings
359- External audit preparation and mock audit protocols
360- Audit program metrics and effectiveness tracking
361
362**Out of Scope:**
363- External audit execution (this skill supports preparation for and response to external audits, not conducting them)
364- Regulatory inspection management (FDA, Notified Body inspections have jurisdiction-specific protocols beyond internal audit scope)
365- Detailed CAPA root cause analysis methodology (use capa-officer skill for 5-Why, Fishbone, FTA, FMEA)
366- ISO 19011 auditor certification or training program administration
367- Technical product testing or process validation
368- QMSR-specific audit checklist generation (use quality-manager-qms-iso13485 for QMSR gap analysis)
369
370---
371
372## Integration Points
373
374| Skill | Integration |
375|-------|------------|
376| [quality-manager-qms-iso13485](../quality-manager-qms-iso13485/) | Provides the QMS process framework that the audit program evaluates; audit results feed into management review inputs |
377| [capa-officer](../capa-officer/) | Major and Minor audit findings trigger CAPA initiation; CAPA effectiveness verification closes the audit finding loop |
378| [quality-documentation-manager](../quality-documentation-manager/) | Document control audit coverage (Clause 4.2) validates document numbering, approval workflows, and Part 11 compliance |
379| [quality-manager-qmr](../quality-manager-qmr/) | Audit program results are a required management review input (Clause 5.6.2); QMR oversees audit program effectiveness |
380| [risk-management-specialist](../risk-management-specialist/) | Risk management process audit (Clause 7.1) verifies ISO 14971 implementation and risk file completeness |
381
382---
383
384## Tool Reference
385
386### audit_schedule_optimizer.py
387
388Generates risk-based audit schedules optimized by process risk, findings history, and time since last audit.
389
390| Flag | Required | Description |
391|------|----------|-------------|
392| `--processes` | Yes (or `--interactive`) | Path to JSON file containing process definitions with `name`, `iso_clause`, `risk_level` (HIGH/MEDIUM/LOW), `last_audit_date`, `previous_findings`, and `criticality_score` |
393| `--interactive` | No | Launch interactive mode for guided process entry (alternative to file input) |
394| `--output` | No | Output format: `json` for structured output, omit for human-readable text |