Specimen Tracking James R. Pomicter, BS,MLS(ASCP) jamespo@softcomputer.com - PowerPoint Presentation

Specimen TrackingJames R. Pomicter, BS,MLS(ASCP)jamespo@softcomputer.com 1

Goals of Client Specimen Tracking SetupPhysical whereabouts of patient sampleOrganize workflow - ActionsDecrease/eliminate lost samplesProvide accurate data for TAT statistics

Manually Track…The status and location of every specimen.To storage areas, with rack# and position.Workstation RedirectionsList Track…Specimen manifests between sitesOld storage racks to discardAutomatically Track… Location of Collecting, Receiving, and Cancelled events Remote Receiving (At intermediate stops) To instrumentsTo Reference Labs What Can It Do?

Workflow DetailsWith basic workflow details may be added that will help you to determine how ST will be able to help.

Drawing a flowchart will help clients identify what stops are needed Workflow SLAB processing MLAB processing WLAB processing REF1 REF2 Draw Station Nursing Home Fridge Fridge Fridge Freezer Freezer Freezer Trash CHM CHM CHM HEM HEM HEM MIC SERO

3 Terms for Every Track…….Specimen Tracking Vocabulary…Status: Single character code to describe what is happening to the specimen. i.e.- C=Collected, R=Received, T=Tested, B=Discarded Location: Used to describe the GENERIC location of the sample, that many “Places” may qualify to. i.e.- C=Collecting Site, R=Receiving Site, F=Sent to RefLab, N=In Transit, S=Storage Place: Used to describe the SPECIFIC physical location of a sample. i.e.- RECA=Receiving Site A, REF12A= Refrigerator 12 Site A, OUTPTCLIN=Outpatient Clinic

SetupIt is recommended to setup ST in the following order…Multisite- OL/CCHosparams Specimen Tracking Status Table Specimen Tracking Location Table Specimen Tracking Stops Table Specimen Tracking – Setup Table (Terminal setup)

Used to define STATUS CodeGeneral description of what is happening to specimen. One Character – Uppercase LettersSetup Step 1-Status Table

Typically STATUS codes are already built in your system.These Code letters are used with Autotracking and are hard coded to the Status DescriptionSetup Step 1-Status Table Do not deviate from these codes without SCC guidance

Used to define LOCATION codesRecommended to be built the same as STATUS codes for ease of setupOne Character – Uppercase LettersSetup Step 2 -Location Table

Combine STATUS/LOCATION codes with an 11 character PLACE code.Combination of STATUS/LOCATION/PLACE called a STOPDefine every STOP in this gridSetup Step 3- specimen Stops Table

Action column opens additional options for each STOPStop table- actions

For each STOP defined in STOP Grid section, the following fields can be customized, to suit the workflow of that STOP.Stops Table (List Specific Options)

Physical LocationEnter the Location, Department, Workstation, or Site associated with this STOP. This field can be used for Workstation Redirection and Remote ReceivingStops Table (List Specific Options)

New List DailyThis generates a new list at the beginning of every day for this stop, and all specimens tracked to this stop will be added to the new list. Great for storage stops.List AvailableThis check box allows this STOP to display in the ST List application.Stops Table (List Specific Options)

Default Next Specimen StopSelect the next STOP to use as the default when list tracking an entire list.Stops Table (List Specific Options)

Qualifying specimens only ifThis is a field used to qualify tubes to Lists depending on their Container, Location, Department, or Workstation.Stops Table (List Specific Options)

Sorting order (for report)The fields checked here will be considered when generating the specimen tracking lists for this stop. Remote Receive OnlyCheck this box for any stops with an R-Receiving Status, that should never be able to flag any specimen as Received.Stops Table (List Specific Options)

This table determines which Terminals have access to which STOPSpecimen Setup -Assign Stops to terminals

Terminal ID5 character IDSoftLab generated ID found at bottom right of screenOL/CC Terminals that are setup in the OL/CC table * All terminals Hide Hide STOP from terminal in application menu Setup Table

If the OL/CC code is used in the “Terminal” column of the ST Setup Table, ALL terminals that belong to that OL/CC will have the same STOPS.OL/CC

STATUS/LOCATION/PLACEChoose a pre-existing STOP from the drop down menuSetup Table

Type, Lo/Dp/Ws, ContainerFilters used to dictate what can or cannot be tracked by this terminal to this STOP.Positive and Negative LogicStep 5 – Setup Table

ActionsSame as STOP tableDifference?STOP table Actions occur when something is LIST tracked to that STOPSetup table Actions occur when something is individually tracked to that STOP Step 5 – Setup Table

