01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Chemical dataset deduplication, database linkage, structure-derived identifiers, and reproducible joins across discovery and laboratory systems.
- Limits
- InChI is not a structure file, registry identifier, or experimental record. Mixtures, reactions, polymers, organometallics, and other extensions have distinct coverage and maturity.
- Best for
- Chemistry and Discovery and Laboratory teams working across Acquire → Harmonize → Exchange → Learn + reuse.
- Maturity
- EstablishedSuitable for production assessment. Pin the exact release and any implementation profile.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Chemistry and Discovery and Laboratory source data, metadata, and local mappings
- InChIWhat changes
Use InChI as a pinned standard across Acquire → Harmonize → Exchange → Learn + reuse
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
A compound registry retains the submitted structure, generation software version, full Standard InChI, InChIKey, local identifier, and normalization exceptions for every released record.
Why it matters: Supports consistent chemical entity joins and deduplication, while stereochemistry, tautomer handling, mixtures, assay context, and representation choices still require explicit review.
04
What it fits with
Complements UDM experiment and reaction records, IDMP medicinal-product identity, and chemical registries; InChIKey supports compact indexing but is not a substitute for the full identifier or source structure.
- Data model / schemaOECD OHTs
Both support Chemistry and Laboratory work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileREMBI
Both support Laboratory and Discovery work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileExpmeta
Both support Discovery and Laboratory work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Data model / schemaOME Model / OME-TIFF
Both support Laboratory and Discovery work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its accountable owner, and the decision InChI must support.
Pin the exact version and companion artifacts: Standard InChI version 1 · software v1.07.5.
Map one representative input to the required standard artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Test the main limitation
InChI is not a structure file, registry identifier, or experimental record. Mixtures, reactions, polymers, organometallics, and other extensions have distinct coverage and maturity.
Run one representative end-to-end pilot and record exactly where InChI loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Supports consistent chemical entity joins and deduplication, while stereochemistry, tautomer handling, mixtures, assay context, and representation choices still require explicit review.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
IUPAC-InChI v1.07.5 release
Official publisher or steward guidance for this standard profile.
- Publisher
- IUPAC InChI Subcommittee · InChI Trust