FAIR peptidtoksicitetsdata: MAOMAO guide til triage

Hvad er MAOMAO, og hvorfor betyder FAIR peptidtoksicitetsdata noget?

MAOMAO står for Metadata-Aware Ontology for Multi-source Annotation Organization, en ontologistyret ressource, der harmoniserer peptidtoksicitetsinformation hentet fra offentlige databaser, litteratur-afledte ressourcer og kuraterede datasæt (MAOMAO-udgivelsespapiret, 2026). Det er ikke en enkelt database med en enkelt upstream. Dens første udgivelse integreres 56 kilder, spænder over offentlige databaser, litteratur-afledte ressourcer, supplerende datasæt og manuelt kurerede depoter (samme papir), og konsoliderer dem til 71,857 unikke peptidsekvenser på tværs af otte toksicitetsrelaterede endepunkter. Kernelaget holder 574,856 harmoniserede peptid-endepunkt-kombinationer for disse sekvenser. Søgninger kørte på Google Scholar og PubMed mellem juni 2025 og september 2026, så udgivelsen afspejler tilgængelige ressourcer til og med september 2026. Figurer af denne type varierer efter kilde og kurationsdato, og en enkelt opstrøms-plade inde i udgivelsen bærer kun vægten af ​​den opstrøms.

Tjenester

FAIR peptidtoksicitetsdata betyder noget snævrere end "velorganiserede data." Det betyder en toksicitetsregistrering, der bærer en vedvarende identifikator, rig herkomst metadata og en angivet licens, så en læser kan spore, hvor kravet kom fra, og under hvilke betingelser det kan genbruges.

Analogien: en post er en lab-notesbog, ikke en dom

Behandl en toksicitetsanmærkning, som du ville behandle en notesbogsindgang med oprindelsesstemplet. Den registrerer, hvem der observerede effekten, når, fra hvilken kilde, på hvilken organisme, og under hvilken bevistilstand. Det bekræfter ikke, at en sekvens er sikker. Denne sondring former enhver downstream-beslutning i denne vejledning, fordi en optegnelse fortæller dig, hvad der blev hævdet, og hvor godt det blev dokumenteret, ikke hvad du har bevist om din egen kandidat.

Hvad FAIR faktisk kræver af en toksicitetsjournal

Akronymet skjuler de operative krav. De originale FAIR-principper (Wilkinson et al., Videnskabelige data, 2016) og den GO FAIR oversigt specificere, at data bærer en vedvarende identifikator (F1), at metadata er rige (F2) og inkludere identifikatoren for de data, de beskriver (F3), at herkomsten skal være detaljeret (R1.2), at posten følger domænerelevante fællesskabsstandarder (R1.3), og det er klart, tilgængelig brugslicens oplyses (R1.1).

MAOMAOs harmoniserede felter er den konkrete implementering: kildeidentifikatorer, litteraturhenvisninger, organisme information, annotations herkomst, hentedatoer, filformater og versionsoplysninger, hvor de er tilgængelige, med hver normaliseret sekvens tastet af en deterministisk SHA-256 identifikator over store bogstaver, sekvens uden mellemrum. Filer sendes som CSV, JSON og YAML.

Nøgle takeaway: En kureret toksicitetsregistrering er en herkomststemplet påstand, ikke en sikkerhedsdom.

Hvorfor kuraterede peptidtoksicitetsmetadata ændrer kandidattriage

Curated peptide toxicity metadata changes peptide candidate triage because it lets you filter on the strength of the underlying evidence rather than on the presence of a label. A database that stores only “toxic” or “non-toxic” collapses very different observations into one field. MAOMAO separates them. Its evidence states distinguish positive, negative, ambiguous, unlabeled and no-information records, and the negative state splits further: strong negatives were explicitly supported by experimental evidence, while weak negatives originated from randomly selected negative sets or lacked confirmation of the absence of toxicity annotations (MAOMAO-udgivelsespapiret, 2026).

The distribution shows why that distinction carries weight. Across the release, MAOMAO reports 31,153 positiv, 91,506 negative, 15,717 ambiguous and 5,044 unlabeled states (MAOMAO’s own documentation of its evidence states, hentet 2026-07-30). The negative bucket is nearly three times the positive bucket, so a triage rule that treats every negative as clearance is not filtering on evidence. It is filtering on volume.

Læser en rekord og beslutter, hvad den beviser

