Chapter 16

Identity Theft File

SECTION 01: INTRODUCTION I. A. B. C. D. DEFINITIONS PURPOSE CRITERIA FOR ENTRY RETENTION PERIOD FOR IDENTITY THEFT VICTIMS RECORDS VALIDATION

3 3 3 4 5 5 6 6 6 6 7 7 7 8 9 10 10 10 10 20 20 20 21 21 22 22 22 22 22 23 23 23 23 24 25 25
Chapter #16-1

SECTION 02: INQUIRIES I. A. B. II. A. B. C. D. DEFINITIONS INQUIRIES INQUIRY SYNTAX PROCEDURE GUIDELINES FOR INQUIRIES OPERATIONAL INQUIRIES RESPONSES PROCEDURES FOR VALID HIT VERIFICATION

SECTION 03: FIELDS AND EDITS I. DEFINITIONS A. MESSAGE KEYS B. FIELDS AND EDITS SECTION 04: ENTRY I. A. B. C. PROCEDURE IDENTITY THEFT VICTIMS FILE ENTRY MASK EXAMPLES OF ENTRIES NOT USING THE MASK MANDATORY FIELDS

SECTION 05: SUPPLEMENTAL DATA ENTRY TRANSACTIONS I. A. II. A. B. C. D. E. F. G. H. DEFINITIONS SUPPLEMENTAL DATA ENTRY TRANSACTIONS PROCEDURE SYNTAX OF A SUPPLEMENTAL DATA ENTRY TRANSACTION IDENTITY THEFT VICTIMS SUPPLEMENTAL DATA ENTRY FIELD EDITS EXAMPLES OF IDENTITY THEFT SUPPLEMENTAL DATA ENTRIES SUPPLEMENTAL DATA ENTRY ACKNOWLEDGMENTS ENTRY GUIDELINES FOR SUPPLEMENTAL DATA ALIAS (AKA) FIELD IN A SUPPLEMENTAL DATA ENTRY ADDITIONAL IDENTIFIERS IN A SUPPLEMENTAL DATA ENTRY ADDITIONAL IDENTIFIERS IN A SUPPLEMENTAL DATA ENTRY MESSAGE

WACIC Manual Revised 10/2010

Chapter 16

Identity Theft File

I.

MODIFICATION OF SUPPLEMENTAL IDENTIFIERS

25 26 26 26 26 27 27 27 29 29 29 30 30 30 31 31 31 31 31 32 32 32 33 33 33 33 34 34 34 34

SECTION 06: MODIFY TRANSACTIONS I. A. B. C. D. E. DEFINITIONS MODIFY TRANSACTIONS SYNTAX IDENTITY THEFT VICTIMS MODIFY FIELD EDITS EXAMPLES OF IDENTITY THEFT VICTIMS RECORD MODIFICATIONS MODIFY ACKNOWLEDGMENTS

SECTION 07: LOCATE TRANSACTIONS I. DEFINITIONS A. LOCATES SECTION 08: CLEAR TRANSACTIONS I. DEFINITIONS A. CLEARS SECTION 09: CANCEL TRANSACTIONS I. A. B. C. D. E. F. DEFINITIONS CANCELS WHEN TO USE A CANCELLATION SYNTAX IDENTITY THEFT VICTIM CANCEL FIELD EDITS EXAMPLES OF IDENTITY THEFT VICTIM RECORD CANCELLATION CANCEL ACKNOWLEDGMENTS

SECTION 10: SUPPLEMENTAL DATA CANCEL TRANSACTIONS I. A. B. C. D. E. F. DEFINITIONS SUPPLEMENTAL DATA CANCELS SYNTAX IDENTITY THEFT VICTIM SUPPLEMENTAL DATA CANCEL FIELD EDITS EXAMPLES OF IDENTITY THEFT VICTIM RECORD CANCELLATION SUPPLEMENTAL DATA CANCEL ACKNOWLEDGMENTS SUPPLEMENTAL DATA CANCELLATION GUIDELINES

WACIC Manual Revised 10/2010

Chapter #16-2

Chapter 16

Identity Theft File

CHAPTER 15: WACIC Identity Theft File SECTION 01: Introduction Procedure #: 15.01.000 Special Order: Supersedes: WACIC Manual 2003 Edition Applies to: ACCESS Users I. DEFINITIONS A. Purpose 1. The Identity Theft Victims File will serve as a means for law enforcement to "flag" stolen identities and identify the imposter when encountered by law enforcement. 2. When an identity theft victim becomes aware that his/her identity has been stolen and reports the incident to law enforcement, the agency's handling of the identity theft case should parallel the criteria as outlined in this chapter. The police officer should complete an incident report and collect pertinent information from the victim to create a victim profile that is entered into the Identity Theft Victims File. The agency enters the information only after the victim signs a consent waiver. The waiver states that the victim provides permission for the information to be entered in the Identity Theft Victims File. It also acknowledges that the victim may withdraw the consent by providing a written request to the entering agency. At that time, the record will be canceled from the Identity Theft File. The profile should include information such as the victim's name, date of birth, Social Security number, and the type of identity theft. Additionally, the police officer should provide the victim with a password that will identify that person as the victim when the police report is filed. (The victim should retain the password to use during any potential future police encounters.) Agencies may also enter a mugshot of the victim into NCIC. The mugshot may be used as an additional form of identification for the victim. When the mugshot is retrieved, it must clearly specify that the mugshot is that of the victim and not that of the offender. Effective Date: August 1, 2006 See Also: CALEA:

WACIC Manual Revised 10/2010

Chapter #16-3

Chapter 16

Identity Theft File

3. During a subsequent encounter by law enforcement, including routine traffic stops, a persons query into WACIC and NCIC will automatically search the Identity Theft Victims File and, if positive, generate a response to the inquiring agency. The officer will receive a response listing the victim profile, including the password, thereby providing the officer with the information necessary to verify that the person encountered is the victim or that the person may be using a false identity. The response should be considered along with additional information or a circumstance surrounding the encounter before the officer takes action. B. Criteria for Entry 1. An entry in the Identity Theft Victims File must be supported by an official complaint recorded by a law enforcement agency. Documentation for the identity theft complaint must meet the following criteria before an entry can be made into the Identity Theft Victims File: 2. Someone is using a means of identification of the victim (denoted in the Identity Theft and Assumption Deterrence Act of 1998 as any name or number that may be used, alone or in conjunction with any other information, to identify a specific individual). a) The identity of the victim is being used without the victim's permission. b) The victim's identity is being used or intended to be used to commit an unlawful activity. c) The victim must sign a consent waiver prior to the information being entered into the Identity Theft File. 3. If the identity of the thief is known and an arrest warrant has been issued, the agency should enter the victim information in the S/F Fields in the Wanted Person File. 4. Only the agency that takes the identity theft complaint may make an NCIC identity theft entry. The only exception is that any criminal justice agency or regional dispatch center may act as a holder of the record for another agency that has no telecommunications equipment. When such an entry is made, the agency holding the record may place its own Originating Agency Identifier (ORI) in the ORI Field only when there is a written agreement between the two agencies that delineates the legal responsibility of each for the record. Additional information concerning these responsibilities can be found in the ORI File Chapter.

WACIC Manual Revised 10/2010

Chapter #16-4

Chapter 16

Identity Theft File

C. Retention Period for Identity Theft Victims Records 1. An identity theft record will remain active until the entering agency cancels it or until the Date of Purge (DOP) is equal to the current date. When the DOP is reached, an administrative message will be sent to the originating agency. The maximum retention period for an identity theft record is 5 years. 2. Other exceptions to the record retention periods will occur in the event a serious error is detected in the record. D. Validation 1. Identify Theft Victims File records will be validated monthly. Each record entered will be subject to validation three months after entry and annually thereafter.

WACIC Manual Revised 10/2010

Chapter #16-5

Chapter 16

Identity Theft File

CHAPTER 15: WACIC Identity Theft File SECTION 02: Inquiries Procedure #: 15.02.000 Special Order: Supersedes: WACIC Manual 2003 Edition Applies to: ACCESS Users I. DEFINITIONS A. Inquiries 1. Operational inquiries (W, QW, DW, QWH) which also search the Identity Theft Victims file are described in the Wanted Person File section. The following will describe the QIT inquiry which searches just the Identify Theft Victims File. B. Inquiry Syntax
Field Header Message Key Originating Agency Identifier Name Date of Birth SEX Race Other Numeric Identifiers Related Search Hit Expanded Name Search Expanded Date of Birth Search End of Text Example W; QIT WA0340500 NAM/SMITH, JOHN J DOB/19490804 SEX/M RAC/W FBI/ MNU/ SOC/ OCA/ NIC/ WAC/ RSH/Y ENS/Y EBS/1 (send)

Effective Date: August 1, 2006 See Also: CALEA:

WACIC Manual Revised 10/2010

Chapter #16-6

Chapter 16

Identity Theft File

II. PROCEDURE A. Guidelines for Inquiries 1. Inquiries with NAM, SEX, RAC, and DOB can be either Message Field Code (MFC) driven or positional. If MFC's are used (NAM/, SEX/, RAC/, DOB/), those fields immediately follow the ORI in the inquiry. If MFC's are not used, then the inquiry is "positional" and the fields must be in the order shown above with each field accounted for, even if not filled. Inquiries using other numerical identifiers (SOC, OLN, MNU, WAC, NIC, etc.) must have the MFC's preceding those identifiers. 2. Inquiries may also contain a RSH Field. If the RSH is Y, secondary hit responses will be returned for all records with the same ORI/OCA contained in the primary hit response. If RSH is not entered, the field will default to N. 3. If ENS/Y is included in an inquiry then additional searches are generated by using each input name part as a last name, interchanging the remaining name parts as given names. For example, Bryan, Morgan Lee; Bryan, Lee Morgan; Morgan, Lee Bryan; Morgan, Bryan Lee; Lee, Morgan Bryan; and Lee, Bryan Morgan. 4. When an inquiry transaction includes the numeric 1 in the EBS Field, the expanded date of birth search will return records with the exact input DOB as well as records with the exact month and day and a range of plus or minus one year of the input DOB. B. Operational Inquiries 1. WACIC/NCIC Inquiry a. Message key QIT checks Identify Theft Victims file records in WACIC and NCIC. Examples: W;QIT.WA0340500.NAM/SMITH, JOHN J.SEX/M.RAC/W. DOB/19490804(Send) W;QIT.WA0340500.NAM/SMITH, JOHN J.OCA/06-1234.RSH/Y(Send) W;QIT.WA0340500.WAC/06J3456789(Send)

WACIC Manual Revised 10/2010

Chapter #16-7

Chapter 16

Identity Theft File

C. Responses 1. WACIC No Record Response WWCIC TIME: 1617 DATE: 042706 TO: LRKPD QIT.WA0340500.NAM/DOE, JOHN J.DOB/19650615 NO WACIC IDENTIFY THEFT VICTIMS RECORDS FOUND 2. WACIC Positive (Hit) Response WWCIC TIME: 1210 DATE: 032105 TO: LRKPD QIT.WA0340500.NAM/DOE, JOHN J.DOB/19490804 ------ RECORD NUMBER 1 OF 1 ---*** CAUTION *** *** DO NOT ARREST ON THIS INFORMATION *** - - - - IDENTITY THEFT VICTIM - - - - - (BASED ON match_ids) MKE/EIT ORI/WA0340500 NAM/DOE, JOHN J .M.W.WA.19490804 HGT/500 WGT/300 EYE/BRO HAI/BRO SKN/FAR OCA/06-1234 SMT/SC R SHLD VICTIM SID/WA123456789 SOC/555332211 MNU/OA-12345 OLN/DOEJJ516ND.WA.2009 LIC/123ABC.WA.2007.PC VIN/119004040.1969.VOLK.BUG.2D.WHI DOT/20070401 DOP/20120401 IDT/CFRD PWD/BIGBOY SUSPECT SID/WA9876543 SUSPECT WAC/06W1234567 MIS/TEST IDENTITY THEFT VICTIM RECORD ENT: 04/21/2004 AT 1206 FROM LRKPD BY/PD LITTLEROCK (LRKPD) WAC/04J0016123 NIC/J490416753 3. NCIC No Record Response NCIC TIME: 1316 DATE: 030206 TO: LRKPD WA0340500 NO NCIC IDENTITY THEFT RECORD DOB/19511012 NAM/SMITH, JOHN

WACIC Manual Revised 10/2010

Chapter #16-8

Chapter 16

Identity Theft File

4. NCIC Positive (Hit) Response

NCIC TIME: 1329 DATE: 030206 TO: LRKPD WA0340500 WARNING - THE IDENTITY OF THE SUBJECT IDENTIFIED IN THIS RECORD HAS BEEN REPORTED STOLEN. REVIEW THE VICTIM PROFILE AND USE CAUTION IN VERIFYING THE IDENTITY OF THIS PERSON. THE PASSWORD INCLUDED IN THIS RESPONSE HAS BEEN ASSIGNED TO THE IDENTITY THEFT VICTIM. VERIFY THAT THE SUBJECT OF INQUIRY CAN CONFIRM THE PASSWORD. MKE/IDENTITY THEFT ORI/MD1012600 NAM/SMITH, JOHN J SEX/M RAC/W POB/MD DOB/19511012 DOE/20040519 HGT/601 WGT/202 EYE/BRO HAI/BRO SKN/ALB SMT/SC R HND FPC/121011CO141159TTCI13 MNU/AS-326141811 SOC/212665660 OCA/123456 MIS/IDENTITY HAS BEEN USED IN CREDIT CARD FRAUD PWD/TOPGUN IDT/CFRD DOT/20041015 ORI IS ANY CITY PD 410 555-5555 NIC/J123456789 DTE/20050505 1400 EST *****WARNING - STANDING ALONE, NCIC IDENTITY THEFT FILE INFORMATION DOES NOT FURNISH GROUNDS FOR THE SEARCH AND SEIZURE OF ANY INDIVIDUAL, VEHICLE, OR DWELLING.***** IMMED CONFIRM IF THIS PERSON IS THE VICTIM OR PERPETRATOR

D. Procedures for Valid Hit Verification 1. Refer to Chapter 1, section 6 for explanation.

WACIC Manual Revised 10/2010

Chapter #16-9

Chapter 16

Identity Theft File

CHAPTER 16: WACIC Manual Identity Theft Victims File SECTION 03: Fields and Edits Procedure #: 16.03.000 Special Order: Supersedes: WACIC Manual 2003 Edition Applies to: ACCESS Users I. DEFINITIONS A. Message Keys
Entry EIT* EN Modify MIT Cancel XIT XN

Effective Date: August 1, 2006 See Also: CALEA:

Identify Theft Victim Supplemental Data

1. A caution indicator, "C", can be added to the message key EIT when it is known that an individual is armed and dangerous, has suicidal tendencies, has previously escaped custody, is a drug addict, or whatever is appropriate to the particular circumstances of the individual. The reason for the caution must be entered in the CMC field, and if necessary further explained in the MIS field. B. Fields and Edits 1. Shown below in the order in which they appear in an entry transaction are the Identity Theft Victims File message fields and their respective MFC, field lengths, entry requirements (required, optional, conditional), and basic edits.

WACIC Manual Revised 10/2010

Chapter #16-10

Chapter 16

Identity Theft File

Field Name Header Message Key Originating Agency Identifier Name Sex Race Place of Birth Date of Birth Height Weight Eye Color Hair Color FBI Number Skin Tone Scars-Marks-Tattoos Date of Purge Fingerprint Class Miscellaneous Number Social Security Number Operators License Nbr Operators License State Operators License Year Date of Theft Originating Agency Case Number Linkage Agency Identifier Linkage Case Number Miscellaneous Notify Originating Agency License Plate License Plate State License Plate Year License Plate Type Vehicle ID Number Vehicle Year Vehicle Make Vehicle Model Vehicle Style Vehicle Color Cautions and Medical Conditions Password Identity Theft Type <Victim>SID <Suspect>SID <Suspect>WAC Citizenship

MFC MKE ORI NAM SEX RAC POB DOB HGT WGT EYE HAI FBI SKN SMT DOP FPC MNU SOC OLN OLS OLY DOT OCA LKI LKA MIS NOA LIC LIS LIY LIT VIN VYR VMA VMO VST VCO CMC PWD IDT

Length 4 9 30 1 1 2 8 3 3 3 3 9 3 10 8 20 15 9 20 2 4 8 20 9 20 500 1 10 2 4 2 20 4 24 3 2 7 2 20 4 10 10 10 2

Required? Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N N N C C N Y N N N N N C C C N C C C C C N Y Y N N N N

Edits A, N, S A A, N A, S A A A N N N A A A, N A A N A, N A, N, S N A, N A N (or NX) N A, N, S A, N A, N, S A, N, S A A, N A N (or NX) A A, N N A A, N A, N A, S A A, N, S A A, N A, N A, N A

CTZ

WACIC Manual Revised 10/2010

Chapter #16-11

Chapter 16

Identity Theft File

Required?:

Y Yes N No C Conditional

Data Type:

A Alphabetic N Numeric S Special Characters

2. MKE (Message Key) a) The MKE field must be a valid message key. 3. ORI (Originating Agency Identifier) a) The ORI field must be a valid NCIC-assigned ORI. The first two characters must be alphabetic. The ORI field must contain the valid NCIC ORI of the agency holding the theft report or the valid NCIC ORI of an agency authorized to act as holder of the record for such entry. 4. NAM (Name) a) The NAM field must contain a minimum of five and maximum of 30 characters, including alphabetics, one comma, hyphen(s), and spaces; comma must follow last name; no more than one space after comma. No more than one hyphen can be entered in the last name. The Personal Descriptors Section of the NCIC Code Manual provides coding instructions. 5. SEX (Sex) a) The SEX field must be a valid code as listed in the Personal Descriptors Section of the NCIC Code Manual. 6. RAC (Race) a) The RAC field must be a valid code as listed in the Personal Descriptors Section of the NCIC Code Manual. 7. POB (Place of Birth) a) The POB field must be two-character alphabetic code from the State and Country Data Codes Section of the NCIC Code Manual. 8. DOB (Date of Birth) a) The DOB field must be eight numbers representing year, month, and day in that order (YYYYMMDD). Days cannot be more than the maximum for the month. Unless the year is a leap year, the date February 29 (----0229) will not be allowed.
WACIC Manual Revised 10/2010 Chapter #16-12

