Release: LDMS for Windows 12.1

Howard Gutzman

Frontier Science is pleased to announce the release of LDMS for Windows version 12.1. The focus of this release was improving the Test Result Entry tool and pharmacology features in LDMS. Here are are a few highlights from these changes.

Test Result Entry Improvements

The Test Result Entry tool is a new feature that was added to LDMS 12.0 so that it could be tested by select users for the PHIA project. Based on user feedback, a number of changes to the Test Result Entry tool have been made.

  • Geenius Report improvements: The Geenius Report will now only show records where the Geenius result field is applicable.
  • New QA Type option: You can now specify the logic for triggering QA within a template.
  • New Geenius Default Setting: You can now specify the logic for selecting the default value for the Geenius assay result.
  • EID options: Users can now specify on templates which assays should be available for EID visits.

More information about using the Test Result Entry tool can be found in the LDMS for Windows User Manual.

Pharmacology Changes

### Code Remappings As part of the routine deploy update 361, three drug codes were-remapped. Those codes were as follows.

  • ABT-267 to OBV (Ombitasvir)
  • ABT-333 to DSV (Dasabuvir)
  • ABT-450 to PTV (Paritaprevir)

Any assay results for these analytes prior to the date that the codes were changed will now have a comment that mentions the code change.

Additional Time Validation

One of the validation checks that LDMS performs is to verify that pharmacology specimens have additional time and time unit fields complete when a specimen is tested or shipped to certain designated pharmacology laboratories. These restrictions have been modified so that specimen type can be taken into consideration. For example, additional time and time unit are now not required for hair specimens collected for pharmacological testing.

Proficiency Results Report

Finally, for the Pharmacology Proficiency Results Report, changes have been made to the logic that determines what results to include and exclude based on censor codes. The report is now smarter about including results that are valid even though they may have a censor code applied, such as the U censor (diluted). Likewise, results that are invalid but have a subsequent valid result are now excluded. For example. If a result has the A censor (greater than the upper limit and needs to be diluted and repeated), which is considered an invalid result, and another result for the same specimen has the U censor, the invalid result will be appropriately excluded.