Standard 6 — Pre-Examination: Specimen Pathway
Criteria in this standard
6.2 — Specimen Labeled at the Point of Collection
6.3 — Rejection Criteria, Applied Consistently
6.4 — Transport Conditions Preserve Specimen Integrity
6.5 — Chain of Custody for Forensic or Legal Specimens
6.6 — Specimen Accessioning Logged in Real Time
6.7 — Urgent/STAT Specimens Prioritized and Tracked
6.8 — Specimen Retention Before Discard
Two-Identifier Patient Verification
Non-Negotiable
In plain terms: The collector genuinely confirms who the patient is, using two real identifiers, every single time — not a quick glance or a question nobody actually waits to hear answered properly.
| Facility category | Standalone lab | Hospital lab | Clinic lab |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
Patient misidentification at collection is one of the most consequential, entirely preventable errors a laboratory can make — a specimen correctly processed but drawn from the wrong patient produces a result that is perfectly accurate for someone else’s blood and dangerously wrong for the patient it’s reported against. The failure is rarely dramatic; it is usually a rushed, routine moment where a name is spoken as a statement rather than genuinely confirmed.
What good looks like
- Two genuine identifiers are actively checked, every time.
- Room or bed number is never used as one of the identifiers.
- A real, documented alternative exists for patients who cannot verbally confirm identity.
Common failure modes
- A name is stated and the patient’s silence or nod is treated as confirmation.
- Room number is used as a de facto second identifier.
- No defined process exists for unconscious or language-barrier patients.
Worked example
If you are starting from zero — do this first
- Observe actual collections today — is verification active or passive?
- Build a required verbal script asking patients to state their own identifiers.
- Define a specific alternative process for patients who cannot verbally respond.
Self-assessment questions
Evidence: Direct observation during survey
Evidence: Collection SOP, direct observation
Evidence: Written alternative identification procedure
Evidence: Staff interview
Common reasons for a PARTIAL answer
- Verification happens but is passive — confirming a stated name rather than asking the patient to state it.
- No written alternative exists for patients who can’t verbally respond.
Implementation plan
| When | What |
|---|---|
| Week 1 | Observe current collection practice for active versus passive verification. |
| Week 2 | Build a required verbal script and retrain collection staff. |
| Week 3 | Write the alternative procedure for non-verbal patients. |
| Ongoing | Spot-check live collections periodically. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| OBSERVE | Live collection observation | Directly observes collections to confirm active, two-identifier verification is genuinely performed. |
Evidence base
Specimen Labeled at the Point of Collection
Non-Negotiable
In plain terms: The label goes on the tube right there, with the patient still present — never later, from memory, after moving on to someone else.
| Facility category | Standalone lab | Hospital lab | Clinic lab |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
Delayed or batch labeling is one of the most well-documented, preventable causes of specimen mix-up in laboratory medicine. Even a short delay across two or three patients collected in quick succession creates a real window for confusion — tubes look alike, memory is fallible under time pressure, and the consequence of a mix-up is a result reported under the wrong patient’s name.
What good looks like
- Labeling is observed happening at bedside or chairside, before moving on.
- No workflow exists where multiple specimens are collected before any labeling.
- Labels carry enough information for independent re-verification.
Common failure modes
- Pre-printed labels are applied later, away from the patient.
- Several specimens are collected in sequence before any are labeled.
- Labels carry only a name, with no date/time or second identifier.
Worked example
If you are starting from zero — do this first
- Check whether any current workflow allows multiple collections before labeling.
- Build an explicit rule: label before moving on, no exceptions, including off-site collection.
- Check label content includes enough information for independent verification.
Self-assessment questions
Evidence: Direct observation
Evidence: Workflow review, including off-site collection
Evidence: Label content review
Common reasons for a PARTIAL answer
- In-facility labeling is correct, but off-site or home-visit collection has a separate, uncontrolled workflow.
- Labels carry a name but lack a second identifier or timestamp.
Implementation plan
| When | What |
|---|---|
| Week 1 | Review all collection workflows, including off-site, for labeling timing. |
| Week 2 | Build an explicit point-of-collection labeling rule covering every workflow. |
| Week 3 | Retrain all collection staff, including off-site teams. |
| Ongoing | Spot-check labeling practice periodically, including off-site visits. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| OBSERVE | Live collection observation | Observes the actual timing of specimen labeling relative to collection and patient departure. |
Evidence base
Rejection Criteria, Applied Consistently
Non-Negotiable
In plain terms: A bad specimen gets rejected every time, by the same rules — even when it was hard to get, and even when someone’s pushing for a fast result.
| Facility category | Standalone lab | Hospital lab | Clinic lab |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
Rejection criteria exist precisely because certain specimen conditions make a result unreliable regardless of how urgently it’s needed or how difficult the specimen was to collect. The moment exceptions begin — “just this once, the patient was a hard draw” — the criteria stop functioning as genuine safeguards and become guidelines applied only when convenient, which defeats their purpose entirely.
What good looks like
- Staff can describe rejection criteria without needing to look them up.
- A documented instance exists of rejection holding despite clinical pressure.
- Rejections are logged with reason and communicated to the requesting clinician.
Common failure modes
- Criteria exist on paper but staff don’t actually know them.
- Difficult-to-obtain specimens are quietly accepted despite not meeting criteria.
- Rejected specimens are silently discarded with no clinician notification.
Worked example
If you are starting from zero — do this first
- Confirm written rejection criteria exist and staff can describe them unprompted.
- Check recent records for any instance of criteria being bypassed under pressure.
- Build a fast notification process so rejection doesn’t feel like it’s only causing delay.
Self-assessment questions
Evidence: Staff interview
Evidence: Rejection log
Evidence: Rejection log with clinician notification record
Common reasons for a PARTIAL answer
- Criteria are applied inconsistently for difficult-to-obtain specimens.
- Rejections happen but aren’t consistently communicated back to clinicians.
Implementation plan
| When | What |
|---|---|
| Week 1 | Confirm written rejection criteria are current and complete. |
| Week 2 | Brief all staff and reinforce no-exception application. |
| Week 3 | Build a fast clinician notification process for rejections. |
| Ongoing | Review rejection log periodically for consistency. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| ASK | Staff knowledge check | Asks staff to describe rejection criteria without reference material. |
| DOCUMENT | Rejection log review | Reviews rejection log entries for consistency and clinician notification. |
Evidence base
Transport Conditions Preserve Specimen Integrity
Non-Negotiable
In plain terms: Specimens that need special handling during transport actually get it, verified — not just assumed because a cooler bag was used.
| Facility category | Standalone lab | Hospital lab | Clinic lab |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
An insulated transport container is a tool, not a guarantee — without actual verification, a cooler bag left in a hot vehicle for an extended period can still fail to maintain required temperature, and nobody would know unless conditions are genuinely checked rather than assumed from the equipment used. Time-sensitive analytes are particularly vulnerable to this gap, since degradation can occur without any visible sign in the specimen itself.
What good looks like
- Transport temperature is actually verified, not assumed from container type.
- Time from collection to receipt is tracked for time-sensitive analytes.
- Out-of-condition specimens have a documented effect on interpretation or rejection.
Common failure modes
- An insulated bag is used with no actual temperature verification.
- No timestamp exists at both collection and receipt for time-sensitive tests.
- A noted condition breach has no consequence for how the result is used.
Worked example
If you are starting from zero — do this first
- Identify every specimen type with specific transport requirements.
- Introduce actual temperature verification, not just an insulated container.
- Add collection and receipt timestamps for time-sensitive analytes.
Self-assessment questions
Evidence: Transport temperature log
Evidence: Collection and receipt timestamps
Evidence: Impact assessment record
Common reasons for a PARTIAL answer
- A cooler or insulated bag is used but temperature is never actually checked.
- Timestamps exist at collection but not at receipt, or vice versa.
Implementation plan
| When | What |
|---|---|
| Week 1 | Identify transport-sensitive specimen types and their requirements. |
| Week 2 | Introduce temperature logging in transport containers. |
| Week 3 | Add collection/receipt timestamping where missing. |
| Ongoing | Review transport condition logs periodically for trends. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Transport log review | Reviews temperature logging and timestamp records for transported specimens. |
Evidence base
Chain of Custody for Forensic or Legal Specimens
Core
In plain terms: For legally sensitive specimens, there’s a complete paper trail showing exactly who had the specimen and when, with no gaps, from start to finish.
| Facility category | Standalone lab | Hospital lab | Clinic lab |
|---|---|---|---|
| Applicability | Where applicable | Where applicable | Where applicable |
Why this matters
A single gap anywhere in a chain-of-custody record — a handoff with no signature, a storage period with no logged access control — can undermine the legal validity of the specimen and its result entirely, regardless of how carefully every other step was handled. This is a case where a process that is otherwise rigorous but incomplete in just one link fails the whole purpose of the requirement.
What good looks like
- Every transfer point requires a signature, with no gaps.
- Chain-of-custody specimens are physically secured differently from routine ones.
- Staff receive training specific to chain-of-custody requirements.
Common failure modes
- Some transfer points are signed, others informally skipped.
- Specimens sit in the same open rack as routine specimens.
- Staff apply routine handling training to chain-of-custody specimens by default.
Worked example
If you are starting from zero — do this first
- Map every handoff point a chain-of-custody specimen passes through, including internal ones.
- Check for any point currently missing a signature requirement.
- Set up separate, secured storage for these specimens.
Self-assessment questions
Evidence: Chain-of-custody form
Evidence: Secure storage inspection
Evidence: Chain-of-custody-specific training record
Common reasons for a PARTIAL answer
- External transfers are signed but internal transfers are skipped.
- No separate secure storage exists for these specimens.
Implementation plan
| When | What |
|---|---|
| Week 1 | Map all handoff points including internal transfers. |
| Week 2 | Close any signature gaps found. |
| Week 3 | Establish separate secure storage and specific staff training. |
| Ongoing | Audit chain-of-custody records for completeness on every case. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Chain-of-custody record review | Reviews a recent custody record for an unbroken chain of signatures at every transfer point. |
Evidence base
Specimen Accessioning Logged in Real Time
Core
In plain terms: When a specimen actually arrives, that moment gets logged right then — the timestamp isn’t quietly adjusted to look tidier later.
| Facility category | Standalone lab | Hospital lab | Clinic lab |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
An accessioning timestamp that mysteriously always matches the expected collection time, with no natural variation, is a signal of backdating rather than genuine real-time logging — and it distorts every downstream turnaround-time metric built on that timestamp, hiding exactly the delays the laboratory most needs visibility into to improve its own process.
What good looks like
- Accessioning timestamp reflects genuine receipt time, with natural variation.
- No meaningful backlog of unaccessioned specimens exists.
- Any record can be retrieved immediately for a selected specimen.
Common failure modes
- Timestamps are manually entered to match the requested collection time.
- A backlog of specimens sits unaccessioned during busy periods.
- Records require reconstruction rather than immediate retrieval.
Worked example
If you are starting from zero — do this first
- Check whether current accessioning timestamps show natural variation or suspiciously always match collection time.
- Consider automated scanning at the point of physical receipt if currently manual.
- Check for any backlog of unaccessioned specimens right now.
Self-assessment questions
Evidence: Timestamp cross-check against courier or transport log
Evidence: Accessioning backlog check
Evidence: Live record retrieval
Common reasons for a PARTIAL answer
- Manual entry during busy periods introduces inaccurate timestamps.
- A regular backlog exists during predictable peak volume times.
Implementation plan
| When | What |
|---|---|
| Week 1 | Review current accessioning timestamp accuracy. |
| Week 2 | Consider automated scanning if accuracy is a genuine issue. |
| Week 3 | Address any identified backlog pattern during peak periods. |
| Ongoing | Periodically cross-check timestamps against an independent record. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Timestamp cross-check | Compares accessioning timestamps against an independent record for genuine correlation. |
Evidence base
Urgent/STAT Specimens Prioritized and Tracked
Core
In plain terms: STAT specimens genuinely jump the queue, in a way that actually changes how fast they get processed — not just a sticker that doesn’t change anything.
| Facility category | Standalone lab | Hospital lab | Clinic lab |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
A STAT flag that doesn’t genuinely change a specimen’s position in the processing queue is worse than no flag at all — it creates false confidence among requesting clinicians that urgency is being honored, when in practice nothing operational has changed. Real STAT prioritization requires both a physical or digital mechanism that actually alters processing order and ongoing tracking to confirm it’s working as intended.
What good looks like
- A visible flagging system genuinely changes processing priority.
- STAT turnaround time is actually tracked against a defined target.
- Missed STAT targets are logged and reviewed as quality events.
Common failure modes
- A “STAT” label exists but doesn’t change actual queue position.
- Turnaround time is tracked for routine specimens but not specifically for STAT.
- Missed STAT targets go unreviewed with no follow-up.
Worked example
If you are starting from zero — do this first
- Check whether your current STAT flag actually changes processing order in practice.
- Set a specific, defined STAT turnaround-time target.
- Build a tracking and review mechanism for STAT performance.
Self-assessment questions
Evidence: Observed prioritization in practice
Evidence: STAT turnaround data
Evidence: Quality event log
Common reasons for a PARTIAL answer
- A flagging system exists but doesn’t genuinely alter processing order.
- Turnaround is tracked but missed targets aren’t reviewed.
Implementation plan
| When | What |
|---|---|
| Week 1 | Observe whether current STAT flagging actually changes processing order. |
| Week 2 | Set a specific turnaround target and build genuine prioritization. |
| Week 3 | Build tracking and a review process for missed targets. |
| Ongoing | Review STAT performance monthly. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| OBSERVE | Processing flow observation | Observes whether a flagged STAT specimen genuinely moves ahead in actual processing order. |
Evidence base
Specimen Retention Before Discard
Standard
In plain terms: Tested specimens are kept around for a sensible amount of time afterward, so a repeat test can happen without making the patient come back.
| Facility category | Standalone lab | Hospital lab | Clinic lab |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
Different analytes genuinely have different stability profiles, which means a single blanket retention period applied regardless of test type will be either unnecessarily long for some specimens or too short for others. Retention that’s genuinely matched to each test’s real needs, with storage conditions that preserve the specimen appropriately, is what actually makes repeat testing possible rather than only theoretically available.
What good looks like
- A written schedule varies retention period genuinely by test type.
- Storage conditions actually match what each retained specimen requires.
- A specific retained specimen can genuinely be located and retrieved.
Common failure modes
- One blanket retention period is applied regardless of analyte stability.
- Retained specimens are stored in conditions that don’t match their requirements.
- Retention exists in policy but retrieval in practice proves difficult.
Worked example
If you are starting from zero — do this first
- Check whether your current retention period is genuinely analyte-appropriate, not one blanket figure.
- Confirm storage conditions actually match what each retained specimen type needs.
- Test retrieval of a specific older retained specimen.
Self-assessment questions
Evidence: Test-specific retention schedule
Evidence: Storage condition inspection
Evidence: Retrieval test
Common reasons for a PARTIAL answer
- A single retention period is applied regardless of analyte-specific stability.
- Retrieval in practice is slower or less reliable than the policy implies.
Implementation plan
| When | What |
|---|---|
| Week 1 | Review analyte-specific stability data for major test types. |
| Week 2 | Build a test-type-specific retention schedule. |
| Week 3 | Match storage conditions to each retention category. |
| Ongoing | Test retrieval periodically to confirm practical reliability. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| ASK | Retrieval test | Requests retrieval of a specific retained specimen and times the result. |