Section 32: Communicating with Canada

From Nlets Wiki
Jump to: navigation, search

Contents

Communicating with Canada

(WQ/WR, VQ/VR, UQ/UR, XQ/XR, CAQ/CAR, CGQ/CGR, CSQ/CSR, CBQ/CBR, IQ/IR, FQ/FR & AQ/AR)

Nlets supports a computer-to-computer interface to Canada for the purpose of exchanging criminal justice and criminal justice related information. Through this interface, a variety of information is available.

It is important to understand that Canadian information is provided from several sources. The Canadian Police Information Center (CPIC), a system somewhat similar to FBI/NCIC, is providing hot file and vehicle registration and driver’s license status information for the provinces and territories. Records are maintained by the individual Provinces and Territories to be shared through CPIC. However, driver’s license information comes directly from CPIC when it pertains to criminal charges and RMV would provide ‘status’.

As a part of this interface, users within Canada also will be obtaining information from users in the United States. Since requests from Canada will conform to formats currently in use, states must be able to accept and send to Canadian ORIs.

Policy for Use of Information from Canada

The CPIC has both confidentiality and dissemination policies regarding the use of the information they provide. Within both the CPIC Policy Manual and Memorandum of Cooperation between the Royal Canadian Mounted Police (RCMP) and the FBI it states:

Information is entrusted to the CPIC system for the purpose of communicating and sharing with the law enforcement and criminal justice community. Understanding that personal information is to be provided, received and used only in accordance with domestic and international law applicable to the United States and Canada for criminal justice purposes to facilitate police and public safety by preservation of the peace and protection of the public.

There is a collective responsibility to ensure this information is safeguarded from improper and unauthorized access, use, disclosure and dissemination. All information contributed to or retrieved from the CPIC system and NCIC/III systems is supplied in confidence and should be protected against disclosure to unauthorized agencies or individuals.

Authorized and unauthorized disclosure of the CPIC system’s information, intentional or otherwise, may take many forms including, but not limited to:

  • verbal communication;
  • viewing files or records on computer screens and printouts;
  • reproduced/copied material and information taken from computerized records;
  • overheard radio transmissions;
  • improperly stored or disposed material.

Disclosure refers to the intentional or unintentional act of making known any data or information from the CPIC system including, but not limited to any investigation, individual or situation, and includes the act of dissemination.

Dissemination refers to the intentional or unintentional disclosure of CPIC system information to one or many people. This includes, but not limited to, the disclosure of CPIC system information by one agency to other agencies or organizations.

Canadian privacy laws and CPIC policy require that users of CPIC data establish the accuracy and validity of the CPIC record prior to its use. Any record placed on the CPIC system is the subject of a police file maintained by the originator of the record, as long as the record is on CPIC. A Canadian agency will be able to confirm its CPIC records promptly, 24 hours a day, 7 days a week. Therefore any and all information obtained from CPIC by U.S. law enforcement which is intended for use or to be acted upon, should be confirmed first by contacting the contributing Canadian agency to confirm accuracy and relevancy.

Types of Information Available

The general types of information available fall under the following categories. See the specific sections that follow for further details.

  • Persons
  • Vehicles
  • Drivers’ Licenses
  • Vehicle Registration
  • Articles
  • Guns
  • Securities
  • Boats
  • Criminal History
  • Administrative
  • ORI Tables
  • HELP

CPIC Access Permissions by ORI Ending

CPIC Transaction Type.png

Persons File (WQ/WR)

Persons File - General

This information is provided by the CPIC file and includes a variety of records, some not normally available from their United States counterpart, FBI/NCIC. Associated records such as vehicles, articles, guns, securities, or boats could be appended to the person record.


WQ.jpg


Note the following important requirements for Person File transactions with Canada:

Take no official action on any response from the Canadian PERSON FILE without
obtaining specific instructions from Washington D.C., INTERPOL. This information is
provided for officer safety and is to be used only in conjunction with other information
the inquiring officer may have at his or her disposal at the time of inquiry.

States must not programmatically generate inquiries to the Canadian PERSON FILE
based on routine inquiries to their state wanted persons file, NCIC's wanted person file,
or inquiries on driver's license by name and date of birth.

Types of Persons Information Available

Below are the different types of information that are available to United States users from the CPIC Persons File:

  • Wanted
  • Accused
  • Prohibited
  • Parolee
  • Court Action
  • Refused
  • Missing
  • Special Interest to Police

Vehicle File (VQ/VR)

Vehicle File - General

This information is provided by the Canadian host system - vehicle file. It will include a variety of records, some not normally available from their United States counterpart, FBI/NCIC.

Note the following important requirements for Vehicle File transactions with Canada:


VQ.jpg


The vehicle has to be confirmed that it is the current and correct vehicle reported to be in
question and the status of such vehicle, as reported by the CPIC system, can be detained
and/or impounded pending specific instructions from the Canadian agency that entered the
vehicle into the CPIC system.

States must not programmatically generate inquiries to the Canadian vehicle file based on
routine inquiries to their state stolen vehicle file or NCIC's stolen vehicle file.

Types of Vehicle Information Available

Following are the different types of information that are available to United States users from the CPIC file. They are as follows:

  • Stolen
  • Observation
  • Crime
  • Abandoned
  • Pointer

Driver License Files (UQ/UR)

Driver License Files - General

Requests to Canada for driver license information must include NAM, DOB, SEX, RSN and PPS.


UQ.jpg


  • The OLN field is optional on inquiries to Alberta, British Columbia, Quebec and Ontario. If the OLN is not included in the inquiries to these provinces, the search of the driver license file will be by name and DOB.
  • If the OLN is included, the search of the driver license file for those provinces will be by OLN.
  • For all other provinces and territories the OLN, as well as the other five fields are required and the search of the driver license file will be by OLN.


Persons File - Wanted (WANT)

This refers to a person who is arrestable and/or for whom a warrant has been issued. Persons wanted by Provincial, Canada-wide and extraditable warrants are recorded on this file.

Persons File - Charged (CHGD)

This refers to a person against whom legal proceedings have commenced in relation to a criminal code offense or an offense under a Federal statute, who is waiting final disposition, including any appeal, and for whom a warrant to arrest is not in force for that offense.

Persons File - Prohibited (PROHIB)

This refers to a person against whom an Order of Prohibition is in effect with regard to liquor, firearms, vehicle driving (and boat operation), hunting or any other court or statute-imposed prohibition.

Note: Individuals with revoked/suspended licenses will be returned as this type of record
by CPIC.
British Columbia however keeps their own status information and therefore on a WQ no
status information will be provided for British Columbia licenses.

Persons File - Parole (PAROL)

This refers to a person who has been convicted of a criminal offense and has been released on:

  • Parole
  • Day Parole
  • Life Parole
  • Mandatory Supervision, or
  • Temporary absence over 24 hours from a federal penitentiary
Persons File - Probation (PROB)

This refers to a person who has been convicted or found guilty of an offense and:

  • Has been given a suspended sentence, or conditional discharge under section 736 (1) CC, or
  • Has been released on probation, or
  • Has been placed on peace bond, recognizance or restraining order, or
  • Is a young offender who is in "open custody".
Persons File - Refused (REF)

This category has been incorporated into the CPIC file to meet the requirements of the Firearms Legislation of the Criminal Code. It is used to record data on a person who:

  • Has been refused the issuance of a Firearm Acquisition Certificate (FAC), or
  • Has been refused the issuance of a Firearm Registration Certificate (FRC), or
  • Had an FRC revoked.
Persons File - Observation (OBS)

In the event a person is reported as being under "observation", take no action based on this information and do not divulge the existence of this information to any non-criminal justice personnel.

This category is used to record data on a person who is:

  • Suspected of committing criminal offenses and sufficient information is not available to prosecute, or
  • Known to be dangerous to himself/herself or to others, or
  • Involved in a serious criminal investigation, and confidential information as to his or her whereabouts is required.

Only observation records containing information about an individual that may pose a danger to an officer will be returned to the inquirer. Other types of "observed" records that are kept merely for surveillance purposes will not be provided to the inquirer.

There may be instances where a "silent hit" occurs. This means that the agency that entered the record will be notified that you inquired on his record but you will receive a "no hit" message. In some instances the agency may contact you in regard to this inquiry.

Persons File - Missing (MISS)

This refers to a person:

  • Reported missing, or
  • Who has been admitted/committed to a mental institution or hospital psychiatric ward and has left without permission or formal discharge (designated as an elopee), or
  • For whom a police agency has undertaken to assist in locating on compassionate grounds.

Persons File - Inquiry Field Requirements (WQ)

The standard Nlets message header (XML or Native format) and sender's ORI are required along with the fields listed below.

The destination code must be "CN".

The Persons File inquiry transaction (WQ) must include the following:

  • Name
  • Date of Birth
  • Sex
  • Reason Code
  • Person/Property Code

The field requirements for an inquiry to Canada are as follows.

XML Entry: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<j:PersonName>
  <j:PersonFullName>
  <j:PersonGivenName>
  <j:PersonMiddleName>
  <j:PersonSurName>
</j:PersonName>
NAM/ Max.
30
Alphabetic
characters

Full name in format;
last name, first name
(space) middle name
or initial (e.g., Tubbs,
Kathleen Dorothy.

<j:PersonBirthDate>
DOB/ 8 Express as
ccyy-mm-dd.
Date of Birth
<j:PersonSexCode>
SEX/ 1 M or F M = male, F = female
Optional
<n:ReasonCode>
RSN/ 1 Single letter: N,
F, V, T, S or H.

Identify reason code:
N - Narcotics
F - Fraud (includes
counterfeit
documents)
V - Violent crimes
(incl. robbery,
murder, rape,
bombing, etc.)
T - Traffic violations
S - Theft
H - Humanitarian,

<n:SightedIndicator>
PPS/ 1

Must be Y or N
for text. True or
False for XML.

Identify "in-sight"
code.

Persons File - Responses (WR)

The inquirer will receive either a hit or a no record from the CPIC Person File as a result of your inquiry.

In the past Interpol Ottawa handled the hit confirmation process. However this has changed. In the future all hit confirmation on person (or any other hot file hits from Canada) must be handled as any other hits. That is, the inquiring agency will contact the entering agency just as they do with NCIC.

When sending a YQ to Canada insert "NONE" in the NIC number field. (e.g., NIC/NONE.)

Persons File - No Record Response (WR)

This occurs when no matching record was found in the Canadian file.

Persons File - Possible Hit (WR)

If a possible hit has been made on the Canadian Person File, the inquiring agency must confirm the hit with the entering agency.

There may be some fields in Canadian messages that are unfamiliar to Nlets users.

Below is a brief explanation of some of these fields.

Entry Explanation
CONFIRM WITH ORIGINATING AGENCY This is a standard portion of the Canadian record.
BEST: 3,1 This field is used by CPIC to return the three
highest scoring records.
* CAUTION *

This is a cautionary warning and will be followed
by one of the four codes below. It will appear when
the record subject is considered dangerous to
himself/herself or to other persons. Unlike the
persons record, this code will not be expanded.

  • VIOLENCE - an automatic caution for charges
    involving violence, robbery, or offensive
    weapons.
  • ESCAPE CUSTODY - when any attempted or
    actual escape, regardless of whether a charge
    is laid, is reported.
  • MENTAL INSTABILITY - a caution generated
    when there is a notation on the FPS file
    indicating mental instability.
  • ATTEMPTED SUICIDE - indicating that the
    subject has suicidal tendencies.
CC Stands for "criminal code".
CONTROL NUMBER Used to record the police agency's control or
warrant number for the subject.
DLT1234-50673-90109 Driver license number of the subject.
POI ONT

"POI" stands for "province of issue" and the
"ONT" is the province where the license was
issued.

Vehicle File (VQ/VR)

Vehicle File - General

This information is provided by the Canadian host system - vehicle file. It will include a variety of records, some not normally available from their United States counterpart, FBI/NCIC.

Note the following important requirements for Vehicle File transactions with Canada:

Once it has been confirmed that the vehicle is the correct vehicle reported to be in question
and the status of such vehicle, as reported by the CPIC system, is current and correct, it
can be detained and/or impounded pending specific instructions from Washington INTERPOL
and/or the Canadian agency that entered the vehicle into the CPIC system. The locating
agency should immediately contact Washington INTERPOL for further instructions regarding
the vehicle.

States must not programmatically generate inquiries to the Canadian vehicle file based on
routine inquiries to their state stolen vehicle file or NCIC's stolen vehicle file.

Types of Vehicle Information Available

Following are the different types of information that are available to United States users from the CPIC file. They are as follows:

  • Stolen
  • Observation
  • Crime
  • Abandoned
  • Pointer
Vehicle File - Stolen (V or VEHICLE)

This refers to a vehicle that has been stolen, or taken from its rightful owner by the commission of a crime, (e.g., a vehicle purchased from a dealer under false pretenses).

Vehicle File - Observation (OBSERVED)

A vehicle under observation is one which is connected with criminal activities and may or may not be related to a specific individual.

Note the following important requirements for Vehicle File Observation transactions with Canada:

In the event a vehicle is reported as being under observation, absolutely no action is to be
taken by the inquiring officer. This information is provided solely for officer safety.

  • Subjects present or associated with the vehicle must not be notified that the vehicle is
    reported under observation by the CPIC system.
  • The inquiring agency should contact Washington INTERPOL for further instructions
    regarding the vehicle and/or occupants of such vehicle.

There may be instances where a "silent hit" occurs. This means that the agency that entered the record will be notified that you inquired on his record but you will receive a "no hit" message. In some instances the agency may contact you in regard to this inquiry.

Vehicle File - Crime (CRIME)

Crime vehicles are those vehicles known to be connected to the commission of a crime, (e.g., hit and run, murder, robbery, etc.). They are entered on the system by an agency wishing to examine the vehicle for possible evidence such as fingerprints, paint samples, bloodstains, disguises, empty shells, etc.

Vehicle File - Abandoned (ABAN or ABANDONED)

This refers to a vehicle that comes into its possession through abandonment, seizure (including seizure by bailiff), or impounding by other means.

Vehicle File - Pointer (PNTRV or POINTERVEH)

This refers to a vehicle record whose function is only to "point" to a prime record in the system. For example, an individual wanted for a specific offense is entered into the system as a wanted person record. He is known to drive a particular car. The vehicle's particulars are entered on the system as a PNTRV record to point to the prime wanted person record should an inquiry be received concerning the vehicle only.

Vehicle Query Field Requirements (VQ)

For VIN inquiries only "CN" is allowed for the destination code.

For LIC inquiries, a providence or territory destination code must be used.

  • All fields are required (with either LIC/or VIN/).
  • For inquiries on license number, a 2-character province code must be used as the destination.
  • For inquiries on a VIN, the 2-character destination "CN" must be used.

The query includes the standard Nlets message header (XML or Legacy format), sender and destination ORIs, followed by the text of the message with the following fields.

The field requirements for an inquiry to Canada are as follows.

XML Entry: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<j:VehicleRegistrationPlateID>
LIC/ 1-10 Alphanumeric License number.
OR
<j:VehicleID>
VIN/ Max.
17
Alphanumeric Vehicle ID #.
Optional
<n:ReasonCode>
RSN/ 1

Single Letter:
N, F, V, T,
S or H

Identify Reason
Code:
N - Narcotics
F - Fraud (includes
counterfeit
documents)
V - Violent crimes
(including robbery,
murder, rape,
bombing, etc.)
T - Traffic violations
S - Theft
H - Humanitarian

<n:SightedIndicator>
PPS/ 1

Must be Y or N
for text. True or
False for XML.

Identify "in-sight"
code.
Note: Control field is used. This is permissible in all messages to Canada.

Vehicle Responses (VR)

The inquirer will receive a response indicating either a hit or a no record from the CPIC Vehicle File. All hit confirmations on person (or any other hot file hits from Canada) must be handled as any other hits. That is, the inquiring agency will contact the entering agency just as they do with NCIC.

When sending a YQ to Canada insert "NONE" in the NIC number field. (e.g., NIC/NONE.)

There may be some fields that are unfamiliar to the Nlets user. Below is a brief explanation of some of these fields from the example above.

Entry Explanation
CONFIRM WITH ORIGINATING AGENCY This is a standard portion of the Canadian
record.
CONTROL NUMBER This is used to record the police agency's
control or warrant number for the subject
DLT1234-50673-90109 This is the driver license number of the
subject.
POI ONT

The "POI" stands for "province of issue" and
the "ONT" is the province where the license
was issued.

Driver License Files (UQ/UR)

Driver License Files - General

Requests to Canada for driver license information must include NAM, DOB, SEX, RSN and PPS.

  • The OLN field is optional on inquiries to Alberta, British Columbia, Quebec and Ontario. If the OLN is not included in the inquiries to these provinces, the search of the driver license file will be by name and DOB.
  • If the OLN is included, the search of the driver license file for these four provinces will be by OLN.
  • For all other provinces and territories the OLN, as well as the other five fields are required and the search of the driver license file will be by OLN.

This inquiry will also result in a check of the Person file located on the CPIC system. The search of the Person file will be by NAM/DOB.

As a result of a single "UQ" inquiry you will receive both "URs" and "WRs". These are responses from the provinces/ territories (UR) and CPIC Person file (WR).


Driver License Files - Person File Access

The inquiry generated from a "UQ" query to the CPIC Person file will be by NAM/DOB. It will be as though you sent a "WQ" to Canada.

Driver License Files - Responses (UR/WR)

There are two types of responses that will result from a "UQ" inquiry:

  • Person file response (WR) and
  • Province/ territory response (UR).
Driver License Files - Person File (WR)

Since a UQ generates an inquiry of the CPIC Person file, the user will be receiving responses from the Person file.

The response will include suspended or prohibited driver status information for all province/territories except British Columbia who will provide the information from their own file.

For those provinces that provide their own registration information, a message following a short line of asterisks will indicate that the query is being processed.

Note the following important requirements for Driver License File transactions with
Canada:

  • Take no official action on any response from the Canadian PERSON FILE without
    obtaining specific instructions from Washington D.C., INTERPOL. This information is
    provided for officer safety and is to be used only in conjunction with other information the
    inquiring officer may have at his or her disposal at the time of inquiry.
  • In the event a person is reported as being under "observation", take no action based on
    this information and do not divulge the existence of this information to any non-criminal
    justice personnel.
Driver License Files - Province Territory (UR)

Only four provinces in Canada have automated driver license files. These four provinces also provide a search of either name and DOB, or OLN depending on whether the inquirer includes the OLN in their inquiry. They are:

  • Quebec
  • Ontario
  • Alberta
  • British Columbia

When sending a Driver License Query (UQ) to an automated province, you will receive:

  • Person file check (includes any notification of driver license prohibition)
  • Check of the Province's driver license file.

When sending a Driver License Query (UQ) to a non-automated province or a territory, you will receive:

  • Person file check (includes notification of driver license prohibition)
  • Driver License Response (UR) message indicating that the province is non-automated
    and, if information OTHER THAN STATUS is needed, send an "AM" message directly to
    the province/territory for a manual check. The message will also contain the address of
    the province or territory as well as a copy of the inquiry that was sent.

Below is a list of the provinces/territories and the ORIs to which the manual requests should be forwarded:

Province/Territory ORI Hours of Service
Alberta AB1010200 8am - 5pm (EST) M-F
Alberta AB1012000 After hours/weekends
British Columbia BC1028700 24 hrs - 7 days per wk
Manitoba MB1007000 24 hrs - 7 days per wk
New Brunswick NK1004000 24 hrs - 7 days per wk
Newfoundland NF1004900 24 hrs - 7 days per wk
Northwest Territory NT1003500 24 hrs - 7 days per wk
Nova Scotia NS1005300 24 hrs - 7 days per wk
Ontario ON4540000 24 hrs - 7 days per wk
Prince Edward Island PE1000800 24 hrs - 7 days per wk
Quebec PQ4004700 24 hrs - 7 days per wk
Saskatchewan SN1011700 24 hrs - 7 days per wk
Yukon Territory YT1001500 24 hrs - 7 days per wk

Receiving driver license information from Canada and the various provinces and territories is no different than receiving the same type information from states of the United States in that the response formats are not standardized or uniform.

Different terminology is used, information is presented in different order, date of birth is recorded differently, and status codes and license type varies among the various provinces and territories.

Users may inquire into the Canadian help files in order to gain insight and interpretation for codes, etc. as Nlets users do for various state information.

Vehicle Registration Files (XQ/XR)

Vehicle Registration Files - General

This inquiry will result in a check of the province/territory registration file AND CPIC's Vehicle file.


XQ.jpg


The user may search on either license number or VIN.

Note that LIY and LIT are not used for Canadian vehicle registration inquiries.

A single vehicle registration query (XQ) may result in both vehicle registration responses from the province/territory files (XR) and CPIC Vehicle file responses (VR).

On all inquiries to Canada the user must include the reason code (RSN/) indicating the reason for the inquiry and the person/property in-sight code (PPS/) indicating whether the person or property is in-sight of the officer actually making or requesting the information.

Vehicle File Access

An inquiry generated from a vehicle registration query (XQ) will interrogate the CPIC vehicle file. It will be as though you sent a vehicle file query (VQ) to Canada.

Vehicle Registration Files - Inquiry Field Requirements (XQ)

Nlets standard header, sender ORI, and 2 character province/territory code followed by the elements below.

The vehicle registration query (XQ) has the following requirements.

XML Entry: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<j:VehicleRegistrationPlateID>
LIC/ 1-10 Alpha/numeric Identify license
plate number.
OR
<j:VehicleID>
VIN/ Max.
17
Alpha/numeric Vehicle ID #.
Optional
<n:ReasonCode>
RSN/ 1

Single letter
code: N, F, V,
T, S or H.

Identify reason
code.
N - Narcotics
F - Fraud (includes
counterfeit
documents)
V - Violent crimes
(incl. robbery,
murder, rape,
bombing, etc.)
T - Traffic violations
S - Theft
H - Humanitarian

<n:SightedIndicator>
PPS/ 1

Must be Y or N
for text. True or
False for XML.

Identify "in-sight"
code.

Vehicle Registration Files - Responses (XR/VR)

There are two types of responses that will result from a "XQ" inquiry:

  • Vehicle file response (VR)
  • Province/territory response (XR).
Vehicle File (VR)

Since a VQ generates an inquiry of the CPIC Vehicle file, the user will be receiving responses from the Vehicle file.

Note the following important requirements below for Vehicle File transactions:
  • Once it has been confirmed that the vehicle is the correct vehicle reported to be in question
    and the status of such vehicle as reported by the CPIC system is current and correct, the
    vehicle can be detained and/or impounded pending specific instructions from Washington
    INTERPOL and/or the Canadian agency that entered the vehicle into the CPIC system.
  • The locating agency should immediately contact Washington INTERPOL for further
    instructions regarding the vehicle.
  • In the event a vehicle is reported as being under observation, absolutely the inquiring
    officer should take no action. This information is provided solely for officer safety.
  • Subjects present or associated with the vehicle must not be notified that the vehicle is
    reported under observation by the CPIC system.
  • The inquiring agency should contact Washington INTERPOL for further instructions
    regarding the vehicle and/or occupants of such vehicle.
Vehicle Registration Files - Province/Territory (XR)

Only five provinces in Canada house their automated vehicle registration files. They are:

  • Quebec
  • Ontario
  • Alberta
  • British Columbia
  • Saskatchewan

All other provincial and territorial vehicle registration files are automated by CPIC thus inquiries to these provinces or territories will result in automated responses from CPIC rather than the provinces or territories.

When sending an "XQ" to a province or territory you will receive:

  • Vehicle file check on the CPIC vehicle file.
  • Vehicle registration check, either from CPIC or, for those five provinces named above,
    directly from their file.

For those provinces that provide their own registration information, a message following a short line of asterisks will indicate that the query is being processed.

For those provinces that have their registration information on CPIC, the second part of the response will contain the registration information and will be separated from the wanted vehicle information by a short line of asterisks.

Note: There may be instances when the user sent an "XQ" and received only a "VR". This is
because CPIC held the file and returned a single response with both the hot file response as
well as the registration information.

The Canadian interface system will wait approximately 30 minutes for a response from the external R.O. system.

If no responses are forthcoming the system will return a canned message to the querying agency which states:

* ABOVE PROVINCIAL RO/DL SYSTEM RESPONSE DELAYED AT THIS TIME, IF NO
RESPONSE, PLEASE RETRY IN 30 MINUTES *

Receiving vehicle registration information from Canada and the various provinces and territories is no different than receiving the same type information from states of the United States in that the response formats are not standardized or uniform.

Different terminology is used, information is presented in different order, and status codes and license type varies among the various provinces and territories.

Users may inquire into the Canadian help files in order to gain insight and interpretation for codes, etc. as Nlets users do today for various state information.

Article File (CAQ/CAR)

Article File - General

This information is provided by the CPIC file. There may also be occasions when the article record is associated with other records on the CPIC system. These will be returned as a part of the initial response.


CAQ.jpg


Once the user has confirmed that the article is the correct article reported to be in question and the status of such article, as reported by the CPIC system, is current and correct, it can be impounded pending specific instructions from the Canadian agency that entered the article into the CPIC system. The locating agency may contact Washington INTERPOL for assistance regarding disposition of the article.

States must not programmatically generate inquiries to the Canadian Article File based on routine inquiries to their state stolen article file or NCIC's stolen article file.

On all inquiries to Canada the user must include the reason code (RSN/) indicating the reason for the inquiry and the person/property in-sight code (PPS/) indicating whether the person or property is in-sight of the officer actually making or requesting the information.

Types of Article Information Available

Following are the different types of information that are available to United States users from the CPIC file. They are as follows:

  • Stolen
  • Lost or Missing
  • Recovered, Found, or Seized
  • Pawned or loaned

"Pawned" or "Loaned" status is defined as follows:

"items of property which have been accepted from individuals as collateral for loans, and, for the purposes of the CPIC Property File, articles obtained by direct purchases where there is reason to believe they may have been stolen."

Article File - Query Field Requirements (CAQ)

The 2 character destination code will always be "CN" for article queries (CAQ).

The serial number field size, 23 characters, is available for input, however only 16 alpha/numeric characters will be stored and searched.

The serial number must be a unique number and not simply a model, stock, style, or part number. Do not enter "UNKNOWN" in this field.

No imbedded spaces or blanks are allowed.

IMPORTANT: If you type in more than 16 characters, the system only searches on the last 16 characters, not the first 16. Therefore if an article has more than 16 characters, the last 16 characters must be used for inquiring to the CPIC system in order to receive a valid search.

The table below describes the required entries.

XML Entry: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<j:PropertySerialID>
SER/ Max.
23
Alpha/numeric Serial number
<j:PropertyTypeCode>
TYP/ 2 2 character
Type Code

Type Field:
AA - domestic appliances,
e.g. stoves, washers.
BI - non-motorized
bicycles, e.g. mountain
bikes, tandems, 10-speeds.
NOTE: Motorized bikes
are in the Vehicle File.
BU - Bulk entries that
have no unique identifiers,
but are the same commodity
and description, e.g.,
large shipment of
cigarettes
HH - Household property,
e.g. rugs, furniture.
JE - jewelry, e.g.
watches, rings.
MI - musical instruments,
e.g. violins, guitars.
MT - machinery and tools,
e.g. electrical motors,
lawn mowers.
NOTE: Lawn mowers
capable of carrying an
operator are in the
Vehicle File.
OM - office machines and
equipment, e.g. computers.
PA - personal accessories,
e.g. hearing aids,
luggage.
PE - photographic
equipment, e.g. camera,
enlargers.
PH - telephones, wireless
communication devices,
i.e. cellular phones,
Blackberry and PDA
RA - radio, TV, sound-
reproducing equipment,
e.g. VCR's.
SC - scientific, optical
and measuring devices,
e.g. binoculars.
SP - sporting goods,
hobby equipment, e.g.
skis, model aircraft,
scuba equipment.
OT - all other articles,
e.g. animals, vending
machines, precious
metals such as gold bars,
uniquely identifiable
gun barrels.

Optional
<n:ReasonCode>
RSN/ 1  

Identify reason code:
N - Narcotics
F - Fraud (includes
counterfeit documents)
V - Violent crimes
(including robbery,
murder, rape,
bombing, etc.)
T - Traffic violations
S - Theft
H - Humanitarian.

<n:SightedIndicator>
PPS/ 1

Must be Y or N
for text. True or
False for XML.

Identify "in-sight"
code.

Article Files - Response (CAR)

The user is responsible for confirming the article hit with the entering Canadian agency.

The "YQ" message and format is to be used for confirming all hits on the article file.

The destination address of the agency that entered the record may be found in the record itself but it is incomplete. It will state "Entered by:" followed by the name and 7 character address of the agency.

The user must add two zeroes to the end of the Canadian address to create the correct destination address.

The user will then proceed through the normal hit confirmation process as with any other stolen article.

Article File Response - No Record

This occurs when no matching record was found in the Canadian file.

Article File Response - Possible Hit

If a possible hit has been made on the Canadian Article File, the user determines that the article matches the article described in the record. He must confirm that the record is still valid with the entering agency prior to taking any action.

Gun File (CGQ/CGR)

Gun File - General

The CPIC file provides this information. There may also be occasions when the gun record is associated with other records on the CPIC system. These will be returned as a part of the initial response.


CGQ.jpg


The user may search on either license number or VIN.


Each inquiry will interrogate both the stolen gun file as well as the Canadian gun registration file.

The term "gun" means any barreled weapon that can discharge a bullet or other missile, or any imitation of such a weapon. The types of weapons include:

  • Revolver or pistol
  • Rifle
  • Shotgun
  • Flint/cap/matchlock muzzleloader
  • Automatic weapons, e.g. machine guns/pistols
  • Signal flare, rocket or gas guns
  • Air guns (rifle or pistol).

Once you have confirmed that the gun is the correct gun reported to be in question and the status of such gun, as reported by the CPIC system, is current and correct, it can be impounded pending specific instructions from the Canadian agency that entered the gun into the CPIC system. The locating agency may contact Washington INTERPOL for assistance regarding disposition of the gun.

States must not programmatically generate inquiries to the Canadian Gun File based on routine inquiries to their state stolen gun file or NCIC's stolen gun file.

On all inquiries to Canada the user must include the serial number (SER), type (TYP), reason code (RSN/) indicating the reason for the inquiry and the person/property in-sight code (PPS/) indicating whether the person or property is in-sight of the officer actually making or requesting the information.

Types of Gun Information Available

Following are the different types of information that are available to United States users from the CPIC file. They are:

  • Stolen
  • Lost or Missing
  • Recovered
  • Pawned or loaned

Pawned or loaned status is defined as follows: "guns which have been accepted from individuals as collateral for loans, and, for the purposes of the CPIC Gun File, guns obtained by direct purchases where there is reason to believe they may have been stolen."

Gun File - Query Field Requirements (CGQ)

Only "CN" is allowed as an address for "CGQ".

IMPORTANT: The serial number field will accept 23 characters but only 11 characters are stored on the CPIC file. When inquiring with more than 11 characters, the CPIC system will search on only the last 11 characters submitted, not the first 11.

The Gun File query (CGQ) will have the following format. All fields are required in addition to the standard Nlets header.

XML Entry: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<j:PropertySerialID>
SER/ Max.
23
Alpha/numeric Serial number.
<j:PropertyTypeCode>
TYP/ 2 2 character
Type Code

Type Field
SG - shotgun
RI - rifle
RW - restricted weapon
OT - other only

Optional
<n:ReasonCode>
RSN/ 1

Single Letter
Code: N, F, V,
T, S or H.

Identify reason code:
N - Narcotics
F - Fraud (includes
counterfeit documents)
V - Violent crimes
(including robbery,
murder, rape, bombing,
etc.)
T - Traffic violations
S - Theft
H - Humanitarian

<n:SightedIndicator>
PPS/ 1

Must be Y or N
for text. True or
False for XML.

Identify "in-sight" code.

Gun File - Response (CGR)

The user is responsible for confirming the gun hit with the entering Canadian agency. The "YQ" message and format is to be used for confirming all hits on the gun file.

The destination address of the agency that entered the record may be found in the record itself but it is incomplete. It will state "Entered by:" followed by the name and 7-character address of the agency.

The user must add two zeroes to the end of the Canadian address to create the correct destination address. Proceed through the normal hit confirmation process as with any other stolen gun.

Gun File Response - No Record (CGR)

This occurs when no matching record was found in the Canadian file.

Gun File Response - Possible Hit (CGR)

If a possible hit has been made on the Canadian Gun File and the user determines that the gun matches the gun described in the record, he must confirm that the record is still valid with the entering agency prior to taking any action.

Gun Registration File Questions

For questions on information received from the registration file, contact:

RCMP's Firearms Registration and Administration Section
P.O. Box 8885, Ottawa, Ontario K1G3M8.
ORI = ON1008100
Phone = (613) 998-6365
Fax = (613) 993-0218

Securities File (CSQ/CSR)

Securities File - General

This information is provided by the CPIC file. There may also be occasions when the securities record is associated with other records on the CPIC system. These will be returned as a part of the initial response.


CSQ.jpg


Once you have confirmed that the security is the correct security reported to be in question and the status of such security, as reported by the CPIC system, is current and correct, it can be impounded pending specific instructions from the Canadian agency that entered the security into the CPIC system. The locating agency may contact Washington INTERPOL for assistance regarding disposition of the security.

States must not programmatically generate inquiries to the Canadian Securities file based on routine inquiries to their state stolen securities file or NCIC's stolen securities file.

On all inquiries to Canada the user must include the reason code (RSN/) indicating the reason for the inquiry and the person/property in-sight code (PPS/) indicating whether the person or property is in-sight of the officer actually making or requesting the information.

Types of Securities Information Available

Following are the different types of securities information that are available to United States users from the CPIC file. They are:

  • Stolen
  • Lost or Missing
  • Pawned or loaned
  • Counterfeit
  • Fraudulent and recovered securities such as bonds, currency, credit cards, ID's traveler's checks and passports.

There are ten different types of securities; each assigned a two-character type code. They are:

Code Type of Security
BD Corporate bonds and debentures issued by corporations, including banks, trust
companies, charitable/religious groups, credit unions and co-operatives.
CC Canadian-issued currency.
CU Foreign-issued currency.
ID Stolen, lost, or fraudulent identification documents.
MO Money orders and traveler's checks.
PP Canadian and foreign passports.
SB Federal, provincial and municipal bonds and debentures.
ST Stocks.
VD Vehicle documents.
OT All other security documents.

Securities File Query Format

Queries may be made on four different combinations.

The type field must be included on all inquiries however only certain types are allowed depending on what you are searching the file on. For example, for a query on "issuer" only the type "ST" (TYP/ST) is permissible.

Below is a list of various data elements for the query along with the allowable types in parentheses.

  • serial # and type (all codes listed above)
  • corporation name and type (SB,BD,MO,OT)
  • issuer and type (ST)
  • owner name and type (BD,ID,MO,PP,SB,VD,OT)

The Serial number, the Issuer, the Corporation name, or the owner name along with the appropriate type are required as well as the RSN and PPS fields.

The destination code for all Securities File queries (CSQ) is "CN".

IMPORTANT: The serial number field will accept 23 characters but only 16 characters are stored on the CPIC file. When inquiring with more than 16 characters, the CPIC system will search on only the last 16 characters submitted, not the first 16.

The inquiry transaction will have the following format.

XML Entry: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<nc:ItemSerialIdentification>
  <nc:IdentificationID>
</nc:ItemSerialIdentification>
SER/ Max.
23
Alpha/numeric Serial number.
OR
<nc:SecurityIssuer>
ISS/ Max.
30
Alpha/numeric Name of issuer of
security
OR
<nc:ItemOwner>
COR/ Max.
30
Alpha

Name of
corporation
registered as
owner of the
security

OR
<nc:SecuritiesIssuer>
  <nc:EntityOrganization>
    <nc:PersonName>
    <nc:PersonFullName>
  </nc:PersonName>
</nc:SecuritiesIssuer>
NAM/ Max.
30
Alpha Name of owner of
security
<nc:ItemCategoryText>
TYP/ 2 2 character
Type Code

Security Type:
BD - Corporate bonds
and debentures issued
by corporations,
including banks, trust
companies,
charitable/religious
groups, credit unions
and co-operatives.
CC - Canadian-issued
currency.
CU - foreign-issued
currency.
ID - stolen, lost, or
fraudulent identification
documents.
MO - money orders
and traveler's checks.
PP - Canadian and
foreign passports.
SB - federal, provincial
and municipal bonds
and debentures
ST - stocks.
VD - vehicle
documents.
OT - all other security
documents.

Optional
<n2:ReasonCode>
RSN/ 1

Single Letter
Code: N, F, V,
T, S or H.

Identify reason code:
N - Narcotics
F - Fraud (includes
counterfeit documents)
V - Violent crimes
(including robbery,
murder, rape,
bombing, etc.)
T - Traffic violations
S - Theft
H - Humanitarian

<j:SightedIndicator>
PPS/ 1

Must be Y or N
for text. True or
False for XML.

Identify "in-sight" code.

Securities File - Responses (CSR)

The user is responsible for confirming the security hit with the entering Canadian agency.

The "YQ" message and format is to be used for confirming all hits on the securities file.

The destination address of the agency that entered the record may be found in the record itself but it is incomplete. It will state "Entered by:" followed by the name and 7 character address of the agency. You must add two zeroes to the end of the Canadian address to create the correct destination address. You will then proceed through the normal hit confirmation process as you would with any other stolen security.

Securities File Response - No Record

This occurs when no matching record was found in the Canadian file.

Securities File Response - Possible Hit

If a possible hit has been made on the Canadian Securities File and the user determines that the security matches the security described in the record he must confirm that the record is still valid with the entering agency prior to taking any action.

Boat File (CBQ/CBR)

Boat File - General

This information is provided by the CPIC stolen boat file. If you need registration information send an administrative request to CPIC (ORI = ON1000000) to affect a manual search. A boat is defined as a watercraft, which may be a small open vessel, a large vessel, or ship, propelled by oars, sails or engine(s).


CBQ.jpg


Users may also query the Boat File for information on stolen motors. The inquiry is made by serial number and requires a type code.

Once you have confirmed that the boat is the correct boat reported to be in question and the status of such boat, as reported by the CPIC system, is current and correct, it can be impounded pending specific instructions from the Canadian agency that entered the boat into the CPIC system. The locating agency may contact Washington INTERPOL for assistance regarding disposition of the boat.

Types of Boat Information Available

Following are the different types of information that are available to United States users from the CPIC file. They are:

  • Stolen
  • Abandoned
  • Missing

Boat File Query Inquiry Format (CBQ)

The 2 character destination code must be "CN" for all CBQ messages to Canada.

At least one of the five key fields must be included in the inquiry (i.e. LIC, BHN, REG, NAM, SER).

When an inquiry is made on any of the five items, Canada will search all five indices. For example, if the query is on LIC/1234 and there is a boat with a hull number of "1234" it will be returned. The Canadian system does this to compensate for human error in recognizing which field is which.

Canada uses the prefix "HIN" for hull number. In the United States "BHN" is used. They are synonymous.

The destination code must be "CN" for BHN queries.

The control field is permissible for all messages to Canada.

The inquiry transaction will have the following format.

XML Entry: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<j:VehicleRegistrationPlateID>
LIC/ 1-10 Alpha/numeric License plate number.
OR
<j:BoatHullID>
BHN/ Max.
12
Alpha/numeric

Identify hull ID
number. CPIC will use
HIN for this field in
their response.

OR
<j:RegistrationID>
REG/ 1-7 Alpha/numeric

Registration number of
large vessels that do
not have to be licensed
but must be registered.

OR
<j:PropertyOwnerAppliedID>
NAM/ Max.
13
Alphabetic Name of boat on hull
or stern.
OR
<j:PropertySerialID>
SER/ 1-18 Alpha/numeric Boat motor serial
number.
<j:PropertyTypeText>
TYP/ 5 Type Code

Type code:
INB
OUTB
INOUT
OTHER

Optional
<n:ReasonCode>
RSN/ 1

Single Letter
Code: N, F, V,
T, S or H.

Identify reason code:
N - Narcotics
F - Fraud (includes
counterfeit documents)
V - Violent crimes
(including robbery,
murder, rape,
bombing, etc.)
T - Traffic violations
S - Theft
H - Humanitarian.

<n:SightedIndicator>
PPS/ 1

Must be Y or N
for text. True or
False for XML.

Identify "in-sight" code.

Boat File - Responses (CBR)

The user is responsible for confirming the boat hit with the entering Canadian agency. The "YQ" message and format is to be used for confirming all hits on the boat file.

The destination address of the agency that entered the record may be found in the record itself but it is incomplete. It will state "Entered by:" followed by the name and 7 character address of the agency.

The user must add two zeroes to the end of the Canadian address to create the correct destination address. Proceed through the normal hit confirmation process as with any other stolen boats.

Boat File Response - No Record (CBR)

This occurs when no matching record was found in the Canadian file.

Boat File Response - Possible Hit (CBR)

If a possible hit has been made on the Canadian Boat File, the user determines whether the boat matches the boat described in the record. He must confirm that the record is still valid with the entering agency prior to taking any action.

Criminal History File (IQ/IR, FQ/FR, AQ/AR)

Criminal History File - General

The process for accessing Canadian criminal history records from the RCMP is the same as accessing criminal records in the United States, IQ/FQ/AQ. There are a few differences in the formats however.

  • Canada's unique number assigned to an individual based on fingerprints is the "FPS" number.
  • Canada has an optional field to access additional records when multiple hits on name inquiries are received.
  • The destination is always "CN".

Only agencies that are allowed access to the Triple I file are allowed access to the Canadian criminal history file.

The Identification Data Bank at the Canadian Police Information Centre(CPIC) contains two categories of criminal record data which may be queried by U. S. agencies.

Criminal name index containing an index of names and identity information on one or more individuals.

Full criminal record, containing conviction history, a summary of police-related information and a list of police agencies who have contributed information to the subject's criminal record.

If you have questions about the accuracy or timeliness of the information in a criminal record file, contact the RCMP Records Compilation Section at ORI = ON1007100.

Criminal Name Index Query (IQ)

The "IQ" is utilized when the agency does not have the FPS Canadian identification number. (The FPS number is Canada's version of the FBI number; a unique number assigned to each criminal record and backed up by fingerprints.)


IQ.jpg


  • Response to this type of inquiry will provide personal identification information of one or multiple individuals.
  • Normally, CPIC will return the three records that achieved the highest score.
  • The user will have the option of retrieving additional records using the "RAR" optional field on a subsequent request.
  • The user may request that more than three records be returned on the initial inquiry by including the "RAR" field in the initial inquiry with the number of records (up to 10) the user wishes to see.

Once the identification record(s) have been returned it is at the option of the inquirer to select the individual the user is interested in and submit an "FQ" in order to retrieve the full criminal record.

This works very much like NCIC's QH/QR or Nlets interstate IQ/FQ procedures.

The Criminal Name Index query (IQ) will have the following format.

XML Entry: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<n:PurposeCode>
PUR/ 1 Must be C, E,
F, D, J or S
Identify purpose code.

See Introduction Page

for more information.
<n:Attention>
ATN/ 30 Alphabetic Identify attention field.
Name of requestor.
<j:PersonFullName>
NAM/ Max.
30
Alphabetic

Full name; format is
last name, comma,
space after comma is
optional) first name,
space, middle initial or
name.

<j:PersonBirthDate>
DOB/ 8 Express as
ccyy-mm-dd
Date of Birth.
<j:PersonSexCode>
SEX/ 1 M or F M = male, F = female
<n:RequestAdditionalRecords>
RAR/
(optional)
13

Format;
XX,YYYYYYY,
ZZ where;
XX = # of
additional
records (up to
10); only field
required on
initial
YYYYYYY
=FPS# of last
record received
ZZ = score of
last record
received

Request additional
records using data
from the last record
received, or request
additional records in
the original inquiry

This query will check CPIC criminal history index and return candidates.

Note that this initial request will return the three records that achieve the highest score.

If the response indicates that there are additional identity records on file, the requestor may retrieve these by using the "RAR" field in a subsequent inquiry.

Note: If the inquirer wanted to retrieve more than 3 records on the initial inquiry he could
include the "RAR" field in the inquiry with only a number indicating the number of records
to be retrieved.

Criminal Name Index Response (IR)

When the user queries the CPIC criminal history file by name he will receive identity information only. There is no manual intervention on this response from CPIC.

If the inquiry was by FPS# a full criminal record may be returned.

Full criminal records will be reviewed by RCMP Identification Services prior to transmission to the inquirer.

Criminal Name Index Response - No Record (IR)

This occurs when no match is found on either the name or FPS number.

Positive Response Based on Name Query (IR)

This response is based on an inquiry by name and DOB. It provides identity information on the subject and an FPS number.

If the user wishes to access the full criminal record he must submit the FPS number using the "FQ" message format.

If there are more than 3 identification records that match your name inquiry only the three highest scoring records will be returned.

In order to retrieve additional records, up to 10, you must send the standard "IQ" message with the optional "RAR" field as the last data field.

It must be in the following format: RAR:XX,YYYYYYY,ZZ

Where:
XX = number of additional records required (up to 10), must be 2 characters
YYYYYYY = the FPS number of the last record received
ZZ = the score value of the last record received

Note: Commas must separate the above values

Explanation of Fields

There are some fields that may be unfamiliar to the recipient of Canadian identity records.

Below is a brief explanation of some of these fields.

Field Explanation
QUERY VALUE This is the maximum score that you could receive based on the
information in your inquiry.
RESPONDENT'S
SCORE
This is the score that the computer calculated when it compared
your I/P information to the record that was returned.
FPC The codes that Canada employs are the Orion Auto-Class
guidelines as published by Printrak, International.
FPS This is the unique number assigned to an individual based on
fingerprints (similar to the FBI number in the United States).
* CAUTION *

This is a cautionary warning and will be followed by one of the four
codes below. It will appear when the record subject is considered
dangerous to himself/herself or to other persons. Unlike the
persons record, this code will not be expanded.

V

Violence, an automatic caution for charges involving violence,
robbery, or offensive weapons. If "V" code is shown (for violent)
the response will also include the line * CR QUERY RECOMMENDED *.
This is an indication to the user to do a "FQ" query on the above
subject to obtain his/her full criminal record.

E Escape Custody, when any attempted or actual escape,
regardless of whether a charge is laid, is reported.
M Mental Instability, a caution generated when there is a notation on
the FPS file indicating mental instability.
S Attempted Suicide, indicating that the subject has suicidal
tendencies.
FILE OPEN

A criminal record is called a "file". Users should only receive files
that have this notation. The following qualifying statements may
appear after the status description of "FILE OPEN".

TRANSFERRED FROM
FPS XXXXX

This indicates that more than one record existed for the same
person and these have been brought together under the one FPS
number.

HISTORY UNDER
REVIEW

This indicates that an attempt by Ident. Services operators to enter
data into the subject history area was rejected by the system and
has not been corrected.

SUBJECT REPORTED
DEAD

This indicates that a notification was received that the subject has
died but the notification was not accompanied by the required set
of confirming fingerprints identifiable to the record subject.

PARDON APPLICANT

This indicates that the subject of the record has applied for a
judicial pardon. Such a record must not be used for any purpose
without the prior authority of the RCMP Identification Services,
Pardons and Human Rights Section (ORI = ON1015400).

Full Criminal Record Query (FQ)

The Full Record Query (FQ) is used to obtain a full criminal record when the FPS is known.


FQ.jpg


XML Entry: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<n:PurposeCode>
PUR/ 1 Must be C, E,
F, D, J or S
Identify purpose code.

See Introduction Page

for more information.
<n:Attention>
ATN/ 30 See NCIC
manual.
Identify attention field. Name
of requestor.
<n:FingerprintFPSID>
FPS/ Max.
7
Alphanumeric

FPS identification number,
based on fingerprints and
assigned by the RCMP; users
may use "SID" if it is more
convenient; Nlets and
Canada will accept either one.
The computer will treat them
the same.

This query will check CPIC criminal history file and return all criminal history that matches the FPS number.

Full Criminal Record Response (FR)

This record may be returned when the user submits an FPS number. All criminal record information in the CPIC file will be returned (with the exception of that information not authorized to be sent internationally).

Because RCMP Identification Services must review all records prior to sending them internationally, users may receive an interim message notifying them that they have realized a hit and it is being verified by the RCMP Identification Services Directorate.

The criminal record is laid out in three columns:
  • The first has the date in CCYY-MM-DD format and the place of the incident.
  • The second column has the charges.
  • The third the disposition.

There are some fields or abbreviations that may be unfamiliar to the Nlets users.

Below is an explanation of some of the more commonly used terms. Should you have difficulty deciphering any of the information you may contact Records Compilation Section at ORI = ON1007100.

Field Explanation
Q CR LANG:E The "Q CR" are control information unique to Canada. The "LANG:E"
indicates that the requested language of the record is in English.
LVL:2 This indicates the amount of information provided by CPIC and is
used by their system.
REM:

This is a remarks field used by the Canadian system to exchange
information. It will contain a control number, the ORI of the US
agency, the Nlets control field, and the attention (ATN) field.

CC An abbreviation for "Criminal code". It will generally be after several
numbers in the 2nd column of the record.
TORONTO PF In the second column, the agency along with the case (1234-88)
number is provided if available.

Non-retrievable Criminal History Record

The RCMP has some unique dissemination requirements for records transmitted internationally. Therefore it is possible to retrieve a valid identity record, request the full record using the FPS number and receive a message that states that the record matching the FPS number submitted contains only information that can not be disseminated outside of Canada.

Supplemental Criminal History Inquiry and Response (AQ/AR)

The AQ format is not accepted by Canada. All information is provided on the initial FQ query.

Administrative Messages

Administrative Messages - General

Nlets users may direct administrative messages to up to 5 destinations on the CPIC network.

Administrative messages must include:

  • Reason for the request
  • Name of the requester

General Administrative Messages

These messages will generally be for investigative reasons of a broad nature, to request driver license information from non-automated provinces or to send broadcast messages of international interest. These messages will be reviewed by the U.S. National Central Bureau of INTERPOL (Washington, D.C. INTERPOL).

Each message must contain the reason for the request and the requestor's name. If an address is unknown, ORION may be used to obtain the Canadian address code.

To broadcast an "AM" message, it must be addressed to "CN" for a country-wide broadcast.

Only narrative messages dealing with urgent operational police matters will be considered for nationwide broadcast in Canada.

Canada has NO facility for broadcasting messages to individual provinces therefore "AM" messages to 2-character province or territory should not be sent. These will be reviewed by INTERPOL in the U.S. prior to forwarding to Canada.

Access Non Automated Driver License Information

Driver license information may be accessed by name, date of birth, and sex from the 6 provinces and 2 territories that do not provide automated responses by name and DOB. This non-automated information must be requested using an "AM" message.

ORION

Canada has added records for their agencies to the NLETS ORION file. You may access it in the same manner as you would a U.S. agency using the two characters "CN" for all provinces and territories as the destination.

All Canadian ORIs are 7 characters but two zeros are added to the end to make them 9 character ORIs.

HELP Files

There have been several HELP files assigned to Canada to assist the users in accessing this interface. The user should recognize that the RCMP supports many of the files that are accessible through the interface thus there will only be a single HELP file for these.

There will however be a HELP file for each province and territory for driver license and vehicle registration information.

Each province/territory in Canada has the following HELP files:
     XXLICHELP = one for each province/territory
     XXOLNHELP =one for each province/territory
Where XX = province/territory code.

Single HELP records exist for the following information:

HELP File Explanation
CNGENHELP General help information on Canada
CNLICHELP General Vehicle Registration help information.
CNOLNHELP General Driver License help information.
CNPERHELP Wanted Persons help information
CNVEHHELP Stolen Vehicles help information.
CNSIRHELP Criminal History help information
CNGUNHELP Stolen Gun help information.
CNSECHELP Stolen Securities help information.
CNARTHELP Stolen Article help information.
CNBOTHELP Boat/Motor help information.

Top

GJXDM (DEPRECATED)

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

Top

NIEM

Communicating with Canada NIEM Specifications

This section describes NIEM format and provides examples for Canadian Person File queries and responses (WQ/WR), Canadian Vehicle File queries and responses (VQ/VR), Canadian Driver License File queries and responses (UQ/UR/WR), Canadian Vehicle Registration queries and responses (XQ/XR/VR), Canadian Article File queries and responses (CAQ/CAR), Canadian Gun File queries and responses (CGQ/CGR), Canadian Securities File queries and responses (CSQ/CSR), Canadian Boat File queries and responses (CBQ/CBR) & Canadian Criminal History queries and responses (IQ/IR/FQ/FR/AQ/AR).

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.

Canadian Person File query notes

The destination code for WQ messages must be "CN".

Canadian Vehicle File query notes

For inquiries on a license number, a 2 character province code must be used as the destination.

For inqiries on a VIN, the 2 character destination "CN" must be used.

Canadian Driver License File query notes

Requests to Canada for driver license information must include name, date of birth, sex, reason code and person/property code.

The OLN field is optional on inquiries to Alberta, British Columbia, Quebec and Ontario.

  • If the OLN is not included in the inquiries to these provinces, the search of the driver license file will be by name and DOB.
  • If the OLN is included, the search of the driver license file for these four provinces will be by OLN.

For all other provinces and territories the OLN, as well as the other five fields are required and the search of the driver license file will be by OLN. This inquiry will also result in a check of the Person file located on the CPIC system.

The search of the Person file will be by name/date of birth.

As a result of a single Driver License Query (UQ) the user will receive both Driver License Responses (URs) and Person File Responses (WRs). These are responses from the provinces/ territories (Driver License Response, UR) and CPIC Person file (Person File Response, WR).

When sending a Driver License Query (UQ) to an automated province, the user will receive:

  • Person file check (includes any notification of driver license prohibition)
  • Check of the Province's driver license file.

When sending a Driver License Query (UQ) to a non-automated province or a territory, the user will receive:

  • Person file check (includes notification of driver license prohibition)
  • Driver License Response (UR) message indicating that the province is non-automated and, if information OTHER THAN STATUS is needed, send an "AM" message directly to the province/territory for a manual check. The message will also contain the address of the province or territory as well as a copy of the inquiry that was sent.

Canadian Vehicle Registration query notes

As a result of a single Vehicle Registration Query (XQ), the user will receive both Vehicle Registration Responses from the province/territory files (XR) and Vehicle Responses from the CPIC Vehicle file (VRs).

Only five provinces in Canada house their automated vehicle registration files. They are as follows:

  • Quebec
  • Ontario
  • Alberta
  • British Columbia
  • Saskatchewan

All other provincial and territorial vehicle registration files are automated by CPIC thus inquiries to these provinces or territories will result in automated responses from CPIC rather than the provinces or territories.

When sending a Vehicle Registration Query (XQ) to a province or territory you will receive:

  • A vehicle file check on the CPIC vehicle file.
  • A vehicle registration check, either from CPIC or, for those four provinces named above, directly from their file.

For those provinces that provide their own registration information, a message following a short line of asterisks will indicate that the query is being processed.

Canadian Article File query notes

Queries must be sent to destination "CN".

The user is responsible for confirming the article hit with the entering Canadian agency.

The "YQ" message and format is to be used for confirming all hits on the article file.

The destination address of the agency that entered the record may be found in the record itself but it is incomplete. It will state "Entered by:" followed by the name and 7 character address of the agency.

The user must add two zeroes to the end of the Canadian address to create the correct destination address. The user will then proceed through the normal hit confirmation process as with any other stolen article.

Canadian Gun File query notes

The CPIC file provides the Gun File information. There may also be occasions when the gun record is associated with other records on the CPIC system. These will be returned as a part of the initial response. Each inquiry will interrogate both the stolen gun file as well as the Canadian gun registration file. Queries must be sent to destination "CN".

The user is responsible for confirming the gun hit with the entering Canadian agency.

The "YQ" message and format is to be used for confirming all hits on the gun file.

The destination address of the agency that entered the record may be found in the record itself but it is incomplete. It will state "Entered by:" followed by the name and 7 character address of the agency.

The user must add two zeroes to the end of the Canadian address to create the correct destination address.

The user will then proceed through the normal hit confirmation process as with any other stolen gun.

Canadian Securities File query notes

The CPIC file provides the Securities File information. Queries must be sent to destination "CN".

The user is responsible for confirming the security hit with the entering Canadian agency.

The "YQ" message and format is to be used for confirming all hits on the securities file.

The destination address of the agency that entered the record may be found in the record itself but it is incomplete. It will state "Entered by:" followed by the name and 7 character address of the agency.

The user must add two zeroes to the end of the Canadian address to create the correct destination address. The user will then proceed through the normal hit confirmation process as with any other stolen security.

Canadian Boat File query notes

This information is provided by the CPIC stolen boat file.

If the user needs registration information, send an administrative request to CPIC (ORI = ON1000000) to initiate a manual search.

A boat is defined as a watercraft, which may be a small open vessel, a large vessel, or ship, propelled by oars, sails or engine(s).

Users may also query the Boat File for information on stolen motors. The inquiry is made by serial number and requires a type code.

Canadian Criminal History query notes

The process for accessing Canadian criminal history records from the RCMP is the same as accessing criminal records in the United States, IQ/FQ/AQ. There are a few differences in the formats however.

  • First, the Canadian system use a unique number assigned to an individual based on fingerprints, the "FPS" number.
  • Second, the Canadian system has an optional field to access additional records when multiple hits on name inquiries are received.
  • Third, the destination is always "CN".

Only agencies that are allowed access to the Triple I file are allowed access to the Canadian criminal history file.

The "IQ" is utilized when the agency does not have the FPS Canadian identification number. (The FPS number is Canada's version of the FBI number; a unique number assigned to each criminal record and backed up by fingerprints.)

Response to this type of inquiry will provide personal identification information of one or multiple individuals. Normally, CPIC will return the three records that achieved the highest score.

  • The user will have the option of retrieving additional records using the "
    <n:RequestAdditionalRecords>
    
    " optional field on a subsequent request.
  • The user may request that more than three records be returned on the initial inquiry by including the
    <n:RequestAdditionalRecords>
    
    field in the initial inquiry with the number of records (up to 10) the user wishes to see.

Once the identification record(s) have been returned it is at the option of the inquirer to select the individual the user is interested in and submit an "FQ" in order to retrieve the full criminal record.

This works very much like NCIC's QH/QR or NLETS interstate IQ/FQ procedures.

Element Dictionary

Transaction types detailed below include: Query by Name, DOB and Sex (WQ), Query by License Plate (VQ), Query by VIN (VQ), Response to Query (WR & VR), Query by Name, DOB and Sex (UQ), Response from Province (UR & XR), Query by License Plate (XQ), Query by VIN (XQ), Query by Serial Number (CAQ), Query by Serial Number (CGQ), Query by Serial Number (CSQ), Query by Owner (CSQ), Query by Issuer (CSQ), Query by Boat Hull Number (CBQ), Query by Registration Number (CBQ), Query by Boat Name (CBQ), Identity Query by Name, DOB and Sex (IQ), Full Record Query by SID (FQ), Rapsheet Response in Free Text (IR,FR), Standardized Criminal History Rapsheet (FR) & Response from CPIC (WR, VR, CAR, CGR, CSR & CBR).

Query Formats

Canadian Person File Query:

Query by Name, DOB and Sex (WQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  nc:Person
  A human being.
This element encapsulates the information about the person being queried.

    nc:PersonBirthDate
    A date a person was born.

      nc:Date
      A full date.
      This element contains the DOB for the person being queried on. This data in this element must be
      in xsd:date format, that is: yyyy-mm-dd.

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

      nc:PersonGivenName
      A first name of a person.
      This optional element containing a person's first name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonMiddleName
      A middle name of a person.
      This optional element containing a person's middle name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonSurName
      A last name or family name of a person.
      This optional element containing a person's last name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonFullName
      A complete name of a person.
      This required element must contain the full name of the person in the format LAST,FIRST MIDDLE.
      The data from this element is the only name data that will be passed onto states receiving text.

    nc:PersonSexCode
    A gender or sex of a person.
    Value must be M, F or U.

  n2:ReasonCode
  This element identifies the reason for query:
  N - Narcotics
  F - Fraud (includes counterfeit documents)
  V - Violent crimes (incl. robbery, murder, rape, bombing, etc.)
  T - Traffic violations
  S - Theft
  H - Humanitarian

  j4:PersonSightedIndicator
  True if a person has been sighted; false otherwise.
  This element identifies whether or not the subject is in sight.

Canadian Vehicle File Query:

Query by License Plate (VQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  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 element will contain the license plate number to be queried.

  n2:ReasonCode (Optional)
  This element identifies the reason for query:
  N - Narcotics
  F - Fraud (includes counterfeit documents)
  V - Violent crimes (incl. robbery, murder, rape, bombing, etc.)
  T - Traffic violations
  S - Theft
  H - Humanitarian

  j4:PersonSightedIndicator (Optional)
  This element identifies whether or not the subject is in sight. Value must be True or False.

Query by VIN (VQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

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

    nc:VehicleIdentification
    A unique combination of alphanumeric characters that identifies a specific vehicle.

      nc:IdentificationID
      A value that identifies something.
      This element will contain the VIN to be queried.

  n2:ReasonCode
  This element identifies the reason for query:
  N - Narcotics
  F - Fraud (includes counterfeit documents)
  V - Violent crimes (incl. robbery, murder, rape, bombing, etc.)
  T - Traffic violations
  S - Theft
  H - Humanitarian

  j4:PersonSightedIndicator
  This element identifies whether or not the subject is in sight. Value must be True or False.

Canadian Driver License File Query:

Query by Name, DOB and Sex (UQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

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

    nc:DriverLicense
    Details about a license issued to a person granting driving privileges.

      nc:DriverLicenseIdentification
      Details about a driver license identifier or driver license permit identifier, including the number and
      state.

        nc:IdentificationID
        A value that identifies something.
        This element should contain the person's driver license number. Optional for Alberta, British
        Columbia, Quebec, and Ontario. Required for all other provinces.

    nc:PersonBirthDate
    A date a person was born.

      nc:Date
      A full date.
      This element contains the DOB for the person being queried on. This data in this element must be
      in xsd:date format, that is: yyyy-mm-dd.

    nc:PersonName
    A combination of names and/or titles by which a person is known.
    This element encloses subelements containing name data for query.

      nc:PersonGivenName
      A first name of a person.
      This optional element containing a person's first name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonMiddleName
      A middle name of a person.
      This optional element containing a person's middle name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonSurName
      A last name or family name of a person.
      This optional element containing a person's last name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonFullName
      A complete name of a person.
      This required element must contain the full name of the person in the format LAST,FIRST MIDDLE.
      The data from this element is the only name data that will be passed onto states receiving text.

    nc:PersonSexCode
    A gender or sex of a person.
    Value must be M, F or U.

  j4:PersonSightedIndicator (Optional)
  This element identifies whether or not the subject is in sight. Value must be True or False.

  n2:ReasonCode (Optional)
  This element identifies the reason for query:
  N - Narcotics
  F - Fraud (includes counterfeit documents)
  V - Violent crimes (incl. robbery, murder, rape, bombing, etc.)
  T - Traffic violations
  S - Theft
  H - Humanitarian

Canadian Vehicle Registration Query:

Query by License Plate (XQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  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 element will contain the license plate number to be queried.

  n2:ReasonCode (Optional)
  This element identifies the reason for query:
  N - Narcotics
  F - Fraud (includes counterfeit documents)
  V - Violent crimes (incl. robbery, murder, rape, bombing, etc.)
  T - Traffic violations
  S - Theft
  H - Humanitarian

  j4:PersonSightedIndicator (Optional)
  This element identifies whether or not the subject is in sight. Value must be True or False.

Query by VIN (XQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

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

    nc:VehicleIdentification
    A unique combination of alphanumeric characters that identifies a specific vehicle.

      nc:IdentificationID
      A value that identifies something.
      This element will contain the VIN to be queried.

  n2:ReasonCode (Optional)
  This element identifies the reason for query:
  N - Narcotics
  F - Fraud (includes counterfeit documents)
  V - Violent crimes (incl. robbery, murder, rape, bombing, etc.)
  T - Traffic violations
  S - Theft
  H - Humanitarian

  j4:PersonSightedIndicator (Optional)
  This element identifies whether or not the subject is in sight. Value must be True or False.

Canadian Article File Query:

Query by Serial Number (CAQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  nc:TangibleItem
  A physical object.
  This element will contain information about the article.

    nc:ItemCategoryText
    A kind of property item.
    Identify Property Type Field:
    AA - domestic appliances, e.g. stoves, washers.
    BI - non-motorized bicycles, e.g. mountain bikes, tandems, 10-speeds.
    NOTE: Motorized bikes are in the Vehicle File.
    HH - Household property, e.g. rugs, furniture.
    JE - jewelry, e.g. watches, rings.
    MI - musical instruments, e.g. violins, guitars.
    MT - machinery and tools, e.g. electrical motors, lawn mowers.
    NOTE: Lawn mowers capable of carrying an operator are in the Vehicle File.
    OM - office machines and equipment, e.g. computers.
    PA - personal accessories, e.g. hearing aids, luggage.
    PE - photographic equipment, e.g. camera, enlargers.
    RA - radio, TV, sound-reproducing equipment, e.g. VCR's.
    SC - scientific, optical and measuring devices, e.g. binoculars.
    SP - sporting goods, hobby equipment, e.g. skis, model aircraft, scuba equipment.
    OT - all other articles, e.g. animals, vending machines, precious metals such as gold bars, uniquely
    identifiable gun barrels.

    nc:ItemSerialIdentification
    An identification inscribed on or attached to a part, collection of parts, or complete unit by the
    manufacturer.

      nc:IdentificationID
      A value that identifies something.
      This element contains the serial number of the article. The serial number must be a unique number
      and not simply a model, stock, style, or part number. Do not enter "UNKNOWN" in this field.
      IMPORTANT: If you type in more than 16 characters, the system only searches on the last 16
      characters, not the first 16.

  n2:ReasonCode (Optional)
  This element identifies the reason for query.
  N - Narcotics
  F - Fraud (includes counterfeit documents)
  V - Violent crimes (incl. robbery, murder, rape, bombing, etc.)
  T - Traffic violations
  S - Theft
  H - Humanitarian

Canadian Gun File Query:

Query by Serial Number (CGQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  nc:Firearm
  A weapon that will, or is designed to, or may readily be converted to expel a projectile by air, carbon
  dioxide, or the action of an explosive.
  This element will contain information about the gun.

    nc:FirearmCategoryDescriptionText
    A description of a kind of firearm.
    Identify type of gun.
    SG - Shotgun
    RI - Rifle
    RW - Restricted Weapon
    OT - Other only.

    nc:ItemSerialIdentification
    An identification inscribed on or attached to a part, collection of parts, or complete unit by the
    manufacturer.

      nc:IdentificationID
      A value that identifies something.
      This element contains the serial number of the article. The serial number field will accept 23
      characters but only 11 characters are stored on the CPIC file. When inquiring with more than 11
      characters, the CPIC system will search on only the last 11 characters submitted, not the first 11.

  n2:ReasonCode (Optional)
  This element identifies the reason for query.
  N - Narcotics
  F - Fraud (includes counterfeit documents)
  V - Violent crimes (incl. robbery, murder, rape, bombing, etc.)
  T - Traffic violations
  S - Theft
  H - Humanitarian

  j4:PersonSightedIndicator (Optional)
  True if a person has been sighted; false otherwise.
  This element identifies whether or not the subject is in sight. Value must be Y or N.

Canadian Securities Query:

Query by Serial Number (CSQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:Securities
  A financial instrument showing ownership or credit.
  This element will contain information about the security.

    nc:ItemCategoryText
    A kind of property item.
    Identify type of security. Security Type:
    BD - Corporate bonds and debentures issued by corporations, including banks, trust companies,
    charitable/religious groups, credit unions and co-operatives.
    CC - Canadian-issued currency.
    CU - Foreign-issued currency.
    ID - stolen, lost, or fraudulent identification documents.
    MO - money orders and traveler's checks.
    PP - Canadian and foreign passports.
    SB - federal, provincial and municipal bonds and debentures
    ST - Stocks.
    VD - Vehicle documents.
    OT - all other security documents.

    nc:ItemSerialIdentification
    An identification inscribed on or attached to a part, collection of parts, or complete unit by the
    manufacturer.

      nc:IdentificationID
      A value that identifies something.
      This element contains the serial number of the security. IMPORTANT: The serial number field will
      accept 23 characters but only 16 characters are stored on the CPIC file. When inquiring with more
      than 16 characters, the CPIC system will search on only the last 16 characters submitted, not the
      first 16.

  n2:ReasonCode (Optional)
  This element identifies the reason for query.
  N - Narcotics
  F - Fraud (includes counterfeit documents)
  V - Violent crimes (incl. robbery, murder, rape, bombing, etc.)
  T - Traffic violations
  S - Theft
  H - Humanitarian

  j4:PersonSightedIndicator (Optional)
  True if a person has been sighted; false otherwise.
  This element identifies whether or not the subject is in sight. Value must be True or False.

Query by Owner (CSQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:Securities
  A financial instrument showing ownership or credit.

    nc:ItemCategoryText
    A kind of property item.
    Identify type of security. Security Type:
    BD - Corporate bonds and debentures issued by corporations, including banks, trust companies,
    charitable/religious groups, credit unions and co-operatives.
    CC - Canadian-issued currency.
    CU - Foreign-issued currency.
    ID - stolen, lost, or fraudulent identification documents.
    MO - money orders and traveler's checks.
    PP - Canadian and foreign passports.
    SB - federal, provincial and municipal bonds and debentures
    ST - stocks.
    VD - vehicle documents.
    OT - all other security documents.

    nc:ItemOwner
    An entity which owns a property item.
    Includes information about the owner of the security.

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

        nc:OrganizationName
        A name of an organization.
        Name of registered corporate owner of the security.

    nc:ItemSerialIdentification
    An identification inscribed on or attached to a part, collection of parts, or complete unit by the
    manufacturer.

      nc:IdentificationID
      A value that identifies something.

  n2:ReasonCode (Optional)
  This element identifies the reason for query.

  j4:PersonSightedIndicator (Optional)
  True if a person has been sighted; false otherwise.
  This element identifies whether or not the subject is in sight. Value must be True or False.

Query by Issuer (CSQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:Securities
  A financial instrument showing ownership or credit.

    nc:ItemCategoryText
    A kind of property item.
    Identify type of security. Security Type:
    BD - Corporate bonds and debentures issued by corporations, including banks, trust companies,
    charitable/religious groups, credit unions and co-operatives.
    CC - Canadian-issued currency.
    CU - foreign-issued currency.
    ID - stolen, lost, or fraudulent identification documents.
    MO - money orders and traveler's checks.
    PP - Canadian and foreign passports.
    SB - federal, provincial and municipal bonds and debentures
    ST - stocks.
    VD - vehicle documents.
    OT - all other security documents.

    nc:SecuritiesIssuer
    An entity which issued a security to a person.

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

        nc:OrganizationName
        A name of an organization.
        Name of registered corporate owner of the security.

  n2:ReasonCode (Optional)
  This element identifies the reason for query.
  N - Narcotics
  F - Fraud (includes counterfeit documents)
  V - Violent crimes (incl. robbery, murder, rape, bombing, etc.)
  T - Traffic violations
  S - Theft
  H - Humanitarian

  j4:PersonSightedIndicator (Optional)
  True if a person has been sighted; false otherwise.
  This element identifies whether or not the subject is in sight. Value must be True or False.

Canadian Boat File Query:

Query by Boat Hull Number (CBQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  nc:Vessel
  A mode of transportation capable of transport by water.
  This element will contain query data about the boat.

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

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

  n2:ReasonCode (Optional)
  This element identifies the reason for query.
  N - Narcotics
  F - Fraud (includes counterfeit documents)
  V - Violent crimes (incl. robbery, murder, rape, bombing, etc.)
  T - Traffic violations
  S - Theft
  H - Humanitarian

  j4:PersonSightedIndicator (Optional)
  True if a person has been sighted; false otherwise.
  This element identifies whether or not the subject is in sight. Value must be True or False.

Query by Registration Number (CBQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  nc:Vessel
  A mode of transportation capable of transport by water.
  This element will contain query data about the boat.

    nc:VesselRegistrationIdentification
    An identification assigned to a vessel by the coast guard or another vessel licensing organization.

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

  n2:ReasonCode (Optional)
  This element identifies the reason for query.
  N - Narcotics
  F - Fraud (includes counterfeit documents)
  V - Violent crimes (incl. robbery, murder, rape, bombing, etc.)
  T - Traffic violations
  S - Theft
  H - Humanitarian

  j4:PersonSightedIndicator (Optional)
  True if a person has been sighted; false otherwise.
  This element identifies whether or not the subject is in sight. Value must be True or False.

Query by Boat Name (CBQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  nc:Vessel
  A mode of transportation capable of transport by water.
  This element will contain query data about the boat.

    nc:ItemOwnerAppliedID
    An identifier applied to an item by the owner.
    This element should contain the boat name.

    nc:ItemSerialIdentification
    An identification inscribed on or attached to a part, collection of parts, or complete unit by the
    manufacturer.

      nc:IdentificationID
      A value that identifies something.

  n2:ReasonCode (Optional)
  This element identifies the reason for query.
  N - Narcotics
  F - Fraud (includes counterfeit documents)
  V - Violent crimes (incl. robbery, murder, rape, bombing, etc.)
  T - Traffic violations
  S - Theft
  H - Humanitarian

  j4:PersonSightedIndicator (Optional)
  True if a person has been sighted; false otherwise.

Query by Serial Number (CBQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  nc:Vessel
  A mode of transportation capable of transport by water.
  This element will contain query data about the boat.

    nc:ItemCategoryText
    A kind of property item.
    Optional element to identify type of boat. Values: INB, OUTB, INOUT, OT.

    nc:ItemOwnerAppliedID
    An identifier applied to an item by the owner.
    This element should contain the boat name.

    nc:ItemSerialIdentification
    An identification inscribed on or attached to a part, collection of parts, or complete unit by the
    manufacturer.

      nc:IdentificationID
      A value that identifies something.
      This element contains the serial number of the boat.

  n2:ReasonCode (Optional)
  This element identifies the reason for query.
  N - Narcotics
  F - Fraud (includes counterfeit documents)
  V - Violent crimes (incl. robbery, murder, rape, bombing, etc.)
  T - Traffic violations
  S - Theft
  H - Humanitarian

  j4:PersonSightedIndicator (Optional)
  True if a person has been sighted; false otherwise.

Canadian Criminal History Queries:

Identity Query by Name, DOB and Sex (IQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:PurposeCode
  This element identifies the reason for query.
  Valid values are: C, F, E, D, J or S

  n2:ResponseAttentionDescriptionText
  This element contains identification of the person or entity to whose attention the driver history response
  will be directed.
  This element contains identification of the person or entity to whose attention the driver history
  response will be directed.

  j4:Person
  Applied augmentation for type nc:PersonType

    nc:PersonBirthDate
    A date a person was born.

      nc:Date
      A full date.
      This element contains the DOB for the person being queried on. This data in this element must be
      in xsd:date format, that is: yyyy-mm-dd.

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

      nc:PersonGivenName
      A first name of a person.
      This optional element containing a person's first name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonMiddleName
      A middle name of a person.
      This optional element containing a person's middle name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonSurName
      A last name or family name of a person.
      This optional element containing a person's last name may be sent via XML if available but will
      only be forwarded onto states receiving XML.

      nc:PersonFullName
      A complete name of a person.
      This required element must contain the full name of the person in the format LAST,FIRST MIDDLE.
      The data from this element is the only name data that will be passed onto states receiving text.

    nc:PersonOtherIdentification
    Information about an identifier with a kind that is not explicitly defined in the standard that refers to a
    person within a certain domain.

      nc:IdentificationID
      A value that identifies something.
      Optional containing miscellaneous number.

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

    nc:PersonSexCode
    A gender or sex of a person.
    Value must be M, F or U.

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

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

Full Record Query by SID (FQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:PurposeCode
  This element identifies the reason for query.
  This element contains a code indicating the purpose for which the record is being requested. Valid
  values are: C, F, E, D, J, I, S or X.

  n2:ResponseAttentionDescriptionText
  This element contains identification of the person or entity to whose attention the response will be
  directed.

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

    n2:PersonFPSIdentification
    The FPS number is Canada's version of the FBI number; a unique number assigned to each criminal
    record and backed up by fingerprints.

      nc:IdentificationID
      A value that identifies something.

    j4:PersonAugmentation
    Additional information about a person.

      j4:PersonStateFingerprintIdentification
      An identifier assigned to a person by a state identification bureau, generally based on submission of
      the person's fingerprints to the state's Automated Fingerprint Identification System (AFIS).

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

  nc:Location
  Details about a physical location.

    nc:LocationAddress
    A geophysical location described by postal information.

      nc:StructuredAddress
      An address.

        nc:AddressBuildingText
        A physical structure at an address.
        This always-optional element contains the building name.

        nc:AddressSecondaryUnitText
        A particular unit within a larger unit or grouping at a location.
        This conditional element contains the department.

        nc:LocationStreet
        A road, thoroughfare or highway.

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

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

          nc:LocationStateName
          A state, commonwealth, province, or other such geopolitical subdivision of a country.
          This conditional element contains the state name.

        nc:LocationPostalCode
        An identifier of a post office-assigned zone for an address.
        This conditional element contains the postal code, or zip code.

Response Formats

Response to Query (WR & VR)

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.

Response from Province (UR & XR)

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.

Response from CPIC (WR, VR, CAR, CGR, CSR & CBR)

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.

Rapsheet Response in Free Text (IR,FR)

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

  Response Text (n:ResponseText)


  This element will contain the free text rapsheet 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.

Standardized Criminal History Rapsheet Response (FR)

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

  Rapsheet (rap:RapSheet)
  This element will contain the standardized criminal history rapsheet response as defined in the Joint
  Task Force Standardized Criminal History XML Specifications.

Communicating with Canada NIEM Examples

Example 1: Persons File query to Canada.

<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>WQ</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>CN</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000190]]> 
    </nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="WQ">
    <nc:Person>
      <nc:PersonBirthDate>
        <nc:Date>1981-08-07</nc:Date> 
      </nc:PersonBirthDate>
      <nc:PersonName>
        <nc:PersonFullName>SMITH, JOHN</nc:PersonFullName> 
      </nc:PersonName>
      <nc:PersonSexCode>M</nc:PersonSexCode> 
    </nc:Person>
    <n2:ReasonCode>T</n2:ReasonCode> 
    <j4:PersonSightedIndicator xmlns:j4="http://niem.gov/niem/domains/jxdm/4.1">true</j4:PersonSightedIndicator> 
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 2: Persons File response from Canada.

<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>WR</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>CN0000000</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000191]]> 
    </nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>01/01/2010</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>08:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>01/01/2010</nh2:MessageSendDate>
    <nh2:MessageSendTime>08:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>41237</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>11236</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="WR">
    <n2:ResponseText>
         ** RESPONSE FROM CANADIAN SYSTEM - PERSONS FILE **
 
         ************************************************************************
         - POSSIBLE CANADIAN CPIC 'PERSONS' FILE HIT. -
 
         YOUR INQUIRY MAY HAVE RESULTED IN A POSSIBLE HIT RECORD
         BEING RETURNED. CONFIRMATION OF THE SELECTED 'PERSONS'
         RECORD 'MUST' BE ACCOMPLISHED USING A 'YQ' MESSAGE
         ADDRESSED TO THE CANADIAN LAW ENFORCEMENT AGENCY
         IDENTIFIED AS THE ORIGINATOR AND OWNER OF THE RECORD.
 
         YOU MUST ADD '00' TO THE END OF THE 7-DIGIT CANADIAN
         AGENCY ORI IN THE RECORD.
 
         EXAMPLE: 'ENTERED BY: TORONTO P.D. ON30570 ON 1991-01-01'
         DESTINATION ORI FOR CONFIRMATION 'YQ' MESSAGE
         WOULD BE ON3057000)
         ************************************************************************
         QUERY POSSIBLE HITS FOR PERSON
         SNME: SMITH G1: JOHN
         SEX: MALE DOB: 1950-01-01
         REM: N,WQ,CNCBP0000,,
         QUERY PERSON SEX: MALE
         MAXIMUM POSSIBLE SCORE 22
         NO: 1 SCORE: 4
         SMITH, JOHN
         **PROHIBITED** 1
         SEX: MALE DOB: 1950-01-01 AGE: 62
         APID: A11111111111111111111111A
         **PROHIBITED** FIREARMS
         SD: 2003-04-07 EXP: INDEF
         CONDITION DESCRIPTION
         1) AA111
         REMARKS
         1) INTERDIT TOUT ARME JUSQU'AU 2010-01-01
         2) APRES LE 2010-01-01 INTERDICTION D'ARME A AUTORISATION RESTR
         3) EINTE OU PROHIBEE SEULEMENT.
 
         CASE: 11111111111111A
         RECORD OWNER
         AA11111 SPVM COUR DU QUEBEC CRIM 514-555-1234 2000-01-01 10:00
         ***CONFIRM WITH ORIGINATING AGENCY***
         201001011011102010010108000
         *** END OF CPIC RESPONSE ***
         OTTAWA, CANADA
    </n2:ResponseText> 
  </n2:NLETSResponseData>
</n2:NLETS>

Example 3: Vehicle File query to Canada.

<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>VQ</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>CN</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000186]]> 
    </nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="VQ">
    <nc:Vehicle>
      <nc:VehicleIdentification>
        <nc:IdentificationID>1X1XX11X11X111111</nc:IdentificationID> 
      </nc:VehicleIdentification>
    </nc:Vehicle>
    <n2:ReasonCode>F</n2:ReasonCode> 
    <j4:PersonSightedIndicator xmlns:j4="http://niem.gov/niem/domains/jxdm/4.1">false</j4:PersonSightedIndicator> 
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 4: Vehicle File response from Canada.

<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>VR</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>CN0000000</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000187]]> 
    </nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>01/01/2010</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>08:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>01/01/2010</nh2:MessageSendDate>
    <nh2:MessageSendTime>08:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>11232</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>11238</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="VR">
    <n2:ResponseText>
         ** RESPONSE FROM CANADIAN SYSTEM - STOLEN VEHICLE FILE **
 
         QUERY VEHICLE
         LIC: AAA111
         PROV: NB
         REM: N,XQ,CNCBP0000,,
         QUERY VEHICLE LIC: AAA111 PROV: NB
         ***NOT ON FILE*** VEHICLE
         QUERY RO LIC: AAA111 PROV: NB
         NO: 1
         LIC: AAA111 PROV: NB EXP: 2015-01-01
         VIN: 1X1XX11X11X111111
         TYPE: AUTO MAKE: OLDS MODEL: AG YEAR: 1990 STYLE: 4HRDTP
         COLOUR: GREEN
         OWNER: SMITH JOHN DOB: 1950-01-01
         ADDR: 1234 ANY STREET FAIRHAVEN NB E5V1A4
         ***CONFIRM STATUS WITH PROVINCIAL MOTOR VEHICLE BRANCH***
         20100101100021201000101100021
         *** END OF CPIC RESPONSE ***
         OTTAWA, CANADA
    </n2:ResponseText> 
  </n2:NLETSResponseData>
</n2:NLETS>

Example 5: Driver License File query to Canada.

<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>UQ</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>PQ</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000183]]> 
    </nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="UQ">
    <n2:Person>
      <nc:PersonBirthDate>
        <nc:Date>1950-01-01</nc:Date> 
      </nc:PersonBirthDate>
      <nc:PersonName>
        <nc:PersonFullName>SMITH, JOHN</nc:PersonFullName> 
      </nc:PersonName>
      <nc:PersonSexCode>M</nc:PersonSexCode> 
    </n2:Person>
    <j4:PersonSightedIndicator xmlns:j4="http://niem.gov/niem/domains/jxdm/4.1">false</j4:PersonSightedIndicator> 
    <n2:ReasonCode>F</n2:ReasonCode> 
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 6: Driver License File response from Canada.

<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>UR</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>CN0000000</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000184]]> 
    </nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>02/20/2010</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>06:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>02/20/2010</nh2:MessageSendDate>
    <nh2:MessageSendTime>06:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>41238</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>10121</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="UR">
    <n2:ResponseText> 
         ** FROM CANADA - QUEBEC R.O. SYSTEM **
 
         REGISTRANT ID NUMBER:B222222222222
         PROV:QUEBEC
         SNAME:SMITH,JOHN
         DOB:1950-01-01 SEX:M EYES:GREENISH-BLUE HT:180
         ADDRESS:123 ANY STREET
         SAINT-CONSTANT QC    POSTAL CODE:A1A1A1
         REF NO:AA111AA1A1 CATEGORY:DRIVER STATUS:VALID
         ISSUE DATE:2010-01-01 EXPIRY DATE:2015-01-01
         CLASS: ALL VEHICLES WITH HOOKUPS OR CLASS 3 VEHICLES TOWING TRAILERS WITH A NET WEIGHT
         OF 2000 KG OR MORE
         BUS ADAPTED FOR MORE THAN 24 PASSENGERSE
         COMMERCIAL VEHICLE OR EQUIPMENT WITH 3 AXLES OR MORE OR VEHICLE WITH 2 AXLES HAVING
         A NET WEIGHT OF 4500 KG OR MORE
         EMERGENCY VEHICLE
         MINIBUS OR BUS ADAPTED FOR 24 PASSENGERS OR LESS
         TAXI
         AUTOMOBILE WITH 2 AXLES AND NET WEIGHT LESS THAN 4500 KG, MOTORHOME, SERVICE OR
         UTILITY VEHICLES
 
         OTTAWA, CANADA
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 7: Vehicle Registration File query to Canada.

<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>XQ</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>ON</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000192]]> 
    </nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="XQ">
    <nc:Vehicle>
      <nc:ConveyanceRegistrationPlateIdentification>
        <nc:IdentificationID>A1111A</nc:IdentificationID> 
      </nc:ConveyanceRegistrationPlateIdentification>
    </nc:Vehicle>
    <n2:ReasonCode>T</n2:ReasonCode> 
    <j4:PersonSightedIndicator xmlns:j4="http://niem.gov/niem/domains/jxdm/4.1">false</j4:PersonSightedIndicator> 
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 8: Vehicle Registration File response from Canada.

