Difference between revisions of "Section 13: Driver License Transactions"

From Nlets Wiki
Jump to: navigation, search
(Driver's License NIEM Examples)
(Downloads)
(15 intermediate revisions by 6 users not shown)
Line 13: Line 13:
 
===Driver's License Query / Driver's License Response===
 
===Driver's License Query / Driver's License Response===
  
This section provides an overview and details regarding the Driver's License Query by license number or by name/date of birth/sex to a state (DQ), and the corresponding Driver's License Response (DR), Driver's License Query by Name to a state (DNQ), and the corresponding Driver's License Response by Name (DNR), and the Driver's License Query by Name/Date of Birth to a region (DQG), and the corresponding Driver's License Response (DRG).
+
This section provides an overview and details regarding the Driver's License Query by license number or by name/date of birth/sex to a state (DQ), and the corresponding Driver's License Response (DR), Driver's License Query by Name to a state (DNQ), and the corresponding Driver's License Response by Name (DNR), and the Driver's License Query by Name/Date of Birth/Sex to a region (DQG).
  
 
===Multi-State Query Functionality===
 
===Multi-State Query Functionality===
Line 28: Line 28:
  
 
To send a Driver's License Query (DQ), 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 (DQ only).
 
To send a Driver's License Query (DQ), 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 (DQ only).
 +
 +
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). States issuing licenses with special characters are encouraged to note this in their OLN Helpfile.
  
 
Positive Driver's License Responses (DR) may contain the driver's name, address, date of birth, description, social security #, license type, restrictions, status, and license number (see "Driver's License Response" below). A Driver's License Response (DR) may include an image if one was requested and is available.
 
Positive Driver's License Responses (DR) may contain the driver's name, address, date of birth, description, social security #, license type, restrictions, status, and license number (see "Driver's License Response" below). A Driver's License Response (DR) may include an image if one was requested and is available.
Line 46: Line 48:
 
<li>A destination code of "Z1" will result in the Query being directed to all states (sends a separate response for each state).
 
<li>A destination code of "Z1" will result in the Query being directed to all states (sends a separate response for each state).
 
<li>A destination code of "NL" will result in the Query being directed to all states (sends a single response for all states).
 
<li>A destination code of "NL" will result in the Query being directed to all states (sends a single response for all states).
<li>Only queries on name and date of birth may be used for DQGs.
+
<li>Only queries on name, date of birth and sex may be used for DQGs.
 
<li>The Driver's License Query (DQ) format includes an optional image field (IMQ/). When this field is included in the inquiry with "Y" (Legacy) or "true" (XML) as a value, the receiver should return an image if one is available.  
 
<li>The Driver's License Query (DQ) format includes an optional image field (IMQ/). When this field is included in the inquiry with "Y" (Legacy) or "true" (XML) as a value, the receiver should return an image if one is available.  
 
<li>If a state wishes to request driver's license information it should, without exception, utilize the Nlets inquiry formats. Administrative Messages should not be used in place of the Nlets operator license inquiry formats.
 
<li>If a state wishes to request driver's license information it should, without exception, utilize the Nlets inquiry formats. Administrative Messages should not be used in place of the Nlets operator license inquiry formats.
Line 318: Line 320:
 
<th align="left">
 
<th align="left">
 
  <syntaxhighlight lang="xml">
 
  <syntaxhighlight lang="xml">
<nc:Next>
+
<n2:RequestAdditionalRecordsText>
 
  </syntaxhighlight>
 
  </syntaxhighlight>
 
</th>
 
</th>
Line 348: Line 350:
  
 
The parsing service can be setup to parse all statewide DRs or to parse DRs for any number of individual ORIs.
 
The parsing service can be setup to parse all statewide DRs or to parse DRs for any number of individual ORIs.
 +
 +
Any standardized message that is received will also be transformed into a text response in the OriginalResponseText element of a PDR.
  
 
To leverage this service or for more information, contact the Nlets Control Center at 1-800-528-4020.
 
To leverage this service or for more information, contact the Nlets Control Center at 1-800-528-4020.
Line 377: Line 381:
 
===Element Dictionary===
 
===Element Dictionary===
  
Transaction types detailed below include: <u>Query by Name, DOB and Sex (DQ,DQG)</u>, <u>Query by Driver's License Number (DQ,DQG)</u>, <u>Query by Name (DNQ)</u>, <u>Response in Free Text (DR)</u>, <u>Standardized Status Response (DR)</u> and <u>Standardized List Response (DNR)</u>.
+
Transaction types detailed below include: <u>Query by Name, DOB and Sex (DQ,DQG)</u>, <u>Query by Driver's License Number (DQ)</u>, <u>Query by Name (DNQ)</u>, <u>Response in Free Text (DR)</u>, <u>Standardized Status Response (DR)</u> and <u>Standardized List Response (DNR)</u>.
  
 
====Query Formats====
 
====Query Formats====
Line 429: Line 433:
 
<br>&nbsp;&nbsp;A value of "true" in this element indicates that an image is being requested if available.
 
<br>&nbsp;&nbsp;A value of "true" in this element indicates that an image is being requested if available.
  
<b><u>Query by Driver's License Number (OLN) (DQ,DQG)</u></b>
+
<b><u>Query by Driver's License Number (OLN) (DQ)</u></b>
  
 
<b>n2:NLETSInquiryData</b>
 
<b>n2:NLETSInquiryData</b>
Line 587: Line 591:
 
     <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
 
     <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
 
     <nh2:DestinationORIID>AZ</nh2:DestinationORIID>
 
     <nh2:DestinationORIID>AZ</nh2:DestinationORIID>
 +
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
 
   </n2:NLETSMessageHeader>
 
   </n2:NLETSMessageHeader>
 
   <n2:NLETSInquiryData n2:key="DQ">
 
   <n2:NLETSInquiryData n2:key="DQ">
Line 616: Line 621:
 
     <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
 
     <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
 
     <nh2:DestinationORIID>AZ</nh2:DestinationORIID>
 
     <nh2:DestinationORIID>AZ</nh2:DestinationORIID>
 +
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
 
   </n2:NLETSMessageHeader>
 
   </n2:NLETSMessageHeader>
 
   <n2:NLETSInquiryData n2:key="DQ">
 
   <n2:NLETSInquiryData n2:key="DQ">
Line 643: Line 649:
 
     <nh2:OriginatingORIID>AZDMV0000</nh2:OriginatingORIID>
 
     <nh2:OriginatingORIID>AZDMV0000</nh2:OriginatingORIID>
 
     <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
 
     <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
 +
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
 
     <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
 
     <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
 
     <nh2:MessageReceiveTime>08:28</nh2:MessageReceiveTime>
 
     <nh2:MessageReceiveTime>08:28</nh2:MessageReceiveTime>
Line 692: Line 699:
 
     <nh2:OriginatingORIID>AZNLETS47</nh2:OriginatingORIID>
 
     <nh2:OriginatingORIID>AZNLETS47</nh2:OriginatingORIID>
 
     <nh2:DestinationORIID>AZNLETS49</nh2:DestinationORIID>
 
     <nh2:DestinationORIID>AZNLETS49</nh2:DestinationORIID>
 +
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
 
     <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
 
     <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
 
     <nh2:MessageReceiveTime>08:30</nh2:MessageReceiveTime>
 
     <nh2:MessageReceiveTime>08:30</nh2:MessageReceiveTime>
Line 712: Line 720:
 
   </n2:NLETSInquiryData>
 
   </n2:NLETSInquiryData>
 
   <n2:NLETSResponseData n2:key="DR">
 
   <n2:NLETSResponseData n2:key="DR">
     <nds2:DriverStatus xmlns:nds2="http://www.nlets.gov/niem/nlets-driver-status/1.0/">
+
     <nds2:DriverStatus xmlns:nds2="http://www.nlets.org/niem/nlets-driver-status/1.0/">
 
       <nds2:StandardResponse>
 
       <nds2:StandardResponse>
 
         <n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
 
         <n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
Line 799: Line 807:
 
     <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
 
     <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
 
     <nh2:DestinationORIID>AZ</nh2:DestinationORIID>
 
     <nh2:DestinationORIID>AZ</nh2:DestinationORIID>
 +
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
 
   </n2:NLETSMessageHeader>
 
   </n2:NLETSMessageHeader>
 
   <n2:NLETSInquiryData n2:key="DQ">
 
   <n2:NLETSInquiryData n2:key="DQ">
Line 830: Line 839:
 
     <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
 
     <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
 
     <nh2:DestinationORIID>AZ</nh2:DestinationORIID>
 
     <nh2:DestinationORIID>AZ</nh2:DestinationORIID>
 +
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
 
   </n2:NLETSMessageHeader>
 
   </n2:NLETSMessageHeader>
 
   <n2:NLETSInquiryData n2:key="DNQ">
 
   <n2:NLETSInquiryData n2:key="DNQ">
Line 855: Line 865:
 
     <nh2:OriginatingORIID>AZDMV0000</nh2:OriginatingORIID>
 
     <nh2:OriginatingORIID>AZDMV0000</nh2:OriginatingORIID>
 
     <nh2:DestinationORIID>AZNLETS49</nh2:DestinationORIID>
 
     <nh2:DestinationORIID>AZNLETS49</nh2:DestinationORIID>
 +
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
 
     <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
 
     <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
 
     <nh2:MessageReceiveTime>08:34</nh2:MessageReceiveTime>
 
     <nh2:MessageReceiveTime>08:34</nh2:MessageReceiveTime>
Line 923: Line 934:
 
     <nh2:OriginatingORIID>AZDMV0000</nh2:OriginatingORIID>
 
     <nh2:OriginatingORIID>AZDMV0000</nh2:OriginatingORIID>
 
     <nh2:DestinationORIID>AZNLETS49</nh2:DestinationORIID>
 
     <nh2:DestinationORIID>AZNLETS49</nh2:DestinationORIID>
 +
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
 
     <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
 
     <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
 
     <nh2:MessageReceiveTime>08:35</nh2:MessageReceiveTime>
 
     <nh2:MessageReceiveTime>08:35</nh2:MessageReceiveTime>
Line 934: Line 946:
 
   </n2:NLETSInquiryData>
 
   </n2:NLETSInquiryData>
 
   <n2:NLETSResponseData n2:key="DNR">
 
   <n2:NLETSResponseData n2:key="DNR">
     <ndm2:DriverMatch xmlns:ndm2="http://www.nlets.gov/niem/nlets-driver-match/1.0/">
+
     <ndm2:DriverMatch xmlns:ndm2="http://www.nlets.org/niem/nlets-driver-match/1.0/">
 
       <ndm2:IndividualMatch>
 
       <ndm2:IndividualMatch>
 
         <n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
 
         <n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
Line 1,179: Line 1,191:
 
<th align="left">
 
<th align="left">
 
   <syntaxhighlight lang="xml">
 
   <syntaxhighlight lang="xml">
<n2:NLETS xmlns:j="http://niem.gov/niem/domains/jxdm/4.1" xmlns:ndc2="http://www.nlets.org/niem/nlets-driver-cert/1.0" xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0" xmlns:nds2="http://www.nlets.org/niem/nlets-driver-status/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:ndm2="http://www.nlets.org/niem/nlets-driver-match/1.0" xmlns:n2="http://www.nlets.org/niem/1.0">
+
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
+
<n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>PDR</nh2:MessageKeyCodeText>
+
<nh2:MessageKeyCodeText>PDR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZDMV0000</nh2:OriginatingORIID>
+
<nh2:OriginatingORIID>AZ007C100</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
+
<nh2:DestinationORIID>AZNLETS39</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>01/01/2016</nh2:MessageReceiveDate>
+
<nh2:DocumentControlFieldText>
    <nh2:MessageReceiveTime>01:01</nh2:MessageReceiveTime>
+
<![CDATA[NL0000TEST]]>
    <nh2:MessageSendDate>01/01/2016</nh2:MessageSendDate>
+
</nh2:DocumentControlFieldText>
    <nh2:MessageSendTime>01:01</nh2:MessageSendTime>
+
<nh2:MessageReceiveDate>11/24/2019</nh2:MessageReceiveDate>
    <nh2:ReceiveMessageNumeric>12345</nh2:ReceiveMessageNumeric>
+
<nh2:MessageReceiveTime>12:21</nh2:MessageReceiveTime>
    <nh2:SendMessageNumeric>54321</nh2:SendMessageNumeric>
+
<nh2:MessageSendDate>11/24/2019</nh2:MessageSendDate>
  </n2:NLETSMessageHeader>
+
<nh2:MessageSendTime>12:21</nh2:MessageSendTime>
  <n2:NLETSResponseData n2:key="PDR">
+
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nc:QualityCommentText>TEXT RESPONSE CONTAINS CONTENT THAT IS NOT PART OF THE DR XML SPECIFICATION, SEE ORIGINAL TEXT FOR ADDITIONAL INFORMATION</nc:QualityCommentText>
+
<nh2:SendMessageNumeric>00404</nh2:SendMessageNumeric>
    <n2:OriginalTextResponse> NAM/SMITH,JOHN.DOB/19810807.SEX/F
+
</n2:NLETSMessageHeader>
NAME:SMITH,JOHN Q                        DOB:08/07/1981  RCPT#:UNKNOWN
+
<n2:NLETSInquiryData n2:key="DQ">
ADDR:1234 ANYSTREET                          PHOENIX                  AZ 85000
+
<n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
ISSUE DT:00/00/0000 EXP:00/00/0000      SEX:F HGT:501 WGT:135 HAIR:BRN EYE:BRN
+
<nc:PersonBirthDate>
OLN:D12345678    SSN:555443333    OLT:NO LICENSE
+
<nc:Date>1956-09-10</nc:Date>
MAIL:4321 ANYSTREET                          PHOENIX                   AZ 85000
+
</nc:PersonBirthDate>
PREV LIC: D12345678                PREV ST: AZ
+
<nc:PersonName>
          D12345678                          AZ
+
<nc:PersonFullName>OFFICE,D L</nc:PersonFullName>
          D12345678                          AZ
+
</nc:PersonName>
 +
<nc:PersonSexCode>M</nc:PersonSexCode>
 +
</n2c:Driver>
 +
</n2:NLETSInquiryData>
 +
<n2:NLETSResponseData n2:key="PDR">
 +
<nds2:DriverStatus xmlns:nds2="http://www.nlets.org/niem/nlets-driver-status/1.0">
 +
<n2c:AdditionalInformation xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
 +
<n2c:StateElement>
 +
<n2c:ElementFieldName>PRIMARY LICENSE RECEIPT CODE</n2c:ElementFieldName>
 +
<n2c:ElementFieldValue>X0000000</n2c:ElementFieldValue>
 +
</n2c:StateElement>
 +
</n2c:AdditionalInformation>
 +
<nds2:StandardResponse>
 +
<n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
 +
<nc:PersonBirthDate>
 +
<nc:Date>1956-09-10</nc:Date>
 +
</nc:PersonBirthDate>
 +
<nc:PersonEyeColorText>BRN</nc:PersonEyeColorText>
 +
<nc:PersonHairColorText>BLK</nc:PersonHairColorText>
 +
<nc:PersonHeightMeasure>
 +
<nc:MeasurePointValue>509</nc:MeasurePointValue>
 +
</nc:PersonHeightMeasure>
 +
<nc:PersonName>
 +
<nc:PersonFullName>D,L,OFFICE</nc:PersonFullName>
 +
</nc:PersonName>
 +
<nc:PersonSexText>M</nc:PersonSexText>
 +
<nc:PersonSSNIdentification>
 +
<nc:IdentificationID si:type="nc:TextType" xmlns:si="http://www.w3.org/2001/XMLSchema-instance">088888222</nc:IdentificationID>
 +
</nc:PersonSSNIdentification>
 +
<nc:PersonWeightMeasure>
 +
<nc:MeasurePointValue>175</nc:MeasurePointValue>
 +
</nc:PersonWeightMeasure>
 +
<n2c:DriverLicense>
 +
<nc:DriverLicenseIdentification>
 +
<j:IdentificationJurisdictionNCICLSTACode xmlns:j="http://niem.gov/niem/domains/jxdm/4.1">OPERATOR</j:IdentificationJurisdictionNCICLSTACode>
 +
<nc:IdentificationID si:type="nc:TextType" xmlns:si="http://www.w3.org/2001/XMLSchema-instance">D00627956</nc:IdentificationID>
 +
</nc:DriverLicenseIdentification>
 +
<nc:DriverLicenseExpirationDate>
 +
<nc:Date>1985-09-10</nc:Date>
 +
</nc:DriverLicenseExpirationDate>
 +
<nc:DriverLicenseIssueDate>
 +
<nc:Date>1983-09-10</nc:Date>
 +
</nc:DriverLicenseIssueDate>
 +
<nc:DriverLicenseNonCommercialStatusText>REVOCATION</nc:DriverLicenseNonCommercialStatusText>
 +
<nc:DriverLicenseNonCommercialStatusText>MANDATORY INSURANCE SUSPENSION</nc:DriverLicenseNonCommercialStatusText>
 +
<nc:DriverLicenseNonCommercialStatusText>SUSPENSION - MVD ACTION REQUIRED</nc:DriverLicenseNonCommercialStatusText>
 +
<nc:DriverLicenseNonCommercialStatusText>SUSPENSION - COURT ACTION REQUIRED</nc:DriverLicenseNonCommercialStatusText>
 +
</n2c:DriverLicense>
 +
<n2c:PersonContactInformation>
 +
<nc:ContactMailingAddress>
 +
<nc:StructuredAddress>
 +
<nc:LocationStreet>
 +
<nc:StreetFullText>1802 W JEFFERSON SUITE 33</nc:StreetFullText>
 +
</nc:LocationStreet>
 +
<nc:LocationCityName>PHOENIX</nc:LocationCityName>
 +
<nc:LocationStateName>AZ</nc:LocationStateName>
 +
<nc:LocationPostalCode>85007</nc:LocationPostalCode>
 +
</nc:StructuredAddress>
 +
</nc:ContactMailingAddress>
 +
</n2c:PersonContactInformation>
 +
<n2c:PersonContactInformation>
 +
<nc:ContactMailingAddress>
 +
<nc:StructuredAddress>
 +
<nc:LocationStreet>
 +
<nc:StreetFullText>PO BOX 2100</nc:StreetFullText>
 +
</nc:LocationStreet>
 +
<nc:LocationCityName>PHOENIX</nc:LocationCityName>
 +
<nc:LocationStateName>AZ</nc:LocationStateName>
 +
<nc:LocationPostalCode>85001</nc:LocationPostalCode>
 +
</nc:StructuredAddress>
 +
</nc:ContactMailingAddress>
 +
</n2c:PersonContactInformation>
 +
</n2c:Driver>
 +
</nds2:StandardResponse>
 +
</nds2:DriverStatus>
 +
