This scorecard belongs to error localization, which traces one corrected glucose result through four systems. Here the task is deciding whether a specific laboratory is worth introducing for this kind of record, and how confident to be.
How the rating works
Count strong answers out of eight. Borderline answers do not count toward the total but are written down, because they become the open items in the introduction. Three criteria are gates: if size, rights or the authorized contact is weak, stop and resolve it first.
| Strong answers | Zone | What it means |
|---|---|---|
| 6 to 8 | Strong | Correction histories likely show each hop; introduce and list the borderline items |
| 3 to 5 | Borderline | Quality records exist, but one hop may be invisible; introduce only with the gaps named |
| 0 to 2 | Weak | The lab has quality data, not localized errors; wait |
The criteria lean on what regulation already fixes. Under 42 CFR 493.1291, a U.S. laboratory that finds an error in a reported result must issue a corrected report and keep duplicates of both the original and the corrected report. Under 42 CFR 493.1105, it must be able to retrieve original, preliminary and corrected reports for at least 2 years after reporting, and pathology reports for at least 10. So the report side is often strong by default. The interface side is not regulated in the same way, which is why it gets its own row.
Eight criteria, applied to a correction history
The generic screen is in the company qualification checklist. This version applies it to laboratory corrections.
| Criterion | Strong | Borderline | Weak | Who answers |
|---|---|---|---|---|
| Company size (gate) | Well over 50 full-time employees at peak | Near 50 | Under 50 full-time, or mostly contractors | CEO or HR |
| Operating history | Several years in one lab information system | Years split by a system replacement | Recently opened | Laboratory director |
| Rights (gate) | Lab owns its records; client and vendor terms known | Some client or interface vendor contracts unreviewed | A hospital client or parent controls the records | CEO or counsel |
| Original and reason kept | Each corrected report keeps the original, a status and a reason | Original kept; reason in free text | Original overwritten | Quality manager |
| Hop linkage | One accession or result ID across analyzer, lab system, interface and receiving record | ID shared by some hops | No common key | IT lead |
| Interface log retention | Outbound message content kept a year or more | Kept for weeks, or receipts only | Not kept | Integration team |
| Mapping change control | Unit, range and template changes dated and tied to a ticket | Changes dated, no ticket | Undocumented | IT lead |
| Authorized contact (gate) | Named executive over the records | Senior contact, authority unconfirmed | Nobody identified | CEO |
Two standards help an introducer recognize a strong answer. FHIR, the HL7 exchange standard, separates a result marked "corrected" to fix an error from one "amended" with new information, so a lab that records this distinction is telling you why each change happened. FHIR's Provenance resource records which person, software or device created or revised each version; a lab with audit trails of that kind scores well on the original-and-reason row even if it does not use FHIR.
Outside the U.S., Canada and the EU, add English share as a gate. 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.
Three Illustrative laboratories, rated
All three are fictional.
| Criterion | 450-person clinical reference lab | 120-person veterinary diagnostics lab | 75-person food testing lab, India |
|---|---|---|---|
| Company size | Strong | Strong | Strong |
| Operating history | Strong | Strong | Borderline |
| Rights | Borderline | Strong | Weak |
| Original and reason kept | Strong | Borderline | Borderline |
| Hop linkage | Strong | Strong | Weak |
| Interface log retention | Strong | Weak | Weak |
| Mapping change control | Borderline | Borderline | Weak |
| Authorized contact | Strong | Strong | Borderline |
| Strong answers | 6 of 8, strong | 5 of 8, borderline | 1 of 8, weak; rights gate failed |
The reference lab archives outbound HL7 messages for three years and links every hop by accession number. Rights are borderline because several hospital clients have contracts nobody has read for data-use terms, and mapping changes are dated but not ticketed.
The veterinary lab is strong on structure, but its interface engine purges message logs after 30 days, so the one hop that most often explains a cross-system error survives only for recent cases.
The food testing lab issues reports in English and Hindi, so the 70% English rule is in doubt, and its manufacturer clients own the results under contract. It has good quality habits; it does not have localizable errors it can license today.
Five questions that change a rating
Ask in this order, and listen for numbers and system names rather than "a few" or "our system".
- How many corrected reports a month, and how many involve a unit, range or mapping problem rather than a re-test? Moves the original-and-reason row.
- Is the original kept alongside each corrected report, with the reason recorded? Keeping both is required for U.S. clinical labs; the reason is what makes a case usable.
- Can you see the value at each system it passes through, including the interface engine, and for how long? Moves linkage and log retention.
- When a mapping or template changes, is that change dated and tied to a ticket? Decides whether cases before and after a fix can be separated.
- Who owns the laboratory, interface and client-facing systems, and who can authorize a licensing discussion? Moves both gates; the laboratory director and COO usually own the records, and the CEO authorizes the discussion.
Weak answers to two of questions 1 to 3 usually mean the lab has quality data but not localized errors in the sense a buyer would test. Where interface logs live is covered on the integration error records page; what to inventory before a system replacement is in lab result correction histories; non-clinical labs are covered on the testing laboratory industry page.
What the rating cannot settle
The rating records what the lab says. It cannot show how many cases pass a fixed acceptance check, how patient identifiers at each hop would be de-identified, whether client or interface vendor contracts permit use, or whether any buyer wants this task. Those are settled in SourceX's review with the company. The evidence gaps analysis shows how to word borderline rows, and the review packet list shows what the lab prepares later. For the broader introducer role, see the business introducer guide to operational data licensing; other record families are 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 laboratory reaches the strong or borderline zone with all three gates passed, register as a partner, check it against who qualifies and read the terms before you introduce the CEO or COO.