Rules – Using Persistent Data Elements

Tips & Tricks

Back to Tips & Tricks

It is sometimes necessary to recall or utilize information from a previous result or sample when writing rules. For example, Hepatitis testing typically requires the review of the results from three runs to make a final determination. It may also be desirable to evaluate whether a test was rerun.

This article will explore how Instrument Manager™ (IM) accommodates this type of workflow. First, it is important to understand that there are three categories of data elements within IM: Patient, Specimen, and Test. There are also general data elements that are not explored in this article.

Persistent data elements store data and may be recalled from run to run. Patient and Specimen data elements are described as persistent because IM stores the data and recalls it each time that test is processed on the same Patient or Specimen.

Test-level data elements tend to not be persistent. That data comes into IM and is not remembered the next time that test is processed on that same patient or specimen. However, there are some exceptions to that:

  • In older versions of IM, there were only two persistent test-level data elements available that were repurposed from their original use: Previous Test Dilution or Previous Test Error.
  • Newer versions of IM have a much wider array of available data elements that can be used to store and remember data from run to run. There are 20 Patient and Specimen User Fields (15 regular fields and five indexed fields) that may be used to store data from run to run and specimen to specimen. Additionally, there are 5 Test User Persistent Fields available. Each of these data elements may be set via rules to store the desired content to be recalled later.
    Example:
    Storing run 1 for Hepatitis testing to be evaluated later
    If: ( {Test Resulted} “HepB1” )

    Then: {Add Test} “HepB” {AND} {Set} {Test User Persistent Field 01} {On Test} “HepB” = {Result} {On Test} “HepB1”
  • There are also several other fields that are set by IM that can be used to recall previous information. Those include Previous Run Result 1-3 and Previous Patient Result 1-3. These fields are automatically populated and recalled by IM if appropriate for the test that is being resulted. These fields cannot be manipulated with rules but often contain the information that rule writers leverage without having to write rules to set or recall that information.
    Example:
    Evaluating if a PLT was rerun
    If: (( {Test Resulted} “PLT” ) {AND} ( {Previous Run Result 1} {On Test} “PLT” {NOT} = “” ))
    Then: {Set} {Hold Test Flag} {On Test} “PLT” = “RERUN”


NOTE: To ensure that the rules function as intended, it is critical that rules be validated by the user prior to being moved into the Live Rule set and put into practice in the laboratory setting. Refer to the Instrument Manager Rules Manual (included with Instrument Manager software) for additional recommendations regarding testing.

Data Innovations’ Technical and Professional Services team is available to assist customers with specific rules development and/or evaluation. For more information, please contact northamerica-sales@datainnovations.com or call 802.658.2850.
For syntax assistance or minor rule questions, please contact support at northamerica-support@datainnovations.com or call 802.658.1955. Support will evaluate if further services are required.

More Tips & Tricks Articles

Tips & Tricks

TCP/IP Keep-Alive

Data Innovations’ (DI’s) Instrument Manager (IM) offers connectivity that enables integration with virtually any instrument, LIS, or EMR/EHR regardless of...

Instrument Manager, Tips & Tricks

Following Driver Updates in My DI Community

Overview

Data Innovations (DI) provides ways to stay up to date on the latest driver updates.The first way is right through...

Instrument Manager, Tips & Tricks

Net Gateway Startup Issues (Error 5023)

Overview

When IRIS and Instrument Manager (IM) are starting after a server shuts down or restarts, the .NET gateway is not...

Tips & Tricks

How to Install Instrument Manager™ Core Software

NOTE These instructions apply for Data Innovations’ North American customers. If this is your first time installing IM, please contact Data...

Tips & Tricks

How to help Data Innovations help you when requesting Support

Data Innovations' Tips & Tricks are intended to promote the effective and productive use of Instrument Manager. Fortunately, Instrument Manager...

Tips & Tricks

Evaluation Rules for Clinical Ranges Precaution

When building an Autoverification Rule Set it's common to include evaluation rules for Clinical Ranges. These rules typically set test...

Tips & Tricks

Instrument Manager System Preventative Maintenance (volume 1)

Instrument Manager is a robust software application with a proven track record of operational stability. However, as with any software...

Tips & Tricks

Instrument Manager System Preventative Maintenance (volume 2)

This month's Tips & Tricks is the second installation of Preventative Maintenance recommendations intended to help you maintain a stable...

Ready to learn more?