EU Pharmacovigilance Inspection Findings: CAPA Effectiveness and Recurrence of Deficiencies

Learn how to distinguish CAPA completion from effectiveness and how recurrence, scope, root cause and verification are assessed during pharmacovigilance inspection follow-up.

Audio Lesson 16 min
Knowledge Assessment Test your understanding of this article. Take the assessment →

EU Pharmacovigilance Inspection Findings: CAPA Effectiveness and Recurrence of Deficiencies

1. Purpose and Scope

A pharmacovigilance inspection finding is not resolved merely because a corrective action and preventive action (CAPA) record has been opened, assigned and eventually marked complete. The regulatory question is whether the organisation has corrected the identified problem, addressed its underlying cause where appropriate, and established controls that prevent recurrence or detect recurrence in a timely manner.

This distinction becomes particularly important when a pharmacovigilance deficiency has arisen from a failure of the quality system. A revised procedure, additional training or a database correction may remove the immediate defect while leaving the mechanism that produced the defect unchanged. An effective inspection assessment therefore extends beyond the status of individual CAPA actions and examines whether the pharmacovigilance system has actually become more reliable.

This article examines CAPA effectiveness and recurrence from that inspection perspective. It does not reproduce the general CAPA framework already covered elsewhere on QPPV.com. Instead, it focuses on how an inspector can evaluate whether remediation has worked and how repeated or related deficiencies can reveal a systemic weakness.

2. Why CAPA Effectiveness Matters in Pharmacovigilance

Pharmacovigilance processes are interconnected. A weakness in intake, case processing, quality control, vendor oversight, signal management or reporting can affect multiple products, markets and reporting periods. The significance of a deficiency therefore cannot always be inferred from the individual record in which it was first detected.

A CAPA that addresses only the observed transaction may correct the visible error without changing the process that allowed it. Conversely, a well-designed CAPA may not eliminate every future error, but it should provide reasonable assurance that the identified failure mode has been controlled and that meaningful recurrence will be detected.

This is why effectiveness is a distinct concept from completion. Completion asks whether the planned action was performed. Effectiveness asks whether the action achieved its intended control objective.

3. Regulatory Framework

The EU pharmacovigilance framework places quality systems at the centre of compliance. GVP Module I describes the quality system, including documentation, compliance management, audits, monitoring and the handling of deficiencies and deviations. It also links quality objectives to methods for monitoring the effectiveness of the pharmacovigilance system. citeturn0search27

GVP Module III establishes the inspection framework. Pharmacovigilance inspections are intended to determine whether the marketing authorisation holder has the personnel, systems and facilities necessary to meet its obligations and to identify, record and address non-compliance that may pose a public-health risk. Inspection follow-up is part of that framework. citeturn0search28

The legal and GVP framework therefore supports an important distinction: an inspection finding is evidence of a compliance problem at a particular point in time, whereas CAPA effectiveness is concerned with whether the control environment has been appropriately improved in response.

4. Finding, Correction, Corrective Action and Preventive Action

These terms describe different stages of the response and should not be treated as interchangeable.

A correction addresses an identified instance of non-conforming work. For example, an incorrectly processed case may be reassessed and corrected.

A corrective action addresses the cause of the identified non-conformity so that the same type of problem is less likely to recur.

A preventive action, where used within the organisation's quality framework, addresses a potential cause of non-conformity before recurrence or occurrence of a related problem.

The inspection significance lies in the relationship between them. If the same control failure could affect other cases, products or affiliates, correcting the sampled record is insufficient. The organisation must assess the wider scope and determine what additional action is justified.

5. CAPA Closure Is Not the Same as CAPA Effectiveness

CAPA closure generally demonstrates that defined actions have been completed or otherwise dispositioned according to the organisation's process. It does not automatically demonstrate that the underlying problem has been controlled.

Consider an illustrative example in which an inspection identifies failures in the quality review of expedited cases. The organisation revises the procedure, retrains the reviewers and reviews a set of historical cases. Those actions may be appropriate, but the inspection question does not end there. The organisation should also establish why the existing control failed and whether the revised control performs as intended.

An effectiveness assessment might therefore examine subsequent cases over an appropriate period, using criteria that are capable of detecting recurrence. The exact sampling strategy should be based on the failure mode and risk rather than a universally fixed number of cases.

This example is illustrative and is not presented as a published inspection finding.

