Features - DOT Random Drug Testing Software

Features

Software Capabilities Questions

Complies

The system must be able to generate and maintain a unique identifier for each client.

Yes

Vendor provided database and software resources to store, manage and protect a projected volume of thousands of drug testing records.

Yes

The System and interfaces, if applicable, must contain HIPAA compliant security to protect content, user, and protected health information data. This security system must maintain a secure set of user privileges, which determine permission levels that users need to control, manage and update content

Yes

Must allow for different county agencies to utilize the same software with the ability to provide random drug testing support to multiple agencies/groups and the ability to configure each agency independently. Would prefer this be within one occurrence (license) of the solution

Should allow for an employee to be flagged if they are out on extended leave (usually > 30 days) with a projected return date so that they can be added back into the pool after that date. Notification of the return date would be preferred.

Yes

Must allow for specific employees to be selected for testing on a given day for various reasons (i.e. follow-up, post-accident, reasonable suspicion, return to duty, new sworn employees etc.) separate from and without impacting the validity of the random selection. These tests should be identified as different from the selections made in the random selection.

Yes

Must allow for random selection of an exact number of employees or by a percent of the available employee pool.

Yes

Must allow for the selection pool for a random test to be based on government requirements (i.e. separate pools for FTA or FMCSA).

Should allow for the selection pool for the random test to exclude employees if they have pre-planned leave (i.e. vacation etc.).

Yes

Must allow for the selection pool for a random test to be based on job function (i.e. safety-sensitive functions).

Must allow employees to be selected for different test types (i.e. Drugs, Alcohol or Both).

Yes

Must allow for the selection pool for a random test to be a specific shift/group (i.e. A,B, C or D).

Must allow for specific employees to be selected for testing on a given day for various reasons (i.e. follow-up, post-accident, reasonable suspicion, return to duty, new sworn employees etc.) separate from and without impacting the validity of the random selection. These tests should be identified as different from the selections made in the random selection.

Yes

Must allow for random selection for multiple testing days in one session (i.e. pull names for a complete week, month etc. at one time).

Yes

Must allow for the selection of employees to be totally randomly (i.e. the same employee could be pulled any number of times within a multiple pull selection processes).

Yes

MIS Reports: With one click of the mouse

Yes

Must allow for the selection of employees to be totally randomly (i.e. the same employee could be pulled any number of times within a multiple pull selection processes).

Yes

Should allow for the entry and tracking of incident settlement issues.

Yes

Must have report capability that allows for the necessary government report requirements (i.e. MTA, FTA and DOT (MIS data report which is done quarterly

Must retain event records indefinitely when a claim has been placed against the County, Agency or an Employee.

Yes

Should allow for the entry and tracking of claims/court case data pertaining to a test.

Yes

Should allow for the entry and tracking of referral for treatment data.

Yes

This document has been edited with the instant web content composer. The online instant HTML converter make a great resource that will help you a lot in your work. Save this link or add it to your bookmarks.