Section 29: National Drug Pointer Index System

From Nlets Wiki
Jump to: navigation, search

National Drug Pointer Index System (DEX/DEA, DUX/DUA, DRX/DRR)

This section describes how agencies may participate through Nlets in the National Drug Pointer Index System (NDPIX) which is a nationwide, multi jurisdictional automated information sharing system emphasizing increased cooperation among law enforcement agencies. Queries/Entries into NDPIX also checks against the National Virtual Pointer System (NVPS).

Note: Whenever a user runs an NDPIX transaction, it will automatically launch a NVPS transaction on their behalf.

NDPIX Background Information

NDPIX is managed by the Drug Enforcement Agency (DEA) and operates at the Department of Justice computer center in Rockville, Maryland, via a secure communication connection to the Nlets network and is available 24 hours per day (less end-of-day maintenance), seven days per week.

NDPIX provides automated response "Point of Contact" (POC) information on active cases to state, local and Federal law enforcement agencies. Records are kept in the database for 180 days and then purged unless updated or renewed. Entry makers have the option of requesting lists of their records in the database.

To participate in this program a law enforcement agency signs a "Participation Agreement" with DEA and, in return, DEA assigns NDPIX User IDs and Passwords.

Agencies interested in learning more about this application should contact DEA's NDPIX Support Staff at 1-800-276-5558. They will provide brochures, participation agreement information or answer additional questions on NDPIX.

Processing of NDPIX transactions includes the following basic operations:

A law enforcement agency submits an entry on a target who is under active investigation for
violation of drug laws. The law enforcement agency can later update or renew the entry.
NDPIX then:
  • Validates the record to assure that the transaction contains an authorized ORI, User ID
    and Password.
  • Validates the record to assure that it contains at least the mandatory fields of data and that
    the data fields are valid.
  • Notifies the entry maker of any errors found in the entry, update or renewal.
  • Adds the valid entry to the database or updates an earlier entry.
  • Searches the database for matches to the entry, update or renewal.
  • Sends POC information to the entry maker on up to 50 matchers and indicates when no matches
    had been found.
  • Sends the POC of the entry or update to owners of matching records.

Overview

The National Drug Pointer Index System uses several transaction types as presented below.

Section29-DEX.jpg
Section29-DUX.jpg
Section29-DRX.jpg
Section29-DTX.jpg

Query Requirements

  • NDPIX messages are identified by a transaction type that follows Nlets standards.
  • All messages addressed to NDPIX must be sent to ORI "VADEADX00".
  • NDPIX has a test file and a production or live file.
Agency Activity: ORI to Use:
Agency is testing. Test ORI "VADEADX88".
Agency initiates participation with actual data. Production ORI "VADEADX00".

There is additional information on this test system in a kit provided by DEA.

When an entry is made, the system performs two primary functions.

Enters the data onto the file.

Searches the existing file for similar subjects and DOBs.

Note: All responses may have a message appended indicating "ARMED AND
DANGEROUS" This has been included for officer safety.

Query Field Requirements

The table below describes the requirements for NDPIX messages. The underlined elements are mandatory.

XML Tag: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<n:UserID>
UID/ 8 See NCIC
manual.
User ID number
<n:PasswordText>
PWD/ 8 Alphanumeric Password
<n:CaseID>
OCA/ Varies See NCIC
manual.
Case number
<j:ContactPerson>
POC/ Varies See NCIC
manual.
Point of Contact;
Name (last, first MI)
<j:ContactTitle>
PTL/ 4 See NCIC
manual.
Title of Contact
<j:ContactOrganization>
POC
Organization
Varies See NCIC
manual.
Name of Law
Enforcement Agency
<j:ContactTelephoneNumber>
PPN/ 10 See NCIC
manual.
Phone number of
Contact
<j:Person>
  <j:PersonName>
    <j:PersonFullName>
NAM/ Varies Alpha
Characters.

Target's name (last
name, first name MI).
May be multiple
occurrences. Inclusion
of either AKA or MON
will satisfy this
mandatory requirement
but all three are
allowed.

<j:PersonSexCode>
SEX/ 1

Code M or F
only, Unknown
not valid

Sex of subject.
The entries that follow are optional data elements.
<j:PersonAlternateName>
AKA/ Varies See NCIC
manual.

Target's alias name
(last name, first
name MI). May be
multiple occurrences.

<n:PersonMonikerName>
MON/ Varies See NCIC
manual.

Target's moniker.
May be multiple
occurrences.

<j:PersonRaceCode>
RAC/ 1 See NCIC
manual.

Race field. Must be
one of the following:
I = American Indian
or Alaskan native.
A = Asian or Pacific
Islander
B = Black
W = White
U = Unknown

<j:PersonBirthDate>
DOB/ 8


(or 2


if Age)

Entered as
ccyy-mm-dd.
See NCIC
manual.

Birth data.
If entered as
estimated age,
NDPIX converts
entry to DOB using
system date as
base.
Must be >16, <100
years. Multiple
occurrences allowed.

<n:Requestor>
FOR/ Varies See NCIC
manual.

Name of the person
who authorized or
requested entry of
the transaction.

<j:PersonHeightMeasure>
HGT/ 3

3 digits: Entry
5'9" is entered
HGT/509.

Height. Range is 3'
to 9'.
<j:PersonWeightMeasure>
WGT/ 3

3 digits, zero
suppressed.
E.g., 98 lbs.
entered as
WGT/98

Weight.
<j:PersonEyeColorCode>
EYE/ 3 See NCIC
manual.

Eye color code
BLK = Black
HAZ = Hazel
BLU = Blue
MAR = Maroon
BRO = Brown
PNK = Pink
GRE = Green
MUL = Multicolored
GRY = Gray
Unknown leave blank

<j:PersonHairColorCode>
HAI/ 3 See NCIC
manual.

Hair color code
followed by a
period.
BLK = Black
RED = Red
BLN = Blonde
SDY = Sandy
BRO = Brown
WHI = White
GRY = Gray or
partly gray
Unknown leave
blank.

<j:PersonPhysicalDetails>
SMT/ 3-10 See NCIC
manual.

Scars, marks and
tattoos. Multiple
occurrences allowed.

NOTE: For each of multiple addresses, enter ADR, CIT, STE and ZIP in sequence.
<j:LocationAddress>
ADR/ Varies See NCIC
manual.

Street address of
subject. Multiple
occurrences allowed.

<j:LocationCityName>
CIT/ Varies See NCIC
manual.

City of subject.
Multiple occurrences
allowed.

<j:LocationStateCode.USPostalService>
STE/ 2 See NCIC
manual.

State of subject.
Multiple occurrences
allowed.

<j:LocationPostalCodeID>
ZIP/ 5 or 9 See NCIC
manual.
ZIP code. Multiple
occurrences allowed.
<j:ContactTelephoneNumber>
TEL/ 10 See NCIC
manual.

Telephone number
of subject. Multiple
occurrences allowed.

