What a standalone LIMS export loses: one corrected lab result read before and after its QMS and report context

Short answer

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.

Visual briefFull-size diagram
Split panel: on the left a LIMS export row shows the original and corrected value with blank fields for why, who approved, scope checked and report version; on the right the same row with those fields filled from the QMS and document control.
Illustrative correction at a fictional food testing lab. The LIMS shows that a value changed; the QMS and controlled documents explain why and what followed.

This before-and-after reading belongs to the result-to-approved-correction guide. 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.

FieldValue in the export
Sample IDPresent
First value and unitNumber in milligrams per 100 grams, released on day 1
Current value and unitSame number in micrograms per 100 grams, changed on day 7
Changed bySenior analyst user name
Reason"Unit entry error"
ReportVersion 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 knowExport row aloneWith the quality system and document control
What was first reported?Yes, from the audit trailYes
What prompted the change?"Unit entry error"Customer's QA team queried an implausible value on day 4
Was it investigated?Not shownNonconformance opened day 4; root cause: unit picked from the wrong list
Who signed off the fix?Only the analyst who edited itQuality manager approval on day 7
Were neighbors checked?Not shownSix other samples from the same run reviewed, none affected
Which certificate does the customer hold?Version 1 created day 1Version 1 sent day 1 and loaded into the customer's supplier portal day 2; version 2 issued day 8
Was version 1 withdrawn?Not shownNo 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 exportWhat it explainsWhere it livesWho can confirm it
How the error was foundWhether a customer query or internal review caught itQMS nonconformance: detection sourceQA manager
Investigation and root causeWhy the change was madeQMS nonconformance and investigation recordQA manager
Investigation scopeWhich samples from the same run were checkedSample IDs listed in the nonconformanceQA manager
Correction approvalWho authorized the change and whenQMS approval event or electronic signatureQA manager
Report versionsThat version 2 superseded version 1Controlled documents: report number with revisionDocument control lead
Distribution of each versionWho holds the wrong unitDistribution log, if one existsDocument control lead
Link back from QMS to LIMSThat the nonconformance and the edit are the same eventNonconformance number in the LIMS reason fieldLab 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, and it is the part a single-system export strips out. The same pattern shows up in finance, where journal entry review records and GL coding history lose their meaning without the reviewer's reason. Missing reasons are one of the gaps described in what data is missing from AI training.

For the controlled-document side in particular, the field guide to 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 names the key behind each join, and the 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, check it on who qualifies and read the program terms before introducing its director.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

If the LIMS keeps the original value, what is actually lost?

The reason and the reach. The audit trail shows that a value changed and when, but the investigation, the approval, the other samples checked and the report versions sit in the QMS and document control.

Does a QMS-only export avoid the problem?

No, it fails in reverse. It holds rich narratives about root cause, but often no reliable path back to the measured value or to the report the client received.

Can a partner learn which context survives without seeing results?

Yes. Ask whether deviations record the sample ID, whether the LIMS reason field carries the deviation number, how reports are versioned and whether distribution is tracked. Those answers locate the gaps.

Sources

  1. ecfr.gov/current/title-21/chapter-I/subchapter-A/part…
  2. ecfr.gov/current/title-21/chapter-I/subchapter-C/part…
  3. fda.gov/media/158416/download
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment