When testing regulated products such as Pharmaceuticals (Prescription and Over-the-counter), Medical Devices, Dietary Supplements or even Cosmetics, the test methods employed must meet certain performance requirements or the results obtained from using the methods will not be accepted by regulatory agencies such as FDA. The way to determine the reliability of an analytical method is to conduct a Method Validation. It should be noted that Method Validation, Method Verification and Method Transfer apply not only to the testing of regulated products, but also to the testing of the ingredients of which regulated products are comprised, and the containers in which they are distributed.

What is Method Validation?

The United States Pharmacopeia (USP) defines method validation as a process by which it is established, through laboratory studies, that the performance characteristics of a method meet the requirements for its intended analytical applications. The USP goes on to state that Method Validation typically evaluates the following analytical characteristics of a method: Accuracy, Precision,
Specificity, Detection Limit, Quantitation Limit, Linearity, Range and Robustness. Depending upon the type of method and its application, not all the analytical characteristics indicated above will be required for validation.

Accuracy refers to the closeness of test results obtained from an analytical method to the true value. The accuracy of a method must be determined across its range of application.

Precision is defined as the degree of agreement among individual test results when the method is applied repeatedly to multiple samplings of a homogenous sample.

Specificity is the ability of a method to assess unequivocally, the analyte in the presence of components expected to be present such as impurities, degradation products, other ingredients and other possible matrix interferences.

Detection Limit is a characteristic applied to Limit Tests, and refers to the lowest amount of analyte in a sample that can be detected, but not necessarily quantitated.

Quantitation Limit is a characteristic of quantitative assays for low levels of compounds in sample matrices, such as impurities and degradation products. It is the lowest amount of analyte in a sample that can be determined by the method with acceptable precision and accuracy.

Linearity is the ability of a method to generate results that are directly proportional to the concentration of analyte in samples across the method’s range of application.

Range of an analytical method is defined as the interval between the upper and lower levels of analyte that yield suitable Precision, Accuracy and Linearity.

Robustness is a measure of a method’s capacity to remain unaffected by small but deliberate variations in procedural parameters.

Specific details regarding method validation may be found in USP General Chapter <1225> entitled “Validation of Compendial Procedures”.

Must USP Methods be Validated?

There is no general requirement that USP methods be validated, since they were successfully validated prior to their inclusion within the USP. It is required, however that the suitability of USP methods be determined under actual conditions of use, i.e., for the specific sample to be tested and by the laboratory doing the testing. USP methods, and Compendial methods in general (e.g., BP, and EP) must be verified.


What is Method Verification?

The USP defines method verification as an assessment whether a Compendial method is suitable under actual conditions of use. USP requires that a method verification be conducted the first time that a laboratory employs a Compendial method for testing a specific sample type. Thus, method verification is specific to the laboratory performing the testing and to the sample type being tested.

Keeping this in mind, if a laboratory has successfully verified a specific method for a specific sample type, but a new sample type is submitted to that lab for testing, it would trigger the need to reconduct method verification for the new sample type. Applying the same logic, if a method verification has been successfully conducted by a laboratory, but the same sample type is sent to a different lab for testing but employing the same method, this too would trigger the need to conduct method verification since this would be the new lab’s first usage of the method.

Strategies for conducting Method Verification can vary greatly, depending upon the nature of the method and of the sample type. One element of Method Verification that must always be performed, however is the determination of method specificity with regard to the sample type being tested. This is important since USP methods are typically developed and validated for only a single sample type. Specificity activities will determine if any interferences, positive or negative, exist when the method is applied to the specific sample type to be tested.

Specific details regarding method verification may be found in USP General Chapter <1226> entitled “Verification of Compendial Procedures.”

What is Method Transfer?

Method Transfer refers to the transferring of a previously validated, non-Compendial method to a different laboratory for use in testing the same sample type. Method Transfer consists of laboratory studies designed to assess the ability of a “receiving” laboratory (i.e., the lab “into which” a method is being transferred) to apply the method to obtain results which closely correlate with those generated by the “sending” laboratory (i.e., the lab “from which” the method is being transferred). Although differing strategies for conducting Method Transfer may be employed, the simplest and most common strategy is to have the “sending” and “receiving” laboratories each conduct replicate testing of the same homogenous sample, and assess the correlation of test results within each lab and between labs.

It should be noted that Method Transfer applies only to previously validated, non-compendial methods. If a compendial method is transferred into a new laboratory, this would trigger the need for conducting a Method Verification and not a Method Transfer.