ORIGINAL COMPANY-CONTEXT PRACTICE
Trace a laboratory result to its inputs
Original practice scenario inspired by Thermo Fisher Scientific Inc.'s public business context; this is not a reported interview question or a description of its internal systems. A fictional laboratory platform imports instrument files and produces derived results. Analysts can rerun processing with a new method version. Design provenance so a displayed result can be reproduced without confusing it with later reruns.
Written for independent practice using company context; this is not a verified question from a company interview.
A REASONED APPROACH
Model answer.
Identify a result by its input artifact and processing specification, not just by sample name. Reruns should create distinct derived versions linked to their immutable inputs and method configuration.
Work through it
- Store source-file checksums, instrument identity, acquisition time, and import validation. Keep original files separate from normalized records.
- Record method version, parameters, software environment, and execution status for each derivation. Promote a result to the current view through an explicit selection action.
- Expose provenance and supersession relationships in the interface. Test duplicate imports, partially uploaded files, method upgrades, and two simultaneous reruns of the same sample.
Tradeoffs to discuss
- Capturing environments and artifacts increases storage but makes discrepancies diagnosable. Reproducibility also depends on preserving external dependencies used by the method.
Common pitfalls
- Overwriting the old value loses scientific context.
- A human-readable filename alone is not a reliable identifier or integrity check.