<j:ContactMobileTelephoneNumber>
SCN/ 10 See NCIC
manual.

Cellular number.
Multiple occurrences
allowed.

<j:ContactPagerNumber>
PAG/ 10 See NCIC
manual.

Pager number.
Multiple occurrences
allowed.

<j:DrugTypeCode>
TYP/ 4

See NCIC
manual; Section
3, Offense
Codes =
DANGEROUS
DRUGS.

Valid NCIC "type of
drug" codes.
Multiple occurrences
allowed.

<n:DrugActivityLocationText>
DAL/ 2 See NCIC
manual.

Location (State or
Country) of drug
activity. Multiple
occurrences allowed.

<n:CautionIndicator>
ADF/ 4 See NCIC
manual.

Caution field. Code
(y) to indicate
armed or dangerous.

<j:PersonFBIID>
FBI/ 9 See NCIC
manual.
FBI number.
<j:PersonSSNID>
SOC/ 9 See NCIC
manual.
Social security #.
<j:Vehicle>
  <j:VehicleLicensePlateID>
LIC/ 1-8 Alphanumeric.

Tag number(s) of
subject's vehicle.
Multiple occurrences
allowed.

  <j:IDIssuingAuthorityText>
LIS/ 2 See NCIC
manual.

State of registration
of subject vehicle.
Multiple occurrences
allowed.

<j:Boat>
  <j:BoatHullID>
BHN/ Varies See NCIC
manual.

Vessel number or
name. Multiple
occurrences allowed.

<j:Aircraft>
  <j:VehicleLicensePlateID>
ACN/ 8 See NCIC
manual.
Aircraft number
<n:CaseTypeText>
TOC/ 1 See NCIC
manual.
For future use, to
identify type of case.
<n:RouterField>
RTE/ Varies N/A

Router field.
Secondary address
(used by state agency
if state is using a
common ORI for its
law enforcement
agencies).

NDPIX Responses to Entries

When an entry is made, the system performs two primary functions.

  • It enters the data onto the file
  • It searches the file for similar subjects and birthdates (DOBs)

Error Messages

When an error is detected, NDPIX will

  • Return the entire text of the message
  • Identify the fields found to be in error.

Below is a listing of the possible error messages that may be returned by NDPIX when a record is entered.

ID ERROR MESSAGE TEXT ERROR DESCRIPTION
00 USER ID/PASSWORD
NOT VALID
Access to NDPIX is denied ' User ID or
Password not valid.
01 ORI NOT VALID FOR NDPIX The ORI is not active in NDPIX.
03 MANDATORY DATA ELEMENT
NOT FOUND
A mandatory data element is missing.
04 KEY WORD NOT VALID A key word is not valid; data element cannot be
processed.
05 NDPIX RECORD NUMBER
MISSING
The NDPIX Number was not entered in an
Update or Renewal
06 UPDATE RECORD NOT
FOUND
The Update found no record in the database.
07 RENEWAL RECORD NOT
FOUND
The Renewal found no record in the database.
08 TEXT MISSING No data was found following a key word.
09 INVALID FORMAT A data element format requirement was violated.
10 INVALID CODE A coded field was not found in the table of
allowable entries.

Matching Record(s) Responses

Using the data in the entered record, NDPIX will scan the existing file selecting records that match several key fields in the entered record.

These include but are not limited to FBI #, SSN, Name, other personal identifiers, address information, etc.

They will notify both the owner of the record and the entering agency of the match(s).

Match Notification Messages

Each match notification record will include the following data:

NDP Number
Renewal Date
Target's Name (or alias or moniker)
Point of Contact Name
Point of Contact Title
Point of Contact Phone #
Armed and Dangerous Caution Notification
Acceptance Notification with count of matches sent
Case Number

Note: Case Number is returned to the owner of a record and not to owners of any
matching records.

Each matching database record is sent by NDPIX to the entering agency as a separate message from NDPIX. For example, if the entered record matches 10 records on the NDPIX database, the entering agency will receive 10 messages. Each owner will receive corresponding notification(s).

Notification of a successful entry when no match is detected will include the following data:

NDP Number
Renewal Data
Case Number
Target's Name (or alias or moniker)
Acknowledgment of record acceptance with no matches found

NDPIX will also notify the owner of the matched record on the database of the fact that a similar record has been entered. This notification will include the following data:

NDP Number
Renewal Date
Case Number (of owner record)
Target's Name (or alias or moniker)
Point of Contact Name (entry maker)
Point of Contact Title (entry maker)
Point of Contact Phone (entry maker)
Armed and Dangerous Caution Notification
Acknowledgment notification

NDPIX sends "Match Notification" messages for only the first 50 matches.

Below are the possible messages that the user may receive after the entry has been completed and the file searched.

20 ENTRY ACCEPTED - NO
MATCHES
The new entry found no matching records in the
database.
21 EXCEEDDS 50 MATCHES Only the first fifty matches are provided.
22 MATCHED RECORD

A database record(s) matched the entry. Each
matching database record is sent as a separate
message.

60/61 RECORD TO BE PURGED Record to be purged in 30/15 days.
62 RECORD PURGED Record has been purged.
NOTE: When an entry is successfully processed, a renewal date is returned with
the "entry acknowledgment" message.

Updating an Existing Record

Users have the ability to update any field in a record except the NDPIX number (NDP/) and the entering ORI by sending an Update transaction (message type = DUX).

It is important to recognize that an update of a record renews the record. In other words, the purge date is recalculated to occur 180 days from the date of the update.

The only mandatory data elements in this transaction are the NDP number assigned by the system, User ID, Password, Target Name, Alias or Moniker.

NDPIX will respond with either a standard error message or one of the responses described in the section below.

Responses to Updating an Existing Record

In all cases the response message type will be "DUA".

The ORI is found only in the Header portion of the message.

30 UPDATE ACCEPTED ' NO MATCHES The update found no matching records in
the database.
31 UPDATE ACCEPTED ' OVER 50
MATCHES
Only the first fifty matches are provided.
32 UPDATE ACCEPTED ' MATCHED
RECORD
The database record matched the update.
51 MATCHED TO YOUR RECORD '
UPDATE
The record in the database matched to
an Update.

Renewing an Existing Record

NDPIX purges records after they have been in the database for 180 days from the Date of Record, unless either renewed or updated.

  • To renew the record, the record owner submits a "DRX" transaction type.
  • The only fields required in this unique message key are the NDPIX number (
    <NDPIXNumber>
    
    for XML or NDP/ for Legacy), User ID, password and subject name, alias or a moniker.
  • All responses to 'DRX' transactions will use the message type 'DRR'.
Responses to Updating an Existing Record

The following responses may be sent from NDPIX to acknowledge a renewal request.

