Section 49: Charge Code Transactions

From Nlets Wiki
Jump to: navigation, search

Charge Code Transactions (CCQ/CCR)

Overview

In 2018, Nlets participated in a project to enhance the capability to support DHS in their mission to notify US law enforcement of ICE custody releases within their jurisdiction. Through this project, Nlets has created a repository of state statute codes for all US states and territories, and mapped those statute codes to NCIC offense codes. NIBRS codes, statute literals and severities are also mapped for many of these statutes. This data is available via the rapsheet parsing service (contact the Nlets help desk for details), as well as through the charge code query (CCQ) and charge code response (CCR).

Section49-CCQ.jpg

Query Requirements

The purpose of this application is to provide Nlets users with on-line information on charge code queries and responses.

Inquiry formats and examples of responses may be found below.

XML Tag: Legacy Prefix: Field Size: Data Requirements: Explanation:
<j6:StatuteCodeIdentification>
   <nc4:IdentificationID>
STC/ 1 - 30 String Statute code for the charge/offense. (example: 13-5-542)
<j6:StatuteOffenseStateCodeText>
STE/ 2 String State code for the statute. (example: AZ)

NIEM

Charge Code NIEM Specifications

This section provides NIEM format and examples for Charge Code Transaction (CCQ/CCR).

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: Charge Code Query (CCQ) and Charge Code Response (CCR).

Query Formats

Charge Code Query (CCQ)

Inquiry Data (n:NLETSInquiryData)
This element will contain all elements specific to this transaction.

  Statute (j6:Statute)
  A unique identifier of a law, rule, or ordinance within a jurisdiction.
  queried.

  Statute Code (j6:StatuteCodeIdentification)
  An identification number of a set of laws for a particular jurisdiction.
  The value for query should be in the stub-element nc:IdentificationID

  Statute State (j6:StatuteOffenseStateCodeText)
  The two-character state of the statute.

Response Formats

Charge Code Response (CCR)

Matches for Statute (n2:StatuteMatches)

  Statute (j6:Statute)
  A unique identifier of a law, rule, or ordinance within a jurisdiction.

  Statute Code (j6:StatuteCodeIdentification)
  An identification number of a set of laws for a particular jurisdiction.
  The value for query should be in the stub-element nc:IdentificationID

  Enacted Date (j6:StatuteEnactmentDate)
  A date a statute was enacted and came into effect.
  The value will be in the sub-element nc:Date

  Repealed Date (j6:StatuteRepealDate)
  A date a statute was repealed and no longer applied.
  The value will be in the sub-element nc:Date

  Statute Literal (j6:StatuteText)
  A full text of a statute or law.

  Statute State (j6:StatuteOffenseStateCodeText)
  The two-character state of the statute.

Statute Augmentation (n2:StatuteAugmentation)
Additional information about the statute

Equivalence (n2:StatuteEquivalence)
Equivalent data for the identified statute

  NCIC Code (j6:ChargeNCICCode)
  An offense within the National Crime Information Center (NCIC) system.

NIBRS Code(n2:NIBRSCode)
NIBRS Code

Charge Code NIEM Examples

Example 1: Charge Code query.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" 
xmlns:nc4="http://release.niem.gov/niem/niem-core/4.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" n2:version="4.00" 
xmlns:j5="http://release.niem.gov/niem/domains/jxdm/5.0/" xmlns:j6="http://release.niem.gov/niem/domains/jxdm/6.1/" 
xmlns:ct="http://release.niem.gov/niem/conformanceTargets/3.0/" xmlns:structures="http://release.niem.gov/niem/structures/3.0/" 
xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>CCQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>NL</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="CCQ">
    <j6:Statute>
      <j6:StatuteCodeIdentification>
        <nc4:IdentificationID>13-2317</nc4:IdentificationID>
      </j6:StatuteCodeIdentification>
      <j6:StatuteOffenseStateCodeText>AZ</j6:StatuteOffenseStateCodeText>
    </j6:Statute>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 2: Charge Code Response.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc4="http://release.niem.gov/niem/niem-core/4.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" n2:version="4.00" 
xmlns:j5="http://release.niem.gov/niem/domains/jxdm/5.0/" xmlns:ct="http://release.niem.gov/niem/conformanceTargets/3.0/" 
xmlns:nc="http://release.niem.gov/niem/niem-core/4.0/"  xmlns:j6="http://release.niem.gov/niem/domains/jxdm/6.1/"  
xmlns:structures="http://release.niem.gov/niem/structures/3.0/" 
xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>CCR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>NL00000000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CONTROL123]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>07/28/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>08:51</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>07/28/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>08:51</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00014</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00010</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="CCQ">
    <j6:Statute>
      <j6:StatuteCodeIdentification>
        <nc:IdentificationID >13-5-542</nc:IdentificationID>
      </j6:StatuteCodeIdentification>
      <j6:StatuteOffenseStateCodeText>AZ</j6:StatuteOffenseStateCodeText>
    </j6:Statute>
  </n2:NLETSInquiryData>
  <n2:NLETSResponseData n2:key="CCR">
    <n2:StatuteMatches>
      <j6:Statute >
        <j6:StatuteCodeIdentification>
          <nc:IdentificationID>13-5-542</nc:IdentificationID>
        </j6:StatuteCodeIdentification>
        <j6:StatuteEnactmentDate>
          <nc:Date>1900-01-01</nc:Date>
        </j6:StatuteEnactmentDate>
        <j6:StatuteRepealDate>
          <nc:Date >2017-08-13</nc:Date>
        </j6:StatuteRepealDate>
        <j6:StatuteText>ASSAULT</j6:StatuteText>
        <j6:StatuteOffenseStateCodeText>AZ</j6:StatuteOffenseStateCodeText>
        <n2:StatuteAugmentation>
          <n2:StatuteEquivalence>
            <j6:ChargeNCICCode>2307</j6:ChargeNCICCode>
            <n2:NIBRSCode>36A</n2:NIBRSCode>
          </n2:StatuteEquivalence>
        </n2:StatuteAugmentation>
      </j6:Statute>
    </n2:StatuteMatches>
  </n2:NLETSResponseData>
</n2:NLETS>

Legacy (DEPRECATED)

Charge Code Legacy Specifications

This section includes formats and examples for charge code queries and responses (CCQ/CCR).

Query Formats

To send a Charge Code Query (CCQ), enter the following.

Entry: Size: Explanation:
CCQ. 3 Message type for searching the CCQ message
database.
Sender ORI 9 Sender ORI followed by a period.
Destination ORI 2 Must always be NL followed by a period.
TXT 3 Field prefix denoting beginning of message.
STC/ 4

Prefix to identify statute code.

Statute Code 1-30

Statute code for the charge/offense. (example: 13-5-542)

STE/ 4 Prefix to identify state.
State Code 2

State code for the statute. (example: AZ)

Charge Code Legacy Examples

Example 1: A Charge Code query by statute and state code.

CCQ.AZNLETS37.NL.TXTSTC/13-2317.STE/AZ

Example 2: A Charge Code response.

CCR.NL0000000
07:51 05/07/2019 04379
07:51 05/07/2019 00088 AZNLETS20
TXT
Matching Statutes
AZ Statute 13-2317
Money laundering, 1st degree
Equivalent NCIC Code: 6300
AZ Statute 13-2317
Money laundering, 2nd degree
Equivalent NCIC Code: 6300
AZ Statute 13-2317
Money laundering, 3rd degree
Equivalent NCIC Code: 6300

Top

LENS/Nlets NCIC Statute Mapping Portal

Nlets has created a portal to allow direct interaction with the NCIC Statute Mapping data. The service will allow you to view statute mappings for all states. Editing is restricted to the users state jurisdiction.

The service is available at: https://LENS.nlets.org

How to use the service:

1. Enter a valid ORI, Control Number, and User Name.
2. Click the "Request Password" button.

When a password is requested, the password will be sent to the ORI indicated, utilizing the provided Control Number, via an AM message from Nlets.

After receipt of the password, return to this screen:

1. Enter the ORI and password.
2. Click the "Login" button.


Section49-NletsWikiLensPortalScreenShot.jpg

Top

Downloads

Download CCQ Schema

Download CCR Schema

Download CCR Stylesheet

Top