Different laboratories use different names for the same chemical. One lab may report "Benzol" while the regulatory standard uses "Benzene". An AnalyteAlias stores each alternate label (the alias field) alongside the source that uses it, and links it back to the canonical Analyte via analyteId. During import, piper looks up incoming analyte names against the alias table first, resolving them to the correct Analyte before creating AnalyticalResult records. This prevents UnrecognizedAnalyte import issues from recurring after you define the mapping once.
Technical section
Data model, API, and internals — visible to developers.