6. The Logic of an Effective CAPA

A useful way to analyse CAPA effectiveness is to follow the chain:

finding → immediate correction → scope assessment → root cause → corrective action → implementation → effectiveness verification → recurrence monitoring

A weakness at any stage can undermine the overall response.

If scope assessment is inadequate, affected processes may remain uncorrected. If root-cause analysis is superficial, the corrective action may address only the symptom. If implementation is incomplete, the intended control may never operate. If effectiveness verification is poorly designed, failure of the new control may go undetected.

The chain also explains why inspectors may return to an apparently closed issue through a different process. A later deviation, audit or case review may provide evidence that the earlier CAPA did not achieve its intended outcome.

7. Scope Assessment After a Finding

The first question after a significant finding is often not "How do we fix this record?" but "How far could this problem extend?"

Scope assessment can consider the period affected, products, indications, countries, affiliates, vendors, systems, process variants and personnel involved. The relevant dimensions depend on the finding.

For example, a failure in a centrally managed case-processing workflow may require assessment across all products using that workflow. A local affiliate issue may have a narrower scope, but the organisation should still consider whether the same procedure or training model exists elsewhere.

Scope assessment should be documented sufficiently to explain the basis for the conclusions reached. A narrow scope may be entirely appropriate, but the rationale should be defensible.

8. Root Cause: From Description to Explanation

Root-cause analysis is useful only if it explains why the control failed.

Statements such as "human error," "lack of attention" or "training gap" may describe an immediate contributor without explaining the system conditions that allowed the failure. An inspector may therefore ask what prevented the organisation's existing controls from detecting or preventing the error.

A stronger analysis may identify factors such as ambiguous procedures, incompatible workflow design, inadequate system configuration, unclear ownership, insufficient workload controls, weak quality review, ineffective escalation or a change-control failure.

Not every finding has a single root cause. Multiple contributing factors may need to be considered, and the organisation should avoid forcing a complex failure into a simplistic causal label merely to complete a CAPA form.

9. Selecting the Effectiveness Measure

The effectiveness measure should test the control that was intended to be improved.

If the root cause concerns inadequate review, the effectiveness assessment should test the quality of subsequent review. If the root cause concerns missed escalation, the assessment should test whether escalation occurs when the defined trigger is met. If the problem concerns vendor oversight, the measure should examine whether the revised oversight mechanism identifies and manages vendor performance appropriately.

This principle can be expressed as:

failed control → revised control → evidence that the revised control works

A measure that merely confirms completion of training or publication of a revised SOP may demonstrate implementation but not effectiveness.

10. Designing an Appropriate Observation Period

The observation period should allow the revised control to encounter the circumstances in which the original failure could recur.

For a high-volume case-processing process, meaningful evidence may accumulate relatively quickly. For a periodic aggregate-reporting process, the appropriate evidence may arise only when the relevant reporting cycle occurs. For an infrequent vendor or governance activity, a longer period or a different verification strategy may be necessary.

There is therefore no universal CAPA-effectiveness duration that can be applied to every pharmacovigilance finding. The period should be justified by the process frequency, risk, recurrence mechanism and available evidence.

11. Sampling and Statistical Interpretation

Sampling can provide useful evidence, but its interpretation requires care. A sample with no observed errors does not prove that a process can never fail. It provides evidence about performance within the sampled conditions.

The sampling approach should therefore be aligned with the question being tested. Random sampling, targeted sampling, consecutive-case review and risk-based sampling answer different questions. Where quantitative thresholds are used, they should have a clear rationale rather than being selected simply because they are convenient.

The purpose of effectiveness verification is not to manufacture a pass/fail number. It is to determine whether the revised control is functioning sufficiently to address the identified failure mode.

12. When a CAPA Appears Effective but the Problem Recurs

Recurrence does not automatically prove that the original CAPA was unreasonable. A process may experience an isolated new failure even after an effective control has been implemented. The important question is whether the recurrence represents the same failure mode, a related failure mode or an unrelated event.

If recurrence demonstrates that the same underlying cause remains uncontrolled, the organisation should reassess the original root-cause analysis and effectiveness methodology. It may also need to examine whether the monitoring period was too short, the sample was unrepresentative or the effectiveness criterion did not test the critical control.

This is where recurrence becomes an important quality-system signal rather than simply another deviation.

13. Recurrence as Evidence of a Control Problem

