NAM data management for IND submissions: what regulators need from organoid and computational evidence

The data-management problem NAMs create

NAMs are intrinsically heterogeneous: FDA's NAM description includes in vitro human-based systems, in silico modeling, and platforms relevant to immunogenicity, toxicity, pharmacodynamics, and human predictivity [2]. An organoid, a PBPK model, a QSAR classifier, and an organ-on-chip device may all qualify as NAMs, but they generate fundamentally different evidence types [2]. Without structured metadata, a reviewer may see a result but not the scientific context needed to evaluate it.

A liver-on-chip toxicity readout is not interpretable unless the submission package captures cell origin, maturity and donor characteristics, chip architecture, media composition, flow and shear conditions, exposure duration, nominal versus measured compound concentration, endpoint definitions, controls, replicate structure, assay acceptance criteria, and known limitations; this list follows the data elements implied by FDA's human biological relevance and technical characterization principles [3]. For an ML or PBPK model, the equivalent metadata covers model version, training data provenance, applicability domain, feature definitions, validation split, uncertainty quantification, parameter sources, sensitivity analysis, and model-lock status, which are needed to evaluate fit-for-purpose model use [3].

This is where ontology-backed metadata infrastructure — the kind NAMO is designed to provide — becomes directly useful [2]. FAIRness is a necessary condition, but it is not sufficient for regulatory decision-making because FDA's draft principles also require context of use, biological relevance, technical characterization, and fit-for-purpose evidence [3]. NAM data management should be designed around regulatory confidence, not just FAIRness.

What FDA's March 2026 draft guidance actually requires

FDA's March 2026 draft guidance on alternatives to animal testing frames NAM validation around four principles: context of use, human biological relevance, technical characterization, and fit-for-purpose use in regulatory decision-making [3]. This is almost exactly a data-management problem translated into regulatory language. Each principle maps to a concrete data requirement:

• Context of use: Explicitly define the regulatory question — e.g., "support hepatotoxicity risk assessment before Phase 1" [3]. This should be stated upfront and should drive every metadata and validation decision downstream.
• Human biological relevance: Capture structured biological metadata: human cell and tissue type, disease context, organ system, endpoint pathway, and ontology-mapped terms [3]. The model does not need to be perfect; it needs to recapitulate the biology relevant to the risk claim [3].
• Technical characterization: Capture protocol versioning, QC rules, acceptance criteria, intra- and inter-lab reproducibility, reference compounds, controls, and deviation records [3].
• Fit-for-purpose: Link each NAM result to a specific risk claim, an uncertainty statement, and a weight-of-evidence argument [3]. The useful claim is not "this model is generally good"; it is closer to "this model, at clinically relevant free concentrations, shows no hepatocellular injury signal."

FDA has also stated that NAM data is encouraged in IND applications, including AI toxicity models, cell lines, organoids, and organ-on-chip systems, as part of its plan to phase out mandatory animal testing requirements for drug development [4].

Five ways better data management facilitates IND submission

Good NAM data management helps in concrete, not abstract, ways. Here are the five that matter most for IND preparation:

1. Reviewability. FDA describes IND applications around nonclinical pharmacology/toxicology, manufacturing, and clinical protocol information [1]. A well-managed NAM dataset links raw data, protocol, test article, biological system, assay endpoints, statistical analysis, model outputs, and conclusions so the nonclinical evidence can be read as a coherent package.
2. Traceability. Under 21 CFR Part 58, nonclinical study reports must document methods, test systems, dose regimen, statistical methods, transformations, data-quality issues, and where raw data and reports are stored [5]. Good data management encodes this from the beginning rather than trying to reconstruct it at submission time.
3. Cross-study comparability. If every organoid or chip experiment describes cell type, organ, endpoint, exposure, and controls differently, cross-study evidence is difficult to build. Ontology-backed metadata — shared terms for cell types, tissues, compounds, and endpoints — enables comparison across platforms, laboratories, and disease models [2].
4. Weight-of-evidence reasoning. FDA's fit-for-purpose framing requires each NAM to be evaluated against the specific regulatory decision it supports [3]. A good data model therefore connects each NAM result to a specific claim: risk domain, organ system, exposure level, uncertainty, and the gap it fills or supports in the overall nonclinical package.
5. eCTD and study-data readiness. FDA requires commercial INDs in eCTD format [6]. Supported study-data standards include SEND for nonclinical data, SDTM for clinical data, ADaM for analysis data, and Define-XML for accompanying metadata [7]. SEND is the CDISC nonclinical exchange standard, but many NAM outputs require upstream harmonisation before crosswalking to animal-study-oriented submission structures [8].

Where NAMO fits in this picture

The previous note in this series introduced NAMO as a unified ontology for NAM metadata [2]. Its role here is more specific: NAMO is a pre-submission semantic and data-quality layer that could help transform heterogeneous NAM outputs into reviewer-ready evidence packages [2]. It is not "the IND standard." It sits upstream of eCTD, SEND, study reports, and regulatory summaries [6][7][8].

Practically, a NAMO-to-IND implementation would need five artefacts:

• Context-of-Use card — a structured document per NAM defining the regulatory question, organ system, risk domain, and decision supported [3]
• NAM study metadata schema — one record per experiment: platform, biological system, test article, exposure protocol, endpoints, controls, and QC [2][3]
• Validation evidence matrix — concordance across reference compounds, inter-lab reproducibility, known limitations, and fit-for-purpose conclusion [3]
• Weight-of-evidence claim graph — each NAM result linked to a risk claim and uncertainty statement [3]
• eCTD Module 4 export map — crosswalk from NAMO metadata to IND Module 4 nonclinical pharmacology/toxicology section structure [1][6]

A critical caution worth stating plainly

Better data management does not make a weak NAM acceptable. It makes the evidence assessable. FDA's draft principles still require context of use, human biological relevance, technical characterization, and fit-for-purpose evidence [3]. A poorly validated organoid assay with perfect metadata is still weak evidence. A strong human-relevant model with poor provenance, missing controls, no reproducibility data, and undefined acceptance criteria may fail reviewer confidence even if the underlying biology is sound [3][5].

The regulatory value of NAM data infrastructure comes from the combination of scientific validity and data integrity. One without the other is insufficient [3][5].

NAMs will not enter regulatory decision-making simply because they are innovative or animal-free. They will enter when their context of use, biological relevance, technical reliability, limitations, and decision impact are captured in a structured, traceable, and reviewable form [3][4].