General Information - Driver History Transactions (KQ/KR)
Driver History Transactions (KQ/KR)
This section describes how to obtain driver history information by sending a Driver History Query (KQ) to the state of record. Information may be requested either by the driver's license number (OLN) OR the name (NAM), date of birth (DOB), and sex (SEX).
U.S. commercial driver license queries are described in section 26: "Commercial Vehicle Information".
Mexican commercial driver license queries are described in Section 33: "Communicating with Mexico".
Driver History Query / Driver History Response
This section provides an overview and details regarding the Driver History Query by license number or by name/date of birth/sex to a state (KQ), and the corresponding Driver History Response (KR).
Overview
To send a Driver History Query (KQ), enter the License Number, (see "Query by License Number" below), or Name/Date of Birth/Sex (see "Query by Name/DOB/Sex" below). The user may request a photo image as an additional option.
The Operators License Number (OLN) is expected to be alphanumeric, made up of numbers and letters. In some cases, a particular state may issue OLNs with special characters. If this is the case, the OLN may be entered as it is displayed on the license (including those special characters). For example, the state of Washington may use an asterisk or a hyphen in their driver license numbers. States issuing licenses with special characters are encouraged to note this in their OLN Helpfile.
Positive Driver's History Responses (KR) may contain information including the driver's name, address, date of birth, description, social security #, license type, restrictions, status, and license number. (See "Driver History Response" in the list below.) A Driver History Response (KR) may include an image if one was requested and is available.
Other possible responses to a query include:
- NOT ON FILE
- FILE NOT AVAILABLE
- TEMPORARILY UNAVAILABLE
Query Requirements
- All inquiries are in a fixed format.
- Only a single 2-character state code destination address is allowed per inquiry.
- The Driver History Query (KQ) format includes an optional image field (IMQ/). When this field is included in the inquiry with a "Y" as a value, the receiver should return an image if one is available.
- The Driver History Query (KQ) format includes two additional optional fields, a purpose code field (PUR) and an attention field (ATN). When used, these must follow the last required field, and both be present in the given sequence (PUR followed by ATN). These fields may be required by some states before they can release driver history information. The states that require the PUR and ATN fields are AK, AL, AZ, CO, CT, GA, HI, MD, MS, MT, NC, ND, NM, PA, VA, WA and WY.
Reason Code (New)
- Driver History Transactions now support an optional Reason Code element. When included in the query, it will be forwarded to users that have opted in to receive Reason Codes in their Driver History Transactions.
- For users that have not opted to receive Reason Codes in their Driver History Transactions, the Reason Code will be removed by Nlets prior to sending the transaction.
- Contact the Nlets Service Center for more information about configuring your state to receive Reason Codes in their Driver History Transactions.
Query Notes
- Driver History queries on name may result in multiple hits. Only close matches (i.e., exact match on the last name and DOB) should be returned.
- Utilize the states help file for additional DMV ORI information.
Query Help
- To obtain explanatory or supplementary information on a state's driver's license files, a user may send an Administrative Message to xxOLNHELP (where xx = 2-character state code).
- A user may determine who is providing automated responses to driver history queries and who is a photo sharing participant by sending an Administrative Message to "NLOLNHELP".
More information on help files can be located in Help File Transactions.
Data Codes
Codes used as input and/or output in the driver's license query/response generally match NCIC formats and content. Please refer to Part II of your NCIC Manual for code translation and instruction.
Field Requirements
The table below describes the XML tags, legacy prefixes, field sizes, data requirements and a translation of each requirement.
XML Tag:
Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
OLN/
1-20
Alphanumeric
Driver's License
Number
NAM/
Max.
30
Alpha Characters
Name
SEX/
1
M, F or U
Sex
DOB/
8 or
10
CCYYMMDD (text)
or ccyy-mm-dd (XML)
Date of Birth
PUR/
1
Must be C, F, E, D,
J or S
Purpose Code (optional)See Introduction Page
for more information.
n2:ResponseAttentionDescriptionText
(Optional)
IMQ/
1
Y (true) or
N (false)
Image Request
(Optional)
RSN/
1
Must be N, F, V, T,
S, H or I
Reason Code (optional)See Introduction Page
for more information.
Driver History Responses (KR)
- Response formats are at the discretion of the responding state, however, states are urged to avoid special codes or phrases that may be foreign to out-of-state agencies.
- Responses to driver history inquiries will vary considerably depending on the responding states.