When a similar deficiency appears after CAPA implementation, the first task is to establish whether the recurrence is genuinely related to the original finding. The organisation should compare the failure mode, process step, causal factors and control that was intended to prevent recurrence.

A recurrence may reveal that the original corrective action was too narrow, that the root cause was incorrectly identified, that implementation was incomplete, or that the effectiveness assessment did not test the relevant control under realistic conditions.

The fact of recurrence should therefore trigger investigation rather than an automatic conclusion that the earlier CAPA was inadequate. The quality-system response should be proportionate to the evidence.

14. Repeated Findings Across Different Processes

A systemic weakness can also appear without an identical finding recurring. For example, an organisation might experience separate deficiencies involving case quality control, aggregate-reporting review and vendor oversight. The individual processes are different, but each may reveal inadequate ownership, weak escalation or ineffective quality review.

Inspectors may therefore consider patterns across findings rather than treating every observation in isolation. This is one reason why trend analysis of deviations, audits, CAPAs and inspection findings can be valuable to management and QPPV oversight.

A pattern does not by itself prove a common root cause. It is evidence that warrants assessment of whether a shared control weakness exists.

15. CAPA Effectiveness and Risk

Effectiveness assessment should be proportionate to the risk associated with the failure. A deficiency affecting a critical reporting obligation may require a more intensive verification approach than a low-impact documentation discrepancy.

Risk assessment can consider the potential effect on patients, regulatory compliance, data integrity, reporting timeliness, signal detection and the scope of potentially affected activities. It should also consider the likelihood that the failure could recur before the revised control has been demonstrated to work.

Risk should inform both the CAPA design and the evidence needed to demonstrate effectiveness. It should not be used as a reason to avoid investigating a recurring problem simply because individual errors appear minor.

16. Immediate Correction Versus Systemic Remediation

A useful inspection distinction is between restoring compliance in the affected records and improving the process that produced the non-compliance.

For example, correcting a set of overdue cases may restore the records. It does not by itself demonstrate that the case-management process can consistently identify and process future cases within the required timeframe.

Systemic remediation may therefore involve workflow changes, system controls, workload management, quality review, escalation or governance. The appropriate action depends on the root cause.

The organisation should be able to explain why the selected CAPA addresses the cause identified by its investigation.

17. Training: When It Is and Is Not a Sufficient CAPA

Training is often an appropriate component of CAPA, but training should not automatically be treated as the solution to a process failure.

If personnel were genuinely unaware of a clearly defined requirement, targeted training may be necessary. If the procedure was ambiguous, the system workflow encouraged the wrong action, the required information was unavailable or the quality-control mechanism failed, training alone may leave the underlying problem intact.

An inspector may therefore ask what evidence demonstrates that training was the appropriate intervention and whether the revised process remains effective after training has been completed.

18. Procedure Revision as CAPA

A revised SOP can correct an inadequate instruction, but publication of the new document is evidence of implementation rather than proof of effectiveness.

The effectiveness assessment should test whether the revised instruction is understood and followed in practice and whether it produces the intended outcome. Depending on the finding, this might involve targeted record review, process observation, quality-control results or other objective evidence.

Where a procedure was not the true cause of the failure, repeatedly revising procedures can create document complexity without improving performance. CAPA effectiveness should therefore be linked to the causal analysis rather than to the number of documents changed.

19. System Changes and CAPA Effectiveness

Technology can be an important corrective intervention when the failure is caused or enabled by system design. Automated controls, mandatory fields, workflow restrictions and escalation alerts can sometimes provide stronger preventive control than reliance on individual attention.

However, a system change also introduces new risks. The organisation should establish that the change was appropriately controlled and that the resulting workflow performs as intended.

For inspection purposes, evidence may therefore extend beyond the CAPA record to change control, validation or qualification documentation where applicable, testing, user acceptance, monitoring and subsequent performance data.

Where a deficiency involves an outsourced activity, CAPA effectiveness should address the interface between the marketing authorisation holder and the service provider.

A vendor may implement a local corrective action while the MAH still needs to demonstrate that the overall pharmacovigilance control is effective. Relevant evidence can include revised procedures, training, quality oversight, performance metrics, audit activity, issue escalation and subsequent service-level or quality results, as appropriate.

The appropriate response depends on the contractual and operational arrangement. The MAH should nevertheless be able to demonstrate effective oversight of outsourced pharmacovigilance activities.

