Laboratory Intake Software: A Received Specimen Is Not an Accepted Specimen

A laboratory receiving a specimen has evidence of arrival, not automatic permission to analyse it. When the identity on a container differs from the accompanying request, a portal must not resolve the discrepancy by quietly copying whichever name looks more complete. Commission a workflow that preserves what arrived and routes the problem to the laboratory's authorised decision maker.

This guide concerns software requirements for specimen reception. It is not a specimen collection procedure, clinical advice or a universal acceptance policy. The laboratory must supply its current discipline-specific rules, responsible roles and approved handling instructions. A developer should not decide whether a particular patient sample can be used.

Connect the request to the actual received container

Consider a fictional laboratory receiving two containers with one request. An intake screen that marks the entire request “accepted” after the first barcode scan could hide a problem with the second container. Ask for a relationship between the request and each received specimen, with an individual review outcome where the laboratory requires it.

Preserve the identifiers actually observed on the container separately from the information supplied in the request. Record who identified a discrepancy and when. Do not make correcting the patient's general profile rewrite the historical intake evidence or imply that the physical label changed.

The precise fields and identification checks come from the laboratory. The software requirement is to make a difference visible and actionable, rather than inventing a supposedly universal number of identifiers or matching threshold.

Distinguish missing information from conflicting identity

The Homerton specimen acceptance guidance provides a concrete local example. It distinguishes unlabelled specimens, mismatches between patient names on specimen and request, other information mismatches, and an unsuitable specimen type or container. These are not interchangeable reasons for an intake problem.

In that guidance, specimens naming one patient while the request names another are rejected. Other information mismatches can be queried with the clinical area. The software should therefore not offer a single generic “fix details and proceed” button for every discrepancy.

Ask the laboratory to define the permitted next action for each relevant category. A reception user may record the issue without being authorised to resolve it. Keep the reason, the responsible reviewer and any outstanding contact visible. A missing reviewer response is an unresolved case, not tacit acceptance.

An exception needs a real decision, not a valuable-sample checkbox

Homerton describes individual senior consideration for certain precious unlabelled specimens, including conditions concerning provenance and contact with the requesting physician. That is a local professional exception, not permission for a portal user to bypass identification rules by selecting “irreplaceable”.

If your laboratory has an approved exception process, model its actual evidence and authorisation requirements. Record the specimen concerned, the identified problem, the person making the decision and the outcome they approved. The system must preserve the original discrepancy even when further processing is authorised.

Do not turn the cited example into a rule for every discipline, another organisation or a different country. In particular, do not infer that transfusion specimens share the same exception route. Require the laboratory to approve the boundaries before implementation.

Keep a repeat request distinct from relabelling the original

The Homerton guidance says that when a clinical area reports a mislabelled specimen, returning it for relabelling is not possible under the described policy; a repeat specimen is required. A customer-facing correction form must not silently promise the opposite.

Where the laboratory requests a repeat, retain the original intake record and create a separately identifiable follow-up. Link a later specimen to that request without replacing the original label evidence or making the new arrival appear to be the old container. Track the requested action and actual receipt independently.

Physical storage, disposal and any urgent clinical escalation remain subject to the laboratory's approved procedures. Do not implement automatic disposal or a clinical delay tolerance from this commissioning guide. An administrative status must not instruct staff to improvise specimen handling.

Accept the workflow with deliberately conflicting examples

Use fabricated training records to demonstrate a clear match, a missing label, a conflicting patient name, a different information discrepancy and an unsuitable container. Include an exception awaiting senior review, an authorised outcome and a requested repeat that has not arrived. Expected actions must be supplied by the laboratory.

Check that reception cannot overwrite the original evidence, an unresolved case cannot look accepted, and a repeat remains distinguishable from the first specimen. Put these behaviours in your application acceptance criteria.

For a business-app discussion, bring a sanitised intake example and the approved decision process, not real patient records. The useful deliverable is a traceable reception and review handoff, not software that claims to establish specimen identity or clinical suitability on its own.