<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>XR</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>CN0000000</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000194]]> 
    </nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>02/01/2010</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>05:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>02/01/2010</nh2:MessageSendDate>
    <nh2:MessageSendTime>05:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>90124</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>11234</nh2:SendMessageNumeric> 
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="XR">
    <n2:ResponseText>
         ** FROM CANADA - ONTARIO R.O. SYSTEM **
 
         HC ON11111
         IC00000
         RE:LIC:A1111A      PG: 01
         RIN:111111111    TYPE:C
         NAME:JOHN SMITH
         L9R 1T9 ADDR: 123 ANY STREET,ALLISTON
         VIN:1A111111A11111111 CLASS:TRL 05 MANA 942 FV WHI NO.CYL:0
         STATUS:FIT POWER:UNKNOWN BRAND:NONE
         LIC:A1111A     STATUS:ATTACHED
         TAG:0000000 EXPIRES:31DEC20
 
         PERMIT:B2222222 ISSUED:10JUN02
 
         ENQUIRY RESPONSE COMPLETE##
 
         OTTAWA, CANADA
    </n2:ResponseText> 
  </n2:NLETSResponseData>
</n2:NLETS>

Example 9: Article File query to Canada.

<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>CAQ</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>CN</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000028]]> 
    </nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="CAQ">
    <nc:TangibleItem>
      <nc:ItemSerialIdentification>
        <nc:IdentificationID>M11111111</nc:IdentificationID> 
      </nc:ItemSerialIdentification>
    </nc:TangibleItem>
    <n2:ReasonCode>F</n2:ReasonCode> 
    <n2:PersonSightedIndicator>Y</n2:PersonSightedIndicator> 
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 10: Article File response from Canada.

