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

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 <![CDATA[]]> 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>