Initial commit for iso-13485-certification

This commit is contained in:
dfty
2026-01-28 12:43:37 +08:00
commit eedb52403c
9 changed files with 5133 additions and 0 deletions

View File

@@ -0,0 +1,453 @@
# Corrective and Preventive Action (CAPA) Procedure Template
**Document Number:** SOP-8.5-001
**Title:** Corrective and Preventive Action (CAPA)
**Revision:** 00
**Effective Date:** [DATE]
**Page:** 1 of [X]
---
## DOCUMENT CONTROL
### Approval Signatures
| Role | Name | Signature | Date |
|------|------|-----------|------|
| Author | [NAME] | | [DATE] |
| Reviewer | [NAME] | | [DATE] |
| Approver (Quality Manager) | [NAME] | | [DATE] |
### Revision History
| Revision | Date | Description of Changes | Approved By |
|----------|------|------------------------|-------------|
| 00 | [DATE] | Initial release | [NAME] |
| | | | |
---
## TABLE OF CONTENTS
1. [Purpose](#1-purpose)
2. [Scope](#2-scope)
3. [Definitions](#3-definitions)
4. [Responsibilities](#4-responsibilities)
5. [Procedure](#5-procedure)
- 5.1 [Corrective Action Process](#51-corrective-action-process)
- 5.2 [Preventive Action Process](#52-preventive-action-process)
- 5.3 [CAPA Prioritization](#53-capa-prioritization)
- 5.4 [Investigation and Root Cause Analysis](#54-investigation-and-root-cause-analysis)
- 5.5 [Action Planning and Implementation](#55-action-planning-and-implementation)
- 5.6 [Effectiveness Review](#56-effectiveness-review)
- 5.7 [CAPA Closure](#57-capa-closure)
6. [Records](#6-records)
7. [References](#7-references)
8. [Attachments](#8-attachments)
---
## 1. PURPOSE
This procedure establishes requirements for:
- Corrective action to eliminate causes of nonconformities and prevent recurrence
- Preventive action to eliminate causes of potential nonconformities and prevent occurrence
- Systematic investigation and analysis of problems and risks
- Implementation and verification of effective actions
- Continuous improvement of the Quality Management System
This procedure ensures compliance with ISO 13485:2016 Clauses 8.5.2 (Corrective Action) and 8.5.3 (Preventive Action).
---
## 2. SCOPE
This procedure applies to:
- All nonconformities identified through any means (internal audits, customer complaints, process monitoring, product inspection, etc.)
- Potential nonconformities identified through risk analysis, trend analysis, and proactive reviews
- All products, processes, and QMS elements
- All departments and personnel within [COMPANY NAME]
---
## 3. DEFINITIONS
| Term | Definition |
|------|------------|
| **CAPA** | Corrective and Preventive Action |
| **Corrective Action** | Action to eliminate the cause of a detected nonconformity or other undesirable situation to prevent recurrence |
| **Preventive Action** | Action to eliminate the cause of a potential nonconformity or other potential undesirable situation to prevent occurrence |
| **Nonconformity** | Non-fulfillment of a requirement |
| **Root Cause** | The fundamental reason for the occurrence of a problem |
| **Root Cause Analysis (RCA)** | Systematic process to identify the root cause of a problem |
| **Effectiveness Check** | Verification that implemented actions have achieved the intended result |
| **5 Whys** | Iterative questioning technique used to explore cause-and-effect relationships |
| **Fishbone Diagram** | Visual tool for categorizing potential causes of a problem (also called Ishikawa diagram) |
---
## 4. RESPONSIBILITIES
### 4.1 Quality Manager
- Overall responsibility for CAPA system
- Reviews all CAPAs for adequacy
- Approves CAPA closures
- Reports CAPA metrics in management review
- Ensures resources are available for CAPA activities
### 4.2 CAPA Coordinator
- Manages CAPA database/system
- Assigns CAPA numbers
- Tracks CAPA status and due dates
- Sends reminders for overdue actions
- Generates CAPA metrics and reports
- Maintains CAPA records
### 4.3 CAPA Owner (Assigned Personnel)
- Leads investigation and root cause analysis
- Develops action plan
- Implements corrective/preventive actions
- Coordinates with affected departments
- Documents all CAPA activities
- Performs effectiveness checks
- Requests CAPA closure when complete
### 4.4 Department Managers
- Provide resources and support for CAPA activities
- Participate in investigations within their areas
- Implement actions within their departments
- Verify implementation of actions
### 4.5 All Personnel
- Report nonconformities and improvement opportunities
- Participate in CAPA investigations as requested
- Implement actions assigned to them
- Support CAPA effectiveness
---
## 5. PROCEDURE
### 5.1 Corrective Action Process
Corrective actions are initiated in response to identified nonconformities from sources including:
**Sources of Nonconformities:**
- Customer complaints (per SOP-[NUMBER])
- Internal nonconforming product (per SOP-[NUMBER])
- Internal audit findings (per SOP-[NUMBER])
- Process monitoring out-of-specification results
- Product inspection failures
- Supplier nonconformances
- Regulatory inspections or observations
- Management review action items
- Risk management outputs
- Returned or rejected product
**5.1.1 CAPA Initiation**
1. When a nonconformity is identified, the individual discovering it:
- Completes a CAPA Request Form (Attachment A) or enters information into CAPA system
- Describes the nonconformity clearly and completely
- Attaches supporting documentation (NCRs, complaints, audit findings, etc.)
- Submits to Quality department
2. CAPA Coordinator:
- Receives CAPA request
- Assigns unique CAPA number: CAPA-[YEAR]-[###]
- Logs CAPA in tracking system
- Routes to Quality Manager for review
3. Quality Manager:
- Reviews CAPA request for completeness and clarity
- Determines if corrective action is warranted
- Assigns priority (see Section 5.3)
- Assigns CAPA Owner
- Sets due date based on priority
- Approves initiation of CAPA investigation
### 5.2 Preventive Action Process
Preventive actions are initiated proactively to address potential problems before they occur.
**Sources of Preventive Action:**
- Trend analysis of complaints, NCRs, or other data
- Risk management activities (per SOP-[NUMBER])
- Process capability studies
- Near-miss events
- Lessons learned from other organizations or devices
- Changes in regulations or standards
- Proactive process improvements
- Management review outputs
- Employee suggestions
**5.2.1 Preventive Action Initiation**
Process is similar to corrective action (Section 5.1.1), but:
- Describes potential nonconformity and its possible consequences
- Includes data or rationale supporting the need for preventive action
- May have different prioritization based on risk of occurrence
### 5.3 CAPA Prioritization
All CAPAs are prioritized based on:
- Severity of impact (safety, regulatory, customer impact)
- Frequency or likelihood of occurrence
- Detectability before reaching customer
**Priority Levels:**
| Priority | Criteria | Due Date for Completion |
|----------|----------|-------------------------|
| **Critical** | Safety issue, regulatory requirement, major customer impact, Class I recall potential | [X] days |
| **High** | Significant quality impact, repeat issue, moderate customer impact, regulatory reporting | [X] days |
| **Medium** | Moderate impact, isolated occurrence, minor customer impact | [X] days |
| **Low** | Minor impact, isolated occurrence, no customer impact, improvement opportunity | [X] days |
Priority is determined by Quality Manager in consultation with CAPA Owner and affected department managers.
### 5.4 Investigation and Root Cause Analysis
**5.4.1 Investigation Planning**
CAPA Owner develops investigation plan including:
- Scope of investigation
- Team members needed (if applicable)
- Data to be collected
- Analysis methods to be used
- Timeline
**5.4.2 Data Collection**
Collect relevant data:
- Review related records (batch records, inspection records, training records, etc.)
- Interview personnel involved
- Review similar past occurrences
- Examine physical evidence (product samples, equipment, etc.)
- Review applicable procedures and work instructions
- Analyze trend data if available
**5.4.3 Root Cause Analysis**
Use appropriate RCA tools based on complexity:
**For Simple Issues:**
- 5 Whys technique
- Cause and effect analysis
**For Complex Issues:**
- Fishbone (Ishikawa) diagram
- Fault tree analysis
- Failure mode and effects analysis (FMEA)
- Statistical analysis
**RCA Requirements:**
- Dig beyond superficial causes to find root cause
- Distinguish between symptoms and causes
- Consider multiple contributing factors
- Ask "why" repeatedly until fundamental cause identified
- Consider human factors, procedural inadequacies, system weaknesses
- Document analysis process and findings
**5.4.4 Root Cause Documentation**
Document in CAPA record:
- Summary of investigation findings
- Root cause(s) identified
- Supporting data and analysis
- RCA tool(s) used
- Team members involved
- Date investigation completed
Quality Manager reviews and approves root cause determination.
### 5.5 Action Planning and Implementation
**5.5.1 Action Planning**
Based on root cause, CAPA Owner develops action plan:
**Actions must be:**
- **Effective:** Address root cause, not just symptoms
- **Achievable:** Realistic with available resources
- **Measurable:** Include objective success criteria
- **Timely:** Include target completion dates
- **Risk-appropriate:** Commensurate with severity and likelihood
**Action Plan includes:**
- Specific actions to be taken
- Responsible person for each action
- Target completion date for each action
- Resources required
- Expected outcome/success criteria
- How effectiveness will be measured
**5.5.2 Types of Actions**
Actions may include:
- Procedure revisions or clarifications
- Training or retraining
- Equipment repair, replacement, or modification
- Process changes or improvements
- Design changes (when applicable)
- Supplier corrective action requests
- Increased inspection or monitoring
- Software updates or validation
- Physical facility changes
- Organizational changes
**5.5.3 Action Approval**
- CAPA Owner submits action plan to Quality Manager
- Quality Manager reviews for adequacy and appropriateness
- Department Managers review actions affecting their areas
- Quality Manager approves action plan
- Actions assigned to responsible parties with due dates
**5.5.4 Implementation**
- Responsible parties implement assigned actions
- Implementation is documented (procedure revisions, training records, etc.)
- CAPA Owner tracks implementation progress
- CAPA Coordinator sends reminders for overdue actions
- Interim updates provided for long-duration CAPAs
**5.5.5 Documentation of Implementation**
For each action, document:
- Date implemented
- Evidence of implementation (updated procedures, training records, work orders, etc.)
- Any deviations from planned actions and justification
- Responsible person confirmation
### 5.6 Effectiveness Review
**5.6.1 Timing of Effectiveness Check**
Effectiveness is verified after:
- Sufficient time has passed to observe results
- Minimum: [X days/weeks] after implementation
- Extended period for process or trend verification: [X months]
- Timing based on priority and nature of issue
**5.6.2 Effectiveness Verification Methods**
Methods appropriate to the CAPA may include:
- Review of process or product data for improved performance
- Inspection or test results showing improvement
- Absence of recurrence over defined period
- Customer feedback or complaint trends
- Internal audit verification
- Process capability analysis
- Statistical analysis of relevant metrics
- Re-audit of corrective action area
- Follow-up inspection or testing
**5.6.3 Effectiveness Determination**
CAPA Owner:
- Collects effectiveness data using planned method
- Analyzes data to determine if actions achieved intended result
- Documents findings in CAPA record
- Recommends effectiveness status:
- **Effective:** Actions achieved intended result, no recurrence
- **Not Effective:** Actions did not achieve intended result, recurrence observed
- **Additional Data Needed:** Insufficient time or data to determine effectiveness
**5.6.4 Ineffective Actions**
If actions determined not effective:
- CAPA remains open
- Re-investigation performed
- Alternative actions developed
- Cycle repeats until effectiveness achieved
### 5.7 CAPA Closure
**5.7.1 Closure Criteria**
CAPA may be closed when:
- All planned actions implemented and verified
- Effectiveness check completed and actions determined effective
- All documentation complete
- No recurrence of issue during effectiveness period
**5.7.2 Closure Process**
1. CAPA Owner:
- Verifies all closure criteria met
- Completes final CAPA summary
- Submits closure request to Quality Manager
2. Quality Manager:
- Reviews entire CAPA record for completeness
- Verifies effectiveness evidence
- Approves closure or requests additional information
- Signs and dates CAPA closure
3. CAPA Coordinator:
- Updates CAPA status to "Closed"
- Files CAPA record per retention requirements
- Updates metrics and reports
**5.7.3 CAPA Extension**
If additional time needed:
- CAPA Owner submits extension request with justification
- Quality Manager reviews and approves/denies extension
- New due date established
- Extension documented in CAPA record
---
## 6. RECORDS
Records generated and maintained per this procedure:
| Record | Retention Period | Location | Responsible Party |
|--------|------------------|----------|-------------------|
| CAPA Request Forms | [X years or device lifetime] | [LOCATION/SYSTEM] | CAPA Coordinator |
| CAPA Investigation Records | [X years or device lifetime] | [LOCATION/SYSTEM] | CAPA Coordinator |
| Root Cause Analysis Documentation | [X years or device lifetime] | [LOCATION/SYSTEM] | CAPA Coordinator |
| Action Plans | [X years or device lifetime] | [LOCATION/SYSTEM] | CAPA Coordinator |
| Implementation Evidence | [X years or device lifetime] | [LOCATION/SYSTEM] | CAPA Coordinator |
| Effectiveness Verification Records | [X years or device lifetime] | [LOCATION/SYSTEM] | CAPA Coordinator |
| CAPA Closure Approvals | [X years or device lifetime] | [LOCATION/SYSTEM] | CAPA Coordinator |
| CAPA Metrics and Trend Reports | [X years] | [LOCATION] | Quality Manager |
---
## 7. REFERENCES
- ISO 13485:2016, Clause 8.5.2 - Corrective Action
- ISO 13485:2016, Clause 8.5.3 - Preventive Action
- Quality Manual, Section 8.5
- SOP-[NUMBER] - Control of Nonconforming Product
- SOP-[NUMBER] - Complaint Handling
- SOP-[NUMBER] - Internal Audit
- SOP-[NUMBER] - Risk Management
- SOP-[NUMBER] - Analysis of Data
---
## 8. ATTACHMENTS
**Attachment A:** CAPA Request Form
**Attachment B:** Root Cause Analysis Worksheet
**Attachment C:** CAPA Action Plan Template
**Attachment D:** Effectiveness Verification Checklist
**Attachment E:** 5 Whys Worksheet
**Attachment F:** Fishbone Diagram Template
**Attachment G:** CAPA Flowchart
---
**END OF PROCEDURE**
---
**Document Number:** SOP-8.5-001
**Revision:** 00
**Page:** [X] of [X]

View File

@@ -0,0 +1,567 @@
# Document Control Procedure Template
**Document Number:** SOP-4.2.4-001
**Title:** Control of Documents
**Revision:** 00
**Effective Date:** [DATE]
**Page:** 1 of [X]
---
## DOCUMENT CONTROL
### Approval Signatures
| Role | Name | Signature | Date |
|------|------|-----------|------|
| Author | [NAME] | | [DATE] |
| Reviewer | [NAME] | | [DATE] |
| Approver (Quality Manager) | [NAME] | | [DATE] |
### Revision History
| Revision | Date | Description of Changes | Approved By |
|----------|------|------------------------|-------------|
| 00 | [DATE] | Initial release | [NAME] |
| | | | |
---
## TABLE OF CONTENTS
1. [Purpose](#1-purpose)
2. [Scope](#2-scope)
3. [Definitions](#3-definitions)
4. [Responsibilities](#4-responsibilities)
5. [Procedure](#5-procedure)
- 5.1 [Document Types and Hierarchy](#51-document-types-and-hierarchy)
- 5.2 [Document Numbering System](#52-document-numbering-system)
- 5.3 [Document Creation](#53-document-creation)
- 5.4 [Document Review and Approval](#54-document-review-and-approval)
- 5.5 [Document Distribution and Access](#55-document-distribution-and-access)
- 5.6 [Document Changes](#56-document-changes)
- 5.7 [Control of Obsolete Documents](#57-control-of-obsolete-documents)
- 5.8 [Control of External Documents](#58-control-of-external-documents)
6. [Records](#6-records)
7. [References](#7-references)
8. [Attachments](#8-attachments)
---
## 1. PURPOSE
This procedure establishes requirements for the control of documents within the Quality Management System to ensure:
- Documents are approved before use
- Documents are reviewed, updated, and re-approved as necessary
- Changes and current revision status are identified
- Relevant versions of documents are available at points of use
- Documents remain legible and readily identifiable
- External documents are identified and controlled
- Obsolete documents are prevented from unintended use
- Obsolete documents are appropriately identified if retained
This procedure ensures compliance with ISO 13485:2016 Clause 4.2.4.
---
## 2. SCOPE
This procedure applies to all controlled documents within the Quality Management System, including but not limited to:
- Quality Manual
- Standard Operating Procedures (SOPs)
- Work Instructions (WIs)
- Forms and templates
- Medical Device Files
- Design and Development documents
- Risk management documents
- Validation and verification protocols and reports
- Specifications (product, process, test methods, materials)
- Drawings and schematics
- Labels and instructions for use
- External documents (standards, regulations, customer specifications)
This procedure does NOT apply to:
- Records (controlled per SOP-[NUMBER] Control of Records)
- Transient documents (emails, meeting notes not part of QMS)
- Marketing and sales materials (unless affecting product quality or regulatory compliance)
---
## 3. DEFINITIONS
| Term | Definition |
|------|------------|
| **Controlled Document** | A document that is subject to review, approval, distribution control, and change management per this procedure |
| **Master Document** | The official controlled copy maintained by Document Control, from which all distributed copies originate |
| **Document Owner** | The person or department responsible for the content, accuracy, and maintenance of a document |
| **Document Control Coordinator** | Person responsible for managing the document control system |
| **Revision** | A change to a controlled document that has been approved and issued |
| **Obsolete Document** | A document that has been superseded by a newer revision or is no longer applicable |
| **External Document** | A document originating from outside the organization (standards, regulations, customer specifications, etc.) |
| **SUPERSEDED** | Watermark applied to obsolete documents retained for reference |
---
## 4. RESPONSIBILITIES
### 4.1 Document Control Coordinator
- Manages document control system
- Assigns document numbers
- Maintains master document repository
- Ensures proper document approval before release
- Distributes controlled documents
- Maintains distribution lists
- Retrieves and destroys/archives obsolete documents
- Maintains document control records
- Trains personnel on document control procedures
### 4.2 Document Owners
- Create and maintain documents within their area
- Ensure document accuracy and completeness
- Initiate document changes when needed
- Participate in document review and approval
- Identify when documents become obsolete
- Ensure personnel in their area use current documents
### 4.3 Quality Manager
- Approves all QMS documents (SOPs, Quality Manual)
- Reviews document changes for QMS impact
- Ensures document control system effectiveness
- Audits document control compliance
### 4.4 Department Managers
- Approve department-specific work instructions
- Ensure current documents available in their areas
- Ensure personnel trained on document changes
- Remove obsolete documents from use areas
### 4.5 All Personnel
- Use only current, approved documents
- Report document issues (errors, illegibility, missing documents)
- Do not use obsolete or unapproved documents
- Maintain documents in good condition
---
## 5. PROCEDURE
### 5.1 Document Types and Hierarchy
QMS documents are organized in a four-tier hierarchy:
**Tier 1: Quality Manual (QM)**
- Policy-level document
- Describes overall QMS
- References all Tier 2 procedures
- Approved by CEO and Quality Manager
**Tier 2: Standard Operating Procedures (SOPs)**
- Define WHAT must be done, WHO does it, WHEN
- Cross-functional processes
- Include all 31 required documented procedures per ISO 13485
- Approved by Quality Manager
**Tier 3: Work Instructions (WIs)**
- Define HOW to perform specific tasks
- Step-by-step instructions
- Department or process-specific
- Approved by Department Manager and Quality Manager
**Tier 4: Forms and Templates**
- Standardized formats for data collection
- Support SOPs and WIs
- Approved by Document Owner and Quality Manager
**Other Controlled Documents:**
- Medical Device Files (MDFs)
- Design History Files (DHFs)
- Validation documents
- Specifications
- Drawings
- Labels and instructions for use
### 5.2 Document Numbering System
All controlled documents are assigned unique identification numbers:
**Quality Manual:**
- Format: QM-[###]
- Example: QM-001
**Standard Operating Procedures:**
- Format: SOP-[ISO Clause]-[###]
- Example: SOP-4.2.4-001 (for Clause 4.2.4 Control of Documents)
- Example: SOP-8.5-001 (for CAPA procedure)
**Work Instructions:**
- Format: WI-[Department Code]-[###]
- Example: WI-MFG-001 (Manufacturing department work instruction)
- Department codes: MFG (Manufacturing), QC (Quality Control), ENG (Engineering), etc.
**Forms:**
- Format: FORM-[SOP/WI Number]-[Letter]
- Example: FORM-SOP-8.5-001-A (CAPA Request Form)
**Medical Device Files:**
- Format: MDF-[Product Code]-[###]
- Example: MDF-ABC-001
**Other Documents:**
- Format varies by document type
- Assigned by Document Control Coordinator
**Revision Designation:**
- Initial release: Revision 00
- First revision: Revision 01
- Subsequent revisions: 02, 03, 04, etc.
- Format: [Document Number] Rev [##]
### 5.3 Document Creation
**5.3.1 Initiating Document Creation**
1. Document Owner identifies need for new document
2. Document Owner notifies Document Control Coordinator
3. Document Control Coordinator:
- Assigns document number
- Provides document template (if applicable)
- Logs document in master list as "In Development"
**5.3.2 Document Format Requirements**
All controlled documents must include:
**Header (on each page):**
- Document number
- Document title
- Revision number
- Effective date
- Page number (Page X of Y)
**Document Control Section:**
- Approval signature table
- Revision history table
**Content Requirements:**
- Clear, concise language
- Present tense, active voice
- Consistent terminology
- Numbered sections and subsections
- References to related documents
- Records generated (if applicable)
**5.3.3 Document Drafting**
1. Document Owner drafts document content
2. Document Owner marks document as "DRAFT" on each page
3. Draft may be circulated for informal review and input
4. When ready for formal review, Document Owner submits to Document Control Coordinator
### 5.4 Document Review and Approval
**5.4.1 Review Process**
1. Document Control Coordinator:
- Verifies document number correct
- Verifies format compliance
- Checks for required sections
- Routes for review
2. Reviews conducted by:
- Technical reviewer (subject matter expert)
- Quality reviewer (for QMS compliance)
- Other stakeholders as appropriate
3. Reviewers:
- Review for technical accuracy
- Review for clarity and completeness
- Review for compliance with requirements
- Provide comments to Document Owner
4. Document Owner:
- Addresses all comments
- Revises document as needed
- Resubmits for approval
**5.4.2 Approval Process**
Approval authority based on document type:
| Document Type | Approval Authority |
|---------------|-------------------|
| Quality Manual | CEO and Quality Manager |
| Standard Operating Procedures | Quality Manager |
| Work Instructions | Department Manager and Quality Manager |
| Forms | Document Owner and Quality Manager |
| Specifications | Engineering Manager and Quality Manager |
| Medical Device Files | [Per regulatory requirements] |
**Approval Steps:**
1. Document Control Coordinator routes document to approvers
2. Approvers review and sign/date approval section
3. All required approvals must be obtained before document becomes effective
4. Document Control Coordinator:
- Removes "DRAFT" watermark
- Adds effective date (typically [X] days after approval)
- Assigns final format
- Adds to controlled document system
- Updates master document list
**5.4.3 Training Requirements**
Before document becomes effective:
- Affected personnel identified
- Training conducted as needed
- Training records maintained per SOP-[NUMBER]
### 5.5 Document Distribution and Access
**5.5.1 Master Document**
- Document Control Coordinator maintains master copy
- Master stored in: [ELECTRONIC SYSTEM or PHYSICAL LOCATION]
- Master clearly identified as "MASTER COPY"
- Master is reference for all distributed copies
**5.5.2 Controlled Copies**
**Electronic Distribution (Primary Method):**
- Documents stored in [DOCUMENT MANAGEMENT SYSTEM]
- Access controlled by user permissions
- Read-only access for most users
- Always displays current revision
- Obsolete revisions automatically removed from access
- Users may print for immediate use (uncontrolled copies)
**Physical Distribution (When Necessary):**
- Controlled copies issued for specific locations/uses
- Each copy stamped "CONTROLLED COPY - [Copy Number]"
- Distribution list maintained showing:
- Copy number
- Document number and revision
- Holder name and location
- Date issued
- Holders responsible for maintaining copy in good condition
- When document revised, Document Control retrieves old copy and issues new copy
**5.5.3 Uncontrolled Copies**
- Printed for temporary, immediate use
- Stamped or marked "UNCONTROLLED COPY"
- User responsible for verifying current revision before each use
- Should be destroyed after use or within [X] days
**5.5.4 Availability at Point of Use**
- Current documents available where work is performed
- Electronic access at workstations
- Controlled physical copies in areas without electronic access
- Documents protected from damage, loss, deterioration
### 5.6 Document Changes
**5.6.1 Initiating Changes**
Changes may be initiated by:
- Document Owner identifying need
- CAPA requiring procedure change
- Internal audit finding
- Management review action
- Regulatory or standard update
- Process improvement
**5.6.2 Change Request Process**
1. Requestor:
- Completes Document Change Request Form (Attachment A)
- Describes change needed and justification
- Submits to Document Owner
2. Document Owner:
- Reviews change request
- Determines if change appropriate
- Approves or denies request
- If approved, initiates document revision
**5.6.3 Making Changes**
1. Document Owner:
- Requests current master from Document Control
- Creates revised version with changes
- Increments revision number
- Updates revision history table
- Identifies changes in document (change bars, highlights, or summary)
- Marks as "DRAFT REVISION"
2. Changes reviewed and approved by:
- Same approval authority as original document
- UNLESS different approval authority designated by original approver
- Reviewers have access to previous revision for comparison
3. Approval:
- New revision approved per Section 5.4.2
- Previous revision becomes obsolete on effective date of new revision
**5.6.4 Indication of Changes**
Changes are indicated by:
- Revision history table (describes nature of changes)
- Change bars or highlights in document (optional but recommended)
- Change summary page for significant revisions (optional)
**5.6.5 Urgent Changes**
For urgent changes affecting safety or regulatory compliance:
- Expedited review and approval process
- May use interim method (e.g., hand-written changes with approval)
- Formal document revision completed as soon as practical
- Document per CAPA process if change due to nonconformity
### 5.7 Control of Obsolete Documents
**5.7.1 When Document Becomes Obsolete**
Document becomes obsolete when:
- New revision approved and becomes effective
- Document no longer applicable to operations
- Product discontinued
- Process changed
**5.7.2 Removal from Use**
1. Document Control Coordinator:
- On effective date of new revision, marks superseded revision as obsolete
- Removes from electronic document system OR limits access with "OBSOLETE" notation
- Retrieves physical controlled copies from distribution locations
- Updates distribution lists
2. Department Managers:
- Remove obsolete copies from work areas
- Return to Document Control or destroy
- Ensure personnel aware of new revision
**5.7.3 Retention of Obsolete Documents**
Obsolete documents may be retained for:
- Reference purposes
- Product investigations
- Regulatory or legal requirements
- Historical record
**If retained:**
- Clearly marked "OBSOLETE - FOR REFERENCE ONLY" or "SUPERSEDED"
- Stored separately from current documents
- Access restricted and controlled
- Retained per applicable retention requirements
**Retention Locations:**
- Electronic archive with "OBSOLETE" watermark
- Separate physical archive area
**5.7.4 Prevention of Unintended Use**
To prevent unintended use:
- Physical copies stamped "OBSOLETE" in red
- Electronic copies watermarked "OBSOLETE"
- Removed from active work areas
- Stored in separate archive
- Training on document control system and how to verify current revision
### 5.8 Control of External Documents
**5.8.1 Types of External Documents**
External documents include:
- ISO standards
- IEC standards
- FDA regulations and guidance documents
- EU regulations (MDR, IVDR)
- Other regulatory requirements
- Customer specifications
- Supplier certifications
- Calibration certificates
- Reference materials
**5.8.2 Identification and Control**
1. Document Owner or requestor:
- Identifies external document needed
- Provides copy to Document Control Coordinator
2. Document Control Coordinator:
- Assigns external document number: EXT-[Category]-[###]
- Logs in external document register including:
- Document title and number
- Source/publisher
- Date/version
- Location in organization
- Responsible person for monitoring updates
- Files in external document repository
**5.8.3 Reviewing for Currency**
- Document Owner responsible for monitoring updates to external documents
- Frequency: [Annually or as notified of updates]
- Check publisher website for updates
- Subscribe to update notifications when available
- When update identified:
- Obtain new version
- Provide to Document Control
- Review for impact on QMS documents
- Update QMS documents as needed (per CAPA if necessary)
- Obsolete previous version per Section 5.7
**5.8.4 Customer-Supplied Documents**
- Customer specifications and drawings controlled as external documents
- Review for clarity and completeness upon receipt
- Discrepancies communicated to customer for resolution
- Controlled per this procedure to ensure current version used
---
## 6. RECORDS
Records generated and maintained per this procedure:
| Record | Retention Period | Location | Responsible Party |
|--------|------------------|----------|-------------------|
| Master Document List | Current + [X] years | [LOCATION/SYSTEM] | Document Control Coordinator |
| Document Approval Records | [X years or device lifetime] | Document Control System | Document Control Coordinator |
| Document Revision History | [X years or device lifetime] | Document Control System | Document Control Coordinator |
| Document Change Requests | [X years] | [LOCATION] | Document Control Coordinator |
| Distribution Lists | Current + [X] years | [LOCATION] | Document Control Coordinator |
| Obsolete Document Archive | [Per retention schedule] | [LOCATION] | Document Control Coordinator |
| External Document Register | Current + [X] years | [LOCATION] | Document Control Coordinator |
---
## 7. REFERENCES
- ISO 13485:2016, Clause 4.2.4 - Control of Documents
- Quality Manual, Section 4.2.4
- SOP-4.2.5 - Control of Records
- SOP-6.2 - Training and Competence
---
## 8. ATTACHMENTS
**Attachment A:** Document Change Request Form
**Attachment B:** Document Templates (QM, SOP, WI, Form)
**Attachment C:** Document Control Flowchart
**Attachment D:** Master Document List Template
**Attachment E:** Distribution List Template
---
**END OF PROCEDURE**
---
**Document Number:** SOP-4.2.4-001
**Revision:** 00
**Page:** [X] of [X]

View File

@@ -0,0 +1,521 @@
# Quality Manual Template
# [COMPANY NAME]
## QUALITY MANUAL
**Document Number:** QM-001
**Revision:** 00
**Effective Date:** [DATE]
**Page:** 1 of [X]
---
## DOCUMENT CONTROL
### Approval Signatures
| Role | Name | Signature | Date |
|------|------|-----------|------|
| Chief Executive Officer | [NAME] | | [DATE] |
| Quality Manager | [NAME] | | [DATE] |
| Management Representative | [NAME] | | [DATE] |
### Revision History
| Revision | Date | Description of Changes | Approved By |
|----------|------|------------------------|-------------|
| 00 | [DATE] | Initial release | [NAME] |
| | | | |
### Distribution List
| Copy No. | Holder | Location | Date Issued |
|----------|--------|----------|-------------|
| 001 | Master Copy | Document Control | [DATE] |
| 002 | [NAME/DEPT] | [LOCATION] | [DATE] |
| | | | |
---
## TABLE OF CONTENTS
1. [Introduction](#1-introduction)
- 1.1 [Company Overview](#11-company-overview)
- 1.2 [Purpose of the Quality Manual](#12-purpose-of-the-quality-manual)
- 1.3 [Document Control and Revisions](#13-document-control-and-revisions)
- 1.4 [Definitions and Abbreviations](#14-definitions-and-abbreviations)
2. [Scope and Exclusions](#2-scope-and-exclusions)
- 2.1 [Scope of QMS](#21-scope-of-qms)
- 2.2 [Products Covered](#22-products-covered)
- 2.3 [Applicable Regulatory Requirements](#23-applicable-regulatory-requirements)
- 2.4 [Exclusions and Justifications](#24-exclusions-and-justifications)
3. [Quality Policy and Objectives](#3-quality-policy-and-objectives)
- 3.1 [Quality Policy Statement](#31-quality-policy-statement)
- 3.2 [Quality Objectives](#32-quality-objectives)
- 3.3 [Communication of Policy and Objectives](#33-communication-of-policy-and-objectives)
4. [Quality Management System](#4-quality-management-system)
- 4.1 [General Requirements](#41-general-requirements)
- 4.2 [Documentation Requirements](#42-documentation-requirements)
5. [Management Responsibility](#5-management-responsibility)
- 5.1 [Management Commitment](#51-management-commitment)
- 5.2 [Customer Focus](#52-customer-focus)
- 5.3 [Quality Policy](#53-quality-policy)
- 5.4 [Planning](#54-planning)
- 5.5 [Responsibility, Authority and Communication](#55-responsibility-authority-and-communication)
- 5.6 [Management Review](#56-management-review)
6. [Resource Management](#6-resource-management)
- 6.1 [Provision of Resources](#61-provision-of-resources)
- 6.2 [Human Resources](#62-human-resources)
- 6.3 [Infrastructure](#63-infrastructure)
- 6.4 [Work Environment and Contamination Control](#64-work-environment-and-contamination-control)
7. [Product Realization](#7-product-realization)
- 7.1 [Planning of Product Realization](#71-planning-of-product-realization)
- 7.2 [Customer-Related Processes](#72-customer-related-processes)
- 7.3 [Design and Development](#73-design-and-development)
- 7.4 [Purchasing](#74-purchasing)
- 7.5 [Production and Service Provision](#75-production-and-service-provision)
- 7.6 [Control of Monitoring and Measuring Equipment](#76-control-of-monitoring-and-measuring-equipment)
8. [Measurement, Analysis and Improvement](#8-measurement-analysis-and-improvement)
- 8.1 [General](#81-general)
- 8.2 [Monitoring and Measurement](#82-monitoring-and-measurement)
- 8.3 [Control of Nonconforming Product](#83-control-of-nonconforming-product)
- 8.4 [Analysis of Data](#84-analysis-of-data)
- 8.5 [Improvement](#85-improvement)
9. [Appendices](#9-appendices)
- Appendix A: [List of Documented Procedures](#appendix-a-list-of-documented-procedures)
- Appendix B: [Organization Chart](#appendix-b-organization-chart)
- Appendix C: [Process Map](#appendix-c-process-map)
- Appendix D: [Definitions and Abbreviations](#appendix-d-definitions-and-abbreviations)
- Appendix E: [Applicable Regulatory Requirements](#appendix-e-applicable-regulatory-requirements)
---
## 1. INTRODUCTION
### 1.1 Company Overview
**Company Legal Name:** [FULL LEGAL COMPANY NAME]
**Business Address:** [STREET ADDRESS, CITY, STATE/PROVINCE, ZIP/POSTAL CODE, COUNTRY]
**Manufacturing Site(s):** [LIST ALL MANUFACTURING SITES]
**Type of Business:** [e.g., Medical Device Manufacturer, Contract Manufacturer, etc.]
[COMPANY NAME] was [established/founded] in [YEAR] and specializes in [BRIEF DESCRIPTION OF BUSINESS FOCUS].
**Mission Statement:** [INSERT COMPANY MISSION STATEMENT]
### 1.2 Purpose of the Quality Manual
This Quality Manual documents the Quality Management System (QMS) of [COMPANY NAME]. The purpose of this manual is to:
- Describe the QMS established and maintained in accordance with ISO 13485:2016
- Demonstrate compliance with applicable regulatory requirements
- Serve as the primary reference document for the structure and operation of the QMS
- Provide guidance for employees, customers, regulatory authorities, and certification bodies
This manual applies to all activities affecting the quality of medical devices designed, manufactured, distributed, and/or serviced by [COMPANY NAME].
### 1.3 Document Control and Revisions
This Quality Manual is a controlled document. The Document Control Coordinator maintains the master copy and distribution list.
- **Approval Authority:** Chief Executive Officer and Quality Manager
- **Review Frequency:** Annually, or as needed when significant changes occur
- **Revision Process:** Changes are reviewed and approved per SOP-4.2.4 Control of Documents
- **Distribution:** Controlled copies are issued to individuals listed in the Distribution List
All recipients of controlled copies are responsible for ensuring they are using the current revision.
### 1.4 Definitions and Abbreviations
| Term/Abbreviation | Definition |
|-------------------|------------|
| CAPA | Corrective and Preventive Action |
| CFR | Code of Federal Regulations |
| DHF | Design History File |
| DHR | Device History Record |
| DMR | Device Master Record |
| FDA | U.S. Food and Drug Administration |
| IFU | Instructions for Use |
| ISO | International Organization for Standardization |
| MDF | Medical Device File |
| MDR | Medical Device Regulation (EU) |
| M&M Equipment | Monitoring and Measuring Equipment |
| NCR | Nonconformance Report |
| QMS | Quality Management System |
| QMSR | Quality Management System Regulation (FDA) |
| QSR | Quality System Regulation (FDA - former) |
| SOP | Standard Operating Procedure |
| WI | Work Instruction |
---
## 2. SCOPE AND EXCLUSIONS
### 2.1 Scope of QMS
This Quality Management System applies to [COMPANY NAME] and covers all activities related to [LIST ACTIVITIES: e.g., design, development, production, storage, distribution, installation, servicing] of medical devices.
**Organizational Scope:**
- All departments and functions at [COMPANY NAME]
- All employees, contractors, and temporary staff performing work affecting product quality
**Physical Locations:**
- [LIST ALL FACILITIES AND ADDRESSES]
**Activities Covered:**
- [✓ / ✗] Design and Development
- [✓ / ✗] Manufacturing and Production
- [✓ / ✗] Installation
- [✓ / ✗] Servicing
- [✓] Storage and Distribution
- [✓] Purchasing
- [✓] Customer Communication
### 2.2 Products Covered
This QMS covers the following medical device product families:
| Product Family | Device Classification | Intended Use | Applicable Markets |
|----------------|----------------------|--------------|-------------------|
| [PRODUCT NAME/FAMILY] | [Class I/II/III] | [BRIEF INTENDED USE] | [FDA/EU/Other] |
| | | | |
### 2.3 Applicable Regulatory Requirements
The QMS is designed to comply with the following standards and regulatory requirements:
**International Standards:**
- ISO 13485:2016 - Medical devices — Quality management systems — Requirements for regulatory purposes
- ISO 14971:[YEAR] - Medical devices — Application of risk management to medical devices
- [OTHER APPLICABLE ISO/IEC STANDARDS]
**Regulatory Requirements:**
- **United States:** FDA 21 CFR Part 820 (QMSR) - Quality Management System Regulation
- **European Union:** EU MDR 2017/745 - Medical Devices Regulation [or IVDR 2017/746 for IVDs]
- **Canada:** Canadian Medical Devices Regulations (SOR/98-282)
- [OTHER APPLICABLE REGIONAL REQUIREMENTS]
**Recognized Standards:**
- [LIST PRODUCT-SPECIFIC STANDARDS, e.g., IEC 60601, ISO 10993, etc.]
### 2.4 Exclusions and Justifications
The following clauses of ISO 13485:2016 are excluded from the scope of this QMS:
[IF NO EXCLUSIONS:]
> There are no exclusions from ISO 13485:2016. All clauses are applicable and have been implemented.
[IF EXCLUSIONS EXIST, USE THIS FORMAT:]
**Clause 7.3 - Design and Development**
**Status:** [EXCLUDED / PARTIALLY EXCLUDED / FULLY IMPLEMENTED]
**Justification (if excluded):**
> [COMPANY NAME] [operates as a contract manufacturer and produces medical devices according to complete design specifications provided by customers / only distributes medical devices designed and manufactured by third parties / etc.]. All design and development activities are [performed by customers / performed by a separate corporate entity / not applicable to business model]. [COMPANY NAME] has no responsibility for design inputs, outputs, verification, validation, design changes, or design history files.
**Clause 7.5.3 - Installation Activities**
**Status:** [EXCLUDED / PARTIALLY EXCLUDED / FULLY IMPLEMENTED]
**Justification (if excluded):**
> The medical devices manufactured by [COMPANY NAME] are [supplied ready for use and do not require installation / intended for installation by customer personnel under separate contractual arrangements]. Installation activities are [not performed / performed by authorized distributors or customers].
**Clause 7.5.4 - Servicing Activities**
**Status:** [EXCLUDED / PARTIALLY EXCLUDED / FULLY IMPLEMENTED]
**Justification (if excluded):**
> [COMPANY NAME] does not provide servicing of medical devices after delivery. Products are [intended for single use / serviced by authorized service partners under separate arrangements / serviced by customer personnel]. Post-delivery activities are limited to technical support and complaint handling.
---
## 3. QUALITY POLICY AND OBJECTIVES
### 3.1 Quality Policy Statement
**QUALITY POLICY**
[INSERT YOUR COMPANY-SPECIFIC QUALITY POLICY HERE. The policy should include:
- Commitment to meeting customer and regulatory requirements
- Commitment to maintaining QMS effectiveness
- Framework for quality objectives
- Signature of top management
- Date
Example:]
> At [COMPANY NAME], quality is our highest priority. We are committed to designing, manufacturing, and delivering medical devices that meet the highest standards of safety, performance, and reliability.
>
> Our commitments include:
> - Compliance with ISO 13485 and all applicable regulatory requirements
> - Understanding and meeting customer and patient needs
> - Establishing and achieving measurable quality objectives
> - Managing risks throughout the product lifecycle
> - Continually improving our processes and products
> - Maintaining competent and motivated personnel
> - Responding promptly and effectively to feedback and complaints
>
> This policy applies to all employees, contractors, and suppliers. This policy is reviewed annually and communicated throughout the organization.
>
> [SIGNATURE]
> [NAME], Chief Executive Officer
> [DATE]
### 3.2 Quality Objectives
The organization has established the following measurable quality objectives to support the Quality Policy:
| Objective | Measurement | Target | Responsibility | Review Frequency |
|-----------|-------------|--------|----------------|------------------|
| Customer Satisfaction | Survey rating | ≥ [X] out of 5.0 | [ROLE] | Quarterly |
| Product Quality | Defect rate | < [X]% | [ROLE] | Monthly |
| On-Time Delivery | % on-time | ≥ [X]% | [ROLE] | Monthly |
| CAPA Effectiveness | % closed on time | ≥ [X]% | [ROLE] | Monthly |
| Training Completion | % complete on schedule | 100% | [ROLE] | Quarterly |
| Internal Audit Findings | Findings addressed | ≥ [X]% within 30 days | [ROLE] | After each audit |
| [OTHER OBJECTIVES] | | | | |
Quality objectives are monitored, reported in management review, and revised as necessary to drive continual improvement.
### 3.3 Communication of Policy and Objectives
The Quality Policy and Quality Objectives are communicated to all personnel through:
- Employee orientation and training
- Posting in common areas of the facility
- Inclusion in employee handbook
- Management review meetings
- Department meetings
- This Quality Manual (available to all personnel)
- [OTHER COMMUNICATION METHODS]
All employees are made aware of the relevance and importance of their activities and how they contribute to achieving quality objectives.
---
## 4. QUALITY MANAGEMENT SYSTEM
### 4.1 General Requirements
#### 4.1.1 QMS Establishment
[COMPANY NAME] has established, documented, implemented, and maintains a Quality Management System in accordance with ISO 13485:2016 and applicable regulatory requirements. The QMS covers all processes necessary to ensure medical device safety, performance, and regulatory compliance.
The QMS processes have been identified and are documented in this Quality Manual and referenced procedures. These processes include:
**Management Processes:**
- Management commitment and review
- Quality planning
- Internal communication
- Resource management
**Product Realization Processes:**
- [Design and development - if applicable]
- Purchasing
- Production and service provision
- Customer-related processes
**Support Processes:**
- Document and record control
- Human resources and training
- Infrastructure and maintenance
- Software validation
**Monitoring and Measurement Processes:**
- Customer feedback and complaints
- Internal audits
- Process and product monitoring
- Nonconformance control
- Corrective and preventive action
- Data analysis
#### 4.1.2 Process Interactions
The QMS processes are interconnected and operate as a system. Process interactions are illustrated in the Process Map (Appendix C). Key interactions include:
- Management review provides direction and resources for all processes
- Product realization processes transform customer requirements into conforming products
- Support processes enable effective product realization
- Monitoring processes provide feedback for improvement
- Risk management is integrated throughout all processes
- All processes contribute to meeting quality objectives
#### 4.1.3 Outsourced Processes
[IF APPLICABLE - otherwise state "Not applicable"]
The following QMS processes are outsourced to external parties:
| Process | Service Provider | Control Method | Responsible Party |
|---------|-----------------|----------------|-------------------|
| [e.g., Sterilization] | [PROVIDER NAME] | Supplier qualification, contract, ongoing monitoring | [ROLE] |
| [e.g., Calibration] | [PROVIDER NAME] | Qualified service provider, certificates reviewed | [ROLE] |
| | | | |
Outsourcing does not relieve [COMPANY NAME] of responsibility for conformity to customer and regulatory requirements. Control of outsourced processes is documented in [REFERENCE PROCEDURE].
#### 4.1.4 Risk Management
[COMPANY NAME] has established documented requirements for risk management throughout product realization in accordance with ISO 14971. Risk management is integrated into:
- Design and development (when applicable)
- Production and process control
- Purchasing and supplier management
- Post-market surveillance and feedback
- Corrective and preventive action
Risk management files are maintained as part of the Medical Device File for each device type. Risk management activities, methods, and records are defined in SOP-[NUMBER] Risk Management.
#### 4.1.5 Software Validation
Computer software applications used in the QMS are validated prior to initial use and after changes that could affect their intended use. Software requiring validation includes:
- [QMS/ERP software]
- [Electronic document management systems]
- [Production control software]
- [Automated test equipment software]
- [Other software affecting product quality or QMS effectiveness]
Validation is based on risk assessment and includes:
- Documented validation approach
- Risk-appropriate validation activities
- Defined acceptance criteria
- User responsibilities
- Validation records maintained
Software validation procedures and records are documented in SOP-[NUMBER] Software Validation.
### 4.2 Documentation Requirements
#### 4.2.1 General
The QMS documentation includes:
**Tier 1:** Quality Policy and Quality Manual (this document)
**Tier 2:** Documented Procedures (SOPs)
- The [31+] documented procedures required by ISO 13485:2016
- Additional procedures established by the organization
- Referenced in Appendix A
**Tier 3:** Work Instructions (WIs)
- Detailed step-by-step instructions for specific tasks
- Department or process-specific documents
**Tier 4:** Records and Forms
- Evidence of conformity to requirements
- Evidence of effective QMS operation
- Maintained per retention requirements
**Additional Documentation:**
- Medical Device Files
- Risk management files
- Design and development files (when applicable)
- Validation and verification documents
- External documents (standards, regulations, customer specifications)
#### 4.2.2 Quality Manual
This Quality Manual is established and maintained to describe the scope of the QMS, document or reference QMS procedures, describe process interactions, and outline the documentation structure.
This manual is controlled per SOP-[NUMBER] Control of Documents and is reviewed annually for continuing suitability.
#### 4.2.3 Medical Device File
A Medical Device File (MDF) is established and maintained for each medical device type or device family. The MDF contains all documentation required by ISO 13485:2016 Clause 4.2.3, including:
- General description of device and intended use/purpose
- Label and instructions for use specifications
- Product specifications
- Manufacturing specifications
- Procedures for purchasing, manufacturing, and servicing
- Procedures for measuring and monitoring
- Installation requirements (when applicable)
- Risk management file(s)
- Verification and validation information
- Design and development file(s) (when applicable)
MDF structure, content, and control are defined in SOP-[NUMBER] Medical Device File.
**Current Medical Device Files:**
- [LIST MDFs MAINTAINED]
#### 4.2.4 Control of Documents
All QMS documents are controlled to ensure:
- Approval before issue
- Review and update as necessary
- Current revision status identified
- Relevant versions available at point of use
- Documents remain legible and identifiable
- External documents controlled
- Obsolete documents prevented from unintended use
- Obsolete documents identified if retained for reference
Document control responsibilities, requirements, and procedures are defined in SOP-[NUMBER] Control of Documents.
The Document Control Coordinator is responsible for document control system operation.
#### 4.2.5 Control of Records
QMS records provide evidence of conformity to requirements and effective QMS operation. Records are controlled to ensure:
- Legibility, identification, and retrievability
- Proper storage, security, and integrity
- Appropriate retention time (minimum: device lifetime)
- Proper disposition
- Changes remain identifiable
Record control responsibilities, requirements, and procedures are defined in SOP-[NUMBER] Control of Records.
Records are retained for at least [X years or device lifetime, whichever is longer], in accordance with applicable regulatory requirements.
---
## 5. MANAGEMENT RESPONSIBILITY
[CONTINUE WITH SECTIONS 5-8 FOLLOWING THE SAME PATTERN: State requirement, describe implementation, reference procedure, identify responsibility]
[Note: For brevity, I'm providing the format. The user can expand each section following this pattern]
---
## 9. APPENDICES
### APPENDIX A: LIST OF DOCUMENTED PROCEDURES
[CREATE TABLE OF ALL 31+ PROCEDURES]
### APPENDIX B: ORGANIZATION CHART
[INSERT ORGANIZATION CHART]
### APPENDIX C: PROCESS MAP
[INSERT PROCESS INTERACTION DIAGRAM]
### APPENDIX D: DEFINITIONS AND ABBREVIATIONS
[EXPAND FROM SECTION 1.4]
### APPENDIX E: APPLICABLE REGULATORY REQUIREMENTS
[DETAILED LIST OF ALL APPLICABLE REGULATIONS]
---
**END OF QUALITY MANUAL**
---
**Document Number:** QM-001
**Revision:** 00
**Page:** [X] of [X]