quality-documentation-manager

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

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.

符合ISO 13485标准的质量管理体系的文档控制系统设计与管理,包括编号规则、审批工作流、变更控制以及电子记录合规性。

Table of Contents

目录

Document Control Workflow

文档控制工作流

Implement document control from creation through obsolescence:
  1. Assign document number per numbering procedure
  2. Create document using controlled template
  3. Route for review to required reviewers
  4. Address review comments and document responses
  5. Obtain required approval signatures
  6. Assign effective date and distribute
  7. Update Document Master List
  8. Validation: Document accessible at point of use; obsolete versions removed
实现从创建到淘汰的全流程文档控制:
  1. 根据编号流程分配文档编号
  2. 使用受控模板创建文档
  3. 发送给指定审核人员进行审核
  4. 处理审核意见并记录回复
  5. 获取所需的审批签名
  6. 分配生效日期并发布
  7. 更新文档主清单
  8. 验证: 文档在使用点可访问;已淘汰版本已移除

Document Lifecycle Stages

文档生命周期阶段

StageDefinitionActions Required
DraftUnder creation or revisionAuthor editing, not for use
ReviewCirculated for reviewReviewers provide feedback
ApprovedAll signatures obtainedReady for training/distribution
EffectiveTraining complete, releasedAvailable for use
SupersededReplaced by newer revisionRemove from active use
ObsoleteNo longer applicableArchive per retention schedule
阶段定义所需操作
草稿正在创建或修订中作者编辑,不可使用
审核分发进行审核审核人员提供反馈
已批准已获取所有签名准备培训/分发
已生效培训完成,已发布可使用
已取代被新版本替代从活跃使用中移除
已淘汰不再适用根据保留计划归档

Document Types and Prefixes

文档类型与前缀

PrefixDocument TypeTypical Content
QMQuality ManualQMS overview, scope, policy
SOPStandard Operating ProcedureProcess-level procedures
WIWork InstructionTask-level step-by-step
TFTemplate/FormControlled forms
SPECSpecificationProduct/process specs
PLNPlanQuality/project plans
前缀文档类型典型内容
QM质量手册QMS概述、范围、政策
SOP标准操作流程流程级程序
WI作业指导书任务级分步说明
TF模板/表单受控表单
SPEC规范产品/流程规范
PLN计划质量/项目计划

Required Reviewers by Document Type

按文档类型划分的指定审核人员

Document TypeRequired ReviewersRequired Approvers
SOPProcess Owner, QAQA Manager, Process Owner
WIArea Supervisor, QAArea Manager
SPECEngineering, QAEngineering Manager, QA
TFProcess OwnerQA
Design DocumentsDesign Team, QADesign Control Authority

文档类型指定审核人员指定审批人员
SOP流程负责人、QAQA经理、流程负责人
WI区域主管、QA区域经理
SPEC工程部、QA工程经理、QA
TF流程负责人QA
设计文档设计团队、QA设计控制负责人

Document Numbering System

文档编号系统

Assign consistent document numbers for identification and retrieval.
分配一致的文档编号以用于识别和检索。

Numbering Format

编号格式

Standard format:
PREFIX-CATEGORY-SEQUENCE[-REVISION]
Example: SOP-02-001-A

SOP = Document type (Standard Operating Procedure)
02  = Category code (Document Control)
001 = Sequential number
A   = Revision indicator
标准格式:
PREFIX-CATEGORY-SEQUENCE[-REVISION]
示例:SOP-02-001-A

SOP = 文档类型(标准操作流程)
02  = 类别代码(文档控制)
001 = 序列号
A   = 修订标识

Category Codes

类别代码

CodeFunctional AreaDescription
01Quality ManagementQMS procedures, management review
02Document ControlThis area
03Human ResourcesTraining, competency
04Design & DevelopmentDesign control processes
05PurchasingSupplier management
06ProductionManufacturing procedures
07Quality ControlInspection, testing
08CAPACorrective/preventive actions
09Risk ManagementISO 14971 processes
10Regulatory AffairsSubmissions, compliance
代码职能领域描述
01质量管理QMS程序、管理评审
02文档控制本领域
03人力资源培训、能力评估
04设计与开发设计控制流程
05采购供应商管理
06生产制造流程
07质量控制检验、测试
08CAPA纠正/预防措施
09风险管理ISO 14971流程
10法规事务申报、合规性

Numbering Workflow

编号工作流

  1. Author requests document number from Document Control
  2. Document Control verifies category assignment
  3. Document Control assigns next available sequence number
  4. Number recorded in Document Master List
  5. Author creates document using assigned number
  6. Validation: Number format matches standard; no duplicates in Master List
  1. 作者向文档控制部门申请文档编号
  2. 文档控制部门验证类别分配
  3. 文档控制部门分配下一个可用的序列号
  4. 编号记录在文档主清单中
  5. 作者使用分配的编号创建文档
  6. 验证: 编号格式符合标准;主清单中无重复

