# LIMS correction export without context | SourceX

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

A standalone LIMS export loses the reason and the approval. It shows that a value changed, both numbers and when, but not why, who signed off, which neighboring samples were rechecked or which report version the customer is relying on. Those facts sit in the quality system and in controlled documents. Without them, a fixed result looks like an unexplained edit, and the wrong unit still sitting in the customer's own systems never appears.

This before-and-after reading belongs to the [result-to-approved-correction guide](/guides/chain-result-to-approved-correction). It takes one Illustrative fix and reads it twice: first as a single export row, then with its surrounding records put back.

## Before: the fix as one export row

Illustrative. A fictional 260-person food and feed testing lab. A vitamin D value for a pet food sample was entered in milligrams per 100 grams when the method reports micrograms per 100 grams, a thousandfold slip. Here is what the export for that sample shows.

| Field | Value in the export |
|---|---|
| Sample ID | Present |
| First value and unit | Number in milligrams per 100 grams, released on day 1 |
| Current value and unit | Same number in micrograms per 100 grams, changed on day 7 |
| Changed by | Senior analyst user name |
| Reason | "Unit entry error" |
| Report | Version 1 created on day 1 |

The audit trail kept both numbers, so a reader knows the unit was put right six days later. What the reader cannot tell matters as much. Did someone investigate, or just overwrite? Were other samples from the same analytical run checked? Did the customer get a corrected certificate, and is the old figure still in the customer's files? The row offers a three-word reason and nothing more. On its own it fits a careful fix and a quiet edit equally well.

## After: the same fix with its quality and document records

Match the export row to the quality system by sample ID and to document control by report number.

| What a reader would want to know | Export row alone | With the quality system and document control |
|---|---|---|
| What was first reported? | Yes, from the audit trail | Yes |
| What prompted the change? | "Unit entry error" | Customer's QA team queried an implausible value on day 4 |
| Was it investigated? | Not shown | Nonconformance opened day 4; root cause: unit picked from the wrong list |
| Who signed off the fix? | Only the analyst who edited it | Quality manager approval on day 7 |
| Were neighbors checked? | Not shown | Six other samples from the same run reviewed, none affected |
| Which certificate does the customer hold? | Version 1 created day 1 | Version 1 sent day 1 and loaded into the customer's supplier portal day 2; version 2 issued day 8 |
| Was version 1 withdrawn? | Not shown | No record in any lab system |

The connected record reads very differently: a customer spotted an impossible number, the lab opened a nonconformance, traced the cause to a unit picklist, checked the other samples from the run, and reissued the certificate with quality approval. It also exposes the one gap nothing fills. The customer's supplier portal took in version 1 on day 2, and no lab record says whether that figure was ever replaced. A single export hides this completely, because it never shows that a copy left the building.

## What is lost, and where it lives

The table below is the evidence asset for a first conversation with a QA manager. It lists each piece of context a LIMS export drops, where it is normally kept and who can confirm it exists.

| Context lost in a LIMS-only export | What it explains | Where it lives | Who can confirm it |
|---|---|---|---|
| How the error was found | Whether a customer query or internal review caught it | QMS nonconformance: detection source | QA manager |
| Investigation and root cause | Why the change was made | QMS nonconformance and investigation record | QA manager |
| Investigation scope | Which samples from the same run were checked | Sample IDs listed in the nonconformance | QA manager |
| Correction approval | Who authorized the change and when | QMS approval event or electronic signature | QA manager |
| Report versions | That version 2 superseded version 1 | Controlled documents: report number with revision | Document control lead |
| Distribution of each version | Who holds the wrong unit | Distribution log, if one exists | Document control lead |
| Link back from QMS to LIMS | That the nonconformance and the edit are the same event | Nonconformance number in the LIMS reason field | Lab operations manager |

In labs that work under FDA drug rules, two regulatory points explain why some of these rows exist at all; a food and feed lab may follow other standards, so ask which apply. Under 21 CFR 11.10, audit trails in closed systems must be secure, computer-generated and time-stamped, and changes must not obscure the earlier value, which is the behavior that keeps the first number in an export row like this one. Under 21 CFR 211.192, an investigation of an unexplained discrepancy extends to other batches that may be associated, and FDA's 2022 out-of-specification guidance describes when an investigation expands beyond the laboratory; the scope row is where that reach is recorded.

The last row runs in both directions. A QMS-only export fails in reverse: it holds the narrative of the investigation but often no reliable path back to the measured value, unless the nonconformance (some labs call it a deviation) names the sample.

## Why the gap matters beyond the lab

Correction records are valuable because they show a qualified person deciding something was wrong and fixing it, with the reason attached. That is the substance of [human review and correction workflows](/guides/how-to-assess-human-review-records-and-correction-workflows), and it is the part a single-system export strips out. The same pattern shows up in finance, where [journal entry review records](/data-types/journal-entry-review-records-ai-training) and [GL coding history](/data-types/gl-coding-history-ai-training-data) lose their meaning without the reviewer's reason. Missing reasons are one of the gaps described in [what data is missing from AI training](/questions/what-data-is-missing-from-ai-training).

For the controlled-document side in particular, the [field guide to document revision histories](/guides/a-partner-field-guide-to-finding-companies-with-document-revision-histories) explains how to ask about versioning without reading documents.

## Describing the gap without opening a result

A partner needs none of the tables above. What SourceX needs is which columns of the after table the lab can fill, from which year, and which it cannot. Ask whether deviations require the sample ID, whether the LIMS reason field carries the deviation number, how reports are versioned and whether distribution is tracked. The [record chain page](/guides/result-to-approved-correction-record-linkage) names the key behind each join, and the [completeness checklist](/resources/result-to-approved-correction-completeness-checklist) scores the trail.

Before introducing, confirm: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license, and an authorized contact: the CEO, or the owner-CEO in an owner-run lab, with the lab director often as sponsor. 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 confidentiality would be handled, SourceX's current data needs and any offer. Partners never handle raw records.

## 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 say which columns of the after table it holds, and admit where distribution tracking stops, [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
