Quality Documentation Manager
Document control system design and management for ISO 13485-compliant quality management systems, including numbering conventions, approval workflows, change control, and electronic record compliance.
Table of Contents
Document Control Workflow
Implement document control from creation through obsolescence:
- 1. Assign document number per numbering procedure
- Create document using controlled template
- Route for review to required reviewers
- Address review comments and document responses
- Obtain required approval signatures
- Assign effective date and distribute
- Update Document Master List
- Validation: Document accessible at point of use; obsolete versions removed
Document Lifecycle Stages
| Stage | Definition | Actions Required |
|---|
| Draft | Under creation or revision | Author editing, not for use |
| Review |
Circulated for review | Reviewers provide feedback |
| Approved | All signatures obtained | Ready for training/distribution |
| Effective | Training complete, released | Available for use |
| Superseded | Replaced by newer revision | Remove from active use |
| Obsolete | No longer applicable | Archive per retention schedule |
Document Types and Prefixes
| Prefix | Document Type | Typical Content |
|---|
| QM | Quality Manual | QMS overview, scope, policy |
| SOP |
Standard Operating Procedure | Process-level procedures |
| WI | Work Instruction | Task-level step-by-step |
| TF | Template/Form | Controlled forms |
| SPEC | Specification | Product/process specs |
| PLN | Plan | Quality/project plans |
Required Reviewers by Document Type
| Document Type | Required Reviewers | Required Approvers |
|---|
| SOP | Process Owner, QA | QA Manager, Process Owner |
| WI |
Area Supervisor, QA | Area Manager |
| SPEC | Engineering, QA | Engineering Manager, QA |
| TF | Process Owner | QA |
| Design Documents | Design Team, QA | Design Control Authority |
Document Numbering System
Assign consistent document numbers for identification and retrieval.
Numbering Format
Standard format: INLINECODE0
CODEBLOCK0
Category Codes
| Code | Functional Area | Description |
|---|
| 01 | Quality Management | QMS procedures, management review |
| 02 |
Document Control | This area |
| 03 | Human Resources | Training, competency |
| 04 | Design & Development | Design control processes |
| 05 | Purchasing | Supplier management |
| 06 | Production | Manufacturing procedures |
| 07 | Quality Control | Inspection, testing |
| 08 | CAPA | Corrective/preventive actions |
| 09 | Risk Management | ISO 14971 processes |
| 10 | Regulatory Affairs | Submissions, compliance |
Numbering Workflow
- 1. Author requests document number from Document Control
- Document Control verifies category assignment
- Document Control assigns next available sequence number
- Number recorded in Document Master List
- Author creates document using assigned number
- Validation: Number format matches standard; no duplicates in Master List
Revision Designation
| Change Type | Revision Increment | Example |
|---|
| Major revision | Increment number | Rev 01 → Rev 02 |
| Minor revision |
Increment sub-revision | Rev 01 → Rev 01.1 |
| Administrative | No change or letter suffix | Rev 01 → Rev 01a |
See references/document-control-procedures.md for complete numbering guidance.
Approval and Review Process
Obtain required reviews and approvals before document release.
Review Workflow
- 1. Author completes document draft
- Author submits for review via routing form or DMS
- Reviewers assigned based on document type
- Reviewers provide comments within review period (5-10 business days)
- Author addresses comments and documents responses
- Author resubmits revised document
- Approvers sign and date
- Validation: All required reviewers completed; all comments addressed with documented disposition
Comment Disposition
| Disposition | Action Required |
|---|
| Accept | Incorporate comment as written |
| Accept with modification |
Incorporate with changes, document rationale |
| Reject | Do not incorporate, document justification |
| Defer | Address in future revision, document reason |
Approval Matrix
CODEBLOCK1
Signature Requirements
| Element | Requirement |
|---|
| Name | Printed name of signer |
| Signature |
Handwritten or electronic signature |
| Date | Date signature applied |
| Role | Function/role of signer |
Change Control Process
Manage document changes systematically through review and approval.
Change Control Workflow
- 1. Identify need for document change
- Complete Change Request Form with justification
- Document Control assigns change number and logs request
- Route to reviewers for impact assessment
- Obtain approvals based on change classification
- Author implements approved changes
- Update revision number and change history
- Validation: Changes match approved scope; change history complete
Change Classification
| Class | Definition | Approval Level | Examples |
|---|
| Administrative | No content impact | Document Control | Typos, formatting |
| Minor |
Limited content change | Process Owner + QA | Clarifications |
| Major | Significant content change | Full review cycle | New requirements |
| Emergency | Urgent safety/compliance | Expedited + retrospective | Safety issues |
Impact Assessment Checklist
| Impact Area | Assessment Questions |
|---|
| Training | Does change require retraining? |
| Equipment |
Does change affect equipment or systems? |
| Validation | Does change require revalidation? |
| Regulatory | Does change affect regulatory filings? |
| Other Documents | Which related documents need updating? |
| Records | What records are affected? |
Change History Documentation
Each document must include change history:
CODEBLOCK2
21 CFR Part 11 Compliance
Implement electronic record and signature controls for FDA compliance.
Part 11 Scope
| Applies To | Does Not Apply To |
|---|
| Records required by FDA regulations | Paper records |
| Records submitted to FDA |
Internal non-regulated documents |
| Electronic signatures on required records | General email communication |
Electronic Record Controls
- 1. Validate system for accuracy and reliability
- Implement secure audit trail for all changes
- Restrict system access to authorized individuals
- Generate accurate copies in human-readable format
- Protect records throughout retention period
- Validation: Audit trail captures who, what, when for all changes
Audit Trail Requirements
| Requirement | Implementation |
|---|
| Secure | Cannot be modified by users |
| Computer-generated |
System creates automatically |
| Time-stamped | Date and time of each action |
| Original values | Previous values retained |
| User identity | Who made each change |
Electronic Signature Requirements
| Requirement | Implementation |
|---|
| Unique to individual | Not shared between persons |
| At least 2 components |
User ID + password minimum |
| Signature manifestation | Name, date/time, meaning displayed |
| Linked to record | Cannot be excised or copied |
Signature Manifestation
Every electronic signature must display:
| Element | Example |
|---|
| Printed name | John Smith |
| Date and time |
2024-03-15 14:32:05 EST |
| Meaning | Approved for Release |
System Controls Checklist
Access Controls:
- - [ ] Unique user ID for each person
- [ ] Password complexity enforced
- [ ] Account lockout after failed attempts
- [ ] Session timeout after inactivity
Audit Trail:
- - [ ] All record creation logged
- [ ] All modifications logged with old/new values
- [ ] User identity captured
- [ ] Date/time stamp on all entries
Security:
- - [ ] Role-based access control
- [ ] Encryption for data at rest and in transit
- [ ] Regular backup and tested recovery
See references/21cfr11-compliance-guide.md for detailed compliance requirements.
Reference Documentation
Document Control Procedures
INLINECODE3 contains:
- - Document numbering system and format
- Document lifecycle stages and transitions
- Review and approval workflow details
- Change control process with classification criteria
- Distribution and access control methods
- Record retention periods and disposal procedures
- Document Master List requirements
21 CFR Part 11 Compliance Guide
INLINECODE4 contains:
- - Part 11 scope and applicability
- Electronic record requirements (§11.10)
- Electronic signature requirements (§11.50, 11.100, 11.200)
- System control specifications
- Validation approach and documentation
- Compliance checklist and gap assessment template
- Common FDA deficiencies and prevention
Tools
Document Validator
CODEBLOCK3
Validates:
- - Document numbering convention compliance
- Title and status requirements
- Date validation (effective, review due)
- Approval requirements by document type
- Change history completeness
- 21 CFR Part 11 controls (audit trail, signatures)
Sample Document Input
CODEBLOCK4
Document Control Metrics
Track document control system performance.
Key Performance Indicators
| Metric | Target | Calculation |
|---|
| Document cycle time | <30 days | Average days from draft to effective |
| Review completion rate |
>95% | Reviews completed on time / Total reviews |
| Change request backlog | <10 | Open change requests at month end |
| Overdue review rate | <5% | Documents past review date / Total effective |
| Audit finding rate | <2 per audit | Document control findings per internal audit |
Periodic Review Schedule
| Document Type | Review Frequency |
|---|
| Policy | Every 3 years |
| SOP |
Every 2 years |
| WI | Every 2 years |
| Specifications | As needed or with product changes |
| Forms/Templates | Every 3 years |
Regulatory Requirements
ISO 13485:2016 Clause 4.2
| Sub-clause | Requirement |
|---|
| 4.2.1 | Quality management system documentation |
| 4.2.2 |
Quality manual |
| 4.2.3 | Medical device file (technical documentation) |
| 4.2.4 | Control of documents |
| 4.2.5 | Control of records |
FDA 21 CFR 820
| Section | Requirement |
|---|
| 820.40 | Document controls |
| 820.180 |
General record requirements |
| 820.181 | Device master record |
| 820.184 | Device history record |
| 820.186 | Quality system record |
Common Audit Findings
| Finding | Prevention |
|---|
| Obsolete documents in use | Implement distribution control |
| Missing approval signatures |
Enforce workflow before release |
| Incomplete change history | Require history update with each revision |
| No periodic review schedule | Establish and enforce review calendar |
| Inadequate audit trail | Validate DMS for Part 11 compliance |
质量文档管理器
针对符合ISO 13485质量管理体系的文档控制系统设计与管理工作,包括编号规范、审批流程、变更控制和电子记录合规性。
目录
文档控制流程
实施从创建到废止的文档控制:
- 1. 按编号程序分配文档编号
- 使用受控模板创建文档
- 流转至所需评审人员进行评审
- 处理评审意见并记录回复
- 获取所需审批签名
- 分配生效日期并分发
- 更新文档主列表
- 验证: 文档在使用点可访问;旧版本已移除
文档生命周期阶段
| 阶段 | 定义 | 所需操作 |
|---|
| 草稿 | 正在创建或修订中 | 作者编辑,不可使用 |
| 评审中 |
已流转供评审 | 评审人员提供反馈 |
| 已批准 | 已获取所有签名 | 准备培训/分发 |
| 已生效 | 培训完成,已发布 | 可供使用 |
| 已取代 | 被新版本替换 | 从活跃使用中移除 |
| 已废止 | 不再适用 | 按保留期限归档 |
文档类型与前缀
| 前缀 | 文档类型 | 典型内容 |
|---|
| QM | 质量手册 | QMS概述、范围、政策 |
| SOP |
标准操作规程 | 流程级程序 |
| WI | 作业指导书 | 任务级逐步说明 |
| TF | 模板/表格 | 受控表格 |
| SPEC | 规范 | 产品/工艺规范 |
| PLN | 计划 | 质量/项目计划 |
按文档类型划分的所需评审人员
| 文档类型 | 所需评审人员 | 所需审批人员 |
|---|
| SOP | 流程负责人、QA | QA经理、流程负责人 |
| WI |
区域主管、QA | 区域经理 |
| SPEC | 工程部、QA | 工程经理、QA |
| TF | 流程负责人 | QA |
| 设计文档 | 设计团队、QA | 设计控制主管 |
文档编号系统
分配一致的文档编号以便识别和检索。
编号格式
标准格式:前缀-类别-序列号[-版本号]
示例:SOP-02-001-A
SOP = 文档类型(标准操作规程)
02 = 类别代码(文档控制)
001 = 序列号
A = 版本标识
类别代码
| 代码 | 职能领域 | 描述 |
|---|
| 01 | 质量管理 | QMS程序、管理评审 |
| 02 |
文档控制 | 本领域 |
| 03 | 人力资源 | 培训、能力 |
| 04 | 设计与开发 | 设计控制流程 |
| 05 | 采购 | 供应商管理 |
| 06 | 生产 | 制造程序 |
| 07 | 质量控制 | 检验、测试 |
| 08 | CAPA | 纠正/预防措施 |
| 09 | 风险管理 | ISO 14971流程 |
| 10 | 法规事务 | 提交、合规 |
编号工作流程
- 1. 作者向文档控制部门申请文档编号
- 文档控制部门验证类别分配
- 文档控制部门分配下一个可用序列号
- 编号记录在文档主列表中
- 作者使用分配的编号创建文档
- 验证: 编号格式符合标准;主列表中无重复
版本标识
| 变更类型 | 版本递增方式 | 示例 |
|---|
| 重大修订 | 递增数字 | Rev 01 → Rev 02 |
| 次要修订 |
递增子版本 | Rev 01 → Rev 01.1 |
| 行政性变更 | 无变更或字母后缀 | Rev 01 → Rev 01a |
完整编号指南请参见 references/document-control-procedures.md。
审批与评审流程
在文档发布前获取所需的评审和审批。
评审工作流程
- 1. 作者完成文档草稿
- 作者通过流转表或DMS提交评审
- 根据文档类型分配评审人员
- 评审人员在评审期内(5-10个工作日)提供意见
- 作者处理意见并记录回复
- 作者重新提交修订后的文档
- 审批人员签名并注明日期
- 验证: 所有所需评审人员已完成;所有意见均已处理并记录处置结果
意见处置
采纳并修改,记录理由 |
| 拒绝 | 不采纳,记录理由 |
| 推迟 | 在后续版本中处理,记录原因 |
审批矩阵
文档级别1(政策/质量手册):CEO或代表 + QA经理
文档级别2(SOP):部门经理 + QA经理
文档级别3(WI/TF):区域主管 + QA代表
签名要求
手写签名或电子签名 |
| 日期 | 签名的日期 |
| 角色 | 签名人的职能/角色 |
变更控制流程
通过评审和审批系统地管理文档变更。
变更控制工作流程
- 1. 识别文档变更需求
- 填写变更申请表并附上理由
- 文档控制部门分配变更编号并记录请求
- 流转至评审人员进行影响评估
- 根据变更分类获取审批
- 作者实施已批准的变更
- 更新版本号和变更历史
- 验证: 变更与批准范围一致;变更历史完整
变更分类
| 类别 | 定义 | 审批级别 | 示例 |
|---|
| 行政性 | 无内容影响 | 文档控制部门 | 拼写错误、格式调整 |
| 次要 |
有限内容变更 | 流程负责人 + QA | 澄清说明 |
| 重大 | 重大内容变更 | 完整评审周期 | 新要求 |
| 紧急 | 紧急安全/合规 | 加急 + 追溯 | 安全问题 |
影响评估检查表
变更是否影响设备或系统? |
| 验证 | 变更是否需要重新验证? |
| 法规 | 变更是否影响法规文件? |
| 其他文档 | 哪些相关文档需要更新? |
| 记录 | 哪些记录受到影响? |
变更历史记录
每个文档必须包含变更历史:
| 版本 | 日期 | 描述 | 作者 | 审批人 |
|---|
| 01 | 2023-01-15 | 初始发布 | J. Smith | M. Jones |
| 02 |
2024-03-01 | 更新工作流程 | J. Smith | M. Jones |
21 CFR Part 11合规性
实施电子记录和签名控制以满足FDA合规要求。
Part 11适用范围
| 适用 | 不适用 |
|---|
| FDA法规要求的记录 | 纸质记录 |
| 提交给FDA的记录 |
内部非受控文档 |
| 所需记录上的电子签名 | 一般电子邮件通信 |
电子记录控制
- 1. 验证系统的准确性和可靠性
- 对所有变更实施安全审计追踪
- 限制系统访问权限仅限授权人员
- 生成可读格式的准确副本
- 在整个保留期内保护记录
- 验证: 审计追踪捕获所有变更的谁、什么、何时
审计追踪要求
系统自动创建 |
| 带时间戳 | 每次操作的日期和时间 |
| 原始值 | 保留先前值 |
| 用户身份 | 谁进行了每次变更 |
电子签名要求
用户ID + 密码(最低要求) |
| 签名显示 | 显示姓名、日期/时间、含义 |
| 与记录关联 | 无法被删除或复制 |
签名显示
每个电子签名必须显示:
2024-03-15 14: