# Result-to-approved-correction record chain | SourceX

Canonical: https://refer.sourcex.si/guides/result-to-approved-correction-record-linkage
Last updated: 2026-11-04

A lab connects result-to-approved-correction records by anchoring everything on the sample ID and checking that two more keys were written beside it: the investigation number in the result's audit reason, and the report number with its revision. Inside the building, almost every hop has a key. The hop that breaks is the one leaving it: nothing links the corrected report to the earlier copies a client already received, so a unit correction can be absent from downstream copies.

This record chain belongs to the [result-to-approved-correction guide](/guides/chain-result-to-approved-correction), which covers the metadata packet a partner fills in. Here the task is narrower: walk one fix through nine records, day by day, and name the identifier that hands it on.

## Nine records from first result to reissued report

Illustrative. A fictional 190-person contract analytical lab. A result is entered and reported, then found during trend review to carry the wrong unit.

| Step | Day | Record | Key to the next record | System |
|---|---|---|---|---|
| 1. Result approved | 0 | Result entered and approved; report v1 generated | Sample ID and report number | LIMS |
| 2. Certificate sent | 1 | Certificate PDF of v1 emailed to the client | Report number in the file name | Email |
| 3. Issue spotted | 6 | Reviewer flags a unit inconsistency during trend review | Sample ID | LIMS |
| 4. Deviation opened | 6 | Deviation record created | Sample ID typed into the deviation | QMS |
| 5. Scope checked | 9 | Keying slip confirmed; 14 sibling samples checked, none affected | Sample IDs listed in the deviation | QMS |
| 6. Correction approved | 11 | Correction and root cause approved by QA | Approver and date as system events | QMS |
| 7. Result corrected | 11 | Original value and reason kept in the audit trail | Deviation number in the reason field | LIMS |
| 8. Report reissued | 12 | Report v2 issued, referencing v1 | Report number with revision suffix | Controlled documents |
| 9. Client notified | 12 | Client told of v2; withdrawal of v1 not recorded | None | None |

Eight of nine steps carry a key. Steps 1, 3 and 7 share one database and the sample ID natively. Steps 4 to 6 sit in a separate quality system and join back only because someone typed the sample ID into the investigation record and its number into the result's reason field. Step 8 joins through the report number. Step 9 has nothing.

## What each key proves

The keys are not equal. A partner describing this chain should know which are generated by a system and which depend on a person typing them correctly.

| Key | Generated or typed | What it proves |
|---|---|---|
| Sample ID | Generated | Which result and which sample |
| Audit trail entry | Generated | The value changed, when, by whom, with the earlier value kept |
| Deviation number in the result's reason field | Typed | This fix belongs to this investigation |
| Sample IDs listed on the deviation | Typed | How far the investigation reached |
| QA approval event | Generated | Who approved the fix and when |
| Report number with revision | Generated by document control | Which version superseded which |
| Distribution record | Usually absent | Who holds which version |

Generated keys are dependable for as long as the system keeps them. Typed keys are only as good as the form that asks for them: if the field is optional, expect gaps in busy months. The regulatory reasons some of these keys exist are set out further down.

## Where the chain usually breaks

Four breaks recur, each with a signature that can be asked about without reading a result.

**The investigation does not name the sample.** If the form has no required sample ID field, investigators describe the sample in narrative text. The signature: investigations searchable by date and type but not by sample.

**The reason field is free text.** The original value survives, but the reason says "keying error" with no investigation number. The signature: corrected results whose reasons match no quality record except by date.

**Paper before a cutover.** Labs that moved from paper forms to an electronic quality system have a clean chain only after the move. The signature: a start year for electronic investigations later than the results history.

**The copy outside the lab.** Report v1 was emailed on day 1. The lab issued v2 on day 12, but nothing records whether the client replaced v1 in its own files or trend spreadsheet. This is the weak link, and it is exactly where a unit correction goes missing downstream; the [missing-context comparison](/guides/result-to-approved-correction-missing-context) shows what a reader of v1 alone would conclude.

## Why regulated labs tend to keep the inner keys

Two rules explain why the keys inside the lab are usually present in regulated settings. For closed systems, 21 CFR 11.10 requires secure, computer-generated, time-stamped audit trails that do not obscure previously recorded values and are kept as long as the records, which is why step 7 preserves the original value. Under 21 CFR 211.192, an investigation of an unexplained discrepancy extends to other batches that may be associated and must be written up with its conclusions and follow-up, and FDA's 2022 out-of-specification guidance describes the laboratory phase of an investigation and when to expand it beyond the lab. The 14 sibling samples in step 5 are that reach, recorded as a key. Neither rule says anything about copies a client already holds, which is why step 9 can stay blank.

## Repairing the downstream link

The repair for step 9 is a distribution record: a log, kept with the controlled report, of who received each version and when the earlier version was withdrawn or acknowledged as superseded.

| Weak link | Repair a lab may already have | Key it creates |
|---|---|---|
| Report v2 to emailed v1 | Distribution log per report number and revision | Who holds which version |
| v1 withdrawal | Client acknowledgement of the superseded version, filed with v2 | Recorded withdrawal |
| Deviation to sample | Required sample ID field on the deviation form | Searchable investigation scope |
| LIMS reason to deviation | Deviation number required in the reason field | Typed join back to the QMS |

For an introduction, the point is to learn which of these exist and from which year, not to fix them. The [completeness checklist](/resources/result-to-approved-correction-completeness-checklist) scores that. Why correction records interest AI training and evaluation buyers is covered in [assessing human review records and correction workflows](/guides/how-to-assess-human-review-records-and-correction-workflows).

## Owners, sponsor and what stays unknown

The lab operations manager owns the LIMS steps, the QA manager the QMS steps, and the document control lead the report versions and any distribution log. Each can describe their hop from form fields, settings and naming conventions without opening a result or a deviation narrative. The CEO, or the owner-CEO in an owner-run lab, authorizes a licensing discussion; the lab director or general manager often sponsors it. Labs owned by investors often sit in [testing, inspection and certification portfolios](/industries/testing-inspection-certification-private-equity), and the engineering parallel is the [engineering QA/QC process](/data-types/engineering-qa-qc-process).

Before introducing, confirm: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

Unknown until SourceX reviews it: which records belong to the lab rather than its clients, how client and regulatory confidentiality would be handled, SourceX's current data needs and any offer. Partners record which hops exist and who owns them, never the records; [data quality due diligence](/resources/data-quality-due-diligence) frames the questions a buyer would ask later.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a lab can name the key at each hop, including whether it tracks who received each report version, [register as a partner](/register), check it on [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing its director.

## Sources

- https://www.ecfr.gov/current/title-21/chapter-I/subchapter-A/part-11/subpart-B/section-11.10
- https://www.ecfr.gov/current/title-21/chapter-I/subchapter-C/part-211/subpart-J/section-211.192
- https://www.fda.gov/media/158416/download
- https://refer.sourcex.si/terms
