TaskCenter 12.1

Page tree

Description

The Sample Inquiry pop-up provides a detailed view of the sample. This includes details pertaining to its order, where it currently exists in the storage hierarchy, and its history log.

Under normal workflows, only one trackable instance will be needed per sample. This will be labeled the Primary Sample. However, if a manual aliquot needs to be made off of the primary sample and tracked into storage, an aliquot label can be printed for the new container and a new trackable instance can be created under the original sample. Each trackable instance associated with the original sample will get a tab on the Sample Inquiry pop-up so that it can be tracked into its own position in the storage hierarchy and maintain its own storage history. The history log for each trackable instance will contain its storage events. The primary sample's history log will also contain additional events related to the order, collection, automation line, and Harvest interactions.

Access

  • TaskCenter > Manage Samples > Sample Management > Samples tab > SID link > Sample Inquiry
  • TaskCenter > Manage Testing > Work in Progress > sample ID link > Sample Inquiry 


Technical Manual

Sample ID

Patient

Displays the name of the patient.

Select the blue patient link to open a contextual menu:

  • Demographics
  • Insurance
  • Order History
  • New Order
  • Collect Samples
  • Blank Requisition
  • Change Log
  • Linked Documents
  • Client Services
MRNDisplays the medical record number for the patient.
DOBDisplays the patient's date of birth.
Order ID

Displays the order ID.

Select the blue order ID link to open a contextual menu:

  • Review Order
  • Samples
  • Labels
  • Requisition
  • Change Log
  • Lab Report
  • Linked Documents
  • Lab Info Request
  • Client Services Tickets
  • Work in Progress: Opens the selected order in a temporary tab in Work in Progress, where all the information related to the selected order is listed.
Order Date/TimeDisplays the date/time the order was placed.
Order ChoicesDisplays the order choices.
PriorityDisplays the priority given to the order.
Order StatusDisplays the status of the order.
Tube/Container TypeDisplays the tube/container type.
Collection Date/TimeDisplays the date/time the order was collected.
Collection LocationDisplays the collection location for the order.
Sample Options

Select this button to open a contextual menu:

  • Select Transfer to open the Transfer Metacontainer pop-up.
  • Select Dispose to open the Dispose Metacontainer Pop-up.
  • Select Order to open the same contextual menu you see if you select the order ID link.
  • Select Patient to open the same contextual menu you see if you select the patient ID link.
New Trackable Instance

Select this button to open the Sample Instance Edit pop-up to create additional trackable instances associated with the sample.

  • Add a description in the Description field. This is a required field.  
  • Select Save for a new tab to appear. Initially, new trackable instances will be uncontained in the storage hierarchy and have an empty history except for the creation event. As the trackable instance is transferred into and out of other metacontainers, it will build a history log and obtain a position in the storage hierarchy. 
  • Select Cancel to close the pop-up without creating a new instance.


Container Parents

The Container Parents attribute of each trackable instance shows an indented view of all parents of the sample. This shows where this instance is currently stored. As is the case for any metacontainer ID that appears anywhere within the system, the ID of each metacontainer in the storage hierarchy brings up the contextual menu for that metacontainer.

Instance Options

Select this button to open a contextual menu of actions that can be performed on the sample:

  • Transfer: Populate the Transfer Metacontainer pop-up's worklist with the trackable instances of the sample.
  • Dispose: Open the Dispose Metacontainer Pop-up with the trackable instances of the sample as the roots in the tree view.
  • Edit: Display the Sample Instance Edit pop-up. 
  • Print History: Open the Sample Instance History pop-up. Select OK to print a PDF on the sample history.


History 

The History table displays the events that have occurred on the trackable instance. The history log for each trackable instance contains the events related to that instance's transfers into other metacontainers and its disposal. The primary sample's history log also contains the events that cannot be associated with a specific trackable instance, but are linked to the sample ID or the order.

For example, events like order creation, label printing, and automation line communications only appear in the history log of the primary sample.

Date/TimeDisplays the date/time the event occurred.
Event

Displays the type of event that occurred.

Sample History Event Types

Note

Items wrapped in curly braces are placeholders for real values.