<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>CAR</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>CN0000000</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000215]]> 
    </nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>01/01/2011</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>01/01/2011</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>11236</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>41231</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="CAR">
    <n2:ResponseText>
         ** RESPONSE FROM CANADIAN SYSTEM - ARTICLE FILE **
 
         QUERY ARTICLE
         SER: 10000
         TYPE: OT
         REM: N,CAQ,AZNLETS20,,
         QUERY ARTICLE SER: 11111
         NO:1
         **ARTICLE** STATUS: STOLEN TYPE: MT
         ITEM: SCIE
         S1: 11111
         MAKE: LENNOX
         REMARKS
         1) KIT DE SCIES EMPORTE-PIECE
         CASE: RDL-100000-000 EXP: 2015-01-01
         RECORD OWNER
         XX11111 SEC PUB RIVIERE-DU-LOUP 418-555-1234 2011-01-01 13:00
         ++ASSOCIATED TO++
         **ARTICLE** STATUS: STOLEN TYPE: MT
         ITEM: ANALYSEUR
         S1: 1111
         MAKE: PROVA
         REMARKS
         1) ANALYSEUR DE PUISSANCE PROVA
         CASE: RDL-100000-000 EXP: 2011-01-01
         RECORD OWNER
         XX11111 SEC PUB RIVIERE-DU-LOUP 418-555-1234 2011-01-01 13:00
         ++ASSOCIATED TO++
         **ARTICLE** STATUS: STOLEN TYPE: MT
         ITEM: BATTERIE
         S1: 11111111
         MAKE: MILWAUKIE
         REMARKS
         1) BATTERIE 28 V
         CASE: RDL-100000-000 EXP: 2015-01-01
         RECORD OWNER
         XX11111 SEC PUB RIVIERE-DU-LOUP 418-555-1234 2011-01-01 13:00
         ++ASSOCIATED TO++
         **ARTICLE** STATUS: STOLEN TYPE: MT
         ITEM: PINCE
         S1: X11111
         MAKE: FLUKEX
         REMARKS
         1) PINCE AMPEREMEETRIQUE
         CASE: RDL-100000-000 EXP: 2015-01-01
         RECORD OWNER
         XX11111 SEC PUB RIVIERE-DU-LOUP 418-555-1234 2011-01-01 13:00
         ++ASSOCIATED TO++
         **ARTICLE** STATUS: STOLEN TYPE: MT
         ITEM: PERCEUSE
         S1: 11111
         MAKE: MILWAUKEE
         REMARKS
         1) PERCEUSE 3-4 350 RPM 120V
         CASE: RDL-100000-000 EXP: 2015-01-01
         RECORD OWNER
         XX11111 SEC PUB RIVIERE-DU-LOUP 418-555-1234 2011-01-01 13:00
         *** CONFIRM WITH ORIGINATING AGENCY ***
         2011010113000320110101130003
         *** END OF CPIC RESPONSE ***
         OTTAWA, CANADA
    </n2:ResponseText> 
  </n2:NLETSResponseData>
