| The Editor and His Contributors |
|
vii | |
| Foreword |
|
xv | |
|
|
|
| Editor's Introduction |
|
xix | |
|
|
|
| Chapter 1 Considerations for Computerized System Validation in the 21st Century Life Sciences Sector |
|
1 | (68) |
|
Tony de Claire, Peter Coady, and Nicola Stevens |
|
|
|
|
|
3 | (3) |
|
|
|
6 | (5) |
|
Computerized Systems Validation |
|
|
11 | (16) |
|
|
|
13 | (1) |
|
System and Application Evaluation |
|
|
14 | (1) |
|
|
|
15 | (1) |
|
|
|
15 | (3) |
|
|
|
18 | (6) |
|
|
|
18 | (2) |
|
Installation Qualification |
|
|
20 | (1) |
|
Operational Qualification |
|
|
21 | (1) |
|
Performance Qualification |
|
|
21 | (3) |
|
|
|
24 | (1) |
|
|
|
25 | (2) |
|
Computerized Systems Development |
|
|
27 | (12) |
|
User Requirements Specification (URS) |
|
|
27 | (1) |
|
|
|
28 | (1) |
|
Supplier Quality Management System |
|
|
29 | (2) |
|
Requirements Traceability |
|
|
31 | (1) |
|
System Development Life Cycle |
|
|
32 | (1) |
|
|
|
33 | (1) |
|
Development Methodologies |
|
|
34 | (1) |
|
System Development Testing |
|
|
35 | (2) |
|
|
|
37 | (1) |
|
|
|
38 | (1) |
|
Computerized Systems Operation |
|
|
39 | (5) |
|
|
|
39 | (1) |
|
|
|
40 | (1) |
|
Error and Problem Reporting |
|
|
40 | (1) |
|
|
|
41 | (1) |
|
Disaster Recovery and Business Contingency Planning |
|
|
42 | (1) |
|
System Maintenance and Support |
|
|
42 | (1) |
|
System Decommissioning and Retirement |
|
|
43 | (1) |
|
|
|
43 | (1) |
|
Electronic Records and Electronic Signatures |
|
|
44 | (14) |
|
FDA Guidance for Industry, Part 11, ERES - Scope and Application |
|
|
44 | (5) |
|
Predicate Rules and Part 11 |
|
|
45 | (1) |
|
Narrow Interpretation of Scope |
|
|
45 | (1) |
|
What the FDA Still Intends to Enforce When Part 11 Applies |
|
|
45 | (1) |
|
The Life Sciences Industry's Responsibilities |
|
|
46 | (1) |
|
|
|
47 | (1) |
|
Hybrid Systems (Paper and Electronic Records) |
|
|
47 | (1) |
|
|
|
47 | (1) |
|
|
|
47 | (1) |
|
|
|
48 | (1) |
|
|
|
48 | (1) |
|
|
|
48 | (1) |
|
Electronic Records Compliance |
|
|
49 | (5) |
|
|
|
49 | (1) |
|
|
|
50 | (1) |
|
|
|
50 | (1) |
|
|
|
51 | (1) |
|
|
|
51 | (1) |
|
|
|
52 | (1) |
|
Batch Release and Qualified Persons |
|
|
52 | (1) |
|
|
|
53 | (1) |
|
|
|
54 | (1) |
|
Electronic Signatures Compliance |
|
|
54 | (4) |
|
Association with Electronic Records |
|
|
54 | (1) |
|
|
|
55 | (1) |
|
|
|
55 | (1) |
|
|
|
56 | (1) |
|
|
|
57 | (1) |
|
Security - Continuous and Interrupted Access |
|
|
57 | (1) |
|
|
|
58 | (3) |
|
Roles and Responsibilities |
|
|
59 | (2) |
|
|
|
61 | (1) |
|
|
|
62 | (1) |
|
|
|
63 | (6) |
| Chapter 2 An Inspector's Viewpoint |
|
69 | (16) |
|
|
|
|
|
|
69 | (2) |
|
|
|
71 | (6) |
|
|
|
77 | (2) |
|
|
|
79 | (2) |
|
|
|
81 | (1) |
|
|
|
82 | (3) |
| Chapter 3 State-of-the-Art Risk Assessment and Management |
|
85 | (28) |
|
|
|
|
|
|
86 | (1) |
|
Risk Assessment Techniques |
|
|
87 | (12) |
|
Failure Mode Effect Analysis (FMEA) |
|
|
87 | (3) |
|
|
|
87 | (1) |
|
|
|
87 | (2) |
|
|
|
89 | (1) |
|
|
|
89 | (1) |
|
Failure Mode Effect Cause Analysis (FMECA) |
|
|
90 | (1) |
|
|
|
90 | (1) |
|
|
|
90 | (1) |
|
Hazard Analysis Critical Control Points (HACCP) |
|
|
90 | (5) |
|
|
|
90 | (1) |
|
|
|
91 | (4) |
|
|
|
95 | (1) |
|
|
|
95 | (1) |
|
Fault Tree Analysis (FTA) |
|
|
95 | (3) |
|
|
|
95 | (3) |
|
|
|
98 | (1) |
|
|
|
98 | (1) |
|
|
|
98 | (1) |
|
Application to the Validation of Computerized Systems |
|
|
99 | (2) |
|
|
|
101 | (4) |
|
High Level GxP Determination |
|
|
101 | (4) |
|
|
|
101 | (1) |
|
Subsystem Impact Assessment |
|
|
102 | (1) |
|
Functional Risk Assessment |
|
|
102 | (3) |
|
|
|
105 | (4) |
|
Step 1 Does the System Impact Part 11? |
|
|
105 | (1) |
|
|
|
106 | (2) |
|
Step 3 Part 11 Assessment |
|
|
108 | (1) |
|
Process Analytical Technology (PAT) |
|
|
109 | (1) |
|
|
|
110 | (1) |
|
|
|
110 | (1) |
|
|
|
110 | (3) |
| Chapter 4 Validation Planning and Reporting |
|
113 | (54) |
|
|
|
|
|
|
114 | (1) |
|
|
|
115 | (4) |
|
Overview of Planning in the Validation Life Cycle |
|
|
115 | (2) |
|
Purpose of the Validation Plan |
|
|
117 | (1) |
|
Relationships with Other Life Cycle Phases and Documents |
|
|
118 | (1) |
|
|
|
119 | (15) |
|
Formation of Project Team |
|
|
119 | (2) |
|
Analyze the GMP Implications |
|
|
121 | (3) |
|
Develop Validation Approach and Strategy |
|
|
124 | (6) |
|
Write the Validation Plan |
|
|
130 | (2) |
|
Review the Validation Plan |
|
|
132 | (1) |
|
Approve the Validation Plan |
|
|
133 | (1) |
|
Document Management and Control |
|
|
134 | (1) |
|
Format and Content of the Validation Plan |
|
|
134 | (9) |
|
Introduction and Project Overview |
|
|
135 | (1) |
|
|
|
136 | (2) |
|
|
|
138 | (1) |
|
|
|
139 | (1) |
|
Validation Documentation Procedures |
|
|
140 | (1) |
|
|
|
141 | (1) |
|
|
|
141 | (1) |
|
Validation Activity Schedule and Timeline |
|
|
142 | (1) |
|
Maintenance of Validation Status |
|
|
142 | (1) |
|
|
|
143 | (1) |
|
Checklist for Completion of a Validation Plan |
|
|
143 | (3) |
|
|
|
146 | (4) |
|
Overview of Validation Life Cycle |
|
|
146 | (1) |
|
Purpose of the Validation Report |
|
|
146 | (3) |
|
Relationships with Other Life Cycle Phases and Documents |
|
|
149 | (1) |
|
|
|
150 | (5) |
|
Review Phase Requirements |
|
|
150 | (2) |
|
Collate and Analyze the Results Obtained |
|
|
152 | (1) |
|
Collate and Analyze the Issues Raised |
|
|
152 | (1) |
|
Write the Validation Report |
|
|
153 | (1) |
|
Review the Validation Report |
|
|
153 | (1) |
|
Approve the Validation Report |
|
|
154 | (1) |
|
Document Management and Control |
|
|
155 | (1) |
|
Format and Content of a Validation Report |
|
|
155 | (9) |
|
|
|
156 | (1) |
|
|
|
157 | (1) |
|
|
|
158 | (3) |
|
|
|
158 | (2) |
|
|
|
160 | (1) |
|
|
|
160 | (1) |
|
Details of Phase Execution |
|
|
160 | (1) |
|
Comprehensive Results Breakdown |
|
|
161 | (1) |
|
Problem Reporting and Resolution |
|
|
161 | (2) |
|
|
|
163 | (1) |
|
|
|
164 | (1) |
|
|
|
164 | (1) |
|
Checklist for Completion of a Validation Report |
|
|
164 | (2) |
|
|
|
166 | (1) |
|
|
|
167 | (1) |
| Chapter 5 Supplier Audits: Question and Answers |
|
167 | (28) |
|
|
|
|
Introduction: Twenty Frequently Asked Questions |
|
|
168 | (1) |
|
Q1 What Is Computer Validation? |
|
|
168 | (1) |
|
Q2 How and by Whom Are Computer Systems Validation Activities Regulated? |
|
|
169 | (1) |
|
Q3 Who Is Responsible for Validating Computer Systems? |
|
|
169 | (1) |
|
Q4 Why Do Customers Conduct Audits? |
|
|
170 | (1) |
|
Q5 Is There a Standard Audit Process? |
|
|
170 | (1) |
|
Q6 When Is an Audit Required? |
|
|
171 | (1) |
|
Q7 What Is the Scope of an Audit? |
|
|
171 | (4) |
|
Q8 What about Electronic Records and Electronic Signatures? |
|
|
175 | (1) |
|
Q9 Who Conducts the Audit? |
|
|
176 | (1) |
|
Q10 How Will the Audit Be Conducted? |
|
|
176 | (1) |
|
Q11 When and How Will Suppliers Be Contacted in Regard to an Audit? |
|
|
177 | (1) |
|
Q12 What Happens in a Quality Review? |
|
|
178 | (1) |
|
Q13 What Happens in a Postal Audit? |
|
|
178 | (1) |
|
Q14 What Happens in a Full Supplier Audit? |
|
|
179 | (1) |
|
Q15 What Happens after an Audit? |
|
|
180 | (1) |
|
Q16 Are Audit Reports Confidential? |
|
|
181 | (1) |
|
Q17 Can a Regulator Such as FDA or MHRA Inspect a Supplier? |
|
|
181 | (1) |
|
Q18 Can Suppliers Be Approved by Regulators? |
|
|
182 | (1) |
|
Q19 What Is an Escrow Account? |
|
|
182 | (1) |
|
Q20 Where Can I Get More Guidance and Advice? |
|
|
183 | (1) |
|
|
|
183 | (1) |
|
|
|
183 | (1) |
|
|
|
184 | (1) |
|
|
|
184 | (1) |
|
Appendix A ISO 9000 Clauses |
|
|
184 | (1) |
|
Appendix B Supplier Audit Postal Questionnaire |
|
|
185 | (3) |
|
Appendix C Full Supplier Audit Checklist |
|
|
188 | (4) |
|
Appendix D Checklist for Customer Audits |
|
|
192 | (3) |
| Chapter 6 Developing Good Specifications |
|
195 | (14) |
|
|
|
|
|
|
196 | (2) |
|
|
|
198 | (1) |
|
User Requirement Specification Sections |
|
|
199 | (5) |
|
|
|
200 | (1) |
|
|
|
200 | (1) |
|
|
|
200 | (1) |
|
|
|
201 | (2) |
|
|
|
203 | (1) |
|
|
|
204 | (1) |
|
|
|
204 | (1) |
|
Electronic Record (ER) Controls |
|
|
204 | (1) |
|
Electronic Signature Requirements |
|
|
205 | (1) |
|
|
|
205 | (1) |
|
Operating Procedures and Training Requirements |
|
|
206 | (1) |
|
|
|
206 | (1) |
|
|
|
206 | (1) |
|
|
|
207 | (1) |
|
System Maintenance and Availability |
|
|
207 | (1) |
|
|
|
207 | (1) |
|
Quality System Requirements |
|
|
208 | (1) |
|
|
|
208 | (1) |
|
Appendices and References |
|
|
208 | (1) |
| Chapter 7 Traceability of Requirements Throughout the Life Cycle |
|
209 | (16) |
|
Keith Collyer and Jeremy Dick |
|
|
|
|
|
210 | (1) |
|
Systems Engineering and Requirements Management |
|
|
210 | (2) |
|
|
|
210 | (1) |
|
|
|
210 | (1) |
|
|
|
211 | (1) |
|
|
|
212 | (5) |
|
|
|
212 | (3) |
|
|
|
215 | (2) |
|
|
|
217 | (1) |
|
|
|
218 | (4) |
|
|
|
218 | (3) |
|
|
|
221 | (1) |
|
|
|
221 | (1) |
|
|
|
221 | (1) |
|
|
|
222 | (1) |
|
|
|
222 | (1) |
|
Risks, Issues, and Assumptions |
|
|
222 | (1) |
|
|
|
222 | (1) |
|
|
|
222 | (1) |
|
|
|
223 | (1) |
|
|
|
223 | (1) |
|
|
|
223 | (2) |
| Chapter 8 Good Documentation in Practice |
|
225 | (16) |
|
|
|
|
|
|
226 | (2) |
|
|
|
227 | (1) |
|
|
|
227 | (1) |
|
|
|
227 | (1) |
|
Document Management Tasks |
|
|
228 | (1) |
|
|
|
228 | (7) |
|
|
|
228 | (1) |
|
|
|
228 | (3) |
|
|
|
229 | (1) |
|
|
|
229 | (1) |
|
|
|
230 | (1) |
|
|
|
230 | (1) |
|
|
|
231 | (1) |
|
|
|
231 | (1) |
|
Document Information and Attributes |
|
|
231 | (1) |
|
|
|
231 | (1) |
|
|
|
231 | (2) |
|
Document and Record Management |
|
|
233 | (2) |
|
Creating and Modifying Documents |
|
|
233 | (1) |
|
|
|
233 | (1) |
|
|
|
234 | (1) |
|
Master Document List (MDL) |
|
|
234 | (1) |
|
|
|
235 | (1) |
|
|
|
235 | (1) |
|
|
|
235 | (1) |
|
Handwritten Record Entries |
|
|
235 | (2) |
|
|
|
235 | (1) |
|
|
|
235 | (1) |
|
|
|
236 | (1) |
|
Changes or Additions to Records |
|
|
236 | (1) |
|
Signature and Initial Logs |
|
|
236 | (1) |
|
|
|
237 | (1) |
|
Electronic Document Security |
|
|
237 | (1) |
|
Hard Copy Document Security |
|
|
237 | (1) |
|
|
|
237 | (5) |
|
|
|
237 | (2) |
|
|
|
239 | (2) |
| Chapter 9 Good Testing Practice: Part 1 |
|
241 | (22) |
|
|
|
|
|
|
242 | (1) |
|
|
|
243 | (1) |
|
|
|
243 | (1) |
|
Testing, Verification, and Validation |
|
|
243 | (1) |
|
|
|
244 | (2) |
|
|
|
244 | (1) |
|
|
|
245 | (1) |
|
Testing Within the Validation Life Cycle |
|
|
246 | (2) |
|
|
|
246 | (1) |
|
Specifications and Requirements |
|
|
247 | (1) |
|
|
|
248 | (8) |
|
|
|
248 | (1) |
|
Testing and Risk Assessment |
|
|
248 | (3) |
|
The Nature and Scope of Testing |
|
|
251 | (5) |
|
|
|
251 | (1) |
|
|
|
251 | (4) |
|
How Much Testing Is Enough? |
|
|
255 | (1) |
|
|
|
256 | (3) |
|
|
|
257 | (2) |
|
Test Coverage and Traceability |
|
|
259 | (1) |
|
Test Procedures and Training |
|
|
259 | (1) |
|
|
|
260 | (1) |
|
|
|
261 | (2) |
| Chapter 10 Enterprise Resource Planning Systems - Aligning Business and Validation Requirements |
|
263 | (28) |
|
A. Nobibux, Julien Peters, Steve Sharp, and James Stafford |
|
|
|
Key Differences in ERP System Usage within Regulated Organizations |
|
|
265 | (2) |
|
Optimizing the Methodology |
|
|
267 | (6) |
|
Implementer's Methodology May Be Incomplete |
|
|
267 | (2) |
|
Organizations' Computer Validation Methodology Inappropriate |
|
|
269 | (2) |
|
Company's IS Organization and Processes Inappropriate |
|
|
271 | (1) |
|
Quality Planning Component of Project Methodology Required |
|
|
271 | (2) |
|
|
|
273 | (2) |
|
Understanding the Project Context |
|
|
274 | (1) |
|
|
|
274 | (1) |
|
Appropriately Incentivized Implementers |
|
|
275 | (1) |
|
Vendor and Implementer Selection |
|
|
275 | (1) |
|
|
|
275 | (2) |
|
Integration of Implementation and Validation Work Streams |
|
|
276 | (1) |
|
|
|
277 | (1) |
|
|
|
277 | (4) |
|
User Requirements Specification |
|
|
278 | (3) |
|
Evolution of Solution Design |
|
|
281 | (1) |
|
Functional Requirements Specification |
|
|
281 | (1) |
|
|
|
281 | (1) |
|
|
|
281 | (1) |
|
|
|
282 | (1) |
|
Test Scripting and User Operating Procedures |
|
|
282 | (1) |
|
|
|
282 | (1) |
|
|
|
282 | (3) |
|
Test Planning and Execution |
|
|
283 | (1) |
|
|
|
283 | (1) |
|
|
|
284 | (1) |
|
|
|
285 | (1) |
|
|
|
285 | (1) |
|
Go Live Is a Process Not Solely a Decision |
|
|
285 | (1) |
|
Vindication of Go-Live Decision |
|
|
286 | (1) |
|
|
|
286 | (3) |
|
Consolidation and Improvement |
|
|
286 | (1) |
|
|
|
287 | (1) |
|
|
|
288 | (1) |
|
|
|
289 | (1) |
|
|
|
289 | (2) |
| Chapter 11 Calibration in Practice |
|
291 | (32) |
|
|
|
|
|
|
292 | (1) |
|
Why Calibration Is Important to Validation? |
|
|
292 | (1) |
|
Key Regulatory Requirements |
|
|
293 | (1) |
|
|
|
294 | (1) |
|
|
|
295 | (3) |
|
|
|
296 | (1) |
|
Adjustment of Calibration Interval |
|
|
297 | (1) |
|
|
|
298 | (1) |
|
|
|
298 | (2) |
|
|
|
300 | (15) |
|
Instrument Selection and Types |
|
|
300 | (2) |
|
|
|
302 | (5) |
|
|
|
307 | (1) |
|
|
|
308 | (1) |
|
|
|
308 | (2) |
|
|
|
310 | (1) |
|
|
|
311 | (1) |
|
Smart Calibrators and Test Equipment |
|
|
312 | (1) |
|
|
|
313 | (1) |
|
|
|
314 | (1) |
|
|
|
314 | (1) |
|
|
|
315 | (1) |
|
|
|
316 | (4) |
|
|
|
317 | (1) |
|
Calibration Results Sheets |
|
|
317 | (2) |
|
|
|
319 | (1) |
|
|
|
320 | (1) |
|
|
|
320 | (1) |
|
|
|
321 | (1) |
|
|
|
321 | (1) |
|
|
|
322 | (1) |
| Chapter 12 Validating Legacy Systems |
|
323 | (48) |
|
|
|
|
|
|
324 | (1) |
|
|
|
324 | (3) |
|
|
|
327 | (21) |
|
|
|
328 | (2) |
|
The System Assessment Documents |
|
|
330 | (15) |
|
|
|
331 | (2) |
|
|
|
333 | (3) |
|
General and Detailed Assessment Protocols |
|
|
336 | (1) |
|
The General Assessment Protocol |
|
|
336 | (5) |
|
The Detailed Assessment Protocol |
|
|
341 | (2) |
|
|
|
343 | (2) |
|
|
|
345 | (2) |
|
|
|
347 | (1) |
|
Managing Legacy Systems (Execution) |
|
|
348 | (18) |
|
Decommissioning (System Retirement) |
|
|
349 | (1) |
|
|
|
350 | (1) |
|
|
|
350 | (1) |
|
Hybrid Systems and Procedural Controls |
|
|
351 | (2) |
|
|
|
353 | (12) |
|
|
|
365 | (1) |
|
|
|
366 | (1) |
|
|
|
366 | (2) |
|
|
|
368 | (1) |
|
Suggestions for Further Reading and Related Websites |
|
|
369 | (2) |
| Chapter 13 Technology Transfer Keys |
|
371 | (28) |
|
Stewart Green and Paul Warren |
|
|
|
|
|
372 | (1) |
|
The Technology Transfer Team |
|
|
372 | (2) |
|
Technology Transfer: Key Activities |
|
|
374 | (19) |
|
|
|
374 | (1) |
|
|
|
375 | (5) |
|
Determining the Process Scope |
|
|
380 | (1) |
|
|
|
380 | (1) |
|
|
|
381 | (1) |
|
|
|
382 | (9) |
|
|
|
383 | (4) |
|
|
|
387 | (11) |
|
|
|
398 | |
|
|
|
390 | (1) |
|
|
|
391 | (1) |
|
|
|
392 | (1) |
|
|
|
393 | (1) |
|
The Technology Transfer Report |
|
|
393 | (2) |
|
|
|
393 | (2) |
|
|
|
395 | (1) |
|
|
|
395 | (1) |
|
Technology Transfer Checklist |
|
|
396 | (1) |
|
|
|
396 | (3) |
| Chapter 14 Qualifying SCADA Systems in Practice Acquisition |
|
399 | (22) |
|
|
|
|
|
|
399 | (1) |
|
|
|
400 | (1) |
|
|
|
401 | (2) |
|
|
|
403 | (1) |
|
|
|
404 | (1) |
|
Qualification and Project Life Cycle |
|
|
405 | (2) |
|
Business and Regulatory Requirements |
|
|
407 | (12) |
|
Software Configuration and Hardware Specifications |
|
|
408 | (4) |
|
Configuration and Installation |
|
|
412 | (2) |
|
|
|
414 | (2) |
|
System Use and Performance Evaluation |
|
|
416 | (3) |
|
|
|
419 | (2) |
| Chapter 15 The Application of GAMP 4 Guidelines to Computer Systems Found in GLP Regulated Areas |
|
421 | (14) |
|
|
|
|
Part 1 The Academic Side of the Subject |
|
|
421 | (6) |
|
Part 2 The Practical Side of the Subject |
|
|
427 | (5) |
|
Definitions of the Main Acronyms in This Chapter |
|
|
432 | (2) |
|
|
|
434 | (1) |
| Chapter 16 The Validation of a LIMS System - A Case Study |
|
435 | (26) |
|
David Hogg and Fernando Pedeconi |
|
|
|
|
|
436 | (1) |
|
LIMS in the Pharmaceutical Industry - Introduction |
|
|
436 | (1) |
|
LIMS Software Development Life Cycle and Validation |
|
|
437 | (11) |
|
The Validation Roadmap - Requirements for a New or Existing System |
|
|
439 | (1) |
|
Risk Management and Traceability Matrix |
|
|
440 | (1) |
|
21 CFR Part 11 - Considerations within a LIMS Environment |
|
|
441 | (2) |
|
Building or Customizing the System - Giving Shape to the Application |
|
|
443 | (2) |
|
|
|
443 | (1) |
|
Interfacing with Other Business Systems |
|
|
444 | (1) |
|
|
|
445 | (1) |
|
Pre-"Cut Over" Testing and "Go or No Go" Decision |
|
|
445 | (2) |
|
Post "Cut Over" Testing Performance Qualification |
|
|
447 | (1) |
|
|
|
448 | (2) |
|
Data Archiving and Migration |
|
|
448 | (1) |
|
Reporting and Query Tools |
|
|
448 | (1) |
|
Disaster Recovery and Business Continuity |
|
|
449 | (1) |
|
|
|
450 | (1) |
|
Case Study: A LIMS in AstraZeneca |
|
|
450 | (9) |
|
Background and Resource Issues |
|
|
451 | (1) |
|
|
|
451 | (1) |
|
|
|
452 | (1) |
|
Project Planning and Start-Up |
|
|
453 | (1) |
|
Documentation Development and Management |
|
|
454 | (2) |
|
|
|
454 | (1) |
|
|
|
454 | (1) |
|
Hardware Design Specification |
|
|
454 | (1) |
|
Software Design Specification |
|
|
454 | (1) |
|
|
|
455 | (1) |
|
|
|
456 | (1) |
|
|
|
456 | (1) |
|
|
|
456 | (1) |
|
|
|
457 | (1) |
|
|
|
458 | (1) |
|
|
|
459 | (2) |
| Chapter 17 Compliance and Validation in Central and Eastern Europe (CEE) |
|
461 | (12) |
|
Paul Irving, Carl Turner, Wayne Duncan, and David Forrest |
|
|
|
|
|
461 | (1) |
|
|
|
462 | (2) |
|
Healthcare Spending in Western Europe |
|
|
463 | (1) |
|
Healthcare and IT Spending in Eastern Europe |
|
|
463 | (1) |
|
Key Areas of GAMP for Emerging European Countries |
|
|
464 | (7) |
|
|
|
464 | (3) |
|
Communication, Training, and Education |
|
|
467 | (1) |
|
|
|
467 | (1) |
|
|
|
468 | (1) |
|
|
|
469 | (1) |
|
|
|
470 | (1) |
|
Software Engineering Techniques |
|
|
470 | (1) |
|
|
|
471 | (2) |
| Chapter 18 Distribution Management Validation in Practice |
|
473 | (18) |
|
|
|
|
|
|
473 | (2) |
|
|
|
475 | (10) |
|
Maintaining the Validated State |
|
|
485 | (1) |
|
|
|
485 | (2) |
|
Electronic Records and Signatures |
|
|
486 | (1) |
|
|
|
487 | (1) |
|
The Regulatory Environment |
|
|
488 | (1) |
|
|
|
489 | (1) |
|
Tackling and Solving Problems |
|
|
489 | (1) |
|
|
|
490 | (1) |
| Chapter 19 Good Testing Practice: Part 2 |
|
491 | (16) |
|
|
|
|
|
|
492 | (1) |
|
|
|
492 | (1) |
|
|
|
492 | (1) |
|
|
|
493 | (1) |
|
|
|
493 | (1) |
|
|
|
494 | (1) |
|
|
|
495 | (2) |
|
Fundamental Understanding |
|
|
497 | (6) |
|
|
|
498 | (1) |
|
"Ensure Complete Traceability" |
|
|
498 | (1) |
|
|
|
499 | (1) |
|
"Everything Should Be Witnessed" |
|
|
500 | (1) |
|
|
|
501 | (1) |
|
|
|
501 | (1) |
|
|
|
502 | (1) |
|
|
|
503 | (3) |
|
|
|
504 | (1) |
|
|
|
504 | (1) |
|
Test Review and Incident Analysis |
|
|
505 | (1) |
|
Test Metrics and Statistics |
|
|
505 | (1) |
|
|
|
506 | (1) |
| Chapter 20 Practical Applications of GAMP Version 4 |
|
507 | (18) |
|
|
|
|
|
|
507 | (1) |
|
Vendor Auditing Using GAMP4 Guidance and Templates |
|
|
508 | (12) |
|
|
|
509 | (1) |
|
B Organization and Quality Management |
|
|
510 | (2) |
|
C Planning and Product, Project Management |
|
|
512 | (1) |
|
|
|
512 | (1) |
|
|
|
513 | (1) |
|
|
|
514 | (2) |
|
|
|
516 | (1) |
|
H Support and Maintenance |
|
|
517 | (2) |
|
I Supporting Procedures and Activities |
|
|
519 | (1) |
|
|
|
520 | (2) |
|
|
|
522 | (1) |
|
|
|
523 | (2) |
| Chapter 21 Glossary and Abbreviations |
|
525 | (12) |
|
|
|
| Index |
|
537 | |