(NORMA) Request For Quality Metrics
(NORMA) Request For Quality Metrics
Draft Guidance for Industry Request for Quality Metrics, published July 28,
2015
For questions regarding this technical specifications document, contact (CDER) Tara Gooen
Bizjak at 301-796-3257 or (CBER) Office of Communication, Outreach and Development at 1-
800-835-4709 or 240-402-8010.
Revision History
TABLE OF CONTENTS
4.2.22 Annual Product Review (APR) / Product Quality Review (PQR) Required........................ 6
4.2.23 DUNS Number.......................................................................................................................... 6
4.2.24 Dosage Form ........................................................................................................................ 6
4.2.25 Facility Establishment Inventory Number (FEI) ................................................................. 6
4.2.26 Establishment Activity Classification ................................................................................... 6
4.3 Mandatory Data Elements – Formats ............................................................................... 6
4.4.1 APR Approval ............................................................................................................................. 8
4.4.3 Percentage of Corrective Actions and Preventive Actions (CAPA) Involving Re-training ..... 8
4.4.4 Process Capability (PC) or Process Performance (PP) Index Calculation .............................. 8
4.4.5 CAPA Trigger Policy .................................................................................................................. 8
4.4.6 Triggers for CAPA...................................................................................................................... 8
4.5 Optional Data Elements – Formats ................................................................................... 9
5.0 DATA VALIDATION RULES .............................................................................................. 9
6.0 GLOSSARY........................................................................................................................... 10
Contains Nonbinding Recommendations
Draft — Not for Implementation
1. INTRODUCTION
1.1 Background
This Quality Metrics Technical Conformance Guide (Guide) serves as the technical reference for
implementation of the draft FDA guidance for industry on Request for Quality Metrics. 1 Since
publication of the Pharmaceutical CGMPs for the 21st Century in 2004, 2 CDER has continued to
promote its vision of “a maximally efficient, agile, flexible manufacturing sector that reliably
produces high-quality drug products without extensive regulatory oversight.” The draft guidance
for industry on Request for Quality Metrics and this technical reference document continue
FDA’s policy efforts to ensure successful implementation of CDER’s objectives outlined in the
21st Century publication. FDA expects that quality metrics calculated from data that it collects
will provide objective measures that, when used with additional internal data, will provide the
Agency with indicators of the effectiveness of pharmaceutical manufacturing quality systems.
The goal of these measures is to assure quality drug products are available to patients. The
objectives of CDER’s quality metrics program can best be achieved through collaboration and a
shared understanding of standards for metric indicators and data exchange/reporting.
This Guide supplements the draft FDA guidance for industry on Request for Quality Metrics and
provides recommendations about submission of information that will support the FDA’s
calculation of quality metrics.
1.2 Purpose
This Guide provides technical recommendations for the submission of quality metric data. It is
intended to ensure clear expectations for industry on the submission of quality metric data as
described in the Request for Quality Metrics draft guidance.
1
See http://www.fda.gov/ucm/groups/fdagov-public/@fdagov-drugs-gen/documents/document/ucm455957.pdf.
We update guidances periodically. To make sure you have the most recent version of a guidance, check the FDA
Drugs guidance Web page at
http://www.fda.gov/Drugs/GuidanceComplianceRegulatoryInformation/Guidances/ucm310704.htm.
2
See Pharmaceutical cGMP’s for the 21st Century: A Risk- Based Approach at
http://www.fda.gov/Drugs/DevelopmentApprovalProcess/Manufacturing/QuestionsandAnswersonCurrentGoodMan
ufacturingPracticescGMPforDrugs/ucm137175.htm.
1
Contains Nonbinding Recommendations
Draft — Not for Implementation
This document is incorporated by reference into the draft FDA guidance for industry on Request
for Quality Metrics. Please refer to the draft guidance at
http://www.fda.gov/downloads/Drugs/GuidanceComplianceRegulatoryInformation/Guidances/U
CM455957.pdf for ongoing changes to the guidance or submission processes before final
adoption.
For resources on data standards, please also refer to the Study Data Technical Conformance
Guide located on the FDA Study Standards Resources Web page at
http://www.fda.gov/forindustry/datastandards/studydatastandards/default.htm.
Currently, FDA receives, processes, and archives electronic dataset files in several formats. The
FDA is committed to open dialog about best practices which includes a review of various
formats. Extensible Markup Language (XML) shall be the recommended format for Drug
Quality Metrics submission.
Extensible Mark-up Language (XML), as defined by the World Wide Web Consortium (W3C),
specifies a set of rules for encoding documents in a format that is both human-readable and
machine-readable. 3 XML’s primary purpose is to facilitate the sharing of structured data across
different information systems.
The length of variable names, descriptive labels, and dataset labels should not exceed the
maximum permissible number of characters described in Table 1:
2
Contains Nonbinding Recommendations
Draft — Not for Implementation
Variable names, as well as variable and dataset labels, should include only American Standard
Code for Information Interchange (ASCII) text codes.
Variable and dataset names should not contain punctuation, dashes, spaces, or other non-
alphanumeric symbols. In addition, the variable and dataset names should not contain special
characters, including:
\ / * ,? < > | “ ‘ : % # + ( ) { } [ ]
Variable and dataset labels can include punctuation characters. However, special characters
should not be used, such as:
The data definition file is a human and machine-readable dataset that contains a list of the
datasets included in the submission along with a detailed description (i.e., metadata) of the
contents of each data set.
Below are product data elements which correlate to column product names described in
Appendix-A of the draft FDA guidance for industry on Request for Quality Metrics.
For drugs that are subject to approved applications under section 505 of the FD&C Act or under
section 351 of the PHS Act, and for drugs that are described in a drug master file (DMF) that is
intended to support an application, the API/drug substance or FDF/drug product name provided
in the application should be used.
3
Contains Nonbinding Recommendations
Draft — Not for Implementation
For drugs that are not subject to an approved application under section 505 of the FD&C Act or
under section 351 of the PHS Act, the API or FDF drug product name should be used. If the drug
product name is included as part of registration, the same name included in registration should be
used.
Indicate if the drug referenced in the completed data table is prescription (Rx) or over-the-
counter (OTC). This element is not required to be reported for an API intended for use in the
manufacture of a drug product.
The applicable monograph, if any, for the drug referenced. This element is not required to be
reported for products that are subject to an application under either section 505 of the FD&C Act
or under section 351 of the PHS Act, or covered by a submission to a DMF that is intended to
support such an application.
The drug product type – Active Pharmaceutical Ingredient (API) or Finished Dosage Form
(FDF). This field is restricted to two options; only one option can be selected.
The name of the labeler listed in the NDC code (for validation of text entered as “final labeler
name”).
The application type is New Drug Application (NDA), Abbreviated NDA (ANDA), Biologics
License Application (BLA), Drug Master File (DMF), or Non-application product (NA).
The NDA, ANDA, BLA number for an approved product or the applicable DMF number. Leave
blank for non-application products.
4
Contains Nonbinding Recommendations
Draft — Not for Implementation
The beginning of the time period within which the data being reported were collected.
The end of the time period within which the data being reported were collected.
The number of lots attempted for the drug referenced above in 4.2.1 for each establishment. 4
The number of specification-related lots rejected for the drug referenced above in 4.2.1 for each
establishment.
The number of lots attempted pending disposition for more than 30 days on the last day of the
time period within which the data being reported was collected.
The number of test results that fall outside the specifications or acceptance criteria for the drug
referenced above in 4.2.1 for each establishment.
The number of lot release and stability tests conducted for the drug referenced above in 4.2.1 for
each establishment.
The number of invalidated OOS results for finished drug product or API and stability tests due to
laboratory error for the drug referenced above in 4.2.1 for each establishment.
4
In this section of the guidance, “establishment” means “covered establishment” as defined in the FDA guidance for
industry on Request for Quality Metrics.
5
Contains Nonbinding Recommendations
Draft — Not for Implementation
The sum of product quality complaints received for product distributed in the United States for
the drug product referenced above in 4.2.1 across all establishments.
The number of lots attempted which are released for distribution or for the next stage of
manufacturing for the finished drug product or API referenced above in 4.2.1 for each
establishment.
4.2.21 Annual Product Review (APR) / Product Quality Review (PQR) Completed
Indication (yes/no) of whether the APR or PQR was performed within 30 days of the annual due
date.
4.2.22 Annual Product Review (APR) / Product Quality Review (PQR) Required
The DUNS number for each establishment listed in the quality metrics data submission.
The dosage form for the drug product referenced above in 4.2.1.
The FEI for each establishment listed in the quality metrics data submission.
List the activity classification (e.g., Direct Product Manufacturing) for all establishments listed in
the quality metrics data submission.
6
Contains Nonbinding Recommendations
Draft — Not for Implementation
7
Contains Nonbinding Recommendations
Draft — Not for Implementation
Indicate Yes/No to indicate whether each associated APR/PQR was reviewed and approved.
If response to 4.4.1 is Y, indicate whether the approving entity was: 1. Head of the quality unit;
2. Head of the operations unit; 3. Both; or 4. Other.
4.4.3 Percentage of Corrective Actions and Preventive Actions (CAPA) Involving Re-
training
Indicate the estimated percentage of your corrective actions plans that involved re-training of
personnel (i.e., a root cause of the deviation is lack of adequate training).
Indicate Yes/No if PC or PP Index was calculated for each critical quality attribute as part of that
product’s APR or PQR.
Indicate Yes/No if establishment management has a policy requiring CAPA at some lower
process capability or performance index.
8
Contains Nonbinding Recommendations
Draft — Not for Implementation
When the FDA guidance for industry on Request for Quality Metrics is published in final, the
validation rules will be posted to the external FDA Web page. Establishments should validate
their metric data before submission using the posted validation rules and correct any validation
errors.
9
Contains Nonbinding Recommendations
Draft — Not for Implementation
6.0 Glossary
The following is a list of acronyms and terms used in this technical specifications document:
10