</n2:NLETS>

Example 11: Gun File query to Canada.

<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>CGQ</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>CN</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000035]]> 
    </nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="CGQ">
    <nc:Firearm>
      <nc:ItemSerialIdentification>
        <nc:IdentificationID>111111</nc:IdentificationID> 
      </nc:ItemSerialIdentification>
    </nc:Firearm>
    <n2:ReasonCode>F</n2:ReasonCode> 
    <j4:PersonSightedIndicator xmlns:j4="http://niem.gov/niem/domains/jxdm/4.1">false</j4:PersonSightedIndicator> 
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 12: Gun File response from Canada.

<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>CGR</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>CN0000000</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000036]]> 
    </nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>02/10/2010</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>10:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>02/10/2010</nh2:MessageSendDate>
    <nh2:MessageSendTime>10:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>61230</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>71239</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="CGR">
    <n2:ResponseText>
         **********************************************************************
 
         THE FOLLOWING RESPONSE IS FROM THE CANADIAN FIREARMS *
 
         REGISTRATION SYSTEM
 
         **********************************************************************
 
 
         RE: 1234
         UN AA00000
         II00000
         Q GUN ID:B/LANG:E/
         REM: L,CGQ,1111X1X11X1111X111XXXX1X111X0000/
         S1: 110000/CFRO: YES/
 
         QUERY POSSIBLE HITS FOR CFIS
         SER: 111111
         REM: L,CGQ,1111X1X11X1111X111XXXX1X111X0000
 
 
         ***NO: 1
 
         SER: 111111
         MAKE: SAVAGE MOD: MARK IIG
         FIN: 212342 CLASS: NON-RESTRICTED FIREARMS
         TYPE: RIFLE ACTION: BOLT ACTION
         CAL: 22 LR SHOTS: 10 BL: 526
         FIREARM STATUS: EXPORTED
 
         BUSINESS ADDR: 1234 ANY ST 1234 LAKEFIELD ONT CA A0A0A0
 
         CORP: FIRE ARMS
         LIC: 10000000 LIC EXP DATE: 2015-10-10 LIC STATUS: VALID
         CERT: 300000 REG STATUS: ADMINISTRATIVELY EXPIRED
 
 
         ***NO: 2
 
         SER: 111111
         MAKE: ENFIELD MOD: SPORTER
         FIN: 4112345 CLASS: NON-RESTRICTED FIREARMS
         TYPE: RIFLE ACTION: BOLT ACTION
         CAL: 264 WIN MAG SHOTS: 4 BL: 610
         FIREARM STATUS: KNOWN FIREARM
 
         RESIDENCE ADDR: 2345 THIS PL SWIFT CURRENT SASK CA X0X0X0
 
         SNME: SMITH G1: JOHN G2: JIM G3: JAMES DOB: 1950-01-01 SEX: M
         LIC: 2222222 LIC EXP DATE: 2001-01-01 LIC STATUS: EXPIRED
         LIC: 55555555 LIC EXP DATE: 2020-01-01 LIC STATUS: VALID
         CERT: 33333333 REG STATUS: REGISTERED/RECORDED VIA TRANSFER
 
 
         TOTAL HITS: 2
 
         Wed Feb 10 10:00:00 2010
 
         TO CONFIRM A HIT OR REQUEST ASSISTANCE ON A SEARCH, PLEASE CONTACT THE
         RCMP CANADIAN FIREARMS REGISTRY BY SENDING A MESSAGE TO ORI ON80190 OR
         BY CALLING THE RCMP CFP POLICE HELP LINE AT 1-800-731-4000 EXTENSION
         2064 (ENGLISH) AND 2063 (FRENCH).
 
 
         OTTAWA, CANADA
    </n2:ResponseText> 
  </n2:NLETSResponseData>
</n2:NLETS>

Example 13: Securities File query to Canada.

<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>CSQ</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>CN</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000044]]> 
    </nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="CSQ">
    <n2:Securities>
      <nc:ItemOwner /> 
      <nc:ItemSerialIdentification>
        <nc:IdentificationID>QD111111</nc:IdentificationID> 
      </nc:ItemSerialIdentification>
      <nc:ItemCategoryText>PP</nc:ItemCategoryText> 
    </n2:Securities>
    <n2:ReasonCode>S</n2:ReasonCode> 
    <j4:PersonSightedIndicator xmlns:j4="http://niem.gov/niem/domains/jxdm/4.1">false</j4:PersonSightedIndicator> 
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 14: Securities File response from Canada.

<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>CSR</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>CN0000000</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000217]]> 
    </nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>01/01/2011</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>11:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>01/01/2011</nh2:MessageSendDate>
    <nh2:MessageSendTime>11:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>01236</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>31233</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="CSR">
    <n2:ResponseText>
         ** RESPONSE FROM CANADIAN SYSTEM - SECURITY FILE **
         QUERY SECURITY
 
         TYPE: PP
         SNME: SMITH G1: JOHN
         REM: N,CSQ,AZNLETS20,,
         QUERY SECURITY
         NO:1
         **SECURITY** STATUS: LOST TYPE: PP
         S1: AA111111
         SNME: SMITH
         G1: MARGE G2: ELIZABETH
         POI: CANADA
         CASE: PPT-20110101-111 EXP: 2015-01-01
         RECORD OWNER PQ00000 DFAIT PASSPORT OFFICE 613-555-1234 2011-01-01 07:00
         **POINTER PERSON**
         SMITH, MARGE ELIZABETH SEX: FEMALE DOB: 1950-01-01 AGE: 61
         REMARKS
         1) PASSPORT HAS BEEN REPORTED LOST, UNLESS BEING HELD AS
         2) EVIDENCE PLEASE RETURN DOCUMENT TO PASSPORT CANADA
         3) 70 CREMAZIE GATINEAU QC K1A 0G3
 
         CASE: PPT-20110101-111
         RECORD OWNER XX11111 DFAIT PASSPORT OFFICE 613-555-1234 2011-01-01 07:00
         NO:2
         **SECURITY** STATUS: LOST TYPE: PP
         S1: XX000000
         SNME: SMITH
         G1: TONY G2: ROBERT
         POI: CANADA
         CASE: PPT-20100101-000 EXP: 2015-01-01
         RECORD OWNER PQ00001 DFAIT PASSPORT OFFICE 613-555-1234 2011-01-01 06:00
         **POINTER PERSON**
         SMITH, TONY ROBERT SEX: MALE DOB: 1950-01-01 AGE: 61
         REMARKS
         1) PASSPORT HAS BEEN REPORTED LOST, UNLESS BEING HELD AS
         2) EVIDENCE PLEASE RETURN DOCUMENT TO PASSPORT CANADA
         3) 70 CREMAZIE GATINEAU QC K1A 0G3
 
         CASE: PPT-20100101-001
         RECORD OWNER PQ00001 DFAIT PASSPORT OFFICE 613-555-1234 2011-01-01 06:00
         NO:3
         **SECURITY** STATUS: LOST TYPE: PP
         S1: 111111
         SNME: SMITH
         G1: JIMMY G2: M
         POI: SAINT LUCIA, AMERICAS
         REMARKS
         1) PASSPORT
         CASE: 1111111.X11 EXP: 2015-01-01
         RECORD OWNER
         ON11111 TORONTO PS RECORDS 416-555-1234 2011-01-01 16:00
         **POINTER PERSON**
         SMITH, JIMMY M
         SEX: MALE DOB: 1950-01-01 AGE: 61
         ADDR: 1234 ANY STREET, TORONTO ONTARIO
         REMARKS
         1) OWNER OF LOST ID
 
         CASE: 1111111.X11
         RECORD OWNER
         ON11111 TORONTO PS RECORDS 416-555-1234 2011-01-01 16:00
         *** CONFIRM WITH ORIGINATING AGENCY ***
         2011010114003420110101140034
         *** END OF CPIC RESPONSE ***
         OTTAWA, CANADA
    </n2:ResponseText> 
  </n2:NLETSResponseData>
</n2:NLETS>

Example 15: Boat File query to Canada.

<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>CBQ</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>CN</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000030]]> 
    </nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="CBQ">
    <nc:Vessel>
      <nc:VesselHullIdentification>
        <nc:IdentificationID>XXX11111X111</nc:IdentificationID>
      </nc:VesselHullIdentification>
    </nc:Vessel>
    <n2:ReasonCode>S</n2:ReasonCode> 
    <j4:PersonSightedIndicator xmlns:j4="http://niem.gov/niem/domains/jxdm/4.1">false</j4:PersonSightedIndicator> 
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 16: Boat File response from Canada.

<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>CBR</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>CN0000000</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000034]]> 
    </nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>01/01/2011</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>09:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>01/01/2011</nh2:MessageSendDate>
    <nh2:MessageSendTime>09:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>01234</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>31230</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="CBR">
    <n2:ResponseText>
         ** RESPONSE FROM CANADIAN SYSTEM - BOAT/MOTOR FILE **
         **********************************************************************
         - POSSIBLE CPIC 'BOAT/MOTOR' FILE HIT. -
         YOUR INQUIRY MAY HAVE RESULTED IN MULTIPLE RECORDS BEING RETURNED.
 
         CONFIRMATION ON THE SELECTED 'BOAT/MOTOR' MUST BE ACCOMPLISHED USING
         A 'YQ' MESSAGE ADDRESSED TO THE CANADIAN LAW ENFORCEMENT AGENCY
         IDENTIFIED AS THE ORIGINATOR OF THE RECORD.
 
         YOU MUST ADD '00' TO THE END OF THE 7-DIGIT CANADIAN AGENCY ORI
         IN THE RECORD.
         (EXAMPLE: 'TORONTO PD ON30570 1991-01-01 12:00'
         DESTINATION ORI FOR CONFIRMATION WOULD BE ON3057000)
         **********************************************************************
         QUERY BOAT
         BOATID: 11XXXXXX
         REM: N,CBQ,AZNLETS20,,
         QUERY BOAT BOATID: 11XXXXXX
         NO: 1
         **BOAT** STATUS: STOLEN TYPE: POWERBOAT LIC: 11XXXXXX
         NAME: MANSPLEASURE HIN: XXXXXXX
         PROP: INBOARD MLG: 4 M ( 13 FT )
         CASE: ACUPIES TEST-02 EXP: 2015-01-01
         RECORD OWNER XX11111 CPIC-CENTRE-FIELD-SERVICE 111-111-1111 2010-01-01 15:00
         ***CONFIRM WITH ORIGINATING AGENCY***2011010110080020110101100800***
         END OF CPIC RESPONSE
         ***OTTAWA, CANADA
    </n2:ResponseText> 
  </n2:NLETSResponseData>