Revision Designation

修订标识

Change TypeRevision IncrementExample
Major revisionIncrement numberRev 01 → Rev 02
Minor revisionIncrement sub-revisionRev 01 → Rev 01.1
AdministrativeNo change or letter suffixRev 01 → Rev 01a
See
references/document-control-procedures.md
for complete numbering guidance.

变更类型修订增量示例
重大修订递增数字修订01 → 修订02
次要修订递增子修订号修订01 → 修订01.1
行政修订无变更或字母后缀修订01 → 修订01a
完整编号指南请参阅
references/document-control-procedures.md

Approval and Review Process

审批与审核流程

Obtain required reviews and approvals before document release.
在文档发布前获取指定的审核和审批。

Review Workflow

审核工作流

  1. Author completes document draft
  2. Author submits for review via routing form or DMS
  3. Reviewers assigned based on document type
  4. Reviewers provide comments within review period (5-10 business days)
  5. Author addresses comments and documents responses
  6. Author resubmits revised document
  7. Approvers sign and date
  8. Validation: All required reviewers completed; all comments addressed with documented disposition
  1. 作者完成文档草稿
  2. 作者通过路由表单或DMS提交审核
  3. 根据文档类型分配审核人员
  4. 审核人员在审核周期(5-10个工作日)内提供意见
  5. 作者处理意见并记录回复
  6. 作者重新提交修订后的文档
  7. 审批人员签名并标注日期
  8. 验证: 所有指定审核人员已完成审核;所有意见均已处理并记录处置结果

Comment Disposition

意见处置

DispositionAction Required
AcceptIncorporate comment as written
Accept with modificationIncorporate with changes, document rationale
RejectDo not incorporate, document justification
DeferAddress in future revision, document reason
处置方式所需操作
接受按原文采纳意见
接受并修改采纳并修改,记录理由
拒绝不采纳,记录正当理由
推迟在未来修订中处理,记录原因

Approval Matrix

审批矩阵

Document Level 1 (Policy/QM): CEO or delegate + QA Manager
Document Level 2 (SOP): Department Manager + QA Manager
Document Level 3 (WI/TF): Area Supervisor + QA Representative
文档级别1(政策/质量手册):CEO或授权代表 + QA经理
文档级别2(SOP):部门经理 + QA经理
文档级别3(作业指导书/表单):区域主管 + QA代表

Signature Requirements

签名要求

ElementRequirement
NamePrinted name of signer
SignatureHandwritten or electronic signature
DateDate signature applied
RoleFunction/role of signer

要素要求
姓名签名人的打印姓名
签名手写或电子签名
日期签名的日期
角色签名人的职能/角色

Change Control Process

变更控制流程

Manage document changes systematically through review and approval.
通过审核和审批系统地管理文档变更。

Change Control Workflow

变更控制工作流

  1. Identify need for document change
  2. Complete Change Request Form with justification
  3. Document Control assigns change number and logs request
  4. Route to reviewers for impact assessment
  5. Obtain approvals based on change classification
  6. Author implements approved changes
  7. Update revision number and change history
  8. Validation: Changes match approved scope; change history complete
  1. 识别文档变更需求
  2. 填写变更请求表并说明理由
  3. 文档控制部门分配变更编号并记录请求
  4. 发送给审核人员进行影响评估
  5. 根据变更分类获取审批
  6. 作者实施已批准的变更
  7. 更新修订号和变更历史
  8. 验证: 变更符合已批准的范围;变更历史完整

Change Classification

变更分类

ClassDefinitionApproval LevelExamples
AdministrativeNo content impactDocument ControlTypos, formatting
MinorLimited content changeProcess Owner + QAClarifications
MajorSignificant content changeFull review cycleNew requirements
EmergencyUrgent safety/complianceExpedited + retrospectiveSafety issues
类别定义审批级别示例
行政类无内容影响文档控制部门打字错误、格式调整
次要类有限的内容变更流程负责人 + QA澄清说明
重大类重大内容变更完整审核周期新要求
紧急类紧急安全/合规需求快速审批 + 追溯审核安全问题

Impact Assessment Checklist

影响评估清单

Impact AreaAssessment Questions
TrainingDoes change require retraining?
EquipmentDoes change affect equipment or systems?
ValidationDoes change require revalidation?
RegulatoryDoes change affect regulatory filings?
Other DocumentsWhich related documents need updating?
RecordsWhat records are affected?
影响领域评估问题
培训变更是否需要重新培训?
设备变更是否影响设备或系统?
验证变更是否需要重新验证?
法规变更是否影响法规申报?
其他文档哪些相关文档需要更新?
记录哪些记录会受到影响?