40 RENEWAL ACCEPTED - NO MATCHES The renewal found no matching
records in the database.
41 RENEWAL ACCEPTED - OVER 50
MATCHES
Only the first fifty matches are provided.
42 RENEWAL ACCEPTED ' MATCHED
RECORD
The database record matched the
Renewal.
52 MATCHED TO YOUR RECORD '
RENEWAL
Your record in the database matched to a
Renewal.

Notifications on Record Purges

NDPIX holds entries in its database for 180 days after which they are purged.

  • The "purge" clock is reset if the record is either renewed or updated.
  • The system performs this aging and purging operation on a once-per-day basis.
  • NDPIX will notify the entry maker of pending record purges 30 days and then 15 days before the record is purged.
  • When the record is purged NDPIX will notify the entry maker.
  • All of these notifications will use the "DRR" message key.
  • The following data elements will be included in the purge message.

Target Name
Case Number
NDPIX number
Notification of purge status

NDPIX Reports

In addition to Points of Contact messages, NDPIX offers supplemental information to its participants. Some of this information is provided directly over the Nlets network while other information is provided off-line in response to written request.

The range of information includes:

  • copies of one's own records currently in the database.
  • copies of audit records created by NDPIX on their entries.
  • copies of their membership data.
  • copies of operating statistics maintained and published by NDPIX.

Requests for records by either a User ID or an ORI are handled via Nlets in standard NDPIX format.

Requests for larger volume lists such as for (1) an Investigative Unit, (2) an entire law enforcement agency or (3) other multiple User ID selections are submitted to DEA's Intelligence Division.

Responses to the larger requests are recorded on diskette or tape cassette and delivered via the U.S. mails.

Data Availability Distribution
Quality assurance statistics Participating law enforcement
agencies

Daily and monthly reports.
Distributed by mail.
Requests are directed to
DEA's Intelligence Division.

Audit information on all
system usage

Law enforcement agencies are
entitled to copies of audit data
on their NDPIX activity.
NDPIX will provide this data
only to individuals designated
by the Chief of the LEA as
authorized to receive such data.

Requests are directed to
DEA's Intelligence Division.

Database of membership
information on each
participant including names,
addresses, User ID and ORI
assignments.

Copies of these records are
available to participating law
enforcement agencies

Distributed by mail.
Requests are directed to
DEA's Intelligence Division.

Copies of Database Records

Participants may request copies of their records in the database. Security and data volume considerations require that there be two categories of this reporting:

  • Those that are submitted and responded to as NDPIX messages (On-line Requests)
  • Those that are requested via contact with DEA's Intelligence Division and satisfied via U.S. mails (Off-line Requests).

On-line Requests

Returned database records will contain only mandatory fields.

To receive a copy of all the records originating from an ORI, the requestor enters an ORI to signify to NDPIX that the request is ORI based. The requester has the option to enter Case Number in order to minimize record output.

Where the search finds no records matching either the requested User ID or ORI, NDPIX responds with the following message:

MSG/80- FOR REPORT-NO RECORDS FOUND.

Off-line Requests

Off-line requests are submitted to DEA's Intelligence Division. Results, written on diskette or tape cassette, are sent to the requestor via the U.S. mails. This off-line processing of requests serves to minimize the risk of compromising the security of NDPIX data and also helps to prevent overburdening the communication lines serving the system.

The following types of lists are available.

  • All Records for Multiple User IDs
  • All Records for Multiple ORIs
  • All Records for a Point of Contact within one's agency
  • All Records for an Investigative Unit
  • All Records for an LEA

Copies of Audit Records

NDPIX will provide this data only to individuals designated by the Chief of the LEA as authorized to receive such data. Requests for copies of NDPIX audit records are directed to DEA's Intelligence Division.

Responses to such requests will be recorded on either diskette or tape cassette and sent Registered via U.S. mails.

Statistical Reports

NDPIX maintains a database of data quality assurance statistics from which it produces daily and monthly reports. Monthly reports are available to participating law enforcement agencies and are distributed by mail. Copies of sample reports are available for review by contacting DEA's Intelligence Division.

Selections may be based on:

  • LEA
  • Investigative Unit
  • ORI
  • User ID

Registration Data

The NDPIX Participant Register maintains membership data on the law enforcement agencies that are enrolled in NDPIX.

The Register contains:

  • Agency name and address
  • Names and telephone numbers of key agency officials
  • ORIs and User IDs of individuals authorized to use NDPIX.

Member agencies direct requests for copies of their Registry data to DEA's Intelligence Division.

Top

GJXDM (DEPRECATED)

GJXDM has been deprecated. Please contact Nlets for additional assistance with GJXDM.

Top

NIEM

National Drug Pointer Index System NIEM Specifications

This section describes the format and provides examples for queries to and responses from the National Drug Pointer Index System (NDPIX) which is an information sharing system for Law Enforcement Agencies (LEAs).

NDPIX messages are identified by a transaction type that follows Nlets standards. All messages addressed to NDPIX must be sent to ORI "VADEADX00".

Note: NDPIX has a test file and a production or live file.
  • When an agency is testing, use the test ORI "VADEADX88".
  • When an agency initiates participation with actual data, use the production ORI "VADEADX00".
There is additional information on this test system in a kit provided by DEA.

NDPIX messages conform to Nlets message format conventions and consist of two parts: (1) the standard Nlets message header and (2) the formatted entry.

When an entry is made to NDPIX, the system performs two primary functions.

  • It enters the data onto the file.
  • It searches the existing file for similar subjects and DOBs.
Note: All responses may have a message appended indicating "ARMED AND DANGEROUS" This has been included for
officer safety.

NDPIX sends a response for every transaction as follows:

  • Point of Contact (POC) for those transactions matching records in the database.
  • Acknowledgments for valid transactions which had no matches.
  • Error message on rejected transactions.

NDPIX assigns a unique number (

<n2:NDPIXID>

) to each valid transaction which record owner would use in any future updating of the record.

Note: When an entry is successfully processed a renewal date is returned with the "entry acknowledgment" message.

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: Entry into NDPIX System (DEX), Modification on NDPIX System (DUX), Renew NDPIX Record (DRX) and Response to NDPIX Message (DEA, DUA, DRR & DTR).

Entry Formats

Entry into NDPIX System (DEX)