Chapter 16

Identity Theft File

9. HGT (Height) a) The HGT field must be three numeric characters. The first character must be 4, 5, 6, or 7. The second character must be zero or one. When the second character is one, the third character must be zero or one. It may be a minimum of 400 but not more than 711. 10. WGT (Weight) a) The WGT field must be three numeric characters. It may contain a minimum of 50 (050) pounds and maximum of 499 pounds. 11. EYE (Eye Color) a) The EYE field must be three-character alphabetic code from the Personal Descriptors Section of the NCIC Code Manual. 12. HAI (Hair Color) a) The HAI field must be three-character alphabetic code from the Personal Descriptors Section of the NCIC Code Manual. 13. FBI (FBI Number) a) The FBI field may be one to nine characters. It may be up to seven numerics, or one to six numerics followed by an alphabetic character A through H; or one to six numerics followed by an alphabetic character J through Z followed by one or two check digits; or one to six numerics followed by two alphabetic characters followed by one check digit. If the number contains one alphabetic character (J-Z), the check digit will be 1 to 11. If the number contains two alphabetic characters, the first alphabetic cannot be B, G, I, 0, Q, S, U, Y, or Z. The second alphabetic must be A, B, or C, and the check digit will be 0 to 9. The alphabetic characters I and 0 are always invalid. 14. SKN (Skin Tone) a) The SKN field must be three-character alphabetic code from the Personal Descriptors Section of the NCIC Code Manual. 15. SMT (Scars-Marks-Tattoos) a) The SMT field must be a valid code from the Personal Descriptors Section of the NCIC Code Manual.

WACIC Manual Revised 10/2010

Chapter #16-13

Chapter 16

Identity Theft File

16. DOP (Date of Purge) a) The DOP field must be a valid Gregorian date, YYYYMMDD. The DOP is optional and must be greater than the current date but not more than 5 years greater. If not entered, the DOP will default to the current date plus five years. 17. FPC (Fingerprint Class) a) The FPC field must be 20 alphabetic and/or numeric classification characters which must be valid codes from the Personal Descriptors Section of the NCIC Code Manual. If the first character of any finger is numeric, the second character must also be numeric. Codes 00 and 50 may not be used. 18. MNU (Miscellaneous Number) a) The first two characters must be a valid NCIC-assigned code as listed in Personal Descriptors, NCIC 2000 Code Manual. The third character must be a hyphen. Entry of one zero only or a run of zeros only is prohibited in positions 4 through 15. An originating agency police or identification number in MNU cannot be the only numeric identifier in the record. If the MNU exceeds 15 characters, the first 15 characters should be entered in the MNU field. The full MNU should be entered in the MIS Field. 19. SOC (Social Security Number) a) The SOC field must be nine numeric characters not less than 001010001. The SOC cannot have a value of 8 or 9 in the first position or have a value of 00 in the fourth and fifth positions. b) Entries of invalid and/or non-issued numbers are allowed. With each entry of this type, a caveat will be generated by NCIC stating that the SOC has not been assigned and that the agency should check for a possible data entry error. 20. OLN (Operators License Number) a) The OLN field must not be more than 20 alpha-numeric characters. One zero only or run of zeros only may not be used.

WACIC Manual Revised 10/2010

Chapter #16-14

Chapter 16

Identity Theft File

21. OLS (Operators License State) a) The OLS field must be two-character alphabetic code from the State and Country Data Codes Section of the NCIC Code Manual. The OLS is required if an OLN is entered. 22. OLY (Operators License Year) a) The OLY field must be four numeric characters representing the expiration year or the alphabetics NX to represent a non-expiring license. 23. DOT (Date of Theft) a) The DOT field must be a valid Gregorian date (YYYYMMDD) and cannot be greater than the current date. 24. OCA (Originating Agency Case Number) a) The OCA field must contain a maximum of twenty alphabetic and/or numeric characters. It must not contain a single zero only, a run of zeros only, the word NONE, or the first seven characters of the ORI field. 25. LKI (Linkage Agency Identifier) a) The LKI field contains nine alphanumeric characters. It must be a valid assigned ORI contained in ACCESS and WACIC system tables. The LKI and LKA cannot be identical to the ORI and OCA of the record. LKI and LKA are entered as a set. b) The Linkage ORI and OCA Fields are provided as separate fields to associate incidents that are handled by multiple departments. An agency entering a record which does not share the ORI and OCA of records associated with the same incident can enter the ORI and OCA of the associated records in the LKI and LKA Fields. The related search hit indicator (RSH/Y) in an inquiry will retrieve all records linked by case number and ORI to the record retrieved in the inquiry.

WACIC Manual Revised 10/2010

Chapter #16-15

Chapter 16

Identity Theft File

26. LKA (Linkage Case Number) a) The LKA field contains a maximum of 20 alphanumeric characters. It must not contain a single zero only, a run of zeros only, a single alphabetic only or the word NONE. The first seven characters of the LKA cannot equal the first seven characters of the LKI. The only valid special character is the hyphen. The LKA must be valid for the LKI. (There must be an ORI and matching OCA in the System). The record will be rejected if the LKI/LKA Fields are the same as the ORI/OCA Fields. LKI and LKA are entered as a set. 27. MIS (Miscellaneous) a) The MIS field contains a maximum of 500 free text characters. Permissible values: space, &, comma, hyphen, /, #, $, A-Z, 0-9. 28. NOA (Notify Originating Agency) a) If an entering agency believes that notification each time its record is hit will provide investigative leads, regardless of whether the location of the person is known, enter Y in the NOA field. If this field is left blank it defaults to N for no. 29. LIC (License Plate) a) The LIC field contains a maximum of ten alpha-numeric characters. It must not be characters UNK, UNKN, or UNKNOWN. If VMA is AERO, LIS is US, and LIT is PP or NP the first character in the LIC must be the alphabetic N. b) If the license plate number exceeds ten characters, the ten right most characters are entered in the LIC field. 30. LIS (License Plate State) a) The LIS field must be a two-character alphabetic code from the State and Country Data Codes Section of the NCIC Code Manual. 31. LIY (License Plate Year) a) The LIY field must be four numeric characters representing a valid year or the alphabetics NX to represent a non-expiring registration.