EventDescriptionUserLocationTriggering Event
Order CreatedOrder ID {Order ID}{User Name}{Signed-in Location}User manually creates an order.
Order CreatedOrder ID {Order ID}System{Host Name}User manually creates an order.
Added to Collection ListCollection List ID {Collection List ID}{User Name}{Signed-in Location}User manually adds the specimen to a collection list.
Removed from Collection ListCollection List ID {Collection List ID}{User Name}{Signed-in Location}User manually removes the specimen from a collection list.
Tube/Container Labels PrintedPrinter {Printer Name}{User Name}{Signed-in Location}User manually prints labels.
Tube/Container Labels PrintedPrinter {Printer Name}SystemSystemLabels printed automatically based on rules or configuration.
Aliquot Labels PrintedPrinter {Printer Name}{User Name}{Signed-in Location}User manually aliquot prints labels.
Aliquot Labels PrintedPrinter {Printer Name}SystemSystemAliquot labels printed automatically based on rules or configuration.
CollectedN/A{User Name}{Signed-in Location}User manually marks the sample as collected.
CollectedN/ASystemSystemSample is automatically marked as collected by rules or configuration.
UncollectedN/A{User Name}{Signed-in Location}User manually marks the sample as uncollected.
Added to ManifestManifest ID {Manifest ID}{User Name}{Signed-in Location}User manually adds the sample to a manifest.
Removed from ManifestManifest ID {Manifest ID}{User Name}{Signed-in Location}User manually removes the sample to a manifest.
Sample ReleasedTesting Host {Host ID}{User Name}{Signed-in Location}User manually releases the sample to the testing host.
Sample ReleasedTesting Host {Host ID}SystemSystemSample automatically released by the system via rules or configuration.
Loaded onto Line{Message Contents}System{Host Name}Automation line has communicated that it has received the sample.
Reached Line Destination{Message Contents}System{Host Name}Automation line has communicated that the sample has reached a destination. The specific destination is expected to be described in the message contents.
Rejected by Line{Message Contents}System{Host Name}Automation line has communicated that the sample has been rejected and directed to the reject lane.
Stored by Line{Message Contents}System{Host Name}Automation line has communicated that the sample has been placed in storage. The storage location is expected to be described in the message contents.
Discarded by Line{Message Contents}System{Host Name}Automation line has communicated that the sample has been discarded.
Transferred{Metacontainer Type}: {Metacontainer Description} ({Metacontainer ID}) at {Position}{User Name}{Signed-in Location}User transfers this sample into a metacontainer or is now uncontained.
DisposedN/A{User Name}{Signed-in Location}This specimen is marked as disposed of.
Parent Transferred{Metacontainer Type}: {Metacontainer Description} ({Metacontainer ID}) into {Destination Metacontainer Type}: {Destination Metacontainer Description} ({Destination Metacontainer ID}) at {Position}{User Name}{Signed-in Location}A parent metacontainer this specimen is transferred into another metacontainer or is uncontained.
New Trackable Instance CreatedN/A{User Name}{Signed-in Location}When this additional trackable instance has been created.
HarvestReleased from stored orders{User Name}{Workstation}User manually releases the order from stored orders.
HarvestReleased from stored ordersSystem{Workstation}Order is automatically released from stored orders when received from the host.
HarvestUpdated Order Choice Status of {Order Choice} to {Name of new status}{User Name}{Workstation}User manually changes the order choice status of an order choice attached to this sample.
HarvestUpdated Order Choice Status of {Order Choice} to {Name of new status}System{Workstation}The order choice status of an order choice attached to this sample is automatically changed through rules or configuration.
HarvestStorage Item {Storage Type}: {Storage ID} Created in {Contained Storage Type}: {Contained Storage ID} at {Position}{User Name}{Workstation}User manually created a storage item that is linked to this sample id. If the storage item is placed into another storage item upon creation, the containing storage item type, ID, and position will also appear in the description column.
HarvestStorage Item {Storage Type}: {Storage ID} Created in {Contained Storage Type}: {Contained Storage ID} at {Position}System{Workstation}System automatically created a storage item that is linked to this sample ID. If the storage item is placed into another storage item upon creation, the containing storage item type, ID, and position will also appear in the description column.
HarvestStorage Item {Storage Type}: {Storage ID} Transferred into {Destination Storage Type}: {Destination Storage ID} at {Position} (Direct){User Name}{Workstation}

User manually transfers a storage item that is linked to this sample ID. The transfer occurred on the storage item directly.

HarvestStorage Item {Storage Type}: {Storage ID} Transferred into {Destination Storage Type}: {Destination Storage ID} at {Position} (Indirect){User Name}{Workstation}User manually transfers a storage item that is linked to this sample ID. The transfer occurred on the storage item indirectly meaning that a containing storage item was transferred.
HarvestStorage Item {Storage Type}: {Storage ID} Verified in {Contained Storage Type}: {Contained Storage ID} at {Position} as Verified{User Name}{Workstation}User verified that the storage item existed in the containing storage item. The verification was performed via a bar code scanner.
HarvestStorage Item {Storage Type}: {Storage ID} Verified in {Contained Storage Type}: {Contained Storage ID} at {Position} as Manual Verified{User Name}{Workstation}User verified that the storage item existed in the containing storage item. The verification was performed manually.
HarvestStorage Item {Storage Type}: {Storage ID} Verified in {Contained Storage Type}: {Contained Storage ID} at {Position} as Missing{User Name}{Workstation}User attempted to verify that the storage item existed in the containing storage item, but it was marked as missing during the verification process.
HarvestStorage Item {Storage Type}: {Storage ID} Disposed in {Contained Storage Type}: {Contained Storage ID} at {Position}{User Name}{Workstation}User disposed of the storage item.
HarvestStorage Item {Storage Type}: {Storage ID} Expired in {Contained Storage Type}: {Contained Storage ID} at {Position} (Direct)System{Workstation}The system automatically expired the storage item.
HarvestStorage Item {Storage Type}: {Storage ID} Expired in {Contained Storage Type}: {Contained Storage ID} at {Position} (Indirect)System{Workstation}The system automatically expired the containing storage item and thus indirectly expired the storage item.

Note

The trackable instance description field contains information useful to identify it. This could be the aliquot ID printed on the aliquot label or a human-readable description, such as Aliquot #1.

The user and location fields in the history log represent the user who triggered the event and their signed-in location while triggering the event. The location field does not necessarily relate to the physical location of the trackable instance at the time the event was triggered.

The Harvest events will only appear in the history log if the testing host for the sample is a Harvest instance. the system queries the Harvest instance when the Sample Inquiry pop-up is opened for relevant information regarding the order, order choice, or related samples tracked within Harvest's Storage module and incorporate the information into the history log of the primary sample. This will be especially useful for showing the storage location of microbiology and anatomic pathology specimens related to the original patient sample. These microbiology and anatomic pathology specimens will have no record in the system, so being able to query into Harvest for this information will give the system user's insight into the location of these specimens.

DescriptionDisplays a description of the event.
UserDisplays the user's name associated with the event.
LocationDisplays the location where the event occurred.
CloseSelect this button to close the pop-up.