Take a record carrying an inferred annotation with no assay context attached. The label says negative. The provenance says the call was inferred rather than measured, and no endpoint, concentration or assay system is recorded alongside it. At that point the record does not answer “is this sequence safe to advance.” It answers “has anyone published a sequence-level toxicity observation for this sequence,” and the answer is no.

That is the decision point. A triage rule built on the presence of a label passes the candidate through. A rule built on evidence state routes it to the ambiguous or unlabeled path, where it needs either a literature check or an assay before it earns a place on a shortlist. The second rule costs more per candidate and produces a shortlist you can defend.

The same logic applies when two sources disagree on the endpoint label for one sequence. The curated record does not pick a winner silently. It holds both annotations with their provenance, and the disagreement itself becomes the signal that the sequence needs orthogonal analytical and biological testing rather than a database verdict.

Hvor beviserne slipper op

Endpoint coverage is uneven, and the gap is structural rather than incidental. MAOMAO states that coverage depends on retrievable sequence-level evidence, which produces class imbalance and limited representation of Cytolysis, Embryotoxic and Ichthyotoxic endpoints (MAOMAO-udgivelsespapiret, 2026). The counts make the thinness concrete: Embryotoxic carries 2 positive states and Ichthyotoxic 5, while Cytolysis holds 343 states in total. Compare that with Toxic root at 57,080 states and 13,824 positives, or Hemolytic at 35,960 states and 4,714 positives.

For a triage rule, this means absence of an annotation in a thin endpoint is not evidence of absence. It means the endpoint was rarely recorded. A shortlist filtered on Embryotoxic or Ichthyotoxic data is filtered on almost nothing, and the honest move is to say so before the candidate reaches a program decision.

Licensing is the second boundary. Annotation content and last-update dates are available for 55 af 56 kilder, but explicit licensing covers only 15 af 56 (MAOMAO’s own documentation of its evidence states, hentet 2026-07-30). Reuse terms for the remainder need checking at the source, not assumed from the aggregate.

Nøgle takeaway： A negative is not one thing. Triage on evidence state and provenance, Butik not on label presence, and treat thin endpoints as unmeasured rather than clean.

Peptidtoksicitetsbeviser og herkomstfelter, Felt for felt

A peptide toxicity record is auditable when two things are explicit: what the evidence state is, and where the record came from. MAOMAO structures both. The ontology has a root class, Toxic, with primary classes Cytotoxic, Neurotoxic, Embryotoxic, and Ichthyotoxic, and Cytotoxic carries subclasses Hemolytic, Cytolysis, and Anti mammalian cells (MAOMAO release paper, 2026). Read branch totals with care: the root Toxic overlaps subclass counts, so summing the branches will overstate the root, a limitation the paper’s methodology note states directly.

Identity is handled by hashing the normalized uppercase sequence with SHA-256, which gives the same sequence the same key across layers and sources. Records ship as CSV, JSON, or YAML.

Evidens-statens ordforråd i praksis

Each state answers a different question for a program. Positiv: is there direct or hierarchy-supported toxicity evidence? Negative: is there direct, endpoint-specific non-toxic evidence? Tvetydigt: are annotations conflicting or unresolved? Unlabeled: was the sequence retained without an explicit class assignment? No information: is there simply no evidence for this endpoint? (MAOMAO release paper, 2026). Treat these as documentation of what the source said, not as a safety determination.

Herkomstfelter, der gør en post reviderbar

MAOMAO’s harmonized fields let a reviewer check a claim without opening the original source. Source identifier and literature reference satisfy Findable and traceable attribution. Organism and annotation provenance satisfy Reusable context. Retrieval date and version satisfy Accessible currency. File format supports Interoperable exchange. Om

Licensing is the honest gap. The paper states no unified dataset license in its main text, reports source-level licensing coverage of 15 af 56 kilder, and places licensing information and versioning records in the Documentation Layer (MAOMAO release paper, 2026). Check source-level terms before reuse in a regulated workflow.

Hvordan FAIR peptidtoksicitetsdata sættes ind i analysedesign og -rapportering