WACIC Manual Revised 10/2010

Chapter #16-16

Chapter 16

Identity Theft File

32. LIT (License Plate Type) a) The LIT field must be a valid code from the Vehicle Data Codes Section of the NCIC Code Manual. 33. VIN (Vehicle Identification Number) a) A single zero only, run of zeros only, single alphabetic character only, or all alphabetic characters only, indicating vehicle identification number is unknown, cannot be used. b) If a state-assigned or non-conforming 17-character VIN, SVIN must be entered in the first four characters of the MIS field. If the VIN exceeds 20 characters, only the last 20 characters should be entered in the VIN field. The full VIN must then be shown in the MIS field. c) Additional edits on the VIN are provided in the Vehicle File section of this manual. 34. VYR (Vehicle Year) a) The VYR field must be four numeric characters representing the production (model) year during which the vehicle was manufactured. The year cannot be more than one year beyond the current model year. For entries of model year 1981 or later and when the VIN is 17 characters, the tenth position (vehicle year) of a VIN must be compatible with the VYR. 35. VMA (Vehicle Make) a) The VMA Field can be up to 24 characters. The first four characters must be alphabetic and a valid code as listed in the Vehicle Data Codes Section of the NCIC Code Manual. If the VMA code is less than four characters and data are included in positions 5 through 24, positions 3 and/or 4 should be blanks. The remaining characters are free text and must contain the name of the manufacturer when the VMA code is AERO, ATV, COEQ, CYL, FARM, SNOW, SPEC, TRLR, or TRUK. If the VMO is TL, the codes must not be ASM, ASMB, ASSE, ASSM, MB, MC, MK, MP, MS, NA, TK, TL, UNK, UNKN, XX, XXX, XXXX, YY, YYY, YYYY, ZZ, ZZZ, or ZZZZ. 36. VMO (Vehicle Model) a) VMO edits are provided in the Vehicle File section of this manual.

WACIC Manual Revised 10/2010

Chapter #16-17

Chapter 16

Identity Theft File

37. VST (Vehicle Style) a) If filled, it must be a valid two-character code. (Further edits on the VST are provided in the Vehicle File section of this manual.) 38. VCO (Vehicle Color) a) The VCO field must be a valid color code from the Vehicle Data Codes Section of the NCIC Code Manual. If seven characters, fourth must be a slash (/). 39. CMC (Cautions and Medical Conditions) a) The CMC field must be a valid code as listed in the Personal Descriptors Section of the NCIC Code Manual. If caution indicator C is added to the entry MKE this field is required. 40. PWD (Password) a) The PWD field may be up to 20 alphabetics, numerics, or special characters. 41. IDT (Identity Theft Type) a) The IDT field must be a valid code as listed in the NCIC Code Manual. 42. <victim>SID (Victims State Identification Number) a) This field contains a maximum of 10 characters. If SID starts with "WA", then it must have a length of 10 and have a valid check digit. Otherwise, first two characters must be a valid State Code and have length 3-10 inclusive. 43. <suspect>SID (Suspects State Identification Number) a) This field contains a maximum of 10 characters. If SID starts with "WA", then it must have a length of 10 and have a valid check digit. Otherwise, first two characters must be a valid State Code and have length 3-10 inclusive. 44. <suspect>WAC (Suspects WACIC Number) a) This field contains a maximum of 10 alphabetic and numeric characters.

WACIC Manual Revised 10/2010

Chapter #16-18

Chapter 16

Identity Theft File

45. WAC (WACIC Number) a) The WAC field contains a number consisting of the year of entry and the letter J, followed by seven numbers which are automatically assigned by WACIC to each accepted entry. For example: 06J1234567. 46. NIC (NCIC Number) a) A self-checking number consisting of the alphabetic character J, followed by nine numeric characters, which are automatically assigned by the NCIC computer to each accepted record. Must have valid check digit when used to identify record in a subsequent transaction. 47. CTZ (Citizenship) a) The CTZ field must contain a two-character country code from the State and Country Data Codes of the NCIC Code Manual.

WACIC Manual Revised 10/2010

Chapter #16-19

Chapter 16

Identity Theft File

CHAPTER 16: WACIC Manual Identity Theft Victim File SECTION 04: Entry Procedure #: 16.04.000 Special Order: Supersedes: WACIC Manual 2003 Edition Applies to: ACCESS Users I. PROCEDURE A. Identity Theft Victims File Entry Mask 1. ACCESS provides a mask for all WEBMSS terminals. The mask allows users to fill in the blanks when making an Identity Theft Victim entry. To retrieve the mask, enter the following transaction:
F;ITV(Send) MKE/____ ORI/ _________ NAM/______________________________ SEX/_ RAC/_ POB/ __ DOB/________ HGT/___ WGT/___ EYE/ ___ HAI/___ FBI/ _________ SKN/ ___ SMT/ __________ DOP/ ________ FPC/ ____________________ MNU/ ______________ SOC/ _________ OLN/ ____________________ OLS/ __ OLY/ ____ DOT/________ OCA/____________________ LKI/ _________ LKA/ ____________________ MIS/ __________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________ NOA/ _ LIC/ ________ LIS/ __ LIY/ ____ LIT/ __ VIN/____________________ VYR/ ____ VMA/ ________________________ VMO/ ___ VST/ __ VCO/ _______ CMC/ __ PWD/ ________ IDT/ ____ VICTIM SID/ __________ SUSPECT SID/ __________ SUSPECT WAC/ __________ _____ REQUIRED FIELD . . . ENTER IDENTITY THEFT VICTIM FORMAT . . .

Effective Date: August 1, 2006 See Also: CALEA:

WACIC Manual Revised 10/2010

Chapter #16-20

Chapter 16

Identity Theft File

