validate-analytical-method
About
This skill validates chromatographic analytical methods according to ICH Q2(R2) regulatory guidelines. It helps developers define the validation scope, establish specificity via forced degradation, and assess critical parameters like linearity, accuracy, and precision. Use it to automate and structure the validation process for regulatory submissions.
Quick Install
Claude Code
Recommendednpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/validate-analytical-methodCopy and paste this command in Claude Code to install this skill
Documentation
分析法のバリデーション
Formal validation of a chromatographic analytical method following ICH Q2(R2) guidelines, covering validation scope definition by method category, specificity/selectivity establishment, linearity and range determination, accuracy and precision assessment, and LOD/LOQ and robustness studies for regulatory compliance.
使用タイミング
- A new chromatographic method has been developed and must be validated before routine use
- A compendial method is being verified for suitability in a specific laboratory
- An existing validated method has undergone significant changes requiring partial or full re-validation
- Preparing a validation package for regulatory submission (NDA, ANDA, MAA, IND)
- Transferring a method to a new laboratory or instrument platform
入力
Required
- Developed method: Fully optimized and documented chromatographic method (column, mobile phase, gradient, detector, etc.)
- Method category: Assay of active ingredient, quantitative impurity test, limit test for impurities, or identification test
- Analyte reference standards: Primary reference standards with certificates of analysis and assigned purity
- Sample matrix: Representative samples including placebo/blank matrix for specificity studies
Optional
- Regulatory guidance: Specific regulatory requirements beyond ICH Q2 (e.g., USP <1225>, FDA guidance, EMA guidelines)
- Forced degradation samples: Pre-stressed samples (acid, base, oxidation, heat, light) if not yet prepared
- Validation protocol: Pre-approved protocol specifying acceptance criteria (required in GMP environments)
- Transfer package: If validating as part of a method transfer, the originating lab's validation report
手順
Step 1: Define バリデーション Scope per ICH Q2(R2)
Identify the method category and determine which validation parameters are required.
| Parameter | Cat I: Assay | Cat II: Impurity (Quant) | Cat III: Impurity (Limit) | Cat IV: Identification |
|---|---|---|---|---|
| Specificity | Yes | Yes | Yes | Yes |
| Linearity | Yes | Yes | No | No |
| Range | Yes | Yes | No | No |
| Accuracy | Yes | Yes | No | No |
| Precision (repeatability) | Yes | Yes | No | No |
| Precision (intermediate) | Yes | Yes | No | No |
| LOD | No | May be needed | Yes | No |
| LOQ | No | Yes | No | No |
| Robustness | Yes | Yes | Yes | No |
- Classify the method into one of the four ICH categories based on its intended purpose.
- From the table, identify all required validation parameters.
- Define acceptance criteria for each parameter before beginning experimental work. Typical criteria:
- Linearity: R^2 >= 0.999 (assay), >= 0.99 (impurity)
- Accuracy: recovery 98.0-102.0% (assay), 80-120% at LOQ level
- Repeatability: RSD <= 2.0% (assay), <= 10% at LOQ level
- Intermediate precision: RSD <= 3.0% (assay)
- Draft a validation protocol documenting all parameters, experimental designs, and acceptance criteria.
- Obtain protocol approval (in GMP environments) before beginning experimental work.
期待結果: Approved validation protocol specifying method category, required parameters, experimental designs, and pre-defined acceptance criteria.
失敗時: If the method category is ambiguous (e.g., a combined assay and impurity method), validate for the most stringent category that applies. Consult the regulatory guidance specific to the submission type.
ステップ2: Establish Specificity and Selectivity
- Prepare the following solutions:
- Blank (solvent/diluent only)
- Placebo (matrix without analyte, e.g., excipients for a drug product)
- Reference standard at working concentration
- Spiked placebo (matrix + reference standard)
- Forced degradation samples (if not already available)
- Perform forced degradation to generate potential degradation products:
| Stress Condition | Typical Treatment | Target Degradation |
|---|---|---|
| Acid hydrolysis | 0.1-1 N HCl, 60-80 C, 1-24 h | 5-20% |
| Base hydrolysis | 0.1-1 N NaOH, 60-80 C, 1-24 h | 5-20% |
| Oxidation | 0.3-3% H2O2, RT-60 C, 1-24 h | 5-20% |
| Thermal | 60-80 C, solid state, 1-7 days | 5-20% |
| Photolytic | ICH Q1B (1.2M lux-hours, 200 Wh/m^2 UV) | 5-20% |
- Inject all solutions and evaluate:
- No interfering peaks from blank or placebo at analyte retention time
- Degradation products resolved from the main analyte peak (Rs >= 1.5)
- Peak purity confirmed by DAD spectral purity index or MS
- Calculate mass balance: assay + impurities + degradation products should account for 95-105% of initial content.
- Document specificity results with chromatograms from all conditions.
期待結果: Method demonstrated to be specific: no interferences from blank/placebo, degradation products resolved from analyte, peak purity confirmed, mass balance within 95-105%.
失敗時: If degradation products co-elute with the analyte, the method is not stability-indicating. Return to method development to improve selectivity (adjust pH, gradient, column chemistry) before proceeding with validation.
ステップ3: Determine Linearity and Range
- Prepare at least 5 concentration levels spanning the intended range:
- Assay methods: typically 80-120% of the target concentration
- Impurity methods: from LOQ to 120-200% of the specification limit
- Dissolution: from 10-120% of the label claim (or as needed for the dissolution profile)
- Prepare each concentration level independently (not by serial dilution) for best practice.
- Inject each level in triplicate (minimum duplicate).
- Perform linear regression of response (area or height) vs. concentration:
- Report slope, intercept, and correlation coefficient (R^2)
- R^2 >= 0.999 for assay; R^2 >= 0.99 for impurity quantitation
- Evaluate residual plots:
- Residuals should be randomly distributed around zero with no systematic pattern
- A curved residual pattern indicates non-linearity -- consider a quadratic fit or narrower range
- Calculate the y-intercept as a percentage of the response at 100% concentration:
- Intercept should be <= 2% of the 100% response for assay methods
- Establish the validated range as the interval between the lowest and highest concentrations for which linearity, accuracy, and precision have been demonstrated.
期待結果: Linear regression with R^2 >= 0.999 (assay) or >= 0.99 (impurity), random residual distribution, intercept <= 2% of target response, and validated range clearly defined.
失敗時: If R^2 is below the criterion, check for preparation errors, detector non-linearity (too high concentration), or analyte instability. Repeat with fresh preparations. If non-linearity is inherent, use a polynomial calibration or narrow the range.
ステップ4: Assess Accuracy
- Prepare accuracy samples at 3 concentration levels (typically 80%, 100%, 120% of target for assay; LOQ, mid, and high for impurity methods).
- At each level, prepare 3 independent replicates (minimum 9 determinations total).
- For drug substance: compare found concentration to known (gravimetric) amount.
- For drug product: use the spiked placebo approach -- add known amounts of analyte to the placebo matrix and measure recovery.
- Calculate percent recovery at each level:
- Recovery (%) = (found amount / added amount) x 100
- Acceptance criteria:
| Method Type | Recovery Range | RSD at Each Level |
|---|---|---|
| Assay (drug substance) | 98.0-102.0% | <= 2.0% |
| Assay (drug product) | 98.0-102.0% | <= 2.0% |
| Impurity (quantitation) | 80-120% at LOQ, 90-110% at higher levels | <= 10% at LOQ, <= 5% at higher |
| Cleaning validation | 70-130% (or tighter per company SOP) | <= 15% |
- Report individual recoveries, mean recovery, and RSD at each level.
期待結果: Mean recovery within acceptance criteria at all concentration levels, with RSD within limits.
失敗時: If recovery is consistently high or low across all levels, suspect a systematic error in the reference standard, sample preparation, or method (e.g., matrix effect causing ion suppression in LC-MS). If recovery varies erratically, investigate sample preparation technique and analyte stability.
ステップ5: Determine Precision
Evaluate three levels of precision:
- Repeatability (intra-day):
- One analyst, one instrument, one day
- Inject 6 determinations at 100% or 3 levels x 3 replicates (same data as accuracy)
- Calculate RSD of results: <= 2.0% for assay, <= 10% at LOQ for impurity
- Intermediate precision (inter-day / inter-analyst):
- Repeat the repeatability study with a different analyst, different day, and (if available) different instrument
- Calculate overall RSD combining both data sets
- Overall RSD <= 3.0% for assay
- If intermediate precision is significantly worse than repeatability, investigate the source of variation (analyst technique, instrument calibration, environmental conditions)
- Reproducibility (for method transfer or multi-site validation):
- Performed at the receiving laboratory following the same protocol
- Compare results between laboratories
- Evaluated by F-test (variance comparison) and t-test (mean comparison) or equivalence testing
| Precision Level | Design | Acceptance (Assay) | Acceptance (Impurity Quant) |
|---|---|---|---|
| Repeatability | n >= 6 at 100%, 1 analyst, 1 day | RSD <= 2.0% | RSD <= 10% at LOQ, <= 5% above |
| Intermediate | 2 analysts, 2 days (or 2 instruments) | RSD <= 3.0% | RSD <= 15% at LOQ, <= 10% above |
| Reproducibility | Multi-laboratory | Per protocol / transfer criteria | Per protocol / transfer criteria |
期待結果: Repeatability and intermediate precision RSDs within acceptance criteria. No statistically significant difference between analysts/days/instruments beyond the allowed RSD.
失敗時: If intermediate precision is much worse than repeatability, identify the variable driving the additional variance (analyst preparation technique, ambient temperature, instrument calibration drift) and control it before repeating.
ステップ6: Establish LOD, LOQ, and Robustness
Limit of Detection (LOD) and Limit of Quantitation (LOQ):
- Calculate LOD and LOQ using the signal-to-noise approach or the standard deviation approach:
- LOD = 3.3 x (sigma / S) where sigma = standard deviation of response at low concentration, S = slope of calibration
- LOQ = 10 x (sigma / S)
- Alternative: S/N approach -- LOD corresponds to S/N >= 3, LOQ to S/N >= 10
- Confirm experimentally: prepare solutions at the calculated LOD and LOQ concentrations and inject.
- At LOD: the peak should be detectable but not necessarily quantifiable with acceptable precision
- At LOQ: inject 6 replicates and confirm RSD <= 10% and accuracy within 80-120%
- Report LOD and LOQ with the method used for determination.
Robustness:
- Identify critical method parameters (typically 5-7 factors):
- Mobile phase composition (+/- 2% organic)
- Mobile phase pH (+/- 0.2 units)
- Column temperature (+/- 5 C)
- Flow rate (+/- 10%)
- Detection wavelength (+/- 2 nm)
- Column lot/batch (if available)
- Vary each parameter deliberately within the specified range while holding others constant (or use a fractional factorial design for efficiency).
- Evaluate the impact on system suitability parameters (retention time, resolution, tailing, area).
- Parameters that cause system suitability failure within the tested range must be tightly controlled and documented as critical method parameters.
- Summarize robustness results in a table showing each varied parameter, the range tested, and the impact on key responses.
期待結果: LOD and LOQ experimentally confirmed. Robustness study completed with critical method parameters identified and control limits established.
失敗時: If LOQ precision exceeds 10% RSD, the method sensitivity is insufficient at that concentration. Options: increase injection volume, concentrate the sample, improve sample cleanup, or use a more sensitive detector. If a parameter shows the method is not robust (fails SST with small deliberate variation), tighten the control of that parameter in the method and flag it during method transfer.
バリデーション
- Method category identified and all required parameters determined per ICH Q2(R2)
- Validation protocol written with pre-defined acceptance criteria
- Specificity demonstrated: no interferences, degradation products resolved, peak purity confirmed
- Mass balance within 95-105% for forced degradation study
- Linearity established with R^2 >= 0.999 (assay) or >= 0.99 (impurity), residuals random
- Accuracy demonstrated at 3 levels with recovery within acceptance criteria
- Repeatability RSD within limits (e.g., <= 2.0% for assay)
- Intermediate precision RSD within limits (e.g., <= 3.0% for assay)
- LOD and LOQ experimentally confirmed (LOQ precision <= 10% RSD)
- Robustness study completed with critical method parameters identified
- All raw data, calculations, and chromatograms compiled into the validation report
よくある落とし穴
- Starting experiments before protocol approval: In GMP environments, validation data generated before protocol approval may not be acceptable to regulators. Always obtain approval first.
- Using serial dilutions for linearity: Serial dilutions propagate pipetting errors. Prepare each concentration level independently from a common stock for the most accurate linearity assessment.
- Insufficient forced degradation: Generating too little degradation (< 5%) may miss important degradation products. Generating too much (> 30%) produces secondary degradation products that complicate interpretation. Target 5-20% degradation per condition.
- Confusing repeatability with intermediate precision: Repeatability is same-day, same-analyst, same-instrument. Intermediate precision must vary at least one of these factors. Both are required for Category I and II methods.
- Neglecting the LOQ verification step: Calculating LOQ from the calibration curve is not sufficient. The calculated LOQ must be experimentally confirmed by demonstrating acceptable precision and accuracy at that concentration.
- Omitting robustness until late in validation: Discovering that the method is not robust after accuracy and precision studies wastes time and materials. Perform a quick robustness screen early in validation to catch fragile parameters.
- Incomplete validation reports: Regulatory reviewers expect to see all raw data, chromatograms (not just tabulated numbers), statistical analysis, and explicit pass/fail conclusions for each parameter. Missing data leads to deficiency letters.
関連スキル
develop-gc-method-- GC method development that precedes validationdevelop-hplc-method-- HPLC method development that precedes validationinterpret-chromatogram-- reading chromatograms generated during validation experimentstroubleshoot-separation-- resolving issues discovered during validation studiesconduct-gxp-audit-- auditing the completed validation for GxP compliancewrite-standard-operating-procedure-- documenting the validated method as an SOP
GitHub Repository
Related Skills
evaluating-llms-harness
TestingThis Claude Skill runs the lm-evaluation-harness to benchmark LLMs across 60+ standardized academic tasks like MMLU and GSM8K. It's designed for developers to compare model quality, track training progress, or report academic results. The tool supports various backends including HuggingFace and vLLM models.
cloudflare-cron-triggers
TestingThis skill provides comprehensive knowledge for implementing Cloudflare Cron Triggers to schedule Workers using cron expressions. It covers setting up periodic tasks, maintenance jobs, and automated workflows while handling common issues like invalid cron expressions and timezone problems. Developers can use it for configuring scheduled handlers, testing cron triggers, and integrating with Workflows and Green Compute.
webapp-testing
TestingThis Claude Skill provides a Playwright-based toolkit for testing local web applications through Python scripts. It enables frontend verification, UI debugging, screenshot capture, and log viewing while managing server lifecycles. Use it for browser automation tasks but run scripts directly rather than reading their source code to avoid context pollution.
finishing-a-development-branch
TestingThis skill helps developers complete finished work by verifying tests pass and then presenting structured integration options. It guides the workflow for merging, creating PRs, or cleaning up branches after implementation is done. Use it when your code is ready and tested to systematically finalize the development process.
