After Piper reads the uploaded lab file using the ImportMappingProfile, it stores the interpreted row data as JSON in the parsedData field. This intermediate representation is what the validation engine inspects to generate ImportValidationIssues. It serves as the source of truth for the row-level review screen where staff resolve warnings and errors before committing. The parsedData remains available until the batch is committed or discarded, enabling re-validation if a profile columnMapping is updated mid-review.
piper
Import Batch Parsed Data
The `parsedData` on an ImportBatch holds the structured JSON output of the file parsing step, used internally during validation before rows become AnalyticalResults.