<n2:OriginalTextResponse>NAM/OFFICE,D L.DOB/19560910.SEX/M.  NAME:D,L,OFFICE                                DOB:09/10/1956  RCPT#:X00000000  ADDR:1802 W JEFFERSON SUITE 33              PHOENIX                  AZ 85007  ISSUE DT:09/10/1983 EXP:09/10/1985      SEX:M HGT:509 WGT:175 HAIR:BLK EYE:BRN  OLN:D00627956    SSN:088888222    OLT:OPERATOR  MAIL:PO BOX 2100                            PHOENIX                  AZ 85001  STATUS    REVOCATION            MANDATORY INSURANCE SUSPENSION            SUSPENSION - MVD ACTION REQUIRED            SUSPENSION - COURT ACTION REQUIRED</n2:OriginalTextResponse>
 +
</n2:NLETSResponseData>
 +
</n2:NLETS>
 +
 
 +
  </syntaxhighlight>
 +
</th>
 +
</tr>
 +
</table>
 +
 
 +
<u>Example 2</u>: A Parsed Driver's License Match List Response.
 +
 
 +
<table border="1">
 +
<tr>
 +
<th align="left">
 +
  <syntaxhighlight lang="xml">
 +
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
 +
<n2:NLETSMessageHeader>
 +
<nh2:MessageKeyCodeText>PDR</nh2:MessageKeyCodeText>
 +
<nh2:OriginatingORIID>NBDMV0000</nh2:OriginatingORIID>
 +
<nh2:DestinationORIID>AZNLETS39</nh2:DestinationORIID>
 +
<nh2:DocumentControlFieldText>
 +
<![CDATA[NL0005TEST]]>
 +
</nh2:DocumentControlFieldText>
 +
<nh2:MessageReceiveDate>11/24/2019</nh2:MessageReceiveDate>
 +
<nh2:MessageReceiveTime>12:35</nh2:MessageReceiveTime>
 +
<nh2:MessageSendDate>11/24/2019</nh2:MessageSendDate>
 +
<nh2:MessageSendTime>12:35</nh2:MessageSendTime>
 +
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
 +
<nh2:SendMessageNumeric>00412</nh2:SendMessageNumeric>
 +
</n2:NLETSMessageHeader>
 +
<n2:NLETSResponseData n2:key="PDR">
 +
<nds2:DriverStatus xmlns:nds2="http://www.nlets.org/niem/nlets-driver-status/1.0">
 +
<n2c:AdditionalInformation xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
 +
<n2c:StateElement>
 +
<n2c:ElementFieldName>HEADER</n2c:ElementFieldName>
 +
<n2c:ElementFieldValue>DR.AZNLETS39..05LW003XXD..</n2c:ElementFieldValue>
 +
</n2c:StateElement>
 +
<n2c:StateElement>
 +
<n2c:ElementFieldName>CAVEAT</n2c:ElementFieldName>
 +
<n2c:ElementFieldValue>THIS INFORMATION MAY BE USED FOR CRIMINAL JUSTICE PURPOSES ONLY.</n2c:ElementFieldValue>
 +
</n2c:StateElement>
 +
</n2c:AdditionalInformation>
 +
</nds2:DriverStatus>
 +
<ndm2:DriverMatch xmlns:ndm2="http://www.nlets.org/niem/nlets-driver-match/1.0">
 +
<ndm2:IndividualMatch>
 +
<n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
 +
<nc:PersonBirthDate>
 +
<nc:Date>1991-06-02</nc:Date>
 +
</nc:PersonBirthDate>
 +
<nc:PersonEyeColorText>BLU</nc:PersonEyeColorText>
 +
<nc:PersonHairColorText>BLN</nc:PersonHairColorText>
 +
<nc:PersonHeightMeasure>
 +
<nc:MeasurePointValue>509</nc:MeasurePointValue>
 +
</nc:PersonHeightMeasure>
 +
<nc:PersonName>
 +
<nc:PersonGivenName>JERROD</nc:PersonGivenName>
 +
<nc:PersonMiddleName>L</nc:PersonMiddleName>
 +
<nc:PersonSurName>DOE</nc:PersonSurName>
 +
</nc:PersonName>
 +
<nc:PersonRaceText>W</nc:PersonRaceText>
 +
<nc:PersonSexText>M</nc:PersonSexText>
 +
<nc:PersonWeightMeasure>
 +
<nc:MeasurePointValue>170</nc:MeasurePointValue>
 +
</nc:PersonWeightMeasure>
 +
<n2c:DriverLicense>
 +
<nc:DriverLicenseIdentification>
 +
<nc:IdentificationID si:type="nc:TextType" xmlns:si="http://www.w3.org/2001/XMLSchema-instance">H12345678</nc:IdentificationID>
 +
</nc:DriverLicenseIdentification>
 +
</n2c:DriverLicense>
 +
<n2c:PersonContactInformation>
 +
<nc:ContactMailingAddress>
 +
<nc:StructuredAddress>
 +
<nc:LocationStreet>
 +
<nc:StreetFullText>321 W CIRCLE DR</nc:StreetFullText>
 +
</nc:LocationStreet>
 +
<nc:LocationCityName>NORTH PLATTE</nc:LocationCityName>
 +
<nc:LocationStateName>NE</nc:LocationStateName>
 +
<nc:LocationPostalCode>69101</nc:LocationPostalCode>
 +
</nc:StructuredAddress>
 +
</nc:ContactMailingAddress>
 +
</n2c:PersonContactInformation>
 +
</n2c:Driver>
 +
</ndm2:IndividualMatch>
 +
<ndm2:IndividualMatch>
 +
<n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
 +
<nc:PersonBirthDate>
 +
<nc:Date>1989-07-18</nc:Date>
 +
</nc:PersonBirthDate>
 +
<nc:PersonEyeColorText>GRN</nc:PersonEyeColorText>
 +
<nc:PersonHairColorText>BRO</nc:PersonHairColorText>
 +
<nc:PersonHeightMeasure>
 +
<nc:MeasurePointValue>508</nc:MeasurePointValue>
 +
</nc:PersonHeightMeasure>
 +
<nc:PersonName>
 +
<nc:PersonGivenName>JAMES</nc:PersonGivenName>
 +
<nc:PersonSurName>DOEE</nc:PersonSurName>
 +
</nc:PersonName>
 +
<nc:PersonRaceText>W</nc:PersonRaceText>
 +
<nc:PersonSexText>M</nc:PersonSexText>
 +
<nc:PersonWeightMeasure>
 +
<nc:MeasurePointValue>160</nc:MeasurePointValue>
 +
</nc:PersonWeightMeasure>
 +
<n2c:DriverLicense>
 +
<nc:DriverLicenseIdentification>
 +
<nc:IdentificationID si:type="nc:TextType" xmlns:si="http://www.w3.org/2001/XMLSchema-instance">H23456789</nc:IdentificationID>
 +
</nc:DriverLicenseIdentification>
 +
</n2c:DriverLicense>
 +
<n2c:PersonContactInformation>
 +
<nc:ContactMailingAddress>
 +
<nc:StructuredAddress>
 +
<nc:LocationStreet>
 +
<nc:StreetFullText>321 S BIRCHWOOD DR APT B</nc:StreetFullText>
 +
</nc:LocationStreet>
 +
<nc:LocationCityName>FREMONT</nc:LocationCityName>
 +
<nc:LocationStateName>NE</nc:LocationStateName>
 +
<nc:LocationPostalCode>68025</nc:LocationPostalCode>
 +
</nc:StructuredAddress>
 +
</nc:ContactMailingAddress>
 +
</n2c:PersonContactInformation>
 +
</n2c:Driver>
 +
</ndm2:IndividualMatch>
 +
<ndm2:IndividualMatch>
 +
<n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
 +
<nc:PersonBirthDate>
 +
<nc:Date>1985-12-12</nc:Date>
 +
</nc:PersonBirthDate>
 +
<nc:PersonEyeColorText>HAZ</nc:PersonEyeColorText>
 +
<nc:PersonHairColorText>BLK</nc:PersonHairColorText>
 +
<nc:PersonHeightMeasure>
 +
<nc:MeasurePointValue>511</nc:MeasurePointValue>
 +
</nc:PersonHeightMeasure>
 +
<nc:PersonName>
 +
<nc:PersonGivenName>JEFFREY</nc:PersonGivenName>
 +
<nc:PersonMiddleName>D</nc:PersonMiddleName>
 +
<nc:PersonSurName>DOEE</nc:PersonSurName>
 +
</nc:PersonName>
 +
<nc:PersonRaceText>W</nc:PersonRaceText>
 +
<nc:PersonSexText>M</nc:PersonSexText>
 +
<nc:PersonWeightMeasure>
 +
<nc:MeasurePointValue>175</nc:MeasurePointValue>
 +
</nc:PersonWeightMeasure>
 +
<n2c:DriverLicense>
 +
<nc:DriverLicenseIdentification>
 +
<nc:IdentificationID si:type="nc:TextType" xmlns:si="http://www.w3.org/2001/XMLSchema-instance">H34567890</nc:IdentificationID>
 +
</nc:DriverLicenseIdentification>
 +
</n2c:DriverLicense>
 +
<n2c:PersonContactInformation>
 +
<nc:ContactMailingAddress>
 +
<nc:StructuredAddress>
 +
<nc:LocationStreet>
 +
<nc:StreetFullText>4321 JACOBS CREEK DR APT 232</nc:StreetFullText>
 +
</nc:LocationStreet>
 +
<nc:LocationCityName>LINCOLN</nc:LocationCityName>
 +
<nc:LocationStateName>NE</nc:LocationStateName>
 +
<nc:LocationPostalCode>68512</nc:LocationPostalCode>
 +
</nc:StructuredAddress>
 +
</nc:ContactMailingAddress>
 +
</n2c:PersonContactInformation>
 +
</n2c:Driver>
 +
</ndm2:IndividualMatch>
 +
<ndm2:IndividualMatch>
 +
<n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
 +
<nc:PersonBirthDate>
 +
<nc:Date>1982-11-27</nc:Date>
 +
</nc:PersonBirthDate>
 +
<nc:PersonEyeColorText>GRN</nc:PersonEyeColorText>
 +
<nc:PersonHairColorText>BRO</nc:PersonHairColorText>
 +
<nc:PersonHeightMeasure>
 +
<nc:MeasurePointValue>604</nc:MeasurePointValue>
 +
</nc:PersonHeightMeasure>
 +
<nc:PersonName>
 +
<nc:PersonGivenName>JACOB</nc:PersonGivenName>
 +
<nc:PersonMiddleName>J</nc:PersonMiddleName>
 +
<nc:PersonSurName>DOOE</nc:PersonSurName>
 +
</nc:PersonName>
 +
<nc:PersonRaceText>W</nc:PersonRaceText>
 +
<nc:PersonSexText>M</nc:PersonSexText>
 +
<nc:PersonWeightMeasure>
 +
<nc:MeasurePointValue>195</nc:MeasurePointValue>
 +
</nc:PersonWeightMeasure>
 +
<n2c:DriverLicense>
 +
<nc:DriverLicenseIdentification>
 +
<nc:IdentificationID si:type="nc:TextType" xmlns:si="http://www.w3.org/2001/XMLSchema-instance">H45678901</nc:IdentificationID>
 +
</nc:DriverLicenseIdentification>
 +
</n2c:DriverLicense>
 +
<n2c:PersonContactInformation>
 +
<nc:ContactMailingAddress>
 +
<nc:StructuredAddress>
 +
<nc:LocationStreet>
 +
<nc:StreetFullText>3210 FIELDCREST DR</nc:StreetFullText>
 +
</nc:LocationStreet>
 +
<nc:LocationCityName>OMAHA</nc:LocationCityName>
 +
<nc:LocationStateName>NE</nc:LocationStateName>
 +
<nc:LocationPostalCode>68114</nc:LocationPostalCode>
 +
</nc:StructuredAddress>
 +
</nc:ContactMailingAddress>
 +
</n2c:PersonContactInformation>
 +
</n2c:Driver>
 +
</ndm2:IndividualMatch>
 +
</ndm2:DriverMatch>
 +
<n2:OriginalTextResponse>NEBRASKA DMV RESPONSE
 +
 
 +
DR.AZNLETS39..05LW003XXD..
 +
STATE OF NEBRASKA DRIVER LICENSE QUERY CANDIDATE LIST
 +
 
 +
THIS INFORMATION MAY BE USED FOR CRIMINAL JUSTICE PURPOSES ONLY.
 +
 
 +
OLN/H12345678  DOE,JERROD,L              DOB/06-02-1991 SEX/M
 +
RAC/W  HGT/509  WGT/170  EYE/BLU  HAI/BLN
 +
321 W CIRCLE DR                  NORTH PLATTE, NE.  69101
 +
 
 +
OLN/H23456789  DOEE,JAMES                   DOB/07-18-1989 SEX/M
 +
RAC/W  HGT/508  WGT/160  EYE/GRN  HAI/BRO
 +
321 S BIRCHWOOD DR APT B          FREMONT, NE.  68025
 +
 
 +
OLN/H34567890  DOEE,JEFFREY,D              DOB/12-12-1985 SEX/M
 +
RAC/W  HGT/511  WGT/175  EYE/HAZ  HAI/BLK
 +
4321 JACOBS CREEK DR APT 232      LINCOLN, NE.  68512
 +
 
 +
OLN/H45678901  DOOE,JACOB,J                DOB/11-27-1982 SEX/M
 +
RAC/W  HGT/604  WGT/195  EYE/GRN  HAI/BRO
 +
3210 FIELDCREST DR                OMAHA, NE.  68114
 +
 
 +
*** END OF CANDIDATE LIST ***
 +
 
 +
 
 +
</n2:OriginalTextResponse>
 +
</n2:NLETSResponseData>
 +
</n2:NLETS>
 +
  </syntaxhighlight>
 +
</th>
 +
</tr>
 +
</table>
  
ACTION INFORMATION:
 
1 TYPE/POINT REVOCATION                    CASE NO/AB12345678  EFF DT/01012016
 
  STATUS/ACTIVE                          ELIGIBLE REI/05 21 2017 OFFENSE ST/
 
  
* ADDTL PERMITS AND LICENSES FOR LIC# D12345678 *******
 
OLT/ID CARD    ISS:02/25/2016 EXP:NONE      STATUS/
 
    .RC#/BB092139</n2:OriginalTextResponse>
 
    <nds2:DriverStatus>
 
      <nds2:StandardResponse>
 
        <n2c:Driver>
 
          <nc:PersonSexText>F</nc:PersonSexText>
 
          <nc:PersonBirthDate>
 
            <nc:Date>1981-08-07</nc:Date>
 
          </nc:PersonBirthDate>
 
          <nc:PersonEyeColorText>EYE:</nc:PersonEyeColorText>
 
          <nc:PersonHairColorText>BRN</nc:PersonHairColorText>
 
          <nc:PersonHeightMeasure>
 
            <nc:MeasureUnitText>501</nc:MeasureUnitText>
 
          </nc:PersonHeightMeasure>
 
          <nc:PersonName>
 
            <nc:PersonFullName>SMITH,JOHN Q</nc:PersonFullName>
 
          </nc:PersonName>
 
          <nc:PersonSSNIdentification>
 
            <nc:IdentificationID>555443333</nc:IdentificationID>
 
          </nc:PersonSSNIdentification>
 
          <nc:PersonWeightMeasure>
 
            <nc:MeasureUnitText>135</nc:MeasureUnitText>
 
          </nc:PersonWeightMeasure>
 
          <n2c:DriverLicense>
 
            <nc:DriverLicenseIdentification>
 
              <nc:IdentificationID>D12345678</nc:IdentificationID>
 
            </nc:DriverLicenseIdentification>
 
            <nc:DriverLicenseExpirationDate>
 
              <nc:Date>00/00/0000</nc:Date>
 
            </nc:DriverLicenseExpirationDate>
 
            <nc:DriverLicenseIssueDate>
 
              <nc:Date>00/00/0000</nc:Date>
 
            </nc:DriverLicenseIssueDate>
 
            <nc:DriverLicenseNonCommercialStatusText>NO LICENSE</nc:DriverLicenseNonCommercialStatusText>
 
          </n2c:DriverLicense>
 
          <n2c:DriverLicense>
 
            <nc:DriverLicenseIdentification>
 
              <nc:IdentificationID>D12345678</nc:IdentificationID>
 
              <nc:IdentificationJurisdictionText>AZ</nc:IdentificationJurisdictionText>
 
            </nc:DriverLicenseIdentification>
 
            <nc:DriverLicenseNonCommercialStatusText>EXPIRED</nc:DriverLicenseNonCommercialStatusText>
 
            <nc:DriverLicenseNonCommercialStatusText>PREV LIC</nc:DriverLicenseNonCommercialStatusText>
 
          </n2c:DriverLicense>
 
          <n2c:DriverLicense>
 
            <nc:DriverLicenseIdentification>
 
              <nc:IdentificationID>D12345678</nc:IdentificationID>
 
              <nc:IdentificationJurisdictionText>AZ</nc:IdentificationJurisdictionText>
 
            </nc:DriverLicenseIdentification>
 
            <nc:DriverLicenseNonCommercialStatusText>EXPIRED</nc:DriverLicenseNonCommercialStatusText>
 
            <nc:DriverLicenseNonCommercialStatusText>PREV LIC</nc:DriverLicenseNonCommercialStatusText>
 
          </n2c:DriverLicense>
 
          <n2c:DriverLicense>
 
            <nc:DriverLicenseIdentification>
 
              <nc:IdentificationID>D12345678</nc:IdentificationID>
 
              <nc:IdentificationJurisdictionText>AZ</nc:IdentificationJurisdictionText>
 
            </nc:DriverLicenseIdentification>
 
            <nc:DriverLicenseNonCommercialStatusText>EXPIRED</nc:DriverLicenseNonCommercialStatusText>
 
            <nc:DriverLicenseNonCommercialStatusText>PREV LIC</nc:DriverLicenseNonCommercialStatusText>
 
          </n2c:DriverLicense>
 
          <n2c:DriverLicense>
 
            <nc:DriverLicenseIdentification>
 
              <nc:IdentificationJurisdictionText>NONE</nc:IdentificationJurisdictionText>
 
            </nc:DriverLicenseIdentification>
 
            <nc:DriverLicenseNonCommercialStatusText>ID CARD</nc:DriverLicenseNonCommercialStatusText>
 
          </n2c:DriverLicense>
 
          <n2c:PersonContactInformation>
 
            <nc:ContactMailingAddress>
 
              <nc:StructuredAddress>
 
                <nc:LocationStreet>
 
                  <nc:StreetFullText>4321 ANYSTREET</nc:StreetFullText>
 
                </nc:LocationStreet>
 
                <nc:LocationCityName>PHOENIX</nc:LocationCityName>
 
                <nc:LocationStateName>AZ</nc:LocationStateName>
 
                <nc:LocationPostalCode>85000</nc:LocationPostalCode>
 
              </nc:StructuredAddress>
 
            </nc:ContactMailingAddress>
 
          </n2c:PersonContactInformation>
 
          <n2c:PersonContactInformation>
 
            <nc:ContactMailingAddress>
 
              <nc:StructuredAddress>
 
                <nc:LocationStreet>
 
                  <nc:StreetFullText>1234 ANYSTREET</nc:StreetFullText>
 
                </nc:LocationStreet>
 
                <nc:LocationCityName>PHOENIX</nc:LocationCityName>
 
                <nc:LocationStateName>AZ</nc:LocationStateName>
 
                <nc:LocationPostalCode>85000</nc:LocationPostalCode>
 
              </nc:StructuredAddress>
 
            </nc:ContactMailingAddress>
 
          </n2c:PersonContactInformation>
 
        </n2c:Driver>
 
      </nds2:StandardResponse>
 
      <n2c:AdditionalInformation>
 
        <n2c:StateElement>
 
          <n2c:ElementFieldName>ID 0 RECEIPT CODE</n2c:ElementFieldName>
 
          <n2c:ElementFieldValue>BB092139</n2c:ElementFieldValue>
 
        </n2c:StateElement>
 
        <n2c:StateElement>
 
          <n2c:ElementFieldName>PRIMARY LICENSE RECEIPT CODE</n2c:ElementFieldName>
 
          <n2c:ElementFieldValue>UNKNOWN</n2c:ElementFieldValue>
 
        </n2c:StateElement>
 
      </n2c:AdditionalInformation>
 
    </nds2:DriverStatus>
 
  </n2:NLETSResponseData>
 
