ISO 15189: Sample Traceability and What an Assessment Asks
What ISO 15189 expects a laboratory to show about a specimen — identity, chain of handling, timings — plus who accredits you and why no software is certified.
Ask a laboratory about sample traceability and you usually get shown a barcode printer. Barcodes are how traceability is made practical, but they are not what is being asked for. What is being asked for is the ability to reconstruct, long after the fact, what happened to one specimen: who it came from, when it was taken, when it arrived, what condition it was in, who handled it, what was measured, and who released the result.
The chain an assessor will follow
An assessment rarely audits a system in the abstract. It picks a report, usually one you did not choose, and walks backwards. Every link below is a place the walk can stop.
| Link | What must be recoverable | Where it usually breaks |
|---|---|---|
| Request | Who requested the test, and what was requested | Verbal add-ons that were never written down |
| Identity | The patient, unambiguously, and the specimen’s unique identifier | Two patients with the same name and no second identifier |
| Collection | Date, time and who collected it | Time recorded as the registration time rather than the collection time |
| Transport | When it arrived, and in what condition | Receipt time not recorded at all, so a delay cannot be assessed |
| Acceptance | Whether it met acceptance criteria, and what happened if not | Rejections handled by conversation and a fresh sample, leaving no record |
| Examination | What was measured, on what instrument, by which method | Instrument not recorded, so a later problem cannot be scoped |
| Verification | Who released the result, and when | A shared login, which makes "who" unanswerable |
| Amendment | Any change after release, with the original still visible | A corrected value overwriting the first one |
The three that catch most laboratories
Two timestamps collapsed into one
Collection time and receipt time answer different questions, and a system that records only one makes an entire category of investigation impossible. If a potassium looks wrong, the first question is how long the sample sat before it was processed. With one timestamp there is no answer.
The shared login
Nothing dissolves traceability faster than one account used by the whole bench. Every verification is then attributable to everybody, which is to say nobody. Individual accounts are not a security nicety here; they are what makes the verification record mean anything.
Amendments that erase
When a released result is corrected, both versions have to remain. A system that overwrites leaves you unable to show what was originally reported — which is precisely what an assessor asks when a correction is found.
Who applies the standard where you are
The standard is international; the body that assesses you is national. Which one applies is a question of where your laboratory operates, not of where your software was written.
| Country | Body | Note |
|---|---|---|
| United Kingdom | UKAS | The national accreditation body |
| Kenya | KENAS | State corporation; also holds international MRA recognition |
| South Africa | SANAS | The only recognised accreditation body in the Republic; accreditation is voluntary |
| Nigeria | MLSCN | Also registers laboratories and licenses practitioners |
| India | NABL | Applies ISO 15189 under its own criteria document |
Note the South African case in particular: accreditation there is voluntary rather than a precondition of operating, which changes the commercial argument for pursuing it — it becomes a signal to referrers and funders rather than a licence.
What software should do, and what it cannot
Software can make the record automatic rather than remembered: separate timestamps captured as events rather than typed, a specimen identifier that follows the tube, per-user accounts with an audit trail, results versioned rather than replaced, and the instrument recorded against the measurement. SamLab does these, and its analyzer integration explains how the analyzer side records which instrument produced a result.
What software cannot do is decide your acceptance criteria, train the person collecting the sample, or make a rejection get recorded when the easier thing is to ask for another tube. Accreditation is granted to the laboratory, never to a product; the software’s job is to make the honest record the path of least resistance.
Frequently asked questions
Which body accredits medical laboratories in my country?+
It is national. UKAS in the United Kingdom, KENAS in Kenya, SANAS in South Africa, MLSCN in Nigeria and NABL in India all apply ISO 15189 under their own schemes. Confirm scope and current requirements with the body itself rather than with a software vendor.
Is ISO 15189 accreditation compulsory?+
It depends on the country. In South Africa it is explicitly voluntary rather than a precondition of operating, so the case for it rests on referrer and funder confidence. Elsewhere it may be tied to licensing or reimbursement. Ask your national body — the answer changes the business case, not just the paperwork.
Does ISO 15189 require barcodes?+
It requires unambiguous identification and traceability, not a specific technology. Barcodes are how most laboratories achieve it at reasonable cost and error rate, but a rigorous manual system can satisfy the same requirement — it is simply much harder to sustain.
Can software be ISO 15189 certified?+
No. ISO 15189 accredits laboratories, through a national accreditation body. A product cannot hold the accreditation; it can only make the evidence straightforward to produce. Treat any vendor claiming otherwise with care.
Why do collection and receipt times both matter?+
They answer different questions. Collection time anchors the result to the patient’s state; receipt time, compared against it, is how you assess whether the specimen was still fit to test. A single timestamp makes delay-related investigation impossible.
Keep reading
- NABL Report Format: Every Field, and Why Each One Is There
A NABL report is not a design problem. It is a list of facts an assessor expects to find, laid out so a clinician can read it quickly.
- LIMS Software in India: What Labs Search vs What They Need
Most Indian labs typing "LIMS" are running a diagnostic lab, and a diagnostic lab wants a LIS. Buying the wrong category is expensive in a specific way.
- ASTM, HL7 and LIS2-A2: How Analyzers Talk to Software
Analyzer integration sounds like magic and is mostly two standards, a cable and a field map. Knowing which is which makes vendor conversations much shorter.