Curated peptide toxicity metadata tells you which orthogonal confirmation to run next; it does not tell you a candidate is safe. That boundary is the whole point of the layer. A database record summarizes what someone else observed under stated conditions, while demonstrated safety rests on orthogonal analytical and biological testing performed on your material: HPLC renhed, MS identitet, counterion state, endotoksin af LAL, sterilitet, and the biological assays your program requires. Each test answers a narrow question. LAL measures endotoxin burden only, not sterility or chemical purity, and counterion mass is not trivial, since the TFA salt can represent roughly 5% til 25% of solid mass and residual TFA can perturb membrane and receptor assay readouts (counterion and orthogonal-testing literature, 2020-12-03).

Til tip: Map each remaining uncertainty to the specific orthogonal test that resolves it before you commit assay time.

Fra en triage-shortlist til en analyseplan

Work from the shortlist your evidence-state filter produced, then convert each open question into a test and a decision rule.

1. Identitet og renhed. If the record carries an inferred annotation with no assay context, confirm molecular identity by MS and chromatographic cleanliness by HPLC under a defined method. Resolve the candidate if identity matches and purity meets your specification.

2. Counterion state. Where the record notes a salt form without quantification, measure it. A counterion result that shifts effective dose or perturbs a receptor assay changes the interpretation of everything downstream.

3. Endotoksin. Set the limit from the compendial endotoxin limit, K/M, med K = 5 USP-EU/kg for routes other than intrathecal and K = 0.2 USP-EU/kg for intrathecal, hvor M er den maksimalt anbefalede humane dosis pr. kg på en enkelt time (USP <85> Test af bakterielle endotoksiner).

4. Sterilitet. Demonstrate absence of viable microorganisms under test conditions, which under USP <71> means inoculation into specified media and 14-day incubation (I Q2(R2), 2023-11-30).

5. Biological confirmation. Only after the analytical layer is settled should you read a toxicity signal as a property of the candidate rather than of the sample.

Dokumentation, der overlever gennemgang

Every result above has to be defensible later, and the metadata layer is where that starts. The MHRA’s 2018 GxP data integrity guidance defines ALCOA as attributable, læselig, samtidige, original, and accurate, med ALCOA+ tilføjelse komplet, konsekvent, udholdende, og tilgængelig (MHRA, Guidance on GxP data integrity, 2018-03-09). Provenance fields map onto those attributes directly: a source identifier and curation date make a record attributable and contemporaneous, an assay-context field keeps it complete, and a stable record link keeps it available. Validation expectations run in parallel, since ICH Q2(R2)’s fit-for-purpose standard requires documenting that a procedure suits its intended use, not merely that it ran (I Q2(R2), 2026-02-20).

A FAIR metadata layer supports this workflow in a modest, replicable way. It can be used to carry evidence states and provenance fields from triage tooling into CoA-grade records without retyping, and it helps keep the analytical results, the method used, and the record they were matched against in one traceable chain. MOL Changes is built around that documentation and analytical-verification layer, including HPLC/MS and sterility testing and Class 100 sterile manufacture. The practical consequence is that the database never stands in for your testing; it decides which testing you owe, and it supplies the audit trail that shows you ran it.

Benchmarking og forudsigelsesmodeller bygget på metadata for peptidtoksicitet

MAOMAO’s benchmark layer exists so that model performance can be compared on a shared footing rather than on each paper’s private split. It defines 300 endpoint-seed-strategy configurations, 1,500 data partitions, 3,300 representation-specific configurations and 16,500 fold instances, stammer fra 5 eligible endpoints Syntetiske peptider × 30 random seeds × 5-fold splitting × 11 representations (MAOMAO, Grænser i farmakologi, 2026). The representation side is equally explicit: 10 protein-language-model embedding matrices plus a one-hot representation covering all 71,857 sekvenser, alongside a descriptor layer of 41 features (MAOMAO, 2026).

The limitation matters as much as the scale. Those predefined partitions use random and stratified splitting and are not homology- or similarity-controlled, so they are not leakage-controlled. A high score on this benchmark tells you a model separates the curated peptide toxicity metadata it was trained on. It does not yet tell you the model transfers to a scaffold it has never seen.

Læser forudsigelsesmodelpåstande med de rigtige forbehold

Published peptide toxicity predictors report strong numbers, and each number carries its own scope. ToxiPep trained on 3,528 toxic and 3,528 non-toxic peptides filtered at CD-HIT 0.9, tested on 883 plus 883, and reported accuracy 0.850, sensitivity 0.827, specificitet 0.873, MCC 0.701 og ToxiPep’s reported 0.92 AUC (2025). ToxGIN’s independent-test AUROC af 0.9172 came with an F1 of 0.8354 and an MCC of 0.6866 (Briefinger i bioinformatik, 2024). PeptiVerse assembled 5,518 toxic and 5,518 non-toxic peptides, men PeptiVerse inherits its toxicity labels from ToxinPred3.0 rather than from assay (2026).

