You dont have javascript enabled! Please enable it! Guidance 040 – Periodic Review of Processes and Systems Pharmaceuticals quality assurance & validation procedures GMPSOP

Guidance 040 – Periodic Review of Processes and Systems

Introduction

This guidance addresses the application of a risk-based approach to:

  • Prioritize the systems and processes for periodic review (PR)
  • Justify frequency and schedule of PR (if applicable)
  • Routine revalidation of processes

The scope of this guidance can be applied to validated test methods, manufacturing processes, sterile processes, equipment cleaning processes, and qualified systems (e.g. equipment, facilities, computer, process control automation and utilities).

The processes of conducting re-qualification and PR are also described.

Validated processes and qualified systems (from this point forward refers to equipment & computer systems) are required to be periodically evaluated to verify that they remain in a validated state. High risk processes (e.g. sterile or aseptic) may also require routine re-qualification and/or revalidation. The application of a risk-based approach allows:

  • The prioritization of PR and routine re-qualification/revalidations activities.
  • The scientific justification of the PR frequency and routine re-qualification /revalidation frequency (if applicable)

A PR is intended to satisfy the “quality review” referenced in ICH Q7A, section 12.60.

Recommendations & Rationale for Recommendations

1. Scope of the PR

Periodic Review (PR) applies to validated processes and systems.

Examples of the terminology used for critical systems include Direct Impact or critical. Periodic Review of the systems will apply according to the qualification approach used as indicated in Appendix1.

For systems, Appendix 1 provides guidance on the steps to be followed based on the approach used, how the risk assessment of systems is used, where it is documented, how the frequency of the PR is established and when the PR cycle starts.

2. Routine Process Revalidation/Requalification

Routine revalidation is only required for high risk processes (e.g. sterile/aseptic). The types of processes that are typically involved in routine revalidation include sterilization and aseptic processing (e.g. autoclaves, de-pyrogenation tunnels, steam-in-place systems, aseptic filling lines).

If Routine revalidation is required, it is typically conducted using a concurrent validation approach. The testing is executed on a preset frequency against a standardized pre-approved protocol or SOP.

If the time for routine revalidation is utilized to make changes to a process or the validated system supporting a process (e.g. change a loading pattern in an autoclave), then the revalidation should proceed in two steps. In this case, the previously validated parameters should be requalified to demonstrate the process has remained in a state of control since the previous re-qualification. Then the changes are made and the process is validated prospectively. The routine revalidation process should be based on conducting at least one validation run. The details of the tests required (for example: load configuration, container size) should be defined in the routine revalidation procedure.

3. Risk Assessment Approach

The risk assessment should include, as a minimum, an evaluation of the process/system criticality (risk to product quality and/or patient safety). In addition, evaluation of the probability of an adverse event and detectability can be used to further assess the level of quality risk associated with a process.

The risk assessment should be conducted jointly by representatives of the Quality Team and the Process Owner and other potential Subject Matter Experts(e.g., Validation/Technical Services).

4. Risk based PR for Processes

Where no significant changes have been made to the process, a PR (with evidence that the process is consistently producing product meeting its specifications) fulfills the need for revalidation.

Below are considerations for some specific types of processes:

  • Sterile and sterilization processes:

For sterile and sterilization processes that are subject, due to their criticality, to routine re-qualification, periodic review is not required as the evaluation of deviations, changes and process trends are covered by the Annual Product

  • Manufacturing processes:

An Annual Product Record Review is to be performed for all critical production stages or steps associated in a GMP site for API and marketed drug product. Depending on regulatory requirements in the intended drug product market, the Annual Product Record Review may include a Validation Summary. This meets the need for Periodic Review of the process.

Where there is no regulatory requirement to include validation in the Annual Product Record Review, it remains good practice to combine the Periodic Review of the manufacturing process with the Annual Product Record Review, as this already includes a review of the changes and deviations associated with the process.

  • Test methods:

Test methods typically have built in controls such as system suitability tests or trending of assay standards that provide a high level of confidence in the ongoing validity of the method. In addition, a review of laboratory data and laboratory investigations / deviations and associated corrective actions is required in the Annual Product Records Review. This meets the need for periodic review.