n2:NLETSUpdateData

  n2:NDPIXEntry
  Encapsulates the information about a NDPIX entry

    nc:Case
    An aggregation of information about a set of related activities and events.

      nc:ActivityIdentification
      An identification that references an activity.

        nc:IdentificationID
        A value that identifies something.
        Optional Agency case number.

    n2:DocumentSubmitterPasswordText
    Optional password corresponding to the User ID.

    n2:DocumentSubmitterUserIDText
    Optional User ID.

    n2:RequestorDescriptionText
    This optional element contains the person who authorized or requested transaction entry.
    This optional element contains the person who authorized or requested transaction entry.

    n2:RouterFieldText
    Optional element will contain router Field. Secondary address (used by state agency if state is using a common
    ORI for its law enforcement agencies).
    This optional element will contain router Field. Secondary address (used by state agency if state is using a
    common ORI for its law enforcement agencies).

    nc:DocumentSubmitter
    An entity responsible for making the resource available.

      nc:EntityOrganization
      An organization capable of bearing legal rights and responsibilities.

        nc:OrganizationName
        A name of an organization.
        This optional element contains the name of the law enforcement agency.

        nc:OrganizationPrimaryContactInformation
        A preferred means of contacting an organization.

          nc:ContactTelephoneNumber
          A telephone number for a telecommunication device by which a person or organization may be contacted.
          The telephone number should actually be placed in nc:FullTelephoneNumber/nc:TelephoneNumberFullID

      nc:EntityPerson
      A person capable of bearing legal rights and responsibilities.

        nc:PersonName
        A combination of names and/or titles by which a person is known.

          nc:PersonFullName
          A complete name of a person.
          This required element must contain the full name of the contact person in the format LAST,FIRST MIDDLE.

  n2:QueryPerson
  This element encapsulates the information about the person being queried.

    n2:PersonCautionIndicator
    This optional element will contain caution field. True indicates armed or dangerous.
    This optional element will contain caution field. Code (y) to indicate armed or dangerous.

    n2:PersonContactInformation
    This element contains contact information.

      nc:ContactTelephoneNumber
      A telephone number for a telecommunication device by which a person or organization may be contacted. The
      telephone number should actually be placed in nc:FullTelephoneNumber/nc:TelephoneNumberFullID.

      nc:ContactMobileTelephoneNumber
      A telephone number for a mobile telecommunication device by which a person or organization may be contacted.
      The telephone number should actually be placed in nc:FullTelephoneNumber/nc:TelephoneNumberFullID.

      nc:ContactPagerNumber
      A telephone number for a paging device by which a person or organization may be contacted. The telephone
      number should actually be placed in nc:FullTelephoneNumber/nc:TelephoneNumberFullID.

    n2:PersonResidentialAddress
    This optional element contains the street address. Actual value should go in the subelement nc:StreetFullText.
    This optional element contains information about the residence of the subject.

      nc:LocationStreet
      A road, thoroughfare or highway.

        nc:StreetFullText
        A complete reference for a street.
        This optional element contains the street address.

      nc:LocationCityName
      A name of a city or town.
      This optional element contains the city.

        nc:LocationStateName
        A state, commonwealth, province, or other such geopolitical subdivision of a country.
        This optional element contains the state. Code should match USPS codes.

      nc:LocationPostalCode
      An identifier of a post office-assigned zone for an address.
      This optional element contains the postal code, or zip code. The actual value should be contained in the
      subelement j:ID.

    j4:PersonAugmentation
    Additional information about a person.

      j4:PersonFBIIdentification
      A number issued by the FBI's Automated Fingerprint Identification System (AFIS) based on submitted
      fingerprints.

        nc:IdentificationID
        A value that identifies something.
        This optional element will contain the FBI number of the person being queried on.

    nc:PersonAgeMeasure
    A measurement of the age of a person.

      nc:MeasurePointValue
      A specific measurement value.
      This conditional element contains the age of the person being queried on. Either Date of Birth or Age is required.

    nc:PersonAlternateName
    An alternate name used by a person.
    This optional element encloses subelements containing alias name data for query. May occur multiple times.

      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.

    nc:PersonBirthDate
    A date a person was born.

      nc:Date
      A full date.
      This conditional 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. Either Date of Birth or Age is required.

    nc:PersonEyeColorText
    A color of the eyes of a person.
    Optional element containing a subject's eye color. Value should conform to NCIC EYE codes.

    nc:PersonHairColorText
    A color of the hair of a person.
    Optional element containing a subject's hair color. Value should conform to NCIC HAI codes.

    nc:PersonHeightMeasure
    A measurement of the height of a person.

      nc:MeasurePointValue
      A specific measurement value.
      Optional element containing subject's height in NCIC format ' 3 digits indicating feet followed by inches. For
      instance, a subject that is 5'11" would have the height value "511".

    n2:PersonName
    This element encloses subelements containing name data for query.

      n2:PersonMonikerName
      This optional element will contain the target_s moniker. May occur multiple times.
      This optional element will contain the target's moniker. May occur multiple times.

      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.

    nc:PersonRaceText
    A classification of a person based on factors such as geographical locations and genetics.
    Optional element conforming to NCIC race codes.

    nc:PersonSexText
    A gender or sex of a person.
    This optional element will contain the target's sex. Value must be M or F.

    nc:PersonSSNIdentification
    A unique reference to a living person; assigned by the United States Social Security Administration.

      nc:IdentificationID
      A value that identifies something.
      Optional element containing SSN.

    nc:PersonWeightMeasure
    A measurement of the weight of a person.

      nc:MeasurePointValue
      A specific measurement value.
      Optional element containing the subject's weight in pounds.

  nc:Aircraft
  A mode of transportation capable of flying in the air.

    nc:AircraftTailID
    An identifier of an aircraft.
    This optional element will contain the registration number of the aircraft.

  nc:Vehicle
  A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.

    nc:ConveyanceRegistrationPlateIdentification
    An identification on a metal plate fixed to a conveyance.

      nc:IdentificationID
      A value that identifies something.
      This optional element will contain the license plate number to be queried.

      nc:IdentificationSourceText
      A person, organization, or locale which issues an identification.
      This optional element will contain the issuing state of the license plate.

  n2:DrugActivity
  Describes illicit drug activity.

    nc:LocationDescriptionText
    A description of a location.
    This optional element will contain location (State or Country) of drug activity. Multiple occurrences allowed.

    nc:Drug
    A legal or illegal substance that can be used as a medicine or a narcotic.

  nc:Vessel
  A mode of transportation capable of transport by water.

    nc:VesselHullIdentification
    An identification found on the main body or frame of a vessel.

      nc:IdentificationID
      A value that identifies something.
      This optional element will contain the hull number for query.

Update Formats

Modification on NDPIX System (DUX)

