The successful upload of the instrument file does not mean that the results have been correctly attributed. Inconsistencies in sample number formats, project names, and units can put data in the wrong place. LIMS import should be divided into parsing, matching, verification and confirmation, and the original files should be retained for review.

How to arrange records and operations

The interface rules clarify field mapping, units and result types, and unfamiliar items or numbers are entered into the waiting list. Numeric values, text results and exception flags are processed separately, and default values ​​cannot be used to replace parsing failures. After the import is confirmed, the original file and the mapped version are associated, and duplicate files will not generate valid results.

The import preview can display the original number, matching sample, project and result unit line by line. The confirmation personnel can see the differences before submitting. The number format and decimal separation agreement must be clear. Blank, lower than the detection range and text results cannot be uniformly converted to zero. The original file contains the source device and creation time, and the rules used in the parsing process are recorded. To repeat the import, first compare the file identifier with the associated results, and enter review if necessary. A complete processing list will be given when some lines fail, and the successful upload message cannot cover up the results that have not yet entered the task.

Specific scenarios that need to be checked

For example, if the instrument output unit is different from the task configuration, the test should prompt for verification and use confirmed conversion rules. Covers decimal formats, null values, and duplicate sample numbers. Manually modify matching permissions and records to avoid directly ignoring all abnormal rows to complete the import.