6. Periodic Review Process

Once the processes and systems for which PR is required have been defined, the PR Process consists of documenting and reviewing information related to the given process or system It involves the internal process of collecting and evaluating information to determine if the current process or system remains in a validated/ qualified state, and is being operated in accordance with applicable cGMP regulations, site policies and procedures. The typical content that may be included in the PR is included in Appendix 1.

Where the review considers records from existing quality systems, the purpose of the review is only to verify that the quality system has been followed and, for changes, evaluate the cumulative impact.

7. PR Frequency and Scheduling

It is recommended that the frequency of PR for systems and processes be determined using a risk based approach, where there is no defined frequency for periodic review, and the periodic review is not conducted in conjunction with another review exercise (such as Annual Product Record Review). The process for determining the frequency and scheduling of PR should be defined and documented. The assignment of frequencies based on risk should be documented and approved by the site Quality Team. The risk assessment and definition of when periodic review must be initiated must be approved by the Quality Team.

For Systems:

The determination of PR frequency and scheduling should be based on the system requirements documentation and any system (e.g. System level impact Assessment,) or component level impact assessments, or Quality Risk Assessment that have been previously completed.

This determination should be conducted jointly by representatives of the site Quality Team and the System Owner and other potential Experts (e.g., Engineering/Maintenance).

As a minimum this determination assessment should include an evaluation of the system criticality.

In addition, evaluation of the probability of an adverse event and detectability can be used to provide further justification of the level of quality risk associated with a system.

Refer to Appendix 2 (I) for systems risk assessment(RA) examples to determine PR frequency.

For Processes:

The initiation of a periodic review should be clearly defined for each process, and should be based on a risk assessment. There are many considerations that need to be included, some of which are listed below:

  • Criticality of the process and associated product(s) – e.g. final product, intermediate, bulk, route of administration.
  • Critical quality attributes of the product that are controlled and/or monitored by the system or process without downstream verification.
  • Probability of a critical parameter deviation being detected before it could reasonably affect product quality attributes.
  • Use of data from the system to demonstrate compliance with a registered process, including batch record, lot release or other GMP records.
  • Ability of trending system(s) being used to detect drift that may impact validation status of process
  • Frequency of trend data recording and review

A typical risk assessment process is based on the combination of process criticality, probability of an adverse event and detectability of an adverse event. This allows the assignment of an overall level of risk to the process, using either a quantitative numerical scale or a qualitative “High – Medium – Low” scale.

Where there is no requirement for a defined Periodic Review frequency, it may also be possible to justify no fixed frequency and to use trending (for example, using RFT techniques) of existing quality/management systems such as:

  • change management
  • deviations and failures
  • routine checks required as part of process set up or operation

Refer to Appendix 2 (II) for processes RA examples to determine PR frequency.

8. Additional considerations

System documentation

Updating of system documentation is typically controlled by a quality management system that includes a review process (for example; Change Management, SOP system, Training system); therefore, the review should not be duplicated by the PR.

The PR will evaluate the effect (if any) of the cumulative changes. However, if these quality management systems are not in place then the PR must also confirm that system documentation reflects the current status and operation, cleaning, maintenance and qualification of the system and documents have been updated as required.

Security Review

Where applicable, a review of system security, including appropriateness of user access and addition/removal of users is often carried out as a routine activity. If this is the case, then security would not need to be included in the PR. However, if there is no separate management system in place for these activities then they must be included in the PR. For example:

  • Security access and privilege review
  • Security log review; System log review
  • System Backup review;
  • Data integrity review, including archived and old data

9. Periodic Review Conclusion

After the analysis of the PR input data, a PR document should be written to address the following points as part of the conclusion:

Should state whether the validation documentation reflects the current process or system validation status and make any recommendations for revalidation/re-qualification, and potential continuous improvement of the process.

A confirmation that corrective actions listed in the document are tracked (e.g. CAPA).

A review of the PR frequency based on the results obtained and provide a recommendation as to whether it remains appropriate (e.g. will the review frequency be kept the same, reduced or increased).

The PR document should be reviewed and approved by the site Quality Authority and System Owner. It may be archived together with the validation files for the system or process.