The tenantId on an AnalyteAlias ensures that a lab-specific name mapping created by one organization does not affect analyte resolution for another. When piper resolves an incoming analyte name during import, it only looks up aliases whose tenantId matches the current tenant. This keeps custom mappings from leaking across organizational boundaries, which is critical in multi-client deployments where different clients use different labs.
Technical section
Data model, API, and internals — visible to developers.