Category Archives: Edit Results

Panels, Drug Classes and Reportable Substances

Posted on by

Understanding Drug Classes and Reportable Substances in DTN

Using Amphetamines and Barbiturates as examples

DrugTestNetwork (DTN) reports drug test results based on Panels, which are defined sets of substances that appear on a test report. To support the wide variation in how laboratories report results—and how users want to present them—DTN separates drug classes from reportable substances
and allows flexible panel configuration.

This tutorial explains how those pieces work together and how different reporting styles affect the final report.

Core Concepts

Panels

A Panel is a record in the Panels table and includes:

  • Panel Name (abbreviation) – e.g., 5DSP
  • Description – the full panel name as referred to by the lab

Panels define what may appear on a report, not necessarily what must appear.

Drug Classes

A Drug Class is a logical grouping of related substances (for example,
Amphetamines or Barbiturates).

  • Drug classes provide grouping and interpretation
  • Drug classes may or may not be directly reportable
  • A drug class can contain one or many related substances

Every reportable substance must be associated with one drug class.

Reportable Substances

A reportable substance is an item that can appear as its own line on a report with a  Positive or Negative result.

Important points:

  • A reportable substance must be associated with a drug class
  • A drug class may also be reportable
  • Panels can include:
    • Only the drug class
    • Only specific substances
    • Both the class and its substances

This flexibility allows DTN to adapt to different lab reporting formats and user preferences.

Example 1: Amphetamines

Drug Class Structure

Drug Class: Amphetamines

Associated Substances: Amphetamine, Methamphetamine

Labs commonly report results as:

Amphetamines: Negative

…even though the testing actually evaluates Amphetamine and Methamphetamine separately.  DTN supports several valid panel configurations.

Panel Configuration Options

Option A: Drug Class Only

Panel includes:

  • Amphetamines

Result behavior:

Report shows only:

Amphetamines: Positive / Negative

If the user is manually entering results and knows the specific substance:

  • Amphetamine or Methamphetamine may be added to the report manually
  • This does not require them to be part of the original panel

Option B: Individual Substances Only

Panel includes:

  • Amphetamine
  • Methamphetamine

Result behavior:

Amphetamine: Positive
Methamphetamine: Negative

No overall “Amphetamines” line appears unless it was explicitly added to the panel.

Option C: Class + Substances

Panel includes:

  • Amphetamines
  • Amphetamine
  • Methamphetamine

Example result (Amphetamine positive):

Amphetamines: Positive
Amphetamine: Positive
Methamphetamine: Negative

This mirrors many lab reports and provides full transparency.

Key Amphetamines Rule

If any included substance is positive:

  • The drug class may also be reported as Positive
  • Whether negative component substances appear depends on:
    • Panel definition
    • Lab EDI data
    • User reporting preferences (manual entry)

Example 2: Barbiturates

Drug Class Structure

Drug Class: Barbiturates

Associated Substances: Amobarbital, Phenobarbital, Secobarbital, Butalbital, Butabarbital, Pentobarbital

This is a common case where users often want simpler reporting.

Typical Panel Setup

Panel includes:

  • Barbiturates

Default result:

Barbiturates: Negative

None of the individual substances appear unless needed.

Reporting a Specific Positive

If, for example, Amobarbital is positive:

  • Amobarbital must already exist as a reportable substance in DTN
  • It must be associated with the Barbiturates drug class
  • The user can then add it during result entry

Result may show:

Barbiturates: Positive
Amobarbital: Positive

Optional Simplification

If the user prefers:

  • They may remove Barbiturates from the report
  • Leaving only:
Amobarbital: Positive

DTN allows this so reports can match employer preferences, MRO guidance, or historical reporting formats.

Electronic Results (EDI) vs Manual Entry

EDI Results

When results are received electronically via EDI (Electronic Data Interchange):

  • Labs may send:
    • Drug class only
    • Drug class + positive substances
    • Drug class + both positive and negative components
  • DTN stores and reports exactly what the lab sends

Different labs behave differently—even for the same substances.

Manual Entry

When entering results manually:

  • Users may choose their reporting style
  • Drug classes and substances can be:
    • Added
    • Removed
    • Marked Positive or Negative independently
  • This allows correction, clarification, or simplification when needed