</n2:NLETS>
 
  </syntaxhighlight>
 
</th>
 
</tr>
 
</table>
 
  
<u>Example 2</u>: A Parsed Driver's License Match List Response.
+
[[#top|Top]]
  
<table border="1">
+
==Legacy (DEPRECATED)==
<tr>
 
<th align="left">
 
  <syntaxhighlight lang="xml">
 
<n2:NLETS xmlns:j="http://niem.gov/niem/domains/jxdm/4.1" xmlns:ndc2="http://www.nlets.org/niem/nlets-driver-cert/1.0" xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0" xmlns:nds2="http://www.nlets.org/niem/nlets-driver-status/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:ndm2="http://www.nlets.org/niem/nlets-driver-match/1.0" xmlns:n2="http://www.nlets.org/niem/1.0">
 
  <n2:NLETSMessageHeader>
 
    <nh2:MessageKeyCodeText>PDR</nh2:MessageKeyCodeText>
 
    <nh2:OriginatingORIID>NBDMV0000</nh2:OriginatingORIID>
 
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
 
    <nh2:MessageReceiveDate>01/01/2016</nh2:MessageReceiveDate>
 
    <nh2:MessageReceiveTime>01:01</nh2:MessageReceiveTime>
 
    <nh2:MessageSendDate>01/01/2016</nh2:MessageSendDate>
 
    <nh2:MessageSendTime>01:01</nh2:MessageSendTime>
 
    <nh2:ReceiveMessageNumeric>12345</nh2:ReceiveMessageNumeric>
 
    <nh2:SendMessageNumeric>54321</nh2:SendMessageNumeric>
 
  </n2:NLETSMessageHeader>
 
  <n2:NLETSResponseData n2:key="PDR">
 
    <n2:OriginalTextResponse>NEBRASKA DMV RESPONSE
 
  
DR.AZNLETS20..04OL000DUD..
 
STATE OF NEBRASKA DRIVER LICENSE QUERY CANDIDATE LIST
 
  
THIS INFORMATION MAY BE USED FOR CRIMINAL JUSTICE PURPOSES ONLY.
+
===Driver's License Legacy Specifications===
  
OLN/H12345678  SMITH,JOHN,S                    DOB/09-14-1978 SEX/U
+
This section describes Legacy format and provides examples for driver's license transactions.
RAC/U  HGT/000  WGT/000  EYE/UNK  HAI/UNK
 
1234 ANYSTREET                    OMAHA, NE. 00000
 
  
OLN/H23456789  SMITH,JOHN,B                    DOB/07-11-1974 SEX/M
+
The following are general specifications for Driver's License queries and responses.
RAC/W  HGT/602  WGT/190  EYE/BLU  HAI/BLN
+
<ul>
2345 ANYSTREET                    OMAHA, NE.  00000
+
<li>All inquiries and responses are in a fixed format.
 +
<li>All messages are preceded by a standard input header as described in [[Section 03: Message Structure|Message Structure]].
 +
<li>All data elements are preceded by a prefix and terminated by a period.
 +
<li>The final character of the message should not be a period (conforms to standard NCIC message structure).
 +
<li>Control characters are permitted throughout the text of the message and should be ignored by the queried state when examining the inquiry.
 +
<li>No embedded spaces or special characters (i.e. hyphens) should be in the inquiry.
 +
<li>If a regional code is used, the message type should be DQG. If it is not, Nlets will change it to DQG and handle it at a lower priority.
 +
<li>States receiving a DQG must respond with a DRG.
 +
</ul>
  
OLN/H34567890  SMITH,JOHN,C                    DOB/11-26-1977 SEX/M
+
====Query Formats====
RAC/B  HGT/603  WGT/200  EYE/BRO  HAI/BLK
 
3456 ANYSTREET                    OMAHA, NE.  00000
 
  
*** MORE ENTRIES IN CANDIDATE LIST. NEXT REFERENCE IS 031 ***
+
To send a driver's license query:
$NSP DQ.CA0330031..04OL000DUD..NAM/SMITH,JOHN.DOB/19771024.SEX/M
 
  
 
+
<table border="1">
</n2:OriginalTextResponse>
+
<tr>
    <ndm2:DriverMatch>
+
<th align="left">Enter the following:</th>
      <ndm2:IndividualMatch>
+
</tr>
        <n2c:Driver>
+
<tr>
          <nc:PersonSexText>U</nc:PersonSexText>
+
<th align="left">DQ. or DQG.</th>
          <nc:PersonBirthDate>
+
</tr>
            <nc:Date>1978-09-14</nc:Date>
+
<tr>
          </nc:PersonBirthDate>
+
<th align="left">Sending ORI followed by a period.</th>
          <nc:PersonEyeColorText>UNK</nc:PersonEyeColorText>
+
</tr>
          <nc:PersonHairColorText>UNK</nc:PersonHairColorText>
+
<tr>
          <nc:PersonHeightMeasure>
+
<th align="left">Destination ORI followed by a period (up to five 2-character state codes or regional codes; if
            <nc:MeasureUnitText>000</nc:MeasureUnitText>
+
<br>a regional code the DQG should be used).</th>
          </nc:PersonHeightMeasure>
+
</tr>
          <nc:PersonName>
+
<tr>
            <nc:PersonGivenName>JOHN</nc:PersonGivenName>
+
<th align="left">If needed, optional control field.</th>
            <nc:PersonMiddleName>A</nc:PersonMiddleName>
+
</tr>
            <nc:PersonSurName>SMITH</nc:PersonSurName>
+
<tr>
          </nc:PersonName>
+
<th align="left">TXT</th>
          <nc:PersonRaceText>U</nc:PersonRaceText>
+
</tr>
          <nc:PersonWeightMeasure>
+
<tr>
            <nc:MeasureUnitText>000</nc:MeasureUnitText>
+
<th align="left">CR,LF,DEL (Optional).</th>
          </nc:PersonWeightMeasure>
+
</tr>
          <n2c:DriverLicense>
+
<tr>
            <nc:DriverLicenseIdentification>
+
<th align="left">Enter either:</th>
              <nc:IdentificationID>H12345678</nc:IdentificationID>
+
</tr>
            </nc:DriverLicenseIdentification>
+
<tr>
          </n2c:DriverLicense>
+
<th align="left">"OLN/" followed by the driver's license number. Not valid for DQG.</th>
          <n2c:PersonContactInformation>
+
</tr>
            <nc:ContactMailingAddress>
+
<tr>
              <nc:StructuredAddress>
+
<th align="left">OR-</th>
                <nc:LocationStreet>
+
</tr>
                  <nc:StreetFullText>1234 ANYSTREET</nc:StreetFullText>
+
<tr>
                </nc:LocationStreet>
+
<th align="left">"NAM/" followed by the name and a period.</th>
                <nc:LocationCityName>MAHA</nc:LocationCityName>
+
</tr>
                <nc:LocationStateName>NE</nc:LocationStateName>
+
<tr>
                <nc:LocationPostalCode>00000</nc:LocationPostalCode>
+
<th align="left">"DOB/" followed by the complete date of birth and a period. Format: mmddyy or ccyymmdd.</th>
              </nc:StructuredAddress>
+
</tr>
            </nc:ContactMailingAddress>
+
<tr>
          </n2c:PersonContactInformation>
+
<th align="left">"SEX/" followed by the sex code.</th>
        </n2c:Driver>
+
</tr>
      </ndm2:IndividualMatch>
+
<tr>
      <ndm2:IndividualMatch>
+
<th align="left">Only queries on NAM/DOB may be used for a DQG.</th>
        <n2c:Driver>
+
</tr>
          <nc:PersonSexText>M</nc:PersonSexText>
+
<tr>
          <nc:PersonBirthDate>
+
<th align="left">"IMQ/" followed by a "Y" or "N"; for DQ only, not for DQG.</th>
            <nc:Date>1974-07-11</nc:Date>
+
</tr>
          </nc:PersonBirthDate>
+
</table>
          <nc:PersonEyeColorText>BLU</nc:PersonEyeColorText>
+
 
          <nc:PersonHairColorText>BLN</nc:PersonHairColorText>
+
<table border="1">
          <nc:PersonHeightMeasure>
+
<tr>
            <nc:MeasureUnitText>602</nc:MeasureUnitText>
+
<th align="left">
          </nc:PersonHeightMeasure>
+
Note: Nlets also supports inquiries on [[Section 14: Driver History Transactions|Driver history information]].
          <nc:PersonName>
+
<br>The user should recognize the differences between these two types of transactions as described below.
            <nc:PersonGivenName>JOHN</nc:PersonGivenName>
+
<ul>
            <nc:PersonMiddleName>B</nc:PersonMiddleName>
+
<li>Driver's License transactions and Driver History transactions utilize different message types.
            <nc:PersonSurName>SMITH</nc:PersonSurName>
+
<li>Driver history requests and responses use KQ and KR respectively, while normal driver
          </nc:PersonName>
+
<br>&nbsp;license requests utilize DQ/DR.
          <nc:PersonRaceText>W</nc:PersonRaceText>
+
<li>Although the required information is identical, users requesting driver history with a KQ may
          <nc:PersonWeightMeasure>
+
<br>&nbsp;include a purpose code and/or an attention field.
            <nc:MeasureUnitText>190</nc:MeasureUnitText>
+
<li>There are no specific response formats for KRs as there are for DRs.
          </nc:PersonWeightMeasure>
+
<li>Unlike DQs only a single two character state code may be used as a destination address for KQs.
          <n2c:DriverLicense>
+
</ul></th>
            <nc:DriverLicenseIdentification>
+
</tr>
              <nc:IdentificationID>H23456789</nc:IdentificationID>
 
            </nc:DriverLicenseIdentification>
 
          </n2c:DriverLicense>
 
          <n2c:PersonContactInformation>
 
            <nc:ContactMailingAddress>
 
              <nc:StructuredAddress>
 
                <nc:LocationStreet>
 
                  <nc:StreetFullText>2345 ANYSTREET</nc:StreetFullText>
 
                </nc:LocationStreet>
 
                <nc:LocationCityName>MAHA</nc:LocationCityName>
 
                <nc:LocationStateName>NE</nc:LocationStateName>
 
                <nc:LocationPostalCode>00000</nc:LocationPostalCode>
 
              </nc:StructuredAddress>
 
            </nc:ContactMailingAddress>
 
          </n2c:PersonContactInformation>
 
        </n2c:Driver>
 
      </ndm2:IndividualMatch>
 
      <ndm2:IndividualMatch>
 
        <n2c:Driver>
 
          <nc:PersonSexText>M</nc:PersonSexText>
 
          <nc:PersonBirthDate>
 
            <nc:Date>1977-11-26</nc:Date>
 
          </nc:PersonBirthDate>
 
          <nc:PersonEyeColorText>BRO</nc:PersonEyeColorText>
 
          <nc:PersonHairColorText>BLK</nc:PersonHairColorText>
 
          <nc:PersonHeightMeasure>
 
            <nc:MeasureUnitText>603</nc:MeasureUnitText>
 
          </nc:PersonHeightMeasure>
 
          <nc:PersonName>
 
            <nc:PersonGivenName>JOHN</nc:PersonGivenName>
 
            <nc:PersonMiddleName>C</nc:PersonMiddleName>
 
            <nc:PersonSurName>SMITH</nc:PersonSurName>
 
          </nc:PersonName>
 
          <nc:PersonRaceText>B</nc:PersonRaceText>
 
          <nc:PersonWeightMeasure>
 
            <nc:MeasureUnitText>200</nc:MeasureUnitText>
 
          </nc:PersonWeightMeasure>
 
          <n2c:DriverLicense>
 
            <nc:DriverLicenseIdentification>
 
              <nc:IdentificationID>H34567890</nc:IdentificationID>
 
            </nc:DriverLicenseIdentification>
 
          </n2c:DriverLicense>
 
          <n2c:PersonContactInformation>
 
            <nc:ContactMailingAddress>
 
              <nc:StructuredAddress>
 
                <nc:LocationStreet>
 
                  <nc:StreetFullText>3456 ANYSTREET</nc:StreetFullText>
 
                </nc:LocationStreet>
 
                <nc:LocationCityName>MAHA</nc:LocationCityName>
 
                <nc:LocationStateName>NE</nc:LocationStateName>
 
                <nc:LocationPostalCode>00000</nc:LocationPostalCode>
 
              </nc:StructuredAddress>
 
            </nc:ContactMailingAddress>
 
          </n2c:PersonContactInformation>
 
        </n2c:Driver>
 
      </ndm2:IndividualMatch>
 
    </ndm2:DriverMatch>
 
  </n2:NLETSResponseData>
 
</n2:NLETS>
 
  </syntaxhighlight>
 
</th>
 
</tr>
 
 
</table>
 
</table>
  
 +
The format for a driver's license inquiry on name and date of birth is as follows.
  
 
+
<table border="1">
[[#top|Top]]
+
<tr>
 
+
<th align="center">Entry</th>
==Legacy (DEPRECATED)==
+
<th align="center"># Char.</th>
 
+
<th align="center">Explanation</th>
 
+
</tr>
===Driver's License Legacy Specifications===
+
<tr>
 
+
<th align="left">
This section describes Legacy format and provides examples for driver's license transactions.
+
DQ.
 
+
<br>or
The following are general specifications for Driver's License queries and responses.
+
<br>DQG
<ul>
+
</th>
<li>All inquiries and responses are in a fixed format.  
+
<th align="center">2</th>
<li>All messages are preceded by a standard input header as described in [[Section 03: Message Structure|Message Structure]].
+
<th align="left">Message type followed by a period.</th>
<li>All data elements are preceded by a prefix and terminated by a period.
 
<li>The final character of the message should not be a period (conforms to standard NCIC message structure).
 
<li>Control characters are permitted throughout the text of the message and should be ignored by the queried state when examining the inquiry.
 
<li>No embedded spaces or special characters (i.e. hyphens) should be in the inquiry.  
 
<li>If a regional code is used, the message type should be DQG. If it is not, Nlets will change it to DQG and handle it at a lower priority.
 
<li>States receiving a DQG must respond with a DRG.
 
</ul>
 
 
 
====Query Formats====
 
 
 
To send a driver's license query:
 
 
 
<table border="1">
 
<tr>
 
<th align="left">Enter the following:</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">DQ. or DQG.</th>
+
<th align="left">Message Header</th>
 +
<th align="center">13-36</th>
 +
<th align="left">
 +
Standard input message header, may include control
 +
<br>field and up to 5 addresses (state or regional codes;
 +
<br>DQG should be used for regionally addressed queries).
 +
</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">Sending ORI followed by a period.</th>
+
<th align="left">TXT</th>
 +
<th align="center">3</th>
 +
<th align="left">Fixed filed prefix to beginning of message.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">Destination ORI followed by a period (up to five 2-character state codes or regional codes; if
+
<th align="left">CR,LF,DEL</th>
<br>a regional code the DQG should be used).</th>
+
<th align="center">3</th>
 +
<th align="left">Control characters (optional).</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">If needed, optional control field.</th>
+
<th align="left">NAM/</th>
 +
<th align="center">4</th>
 +
<th align="left">Prefix to identify name.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">TXT</th>
+
<th align="left">Name</th>
 +
<th align="center">Max. 30</th>
 +
<th align="left">
 +
Full name; format is last name, comma, space after
 +
<br>comma is optional) first name, space, middle initial or
 +
<br>name, space, suffix (Jr., III, etc.) Followed by a period.
 +
<br>Titles or degrees should not be used as part of the
 +
<br>name.
 +
</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">CR,LF,DEL (Optional).</th>
+
<th align="left">DOB/</th>
 +
<th align="center">4</th>
 +
<th align="left">Prefix to identify date of birth.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">Enter either:</th>
+
<th align="left">Date of Birth</th>
 +
<th align="center">6</th>
 +
<th align="left">
 +
Date of Birth followed by a period. Express as mmddyy
 +
<br>or ccyymmdd. Complete DOB must be present. Some
 +
<br>states have different requirements. Check their OLN
 +
<br>HELP file for details.
 +
</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">"OLN/" followed by the driver's license number.</th>
+
<th align="left">SEX/</th>
 +
<th align="center">4</th>
 +
<th align="left">Prefix to identify sex.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">OR-</th>
+
<th align="left">Sex</th>
 +
<th align="center">1</th>
 +
<th align="left">Sex; conforms to NCIC codes.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">"NAM/" followed by the name and a period.</th>
+
<th align="left">IMQ/</th>
 +
<th align="center">4</th>
 +
<th align="left">(For XML use only) Prefix to identify image request field.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">"DOB/" followed by the complete date of birth and a period. Format: mmddyy or ccyymmdd.</th>
+
<th align="left">Image Request</th>
 +
<th align="center">1</th>
 +
<th align="left">Y to request driver photo; use N if no image is wanted
 +
<br>or omit IMQ/ field.</th>
 
</tr>
 
</tr>
 +
</table>
 +
 +
The format for a driver's license inquiry or driver's license number is:
 +
 +
<table border="1">
 
<tr>
 
<tr>
<th align="left">"SEX/" followed by the sex code.</th>
+
<th align="center">Entry</th>
 +
<th align="center"># Char.</th>
 +
<th align="center">Explanation</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">Only queries on NAM/DOB may be used for a DQG.</th>
+
<th align="left">DQ.</th>
 +
<th align="center">3</th>
 +
<th align="left">Message type followed by a period.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">"IMQ/" followed by a "Y" or "N"; for DQ only, not for DQG.</th>
+
<th align="left">Message Header</th>
 +
<th align="center">13-36</th>
 +
<th align="left">Standard input message header may include control field.</th>
 
</tr>
 
</tr>
</table>
 
 
<table border="1">
 
 
<tr>
 
<tr>
<th align="left">
+
<th align="left">TXT</th>
Note: Nlets also supports inquiries on [[Section 14: Driver History Transactions|Driver history information]].
+
<th align="center">3</th>
<br>The user should recognize the differences between these two types of transactions as described below.
+
<th align="left">Fixed filed prefix to beginning of message.</th>
<ul>
+
</tr>
<li>Driver's License transactions and Driver History transactions utilize different message types.
+
<tr>
<li>Driver history requests and responses use KQ and KR respectively, while normal driver
+
<th align="left">CR,LF,DEL</th>
<br>&nbsp;license requests utilize DQ/DR.
+
<th align="center">3</th>
<li>Although the required information is identical, users requesting driver history with a KQ may
+
<th align="left">Control characters (optional).</th>
<br>&nbsp;include a purpose code and/or an attention field.
 
<li>There are no specific response formats for KRs as there are for DRs.
 
<li>Unlike DQs only a single two character state code may be used as a destination address for KQs.
 
</ul></th>
 
 
</tr>
 
</tr>
</table>
 
 
The format for a driver's license inquiry on name and date of birth is as follows.
 
 
<table border="1">
 
 
<tr>
 
<tr>
<th align="center">Entry</th>
+
<th align="left">OLN/</th>
<th align="center"># Char.</th>
+
<th align="center">4</th>
<th align="center">Explanation</th>
+
<th align="left">Prefix to identify driver license number.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">
+
<th align="left">Driver's Lic. #</th>
DQ.
+
<th align="center">1-20</th>
<br>or
+
<th align="left">Driver license number.</th>
<br>DQG
 
</th>
 
<th align="center">2</th>
 
<th align="left">Message type followed by a period.</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">Message Header</th>
+
<th align="left">IMQ/</th>
<th align="center">13-36</th>
+
<th align="center">4</th>
<th align="left">
+
<th align="left">(For XML use only) Prefix to identify image request field.</th>
Standard input message header, may include control
 
<br>field and up to 5 addresses (state or regional codes;
 
<br>DQG should be used for regionally addressed queries).
 
</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">TXT</th>
+
<th align="left">Image Request</th>
<th align="center">3</th>
+
<th align="center">1</th>
<th align="left">Fixed filed prefix to beginning of message.</th>
+
<th align="left">Y to request driver photo; use N if no image is wanted
 +
<br>or omit IMQ/ field.</th>
 
</tr>
 
</tr>
 +
</table>
 +
 +
====Response Formats====
 +
 +
<ul>
 +
<li>Should the information be unavailable, or, after interrogation of the state files, no information is found, a standard response message is returned.
 +
<li>If a data field is unavailable, the prefix, data element, and period should be omitted from the response.
 +
<li>The message should be compacted to eliminate the resultant spaces.
 +
</ul>
 +
 +
<table border="1">
 
<tr>
 
<tr>
<th align="left">CR,LF,DEL</th>
+
<th align="left">
<th align="center">3</th>
+
Note: Inquiries on name may result in multiple hits. Only close matches (i.e., exact match on
<th align="left">Control characters (optional).</th>
+
<br>last name and DOB) should be returned. When multiple hits do occur, they should be
 +
<br>returned as separate messages.
 +
</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">NAM/</th>
+
<th align="left">Note: All responses to DNQ inquiries must have a message type of DNR.</th>
<th align="center">4</th>
 
<th align="left">Prefix to identify name.</th>
 
 
</tr>
 
</tr>
 +
</table>
 +
 +
<table border="1">
 
<tr>
 
<tr>
<th align="left">Name</th>
 
<th align="center">Max. 30</th>
 
 
<th align="left">
 
<th align="left">
Full name; format is last name, comma, space after
+
Note: "NOT ON FILE", "FILE NOT AVAILABLE" and "TEMPORARILY UNAVAILABLE"
<br>comma is optional) first name, space, middle initial or
+
<br>messages will be followed by either the driver's name or driver's license number upon which
<br>name, space, suffix (Jr., III, etc.) Followed by a period.
+
<br>the query was based.
<br>Titles or degrees should not be used as part of the
 
<br>name.
 
 
</th>
 
</th>
 
</tr>
 
</tr>
 +
</table>
 +
 +
<b>Driver's License by Name Only General Specifications (DNQ)</b>
 +
 +
To send a Driver's License by Name Only Query (DNQ) enter the following.
 +
 +
<table border="1">
 
<tr>
 
<tr>
<th align="left">DOB/</th>
+
<th align="left">Enter:</th>
<th align="center">4</th>
 
<th align="left">Prefix to identify date of birth.</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">Date of Birth</th>
+
<th align="left">DNQ.</th>
<th align="center">6</th>
 
<th align="left">
 
Date of Birth followed by a period. Express as mmddyy
 
<br>or ccyymmdd. Complete DOB must be present. Some
 
<br>states have different requirements. Check their OLN
 
<br>HELP file for details.
 
</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">SEX/</th>
+
<th align="left">Sending ORI followed by a period</th>
<th align="center">4</th>
 
<th align="left">Prefix to identify sex.</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">Sex</th>
+
<th align="left">Destination ORI followed by a period (only one 2-character state code)</th>
<th align="center">1</th>
 
<th align="left">Sex; conforms to NCIC codes.</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">IMQ/</th>
+
<th align="left">If needed, optional control field</th>
<th align="center">4</th>
 
<th align="left">(For XML use only) Prefix to identify image request field.</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">Image Request</th>
+
<th align="left">TXT</th>
<th align="center">1</th>
+
</tr>
<th align="left">Y to request driver photo; use N if no image is wanted
+
<tr>
<br>or omit IMQ/ field.</th>
+
<th align="left">CR,LF,DEL (Optional)</th>
 
</tr>
 
</tr>
</table>
 
 
The format for a driver's license inquiry or driver's license number is:
 
 
<table border="1">
 
 
<tr>
 
<tr>
<th align="center">Entry</th>
+
<th align="left">Then enter:</th>
<th align="center"># Char.</th>
 
<th align="center">Explanation</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">DQ.</th>
+
<th align="left">"NAM/" followed by, at minimum, the last, first name</th>
<th align="center">3</th>
 
<th align="left">Message type followed by a period.</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">Message Header</th>
+
<th align="left">And any of these optional fields:</th>
<th align="center">13-36</th>
 
<th align="left">Standard input message header may include control field.</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">TXT</th>
+
<th align="left">"AGE/" followed by the age</th>
<th align="center">3</th>
 
<th align="left">Fixed filed prefix to beginning of message.</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">CR,LF,DEL</th>
+
<th align="left">"SEX/" followed by the sex</th>
<th align="center">3</th>
 
<th align="left">Control characters (optional).</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">OLN/</th>
+
<th align="left">"CTY/" followed by city, town or village of subject</th>
<th align="center">4</th>
 
<th align="left">Prefix to identify driver license number.</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">Driver's Lic. #</th>
+
<th align="left">"COU/" followed by the county where the subject lives</th>
<th align="center">1-20</th>
 
<th align="left">Driver license number.</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">IMQ/</th>
+
<th align="left">"NXT/" followed by special codes or numbers to request the next screen or page.</th>
<th align="center">4</th>
 
<th align="left">(For XML use only) Prefix to identify image request field.</th>
 
</tr>
 
<tr>
 
<th align="left">Image Request</th>
 
<th align="center">1</th>
 
<th align="left">Y to request driver photo; use N if no image is wanted
 
<br>or omit IMQ/ field.</th>
 
 
</tr>
 
</tr>
 
</table>
 
</table>
  
====Response Formats====
+
Obtain this information from the state's HELP file.
 +
 
 +
The format for a driver's license inquiry (DNQ) when a complete date of birth is not known is presented below.
  
<ul>
+
Note that the message key is different than a normal driver license query.
<li>Should the information be unavailable, or, after interrogation of the state files, no information is found, a standard response message is returned.
 
<li>If a data field is unavailable, the prefix, data element, and period should be omitted from the response.
 
<li>The message should be compacted to eliminate the resultant spaces.
 
</ul>
 
  
 
<table border="1">
 
<table border="1">
 
<tr>
 
<tr>
<th align="left">
+
<th align="center">Entry</th>
Note: Inquiries on name may result in multiple hits. Only close matches (i.e., exact match on
+
<th align="center"># Char.</th>
<br>last name and DOB) should be returned. When multiple hits do occur, they should be
+
<th align="center">Explanation</th>
<br>returned as separate messages.
 
</th>
 
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">Note: All responses to DNQ inquiries must have a message type of DNR.</th>
+
<th align="left">DNQ.</th>
 +
<th align="center">3</th>
 +
<th align="left">Message type followed by a period.</th>
 
</tr>
 
</tr>
</table>
 
 
<table border="1">
 
 
<tr>
 
<tr>
<th align="left">
+
<th align="left">Message Header</th>
Note: "NOT ON FILE", "FILE NOT AVAILABLE" and "TEMPORARILY UNAVAILABLE"
+
<th align="center">13-24</th>
<br>messages will be followed by either the driver's name or driver's license number upon which
+
<th align="left">Standard input message header, may include control field
<br>the query was based.
+
<br>but only a single 2 character state code.</th>
</th>
 
 
</tr>
 
</tr>
</table>
 
 
<b>Driver's License by Name Only General Specifications (DNQ)</b>
 
 
To send a Driver's License by Name Only Query (DNQ) enter the following.
 
 
<table border="1">
 
 
<tr>
 
<tr>
<th align="left">Enter:</th>
+
<th align="left">TXT</th>
 +
<th align="center">3</th>
 +
<th align="left">Fixed filed prefix to beginning of message.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">DNQ.</th>
+
<th align="left">CR,LF,DEL</th>
 +
<th align="center">3</th>
 +
<th align="left">Control characters (optional).</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">Sending ORI followed by a period</th>
+
<th align="left">NAM/</th>
 +
<th align="center">4</th>
 +
<th align="left">Prefix to identify name.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">Destination ORI followed by a period (only one 2-character state code)</th>
+
<th align="left">Name</th>
 +
<th align="center">Max. 30</th>
 +
<th align="left">
 +
This field must include at least a first and last name in the
 +
<br>standard name format (surname, first name). Some
 +
<br>states allow a question mark "?" in the surname if the full
 +
<br>surname is not known. Consult state help files to
 +
<br>determine if a state can support this capability. (E.g.,
 +
<br>NAM/PUBL?, JOHN Q.).
 +
</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">If needed, optional control field</th>
+
<th align="left">AGE/ (optional)</th>
 +
<th align="center">4</th>
 +
<th align="left">Prefix to identify age.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">TXT</th>
+
<th align="left">Age</th>
 +
<th align="center">2</th>
 +
<th align="left">
 +
Age followed by a period. If a complete date of birth is
 +
<br>known a DQ should be used. Some states may handle
 +
<br>age differently than others. Consult their HELP file for
 +
<br>details. The address is xxOLNHELP where xx=2
 +
<br>character state code.
 +
</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">CR,LF,DEL (Optional)</th>
+
<th align="left">SEX/ (optional)</th>
 +
<th align="center">4</th>
 +
<th align="left">Prefix to identify sex.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">Then enter:</th>
+
<th align="left">Sex</th>
 +
<th align="center">1</th>
 +
<th align="left">Sex; conforms to NCIC codes.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">"NAM/" followed by, at minimum, the last, first name</th>
+
<th align="left">CTY/ (optional)</th>
 +
<th align="center">4</th>
 +
<th align="left">Prefix to identify city, village or town where subject lives.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">And any of these optional fields:</th>
+
<th align="left">City</th>
 +
<th align="center">20</th>
 +
<th align="left">City, village or town where subject lives.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">"AGE/" followed by the age</th>
+
<th align="left">COU/ (optional)</th>
 +
<th align="center">4</th>
 +
<th align="left">Prefix to identify county.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">"SEX/" followed by the sex</th>
+
<th align="left">County</th>
 +
<th align="center">20</th>
 +
<th align="left">County where subject lives.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">"CTY/" followed by city, town or village of subject</th>
+
<th align="left">NXT/ (optional)</th>
 +
<th align="center">4</th>
 +
<th align="left">Prefix to identify the Next field.</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th align="left">"COU/" followed by the county where the subject lives</th>
+
<th align="left">Next page or group</th>
</tr>
+
<th align="center">20</th>
<tr>
+
<th align="left">
<th align="left">"NXT/" followed by special codes or numbers to request the next screen or page.</th>
+
A free form field used to request additional pages.
 +
<br>Individual state HELP files will dictate if this field is used
 +
<br>and what it must contain.
 +
</th>
 
</tr>
 
</tr>
 
</table>
 
</table>
  
Obtain this information from the state's HELP file.
+
<b>Driver's License by Name Only Response Format (DNR)</b>
 +
 
 +
All responses to DNQ inquiries must have a message type of "DNR" but otherwise are identical to DQ responses (DR).
  
The format for a driver's license inquiry (DNQ) when a complete date of birth is not known is presented below.
+
States must use the "DNR" message type for responses to DNQ messages.
  
Note that the message key is different than a normal driver license query.
+
The free form fields "RSTR:" and "STATUS:" are for the states to indicate restrictions on an individual when operating his vehicle (i.e. corrective lenses) and the status of the individual's license (i.e. revoked), respectively.
  
<table border="1">
+
Information should be confined to short, concise, plain English messages.
<tr>
+
 
<th align="center">Entry</th>
+
=====Driver's License Legacy Examples=====
<th align="center"># Char.</th>
+
 
<th align="center">Explanation</th>
+
<u>Example 1</u>: A Driver License query by name, date of birth and sex.
</tr>
+
 
 +
<table border="1">
 
<tr>
 
<tr>
<th align="left">DNQ.</th>
+
<th align="left">
<th align="center">3</th>
+
DQ.AZNLETS20.AZ.TXT
<th align="left">Message type followed by a period.</th>
+
<br>NAM/SMITH,JOHN.DOB/19500101.SEX/M
 +
</th>
 
</tr>
 
</tr>
 +
</table>
 +
 +
<u>Example 2</u>: A Driver License query by OLN.
 +
 +
<table border="1">
 
<tr>
 
<tr>
<th align="left">Message Header</th>
+
<th align="left">
<th align="center">13-24</th>
+
DQ.AZNLETS20.AZ.TXT
<th align="left">Standard input message header, may include control field
+
<br>OLN/111111111
<br>but only a single 2 character state code.</th>
+
</th>
 
</tr>
 
</tr>
 +
</table>
 +
 +
<u>Example 3</u>: A Driver License response.
 +
 +
<table border="1">
 
<tr>
 
<tr>
<th align="left">TXT</th>
 
<th align="center">3</th>
 
<th align="left">Fixed filed prefix to beginning of message.</th>
 
</tr>
 
<tr>
 
<th align="left">CR,LF,DEL</th>
 
<th align="center">3</th>
 
<th align="left">Control characters (optional).</th>
 
</tr>
 
<tr>
 
<th align="left">NAM/</th>
 
<th align="center">4</th>
 
<th align="left">Prefix to identify name.</th>
 
</tr>
 
<tr>
 
<th align="left">Name</th>
 
<th align="center">Max. 30</th>
 
 
<th align="left">
 
<th align="left">
This field must include at least a first and last name in the
+
DR.AZDMV0000
<br>standard name format (surname, first name). Some
+
<br>11:08 10/07/2011 00248
<br>states allow a question mark "?" in the surname if the full
+
<br>11:08 10/07/2011 00052 AZNLETS20
<br>surname is not known. Consult state help files to
+
<br>TXT
<br>determine if a state can support this capability. (E.g.,
+
<br>Query data:
<br>NAM/PUBL?, JOHN Q.).
+
<br>OLN/111111111.IMQ/N.
 +
<br>NAME: SMITH, JOHN
 +
<br>RESIDENCE ADDRESS: 1234 ANYSTREET; PHOENIX,AZ 85000
 +
<br>COUNTRY: United States
 +
<br>DATE OF BIRTH: 1950-01-01
 +
<br>HEIGHT: 507
 +
<br>WEIGHT: 150
 +
<br>GENDER: MALE
 +
<br>RACE: UNKNOWN
 +
<br>*** DRIVER LICENSE DETAILS ***
 +
<br>DRIVER AUTHORIZATION ID: 111111111
 +
<br>JURISDICTION AUTHORITY CODE: AZ
 +
<br>ISSUE DATE: 2009-01-10
 +
<br>EXPIRATION DATE: 2045-01-10
 +
<br>DRIVER ENDORSEMENT: MOTORCYCLE
 +
<br>DRIVING ENDORSMENT CODE: M
 +
<br>DRIVER LICENSE NON-COMMERCIAL CLASS: LICENSE
 +
<br>DRIVER LICENSE NON-COMMERCIAL CLASS CODE: C
 +
<br>LICENSED COMMERCIAL DRIVER: NO
 +
<br>LICENSED NON-COMMERCIAL DRIVER: YES
 +
<br>DRIVER LICENSE NON-COMMERCIAL STATUS: VALID OPERATORS LICENSE
 +
<br>DRIVER ORGAN DONOR: true
 
</th>
 
</th>
 
</tr>
 
</tr>
 +
</table>
 +
 +
<u>Example 4</u>: A Driver License query by Region. The response will be a standard Driver License response (DR).
 +
 +
<table border="1">
 
<tr>
 
<tr>
<th align="left">AGE/ (optional)</th>
 
<th align="center">4</th>
 
<th align="left">Prefix to identify age.</th>
 
</tr>
 
<tr>
 
<th align="left">Age</th>
 
<th align="center">2</th>
 
 
<th align="left">
 
<th align="left">
Age followed by a period. If a complete date of birth is
+
DQG.AZNLETS20.A1.TXT
<br>known a DQ should be used. Some states may handle
+
<br>NAM/SMITH,JOHN.DOB/19500101.SEX/M
<br>age differently than others. Consult their HELP file for
 
<br>details. The address is xxOLNHELP where xx=2
 
<br>character state code.
 
 
</th>
 
</th>
 
</tr>
 
</tr>
 +
</table>
 +
 +
<u>Example 5</u>: A Driver License query by name.
 +
 +
<table border="1">
 
<tr>
 
<tr>
<th align="left">SEX/ (optional)</th>
+
<th align="left">
<th align="center">4</th>
+
DNQ.AZNLETS20.AZ.TXT
<th align="left">Prefix to identify sex.</th>
+
<br>NAM/SMITH,JOHN
 +
</th>
 
</tr>
 
</tr>
 +
</table>
 +
 +
<u>Example 6</u>: A Driver License response by name.
 +
 +
<table border="1">
 
<tr>
 
<tr>
<th align="left">Sex</th>
+
<th align="left">
<th align="center">1</th>
+
DNR.AZDMV0000
<th align="left">Sex; conforms to NCIC codes.</th>
+
<br>08:10 10/11/2011 79931
</tr>
+
<br>08:10 10/11/2011 00711 AZNLETS20
<tr>
+
<br>TXT
<th align="left">CTY/ (optional)</th>
+
<br>JOHN SMITH
<th align="center">4</th>
+
<br>RESIDENCE ADDRESS: 1234 ANY STREET; PHOENIX,AZ 85000
<th align="left">Prefix to identify city, village or town where subject lives.</th>
+
<br>COUNTRY: UNITED STATES
</tr>
+
<br>COUNTY: MARICOPA
<tr>
+
<br>LOCATION COUNTY: MARICOPA
<th align="left">City</th>
+
<br>RACE: Black
<th align="center">20</th>
+
<br>GENDER: Male
<th align="left">City, village or town where subject lives.</th>
+
<br>DATE OF BIRTH: 1950-01-01
</tr>
+
<br>DRIVER AUTHORIZATION ID: 12345
<tr>
+
<br>
<th align="left">COU/ (optional)</th>
+
<br>JOHN SMITH
<th align="center">4</th>
+
<br>RESIDENCE ADDRESS: 2345 THAT PLACE; GLENDALE,AZ 85000
<th align="left">Prefix to identify county.</th>
+
<br>COUNTRY: UNITED STATES
</tr>
+
<br>COUNTY: MARICOPA
<tr>
+
<br>LOCATION COUNTY: MARICOPA
<th align="left">County</th>
+
<br>RACE: White
<th align="center">20</th>
+
<br>GENDER: Male
<th align="left">County where subject lives.</th>
+
<br>DATE OF BIRTH: 1951-01-01
</tr>
+
<br>DRIVER AUTHORIZATION ID: 23456
<tr>
+
<br>
<th align="left">NXT/ (optional)</th>
+
<br>JOHN SMITH
<th align="center">4</th>
+
<br>RESIDENCE ADDRESS: 3456 SOME DRIVE; PEORIA,AZ 85000
<th align="left">Prefix to identify the Next field.</th>
+
<br>COUNTRY: UNITED STATES
</tr>
+
<br>COUNTY: MARICOPA
<tr>
+
<br>LOCATION COUNTY: MARICOPA
<th align="left">Next page or group</th>
+
<br>RACE: Black
<th align="center">20</th>
+
<br>GENDER: Male
<th align="left">
+
<br>DATE OF BIRTH: 1952-01-01
A free form field used to request additional pages.
+
<br>DRIVER AUTHORIZATION ID: 34567
<br>Individual state HELP files will dictate if this field is used
+
<br>
<br>and what it must contain.
+
<br>JOHN SMITH
 +
<br>RESIDENCE ADDRESS: 4567 THIS AVENUE; PHOENIX,AZ 85000
 +
<br>COUNTRY: UNITED STATES
 +
<br>COUNTY: MARICOPA
 +
<br>LOCATION COUNTY: MARICOPA
 +
<br>GENDER: Unknown
 +
<br>DATE OF BIRTH: 1901-01-01
 +
<br>DRIVER AUTHORIZATION ID: 45678
 
</th>
 
</th>
 
</tr>
 
</tr>
 
</table>
 
</table>
  
<b>Driver's License by Name Only Response Format (DNR)</b>
+
[[#top|Top]]
  
All responses to DNQ inquiries must have a message type of "DNR" but otherwise are identical to DQ responses (DR).
+
== Downloads ==
  
States must use the "DNR" message type for responses to DNQ messages.
+
[https://schema.nlets.org/Wiki/Schemas/DQ.ZIP Download DQ Schema]
  
The free form fields "RSTR:" and "STATUS:" are for the states to indicate restrictions on an individual when operating his vehicle (i.e. corrective lenses) and the status of the individual's license (i.e. revoked), respectively.
+
[https://schema.nlets.org/Wiki/Schemas/DR.ZIP Download DR Schema] (updated 6/28/2019)
  
Information should be confined to short, concise, plain English messages.
+
[https://schema.nlets.org/Wiki/Stylesheets/DR.xslt Download DR Stylesheet] (updated 05/05/2021)
  
=====Driver's License Legacy Examples=====
+
[https://schema.nlets.org/Wiki/Schemas/DQG.ZIP Download DQG Schema]
  
<u>Example 1</u>: A Driver License query by name, date of birth and sex.
+
[https://schema.nlets.org/Wiki/Schemas/DNQ.ZIP Download DNQ Schema]
  
<table border="1">
+
[https://schema.nlets.org/Wiki/Schemas/DNR.ZIP Download DNR Schema] (updated 7/1/2019)
<tr>
 
<th align="left">
 
DQ.AZNLETS20.AZ.TXT
 
<br>NAM/SMITH,JOHN.DOB/19500101.SEX/M
 
</th>
 
</tr>
 
</table>
 
 
 
<u>Example 2</u>: A Driver License query by OLN.
 
 
 
<table border="1">
 
<tr>
 
<th align="left">
 
DQ.AZNLETS20.AZ.TXT
 
<br>OLN/111111111
 
</th>
 
</tr>
 
</table>
 
 
 
<u>Example 3</u>: A Driver License response.
 
 
 
<table border="1">
 
<tr>
 
<th align="left">
 
DR.AZDMV0000
 
<br>11:08 10/07/2011 00248
 
<br>11:08 10/07/2011 00052 AZNLETS20
 
<br>TXT
 
<br>Query data:
 
<br>OLN/111111111.IMQ/N.
 
<br>NAME: SMITH, JOHN
 
<br>RESIDENCE ADDRESS: 1234 ANYSTREET; PHOENIX,AZ 85000
 
<br>COUNTRY: United States
 
<br>DATE OF BIRTH: 1950-01-01
 
<br>HEIGHT: 507
 
<br>WEIGHT: 150
 
<br>GENDER: MALE
 
<br>RACE: UNKNOWN
 
<br>*** DRIVER LICENSE DETAILS ***
 
<br>DRIVER AUTHORIZATION ID: 111111111
 
<br>JURISDICTION AUTHORITY CODE: AZ
 
<br>ISSUE DATE: 2009-01-10
 
<br>EXPIRATION DATE: 2045-01-10
 
<br>DRIVER ENDORSEMENT: MOTORCYCLE
 
<br>DRIVING ENDORSMENT CODE: M
 
<br>DRIVER LICENSE NON-COMMERCIAL CLASS: LICENSE
 
<br>DRIVER LICENSE NON-COMMERCIAL CLASS CODE: C
 
<br>LICENSED COMMERCIAL DRIVER: NO
 
<br>LICENSED NON-COMMERCIAL DRIVER: YES
 
<br>DRIVER LICENSE NON-COMMERCIAL STATUS: VALID OPERATORS LICENSE
 
<br>DRIVER ORGAN DONOR: true
 
</th>
 
</tr>
 
</table>
 
 
 
<u>Example 4</u>: A Driver License query by Region. The response will be a standard Driver License response (DR).
 
 
 
<table border="1">
 
<tr>
 
<th align="left">
 
DQG.AZNLETS20.A1.TXT
 
<br>NAM/SMITH,JOHN.DOB/19500101.SEX/M
 
</th>
 
</tr>
 
</table>
 
 
 
<u>Example 5</u>: A Driver License query by name.
 
 
 
<table border="1">
 
<tr>
 
<th align="left">
 
DNQ.AZNLETS20.AZ.TXT
 
<br>NAM/SMITH,JOHN
 
</th>
 
</tr>
 
</table>
 
 
 
<u>Example 6</u>: A Driver License response by name.
 
 
 
<table border="1">
 
<tr>
 
<th align="left">
 
DNR.AZDMV0000
 
<br>08:10 10/11/2011 79931
 
<br>08:10 10/11/2011 00711 AZNLETS20
 
<br>TXT
 
<br>JOHN SMITH
 
<br>RESIDENCE ADDRESS: 1234 ANY STREET; PHOENIX,AZ 85000
 
<br>COUNTRY: UNITED STATES
 
<br>COUNTY: MARICOPA
 
<br>LOCATION COUNTY: MARICOPA
 
<br>RACE: Black
 
<br>GENDER: Male
 
<br>DATE OF BIRTH: 1950-01-01
 
<br>DRIVER AUTHORIZATION ID: 12345
 
<br>
 
<br>JOHN SMITH
 
<br>RESIDENCE ADDRESS: 2345 THAT PLACE; GLENDALE,AZ 85000
 
<br>COUNTRY: UNITED STATES
 
<br>COUNTY: MARICOPA
 
<br>LOCATION COUNTY: MARICOPA
 
<br>RACE: White
 
<br>GENDER: Male
 
<br>DATE OF BIRTH: 1951-01-01
 
<br>DRIVER AUTHORIZATION ID: 23456
 
<br>
 
<br>JOHN SMITH
 
<br>RESIDENCE ADDRESS: 3456 SOME DRIVE; PEORIA,AZ 85000
 
<br>COUNTRY: UNITED STATES
 
<br>COUNTY: MARICOPA
 
<br>LOCATION COUNTY: MARICOPA
 
<br>RACE: Black
 
<br>GENDER: Male
 
<br>DATE OF BIRTH: 1952-01-01
 
<br>DRIVER AUTHORIZATION ID: 34567
 
<br>
 
<br>JOHN SMITH
 
<br>RESIDENCE ADDRESS: 4567 THIS AVENUE; PHOENIX,AZ 85000
 
<br>COUNTRY: UNITED STATES
 
<br>COUNTY: MARICOPA
 
<br>LOCATION COUNTY: MARICOPA
 
<br>GENDER: Unknown
 
<br>DATE OF BIRTH: 1901-01-01
 
<br>DRIVER AUTHORIZATION ID: 45678
 
</th>
 
</tr>
 
</table>
 
  
[[#top|Top]]
+
[https://schema.nlets.org/Wiki/Stylesheets/DNR.xslt Download DNR Stylesheet] (updated 11/13/2020)
 
 
== Downloads ==
 
 
 
[https://schema.nlets.org/Wiki/Schemas/DQ.ZIP Download DQ Schema]
 
 
 
[https://schema.nlets.org/Wiki/Schemas/DR.ZIP Download DR Schema] (updated 6/28/2019)
 
 
 
[https://schema.nlets.org/Wiki/Stylesheets/DR.xslt Download DR Stylesheet] (updated 8/13/2019)
 
 
 
[https://schema.nlets.org/Wiki/Schemas/DQG.ZIP Download DQG Schema]
 
 
 
[https://schema.nlets.org/Wiki/Schemas/DNQ.ZIP Download DNQ Schema]
 
 
 
[https://schema.nlets.org/Wiki/Schemas/DNR.ZIP Download DNR Schema] (updated 7/1/2019)
 
  
[https://schema.nlets.org/Wiki/Stylesheets/DNR.xslt Download DNR Stylesheet] (updated 7/1/2019)
+
[https://schema.nlets.org/Wiki/Stylesheets/PDR.xslt Download PDR Stylesheet] (Added 06/02/2020)
  
 
[[Media:CANDLE Specifications.pdf | CANDLE Specifications]]
 
[[Media:CANDLE Specifications.pdf | CANDLE Specifications]]
  
 
[[#top|Top]]
 
[[#top|Top]]

Revision as of 15:17, 5 May 2021

Driver's License Transactions (DQ/DR, DQG & DNQ/DNR)

This section describes how to access out-of-state driver's license information (driver's name, address, date of birth, description, social security #, license type, restrictions, license status, and license number) by sending a query through Nlets to a state or multi-state region by License Number or Name/Date of Birth/Sex or by Name Only.

Canadian driver's license queries are described in Section 32: "Communicating with Canada".

Mexican commercial driver license queries are described in Section 33: "Communicating with Mexico".

U.S. commercial driver license queries are described in section 26: "Commercial Vehicle Information".

Driver's License Query / Driver's License Response

This section provides an overview and details regarding the Driver's License Query by license number or by name/date of birth/sex to a state (DQ), and the corresponding Driver's License Response (DR), Driver's License Query by Name to a state (DNQ), and the corresponding Driver's License Response by Name (DNR), and the Driver's License Query by Name/Date of Birth/Sex to a region (DQG).

Multi-State Query Functionality

Nlets supports the Multi-State Query functionality for the DQ message format. This functionality allows the query to be automatically sent to all states that participate in the message type and returns a single merged response.

In order to send a Driver License transaction using the Multi-State Query, the query should be sent in its typical format to the destination NL. Nlets will take this query and send it to ALL states that support the DQ message key. Nlets then collects all relevant responses to this query, merges them together while suppressing the NO HIT responses, and sends them onto the querying user as a single response. These responses will also contain summary data indicating which states this query was sent to, which states responded with hits, which responded with no hits, and which states did not respond at all.

States receiving legacy text or GJXDM formats will see the summary data and state responses in a flattened text format (wrapped in XML for GJXDM), whereas states receiving responses in NIEM will receive the summary and state responses in a standardized XML structure detailed below.

An important detail to note is that if a response is received after Nlets has forwarded on the merged Multi-State response, the late response will be sent individually to the original user. This would be most likely to occur if a participating state happened to be 'down' at the time of the query but came back up at a later time and responded.

Overview

To send a Driver's License Query (DQ), 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 (DQ only).

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). States issuing licenses with special characters are encouraged to note this in their OLN Helpfile.

Positive Driver's License Responses (DR) may contain the driver's name, address, date of birth, description, social security #, license type, restrictions, status, and license number (see "Driver's License Response" below). A Driver's License Response (DR) may include an image if one was requested and is available.

Section13-DQ.jpg

Other possible responses to a query are:

  • NOT ON FILE
  • FILE NOT AVAILABLE
  • TEMPORARILY UNAVAILABLE

Query Requirements

  • Each Driver's License Query (DQ/ DQG) can be sent to no more than five addresses.
  • A destination code of "Z1" will result in the Query being directed to all states (sends a separate response for each state).
  • A destination code of "NL" will result in the Query being directed to all states (sends a single response for all states).
  • Only queries on name, date of birth and sex may be used for DQGs.
  • The Driver's License Query (DQ) format includes an optional image field (IMQ/). When this field is included in the inquiry with "Y" (Legacy) or "true" (XML) as a value, the receiver should return an image if one is available.
  • If a state wishes to request driver's license information it should, without exception, utilize the Nlets inquiry formats. Administrative Messages should not be used in place of the Nlets operator license inquiry formats.
  • Any indicators or flags from the DMV file that depict an individual as wanted must be suppressed from interstate transmission over Nlets.
  • Users may search state driver license files when an exact date of birth is not known. This feature requires a different message type (DNQ) and may only be addressed to a single 2-character state code. Several data elements are provided to limit the search.

Query Notes

If there is additional information required that was not included in the reply, an Administrative Message may be sent. These Administrative Messages should be sent to the applicable standardized ORI:
                 Operators License Data - xxOLN0000
                 xx = 2 position state destination code.

If driver history information is needed, a Driver History Query (KQ) message type should be used. An Administrative Message should not be used to request driver history data.

Driver's License queries on name and DOB may result in multiple hits. Only close matches (i.e., exact match on the last name and DOB) should be returned. When multiple hits do occur, they should be returned to the inquirer as separate messages.

Information in free form fields should be confined to short, concise, plain English messages.

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's license queries and who is a photo sharing participant by sending an Administrative Message to "NLOLNHELP".

More information on help files can be located in [[[Section 05: Help File Transactions|File Transactions]]].

Technical Notes

This section provides guidance for data codes and query and response field requirements.

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.

Query Requirements
XML Tag: Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
<nc:DriverLicenseIdentification>
  <nc:IdentificationID>
</nc:DriverLicenseIdentification>
OLN/ 1-20 Alphanumeric Driver's License
Number
<nc:PersonName>
  <nc:PersonFullName>
  <nc:PersonGivenName>
  <nc:PersonMiddleName>
  <nc:PersonSurName>
</nc:PersonName>
NAM/ 1-30 Alpha
Characters
Name
<nc:PersonSexCode>
SEX/ 1 M, F or U Sex
<nc:PersonBirthDate>
  <nc:Date>
</nc:PersonBirthDate>
DOB/ 8 or 10 ccyy-mm-dd
(XML)
Date of Birth
<n2:ImageIndicator>
IMQ/ 1 See NCIC
Manual
Image Request
(Optional DQ only)
Response Requirements

Positive responses (license information) must be in the format presented below.

  • Should the information be unavailable, a standard message is returned by the state.
  • If the query was processed and there was no information on file, a standard "no record" message is returned. The format for each of these follows the positive response format.
  • If a data field presented in the Native format is unavailable, the prefix, data element, and period should be omitted from the response.
  • The message should be compacted to eliminate spaces resulting from missing or unavailable data elements. An example of this would be Driver License Endorsements. Some drivers do not have this information on their record.

Driver's Name-Only Query / Response (DNQ/DNR)

This section provides an overview and details regarding the DNQ/DNR (query by name only to a state and its response).

Overview

DNQs allow users to search state driver's license files when an exact date of birth is not known. To send a Driver's Name-Only Query (DNQ), a user must enter the name (last and first) and may include any of these optional fields: age, sex, city, town or village, county, special codes or numbers (see "Query by Name" below).

Positive Driver's License Responses (DNR) may contain the address, sex, date of birth, physical description, social security number, driver's license number, type of license, restrictions and/or status (see "Driver's License Response" below).

Section13-DNQ.jpg

The other possible driver license responses are:

  • FILE NOT AVAILABLE
  • NOT ON FILE
  • TEMPORARILY UNAVAILABLE.

Query Requirements

Use the Driver Name-Only Response (DNR) message type for response to a Driver Name-Only Query (DNQ).

XML Tag: Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
<nc:PersonName>
  <nc:PersonFullName>
  <nc:PersonGivenName>
  <nc:PersonMiddleName>
  <nc:PersonSurName>
</nc:PersonName>
NAM/ 1-30 Alpha
Characters

Person Name.
This field must
include at least a
first and last name
in the standard
name format
(surname, first
name). Some
states allow a
question mark "?"
in the surname if
the full surname is
not known. Consult
state help files to
determine if a
state can support
this capability.

<nc:PersonAgeMeasure>
AGE/ 2 Numeric

Age (Optional)
If a complete date
of birth is unknown
some states
support inquiries
on age. Consult
state vehicle
registration HELP
file for details. The
address is
xxOLNHELP where
xx=2 character state
code.

<nc:PersonSexCode>
SEX/ 1 See NCIC
Manual

Sex (Optional)

<nc:LocationCityName>
CTY/ 4 Alpha
Characters

City, town
or village name
(optional)

<nc:LocationCountyName>
COU/ 4 Alpha
Characters

County name
(optional)

<n2:RequestAdditionalRecordsText>
NXT/ 4 Free form

A free form
field used to request
additional pages.
Individual state
HELP files will
dictate if this field is
used and what it must
contain. (Perhaps
special codes or
numbers - optional)

Parsed Driver License Response

Nlets now provides the option for users to receive fully tagged NIEM formatted Driver's License Responses from all states via our message parsing service. DRs destined to an individual terminal or an entire state can be redirected to the Message Parsing Service to be converted to a Parsed Driver's License Response (PDR).

The Parsed Driver's License Response is structured similarly to a standard Driver's License Response with the addition of some parsing related elements and the removal of some cardinalities and enumerations.

See the Parsed Driver's License NIEM Specifications section below for additional details on formatting.

The parsing service can be setup to parse all statewide DRs or to parse DRs for any number of individual ORIs.

Any standardized message that is received will also be transformed into a text response in the OriginalResponseText element of a PDR.

To leverage this service or for more information, contact the Nlets Control Center at 1-800-528-4020.


Top

GJXDM (DEPRECATED)

GJXDM has been deprecated. Please contact Nlets for additional assistance with GJXDM.

Top

NIEM

Driver's License NIEM Specifications

This section provides NIEM format and examples for Driver's License Query to a state (DQ), the Driver's License Query by to a region (DQG), the Driver's License Query by Name Only (DNQ) and Driver's License Response (DR and DNR).

Not all states reply to Driver's License Query by Name Only. Consult the NLNOQHELP file for a list of participating states.

Canadian driver license queries are described in "Communicating with Mexico".

Mexican driver license queries are described in "Communicating with Mexico".

All Nlets NIEM messages must be based on the Nlets NIEM Message Structure and include the standard Nlets XML Header as detailed in Message Structure. The NIEM header and hierarchy of the elements in this section have been omitted to avoid redundancy. The associated schemas and instances should be consulted to determine the correct XPaths of the elements.

Element Dictionary

Transaction types detailed below include: Query by Name, DOB and Sex (DQ,DQG), Query by Driver's License Number (DQ), Query by Name (DNQ), Response in Free Text (DR), Standardized Status Response (DR) and Standardized List Response (DNR).

Query Formats

Query by Name, DOB and Sex (DQ,DQG)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:Person
  This element encapsulates the information about the person being queried.

    nc:PersonBirthDate
    A date a person was born.

      nc:Date
      A full date.
      This element contains the DOB for the person being queried on. This data in this element must
      be in xsd:date format, that is: yyyy-mm-dd.

    nc:PersonName
    A combination of names and/or titles by which a person is known.

      nc:PersonGivenName
      A first name of a person.
      This optional element containing a person's first name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonMiddleName
      A middle name of a person.
      This optional element containing a person's middle name may be sent via XML if available but
      will only be forwarded onto states receiving XML.

      nc:PersonSurName
      A last name or family name of a person.
      This optional element containing a person's last name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonFullName
      A complete name of a person.
      This required element must contain the full name of the person in the format LAST,FIRST
      MIDDLE. The data from this element is the only name data that will be passed onto states
      receiving text.

    nc:PersonSexCode
    A gender or sex of a person.
    Value must be M, F or U.

  n2:ImageIndicator
  Y if an image is being requested if available.
  A value of "true" in this element indicates that an image is being requested if available.

Query by Driver's License Number (OLN) (DQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:Person
  This element encapsulates the information about the person being queried.

    nc:DriverLicense
    Details about a license issued to a person granting driving privileges.

      nc:DriverLicenseIdentification
      Details about a driver license identifier or driver license permit identifier, including the number and
      state.

        nc:IdentificationID
        A value that identifies something.
        This element should contain the person's driver license number.

  n2:ImageIndicator
  Y if an image is being requested if available.

Query by Name (DNQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:Person
  This element encapsulates the information about the person being queried.
  This element encapsulates the information about the person being queried.

    n2:PersonResidentialAddress
    This optional element contains the street address. Actual value should go in the subelement
    nc:StreetFullText
    This optional element contains subelements describing an address when present. When
    subelements are present, all must be present (excluding the always optional element Building
    Name)

      nc:LocationCityName
      A name of a city or town.
      This optional element contains the city.

      nc:LocationCountyName
      A name of a county, parish, vicinage, or other such geopolitical subdivision of a state

    nc:PersonAgeMeasure
    A measurement of the age of a person.

      nc:MeasurePointValue
      A specific measurement value.
      This optional element contains the age of a person. Value should be numeric.

    nc:PersonName
    A combination of names and/or titles by which a person is known.

      nc:PersonGivenName
      A first name of a person.
      This optional element containing a person's first name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonMiddleName
      A middle name of a person.
      This optional element containing a person's middle name may be sent via XML if available but
      will only be forwarded onto states receiving XML.

      nc:PersonSurName
      A last name or family name of a person.
      This optional element containing a person's last name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonFullName
      A complete name of a person.
      This required element must contain the full name of the person in the format LAST,FIRST
      MIDDLE. The data from this element is the only name data that will be passed onto states
      receiving text.

    nc:PersonSexCode
    A gender or sex of a person.
    This optional element contains the person's sex. Value must be M, F or U.

  n2:ImageIndicator
  True if an image is being requested if available.

Response Formats

Driver's License Response in Free Text (DR)

Response Data (n2:NLETSResponseData)
This element will contain all elements specific to this transaction.

  Response Text (n2:ResponseText)
  This element will contain the free text driver's license response. Nlets recommends the use of


  

<!&#91;CDATA&#91;&#93;&#93;>

tags to ensure that the response does not contain any characters illegal in XML.

  Digital Image (j2:PersonDigitalImage)
  GJXDM: A photograph or image of a person in a digital format.
  This optional element may contain a person's driver license photo and related metadata. This
  element should only be returned when the original query contained an image request.

    Base64 Encoded Image (j2:BinaryObject.Base64)
    GJXDM: A binary encoding of data, e.g., a binary encoding of a picture, photo, image, graphic,
    sound or video.
    This element contains the Base64 encoded image.

    Binary Format (j2:BinaryFormatText)
    GJXDM: A format of a binary object, e.g., image/jpeg
    This element contains the format and value should be image/jpeg.

    Binary Type (j2:BinaryTypeText)
    GJXDM: A type of binary object that is encoded, e.g., mug shot, driver license picture, audio
    confession.
    This element contains the type.

    Capture Date (j2:BinaryCaptureDate)
    GJXDM: A date on which the data represented by the binary object is captured, e.g., an image
    taken or an audio recorded.
    This element contains the date a photo was taken.

    Capture Time (j2:BinaryCaptureTime)
    GJXDM: A time at which the data represented by the binary object is captured, e.g., an image
    taken or an audio recorded.
    This element contains the time a photo was taken.

    Available Indicator (j2:BinaryAvailableIndicator)
    GJXDM: True if a binary is available; false if it is not.
    This element should be present with a value of true if a photo is being returned.

Standardized Driver's License Status Response (DR)

Response Data (n2:NLETSResponseData)
This element will contain all elements specific to this transaction.

  Driver Status (n2:DriverStatus)
  This element will contain the standardized driver status response as defined in the
  Collaboration of AAMVA and Nlets for Driver License Exchange (CANDLE) specifications.

Standardized Driver's License Match List Response (DR)

Response Data (n2:NLETSResponseData)
This element will contain all elements specific to this transaction.

  Driver Matches (n2:DriverMatches)
  This element will contain the standardized driver match list response as defined in the
  Collaboration of AAMVA and Nlets for Driver License Exchange (CANDLE) specifications.

Driver's License NIEM Examples

Example 1: A Driver License query by name, date of birth and sex.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>DQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZ</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="DQ">
    <n2:Person>
      <nc:PersonBirthDate>
        <nc:Date>1950-01-01</nc:Date>
      </nc:PersonBirthDate>
      <nc:PersonName>
        <nc:PersonFullName>SMITH,JOHN</nc:PersonFullName>
      </nc:PersonName>
      <nc:PersonSexCode>M</nc:PersonSexCode>
    </n2:Person>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 2: A Driver License query by OLN.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>DQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZ</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="DQ">
    <n2:Person>
      <nc:DriverLicense>
        <nc:DriverLicenseIdentification>
          <nc:IdentificationID>111111111</nc:IdentificationID>
        </nc:DriverLicenseIdentification>
      </nc:DriverLicense>
    </n2:Person>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 3: A Driver License response in free text form.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>PDR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZDMV0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>08:28</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>08:28</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00299</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="DR">
    <nc:QualityCommentText>TEXT RESPONSE COULD NOT BE PARSED, SEE ORIGINALTEXT FOR FULL CONTENT</nc:QualityCommentText>
    <n2:OriginalTextResponse>NAME: SMITH, JOHN
         RESIDENCE ADDRESS: 1234 ANYSTREET; PHOENIX,AZ 85000
         COUNTRY: United States
         DATE OF BIRTH: 1950-01-01
         HEIGHT: 507
         WEIGHT: 150
         GENDER: MALE
         RACE: UNKNOWN
         *** DRIVER LICENSE DETAILS ***
         DRIVER AUTHORIZATION ID: 111111111
         JURISDICTION AUTHORITY CODE: AZ
         ISSUE DATE: 2009-01-10
         EXPIRATION DATE: 2045-01-10
         DRIVER ENDORSEMENT: MOTORCYCLE
         DRIVING ENDORSMENT CODE: M
         DRIVER LICENSE NON-COMMERCIAL CLASS: LICENSE
         DRIVER LICENSE NON-COMMERCIAL CLASS CODE: C
         LICENSED COMMERCIAL DRIVER: NO
         LICENSED NON-COMMERCIAL DRIVER: YES
         DRIVER LICENSE NON-COMMERCIAL STATUS: VALID OPERATORS LICENSE
         DRIVER ORGAN DONOR: true
    </n2:OriginalTextResponse>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 4: A Driver License response in standardized form.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>DR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS47</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS49</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>08:30</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>08:30</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00310</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="DQ">
    <n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
      <nc:PersonBirthDate />
      <n2c:DriverLicense>
        <nc:DriverLicenseIdentification>
          <nc:IdentificationID>111111111</nc:IdentificationID>
        </nc:DriverLicenseIdentification>
      </n2c:DriverLicense>
    </n2c:Driver>
    <n2:ImageIndicator>false</n2:ImageIndicator>
    <n2:PurposeCode></n2:PurposeCode>
  </n2:NLETSInquiryData>
  <n2:NLETSResponseData n2:key="DR">
    <nds2:DriverStatus xmlns:nds2="http://www.nlets.org/niem/nlets-driver-status/1.0/">
      <nds2:StandardResponse>
        <n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
          <nc:PersonBirthDate>
            <nc:Date>1950-01-01</nc:Date>
          </nc:PersonBirthDate>
          <nc:PersonHeightMeasure>
            <nc:MeasurePointValue>507</nc:MeasurePointValue>
          </nc:PersonHeightMeasure>
          <nc:PersonName>
            <nc:PersonGivenName>JOHN</nc:PersonGivenName>
            <nc:PersonSurName>SMITH</nc:PersonSurName>
          </nc:PersonName>
          <nc:PersonOrganDonatorIndicator>true</nc:PersonOrganDonatorIndicator>
          <nc:PersonOtherIdentification />
          <nc:PersonRaceText>UNKNOWN</nc:PersonRaceText>
          <nc:PersonSexText>MALE</nc:PersonSexText>
          <nc:PersonSSNIdentification />
          <nc:PersonWeightMeasure>
            <nc:MeasurePointValue>150</nc:MeasurePointValue>
          </nc:PersonWeightMeasure>
          <n2c:DriverLicense>
            <nc:DriverLicenseIdentification>
              <nc:IdentificationID>111111111</nc:IdentificationID>
              <j:IdentificationJurisdictionNCICLSTACode xmlns:j="http://niem.gov/niem/domains/jxdm/4.1">
                AZ</j:IdentificationJurisdictionNCICLSTACode>
            </nc:DriverLicenseIdentification>
            <j:DriverLicenseEndorsement xmlns:j="http://niem.gov/niem/domains/jxdm/4.1">
              <j:DriverLicenseHMEThreatDate />
            </j:DriverLicenseEndorsement>
            <nc:DriverLicenseEndorsementCode>M</nc:DriverLicenseEndorsementCode>
            <nc:DriverLicenseEndorsementText>MOTORCYCLE</nc:DriverLicenseEndorsementText>
            <nc:DriverLicenseExpirationDate>
              <nc:Date>2045-01-10</nc:Date>
            </nc:DriverLicenseExpirationDate>
            <nc:DriverLicenseIssueDate>
              <nc:Date>2009-01-10</nc:Date>
            </nc:DriverLicenseIssueDate>
            <nc:DriverLicenseNonCommercialClassText>LICENSE
               </nc:DriverLicenseNonCommercialClassText>
            <nc:DriverLicenseNonCommercialStatusText>VALID OPERATORS LICENSE
               </nc:DriverLicenseNonCommercialStatusText>
            <nc:DriverLicensePermitQuantity>NaN</nc:DriverLicensePermitQuantity>
            <n2c:DriverLicenseCommercialLicensedIndicator>false
               </n2c:DriverLicenseCommercialLicensedIndicator>
            <n2c:DriverLicenseNonCommercialLicensedIndicator>true
               </n2c:DriverLicenseNonCommercialLicensedIndicator>
            <n2c:DriverLicenseNonCommercialLocalClassText>C
               </n2c:DriverLicenseNonCommercialLocalClassText>
          </n2c:DriverLicense>
          <n2c:PersonContactInformation>
            <nc:ContactMailingAddress />
          </n2c:PersonContactInformation>
          <n2c:PersonResidentialAddress>
            <nc:LocationStreet>
              <nc:StreetFullText>1234 ANYSTREET</nc:StreetFullText>
            </nc:LocationStreet>
            <nc:LocationCityName>PHOENIX</nc:LocationCityName>
            <nc:LocationCountyName></nc:LocationCountyName>
            <nc:LocationStateName>AZ</nc:LocationStateName>
            <nc:LocationCountryName>United States</nc:LocationCountryName>
            <nc:LocationPostalCode>85000</nc:LocationPostalCode>
            <n2c:ResidenceDateRange>
              <nc:EndDate />
            </n2c:ResidenceDateRange>
          </n2c:PersonResidentialAddress>
        </n2c:Driver>
      </nds2:StandardResponse>
    </nds2:DriverStatus>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 5: A Driver License query by Region. The response will be a standard Driver License response (DR).

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>DQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZ</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="DQ">
    <n2:Person>
      <nc:PersonBirthDate>
        <nc:Date>1950-01-01</nc:Date>
      </nc:PersonBirthDate>
      <nc:PersonName>
        <nc:PersonGivenName>JOHN</nc:PersonGivenName>
        <nc:PersonSurName>SMITH</nc:PersonSurName>
        <nc:PersonFullName>SMITH,JOHN</nc:PersonFullName>
      </nc:PersonName>
      <nc:PersonSexCode>M</nc:PersonSexCode>
    </n2:Person>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 6: A Driver License query by name.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>DNQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZ</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="DNQ">
    <n2:Person>
      <nc:PersonName>
        <nc:PersonFullName>SMITH,JOHN</nc:PersonFullName>
      </nc:PersonName>
    </n2:Person>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 7: A Driver License response by name in free text form.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>DNR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZDMV0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS49</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>08:34</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>08:34</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00313</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="DNQ">
    <n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0" />
  </n2:NLETSInquiryData>
  <n2:NLETSResponseData n2:key="DNR">
    <n2:ResponseText>JOHN SMITH
         RESIDENCE ADDRESS: 1234 ANY STREET; PHOENIX,AZ 85000
         COUNTRY: UNITED STATES
         COUNTY: MARICOPA
         LOCATION COUNTY: MARICOPA
         RACE: Black
         GENDER: Male
         DATE OF BIRTH: 1950-01-01
         DRIVER AUTHORIZATION ID: 12345
         
         JOHN SMITH
         RESIDENCE ADDRESS: 2345 THAT PLACE; GLENDALE,AZ 85000
         COUNTRY: UNITED STATES
         COUNTY: MARICOPA
         LOCATION COUNTY: MARICOPA
         RACE: White
         GENDER: Male
         DATE OF BIRTH: 1951-01-01
         DRIVER AUTHORIZATION ID: 23456
         
         JOHN SMITH
         RESIDENCE ADDRESS: 3456 SOME DRIVE; PEORIA,AZ 85000
         COUNTRY: UNITED STATES
         COUNTY: MARICOPA
         LOCATION COUNTY: MARICOPA
         RACE: Black
         GENDER: Male
         DATE OF BIRTH: 1952-01-01
         DRIVER AUTHORIZATION ID: 34567
         
         JOHN SMITH
         RESIDENCE ADDRESS: 4567 THIS AVENUE; PHOENIX,AZ 85000
         COUNTRY: UNITED STATES
         COUNTY: MARICOPA
         LOCATION COUNTY: MARICOPA
         GENDER: Unknown
         DATE OF BIRTH: 1901-01-01
         DRIVER AUTHORIZATION ID: 45678
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 8: A Driver License response by name in standardized form.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>DNR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZDMV0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS49</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>08:35</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>08:35</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00314</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="DNQ">
    <n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0" />
  </n2:NLETSInquiryData>
  <n2:NLETSResponseData n2:key="DNR">
    <ndm2:DriverMatch xmlns:ndm2="http://www.nlets.org/niem/nlets-driver-match/1.0/">
      <ndm2:IndividualMatch>
        <n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
          <nc:PersonBirthDate>
            <nc:Date>1950-01-01</nc:Date>
          </nc:PersonBirthDate>
          <nc:PersonHeightMeasure />
          <nc:PersonName>
            <nc:PersonGivenName>JOHN</nc:PersonGivenName>
            <nc:PersonMiddleName></nc:PersonMiddleName>
            <nc:PersonSurName>SMITH</nc:PersonSurName>
          </nc:PersonName>
          <nc:PersonRaceText>Black</nc:PersonRaceText>
          <nc:PersonSexText>Male</nc:PersonSexText>
          <nc:PersonSSNIdentification />
          <nc:PersonWeightMeasure />
          <n2c:DriverLicense>
            <nc:DriverLicenseIdentification>
              <nc:IdentificationID>12345</nc:IdentificationID>
            </nc:DriverLicenseIdentification>
            <nc:DriverLicenseExpirationDate>
              <nc:Date></nc:Date>
            </nc:DriverLicenseExpirationDate>
            <nc:DriverLicenseRestriction />
            <nc:DriverLicenseNonCommercialClassText></nc:DriverLicenseNonCommercialClassText>
            <nc:DriverLicenseNonCommercialStatusText></nc:DriverLicenseNonCommercialStatusText>
          </n2c:DriverLicense>
          <n2c:PersonContactInformation>
            <nc:ContactMailingAddress />
          </n2c:PersonContactInformation>
          <n2c:PersonResidentialAddress>
            <nc:LocationStreet>
              <nc:StreetFullText>1234 ANY STREET</nc:StreetFullText>
            </nc:LocationStreet>
            <nc:LocationCityName>PHOENIX</nc:LocationCityName>
            <nc:LocationCountyName>MARICOPA</nc:LocationCountyName>
            <nc:LocationStateName>AZ</nc:LocationStateName>
            <nc:LocationCountryName>UNITED STATES</nc:LocationCountryName>
            <nc:LocationPostalCode>85000</nc:LocationPostalCode>
            <n2c:ResidenceDateRange>
              <nc:EndDate />
            </n2c:ResidenceDateRange>
          </n2c:PersonResidentialAddress>
        </n2c:Driver>
      </ndm2:IndividualMatch>
      <ndm2:IndividualMatch>
        <n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
          <nc:PersonBirthDate>
            <nc:Date>1951-01-01</nc:Date>
          </nc:PersonBirthDate>
          <nc:PersonHeightMeasure />
          <nc:PersonName>
            <nc:PersonGivenName>JOHN</nc:PersonGivenName>
            <nc:PersonMiddleName></nc:PersonMiddleName>
            <nc:PersonSurName>SMITH</nc:PersonSurName>
          </nc:PersonName>
          <nc:PersonRaceText>White</nc:PersonRaceText>
          <nc:PersonSexText>Male</nc:PersonSexText>
          <nc:PersonSSNIdentification />
          <nc:PersonWeightMeasure />
          <n2c:DriverLicense>
            <nc:DriverLicenseIdentification>
              <nc:IdentificationID>23456</nc:IdentificationID>
            </nc:DriverLicenseIdentification>
            <nc:DriverLicenseExpirationDate>
              <nc:Date></nc:Date>
            </nc:DriverLicenseExpirationDate>
            <nc:DriverLicenseRestriction />
            <nc:DriverLicenseNonCommercialClassText></nc:DriverLicenseNonCommercialClassText>
            <nc:DriverLicenseNonCommercialStatusText></nc:DriverLicenseNonCommercialStatusText>
          </n2c:DriverLicense>
          <n2c:PersonContactInformation>
            <nc:ContactMailingAddress />
          </n2c:PersonContactInformation>
          <n2c:PersonResidentialAddress>
            <nc:LocationStreet>
              <nc:StreetFullText>2345 THAT PLACE</nc:StreetFullText>
            </nc:LocationStreet>
            <nc:LocationCityName>GLENDALE</nc:LocationCityName>
            <nc:LocationCountyName>MARICOPA</nc:LocationCountyName>
            <nc:LocationStateName>AZ</nc:LocationStateName>
            <nc:LocationCountryName>UNITED STATES</nc:LocationCountryName>
            <nc:LocationPostalCode>85000</nc:LocationPostalCode>
            <n2c:ResidenceDateRange>
              <nc:EndDate />
            </n2c:ResidenceDateRange>
          </n2c:PersonResidentialAddress>
        </n2c:Driver>
      </ndm2:IndividualMatch>
      <ndm2:IndividualMatch>
        <n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
          <nc:PersonBirthDate>
            <nc:Date>1952-01-01</nc:Date>
          </nc:PersonBirthDate>
          <nc:PersonHeightMeasure />
          <nc:PersonName>
            <nc:PersonGivenName>JOHN</nc:PersonGivenName>
            <nc:PersonMiddleName></nc:PersonMiddleName>
            <nc:PersonSurName>SMITH</nc:PersonSurName>
          </nc:PersonName>
          <nc:PersonRaceText>Black</nc:PersonRaceText>
          <nc:PersonSexText>Male</nc:PersonSexText>
          <nc:PersonSSNIdentification />
          <nc:PersonWeightMeasure />
          <n2c:DriverLicense>
            <nc:DriverLicenseIdentification>
              <nc:IdentificationID>34567</nc:IdentificationID>
            </nc:DriverLicenseIdentification>
            <nc:DriverLicenseExpirationDate>
              <nc:Date></nc:Date>
            </nc:DriverLicenseExpirationDate>
            <nc:DriverLicenseRestriction />
            <nc:DriverLicenseNonCommercialClassText></nc:DriverLicenseNonCommercialClassText>
            <nc:DriverLicenseNonCommercialStatusText></nc:DriverLicenseNonCommercialStatusText>
          </n2c:DriverLicense>
          <n2c:PersonContactInformation>
            <nc:ContactMailingAddress />
          </n2c:PersonContactInformation>
          <n2c:PersonResidentialAddress>
            <nc:LocationStreet>
              <nc:StreetFullText>3456 SOME DRIVE</nc:StreetFullText>
            </nc:LocationStreet>
            <nc:LocationCityName>PEORIA</nc:LocationCityName>
            <nc:LocationCountyName>MARICOPA</nc:LocationCountyName>
            <nc:LocationStateName>AZ</nc:LocationStateName>
            <nc:LocationCountryName>UNITED STATES</nc:LocationCountryName>
            <nc:LocationPostalCode>85000</nc:LocationPostalCode>
            <n2c:ResidenceDateRange>
              <nc:EndDate />
            </n2c:ResidenceDateRange>
          </n2c:PersonResidentialAddress>
        </n2c:Driver>
      </ndm2:IndividualMatch>
      <ndm2:IndividualMatch>
        <n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
          <nc:PersonBirthDate>
            <nc:Date>1901-01-01</nc:Date>
          </nc:PersonBirthDate>
          <nc:PersonHeightMeasure />
          <nc:PersonName>
            <nc:PersonGivenName>JOHN</nc:PersonGivenName>
            <nc:PersonMiddleName></nc:PersonMiddleName>
            <nc:PersonSurName>SMITH</nc:PersonSurName>
          </nc:PersonName>
          <nc:PersonSexText>Unknown</nc:PersonSexText>
          <nc:PersonSSNIdentification />
          <nc:PersonWeightMeasure />
          <n2c:DriverLicense>
            <nc:DriverLicenseIdentification>
              <nc:IdentificationID>45678</nc:IdentificationID>
            </nc:DriverLicenseIdentification>
            <nc:DriverLicenseExpirationDate>
              <nc:Date></nc:Date>
            </nc:DriverLicenseExpirationDate>
            <nc:DriverLicenseRestriction />
            <nc:DriverLicenseNonCommercialClassText></nc:DriverLicenseNonCommercialClassText>
            <nc:DriverLicenseNonCommercialStatusText></nc:DriverLicenseNonCommercialStatusText>
          </n2c:DriverLicense>
          <n2c:PersonContactInformation>
            <nc:ContactMailingAddress />
          </n2c:PersonContactInformation>
          <n2c:PersonResidentialAddress>
            <nc:LocationStreet>
              <nc:StreetFullText>4567 THIS AVENUE</nc:StreetFullText>
            </nc:LocationStreet>
            <nc:LocationCityName>PHOENIX</nc:LocationCityName>
            <nc:LocationCountyName>MARICOPA</nc:LocationCountyName>
            <nc:LocationStateName>AZ</nc:LocationStateName>
            <nc:LocationCountryName>UNITED STATES</nc:LocationCountryName>
            <nc:LocationPostalCode>85000</nc:LocationPostalCode>
            <n2c:ResidenceDateRange>
              <nc:EndDate />
            </n2c:ResidenceDateRange>
          </n2c:PersonResidentialAddress>
        </n2c:Driver>
      </ndm2:IndividualMatch>
    </ndm2:DriverMatch>
  </n2:NLETSResponseData>
</n2:NLETS>

Top

Parsed Driver's License NIEM Specifications

This section provides NIEM format and examples for Parsed Driver's License Response to a state (PDR),

All Nlets NIEM messages must be based on the Nlets NIEM Message Structure and include the standard Nlets XML Header as detailed in Message Structure. The NIEM header and hierarchy of the elements in this section have been omitted to avoid redundancy. The associated schemas and instances should be consulted to determine the correct XPaths of the elements.

Element Dictionary

Transaction types detailed below include: Standardized Parsed Status Response (PDR) and Standardized Parsed List Response (PDR).

Response Formats

Standardized Parsed Driver's License Status Response (PDR)

Response Data (n2:NLETSResponseData)
This element will contain all elements specific to this transaction.

  QualityCommentText (nc:QualityCommentText)
  This element will contain notes on any issue encountered during the parsing of the Text Response.
  An example of some of the issues that might be encountered and notated here include:
  An indication that the original response could only be partially parsed.
  An indication that the original response could not be parsed.
  An indication that the original response contains content that is not part of the CANDLE DR specification.
  In this case, it will also include a note to reference the OriginalTextResponse for additional information.

  OriginalTextResponse (n2:OriginalTextResponse)
  This element will contain the original, unaltered, text response from the incoming DR. If any issues
  were encountered during the parsing of the original text response, you can refer to this element for any
  additional information. Content in the original text response that is outside of the scope of a standard
  CANDLE DR specification will not be parsed and only be located in this element.

  Driver Status (n2:DriverStatus)
  This element will contain the standardized driver status response as defined in the
  Collaboration of AAMVA and Nlets for Driver License Exchange (CANDLE) specifications.

Standardized Parsed Driver's License Match List Response (PDR)

Response Data (n2:NLETSResponseData)
This element will contain all elements specific to this transaction.

  QualityCommentText (nc:QualityCommentText)
  This element will contain notes on any issue encountered during the parsing of the Text Response.

  OriginalTextResponse (n2:OriginalTextResponse)
  This element will contain the original, unaltered, text response from the incoming DR.

  Driver Matches (n2:DriverMatches)
  This element will contain the standardized driver match list response as defined in the
  Collaboration of AAMVA and Nlets for Driver License Exchange (CANDLE) specifications.


Parsed Driver's License NIEM Examples

Example 1: A Parsed Driver License response in standardized form.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>PDR</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZ007C100</nh2:OriginatingORIID>
		<nh2:DestinationORIID>AZNLETS39</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[NL0000TEST]]>
		</nh2:DocumentControlFieldText>
		<nh2:MessageReceiveDate>11/24/2019</nh2:MessageReceiveDate>
		<nh2:MessageReceiveTime>12:21</nh2:MessageReceiveTime>
		<nh2:MessageSendDate>11/24/2019</nh2:MessageSendDate>
		<nh2:MessageSendTime>12:21</nh2:MessageSendTime>
		<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
		<nh2:SendMessageNumeric>00404</nh2:SendMessageNumeric>
	</n2:NLETSMessageHeader>
	<n2:NLETSInquiryData n2:key="DQ">
		<n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
			<nc:PersonBirthDate>
				<nc:Date>1956-09-10</nc:Date>
			</nc:PersonBirthDate>
			<nc:PersonName>
				<nc:PersonFullName>OFFICE,D L</nc:PersonFullName>
			</nc:PersonName>
			<nc:PersonSexCode>M</nc:PersonSexCode>
		</n2c:Driver>
	</n2:NLETSInquiryData>
	<n2:NLETSResponseData n2:key="PDR">
		<nds2:DriverStatus xmlns:nds2="http://www.nlets.org/niem/nlets-driver-status/1.0">
			<n2c:AdditionalInformation xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
				<n2c:StateElement>
					<n2c:ElementFieldName>PRIMARY LICENSE RECEIPT CODE</n2c:ElementFieldName>
					<n2c:ElementFieldValue>X0000000</n2c:ElementFieldValue>
				</n2c:StateElement>
			</n2c:AdditionalInformation>
			<nds2:StandardResponse>
				<n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
					<nc:PersonBirthDate>
						<nc:Date>1956-09-10</nc:Date>
					</nc:PersonBirthDate>
					<nc:PersonEyeColorText>BRN</nc:PersonEyeColorText>
					<nc:PersonHairColorText>BLK</nc:PersonHairColorText>
					<nc:PersonHeightMeasure>
						<nc:MeasurePointValue>509</nc:MeasurePointValue>
					</nc:PersonHeightMeasure>
					<nc:PersonName>
						<nc:PersonFullName>D,L,OFFICE</nc:PersonFullName>
					</nc:PersonName>
					<nc:PersonSexText>M</nc:PersonSexText>
					<nc:PersonSSNIdentification>
						<nc:IdentificationID si:type="nc:TextType" xmlns:si="http://www.w3.org/2001/XMLSchema-instance">088888222</nc:IdentificationID>
					</nc:PersonSSNIdentification>
					<nc:PersonWeightMeasure>
						<nc:MeasurePointValue>175</nc:MeasurePointValue>
					</nc:PersonWeightMeasure>
					<n2c:DriverLicense>
						<nc:DriverLicenseIdentification>
							<j:IdentificationJurisdictionNCICLSTACode xmlns:j="http://niem.gov/niem/domains/jxdm/4.1">OPERATOR</j:IdentificationJurisdictionNCICLSTACode>
							<nc:IdentificationID si:type="nc:TextType" xmlns:si="http://www.w3.org/2001/XMLSchema-instance">D00627956</nc:IdentificationID>
						</nc:DriverLicenseIdentification>
						<nc:DriverLicenseExpirationDate>
							<nc:Date>1985-09-10</nc:Date>
						</nc:DriverLicenseExpirationDate>
						<nc:DriverLicenseIssueDate>
							<nc:Date>1983-09-10</nc:Date>
						</nc:DriverLicenseIssueDate>
						<nc:DriverLicenseNonCommercialStatusText>REVOCATION</nc:DriverLicenseNonCommercialStatusText>
						<nc:DriverLicenseNonCommercialStatusText>MANDATORY INSURANCE SUSPENSION</nc:DriverLicenseNonCommercialStatusText>
						<nc:DriverLicenseNonCommercialStatusText>SUSPENSION - MVD ACTION REQUIRED</nc:DriverLicenseNonCommercialStatusText>
						<nc:DriverLicenseNonCommercialStatusText>SUSPENSION - COURT ACTION REQUIRED</nc:DriverLicenseNonCommercialStatusText>
					</n2c:DriverLicense>
					<n2c:PersonContactInformation>
						<nc:ContactMailingAddress>
							<nc:StructuredAddress>
								<nc:LocationStreet>
									<nc:StreetFullText>1802 W JEFFERSON SUITE 33</nc:StreetFullText>
								</nc:LocationStreet>
								<nc:LocationCityName>PHOENIX</nc:LocationCityName>
								<nc:LocationStateName>AZ</nc:LocationStateName>
								<nc:LocationPostalCode>85007</nc:LocationPostalCode>
							</nc:StructuredAddress>
						</nc:ContactMailingAddress>
					</n2c:PersonContactInformation>
					<n2c:PersonContactInformation>
						<nc:ContactMailingAddress>
							<nc:StructuredAddress>
								<nc:LocationStreet>
									<nc:StreetFullText>PO BOX 2100</nc:StreetFullText>
								</nc:LocationStreet>
								<nc:LocationCityName>PHOENIX</nc:LocationCityName>
								<nc:LocationStateName>AZ</nc:LocationStateName>
								<nc:LocationPostalCode>85001</nc:LocationPostalCode>
							</nc:StructuredAddress>
						</nc:ContactMailingAddress>
					</n2c:PersonContactInformation>
				</n2c:Driver>
			</nds2:StandardResponse>
		</nds2:DriverStatus>
		<n2:OriginalTextResponse>NAM/OFFICE,D L.DOB/19560910.SEX/M.  NAME:D,L,OFFICE                                DOB:09/10/1956   RCPT#:X00000000  ADDR:1802 W JEFFERSON SUITE 33               PHOENIX                   AZ 85007  ISSUE DT:09/10/1983 EXP:09/10/1985      SEX:M HGT:509 WGT:175 HAIR:BLK EYE:BRN  OLN:D00627956     SSN:088888222     OLT:OPERATOR  MAIL:PO BOX 2100                             PHOENIX                   AZ 85001  STATUS    REVOCATION            MANDATORY INSURANCE SUSPENSION            SUSPENSION - MVD ACTION REQUIRED            SUSPENSION - COURT ACTION REQUIRED</n2:OriginalTextResponse>
	</n2:NLETSResponseData>
</n2:NLETS>

Example 2: A Parsed Driver's License Match List Response.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>PDR</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>NBDMV0000</nh2:OriginatingORIID>
		<nh2:DestinationORIID>AZNLETS39</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[NL0005TEST]]>
		</nh2:DocumentControlFieldText>
		<nh2:MessageReceiveDate>11/24/2019</nh2:MessageReceiveDate>
		<nh2:MessageReceiveTime>12:35</nh2:MessageReceiveTime>
		<nh2:MessageSendDate>11/24/2019</nh2:MessageSendDate>
		<nh2:MessageSendTime>12:35</nh2:MessageSendTime>
		<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
		<nh2:SendMessageNumeric>00412</nh2:SendMessageNumeric>
	</n2:NLETSMessageHeader>
	<n2:NLETSResponseData n2:key="PDR">
		<nds2:DriverStatus xmlns:nds2="http://www.nlets.org/niem/nlets-driver-status/1.0">
			<n2c:AdditionalInformation xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
				<n2c:StateElement>
					<n2c:ElementFieldName>HEADER</n2c:ElementFieldName>
					<n2c:ElementFieldValue>DR.AZNLETS39..05LW003XXD..</n2c:ElementFieldValue>
				</n2c:StateElement>
				<n2c:StateElement>
					<n2c:ElementFieldName>CAVEAT</n2c:ElementFieldName>
					<n2c:ElementFieldValue>THIS INFORMATION MAY BE USED FOR CRIMINAL JUSTICE PURPOSES ONLY.</n2c:ElementFieldValue>
				</n2c:StateElement>
			</n2c:AdditionalInformation>
		</nds2:DriverStatus>
		<ndm2:DriverMatch xmlns:ndm2="http://www.nlets.org/niem/nlets-driver-match/1.0">
			<ndm2:IndividualMatch>
				<n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
					<nc:PersonBirthDate>
						<nc:Date>1991-06-02</nc:Date>
					</nc:PersonBirthDate>
					<nc:PersonEyeColorText>BLU</nc:PersonEyeColorText>
					<nc:PersonHairColorText>BLN</nc:PersonHairColorText>
					<nc:PersonHeightMeasure>
						<nc:MeasurePointValue>509</nc:MeasurePointValue>
					</nc:PersonHeightMeasure>
					<nc:PersonName>
						<nc:PersonGivenName>JERROD</nc:PersonGivenName>
						<nc:PersonMiddleName>L</nc:PersonMiddleName>
						<nc:PersonSurName>DOE</nc:PersonSurName>
					</nc:PersonName>
					<nc:PersonRaceText>W</nc:PersonRaceText>
					<nc:PersonSexText>M</nc:PersonSexText>
					<nc:PersonWeightMeasure>
						<nc:MeasurePointValue>170</nc:MeasurePointValue>
					</nc:PersonWeightMeasure>
					<n2c:DriverLicense>
						<nc:DriverLicenseIdentification>
							<nc:IdentificationID si:type="nc:TextType" xmlns:si="http://www.w3.org/2001/XMLSchema-instance">H12345678</nc:IdentificationID>
						</nc:DriverLicenseIdentification>
					</n2c:DriverLicense>
					<n2c:PersonContactInformation>
						<nc:ContactMailingAddress>
							<nc:StructuredAddress>
								<nc:LocationStreet>
									<nc:StreetFullText>321 W CIRCLE DR</nc:StreetFullText>
								</nc:LocationStreet>
								<nc:LocationCityName>NORTH PLATTE</nc:LocationCityName>
								<nc:LocationStateName>NE</nc:LocationStateName>
								<nc:LocationPostalCode>69101</nc:LocationPostalCode>
							</nc:StructuredAddress>
						</nc:ContactMailingAddress>
					</n2c:PersonContactInformation>
				</n2c:Driver>
			</ndm2:IndividualMatch>
			<ndm2:IndividualMatch>
				<n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
					<nc:PersonBirthDate>
						<nc:Date>1989-07-18</nc:Date>
					</nc:PersonBirthDate>
					<nc:PersonEyeColorText>GRN</nc:PersonEyeColorText>
					<nc:PersonHairColorText>BRO</nc:PersonHairColorText>
					<nc:PersonHeightMeasure>
						<nc:MeasurePointValue>508</nc:MeasurePointValue>
					</nc:PersonHeightMeasure>
					<nc:PersonName>
						<nc:PersonGivenName>JAMES</nc:PersonGivenName>
						<nc:PersonSurName>DOEE</nc:PersonSurName>
					</nc:PersonName>
					<nc:PersonRaceText>W</nc:PersonRaceText>
					<nc:PersonSexText>M</nc:PersonSexText>
					<nc:PersonWeightMeasure>
						<nc:MeasurePointValue>160</nc:MeasurePointValue>
					</nc:PersonWeightMeasure>
					<n2c:DriverLicense>
						<nc:DriverLicenseIdentification>
							<nc:IdentificationID si:type="nc:TextType" xmlns:si="http://www.w3.org/2001/XMLSchema-instance">H23456789</nc:IdentificationID>
						</nc:DriverLicenseIdentification>
					</n2c:DriverLicense>
					<n2c:PersonContactInformation>
						<nc:ContactMailingAddress>
							<nc:StructuredAddress>
								<nc:LocationStreet>
									<nc:StreetFullText>321 S BIRCHWOOD DR APT B</nc:StreetFullText>
								</nc:LocationStreet>
								<nc:LocationCityName>FREMONT</nc:LocationCityName>
								<nc:LocationStateName>NE</nc:LocationStateName>
								<nc:LocationPostalCode>68025</nc:LocationPostalCode>
							</nc:StructuredAddress>
						</nc:ContactMailingAddress>
					</n2c:PersonContactInformation>
				</n2c:Driver>
			</ndm2:IndividualMatch>
			<ndm2:IndividualMatch>
				<n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
					<nc:PersonBirthDate>
						<nc:Date>1985-12-12</nc:Date>
					</nc:PersonBirthDate>
					<nc:PersonEyeColorText>HAZ</nc:PersonEyeColorText>
					<nc:PersonHairColorText>BLK</nc:PersonHairColorText>
					<nc:PersonHeightMeasure>
						<nc:MeasurePointValue>511</nc:MeasurePointValue>
					</nc:PersonHeightMeasure>
					<nc:PersonName>
						<nc:PersonGivenName>JEFFREY</nc:PersonGivenName>
						<nc:PersonMiddleName>D</nc:PersonMiddleName>
						<nc:PersonSurName>DOEE</nc:PersonSurName>
					</nc:PersonName>
					<nc:PersonRaceText>W</nc:PersonRaceText>
					<nc:PersonSexText>M</nc:PersonSexText>
					<nc:PersonWeightMeasure>
						<nc:MeasurePointValue>175</nc:MeasurePointValue>
					</nc:PersonWeightMeasure>
					<n2c:DriverLicense>
						<nc:DriverLicenseIdentification>
							<nc:IdentificationID si:type="nc:TextType" xmlns:si="http://www.w3.org/2001/XMLSchema-instance">H34567890</nc:IdentificationID>
						</nc:DriverLicenseIdentification>
					</n2c:DriverLicense>
					<n2c:PersonContactInformation>
						<nc:ContactMailingAddress>
							<nc:StructuredAddress>
								<nc:LocationStreet>
									<nc:StreetFullText>4321 JACOBS CREEK DR APT 232</nc:StreetFullText>
								</nc:LocationStreet>
								<nc:LocationCityName>LINCOLN</nc:LocationCityName>
								<nc:LocationStateName>NE</nc:LocationStateName>
								<nc:LocationPostalCode>68512</nc:LocationPostalCode>
							</nc:StructuredAddress>
						</nc:ContactMailingAddress>
					</n2c:PersonContactInformation>
				</n2c:Driver>
			</ndm2:IndividualMatch>
			<ndm2:IndividualMatch>
				<n2c:Driver xmlns:n2c="http://www.nlets.org/niem/nlets-core/1.0">
					<nc:PersonBirthDate>
						<nc:Date>1982-11-27</nc:Date>
					</nc:PersonBirthDate>
					<nc:PersonEyeColorText>GRN</nc:PersonEyeColorText>
					<nc:PersonHairColorText>BRO</nc:PersonHairColorText>
					<nc:PersonHeightMeasure>
						<nc:MeasurePointValue>604</nc:MeasurePointValue>
					</nc:PersonHeightMeasure>
					<nc:PersonName>
						<nc:PersonGivenName>JACOB</nc:PersonGivenName>
						<nc:PersonMiddleName>J</nc:PersonMiddleName>
						<nc:PersonSurName>DOOE</nc:PersonSurName>
					</nc:PersonName>
					<nc:PersonRaceText>W</nc:PersonRaceText>
					<nc:PersonSexText>M</nc:PersonSexText>
					<nc:PersonWeightMeasure>
						<nc:MeasurePointValue>195</nc:MeasurePointValue>
					</nc:PersonWeightMeasure>
					<n2c:DriverLicense>
						<nc:DriverLicenseIdentification>
							<nc:IdentificationID si:type="nc:TextType" xmlns:si="http://www.w3.org/2001/XMLSchema-instance">H45678901</nc:IdentificationID>
						</nc:DriverLicenseIdentification>
					</n2c:DriverLicense>
					<n2c:PersonContactInformation>
						<nc:ContactMailingAddress>
							<nc:StructuredAddress>
								<nc:LocationStreet>
									<nc:StreetFullText>3210 FIELDCREST DR</nc:StreetFullText>
								</nc:LocationStreet>
								<nc:LocationCityName>OMAHA</nc:LocationCityName>
								<nc:LocationStateName>NE</nc:LocationStateName>
								<nc:LocationPostalCode>68114</nc:LocationPostalCode>
							</nc:StructuredAddress>
						</nc:ContactMailingAddress>
					</n2c:PersonContactInformation>
				</n2c:Driver>
			</ndm2:IndividualMatch>
		</ndm2:DriverMatch>
		<n2:OriginalTextResponse>NEBRASKA DMV RESPONSE

DR.AZNLETS39..05LW003XXD..
STATE OF NEBRASKA DRIVER LICENSE QUERY CANDIDATE LIST

THIS INFORMATION MAY BE USED FOR CRIMINAL JUSTICE PURPOSES ONLY.

OLN/H12345678   DOE,JERROD,L               DOB/06-02-1991 SEX/M
RAC/W   HGT/509   WGT/170   EYE/BLU   HAI/BLN
321 W CIRCLE DR                   NORTH PLATTE, NE.  69101

OLN/H23456789   DOEE,JAMES                   DOB/07-18-1989 SEX/M
RAC/W   HGT/508   WGT/160   EYE/GRN   HAI/BRO
321 S BIRCHWOOD DR APT B          FREMONT, NE.  68025

OLN/H34567890   DOEE,JEFFREY,D               DOB/12-12-1985 SEX/M
RAC/W   HGT/511   WGT/175   EYE/HAZ   HAI/BLK
4321 JACOBS CREEK DR APT 232      LINCOLN, NE.  68512

OLN/H45678901   DOOE,JACOB,J                DOB/11-27-1982 SEX/M
RAC/W   HGT/604   WGT/195   EYE/GRN   HAI/BRO
3210 FIELDCREST DR                OMAHA, NE.  68114

*** END OF CANDIDATE LIST ***


		</n2:OriginalTextResponse>
	</n2:NLETSResponseData>
</n2:NLETS>


Top

Legacy (DEPRECATED)

Driver's License Legacy Specifications

This section describes Legacy format and provides examples for driver's license transactions.

The following are general specifications for Driver's License queries and responses.

  • All inquiries and responses are in a fixed format.
  • All messages are preceded by a standard input header as described in Message Structure.
  • All data elements are preceded by a prefix and terminated by a period.
  • The final character of the message should not be a period (conforms to standard NCIC message structure).
  • Control characters are permitted throughout the text of the message and should be ignored by the queried state when examining the inquiry.
  • No embedded spaces or special characters (i.e. hyphens) should be in the inquiry.
  • If a regional code is used, the message type should be DQG. If it is not, Nlets will change it to DQG and handle it at a lower priority.
  • States receiving a DQG must respond with a DRG.

Query Formats

To send a driver's license query:

Enter the following:
DQ. or DQG.
Sending ORI followed by a period.
Destination ORI followed by a period (up to five 2-character state codes or regional codes; if
a regional code the DQG should be used).
If needed, optional control field.
TXT
CR,LF,DEL (Optional).
Enter either:
"OLN/" followed by the driver's license number. Not valid for DQG.
OR-
"NAM/" followed by the name and a period.
"DOB/" followed by the complete date of birth and a period. Format: mmddyy or ccyymmdd.
"SEX/" followed by the sex code.
Only queries on NAM/DOB may be used for a DQG.
"IMQ/" followed by a "Y" or "N"; for DQ only, not for DQG.

Note: Nlets also supports inquiries on Driver history information.
The user should recognize the differences between these two types of transactions as described below.

  • Driver's License transactions and Driver History transactions utilize different message types.
  • Driver history requests and responses use KQ and KR respectively, while normal driver
     license requests utilize DQ/DR.
  • Although the required information is identical, users requesting driver history with a KQ may
     include a purpose code and/or an attention field.
  • There are no specific response formats for KRs as there are for DRs.
  • Unlike DQs only a single two character state code may be used as a destination address for KQs.

The format for a driver's license inquiry on name and date of birth is as follows.

Entry # Char. Explanation

DQ.
or
DQG

2 Message type followed by a period.
Message Header 13-36

Standard input message header, may include control
field and up to 5 addresses (state or regional codes;
DQG should be used for regionally addressed queries).

TXT 3 Fixed filed prefix to beginning of message.
CR,LF,DEL 3 Control characters (optional).
NAM/ 4 Prefix to identify name.
Name Max. 30

Full name; format is last name, comma, space after
comma is optional) first name, space, middle initial or
name, space, suffix (Jr., III, etc.) Followed by a period.
Titles or degrees should not be used as part of the
name.

DOB/ 4 Prefix to identify date of birth.
Date of Birth 6

Date of Birth followed by a period. Express as mmddyy
or ccyymmdd. Complete DOB must be present. Some
states have different requirements. Check their OLN
HELP file for details.

SEX/ 4 Prefix to identify sex.
Sex 1 Sex; conforms to NCIC codes.
IMQ/ 4 (For XML use only) Prefix to identify image request field.
Image Request 1 Y to request driver photo; use N if no image is wanted
or omit IMQ/ field.

The format for a driver's license inquiry or driver's license number is:

Entry # Char. Explanation
DQ. 3 Message type followed by a period.
Message Header 13-36 Standard input message header may include control field.
TXT 3 Fixed filed prefix to beginning of message.
CR,LF,DEL 3 Control characters (optional).
OLN/ 4 Prefix to identify driver license number.
Driver's Lic. # 1-20 Driver license number.
IMQ/ 4 (For XML use only) Prefix to identify image request field.
Image Request 1 Y to request driver photo; use N if no image is wanted
or omit IMQ/ field.

Response Formats

  • Should the information be unavailable, or, after interrogation of the state files, no information is found, a standard response message is returned.
  • If a data field is unavailable, the prefix, data element, and period should be omitted from the response.
  • The message should be compacted to eliminate the resultant spaces.

Note: Inquiries on name may result in multiple hits. Only close matches (i.e., exact match on
last name and DOB) should be returned. When multiple hits do occur, they should be
returned as separate messages.

Note: All responses to DNQ inquiries must have a message type of DNR.

Note: "NOT ON FILE", "FILE NOT AVAILABLE" and "TEMPORARILY UNAVAILABLE"
messages will be followed by either the driver's name or driver's license number upon which
the query was based.

Driver's License by Name Only General Specifications (DNQ)

To send a Driver's License by Name Only Query (DNQ) enter the following.

Enter:
DNQ.
Sending ORI followed by a period
Destination ORI followed by a period (only one 2-character state code)
If needed, optional control field
TXT
CR,LF,DEL (Optional)
Then enter:
"NAM/" followed by, at minimum, the last, first name
And any of these optional fields:
"AGE/" followed by the age
"SEX/" followed by the sex
"CTY/" followed by city, town or village of subject
"COU/" followed by the county where the subject lives
"NXT/" followed by special codes or numbers to request the next screen or page.

Obtain this information from the state's HELP file.

The format for a driver's license inquiry (DNQ) when a complete date of birth is not known is presented below.

Note that the message key is different than a normal driver license query.

Entry # Char. Explanation
DNQ. 3 Message type followed by a period.
Message Header 13-24 Standard input message header, may include control field
but only a single 2 character state code.
TXT 3 Fixed filed prefix to beginning of message.
CR,LF,DEL 3 Control characters (optional).
NAM/ 4 Prefix to identify name.
Name Max. 30

This field must include at least a first and last name in the
standard name format (surname, first name). Some
states allow a question mark "?" in the surname if the full
surname is not known. Consult state help files to
determine if a state can support this capability. (E.g.,
NAM/PUBL?, JOHN Q.).

AGE/ (optional) 4 Prefix to identify age.
Age 2

Age followed by a period. If a complete date of birth is
known a DQ should be used. Some states may handle
age differently than others. Consult their HELP file for
details. The address is xxOLNHELP where xx=2
character state code.

SEX/ (optional) 4 Prefix to identify sex.
Sex 1 Sex; conforms to NCIC codes.
CTY/ (optional) 4 Prefix to identify city, village or town where subject lives.
City 20 City, village or town where subject lives.
COU/ (optional) 4 Prefix to identify county.
County 20 County where subject lives.
NXT/ (optional) 4 Prefix to identify the Next field.
Next page or group 20

A free form field used to request additional pages.
Individual state HELP files will dictate if this field is used
and what it must contain.

Driver's License by Name Only Response Format (DNR)

All responses to DNQ inquiries must have a message type of "DNR" but otherwise are identical to DQ responses (DR).

States must use the "DNR" message type for responses to DNQ messages.

The free form fields "RSTR:" and "STATUS:" are for the states to indicate restrictions on an individual when operating his vehicle (i.e. corrective lenses) and the status of the individual's license (i.e. revoked), respectively.

Information should be confined to short, concise, plain English messages.

Driver's License Legacy Examples

Example 1: A Driver License query by name, date of birth and sex.

DQ.AZNLETS20.AZ.TXT
NAM/SMITH,JOHN.DOB/19500101.SEX/M

Example 2: A Driver License query by OLN.

DQ.AZNLETS20.AZ.TXT
OLN/111111111

Example 3: A Driver License response.

DR.AZDMV0000
11:08 10/07/2011 00248
11:08 10/07/2011 00052 AZNLETS20
TXT
Query data:
OLN/111111111.IMQ/N.
NAME: SMITH, JOHN
RESIDENCE ADDRESS: 1234 ANYSTREET; PHOENIX,AZ 85000
COUNTRY: United States
DATE OF BIRTH: 1950-01-01
HEIGHT: 507
WEIGHT: 150
GENDER: MALE
RACE: UNKNOWN
*** DRIVER LICENSE DETAILS ***
DRIVER AUTHORIZATION ID: 111111111
JURISDICTION AUTHORITY CODE: AZ
ISSUE DATE: 2009-01-10
EXPIRATION DATE: 2045-01-10
DRIVER ENDORSEMENT: MOTORCYCLE
DRIVING ENDORSMENT CODE: M
DRIVER LICENSE NON-COMMERCIAL CLASS: LICENSE
DRIVER LICENSE NON-COMMERCIAL CLASS CODE: C
LICENSED COMMERCIAL DRIVER: NO
LICENSED NON-COMMERCIAL DRIVER: YES
DRIVER LICENSE NON-COMMERCIAL STATUS: VALID OPERATORS LICENSE
DRIVER ORGAN DONOR: true

Example 4: A Driver License query by Region. The response will be a standard Driver License response (DR).

DQG.AZNLETS20.A1.TXT
NAM/SMITH,JOHN.DOB/19500101.SEX/M

Example 5: A Driver License query by name.

DNQ.AZNLETS20.AZ.TXT
NAM/SMITH,JOHN

Example 6: A Driver License response by name.

DNR.AZDMV0000
08:10 10/11/2011 79931
08:10 10/11/2011 00711 AZNLETS20
TXT
JOHN SMITH
RESIDENCE ADDRESS: 1234 ANY STREET; PHOENIX,AZ 85000
COUNTRY: UNITED STATES
COUNTY: MARICOPA
LOCATION COUNTY: MARICOPA
RACE: Black
GENDER: Male
DATE OF BIRTH: 1950-01-01
DRIVER AUTHORIZATION ID: 12345

JOHN SMITH
RESIDENCE ADDRESS: 2345 THAT PLACE; GLENDALE,AZ 85000
COUNTRY: UNITED STATES
COUNTY: MARICOPA
LOCATION COUNTY: MARICOPA
RACE: White
GENDER: Male
DATE OF BIRTH: 1951-01-01
DRIVER AUTHORIZATION ID: 23456

JOHN SMITH
RESIDENCE ADDRESS: 3456 SOME DRIVE; PEORIA,AZ 85000
COUNTRY: UNITED STATES
COUNTY: MARICOPA
LOCATION COUNTY: MARICOPA
RACE: Black
GENDER: Male
DATE OF BIRTH: 1952-01-01
DRIVER AUTHORIZATION ID: 34567

JOHN SMITH
RESIDENCE ADDRESS: 4567 THIS AVENUE; PHOENIX,AZ 85000
COUNTRY: UNITED STATES
COUNTY: MARICOPA
LOCATION COUNTY: MARICOPA
GENDER: Unknown
DATE OF BIRTH: 1901-01-01
DRIVER AUTHORIZATION ID: 45678

Top

Downloads

Download DQ Schema

Download DR Schema (updated 6/28/2019)

Download DR Stylesheet (updated 05/05/2021)

Download DQG Schema

Download DNQ Schema

Download DNR Schema (updated 7/1/2019)

Download DNR Stylesheet (updated 11/13/2020)

Download PDR Stylesheet (Added 06/02/2020)

CANDLE Specifications

Top