Trace diagnostic samples through collection and transport handovers
For Diagnostic/specialty operations director · Plan implementation
TL;DR — what you’ll learn
- Track custody events from collection to laboratory receipt using stable identifiers.
- Separate physical arrival from the laboratory's authorised acceptance decision.
- Keep missing acknowledgements and late offline scans visible.
- Test duplicates, corrections and interrupted synchronisation before connecting the workflow to the LIS.
A collection centre dispatches twelve samples. The receiving laboratory acknowledges eleven. The courier marks the trip delivered, so the transport dashboard turns green while sample S-12 remains unexplained.
Laboratory sample tracking should identify the last supported custody event for each sample and the owner of the next inquiry. A completed trip does not prove that every sample arrived or that the laboratory accepted it for testing.
Reconcile individual samples within the manifest
In this illustrative case, manifest M-07 contains S-01 through S-12. Eleven have receiving acknowledgements. S-12 has a dispatch event but no confirmed receipt. Report eleven received and one unresolved; do not create a twelfth receipt simply because the transport job closed.
Scroll horizontally to see all columns.
| Record | Minimum purpose in the pilot |
|---|---|
| Sample identity | Distinguish the sample without relying on a person's name |
| Order reference | Link the sample to the correct request |
| Custody event | Record source, destination, actor and event time |
| Manifest identity | Group the expected handover without replacing item-level identity |
| Laboratory decision | Preserve authorised acceptance, rejection or pending review |
The proposed pilot tracks custody evidence only. Labels, transport conditions, specimen suitability and laboratory acceptance must come from the laboratory’s approved procedures; the example does not prescribe them or infer suitability from a timestamp.
Put scans where responsibility changes
A scan is most useful when it corresponds to a real handover: collection-centre dispatch, courier custody or laboratory receipt. Scanning every few minutes without a clear event meaning creates more data without resolving responsibility.
MocDoc describes collection and rejection features. For the proposed pilot, ask the deployed LIS to demonstrate its actual sample/order identities, receiving events and correction path. A product description is not proof that the intended interface passes those tests.
Worked workflow
Original illustrative workflow. Follow the labelled transitions, including the exception paths.
- A · StepCollection centre records dispatch
- B · StepTransport custody acknowledgement
- C · DecisionExpected sample received
- D · StepCustody inquiry with last known event
- E · StepLaboratory records physical receipt
- F · DecisionAuthorised acceptance decision
- G · StepProceed through approved laboratory workflow
- H · StepLaboratory-owned exception
Scroll horizontally to see all columns.
| From | Condition | Next |
|---|---|---|
| A: Collection centre records dispatch | Continue | B: Transport custody acknowledgement |
| B: Transport custody acknowledgement | Continue | C: Expected sample received |
| C: Expected sample received | No | D: Custody inquiry with last known event |
| C: Expected sample received | Yes | E: Laboratory records physical receipt |
| E: Laboratory records physical receipt | Continue | F: Authorised acceptance decision |
| F: Authorised acceptance decision | Accepted | G: Proceed through approved laboratory workflow |
| F: Authorised acceptance decision | Rejected or uncertain | H: Laboratory-owned exception |
The inquiry should show who is responsible and when it was last updated. The laboratory acceptance queue remains separate from the courier's delivery-status screen.
Handle offline events without rewriting history
Suppose a receiving device records S-12 offline and uploads later. Preserve the event time and the time the server received it. The inquiry can then be resolved using the late evidence rather than pretending the central system knew the result earlier.
Give each event a stable identity and validate its sample, source and destination. Repeated uploads of the same scan should not create additional samples or custody movements. A contradictory late event requires review; a timestamp alone should not override a confirmed correction.
If a label is unreadable or missing, follow the laboratory's approved escalation procedure. The tracking tool must not generate a plausible identity or silently assign the sample to the nearest matching name.
Define the integration and fallback
Limit the first synthetic pilot to one collection centre and receiving laboratory. Before using real records, agree the minimum custody fields, transport labels, device access and retention with the responsible privacy and laboratory owners. Confirm supported interfaces instead of copying full clinical records into a tracking tool.
The pilot may create administrative custody events, subject to authorisation. It must not create clinical acceptance or release decisions. If the LIS is unavailable, retain the approved temporary manifest and queue the interface work. Reconcile any manual entry before replay so the recovery does not double-record the sample.
Test the twelve-sample manifest with one missing acknowledgement, a repeated scan, an unknown sample, a late offline receipt and an unauthorised device. Require all twelve samples to be accounted for as received or explicitly unresolved, and require no duplicates in the challenge set. Measure handover age and time to resolve missing evidence separately from clinical laboratory turnaround.
Test the clock and the identity independently
For synthetic S-12, use a dispatch event at 09:00, an offline receipt at 09:40 and server synchronisation at 10:10 on the same day and time basis. The physical handover interval is 40 minutes; the central system lacked that receipt evidence for a further 30 minutes. Reporting a single 70-minute “transport time” would mix transport and reporting delay. Neither interval establishes sample suitability.
Scroll horizontally to see all columns.
| Challenge | Expected tracking result |
|---|---|
| Offline receipt uploads twice | One receiving event, with duplicate delivery recorded or ignored according to the supported contract |
| Manifest lists a sample with no valid order link | Administrative exception; no guessed order association |
| Trip closes with eleven of twelve receipts | One unresolved sample remains visible |
| Receipt is confirmed but laboratory decision is pending | Custody complete; acceptance queue still pending |
Have collection and laboratory owners compare the twelve expected identifiers with the recorded outcomes, rather than accept a matching total alone. Twelve rows can still hide one duplicate and one missing sample. The LIS owner should verify the correction path and time-zone handling in the deployed configuration.
Use missing-handover age to manage the inquiry queue and synchronisation delay to manage the interface. Keeping the two measures separate helps the team fix the right handover without drawing a clinical conclusion from a transport event.
Next actions
- Agree custody events and identifiers with collection, transport and laboratory owners.
- Map the supported LIS interface and the offline reconciliation procedure.
- Run the missing-sample and replay cases before expanding beyond the first route.
Discuss this workflow
Discuss a sample-custody pilot for one collection route, including missing acknowledgements, offline scans and laboratory-owned acceptance.
Describe the operation using business information only. Please leave out patient details.
Applying this guide
The scenarios and numbers are illustrative. Confirm these provider-specific inputs before implementation:
- Laboratory director, quality manager and authorised acceptance staff: Current sample-handling SOPs and applicable requirements; this draft provides no transport parameters or clinical acceptance criteria.
- LIS vendor and integration lead: Versioned interface evidence and twelve-sample challenge set with duplicate, unknown and late events.
- Privacy lead, laboratory operations and logistics owner: Approved minimised data-flow and device/access/retention controls.
References
- MocDoc sample management — Advertised collection/tracking topics; not clinical sample criteria, accreditation or outcome evidence.
Topics: laboratory sample tracking · lab sample barcode tracking · sample chain of custody · collection centre logistics