21. CAPA Metrics and Their Limitations

Quality metrics can help identify whether a control is improving, but a metric should not be confused with effectiveness evidence.

For example, a reduction in the number of deviations may reflect genuine improvement, but it could also reflect under-reporting. A high CAPA on-time-closure rate may demonstrate administrative performance while saying little about whether the CAPAs solved the underlying problems.

Useful metrics should therefore be interpreted alongside qualitative evidence and, where appropriate, direct testing of the affected process.

22. What Inspectors May Examine During Follow-Up

A follow-up assessment can examine several layers of evidence:

Layer Example evidence Question
Finding Inspection observation and scope assessment What was the original problem?
Correction Corrected cases or records Was the immediate problem addressed?
Root cause Investigation and causal analysis Why did the control fail?
CAPA Approved action plan Does the action address the cause?
Implementation Revised process, system or training evidence Was the action actually implemented?
Effectiveness Subsequent performance evidence Does the revised control work?
Recurrence Later deviations, audits or inspection evidence Has the failure or a related weakness returned?

This layered approach helps distinguish administrative completion from substantive remediation.

23. Illustrative Inspection Scenario: The Closed CAPA That Did Not Control the Failure

Consider a hypothetical finding involving repeated late processing of safety information received through a particular intake channel.

The organisation identifies insufficient staff training as the root cause, conducts refresher training and closes the CAPA after confirming that all personnel completed the course.

Several months later, a review identifies further late cases from the same channel.

The recurrence should prompt a reassessment. The underlying problem might instead involve unclear ownership of the intake channel, inadequate monitoring, a workflow configuration problem or an escalation mechanism that was not functioning. The original effectiveness measure tested training completion rather than the performance of the intake control.

The scenario is illustrative. It is not presented as a published regulatory finding.

24. Illustrative Inspection Scenario: A CAPA That Addresses the Control

In a second hypothetical example, an organisation identifies that a quality-control step was not reliably performed because the workflow allowed a case to progress without completion of the required review.

The corrective action changes the workflow so that the next processing stage cannot be completed until the review is documented. The organisation then monitors subsequent cases and independently verifies that the control operates as intended.

Here the CAPA is more closely connected to the identified failure mechanism. The effectiveness evidence tests the revised control rather than simply demonstrating that personnel were informed about it.

Again, this is an illustrative scenario, not a reported inspection finding.

25. The Role of Audits in CAPA Effectiveness

Internal audits can provide evidence about whether CAPA has worked, particularly when they are designed to test the relevant process rather than simply confirm document availability.

An audit performed shortly after implementation may demonstrate that the new process exists. A later risk-based audit may provide stronger evidence about sustained effectiveness, depending on the nature of the finding.

The audit programme should remain independent enough to provide meaningful assurance, and audit results should feed into the broader quality-system oversight process.

26. QPPV Oversight of Significant CAPA

The QPPV should have appropriate visibility of significant pharmacovigilance deficiencies and their remediation. The precise governance mechanism is organisation-specific, but significant CAPA should not become invisible after assignment to an operational owner.

Useful oversight may include review of major inspection findings, risk assessments, significant deviations, recurring problems, overdue CAPA, effectiveness results and escalation where remediation is not achieving its intended outcome.

The QPPV's role is not to replace the quality function or CAPA owner. It is to maintain appropriate oversight of issues that may affect the pharmacovigilance system and its compliance.

27. When Effectiveness Evidence Is Negative

An unsuccessful effectiveness assessment is not necessarily a failure of the quality system. It can provide valuable evidence that the initial CAPA was insufficient and needs to be redesigned.

The important governance question is whether the organisation recognises the result, reassesses the problem and acts appropriately. Attempting to redefine the effectiveness criterion after an unsuccessful result merely to obtain a favourable outcome would undermine the purpose of effectiveness monitoring.

A mature system treats negative effectiveness evidence as information for further improvement.

28. Inspection Questions for CAPA Effectiveness

The following are illustrative inspection questions, not a published regulator checklist:

29. Practical Self-Inspection Framework

A useful internal review can be organised around seven questions:

Question Evidence to seek
What failed? Original finding, deviation or audit evidence
How broad was it? Scope assessment and affected-population analysis
Why did it fail? Root-cause and contributing-factor analysis
What changed? CAPA, procedures, systems and training
Does the change address the cause? Traceability from root cause to action
Does the new control work? Objective effectiveness evidence
Has the problem stayed controlled? Subsequent trends, deviations, audits and other evidence

