MCP HubMCP Hub
스킬 목록으로 돌아가기

validate-analytical-method

pjt222
업데이트됨 Yesterday
5 조회
17
2
17
GitHub에서 보기
테스팅design

정보

이 스킬은 ICH Q2(R2) 규제 가이드라인에 따라 크로마토그래피 분석 방법을 검증합니다. 개발자가 검증 범위를 정의하고, 특이성을 확립하며, 직선성, 정확도, 정밀도, 강건성과 같은 중요한 매개변수를 평가하는 데 도움을 줍니다. 규제 제출을 위한 검증 과정을 자동화하고 구조화하는 데 활용하세요.

빠른 설치

Claude Code

추천
기본
npx skills add pjt222/agent-almanac -a claude-code
플러그인 명령대체
/plugin add https://github.com/pjt222/agent-almanac
Git 클론대체
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/validate-analytical-method

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

Validate an Analytical Method

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.

When to Use

  • 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

Inputs

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

Procedure

Step 1: Define Validation Scope per ICH Q2(R2)

Identify the method category and determine which validation parameters are required.

ParameterCat I: AssayCat II: Impurity (Quant)Cat III: Impurity (Limit)Cat IV: Identification
SpecificityYesYesYesYes
LinearityYesYesNoNo
RangeYesYesNoNo
AccuracyYesYesNoNo
Precision (repeatability)YesYesNoNo
Precision (intermediate)YesYesNoNo
LODNoMay be neededYesNo
LOQNoYesNoNo
RobustnessYesYesYesNo
  1. Classify the method into one of the four ICH categories based on its intended purpose.
  2. From the table, identify all required validation parameters.
  3. 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)
  4. Draft a validation protocol documenting all parameters, experimental designs, and acceptance criteria.
  5. Obtain protocol approval (in GMP environments) before beginning experimental work.

Got: Approved validation protocol specifying method category, required parameters, experimental designs, and pre-defined acceptance criteria.

If fail: 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.

Step 2: Establish Specificity and Selectivity

  1. 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)
  2. Perform forced degradation to generate potential degradation products:
Stress ConditionTypical TreatmentTarget Degradation
Acid hydrolysis0.1-1 N HCl, 60-80 C, 1-24 h5-20%
Base hydrolysis0.1-1 N NaOH, 60-80 C, 1-24 h5-20%
Oxidation0.3-3% H2O2, RT-60 C, 1-24 h5-20%
Thermal60-80 C, solid state, 1-7 days5-20%
PhotolyticICH Q1B (1.2M lux-hours, 200 Wh/m^2 UV)5-20%
  1. 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
  2. Calculate mass balance: assay + impurities + degradation products should account for 95-105% of initial content.
  3. Document specificity results with chromatograms from all conditions.

Got: Method demonstrated to be specific: no interferences from blank/placebo, degradation products resolved from analyte, peak purity confirmed, mass balance within 95-105%.

If fail: 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.

Step 3: Determine Linearity and Range

  1. 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)
  2. Prepare each concentration level independently (not by serial dilution) for best practice.
  3. Inject each level in triplicate (minimum duplicate).
  4. 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
  5. 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
  6. Calculate the y-intercept as a percentage of the response at 100% concentration:
    • Intercept should be <= 2% of the 100% response for assay methods
  7. Establish the validated range as the interval between the lowest and highest concentrations for which linearity, accuracy, and precision have been demonstrated.

Got: 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 fail: 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.

Step 4: Assess Accuracy

  1. Prepare accuracy samples at 3 concentration levels (typically 80%, 100%, 120% of target for assay; LOQ, mid, and high for impurity methods).
  2. At each level, prepare 3 independent replicates (minimum 9 determinations total).
  3. For drug substance: compare found concentration to known (gravimetric) amount.
  4. For drug product: use the spiked placebo approach -- add known amounts of analyte to the placebo matrix and measure recovery.
  5. Calculate percent recovery at each level:
    • Recovery (%) = (found amount / added amount) x 100
  6. Acceptance criteria:
Method TypeRecovery RangeRSD 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 validation70-130% (or tighter per company SOP)<= 15%
  1. Report individual recoveries, mean recovery, and RSD at each level.

Got: Mean recovery within acceptance criteria at all concentration levels, with RSD within limits.

If fail: 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.

Step 5: Determine Precision

