Section 16: Hit Confirmation Transactions: Difference between revisions
No edit summary |
m (correcting explanation for "VYR/ (optional)" to show "year" instead of "make") |
||
(22 intermediate revisions by 7 users not shown) | |||
Line 7: | Line 7: | ||
Users may send a request for a hit confirmation on an NCIC record (YQ) to a state via Nlets. The destination agency will return a hit confirmation response (YR). Nlets will edit the messages before forwarding the request and response to the destination state(s). | Users may send a request for a hit confirmation on an NCIC record (YQ) to a state via Nlets. The destination agency will return a hit confirmation response (YR). Nlets will edit the messages before forwarding the request and response to the destination state(s). | ||
Although a hit confirmation request relies primarily on the cooperation of the entering agency, the agency making the request also should provide sufficient information, in the proper format, to | Although a hit confirmation request relies primarily on the cooperation of the entering agency, the agency making the request also should provide sufficient information, in the proper format, to ensure an efficient exchange of information. | ||
When an agency receives a hit, and an individual is being detained, or piece of property seized, confirmation with the entering agency is necessary to ensure the validity of the record prior to taking action. The entering agency, or a secondary agency acting on their behalf, must be available 24-hours a day, 7 days a week for confirmation. | When an agency receives a hit, and an individual is being detained, or piece of property seized, confirmation with the entering agency is necessary to ensure the validity of the record prior to taking action. The entering agency, or a secondary agency acting on their behalf, must be available 24-hours a day, 7 days a week for confirmation. | ||
Line 20: | Line 20: | ||
<li>Do not include sets of data elements that do not pertain to the type of hit confirmation request (YQ). For example, if you are attempting to confirm a wanted person record, you should include only the required data elements plus name (NAM), date of birth (DOB), and sex (SEX) (optional). If you include other data elements such as license plate (LIC) or vehicle identification number (VIN) for a wanted person type record, the message will be rejected by Nlets. | <li>Do not include sets of data elements that do not pertain to the type of hit confirmation request (YQ). For example, if you are attempting to confirm a wanted person record, you should include only the required data elements plus name (NAM), date of birth (DOB), and sex (SEX) (optional). If you include other data elements such as license plate (LIC) or vehicle identification number (VIN) for a wanted person type record, the message will be rejected by Nlets. | ||
<li>Blank data fields should not be sent to Nlets. Both the field and the prefix MUST be eliminated. | <li>Blank data fields should not be sent to Nlets. Both the field and the prefix MUST be eliminated. | ||
<li>Use the vehicle identification number (<syntaxhighlight lang="xml"><nc:IdentificationID></nc:IdentificationID></syntaxhighlight> | <li>Use the vehicle identification number (or VIN/ prefix) to identify an owner applied number on a vehicle. <syntaxhighlight lang="xml"><nc:IdentificationID></nc:IdentificationID></syntaxhighlight> | ||
<li>When sending a request for hit confirmation (YQ) to Canada insert "NONE" in the NCIC field (e.g., <syntaxhighlight lang="xml"><scr:NCICRecordID>NONE</scr:NCICRecordID></syntaxhighlight> | <li>When sending a request for hit confirmation (YQ) to Canada insert "NONE" in the NCIC field (e.g., or NIC/NONE.) <syntaxhighlight lang="xml"><scr:NCICRecordID>NONE</scr:NCICRecordID></syntaxhighlight> | ||
</ul> | </ul> | ||
Line 62: | Line 62: | ||
</ul> | </ul> | ||
The agency making the request should provide as much information, in the proper format, to | The agency making the request should provide as much information, in the proper format, to ensure an efficient exchange of information. This includes using the priority designation appropriately. | ||
Agencies are encouraged to use the lower priority when an immediate response is not necessary. It will make the entire process more efficient and responsive. | Agencies are encouraged to use the lower priority when an immediate response is not necessary. It will make the entire process more efficient and responsive. | ||
Line 72: | Line 72: | ||
<table border="1"> | <table border="1"> | ||
<tr> | <tr> | ||
<th align="center">****HIT CONFIRMATION REQUEST - | <th align="center">****HIT CONFIRMATION REQUEST - RNO VALUE****</th> | ||
</tr> | </tr> | ||
</table> | </table> | ||
<table border="1"> | <table border="1"> | ||
<tr> | |||
<th align="center">RNO is "1"</th> | |||
<th align="center">"FIRST" request will be sent. </th> | |||
<th align="center"> | |||
The message will only be addressed to the given destination. | |||
</th> | |||
</tr> | |||
<tr> | <tr> | ||
<th align="center">RNO is "2"</th> | <th align="center">RNO is "2"</th> | ||
Line 100: | Line 107: | ||
<li>The line in the inquiry identifying the record's unique fields (license plate, name, serial number, etc.) will vary depending on the type of record being confirmed. This is identified in the request type field (RTY). | <li>The line in the inquiry identifying the record's unique fields (license plate, name, serial number, etc.) will vary depending on the type of record being confirmed. This is identified in the request type field (RTY). | ||
<li>Nlets has inserted several phrases to make the hit confirmation readable. These include indication of first notice, priority, and the type of record being requested for confirmation (e.g. MISSING PERSON). | <li>Nlets has inserted several phrases to make the hit confirmation readable. These include indication of first notice, priority, and the type of record being requested for confirmation (e.g. MISSING PERSON). | ||
<li>Nlets will translate the priority field ( | <li>Nlets will translate the priority field (or PRI/) to a plain English sentence, such as "URGENT! - RESPOND WITHIN 10 MINUTES". Only the selection made will be displayed. The sender will ALWAYS determine the priority. <syntaxhighlight lang="xml"><n2:RequestPriorityCode></syntaxhighlight> | ||
<li>For a second or third request, Nlets will send the original YQ to multiple destinations and will add an XML element <n2:Recipients> as a child to <n2:NLETSInquiryData> that contains all ORIs to which Nlets has sent the YQ message. This element is informational only and included as a "value add" only. For a second request, the recipients will be the destination ORI of the original YQ message and the ORI ssHITC000, where ss is the two-letter state code of the original destination ORI. For a third request, recipients will additionally include the ORI DCFBIWA00. Note that each of the YQ messages is identical, except the destination ORI, and each one includes the same <n2:Recipients> element. For example, in the code snippet below for a third request, the <n2:Recipients> element indicates that Nlets has sent three YQ messages, one to "ZZ0101010", one to "ZZHITC000", and one to "DCFBIWA00", each of which would include and identical <n2:Recipients> element: | |||
<syntaxhighlight lang="xml"> | |||
<n2:NLETSInquiryData n2:key="YQ"> | |||
<!-- All other elements here --> | |||
<n2:Recipients> <!-- Nlets addition to original message --> | |||
<j:OrganizationORIIdentification> | |||
<nc:IdentificationID>ZZ0101010</nc:IdentificationID> | |||
</j:OrganizationORIIdentification> | |||
<j:OrganizationORIIdentification> | |||
<nc:IdentificationID>ZZHITC000</nc:IdentificationID> | |||
</j:OrganizationORIIdentification> | |||
<j:OrganizationORIIdentification> | |||
<nc:IdentificationID>DCFBIWA00</nc:IdentificationID> | |||
</j:OrganizationORIIdentification> | |||
</n2:Recipients> | |||
</n2:NLETSInquiryData> | |||
</syntaxhighlight> | |||
<li>Nlets will edit all requests for hit confirmation (YQs) for required data elements, field length and allowable data within the fields. Editing will be similar to editing on Vehicle Registration queries (RQs) and Driver Registration queries (DQs). | <li>Nlets will edit all requests for hit confirmation (YQs) for required data elements, field length and allowable data within the fields. Editing will be similar to editing on Vehicle Registration queries (RQs) and Driver Registration queries (DQs). | ||
</ul> | </ul> | ||
Line 532: | Line 556: | ||
<th align="center">Alphanumeric</th> | <th align="center">Alphanumeric</th> | ||
<th align="center">Boat registration number</th> | <th align="center">Boat registration number</th> | ||
</tr> | |||
<tr> | |||
<th align="left"> | |||
<syntaxhighlight lang="xml"> | |||
<nc:Vessel> | |||
<nc:ItemMakeName>XXXX</nc:ItemMakeName> | |||
</nc:Vessel> | |||
</syntaxhighlight> | |||
</th> | |||
<th align="center">BMA/</th> | |||
<th align="center">1-24</th> | |||
<th align="center">See NCIC Manual</th> | |||
<th align="center">Boat make (optional)</th> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 550: | Line 587: | ||
<th align="center">See NCIC Manual</th> | <th align="center">See NCIC Manual</th> | ||
<th align="center">Boat hull number</th> | <th align="center">Boat hull number</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 565: | Line 599: | ||
<th align="center">1-24</th> | <th align="center">1-24</th> | ||
<th align="center">See NCIC Manual</th> | <th align="center">See NCIC Manual</th> | ||
<th align="center">Boat make</th> | <th align="center">Boat make (optional)</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 713: | Line 747: | ||
<j:Warrant> | <j:Warrant> | ||
<j:CourtOrderIssuingCourt> | <j:CourtOrderIssuingCourt> | ||
< | <nc:OrganizationIdentification> | ||
<nc:IdentificationID>XXXX</nc:IdentificationID> | <nc:IdentificationID>XXXX</nc:IdentificationID> | ||
</nc: | </nc:OrganizationIdentification> | ||
</j:CourtOrderIssuingCourt> | |||
</j:Warrant> | |||
</syntaxhighlight> | </syntaxhighlight> | ||
</th> | </th> | ||
Line 2,553: | Line 2,589: | ||
</table> | </table> | ||
<u>Example 11</u>: Hit Confirmation | <u>Example 11</u>: Hit Confirmation response for Missing Person. | ||
<table border="1"> | <table border="1"> | ||
Line 2,559: | Line 2,595: | ||
<th align="left"> | <th align="left"> | ||
<syntaxhighlight lang="xml"> | <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/ | <n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | ||
<n2:NLETSMessageHeader> | <n2:NLETSMessageHeader> | ||
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText> | <nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText> | ||
<nh2:OriginatingORIID>AZNLETS40</nh2:OriginatingORIID> | <nh2:OriginatingORIID>AZNLETS40</nh2:OriginatingORIID> | ||
<nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID> | <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID> | ||
<nh2:DocumentControlFieldText> | <nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText> | ||
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate> | <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate> | ||
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime> | <nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime> | ||
Line 2,573: | Line 2,609: | ||
</n2:NLETSMessageHeader> | </n2:NLETSMessageHeader> | ||
<n2:NLETSResponseData n2:key="YR"> | <n2:NLETSResponseData n2:key="YR"> | ||
<n2:QueryRequestActivity> | <n2-yr:HitConfirmation> | ||
<n2-yr:QueryRequestActivity> | |||
<n2-yr:RequestCategoryCode>MP</n2-yr:RequestCategoryCode> | |||
<nc:Incident> | |||
<nc:ActivityIdentification> | |||
</nc: | <nc:IdentificationID>CASE-1234</nc:IdentificationID> | ||
</nc: | <nc:IdentificationJurisdiction> | ||
<n2: | <nc:JurisdictionText>AZ</nc:JurisdictionText> | ||
<nc:OrganizationName>NLETS | </nc:IdentificationJurisdiction> | ||
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>1957-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ActivityIdentification> | |||
<nc:ActivityStatus> | |||
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText> | |||
</nc:ActivityStatus> | |||
</nc:Incident> | |||
<scr:NCICRecordID>W123456789</scr:NCICRecordID> | |||
</nc: | </n2-yr:QueryRequestActivity> | ||
</ | <nc:Person> | ||
</n2: | <nc:PersonBirthDate> | ||
<nc:Date>1920-01-26</nc:Date> | |||
</nc:PersonBirthDate> | |||
<n2: | <nc:PersonName> | ||
<nc:PersonGivenName>MINNIE</nc:PersonGivenName> | |||
<nc:PersonSurName>MOUSE</nc:PersonSurName> | |||
<nc:PersonFullName>MOUSE, MINNIE</nc:PersonFullName> | |||
</nc:PersonName> | |||
<nc:PersonSexText>F</nc:PersonSexText> | |||
</nc:Person> | |||
<n2-yr:Confirmation> | |||
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText> | |||
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText> | |||
<n2-yr:ConfirmingAgency> | |||
<nc:OrganizationName>NLETS</nc:OrganizationName> | |||
<nc:OrganizationPrimaryContactInformation> | |||
<nc:ContactTelephoneNumber> | |||
<nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID> | |||
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID> | |||
</nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText> | |||
</nc:ContactTelephoneNumber> | |||
<nc:ContactEntity> | |||
<nc:EntityPerson> | |||
<nc:PersonName> | |||
<nc:PersonFullName>John D Smith</nc:PersonFullName> | |||
</nc:PersonName> | |||
</nc:EntityPerson> | |||
</nc:ContactEntity> | |||
</nc:OrganizationPrimaryContactInformation> | |||
</n2-yr:ConfirmingAgency> | |||
<n2-yr:Remarks>MISSING PERSON IS CONFIRMED PER SGT PLEASE CONTACT | |||
SUBJECT ALONE TO ASK IF SHE IS OKAY AND EVERYTHING IS GOOD AND IF | |||
SO THEN SHE CAN BE LET GO PLEASE PLACE LOCATE AND ADVISE INFORMATION THANK YOU</n2-yr:Remarks> | |||
</n2-yr:Confirmation> | |||
</n2-yr:HitConfirmation> | |||
</n2:NLETSResponseData> | |||
</n2:NLETS> | |||
</syntaxhighlight> | |||
</th> | |||
</tr> | |||
</table> | |||
<u>Example 12</u>: Hit Confirmation response for Protection Order. | |||
<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://release.niem.gov/niem/niem-core/3.0/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | |||
<n2:NLETSMessageHeader> | |||
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText> | |||
<nh2:OriginatingORIID>AZNLETS40</nh2:OriginatingORIID> | |||
<nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID> | |||
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText> | |||
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate> | |||
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime> | |||
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate> | |||
<nh2:MessageSendTime>08:55</nh2:MessageSendTime> | |||
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric> | |||
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric> | |||
</n2:NLETSMessageHeader> | |||
<n2:NLETSResponseData n2:key="YR"> | |||
<n2-yr:HitConfirmation> | |||
<n2-yr:QueryRequestActivity> | |||
<n2-yr:RequestCategoryCode>PO</n2-yr:RequestCategoryCode> | |||
<nc:Incident> | |||
<nc:ActivityIdentification> | |||
<nc:IdentificationID>CASE-1234</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>1957-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ActivityIdentification> | |||
<nc:ActivityStatus> | |||
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText> | |||
</nc:ActivityStatus> | |||
</nc:Incident> | |||
<scr:NCICRecordID>W123456789</scr:NCICRecordID> | |||
</n2-yr:QueryRequestActivity> | |||
<nc:Person> | |||
<nc:PersonBirthDate> | |||
<nc:Date>1920-01-26</nc:Date> | |||
</nc:PersonBirthDate> | |||
<nc:PersonName> | |||
<nc:PersonGivenName>MINNIE</nc:PersonGivenName> | |||
<nc:PersonSurName>MOUSE</nc:PersonSurName> | |||
<nc:PersonFullName>MOUSE, MINNIE</nc:PersonFullName> | |||
</nc:PersonName> | |||
<nc:PersonSexText>F</nc:PersonSexText> | |||
</nc:Person> | |||
<n2-yr:Confirmation> | |||
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText> | |||
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText> | |||
<n2-yr:ConfirmingAgency> | |||
<nc:OrganizationName>NLETS</nc:OrganizationName> | |||
<nc:OrganizationPrimaryContactInformation> | |||
<nc:ContactTelephoneNumber> | |||
<nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID> | |||
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID> | |||
</nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText> | |||
</nc:ContactTelephoneNumber> | |||
<nc:ContactEntity> | |||
<nc:EntityPerson> | |||
<nc:PersonName> | |||
<nc:PersonFullName>John D Smith</nc:PersonFullName> | |||
</nc:PersonName> | |||
</nc:EntityPerson> | |||
</nc:ContactEntity> | |||
</nc:OrganizationPrimaryContactInformation> | |||
</n2-yr:ConfirmingAgency> | |||
<n2-yr:Remarks>MISSING PERSON IS CONFIRMED PER SGT PLEASE CONTACT | |||
SUBJECT ALONE TO ASK IF SHE IS OKAY AND EVERYTHING IS GOOD AND IF | SUBJECT ALONE TO ASK IF SHE IS OKAY AND EVERYTHING IS GOOD AND IF | ||
SO THEN SHE CAN BE LET GO PLEASE PLACE LOCATE AND ADVISE INFORMATION THANK YOU</n2:Remarks> | SO THEN SHE CAN BE LET GO PLEASE PLACE LOCATE AND ADVISE INFORMATION THANK YOU</n2-yr:Remarks> | ||
</n2-yr:Confirmation> | |||
</n2-yr:HitConfirmation> | |||
</n2:NLETSResponseData> | </n2:NLETSResponseData> | ||
</n2:NLETS> | </n2:NLETS> | ||
Line 2,620: | Line 2,759: | ||
</table> | </table> | ||
<u>Example 13</u>: Hit Confirmation response for Stolen Article. | |||
== | <table border="1"> | ||
<tr> | |||
<th align="left"> | |||
<syntaxhighlight lang="xml"> | |||
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | |||
<n2:NLETSMessageHeader> | |||
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText> | |||
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID> | |||
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID> | |||
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText> | |||
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate> | |||
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime> | |||
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate> | |||
<nh2:MessageSendTime>08:55</nh2:MessageSendTime> | |||
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric> | |||
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric> | |||
</n2:NLETSMessageHeader> | |||
<n2:NLETSResponseData n2:key="YR"> | |||
<n2-yr:HitConfirmation> | |||
<n2-yr:QueryRequestActivity> | |||
<n2-yr:RequestCategoryCode>SA</n2-yr:RequestCategoryCode> | |||
<nc:Incident> | |||
<nc:ActivityIdentification> | |||
<nc:IdentificationID>CASE-1234</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>1957-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ActivityIdentification> | |||
<nc:ActivityStatus> | |||
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText> | |||
</nc:ActivityStatus> | |||
</nc:Incident> | |||
<scr:NCICRecordID>W123456789</scr:NCICRecordID> | |||
</n2-yr:QueryRequestActivity> | |||
<nc:Item> | |||
<nc:ItemSerialIdentification> | |||
<nc:IdentificationID>SER12345678</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>Item Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>2021-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ItemSerialIdentification> | |||
<nc:ItemBrandName>Item Brand</nc:ItemBrandName> | |||
<nc:ItemCategoryText>Item Category</nc:ItemCategoryText> | |||
<nc:ItemMakeName>Item Make</nc:ItemMakeName> | |||
<nc:ItemModelName>Item Model</nc:ItemModelName> | |||
<nc:ItemModelYearDate>2001</nc:ItemModelYearDate> | |||
</nc:Item> | |||
<n2-yr:Confirmation> | |||
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText> | |||
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText> | |||
<n2-yr:ConfirmingAgency> | |||
<nc:OrganizationName>NLETS</nc:OrganizationName> | |||
<nc:OrganizationPrimaryContactInformation> | |||
<nc:ContactTelephoneNumber> | |||
<nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID> | |||
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID> | |||
</nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText> | |||
</nc:ContactTelephoneNumber> | |||
<nc:ContactEntity> | |||
<nc:EntityPerson> | |||
<nc:PersonName> | |||
<nc:PersonFullName>John D Smith</nc:PersonFullName> | |||
</nc:PersonName> | |||
</nc:EntityPerson> | |||
</nc:ContactEntity> | |||
</nc:OrganizationPrimaryContactInformation> | |||
</n2-yr:ConfirmingAgency> | |||
<n2-yr:Remarks>Remarks</n2-yr:Remarks> | |||
</n2-yr:Confirmation> | |||
</n2-yr:HitConfirmation> | |||
</n2:NLETSResponseData> | |||
</n2:NLETS> | |||
</syntaxhighlight> | |||
</th> | |||
</tr> | |||
</table> | |||
<u>Example 14</u>: Hit Confirmation response for Stolen Boat. | |||
=== | <table border="1"> | ||
<tr> | |||
<th align="left"> | |||
<syntaxhighlight lang="xml"> | |||
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | |||
<n2:NLETSMessageHeader> | |||
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText> | |||
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID> | |||
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID> | |||
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText> | |||
</n2:NLETSMessageHeader> | |||
<n2:NLETSResponseData n2:key="YR"> | |||
<n2-yr:HitConfirmation> | |||
<n2-yr:QueryRequestActivity> | |||
<n2-yr:RequestCategoryCode>SB</n2-yr:RequestCategoryCode> | |||
<nc:Incident> | |||
<nc:ActivityIdentification> | |||
<nc:IdentificationID>CASE-1234</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>1957-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ActivityIdentification> | |||
<nc:ActivityStatus> | |||
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText> | |||
</nc:ActivityStatus> | |||
</nc:Incident> | |||
<scr:NCICRecordID>W123456789</scr:NCICRecordID> | |||
</n2-yr:QueryRequestActivity> | |||
<nc:Vessel> | |||
<nc:ItemSerialIdentification> | |||
<nc:IdentificationID>BHN123456789</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>Vessel Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>2021-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ItemSerialIdentification> | |||
<nc:ItemBrandName>Vessel Brand</nc:ItemBrandName> | |||
<nc:ItemCategoryText>Vessel Category</nc:ItemCategoryText> | |||
<nc:ItemMakeName>Vessel Make</nc:ItemMakeName> | |||
<nc:ItemModelName>Vessel Model</nc:ItemModelName> | |||
<nc:ItemModelYearDate>2001</nc:ItemModelYearDate> | |||
<nc:VesselHullIdentification> | |||
<nc:IdentificationID>HID12345678</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>VesselHull Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>2021-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:VesselHullIdentification> | |||
</nc:Vessel> | |||
<j:ItemRegistration> | |||
<j:RegistrationIdentification> | |||
<nc:IdentificationID>REG12345678</nc:IdentificationID> | |||
</j:RegistrationIdentification> | |||
</j:ItemRegistration> | |||
<n2-yr:Confirmation> | |||
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText> | |||
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText> | |||
<n2-yr:ConfirmingAgency> | |||
<nc:OrganizationName>NLETS</nc:OrganizationName> | |||
<nc:OrganizationPrimaryContactInformation> | |||
<nc:ContactTelephoneNumber> | |||
<nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID> | |||
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID> | |||
</nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText> | |||
</nc:ContactTelephoneNumber> | |||
<nc:ContactEntity> | |||
<nc:EntityPerson> | |||
<nc:PersonName> | |||
<nc:PersonFullName>John D Smith</nc:PersonFullName> | |||
</nc:PersonName> | |||
</nc:EntityPerson> | |||
</nc:ContactEntity> | |||
</nc:OrganizationPrimaryContactInformation> | |||
</n2-yr:ConfirmingAgency> | |||
<n2-yr:Remarks>Remarks</n2-yr:Remarks> | |||
</n2-yr:Confirmation> | |||
</n2-yr:HitConfirmation> | |||
</n2:NLETSResponseData> | |||
</n2:NLETS> | |||
</syntaxhighlight> | |||
</th> | |||
</tr> | |||
</table> | |||
<u>Example 15</u>: Hit Confirmation response for Stolen gun. | |||
<table border="1"> | <table border="1"> | ||
<tr> | <tr> | ||
<th align="center">Entry</th> | <th align="left"> | ||
<th align="center"># Char.</th> | <syntaxhighlight lang="xml"> | ||
<th align="center">Explanation</th> | <n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | ||
</tr> | <n2:NLETSMessageHeader> | ||
<tr> | <nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText> | ||
<th align="left">YQ.</th> | <nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID> | ||
<th align="center">2</th> | <nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID> | ||
<th align="left">Message type followed by a period.</th> | <nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText> | ||
</tr> | <nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate> | ||
<tr> | <nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime> | ||
<th align="left">Message Header</th> | <nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate> | ||
<th align="center">10-62</th> | <nh2:MessageSendTime>08:55</nh2:MessageSendTime> | ||
<th align="left">Standard input message header, may include | <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric> | ||
<br>control field and up to three 9 character ORIs.</th> | <nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric> | ||
</tr> | </n2:NLETSMessageHeader> | ||
<tr> | <n2:NLETSResponseData n2:key="YR"> | ||
<th align="left">TXT</th> | <n2-yr:HitConfirmation> | ||
<th align="center">3</th> | <n2-yr:QueryRequestActivity> | ||
<th align="left">Fixed filed prefix to beginning of message.</th> | <n2-yr:RequestCategoryCode>SG</n2-yr:RequestCategoryCode> | ||
</tr> | <nc:Incident> | ||
<tr> | <nc:ActivityIdentification> | ||
<th align="left">CR,LF,DEL</th> | <nc:IdentificationID>CASE-1234</nc:IdentificationID> | ||
<th align="center">3</th> | <nc:IdentificationJurisdiction> | ||
<th align="left">Control characters (optional).</th> | <nc:JurisdictionText>AZ</nc:JurisdictionText> | ||
</tr> | </nc:IdentificationJurisdiction> | ||
<tr> | <nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText> | ||
<th align="left">RTY/</th> | <nc:IdentificationExpirationDate> | ||
<th align="center">4</th> | <nc:Date>1957-08-13</nc:Date> | ||
</nc:IdentificationExpirationDate> | |||
<th align="left">Prefix to identify request type.</th> | </nc:ActivityIdentification> | ||
</tr> | <nc:ActivityStatus> | ||
<tr> | <nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText> | ||
<th align="left">Request type</th> | </nc:ActivityStatus> | ||
<th align="center">2</th> | </nc:Incident> | ||
<th align="left">Request type: | <scr:NCICRecordID>W123456789</scr:NCICRecordID> | ||
<br><ul><li>SV = stolen/felony vehicle | </n2-yr:QueryRequestActivity> | ||
<br><li>WP = wanted person | <j:Firearm> | ||
<nc:ItemSerialIdentification> | |||
<nc:IdentificationID>SER12345678</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>GUN Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>2021-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ItemSerialIdentification> | |||
<nc:ItemBrandName>Ruger</nc:ItemBrandName> | |||
<nc:ItemCategoryText>Semi-Automatic pistol</nc:ItemCategoryText> | |||
<nc:ItemMakeName>Ruger</nc:ItemMakeName> | |||
<nc:ItemModelName>Ruger-57</nc:ItemModelName> | |||
<nc:ItemModelYearDate>2001</nc:ItemModelYearDate> | |||
<j:FirearmBoreSizeText>50</j:FirearmBoreSizeText> | |||
</j:Firearm> | |||
<n2-yr:Confirmation> | |||
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText> | |||
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText> | |||
<n2-yr:ConfirmingAgency> | |||
<nc:OrganizationName>NLETS</nc:OrganizationName> | |||
<nc:OrganizationPrimaryContactInformation> | |||
<nc:ContactTelephoneNumber> | |||
<nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID> | |||
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID> | |||
</nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText> | |||
</nc:ContactTelephoneNumber> | |||
<nc:ContactEntity> | |||
<nc:EntityPerson> | |||
<nc:PersonName> | |||
<nc:PersonFullName>John D Smith</nc:PersonFullName> | |||
</nc:PersonName> | |||
</nc:EntityPerson> | |||
</nc:ContactEntity> | |||
</nc:OrganizationPrimaryContactInformation> | |||
</n2-yr:ConfirmingAgency> | |||
<n2-yr:Remarks>Remarks</n2-yr:Remarks> | |||
</n2-yr:Confirmation> | |||
</n2-yr:HitConfirmation> | |||
</n2:NLETSResponseData> | |||
</n2:NLETS> | |||
</syntaxhighlight> | |||
</th> | |||
</tr> | |||
</table> | |||
<u>Example 16</u>: Hit Confirmation response for Stolen License Plate. | |||
<table border="1"> | |||
<tr> | |||
<th align="left"> | |||
<syntaxhighlight lang="xml"> | |||
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | |||
<n2:NLETSMessageHeader> | |||
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText> | |||
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID> | |||
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID> | |||
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText> | |||
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate> | |||
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime> | |||
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate> | |||
<nh2:MessageSendTime>08:55</nh2:MessageSendTime> | |||
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric> | |||
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric> | |||
</n2:NLETSMessageHeader> | |||
<n2:NLETSResponseData n2:key="YR"> | |||
<n2-yr:HitConfirmation> | |||
<n2-yr:QueryRequestActivity> | |||
<n2-yr:RequestCategoryCode>SL</n2-yr:RequestCategoryCode> | |||
<nc:Incident> | |||
<nc:ActivityIdentification> | |||
<nc:IdentificationID>CASE-1234</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>1957-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ActivityIdentification> | |||
<nc:ActivityStatus> | |||
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText> | |||
</nc:ActivityStatus> | |||
</nc:Incident> | |||
<scr:NCICRecordID>W123456789</scr:NCICRecordID> | |||
</n2-yr:QueryRequestActivity> | |||
<j:ConveyanceRegistrationPlateIdentification> | |||
<nc:IdentificationID>ABC123</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>PC</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>2021-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</j:ConveyanceRegistrationPlateIdentification> | |||
<n2-yr:Confirmation> | |||
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText> | |||
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText> | |||
<n2-yr:ConfirmingAgency> | |||
<nc:OrganizationName>NLETS</nc:OrganizationName> | |||
<nc:OrganizationPrimaryContactInformation> | |||
<nc:ContactTelephoneNumber> | |||
<nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID> | |||
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID> | |||
</nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText> | |||
</nc:ContactTelephoneNumber> | |||
<nc:ContactEntity> | |||
<nc:EntityPerson> | |||
<nc:PersonName> | |||
<nc:PersonFullName>John D Smith</nc:PersonFullName> | |||
</nc:PersonName> | |||
</nc:EntityPerson> | |||
</nc:ContactEntity> | |||
</nc:OrganizationPrimaryContactInformation> | |||
</n2-yr:ConfirmingAgency> | |||
<n2-yr:Remarks>Remarks</n2-yr:Remarks> | |||
</n2-yr:Confirmation> | |||
</n2-yr:HitConfirmation> | |||
</n2:NLETSResponseData> | |||
</n2:NLETS> | |||
</syntaxhighlight> | |||
</th> | |||
</tr> | |||
</table> | |||
<u>Example 17</u>: Hit Confirmation response for Stolen Part. | |||
<table border="1"> | |||
<tr> | |||
<th align="left"> | |||
<syntaxhighlight lang="xml"> | |||
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | |||
<n2:NLETSMessageHeader> | |||
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText> | |||
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID> | |||
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID> | |||
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText> | |||
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate> | |||
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime> | |||
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate> | |||
<nh2:MessageSendTime>08:55</nh2:MessageSendTime> | |||
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric> | |||
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric> | |||
</n2:NLETSMessageHeader> | |||
<n2:NLETSResponseData n2:key="YR"> | |||
<n2-yr:HitConfirmation> | |||
<n2-yr:QueryRequestActivity> | |||
<n2-yr:RequestCategoryCode>SP</n2-yr:RequestCategoryCode> | |||
<nc:Incident> | |||
<nc:ActivityIdentification> | |||
<nc:IdentificationID>CASE-1234</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>1957-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ActivityIdentification> | |||
<nc:ActivityStatus> | |||
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText> | |||
</nc:ActivityStatus> | |||
</nc:Incident> | |||
<scr:NCICRecordID>W123456789</scr:NCICRecordID> | |||
</n2-yr:QueryRequestActivity> | |||
<j:ConveyancePart> | |||
<nc:ItemSerialIdentification> | |||
<nc:IdentificationID>PART123456789</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>Part Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>2021-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ItemSerialIdentification> | |||
<nc:ItemBrandName>Item Brand Name</nc:ItemBrandName> | |||
<nc:ItemCategoryText>Item Category Text</nc:ItemCategoryText> | |||
<nc:ItemMakeName>Item Make Name</nc:ItemMakeName> | |||
<nc:ItemModelName>Item Model Name</nc:ItemModelName> | |||
<nc:ItemModelYearDate>2001</nc:ItemModelYearDate> | |||
<j:ConveyancePartID>Part ID</j:ConveyancePartID> | |||
<j:ConveyancePartBrandName>Part Brand Name</j:ConveyancePartBrandName> | |||
<j:ConveyancePartCategoryText>Part Category</j:ConveyancePartCategoryText> | |||
</j:ConveyancePart> | |||
<n2-yr:Confirmation> | |||
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText> | |||
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText> | |||
<n2-yr:ConfirmingAgency> | |||
<nc:OrganizationName>NLETS</nc:OrganizationName> | |||
<nc:OrganizationPrimaryContactInformation> | |||
<nc:ContactTelephoneNumber> | |||
<nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID> | |||
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID> | |||
</nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText> | |||
</nc:ContactTelephoneNumber> | |||
<nc:ContactEntity> | |||
<nc:EntityPerson> | |||
<nc:PersonName> | |||
<nc:PersonFullName>John D Smith</nc:PersonFullName> | |||
</nc:PersonName> | |||
</nc:EntityPerson> | |||
</nc:ContactEntity> | |||
</nc:OrganizationPrimaryContactInformation> | |||
</n2-yr:ConfirmingAgency> | |||
<n2-yr:Remarks>Remarks</n2-yr:Remarks> | |||
</n2-yr:Confirmation> | |||
</n2-yr:HitConfirmation> | |||
</n2:NLETSResponseData> | |||
</n2:NLETS> | |||
</syntaxhighlight> | |||
</th> | |||
</tr> | |||
</table> | |||
<u>Example 18</u>: Hit Confirmation response for Stolen Security. | |||
<table border="1"> | |||
<tr> | |||
<th align="left"> | |||
<syntaxhighlight lang="xml"> | |||
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | |||
<n2:NLETSMessageHeader> | |||
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText> | |||
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID> | |||
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID> | |||
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText> | |||
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate> | |||
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime> | |||
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate> | |||
<nh2:MessageSendTime>08:55</nh2:MessageSendTime> | |||
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric> | |||
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric> | |||
</n2:NLETSMessageHeader> | |||
<n2:NLETSResponseData n2:key="YR"> | |||
<n2-yr:HitConfirmation> | |||
<n2-yr:QueryRequestActivity> | |||
<n2-yr:RequestCategoryCode>SS</n2-yr:RequestCategoryCode> | |||
<nc:Incident> | |||
<nc:ActivityIdentification> | |||
<nc:IdentificationID>CASE-1234</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>1957-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ActivityIdentification> | |||
<nc:ActivityStatus> | |||
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText> | |||
</nc:ActivityStatus> | |||
</nc:Incident> | |||
<scr:NCICRecordID>W123456789</scr:NCICRecordID> | |||
</n2-yr:QueryRequestActivity> | |||
<nc:Securities> | |||
<nc:ItemSerialIdentification> | |||
<nc:IdentificationID>SER12345678</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>Securities Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>2021-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ItemSerialIdentification> | |||
<nc:ItemBrandName>Securities Brand</nc:ItemBrandName> | |||
<nc:ItemCategoryText>Securities Category</nc:ItemCategoryText> | |||
<nc:ItemMakeName>Securities Make</nc:ItemMakeName> | |||
<nc:ItemModelName>Securities Model</nc:ItemModelName> | |||
<nc:ItemModelYearDate>2001</nc:ItemModelYearDate> | |||
</nc:Securities> | |||
<n2-yr:Confirmation> | |||
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText> | |||
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText> | |||
<n2-yr:ConfirmingAgency> | |||
<nc:OrganizationName>NLETS</nc:OrganizationName> | |||
<nc:OrganizationPrimaryContactInformation> | |||
<nc:ContactTelephoneNumber> | |||
<nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID> | |||
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID> | |||
</nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText> | |||
</nc:ContactTelephoneNumber> | |||
<nc:ContactEntity> | |||
<nc:EntityPerson> | |||
<nc:PersonName> | |||
<nc:PersonFullName>John D Smith</nc:PersonFullName> | |||
</nc:PersonName> | |||
</nc:EntityPerson> | |||
</nc:ContactEntity> | |||
</nc:OrganizationPrimaryContactInformation> | |||
</n2-yr:ConfirmingAgency> | |||
<n2-yr:Remarks>Remarks</n2-yr:Remarks> | |||
</n2-yr:Confirmation> | |||
</n2-yr:HitConfirmation> | |||
</n2:NLETSResponseData> | |||
</n2:NLETS> | |||
</syntaxhighlight> | |||
</th> | |||
</tr> | |||
</table> | |||
<u>Example 19</u>: Hit Confirmation response for Stolen/Felony Vehicle. | |||
<table border="1"> | |||
<tr> | |||
<th align="left"> | |||
<syntaxhighlight lang="xml"> | |||
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | |||
<n2:NLETSMessageHeader> | |||
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText> | |||
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID> | |||
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID> | |||
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText> | |||
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate> | |||
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime> | |||
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate> | |||
<nh2:MessageSendTime>08:55</nh2:MessageSendTime> | |||
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric> | |||
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric> | |||
</n2:NLETSMessageHeader> | |||
<n2:NLETSResponseData n2:key="YR"> | |||
<n2-yr:HitConfirmation> | |||
<n2-yr:QueryRequestActivity> | |||
<n2-yr:RequestCategoryCode>SV</n2-yr:RequestCategoryCode> | |||
<nc:Incident> | |||
<nc:ActivityIdentification> | |||
<nc:IdentificationID>CASE-1234</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>1957-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ActivityIdentification> | |||
<nc:ActivityStatus> | |||
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText> | |||
</nc:ActivityStatus> | |||
</nc:Incident> | |||
<scr:NCICRecordID>W123456789</scr:NCICRecordID> | |||
</n2-yr:QueryRequestActivity> | |||
<nc:Vehicle> | |||
<nc:ItemSerialIdentification> | |||
<nc:IdentificationID>ABC1234</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>Item Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>2021-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ItemSerialIdentification> | |||
<nc:ItemBrandName>BMW MANUFACTURER CORPORATION / BMW NORTH AMERICA</nc:ItemBrandName> | |||
<nc:ItemCategoryText>PC</nc:ItemCategoryText> | |||
<nc:ItemMakeName>BMW</nc:ItemMakeName> | |||
<nc:ItemModelName>X3</nc:ItemModelName> | |||
<nc:ItemModelYearDate>2011</nc:ItemModelYearDate> | |||
<nc:VehicleIdentification> | |||
<nc:IdentificationID>5UXWX7C5XMN0191BA</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>VIN Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>2021-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:VehicleIdentification> | |||
</nc:Vehicle> | |||
<n2-yr:Confirmation> | |||
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText> | |||
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText> | |||
<n2-yr:ConfirmingAgency> | |||
<nc:OrganizationName>NLETS</nc:OrganizationName> | |||
<nc:OrganizationPrimaryContactInformation> | |||
<nc:ContactTelephoneNumber> | |||
<nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID> | |||
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID> | |||
</nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText> | |||
</nc:ContactTelephoneNumber> | |||
<nc:ContactEntity> | |||
<nc:EntityPerson> | |||
<nc:PersonName> | |||
<nc:PersonFullName>John D Smith</nc:PersonFullName> | |||
</nc:PersonName> | |||
</nc:EntityPerson> | |||
</nc:ContactEntity> | |||
</nc:OrganizationPrimaryContactInformation> | |||
</n2-yr:ConfirmingAgency> | |||
<n2-yr:Remarks>Remarks</n2-yr:Remarks> | |||
</n2-yr:Confirmation> | |||
</n2-yr:HitConfirmation> | |||
</n2:NLETSResponseData> | |||
</n2:NLETS> | |||
</syntaxhighlight> | |||
</th> | |||
</tr> | |||
</table> | |||
<u>Example 20</u>: Hit Confirmation response for Wanted Person. | |||
<table border="1"> | |||
<tr> | |||
<th align="left"> | |||
<syntaxhighlight lang="xml"> | |||
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | |||
<n2:NLETSMessageHeader> | |||
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText> | |||
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID> | |||
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID> | |||
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText> | |||
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate> | |||
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime> | |||
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate> | |||
<nh2:MessageSendTime>08:55</nh2:MessageSendTime> | |||
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric> | |||
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric> | |||
</n2:NLETSMessageHeader> | |||
<n2:NLETSResponseData n2:key="YR"> | |||
<n2-yr:HitConfirmation> | |||
<n2-yr:QueryRequestActivity> | |||
<n2-yr:RequestCategoryCode>WP</n2-yr:RequestCategoryCode> | |||
<nc:Incident> | |||
<nc:ActivityIdentification> | |||
<nc:IdentificationID>CASE-1234</nc:IdentificationID> | |||
<nc:IdentificationJurisdiction> | |||
<nc:JurisdictionText>AZ</nc:JurisdictionText> | |||
</nc:IdentificationJurisdiction> | |||
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText> | |||
<nc:IdentificationExpirationDate> | |||
<nc:Date>1957-08-13</nc:Date> | |||
</nc:IdentificationExpirationDate> | |||
</nc:ActivityIdentification> | |||
<nc:ActivityStatus> | |||
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText> | |||
</nc:ActivityStatus> | |||
</nc:Incident> | |||
<scr:NCICRecordID>W123456789</scr:NCICRecordID> | |||
</n2-yr:QueryRequestActivity> | |||
<nc:Person> | |||
<nc:PersonBirthDate> | |||
<nc:Date>1981-08-07</nc:Date> | |||
</nc:PersonBirthDate> | |||
<nc:PersonName> | |||
<nc:PersonGivenName>TEST</nc:PersonGivenName> | |||
<nc:PersonMiddleName>MIDDLE</nc:PersonMiddleName> | |||
<nc:PersonSurName>NAME</nc:PersonSurName> | |||
<nc:PersonFullName>TEST MIDDLE NAME</nc:PersonFullName> | |||
</nc:PersonName> | |||
<nc:PersonSexText>M</nc:PersonSexText> | |||
</nc:Person> | |||
<n2-yr:Confirmation> | |||
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText> | |||
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText> | |||
<n2-yr:ConfirmingAgency> | |||
<nc:OrganizationName>NLETS</nc:OrganizationName> | |||
<nc:OrganizationPrimaryContactInformation> | |||
<nc:ContactTelephoneNumber> | |||
<nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID> | |||
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID> | |||
</nc:FullTelephoneNumber> | |||
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText> | |||
</nc:ContactTelephoneNumber> | |||
<nc:ContactEntity> | |||
<nc:EntityPerson> | |||
<nc:PersonName> | |||
<nc:PersonFullName>John D Smith</nc:PersonFullName> | |||
</nc:PersonName> | |||
</nc:EntityPerson> | |||
</nc:ContactEntity> | |||
</nc:OrganizationPrimaryContactInformation> | |||
</n2-yr:ConfirmingAgency> | |||
<n2-yr:Remarks>Remarks</n2-yr:Remarks> | |||
</n2-yr:Confirmation> | |||
</n2-yr:HitConfirmation> | |||
</n2:NLETSResponseData> | |||
</n2:NLETS> | |||
</syntaxhighlight> | |||
</th> | |||
</tr> | |||
</table> | |||
[[#top|Top]] | |||
==Legacy (DEPRECATED)== | |||
===Hit Confirmation Legacy Specifications=== | |||
This section provides Legacy formats and examples for Hit Confirmation queries and responses (YQ/YR). | |||
The format for a YQ message is described below. Optional fields have been noted. | |||
Note that NCIC formats for data fields are used whenever possible. | |||
====Query Formats==== | |||
<table border="1"> | |||
<tr> | |||
<th align="center">Entry</th> | |||
<th align="center"># Char.</th> | |||
<th align="center">Explanation</th> | |||
</tr> | |||
<tr> | |||
<th align="left">YQ.</th> | |||
<th align="center">2</th> | |||
<th align="left">Message type followed by a period.</th> | |||
</tr> | |||
<tr> | |||
<th align="left">Message Header</th> | |||
<th align="center">10-62</th> | |||
<th align="left">Standard input message header, may include | |||
<br>control field and up to three 9 character ORIs.</th> | |||
</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">RTY/</th> | |||
<th align="center">4</th> | |||
<th align="left">Prefix to identify request type.</th> | |||
</tr> | |||
<tr> | |||
<th align="left">Request type</th> | |||
<th align="center">2</th> | |||
<th align="left">Request type: | |||
<br><ul><li>SV = stolen/felony vehicle | |||
<br><li>WP = wanted person | |||
<br><li>PO = protection order | <br><li>PO = protection order | ||
<br><li>MP = missing person | <br><li>MP = missing person | ||
Line 2,793: | Line 3,655: | ||
<th align="left">VYR/ (optional)</th> | <th align="left">VYR/ (optional)</th> | ||
<th align="center">4</th> | <th align="center">4</th> | ||
<th align="left">Prefix to identify vehicle | <th align="left">Prefix to identify vehicle year.</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 3,526: | Line 4,388: | ||
== Downloads == | == Downloads == | ||
[https://schema.nlets.org/Wiki/Schemas/YQ.ZIP Download YQ Schema] | {| class="wikitable" | ||
|- | |||
[https://schema.nlets.org/Wiki/Stylesheets/YQ.xslt Download YQ Stylesheet] | ! File !! Last Updated | ||
|- | |||
[https://schema.nlets.org/Wiki/Stylesheets/YQ_caveats.xslt Download YQ Stylesheet with | | [https://schema.nlets.org/Wiki/Schemas/YQ.ZIP Download YQ Schema] || 10/8/2020 | ||
|- | |||
[https://schema.nlets.org/Wiki/Schemas/YR.ZIP Download YR Schema] | | [https://schema.nlets.org/Wiki/Stylesheets/YQ.xslt Download YQ Stylesheet] || 4/6/2023 | ||
|- | |||
[https://schema.nlets.org/Wiki/Stylesheets/YR.xslt Download YR Stylesheet] | | [https://schema.nlets.org/Wiki/Stylesheets/YQ_caveats.xslt Download YQ Stylesheet with Caveats] || 7/11/2023 | ||
|- | |||
| [https://schema.nlets.org/Wiki/Schemas/YR.ZIP Download YR Schema] || N/A | |||
|- | |||
| [https://schema.nlets.org/Wiki/Stylesheets/YR.xslt Download YR Stylesheet] || 3/09/2023 | |||
|} | |||
[[#top|Top]] | [[#top|Top]] |
Latest revision as of 17:57, 17 November 2023
Hit Confirmation Transactions (YQ/YR)
This section provides information for implementation of the hit confirmation policy approved by the NCIC Advisory Policy Board. Nlets use is an integral part of this policy.
Users may send a request for a hit confirmation on an NCIC record (YQ) to a state via Nlets. The destination agency will return a hit confirmation response (YR). Nlets will edit the messages before forwarding the request and response to the destination state(s).
Although a hit confirmation request relies primarily on the cooperation of the entering agency, the agency making the request also should provide sufficient information, in the proper format, to ensure an efficient exchange of information.
When an agency receives a hit, and an individual is being detained, or piece of property seized, confirmation with the entering agency is necessary to ensure the validity of the record prior to taking action. The entering agency, or a secondary agency acting on their behalf, must be available 24-hours a day, 7 days a week for confirmation.

Requirements for Hit Confirmation Requests
- Requests for Hit Confirmation (YQs) may be addressed to up to three 9-character ORIs.
- The decision for establishing priorities is ALWAYS made by the agency requesting confirmation and is a required field for all hit confirmations.
- Do not include sets of data elements that do not pertain to the type of hit confirmation request (YQ). For example, if you are attempting to confirm a wanted person record, you should include only the required data elements plus name (NAM), date of birth (DOB), and sex (SEX) (optional). If you include other data elements such as license plate (LIC) or vehicle identification number (VIN) for a wanted person type record, the message will be rejected by Nlets.
- Blank data fields should not be sent to Nlets. Both the field and the prefix MUST be eliminated.
- Use the vehicle identification number (or VIN/ prefix) to identify an owner applied number on a vehicle.
<nc:IdentificationID></nc:IdentificationID>
- When sending a request for hit confirmation (YQ) to Canada insert "NONE" in the NCIC field (e.g., or NIC/NONE.)
<scr:NCICRecordID>NONE</scr:NCICRecordID>
Priority
There are two levels of priority provided when requesting a hit confirmation over Nlets; urgent and routine. The response time and basis for assignment are described below.
Priority Level: | Priority Code: | Response Time: | Basis for Assigning Priority: |
---|---|---|---|
Urgent | U | Within 10 minutes |
In those instances where the hit is the only basis for detaining
|
Routine | R | Within 1 hour |
Generally, this will be used when the person or property is being
|
In both cases a response is defined as either
- confirming the record or
- providing a time when the record will be confirmed.
The agency making the request should provide as much information, in the proper format, to ensure an efficient exchange of information. This includes using the priority designation appropriately.
Agencies are encouraged to use the lower priority when an immediate response is not necessary. It will make the entire process more efficient and responsive.
Notes
At the beginning of the request for a hit confirmation message (YQ) and based on the request number (RNO/), Nlets will insert this phrase:
****HIT CONFIRMATION REQUEST - RNO VALUE**** |
---|
RNO is "1" | "FIRST" request will be sent. |
The message will only be addressed to the given destination. |
---|---|---|
RNO is "2" | "FIRST" will be replaced by "SECOND" |
The message will be addressed to both the given destination as
|
RNO is "3" | "FIRST" will be replaced by "THIRD" |
The message will be addressed to the given destination, the
|
- The request type field (RTY) identifies the type of request that was made.
- The line in the inquiry identifying the record's unique fields (license plate, name, serial number, etc.) will vary depending on the type of record being confirmed. This is identified in the request type field (RTY).
- Nlets has inserted several phrases to make the hit confirmation readable. These include indication of first notice, priority, and the type of record being requested for confirmation (e.g. MISSING PERSON).
- Nlets will translate the priority field (or PRI/) to a plain English sentence, such as "URGENT! - RESPOND WITHIN 10 MINUTES". Only the selection made will be displayed. The sender will ALWAYS determine the priority.
<n2:RequestPriorityCode>
- For a second or third request, Nlets will send the original YQ to multiple destinations and will add an XML element <n2:Recipients> as a child to <n2:NLETSInquiryData> that contains all ORIs to which Nlets has sent the YQ message. This element is informational only and included as a "value add" only. For a second request, the recipients will be the destination ORI of the original YQ message and the ORI ssHITC000, where ss is the two-letter state code of the original destination ORI. For a third request, recipients will additionally include the ORI DCFBIWA00. Note that each of the YQ messages is identical, except the destination ORI, and each one includes the same <n2:Recipients> element. For example, in the code snippet below for a third request, the <n2:Recipients> element indicates that Nlets has sent three YQ messages, one to "ZZ0101010", one to "ZZHITC000", and one to "DCFBIWA00", each of which would include and identical <n2:Recipients> element:
<n2:NLETSInquiryData n2:key="YQ"> <!-- All other elements here --> <n2:Recipients> <!-- Nlets addition to original message --> <j:OrganizationORIIdentification> <nc:IdentificationID>ZZ0101010</nc:IdentificationID> </j:OrganizationORIIdentification> <j:OrganizationORIIdentification> <nc:IdentificationID>ZZHITC000</nc:IdentificationID> </j:OrganizationORIIdentification> <j:OrganizationORIIdentification> <nc:IdentificationID>DCFBIWA00</nc:IdentificationID> </j:OrganizationORIIdentification> </n2:Recipients> </n2:NLETSInquiryData>
- Nlets will edit all requests for hit confirmation (YQs) for required data elements, field length and allowable data within the fields. Editing will be similar to editing on Vehicle Registration queries (RQs) and Driver Registration queries (DQs).
Field Requirements
The table that follows describes field requirements for Hit Confirmation transactions.
XML Tag: | Legacy
Prefix: |
Field
Size: |
Data Requirements: | Translation: |
---|---|---|---|---|
<nc:QueryRequestActivity>
<n2:RequestCategoryCode>XX</n2:RequestCategoryCode>
</nc:QueryRequestActivity>
|
RTY/SV
|
2 | 2-character code |
Request type:
|
<nc:QueryRequestActivity>
<n2:QueryRequestSequenceNumber>X</n2:QueryRequestSequenceNumber>
</nc:QueryRequestActivity>
|
RNO/ | 1 | Must be 1, 2 or 3 | Request number |
<nc:QueryRequestActivity>
<n2:RequestPriorityCode>X</n2:RequestPriorityCode>
</nc:QueryRequestActivity>
|
PRI/ | 1 | Must be U (urgent)
or R (routine) |
Priority destination |
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE123</nc:IdentificationID>
</nc:ActivityIdentification>
</nc:Incident>
|
OCA/ | 1-20 | Alphanumeric | Agency case number |
<nc:QueryRequestActivity>
<scr:NCICRecordID>NCIC123</scr:NCICRecordID>
</nc:QueryRequestActivity>
|
NIC/ | 1-10 | See NCIC Manual | NCIC number. (Insert "NONE" in
this field if YQ is going to Canada). |
AND ONE OF THE SETS OF DATA ELEMENTS BELOW: | ||||
<nc:Vehicle>
<nc:ConveyanceRegistrationPlateIdentification>
<nc:IdentificationID>ABC123</nc:IdentificationID>
</nc:ConveyanceRegistrationPlateIdentification>
<nc:Vehicle>
|
LIC/ | 1-10 | Alphanumeric | License plate number |
<nc:Vehicle>
<nc:ConveyanceRegistrationPlateIdentification>
<nc:IdentificationJurisdictionText>XX</nc:IdentificationJurisdictionText>
</nc:ConveyanceRegistrationPlateIdentification>
<nc:Vehicle>
|
LIS/ | 2 | 2-character designation |
License state
|
<nc:Vehicle>
<nc:ConveyanceRegistrationPlateIdentification>
<nc:IdentificationExpirationDate>
<nc:Year>ccyy</nc:Year>
</nc:IdentificationExpirationDate>
</nc:ConveyanceRegistrationPlateIdentification>
<nc:Vehicle>
|
LIY/ | 4 | 4 numeric digits; ccyy | License year (optional) |
<nc:Vehicle>
<nc:ConveyanceRegistrationPlateIdentification>
<nc:IdentificationCategoryText>XX</nc:IdentificationCategoryText>
</nc:ConveyanceRegistrationPlateIdentification>
<nc:Vehicle>
|
LIT/ | 2 | 2-character designation for
type of license |
License type
|
OR | ||||
<nc:Vehicle>
<nc:VehicleIdentification>
<nc:IdentificationID>XXXXXXX</nc:IdentificationID>
</nc:VehicleIdentification>
</nc:Vehicle>
|
VIN/ | 1-20 | Alphanumeric | Vehicle ID # |
<nc:Vehicle>
<nc:ItemModelYearDate>CCYY</nc:ItemModelYearDate>
</nc:Vehicle>
|
VYR/ | 2-4 | 2-4 numeric digits designating
year of current license |
Vehicle year (optional) |
<nc:Vehicle>
<nc:VehicleMakeCode>XXXX</nc:VehicleMakeCode>
<nc:Vehicle>
|
VMA/ | 2-4 | See NCIC Manual | Vehicle make (optional) |
OR | ||||
<nc:Person>
<nc:PersonName>
<nc:PersonFullName>Last, First</nc:PersonFullName>
<nc:PersonName>
</nc:Person>
|
NAM/ | 1-30 | Alpha Characters | Name
(last name, first name middle) |
<nc:Person>
<nc:PersonBirthDate>
<nc:Date>CCYYMMDD</nc:Date>
</nc:PersonBirthDate>
</nc:Person>
|
DOB/ | 6-10 | ccyymmdd | Date of birth |
<nc:Person>
<nc:PersonSexCode>U</nc:PersonSexCode>
</nc:Person>
|
SEX/ | 1 | See NCIC Manual | Sex |
OR | ||||
<nc:Firearm>
<nc:ItemSerialIdentification>
<nc:IdentificationID>GUN123</nc:IdentificationID>
<nc:ItemSerialIdentification>
</nc:Firearm>
|
SER/ | 1-20 | Alphanumeric | Gun serial number |
<nc:Firearm>
<nc:FirearmCaliberCode>380</nc:FirearmCaliberCode>
</nc:Firearm>
|
CAL/ | 1-4 | See NCIC Manual | Gun caliber |
<nc:Firearm>
<nc:FirearmMakeCode>String</nc:FirearmMakeCode>
<nc:Firearm>
|
MAK/ | 1-23 | See NCIC Manual | Gun make |
<nc:Firearm>
<nc:ItemModelName>String</nc:ItemModelName>
<nc:Firearm>
|
MOD/ | 1-20 | See NCIC Manual | Gun model (optional) |
OR | ||||
<nc:TangibleItem>
<nc:ItemCategoryText>Crossbow</nc:ItemCategoryText>
</nc:TangibleItem>
|
TYP/ | 1-7 | See NCIC Manual | Article type |
<nc:TangibleItem>
<nc:ItemSerialIdentification>
<nc:IdentificationID>Article123</nc:IdentificationID>
</nc:ItemSerialIdentification>
</nc:TangibleItem>
|
SER/ | 1-20 | Alphanumeric | Serial number |
<nc:TangibleItem>
<nc:ItemBrandName>String</nc:ItemBrandName>
<nc:TangibleItem>
|
BRA/ | 1-6 | See NCIC Manual | Article brand |
OR | ||||
<n2:Securities>
<nc:ItemCategoryText>XX</nc:ItemCategoryText>
</n2:Securities>
|
TYP/ | 1-7 | See NCIC Manual | Security type |
<n2:Securities>
<nc:ItemSerialIdentification>
<nc:IdentificationID>XXXX<nc:IdentificationID>
<nc:ItemSerialIdentification>
<n2:Securities>
|
SER/ | 1-20 | See NCIC Manual | Serial number |
<n2:Securities>
<nc:SecuritiesDenominationText>XXXX</nc:SecuritiesDenominationText>
</n2:Securities>
|
DEN/ | 1-9 | See NCIC Manual | Denomination |
OR | ||||
<nc:Vessel>
<nc:VesselRegistrationIdentification>
<nc:IdentificationID>XXXX</nc:IdentificationID>
</nc:VesselRegistrationIdentification>
<nc:Vessel>
|
REG/ | 1-8 | Alphanumeric | Boat registration number |
<nc:Vessel>
<nc:ItemMakeName>XXXX</nc:ItemMakeName>
</nc:Vessel>
|
BMA/ | 1-24 | See NCIC Manual | Boat make (optional) |
OR | ||||
<nc:Vessel>
<nc:VesselHullIdentification>
<nc:IdentificationID>XXXX</nc:IdentificationID>
</nc:VesselHullIdentification>
</nc:Vessel>
|
BHN/ | 1-18 | See NCIC Manual | Boat hull number |
<nc:Vessel>
<nc:ItemMakeName>XXXX</nc:ItemMakeName>
</nc:Vessel>
|
BMA/ | 1-24 | See NCIC Manual | Boat make (optional) |
OR | ||||
<nc:ConveyancePart>
<nc:ItemSerialIdentification>
<nc:IdentificationID>XXXX</nc:IdentificationID>
</nc:ItemSerialIdentification>
</nc:ConveyancePart>
|
SER/ | 1-20 | See NCIC Manual | Stolen part serial number |
<nc:ConveyancePart>
<nc:ConveyancePartBrandName>XXXX</nc:ConveyancePartBrandName>
</nc:ConveyancePart>
|
BRA/ | 1-6 | See NCIC Manual | Brand name (optional) |
<nc:ConveyancePart>
<nc:ConveyancePartCategoryText></nc:ConveyancePartCategoryText>
</nc:ConveyancePart>
|
CAT/ | 1-2 | See NCIC Manual | Category (optional) |
AND | ||||
<nc:OrganizationPrincipalOfficial>
<nc:PersonName>
<nc:PersonFullName>Requestor, I.M.</nc:PersonFullName>
<nc:PersonName>
<nc:OrganizationPrincipalOfficial>
|
RNA/ | 1-30 | See NCIC Manual | Name of requester |
<n2:QueryRequestActivity>
<n2:RequestingAgency>
<nc:OrganizationName>XXXX</nc:OrganizationName>
</n2:RequestingAgency>
</n2:QueryRequestActivity>
|
RAG/ | 1-60 | See NCIC Manual | Requesting agency name |
<n2:QueryRequestActivity>
<n2:RequestingAgency>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>XXXXX</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
</nc:OrganizationPrimaryContactInformation>
</n2:RequestingAgency>
</n2:QueryRequestActivity>
|
PHO | 1-10 | Numeric | Phone number (optional) |
<n2:QueryRequestActivity>
<n2:RequestingAgency>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneSuffixID>XXXXX</nc:TelephoneSuffixID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
</nc:OrganizationPrimaryContactInformation>
</n2:RequestingAgency>
</n2:QueryRequestActivity>
|
EXT/ | 1-4 | Numeric | Phone extension number
(optional) |
<n2:QueryRequestActivity>
<n2:RequestingAgency>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>XXXXX</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
</nc:OrganizationPrimaryContactInformation>
</n2:RequestingAgency>
</n2:QueryRequestActivity>
|
FAX/ | 1-10 | Numeric | Fax number (optional) |
<j:Warrant>
<j:CourtOrderIssuingCourt>
<nc:OrganizationIdentification>
<nc:IdentificationID>XXXX</nc:IdentificationID>
</nc:OrganizationIdentification>
</j:CourtOrderIssuingCourt>
</j:Warrant>
|
CTO/ | 20 | Free text | Court order number (optional) |
<j:Warrant>
<nc:ActivitytiIdentification>
<nc:IdentificationID>XXXX</nc:IdentificationID>
</nc:ActivitytiIdentification>
</j:Warrant>
|
WNO/ | 20 | Free text | Warrant number (optional) |
<n2:QueryRequestActivity>
<n2:Remarks>XXXX</n2:Remarks>
</n2:QueryRequestActivity>
|
REM/ | 1-500 | Free text | Remarks field (optional) |
Hit Confirmation Responses (YR)
NCIC formats for data fields are used whenever possible.
Nlets will insert this phrase at the beginning of the response (YR):
****HIT CONFIRMATION RESPONSE**** |
---|
Nlets will translate the confirmation status field ("CON/").
The four permissible codes are:
Code | Confirmation Status Fields |
---|---|
Y | YES |
N | NO |
P | IN PROCESS OF BEING CONFIRMED |
E | VALID BUT AWAITING A DECISION ON EXTRADITION |
Only one status will be included in the message.
Requirements for Hit Confirmation Responses
- The hours field ("HRS/") is required when the confirmation status field is either "E" or "P".
- Do not include sets of data elements that do not pertain to the type of hit confirmation request (YR). For example, if you are responding to a request to confirm a stolen/felony vehicle, you should include only the required data elements plus license plate number (LIC) or vehicle identification number (VIN).
- If you include other data elements not in the stolen/felony vehicle set as either mandatory or optional, the message will be rejected by Nlets.
- Blank data fields should not be sent to Nlets. Both the field and the prefix (Legacy) must be eliminated.
- Hit Confirmation responses (YRs) from Canada will not have NCIC numbers.
Notes
- The line in the response identifying the record's unique fields (license plate, name, serial number, etc.) will vary depending on the type of record being confirmed. This is identified in the request type field (RTY).
GJXDM (DEPRECATED)
GJXDM has been deprecated. Please contact Nlets for additional assistance with GJXDM.
NIEM
Hit Confirmation NIEM Specifications
This section provides NIEM formats and examples for Hit Confirmation Transactions (YQ/YR).
Nlets now provides a standardized response format for this message type. The standardized format for this message is anticipated to be supported on the Nlets production system by June of 2016. Please contact Kate Silhol at ksilhol@nlets.org for additional information regarding implementation.
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 Plate (YQ), Query by VIN (YQ), Query by Name and DOB (YQ), Query on Firearm (YQ), Query on Article (YQ), Query on Security (YQ), Query on Boat by REG (YQ), Query on Boat by BHN (YQ), Query on Vehicle Part (YQ) and Hit Confirmation Response (YR).
Query Formats
Query by Plate (YQ)
n2:NLETSInquiryData
This element will contain all elements specific to this transaction.
n2:QueryRequestActivity
Request information.
n2:QueryRequestSequenceNumber
Request Number. Value must be 1, 2 or 3.
nc:Incident
An occurrence or an event that may require a response.
nc:ActivityIdentification
An identification that references an activity.
nc:IdentificationID
A value that identifies something.
Agency case number.
n2:RequestingAgency
This element contains contact information for the requesting agency.
nc:OrganizationName
A name of an organization.
This element contains the name of the requesting agency.
nc:OrganizationPrimaryContactInformation
A preferred means of contacting an organization.
nc:ContactTelephoneNumber
A telephone number for a telecommunication device by which a person or organization may be contacted. The actual
telephone number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:ContactFaxNumber
A telephone number for a facsimile device by which a person or organization may be contacted. The actual telephone
number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:OrganizationPrincipalOfficial
A chief or high-ranking executive of an organization.
nc:PersonName
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.
n2:Remarks
Free form remarks field. Must be populated when the confirmation status if Pending.
n2:RequestCategoryCode
Describes the specific type of request.
Request type:
SV = stolen/felony vehicle
WP = wanted person
PO = protection order
MP = missing person
SL = stolen license plate
SG = stolen gun
SA = stolen article
SS = stolen security
SB = stolen boat
SP = stolen part
scr:NCICRecordID
A value that identifies an entity within NCIC domain.
NCIC Number. Insert "NONE" in this field if YQ is going to Canada.
n2:RequestPriorityCode
Priority designation. Value must be U (urgent) or R (routine).
nc:Vehicle
A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.
nc:ConveyanceRegistrationPlateIdentification
An identification on a metal plate fixed to a conveyance.
nc:IdentificationID
A value that identifies something.
This element will contain the license plate number to be queried.
nc:IdentificationCategoryText
A kind of identification.
This element should contain the type of license plate being queried. Allowable values come from the NCIC LIT code
table.
nc:IdentificationExpirationDate
A date after which an identification is no longer valid.
nc:Year
A year.
This element's value should be the expiration date of the license plate, also known as the plate year. The value
should be in the format CCYY. For non-expiring plates NX or CCYY may be entered.
nc:IdentificationJurisdictionText
An area, region, or unit in which a unique identification is issued.
This element's value should be the issuing state of the license plate.
Query by VIN (Vehicle Identification Number) (YQ)
n2:NLETSInquiryData
This element will contain all elements specific to this transaction.
n2:QueryRequestActivity
Request Number.
n2:QueryRequestSequenceNumber
Request Number. Value must be 1, 2 or 3.
nc:Incident
An occurrence or an event that may require a response.
nc:ActivityIdentification
An identification that references an activity.
nc:IdentificationID
A value that identifies something.
Agency case number.
n2:RequestingAgency
This element contains contact information for the requesting agency.
nc:OrganizationName
A name of an organization.
This element contains the name of the requesting agency.
nc:OrganizationPrimaryContactInformation
A preferred means of contacting an organization.
nc:ContactTelephoneNumber
A telephone number for a telecommunication device by which a person or organization may be contacted. The actual
telephone number should be placed in <nc:FullTelephoneNumber></nc:FullTelephoneNumber>.
nc:ContactFaxNumber
A telephone number for a facsimile device by which a person or organization may be contacted. The actual telephone
number should be placed in nc:FullTelephoneNumber/nc:TelephoneNumberFullID.
OrganizationPrincipalOfficial
A chief or high-ranking executive of an organization.
nc:PersonName
nc:PersonName
A combination of names and/or titles by which a person is known.
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.
n2:Remarks
Free form remarks field. Must be populated when the confirmation status if Pending.
n2:RequestCategoryCode
Describes the specific type of request.
Request type:
SV = stolen/felony vehicle
WP = wanted person
PO = protection order
MP = missing person
SL = stolen license plate
SG = stolen gun
SA = stolen article
SS = stolen security
SB = stolen boat
SP = stolen part
scr:NCICRecordID
A value that identifies an entity within NCIC domain.
NCIC Number. Insert "NONE" in this field if YQ is going to Canada.
n2:RequestPriorityCode
Priority designation. Value must be U (urgent) or R (routine).
nc:Vehicle
A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.
nc:VehicleIdentification
A unique combination of alphanumeric characters that identifies a specific vehicle.
nc:IdentificationID
A value that identifies something.
This element will contain the VIN (Vehicle Identification Number) to be queried.
nc:VehicleMakeCode
A manufacturer of a vehicle.
This optional element will contain the make of the vehicle being queried. Allowable values come from the NCIC VMA
code table.
nc:ItemModelYearDate
A year in which an item was manufactured or produced.
This element will contain the year of the vehicle. Data should be formatted CCYY.
Query by Name and Date Of Birth (DOB) (YQ)
n2:NLETSInquiryData
This element will contain all elements specific to this transaction.
n2:QueryRequestActivity
Request Number.
n2:QueryRequestSequenceNumber
Request Number. Value must be 1, 2 or 3.
nc:Incident
An occurrence or an event that may require a response.
nc:ActivityIdentification
An identification that references an activity.
nc:IdentificationID
A value that identifies something.
Agency case number.
n2:RequestingAgency
This element contains contact information for the requesting agency.
nc:OrganizationName
A name of an organization.
This element contains the name of the requesting agency.
nc:OrganizationPrimaryContactInformation
A preferred means of contacting an organization.
nc:ContactTelephoneNumber
A telephone number for a telecommunication device by which a person or organization may be contacted. The actual
telephone number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:ContactFaxNumber
A telephone number for a facsimile device by which a person or organization may be contacted. The actual telephone
number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:OrganizationPrincipalOfficial
A chief or high-ranking executive of an organization.
nc:PersonName
nc:PersonName
A combination of names and/or titles by which a person is known.
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.
n2:Remarks
Free form remarks field. Must be populated when the confirmation status if Pending.
n2:RequestCategoryCode
Describes the specific type of request.
Request type:
SV = stolen/felony vehicle
WP = wanted person
PO = protection order
MP = missing person
SL = stolen license plate
SG = stolen gun
SA = stolen article
SS = stolen security
SB = stolen boat
SP = stolen part
scr:NCICRecordID
A value that identifies an entity within NCIC domain.
NCIC Number. Insert "NONE" in this field if YQ is going to Canada.
n2:RequestPriorityCode
Priority designation. Value must be U (urgent) or R (routine).
nc:Person
A human being.
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 (Date of Birth) for the person being queried on. This data in this element must be in xsd:date
format, that is: CCYYMMDD.
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.
j:Warrant
An authorization for an enforcement official to perform a specified action.
j:CourtOrderIssuingCourt
A court that issued a court order.
nc:OrganizationIdentification
An identification that references an organization.
nc:IdentificationID
A value that identifies something.
This optional element will contain the court ORI.
nc:ActivityIdentification
An identification that references an activity.
nc:IdentificationID
A value that identifies something.
This optional element will contain the warrant number.
Query on Firearm (YQ)
n2:NLETSInquiryData
This element will contain all elements specific to this transaction.
n2:QueryRequestActivity
Request Number.
n2:QueryRequestSequenceNumber
Request Number. Value must be 1, 2 or 3.
nc:Incident
An occurrence or an event that may require a response.
nc:ActivityIdentification
An identification that references an activity.
nc:IdentificationID
A value that identifies something.
Agency case number.
n2:RequestingAgency
This element contains contact information for the requesting agency.
nc:OrganizationName
A name of an organization.
This element contains the name of the requesting agency.
nc:OrganizationPrimaryContactInformation
A preferred means of contacting an organization.
nc:ContactTelephoneNumber
A telephone number for a telecommunication device by which a person or organization may be contacted. The actual
telephone number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:ContactFaxNumber
A telephone number for a facsimile device by which a person or organization may be contacted. The actual telephone
number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:OrganizationPrincipalOfficial
A chief or high-ranking executive of an organization.
nc:PersonName
nc:PersonName
A combination of names and/or titles by which a person is known.
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.
n2:Remarks
Free form remarks field. Must be populated when the confirmation status if Pending.
n2:RequestCategoryCode
Describes the specific type of request.
Request type:
SV = stolen/felony vehicle
WP = wanted person
PO = protection order
MP = missing person
SL = stolen license plate
SG = stolen gun
SA = stolen article
SS = stolen security
SB = stolen boat
SP = stolen part
scr:NCICRecordID
A value that identifies an entity within NCIC domain.
NCIC Number. Insert "NONE" in this field if YQ is going to Canada.
n2:RequestPriorityCode
Priority designation. Value must be U (urgent) or R (routine).
nc:Firearm
A weapon that will, or is designed to, or may readily be converted to expel a projectile by air,
carbon dioxide, or the action of
an explosive.
This element will contain information about the gun.
nc:FirearmMakeCode
A manufacturer of a firearm.
This element should contain the make of the gun. The value should be consistent with
NCIC firearm MAK codes.
nc:FirearmCaliberCode
A diameter of the inside of a barrel of a firearm.
This element should contain the caliber of the firearm. The value should be consistent with
NCIC caliber codes.
nc:ItemModelName
A name of a specific design or kind of item made by a manufacturer.
This element contains the model name of the gun.
nc:ItemSerialIdentification
An identification inscribed on or attached to a part, collection of parts, or complete
unit by the manufacturer.
nc:IdentificationID
A value that identifies something.
This element contains the serial number of the gun.
Query on Article (YQ)
n2:NLETSInquiryData
This element will contain all elements specific to this transaction.
n2:QueryRequestActivity
Request Number.
n2:QueryRequestSequenceNumber
Request Number. Value must be 1, 2 or 3.
nc:Incident
An occurrence or an event that may require a response.
nc:ActivityIdentification
An identification that references an activity.
nc:IdentificationID
A value that identifies something.
Agency case number.
n2:RequestingAgency
This element contains contact information for the requesting agency.
nc:OrganizationName
A name of an organization.
This element contains the name of the requesting agency.
nc:OrganizationPrimaryContactInformation
A preferred means of contacting an organization.
nc:ContactTelephoneNumber
A telephone number for a telecommunication device by which a person or organization may be contacted. The actual
telephone number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:ContactFaxNumber
A telephone number for a facsimile device by which a person or organization may be contacted. The actual telephone
number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:OrganizationPrincipalOfficial
A chief or high-ranking executive of an organization.
nc:PersonName
nc:PersonName
A combination of names and/or titles by which a person is known.
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.
n2:Remarks
Free form remarks field. Must be populated when the confirmation status if Pending.
n2:RequestCategoryCode
Describes the specific type of request.
Request type:
SV = stolen/felony vehicle
WP = wanted person
PO = protection order
MP = missing person
SL = stolen license plate
SG = stolen gun
SA = stolen article
SS = stolen security
SB = stolen boat
SP = stolen part
scr:NCICRecordID
A value that identifies an entity within NCIC domain.
NCIC Number. Insert "NONE" in this field if YQ is going to Canada.
n2:RequestPriorityCode
Priority designation. Value must be U (urgent) or R (routine).
nc:TangibleItem
A physical object.
nc:ItemCategoryText
A kind of property item.
This element will indicate the type of security. The value should align with NCIC security type codes.
nc:ItemBrandName
A distinctive name that identifies a manufacturer of a property item.
This element contains the brand name of the article.
nc:ItemSerialIdentification
An identification inscribed on or attached to a part, collection of parts, or complete unit by the manufacturer.
nc:IdentificationID
A value that identifies something.
This element contains the serial number of the article.
Query on Security (YQ)
n2:NLETSInquiryData
This element will contain all elements specific to this transaction.
n2:QueryRequestActivity
Request Number.
n2:QueryRequestSequenceNumber
Request Number. Value must be 1, 2 or 3.
nc:Incident
An occurrence or an event that may require a response.
nc:ActivityIdentification
An identification that references an activity.
nc:IdentificationID
A value that identifies something.
Agency case number.
n2:RequestingAgency
This element contains contact information for the requesting agency.
nc:OrganizationName
A name of an organization.
This element contains the name of the requesting agency.
nc:OrganizationPrimaryContactInformation
A preferred means of contacting an organization.
nc:ContactTelephoneNumber
A telephone number for a telecommunication device by which a person or organization may be contacted. The actual
telephone number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:ContactFaxNumber
A telephone number for a facsimile device by which a person or organization may be contacted. The actual telephone
number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:OrganizationPrincipalOfficial
A chief or high-ranking executive of an organization.
nc:PersonName
nc:PersonName
A combination of names and/or titles by which a person is known.
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.
n2:Remarks
Free form remarks field. Must be populated when the confirmation status if Pending.
n2:RequestCategoryCode
Describes the specific type of request.
Request type:
SV = stolen/felony vehicle
WP = wanted person
PO = protection order
MP = missing person
SL = stolen license plate
SG = stolen gun
SA = stolen article
SS = stolen security
SB = stolen boat
SP = stolen part
scr:NCICRecordID
A value that identifies an entity within NCIC domain.
NCIC Number. Insert "NONE" in this field if YQ is going to Canada.
n2:RequestPriorityCode
Priority designation. Value must be U (urgent) or R (routine).
n2:Securities
A financial instrument showing ownership or credit.
nc:ItemCategoryText
A kind of property item.
This element will indicate the type of security. The value should align with NCIC security type codes.
nc:SecuritiesDenominationText
A value within a series of values reflecting the worth of a security note.
This element will indicate the denomination of security. The value should align with NCIC denomination codes.
nc:ItemSerialIdentification
An identification inscribed on or attached to a part, collection of parts, or complete unit by the manufacturer.
nc:IdentificationID
A value that identifies something.
This element contains the serial number of the security.
Query on Boat by Registration Number (YQ)
n2:NLETSInquiryData
This element will contain all elements specific to this transaction.
n2:QueryRequestActivity
Request Number.
n2:QueryRequestSequenceNumber
Request Number. Value must be 1, 2 or 3.
nc:Incident
An occurrence or an event that may require a response.
nc:ActivityIdentification
An identification that references an activity.
nc:IdentificationID
A value that identifies something.
Agency case number.
n2:RequestingAgency
This element contains contact information for the requesting agency.
nc:OrganizationName
A name of an organization.
This element contains the name of the requesting agency.
nc:OrganizationPrimaryContactInformation
A preferred means of contacting an organization.
nc:ContactTelephoneNumber
A telephone number for a telecommunication device by which a person or organization may be contacted. The actual
telephone number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:ContactFaxNumber
A telephone number for a facsimile device by which a person or organization may be contacted. The actual telephone
number should be placed in nc:FullTelephoneNumber/nc:TelephoneNumberFullID.
nc:OrganizationPrincipalOfficial
A chief or high-ranking executive of an organization.
nc:PersonName
nc:PersonName
A combination of names and/or titles by which a person is known.
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.
n2:Remarks
Free form remarks field. Must be populated when the confirmation status if Pending.
n2:RequestCategoryCode
Describes the specific type of request.
Request type:
SV = stolen/felony vehicle
WP = wanted person
PO = protection order
MP = missing person
SL = stolen license plate
SG = stolen gun
SA = stolen article
SS = stolen security
SB = stolen boat
SP = stolen part
scr:NCICRecordID
A value that identifies an entity within NCIC domain.
NCIC Number. Insert "NONE" in this field if YQ is going to Canada.
n2:RequestPriorityCode
Priority designation. Value must be U (urgent) or R (routine).
nc:Vessel
A mode of transportation capable of transport by water.
nc:VesselRegistrationIdentification
An identification assigned to a vessel by the coast guard or another vessel licensing organization.
Query on Boat by Hull Number (YQ)
n2:NLETSInquiryData
This element will contain all elements specific to this transaction.
n2:QueryRequestActivity
Request Number.
n2:QueryRequestSequenceNumber
Request Number. Value must be 1, 2 or 3.
nc:Incident
An occurrence or an event that may require a response.
nc:ActivityIdentification
An identification that references an activity.
nc:IdentificationID
A value that identifies something.
Agency case number.
n2:RequestingAgency
This element contains contact information for the requesting agency.
nc:OrganizationName
A name of an organization.
This element contains the name of the requesting agency.
nc:OrganizationPrimaryContactInformation
A preferred means of contacting an organization.
nc:ContactTelephoneNumber
A telephone number for a telecommunication device by which a person or organization may be contacted. The actual
telephone number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:ContactFaxNumber
A telephone number for a facsimile device by which a person or organization may be contacted. The actual telephone
number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:OrganizationPrincipalOfficial
A chief or high-ranking executive of an organization.
nc:PersonName
nc:PersonName
A combination of names and/or titles by which a person is known.
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.
n2:Remarks
Free form remarks field. Must be populated when the confirmation status if Pending.
n2:RequestCategoryCode
Describes the specific type of request.
Request type:
SV = stolen/felony vehicle
WP = wanted person
PO = protection order
MP = missing person
SL = stolen license plate
SG = stolen gun
SA = stolen article
SS = stolen security
SB = stolen boat
SP = stolen part
scr:NCICRecordID
A value that identifies an entity within NCIC domain.
NCIC Number. Insert "NONE" in this field if YQ is going to Canada.
n2:RequestPriorityCode
Priority designation. Value must be U (urgent) or R (routine).
nc:Vessel
A mode of transportation capable of transport by water.
nc:VesselHullIdentification
An identification found on the main body or frame of a vessel.
nc:IdentificationID
A value that identifies something.
This element will contain the hull number for query.
nc:ItemMakeName
A name of the manufacturer that produced an item.
This optional element will contain the boat make code. Value should be consistent with NCIC BMA codes.
Query on Vehicle Part (YQ)
n2:NLETSInquiryData
This element will contain all elements specific to this transaction.
n2:QueryRequestActivity
Request Number.
n2:QueryRequestSequenceNumber
Request Number. Value must be 1, 2 or 3.
nc:Incident
An occurrence or an event that may require a response.
nc:ActivityIdentification
An identification that references an activity.
nc:IdentificationID
A value that identifies something.
Agency case number.
n2:RequestingAgency
This element contains contact information for the requesting agency.
nc:OrganizationName
A name of an organization.
This element contains the name of the requesting agency.
nc:OrganizationPrimaryContactInformation
A preferred means of contacting an organization.
nc:ContactTelephoneNumber
A telephone number for a telecommunication device by which a person or organization may be contacted. The actual
telephone number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:ContactFaxNumber
A telephone number for a facsimile device by which a person or organization may be contacted. The actual telephone
number should be placed in <nc:FullTelephoneNumber></nc:TelephoneNumberFullID>.
nc:OrganizationPrincipalOfficial
A chief or high-ranking executive of an organization.
nc:PersonName
nc:PersonName
A combination of names and/or titles by which a person is known.
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.
n2:Remarks
Free form remarks field. Must be populated when the confirmation status if Pending.
n2:RequestCategoryCode
Describes the specific type of request.
Request type:
SV = stolen/felony vehicle
WP = wanted person
PO = protection order
MP = missing person
SL = stolen license plate
SG = stolen gun
SA = stolen article
SS = stolen security
SB = stolen boat
SP = stolen part
scr:NCICRecordID
A value that identifies an entity within NCIC domain.
NCIC Number. Insert "NONE" in this field if YQ is going to Canada.
n2:RequestPriorityCode
Priority designation. Value must be U (urgent) or R (routine).
nc:ConveyancePart
A part or component of a conveyance.
nc:ConveyancePartSerialIdentification
An identifier assigned to a conveyance part.
This element will contain the part number in the nc:IdentificationID subelement.
nc:ConveyancePartBrandName
A brand name or manufacturer name of a conveyance part.
This element contains the brand name of the vehicle part.
nc:ConveyancePartCategoryText
A kind of conveyance part.
This element contains the category of the vehicle part. Value should be consistent with NCIC CAT codes.
nc:ItemBrandName
A distinctive name that identifies a manufacturer of a property item.
Response Formats
Hit Confirmation Free Form Response (YR)
n2:NLETSResponseData
n2:ResponseText
This element will contain the free text hit confirmation response. Nlets recommends the use of
<![CDATA[1234567890]]>
tags to ensure that the response does not contain any characters illegal in XML.
Hit Confirmation Standardized Response (YR)
n2:NLETSResponseData
n2:HitConfirmation
The hit confirmation information.
n2:QueryRequestActivity
Data associated with the request for hit confirmation
n2:RequestActivityCode
The request type value from the query.
Value values are:
SV = stolen/felony vehicle
WP = wanted person
PO = protection order
MP = missing person
SL = stolen license plate
SG = stolen gun
SA = stolen article
SS = stolen security
SB = stolen boat
SP = stolen part
nc:StatusDescriptionText
n2:AdditionalHoursRequiredText
The number of additional hours needed to confirm the hit.
nc:Incident
An occurrence or an event that may require a response.
nc:ActivityIdentification
An identification that references an activity.
nc:IdentificationID
A value that identifies something.
Agency case number.
scr:NCICRecordID
A value that identifies an entity within NCIC domain.
NCIC Number. Insert "NONE" in this field if YQ is going to Canada.
AND
nc:ConveyanceRegistrationPlateIdentification
An identification on a metal plate fixed to a conveyance.
nc:IdentificationID
A value that identifies something.
This element will contain the license plate number to be queried.
nc:IdentificationCategoryText
A kind of identification.
This element should contain the type of license plate being queried. Allowable values come from the NCIC LIT code
table.
nc:IdentificationExpirationDate
A date after which an identification is no longer valid.
nc:Year
A year.
This element's value should be the expiration date of the license plate, also known as the plate year. The value
should be in the format CCYY. For non-expiring plates NX or CCYY may be entered.
nc:IdentificationJurisdiction
An area, region, or unit in which a unique identification is issued.
nc:JurisdictionText
An area in which an organization or person has some kind of authoritative capacity or responsibility over.
This element's value should be the issuing state of the license plate.
OR
nc:Vehicle
A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.
As with a hit confirmation inquiry, the appropriate set of data for the Request Type should be included.
nc:VehicleIdentification
A unique combination of alphanumeric characters that identifies a specific vehicle.
nc:IdentificationID
A value that identifies something.
This element will contain the VIN (Vehicle Identification Number) to be queried.
nc:ItemMakeName
The name of a manufacturer that produced an item.
This optional element will contain the make of the vehicle being queried. Allowable values come from the NCIC VMA
code table.
nc:ItemModelYearDate
A year in which an item was manufactured or produced.
This element will contain the year of the vehicle. Data should be formatted CCYY.
OR
nc:Person
A human being.
As with a hit confirmation inquiry, the appropriate set of data for the Request Type should be included.
nc:PersonBirthDate
A date a person was born.
nc:Date
A full date.
This element contains the DOB for the person. This data in this element must be in xsd:date format, that is: ccyymmdd.
nc:PersonName
A combination of names and/or titles by which a person is known.
nc:PersonFullName
A complete name of a person.
nc:PersonSexText
A gender or sex of a person.
OR
nc:Firearm
A weapon that will, or is designed to, or may readily be converted to expel a projectile by air,
carbon dioxide, or the action of
an explosive.
This element will contain information about the gun.
nc:FirearmMakeCode
A manufacturer of a firearm.
This element should contain the make of the gun. The value should be consistent with
NCIC firearm MAK codes.
nc:FirearmBoreSizeText
A size of the inside diameter a firearm barrel or bore.
This element should contain the caliber of the firearm. The value should be consistent with
NCIC caliber codes.
nc:ItemModelName
A name of a specific design or kind of item made by a manufacturer.
This element contains the model name of the gun.
nc:ItemSerialIdentification
An identification inscribed on or attached to a part, collection of parts, or complete
unit by the manufacturer.
nc:IdentificationID
A value that identifies something.
This element contains the serial number of the gun.
OR
nc:Item
An article or thing.
As with a hit confirmation inquiry, the appropriate set of data for the Request Type should be included.
nc:ItemCategoryText
A kind of property item.
This element will indicate the type of security. The value should align with NCIC security type codes.
nc:ItemBrandName
A distinctive name that identifies a manufacturer of a property item.
This element contains the brand name of the article.
nc:ItemSerialIdentification
An identification inscribed on or attached to a part, collection of parts, or complete unit by the manufacturer.
nc:IdentificationID
A value that identifies something.
This element contains the serial number of the article.
OR
nc:Securities
A financial instrument showing ownership or credit.
As with a hit confirmation inquiry, the appropriate set of data for the Request Type should be included.
nc:ItemCategoryText
A kind of property item.
This element will indicate the type of security. The value should align with NCIC security type codes.
nc:SecuritiesDenominationText
A value within a series of values reflecting the worth of a security note.
This element will indicate the denomination of security. The value should align with NCIC denomination codes.
nc:ItemSerialIdentification
An identification inscribed on or attached to a part, collection of parts, or complete unit by the manufacturer.
nc:IdentificationID
A value that identifies something.
This element contains the serial number of the security.
OR
nc:Vessel
A mode of transportation capable of transport by water.
As with a hit confirmation inquiry, the appropriate set of data for the Request Type should be included.
nc:VesselHullIdentification
An identification found on the main body or frame of a vessel.
nc:IdentificationID
A value that identifies something.
This element will contain the hull number for query.
nc:ItemMakeName
A name of the manufacturer that produced an item.
This optional element will contain the boat make code. Value should be consistent with NCIC BMA codes.
nc:ItemRegistration
A registration of an item with an authority.
nc:RegistrationIdentification
An identification of a registration certificate or document. The actual value will be in the nc:IdentificationID sub-element
OR
nc:ConveyancePart
A part or component of a conveyance.
As with a hit confirmation inquiry, the appropriate set of data for the Request Type should be included.
nc:ConveyancePartID
An identifier assigned to a conveyance part.
This element will contain the part number.
nc:ConveyancePartBrandName
A brand name or manufacturer name of a conveyance part.
This element contains the brand name of the vehicle part.
nc:ConveyancePartCategoryText
A kind of conveyance part.
This element contains the category of the vehicle part. Value should be consistent with NCIC CAT codes.
nc:ItemBrandName
A distinctive name that identifies a manufacturer of a property item.
n2:Confirmation
Data about the confirmation.
n2:ConfirmingAgency
Details of the agency providing the hit confirmation.
nc:OrganizationPrimaryContactInformation
A preferred means of contacting an organization.
nc:ContactTelephoneNumber
A telephone number for a telecommunication device by which a person or organization may be contacted. The actual
telephone number should be placed in <nc:FullTelephoneFullID></nc:TelephoneNumberFullID>.
if an extension is necessary, it may be placed in <TelephoneSuffixID></nc:TelephoneSuffixID>.
this element may appear twice, once for a phone and once for a fax;
when a fax number is being reported, the value 'Facsimile' should be placed in <nc:TelephoneNumberCategoryText>.
nc:ContactEntity
nc:EntityPerson
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.
n2:Remarks
Additional remarks. Must be populated when the confirmation status if Pending.
Hit Confirmation NIEM Examples
Example 1: Hit Confirmation query by VIN.
<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>YQ</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
<nh2:DocumentControlFieldText><![CDATA[1234567890]]></nh2:DocumentControlFieldText>
</n2:NLETSMessageHeader>
<n2:NLETSInquiryData n2:key="YQ">
<n2:QueryRequestActivity>
<n2:QueryRequestSequenceNumber>1</n2:QueryRequestSequenceNumber>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE-1234</nc:IdentificationID>
</nc:ActivityIdentification>
</nc:Incident>
<n2:RequestingAgency>
<nc:OrganizationName>NLETS PD</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>8005284020</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
</nc:OrganizationPrimaryContactInformation>
<nc:OrganizationPrincipalOfficial>
<nc:PersonName>
<nc:PersonFullName>MOUSE, MICKEY</nc:PersonFullName>
</nc:PersonName>
</nc:OrganizationPrincipalOfficial>
</n2:RequestingAgency>
<n2:Remarks>IS THIS ENTRY STILL VALID. OUR OFFICER IS OUT WITH THIS VEHICLE, NO KEYS, NO DMG, VEHICLE IS UNLOCKED.
PLEASE CONFIRM AND WHAT YOU WANT DONE WITH THE VEHICLE. THANK YOU.</n2:Remarks>
<n2:RequestCategoryCode>SV</n2:RequestCategoryCode>
<scr:NCICRecordID xmlns:scr="http://niem.gov/niem/domains/screening/2.1">V123456789</scr:NCICRecordID>
<n2:RequestPriorityCode>U</n2:RequestPriorityCode>
</n2:QueryRequestActivity>
<nc:Vehicle>
<nc:VehicleMakeCode>CHEV</nc:VehicleMakeCode>
<nc:ItemModelYearDate>1950</nc:ItemModelYearDate>
<nc:VehicleIdentification>
<nc:IdentificationID>1ABCD23E456789012</nc:IdentificationID>
</nc:VehicleIdentification>
</nc:Vehicle>
</n2:NLETSInquiryData>
</n2:NLETS>
|
---|
Example 2: Hit Confirmation query by Plate.
<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>YQ</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
<nh2:DocumentControlFieldText><![CDATA[1234567890]]></nh2:DocumentControlFieldText>
</n2:NLETSMessageHeader>
<n2:NLETSInquiryData n2:key="YQ">
<n2:QueryRequestActivity>
<n2:QueryRequestSequenceNumber>1</n2:QueryRequestSequenceNumber>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE-1234</nc:IdentificationID>
</nc:ActivityIdentification>
</nc:Incident>
<n2:RequestingAgency>
<nc:OrganizationName>NLETS PD</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>8005284020</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
</nc:OrganizationPrimaryContactInformation>
<nc:OrganizationPrincipalOfficial>
<nc:PersonName>
<nc:PersonFullName>MOUSE, MINNIE</nc:PersonFullName>
</nc:PersonName>
</nc:OrganizationPrincipalOfficial>
</n2:RequestingAgency>
<n2:Remarks>IS THIS ENTRY STILL VALID. OUR OFFICER IS OUT ON TRAFFIC STOP WITH IT.</n2:Remarks>
<n2:RequestCategoryCode>SV</n2:RequestCategoryCode>
<scr:NCICRecordID xmlns:scr="http://niem.gov/niem/domains/screening/2.1">V123456789</scr:NCICRecordID>
<n2:RequestPriorityCode>U</n2:RequestPriorityCode>
</n2:QueryRequestActivity>
<nc:Vehicle>
<nc:ConveyanceRegistrationPlateIdentification>
<nc:IdentificationID>ABC123</nc:IdentificationID>
</nc:ConveyanceRegistrationPlateIdentification>
<nc:ItemModelYearDate>1999</nc:ItemModelYearDate>
<nc:VehicleMakeCode>CHEV</nc:VehicleMakeCode>
</nc:Vehicle>
</n2:NLETSInquiryData>
</n2:NLETS>
|
---|
Example 3: Hit Confirmation query by name and date of birth (DOB).
<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>YQ</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS49</nh2:DestinationORIID>
<nh2:DocumentControlFieldText><![CDATA[z234z678z0]]></nh2:DocumentControlFieldText>
</n2:NLETSMessageHeader>
<n2:NLETSInquiryData n2:key="YQ">
<n2:QueryRequestActivity>
<n2:QueryRequestSequenceNumber>1</n2:QueryRequestSequenceNumber>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>1234-567890</nc:IdentificationID>
</nc:ActivityIdentification>
</nc:Incident>
<n2:RequestingAgency>
<nc:OrganizationName>NLETS PD</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>8005284020</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
</nc:OrganizationPrimaryContactInformation>
<nc:OrganizationPrincipalOfficial>
<nc:PersonName>
<nc:PersonFullName>DUCK, DONALD</nc:PersonFullName>
</nc:PersonName>
</nc:OrganizationPrincipalOfficial>
</n2:RequestingAgency>
<n2:RequestCategoryCode>WP</n2:RequestCategoryCode>
<scr:NCICRecordID xmlns:scr="http://niem.gov/niem/domains/screening/2.1">W1234567</scr:NCICRecordID>
<n2:RequestPriorityCode>U</n2:RequestPriorityCode>
<n2:Remarks>THIS AN EXAMPLE FOR HIT CONFIRMATION QUERY BY NAME AND DATE OF BIRTH</n2:Remarks>
</n2:QueryRequestActivity>
<nc:Person>
<nc:PersonBirthDate>
<nc:Date>1940-07-27</nc:Date>
</nc:PersonBirthDate>
<nc:PersonName>
<nc:PersonFullName>BUNNY,BUGS</nc:PersonFullName>
</nc:PersonName>
<nc:PersonSexCode>M</nc:PersonSexCode>
</nc:Person>
</n2:NLETSInquiryData>
</n2:NLETS>
|
---|
Example 4: Hit Confirmation query on firearm.
<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>YQ</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
</n2:NLETSMessageHeader>
<n2:NLETSInquiryData n2:key="YQ">
<n2:QueryRequestActivity>
<n2:QueryRequestSequenceNumber>1</n2:QueryRequestSequenceNumber>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>01-2345</nc:IdentificationID>
</nc:ActivityIdentification>
</nc:Incident>
<n2:RequestingAgency>
<nc:OrganizationName>NLETS PD</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>8005284020</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
</nc:OrganizationPrimaryContactInformation>
<nc:OrganizationPrincipalOfficial>
<nc:PersonName>
<nc:PersonFullName>MCDUCK, SCROOGE</nc:PersonFullName>
</nc:PersonName>
</nc:OrganizationPrincipalOfficial>
</n2:RequestingAgency>
<n2:Remarks>PLEASE VERIFY IF THIS IS VALID. HAVE UNITS OUT WITH A SUBJ IN POSSESSION OF THIS FIREARM</n2:Remarks>
<n2:RequestCategoryCode>SG</n2:RequestCategoryCode>
<scr:NCICRecordID xmlns:scr="http://niem.gov/niem/domains/screening/2.1">G123456789</scr:NCICRecordID>
<n2:RequestPriorityCode>R</n2:RequestPriorityCode>
</n2:QueryRequestActivity>
<nc:Firearm>
<nc:ItemSerialIdentification>
<nc:IdentificationID>NB123456</nc:IdentificationID>
</nc:ItemSerialIdentification>
<nc:FirearmMakeCode>TAS</nc:FirearmMakeCode>
<nc:FirearmCaliberCode>40</nc:FirearmCaliberCode>
</nc:Firearm>
</n2:NLETSInquiryData>
</n2:NLETS>
|
---|
Example 5: Hit Confirmation query on article.
<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>YQ</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
<nh2:DocumentControlFieldText><![CDATA[1234567890]]></nh2:DocumentControlFieldText>
</n2:NLETSMessageHeader>
<n2:NLETSInquiryData n2:key="YQ">
<nc:TangibleItem>
<nc:ItemBrandName>NOVARA</nc:ItemBrandName>
<nc:ItemCategoryText>BBICYCL</nc:ItemCategoryText>
<nc:ItemSerialIdentification>
<nc:IdentificationID>S10161</nc:IdentificationID>
</nc:ItemSerialIdentification>
</nc:TangibleItem>
<n2:QueryRequestActivity>
<n2:RequestPriorityCode>U</n2:RequestPriorityCode>
<n2:QueryRequestSequenceNumber>1</n2:QueryRequestSequenceNumber>
<n2:RequestCategoryCode>SA</n2:RequestCategoryCode>
<scr:NCICRecordID xmlns:scr="http://niem.gov/niem/domains/screening/2.1">A123456789</scr:NCICRecordID>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>01-2345</nc:IdentificationID>
</nc:ActivityIdentification>
</nc:Incident>
<n2:RequestingAgency>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>8005244020</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
</nc:OrganizationPrimaryContactInformation>
<nc:OrganizationPrincipalOfficial>
<nc:PersonName>
<nc:PersonFullName>BELL, TINKER</nc:PersonFullName>
</nc:PersonName>
</nc:OrganizationPrincipalOfficial>
<nc:OrganizationName>NLETS PD</nc:OrganizationName>
</n2:RequestingAgency>
<n2:Remarks>IS THIS ACTIVE? OFFICERS ARE OUT WITH A NOVARA BICYCLE THAT MATCHES THAT SERIAL NUMBER - HOWEVER,
IT IS UNKNOWN IF THIS IS THE SAME BICYCLE IN THE HIT, OUR BICYCLE IS ORANGE AND WHITE, UNK IF IT WAS PAINTED AFTER
STOLEN OR IF THIS IS A GENERIC SERIAL NUMBER // OPR 14</n2:Remarks>
</n2:QueryRequestActivity>
</n2:NLETSInquiryData>
</n2:NLETS>
|
---|
Example 6: Hit Confirmation query on security.
<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>YQ</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS43</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>
<![CDATA[1234567890]]>
</nh2:DocumentControlFieldText>
</n2:NLETSMessageHeader>
<n2:NLETSInquiryData n2:key="YQ">
<n2:QueryRequestActivity>
<n2:QueryRequestSequenceNumber>1</n2:QueryRequestSequenceNumber>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>TEST</nc:IdentificationID>
</nc:ActivityIdentification>
</nc:Incident>
<n2:RequestingAgency>
<nc:OrganizationName>TEST</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>0001234567</nc:TelephoneNumberFullID>
<nc:TelephoneSuffixID>0123</nc:TelephoneSuffixID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
<nc:ContactFaxNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>1234567891</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactFaxNumber>
</nc:OrganizationPrimaryContactInformation>
<nc:OrganizationPrincipalOfficial>
<nc:PersonName>
<nc:PersonFullName>TEST</nc:PersonFullName>
</nc:PersonName>
</nc:OrganizationPrincipalOfficial>
</n2:RequestingAgency>
<n2:RequestCategoryCode>SS</n2:RequestCategoryCode>
<scr:NCICRecordID xmlns:scr="http://niem.gov/niem/domains/screening/2.1">V137583492</scr:NCICRecordID>
<n2:RequestPriorityCode>U</n2:RequestPriorityCode>
<n2:Remarks>TEST</n2:Remarks>
</n2:QueryRequestActivity>
<n2:Securities>
<nc:ItemSerialIdentification>
<nc:IdentificationID>TEST82395</nc:IdentificationID>
</nc:ItemSerialIdentification>
<nc:ItemCategoryText>BC</nc:ItemCategoryText>
<nc:SecuritiesDenominationText>1000</nc:SecuritiesDenominationText>
</n2:Securities>
</n2:NLETSInquiryData>
</n2:NLETS>
|
---|
Example 7: Hit Confirmation query on a boat by registration.
<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>YQ</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
<nh2:DocumentControlFieldText><![CDATA[1234567890]]></nh2:DocumentControlFieldText>
</n2:NLETSMessageHeader>
<n2:NLETSInquiryData n2:key="YQ">
<n2:QueryRequestActivity>
<n2:QueryRequestSequenceNumber>1</n2:QueryRequestSequenceNumber>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE123</nc:IdentificationID>
</nc:ActivityIdentification>
</nc:Incident>
<n2:RequestingAgency>
<nc:OrganizationName>NLETS PD</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>8005284020</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
</nc:OrganizationPrimaryContactInformation>
<nc:OrganizationPrincipalOfficial>
<nc:PersonName>
<nc:PersonFullName>HOOD, ROBIN</nc:PersonFullName>
</nc:PersonName>
</nc:OrganizationPrincipalOfficial>
</n2:RequestingAgency>
<n2:RequestCategoryCode>SB</n2:RequestCategoryCode>
<scr:NCICRecordID xmlns:scr="http://niem.gov/niem/domains/screening/2.1">X111111111</scr:NCICRecordID>
<n2:RequestPriorityCode>R</n2:RequestPriorityCode>
</n2:QueryRequestActivity>
<nc:Vessel>
<nc:VesselRegistrationIdentification>
<nc:IdentificationID>Vess123</nc:IdentificationID>
<nc:IdentificationCategoryText>String</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Year>2001</nc:Year>
</nc:IdentificationExpirationDate>
<nc:IdentificationJurisdictionText>String</nc:IdentificationJurisdictionText>
</nc:VesselRegistrationIdentification>
</nc:Vessel>
<nc:Remarks>WE ARE OUT WITH THE ABOVE VESSEL/PLEASE ADVISE OF OWNER INFORMATION/RECOVERY
WILL FOLLOW WHEN AVAILABLE</nc:Remarks>
</n2:NLETSInquiryData>
</n2:NLETS>
|
---|
Example 8: Hit Confirmation query on a boat by boat hull number.
<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>YQ</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
<nh2:DocumentControlFieldText><![CDATA[1234567890]]></nh2:DocumentControlFieldText>
</n2:NLETSMessageHeader>
<n2:NLETSInquiryData n2:key="YQ">
<n2:QueryRequestActivity>
<n2:QueryRequestSequenceNumber>1</n2:QueryRequestSequenceNumber>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE123</nc:IdentificationID>
</nc:ActivityIdentification>
</nc:Incident>
<n2:RequestingAgency>
<nc:OrganizationName>NLETS PD</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>8005284020</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
</nc:OrganizationPrimaryContactInformation>
<nc:OrganizationPrincipalOfficial>
<nc:PersonName>
<nc:PersonFullName>PAN, PETER</nc:PersonFullName>
</nc:PersonName>
</nc:OrganizationPrincipalOfficial>
</n2:RequestingAgency>
<n2:RequestCategoryCode>SB</n2:RequestCategoryCode>
<scr:NCICRecordID xmlns:scr="http://niem.gov/niem/domains/screening/2.1">X111111111</scr:NCICRecordID>
<n2:RequestPriorityCode>R</n2:RequestPriorityCode>
</n2:QueryRequestActivity>
<nc:Vessel>
<nc:ItemMakeName>BOSTON</nc:ItemMakeName>
<nc:ItemMakeYearDate>2001</nc:ItemMakeYearDate>
<nc:VesselHullIdentification>
<nc:IdentificationID>AAAA1111A111</nc:IdentificationID>
</nc:VesselHullIdentification>
</nc:Vessel>
<nc:Remarks>WE ARE OUT WITH THE ABOVE VESSEL/PLEASE ADVISE OF
OWNER INFORMATION/RECOVERY WILL FOLLOW WHEN AVAILABLE</nc:Remarks>
</n2:NLETSInquiryData>
</n2:NLETS>
|
---|
Example 9: Hit Confirmation query on vehicle part.
<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>YQ</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
<nh2:DocumentControlFieldText><![CDATA[1234567890]]></nh2:DocumentControlFieldText>
</n2:NLETSMessageHeader>
<n2:NLETSInquiryData n2:key="YQ">
<n2:QueryRequestActivity>
<n2:QueryRequestSequenceNumber>1</n2:QueryRequestSequenceNumber>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE123</nc:IdentificationID>
</nc:ActivityIdentification>
</nc:Incident>
<n2:RequestingAgency>
<nc:OrganizationName>NLETS PD</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>8005284020</nc:TelephoneNumberFullID>
</nc:FullTelephoneNumber>
</nc:ContactTelephoneNumber>
</nc:OrganizationPrimaryContactInformation>
<nc:OrganizationPrincipalOfficial>
<nc:PersonName>
<nc:PersonFullName>McQuack, Launchpad</nc:PersonFullName>
</nc:PersonName>
</nc:OrganizationPrincipalOfficial>
</n2:RequestingAgency>
<n2:RequestCategoryCode>SP</n2:RequestCategoryCode>
<scr:NCICRecordID xmlns:scr="http://niem.gov/niem/domains/screening/2.1">X111111111</scr:NCICRecordID>
<n2:RequestPriorityCode>R</n2:RequestPriorityCode>
</n2:QueryRequestActivity>
<nc:ConveyancePart>
<nc:ItemSerialIdentification>
<nc:IdentificationID>Part123</nc:IdentificationID>
</nc:ItemSerialIdentification>
<nc:ConveyancePartID>XMI12567894</nc:ConveyancePartID>
<nc:ConveyancePartBrandName>ACUR</nc:ConveyancePartBrandName>
<nc:ConveyancePartCategoryText>TN</nc:ConveyancePartCategoryText>
</nc:ConveyancePart>
<nc:Remarks>WE ARE OUT WITH THE ABOVE VEHICLE PART/PLEASE ADVISE OF OWNER
INFORMATION/RECOVERY WILL FOLLOW WHEN AVAILABLE</nc:Remarks>
</n2:NLETSInquiryData>
</n2:NLETS>
|
---|
Example 10: Hit Confirmation free form 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>YR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
<nh2:DocumentControlFieldText><![CDATA[1234567890]]></nh2:DocumentControlFieldText>
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
<nh2:MessageReceiveTime>08:54</nh2:MessageReceiveTime>
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
<nh2:MessageSendTime>08:54</nh2:MessageSendTime>
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
<nh2:SendMessageNumeric>00373</nh2:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="">
<n2:ResponseText>****HIT CONFIRMATION RESPONSE****
THE RECORD BELOW:IS NOT CONFIRMED
OCA/01-1234.NIC/W123456789.
*** WANTED PERSON ***
NAM/LAUNCHPAD,MCQUACK.DOB/19290126.SEX/M.
EXTRADITE // WILL BE DISNEY PICKUP ONLY
NAME OF CONFIRMER: PAN, PETER
CONFIRMING AGENCY: DS123456789
PHONE: (123)456-7890 FAX: (123)456-0987
REMARKS: WE DO HOLD VALID CIMINAL SUPPORT
WARRANT FOR THE ABOVE SUBJ BUT WILL NOT.</n2:ResponseText>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Example 11: Hit Confirmation response for Missing Person.
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS40</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText>
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime>
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
<nh2:MessageSendTime>08:55</nh2:MessageSendTime>
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="YR">
<n2-yr:HitConfirmation>
<n2-yr:QueryRequestActivity>
<n2-yr:RequestCategoryCode>MP</n2-yr:RequestCategoryCode>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE-1234</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>1957-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ActivityIdentification>
<nc:ActivityStatus>
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText>
</nc:ActivityStatus>
</nc:Incident>
<scr:NCICRecordID>W123456789</scr:NCICRecordID>
</n2-yr:QueryRequestActivity>
<nc:Person>
<nc:PersonBirthDate>
<nc:Date>1920-01-26</nc:Date>
</nc:PersonBirthDate>
<nc:PersonName>
<nc:PersonGivenName>MINNIE</nc:PersonGivenName>
<nc:PersonSurName>MOUSE</nc:PersonSurName>
<nc:PersonFullName>MOUSE, MINNIE</nc:PersonFullName>
</nc:PersonName>
<nc:PersonSexText>F</nc:PersonSexText>
</nc:Person>
<n2-yr:Confirmation>
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText>
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText>
<n2-yr:ConfirmingAgency>
<nc:OrganizationName>NLETS</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID>
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID>
</nc:FullTelephoneNumber>
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText>
</nc:ContactTelephoneNumber>
<nc:ContactEntity>
<nc:EntityPerson>
<nc:PersonName>
<nc:PersonFullName>John D Smith</nc:PersonFullName>
</nc:PersonName>
</nc:EntityPerson>
</nc:ContactEntity>
</nc:OrganizationPrimaryContactInformation>
</n2-yr:ConfirmingAgency>
<n2-yr:Remarks>MISSING PERSON IS CONFIRMED PER SGT PLEASE CONTACT
SUBJECT ALONE TO ASK IF SHE IS OKAY AND EVERYTHING IS GOOD AND IF
SO THEN SHE CAN BE LET GO PLEASE PLACE LOCATE AND ADVISE INFORMATION THANK YOU</n2-yr:Remarks>
</n2-yr:Confirmation>
</n2-yr:HitConfirmation>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Example 12: Hit Confirmation response for Protection Order.
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS40</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText>
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime>
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
<nh2:MessageSendTime>08:55</nh2:MessageSendTime>
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="YR">
<n2-yr:HitConfirmation>
<n2-yr:QueryRequestActivity>
<n2-yr:RequestCategoryCode>PO</n2-yr:RequestCategoryCode>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE-1234</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>1957-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ActivityIdentification>
<nc:ActivityStatus>
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText>
</nc:ActivityStatus>
</nc:Incident>
<scr:NCICRecordID>W123456789</scr:NCICRecordID>
</n2-yr:QueryRequestActivity>
<nc:Person>
<nc:PersonBirthDate>
<nc:Date>1920-01-26</nc:Date>
</nc:PersonBirthDate>
<nc:PersonName>
<nc:PersonGivenName>MINNIE</nc:PersonGivenName>
<nc:PersonSurName>MOUSE</nc:PersonSurName>
<nc:PersonFullName>MOUSE, MINNIE</nc:PersonFullName>
</nc:PersonName>
<nc:PersonSexText>F</nc:PersonSexText>
</nc:Person>
<n2-yr:Confirmation>
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText>
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText>
<n2-yr:ConfirmingAgency>
<nc:OrganizationName>NLETS</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID>
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID>
</nc:FullTelephoneNumber>
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText>
</nc:ContactTelephoneNumber>
<nc:ContactEntity>
<nc:EntityPerson>
<nc:PersonName>
<nc:PersonFullName>John D Smith</nc:PersonFullName>
</nc:PersonName>
</nc:EntityPerson>
</nc:ContactEntity>
</nc:OrganizationPrimaryContactInformation>
</n2-yr:ConfirmingAgency>
<n2-yr:Remarks>MISSING PERSON IS CONFIRMED PER SGT PLEASE CONTACT
SUBJECT ALONE TO ASK IF SHE IS OKAY AND EVERYTHING IS GOOD AND IF
SO THEN SHE CAN BE LET GO PLEASE PLACE LOCATE AND ADVISE INFORMATION THANK YOU</n2-yr:Remarks>
</n2-yr:Confirmation>
</n2-yr:HitConfirmation>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Example 13: Hit Confirmation response for Stolen Article.
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText>
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime>
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
<nh2:MessageSendTime>08:55</nh2:MessageSendTime>
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="YR">
<n2-yr:HitConfirmation>
<n2-yr:QueryRequestActivity>
<n2-yr:RequestCategoryCode>SA</n2-yr:RequestCategoryCode>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE-1234</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>1957-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ActivityIdentification>
<nc:ActivityStatus>
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText>
</nc:ActivityStatus>
</nc:Incident>
<scr:NCICRecordID>W123456789</scr:NCICRecordID>
</n2-yr:QueryRequestActivity>
<nc:Item>
<nc:ItemSerialIdentification>
<nc:IdentificationID>SER12345678</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Item Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>2021-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ItemSerialIdentification>
<nc:ItemBrandName>Item Brand</nc:ItemBrandName>
<nc:ItemCategoryText>Item Category</nc:ItemCategoryText>
<nc:ItemMakeName>Item Make</nc:ItemMakeName>
<nc:ItemModelName>Item Model</nc:ItemModelName>
<nc:ItemModelYearDate>2001</nc:ItemModelYearDate>
</nc:Item>
<n2-yr:Confirmation>
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText>
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText>
<n2-yr:ConfirmingAgency>
<nc:OrganizationName>NLETS</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID>
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID>
</nc:FullTelephoneNumber>
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText>
</nc:ContactTelephoneNumber>
<nc:ContactEntity>
<nc:EntityPerson>
<nc:PersonName>
<nc:PersonFullName>John D Smith</nc:PersonFullName>
</nc:PersonName>
</nc:EntityPerson>
</nc:ContactEntity>
</nc:OrganizationPrimaryContactInformation>
</n2-yr:ConfirmingAgency>
<n2-yr:Remarks>Remarks</n2-yr:Remarks>
</n2-yr:Confirmation>
</n2-yr:HitConfirmation>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Example 14: Hit Confirmation response for Stolen Boat.
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="YR">
<n2-yr:HitConfirmation>
<n2-yr:QueryRequestActivity>
<n2-yr:RequestCategoryCode>SB</n2-yr:RequestCategoryCode>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE-1234</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>1957-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ActivityIdentification>
<nc:ActivityStatus>
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText>
</nc:ActivityStatus>
</nc:Incident>
<scr:NCICRecordID>W123456789</scr:NCICRecordID>
</n2-yr:QueryRequestActivity>
<nc:Vessel>
<nc:ItemSerialIdentification>
<nc:IdentificationID>BHN123456789</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Vessel Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>2021-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ItemSerialIdentification>
<nc:ItemBrandName>Vessel Brand</nc:ItemBrandName>
<nc:ItemCategoryText>Vessel Category</nc:ItemCategoryText>
<nc:ItemMakeName>Vessel Make</nc:ItemMakeName>
<nc:ItemModelName>Vessel Model</nc:ItemModelName>
<nc:ItemModelYearDate>2001</nc:ItemModelYearDate>
<nc:VesselHullIdentification>
<nc:IdentificationID>HID12345678</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>VesselHull Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>2021-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:VesselHullIdentification>
</nc:Vessel>
<j:ItemRegistration>
<j:RegistrationIdentification>
<nc:IdentificationID>REG12345678</nc:IdentificationID>
</j:RegistrationIdentification>
</j:ItemRegistration>
<n2-yr:Confirmation>
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText>
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText>
<n2-yr:ConfirmingAgency>
<nc:OrganizationName>NLETS</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID>
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID>
</nc:FullTelephoneNumber>
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText>
</nc:ContactTelephoneNumber>
<nc:ContactEntity>
<nc:EntityPerson>
<nc:PersonName>
<nc:PersonFullName>John D Smith</nc:PersonFullName>
</nc:PersonName>
</nc:EntityPerson>
</nc:ContactEntity>
</nc:OrganizationPrimaryContactInformation>
</n2-yr:ConfirmingAgency>
<n2-yr:Remarks>Remarks</n2-yr:Remarks>
</n2-yr:Confirmation>
</n2-yr:HitConfirmation>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Example 15: Hit Confirmation response for Stolen gun.
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText>
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime>
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
<nh2:MessageSendTime>08:55</nh2:MessageSendTime>
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="YR">
<n2-yr:HitConfirmation>
<n2-yr:QueryRequestActivity>
<n2-yr:RequestCategoryCode>SG</n2-yr:RequestCategoryCode>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE-1234</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>1957-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ActivityIdentification>
<nc:ActivityStatus>
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText>
</nc:ActivityStatus>
</nc:Incident>
<scr:NCICRecordID>W123456789</scr:NCICRecordID>
</n2-yr:QueryRequestActivity>
<j:Firearm>
<nc:ItemSerialIdentification>
<nc:IdentificationID>SER12345678</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>GUN Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>2021-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ItemSerialIdentification>
<nc:ItemBrandName>Ruger</nc:ItemBrandName>
<nc:ItemCategoryText>Semi-Automatic pistol</nc:ItemCategoryText>
<nc:ItemMakeName>Ruger</nc:ItemMakeName>
<nc:ItemModelName>Ruger-57</nc:ItemModelName>
<nc:ItemModelYearDate>2001</nc:ItemModelYearDate>
<j:FirearmBoreSizeText>50</j:FirearmBoreSizeText>
</j:Firearm>
<n2-yr:Confirmation>
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText>
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText>
<n2-yr:ConfirmingAgency>
<nc:OrganizationName>NLETS</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID>
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID>
</nc:FullTelephoneNumber>
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText>
</nc:ContactTelephoneNumber>
<nc:ContactEntity>
<nc:EntityPerson>
<nc:PersonName>
<nc:PersonFullName>John D Smith</nc:PersonFullName>
</nc:PersonName>
</nc:EntityPerson>
</nc:ContactEntity>
</nc:OrganizationPrimaryContactInformation>
</n2-yr:ConfirmingAgency>
<n2-yr:Remarks>Remarks</n2-yr:Remarks>
</n2-yr:Confirmation>
</n2-yr:HitConfirmation>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Example 16: Hit Confirmation response for Stolen License Plate.
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText>
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime>
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
<nh2:MessageSendTime>08:55</nh2:MessageSendTime>
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="YR">
<n2-yr:HitConfirmation>
<n2-yr:QueryRequestActivity>
<n2-yr:RequestCategoryCode>SL</n2-yr:RequestCategoryCode>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE-1234</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>1957-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ActivityIdentification>
<nc:ActivityStatus>
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText>
</nc:ActivityStatus>
</nc:Incident>
<scr:NCICRecordID>W123456789</scr:NCICRecordID>
</n2-yr:QueryRequestActivity>
<j:ConveyanceRegistrationPlateIdentification>
<nc:IdentificationID>ABC123</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>PC</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>2021-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</j:ConveyanceRegistrationPlateIdentification>
<n2-yr:Confirmation>
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText>
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText>
<n2-yr:ConfirmingAgency>
<nc:OrganizationName>NLETS</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID>
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID>
</nc:FullTelephoneNumber>
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText>
</nc:ContactTelephoneNumber>
<nc:ContactEntity>
<nc:EntityPerson>
<nc:PersonName>
<nc:PersonFullName>John D Smith</nc:PersonFullName>
</nc:PersonName>
</nc:EntityPerson>
</nc:ContactEntity>
</nc:OrganizationPrimaryContactInformation>
</n2-yr:ConfirmingAgency>
<n2-yr:Remarks>Remarks</n2-yr:Remarks>
</n2-yr:Confirmation>
</n2-yr:HitConfirmation>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Example 17: Hit Confirmation response for Stolen Part.
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText>
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime>
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
<nh2:MessageSendTime>08:55</nh2:MessageSendTime>
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="YR">
<n2-yr:HitConfirmation>
<n2-yr:QueryRequestActivity>
<n2-yr:RequestCategoryCode>SP</n2-yr:RequestCategoryCode>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE-1234</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>1957-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ActivityIdentification>
<nc:ActivityStatus>
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText>
</nc:ActivityStatus>
</nc:Incident>
<scr:NCICRecordID>W123456789</scr:NCICRecordID>
</n2-yr:QueryRequestActivity>
<j:ConveyancePart>
<nc:ItemSerialIdentification>
<nc:IdentificationID>PART123456789</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Part Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>2021-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ItemSerialIdentification>
<nc:ItemBrandName>Item Brand Name</nc:ItemBrandName>
<nc:ItemCategoryText>Item Category Text</nc:ItemCategoryText>
<nc:ItemMakeName>Item Make Name</nc:ItemMakeName>
<nc:ItemModelName>Item Model Name</nc:ItemModelName>
<nc:ItemModelYearDate>2001</nc:ItemModelYearDate>
<j:ConveyancePartID>Part ID</j:ConveyancePartID>
<j:ConveyancePartBrandName>Part Brand Name</j:ConveyancePartBrandName>
<j:ConveyancePartCategoryText>Part Category</j:ConveyancePartCategoryText>
</j:ConveyancePart>
<n2-yr:Confirmation>
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText>
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText>
<n2-yr:ConfirmingAgency>
<nc:OrganizationName>NLETS</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID>
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID>
</nc:FullTelephoneNumber>
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText>
</nc:ContactTelephoneNumber>
<nc:ContactEntity>
<nc:EntityPerson>
<nc:PersonName>
<nc:PersonFullName>John D Smith</nc:PersonFullName>
</nc:PersonName>
</nc:EntityPerson>
</nc:ContactEntity>
</nc:OrganizationPrimaryContactInformation>
</n2-yr:ConfirmingAgency>
<n2-yr:Remarks>Remarks</n2-yr:Remarks>
</n2-yr:Confirmation>
</n2-yr:HitConfirmation>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Example 18: Hit Confirmation response for Stolen Security.
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText>
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime>
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
<nh2:MessageSendTime>08:55</nh2:MessageSendTime>
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="YR">
<n2-yr:HitConfirmation>
<n2-yr:QueryRequestActivity>
<n2-yr:RequestCategoryCode>SS</n2-yr:RequestCategoryCode>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE-1234</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>1957-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ActivityIdentification>
<nc:ActivityStatus>
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText>
</nc:ActivityStatus>
</nc:Incident>
<scr:NCICRecordID>W123456789</scr:NCICRecordID>
</n2-yr:QueryRequestActivity>
<nc:Securities>
<nc:ItemSerialIdentification>
<nc:IdentificationID>SER12345678</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Securities Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>2021-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ItemSerialIdentification>
<nc:ItemBrandName>Securities Brand</nc:ItemBrandName>
<nc:ItemCategoryText>Securities Category</nc:ItemCategoryText>
<nc:ItemMakeName>Securities Make</nc:ItemMakeName>
<nc:ItemModelName>Securities Model</nc:ItemModelName>
<nc:ItemModelYearDate>2001</nc:ItemModelYearDate>
</nc:Securities>
<n2-yr:Confirmation>
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText>
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText>
<n2-yr:ConfirmingAgency>
<nc:OrganizationName>NLETS</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID>
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID>
</nc:FullTelephoneNumber>
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText>
</nc:ContactTelephoneNumber>
<nc:ContactEntity>
<nc:EntityPerson>
<nc:PersonName>
<nc:PersonFullName>John D Smith</nc:PersonFullName>
</nc:PersonName>
</nc:EntityPerson>
</nc:ContactEntity>
</nc:OrganizationPrimaryContactInformation>
</n2-yr:ConfirmingAgency>
<n2-yr:Remarks>Remarks</n2-yr:Remarks>
</n2-yr:Confirmation>
</n2-yr:HitConfirmation>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Example 19: Hit Confirmation response for Stolen/Felony Vehicle.
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText>
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime>
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
<nh2:MessageSendTime>08:55</nh2:MessageSendTime>
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="YR">
<n2-yr:HitConfirmation>
<n2-yr:QueryRequestActivity>
<n2-yr:RequestCategoryCode>SV</n2-yr:RequestCategoryCode>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE-1234</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>1957-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ActivityIdentification>
<nc:ActivityStatus>
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText>
</nc:ActivityStatus>
</nc:Incident>
<scr:NCICRecordID>W123456789</scr:NCICRecordID>
</n2-yr:QueryRequestActivity>
<nc:Vehicle>
<nc:ItemSerialIdentification>
<nc:IdentificationID>ABC1234</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Item Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>2021-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ItemSerialIdentification>
<nc:ItemBrandName>BMW MANUFACTURER CORPORATION / BMW NORTH AMERICA</nc:ItemBrandName>
<nc:ItemCategoryText>PC</nc:ItemCategoryText>
<nc:ItemMakeName>BMW</nc:ItemMakeName>
<nc:ItemModelName>X3</nc:ItemModelName>
<nc:ItemModelYearDate>2011</nc:ItemModelYearDate>
<nc:VehicleIdentification>
<nc:IdentificationID>5UXWX7C5XMN0191BA</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>VIN Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>2021-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:VehicleIdentification>
</nc:Vehicle>
<n2-yr:Confirmation>
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText>
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText>
<n2-yr:ConfirmingAgency>
<nc:OrganizationName>NLETS</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID>
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID>
</nc:FullTelephoneNumber>
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText>
</nc:ContactTelephoneNumber>
<nc:ContactEntity>
<nc:EntityPerson>
<nc:PersonName>
<nc:PersonFullName>John D Smith</nc:PersonFullName>
</nc:PersonName>
</nc:EntityPerson>
</nc:ContactEntity>
</nc:OrganizationPrimaryContactInformation>
</n2-yr:ConfirmingAgency>
<n2-yr:Remarks>Remarks</n2-yr:Remarks>
</n2-yr:Confirmation>
</n2-yr:HitConfirmation>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Example 20: Hit Confirmation response for Wanted Person.
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://release.niem.gov/niem/niem-core/3.0/" xmlns:j="http://release.niem.gov/niem/domains/jxdm/5.1/" xmlns:scr="http://release.niem.gov/niem/domains/screening/3.1/" xmlns:n2-yr="http://www.nlets.org/niem/nlets-hit-confirmation/1.0" n2:version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>YR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS34</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS34</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>SAMPLEYR00</nh2:DocumentControlFieldText>
<nh2:MessageReceiveDate>11/15/2019</nh2:MessageReceiveDate>
<nh2:MessageReceiveTime>08:55</nh2:MessageReceiveTime>
<nh2:MessageSendDate>11/15/2019</nh2:MessageSendDate>
<nh2:MessageSendTime>08:55</nh2:MessageSendTime>
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
<nh2:SendMessageNumeric>00374</nh2:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="YR">
<n2-yr:HitConfirmation>
<n2-yr:QueryRequestActivity>
<n2-yr:RequestCategoryCode>WP</n2-yr:RequestCategoryCode>
<nc:Incident>
<nc:ActivityIdentification>
<nc:IdentificationID>CASE-1234</nc:IdentificationID>
<nc:IdentificationJurisdiction>
<nc:JurisdictionText>AZ</nc:JurisdictionText>
</nc:IdentificationJurisdiction>
<nc:IdentificationCategoryText>Incident Category</nc:IdentificationCategoryText>
<nc:IdentificationExpirationDate>
<nc:Date>1957-08-13</nc:Date>
</nc:IdentificationExpirationDate>
</nc:ActivityIdentification>
<nc:ActivityStatus>
<nc:StatusDescriptionText>Status Description</nc:StatusDescriptionText>
</nc:ActivityStatus>
</nc:Incident>
<scr:NCICRecordID>W123456789</scr:NCICRecordID>
</n2-yr:QueryRequestActivity>
<nc:Person>
<nc:PersonBirthDate>
<nc:Date>1981-08-07</nc:Date>
</nc:PersonBirthDate>
<nc:PersonName>
<nc:PersonGivenName>TEST</nc:PersonGivenName>
<nc:PersonMiddleName>MIDDLE</nc:PersonMiddleName>
<nc:PersonSurName>NAME</nc:PersonSurName>
<nc:PersonFullName>TEST MIDDLE NAME</nc:PersonFullName>
</nc:PersonName>
<nc:PersonSexText>M</nc:PersonSexText>
</nc:Person>
<n2-yr:Confirmation>
<nc:StatusDescriptionText>Y</nc:StatusDescriptionText>
<n2-yr:AdditionalHoursRequiredText>2</n2-yr:AdditionalHoursRequiredText>
<n2-yr:ConfirmingAgency>
<nc:OrganizationName>NLETS</nc:OrganizationName>
<nc:OrganizationPrimaryContactInformation>
<nc:ContactTelephoneNumber>
<nc:FullTelephoneNumber>
<nc:TelephoneNumberFullID>6233083500</nc:TelephoneNumberFullID>
<nc:TelephoneSuffixID>623</nc:TelephoneSuffixID>
</nc:FullTelephoneNumber>
<nc:TelephoneNumberCategoryText>Primary</nc:TelephoneNumberCategoryText>
</nc:ContactTelephoneNumber>
<nc:ContactEntity>
<nc:EntityPerson>
<nc:PersonName>
<nc:PersonFullName>John D Smith</nc:PersonFullName>
</nc:PersonName>
</nc:EntityPerson>
</nc:ContactEntity>
</nc:OrganizationPrimaryContactInformation>
</n2-yr:ConfirmingAgency>
<n2-yr:Remarks>Remarks</n2-yr:Remarks>
</n2-yr:Confirmation>
</n2-yr:HitConfirmation>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Legacy (DEPRECATED)
Hit Confirmation Legacy Specifications
This section provides Legacy formats and examples for Hit Confirmation queries and responses (YQ/YR).
The format for a YQ message is described below. Optional fields have been noted.
Note that NCIC formats for data fields are used whenever possible.
Query Formats
Entry | # Char. | Explanation |
---|---|---|
YQ. | 2 | Message type followed by a period. |
Message Header | 10-62 | Standard input message header, may include
control field and up to three 9 character ORIs. |
TXT | 3 | Fixed filed prefix to beginning of message. |
CR,LF,DEL | 3 | Control characters (optional). |
RTY/ | 4 | Prefix to identify request type. |
Request type | 2 | Request type:
|
RNO/ | 4 | Prefix to identify request number. |
Request Number | 1 | Must be 1, 2 or 3 followed by a period. |
PRI/ | 4 | Prefix to identify priority. |
Priority destination | 1 | Must be U (urgent) or R (routine) followed by a
period. |
OCA/ | 4 | Prefix to identify case number. |
Case number | 20 | Agency case number followed by a period. |
NIC/ | 4 | Prefix to identify NCIC number. |
NIC# | 10 | NCIC number followed by a period (insert "NONE"
in this field if YQ is going to Canada). |
AND ONE OF THE SETS OF DATA ELEMENTS BELOW: | ||
LIC/ | 4 | Prefix to identify license plate. |
License number | 1-10 | License number followed by a period. |
LIS/ | 4 | Prefix to identify license state (only valid on
Request type SL). |
License state | 2 | License state followed by a period. |
LIY/ (optional) | 4 | Prefix to identify license year (only valid on
Request type SL). |
License year | 2-4 |
License year followed by a period; 2 or 4 numeric
|
LIT/ (optional) | 4 | Prefix to identify license type (only valid on
Request type SL). |
License type | 2 | License type; 2 character designating type of
license followed by a period. |
AND/OR | ||
VIN/ | 4 | Prefix to identify VIN. |
Vehicle ID # | 1-20 | Vehicle ID # followed by a period. |
VYR/ (optional) | 4 | Prefix to identify vehicle year. |
Vehicle year | 2-4 | Vehicle year followed by a period. |
VMA/ (optional) | 4 | Prefix to identify vehicle make. |
Vehicle make | 2-4 | Vehicle make followed by a period (optional). |
OR | ||
NAM/ | 4 | Prefix to identify Name. |
Name | Max.30 | Name (last name, first name middle) followed by a
period. |
DOB/ | 4 | Prefix to identify date of birth. |
Date of birth | 6-8 | mmddyy or ccyymmdd followed by a period. |
SEX/ (optional) | 4 | Prefix to identify sex. |
Sex | 1 | Sex followed by a period. |
WNO/ (optional) | 4 | Prefix to identify warrant number. |
Warrant Number | 20 | Warrant number followed by a period. |
CTI/ (optional) | 4 | Prefix to identify Court ORI. |
Court ORI Number | 9 | Court ORI number followed by a period. |
OR | ||
SER/ | 4 | Prefix to identify Serial #. |
Serial # | 20 | Gun serial number followed by a period. |
CAL/ | 4 | Prefix to identify caliber. |
Caliber | 4 | Gun caliber followed by a period. |
MAK/ | 4 | Prefix to identify gun make. |
Make | 23 | Gun make followed by a period. |
MOD/ (optional) | 4 | Prefix to identify gun model. |
Gun model | 20 | Gun Model followed by a period. |
OR | ||
TYP/ | 4 | Prefix to identify Article type. |
Article type | 7 | Article type followed by a period. |
SER/ | 4 | Prefix to identify Serial number. |
Serial number | 20 | Serial number followed by a period. |
BRA/ (optional) | 4 | Prefix to identify Article brand. |
Brand | 6 | Article brand followed by a period. |
OR | ||
TYP/ | 4 | Prefix to identify Security type. |
Security type | 2 | Security type followed by a period. |
SER/ | 4 | Prefix to identify serial number. |
Serial number | 20 | Serial number followed by a period. |
DEN/ (optional) | 4 | Prefix to identify denomination. |
Denomination | 9 | Denomination followed by a period. |
OR | ||
REG/ | 4 | Prefix to identify boat registration number. |
Registration # | 8 | Boat registration number followed by a period. |
OR | ||
BHN/ | 4 | Prefix to identify Boat hull number. |
Boat hull number | 18 | Boat hull number followed by a period. |
AND | ||
BMA/ (optional) | 4 | Prefix to identify Boat make. |
Boat make | 24 | Boat make followed by a period. |
OR | ||
SER/ | 4 | Prefix to identify stolen part serial number. |
Serial number | 20 | Stolen part serial number followed by a period. |
BRA/ (optional) | 4 | Prefix to identify Brand name. |
Brand name | 4 | Brand name followed by a period. |
CAT/ (optional) | 4 | Prefix to identify Category. |
Category | 2 | Category followed by a period. |
AND | ||
RNA/ | 4 | Prefix to identify name of requester. |
Requester | 30 | Name of requester followed by a period. |
RAG/ | 4 | Prefix to identify Requesting agency. |
Requesting agency | 60 | Requesting agency name followed by a period. |
PHO/ (optional) | 4 | Prefix to identify phone number. |
Phone number | 10 | Phone number followed by a period. |
EXT/ (optional) | 4 | Prefix to identify extension number. |
Extension # model | 4 | Extension number followed by a period. |
FAX/ (optional) | 4 | Prefix to identify FAX number. |
FAX number | 10 | FAX number followed by a period. |
REM/ (optional) | 4 | Prefix to identify Remarks field. |
Remarks | =<500 | Remarks field. (.) are not allowed in the remarks field.
Must be used when the confirmation status if Pending. |
Response Formats
The format for a YR message is described below. Note that NCIC formats for data fields are used whenever possible. Optional fields are noted. All other fields are required.
Entry | # Char. | Explanation |
---|---|---|
YR. | 2 | 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 (optional) | 3 | Control characters. |
RTY/ | 4 | Prefix to identify request type. |
Request type | 2 | Request type:
|
CON/ | 4 | Prefix to identify confirmation status number. |
Confirmation status | 1 | Confirmation status:
|
HRS/ | 4 | Prefix to identify Hours to complete confirmation. |
Hours for confirmation | 3 | Hours to complete confirmation of record: required
when CON = "E" or "P". Followed by a period. |
OCA/ | 4 | Prefix to identify case number. |
Case number | 20 | Agency case number followed by a period. |
NIC/ | 4 | Prefix to identify NCIC number (not required for YQs
to Canada). |
NIC# | 10 | NCIC number followed by a period. |
AND ONE OF THE SETS OF DATA ELEMENTS BELOW:
Type of Record | Description | Optional |
---|---|---|
stolen/felony vehicle |
License plate (LIC/).and/or
|
Vehicle Year (VYR/), Vehicle
Make (VMA/) |
wanted person | Name (NAM/) Date of Birth
(DOB/) |
Sex (SEX/) |
protection order | Name (NAM/) Date of Birth
(DOB/) |
Sex (SEX/) |
missing person | Name (NAM/) Date of Birth
(DOB/) |
Sex (SEX/) |
stolen license plate | License plate (LIC/) and
License state (LIS/) |
License Year (LIY/) License
Type (LIT/) |
stolen gun | Serial Number(SER/), Caliber
(CAL/), Make (MAK/) |
Model (MOD/) |
stolen article | Type (TYP/) Serial Number
(SER/) |
Brand (BRA/) |
stolen security | Type (TYP/) Serial
Number (SER/) |
Denomination (DEN/) |
stolen boat | Registration (REG/) or Boat Hull
Number (BHN/) |
Boat Make (BMA/) |
stolen part | Serial Number (SER/) | Brand (BRA/), Category (CAT/) |
FOLLOWED BY:
Entry | # Char. | Explanation |
---|---|---|
CNA/ | 4 | Prefix to identify name of individual confirming the
record. |
Name | Max.30 | Name of Confirmer followed by a period. |
CAG/ | 4 | Prefix to identify name of confirming agency. |
Confirming agency | Max.30 | Name of confirming agency followed by a period. |
PHO/ (optional) | 4 | Prefix to identify phone number of confirming
agency. |
Phone number | 10 | Phone number of confirming agency followed by a
period. |
EXT/ (optional) | 4 | Prefix to identify extension number. |
Extension # | 4 | Extension # followed by a period. |
FAX/ (optional) | 1 | Prefix to identify Fax number. |
FAX number | 10 | Confirming agencies FAX number followed by a
period. |
REM/ (optional) | 4 | Prefix to identify remarks field. |
Remarks | =<500 | Free form Remarks field.
Must be used when the confirmation status is Pending. |
Hit Confirmation Legacy Examples
Example 1: Hit Confirmation query by Plate.
YQ.AZNLETS20.AZ0000000.TXT
|
---|
Example 2: Hit Confirmation query by VIN.
YQ.AZNLETS20.AZ0000000.TXT
|
---|
Example 3: Hit Confirmation query by name and date of birth.
YQ.AZNLETS20.AZ0000000.TXT
|
---|
Example 4: Hit Confirmation query on firearm.
YQ.AZNLETS20.AZ0000000.TXT
|
---|
Example 5: Hit Confirmation query on article.
YQ.AZNLETS20.AZ0000000.TXT
|
---|
Example 6: Hit Confirmation query on security.
YQ.AZNLETS20.AZNLETS19.TXT
|
---|
Example 7: Hit Confirmation query on a boat by registration.
YQ.AZNLETS20.AZ0000000.TXT
|
---|
Example 8: Hit Confirmation query on a boat by boat hull number.
YQ.AZNLETS20.AZ0000000.TXT
|
---|
Example 9: Hit Confirmation query on vehicle part.
YQ.AZNLETS20.AZ0000000.TXT
|
---|
Example 10: Hit Confirmation response.
YR.AZ0000000
|
---|
Downloads
File | Last Updated |
---|---|
Download YQ Schema | 10/8/2020 |
Download YQ Stylesheet | 4/6/2023 |
Download YQ Stylesheet with Caveats | 7/11/2023 |
Download YR Schema | N/A |
Download YR Stylesheet | 3/09/2023 |