n2:NLETSUpdateData

  n2:NDPIXEntry
  Encapsulates the information about a NDPIX entry

    nc:Case
    An aggregation of information about a set of related activities and events.

      nc:ActivityIdentification
      An identification that references an activity.

        nc:IdentificationID
        A value that identifies something.
        Optional Agency case number.

    n2:DocumentSubmitterPasswordText
    Optional password corresponding to the User ID.

    n2:DocumentSubmitterUserIDText
    Optional User ID.

    n2:RequestorDescriptionText
    This optional element contains the person who authorized or requested transaction entry.
    This optional element contains the person who authorized or requested transaction entry.

    n2:NDPIXID
    Mandatory NDPIX number for record identification.

    n2:RouterFieldText
    Optional element will contain router Field. Secondary address (used by state agency if state is using a common
    ORI for its law enforcement agencies).
    This optional element will contain router Field. Secondary address (used by state agency if state is using a
    common ORI for its law enforcement agencies).

    nc:DocumentSubmitter
    An entity responsible for making the resource available.

      nc:EntityOrganization
      An organization capable of bearing legal rights and responsibilities.

        nc:OrganizationName
        A name of an organization.
        This optional element contains the name of the law enforcement agency.

        nc:OrganizationPrimaryContactInformation
        A preferred means of contacting an organization.

          nc:ContactTelephoneNumber
          A telephone number for a telecommunication device by which a person or organization may be contacted.
          The telephone number should actually be placed in nc:FullTelephoneNumber/nc:TelephoneNumberFullID.

      nc:EntityPerson
      A person capable of bearing legal rights and responsibilities.

        nc:PersonName
        A combination of names and/or titles by which a person is known.

          nc:PersonFullName
          A complete name of a person.
          This required element must contain the full name of the contact person in the format LAST,FIRST MIDDLE.

  n2:QueryPerson
  This element encapsulates the information about the person being queried.

    n2:PersonCautionIndicator
    This optional element will contain caution field. True indicates armed or dangerous.
    This optional element will contain caution field. Code (y) to indicate armed or dangerous.

    n2:PersonContactInformation
    This element contains contact information.

      nc:ContactTelephoneNumber
      A telephone number for a telecommunication device by which a person or organization may be contacted. The
      actual telephone number should be placed in nc:FullTelephoneNumber/nc:TelephoneNumberFullID.

      nc:ContactMobileTelephoneNumber
      A telephone number for a mobile telecommunication device by which a person or organization may be contacted.
      The actual telephone number should be placed in nc:FullTelephoneNumber/nc:TelephoneNumberFullID.

      nc:ContactPagerNumber
      A telephone number for a paging device by which a person or organization may be contacted. The actual
      telephone number should be placed in nc:FullTelephoneNumber/nc:TelephoneNumberFullID.

    n2:PersonResidentialAddress
    This optional element contains the street address. Actual value should go in the subelement nc:StreetFullText.
    This optional element contains information about the residence of the subject.

      nc:LocationStreet
      A road, thoroughfare or highway.

        nc:StreetFullText
        A complete reference for a street.
        This optional element contains the street address.

      nc:LocationCityName
      A name of a city or town.
      This optional element contains the city.

        nc:LocationStateName
        A state, commonwealth, province, or other such geopolitical subdivision of a country.
        This optional element contains the state. Code should match USPS codes.

      nc:LocationPostalCode
      An identifier of a post office-assigned zone for an address.
      This optional element contains the postal code, or zip code. The actual value should be contained in the
      subelement j:ID.

    j4:PersonAugmentation
    Additional information about a person.

      j4:PersonFBIIdentification
      A number issued by the FBI's Automated Fingerprint Identification System (AFIS) based on submitted
      fingerprints.

        nc:IdentificationID
        A value that identifies something.
        This optional element will contain the FBI number of the person being queried on.

    nc:PersonAgeMeasure
    A measurement of the age of a person.

      nc:MeasurePointValue
      A specific measurement value.
      This conditional element contains the age of the person being queried on. Either Date of Birth or Age is required.

    nc:PersonAlternateName
    An alternate name used by a person.
    This optional element encloses subelements containing alias name data for query. May occur multiple times.

      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.

    nc:PersonBirthDate
    A date a person was born.

      nc:Date
      A full date.
      This conditional 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. Either Date of Birth or Age is required.

    nc:PersonEyeColorText
    A color of the eyes of a person.
    Optional element containing a subject's eye color. Value should conform to NCIC EYE codes.

    nc:PersonHairColorText
    A color of the hair of a person.
    Optional element containing a subject's hair color. Value should conform to NCIC HAI codes.

    nc:PersonHeightMeasure
    A measurement of the height of a person.

      nc:MeasurePointValue
      A specific measurement value.
      Optional element containing subject's height in NCIC format ' 3 digits indicating feet followed by inches. For
      instance, a subject that is 5'11" would have the height value "511".

    n2:PersonName
    This element encloses subelements containing name data for query.

      ;n2:PersonMonikerName
      This optional element will contain the target_s moniker. May occur multiple times.
      This optional element will contain the target's moniker. May occur multiple times.

      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.

    nc:PersonRaceText
    A classification of a person based on factors such as geographical locations and genetics.
    Optional element conforming to NCIC race codes.

    nc:PersonSexText
    A gender or sex of a person.
    This optional element will contain the target's sex. Value must be M or F.

    nc:PersonSSNIdentification
    A unique reference to a living person; assigned by the United States Social Security Administration.

      nc:IdentificationID
      A value that identifies something.
      Optional element containing SSN.

    nc:PersonWeightMeasure
    A measurement of the weight of a person.

      nc:MeasurePointValue
      A specific measurement value.
      Optional element containing the subject's weight in pounds.

  nc:Aircraft
  A mode of transportation capable of flying in the air.

    nc:AircraftTailID
    An identifier of an aircraft.
    This optional element will contain the registration number of the aircraft.

  nc:Vehicle
  A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.

    nc:ConveyanceRegistrationPlateIdentification
    An identification on a metal plate fixed to a conveyance.

      nc:IdentificationID
      A value that identifies something.
      This optional element will contain the license plate number to be queried.

      nc:IdentificationSourceText
      A person, organization, or locale which issues an identification.
      This optional element will contain the issuing state of the license plate.

  n2:DrugActivity
  Describes illicit drug activity.

    nc:LocationDescriptionText
    A description of a location.
    This optional element will contain location (State or Country) of drug activity. Multiple occurrences allowed.

    nc:Drug
    A legal or illegal substance that can be used as a medicine or a narcotic.

  nc:Vessel
  A mode of transportation capable of transport by water.

    nc:VesselHullIdentification
    An identification found on the main body or frame of a vessel.

      nc:IdentificationID
      A value that identifies something.
      This optional element will contain the hull number for query.

Renew Formats

Renew NDPIX Record (DRX)

n2:NLETSUpdateData

  n2:NDPIXEntry
  A structure that defines the root element of an NLETS message.

    n2:DocumentSubmitterPasswordText
    Optional password corresponding to the User ID.

    n2:DocumentSubmitterUserIDText
    Optional User ID.

    n2:NDPIXID
    Mandatory NDPIX number for record identification.

  n2:Person
  This element encapsulates the information about the person being updated.

    nc:PersonName
    A combination of names and/or titles by which a person is known.

      nc:PersonFullName
      A complete name of a person.
      This required element must contain the full name of the person in the format LAST,FIRST MIDDLE.

Response Formats

Response to NDPIX Message (DEA,DUA,DRR,DTR)

n2:NLETSResponseData

  n2:ResponseText


  This element will contain the free text response. Nlets recommends the use of

<!&#91;CDATA&#91;&#93;&#93;>

tags to ensure that the


  response does not contain any characters illegal in XML.

National Drug Pointer Index System NIEM Examples

Example 1: A query to enter data into the NDPIX System.

