Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/stage-bluereg/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the all-in-one-wp-security-and-firewall domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/stage-bluereg/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the lazy-load-for-videos domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/stage-bluereg/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-migrate-db domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/stage-bluereg/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpcf7-redirect domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/stage-bluereg/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the insert-headers-and-footers domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/stage-bluereg/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the all-in-one-wp-security-and-firewall domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/stage-bluereg/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/stage-bluereg/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the polylang domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/stage-bluereg/wp-includes/functions.php on line 6131
Product Quality Review - BlueReg Group

Product Quality Review

Blue Reg has an experienced team for Product Quality Review (PQR) writing including CMC, Quality and Regulatory Affairs consultants dedicated to supporting your company through PQR reviews for your medicinal products.

From data gathering, through data analysis and PQR writing, we provide flexible solutions to meet your company’s requirements.

Our services

PQR is a regulatory requirement (EU-GMP chap 8, US 21 CFR part211, and ICHQ7A) and an effective quality improvement tool to verify the consistency of the existing process and overall quality of the product, to be conducted annually. These PQRs are assessed thoroughly by inspectors during Health authority inspections and should be carefully managed by trained and knowledgeable staff.

 

BlueReg can fully support you to set up the PQR process in your company and/or manage your annual reviews. Our experienced team utilize the following approach which can be tailored to your specific needs:

Data Gathering

  • Manufacturer PQR
  • Local data (variations, deviations, contracts, complaints and recalls)

Data Analysis

  • Compliance to GMP requirements
  • Critical review of batch data evaluation performed by the manufacturer
  • Evaluation of the overall quality of the product
  • Assessment of the consistency of the existing manufacturing process
  • Highlight of any trends
  • Review of the proposed CAPAs, highlighting action plans to be monitored or added
  • Verification of the consistency between local data and information provided by the manufacturer

Writing the PQR for the « Exploitant »

  • Writing in accordance with the client or BlueReg template
  • Assessing manufacturing results and setting conclusions on process control
  • Providing a global assessment on the local data and the evaluation undertaken by the manufacturer