Design Principles Behind DTN’s Model

DTN intentionally separates:

  • Drug classes (logical grouping)
  • Reportable substances (what appears on reports)

This design:

  • Supports inconsistent lab reporting
  • Prevents forced over-reporting
  • Allows minimal or detailed reports
  • Keeps regulatory and clinical accuracy intact

Summary

  • Every reportable substance belongs to a drug class
  • Drug classes may or may not be reportable
  • Panels define what can appear, not what must appear
  • Users control reporting detail—especially during manual entry
  • Amphetamines show how classes and components may overlap
  • Barbiturates show why classes are often reported alone

This flexibility is essential for real-world drug testing workflows.

NOTE: You will find management features for Panels, Drug Classes and Reportable Items under the Other-Data menu.

Refer to sections:

  • Test Panels & Other Services
  • Reporting Classifications, Substances, Analytes, Metabolites & Validation Tests

When One or Both Parts of a Random Test are NOT Collected

Posted on by

A Random Test, sometimes requires both a Drug and a separate Alcohol test. However, there are cases when only one component of the test (e.g., drug or alcohol) was actually conducted. This can happen for a number of reasons. For some compliance considerations, you may want to record why the test was not conducted, and indicate a reason in the report record, for each test component not conducted. If the Date of Collection is set, the test is considered collected and will count toward the annual random selection percentages.  Keep in mind, if a random drug test record is not completed, it will not create any issue with your data or statistical reports.  The record simply exists as an incomplete random test. If you issue non-completed random test reports to the client, these tests will continue to be included.  Random test result records with a collection date or an Overall Qualitative Result are considered resolved. If you resolve the record, the tests will not be included in the non-completed reports.  However, if you don’t want the tests to contribute to the annual percentages, you can leave the collection date blank or, if you enter a collection date, you can use a special Overall Qualitative Result (OQR) that has its attribute set that prevents the test from getting counted as a collected test.  When you use a special OQR, the collection date can then serve as the date the record was resolved.

For example, you might consider these OQRs:

  • Not Conducted
  • No Longer Employed
  • Test Overlooked
If an OQR has the attribute set, Does NOT Contribute to Random Selection Statistics, it prevents the test from getting counted.  See below for instructions to add these OQRs if they are not already in your database.

For tests that were not conducted, follow the guidance below:

Open the test result in the Full Record Editor where you can manage the OQR for the drug and alcohol tests.

You have three options:
Option 1: Omit the Specimen Type

In the Full Record Editor, where you see “Specimen Type” for the drug or “Alcohol Test” for the type of alcohol test to conduct, select the option: Not Tested (or blank if Not Tested isn’t found). Using the option implies the test was not required.
This indicates that no test was required or performed for that portion.
The test result will not be included in the random selection statistics.

Option 2: Use a Special OQR (Overall Qualitative Result) that prevents the test (drug or alcohol) from getting counted. If a collection occurred but one part of the test was overlooked, you can set the OQR for that component using one of the special OQRs.

Option 3: Use OQR Participant Is No Longer Employed

In some cases, the participant may no longer be employed by the company at the time of the scheduled test. The user may still wish to complete the record for data management purposes.

This allows the record to be marked complete while excluding the test from statistics.

To add new OQR with the special attribute:

  1. Navigate to: Other-Data and tap the option: 
    Test Result Codes: Overall Qualitative Results [OQR]
  2. Tap the option to add a new OQR, such as:Test Collection Overlooked
  3. Set check-box for the attribute: Does NOT Contribute to Random selection statistics (see image below).
  4. In the Full Record Editor, apply this OQR to the drug or alcohol component that was not collected.

This ensures that:

  • The urine (drug) test does not count toward annual random selection stats.
  • The Collection Date still applies — for example, to record the alcohol test.

Summary Logic

  • If a Collection Date is entered:
    • The test is normally counted for statistics.
    • Unless the Specimen Type is blank or the selected OQR is set to one marked  Does NOT Contribute to Random selection statistics.

Tip

Use these procedures for cases such as participant not available, overlooked test, or no longer employed. These methods help you maintain a complete record while ensuring your random test statistics remain accurate.