Two caveats follow. Først, these are largely vendor-of-own-method results, evaluated by the teams that built the models. Anden, applicability domain is bounded by construction: ToxiPep’s CD-HIT 0.9 filtering means its claims hold for sequences similar to its training data, not for arbitrary novel chemistry. PeptiVerse compounds this, because a label inherited from a predictor carries that predictor’s error forward.

Hvad et lækage-kontrolleret benchmark ville ændre

If you are deciding whether to trust a model on a novel scaffold, the split is the claim. Homology- or similarity-controlled partitioning holds near-duplicate sequences out of training, so a test score reflects extrapolation rather than memorisation of close relatives. Random and stratified splits cannot distinguish the two, which is why a 0.92 AUC on a random split and a 0.92 AUC on a homology-controlled split mean different things for your program.

The practical reading: treat published peptide toxicity metadata scores as evidence of internal discrimination, not as a transfer guarantee. Before a model informs a synthesis or testing decision, check whether its evaluation controlled for sequence similarity, and confirm the endpoint and assay context behind its labels. Where that control is absent, the score is a starting hypothesis for orthogonal analytical and biological testing, not a substitute for it.

Almindelige misforståelser om peptidtoksicitetsdatabaser

The most common error is treating a database label as a safety determination. A label records what was observed, in what system, under what conditions; it does not certify that a sequence is safe to advance.

The first misconception is that a negative label means non-toxic. Negatives are not one thing. A strong negative rests on a documented assay with a stated endpoint and concentration range; a weak negative may reflect an untested sequence, an unreported result, or an assay that could not detect the effect. A triage rule that collapses the two into a single “clean” flag is the failure mode.

The second is that more sources means more confidence. Source count and evidential independence are different quantities. A large aggregate can still trace back to one upstream contributor, so the apparent breadth of support is narrower than the number suggests.

The third is that a model score transfers to a novel sequence. Prediction models carry an applicability domain, and a score computed outside it is an extrapolation, ikke en måling.

The fourth is that harmonized data removes the need for orthogonal testing. Harmonization makes records comparable; it does not make them sufficient. Decisions on peptide safety still require qualified professional judgement and orthogonal analytical and biological testing.

Advarsel: a negative label is not one thing. Strong and weak negatives carry different evidential weight, and a triage rule that treats them as one thing is the failure mode.

Part of why the negative side is structurally thinner is toxicology’s publication bias, measured as a 3.3-fold publication advantage for positive findings, with positive-result prevalence rising from roughly 50% til 90% between 1991 og 2007 (Bero et al., risk-of-bias review, 2016, covering the 1991–2007 window). A literature-derived dataset inherits that asymmetry.

Hvorfor ikke-klinisk toksikologisk nedslidning gør dette til en beslutning, ikke en kuriosum

The stakes are why peptide candidate triage deserves this level of care rather than a quick database lookup. In the four-company attrition audit, non-clinical toxicology accounted for 40% of terminations, the largest single cause, på tværs nogenlunde 605 terminated compounds from AstraZeneca, Eli Lilly, GSK and Pfizer between 2000 og 2010 (Waring et al., Nature Reviews Drug Discovery, 2015).

A pharmacology review reaches the same order of magnitude, putting toxicity at roughly one third of drug-candidate attrition and reporting clinical-development safety failure rates of 35% from phase 1 to submission and 28% from phase 2 to submission (Karnes et al., 2010). The two sources converge on the same conclusion through different samples and methods, which strengthens the signal without making them fully independent estimates.

Kom godt i gang med FAIR peptidtoksicitetsdata

The first action is to pull one candidate sequence and read its record end to end before you run anything. That single pass tells you what the record already supports and what it does not.

Trin 1: Resolve the sequence and read the record. Resolve the sequence to its deterministic identifier, then read the evidence state and provenance fields attached to it. MAOMAO’s harmonized fields are designed for exactly this pass: a SHA-256 identifier ties the entry to one sequence, and the provenance fields state where the underlying measurement came from. If a field is empty, treat that as information, not as a gap to fill by assumption.

