During import, Piper applies an ImportMappingProfile to translate the lab file's columns into structured fields. The profileId recorded on the ImportBatch identifies exactly which profile was used. If a batch produces unexpected ImportValidationIssues or incorrect AnalyticalResults after commit, checking the profileId lets you pull up the profile's columnMapping and verify whether it was configured correctly for the labName in question, or whether a profile update is needed before re-importing the file.
piper
Import Batch Profile ID
The `profileId` on an ImportBatch references the ImportMappingProfile whose columnMapping and options were applied when parsing the file.