This framework can be applied internally without presenting the resulting questions as regulatory requirements.

30. Inspection Implications

From an inspection perspective, the strongest remediation package is one in which the organisation can reconstruct the reasoning from the original finding to the evidence of sustained control.

The inspector should be able to understand what failed, why it failed, how the organisation determined the scope, why the CAPA was selected, how implementation was verified and what evidence demonstrates effectiveness.

Where recurrence occurs, the organisation should be able to explain whether it represents a failure of the original control, a different failure mode or an isolated event, and what action was taken as a result.

The quality of this evidence often matters more than the apparent sophistication of the CAPA terminology.

31. Distinguishing Published Findings from Illustrative Failure Modes

Inspection literature should be handled carefully. EMA and national competent authorities publish inspection statistics, reports and, in some circumstances, descriptions of deficiencies. These sources can support statements about actual regulatory findings.

By contrast, a scenario such as an ineffective training CAPA, an inappropriate sampling plan or recurrence after a procedure change is not a regulatory finding merely because it is plausible. Such examples are useful for teaching inspection reasoning, but they should be labelled as illustrative.

This distinction is particularly important when discussing CAPA because organisations can experience many potential failure modes that are never published as inspection observations. The article therefore uses examples to explain how an inspector could test a control, not to imply that a regulator has made the specific observation.

32. What Recurrence Can Reveal About the Quality System

Repeated or related deficiencies can provide evidence about the performance of the quality system itself. If the organisation repeatedly identifies similar problems but CAPA does not prevent recurrence, the issue may extend beyond the individual operational process.

Possible explanations include inadequate root-cause analysis, weak management oversight, poor trend review, ineffective change control, insufficient resources or a quality system that is better at documenting problems than controlling them.

The appropriate conclusion depends on the evidence. A pattern should trigger assessment rather than automatic classification as a systemic failure.

33. CAPA Effectiveness as a Management Signal

CAPA effectiveness information should not remain confined to the individual CAPA owner. Trends in recurring deficiencies can provide management with information about whether the pharmacovigilance system is improving or whether certain controls remain fragile.

Useful governance questions include whether significant CAPA is recurring, whether effectiveness failures cluster in particular processes or vendors, whether actions remain overdue, and whether repeated findings share contributing factors.

This provides a bridge between operational quality management and senior pharmacovigilance oversight. The objective is not to maximise CAPA closure rates but to understand whether the system is controlling important risks.

34. Relationship Between Inspection Findings and Internal Findings

An organisation should not wait for an external inspection to discover that CAPA is ineffective. Deviations, audits, quality reviews, vendor oversight and management monitoring can all provide earlier evidence.

An external inspection finding may therefore be viewed as one point in a broader evidence system. If internal controls were already identifying the same problem, the organisation should be able to demonstrate how it assessed and managed those signals. If internal controls did not detect an important failure, that absence may itself warrant examination of the quality system.

The purpose is not to make internal systems imitate an inspector. It is to ensure that important failures are identified and addressed before they become persistent compliance problems.

35. CAPA Effectiveness and Data Integrity

Effectiveness conclusions depend on the reliability of the evidence used to support them. If the records used to demonstrate improvement are incomplete, selectively sampled or not traceable to the underlying process, the conclusion may be weak even if the CAPA itself is well designed.

The evidence should therefore be sufficiently attributable, contemporaneous, traceable and representative for the question being answered. Where automated data are used, the organisation should understand how the relevant metric is generated and whether the underlying data are complete.

This is another reason why a numerical effectiveness metric should not automatically be treated as objective proof of control.

36. CAPA Effectiveness After Organisational Change

A CAPA can become less effective if the organisation changes after the corrective action has been implemented. Reorganisation, outsourcing, system migration, product acquisition or transfer of responsibilities can alter the assumptions on which the original control was based.

Where a material change affects the remediated process, the organisation should assess whether the CAPA control remains applicable and whether additional verification is needed.

This connects CAPA governance with the broader change-control principles discussed in the PSMF and cross-functional interface articles in this series.

37. A Practical Evidence Hierarchy