<n2:NLETS 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"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>DEX</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>VADEADX00</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSUpdateData n2:key="DEX">
    <n2:NDPIXEntry>
      <nc:DocumentSubmitter>
        <nc:EntityOrganization>
          <nc:OrganizationName>AZ-NLETS</nc:OrganizationName>
          <nc:OrganizationPrimaryContactInformation>
            <nc:ContactTelephoneNumber>
              <nc:FullTelephoneNumber>
                <nc:TelephoneNumberFullID>6025551234</nc:TelephoneNumberFullID>
              </nc:FullTelephoneNumber>
            </nc:ContactTelephoneNumber>
          </nc:OrganizationPrimaryContactInformation>
        </nc:EntityOrganization>
        <nc:EntityPerson>
          <nc:PersonName />
        </nc:EntityPerson>
      </nc:DocumentSubmitter>
      <nc:Case>
        <nc:ActivityIdentification />
      </nc:Case>
      <n2:RouterFieldText>
         CIB:0000000000000000:0000000000000000;-RTR *XXXX000000-FWD
         XX0000000-UID XXX000000-NDP 000000-TOT 00:00:00
      </n2:RouterFieldText>
    </n2:NDPIXEntry>
    <n2:QueryPerson>
      <nc:PersonAgeMeasure />
      <nc:PersonAlternateName />
      <nc:PersonBirthDate>
        <nc:Date>1950-01-01</nc:Date>
      </nc:PersonBirthDate>
      <nc:PersonHeightMeasure />
      <nc:PersonSexText>M</nc:PersonSexText>
      <nc:PersonSSNIdentification />
      <nc:PersonWeightMeasure />
      <j4:PersonAugmentation xmlns:j="http://niem.gov/niem/domains/jxdm/4.1">
        <j4:PersonFBIIdentification />
      </j4:PersonAugmentation>
    </n2:QueryPerson>
    <n2:DrugActivity>
      <nc:Drug />
    </n2:DrugActivity>
  </n2:NLETSUpdateData>
</n2:NLETS>

Example 2: A response to enter data into the NDPIX Record System.

<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>DEA</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>VADEADX00</nh2:OriginatingORIID>
		<nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
		<nh2:MessageReceiveDate>12/08/2019</nh2:MessageReceiveDate>
		<nh2:MessageReceiveTime>22:37</nh2:MessageReceiveTime>
		<nh2:MessageSendDate>12/08/2019</nh2:MessageSendDate>
		<nh2:MessageSendTime>22:37</nh2:MessageSendTime>
		<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
		<nh2:SendMessageNumeric>00318</nh2:SendMessageNumeric>
	</n2:NLETSMessageHeader>
	<n2:NLETSResponseData n2:key="DEA">
		<n2:ResponseText>
          20-ENTRY ACCEPTED-NO MATCHES
		</n2:ResponseText>
	</n2:NLETSResponseData>
</n2:NLETS>

Example 3: A query to modify a record in the NDPIX System.

<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>DUX</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>VADEADX00</nh2:DestinationORIID>
	</n2:NLETSMessageHeader>
	<n2:NLETSUpdateData n2:key="DUX">
		<n2:NDPIXEntry>
			<nc:DocumentSubmitter>
				<nc:EntityOrganization>
					<nc:OrganizationName>NLETS</nc:OrganizationName>
					<nc:OrganizationPrimaryContactInformation>
						<nc:ContactTelephoneNumber>
							<nc:FullTelephoneNumber>
								<nc:TelephoneNumberFullID>8005284020</nc:TelephoneNumberFullID>
							</nc:FullTelephoneNumber>
						</nc:ContactTelephoneNumber>
					</nc:OrganizationPrimaryContactInformation>
				</nc:EntityOrganization>
				<nc:EntityPerson>
					<nc:PersonName>
						<nc:PersonFullName>NLETS_ANALYST</nc:PersonFullName>
					</nc:PersonName>
				</nc:EntityPerson>
			</nc:DocumentSubmitter>
			<nc:Case>
				<nc:ActivityIdentification>
					<nc:IdentificationID>00-111</nc:IdentificationID>
				</nc:ActivityIdentification>
			</nc:Case>
			<n2:DocumentSubmitterPasswordText>XXXXXXXX</n2:DocumentSubmitterPasswordText>
			<n2:DocumentSubmitterUserIDText>AAA11111</n2:DocumentSubmitterUserIDText>
			<n2:NDPIXID>111111</n2:NDPIXID>
		</n2:NDPIXEntry>
		<n2:QueryPerson>
			<nc:PersonAlternateName />
			<nc:PersonBirthDate>
				<nc:Date>1950-01-01</nc:Date>
			</nc:PersonBirthDate>
			<nc:PersonHeightMeasure />
			<nc:PersonRaceText>W</nc:PersonRaceText>
			<nc:PersonSexText>M</nc:PersonSexText>
			<nc:PersonSSNIdentification>
				<nc:IdentificationID>123456789</nc:IdentificationID>
			</nc:PersonSSNIdentification>
			<n2:PersonContactInformation />
			<n2:PersonResidentialAddress>
				<nc:LocationStreet>
					<nc:StreetFullText>1234 ANY ST</nc:StreetFullText>
				</nc:LocationStreet>
				<nc:LocationCityName>PHOENIX</nc:LocationCityName>
				<nc:LocationStateName>AZ</nc:LocationStateName>
				<nc:LocationPostalCode>85000</nc:LocationPostalCode>
			</n2:PersonResidentialAddress>
		</n2:QueryPerson>
		<n2:DrugActivity>
			<nc:Drug />
		</n2:DrugActivity>
		<nc:Vessel>
			<nc:VesselHullIdentification />
		</nc:Vessel>
	</n2:NLETSUpdateData>
</n2:NLETS>

Example 4: A response to modify a record in the NDPIX System.

<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>DUA</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>VADEADX00</nh2:OriginatingORIID>
		<nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
		<nh2:MessageReceiveDate>12/08/2019</nh2:MessageReceiveDate>
		<nh2:MessageReceiveTime>22:51</nh2:MessageReceiveTime>
		<nh2:MessageSendDate>12/08/2019</nh2:MessageSendDate>
		<nh2:MessageSendTime>22:51</nh2:MessageSendTime>
		<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
		<nh2:SendMessageNumeric>00338</nh2:SendMessageNumeric>
	</n2:NLETSMessageHeader>
	<n2:NLETSResponseData n2:key="DUA">
		<n2:ResponseText>
         30-UPDATE ACCEPTED-NO MATCHES
		</n2:ResponseText>
	</n2:NLETSResponseData>
</n2:NLETS>

Example 5: A response to request a NDPIX Record.

