WHEN AUDIT IS PARAMOUNT

Every packed kit.
Its own lifecycle assembly UID.

A kit may be processed many times. SurgiDat gives every newly packed assembly its own unique identity, so audit and tracing can follow a specific processing lifecycle rather than relying only on the reusable kit number.

PHYSICAL KIT IDENTITYKIT-DEMO-01

Identifies the reusable child kit, with its own kit code, serial and alternate identifiers.

PACKING LIFECYCLE AASM-DEMO-001

The assembly UID identifies this specific packing and its downstream journey.

PACKING LIFECYCLE BASM-DEMO-002

When the kit is packed again, a new assembly UID identifies the next lifecycle.

Illustrative identifiers, not actual facility records.

WHAT THE IDENTITY CONNECTS

A precise starting point
for following the record.

01

Packing & exceptions

Find the specific assembly created during packing and the recorded count and missing-instrument information for that packing event.

02

Processing & release

Follow the assembly to its sterilizer load and cycle, then review the related release or biological quarantine record where required.

03

Location & case allocation

Trace recorded stock location and allocation to an OR case. A patient link reflects recorded case allocation; it does not by itself prove clinical use.

WHY THIS MATTERS IN AN AUDIT

Trace the right event.
Keep separate journeys distinct.

The reusable kit identity gives continuity across many uses. The lifecycle assembly UID gives specificity within one packing and processing journey.

“Which packing are we reviewing?”

Start with the assembly UID to identify the specific lifecycle. Repacking the same kit creates a different assembly identity.

“Which load processed this assembly?”

Follow the assembly’s load association and review the load record, cycle and relevant release or quarantine details.

“Which assemblies were associated with this load?”

Search by sterilizer load to find associated assemblies, then follow recorded lifecycle, patient allocation and stock-location information.

“Where did it go after processing?”

Use recorded distribution and case allocation to trace the handoffs captured in SurgiDat, with assembly detail and CSV exports for review.

THE LIFECYCLE BOUNDARY

Return closes one journey.
Repacking starts another.

Receiving an assembly UID in decontam ends that assembly’s sterile-processing life. That decontaminated assembly cannot be packed, sterilized, stocked or picked to a case.

The reusable kit can go through preparation and packing again, creating a new assembly UID. Changing a kit’s serial or alternate number does not rewrite assemblies already packed.

Traceability depends on the scans, counts, results and handoffs recorded by the team. The unique assembly UID is the link that keeps each lifecycle identifiable.

SEE THE RECORD, NOT JUST THE NUMBER

Bring an audit question
to your walkthrough.

We can follow a sample assembly through packing, processing, stock, case allocation and return—and show how to search from an assembly UID, kit, load, patient or location.

Explore audit & tracing ↗
START WITH YOUR WORKFLOW

Make readiness
everyone’s business.

Let’s walk through your process, your pressure points,
and what a connected workflow could look like.

Explore SurgiDat with us ↗

Crawler-visible interactive content

This section expands JavaScript-driven demos and filters so crawlers can index the full workflow text.

mobile-nav-toggle

Opens and closes the main navigation on small screens.