The traceability function is not completed if you can search for the sample number. For a report, it is necessary to check sample receipt, task assignment, method version, original data and audit records, and understand the changes in between. The complete scenario including sampling, modification and review should be selected for acceptance.

How to arrange records and operations

First determine the scope of records and associated identifiers that need to be retained, and gradually check the source of results used in the report. Attachments, original instrument files and manual entries are identified separately, and historical versions remain accessible. Permission testing is scheduled together with backup recovery, and it makes more sense to restore the relationship intact rather than just restoring the number of files.

For retrospective acceptance, you can first fix a report version, check the methods, original documents and confirmation steps corresponding to each result, and then check the upstream and downstream relationships between the sample and the task. There must be a clear entrance to query current records and historical records, and you cannot use the latest information to create a seemingly complete old chain. The recovery drill also checks the readability of attachments, role permissions, and version correspondence. For manually supplemented relationships, indicate the source, register the responsibilities and processing arrangements after the gap is found during acceptance inspection, and re-query and verify along the same report after filling the gaps.

Specific scenarios that need to be checked

For example, if there is a result correction before the report is released, the acceptance inspection should be able to see the original results, the reason for the correction and the re-examination process. Randomly check the query scope of different roles to ensure that traceback does not become unlimited export. Record the verified scenarios and matters to be improved, and continue to review the associated chain when new methods or interfaces are added later.