<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>DTR</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>VADEADX00</nh2:OriginatingORIID>
		<nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
		<nh2:MessageReceiveDate>12/08/2019</nh2:MessageReceiveDate>
		<nh2:MessageReceiveTime>22:53</nh2:MessageReceiveTime>
		<nh2:MessageSendDate>12/08/2019</nh2:MessageSendDate>
		<nh2:MessageSendTime>22:53</nh2:MessageSendTime>
		<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
		<nh2:SendMessageNumeric>00339</nh2:SendMessageNumeric>
	</n2:NLETSMessageHeader>
	<n2:NLETSResponseData n2:key="DTR">
		<n2:ResponseText>
         **********************************************
		</n2:ResponseText>
	</n2:NLETSResponseData>
</n2:NLETS>

Top

Legacy (DEPRECATED)

National Drug Pointer Index System Legacy Specifications

This section describes the format and provides examples for queries to and responses from the National Drug Pointer Index System (NDPIX) which is an information sharing system for Law Enforcement Agencies (LEAs).

NDPIX messages are identified by a transaction type that follows Nlets standards. All messages addressed to NDPIX must be sent to ORI "VADEADX00".

Note: NDPIX has a test file and a production or live file.

  • When an agency is testing, use the test ORI "VADEADX88".
  • When an agency initiates participation with actual data, use the production ORI "VADEADX00".


There is additional information on this test system in a kit provided by DEA.

NDPIX messages conform to Nlets message format conventions and consist of two parts: (1) the standard Nlets message header and (2) the formatted entry.

The formatted entry is made up of mandatory and optional data elements. The mandatory elements are underlined in the table below (and with the exception of Control Field and TXT, they are the first 11 entries in the table).

Entry # Char. Explanation
Message Type 4 A 3 character message type followed by a period.
Sending ORI 9 Sending ORI followed by a period (Found in Message Header).
Destination ORI 9 Destination ORI followed by a period (Found in Message Header).
* 1 Asterisk to identify the start of the control field (omit if no control
field present).
Control Field 10 Optional Control field followed by a period.
TXT 3 Identifies beginning of text of message.
UID/ 4 Prefix to identify User ID field.
User ID 8 User ID number followed by a period.
PWD/ 4 Prefix to identify password.
Password 8 Password followed by a period.
OCA/ 4 Prefix to identify case number.
Case Number Variable Case number followed by a period.
POC/ 4 Prefix to identify Point of Contact.
Point of Contact Variable Name (last, first MI) followed by a period.
PTL/ 4 Prefix to identify Title of Contact.
POC
Organization
Variable Name of Law Enforcement Agency.
PPN/ 4 Prefix to identify phone number of Contact.
Phone number 10 Phone number of contact followed by a period.
NAM/ 4 Prefix to identify target's name. May be multiple occurrences.
Name Variable

Target's name (last name, first name MI) followed by a period.
May be multiple occurrences. Inclusion of either AKA or MON will
satisfy this mandatory requirement but all three are allowed.

SEX/ 4 Prefix to identify sex of subject.
Sex 1 Code followed by period. M or F only, Unknown not valid.
AKA/ 4 Prefix to identify Alias name. May be multiple occurrences.
Alias name Variable Target's alias (last name, first name MI) followed by a period.
May be multiple occurrences.
MON/ 4 Prefix to identify targets moniker. May be multiple occurrences.
Moniker Variable Target's moniker followed by a period. May be multiple
occurrences.
RAC/ 4 Prefix to identify race field.
Race 1

Race field followed by a period. Must be one of the following:
I = American Indian or Alaskan native
A = Asian or Pacific Islander
B = Black
W = White
U = Unknown

DOB/ 4 Prefix to identify data of birth.
Date of Birth

8
(or 2 if
Age)

Entered as CCYYMMDD. If entered as estimated age, NDPIX
converts entry to DOB using system date as base. Must be >16,
<100 years. Multiple occurrences allowed.

FOR/ 4 Prefix to identify the name of the person for whom this record is
requested.
For Variable Person who authorized or requested entry of the transaction.
HGT/ 4 Prefix to identify height.
Height 3 Height is entered as 3 digits followed by a period. The entry
5'9" is entered HGT/509. Range is 3' to 9'.
WGT/ 4 Prefix to identify weight.
Weight 3 Entered as 3 digits, zero suppressed followed by a period.
E.g., 98 lbs. entered as WGT/98.
EYE/ 4 Prefix to identify eye color.
Eye 3

Eye color code followed by a period
BLK = Black HAZ = Hazel
BLU = Blue MAR = Maroon
BRO = Brown PNK = Pink
GRE = Green MUL = Multicolored
GRY = Gray Unknown leave blank

HAI/ 4 Prefix to identify hair color.
Hair color 3

Hair color code followed by a period.
BLK = Black RED = Red
BLN = Blonde SDY = Sandy
BRO = Brown WHI = White
GRY = Gray or partly gray Unknown leave blank.

SMT/ 4 Prefix to identify scars, marks and tattoos.
Scars, marks and
tattoos
3-10 Scars, marks and tattoos followed by a period. Multiple
occurrences allowed.
NOTE: For each of multiple addresses, enter ADR, CIT, STE and ZIP in sequence.
ADR/ 4 Prefix to identify address of subject.
Address (Street) Variable Address of subject followed by a period. Multiple occurrences
allowed.
CIT/ 4 Prefix to identify city.
City Variable City of subject followed by a period. Multiple occurrences allowed.
STE/ 4 Prefix to identify State.
State 2 State of subject followed by a period. Multiple occurrences allowed.
ZIP/ 4 Prefix to identify ZIP code.
ZIP code 5 or 9 ZIP code followed by a period. Multiple occurrences allowed.
TEL/ 4 Prefix to identify telephone number.
Telephone
number
10 Telephone number of subject followed by a period. Multiple
occurrences allowed.
SCN/ 4 Prefix to identify cellular number.
Cellular number 10 Cellular number followed by a period. Multiple occurrences
allowed.
PAG/ 4 Prefix to identify pager number.
Pager number 10 Pager number followed by a period. Multiple occurrences allowed.
TYP/ 4 Prefix to identify type of drug.
Type of Drug 4

Valid "type of drug" codes are listed in the Code Manual of the
NCIC, Section 3, Offense Codes = DANGEROUS DRUGS.
Multiple occurrences allowed.

DAL/ 4 Prefix to identify location-drug activity.
Drug activity
location
2 Location (State or Country) of drug activity followed by a period.
Multiple occurrences allowed.
ADF/ 4 Prefix to identify caution field.
Caution indicator 1 Code (y) to indicate armed or dangerous followed by a period.
FBI/ 4 Prefix to identify FBI number.
FBI Number 9 FBI number followed by a period.
SOC/ 4 Prefix to identify social security #.
SOC 9 SOC followed by a period.
LIC/ 4 Prefix to identify license number of subject.
License # 1-8 Tag number(s) of subject's vehicle followed by a period. Multiple
occurrences allowed.
LIS/ 4 Prefix to identify license state of subject.
License state 2 State of registration of subject vehicle followed by a period.
Multiple occurrences allowed.
BHN/ 4 Prefix to identify vessels number or name.
Vessel number
or name
Variable Vessel number or name followed by a period. Multiple
occurrences allowed.
RES/ 4 Prefix to identify vessel registration state.
Reg. state 2 Vessel registration state. Multiple occurrences allowed.
ACN/ 4 Prefix to identify aircraft number.
Aircraft number 8 Aircraft number followed by a period.
TOC/ 4 Prefix to identify type of case.
Type of case 1 For future use, to identify type of case.
RTE/ 4 Prefix to identify router field.
Router Variable Secondary address (used by state agency if state is using a
common ORI for its law enforcement agencies).

