25.10.2013 Views

Implementation Guidelines - Federal Transit Administration - U.S. ...

Implementation Guidelines - Federal Transit Administration - U.S. ...

Implementation Guidelines - Federal Transit Administration - U.S. ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

attempts to contact the employee<br />

must be documented.<br />

• If, after making a reasonable effort,<br />

the MRO is unable to reach the<br />

individual directly, the MRO shall<br />

contact the DER/DAPM. The DER<br />

should make at least three attempts<br />

to contact the employee within a 24hour<br />

period. If contact is made, the<br />

DER must instruct the employee to<br />

contact the MRO immediately (no<br />

longer than 72 hours) and explain the<br />

consequences of failing to do so. If<br />

the employee fails to contact the<br />

MRO within 72 hours, the test will<br />

be verified as a no-contact positive.<br />

If, after making reasonable efforts<br />

for a 24-hour period, the DER is<br />

unable to contact the employee, the<br />

employer may leave a message for<br />

the employee instructing him/her to<br />

contact the MRO and place the<br />

employee on temporary unqualified<br />

status or medical leave. If 10 days<br />

pass with no employee contact, the<br />

MRO will verify the test result as a<br />

no-contact positive. All attempts to<br />

contact the employee must be<br />

documented.<br />

• If contact is made, the MRO must<br />

provide the employee with the<br />

opportunity to discuss the test result<br />

on a confidential basis. If the<br />

employee declines to discuss the test<br />

result with the MRO, the test will be<br />

verified as a no-contact positive test<br />

result. If the employee wishes to talk<br />

to the MRO, the MRO staff may<br />

schedule the interview, but must not<br />

gather any medical information or<br />

information concerning possible<br />

explanations for the test result. The<br />

staff may advise an employee to<br />

have medical information ready to<br />

present to the MRO.<br />

• The MRO verification interview with<br />

the employee must be made by<br />

telephone or in person. The MRO<br />

must tell the employee that the test<br />

result was positive, adulterated,<br />

substituted, or invalid and the basis<br />

for the test result (i.e., presence of<br />

drug or adulterant, or validity test<br />

results). The MRO must explain the<br />

verification process and the potential<br />

need for further medical evaluation.<br />

The MRO must warn the employee<br />

before any medical information is<br />

discussed that the MRO must<br />

disclose to third parties (i.e.,<br />

employer, SAP, NTSB, DOT, FTA)<br />

without the employee’s consent for<br />

drug test result information and<br />

medical information affecting the<br />

performance of safety-sensitive<br />

duties that the employee provides.<br />

• The MRO will review and interpret<br />

an individual’s confirmed nonnegative<br />

(i.e., positive, adulterated,<br />

substituted, invalid) test by (1)<br />

reviewing the individual’s medical<br />

history, including any medical<br />

records and biomedical information<br />

provided; (2) affording the individual<br />

an opportunity to discuss the test<br />

result; and (3) verifying the<br />

authenticity of all medical records<br />

(i.e., prescriptions, medical<br />

procedures) the employee provides.<br />

The MRO may contact the<br />

employee’s physician or other<br />

relevant medical personnel for<br />

further information. Based on the<br />

information that was provided and<br />

verified, the MRO must decide<br />

whether there is a legitimate medical<br />

explanation for the result, including<br />

legally prescribed medication.<br />

Chapter 7. Drug Testing Procedures 7-18 August 2002

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!