claude nmr · ai nmr analysis
Claude for NMR and LC-MS Analysis Validation: Protocol Guide
October 31, 2026
30 min read
A 2026 validation protocol for Claude in NMR and LC-MS: separates forward prediction, elucidation, raw FID and LC-MS purity, using Anthropic's 20-compound and one-sample results, ICH Q2(R2) and draft Annex 22.

- 01Forward NMR prediction, inverse structure elucidation, raw NMR processing, and LC-MS processing with purity calculation are separate tasks. Evidence for one should not validate another.
- 02The June benchmark reports favorable mean errors on small samples. Raw NMR and LC-MS processing each have one documented sample, without public replicate statistics.
- 03Claude's headline purity and the laboratory's purity use different peak sets. A laboratory should define wavelength, start time, peak list, and void-peak treatment before comparing results.
- 04Each task needs its own intended-use statement, blinded reference set, replicate design, metrics, and stop conditions. Pin model identifiers, reconcile raw-file parsing, and document qualified human review.
- 05The evidence most directly supports low-consequence, expert-reviewed assistance. It does not support unreviewed identity, purity, or release statements, and acceptance thresholds belong to each laboratory.
Executive Summary
Anthropic published two sets of results in 2026 that are often discussed together as "Claude for NMR" but support four different claims: forward nuclear magnetic resonance (NMR) prediction, inverse structure elucidation, raw NMR file processing, and liquid chromatography-mass spectrometry (LC-MS) processing with a purity calculation. The June 5, 2026 white paper assessed Claude Opus 4.7 against ChemDraw 25.0.2 and MestReNova 17.0.0 ([1]), using 20 forward-prediction compounds and 15 elucidation problems ([2]). The August 18, 2026 report followed one routine quality-control sample from a contract research organization through Claude Opus 5 ([3]).
The June numbers are favorable but small. Opus 4.7 posted a mean 1H error of 0.079 ppm, the lowest of any tool tested ([4]), and on 13C it was comparable with MestReNova at 1.37 and 1.48 ppm ([5]). It recovered all eight simpler inverse problems on every attempt ([6]). Anthropic itself calls the results indicative rather than precise and excludes 2D experiments and stereochemistry ([7]). The August workflow returned processed NMR and LC-MS results in 23 and 19 minutes ([8]), with a purity of 96.4% against the laboratory's 96.33% ([9]). The technical report shows those two figures rest on different peak sets: three peaks for Claude and seven for the laboratory ([10]) ([11]).
No regulator has published a validation standard for this use. The usable anchors are the International Council for Harmonisation (ICH) Q2(R2) principle that a procedure must be fit for its intended purpose ([12]), the validation requirement in 21 CFR Part 11 ([13]), and the draft EU GMP Annex 22, which as drafted does not apply to generative AI and large language models. EMA said in mid-2026 that it was still weighing consultation results ([14]).
This report proposes a four-task pilot protocol: a written intended-use statement per task, a blinded post-cutoff reference set, replicate runs with pinned model identifiers, peak-level error metrics, top-k tables, raw-file checksums with reconciliation, and named human review. It sets no universal acceptance thresholds, because those belong to each laboratory's own risk assessment. Nothing here suggests an AI result establishes identity, purity, release, or GMP suitability. All performance figures are vendor research on small samples.
Mean proton prediction error for Opus 4.7 in the June benchmark
Compounds in the forward-prediction benchmark
Problems in the inverse-elucidation benchmark
Claude's headline purity, based on three detected peaks including the void peak
Introduction and Background
Searches for "Claude NMR" bundle analytical jobs that differ in input, reference method, and consequence of error. A chemist who pastes a SMILES string (a line-text structure notation) and asks for a predicted 1H spectrum is doing a different task from an analyst who uploads a raw free induction decay (FID, the time-domain signal an NMR spectrometer records) and asks for an integrated peak table. Both differ again from asking a model to read a vendor LC-MS binary and report area-percent purity.
This report examines how a laboratory can convert the 2026 results into a pilot. It is written for medicinal and process chemists, analytical development leaders, chemistry informatics teams, lab automation owners, research IT, and quality partners. The perspective is that of an adjacent advisor: IntuitionLabs is a life-sciences and AI consultancy, not a vendor of NMR, LC-MS, or AI software, and has no product in the comparisons below. The report does not claim that Claude replaces ChemDraw, MestReNova, instrument software, or a qualified analyst. Anthropic's June post is similarly modest, describing Claude as starting to assist with translation, recall, and integration work that complements chemists' judgment ([15]).
Three points frame the analysis. The instrument run is short (two to three minutes for a routine proton spectrum, about 10 for LC-MS) and the tedious part is analyzing the output ([16]). The evidence base is two vendor-authored studies, with no independent replication located in the sources reviewed. And the regulatory frame was unsettled as of October 2026: the main GMP-specific artificial intelligence (AI) text is a consultation draft, as is the main FDA AI document.
Terms used below: forward prediction is structure in, spectrum out; inverse elucidation is spectrum and formula in, candidate structures out; raw processing is vendor file in, calibrated spectrum or chromatogram out; and purity means UV area percent, which differs from content by weight. Dates and model availability are stated as of October 2026.
Key Changes: What the 2026 Evidence Does and Does Not Establish
Change 1: A June benchmark of forward and inverse NMR tasks
The white paper, authored by David Kamber ([17]), drew compounds from ChemRxiv preprints posted after the models' training cutoff, taking the first fully characterized novel compounds per preprint ([18]). Compounds were chosen and locked before predictions were generated. Each Claude model was queried three times per compound, while the two deterministic classical tools ran once ([19]). Scoring used fixed denominators of 401 hydrogen and 225 carbon atoms ([20]), and a peak counted as correct within ±0.20 ppm for hydrogen or ±1.0 ppm for carbon ([21]). About 80% of Claude's sub-peak spacings fell within half a hertz ([22]).
The inverse task asked Opus 4.7 for up to three ranked SMILES candidates per attempt, with stereochemistry excluded ([23]). Eight simpler targets received only the high-resolution mass spectrometry (HRMS) formula and 1D spectra and were all recovered on every attempt. Seven denser targets also received the starting-material structure; four were solved on all three runs and the rest on two of three ([24]). Without that hint the model could loop without committing to a structure ([25]).
Several caveats belong in any pilot design. MestReNova's 1H score excluded experimental multiplets wider than 0.3 ppm, so tools were not scored on identical atoms ([26]). Every tool predicted carbonyl carbons slightly low, so agreement between two tools on that shift is not independent evidence ([27]). Anthropic's own wish list is several hundred compounds across 20 to 30 scaffold classes, with at least 15 compounds per class ([28]).
Change 2: An August raw-file workflow on one sample
The August 18, 2026 technical report, titled "Automated processing of raw NMR and LC-MS data with Claude Opus 5 on Claude Science", follows one routine QC sample through the Claude Science platform running Claude Opus 5, including its built-in tooling and auditor. A pilot on a different surface, such as the plain API or chat, would therefore be testing a different system. Both measurements begin as raw proprietary instrument files ([29]): the NMR session received the first FID with its header ([30]), and the LC-MS session received a single instrument file ([31]) acquired on a single-quadrupole system ([32]). Where Claude's peak table and the operator's integral regions could be matched they agreed within 0.08 H on a common scale, while four weak operator regions of 0.1 to 0.2 H had no counterpart in the table ([33]) ([34]).
For LC-MS, the report states that decoded intensities matched instrument-stored totals for all 2,664 scans and that all 3,751 photodiode-array blocks parsed with exact byte consumption ([35]). The headline purity was 96.4% against the laboratory's 96.33%. The technical report states that the 96.4% sums only three peaks detected from 0 min, void peak included, whereas the laboratory's figure is computed over seven peaks from 3.46 min. On the laboratory's seven-peak basis, Claude's own areas give 98.8% ([36]). The match of 96.4% to 96.33% is therefore a match of two differently defined numbers, so a laboratory should fix the integration basis in advance.
The self-correction example is instructive. In the heavy-water exchange comparison, Claude's first reading overstated the result and was corrected ([37]); the technical report attributes the catch to a built-in auditor ([38]). The comparison is against the laboratory's own processing records, not an independent ground truth ([39]).
Change 3: A moving model and platform baseline
The June study used Opus 4.7, the August report used Opus 5, and Anthropic's October 2026 documentation recommends Opus 5.5 as the starting point for most workloads ([40]). Opus 4.7 is listed as active with retirement not sooner than April 16, 2027 ([41]). Each model identifier is a pinned version whose underlying model remains constant ([42]), although serving infrastructure around it can change ([43]).
Repeatability controls have narrowed. Anthropic's Opus 5.5 migration guide states that temperature zero never guaranteed identical outputs on prior models ([44]), and the API version dated 2026-10-21 returns a 400 error when temperature, top_p, or top_k is sent, even at the default value ([45]). Replicate runs must therefore supply the evidence of consistency. Academic work agrees: one study found accuracy variations up to 15% across naturally occurring runs ([46]), and another found nondeterminism persisting at temperature 0.0 ([47]).
Access is a further variable. The August post says life science research tasks were blocked in Anthropic's most capable model ([48]), and the June launch notes describe biology and chemistry requests on Fable 5 falling back to Opus 4.8 ([49]). A Life Sciences Verification Program offers vetted organizations more permissive access ([50]). A pilot should record which model actually served each run.
Change 4: A regulatory frame without a finished AI rulebook
Method validation comes first. ICH Q2(R2) states that validation demonstrates a procedure is fit for its intended purpose, and EMA lists a legal effective date of June 14, 2024 ([51]). For electronic records, 21 CFR 11.10 requires system validation and secure, time-stamped audit trails ([52]), and FDA's 2003 scope guidance states it interprets Part 11's scope narrowly and recommends a documented risk assessment ([53]) ([54]).
The AI-specific layer remains in draft. The EU draft Annex 22 applies to AI models in critical applications with direct effect on patient safety, product quality, or data integrity ([55]). It covers only static ([56]) and deterministic ([57]) models and says it does not apply to generative AI and large language models ([58]). For non-critical uses it expects qualified personnel to remain responsible for output suitability ([59]). EMA's mid-2026 workshop report records consultation comments supporting a wider approach and states that the drafting group has discussed allowing generative AI and LLMs in GMP applications under a documented, risk-based control strategy, so the draft exclusion may change ([60]), but no adopted text was located. FDA's AI credibility draft is dated January 2025 and still described as a draft ([61]); it excludes drug discovery and operational-efficiency uses that do not affect patient safety, drug quality, or study-result reliability ([62]).
“Nothing in the public record shows that an AI result establishes identity, purity, release, or GMP suitability.
Implementation Considerations: A Four-Task Validation Protocol
Intended-use statements and risk classification
Write one intended-use statement per task and do not let one task's evidence support another. ICH Q14 frames this through an analytical target profile (ATP) that drives technology choice ([63]). The FDA draft starts from the question of interest and the context of use, the specific role and scope of the model ([64]), and treats model risk as a combination of model influence and decision consequence ([65]). A laboratory can borrow that logic without claiming the draft applies to its work.
Table 1 below summarizes the four claims side by side, using the vendor's own design descriptions. The risk column is this report's analytical judgment, not a regulatory classification.
| Task | Input | Reference and ground truth | Replicates and n | Documented limits | Risk if wrong, and minimum control |
|---|---|---|---|---|---|
| 1. Forward NMR prediction | SMILES string plus solvent | ChemDraw and MestReNova; published experimental peak lists transcribed by a chemist | Three runs per compound; 20 compounds, four scaffold families | No 2D or stereochemistry; three solvents ([66]) | Low to moderate for planning; chemist compares with the experimental spectrum |
| 2. Inverse elucidation | HRMS formula, 1H and 13C peak lists; starting material for hard cases | Published target structures | 15 problems, three attempts, up to three candidates | Hard cases needed a hint; no stereochemistry | Moderate to high; candidates are hypotheses until confirmed by orthogonal data |
| 3. Raw NMR processing | Raw FID with header | Contract laboratory operator processing | One sample, one run | No replicate statistics reported; weak peaks absent | Moderate; analyst overlays output on instrument-software spectrum |
| 4. LC-MS processing and purity | Proprietary single-quadrupole run file | Laboratory seven-peak PDA table | One sample, one run | Nominal mass only ([67]); different peak basis | Moderate to high if area percent informs a go or no-go decision; written integration basis and reconciliation to instrument software |
Table 1 shows that only tasks 1 and 2 have any replicate design and only tasks 3 and 4 involve raw instrument files, so evidence cannot be pooled across them. The risk column is what each organization must replace with its own assessment.
Within a GxP (good practice quality) context, two gates apply before any task touches regulated work. First, whether the output enters a regulated record at all: FDA's data integrity guidance lists the ALCOA attributes (attributable, legible, contemporaneous, original or true copy, accurate) ([68]), and MHRA adds complete, consistent, enduring, and available ([69]). Second, the Annex 22 scope question: for critical GMP uses the draft excludes language models, so a pilot there needs a documented regulatory position first. Teams should consult qualified quality and regulatory professionals for that determination.
Reference dataset design
The June design is a template and shows what to improve. A laboratory dataset should include:
- Post-cutoff or in-house compounds, with the model's stated knowledge cutoff recorded from vendor documentation.
- Scaffold diversity matched to the lab's chemotypes. Anthropic's four families each probe one NMR challenge, such as a slow-exchange NH proton, and the authors name untested scaffolds ([70]).
- Solvents used locally, tested separately, since the June set covered only DMSO-d6, CDCl3, and D2O.
- Each instrument model feeding the pilot, since file headers differ. The August sample was a 400 MHz DMSO-d6 spectrum.
- Impurities, residual solvents, and water, because purity claims depend on them.
- Blinded ground truth. The Annex 22 draft says test data must not be used in development, training, or validation ([71]), and that generating test labels with generative AI is not recommended ([72]).
- Adequate sample size. The draft requires adequate statistical confidence but gives no numeric minimum ([73]).
Table 2 converts the June coverage and limits into a checklist a laboratory can extend.
| Dimension | June benchmark coverage | Gap to close in a lab pilot |
|---|---|---|
| Compounds | 20 forward and 15 inverse, from four ChemRxiv preprints | Own chemotypes; several hundred if feasible |
| Scaffolds | Chloropyridazines, Boc-N-aryl maleimides and N-Boc ynamides, spiroketones, alpha-silyl methanesulfonamides | Other NH-active heteroaromatics; natural products |
| Solvents | DMSO-d6, CDCl3, D2O | Methanol-d4, benzene-d6, acetone-d6, others |
| Experiments | 1D 1H and 13C only | 2D COSY, HSQC, HMBC if the use case needs them |
| Stereochemistry | Excluded by design | Separate task with separate evidence |
| Scoring | 401 hydrogens and 225 carbons | Report coverage and omitted atoms per tool |
| Replicates | Three per Claude model | Enough runs to estimate spread; pin the identifier |
Table 2 makes the external-validity problem concrete: a laboratory working with heteroaromatic amines in methanol-d4 has essentially no direct coverage in the June paper.
Repeatability and model-version controls
ICH Q2(R2) distinguishes repeatability from intermediate precision. Its repeatability design calls for a minimum of 9 determinations across the reportable range or 6 at 100% of test concentration ([74]) ([75]), and it encourages design-of-experiments studies for intermediate precision ([76]). Those numbers describe chemical procedures and do not transfer to language-model runs, but the structure does: repeat identical inputs, then vary the factors that could matter. Suggested controls:
- Pin the identifier and record it for every run. Anthropic states it gives at least 60 days of notice before retiring a publicly released model ([77]).
- Record platform state, including timestamps and tool-call logs, since infrastructure can change under an unchanged identifier.
- Run replicates and report the spread, not only the mean. A 2026 agentic NMR paper notes that some tasks converge on one answer while others do not ([78]).
- Freeze the prompt and attachments. The August prompts were short plain-language requests, which are easy to version and equally easy to vary by accident.
- Treat changes as events. The Annex 22 draft expects change control before deployment ([79]).
Data handling needs review. Claude Science keeps raw datasets on the user's own systems and sends only the context needed for each step ([80]), while prompts and responses are processed under standard retention ([81]). Anthropic's code-execution documentation states that container data, including uploaded files and outputs, is retained for up to 30 days ([82]), and uploaded files cannot be modified after upload ([83]). Compliance documentation is routed through Anthropic's trust portal ([84]); the pages reviewed contained no statement on 21 CFR Part 11 conformance for Claude products.
Forward-prediction acceptance metrics
Compute, per nucleus and per scaffold: mean absolute error (MAE), root-mean-square error (RMSE), the fraction of atoms within a stated tolerance, and coverage (the fraction of experimental atoms for which a prediction was returned). Tolerances are a laboratory decision derived from how the prediction will be used, such as distinguishing regioisomers.
(Hypothetical Example) A chemist scores six 1H peaks with absolute errors of 0.03, 0.05, 0.12, 0.08, 0.31, and 0.02 ppm. MAE is 0.61 divided by 6, or 0.102 ppm. RMSE is the square root of 0.1207 divided by 6, or 0.142 ppm. Five of six peaks, 83.3%, fall within ±0.20 ppm. The single 0.31 ppm outlier lifts RMSE about 40% above MAE, so both are reported and the outlier peak is named so a reviewer can see whether it is an exchangeable proton.
Report in the scorecard: MAE and RMSE for each tool on identical atoms, the within-tolerance percentage with a confidence interval, atoms excluded, per-scaffold results, the replicate range, and a systematic-bias table. Always keep the experimental spectrum in the comparison, because two predictors can share an error.
Inverse-elucidation ranking and confirmation
Define success before running. Anthropic reports success counts out of three attempts with up to three ranked candidates, and the public text reviewed does not state whether success required the top-ranked candidate, so a laboratory should specify top-1 and top-3 separately. A candidate that matches constitution is not a confirmed structure, because stereochemistry is outside the design.
From Anthropic's reported counts, the derived arithmetic is 24 of 24 attempts on the eight simple problems and 12 plus 6 correct attempts out of 21 on the seven harder problems ([85]), or 42 of 45 attempts (93.3%). Attempts cluster within problems, so the effective sample is 15 problems, not 45. As a worked bound, a tool that solves 8 of 8 independent problems has an exact one-sided 95% lower confidence bound on its success rate of about 69%, so small perfect scores do not substitute for a larger set.
Metric choice changes the picture elsewhere in the literature. A 2025 model (ChefNMR) reported 40% top-1 accuracy on simulated natural-product spectra ([86]), and 56% top-1 on a teaching set but 21% on experimental NMRShiftDB2 spectra ([87]). Another reported 60.4% within the first 15 predictions ([88]), a hit counted if the target appears among 15 candidates ([89]). A 2026 LLM-agent system reported 71% top-1 on a 15-molecule set ([90]). These are not interchangeable with Anthropic's results.
Confirmation workflow:
- Log all ranked candidates, not only the one selected.
- Forward check each candidate with an independent predictor against the experimental peak list.
- Require orthogonal data, such as 2D NMR. Established computer-assisted structure elucidation (CASE) software documents 2D inputs; one open-source system builds structures from 2D connectivity without a shift database ([91]).
- Insert controls: problems with known answers and problems with no valid answer, recording whether the model commits to a wrong structure.
Raw FID and LC-MS integrity, parsing, calibration, and reconciliation
The August report documents reconciliation steps any laboratory can require.
- Hash at ingest. Compute a SHA-256 digest of each raw file before upload. FIPS 180-4 notes that a changed message yields a different digest with very high probability ([92]).
- Preserve originals in the controlled system. 21 CFR 211.194 requires a record of all graphs, charts, and spectra from laboratory instrumentation ([93]), and FDA describes reprocessable chromatographic records as dynamic ([94]).
- Reconcile the parse against quantities the instrument stored, as the LC-MS run did with all 2,664 scans. For NMR, echo acquisition parameters from the header and compare with the instrument record.
- Demand processing parameters (phase, apodization, baseline, referencing, fitting) in the report. The August report, for example, reported a coupling constant only where a reconstructed first-order pattern reproduced every observed line.
- Check calibration. Single-quadrupole data give nominal mass only; accurate-mass instruments are described as capable of precision of 10 ppm or better ([95]), and unit mass resolution has a fundamental limitation when candidates give near-identical spectra ([96]).
- Define the purity basis: wavelength, start time, peak list, and void-peak treatment. The August report shows why: the same sample gives different purities on a three-peak and a seven-peak basis.
- Cross-check in instrument software and an independent converter. ProteoWizard's msConvert converts between file formats ([97]), though vendor formats need Windows and vendor libraries ([98]). The open nmrglue library reads Bruker, Varian, JCAMP-DX, nmrML and other NMR formats ([99]).
Purity needs separate care. Diode-array peak-purity checks can miss impurities at much lower absorbance than the main compound ([100]) or with matching spectra ([101]). The Journal of Medicinal Chemistry editors note that HPLC typically will not detect solvent residues, water, or inorganic impurities ([102]), and, in a 2014 editorial, the journal named quantitative 1H NMR following its protocol an accepted purity method ([103]). A literature qNMR example found a commercial sample sold as 97% pure to contain 78.4% w/w of the labeled compound ([104]). An AI-computed area percent should never be presented as content or release purity.
Human review, exception handling, and audit artifacts
Assume the model can be wrong in a fluent way. NIST defines confabulation as confidently stated but erroneous or false content ([105]), and a Nature Chemistry benchmark found many models cannot reliably estimate their own limitations ([106]). Model self-reports are not a control. Review controls that map to existing GxP expectations:
- Second-person review. 21 CFR 211.194 expects a second person to show that original records were reviewed for accuracy, completeness, and compliance ([107]).
- Output checking. 21 CFR 211.68 requires checks of computer input and output for accuracy ([108]).
- Audit trail review, which FDA likens to assessing cross-outs on paper ([109]).
- Authority checks and signatures ([110]), with record changes that do not obscure previously recorded information ([111]).
- Reconstruction. MHRA states raw data must permit full reconstruction of the activities ([112]), so store prompts, files, tool logs, model identifier, and outputs together.
- Exception triggers. The Annex 22 draft asks that models log confidence scores ([113]). Language models do not provide calibrated confidence by default, so define explicit triggers: unmatched peaks, integrals outside tolerance, replicate disagreement, or any unparsed data stream.
Claude Science records an auditable history of how each output was made ([114]), a useful artifact that does not by itself make a system validated for Part 11 purposes. Annex 11 requires validated applications and qualified infrastructure ([115]). ISPE's GAMP AI guide is described as suitable for all types of computerized systems using AI ([116]), and FDA's computer software assurance guidance applies a risk-based approach to AI/ML tools ([117]), though it addresses device manufacturing rather than drug GMP.
Pilot scorecard and stop conditions
End the pilot with a decision per task, not one decision for "Claude". Define pass criteria before data are unblinded, derived from the intended use. Record:
- Accuracy: peak-level error, within-tolerance fraction, top-k success, integral agreement, purity agreement on a stated basis.
- Repeatability: replicate spread and the share of inputs where replicates disagree on the final answer.
- Coverage: atoms, peaks, or scans for which a result was returned.
- Review burden: measured analyst minutes and correction cycles. The laboratory operator's 1 min 49 s of hands-on NMR processing ([118]) excludes review and interpretation time, so each lab should measure its own.
- Exceptions: count, category, and time to resolve.
(Hypothetical Example) If processing takes 4 minutes of analyst time today, and the pilot measures 3 minutes of review plus 0.4 correction cycles at 2 minutes each, the pilot cost is 3.8 minutes, which is not meaningfully better. Savings appear only if review time is lower than manual time and the exception rate stays low. The numbers are invented to show the arithmetic.
Stop conditions should be explicit: a confident wrong structure on a control problem with no review flag; unexplained replicate disagreement on a final answer; a raw-file parse that cannot be reconciled; a purity basis that cannot be reproduced; a model change that alters results on the locked reference set; or AI output entering a regulated record without the agreed review step. The outcome of a stop is a documented decision to narrow scope, retrain staff, or end that task's pilot.
Write one intended-use statement per task. Set pass criteria from that use before unblinding data.
Include post-cutoff or in-house compounds, local scaffolds and solvents, each instrument model, impurities, and blinded ground truth.
Pin and record the model identifier, freeze prompts and attachments, record platform state, and report replicate spread.
Report peak-level error, coverage, repeatability, top-k success, integral agreement, and purity agreement on a stated basis.
Hash raw files, preserve originals, reconcile parsing against instrument records, define the purity basis, and cross-check in instrument software.
Document human review, analyst minutes, correction cycles, and exceptions. Apply explicit stop conditions and decide whether to narrow scope or end the pilot.
Define pass criteria before data are unblinded, derived from the intended use. End with a decision per task.
Stop for a confident wrong structure without a review flag, unexplained replicate disagreement, an unreconciled parse, an irreproducible purity basis, or output bypassing agreed review.
Reference Tools and Competitive Context
The pilot should run against current reference software. Table 3 summarizes documented capabilities from vendor and project pages, which are producers' statements about their own tools. It does not rank them, and no prices are listed because the pages reviewed published none.
| Tool | Documented scope | Inputs and formats | Documented limits or notes |
|---|---|---|---|
| Mestrelab Mnova | Verify checks a proposed structure against analytical data ([119]) with a quality score from -1.0 to +1.0 ([120]); Structure Elucidation ranks candidates using 13C shift predictions ([121]); qNMR purity uses a library method ([122]) | Many vendor NMR formats ([123]); MSChrom opens LC and GC-MS data from several vendors ([124]) | Pages reviewed state no accuracy figures for Verify or Structure Elucidation |
| NMRium | Open-source browser NMR processing; online app available for non-commercial use ([125]) | Auto-processes raw FIDs; prefers a post-FT spectrum if both exist ([126]) | No validation statements in the documentation reviewed |
| ChemDraw NMR prediction (Revvity Signals) | 1D 1H and 13C; equimolar mixtures only ([127]) | Drawn or imported structures | Revvity lists separate NMR Predictors with incremental, HOSE code, and neural network algorithms ([128]) |
| ACD/Labs Spectrus Structure Elucidator Suite (now under Revvity Signals) | Generates and ranks candidate structures from NMR and MS data ([129]); numerical match factor for verification ([130]) | Structure and spectral data | Offers 3D configuration selection using NOESY or ROESY data ([131]) |
| Bruker software | CMC-se supports elucidation and verification workflows ([132]); CMC-assist is listed as end-of-life ([133]); deep learning added to TopSpin for 1H signal detection ([134]) | Bruker instrument data | NMRtist is a cloud AI platform for protein NMR, not small-molecule verification ([135]) |
| Open-source CASE and tools | SENECA ranks candidates by evolutionary search ([136]); DP4-AI automates raw NMR processing and assignment ([137]); nmrshiftdb2 is an open database ([138]) | Varies by project | Academic software with small validation sets, for example 41 molecules for SENECA |
The table indicates that established tools differ from Claude mainly in what they document and how they are controlled. Commercial packages specify supported formats, and the two classical predictors in the June study are deterministic, while Claude's strengths in the June paper were on peak shape and coupling prediction and on 1D elucidation without 2D data. A pilot should compare task by task, not tool against tool.
Data Analysis and Evidence
The public quantitative record is small.
Forward prediction. Opus 4.7's mean 1H error of 0.079 ppm is under half the 0.20 ppm window. On 13C the gap to MestReNova is 0.11 ppm (1.37 versus 1.48), small against a 1.0 ppm tolerance. Claude values are averages of three runs while classical tools are single points, and the authors report that Opus 4.7's run-to-run error varied by less than its margin over the next-best tool ([139]), with ranges shown only in figures. For context, a graph-network 13C predictor reported accuracy comparable to the best density functional methods at 1.5 ppm ([140]). Test sets differ, so no ranking is implied.
Inverse elucidation. The derived counts are 24 of 24 attempts on simple problems and 18 of 21 on harder ones. Trained models report different metrics. MSNovelist ranked the correct structure first for 25% of 3,863 spectra and retrieved it for 45% ([141]). DiffMS reported more than doubling accuracy on a harder benchmark ([142]), while its authors caution that another test set contains molecules nearly identical to training molecules ([143]). A 2026 benchmark found in-domain retraining far outperformed general models ([144]), and models trained on computed spectra drop in performance on experimental NMR measurements ([145]). Test-set provenance can move accuracy more than architecture.
Raw processing and LC-MS. The quantitative statements are the timings, the matched-region agreement, and the purity pair. The arithmetic matters: 96.4 minus 96.33 is 0.07 percentage points, but 98.8 minus 96.33 is 2.47 percentage points on the laboratory's own basis. Timing definitions also need care: the 23 and 19 minutes run from prompt to delivered answer, while the laboratory's finished report is reported to have arrived four days after the first spectrum ([146]). Calendar lag and analyst effort are different quantities, and neither measures review burden.
Variability and capability. One study of five language models configured to be deterministic found none gave repeatable accuracy on every task ([147]). A 2,788-question chemistry benchmark found the best models outperformed the best human chemists on average ([148]), yet predicting the number of NMR signals from SMILES proved hard even for the best models, for example 22% correct for o1-preview ([149]).
Regulatory numbers. ICH Q2(R2) gives design minima for chemical procedures, such as at least five concentrations for linearity ([150]) and a signal-to-noise ratio of at least 10:1 for the quantitation limit ([151]). Integration quality depends on a flat baseline ([152]), and quantitative NMR work uses long relaxation delays, with shorter ones justified only when reduced accuracy is acceptable ([153]).
- The headline purity was 96.4% for Claude against 96.33% for the laboratory.
- Claude used three peaks from 0 min, including the void peak; the laboratory used seven peaks from 3.46 min.
- Claude's own areas give 98.8% on the laboratory's seven-peak basis.
- The difference from 96.33% is 2.47 percentage points on the laboratory basis, versus 0.07 percentage points for the headline pair.
Define the purity basis in advance: wavelength, start time, peak list, and void-peak treatment. UV area percent differs from content by weight.
Implications and Future Directions
Intended use. The evidence most directly supports low-consequence, expert-reviewed use: forward prediction for planning, first-pass peak tables from raw files that an analyst overlays on instrument-software output, and candidate generation for 1D elucidation with a documented starting material. It does not support unreviewed identity, purity, or release statements.
Regulated work. The draft Annex 22 treats language models as outside its scope, while EMA's workshop record shows the question is under discussion ([154]). The joint FDA and EMA principles call for risk-based approaches with proportionate validation ([155]) and performance assessment of the complete system including human-AI interactions ([156]). The human review step is therefore part of the system under test, and documentation should say so. MHRA's 2026 commentary on AI-assisted inspection responses likewise expects technical review by experienced people ([157]).
Evidence gaps. Replicate statistics for raw-file processing do not exist in the public record, independent replication of the June benchmark is absent from the sources reviewed, and the benchmark has not been extended to the scaffolds, solvents, and 2D experiments Anthropic lists as next steps. Laboratories that publish de-identified pilot results on shared reference sets would close these gaps faster than additional vendor demonstrations. Anthropic expects Claude's scientific judgment to become more acute ([158]), so any pilot should be repeated when the model identifier changes.
Tool owners. A hybrid arrangement is plausible: a language model for flexible parsing and hypothesis generation, then confirmation with deterministic software. Quality partners belong in the first protocol draft.
Frequently Asked Questions (FAQs)
Can Claude be used for NMR spectra interpretation?
In Anthropic's June study, Opus 4.7 matched or beat ChemDraw and MestReNova on average for forward 1D shift prediction and solved the simple inverse problems. The study covered 20 and 15 compounds and excluded 2D NMR and stereochemistry. Interpretation of a real spectrum should remain an analyst's task, with Claude as a first-pass assistant.
Can an LLM analyze LC-MS data?
In one documented case Claude decoded a proprietary single-quadrupole file and reproduced instrument totals for all scans, and the resulting purity depends on how peaks are counted. This is a single-sample demonstration. Trained spectrum-to-structure models report modest accuracy on broad MS/MS benchmarks, for example 26% top-1 on the CASMI 2016 challenge ([159]), so structure assignment from MS/MS is a different task from file processing.
How should AI tools be validated in an analytical chemistry laboratory?
Start from an intended-use statement and ATP, build a blinded reference set, run replicates, report error and top-k metrics, reconcile raw-file parsing, and document human review. Acceptance criteria are laboratory decisions; the Annex 22 draft sets no numeric limits and requires only that criteria be at least as high as the process replaced ([160]).
Does ICH Q2(R2) apply to AI-assisted analysis?
Q2(R2) covers analytical procedures and states the fit-for-purpose principle. It was not written for AI tools, but its characteristics (specificity, accuracy, repeatability, intermediate precision, range) supply a vocabulary for pilot design, and a quality unit should decide how far to extend it ([161]).
What does GxP validation of generative AI in analytical labs require?
No finalized AI-specific GMP rule was located in the sources reviewed. The practical anchors are risk-based computerized system validation ([162]), data integrity principles ([163]), change control, and documented human oversight.
How does 21 CFR Part 11 relate to AI review of analytical data?
Part 11 calls for system validation, audit trails, and signed records that show signer, time, and meaning ([164]). FDA interprets the scope narrowly and endorses risk-based validation. A model session producing records used in regulated decisions falls under the same expectations as other software. No Part 11 conformance statement for Claude products was found.
What other AI approaches exist for structure elucidation from NMR and mass spectrometry?
Simulation-trained transformers, LLM agents with tool environments, and established CASE systems all exist (see Table 3 and the inverse-elucidation section). Results are not directly comparable because datasets and metrics differ, and one agent paper lists repeated-run robustness as an open limitation ([165]).
Is Claude a replacement for ChemDraw, MestReNova, or an analyst?
No. Anthropic states its goal as ensuring chemists know where Claude can save them time ([166]), and the analyst remains the reviewer of record.
Conclusion
"Claude for NMR and LC-MS" is not one claim. Forward prediction has a 20-compound, three-run benchmark with favorable mean errors. Inverse elucidation has a 15-problem benchmark that works best on simpler targets or with a starting-material hint. Raw NMR processing and LC-MS processing each have one documented sample, with timings that compare favorably to calendar lag but not to measured analyst effort, and the purity pair compares two differently defined numbers.
For a laboratory, the implication is a staged pilot with four independent decisions. Each task needs its own intended-use statement, blinded reference set, replicate design, metrics, and stop conditions. Model identifiers should be pinned and changes treated as change events, because sampling parameters (temperature, top_p, top_k) are rejected on API version 2026-10-21 and, on earlier versions, when set to non-default values on Claude 4.7 and later models, so the API version in use should be verified. Raw files should be hashed, parses reconciled, purity bases defined, and results reviewed by a qualified person against instrument-software output. In GMP contexts, the draft Annex 22 currently excludes language models, although the drafting group is considering changing that position, so critical uses should wait for a documented regulatory position until guidance is finalized.
Nothing in the public record shows that an AI result establishes identity, purity, release, or GMP suitability. What the 2026 results show is that a general-purpose model can be a credible assistant on routine NMR and LC-MS data, and that the open question is how much of that holds on a laboratory's own compounds, solvents, instruments, and review process. The protocol above answers it with measurements. Questions about regulatory status should go to qualified quality and regulatory professionals.
About IntuitionLabs
Build practical AI for pharma and biotech with IntuitionLabs. We help life-science teams turn complex information and workflows into useful software, governed knowledge systems and AI tools.
IntuitionLabs is an AI consulting, custom software development and data engineering firm serving pharmaceutical, biotechnology, medical-device and other life-science organizations. We work with clinical, regulatory, medical-affairs, commercial, quality and IT teams to connect technology decisions with the work people need to accomplish.
AI consulting and adoption
Our AI enablement services cover readiness assessments, use-case selection, governance and policies, team workshops, adoption measurement and ongoing advisory support. We help organizations structure the information layer behind AI: source material, context, permissions and maintained knowledge that make generated answers useful and reviewable. Private LLM inference and hosted AI options support teams evaluating how to operate AI with appropriate control over their data and infrastructure.
Software, data and life-science workflows
IntuitionLabs develops custom software for pharma and biotech, integrates enterprise systems, and builds data engineering and business intelligence solutions. Areas of focus include AI agents, regulatory research, medical writing, medical affairs, CMC information, competitive intelligence and clinical-document workflows. Our eTMF intelligence work includes cross-system reconciliation and inspection-readiness support.
Enterprise platforms and regulated delivery
We provide Veeva services, application support, managed services, integrations and custom applications, alongside enterprise content work involving platforms such as Egnyte. For regulated workflows, our services include GxP enablement, computer-system validation and software development addressing 21 CFR Part 11 requirements. The applicable controls, validation responsibilities and acceptance criteria are defined for each engagement.
Work with IntuitionLabs
Explore AI enablement, pharma and biotech software development, data engineering and BI, and Veeva services. Contact IntuitionLabs to discuss your workflow, information sources and implementation needs.
IntuitionLabs publishes educational research to help life-science teams make informed technology decisions. Coverage of a product or organization does not imply a client relationship, endorsement or partnership.
Sources / 166

Need Expert Guidance on This Topic?
Let's discuss how IntuitionLabs can help you navigate the challenges covered in this article.
I'm Adrien Laurent, Founder & CEO of IntuitionLabs. With 25+ years of experience in enterprise software development, I specialize in creating custom AI solutions for the pharmaceutical and life science industries.
The information contained in this document is provided for educational and informational purposes only. We make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability of the information contained herein. Any reliance you place on such information is strictly at your own risk. In no event will IntuitionLabs.ai or its representatives be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from the use of information presented in this document. This document may contain content generated with the assistance of artificial intelligence technologies. AI-generated content may contain errors, omissions, or inaccuracies. Readers are advised to independently verify any critical information before acting upon it. All product names, logos, brands, trademarks, and registered trademarks mentioned in this document are the property of their respective owners. All company, product, and service names used in this document are for identification purposes only. Use of these names, logos, trademarks, and brands does not imply endorsement by the respective trademark holders. IntuitionLabs.ai is an AI software development company specializing in helping life-science companies implement and leverage artificial intelligence solutions. Founded in 2023 by Adrien Laurent and based in San Jose, California. This document does not constitute professional or legal advice. For specific guidance related to your business needs, please consult with appropriate qualified professionals.