</n2:NLETS>

Example 17: Criminal Name Index query to Canada.

<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>IQ</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>CN</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000088]]> 
    </nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="IQ">
    <n2:PurposeCode>C</n2:PurposeCode> 
    <n2:ResponseAttentionDescriptionText>NLETS_ANALYST</n2:ResponseAttentionDescriptionText> 
    <j4:Person xmlns:j="http://niem.gov/niem/domains/jxdm/4.1">
      <nc:PersonBirthDate>
        <nc:Date>1950-01-01</nc:Date> 
      </nc:PersonBirthDate>
      <nc:PersonName>
        <nc:PersonFullName>SMITH, JOHN</nc:PersonFullName> 
      </nc:PersonName>
      <nc:PersonRaceText>W</nc:PersonRaceText> 
      <nc:PersonSexCode>M</nc:PersonSexCode> 
    </j4:Person>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 18: Criminal Name Index response from Canada.

<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>IR</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>CN0000000</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
    <![CDATA[ LTN2000093]]> 
    </nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>01/01/2010</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>12:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>01/01/2010</nh2:MessageSendDate>
    <nh2:MessageSendTime>12:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>41233</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>81231</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="IR">
    <n:ResponseText xmlns:n="http://www.nlets.org">
         ** RESPONSE FROM CANADIAN SYSTEM - CRIMINAL NAME INDEX FILE **
         ATN/NLETS_ANALYST
 
         *********************************************************************
         - POSSIBLE CPIC CRIMINAL NAME INDEX FILE HIT. -
 
         - THIS IS NOT A CRIMINAL RECORD -
 
         THIS RECORD MAY OR MAY NOT PERTAIN TO THE SUBJECT OF YOUR ENQUIRY.
         POSITIVE IDENTIFICATION CAN ONLY BE CONFIRMED THROUGH SUBMISSION
         OF FINGERPRINTS TO RCMP IDENTIFICATION SERVICES DIRECTORATE,
         OTTAWA, ONTARIO, CANADA.
 
         TO OBTAIN THE CRIMINAL HISTORY ASSOCIATED WITH YOUR ENQUIRY,
         SUBMIT THE APPROPRIATE NLETS TRANSACTION USING THE 'FPS' NUMBER
         FROM THE RECORD.
         *********************************************************************
 
         RESPONDENTS 2 FOR:
         SMITH JOHN
         SEX: M DOB: 19500101
         >>>QUERY REMARKS: N,IQ,AZNLETS20,,NLETS_ANALYST
         QUERY VALUE 30
 
         RESPONDENT SCORE: 01
 
         FPS: 111111A FPC:W01,W02,W03,W04,W05,W06,W07,W08,W09,W10
         FILE OPEN
 
         MALE, BORN 1950-01-01, NFLD, AGE-NOW 62
         EYES BLUE, WAS 155 CM ( 5FT 01IN) 081 KG ( 178LBS) IN 2003-12
         KNOWN-AS:.... 01....SMITH; JOHN
 
         RESPONDENT SCORE: 01
 
         FPS: 11111B FPC:W01,W02,W03,W04,W05,W06,W07,W08,W09,W10
         FILE OPEN
 
         MALE, WHITE, BORN 1950-01-01, ONT, AGE-NOW 62
         EYES BLUE, WAS 160 CM ( 5FT 03IN) 050 KG ( 110LBS) IN 1991-12
         MARKS NONE
         KNOWN-AS:.... 01....SMITH;JOHN
         2010010113005820100101130058
         *** END OF CPIC RESPONSE ***
         OTTAWA, CANADA
    </n:ResponseText> 
  </n2:NLETSResponseData>
</n2:NLETS>

Example 19: Full Criminal Record query to Canada.

<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>FQ</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>CN</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000071]]> 
    </nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="FQ">
    <n2:PurposeCode>C</n2:PurposeCode> 
    <n2:ResponseAttentionDescriptionText>NLETS_ANALYST</n2:ResponseAttentionDescriptionText> 
    <n2:Person>
      <j4:PersonAugmentation xmlns:j4="http://niem.gov/niem/domains/jxdm/4.1">
        <j4:PersonStateFingerprintIdentification /> 
      </j4:PersonAugmentation>
      <n2:PersonFPSIdentification>
        <nc:IdentificationID>111111A</nc:IdentificationID> 
      </n2:PersonFPSIdentification>
    </n2:Person>
    <nc:Location />
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 20: Full Criminal Record response from Canada.

<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>FR</nh2:MessageKeyCodeText> 
    <nh2:OriginatingORIID>CN0000000</nh2:OriginatingORIID> 
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID> 
    <nh2:DocumentControlFieldText>
      <![CDATA[ LTN2000073]]> 
    </nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>01/01/2010</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>17:00</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>01/01/2010</nh2:MessageSendDate>
    <nh2:MessageSendTime>17:00</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>41236</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>91233</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="FR">
    <n:ResponseText xmlns:n="http://www.nlets.org">
         ** RESPONSE FROM CANADIAN SYSTEM - CRIMINAL HISTORY FILE **
         ATN/NLETS_ANALYSTX174
         FPS:111111A
 
         Q CR LANG:E LVL: 1
         REM: N,FQ,AZNLETS20,,X174
 
         *ROYAL CANADIAN MOUNTED POLICE - IDENTIFICATION SERVICES
         *RESTRICTED - INFORMATION SUPPORTED BY FINGERPRINTS SUBMITTED BY LAW
         *ENFORCEMENT AGENCIES - DISTRIBUTION TO AUTHORIZED AGENCIES ONLY.
         FPS: 111111A
         SMITH. JOHN
 
         *CRIMINAL CONVICTIONS CONDITIONAL AND ABSOLUTE DISCHARGES
         *AND RELATED INFORMATION
         2001-01-01              DRIVING WITH MORE THAN 80      $920 I-D 19 DAYS
         WOODSTOCK NB      MGS OF ALCOHOL IN BLOOD         & PROH DRI 1 YR
                                                                SEC 253(B) CC
                                                                (RCMP WOODSTOCK
                                                                03-2558)
         *END OF CONVICTIONS AND DISCHARGES
         2010010120001120100101200011
         *** END OF CPIC RESPONSE ***
         OTTAWA, CANADA
    </n:ResponseText> 
  </n2:NLETSResponseData>
</n2:NLETS>

Top

Legacy (DEPRECATED)

Communicating with Canada

This section provides detailed specifications for Legacy formats and provides Legacy examples that allow Nlets members to implement the necessary programming and perform the required training to obtain and use information from Canada.

As a part of this interface, users within Canada also will be obtaining information from users in the United States. Since requests from Canada will conform to formats currently in use, states must be able to accept and send to Canadian ORIs.

General Rules

The following are general rules that users must follow when communicating with Canada.

Canadian Addressing Code

All codes are 9 characters with the first 2 characters representing the province or territory and the last two characters zero.

Note that although NCIC has assigned ORIs to Canadian agencies, these are not always used by Canada for this interface. These codes are listed in Canada's ORI file called SAFEFILE. It is accessed using the Nlets TQ message.

At present, you cannot access Canadian ORIs by location. Inquiries can be done by ORI only. Use the two-character code "CN" as the destination address for the TQ.

Message Size

Maximum message size is 14,400 characters per message.

Special Requirements

There are a few special requirements imposed by the international nature of this interface. Details on these may be found within the specifications for each message.

Reason Code (RSN) (Optional)

Following is a list of the authorized reason codes.

Reason for Request Code
Narcotics N
Fraud (includes counterfeit documents) F
Violent crimes (includes robbery, murder, rape, bombing, etc.) V
Traffic Violations T
Theft S
Humanitarian H
Person/Property in Sight (PPS/) (Optional)

The user will indicate "in sight" by inserting a "Y" in this field (e.g. PPS/Y).

If the inquiry is for investigative purposes or the subject of the message, for whatever reason, is not present or available place an "N" in this field (e.g., PPS/N).

Error Messages

All error messages generated by Canada as a result of a fixed format inquiry will be returned to the requester as a response to the inquiry.

For example, an error on a driver license inquiry (message type = UQ) will be returned as a "UR" with a self-explanatory error message.

Status Messages

All status messages relating to the condition of the Canadian interface will be sent as an "SM" type message (as they are on the current Nlets network).

Persons File (WQ/WR)

Persons File Query Specifications (WQ)

The Persons File Query (WQ) must include the following:

  • WQ. (Sender ORI).("CN" Code).TXT
  • NAM/(Name).
  • DOB/(Date of Birth).
  • SEX/(Sex).
  • RSN/(Reason Code).
  • PPS/(Person/Property Code)

All fields are required.

The destination code must be "CN".

The Persons File Query format is described below.

Entry # Char. Explanation
WQ. 2 Message type followed by a period.
Sender ORI 9 Sender ORI followed by a period.
CN. 2 2-character destination code (always CN).
TXT 3 Fixed filed prefix to beginning of message.
NAM/ 4 Prefix to identify name
Name Max. 30

Full name; format is last name, comma, space after
comma is optional) first name, space, middle initial
or name followed by a period.

DOB/ 4 Prefix to identify date of birth.
Date of Birth 6-8 Date of Birth followed by a period. Express as
mmddyy or ccyymmdd.
SEX/ 4 Prefix to identify sex.
Sex 1 Sex; M = male, F = female followed by a period.
Optional
RSN/ 4 Prefix to identify reason code.
Reason code 1

N - Narcotics
F - Fraud (includes counterfeit documents)
V - Violent crimes (incl. robbery, murder, rape,
bombing, etc.)
T - Traffic violations
S - Theft
H - Humanitarian, followed by a period.

PPS/ 4 Prefix identifies "in-sight" field.
Person/Property in sight 1 Must be Y or N.
Note: No period after the last field.

Person File Response Specifications (WR)

The inquirer will receive either a hit or a no record response from the CPIC Person File.

All hit confirmations on a person (or any other hot file hits from Canada) must be handled as any other hits. That is, the inquiring agency will contact the entering agency just as they do with NCIC.

When sending a YQ to Canada insert "NONE" in the NIC number field. (e.g., NIC/NONE.)

Vehicle File (VQ/VR)

Vehicle File Query Specifications (VQ/VR)

All fields are required (with either LIC/or VIN/).

For inquiries on license number, a 2 character province code must be used as the destination.
For inquiries on a VIN, the 2 character destination "CN" must be used.

The vehicle inquiry transaction (VQ) will have the following format:

Entry # Char. Explanation
VQ. 2 Message type followed by a period
Sender ORI 9 Sender ORI followed by a period.
Destination code 2

2 character destination code followed by a period. For
VIN inquiries only "CN" is allowed. For LIC inquiries,
a providence or territory code must be used

TXT 3 Fixed filed prefix to beginning of message
AND
LIC/ 4 Prefix to identify license plate
License number 1-10 License number followed by a period
OR
VIN/ 4 Prefix to identify VIN
Vehicle ID # Max.17 Vehicle ID # followed by a period
Optional
RSN/ 4

Prefix to identify reason code
N - Narcotics
F - Fraud (includes counterfeit documents)
V - Violent crimes (incl. robbery, murder, rape,
bombing, etc.)
T - Traffic violations
S - Theft
H - Humanitarian, followed by a period

PPS/ 4 Prefix to identify "in-sight" code
Person/property
code in-sight
1 Must be Y or N
Note: No period after the last field.

Vehicle File Responses (VR)

Vehicle File Response - No Record (VR)

The NOT ON FILE response occurs when no matching record was found in the Canadian file.

Vehicle File Response - Possible Hit (VR)

A response indicating a possible hit has been made on the Canadian Person File requires that the inquiring agency must confirm the hit with the entering agency.

Driver License Files (UQ/UR)

Driver License Specifications (UQ/UR)

Requests to Canada for driver license information must include NAM, DOB, SEX, RSN and PPS.

The OLN field is optional on inquiries to Alberta, British Columbia, Quebec and Ontario.

If the OLN is not included in the inquiries to these provinces, the search
of the driver license file will be by name and DOB.
If the OLN is included, the search of the driver license file for these four
provinces will be by OLN.

For all other provinces and territories the OLN, as well as the other five fields are required and the search of the driver license file will be by OLN.

This inquiry will also result in a check of the Person file located on the CPIC system. The search of the Person file will be by NAM/DOB.

As a result of a single Driver License Query (UQ) the user will receive both Driver License Responses (URs) and Person File Responses (WRs). These are responses from the provinces/ territories (Driver License Response, UR) and CPIC Person file (Person File Response, WR).

The Driver License File query (UQ) format is described in the table below.

Entry # Char. Explanation
UQ. 2 Message type followed by a period.
Sender ORI 9 Sender ORI followed by a period.
Province/Territory
code
2 2 character province/territory code followed by a period.
TXT 3 Fixed filed prefix to beginning of message.
NAM/ 4 Prefix to identify name.
Name Max.30

Full name in format; last name, first name (space) middle
name or initial (e.g., Tubbs, Kathleen Dorothy) followed
by a period.

DOB/ 4 Prefix to identify date of birth.
Date of birth 6-8 Express as mmddyy or ccyymmdd.
SEX/ 4 Prefix to identify sex field.
Sex 1 M = male, F = female, followed by a period.
OLN/ 4 Prefix to identify driver license field.
Driver lic. # Max.20 Complete driver license number, optional for Alberta,
British Columbia, Quebec, and Ontario.
Optional
RSN/ 4 Prefix to identify reason code.
Reason code 1

N ' Narcotics
F - Fraud (includes counterfeit documents)
V - Violent crimes (incl. robbery, murder, rape, bombing,
etc.)
T - Traffic violations
S - Theft
H - Humanitarian, followed by a period

PPS/ 4 Prefix to identify "in-sight" code.
Person/property
in-sight
1 Must be Y or N.

Note: All fields are required with the exception of OLN when a search on name and DOB is
needed from the four provinces listed above.
No period after the last field.

Person File Access

The inquiry generated from a Driver License Query (UQ) to the CPIC Person file will be by NAM/DOB. It will be as though you sent a Person File Query (WQ) to Canada.

An inquiry result in two inquiries to Canada; one to the CPIC Person file and one to British Columbia.

British Columbia will search their file on the name and DOB since OLN has been left
out and provide the driver license status information.
The CPIC Person file will provide Suspended/prohibited driver status for all other
provinces/ territories.

An inquiry addressed to Nova Scotia, a non-automated province. The message will generate an inquiry to the CPIC Person file and return suspended/prohibited license information. However, other driver license information is not available via a Driver License Query (UQ) since Nova Scotia is not automated. Note, that the OLN is a required field for this province.

Driver License Responses (UR/WR)

There are two types of responses that will result from a Driver License Query (UQ):

  • Person file response (WR) and
  • Province/ territory response (UR).

Since a Driver License Query (UQ) generates an inquiry of the CPIC Person file, the user will be receiving responses from the Person file (WR).

The response will include suspended or prohibited driver status information for all province/territories except British Columbia who will provide the information from their own file.

For those provinces that provide their own registration information, a message following a short line of asterisks will indicate that the query is being processed.

Note: The phrase "RO/DL TRANSACTION BEING PROCESSED" will only be received when
a "UQ" was sent to one of the four automated provinces; British Columbia, Alberta, Ontario
or Quebec.

Province Driver License File Responses (UR)

Only four provinces in Canada have automated driver license files.

These four provinces also provide a search of either name and DOB, or OLN depending on whether the inquirer includes the OLN in their inquiry. They are as follows:

  • Quebec
  • Ontario
  • Alberta
  • British Columbia

When sending a Driver License Query (UQ) to an automated province, the user will receive:

  • Person file check (includes any notification of driver license prohibition)
  • Check of the Province's driver license file.

When sending a Driver License Query (UQ) to a non-automated province or a territory, the user will receive:

  • Person file check (includes notification of driver license prohibition)
  • Driver License Response (UR) message indicating that the province is non-
    automated and, if information OTHER THAN STATUS is needed, send an
    "AM" message directly to the province/territory for a manual check. The
    message will also contain the address of the province or territory as well as
    a copy of the inquiry that was sent.

Vehicle Registration File (XQ/XR)

General requirements include the following:

  • The Vehicle Registration Query will result in a check of the province/territory registration file AND CPIC's Vehicle file.
  • Search on either license number or VIN.
  • License Year (LIY) and License Type (LIT) are not used for Canadian vehicle registration inquiries.
  • As a result of a single Vehicle Registration Query (XQ), the user will receive both Vehicle Registration Responses from the province/territory files (XR) and Vehicle Responses from the CPIC Vehicle file (VRs).
  • On all inquiries to Canada the user must include the reason code (RSN/) indicating the reason for the inquiry and the person/property in-sight code (PPS/) indicating whether the person or property is in-sight of the officer actually making or requesting the information.

An inquiry generated from a Vehicle Registration Query (XQ) will interrogate the CPIC vehicle file. It will be as though you sent a Vehicle File Query (VQ) to Canada.

For those provinces that provide their own registration information, a message following a short line of asterisks will indicate that the query is being processed.

Vehicle Registration File Query Specifications (XQ)

The Vehicle Registration Query (XQ) will have the following format:

Entry # Char. Explanation
XQ. 2 Message type followed by a period.
Sender ORI 9 Sender ORI followed by a period.
Destination code 2 2 character province/territory code followed by a period.
TXT 3 Fixed filed prefix to beginning of message.
THEN EITHER
LIC/ 4 Prefix to identify license plate.
License number 1-10 License number followed by a period.
OR
VIN/ 4 Prefix to identify VIN.
Vehicle ID # Max.17 Vehicle ID # followed by a period.
Optional
RSN/ 4 Prefix to identify reason code.
Reason code 1

N - Narcotics
F - Fraud (includes counterfeit documents)
V - Violent crimes (incl. robbery, murder, rape,
bombing, etc.)
T - Traffic violations
S - Theft
H - Humanitarian, followed by a period.

PPS/ 4 Prefix to identify "in-sight" code.
Person/property
code in-sight
1 Must be Y or N.
Note: No period after the last field.

Vehicle File Responses (XR/VR)

There are two types of responses that will result from a Vehicle Registration Query (XQ):

  • Vehicle file response (VR)
  • Province/territory response (XR).
Vehicle File Response - CPIC (VR)

Since a Vehicle Query generates an inquiry of the CPIC Vehicle file, the user will be receiving responses from the Vehicle File.

Vehicle File Response - Province/Territory (XR)

Only five provinces in Canada house their automated vehicle registration files. They are as follows:

  • Quebec
  • Ontario
  • Alberta
  • British Columbia
  • Saskatchewan

All other provincial and territorial vehicle registration files are automated by CPIC thus inquiries to these provinces or territories will result in automated responses from CPIC rather than the provinces or territories.

When sending a Vehicle Registration Query (XQ) to a province or territory you will receive:

  • A vehicle file check on the CPIC vehicle file.
  • A vehicle registration check, either from CPIC or, for those four provinces
    named above, directly from their file.

For those provinces that provide their own registration information, a message following a short line of asterisks will indicate that the query is being processed.

Vehicle Registration Response Examples (VR/XR)

For those provinces that have their registration information on CPIC, the second part of the response will contain the registration information and will be separated from the wanted vehicle information by a short line of asterisks.

Note: The user may send an Vehicle Registration Query (XQ) and receive only a Vehicle
Response (VR). This is because CPIC may hold the file and return a single response with
both the hot file response as well as the registration information.

The Canadian interface system will wait approximately 30 minutes for a response from the external R.O. system. If no responses is forthcoming the system will return a canned message to the querying agency which states:

ABOVE PROVINCIAL RO/DL SYSTEM RESPONSE DELAYED AT THIS TIME, IF NO RESPONSE
PLEASE RETRY IN 30 MINUTES

Article File (CAQ/CAR)

On all inquiries to Canada the user must include the reason code (RSN/) indicating the reason for the inquiry and the person/property in-sight code (PPS/) indicating whether the person or property is in-sight of the officer actually making or requesting the information.

Article File Inquiry Specifications (CAQ)

The specifications for article file queries include the following:

  • Only "CN" is allowed as an address for "CAQ".
  • The serial number field size, 23 characters, is available for input. However only 16 alpha/numeric characters will be stored and searched.
  • The serial number must be a unique number and not simply a model, stock, style, or part number. Do not enter "UNKNOWN" in this field.
  • No imbedded spaces or blanks are allowed.
  • IMPORTANT: If you type in more than 16 characters, the system only searches on the last 16 characters, not the first 16. Therefore if an article has more than 16 characters, the last 16 characters must be used for inquiring to the CPIC system in order to receive a valid search.