B. Examples of Entries Not Using the Mask 1. Identity Theft Victim Entry W;EIT.WA0340500.SMITH, JOHN J.M.W.WA.19490804.502.300.BRO.BRO.. FAR.SC R SHLD.20110410...555332211.SMITHJJ516ND.WA. 2009.20060410.06-54321...MISC IDENTITY THEFT VICTIM INFO.Y. ZYX123.WA.2006.PC.119001122.69.VOLK.BUG.2D.WHI..BIGBOY.CFRD... 06W1234567(Send) 2. Entry Acknowledgments. A successful entry results in an acknowledgment from WACIC and NCIC sent to a terminal printer. a) WACIC Identity Theft Victim Entry Acknowledgment WWCIC TIME: 1338 DATE: 041005 TO: LRKPD WA0340500 ENTERED EIT NAM/SMITH, JOHN J WAC/06J1234567 OCA/06-54321 04/10/06 AT 1336 b) NCIC Identity Theft Victim Entry Acknowledgment NCIC TIME: 1327DATE: 030206 TO: ABCPD WA0340500 NAM/SMITH, JOHN J NIC/J146203706 C. Mandatory Fields 1. The following fields are mandatory to enable an Identity Theft Victim entry to be accepted: MKE, NAM, SEX, RAC, POB, DOB, HGT, WGT, EYE, HAI, OCA, PWD, and IDT. The entry will be rejected if one of the mandatory fields is left unfilled.

WACIC Manual Revised 10/2010

Chapter #16-21

Chapter 16

Identity Theft File

CHAPTER 16: WACIC Manual Identity Theft Victims File SECTION 05: Supplemental Data Entry Transactions Procedure #: 03.06.000 Special Order: Supersedes: WACIC Manual 2003 Edition Applies to: ACCESS Users I. DEFINITIONS A. Supplemental Data Entry Transactions 1. The supplemental data entry transaction is used to append additional identifiers to the Identity Theft Victim record. To enter information into a supplemental record, that field must first be filled in the base record. That is, if an attempt is made to enter an SOC as a supplemental data entry, a reject will occur if no SOC exists in the base record. 2. Supplemental data entry to a record is restricted to the agency that entered the record. II. PROCEDURE A. Syntax of a Supplemental Data Entry Transaction
Field Header Message Key Originating Agency Identifier Record Identifier Record Identifier Supplemental Field(s) or Set(s) End of Text Example W; EN WA0340500 NAM/SMITH, JOHN J OCA/06-54321 DOB/19480804.19500804. SMT/POCKMARKS.SC L SHLD. (Send)

Effective Date: August 1, 2006 See Also: CALEA:

1. The supplemental data entry transaction consists of the message key, ORI, two record identifiers, and the supplemental fields being added. Permissible record identifiers are NAM and OCA, NAM and WAC, or NAM and NIC. The supplemental fields being added must be identified by their appropriate MFC.

WACIC Manual Revised 10/2010

Chapter #16-22

Chapter 16

Identity Theft File

B. Identity Theft Victims Supplemental Data Entry Field Edits

Field MKE ORI 1 Record Identifier 2 Record Identifier Supplemental Fields(s) or Set(s)
nd st

Edits The MKE for all Identity Theft Victims supplemental data entries is EN. Must be a valid ORI and match the ORI in the record being supplemented. The first of two identifiers to identify the record to be supplemented. Must be NAM. The second of two identifiers to identify the record to be supplemented. Can be OCA, WAC, or NIC. The field(s) or set(s) to be added. Each must be identified by its MFC.

C. Examples of Identity Theft Supplemental Data Entries W;EN.WA0340500.NAM/SMITH, JOHN J.OCA/06-54321. DOB/19480804.19500804.SMT/SC R SHLD.POCKMARKS(send) D. Supplemental Data Entry Acknowledgments 1. WACIC Acknowledgement WACIC TIME: 0735 DATE: 050306 TO: LRKPD WA0340500 SUPP RECORD NAM/SMITH, JOHN J OCA/06-54321 MODIFIED FIELDS: DOB.SMT 2. NCIC Acknowledgement NCIC TIME: 1330 DATE: 050306 TO: LRKPD WA0340500 SUPP NAM/SMITH, JOHN J OCA/06-54321 E. Entry Guidelines for Supplemental Data 1. The Alias field and all other additional identifying data fields which may be included in a supplemental record are listed below with their field codes and the maximum number of aliases and/or additional identifiers that may be added to an identity theft victim record.
FIELD Alias Date of Birth Scars, Marks, Tattoos, etc. Miscellaneous Identifying Number WACIC Manual Revised 10/2010 FIELD CODE AKA DOB SMT MNU MAX NUMBER PERMITTED 99 9 9 9 Chapter #16-23

Chapter 16

Identity Theft File

Social Security Number Cautions and Medical Conditions Images (set)

SOC CMC IID

9 10 12

2. After the identity theft victim record has been identified, each field included in a supplemental record entry, except those entered in sets of data, must be identified by the appropriate field code followed by a slash and the item(s) of data. The data elements must be separated by a period and each field must end with a period. Fields that are not a part of sets of data may be entered in any order in a supplemental record entry. 3. The IID field in the supplemental record format is a multiple element data field; that is, this field has more than one data element following the field code and slash and is entered in sets. 4. Each set of data must be preceded by the appropriate field code followed by a slash. The data elements within a set of data must be entered in sequence after the slash, and each data element must be filled. 5. The DOB, SMT, MNU, SOC fields in the main record must be filled before any supplemental entry for that same field will be accepted. For example, any attempt to enter a Social Security number in a supplemental record will be rejected as a format error if the main record does not contain a Social Security number in the SOC. 6. Further guidelines for the coding of personal identifiers are provided in Personal Descriptors of the NCIC Code Manual. F. Alias (AKA) Field in a Supplemental Data Entry 1. Field code AKA followed by a slash is used to identify an alias (es). 2. An alias includes any names in which any last, first, or middle name is different from that in the NAM Field (or those previously entered in the AKA Field) for the record, i.e. NAM/Smith, Michael Lee and AKA/Smith, Lee Michael 3. Aliases are to be listed with the last name, comma (space after comma is optional), first name or initial, space, middle name or initial, if any, space, and suffix indicating seniority, if any. Aliases and/or variations in name spelling must be separated by a period without repeating the MFC AKA. 4. Nicknames (monikers) are entered in the AKA Field of the record. Further guidelines for the coding of aliases are provided in Personal Descriptors of the NCIC Code Manual.

WACIC Manual Revised 10/2010

Chapter #16-24

Chapter 16

Identity Theft File

