General Information - Criminal History Record Information Transactions (CHRI/CCH) (IQ/IR, FQ/FR, AQ/AR & CR)
Criminal History Record Information Transactions (CHRI) (IQ/IR, FQ/FR, AQ/AR & CR)
This section describes how Nlets users may acquire Criminal History Record Information (CHRI) and CHRI-related information from state and local law enforcement and criminal justice agencies with a standardized, secure and efficient method.
This capability allows states that have automated criminal history systems to respond automatically (without manual intervention) to requests from other states over Nlets. Those states without automated systems should respond manually.
The Nlets inquiries are used to retrieve criminal history records that are not presently available on NCIC's Triple I system. They should never be used as a substitute for the Triple I system, but rather as a secondary inquiry after the user has:
- Inquired on the Triple I system and received a no record; or
- Received a record but feels that there may be additional data on the state file.
Users may also access criminal records from the Canadian Police Information Centre using the IQ/FQ and an address of "CN". "AQs" may also be sent to Canada.
See critical reference document "Interstate Criminal History Transmission Specification" (revised November, 2002) for additional information.
Documentation for the Rapsheets (version 4.0 and 4.1) are available from the Downloads page.
CHRI Inquiries / CHRI Responses
This section provides an overview and details regarding the CHRI Query by using three types of queries, IQ, FQ and AQ, and the corresponding responses, IR, FR and AR. Triple I Responses from NCIC (CR) are included at the end of this section.
Multi-State Query Functionality
Nlets supports the Multi-State Query functionality for the IQ message format. This functionality allows the inquiry to be automatically sent to all states that participate in the message type and returns a single merged response.
In order to send a Identity Query transaction using the Multi-State Query, the inquiry should be sent in its typical format to the destination NL. Nlets will take this query and send it to ALL states that support the IQ message key. Nlets then collects all relevant responses to this query, merges them together while suppressing the NO HIT responses, and sends them onto the querying user as a single response. These responses will also contain summary data indicating which states this query was sent to, which states responded with hits, which responded with no hits, and which states did not respond at all.
States receiving legacy text or GJXDM formats will see the summary data and state responses in a flattened text format (wrapped in XML for GJXDM), whereas states receiving responses in NIEM will receive the summary and state responses in a standardized XML structure detailed below.
An important detail to note is that if a response is received after Nlets has forwarded on the merged Multi-State response, the late response will be sent individually to the original user. This would be most likely to occur if a participating state happened to be 'down' at the time of the inquiry but came back up at a later time and responded.
Overview
Generally the Identity Query (IQ) will be used to request identification information on a subject using three different indices: Name, Social Security Number (SS#) or Miscellaneous Number (MNU). There are five combinations of the inquireable data elements that may be sent by the requestor.
Response(s) will be returned and the requestor will select the desired record and submit a Full Record Query (FQ) on the state identification number (SID). The corresponding response (FR) will return the full record on file.
The AQ Query will be used to request supplemental information not available through the normal IQ/FQ or to request information from a local agency. This is a general free-form request for CHRI when all required data is not available.
Purpose Codes
The NCIC/Nlets purpose codes are located at the bottom of the Introduction Page (Introductory Information | Knowledge Base | Nlets (freshservice.com))
Query Help
- To obtain explanatory or supplementary information on a state's Criminal History Records, a user may send an Administrative Message to xxSIRHELP (where xx = 2 character state code).
- A user may determine who is providing automated responses to Criminal History Records by sending an Administrative Message to "NLSIRHELP".
More information on help files can be located in Help File Transactions.
Identity Query (IQ/IR)
The sections that follow describe requirements for the Identity Query and Response.
Query Requirements (IQ)
- Identity Query (IQ) messages may be sent to up to five 2-character state codes.
- Full nine-character destination ORIs will cause rejection of the entire message.
- All Identity Queries (IQs) should be answered by an Identity Response (IR) from the destination. However, if a state returns a full record, they may use a Full Record Response (FR).
- It is recommended that states leverage the JTF Interstate Criminal History Rapsheet where applicable.
- If one uses a format with more than one index (i.e., Name/Date of Birth and Social Security Number or Name/Date of Birth and Miscellaneous Number) the responder should indicate which search element was used to search the file and which one, if any, produced the hit.
- Identity Queries (IQs) sent to Canada may only include Name, Date of Birth and Sex.
- Race code is optional. However, when used, Nlets recommends that all states use NCIC's standard race codes. Those states who do not use standard race codes should, on incoming Identity Queries (IQs), adjust incoming race codes to match their race codes so that accurate searches are made of their state files.
- If one wishes to request CHRI information on a subject and does not have a full date of birth or a Miscellaneous or Social Security Number, the AQ Query message type should be used.
- If one of the three indices is available, IQ should always be utilized.
Codes used as input and/or output generally match NCIC formats and content. Please refer to Part II of your NCIC Manual for code translation and instruction.
The table that follows describes field requirements for Criminal History Identity (IQ) Queries.
XML Tag:
Legacy
Prefix:
Field Size:
Data Requirements:
Translation:
PUR/
1
Must be A,C, D, E,
F, H, I, J, R, S, V or X
Purpose Code (Optional)See Introduction Page
for more information.
<n2:ResponseAttentionDescriptionText>
(Optional)
<j4:Person>
<nc:PersonName>
<nc:PersonFullName>For Legacy full name:
format is last name,
comma, (space after
comma is optional),
first name, space, middle
initial or name, space,
suffix (Jr., III, etc.)
Titles or degrees should
not be used as part of the
name.
<j4:Person>
<nc:PersonBirthDate>
<nc:Date>Date of Birth. Complete
DOB must be present.
Some states have
different requirements.
Check on their OLN HELP
file for details.
<j4:Person>
<nc:PersonRaceText>
NCIC codes
Race code (Optional)
<j4:Person>
<nc:PersonSexCode>
to NCIC codes
Sex
<j4:Person>
<nc:PersonSSNIdentification>
<nc:IdentificationID>
(Optional)
<j4:Person>
<nc:PersonOtherIdentification>
<nc:IdentificationID>
(Optional)
Response Requirements (IR)
- All Identity Queries (IQs) should be answered by an Identity Response (IR) from the destination. However, if a state returns a full record, they may use a Full Record Response (FR).
- IR formats may include inquiry data received in the IQ.
- It is recommended that states leverage the JTF Interstate Criminal History Rapsheet where applicable.
- It is anticipated that states will respond with a single or multiple identity segments.
- The requestor will then submit a record request using the Full Record Query (FQ) to request the record by SID or FBI number. This is similar to the Triple I application.
- To avoid receiving multiple inquiries, a state that does not reply with an automated response should provide an interim message (ideally, computer generated) that will notify the requestor that the response will be delayed until a manual search can be conducted.
- The interim message should include the text of the inquiry received.
- States should use the sending ORI of "xxSIR0000" (where xx = sending state code) for all IR messages.
Full Record Query (FQ/FR)
The purpose of this query is to retrieve a full record from a state. Normally this message will be used after an IQ has been sent and the requestor has reviewed the hits and made a selection.
Query Requirements (FQ)
- Only a single 2-character state code is allowed as the destination because this is a query by a specific State Identification Number (SID).
- FQs sent to Canada will use the FPS number rather than the SID.
- The State Identification Number (SID), Purpose (PUR) and Attention (ATN) fields are always required.
- The mailing address fields are optional.
- If the address fields are present, all address fields must be present, except for BLD (BLD is optional).
- Utilize the Image Flag (IMQ/Binary Request Indicator) to request the images associated with the record.
Response Requirements (FR)
- This message type must be used to respond to all FQ queries.
- Full Record response (FR) formats must include all inquiry data received in the FQ.
- To avoid receiving multiple inquiries, a state that does not reply with an automated response should provide an interim message (ideally computer generated) that will notify the requester that the response will be delayed until a manual search can be conducted.
- The interim message should include the inquiry data received.
- States should use the sending ORI of xxSIR0000 (where xx = sending state code) for all FR messages.
- It is recommended that states leverage the JTF Interstate Criminal History Rapsheet format when applicable.
Additional Query (AQ/AR)
The purpose of the AQ is to request supplemental or other information not available through the normal IQ or FQ queries.
This includes requests for mailed records, photos, F/P cards, dispositions, special handling of the inquiry, inquiry when only a partial DOB is known, etc.
This message may also be used to request information from a local agency.
Query Requirements (AQ)
- This message is a controlled free form message.
- An AQ may be addressed to multiple 2-character or 9 character ORIs.
- When sending an AQ, only one subject per message is allowed.
- An AQ should never be used to access criminal record information from a state bureau when adequate data for an IQ or FQ is available.
- When using an AQ to request additional information, use person descriptors (i.e., name/sex) with other relevant data (i.e., case#, booking #, SID, MNU), followed by a free text request.
- If a mailing response is anticipated, include a complete mailing address.
XML Tag:
Legacy
Prefix:
Field Size:
Data Requirements:
Translation:
PUR/
1
Must be A, C, D, E,
F, H, I, J, R, S, V or X
Purpose Code (Optional)See Introduction Page
for more information.
<n2:ResponseAttentionDescriptionText>
(Optional)
<n2:InquiryDescriptionText>
<![CDATA[
char
No special format
used
Free text
Response Requirements (AR)
- This message type should be used to respond to all AQs. AR messages must include the purpose code and requester (ATN data) that were received in the AQ.
- Since this is a response to a non-standard or special request, the format is at the discretion of the sender, provided it adheres to basic Nlets rules for message transmission.
CR Responses
This message type will only be used as a response to a Triple I record request.
- CR messages will include the letters "III" as the 3rd, 4th and 5th characters in the responder's ORI. The remainder of the format will be at the discretion of the sending state.
- It is recommended that states leverage the JTF Interstate Criminal History Rapsheet format when applicable.
- CR messages should not be used for responses to CHRI or related requests over Nlets. This is the purpose of the IR, FR and AR message types.
- The NCIC header (HDR) must be included in a CR.
Interstate Identification Index (Triple III)
This application involves the utilization of a national index housed at the FBI CJIS Division and state criminal history files.
- To obtain criminal history data using Triple I, inquire into the index over NCIC (QH), by name and the personal identifiers.
- Following receipt of a response from the national index, submit a NCIC record request (QR) to NCIC on FBI # or SID # for the record.
- NCIC will pass this request to the state of record who will normally respond via Nlets. This response will be a CR type message.
- Triple I responses over Nlets will have the letters "III" in the 3rd, 4th, and 5th characters of the sender ORI.
- When accessing records from participating states, users will be receiving Triple I responses from them containing this unique ORI.
If you realize a hit on a record from a non-participating state, a record that a state has not taken responsibility for, a Federal offender file record, or, a record as a result of an arrest in a foreign country; a response will be forthcoming from Triple I over NCIC. Under the above conditions, no response will be received over Nlets.
For further information on this application, contact:
Criminal Justice Information Services Division
Federal Bureau of Investigation
1000 Custer Hollow Road
Clarksburg, WV 26306
Phone: (304) 625-3652
Parsed Triple I and Full Record Response Messages
Nlets provides the option for users to receive fully tagged NIEM formatted Triple I NCIC Responses and Full Record Responses from all states via our message parsing service. CR and FR messages destined to an individual terminal or an entire state can be redirected to the Message Parsing Service to be converted to a Parsed Response. The parsing service changes the message key of CR messages to PII and FR messages to PFR.
The Parsed Response is structured similarly to a standard Response with the addition of some parsing related elements and the removal of some cardinalities and enumerations.
The parsing service constructs the PII/PFR response message as follows:
- If the original message (CR or FR) is in Legacy Text format, the parsing service converts the text into fully tagged XML and includes the original text content in an OriginalTextResponse element.
- If the original message (CR or FR) is in fully tagged XML format, the parsing service will leave the XML as-is, but will also transform the XML into Legacy Text and place the contents in an OriginalTextResponse element.
- In this way, parsed response messages have both machine readable and human readable content.
The parsing service can be setup to parse all statewide CRs/FRs or to parse CRs/FRs for any number of individual ORIs.
To leverage this service or for more information, contact the Nlets Control Center at 1-800-528-4020.