# Error localization: a lab unit error traced | SourceX

Canonical: https://refer.sourcex.si/guides/concept-error-localization
Last updated: 2026-11-04

Error localization is finding the earliest step in a process where a record became wrong. In an ordinary business workflow, errors usually surface far from where they start: in this page's fictional laboratory case, a clinician notices an impossible glucose unit, but the unit was introduced one system earlier, by an interface template, after a technologist had corrected the number properly. Localizing the error means checking the value at each hop until the first bad one is found.

## What does error localization mean in an ordinary business workflow?

It is a narrower job than fixing an error or explaining it. Localization answers only where the record first went wrong. It sits between noticing an error and fixing it, and it is often the hardest part, because errors tend to surface far from where they started.

Laboratories make a clear example because the rules already demand much of the evidence. Under 42 CFR 493.1291, a U.S. laboratory that detects an error in a reported patient result must promptly notify the person who ordered the test, issue a corrected report, and keep copies of both the original and the corrected report. Health data standards add structure: FHIR, the HL7 exchange standard, separates a result that was "corrected" to fix an error from one that was "amended" with new information, and its Provenance resource records which person, software or device created or revised each version. UCUM, the code system FHIR uses for units, exists so that machines exchange units without ambiguity, which is exactly what fails in the case below.

AI researchers test the same skill directly. The ProcessBench benchmark asks models to identify the earliest step that contains an error in a worked solution, or to say that every step is correct, with error locations marked by human experts. Business records that already mark the first bad step in a real process are the workplace version of that annotation.

## A unit error, traced hop by hop (Illustrative)

This case is fictional. A 340-person regional reference laboratory reports a serum glucose result. The analyzer reads 126 mg/dL, but the original report goes out as 162 mg/dL because two digits were transposed during a manual step. A technologist catches it the same afternoon and issues a correction. The correction fixes the number and breaks something else.

| Hop | System | Value as recorded | Check | What the record shows |
|---|---|---|---|---|
| 1 | Analyzer | 126 mg/dL | Pass | Instrument file with run time |
| 2 | Lab information system, correction screen | 126 mg/dL, status corrected | Pass | Correction with user, time and reason "transposition" |
| 3 | Interface engine, outbound message | 126 mmol/L | **Fail, first** | Message log: unit field filled from the correction template's default |
| 4 | Clinician's record | 126 mmol/L, flagged critical | Fail | Display flag; a nurse calls the lab |

The error was noticed at hop 4, because a glucose of 126 mmol/L is implausible for almost any patient. It entered at hop 3. The person who made the correction at hop 2 did their part right. That is the whole point of error localization: the place where an error is seen, the place where someone acted, and the place where the error entered can be three different steps, and only the version at each hop tells them apart.

Notice how the hops were checked. Rather than walking from the start, the reviewer checked hop 2 (correct), then hop 4 (wrong), then hop 3 (wrong), which pins the first bad hop in three looks. With a long chain, splitting the remaining range in half each time finds the first bad step quickly, but only if every intermediate version was kept.

## The fields that let each hop be checked

The trace works only because each hop kept its own version of the value. These are the fields the example relies on.

| Field | Where it sits in the example | Why the trace depends on it |
|---|---|---|
| Raw instrument value and unit | Analyzer file, hop 1 | The ground truth every later hop is compared with |
| Original and corrected report | Lab information system, hop 2 | U.S. rules require both copies to be kept, so the change is visible |
| Result status | "Corrected" rather than "amended" | Tells a reviewer the change fixed an error, not added information |
| Correction reason, user and time | Correction screen, hop 2 | Shows who acted and why |
| Outbound message as sent | Interface engine log, hop 3 | The only place the wrong unit can be caught entering |
| Template or mapping default | Interface configuration | Explains why hop 3 changed the unit |
| Received value and flag | Clinician's record, hop 4 | Where the error was noticed |
| Shared accession or result ID | All four hops | Joins the versions into one chain |

If the interface engine had kept only delivery receipts, not message content, hop 3 would be a blank, and the error would appear to jump from a correct correction to a wrong clinical record.

## What the trace shows, and what it cannot

- **Where is not why.** The trace finds hop 3. Why the template defaulted to mmol/L, and why no validation rule caught it, is root cause analysis, a later step.
- **Half-splitting needs every version.** Checking hop 2, then 4, then 3 is fast only because each intermediate value survived. A missing hop forces a guess.
- **Plausible errors hide.** A wrong unit that produced a believable number would not have been flagged at hop 4 at all, and many such errors are never traced.
- **Real chains are hard to invent.** The timing, system names and defaults in a real trace are what make it useful, one reason [synthetic data rarely replaces real data](/questions/will-synthetic-data-replace-real-data). The same principle of tracing every number to its source runs through our page on [MCP for CFO dashboards](/resources/mcp/mcp-cfo-dashboard).

## Who owns these records, and what stays unknown

In a laboratory, the quality manager and laboratory director own correction records and reports, IT or an integration team owns the interface engine and its logs, and the receiving clinical systems belong to the client. Authority to discuss licensing usually rests with the CEO or COO.

The company needs 50 or more full-time employees at peak (contractors excluded), documented operating history, rights to license its records, 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.

Clinical records add a layer: patient information is involved at every hop, so whether and how it can be de-identified, and whether client or vendor contracts permit any use, is decided in SourceX's review with the company, not by the introducer. For framing the conversation with healthcare operators, see [how advisors introduce healthcare administration clients](/guides/how-advisors-introduce-healthcare-administration-clients-to-a-data-licensing-opportunity). Also unknown until review: how many cases pass an acceptance check and whether any buyer wants this task type. Partners never request exports, screenshots or sample reports. Related concepts are in the [data types hub](/data-types).

## Go deeper on error localization

- [Questions to ask a client about error localization](/questions/does-error-localization-data-qualify): a short discovery script for checking whether a company keeps every version of a value as it moves between systems.
- [Record gaps that make error localization hard to assess](/questions/error-localization-evidence-gaps): a guide to the missing interface logs and overwritten originals that hide where an error entered.
- [Error localization review packet](/resources/error-localization-review-packet): a list of the metadata a company prepares before SourceX reviews its correction histories.

## 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 the quality manager confirms that corrected reports keep their originals and reasons and that interface logs survive long enough to show each hop, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [terms](/terms) before you introduce the CEO or COO.

## Sources

- https://hl7.org/fhir/R4B/valueset-observation-status.html
- https://ucum.org/about
- https://www.ecfr.gov/current/title-42/chapter-IV/subchapter-G/part-493/subpart-K/subject-group-ECFR9482366886d579f/section-493.1291
- https://hl7.org/fhir/provenance.html
- https://arxiv.org/abs/2412.06559
- https://refer.sourcex.si/terms