Trin 2: Classify each uncertainty and assign a test. Sort what you found into analytical uncertainty and biological uncertainty, then name the orthogonal test that resolves each one. Orthogonal analytical and biological testing means the second method does not share the failure mode of the first, so agreement between them carries weight that a repeat run does not.

Trin 3: Record the outcome so it stays reusable. Write the result against the ALCOA+ attributes the MHRA’s ALCOA definition sets out: henføres, læselig, samtidige, original, nøjagtig, plus komplet, konsekvent, udholdende og tilgængelig. A result recorded this way can be reused in the next program instead of re-derived.

The metadata layer is a starting point, not a substitute for testing. It tells you which experiment to run next; only the experiment tells you what the peptide does.

Ofte stillede spørgsmål

Hvad står MAOMAO for, og hvad integrerer det?

MAOMAO is a curated peptide toxicity resource that brings sequence records, assay context and provenance metadata into one FAIR-aligned layer, so a toxicity label arrives with the conditions that produced it rather than as a bare flag. The integration point matters more than the acronym: rækkefølge, endpoint, assay system and curation date travel together.

Betyder et negativt toksicitetsmærke, at et peptid er sikkert?

Ingen. A negative label means the curated record contains no toxicity signal for the tested conditions, which is a statement about the evidence, not about the molecule. Absence of a recorded effect in one assay system does not establish safety, and any development decision still needs qualified toxicological judgement plus orthogonal analytical and biological testing.

Hvordan sammenligner MAOMAO med DBAASP v3?

DBAASP v3, the experimental-record counterpart, covers more than 15,700 peptide entries, herunder over 14,500 monomeric peptides and roughly 400 homo- and hetero-multimers, with activity and toxicity measurements against 8 target species or cell-type groups (DBAASP v3, released November 2020). The two resources answer different questions: DBAASP v3 aggregates measured records, while a FAIR layer adds the evidence-state and provenance fields that make each record auditable.

Kan forudsigelsesmodeller som ToxiPep eller ToxGIN erstatte assaytest?

Not as a substitute for experimental confirmation. ToxiPep’s reported 0.92 AUC describes discrimination on its evaluation set, which is a performance statement about a model, not a safety finding about a sequence. Prediction output is best used to rank and prioritise candidates before orthogonal analytical and biological testing, not to close a toxicity question.

Hvilken ortogonal test kræver en triage-shortlist stadig?

A shortlist produced from curated peptide toxicity metadata still needs confirmatory analytical work, typically identity and purity assessment by HPLC and mass spectrometry alongside the relevant biological or cell-based assays for the intended endpoint. The database narrows what you test first; it does not remove the testing.

Hvordan understøtter FAIR-metadata IND-aktiverende dokumentation?

FAIR metadata supports IND-enabling documentation because it keeps each record traceable to its source, method and curation date, which is the same property the MHRA’s ALCOA definition requires of attributable, læselig, samtidige, original and accurate records. Regulators review the evidence chain, so a well-documented peptide toxicity metadata layer reduces the reconstruction work later.

Konklusion

Curated FAIR peptide toxicity data improves candidate triage, assay design and reporting, and it does not demonstrate safety. That distinction is the whole argument: a provenance-stamped record tells you what was measured, in what system, under what conditions, and where the evidence stops. It does not tell you a peptide is safe, and no database label can carry that weight on its own.

The layered case runs from the data model outward. Evidence states and provenance fields make a record auditable; auditable records make triage defensible; defensible triage produces an assay plan that survives review. Each step depends on the one before it, which is why partial adoption tends to stall at the first ambiguous record.

The resource and its surrounding model ecosystem are still moving. Coverage gaps remain, licensing coverage is incomplete, and benchmarks are not yet leakage-controlled. The MAOMAO release paper reports that 15 af 56 datasets carry explicit licensing information, so verify terms before you build on any table. Treat current prediction-model claims as directional, not settled.

If you are weighing adoption, the useful next step is a scoped conversation about your own triage workflow. Peptid produktion

Afsløring: MOL Changes publishes peptide documentation and analytical verification, including HPLC, MS and sterility testing under Class 100 sterile manufacture. This article is educational and does not recommend or endorse any specific peptide.

Decisions about peptide safety require qualified professional judgement and orthogonal analytical and biological testing, not a database label alone.