Section 15: Criminal History Record Information Transactions (CHRI)
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.
Below are the Rapsheets for version 4.0 and 4.1. The files can be displayed by clicking on the links or downloaded by right-clicking and selecting "Save As...".
Rap_V4.1_Element_Dictionary_December_2011 (PDF)
Rapsheet V4.1 SpecificationDetailedStructure (PDF File)
Rapsheet V4.1 Data Model (PDF File)
Rapsheet V4.1 Schemas (Zip File)
Rapsheet V4.0 Full Documentation August 2009 (PDF File)
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 query to be automatically sent to all states that participate in the message type and returns a single merged response.
In order to send a Identity Query transaction using the Multi-State Query, the query should be sent in its typical format to the destination NL. Nlets will take this query and send it to ALL states that support the 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 query 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 in Section 1.6 of the Introduction Page.
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: |
---|---|---|---|---|
<n2:PurposeCode>
|
PUR/ | 1 | Must be C, F,
E, D, J or S |
Purpose Code (Optional) for more information. |
<n2:ResponseAttentionDescriptionText>
|
ATN/ | 30 | See NCIC Manual | Name of Requester
(Optional) |
<j4:Person>
<nc:PersonName>
<nc:PersonFullName>
|
NAM/ | Max. 30 | Alpha Characters |
For Legacy full name:
|
<j4:Person>
<nc:PersonBirthDate>
<nc:Date>
|
DOB/ | 8 | ccyy-mm-dd |
Date of Birth. Complete
|
<j4:Person>
<nc:PersonRaceText>
|
RAC/ | 4 | Conforms to
NCIC codes |
Race code (Optional) |
<j4:Person>
<nc:PersonSexCode>
|
SEX/ | 1 | M or F; Conforms
to NCIC codes |
Sex |
<j4:Person>
<nc:PersonSSNIdentification>
<nc:IdentificationID>
|
SOC/ | 9 | See NCIC manual | Social Security Number
(Optional) |
<j4:Person>
<nc:PersonOtherIdentification>
<nc:IdentificationID>
|
MNU/ | 15 | See NCIC manual | Miscellaneous Number
(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.
- There are two required fields: Purpose (PUR) and Attention (ATN).
- 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: |
---|---|---|---|---|
<n2:PurposeCode>
|
PUR/ | 1 | Must be C, F,
E, D, J or S |
Purpose Code (Optional) for more information. |
<n2:ResponseAttentionDescriptionText>
|
ATN/ | Max. 30 | See NCIC Manual | Name of Requester
(Optional) |
<n2:InquiryDescriptionText>
<![CDATA[
|
Free Text | Max 14,400
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
|
---|
GJXDM (DEPRECATED)
GJXDM has been deprecated. Please contact Nlets for additional assistance with GJXDM.
NIEM
Criminal History NIEM Specifications
This section describes the format and provides examples for Criminal History Record Information (CHRI) queries using three query types (IQ, FQ, AQ) and the corresponding responses (IR, FR, AR). Triple I Responses from NCIC (CR) are included at the end of this section.
CHRI Query and Response Descriptions (IQ/FQ/AQ and IR/FR/AR)
Identity Query (IQ) |
Generally the Identify Query (IQ) is used to request identity information on a
|
---|---|
Full record query (FQ) |
A full record query (FQ) is used to retrieve a full record from a state.
|
Additional query (AQ) |
An additional query (AQ) is used to request supplemental or other information
|
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: Identity Query by Name, DOB, Sex (IQ), Full Record Query by SID (FQ), Additional Response Query (AQ), Response in Free Text (IR,FR,AR,CR) and Standardized Rapsheet Response (FR,CR).
Query Formats
Identity Query by Name, DOB and Sex (IQ)
n2:NLETSInquiryData
This element will contain all elements specific to this transaction.
n2:PurposeCode
This element identifies the reason for query.
Valid values are: C, F, E, D, J or S
n2:ResponseAttentionDescriptionText
This element contains identification of the person or entity to whose attention the response will be directed.
This element contains identification of the person or entity to whose attention the response will be directed.
j4:Person
Applied augmentation for type nc:PersonType
nc:PersonBirthDate
A date a person was born.
nc:Date
A full date.
This element contains the DOB for the person being queried on. This data in this element must be in xsd:date
format, that is: yyyy-mm-dd.
nc:PersonName
A combination of names and/or titles by which a person is known.
nc:PersonGivenName
A first name of a person.
This optional element containing a person's first name may be sent via XML if available but will only be forwarded
onto states receiving XML.
nc:PersonMiddleName
A middle name of a person.
This optional element containing a person's middle name may be sent via XML if available but will only be
forwarded onto states receiving XML.
nc:PersonSurName
A last name or family name of a person.
This optional element containing a person's last name may be sent via XML if available but will only be forwarded
onto states receiving XML.
nc:PersonFullName
A complete name of a person.
This required element must contain the full name of the person in the format LAST,FIRST MIDDLE. The data from
this element is the only name data that will be passed onto states receiving text.
nc:PersonOtherIdentification
Information about an identifier with a kind that is not explicitly defined in the standard that refers to a person within a
certain domain. Cannot be used with nc:PersonSSNIdentification.
nc:IdentificationID
A value that identifies something.
Optional containing miscellaneous number. (MNU)
nc:PersonRaceText
A classification of a person based on factors such as geographical locations and genetics.
Optional element conforming to NCIC race codes.
nc:PersonSexCode
A gender or sex of a person.
Value must be M, F or U.
nc:PersonSSNIdentification
A unique reference to a living person; assigned by the United States Social Security Administration. Cannot be used with nc:PersonOtherIdentification.
nc:IdentificationID
A value that identifies something.
Optional element containing SSN.
Full Record Query by SID (FQ)
n2:NLETSInquiryData
This element will contain all elements specific to this transaction.
n2:PurposeCode
This element identifies the reason for query.
This element contains a code indicating the purpose for which the record is being requested. Valid values are:
C, F, E, D, J, I, S or X.
n2:ResponseAttentionDescriptionText
This element contains identification of the person or entity to whose attention the response will be directed.
n2:Person
A person
This element encapsulates the information about the person being queried.
j4:PersonAugmentation
Additional information about a person.
j4:PersonStateFingerprintIdentification
An identifier assigned to a person by a state identification bureau, generally based on submission of the person's
fingerprints to the state's Automated Fingerprint Identification System (AFIS).
nc:IdentificationID
A value that identifies something.
This element will contain the SID number of the person being queried on.
nc:Location
Details about a physical location.
nc:LocationAddress
A geophysical location described by postal information.
nc:StructuredAddress
An address.
nc:AddressBuildingText
A physical structure at an address.
This always-optional element contains the building name.
nc:AddressSecondaryUnitText
A particular unit within a larger unit or grouping at a location.
This conditional element contains the department.
nc:LocationStreet
A road, thoroughfare or highway.
nc:StreetFullText
A complete reference for a street.
This conditional element contains the street address.
nc:LocationCityName
A name of a city or town.
conditional element contains the city.
nc:LocationStateName
A state, commonwealth, province, or other such geopolitical subdivision of a country.
This conditional element contains the state name.
nc:LocationPostalCode
An identifier of a post office-assigned zone for an address.
This conditional element contains the postal code, or zip code.
Additional Response Query (AQ)
n2:NLETSInquiryData
This element will contain all elements specific to this transaction.
n2:PurposeCode
This element identifies the reason for query.
n2:ResponseAttentionDescriptionText
This element contains identification of the person or entity to whose attention the response will be directed.
n2:InquiryDescriptionText
This element contains free text. Include personal descriptors (name, sex) with other relevant data (case number, booking
number, state ID, miscellaneous number) followed by any additional free text.
This element contains free text. Include personal descriptors (name, sex) with other relevant data (case number,
booking number, state ID, miscellaneous number) followed by any additional free text.
Response Formats
Rapsheet Response in Free Text (IR,AR,FR,CR)
n2:NLETSResponseData
n2:ResponseText
This element will contain the free text response. Nlets recommends the use of
<![CDATA[]]>
tags to ensure that the
response does not contain any characters illegal in XML.
Standardized Criminal History Rapsheet Response (FR,CR)
Response Data (n2:NLETSResponseData)
This element will contain all elements specific to this transaction.
rap:RapSheet
This element will contain the standardized criminal history rapsheet response as defined in the Joint Task Force
Standardized Criminal History XML Specifications; Nlets supports v3.0.X, 4.0 & 4.1. Please refer to JTF specifications for more details.
Criminal History NIEM Examples
Example 1: Identity query by name, date of birth and sex.
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>IQ</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZ</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>
<![CDATA[NN11111111]]>
</nh2:DocumentControlFieldText>
</n2:NLETSMessageHeader>
<n2:NLETSInquiryData n2:key="IQ">
<n2:PurposeCode>C</n2:PurposeCode>
<n2:ResponseAttentionDescriptionText>HELP DESK</n2:ResponseAttentionDescriptionText>
<j4:Person xmlns:j4="http://niem.gov/niem/domains/jxdm/4.1">
<nc:PersonName>
<nc:PersonFullName>SMITH, JOHN</nc:PersonFullName>
</nc:PersonName>
<nc:PersonBirthDate>
<nc:Date>1950-01-01</nc:Date>
</nc:PersonBirthDate>
<nc:PersonSexCode>M</nc:PersonSexCode>
</j4:Person>
</n2:NLETSInquiryData>
</n2:NLETS>
|
---|
Example 2: Full Record query by SID.
<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>FQ</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS45</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZ</nh2:DestinationORIID>
</n2:NLETSMessageHeader>
<n2:NLETSInquiryData n2:key="FQ">
<n2:PurposeCode>C</n2:PurposeCode>
<n2:ResponseAttentionDescriptionText>NLETS_ANALYST</n2:ResponseAttentionDescriptionText>
<n2:Person>
<j:PersonAugmentation xmlns:j="http://niem.gov/niem/domains/jxdm/4.1">
<j:PersonStateFingerprintIdentification>
<nc:IdentificationID>AZ11111111</nc:IdentificationID>
</j:PersonStateFingerprintIdentification>
</j:PersonAugmentation>
<n2:PersonFPSIdentification />
</n2:Person>
</n2:NLETSInquiryData>
</n2:NLETS>
|
---|
Example 3: Additional query.
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.nlets.org/niem/1.0 ../xsd/AQ.xsd" version="4.00">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>AQ</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS45</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZ</nh2:DestinationORIID>
</n2:NLETSMessageHeader>
<n2:NLETSInquiryData n2:key="AQ">
<n2:PurposeCode>C</n2:PurposeCode>
<n2:ResponseAttentionDescriptionText>SGT JOHN DOE</n2:ResponseAttentionDescriptionText>
<nc:Person>
<nc:PersonBirthDate>
<nc:Date>1950-01-01</nc:Date>
</nc:PersonBirthDate>
<nc:PersonGeneralAppearanceDescriptionText>
6'0", 220 LBS., BROWN HAIR
</nc:PersonGeneralAppearanceDescriptionText>
<nc:PersonName>
<nc:PersonFullName>JOHN Q. PUBLIC</nc:PersonFullName>
</nc:PersonName>
<nc:PersonOtherIdentification/>
<nc:PersonStateIdentification/>
</nc:Person>
<n2:ImageIndicator>false</n2:ImageIndicator>
<n2:InquiryDescriptionText>PLEASE SEARCH YOUR FILES FOR SUBJECT</n2:InquiryDescriptionText>
</n2:NLETSInquiryData>
</n2:NLETS>
|
---|
Example 4: Identity response in free text form.
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:rap41="http://nlets.org/niem2/rapsheet/1.0" xmlns:nist="http://niem.gov/niem/ansi-nist/2.0" xmlns:j4="http://niem.gov/niem/domains/jxdm/4.1" xmlns:n2="http://www.nlets.org/niem/1.0">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>IR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZSIR0000</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS45</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>
<![CDATA[1234567890]]>
</nh2:DocumentControlFieldText>
<nh2:MessageReceiveDate>11/13/2019</nh2:MessageReceiveDate>
<nh2:MessageReceiveTime>13:32</nh2:MessageReceiveTime>
<nh2:MessageSendDate>11/13/2019</nh2:MessageSendDate>
<nh2:MessageSendTime>13:32</nh2:MessageSendTime>
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
<nh2:SendMessageNumeric>00001</nh2:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="IR">
<n2:ResponseText>THIS IDENTIFICATION INFORMATION IS IN RESPONSE TO YOUR INQUIRY ON:
PUR/C.ATN/NLETS_ANALYST.NAM/SMITH,JOHN.DOB/19500101.SEX/M.RAC/U
* * * MATCHED RECORD * * *
SID/123456 FBI/234567890
NAME/SMITH,JOHN DOB/19500101 SEX/M RACE/W
ADR/1234 ANY STREET PHOENIX AZ 85000
EYE/BRO HAIR/BRO WGT/200 HGT/510 POB/AZ SOC/123456789
DATA TO BE USED ONLY FOR CRIMINAL JUSTICE OR OTHER LAWFUL PURPOSES.
</n2:ResponseText>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Example 5: Full Record response in free text form.
<n2:NLETS version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>FR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZSIR0000</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS43</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>NN38970221</nh2:DocumentControlFieldText>
<ns6:MessageReceiveDate>2019-11-14</ns6:MessageReceiveDate>
<ns6:MessageReceiveTime>10:49:24</ns6:MessageReceiveTime>
<ns6:MessageSendDate>2019-11-14</ns6:MessageSendDate>
<ns6:MessageSendTime>10:49:24</ns6:MessageSendTime>
<ns6:ReceiveMessageNumeric>00000</ns6:ReceiveMessageNumeric>
<ns6:SendMessageNumeric>37062</ns6:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="FR">
<n2:ResponseText>
<![CDATA[ PUR/C.ATN/NLETS_ANALYST.SID/AZ1111111 SID: AZ1111111 PAGE 1 OF 1
REQUESTED BY:
STATE OF ARIZONA
*FOR USE BY AUTHORIZED CRIMINAL JUSTICE AGENCIES ONLY*
(FINGERPRINTS ARE NECESSARY FOR A POSITIVE ID)
INVESTIGATIVE REPORT CONFIDENTIAL RECORDS
----------------
CRIMINAL RECORD OF: SMITH, JOHN FBI: 3456789012
STATE ID: 1111111 BIRTH DATE: 01/01/1950 PLACE: AZ DOC:
RACE: W HEIGHT: 5'8" HAIR: BRO DNA ON FILE:NO
SEX: M WEIGHT: 160 EYES: BRO
SSN: 123456789 OLS/OLN: III: SSO
STATUS:
----------------
ALIASES SSN OLS/OLN ID THEFT
SMITH, JOHNNY 123456789
----------------
SUMMARY
DATE AGENCY TEXT
10/10/2000 GLENDALE, AZ PD ARRESTED, ATN: 000000000001
----------------
ARREST DATE: 10/10/2011 LID: 00000001
AGENCY: GLENDALE, AZ PD (AZ00000001) AFIS ATN: 000000000001
NAME: SMITH, JOHN
CHARGE 1 GLENDALE, AZ PD COUNTS 2
R.S. 14:63 CRIMINAL TRESPASS
CHARGE 2 GLENDALE, AZ PD COUNTS 2
R.S. 14:62.3 UNAUTHORIZED ENTRY OF AN INHABITED DWELLING
CHARGE 3 GLENDALE, AZ PD COUNTS 2
R.S. 14:67(FELONY) THEFT
CHARGE 4 GLENDALE, AZ PD COUNTS 2
R.S. 14:26 CRIMINAL CONSPIRACY
----------------
THE RESPONSE TO YOUR REQUEST FOR CRIMINAL HISTORY RECORD CHECK IS
BASED ON A REVIEW OF THE STATE OF ARIZONA'S CRIMINAL HISTORY RECORDS
DATABASE ONLY. THIS DOES NOT PRECLUDE THE EXISTENCE OF A RECORD IN A
LOCAL AGENCY, ANOTHER STATE, OR THE FBI CJIS DIVISION.
** END OF RAPSHEET **]]>
</n2:ResponseText>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Example 6: Aditional response in free text form.
<n2:NLETS version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>AR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZSIR0000</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS43</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>NN38970221</nh2:DocumentControlFieldText>
<ns6:MessageReceiveDate>2019-11-14</ns6:MessageReceiveDate>
<ns6:MessageReceiveTime>10:49:24</ns6:MessageReceiveTime>
<ns6:MessageSendDate>2019-11-14</ns6:MessageSendDate>
<ns6:MessageSendTime>10:49:24</ns6:MessageSendTime>
<ns6:ReceiveMessageNumeric>00000</ns6:ReceiveMessageNumeric>
<ns6:SendMessageNumeric>37062</ns6:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key=AR">
<n2:ResponseText>
<![CDATA[
PUR/C.ATN/NLETS_ANALYST.
PHOENIX PD
PER REQUEST ON SMITH, JOHN
COMPLAINT FILED AGAINST HIM ON 12/01/01 FOR DOMESTIC
BATTERY]]>
</n2:ResponseText>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Example 7: Triple I response in free text form.
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:rap41="http://nlets.org/niem2/rapsheet/1.0" xmlns:nist="http://niem.gov/niem/ansi-nist/2.0" xmlns:j4="http://niem.gov/niem/domains/jxdm/4.1" xmlns:n2="http://www.nlets.org/niem/1.0">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>CR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>OHIII0000</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS43</nh2:DestinationORIID>
<ns6:MessageReceiveDate>2019-11-14</ns6:MessageReceiveDate>
<ns6:MessageReceiveTime>10:49:24</ns6:MessageReceiveTime>
<ns6:MessageSendDate>2019-11-14</ns6:MessageSendDate>
<ns6:MessageSendTime>10:49:24</ns6:MessageSendTime>
<ns6:ReceiveMessageNumeric>00000</ns6:ReceiveMessageNumeric>
<ns6:SendMessageNumeric>37062</ns6:SendMessageNumeric>
<nh2:DocumentControlFieldText>
<![CDATA[VMYHBMXPIW]]>
</nh2:DocumentControlFieldText>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="CR">
<n2:ResponseText>HDR/11111111.
ATTENTION: NLETS_ANALYST
THE FOLLOWING RECORD IS IN RESPONSE TO YOUR INQUIRY ON SID/123456
ARIZONA CRIMINAL HISTORY
BECAUSE ADDITIONS OR DELETIONS MAY BE MADE AT ANY TIME, A NEW COPY
SHOULD BE REQUESTED FROM ARIZONA STATE PATROL - CID WHEN NEEDED FOR
SUBSEQUENT USE. WHEN EXPLANATION OF AN ARREST OR DISPOSITION IS
NEEDED, COMMUNICATE DIRECTLY WITH THE AGENCY THAT CONTRIBUTED THE
FINGERPRINTS.
"INFRCTN" - MEANS "INFRACTION" WHICH IS A VIOLATION OF ANY LAW,
ORDINANCE, ORDER, RULE OR REGULATION THAT IS NOT A MISDEMEANOR,
FELONY, OR TRAFFIC OFFENSE.
SWITCH ONLY - NOT FOR DISSEMINATION
NAME FEL STATE ID FBI NO. DATE REQUESTED
SMITH,JOHN N 123456 1234567 10/19/2011
MULTI-STATE Y
SEX RACE DATE OF BIRTH DATE DECEASED HEIGHT WEIGHT EYES HAIR
M W 01/01/1950 6 04 210 BRO BRO
PLACE OF BIRTH PLACE OF CITIZENSHIP NCIC FINGERPRINT SKIN
ARIZONA UNITED STATES OF AMERICA 00 00 00 00 00 XXX
00 00 00 00 00
******************************************************
MULTISTATE OFFENDER
******************************************************
ADDITIONAL IDENTIFIERS:
ALIAS NAMES RACE DATE OF BIRTH SOCIAL SECURITY NO.
SMITH,JOHNNY W 01/01/1950 123 45 6789
ARREST 01* * * *10/01/2000* * * * DCN 0000000001
AGENCY-PHOENIX PD (AZ0000002)
CASE NUMBER- A00001 NAME USED-SMITH,JOHN
CHARGE-1312 AGGRAVATED ASSAULT-POLICE OFFICER-STRONGARM(1)/FELONY -4
CHARGE-4801 RESISTING OFFICER(1)/MISDEMEANOR
CHARGE-1312 AGGRAVATED ASSAULT-POLICE OFFICER-STRONGARM(1)/FELONY -4
COURT-COUNTY COURT GLENDALE (AZ0000001)
COURT DISP DATE-12/01/2000 TIME-14.16.33 DOCKET-A01AA000000001
CHARGE-1312 ASSAULT OFFICER-3RD DEGREE(1)/FELONY -3
DISPOSITION-PRELIMINARY HEARING WAIVED
SENTENCE- COURT COST
PARDON INFO:
CHARGE-1312 ASSAULT OFFICER-3RD DEGREE(1)/FELONY -3
DISPOSITION-PRELIMINARY HEARING WAIVED
SENTENCE- COURT COST
PARDON INFO:
COURT-DOUGLAS COUNTY DISTRICT COURT (AZ0000000)
COURT DISP DATE-01/01/2001 DOCKET-A01AA000000002
CHARGE-1399 ASSAULT OFFICER 3RD DEGREE(1)/FELONY -3
DISPOSITION-COURT DISMISSAL
SENTENCE- COURT COST
PARDON INFO:
CHARGE-1399 ASSAULT OFFICER 3RD DEGREE(1)/FELONY -3
DISPOSITION-COURT DISMISSAL
SENTENCE- COURT COST
PARDON INFO:
**********
THE USE OF THIS RECORD IS CONTROLLED BY STATE AND FEDERAL
REGULATIONS.
IT IS PROVIDED FOR OFFICIAL USE ONLY AND MAY BE USED ONLY FOR THIS
PURPOSE.
END OF RECORD
</n2:ResponseText>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Example 8: Full Record response in standardized rapsheet form.
<ns7:NLETS version="4.00" xmlns:rap="http://nlets.org/niem2/rapsheet/1.0" xmlns:ansi-nist="http://niem.gov/niem/ansi-nist/2.0" xmlns:ns6="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:ns8="http://niem.gov/niem/domains/familyServices/2.1" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:ns7="http://www.nlets.org/niem/1.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.1">
<ns7:NLETSMessageHeader>
<ns6:MessageKeyCodeText>FR</ns6:MessageKeyCodeText>
<ns6:OriginatingORIID>FLSIR0000</ns6:OriginatingORIID>
<ns6:DestinationORIID>AZNLETS43</ns6:DestinationORIID>
<ns6:DocumentControlFieldText>1234567890</ns6:DocumentControlFieldText>
<ns6:MessageReceiveDate>2019-11-14</ns6:MessageReceiveDate>
<ns6:MessageReceiveTime>10:49:24</ns6:MessageReceiveTime>
<ns6:MessageSendDate>2019-11-14</ns6:MessageSendDate>
<ns6:MessageSendTime>10:49:24</ns6:MessageSendTime>
<ns6:ReceiveMessageNumeric>00000</ns6:ReceiveMessageNumeric>
<ns6:SendMessageNumeric>37062</ns6:SendMessageNumeric>
</ns7:NLETSMessageHeader>
<ns7:NLETSResponseData ns7:key="FR">
<rap:RapSheet>
<rap:Metadata>
<nc:ReportedDate>
<nc:Date>2015-01-01</nc:Date>
</nc:ReportedDate>
<nc:ReportingOrganizationText>Florida Department of Law Enforcement Headquarters</nc:ReportingOrganizationText>
<nc:SourceIDText/>
<rap:Version>4.1</rap:Version>
</rap:Metadata>
<rap:Introduction>
<rap:Caveat>
<nc:CaveatText>This record contains Florida information only. When explanation of a charge or disposition is needed, communicate directly with the agency that contributed the record information.</nc:CaveatText>
<rap:CaveatReferenceDate>2015-01-01</rap:CaveatReferenceDate>
<rap:CaveatIssuingAuthorityText/>
</rap:Caveat>
<rap:Caveat>
<nc:CaveatText>This record may only be used for the purpose requested as defined by the Code of Federal Regulations and/or Florida Statute.</nc:CaveatText>
<rap:CaveatReferenceDate>2015-01-01</rap:CaveatReferenceDate>
<rap:CaveatIssuingAuthorityText/>
</rap:Caveat>
<rap:Caveat>
<nc:CaveatText>This is a multi-source offender record.</nc:CaveatText>
<rap:CaveatReferenceDate>2015-01-01</rap:CaveatReferenceDate>
<rap:CaveatIssuingAuthorityText/>
</rap:Caveat>
<rap:RapSheetRequest>
<rap:PurposeCode>C</rap:PurposeCode>
<rap:Attention>HELP DESK</rap:Attention>
<rap:RapSheetPerson>
<j:PersonAugmentation>
<j:PersonFBIIdentification>
<nc:IdentificationID>111111111</nc:IdentificationID>
</j:PersonFBIIdentification>
<j:PersonStateFingerprintIdentification s:id="R7954519686400000000">
<nc:IdentificationID>FL00000000</nc:IdentificationID>
</j:PersonStateFingerprintIdentification>
</j:PersonAugmentation>
</rap:RapSheetPerson>
</rap:RapSheetRequest>
</rap:Introduction>
<rap:RapSheetPerson s:id="R7957824657200000000">
<nc:PersonAlternateName>
<nc:PersonGivenName>JOHN</nc:PersonGivenName>
<nc:PersonMiddleName>MICHAEL</nc:PersonMiddleName>
<nc:PersonSurName>DOE</nc:PersonSurName>
<nc:PersonFullName>DOE,JOHN MICHAEL</nc:PersonFullName>
</nc:PersonAlternateName>
<nc:PersonBirthDate>
<nc:Date>1950-01-01</nc:Date>
</nc:PersonBirthDate>
<nc:PersonBirthDate>
<nc:Date>1950-01-01</nc:Date>
</nc:PersonBirthDate>
<nc:PersonBirthLocation>
<nc:LocationName>Louisiana</nc:LocationName>
</nc:PersonBirthLocation>
<rap:PersonEyeColorText>BROWN</rap:PersonEyeColorText>
<rap:PersonHairColorText>BROWN</rap:PersonHairColorText>
<nc:PersonHeightMeasure>
<nc:MeasureText>600</nc:MeasureText>
</nc:PersonHeightMeasure>
<nc:PersonName>
<nc:PersonGivenName>JOHN</nc:PersonGivenName>
<nc:PersonMiddleName>MICHAEL</nc:PersonMiddleName>
<nc:PersonSurName>DOE</nc:PersonSurName>
<nc:PersonFullName>DOE,JOHN MICHAEL</nc:PersonFullName>
</nc:PersonName>
<nc:PersonPhysicalFeature>
<nc:PhysicalFeatureCategoryCode>TAT R SHLD</nc:PhysicalFeatureCategoryCode>
<nc:PhysicalFeatureDescriptionText>SHOULDER, RIGHT</nc:PhysicalFeatureDescriptionText>
</nc:PersonPhysicalFeature>
<nc:PersonPhysicalFeature>
<nc:PhysicalFeatureCategoryCode>SC FHD</nc:PhysicalFeatureCategoryCode>
<nc:PhysicalFeatureDescriptionText>FOREHEAD</nc:PhysicalFeatureDescriptionText>
</nc:PersonPhysicalFeature>
<rap:PersonRaceText>White</rap:PersonRaceText>
<rap:PersonSexText>Male</rap:PersonSexText>
<nc:PersonSSNIdentification>
<nc:IdentificationID>111111111</nc:IdentificationID>
</nc:PersonSSNIdentification>
<nc:PersonSSNIdentification>
<nc:IdentificationID>222222222</nc:IdentificationID>
</nc:PersonSSNIdentification>
<nc:PersonWeightMeasure>
<nc:MeasureText>160</nc:MeasureText>
</nc:PersonWeightMeasure>
<j:PersonAugmentation>
<j:PersonFBIIdentification>
<nc:IdentificationID>111111AA1</nc:IdentificationID>
</j:PersonFBIIdentification>
<j:PersonStateFingerprintIdentification s:id="R7952867203200000000">
<nc:IdentificationID>FL00000000</nc:IdentificationID>
</j:PersonStateFingerprintIdentification>
</j:PersonAugmentation>
</rap:RapSheetPerson>
<rap:PersonBiometricsAssociation>
<rap:PersonBiometrics>
<rap:PersonDNA>
<nc:BiometricImage>
<nc:BinaryAvailableIndicator>false</nc:BinaryAvailableIndicator>
</nc:BiometricImage>
</rap:PersonDNA>
<rap:PersonFingerprintSet>
<nc:BiometricImage>
<nc:BinaryAvailableIndicator>true</nc:BinaryAvailableIndicator>
</nc:BiometricImage>
</rap:PersonFingerprintSet>
</rap:PersonBiometrics>
</rap:PersonBiometricsAssociation>
<rap:Court s:id="RFL041063J-7878505428400000000">
<nc:OrganizationName>Manatee County Clerk of Court</nc:OrganizationName>
<j:OrganizationAugmentation>
<j:OrganizationORIIdentification>
<nc:IdentificationID>FL00000A</nc:IdentificationID>
</j:OrganizationORIIdentification>
</j:OrganizationAugmentation>
</rap:Court>
<rap:Court s:id="RFL003023J-7876852945000000000">
<nc:OrganizationLocation>
<nc:LocationAddress>
<nc:StructuredAddress>
<nc:LocationStreet>
<nc:StreetFullText>123 EAST MAIN STREET</nc:StreetFullText>
</nc:LocationStreet>
<nc:LocationCityName>ANY CITY</nc:LocationCityName>
<nc:LocationCountyName>1</nc:LocationCountyName>
<nc:LocationStateName>FL</nc:LocationStateName>
<nc:LocationCountryName>USA</nc:LocationCountryName>
<nc:LocationPostalCode>32000</nc:LocationPostalCode>
</nc:StructuredAddress>
</nc:LocationAddress>
</nc:OrganizationLocation>
<nc:OrganizationName>Bay County Clerk of Court</nc:OrganizationName>
<j:OrganizationAugmentation>
<j:OrganizationORIIdentification>
<nc:IdentificationID>FL000000A</nc:IdentificationID>
</j:OrganizationORIIdentification>
</j:OrganizationAugmentation>
</rap:Court>
<rap:Agency s:id="RFL0410000-7921470009200000000">
<nc:OrganizationName>Manatee County Sheriffs Office</nc:OrganizationName>
<j:OrganizationAugmentation>
<j:OrganizationORIIdentification>
<nc:IdentificationID>FL0000000</nc:IdentificationID>
</j:OrganizationORIIdentification>
</j:OrganizationAugmentation>
</rap:Agency>
<rap:Agency s:id="RFL003015A-7924774979990000000">
<nc:OrganizationLocation>
<nc:LocationAddress>
<nc:StructuredAddress>
<nc:LocationStreet>
<nc:StreetFullText>123 ANY PLACE</nc:StreetFullText>
</nc:LocationStreet>
<nc:LocationCityName>SMALL TOWN</nc:LocationCityName>
<nc:LocationCountyName>1</nc:LocationCountyName>
<nc:LocationStateName>FL</nc:LocationStateName>
<nc:LocationCountryName>USA</nc:LocationCountryName>
<nc:LocationPostalCode>32000</nc:LocationPostalCode>
</nc:StructuredAddress>
</nc:LocationAddress>
</nc:OrganizationLocation>
<nc:OrganizationName>Bay County State Attorney's Office</nc:OrganizationName>
<j:OrganizationAugmentation>
<j:OrganizationORIIdentification>
<nc:IdentificationID>FL000000A</nc:IdentificationID>
</j:OrganizationORIIdentification>
</j:OrganizationAugmentation>
</rap:Agency>
<rap:Agency s:id="RFL0030100-7914860076400000000">
<nc:OrganizationLocation>
<nc:LocationAddress>
<nc:StructuredAddress>
<nc:LocationStreet>
<nc:StreetFullText>123 ANY STREET</nc:StreetFullText>
</nc:LocationStreet>
<nc:LocationCityName>ANY TOWN</nc:LocationCityName>
<nc:LocationCountyName>1</nc:LocationCountyName>
<nc:LocationStateName>FL</nc:LocationStateName>
<nc:LocationCountryName>USA</nc:LocationCountryName>
<nc:LocationPostalCode>32000</nc:LocationPostalCode>
</nc:StructuredAddress>
</nc:LocationAddress>
</nc:OrganizationLocation>
<nc:OrganizationName>Panama City Police Department</nc:OrganizationName>
<j:OrganizationAugmentation>
<j:OrganizationORIIdentification>
<nc:IdentificationID>FL0000000</nc:IdentificationID>
</j:OrganizationORIIdentification>
</j:OrganizationAugmentation>
</rap:Agency>
<rap:RapSheetCycle>
<rap:CycleEarliestDate>
<nc:Date>1990-01-01</nc:Date>
</rap:CycleEarliestDate>
<rap:CycleTrackingIdentificationID>0000000000</rap:CycleTrackingIdentificationID>
<rap:Incident>
<nc:ActivityDate>
<nc:Date>1990-01-01</nc:Date>
</nc:ActivityDate>
</rap:Incident>
<rap:Arrest s:id="R7956172173990000000">
<nc:ActivityDate>
<nc:Date>1990-01-01</nc:Date>
</nc:ActivityDate>
<j:ArrestAgencyRecordIdentification>
<nc:IdentificationID>0000000000</nc:IdentificationID>
</j:ArrestAgencyRecordIdentification>
<rap:ArrestCharge s:id="R7895030269200000000">
<j:ChargeCountQuantity>1</j:ChargeCountQuantity>
<j:ChargeDescriptionText>PETTY</j:ChargeDescriptionText>
<j:ChargeNCICCode>2300</j:ChargeNCICCode>
<j:ChargeSequenceID>
<nc:IdentificationID>001</nc:IdentificationID>
</j:ChargeSequenceID>
<j:ChargeSeverityText>Misdemeanor</j:ChargeSeverityText>
<j:ChargeText>Larc</j:ChargeText>
<rap:ChargeNCICText>Larc</rap:ChargeNCICText>
<rap:ChargeSeverityDescriptionText>Unknown</rap:ChargeSeverityDescriptionText>
<rap:ChargeStatute>
<j:StatuteText>PETIT THEFT 1ST DEGREE 100 LESS 300 DOLS</j:StatuteText>
<j:StatuteOffenseIdentification>
<nc:IdentificationID>812.000</nc:IdentificationID>
</j:StatuteOffenseIdentification>
</rap:ChargeStatute>
</rap:ArrestCharge>
</rap:Arrest>
<rap:CourtAction s:id="R7893377781700000000">
<nc:ActivityDate>
<nc:Date>1990-01-01</nc:Date>
</nc:ActivityDate>
<nc:ActivityDescriptionText>Arrest Charge Status - Charge Resulted From Arrest</nc:ActivityDescriptionText>
<rap:CourtCharge s:id="R7898335235640000000">
<j:ChargeCountQuantity>1</j:ChargeCountQuantity>
<j:ChargeDescriptionText>RETAIL THEFT</j:ChargeDescriptionText>
<j:ChargeDisposition>
<nc:DispositionDate>
<nc:Date>1990-01-01</nc:Date>
</nc:DispositionDate>
<nc:DispositionDescriptionText>Same</nc:DispositionDescriptionText>
<j:ChargeDispositionOtherText>Guilty/Convicted</j:ChargeDispositionOtherText>
</j:ChargeDisposition>
<j:ChargeNCICCode>2300</j:ChargeNCICCode>
<j:ChargeSequenceID>
<nc:IdentificationID>1</nc:IdentificationID>
</j:ChargeSequenceID>
<j:ChargeSeverityText>Misdemeanor</j:ChargeSeverityText>
<j:ChargeText>Larc</j:ChargeText>
<j:ChargeTrackingIdentification>
<nc:IdentificationID>1</nc:IdentificationID>
</j:ChargeTrackingIdentification>
<rap:ChargeNCICText>Larc</rap:ChargeNCICText>
<rap:ChargeSeverityDescriptionText>2nd Degree</rap:ChargeSeverityDescriptionText>
<rap:ChargeStatute>
<j:StatuteText>Petit Theft 2nd Degree 1st Offense</j:StatuteText>
<j:StatuteOffenseIdentification>
<nc:IdentificationID>812.000</nc:IdentificationID>
</j:StatuteOffenseIdentification>
</rap:ChargeStatute>
</rap:CourtCharge>
<rap:CourtRecordIdentification>
<nc:IdentificationID>00000000AA</nc:IdentificationID>
</rap:CourtRecordIdentification>
</rap:CourtAction>
<rap:Sentencing s:id="R7896682752420000000">
<rap:Sentence>
<nc:ActivityIdentification>
<nc:IdentificationID>00000000AA</nc:IdentificationID>
</nc:ActivityIdentification>
<j:SentenceDescriptionText>CREDITED TIME-0 days</j:SentenceDescriptionText>
<j:SentenceDescriptionText>COURT COST-0.0</j:SentenceDescriptionText>
<j:SentenceDescriptionText>FINE-0.0</j:SentenceDescriptionText>
<j:SentenceDescriptionText>RESTITUTION-0.0</j:SentenceDescriptionText>
<j:SentenceDescriptionText>SENT PROVISIONS-N/A - Not Applicable null</j:SentenceDescriptionText>
<rap:CourtCostAmount>0.00</rap:CourtCostAmount>
<rap:SentenceCharge s:id="R7888420332000000000">
<j:ChargeCountQuantity>1</j:ChargeCountQuantity>
<j:ChargeDescriptionText>RETAIL THEFT</j:ChargeDescriptionText>
<j:ChargeDisposition>
<nc:DispositionDate>
<nc:Date>1990-01-01</nc:Date>
</nc:DispositionDate>
</j:ChargeDisposition>
<j:ChargeNCICCode>2300</j:ChargeNCICCode>
<j:ChargeSequenceID>
<nc:IdentificationID>0</nc:IdentificationID>
</j:ChargeSequenceID>
<j:ChargeSeverityText>Misdemeanor</j:ChargeSeverityText>
<j:ChargeText>Larc</j:ChargeText>
<rap:ChargeNCICText>Larc</rap:ChargeNCICText>
<rap:ChargeSeverityDescriptionText>2nd Degree</rap:ChargeSeverityDescriptionText>
<rap:ChargeStatute>
<j:StatuteText>Petit Theft 2nd Degree 1st Offense</j:StatuteText>
<j:StatuteOffenseIdentification>
<nc:IdentificationID>812.000</nc:IdentificationID>
</j:StatuteOffenseIdentification>
</rap:ChargeStatute>
</rap:SentenceCharge>
<j:SupervisionAssignedTerm>
<nc:ActivityDescriptionText>SENTENCE TYPE-N/A - Not Applicable</nc:ActivityDescriptionText>
<nc:ActivityDescriptionText>CONFINEMENT TYPE-Not Applicable</nc:ActivityDescriptionText>
</j:SupervisionAssignedTerm>
<j:SupervisionDisciplinaryAction xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<rap:SupervisionFineAmount>0.00</rap:SupervisionFineAmount>
</rap:Sentence>
</rap:Sentencing>
</rap:RapSheetCycle>
<rap:RapSheetCycle>
<rap:CycleEarliestDate>
<nc:Date>1990-01-01</nc:Date>
</rap:CycleEarliestDate>
<rap:CycleTrackingIdentificationID>0000000000</rap:CycleTrackingIdentificationID>
<rap:Incident>
<nc:ActivityDate>
<nc:Date>1990-01-01</nc:Date>
</nc:ActivityDate>
</rap:Incident>
<rap:Arrest s:id="R7886767844530000000">
<nc:ActivityDate>
<nc:Date>1990-01-01</nc:Date>
</nc:ActivityDate>
<j:ArrestAgencyRecordIdentification>
<nc:IdentificationID>30000</nc:IdentificationID>
</j:ArrestAgencyRecordIdentification>
<rap:ArrestCharge s:id="R7891725298480000000">
<j:ChargeCountQuantity>1</j:ChargeCountQuantity>
<j:ChargeDisposition>
<nc:DispositionDescriptionText>Turned Over TO ORI - FL0000000</nc:DispositionDescriptionText>
<nc:DispositionDescriptionText>Turned Over TO Agency Name - Bay County Sheriffs Office</nc:DispositionDescriptionText>
</j:ChargeDisposition>
<j:ChargeNCICCode>3600</j:ChargeNCICCode>
<j:ChargeSequenceID>
<nc:IdentificationID>001</nc:IdentificationID>
</j:ChargeSequenceID>
<j:ChargeSeverityText>Misdemeanor</j:ChargeSeverityText>
<j:ChargeText>Indecent Exposure</j:ChargeText>
<rap:ChargeNCICText>Indecent Exposure</rap:ChargeNCICText>
<rap:ChargeSeverityDescriptionText>Unknown</rap:ChargeSeverityDescriptionText>
<rap:ChargeStatute>
<j:StatuteText>Exposure Of Sexual Organs</j:StatuteText>
<j:StatuteOffenseIdentification>
<nc:IdentificationID>800.00</nc:IdentificationID>
</j:StatuteOffenseIdentification>
</rap:ChargeStatute>
</rap:ArrestCharge>
<rap:ArrestCharge s:id="R7880157911670000000">
<j:ChargeCountQuantity>1</j:ChargeCountQuantity>
<j:ChargeDisposition>
<nc:DispositionDescriptionText>Turned Over TO ORI - FL0000000</nc:DispositionDescriptionText>
<nc:DispositionDescriptionText>Turned Over TO Agency Name - Bay County Sheriffs Office</nc:DispositionDescriptionText>
</j:ChargeDisposition>
<j:ChargeNCICCode>5300</j:ChargeNCICCode>
<j:ChargeSequenceID>
<nc:IdentificationID>002</nc:IdentificationID>
</j:ChargeSequenceID>
<j:ChargeSeverityText>Misdemeanor</j:ChargeSeverityText>
<j:ChargeText>Disorderly Conduct</j:ChargeText>
<rap:ChargeNCICText>Disorderly Conduct</rap:ChargeNCICText>
<rap:ChargeSeverityDescriptionText>Unknown</rap:ChargeSeverityDescriptionText>
<rap:ChargeStatute>
<j:StatuteText>Brawling Fighting Corrupt Public Moral Decency</j:StatuteText>
<j:StatuteOffenseIdentification>
<nc:IdentificationID>877.00</nc:IdentificationID>
</j:StatuteOffenseIdentification>
</rap:ChargeStatute>
</rap:ArrestCharge>
</rap:Arrest>
<rap:Prosecution s:id="R789007281500000000">
<nc:ActivityDescriptionText>Arrest Charge Status - Charge Resulted From Arrest</nc:ActivityDescriptionText>
<rap:ProsecutionCharge s:id="R7881810399180000000">
<j:ChargeCountQuantity>1</j:ChargeCountQuantity>
<j:ChargeDescriptionText>EXPOSE SEXUAL ORGANS</j:ChargeDescriptionText>
<j:ChargeDescriptionText>Counsel Type - Public Defender</j:ChargeDescriptionText>
<j:ChargeDisposition>
<nc:DispositionDate>
<nc:Date>1990-01-01</nc:Date>
</nc:DispositionDate>
<nc:DispositionDescriptionText>Same As Above</nc:DispositionDescriptionText>
<j:ChargeDispositionOtherText>Dropped/Abandoned</j:ChargeDispositionOtherText>
</j:ChargeDisposition>
<j:ChargeNCICCode>3600</j:ChargeNCICCode>
<j:ChargeSequenceID>
<nc:IdentificationID>1</nc:IdentificationID>
</j:ChargeSequenceID>
<j:ChargeSeverityText>Misdemeanor</j:ChargeSeverityText>
<j:ChargeText>Indecent Exposure</j:ChargeText>
<j:ChargeTrackingIdentification>
<nc:IdentificationID>1</nc:IdentificationID>
</j:ChargeTrackingIdentification>
<rap:ChargeNCICText>Indecent Exposure</rap:ChargeNCICText>
<rap:ChargeSeverityDescriptionText>1st Degree</rap:ChargeSeverityDescriptionText>
<rap:ChargeStatute>
<j:StatuteText>Exposure Of Sexual Organs</j:StatuteText>
<j:StatuteOffenseIdentification>
<nc:IdentificationID>800.00</nc:IdentificationID>
</j:StatuteOffenseIdentification>
</rap:ChargeStatute>
</rap:ProsecutionCharge>
<rap:ProsecutionAgencyRecordIdentification>
<nc:IdentificationID>0000000AAA</nc:IdentificationID>
</rap:ProsecutionAgencyRecordIdentification>
<rap:ProsecutionSubject/>
</rap:Prosecution>
<rap:CourtAction s:id="R7885115365610000000">
<nc:ActivityDate>
<nc:Date>1990-01-01</nc:Date>
</nc:ActivityDate>
<nc:ActivityDescriptionText>Arrest Charge Status - Charge Resulted From Arrest</nc:ActivityDescriptionText>
<rap:CourtCharge s:id="R7883462882400000000">
<j:ChargeCountQuantity>1</j:ChargeCountQuantity>
<j:ChargeDisposition>
<nc:DispositionDate>
<nc:Date>1990-01-01</nc:Date>
</nc:DispositionDate>
<nc:DispositionDescriptionText>Same</nc:DispositionDescriptionText>
<j:ChargeDispositionOtherText>Guilty/Convicted</j:ChargeDispositionOtherText>
</j:ChargeDisposition>
<j:ChargeNCICCode>5300</j:ChargeNCICCode>
<j:ChargeSequenceID>
<nc:IdentificationID>2</nc:IdentificationID>
</j:ChargeSequenceID>
<j:ChargeSeverityText>Misdemeanor</j:ChargeSeverityText>
<j:ChargeText>Disorderly Conduct</j:ChargeText>
<j:ChargeTrackingIdentification>
<nc:IdentificationID>2</nc:IdentificationID>
</j:ChargeTrackingIdentification>
<rap:ChargeNCICText>Disorderly Conduct</rap:ChargeNCICText>
<rap:ChargeSeverityDescriptionText>2nd Degree</rap:ChargeSeverityDescriptionText>
<rap:ChargeStatute>
<j:StatuteText>Brawling Fighting Corrupt Public Moral Decency</j:StatuteText>
<j:StatuteOffenseIdentification>
<nc:IdentificationID>877.00</nc:IdentificationID>
</j:StatuteOffenseIdentification>
</rap:ChargeStatute>
</rap:CourtCharge>
<rap:CourtRecordIdentification>
<nc:IdentificationID>0000000AAA</nc:IdentificationID>
</rap:CourtRecordIdentification>
</rap:CourtAction>
<rap:Sentencing s:id="R7875200462021000000">
<rap:Sentence>
<nc:ActivityIdentification>
<nc:IdentificationID>0000000AAA</nc:IdentificationID>
</nc:ActivityIdentification>
<j:SentenceDescriptionText>CRT PROVISIONS-Confinement or Fine</j:SentenceDescriptionText>
<j:SentenceDescriptionText>CONFINEMENT- - 10 days</j:SentenceDescriptionText>
<j:SentenceDescriptionText>CREDITED TIME-2 days</j:SentenceDescriptionText>
<j:SentenceDescriptionText>COURT COST-0.0</j:SentenceDescriptionText>
<j:SentenceDescriptionText>FINE-0.0</j:SentenceDescriptionText>
<j:SentenceDescriptionText>RESTITUTION-0.0</j:SentenceDescriptionText>
<j:SentenceDescriptionText>SENT PROVISIONS-N/A - Not Applicable null</j:SentenceDescriptionText>
<rap:CourtCostAmount>0.00</rap:CourtCostAmount>
<rap:SentenceCharge s:id="R7873547974510000000">
<j:ChargeCountQuantity>1</j:ChargeCountQuantity>
<j:ChargeDisposition>
<nc:DispositionDate>
<nc:Date>1990-01-01</nc:Date>
</nc:DispositionDate>
</j:ChargeDisposition>
<j:ChargeNCICCode>5300</j:ChargeNCICCode>
<j:ChargeSequenceID>
<nc:IdentificationID>0</nc:IdentificationID>
</j:ChargeSequenceID>
<j:ChargeSeverityText>Misdemeanor</j:ChargeSeverityText>
<j:ChargeText>Disorderly Conduct</j:ChargeText>
<rap:ChargeNCICText>Disorderly Conduct</rap:ChargeNCICText>
<rap:ChargeSeverityDescriptionText>2nd Degree</rap:ChargeSeverityDescriptionText>
<rap:ChargeStatute>
<j:StatuteText>Brawling Fighting Corrupt Public Moral Decency</j:StatuteText>
<j:StatuteOffenseIdentification>
<nc:IdentificationID>877.00</nc:IdentificationID>
</j:StatuteOffenseIdentification>
</rap:ChargeStatute>
</rap:SentenceCharge>
<j:SupervisionAssignedTerm>
<nc:ActivityDescriptionText>SENTENCE TYPE-N/A - Not Applicable</nc:ActivityDescriptionText>
<nc:ActivityDescriptionText>CONFINEMENT TYPE-County Jail</nc:ActivityDescriptionText>
<nc:ActivityDescriptionText>CONFINEMENT</nc:ActivityDescriptionText>
<j:TermMaximumDuration>P0Y0M10DT0H0M0S</j:TermMaximumDuration>
<j:TermMinimumDuration>P0Y0M0DT0H0M0S</j:TermMinimumDuration>
</j:SupervisionAssignedTerm>
<j:SupervisionDisciplinaryAction xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<rap:SupervisionFineAmount>0.00</rap:SupervisionFineAmount>
</rap:Sentence>
</rap:Sentencing>
</rap:RapSheetCycle>
<rap:ArrestAgencyAssociation>
<nc:ActivityReference s:ref="R7886767844538000000"/>
<nc:OrganizationReference s:ref="RFL0030100-7914860076402000000"/>
<j:ArrestAgencyRecordIdentification xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</rap:ArrestAgencyAssociation>
<rap:ArrestAgencyAssociation>
<nc:ActivityReference s:ref="R7956172173999000000"/>
<nc:OrganizationReference s:ref="RFL0410000-7921470009260000000"/>
<j:ArrestAgencyRecordIdentification xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</rap:ArrestAgencyAssociation>
<rap:ChargeAgencyAssociation>
<j:ChargeReference s:ref="R7895030269210000000"/>
<nc:OrganizationReference s:ref="RFL0410000-7921470009269000000"/>
</rap:ChargeAgencyAssociation>
<rap:ChargeAgencyAssociation>
<j:ChargeReference s:ref="R7880157911672000000"/>
<nc:OrganizationReference s:ref="RFL0030100-7914860076402000000"/>
</rap:ChargeAgencyAssociation>
<rap:ChargeAgencyAssociation>
<j:ChargeReference s:ref="R7891725298483000000"/>
<nc:OrganizationReference s:ref="RFL0030100-7914860076402000000"/>
</rap:ChargeAgencyAssociation>
<rap:CourtActionCourtAssociation>
<nc:ActivityReference s:ref="R7893377781700000000"/>
<j:CourtReference s:ref="RFL041063J-7878505428455000000"/>
</rap:CourtActionCourtAssociation>
<rap:CourtActionCourtAssociation>
<nc:ActivityReference s:ref="R7885115365617000000"/>
<j:CourtReference s:ref="RFL003023J-7876852945200000000"/>
</rap:CourtActionCourtAssociation>
<rap:ProsecutionAgencyAssociation>
<rap:ProsecutionReference s:ref="R7890072815260000000"/>
<nc:OrganizationReference s:ref="RFL003015A-7924774979990000000"/>
</rap:ProsecutionAgencyAssociation>
<rap:SentencingCourtAssociation>
<nc:ActivityReference s:ref="R7875200462020000000"/>
<j:CourtReference s:ref="RFL003023J-7876852945230000000"/>
</rap:SentencingCourtAssociation>
<rap:SentencingCourtAssociation>
<nc:ActivityReference s:ref="R7896682752428000000"/>
<j:CourtReference s:ref="RFL041063J-7878505428455000000"/>
</rap:SentencingCourtAssociation>
</rap:RapSheet>
</ns7:NLETSResponseData>
</ns7:NLETS>
|
---|
Example 9: Triple I response in standardized rapsheet form.
<n2:NLETS xmlns:n2="http://www.nlets.org/niem/1.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" version="4.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>CR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>TXIII0000</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS43</nh2:DestinationORIID>
<nh2:DocumentControlFieldText>NN39350874</nh2:DocumentControlFieldText>
<ns6:MessageReceiveDate>2019-11-14</ns6:MessageReceiveDate>
<ns6:MessageReceiveTime>10:49:24</ns6:MessageReceiveTime>
<ns6:MessageSendDate>2019-11-14</ns6:MessageSendDate>
<ns6:MessageSendTime>10:49:24</ns6:MessageSendTime>
<ns6:ReceiveMessageNumeric>00000</ns6:ReceiveMessageNumeric>
<ns6:SendMessageNumeric>37062</ns6:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData
xmlns:n2="http://www.nlets.org/niem/1.0" Key="CR">
<rap:RapSheet xmlns:rap="http://nlets.org/niem2/rapsheet/1.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.1" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" s:metadata="reportDate">
<rap:Metadata s:id="reportDate">
<nc:ReportedDate>
<nc:Date>2010-01-01</nc:Date>
</nc:ReportedDate>
<rap:Version>4.1</rap:Version>
<rap:TripleIStatusText>Multi-source</rap:TripleIStatusText>
</rap:Metadata>
<rap:Introduction>
<rap:Caveat>
<nc:CaveatText>UNAUTHORIZED USE OR DISCLOSURE OF THE INFORMATION CONTAINED IN THIS RECORD MAY RESULT IN SEVERE CRIMINAL PENALTIES. SEE TEXAS GOVERNMENT CODE SECTION 411.085.</nc:CaveatText>
<rap:CaveatIssuingAuthorityText>TX</rap:CaveatIssuingAuthorityText>
</rap:Caveat>
<rap:RapSheetRequest>
<rap:PurposeCode>C</rap:PurposeCode>
<rap:Attention>HELP DESK</rap:Attention>
<rap:RapSheetPerson>
<j:PersonAugmentation>
<j:PersonStateFingerprintIdentification>
<nc:IdentificationID>11111111</nc:IdentificationID>
<j:IdentificationJurisdictionNCICLSTACode>TX</j:IdentificationJurisdictionNCICLSTACode>
</j:PersonStateFingerprintIdentification>
</j:PersonAugmentation>
</rap:RapSheetPerson>
</rap:RapSheetRequest>
<rap:ControlData>
<nc:IdentificationID>0A00AA00000000</nc:IdentificationID>
<nc:IdentificationCategoryText>NCIChdr</nc:IdentificationCategoryText>
</rap:ControlData>
</rap:Introduction>
<rap:RapSheetPerson s:id="N10000">
<nc:PersonAlternateName>
<nc:PersonGivenName>JOHN</nc:PersonGivenName>
<nc:PersonSurName>SMITH</nc:PersonSurName>
</nc:PersonAlternateName>
<nc:PersonBirthDate>
<nc:Date>1950-01-01</nc:Date>
</nc:PersonBirthDate>
<nc:PersonBirthLocation>
<nc:LocationName>MM</nc:LocationName>
</nc:PersonBirthLocation>
<nc:PersonCitizenshipText>MM</nc:PersonCitizenshipText>
<rap:PersonEthnicityText>AMERICAN</rap:PersonEthnicityText>
<rap:PersonEyeColorText>BROWN</rap:PersonEyeColorText>
<rap:PersonHairColorText>Black</rap:PersonHairColorText>
<nc:PersonHeightMeasure>
<nc:MeasureText>520</nc:MeasureText>
</nc:PersonHeightMeasure>
<nc:PersonName>
<nc:PersonGivenName>JOHN</nc:PersonGivenName>
<nc:PersonSurName>SMITH</nc:PersonSurName>
</nc:PersonName>
<nc:PersonPhysicalFeature>
<nc:PhysicalFeatureCategoryCode>TAT CHEST</nc:PhysicalFeatureCategoryCode>
<nc:PhysicalFeatureDescriptionText>NA</nc:PhysicalFeatureDescriptionText>
</nc:PersonPhysicalFeature>
<rap:PersonRaceText>WHITE</rap:PersonRaceText>
<rap:PersonSexText>MALE</rap:PersonSexText>
<rap:PersonSkinToneText>MEDIUM</rap:PersonSkinToneText>
<nc:PersonWeightMeasure>
<nc:MeasureText>220</nc:MeasureText>
</nc:PersonWeightMeasure>
<j:PersonAugmentation>
<j:PersonFBIIdentification>
<nc:IdentificationID>AAAA0AAAA</nc:IdentificationID>
</j:PersonFBIIdentification>
<j:PersonStateFingerprintIdentification>
<nc:IdentificationID>11111111</nc:IdentificationID>
<j:IdentificationJurisdictionNCICLSTACode>TX</j:IdentificationJurisdictionNCICLSTACode>
</j:PersonStateFingerprintIdentification>
</j:PersonAugmentation>
</rap:RapSheetPerson>
<rap:PersonBiometricsAssociation>
<nc:PersonReference s:ref="N10000"/>
<rap:PersonBiometrics>
<nc:PersonDigitalImage>
<nc:BinaryAvailableIndicator>true</nc:BinaryAvailableIndicator>
<nc:BinaryCaptureDate>
<nc:Date>2019-01-01</nc:Date>
</nc:BinaryCaptureDate>
<nc:BinaryDescriptionText>NCIC2000</nc:BinaryDescriptionText>
<nc:BinaryFormatID>image/jpeg</nc:BinaryFormatID>
<nc:BinaryLocationURI>11111111</nc:BinaryLocationURI>
<nc:BinarySizeValue>6300</nc:BinarySizeValue>
<nc:BinaryCategoryText>M</nc:BinaryCategoryText>
</nc:PersonDigitalImage>
<rap:PersonDNA>
<nc:BiometricDescriptionText>DNA Not Available</nc:BiometricDescriptionText>
<nc:BiometricCapturer>
<rap:EntityOrganization>
<nc:OrganizationName>TEXAS DPS DNA CRIME LABORATORY AUSTIN</nc:OrganizationName>
<j:OrganizationAugmentation>
<j:OrganizationORIIdentification>
<nc:IdentificationID>TXDPS0000</nc:IdentificationID>
</j:OrganizationORIIdentification>
</j:OrganizationAugmentation>
</rap:EntityOrganization>
</nc:BiometricCapturer>
</rap:PersonDNA>
<rap:PersonFingerprintSet>
<nc:BiometricValueText>AAAAAAAAAA</nc:BiometricValueText>
<nc:BiometricEncodingMethodText>APC</nc:BiometricEncodingMethodText>
</rap:PersonFingerprintSet>
</rap:PersonBiometrics>
</rap:PersonBiometricsAssociation>
<rap:Agency s:id="TX0000000">
<nc:OrganizationName>EL PASO CO SHERIFF'S OFFICE</nc:OrganizationName>
<j:OrganizationAugmentation>
<j:OrganizationORIIdentification>
<nc:IdentificationID>TX0000000</nc:IdentificationID>
</j:OrganizationORIIdentification>
</j:OrganizationAugmentation>
</rap:Agency>
<rap:RapSheetCycle>
<rap:CycleEarliestDate>
<nc:Date>2019-01-01</nc:Date>
</rap:CycleEarliestDate>
<rap:CycleTrackingIdentificationID>0000000000</rap:CycleTrackingIdentificationID>
<rap:CycleTrackingIdentificationID>Sequence: A</rap:CycleTrackingIdentificationID>
<rap:Arrest s:id="N000AA">
<nc:ActivityCategoryText>Adult</nc:ActivityCategoryText>
<nc:ActivityDate>
<nc:Date>2019-01-01</nc:Date>
</nc:ActivityDate>
<rap:ArrestCharge s:id="N10000">
<j:ChargeDescriptionText>Date Of Offense: 2019-01-01</j:ChargeDescriptionText>
<j:ChargeDescriptionText>Arresting Agency Number: 1111111</j:ChargeDescriptionText>
<j:ChargeDescriptionText>Referred Agency: TX000000A - DISTRICT ATTORNEYS OFFICE EL PASO</j:ChargeDescriptionText>
<j:ChargeDisposition>
<nc:DispositionDate>
<nc:Date>2019-01-01</nc:Date>
</nc:DispositionDate>
<nc:DispositionDescriptionText>TRANSFERRED FOR FEDERAL PROSECUTION</nc:DispositionDescriptionText>
</j:ChargeDisposition>
<j:ChargeIdentification>
<nc:IdentificationID>1111111111</nc:IdentificationID>
</j:ChargeIdentification>
<j:ChargeNCICCode>8800</j:ChargeNCICCode>
<j:ChargeSequenceID>
<nc:IdentificationID>A001</nc:IdentificationID>
</j:ChargeSequenceID>
<j:ChargeSeverityText>FELONY - UNCLASSIFIED DEGREE</j:ChargeSeverityText>
<j:ChargeText>FEDERAL OFFENSE</j:ChargeText>
<j:ChargeTrackingIdentification>
<nc:IdentificationID>1111111111</nc:IdentificationID>
</j:ChargeTrackingIdentification>
<rap:ChargeStatute>
<j:StatuteCodeIdentification>
<nc:IdentificationID>X FEDERAL OFFENSE</nc:IdentificationID>
</j:StatuteCodeIdentification>
<j:StatuteOffenseIdentification>
<nc:IdentificationID>88888888</nc:IdentificationID>
</j:StatuteOffenseIdentification>
</rap:ChargeStatute>
</rap:ArrestCharge>
<rap:ArrestSubject>
<rap:SubjectFullName>SMITH,JOHN</rap:SubjectFullName>
</rap:ArrestSubject>
</rap:Arrest>
</rap:RapSheetCycle>
<rap:ArrestAgencyAssociation>
<nc:ActivityReference s:ref="N10000"/>
<nc:OrganizationReference s:ref="TX0000000"/>
</rap:ArrestAgencyAssociation>
<rap:ChargeAgencyAssociation>
<j:ChargeReference s:ref="N10000"/>
<nc:OrganizationReference s:ref="TX0000000"/>
</rap:ChargeAgencyAssociation>
<rap:ExtensionField s:id="DTE_TMSN10000">
<rap:FieldName>ORIGINATION DATE</rap:FieldName>
<rap:FieldValue>2019-01-01T16:58:00.000000</rap:FieldValue>
</rap:ExtensionField>
<rap:ExtensionField s:id="DTE_TMSN10177">
<rap:FieldName>DATE OF LAST UPDATE</rap:FieldName>
<rap:FieldValue>2019-01-01T15:05:00.000000</rap:FieldValue>
</rap:ExtensionField>
<rap:ExtensionField>
<rap:FieldName>Transaction</rap:FieldName> <rap:FieldValue>$.A.CHR.HDR/2A000AA00000000.NCF/AA00000000.TME/1028.TMZ/EST.DTE/20190101.ORI/VACBP0000.SID/TX11111111.FBI/AAAA1AAAA.NAM/SMITH,JOHN,CARLOS.PUR/C.TOS/BASED ON FBI NUMBER ONLY.ORT/CUSTOMS BORDER PROTECTION.ATN/TASPD.CRIMINAL HISTORY REQUESTEDNIC#</rap:FieldValue>
</rap:ExtensionField>
</rap:RapSheet>
</n2:NLETSResponseData>
</n2:NLETS>
|
---|
Legacy (DEPRECATED)
Criminal History Legacy Specifications
This section describes the format and provides examples for Criminal History (CHRI) queries using three query types (IQ, FQ, AQ) and the corresponding responses (IR, FR, AR).
Triple I Responses from NCIC (CR) are included at the end of this section.
Identity Query (IQ) |
Generally the Identity Query (IQ) will be used to request identity
|
---|---|
Full Record Query (FQ) |
A full record query (FQ) is used to retrieve a full record from a
|
Additional Query (AQ) |
An additional query (AQ) is used to request supplemental or other
|
Query Formats
Specifications for Identity Query (IQ) messages are as follows:
- 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.
An Identity inquiry (IQ) uses the following data elements:
Entry | # Char. | Explanation |
---|---|---|
IQ. | 2 | Message type followed by a period |
Message Header | 13-36 | Standard input message header may include control
field and up to 5 addresses. |
TXT | 3 | Fixed filed prefix to beginning of message |
CR,LF,DEL | 3 | Control characters (optional) |
PUR/ | 4 | Prefix to identify purpose code |
Purpose code | 1 | Must be C, F, E, D, J, I or S followed by a period |
ATN/ | 4 | Prefix to identify attention field |
Attention field | 30 | Name of requester followed by a period |
NAM/ | 4 | Prefix to identify name |
Name | Max. 30 |
Full name; format is last name, comma, space after
|
DOB/ | 4 | Prefix to identify date of birth |
Date of Birth | 6-8 |
Date of Birth followed by a period. Express as
|
SEX/ | 4 | Prefix to identify sex |
Sex | 1 | Sex followed by a period; conforms to NCIC codes |
RAC/ (optional) | 4 | Prefix to identify race |
Race | 1 | Race code followed by a period, conforms to NCIC
codes |
SOC/ (optional) | 4 | Prefix to identify Soc. Sec. Number |
Soc. Sec. # | 9 | Social Security Number followed by a period |
MNU/ (optional) | 4 | Prefix to identify miscellaneous number |
Misc. # | 15 | Miscellaneous number |
IMQ/ | 4 | (For XML use only) Prefix to identify image request
field |
Image Request | 1 | Y to request driver photo;
omit IMQ/ field if photo not wanted |
Full Record Query (FQ) 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 requester has reviewed the hits and made a selection.
- Only a single 2-character state code is allowed as the destination because this is a State Identification (SID) query.
- 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 any one of the fields, except for BLD, is present, all fields must be present (again, except for BLD).
- Utilize the Image Flag (IMQ/Binary Request Indicator) to request the images associated with the record.
The format for a Full Record Query (FQ) is as follows.
Entry | # Char. | Explanation |
---|---|---|
FQ. | 2 | Message type followed by a period. |
Message Header | 13-25 | Standard input message header, may include control
field. |
TXT | 3 | Fixed filed prefix to beginning of message. |
CR,LF,DEL | 3 | Control characters (optional). |
PUR/ | 4 | Prefix to identify purpose code. |
Purpose code | 1 | Must be C, F, E, D, J, I or S. |
ATN/ | 4 | Prefix to identify attention field. |
Attention field | Max.30 | Attention field, includes name of individual making the
inquiry followed by a period. |
SID/ | 4 | Prefix to identify state ID#. |
SID Number | Max. 10 | State ID# followed by a period. |
The following are optional entries.
Entry | # Char. | Explanation |
---|---|---|
*DPT/ (optional) | 4 | Prefix to identify department |
Department | Max.30 | Department name or # followed by a period |
BLD/ (optional) | 4 | Prefix to identify building number |
Building | Max.30 | Building name or number |
*ADR/ (optional) | 4 | Prefix to identify address |
Address | Max.30 | Address |
*CIS/ (optional) | 4 | Prefix to identify city and state |
City & State | Max.30 | City and State |
*ZIP/ (optional) | 4 | Prefix to identify ZIP code |
ZIP code | 5 or 9 | ZIP code (allow alpha or numeric) |
IMQ/ | 4 | (For XML use only) Prefix to identify image request field |
Image Request | 1 | Y to request driver photo; omit IMQ/ field if photo not
wanted |
- When address is included, these fields are mandatory (BLD is always optional).
Additional Response Query (AQ) The purpose of the AQ is to request supplemental or other information not available through the normal IQ or FQ queries. This may include 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.
- This message is a controlled free form message.
- There are two required fields: Purpose (PUR) and Attention (ATN).
- 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 see 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.
The format is as follows.
Entry | # Char. | Explanation |
---|---|---|
AQ. | 2 | Message type followed by a period. |
Message Header | 13-36 | Standard input message header, may include control field
and up to 5 addresses (state or regional codes). |
TXT | 3 | Fixed filed prefix to beginning of message. |
CR,LF,DEL | 3 | Control characters (optional). |
PUR/ | 4 | Prefix to identify purpose code. |
Purpose code | 1 | Must be C, E, F, D, J, I or S |
ATN/ | 4 | Prefix to identify attention field. |
Free text | Max.
14,400 |
No special format used. |
Response Formats
This section describes the requirements for message responses.
Identity Response (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 Response (FR)
- This message type must be used to respond to all FQ queries.
- Full Record response (FR) formats must include all information received in the FQ starting after the TXT to the end of the message.
- 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 query 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 Response (AR)
- This message type should be used to respond to all AQs. AR messages must include, immediately after the TXT, the purpose code and requester 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.
Triple I Response (CR)
- 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.
Criminal History Legacy Examples
Example 1: Identity query by name, date of birth and sex.
IQ.AZNLETS20.AZ.TXT
PUR/C.ATN/NLETS_ANALYST.NAM/SMITH,JOHN.DOB/19500101.SEX/M |
---|
Example 2: Full Record query by SID.
FQ.AZNLETS20.AZ.TXT
PUR/C.ATN/NLETS_ANALYST.SID/AZ1111111 |
---|
Example 3: Additional Response query.
AQ.AZNLETS20.AZ0000000.TXT
|
---|
Example 4: Identity response.
IR.AZSIR0000
|
---|
Example 5: Full Record response.
FR.AZSIR0000
|
---|
Example 6: Aditional response.
AR.AZ0000000
|
---|
Example 7: Triple I response.
CR.AZIII0000
|
---|
Downloads
Download IR Schema (updated 6/6/2019)
Download IR Stylesheet (updated 9/9/2019)