The Article File Query (CAQ) will have the following format:

Entry # Char. Explanation
CAQ. 3 Message type followed by a period.
Sender ORI 9 Sender ORI followed by a period.
Destination ORI 2 2 character destination code followed by a period, will
always be "CN".
TXT 3 Fixed filed prefix to beginning of message.
SER/ 4 Prefix to identify serial number.
Serial number Max.23 Serial number followed by a period.
TYP/ 4 Prefix to identify type of article.
Type 2

Type Field
AA - domestic appliances, e.g. stoves, washers.
BI - non-motorized bicycles, e.g. mountain bikes,
tandems, 10-speeds.
NOTE: Motorized bikes are in the Vehicle File.
BU - Bulk entries that have no unique identifiers,
but are the same commodity and description, e.g.,
large shipment of cigarettes
HH - Household property, e.g. rugs, furniture.
JE - jewelry, e.g. watches, rings.
MI - musical instruments, e.g. violins, guitars.
MT - machinery and tools, e.g. electrical motors,
lawn mowers.
NOTE: Lawn mowers capable of carrying an operator are
in the Vehicle File.
OM - office machines and equipment, e.g. computers.
PA - personal accessories, e.g. hearing aids, luggage.
PE - photographic equipment, e.g. camera, enlargers.
PH - telephones, wireless communication devices, i.e.
cellular phones, Blackberry and PDA.
RA - radio, TV, sound-reproducing equipment, e.g. VCR's.
SC - scientific, optical and measuring devices, e.g.
binoculars.
SP - sporting goods, hobby equipment, e.g. skis, model
aircraft, scuba equipment.
OT - all other articles, e.g. animals, vending machines,
precious metals such as gold bars, uniquely identifiable
gun barrels.

Optional
RSN/ 4 Prefix to identify reason code.
Reason code 1

N - Narcotics
F - Fraud (includes counterfeit documents)
V - Violent crimes (incl. robbery, murder, rape, bombing,
etc.)
T - Traffic violations
S - Theft
H - Humanitarian, followed by a period.

PPS/ 4 Prefix to identify "in-sight" code.
Person/property
in-sight
1 Must be Y or N.

Article File Response Specifications (CAR)

The user is responsible for confirming the article hit with the entering Canadian agency.

The "YQ" message and format is to be used for confirming all hits on the article file.

The destination address of the agency that entered the record may be found in the record itself but it is incomplete. It will state "Entered by:" followed by the name and 7 character address of the agency.

The user must add two zeroes to the end of the Canadian address to create the correct destination address. The user will then proceed through the normal hit confirmation process as with any other stolen article.

Gun File (CGQ/CGR)

The CPIC file provides this information. There may also be occasions when the gun record is associated with other records on the CPIC system. These will be returned as a part of the initial response. Each inquiry will interrogate both the stolen gun file as well as the Canadian gun registration file.

Gun Inquiry Specifications (CGQ)

On all inquiries to Canada the user must include the serial number (SER), type (TYP), reason code (RSN/) indicating the reason for the inquiry and the person/property in-sight code (PPS/) indicating whether the person or property is in-sight of the officer actually making or requesting the information.

  • Only "CN" is allowed as an address for Gun File Queries (CGQ).
  • All fields are required.
  • No period after the last field.
  • IMPORTANT: The serial number field will accept 23 characters but only 11 characters are stored on the CPIC file.
  • When inquiring with more than 11 characters, the CPIC system will search on only the last 11 characters submitted, not the first 11.

The Gun File Query (CGQ) will have the following format:

Entry # Char. Explanation
CGQ. 3 Message type followed by a period.
Sender ORI 9 Sender ORI followed by a period.
Destination ORI 2 2 character destination code followed by a period, will
always be "CN".
TXT 3 Fixed filed prefix to beginning of message.
SER/ 4 Prefix to identify serial number.
Serial number Max.23 Serial number followed by a period.
TYP/ 4 Prefix to identify type of article.
Type 2

Type Field:
SG - shotgun
RI - rifle
RW - restricted weapon
OT - other only.

Optional
RSN/ 4 Prefix to identify reason code.
Reason code 1

N - Narcotics
F - Fraud (includes counterfeit documents)
V - Violent crimes (incl. robbery, murder, rape,
bombing, etc.)
T - Traffic violations
S - Theft
H - Humanitarian, followed by a period.

PPS/ 4 Prefix to identify "in-sight" code.
Person/property
in-sight
1 Must be Y or N.
Gun File Response (CGR)

The user is responsible for confirming the gun hit with the entering Canadian agency.

The "YQ" message and format is to be used for confirming all hits on the gun file.

The destination address of the agency that entered the record may be found in the record itself but it is incomplete. It will state "Entered by:" followed by the name and 7-character address of the agency.

The user must add two zeroes to the end of the Canadian address to create the correct destination address.

The user will then proceed through the normal hit confirmation process as with any other stolen gun.

Gun File Response - No Record (CGR)

This occurs when no matching record was found in the Canadian file.

Gun File Response - Possible Hit (CGR)

A possible hit has been made on the Canadian Gun File. If the user determines that the gun matches the gun described in the record he must confirm that the record is still valid with the entering agency prior to taking any action.

Securities File (CSQ/CSR)

Securities File Query Specifications (CSQ)

Securities File Queries (CSQ) may be made on four different combinations.

The type field must be included on all inquiries; however only certain types are allowed depending on what the user is searching the file. For example, if the user inquires on "issuer", only a type "ST" (TYP/ST) is permissible.

Below is a list of various data elements the user may inquire upon along with the allowable types in parentheses.

  • Serial # and type (all codes listed above)
  • Corporation name and type (SB,BD,MO,OT)
  • Issuer and type (ST)
  • Owner name and type (BD,ID,MO,PP,SB,VD,OT)

The Serial number, the Issuer, the Corporation name, or the owner name and the appropriate type are required.

The RSN and PPS fields are required.

The destination for all Securities File inquiries is "CN".

No period after the last field.

Only "CN" is allowed as an address for "CSQ".

IMPORTANT: The serial number field will accept 23 characters but only 16 characters are stored on the CPIC file. When inquiring with more than 16 characters, the CPIC system will search on only the last 16 characters submitted, not the first 16.

The Securities File Query (CSQ) will have the following format.

Entry # Char. Explanation
CSQ. 3 Message type followed by a period.
Sender ORI 9 Sender ORI followed by a period.
Destination ORI 2 2 character destination code followed by a period, will
always be "CN".
TXT 3 Fixed filed prefix to beginning of message.
SER/ 4 Prefix to identify serial number.
Serial number Max.23 Serial number followed by a period.
OR
ISS/ 4 Prefix to identify issuer of security.
Issuer Max.30 Name of issuer of security followed by a period.
OR
COR/ 4 Prefix to identify name of corporation.
Corporation Max.30 Name of corporation registered as owner of the security
followed by a period.
OR
NAM/ 4 Prefix to identify owner.
Owner's name Max.14 Name of owner of security followed by a period.
FOLLOWED BY
TYP/ 4 Prefix to identify TYP field.
Type 2

BD - Corporate bonds and debentures issued by
corporations, including banks, trust companies,
charitable/religious groups, credit unions and
co-operatives.
CC - Canadian-issued currency.
CU - foreign-issued currency.
ID - stolen, lost, or fraudulent identification documents.
MO - money orders and traveler's checks.
PP - Canadian and foreign passports.
SB - federal, provincial and municipal bonds and
debentures.
ST - stocks.
VD - vehicle documents.
OT - all other security documents followed by a period.

Optional
RSN/ 4 Prefix to identify reason code.
Reason code 1

N - Narcotics
F - Fraud (includes counterfeit documents)
V - Violent crimes (incl. robbery, murder, rape, bombing,
etc.)
T - Traffic violations
S - Theft
H - Humanitarian, followed by a period.

PPS/ 4 Prefix to identify "in-sight" code.
Person/property
in-sight
1 Must be Y or N.

Security File Response (CSR)

The user is responsible for confirming the security hit with the entering Canadian agency.

The "YQ" message and format is to be used for confirming all hits on the securities file.

The destination address of the agency that entered the record may be found in the record itself but it is incomplete. It will state "Entered by:" followed by the name and 7 character address of the agency.

The user must add two zeroes to the end of the Canadian address to create the correct destination address. The user will then proceed through the normal hit confirmation process as with any other stolen security.

Security File Response - No Record (CSR)

This occurs when no matching record was found in the Canadian file.

Boat File (CBQ/CBR)

This information is provided by the CPIC stolen boat file.

If the user needs registration information, send an administrative request to CPIC (ORI = ON1000000) to initiate a manual search.

A boat is defined as a watercraft, which may be a small open vessel, a large vessel, or ship, propelled by oars, sails or engine(s).

Users may also query the Boat File for information on stolen motors. The inquiry is made by serial number and requires a type code.

Boat File Query Specifications (CBQ)

Only the "CN" address is allowed for BHN queries.

At least one of the five key fields must be included in the inquiry (i.e. LIC, BHN, REG, NAM, SER).

When an inquiry is made on any of the five items the computer will search all five indices. For example, if a query is on LIC/1234 and there is a boat with a hull number of "1234", it will be returned. The Canadian system does this to compensate for human error in recognizing which field is which.

The RSN/ and PPS/ fields are required.

The Boat File Query (CBQ) will have the following format.

Entry # Char. Explanation
CBQ. 3 Message type followed by a period.
Sender ORI 9 Sender ORI followed by a period.
Destination code 2

2 character destination code followed by a period. For
VIN inquiries only "CN" is allowed. For LIC inquiries, a
providence or territory code must be used.

TXT 3 Fixed filed prefix to beginning of message.
OR
LIC/ 4 Prefix to identify license plate.
License number 1-10 License number followed by a period.
OR
BHN/ 4 Prefix to identify hull number, CPIC will use HIN for
this field in their response.
Hull ID # Max.12 Hull ID # followed by a period.
OR
REG/ 4 Prefix to identify registration number.
Registration number 1-7

Registration number of large vessels that do not have
to be licensed but must be registered followed by a
period.

OR
NAM/ 4 Prefix to identify boat name field.
Boat name Max.13 Name of boat on hull or stern followed by a period.
OR
SER/ 4 Prefix to identify boat motor number.
Motor serial number 1-18 Boat motor serial number followed by a period.
TYP/ 4 Prefix to identify motor type.
Motor type 5 Optional type code: INB, OUTB, INOUT, OTHER followed by a period.
Optional
RSN/ 4 Prefix to identify reason code.
Reason code 1

N - Narcotics
F - Fraud (includes counterfeit documents)
V - Violent crimes (incl. robbery, murder, rape,
bombing, etc.)
T - Traffic violations
S - Theft
H - Humanitarian, followed by a period.

PPS/ 4 Prefix to identify "in-sight" code.
Person/property
code in-sight
1 Must be Y or N.
Note: No period after the last field

Boat File Response (CBR)

The user is responsible for confirming the boat hit with the entering Canadian agency.

The "YQ" message and format is to be used for confirming all hits on the boat file.

The destination address of the agency that entered the record may be found in the record itself but it is incomplete. It will state "Entered by:" followed by the name and 7 character address of the agency.

The user must add two zeroes to the end of the Canadian address to create the correct destination address. The user will then proceed through the normal hit confirmation process as with any other stolen boats.

Note: Canada uses the prefix "HIN" for hull number. In the United States "BHN" is used.
They are synonymous.

Criminal History Files (IQ/IR, FQ/FR, AQ/AR)

The process for accessing Canadian criminal history records from the RCMP is the same as accessing criminal records in the United States, IQ/FQ/AQ. There are a few differences in the formats however.

  • First, the Canadian system use a unique number assigned to an individual based on fingerprints, the "FPS" number.
  • Second, the Canadian system has an optional field to access additional records when multiple hits on name inquiries are received.
  • Third, the destination is always "CN".

Only agencies that are allowed access to the Triple I file are allowed access to the Canadian criminal history file.

Criminal Name Index Query Specifications (IQ)

The "IQ" is utilized when the agency does not have the FPS Canadian identification number. (The FPS number is Canada's version of the FBI number; a unique number assigned to each criminal record and backed up by fingerprints.)

Response to this type of inquiry will provide personal identification information of one or multiple individuals. Normally, CPIC will return the three records that achieved the highest score.

The user will have the option of retrieving additional records using the "RAR" optional field on a subsequent request.

The user may request that more than three records be returned on the initial inquiry by including the "RAR" field in the initial inquiry with the number of records (up to 10) the user wishes to see.

Once the identification record(s) have been returned it is at the option of the inquirer to select the individual the user is interested in and submit an "FQ" in order to retrieve the full criminal record.

This works very much like NCIC's QH/QR or Nlets interstate IQ/FQ procedures.

The inquiry transaction will have the following format.

Entry # Char. Explanation
IQ 2 Message type followed by a period.
Sender ORI 9 Standard ORI followed by a period.
Destination ORI 2 Must be CN, followed by a period.
TXT 3 Fixed filed prefix to beginning of message.
PUR/ 4 Prefix to identify purpose code.
Purpose code 1 Must be C, E, F, D, J or S followed by a period.

See Introduction Page

for more information.
ATN/ 4 Prefix to identify attention field.
Attention field 30 Name of requestor followed by a period.
NAM/ 4 Prefix to identify name.
Name Max. 30

Full name; format is last name, comma, space after
comma is optional) first name, space, middle initial or
name followed by a period.

DOB/ 4 Prefix to identify date of birth.
Date of Birth 6-8 Date of Birth followed by a period. Express as mmddyy
or ccyymmdd.
SEX/ 4 Prefix to identify sex.
Sex 1 Sex followed by a period; M = male, F = female.
RAR/ (optional) 4 Prefix to identify field used to request additional records.
Request additional
records
13

Request additional records using data from the last record
received, or request additional records in the original
inquiry in the format;
XX,YYYYYYY,ZZ where;
XX = # of additional records (up to 10); only field
required on initial
YYYYYYY =FPS# of last record received
ZZ = score of last record received.

If the response indicates that there are additional identity records on file, the requestor may retrieve these by using the "RAR" field in a subsequent inquiry.

Note: IF THE INQUIRER WANTED TO RETRIEVE MORE THAN 3 RECORDS ON THE
INITIAL INQUIRY HE COULD INCLUDE THE "RAR" FIELD IN THE INQUIRY WITH ONLY A
NUMBER INDICATING THE NUMBER OF RECORDS TO BE RETRIEVED.

This request would return the first 7 records that matched the input data.

Criminal Name Index Response (IR)

When the inquirer queries the CPIC criminal history file by name he will receive identity information only.

There is no manual intervention on this response from CPIC.

If the inquiry was by FPS# a full criminal record may be returned.

Full criminal records will be reviewed by RCMP Identification Services prior to transmission to the inquirer.

If the user wishes to access the full criminal record he must submit the FPS number using the "FQ" message format.

If there are more than 3 identification records that match your name inquiry only the three highest scoring records will be returned.

In order to retrieve additional records, up to 10, you must send the standard "IQ" message with the optional "RAR" field as the last data field. It must be in the following format; RAR:XX,YYYYYYY,ZZ

Where:
     xx = number of additional records required (up to 10), must be 2 characters
     YYYYYYY = the FPS number of the last record received
     ZZ = the score value of the last record received

Note: COMMAS MUST SEPARATE THE ABOVE VALUES

There are some fields that may be unfamiliar to the recipient of Canadian identity records.

Full Criminal Record Query (FQ)

This type of inquiry is used to obtain a full criminal record when the FPS is known.

The Full Criminal Record Query (FQ) format is as follows.

Entry # Char. Explanation
FQ. 2 Message type followed by a period.
Sender ORI 9 Standard ORI followed by a period.
Destination ORI 2 Must be CN, followed by a period.
TXT 3 Fixed filed prefix to beginning of message.
PUR/ 4 Prefix to identify purpose code.
Purpose code 1 Must be C, F, D, J or S followed by a period.

See Introduction Page

for more information.
ATN/ 4 Prefix to identify attention field.
Attention field 30 Name of requestor followed by a period.
FPS/ 4 Prefix to identify FPS field; may use "SID/" as an optional
prefix. The computer will treat them the same.
FPS #Name Max. 7

FPS identification number, based on fingerprints and
assigned by the RCMP; users may use "SID" if it is more
convenient; Nlets and Canada will accept either one.

Full Criminal Record Response Specifications (FR)

This record may be returned when the user submits an FPS number.

All criminal record information in the CPIC file will be returned (with the exception of that information not authorized to be sent internationally).

Because RCMP Identification Services must review all records prior to sending them internationally, users may receive an interim message notifying them that they have realized a hit and it is being verified by the RCMP Identification Services Directorate.

The criminal record is laid out in three columns.

  • The first has the date in yyyy-mm-dd format and the place of the incident.
  • The second column has the charges.
  • The third has the disposition.
Non-retrieveable Criminal History Record

The RCMP has some unique dissemination requirements for records transmitted internationally.

Therefore it is possible to retrieve a valid identity record, request the full record using the FPS number and receive a message that states that the record matching the FPS number submitted contains only information that can not be disseminated outside of Canada.

Supplemental Criminal History Inquiry and Response (AQ/AR)

The AQ format is not accepted by Canada. All information is provided on the initial FQ query

Administrative Messages

Nlets users may direct administrative messages to up to 5 destinations on the CPIC network.

Administrative messages must include:

  • Reason for the request
  • Name of the requester

To broadcast an "AM" message, it must be addressed to "CN" for a country-wide broadcast.

Only narrative messages dealing with urgent operational police matters will be considered for nationwide broadcast in Canada.

Canada has NO facility for broadcasting messages to individual provinces therefore "AM" messages to 2-character province or territory should not be sent. These will be reviewed by INTERPOL in the U.S. prior to forwarding to Canada.

ORION

Access Canada's ORION files in the same manner as with a U.S. agency.

  • Use the two characters "CN" for all provinces and territories of Canada.
  • All Canadian ORIs are 7 characters but two zeros are added to the end to make them 9 character ORIs.
Communicating with Canada Legacy Examples

Example 1: Persons File query to Canada.

WQ.AZNLETS20.CN.TXT
NAM/SMITH,JOHN.DOB/19500101.SEX/M.RSN/T.PPS/Y

Example 2: Persons File response from Canada.

WR.CN0000000
08:00 01/01/2010 41237
08:00 01/01/2010 11236 AZNLETS20
TXT
** RESPONSE FROM CANADIAN SYSTEM - PERSONS FILE **
 
*************************************************************
- POSSIBLE CANADIAN CPIC 'PERSONS' FILE HIT. -
 
YOUR INQUIRY MAY HAVE RESULTED IN A POSSIBLE HIT RECORD
BEING RETURNED. CONFIRMATION OF THE SELECTED 'PERSONS'
RECORD 'MUST' BE ACCOMPLISHED USING A 'YQ' MESSAGE
ADDRESSED TO THE CANADIAN LAW ENFORCEMENT AGENCY
IDENTIFIED AS THE ORIGINATOR AND OWNER OF THE RECORD.
 
YOU MUST ADD '00' TO THE END OF THE 7-DIGIT CANADIAN
AGENCY ORI IN THE RECORD.
 
EXAMPLE: 'ENTERED BY: TORONTO P.D. ON30570 ON 1991-01-01'
DESTINATION ORI FOR CONFIRMATION 'YQ' MESSAGE
WOULD BE ON3057000)
*************************************************************
QUERY POSSIBLE HITS FOR PERSON
SNME: SMITH G1: JOHN
SEX: MALE DOB: 1950-01-01
REM: N,WQ,CNCBP0000,,
QUERY PERSON SEX: MALE
MAXIMUM POSSIBLE SCORE 22
NO: 1 SCORE: 4
SMITH, JOHN
**PROHIBITED** 1
SEX: MALE DOB: 1950-01-01 AGE: 62
APID: A11111111111111111111111A
**PROHIBITED** FIREARMS
SD: 2003-04-07 EXP: INDEF
CONDITION DESCRIPTION
1) AA111
REMARKS
1) INTERDIT TOUT ARME JUSQU'AU 2010-01-01
2) APRES LE 2010-01-01 INTERDICTION D'ARME A AUTORISATION RESTR
3) EINTE OU PROHIBEE SEULEMENT.
 