5. It is not necessary to make alias entries for each combination of a compound or hyphenated surname. Both the WACIC and NCIC systems index each component of compound or hyphenated surnames so an inquiry on any component or combination will produce a hit on the name as entered. For example, a record entered with NAM/SMITH-JONES, JOHN JAY will be retrieved by an inquiry with NAM/SMITH, JOHN JAY, NAM/JONES, JOHN JAY, or NAM/SMITHJONES, JOHN JAY. If a possibility exists that the surname and given name could be reversed, then an alias entry should be made. G. Additional Identifiers in a Supplemental Data Entry 1. The MFCs followed by a slash are used to identify additional data to be included in a supplemental record, i.e. DOB/, SMT/, MNU/, and SOC/. Multiples can be entered without repeating the MFC and separated only by periods. For example, an entry might include: DOB/19500101.19490804.SMT/SC L SHLD.POCKMARKS. MNU/PI-WA12252333.SOC/123456789 2. When identifying data are entered in a supplemental record, the corresponding fields in the corresponding base record must be filled. H. Additional Identifiers in a Supplemental Data Entry Message 1. A maximum of nine additional identifiers of various kinds may be entered in one supplemental record entry message. Additional messages are required if more identifiers are to be entered. Each AKA (or variation of name spelling); DOB, SMTs, MNU, or SOC, etc.; is counted as one identifier. Each set of data relating to an image is likewise counted as one identifier. I. Modification of Supplemental Identifiers 1. No one-step procedure is available to modify an alias or other identifier in a supplemental record to a record. To modify (change) an alias or other identifier in a supplemental record, the incorrect alias or other identifier must be cancelled and re-entered. 2. A modify message to the base record to delete information in a field will cause the same data in the supplemental record to move up to the base record.

WACIC Manual Revised 10/2010

Chapter #16-25

Chapter 16

Identity Theft File

CHAPTER 16: WACIC Manual Identity Theft Victims File SECTION 06: Modify Transactions Procedure #: 16.06.000 Special Order: Supersedes: WACIC Manual 2003 Edition Applies to: ACCESS Users I. DEFINITIONS A. Modify Transactions 1. The modify transaction is used to add, delete, or change information in one or more fields of an active identity theft victim record. A record cannot be modified if the record is in a located status. 2. Modification of a record is restricted to the agency that entered the record. B. Syntax
Field Header Message Key Originating Agency Identifier Record Identifier Record Identifier Modified Field(s) End of Text Example W; MIT WA0340500 NAM/SMITH, JOHN J OCA/06-54321 EYE/BLU.HAI/BLN (Send)

Effective Date: August 1, 2006 See Also: CALEA:

1. The modify transaction consists of the message key, ORI, two record identifiers, and the fields being modified. Permissible record identifiers are NAM and OCA, NAM and WAC, or NAM and NIC. The fields being modified must be identified by their appropriate MFC. Any field except the MKE can be modified. To delete information from a field, use the MFC followed by a period, (e.g., SMT/.). Data cannot be deleted from a required field.

WACIC Manual Revised 10/2010

Chapter #16-26

Chapter 16

Identity Theft File

C. Identity Theft Victims Modify Field Edits

Field MKE ORI 1 Record Identifier 2 Record Identifier Modified Field(s)
nd st

Edits The MKE for all Identity Theft Victims modifies is MIT. Must be a valid ORI and match the ORI in the record being modified. The first of two identifiers to identify the record to be modified. Must be NAM. The second of two identifiers to identify the record to be modified. Can be OCA, WAC, or NIC. The field(s) in the record to be modified. Each must be identified by its MFC.

D. Examples of Identity Theft Victims Record Modifications W;MIT.WA0340500.NAM/SMITH, JOHN J.OCA/06-54321.EYE/BLU. HAI/BLN(send) E. Modify Acknowledgments 1. WACIC Acknowledgment WWCIC TIME: 1341 DATE: 041006 TO: LRKPD WA0340500 MODIFIED EIT NAM/SMITH, JOHN J WAC/06J0087257 OCA/06-54321 MODIFIED FIELDS: EYE, HAI 04/10/2006 AT 13/41 2. NCIC Acknowledgment NCIC TIME: 1341 DATE: 041006 TO: LRKPD WA0340500 MODIFY NAM/SMITH, JOHN J NIC/J146203706 F. Additional Guidelines 1. To remove all operator license data, a modification message, which includes OLN/. will remove OLN, OLY and OLS fields. 2. To remove all license information, a modification message, which includes LIC/. will remove LIC, LIS, LIY, and LIT fields.

WACIC Manual Revised 10/2010

Chapter #16-27

Chapter 16

Identity Theft File

3. To remove all vehicle information, a modification message, which includes VIN/. will remove all vehicle information except license information. To remove all vehicular information, include LIC/LIC-VCO/. in your modify message. 4. Required fields can be modified; however, they cannot be deleted by the use of a modify entry. 5. If a modify deletes information from a field in a base record for which there is supplemental data entered, the first supplemental data value will roll up into the base record. For example, if you modify the base record to delete to SMT field, the first supplemental SMT will roll up to the base record.

WACIC Manual Revised 10/2010

Chapter #16-28

Chapter 16

Identity Theft File

CHAPTER 16: WACIC Manual Identity Theft Victim File SECTION 07: Locate Transactions Procedure #: 16.07.000 Special Order: Supersedes: WACIC Manual 2003 Edition Applies to: ACCESS Users I. DEFINITIONS Effective Date: August 1, 2006 See Also: CALEA:

A. Locates 1. There is no locate transaction associated with the Identity Theft Victims File.

WACIC Manual Revised 10/2010

Chapter #16-29

Chapter 16

Identity Theft File

CHAPTER 16: WACIC Manual Identity Theft Victim File SECTION 08: Clear Transactions Procedure #: 16.08.000 Special Order: Supersedes: WACIC Manual 2003 Edition Applies to: ACCESS Users I. DEFINITIONS Effective Date: August 1, 2006 See Also: CALEA:

A. Clears 1. There is no clear transaction associated with the Identify Theft Victims File.

WACIC Manual Revised 10/2010

Chapter #16-30

Chapter 16

Identity Theft File