Change History Documentation

变更历史文档

Each document must include change history:
| Revision | Date | Description | Author | Approver |
|----------|------|-------------|--------|----------|
| 01 | 2023-01-15 | Initial release | J. Smith | M. Jones |
| 02 | 2024-03-01 | Updated workflow | J. Smith | M. Jones |

每个文档必须包含变更历史:
| 修订版本 | 日期 | 描述 | 作者 | 审批人 |
|----------|------|-------------|--------|----------|
| 01 | 2023-01-15 | 首次发布 | J. Smith | M. Jones |
| 02 | 2024-03-01 | 更新工作流 | J. Smith | M. Jones |

21 CFR Part 11 Compliance

21 CFR Part 11合规性

Implement electronic record and signature controls for FDA compliance.
实施电子记录和签名控制以符合FDA要求。

Part 11 Scope

Part 11适用范围

Applies ToDoes Not Apply To
Records required by FDA regulationsPaper records
Records submitted to FDAInternal non-regulated documents
Electronic signatures on required recordsGeneral email communication
适用对象不适用对象
FDA法规要求的记录纸质记录
提交给FDA的记录内部非法规文档
要求记录上的电子签名普通电子邮件通信

Electronic Record Controls

电子记录控制

  1. Validate system for accuracy and reliability
  2. Implement secure audit trail for all changes
  3. Restrict system access to authorized individuals
  4. Generate accurate copies in human-readable format
  5. Protect records throughout retention period
  6. Validation: Audit trail captures who, what, when for all changes
  1. 验证系统的准确性和可靠性
  2. 为所有变更实施安全审计追踪
  3. 限制系统访问权限至授权人员
  4. 生成人类可读格式的准确副本
  5. 在保留期内保护记录
  6. 验证: 审计追踪捕获所有变更的执行人、内容和时间

Audit Trail Requirements

审计追踪要求

RequirementImplementation
SecureCannot be modified by users
Computer-generatedSystem creates automatically
Time-stampedDate and time of each action
Original valuesPrevious values retained
User identityWho made each change
要求实施方式
安全用户无法修改
计算机生成系统自动创建
带时间戳每个操作的日期和时间
保留原始值保留之前的值
用户身份记录每个变更的执行人

Electronic Signature Requirements

电子签名要求

RequirementImplementation
Unique to individualNot shared between persons
At least 2 componentsUser ID + password minimum
Signature manifestationName, date/time, meaning displayed
Linked to recordCannot be excised or copied
要求实施方式
个人唯一不得在人员间共享
至少2个组件至少用户ID + 密码
签名显示显示姓名、日期/时间、签名含义
与记录关联不得被删除或复制

Signature Manifestation

签名显示

Every electronic signature must display:
ElementExample
Printed nameJohn Smith
Date and time2024-03-15 14:32:05 EST
MeaningApproved for Release
每个电子签名必须显示:
要素示例
打印姓名John Smith
日期和时间2024-03-15 14:32:05 EST
含义批准发布

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.

访问控制:
  • 为每个人分配唯一用户ID
  • 强制要求密码复杂度
  • 多次尝试失败后锁定账户
  • 闲置后会话超时
审计追踪:
  • 记录所有记录创建操作
  • 记录所有修改操作及新旧值
  • 捕获用户身份
  • 所有条目带日期/时间戳
安全:
  • 基于角色的访问控制
  • 静态和传输数据加密
  • 定期备份并测试恢复
详细合规要求请参阅
references/21cfr11-compliance-guide.md

Reference Documentation

参考文档

Document Control Procedures

文档控制流程

references/document-control-procedures.md
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
references/document-control-procedures.md
包含:
  • 文档编号系统和格式
  • 文档生命周期阶段与转换
  • 审核和审批工作流详情
  • 带分类标准的变更控制流程
  • 分发和访问控制方法
  • 记录保留期和处置流程
  • 文档主清单要求

21 CFR Part 11 Compliance Guide

21 CFR Part 11合规指南

references/21cfr11-compliance-guide.md
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

references/21cfr11-compliance-guide.md
包含:
  • Part 11的范围和适用性
  • 电子记录要求(§11.10)
  • 电子签名要求(§11.50, 11.100, 11.200)
  • 系统控制规范
  • 验证方法和文档
  • 合规清单和差距评估模板
  • FDA常见缺陷及预防措施

Tools

工具

Document Validator

文档验证器

bash
undefined
bash
undefined

Validate document metadata

Validate document metadata