Specimen Setup Actions!For all Actions, except Tags (T), use the drop down menu to select…

Specimen Setup Actions!(W) - Enable Workstation Redirection: Enables workstation redirection for tests on the scanned tube that are available at that Stop.(N) - Check for Incomplete Tests: Useful for storage stops, this action will check for any unverified results on the specimen. (C) - Collection Labels: Print Collection Labels (L) - Aliquot Labels: Print Aliquot Labels(P) - Use Printer: Define a printer for Labels (B) - Create Aliquot and Print Labels: Once the collection tube is scanned, that tube and all of its aliquots appear at this stop and labels print.

Specimen Setup Actions!(A) - Aliquot: Allows this stop to only track tube that is being Scanned without its aliquot tube. (D) - Discard: This action will not allow this tube to be scanned into any other stop. (U) - Use Actions from Terminal: Copies actions from another terminal listed in the table. (R) - Tag Request: This action requires mandatory data entry into the Tag field before specimens can qualify to a list. This is the action that makes it possible to assign specimens to rack positions. (T) - Pass Tag to Next Stop: This action is used with the Tag Request to pass the Tag data to the next Stop . Without it, the Tag data is lost when the tube is scanned into the next Stop .

Most of the setup should be complete at this point, but there are a few other useful features that require additional consideration and setup.AutoTrackingRemote ReceivingWorkstation RedirectionAdditional Specimen Tracking Setup

TR_AutoTracking “Y”STOP has to be setup for terminal (Setup Table)Tracking Server must be runningAutoTracking Setup

Remote ReceivingAnother feature your Multisite clients may want to utilize is “Remote Receiving”This allows specimens to be “Remote Received” at sites other than the testing Depot, but will NOT flag as “Received” in Specimen Tracking or SoftLab until they are Received at their testing site. This helps avoid altering TAT times, pending reports, resulting worklists, etc.

Only allows Terminals at testing location to flag specimens as Received.Intermediate STOPs can receive anywhere in system but it will never set flag.Remote Receiving

TR_RemoteReceiving “Y”Two setups in Stops TablePhysical Location fieldRemote Receiving Only flagRemote Receiving Setup

Physical LocationIf specimen has any other Loc/Dep/Wrkst than this field in Stops Table, it will be Remote Received.Remote Receiving Setup (Physical Location)

Remote Receiving OnlyWhen checked, EVERYTHING tracked to this stop will be Remote Received regardless of Physical Location field. Remote Receiving Setup(Remote Receiving Only)

Qualify containers to a List automatically when scanned.

Brief description of how this should flow/be used. R-Received, L-Laboratory, RKLB  Only orders for location RKLB will qualify for this stop.  Specimens will be hard receivedR-Received, P- Processing, RK for FS – only orders that will not be performed at the regional lab will qualify for this stop. Specimens will be Remote R eceived only.       These stops are all hidden, so users should receive all specimens in OE or Phlebotomy in order for the setup to function as follows.  Using Rockingham as an example: An order is created at Rockingham, this order contains tests for Rockingham and Fiona Stanley.  A user receives all containers in scanner receiving. The containers will be autotracked as follows: The container(s) for the test(s) to be run at Rockingham will be autotracked into the “R L RKLB” stop, the container(s) will be hard received. The container(s) for the test(s) to be run at Fiona Stanley will be autotracked into the “R P RK for FS” stop, the container(s) will be remote received.

A user can go into the Specimen Tracking List option and open the list for the “R P RK for FS” and the system will display a list of all containers that were received at Rockingham, are to be sent to and run at Fiona Stanley, but have not yet been placed on a Transit list.User opens tracking, scans all containers that are to be sent to Rockingham into the “T T RKLB>FSLB” (or the appropriate stop for Bacto, Drug Screens and so on) transit stop and a list is printed. The user opens the “ R P RK for FS ” list again.  If all containers were successfully scanned into the transit stop(s), this list will now be empty.  If there were any containers that were scanned in Scanner Receiving, but were not placed into the transit stop, then they will still be on this pending “R P RK for FS” stop.

Specimen Tracked to certain Stops can be workstation redirected based on Specimen Tracking Setup.Workstation Redirection

ActionsW Action set in Set on BOTH the Receiving Track for the Original Lab and the Receiving Track for the other Lab. Workstation Redirection Setup

Physical Location set in Stops TableSet the Physical Location on each Receiving Track you wish to allow Workstation Redirection.Set to the Loc/Dep/Wkst you want the specimen to be redirected toWorkstation Redirection Setup 40

Check for Incomplete Tests - Storage Track

Questions ????