General Information - Hit Confirmation Transactions (YQ/YR)

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 an agency 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(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
a suspect, or the nature of a case requires urgent confirmation of a hit,
the highest level of priority is specified.

Routine R Within 1 hour

Generally, this will be used when the person or property is being
held on local charges or when an urgent confirmation is not required.

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
well as the destination agency's control terminal ORI. (which is usually a generic ORI
of "ssHITC000" where ss = 2-character state/agency code)

RNO is "3" "FIRST" will be replaced by "THIRD"

The message will be addressed to the given destination, the
destination agency control terminal ORI (generic) and NCIC (DCFBIWA00).

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">
    
    <n2:Recipients> 
      <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
(Replace "SV"
with specified
request type.)

2 2-character code

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

<nc:QueryRequestActivity>
   <n2:QueryRequestSequenceNumber>X</n2:QueryRequestSequenceNumber>
</nc:QueryRequestActivity>

RNO/ 1 Must be 1, 2 or 3 Sequence or 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
(only valid on Request type SL)
(optional)

<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
(only valid on Request type SL)
(optional)

<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).