Formats are described in the sections that follow for the four message types (DEX, DUX and DRX) and the resulting responses (DEA, DUA and DRR)

Entry Formats

Prepare the message header with the DEX message type and provide at least the mandatory data elements.

Responses to a New Entry

When an entry is made to NDPIX, the system performs two primary functions.

  • It enters the data onto the file
  • It searches the existing file for similar subjects and DOBs.
Note: All responses (DEA) may have a message appended indicating "ARMED AND
DANGEROUS" This has been included for officer safety.

NDPIX sends a response for every transaction as follows:

  • Point of Contact (POC) for those transactions matching records in the database.
  • Acknowledgments for valid transactions which had no matches
  • Error message on rejected transactions.

NDPIX assigns a unique number (NDP/) to each valid transaction which record owner would use in any future updating of the record.

Note: When an entry is successfully processed a renewal date is returned with the "entry
acknowledgment" message.

Error Response Messages

If the transaction contained data errors, the record would be rejected and an error message sent to the entry maker.

Typical data errors and the appropriate response would include:

  • One or more elements missing.
  • Alphabetic characters in DOB field, for example.
  • The key word OCA was not followed by data.
Note: NDPIX returns the entire input transaction with the error message but replaces the
password (PWD) with all X's.

Message to Update an Earlier Entry

Prepare the message header with the DUX message type and enter the following data elements:

  • User ID
  • Password
  • NDPIX number
  • Name of Target (Alias or Moniker)
  • All data elements to be changed

Users may update any field in a record except the NDPIX Number (NDP/) and the entering ORI.

Responses to Updating a Record

NDPIX returns a response (DUA) for every entry either in the form of "Update Accepted" indicating no matches or match information for accepted records or error messages on rejected input entries. The ORI is found only in the Header portion of the message.

This renews the record for 180 days. The purge date is recalculated to occur 180 days from the date of the update.

Message to Renew an Earlier Entry

NDPIX purges records after they have been in the database for 180 days from the Date of Record unless renewed or updated. To renew the record, the record owner submits a DRX transaction type.

Prepare the message header with the DRX message type and enter the following data elements:

  • User ID
  • Password
  • Name of Target (Alias or Moniker)
  • NDPIX Number of the record to be renewed.

Responses to Renewal Messages

NDPIX returns a response (DRR) for every entry either in the form of "Renewal Accepted" with match notification for accepted records or error messages on rejected input entries. This renews the record for 180 days.

Notifications on Record Purges

NDPIX holds entries in its database for 180 days after which they are purged. These messages use the DRR message key.

To Request NDPIX Reports

NDPIX offers supplemental information to its participants. Participants may request copies of all records for which he/she is the originator.

  • Those requested via contact with DEA's Intelligence Division and satisfied via U.S. mails (off-line requests). To receive a copy of all the records originating from an ORI, the requestor enters an ORI to signify to NDIPIX that the request is ORI based. The requestor has the option to enter Case Number in order to minimize record output.
    National Drug Pointer Index System Legacy Examples

    Example 1: A query to enter data into the NDPIX System.

    DEX.AZNLETS20.VADEADX00.TXT
    UID/XXX11111.PWD/XXXXXXXX.OCA/201001AA111111111.ORG/AZNLETS20.
    POC/NLETS_ANALYST.PTL/NLETS.PPN/8005284020.NAM/SMITH, JOHN.
    DOB/19500101.SEX/M.RTE/00:111111

    Example 2: A response to enter data into the NDPIX Record System.

    DEA.VADEADX00
    05:00 01/01/2011 41238
    05:00 01/01/2011 41231 AZNLETS20
    TXT
    RTE/*1111111111.NDP/111111.NAM/SMITH, JOHN.
    DLR/20120101.OCA/00-111.
    POC/NLETS_ANALYST.
    PTL/NLETS.
    PPN/8005284020.MSG/20-ENTRY ACCEPTED-NO MATCHES.

    Example 3: A query to modify a record in the NDPIX System.

    DUX.AZNLETS20.VADEADX00.TXT
    NDP/111111.UID/AAA11111.PWD/XXXXXXXX.OCA/00-111.
    POC/NLETS_ANALYST.PTL/NLETS.PPN/8005284020.NAM/SMITH, JOHN.SEX/M.SOC/123456789.RAC/W.
    DOB/19500101.ADR/1234 ANY ST.CIT/PHOENIX.STE/FL.ZIP/85000.
    SSN/123456789.TOC/M

    Example 4: A response to modify a record in the NDPIX System.

    DUA.VADEADX00
    06:00 01/01/2011 51238
    06:00 01/01/2011 61232 AZNLETS20
    TXT
    RTE/*1111111111.NDP/111111.NAM/SMITH, JOHN.
    DLR/20120101.OCA/00-111.POC/NLETS_ANALYST.
    PTL/NLETS.
    PPN/8005284020.MSG/30-UPDATE ACCEPTED-NO MATCHES.

    Example 5: A response to request a NDPIX Record.

    DTR.VADEADX00
    22:00 01/01/2011 31238
    22:00 01/01/2011 41238 AZNLETS20
    TXT
    NDP/111111.NAM/SMITH, JOHN.DLR/20110101.OCA/CSII-11111111.
    MSG/60-RECORD TO BE PURGED IN 15 DAYS NDP-111111.
    MSG/************************************************.
    MSG/* "D O N O T D I S C A R D" *.
    MSG/************************************************.
    MSG/ "IMPORTANT NOTIFICATION - ACTION REQUIRED" *.
    MSG/* POC: WATCH CENTER STAFF, *.
    MSG/* THIS RECORD WILL BE DELETED FROM NDPIX UNLESS *.
    MSG/* TIMELY RENEWAL OR UPDATE IS PERFORMED *.
    MSG/* DATE OF THIS NOTIFICATION: January 01, 2011 *.
    MSG/*************************************************

    Top

    Downloads

    Download DEX Schema

    Download DEX Stylesheet

    Download DEA Schema

    Download DEA Stylesheet

    Download DUX Schema

    Download DUX Stylesheet

    Download DUA Schema

    Download DUA Stylesheet

    Download DRX Schema

    Download DRX Stylesheet

    Download DRR Schema

    Download DRR Stylesheet

    Download DTX Schema -- Deprecated

    Download DTX Stylesheet -- Deprecated

    Download DTR Schema -- Deprecated

    Download DTR Stylesheet -- Deprecated

    Top