python scripts/document_validator.py --doc document.json
python scripts/document_validator.py --doc document.json

Interactive validation mode

Interactive validation mode

python scripts/document_validator.py --interactive
python scripts/document_validator.py --interactive

JSON output for integration

JSON output for integration

python scripts/document_validator.py --doc document.json --output json
python scripts/document_validator.py --doc document.json --output json

Generate sample document JSON

Generate sample document JSON

python scripts/document_validator.py --sample > sample_doc.json

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)
python scripts/document_validator.py --sample > sample_doc.json

验证内容:
- 文档编号规则合规性
- 标题和状态要求
- 日期验证(生效日期、审核到期日)
- 按文档类型划分的审批要求
- 变更历史完整性
- 21 CFR Part 11控制(审计追踪、签名)

Sample Document Input

示例文档输入

json
{
  "number": "SOP-02-001",
  "title": "Document Control Procedure",
  "doc_type": "SOP",
  "revision": "03",
  "status": "Effective",
  "effective_date": "2024-01-15",
  "review_date": "2025-01-15",
  "author": "J. Smith",
  "approver": "M. Jones",
  "change_history": [
    {"revision": "01", "date": "2022-01-01", "description": "Initial release"},
    {"revision": "02", "date": "2023-01-15", "description": "Updated workflow"},
    {"revision": "03", "date": "2024-01-15", "description": "Added e-signature requirements"}
  ],
  "has_audit_trail": true,
  "has_electronic_signature": true,
  "signature_components": 2
}

json
{
  "number": "SOP-02-001",
  "title": "Document Control Procedure",
  "doc_type": "SOP",
  "revision": "03",
  "status": "Effective",
  "effective_date": "2024-01-15",
  "review_date": "2025-01-15",
  "author": "J. Smith",
  "approver": "M. Jones",
  "change_history": [
    {"revision": "01", "date": "2022-01-01", "description": "Initial release"},
    {"revision": "02", "date": "2023-01-15", "description": "Updated workflow"},
    {"revision": "03", "date": "2024-01-15", "description": "Added e-signature requirements"}
  ],
  "has_audit_trail": true,
  "has_electronic_signature": true,
  "signature_components": 2
}

Document Control Metrics

文档控制指标

Track document control system performance.
跟踪文档控制系统的性能。

Key Performance Indicators

关键绩效指标

MetricTargetCalculation
Document cycle time<30 daysAverage days from draft to effective
Review completion rate>95%Reviews completed on time / Total reviews
Change request backlog<10Open change requests at month end
Overdue review rate<5%Documents past review date / Total effective
Audit finding rate<2 per auditDocument control findings per internal audit
指标目标计算方式
文档周期时间<30天从草稿到生效的平均天数
审核完成率>95%按时完成的审核数 / 总审核数
变更请求积压<10月末未处理的变更请求数
逾期审核率<5%超过审核日期的文档数 / 总生效文档数
审计发现率<2个/审计每次内部审计中的文档控制发现数

Periodic Review Schedule

定期审核计划

Document TypeReview Frequency
PolicyEvery 3 years
SOPEvery 2 years
WIEvery 2 years
SpecificationsAs needed or with product changes
Forms/TemplatesEvery 3 years

文档类型审核频率
政策每3年一次
SOP每2年一次
作业指导书每2年一次
规范按需或随产品变更
表单/模板每3年一次

Regulatory Requirements

法规要求

ISO 13485:2016 Clause 4.2

ISO 13485:2016 第4.2条

Sub-clauseRequirement
4.2.1Quality management system documentation
4.2.2Quality manual
4.2.3Medical device file (technical documentation)
4.2.4Control of documents
4.2.5Control of records
子条款要求
4.2.1质量管理体系文档
4.2.2质量手册
4.2.3医疗器械文件(技术文档)
4.2.4文档控制
4.2.5记录控制

FDA 21 CFR 820

FDA 21 CFR 820

SectionRequirement
820.40Document controls
820.180General record requirements
820.181Device master record
820.184Device history record
820.186Quality system record
章节要求
820.40文档控制
820.180通用记录要求
820.181设备主记录
820.184设备历史记录
820.186质量体系记录

Common Audit Findings

常见审计发现

FindingPrevention
Obsolete documents in useImplement distribution control
Missing approval signaturesEnforce workflow before release
Incomplete change historyRequire history update with each revision
No periodic review scheduleEstablish and enforce review calendar
Inadequate audit trailValidate DMS for Part 11 compliance
发现预防措施
使用已淘汰的文档实施分发控制
缺少审批签名发布前强制执行工作流
变更历史不完整要求每次修订时更新历史
无定期审核计划建立并执行审核日历
审计追踪不足验证DMS符合Part 11合规性