CHAPTER 16: WACIC Manual Identity Theft Victim File SECTION 09: Cancel Transactions Procedure #: 16.09.000 Special Order: Supersedes: WACIC Manual 2003 Edition Applies to: ACCESS Users I. DEFINITIONS A. Cancels 1. The cancel transaction deletes a record that is incorrect or invalid from the Identity Theft Victims File. B. When to Use a Cancellation 1. Cancellation of a record is restricted to the agency that entered the record. A cancellation message is used when the entering agency determines that the record is no longer valid; for example, the identity theft complaint was found to be invalid. C. Syntax
Field Header Message Key Originating Agency Identifier Record Identifier Record Identifier Date of Cancel Reason for Property Record Removal End of Text Example W; XIT WA0340500 NAM/SMITH, JOHN J OCA/06-54321 20060425 CASE DROPPED (send)

Effective Date: August 1, 2006 See Also: CALEA:

WACIC Manual Revised 10/2010

Chapter #16-31

Chapter 16

Identity Theft File

1. The cancel transaction consists of the message key, ORI, two record identifiers, the date of cancel, and optional benefits data field. Permissible record identifiers are NAM and OCA, NAM and WAC, or NAM and NIC. The date of cancel is optional and if not used the record is cancelled as of the current date, this field must be accounted for by including a blank field when benefits data is included at the end of the transaction. D. Identity Theft Victim Cancel Field Edits
Field MKE ORI 1 Record Identifier 2 Record Identifier Date of Cancel
nd st

Reason for Property Record Removal

Edits The message key for all Identity Theft Victims cancels is XIT. Must be a valid ORI and match the ORI in the record being cancelled. The first of two identifiers to identify the record to be cleared. Must be NAM. The second of two identifiers to identify the record to be cleared. Can be OCA, WAC, or NIC. OPTIONAL. If used must be a valid date in the format YYYYMMDD and must be the current date or the current date minus one day. If not used the record is cancelled as of the current date. Can be 10-21 alpha-numeric characters, possible values are: CASE DROPPED NOT WANTED WARRANT DISMISSED

E. Examples of Identity Theft Victim Record Cancellation W;XIT.WA0340500.NAM/SMITH, JOHN J.OCA/0654321.20060425.CASE DROPPED(send) F. Cancel Acknowledgments 1. WACIC Acknowledgment WWCIC TIME: 0837 DATE 042506 TO: LRKPX WA0340500 CANCELED EIT NAM/SMITH, JOHN J WAC/06J0073824 OCA/06-54321 2. NCIC Acknowledgment NCIC TIME: 1330 DATE: 030206 TO: ABCPD WA0340500 CANCEL NAM/SMITH, JOHN J NIC/J146203706
WACIC Manual Revised 10/2010 Chapter #16-32

Chapter 16

Identity Theft File

CHAPTER 16: WACIC Manual Identity Theft Victim File SECTION 10: Supplemental Data Cancel Transactions Procedure #: 16.10.000 Special Order: Supersedes: WACIC Manual 2003 Edition Applies to: ACCESS Users I. DEFINITIONS A. Supplemental Data Cancels 1. The supplemental data cancellation is used to remove supplemental data appended to an identity theft victim base record that is determined to be inaccurate or invalid. Supplemental data cannot be modified; in order to change a supplemental identifier, it must be cancelled and reentered. 2. Canceling supplemental data appended to an identity theft victim record is restricted to the agency that entered the record. B. Syntax
Field Header Message Key Originating Agency Identifier Record Identifier Record Identifier Supplemental Field(s) or Set(s) End of Text Example W; XN WA0340500 NAM/SMITH, JOHN J OCA/06-54321 SMT/SC L SHLD.DOB/19480501.19500408 (send)

Effective Date: August 1, 2006 See Also: CALEA:

1. The supplemental data cancel transaction consists of the message key, ORI, two record identifiers, and the supplemental field(s) being cancelled. Permissible record identifiers are NAM and OCA, NAM and WAC, or NAM and NIC.

WACIC Manual Revised 10/2010

Chapter #16-33

Chapter 16

Identity Theft File

C. Identity Theft Victim Supplemental Data Cancel Field Edits

Field MKE ORI 1 Record Identifier 2 Record Identifier Supplemental Field(s) or Set(s)
nd st

Edits The message key for all Identity Theft Victims supplemental data cancels is XN. Must be a valid ORI and match the ORI in the record being cancelled. The first of two identifiers to identify the record to be cleared. Must be NAM. The second of two identifiers to identify the record to be cleared. Can be OCA, WAC, or NIC.

THE SUPPLEMENTAL DATA FIELD(S) OR SET(S) TO BE CANCELLED. EACH MUST BE IDENTIFIED BY ITS MFC

D. Examples of Identity Theft Victim Record Cancellation W;XN.WA0340500.NAM/SMITH, JOHN J.OCA/06-54321.SMT/SC L SHLD.DOB/19480804.19500408(send) E. Supplemental Data Cancel Acknowledgments 1. WACIC Acknowledgment WWCIC TIME: 0837 DATE 042506 TO: LRKPX WA0340500 CANCELED SUPP NAM/SMITH, JOHN J SMT/SC L SHLD DOB/19480804.19500408 2. NCIC Acknowledgment NCIC TIME: 1330 DATE: 030206 TO: ABCPD WA0340500 CANCEL SUPP NAM/SMITH, JOHN J NIC/J146203706 SMT/SC L SHLD DOB/19480804 19500408 F. Supplemental Data Cancellation Guidelines 1. A maximum of nine identifiers of various kinds may be cancelled in one cancel message. Additional messages are required if more than nine identifiers are to be cancelled. Each AKA (or name spelling variation); DOB; SMTs, MNU; or SOC, etc.; is counted as one identifier. Each set of image data (multiple data element fields) is counted as one identifier.

WACIC Manual Revised 10/2010

Chapter #16-34

Chapter 16

Identity Theft File

2. Aliases; dates of birth; scars, marks, tattoos, and other characteristics; miscellaneous numbers; Social Security numbers; and caution and medical conditions to be cancelled should be set out in the cancel message in the same manner as in a supplemental record entry. That is, more than one identifier of the same type may follow the MFC without repetition of the MFC. However, character for character, each identifier to be cancelled must be set out exactly as it appears in the supplemental record on file. 3. When an Identity Theft Victim record is cancelled, its entire supplemental record is automatically cancelled.

WACIC Manual Revised 10/2010

Chapter #16-35