Not all evidence provides the same level of assurance. A useful conceptual hierarchy is:

  1. Action completed — the CAPA step was performed.
  2. Process implemented — the revised control is operating.
  3. Performance demonstrated — objective evidence shows the control is producing the intended result.
  4. Sustained performance — the control continues to work under relevant operating conditions.
  5. Recurrence surveillance — subsequent information does not indicate return of the failure mode or reveals recurrence early enough for effective intervention.

The hierarchy is analytical rather than a regulatory grading system. Not every CAPA requires every layer to the same extent. The appropriate evidence depends on risk and the nature of the finding.

38. Common Weak CAPA Patterns

The following are useful analytical categories for self-assessment, not claims of published inspection findings:

Pattern Why it may be weak
Training-only response May not address process or system causes
SOP-only response May correct wording without changing practice
Correction-only response Does not address recurrence
Root cause = human error May stop the investigation too early
Closure based on action completion Does not demonstrate effectiveness
Very short effectiveness period May not expose the failure mode
Arbitrary sample size May provide weak evidence for the question being tested
Metric without source-data review May conceal data or denominator problems
No recurrence review Misses evidence that the control later failed
CAPA owned in isolation Can miss cross-functional or system-level causes

These categories help an organisation test the reasoning behind its CAPA without presenting them as regulatory requirements.

39. CAPA Effectiveness and the QPPV's Broader Oversight

The QPPV's oversight of significant deficiencies should extend beyond awareness that a CAPA exists. Where a deficiency may materially affect the pharmacovigilance system, the QPPV should have appropriate visibility of the problem, its risk assessment, remediation and relevant effectiveness evidence.

This does not mean that the QPPV becomes the operational CAPA manager. The quality system should retain defined ownership and accountability. The QPPV's contribution is to ensure that significant pharmacovigilance risks and system weaknesses receive appropriate oversight and escalation.

Where recurring CAPA failures reveal a broader weakness, that information may be relevant to the QPPV's assessment of the overall effectiveness of the pharmacovigilance system.

40. Key Takeaways

41. References

  1. European Medicines Agency. Guideline on good pharmacovigilance practices (GVP) Module I — Pharmacovigilance systems and their quality systems, current published version. EMA/541760/2011. urlEMA GVP Module Ihttps://www.ema.europa.eu/en/documents/scientific-guideline/guideline-good-pharmacovigilance-practices-module-i-pharmacovigilance-systems-and-their-quality-systems_en.pdf
  2. European Medicines Agency. GVP Module III — Pharmacovigilance inspections, Rev. 1. EMA/119871/2012. urlEMA GVP Module IIIhttps://www.ema.europa.eu/en/documents/scientific-guideline/guideline-good-pharmacovigilance-practices-module-iii-pharmacovigilance-inspections_en.pdf
  3. European Commission. Commission Implementing Regulation (EU) No 520/2012, as amended, concerning the performance of pharmacovigilance activities. urlEUR-Lex — Regulation 520/2012https://eur-lex.europa.eu/eli/reg_impl/2012/520/oj
  4. European Medicines Agency. Annual report of the Pharmacovigilance Inspectors' Working Group for 2024. EMA. urlEMA PhV IWG annual reportshttps://www.ema.europa.eu/en/human-regulatory-overview/marketing-authorisation/compliance-marketing-authorisation/pharmacovigilance-inspections-veterinary-medicines/pharmacovigilance-inspectors-working-group
  5. European Medicines Agency. Annual report of the Pharmacovigilance Inspectors' Working Group for 2023. EMA/INS/PhV/471069/2024. urlEMA PhV IWG 2023 reporthttps://www.ema.europa.eu/system/files/documents/report/annual-report-pharmacovigilance-inspectors-working-group-2023_final_en_0.pdf
  6. European Medicines Agency. Inspections and compliance — EMA Annual Report 2024. urlEMA Annual Report 2024 — Inspections and compliancehttps://www.ema.europa.eu/assets/en/annual-report/2024/inspections-and-compliance/index.html

Regulatory Note

This article is an educational analysis of CAPA effectiveness and recurrence in the context of EU pharmacovigilance inspections. It distinguishes legal requirements and GVP guidance from recommended operational practice and illustrative scenarios. The hypothetical examples and analytical categories in this article are not presented as published regulatory inspection findings. Current legislation, GVP guidance, national requirements and applicable inspection procedures should be checked before the material is used for a specific regulatory or compliance decision.

Revision History