Evaluate three levels of precision:

  1. 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
  2. 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)
  3. 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 LevelDesignAcceptance (Assay)Acceptance (Impurity Quant)
Repeatabilityn >= 6 at 100%, 1 analyst, 1 dayRSD <= 2.0%RSD <= 10% at LOQ, <= 5% above
Intermediate2 analysts, 2 days (or 2 instruments)RSD <= 3.0%RSD <= 15% at LOQ, <= 10% above
ReproducibilityMulti-laboratoryPer protocol / transfer criteriaPer protocol / transfer criteria

Got: Repeatability and intermediate precision RSDs within acceptance criteria. No statistically significant difference between analysts/days/instruments beyond the allowed RSD.

If fail: 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.

Step 6: Establish LOD, LOQ, and Robustness

Limit of Detection (LOD) and Limit of Quantitation (LOQ):

  1. 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
  2. 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%
  3. Report LOD and LOQ with the method used for determination.

Robustness:

  1. 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)
  2. Vary each parameter deliberately within the specified range while holding others constant (or use a fractional factorial design for efficiency).
  3. Evaluate the impact on system suitability parameters (retention time, resolution, tailing, area).
  4. Parameters that cause system suitability failure within the tested range must be tightly controlled and documented as critical method parameters.
  5. Summarize robustness results in a table showing each varied parameter, the range tested, and the impact on key responses.

Got: LOD and LOQ experimentally confirmed. Robustness study completed with critical method parameters identified and control limits established.

If fail: 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.

Validation

  • 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

Pitfalls

  • 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.

Related Skills

  • develop-gc-method -- GC method development that precedes validation
  • develop-hplc-method -- HPLC method development that precedes validation
  • interpret-chromatogram -- reading chromatograms generated during validation experiments
  • troubleshoot-separation -- resolving issues discovered during validation studies
  • conduct-gxp-audit -- auditing the completed validation for GxP compliance
  • write-standard-operating-procedure -- documenting the validated method as an SOP

GitHub 저장소

pjt222/agent-almanac
경로: i18n/caveman-lite/skills/validate-analytical-method
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

연관 스킬

evaluating-llms-harness

테스팅

이 Claude Skill은 MMLU, GSM8K를 포함한 60개 이상의 표준화된 학술 과제에서 LLM 성능을 벤치마크하기 위해 lm-evaluation-harness를 실행합니다. 개발자들이 모델 품질을 비교하고, 학습 진행 상황을 추적하거나 학술 결과를 보고할 수 있도록 설계되었습니다. 이 도구는 HuggingFace와 vLLM 모델을 포함한 다양한 백엔드를 지원합니다.

스킬 보기

cloudflare-cron-triggers

테스팅

이 스킬은 cron 표현식을 사용하여 Worker를 스케줄링하기 위한 Cloudflare Cron Triggers 구현에 관한 포괄적인 지식을 제공합니다. 주기적 작업, 유지보수 작업, 자동화된 워크플로우 설정 방법을 다루며, 잘못된 cron 표현식이나 시간대 문제 같은 일반적인 이슈들을 해결하는 방법을 포함합니다. 개발자들은 이를 통해 스케줄된 핸들러 구성, cron 트리거 테스트, Workflows 및 Green Compute와의 연동 작업을 수행할 수 있습니다.

스킬 보기

webapp-testing

테스팅

이 Claude Skill은 Python 스크립트를 통해 로컬 웹 애플리케이션을 테스트하기 위한 Playwright 기반 툴킷을 제공합니다. 프론트엔드 검증, UI 디버깅, 스크린샷 캡처, 로그 확인 기능을 지원하며 서버 라이프사이클을 관리합니다. 브라우저 자동화 작업에 사용하되 컨텍스트 오염을 방지하기 위해 소스 코드를 읽지 않고 스크립트를 직접 실행하세요.

스킬 보기

finishing-a-development-branch

테스팅

이 스킬은 테스트 통과를 확인한 후 체계적인 통합 옵션을 제시하여 개발자가 완성된 작업을 마무리하도록 돕습니다. 구현이 완료된 후 머지, PR 생성, 브랜치 정리와 같은 워크플로우를 안내합니다. 코드가 준비되고 테스트가 완료되었을 때 개발 프로세스를 체계적으로 마무리하기 위해 사용하세요.

스킬 보기