This list belongs to error localization. It follows the introducer's conversation: the qualification scorecard decides whether to introduce, and the evidence gaps analysis explains which weaknesses the packet should state.
The seven documents at a glance
Each document builds on the one before. The acceptance check, for instance, names systems, so it cannot be written until the system route map exists.
| Order | Document | What it shows | Prepared by |
|---|---|---|---|
| 1 | Task statement | The one question each case answers | Quality manager |
| 2 | System route map | Every system the value passes through, in order | IT or integration lead |
| 3 | Versions kept per system | What record survives in each system, and for how long | Lab system administrator with integration lead |
| 4 | Agent map | Which person, software or device creates each version | Quality manager |
| 5 | Acceptance check | The test an answer must pass, fixed before review | Laboratory director with quality manager |
| 6 | Volume and span | Corrections per month, share involving units or ranges, retained months | Quality manager |
| 7 | Rights and sensitivity note | Identifiers in each system, client and vendor terms, the authorizer | Compliance lead, counsel or CEO |
Documents 1 to 4: defining the case and its route
1. Task statement. One sentence, for example: given a corrected result and its step history, identify the first step at which the value or unit differs from the source reading (the value the analyzer first produced), or confirm that no step differs. The "or confirm" clause matters; it mirrors how the ProcessBench benchmark asks models to find the earliest erroneous step or conclude that all steps are correct.
2. System route map. The systems in order, with the system of record for each: analyzer, lab information system, interface engine, receiving record at the client. Include middleware if it touches values, and note any system the lab does not control.
3. Versions kept per system. Raw analyzer output files; correction entries with status and reason; outbound message logs; receiving-side display or audit records, where the lab can see them. State the retention of each. In U.S. clinical labs the report stage is fixed by rule, since 42 CFR 493.1291 requires both the original and the corrected report to be kept; say whether the lab records corrections with a status that separates a fix from new information, as the HL7 "corrected" and "amended" status codes do.
4. Agent map. For each system, what creates the version: a named technologist, an interface template, a device. The HL7 Provenance resource is a useful model, because it records the agents responsible for each version, whether people, organizations, software or devices. The lab does not need that standard; it needs to say whether its audit trail answers the same question.
Document 5: the acceptance check, written before review
Without a fixed check, "the interface did it" is an opinion. With one, anyone holding the step history can test the answer. The packet states, in advance:
- ☐The answer names exactly one step, or states that no step differs.
- ☐At the named step, the recorded value or unit first differs from the source reading.
- ☐Every earlier step matches the source reading.
- ☐The original and the corrected report are both retained.
- ☐The final corrected report is linked to the earlier versions, so the case has an outcome.
For the glucose example on the main guide, the correct answer is the third step, the interface engine: the analyzer and correction entry match, and the outbound message is the first to show the wrong unit. Cases that fail any condition stay out of the set, and the packet reports how many.
Documents 6 and 7: volume, span and rights
6. Volume and span. Corrected reports per month; the share involving a unit, reference range or mapping problem rather than a re-test; months of retained interface logs; dates of interface, template or system changes. Use ranges if exact counts would take a project to produce.
7. Rights and sensitivity note. Patient identifiers appear in every system, so name them by type. List clinician names, the interface vendor's terms and any client contracts that limit reuse, and name who can authorize a licensing discussion. The review of those terms happens with SourceX after the introduction; the introducer does not read the contracts.
Illustrative cover sheet
This cover sheet is fictional, for a 310-person regional clinical laboratory. It shows the expected level of detail.
| Field | Entry |
|---|---|
| Task | First step where value or unit differs from source reading |
| Systems | Analyzer, lab information system, interface engine, client record |
| Interface log retention | Outbound message content kept 18 months |
| Corrections | Roughly 150 per month; about one in ten involve a unit or range |
| Change control | Mapping changes ticketed for the last three years |
| Identifiers present | Patient name, date of birth, accession number, ordering clinician |
| Client terms | Hospital outreach contracts under review by counsel |
| Authorizer | CEO, with the laboratory director consulted |
Where interface logs tend to live is covered on integration error records. For framing the conversation with healthcare operators before any of this, see how advisors introduce healthcare administration clients. Eligibility still applies: 50 or more full-time employees at peak, documented 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. Other record families are listed under data types.
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 could fill most of the seven slots from what the lab already keeps, register as a partner, confirm the lab against who qualifies and read the terms, then introduce the CEO and let the lab prepare the packet with SourceX.