analytical-method-validation

Files (17)

• SKILL.md
• validation-protocol-template.md · assets/
• validation-report-template.md · assets/
• compendial-and-clsi.md · references/
• framework-selection.md · references/
• ich-m10-bioanalytical.md · references/
• ich-q2r2.md · references/
• source-ledger.md · references/
• statistics.md · references/
• _catalog.py · scripts/
• _common.py · scripts/
• check_accuracy_precision.py · scripts/
• check_bioanalytical_run.py · scripts/
• check_detection_limits.py · scripts/
• check_response.py · scripts/
• compare_methods.py · scripts/
• plan_validation.py · scripts/

SKILL.md (first lines)

# Analytical Method Validation

## When to use

Any time the question is whether an analytical procedure is fit for its intended purpose:
designing a validation study, evaluating validation data, verifying a compendial procedure,
transferring a procedure to another laboratory or instrument, or defending any of these in a
report.

## The two rules

**1. Establish which framework governs before designing anything.** The same assay validates
differently under ICH Q2(R2), USP <1225>, ICH M10, CLSI EP, and ISO/IEC 17025. They differ in
which characteristics are required, how the studies are laid out, and whether numeric acceptance
criteria are supplied at all. Blending them produces a protocol that satisfies none of them.

**2. State acceptance criteria before collecting data.** Criteria chosen after seeing results are
not acceptance criteria, and deciding them post hoc is a standing audit finding. ICH Q2(R2)
deliberately supplies almost no numeric criteria — they have to come from the specification, the
analytical target profile (ICH Q14 section 3), or development data. ICH M10 is the exception: it
supplies explicit numbers, and they differ between chromatographic assays and ligand binding
assays.

## Scope

This skill plans studies, computes the statistics correctly, and structures the documentation. It
does **not** decide that a procedure is validated, release a batch, accept or reject a run, close
an investigation, or substitute for the analyst, the technical reviewer, the quality unit, or the
regulator. Every script reports; none of them concludes.

## Copyright boundary

ICH guidelines are published openly and licensed for reuse with acknowledgement, so their
requirements are encoded directly in this skill. **USP general chapters, CLSI EP documents, and
ISO standards are copyrighted and paywalled.** For those, this skill supplies the designation,
scope, and where to obtain an authorised copy — never the text, never invented thresholds. Do not
ask an agent to retrieve, transcribe, or reconstruct their content. If a number matters and it
lives in a paywalled document, read it from the authorised copy.

## Frameworks

```bash
cd skills/analytical-method-validation/scripts
python3 plan_validation.py --list-frameworks
```

| Key | Governs | Numeric criteria supplied |
| --- | --- | --- |
| `ich-q2r2` | Release and stability testing of drug substances and products | Almost none — you derive them |
| `ich-m10` | Bioanalytical concentration measurement (PK, TK, BE) | Yes, and they differ by modality |
| `usp-1220` | Compendial procedure lifecycle, three stages | Paywalled |
| `usp-1225` / `usp-1226` | Validation / verification of compendial procedures | Paywalled |
| `clsi` | Clinical laboratory measurement procedures (EP series) | Paywalled |
| `iso-17025` | Lab-developed and modified methods under accreditation | No — "to the extent necessary" |

**Q2(R2) replaced Q2(R1) in November 2023 and restructured the characteristics.** Range is now
the parent characteristic (section 3.2), containing *response* (linearity) and *validation of
lower range limits* (DL/QL). Accuracy and precision are section 3.3 and may be evaluated in
combination against a single criterion. Robustness is treated as a development activity and
cross-refers to ICH Q14. Multivariate procedures are addressed explicitly (2.5 and 3.2.2.3), and
Annex 2 adds worked examples for techniques Q2(R1) never covered — quantitative ¹H-NMR, NIR,
quantitative LC/MS, qPCR, biological assays, and particle size. A Q2(R1)-shaped protocol — a flat
list of linearity, range, accuracy, precision, specificity, LOD, LOQ, robustness — is out of date.
Note also the error correction dated 30 November 2023 to Table 5 and Tables 6–11.

## Scripts

```bash
cd skills/analytical-method-validation/scripts
```

| Script | Question answered |
| --- | --- |
| `plan_validation.py` | Which framework, which characteristics, what study layout, what protocol? |
| `check_response.py` | Does the calibration model actually hold across the range? |
| `check_accuracy_precision.py` | What is the recovery, and how much of the variability is between days? |
| `check_detection_limits.py` | What are DL and QL by each allowed approach, and do they serve the reporting threshold? |
| `check_bioanalytical_run.py` | Does this run meet ICH M10 for its modality? |
| `compare_methods.py` | Are two procedures equivalent, at a pre-stated margin? |

All take `--format table|tsv|json`. Provenance, guideline citations, and caveats go to stderr;
data goes to stdout, so `> out.tsv` keeps them separate. Exit code is `0` for no findings, `1`
when findings were raised, `2` for bad input — so any of them can gate a workflow.

## Workflow

### 1. Fix the framework and the required characteristics

```bash
python3 plan_validation.py --framework ich-q2r2 --attribute assay --technique hplc --range-use assay
```

Q2(R2) Table 1 decides what is required from the *measured attribute*, not from the technique. For
an assay: specificity, response, accuracy, repeatability, intermediate precision. For a limit
test: specificity and DL only. For an identity test: specificity alone. Attributes accepted include
`assay`, `impurity` (quantitative), `impurity-limit`, and `identity`.

Reportable range comes from the specification. Q2(R2) Table 2 gives worked examples — 80–120% of
declared content for an assay, 70–130% for content uniformity, reporting threshold to 120% of the
specification for an impurity.

### 2. Generate the protocol and fill in the criteria

```bash
python3 plan_validation.py --framework ich-q2r2 --attribute impurity --protocol > protocol.md
```

Every bracketed field is a decision to make and record *before* data collection. The protocol
skeleton deliberately refuses to pre-fill acceptance criteria for Q2(R2) work, because there is no
defensible default.

### 3. Evaluate the response

```bash
python3 check_response.py -i calibration.csv --max-back-calc-error 2
```

Input is `level,response`, one row per injection; repeated rows at the same level are replicates,
and supplying them is what makes the linearity test possible.

From nikhilesh-s/claude-toolkit, MIT.

More from nikhilesh-s/claude-toolkit