CASE: 11111111111111A
RECORD OWNER
AA11111 SPVM COUR DU QUEBEC CRIM 514-555-1234 2000-01-01 10:00
***CONFIRM WITH ORIGINATING AGENCY***
201001011011102010010108000
*** END OF CPIC RESPONSE ***
OTTAWA, CANADA

Example 3: Vehicle File query to Canada.

VQ.AZNLETS20.CN.TXT
VIN/1X1XX11X11X111111.RSN/T.PPS/Y

Example 4: Vehicle File response from Canada.

VR.CN0000000
08:00 01/01/2010 11232
08:00 01/01/2010 11238 AZNLETS20
TXT
** RESPONSE FROM CANADIAN SYSTEM - STOLEN VEHICLE FILE **
 
QUERY VEHICLE
LIC: AAA111
PROV: NB
REM: N,XQ,CNCBP0000,,
QUERY VEHICLE LIC: AAA111 PROV: NB
***NOT ON FILE*** VEHICLE
QUERY RO LIC: AAA111 PROV: NB
NO: 1
LIC: AAA111 PROV: NB EXP: 2015-01-01
VIN: 1X1XX11X11X111111
TYPE: AUTO MAKE: OLDS MODEL: AG YEAR: 1990 STYLE: 4HRDTP
COLOUR: GREEN
OWNER: SMITH JOHN DOB: 1950-01-01
ADDR: 1234 ANY STREET FAIRHAVEN NB E5V1A4
***CONFIRM STATUS WITH PROVINCIAL MOTOR VEHICLE BRANCH***
20100101100021201000101100021
*** END OF CPIC RESPONSE ***
OTTAWA, CANADA

Example 5: Driver License File query to Canada.

UQ.AZNLETS20.PQ.TXT
NAM/SMITH,JOHN.DOB/19500101.SEX/M.RSN/T.PPS/Y

Example 6: Driver License File response from Canada.

UR.CN0000000
06:00 02/20/2010 41238
06:00 02/20/2010 10121 AZNLETS20
TXT
** FROM CANADA - QUEBEC R.O. SYSTEM **
 
REGISTRANT ID NUMBER:B222222222222
PROV:QUEBEC
SNAME:SMITH,JOHN
DOB:1950-01-01 SEX:M EYES:GREENISH-BLUE HT:180
ADDRESS:123 ANY STREET
SAINT-CONSTANT QC    POSTAL CODE:A1A1A1
REF NO:AA111AA1A1 CATEGORY:DRIVER STATUS:VALID
ISSUE DATE:2010-01-01 EXPIRY DATE:2015-01-01
CLASS: ALL VEHICLES WITH HOOKUPS OR CLASS 3 VEHICLES TOWING TRAILERS WITH A NET WEIGHT
OF 2000 KG OR MORE
BUS ADAPTED FOR MORE THAN 24 PASSENGERSE
COMMERCIAL VEHICLE OR EQUIPMENT WITH 3 AXLES OR MORE OR VEHICLE WITH 2 AXLES HAVING
A NET WEIGHT OF 4500 KG OR MORE
EMERGENCY VEHICLE
MINIBUS OR BUS ADAPTED FOR 24 PASSENGERS OR LESS
TAXI
AUTOMOBILE WITH 2 AXLES AND NET WEIGHT LESS THAN 4500 KG, MOTORHOME, SERVICE OR
UTILITY VEHICLES
 
OTTAWA, CANADA

Example 7: Vehicle Registration File query to Canada.

XQ.AZNLETS20.ON.TXT
LIC/A1111A.RSN/T.PPS/Y

Example 8: Vehicle Registration File response from Canada.

XR.CN0000000
05:00 02/01/2010 90124
05:00 02/01/2010 11234 AZNLETS20
TXT
** FROM CANADA - ONTARIO R.O. SYSTEM **
 
HC ON11111
IC00000
RE:LIC:A1111A      PG: 01
RIN:111111111    TYPE:C
NAME:JOHN SMITH
L9R 1T9 ADDR: 123 ANY STREET,ALLISTON
VIN:1A111111A11111111 CLASS:TRL 05 MANA 942 FV WHI NO.CYL:0
STATUS:FIT POWER:UNKNOWN BRAND:NONE
LIC:A1111A     STATUS:ATTACHED
TAG:0000000 EXPIRES:31DEC20
 
PERMIT:B2222222 ISSUED:10JUN02
 
ENQUIRY RESPONSE COMPLETE##
 
OTTAWA, CANADA

Example 9: Article File query to Canada.

CAQ.AZNLETS20.CN.TXT
SER/M11111111.TYP/RA.RSN/S.PPS/Y

Example 10: Article File response from Canada.

CAR.CN0000000
13:00 01/01/2011 11236
13:00 01/01/2011 41231 AZNLETS20
TXT
** RESPONSE FROM CANADIAN SYSTEM - ARTICLE FILE **
 
QUERY ARTICLE
SER: 10000
TYPE: OT
REM: N,CAQ,AZNLETS20,,
QUERY ARTICLE SER: 11111
NO:1
**ARTICLE** STATUS: STOLEN TYPE: MT
ITEM: SCIE
S1: 11111
MAKE: LENNOX
REMARKS
1) KIT DE SCIES EMPORTE-PIECE
CASE: RDL-100000-000 EXP: 2015-01-01
RECORD OWNER
XX11111 SEC PUB RIVIERE-DU-LOUP 418-555-1234 2011-01-01 13:00
++ASSOCIATED TO++
**ARTICLE** STATUS: STOLEN TYPE: MT
ITEM: ANALYSEUR
S1: 1111
MAKE: PROVA
REMARKS
1) ANALYSEUR DE PUISSANCE PROVA
CASE: RDL-100000-000 EXP: 2011-01-01
RECORD OWNER
XX11111 SEC PUB RIVIERE-DU-LOUP 418-555-1234 2011-01-01 13:00
++ASSOCIATED TO++
**ARTICLE** STATUS: STOLEN TYPE: MT
ITEM: BATTERIE
S1: 11111111
MAKE: MILWAUKIE
REMARKS
1) BATTERIE 28 V
CASE: RDL-100000-000 EXP: 2015-01-01
RECORD OWNER
XX11111 SEC PUB RIVIERE-DU-LOUP 418-555-1234 2011-01-01 13:00
++ASSOCIATED TO++
**ARTICLE** STATUS: STOLEN TYPE: MT
ITEM: PINCE
S1: X11111
MAKE: FLUKEX
REMARKS
1) PINCE AMPEREMEETRIQUE
CASE: RDL-100000-000 EXP: 2015-01-01
RECORD OWNER
XX11111 SEC PUB RIVIERE-DU-LOUP 418-555-1234 2011-01-01 13:00
++ASSOCIATED TO++
**ARTICLE** STATUS: STOLEN TYPE: MT
ITEM: PERCEUSE
S1: 11111
MAKE: MILWAUKEE
REMARKS
1) PERCEUSE 3-4 350 RPM 120V
CASE: RDL-100000-000 EXP: 2015-01-01
RECORD OWNER
XX11111 SEC PUB RIVIERE-DU-LOUP 418-555-1234 2011-01-01 13:00
*** CONFIRM WITH ORIGINATING AGENCY ***
2011010113000320110101130003
*** END OF CPIC RESPONSE ***
OTTAWA, CANADA

Example 11: Gun File query to Canada.

CGQ.AZNLETS20.CN.TXT
SER/111111.TYP/OT.RSN/S.PPS/Y

Example 12: Gun File response from Canada.

CGR.CN0000000
10:00 02/10/2010 61230
10:00 02/10/2010 71239 AZNLETS20
TXT
*******************************************************************
 
THE FOLLOWING RESPONSE IS FROM THE CANADIAN FIREARMS *
 
REGISTRATION SYSTEM
 
*******************************************************************
 
 
RE: 1234
UN AA00000
II00000
Q GUN ID:B/LANG:E/
REM: L,CGQ,1111X1X11X1111X111XXXX1X111X0000/
S1: 110000/CFRO: YES/
 
QUERY POSSIBLE HITS FOR CFIS
SER: 111111
REM: L,CGQ,1111X1X11X1111X111XXXX1X111X0000
 
 
***NO: 1
 
SER: 111111
MAKE: SAVAGE MOD: MARK IIG
FIN: 212342 CLASS: NON-RESTRICTED FIREARMS
TYPE: RIFLE ACTION: BOLT ACTION
CAL: 22 LR SHOTS: 10 BL: 526
FIREARM STATUS: EXPORTED
 
BUSINESS ADDR: 1234 ANY ST 1234 LAKEFIELD ONT CA A0A0A0
 
CORP: FIRE ARMS
LIC: 10000000 LIC EXP DATE: 2015-10-10 LIC STATUS: VALID
CERT: 300000 REG STATUS: ADMINISTRATIVELY EXPIRED
 
 
***NO: 2
 
SER: 111111
MAKE: ENFIELD MOD: SPORTER
FIN: 4112345 CLASS: NON-RESTRICTED FIREARMS
TYPE: RIFLE ACTION: BOLT ACTION
CAL: 264 WIN MAG SHOTS: 4 BL: 610
FIREARM STATUS: KNOWN FIREARM
 
RESIDENCE ADDR: 2345 THIS PL SWIFT CURRENT SASK CA X0X0X0
 
SNME: SMITH G1: JOHN G2: JIM G3: JAMES DOB: 1950-01-01 SEX: M
LIC: 2222222 LIC EXP DATE: 2001-01-01 LIC STATUS: EXPIRED
LIC: 55555555 LIC EXP DATE: 2020-01-01 LIC STATUS: VALID
CERT: 33333333 REG STATUS: REGISTERED/RECORDED VIA TRANSFER
 
 
TOTAL HITS: 2
 
Wed Feb 10 10:00:00 2010
 
TO CONFIRM A HIT OR REQUEST ASSISTANCE ON A SEARCH, PLEASE CONTACT THE
RCMP CANADIAN FIREARMS REGISTRY BY SENDING A MESSAGE TO ORI ON80190 OR
BY CALLING THE RCMP CFP POLICE HELP LINE AT 1-800-731-4000 EXTENSION
2064 (ENGLISH) AND 2063 (FRENCH).
 
 
OTTAWA, CANADA

Example 13: Securities File query to Canada.

CSQ.AZNLETS20.CN.TXT SER/QD111111.TYP/PP.RSN/H.PPS/N

Example 14: Securities File response from Canada.

CSR.CN0000000
11:00 01/01/2011 01236
11:00 01/01/2011 31231 AZNLETS20
TXT
** RESPONSE FROM CANADIAN SYSTEM - SECURITY FILE **
QUERY SECURITY
 
TYPE: PP
SNME: SMITH G1: JOHN
REM: N,CSQ,AZNLETS20,,
QUERY SECURITY
NO:1
**SECURITY** STATUS: LOST TYPE: PP
S1: AA111111
SNME: SMITH
G1: MARGE G2: ELIZABETH
POI: CANADA
CASE: PPT-20110101-111 EXP: 2015-01-01
RECORD OWNER PQ00000 DFAIT PASSPORT OFFICE 613-555-1234 2011-01-01 07:00
**POINTER PERSON**
SMITH, MARGE ELIZABETH SEX: FEMALE DOB: 1950-01-01 AGE: 61
REMARKS
1) PASSPORT HAS BEEN REPORTED LOST, UNLESS BEING HELD AS
2) EVIDENCE PLEASE RETURN DOCUMENT TO PASSPORT CANADA
3) 70 CREMAZIE GATINEAU QC K1A 0G3
 
CASE: PPT-20110101-111
RECORD OWNER XX11111 DFAIT PASSPORT OFFICE 613-555-1234 2011-01-01 07:00
NO:2
**SECURITY** STATUS: LOST TYPE: PP
S1: XX000000
SNME: SMITH
G1: TONY G2: ROBERT
POI: CANADA
CASE: PPT-20100101-000 EXP: 2015-01-01
RECORD OWNER PQ00001 DFAIT PASSPORT OFFICE 613-555-1234 2011-01-01 06:00
**POINTER PERSON**
SMITH, TONY ROBERT SEX: MALE DOB: 1950-01-01 AGE: 61
REMARKS
1) PASSPORT HAS BEEN REPORTED LOST, UNLESS BEING HELD AS
2) EVIDENCE PLEASE RETURN DOCUMENT TO PASSPORT CANADA
3) 70 CREMAZIE GATINEAU QC K1A 0G3
 
CASE: PPT-20100101-001
RECORD OWNER PQ00001 DFAIT PASSPORT OFFICE 613-555-1234 2011-01-01 06:00
NO:3
**SECURITY** STATUS: LOST TYPE: PP
S1: 111111
SNME: SMITH
G1: JIMMY G2: M
POI: SAINT LUCIA, AMERICAS
REMARKS
1) PASSPORT
CASE: 1111111.X11 EXP: 2015-01-01
RECORD OWNER
ON11111 TORONTO PS RECORDS 416-555-1234 2011-01-01 16:00
**POINTER PERSON**
SMITH, JIMMY M
SEX: MALE DOB: 1950-01-01 AGE: 61
ADDR: 1234 ANY STREET, TORONTO ONTARIO
REMARKS
1) OWNER OF LOST ID
 
CASE: 1111111.X11
RECORD OWNER
ON11111 TORONTO PS RECORDS 416-555-1234 2011-01-01 16:00
*** CONFIRM WITH ORIGINATING AGENCY ***
2011010114003420110101140034
*** END OF CPIC RESPONSE ***
OTTAWA, CANADA

Example 15: Boat File query to Canada.

CBQ.AZNLETS20.CN.TXT
BHN/XXX11111X111.RSN/S.PPS/N

Example 16: Boat File response from Canada.

CBR.CN0000000
09:00 01/01/2011 01234
09:00 01/01/2011 31230 AZNLETS20
TXT
** RESPONSE FROM CANADIAN SYSTEM - BOAT/MOTOR FILE **
**********************************************************************
- POSSIBLE CPIC 'BOAT/MOTOR' FILE HIT. -
YOUR INQUIRY MAY HAVE RESULTED IN MULTIPLE RECORDS BEING RETURNED.
 
CONFIRMATION ON THE SELECTED 'BOAT/MOTOR' MUST BE ACCOMPLISHED USING
A 'YQ' MESSAGE ADDRESSED TO THE CANADIAN LAW ENFORCEMENT AGENCY
IDENTIFIED AS THE ORIGINATOR OF THE RECORD.
 
YOU MUST ADD '00' TO THE END OF THE 7-DIGIT CANADIAN AGENCY ORI
IN THE RECORD.
(EXAMPLE: 'TORONTO PD ON30570 1991-01-01 12:00'
DESTINATION ORI FOR CONFIRMATION WOULD BE ON3057000)
**********************************************************************
QUERY BOAT
BOATID: 11XXXXXX
REM: N,CBQ,AZNLETS20,,
QUERY BOAT BOATID: 11XXXXXX
NO: 1
**BOAT** STATUS: STOLEN TYPE: POWERBOAT LIC: 11XXXXXX
NAME: MANSPLEASURE HIN: XXXXXXX
PROP: INBOARD MLG: 4 M ( 13 FT )
CASE: ACUPIES TEST-02 EXP: 2015-01-01
RECORD OWNER XX11111 CPIC-CENTRE-FIELD-SERVICE 111-111-1111 2010-01-01 15:00
***CONFIRM WITH ORIGINATING AGENCY***2011010110080020110101100800***
END OF CPIC RESPONSE
***OTTAWA, CANADA

Example 17: Criminal Name Index query to Canada.

IQ.AZNLETS20.CN.TXT
PUR/C.ATN/NLETS_ANALYST.NAM/SMITH,JOHN.DOB/19500101.SEX/M

Example 18: Criminal Name Index response from Canada.

IR.CN0000000
12:00 01/01/2010 41233
12:00 01/01/2010 81231 AZNLETS20
TXT
** RESPONSE FROM CANADIAN SYSTEM - CRIMINAL NAME INDEX FILE **
ATN/NLETS_ANALYST
 
*********************************************************************
- POSSIBLE CPIC CRIMINAL NAME INDEX FILE HIT. -
 
- THIS IS NOT A CRIMINAL RECORD -
 
THIS RECORD MAY OR MAY NOT PERTAIN TO THE SUBJECT OF YOUR ENQUIRY.
POSITIVE IDENTIFICATION CAN ONLY BE CONFIRMED THROUGH SUBMISSION
OF FINGERPRINTS TO RCMP IDENTIFICATION SERVICES DIRECTORATE,
OTTAWA, ONTARIO, CANADA.
 
TO OBTAIN THE CRIMINAL HISTORY ASSOCIATED WITH YOUR ENQUIRY,
SUBMIT THE APPROPRIATE NLETS TRANSACTION USING THE 'FPS' NUMBER
FROM THE RECORD.
*********************************************************************
 
RESPONDENTS 2 FOR:
SMITH JOHN
SEX: M DOB: 19500101
>>>QUERY REMARKS: N,IQ,AZNLETS20,,NLETS_ANALYST
QUERY VALUE 30
 
RESPONDENT SCORE: 01
 
FPS: 111111A FPC:W01,W02,W03,W04,W05,W06,W07,W08,W09,W10
FILE OPEN
 
MALE, BORN 1950-01-01, NFLD, AGE-NOW 62
EYES BLUE, WAS 155 CM ( 5FT 01IN) 081 KG ( 178LBS) IN 2003-12
KNOWN-AS:.... 01....SMITH; JOHN
 
RESPONDENT SCORE: 01
 
FPS: 11111B FPC:W01,W02,W03,W04,W05,W06,W07,W08,W09,W10
FILE OPEN
 
MALE, WHITE, BORN 1950-01-01, ONT, AGE-NOW 62
EYES BLUE, WAS 160 CM ( 5FT 03IN) 050 KG ( 110LBS) IN 1991-12
MARKS NONE
KNOWN-AS:.... 01....SMITH;JOHN
2010010113005820100101130058
*** END OF CPIC RESPONSE ***
OTTAWA, CANADA

Example 19: Full Criminal Record query to Canada.

FQ.AZNLETS20.CN.TXT
PUR/C.ATN/NLETS_ANALYST.FPS/111111A

Example 20: Full Criminal Record response from Canada.

FR.CN0000000
17:00 01/01/2010 41236
17:00 01/01/2010 91233 AZNLETS20
TXT
** RESPONSE FROM CANADIAN SYSTEM - CRIMINAL HISTORY FILE **
ATN/NLETS_ANALYSTX174
FPS:111111A
 
Q CR LANG:E LVL: 1
REM: N,FQ,AZNLETS20,,X174
 
*ROYAL CANADIAN MOUNTED POLICE - IDENTIFICATION SERVICES
*RESTRICTED - INFORMATION SUPPORTED BY FINGERPRINTS SUBMITTED BY LAW
*ENFORCEMENT AGENCIES - DISTRIBUTION TO AUTHORIZED AGENCIES ONLY.
FPS: 111111A
SMITH. JOHN
 
*CRIMINAL CONVICTIONS CONDITIONAL AND ABSOLUTE DISCHARGES
*AND RELATED INFORMATION
2001-01-01              DRIVING WITH MORE THAN 80      $920 I-D 19 DAYS
WOODSTOCK NB      MGS OF ALCOHOL IN BLOOD         & PROH DRI 1 YR
                                                                                             SEC 253(B) CC
                                                                                             (RCMP WOODSTOCK
                                                                                             03-2558)
*END OF CONVICTIONS AND DISCHARGES
2010010120001120100101200011
*** END OF CPIC RESPONSE ***
OTTAWA, CANADA

Top

Downloads

Download WQ Schema

Download WR Schema

Download WR Stylesheet

Download VQ Schema

Download VR Schema

Download VR Stylesheet

Download UQ Schema

Download UR Schema

Download UR Stylesheet

Download XQ Schema

Download XR Schema

Download XR Stylesheet

Download CAQ Schema

Download CAR Schema

Download CAR Stylesheet

Download CGQ Schema

Download CGR Schema

Download CGR Stylesheet

Download CSQ Schema

Download CSR Schema

Download CSR Stylesheet

Download CBQ Schema

Download CBR Schema

Download CBR Stylesheet

Download IQ Schema

Download IR Schema

Download IR Stylesheet

Download FQ Schema

Download FR Schema

Download FR Stylesheet

Download AQ Schema

Download AR Schema

Download AR Stylesheet

Top