Back to OmniTrace

END-TO-END BIOLOGICAL SAMPLE TRACEABILITY

Every sample.
One identity.
Complete traceability.

BioSampleTrace creates a controlled digital chain between the hospital and external laboratory, from registration and labeling through dispatch, processing and secure return of results.

Unique Sample CodeChain of CustodyPrivacy by Architecture
Sample Tracking● LIVE
SAMPLE CODEBST-26-08F4A91C
|||| ||| || |||| | ||| || ||||
✓RegistrationHospital · 08:42
✓LabelingBarcode generated · 08:44
✓DispatchDispatch list #184 · 10:12
4Laboratory receiptProcessing · 11:03
5ResultPending
Hospital→Secure Exchange→External Laboratory→Clinical Result

THE TRACEABILITY GAP

The sample moves physically.
Its information must follow it.

When transfers between hospitals and external laboratories rely on paper, telephone calls and disconnected systems, the actual status of a sample cannot be readily verified.

01

Loss of visibility

There is no unified view of where the sample is or who received it.

02

Disconnected handovers

Dispatch lists, laboratories and results function as separate processes.

03

Delays

A delay is identified only when someone searches for a sample or result.

04

Incomplete audit trail

Establishing who did what and when requires manual investigation.

BIOSAMPLETRACE PLATFORM

The physical journey becomes a digital chain of custody.

Each sample receives a unique code and follows controlled status transitions. The physical sample stays connected to the proper workflow without sending patient identifiers to the external environment.

  • Server-generated unique Sample Code
  • Barcode / QR labeling and printing
  • Dispatch lists and receipt confirmation
  • Role-scoped access and audit history
  • Controlled return of results
DIGITAL SAMPLE IDENTITY
UNIQUE SAMPLE CODEBST-26-08F4A91C
||||| || ||| | |||| || ||| ||||
ORIGINHospitalSTATEDispatchedDESTINATIONExternal Lab

SAMPLE LIFECYCLE

From registration to result.
Every transition is recorded.

01+

Registration

Register the examination and create a Sample Code.

02▦

Label

Connect barcode / QR to the physical sample.

03⇢

Dispatch

Dispatch list and controlled shipment.

04✓

Lab Received

Confirm physical receipt.

05⌁

Processing

Update operational status.

06PDF

Result

Secure return of results.

Exception handlingRejected sample→Mandatory reason→Audit event→Hospital notification

PRIVACY BY ARCHITECTURE

Patient information remains within the hospital environment.

The external workflow relies on the operational identity of the sample, not the patient's identity.

TRUST ZONE A

Hospital Environment

PatientAMKAClinical DataDoctorExamination

Identifiers and clinical information remain in the internal system.

⌾SECURE EXCHANGESampleCodeExam TypeStatusOperational MetadataNO PATIENT IDENTIFIERS
TRUST ZONE B

External Laboratory

Sample CodeProcessingStatusResult

The laboratory uses a coded sample identity.

ROLE-BASED OPERATIONS

The right information for the right role.

Access is restricted by organization, clinic, physician, laboratory and operational responsibility.

S
SECRETARIAT

Secretariat

Sample registration, codes, dispatch lists and status.

D
DOCTOR

Physician

Their examinations, history and available results.

A
ADMINISTRATION

Administration

Aggregated KPIs and statistics without access to clinical PDFs.

L
EXTERNAL LAB

Laboratory

Receipt of dispatched samples, status and return of results.

External Laboratory Portal● ONLINE
Sample codeStatus: All
SampleExamReceivedStatus
…A91CEX-10411:03Processing
…70F2EX-22110:48Completed
…1D83EX-10410:17Processing

EXTERNAL LABORATORY PORTAL

The laboratory sees only what it needs to process.

The laboratory queue contains only samples actually dispatched to it. Creating an examination in the hospital does not constitute dispatch.

  • Confirm physical receipt
  • Status by Sample Code
  • Reject with a reason
  • Controlled delivery of results

SECURE RESULT DELIVERY

The result returns to where it belongs.

Results follow a controlled path back to the hospital and become available to authorized users in the internal environment.

External Lab→Secure Exchange→Hospital→Authorized Doctor
PDFRESULT DOCUMENTSecure clinical resultControlled access · Audit logged✓

ENTERPRISE ARCHITECTURE

Separate systems.
Controlled exchange.

HOSPITAL / ON-PREMISE

Hospital Application

ASP.NET CoreSQL ServerIdentity & RBACPrint / PDF Services
⇄API
CONTROLLED BOUNDARY

Secure Exchange

Sample identityStatus eventsOperational metadataResult transport
⇄API
EXTERNAL

Laboratory Portal

Dispatch queueReceiptProcessingResults

OPERATIONAL VALUE

From “where is it?” to “we know precisely.”

01

Traceability

Unique identity and history for every sample.

02

Fewer errors

Controlled workflows instead of disconnected entries.

03

Data protection

Separation of hospital data and external workflows.

04

Management oversight

KPIs, turnaround times and aggregate reports.

BIOLOGICAL SAMPLE TRACEABILITY INFRASTRUCTURE

From sample to result — one controlled digital chain.

Presentation of the platform, architecture and implementation model.

Request a demo ↗