The following 'Involved Persons Data' relates to which victim?
VICTIM NAME - REQUIRED
Select ONE from a Pull Down menu that will contain all of the victim's names that were entered on the previous screen. When filling in the information for the various "INVOLVED PERSONS" that may be associated with this incident, keep in mind that all subsequent information - including the relationship of the involved person to the victim - relates only to the victim that is selected at the top of the screen.

Comment: It is understood, that all persons designated as 'offenders' are "alleged" to be offenders pending formal disposition of any criminal or civil charges.  If "Offender" is checked then the "Witness" field will be disabled. Also note that for incidents where cross complaints are filed, an individual may be listed as both a victim and as an alleged offender.
Special Instructions: If "Offender Name Unknown" is checked (as would be the case for a stranger rape) the DET will simply enter John Doe or Jane Doe for the NAME and the first day and month of the year the incident was reported as the BIRTH DATE. It may also be desirable to enter a tracking number as the middle name (e.g. "FY 2001-1") for multiple John or Jane Does in a fiscal year. In some cases the gender of the alleged vendor may be unknown, so a best guess system will be used to fill in the gender and the first name as either John or Jane. Again, for the 'Does' is may be a good idea to keep a paper record of any data entered.
 

New Feature: If the stranger is subsequently identified via DNA evidence, etc. then the previous 'Doe' alias as well as the correct name, gender and birth date can be entered using the "Enter Another Alias" button.

For this victim, who is the 'Involved Person' below? Check ALL that apply.
Offender  Offender Name Unknown  Household Member  Witness

Data to be hashed
FIRST NAME - REQUIRED
If possible, ask the involved person to give you their FIRST NAME as it appears on their Social Security card. After the first hashed alias is generated, the software will prompt for additional aliases, and this is when the DET records any nicknames that the victim may go by.
Comment: The FVC-APP does not record the social security number. Use of the social security number to uniquely identify an individual has the potential to compromise confidentiality and/or individual privacy. If a person was previously entered in the database and the hashed ID matches a previous entry, then the prompt for aliases/nicknames will not be enabled. Lack of a prompt for aliases lets the DET know that the individual is already entered in the database. The DET will not have any information about previous entries. The person may have been a victim, an offender and/or a household member.

MIDDLE NAME - (optional)
Enter the involved person's MIDDLE NAME. Hash aliases will be created with/without the middle name and with just the middle initial.
Special Instructions: Enter multiple middle names with a singe space between them - (no commas or underscoring).

LAST NAME - REQUIRED
Enter the involved person's LAST NAME. When the gender entered is "female" the software will prompt for "maiden name," and the maiden name will be used to generate an additional alias.
Comment: To cut down on errors, name fields are not case sensitive. e.g. McDonald will become MCDONALD.
 

RECOMMENDATION: It is possible for a person to have the same name, birth date and gender. To cut down on the potential for duplicate Hashed IDs, addition of a 'wild card' field for MOTHER'S MAIDEN NAME is desired. This field will be used to generate another alias for both males and females. This will require additional programming of the Client Identification Hashing Module (CIHM).

BIRTH DATE (mm/dd/yyyy) - REQUIRED
Enter the involved person's birth date.
Comment:  When the involved person's BIRTH DATE is entered, the age of the involved person as of the INCIDENT DATE will Auto Fill in the AGE field below.
Special Instruction: If the exact BIRTH DATE is unknown, enter any known information. If you know the person's age, but not their date of birth enter 01/01 and the approximate year of their birth. This type of data entry is discouraged as a change in the date of birth will generate a different Hashed ID. A remedy to this situation is to use the "Enter Another Alias" button to enter both the old and new information when the correct birth date is known.

GENERATION - (optional)
As indicated, use the predefined look-up table (LUT) to select the generation. The default for this field is "Not Applicable."
Comment:  Default hash aliases are created with/without the "Generation" suffix.

LUT_GENERATION

GENERATION_CODE

GENERATION

0 Not Applicable
1 JR
2 SR
3 I
4 II
5 III
6 IV

Additional Involved Person Information as of Incident Date
Comment: The Hispanic Origin and Race Codes are from the Census 2000 questionnaire.

Is this person Spanish/Hispanic/Latino?
HISPANIC ORIGIN
Is this person Spanish/Hispanic/Latino?
Use the look up table for HISPANIC ORIGIN to respond to this question.

LUT_HISPANIC ORIGIN

HISPANIC_ORIGIN_CODE

HISPANIC_ORIGIN

1 NO, not Spanish/Hispanic/Latino
2 Yes, Mexican, Mexican Am, Chicano
3 Yes, Puerto Rican
4 Yes, Cuban
5 Yes, other Spanish/Hispanic/Latino

1 White (Caucasian)
2 Black, African American, or Negro
3 American Indian or Alaska Native
4 Asian Indian
5 Chinese
6 Filipino
7 Japanese
8 Korean
9 Vietnamese
10 Other Asian
11 Native Hawaiian
12 Guamanion or Chamorro
13 Samoan
14 Other Pacific Islander
15 Other race (not listed above)

AGE
Auto Fills with the age of the involved person in years. The involved person's age is calculated as of the INCIDENT DATE when the BIRTH DATE field is populated.
Special Instruction: Data entry is required only if DOB is unknown. For victims who are children less than age 1, the age is displayed in months.

PERSON'S STATUS
Check ALL conditions below that apply for the involved person on the date of the incident. The default is unchecked = NO. A check = YES.

Disabled/Handicapped  Vulnerable Adult  Pregnant
Serious Mental Illness  Unemployed Spouse   Child less than one year old
Comment: Populations that are especially vulnerable to involvement in family violence are listed here.

RELATED
Select one from a Pull Down menu. Data entry is required if "Related" was selected in the RELATION TO VICTIM field.  Items listed are reproduced directly from Census 2000. The census "Parent-in-law" designation was expanded to read Father-in-law/mother-in-law. Two items were added to the census list to cover instances where the offender is a minor: Stepfather/stepmother and Grandfather/grandmother.

LUT_RELATED
(Relationship of the Involved Person to the Victim)

RELATED_CODE

RELATED

1 Husband/wife
2 Natural-born son/daughter
3 Adopted son/daughter
4 Stepson/stepdaughter
5 Brother/sister
6 Father/mother
7 Grandchild
8 Father-in-law/mother-in-law
9 Son-in-law/daugher-in-law
10 Stepfather/stepmother
11 Grandfather/grandmother
12 Other relative

1 Roomer, boarder
2 Housemate, roommate (friend)
3 Unmarried partner (current live-in)
4 Unmarried partner (former live-in)
5 Foster child
6 Currently dating or engaged
7 Formerly dating or engaged
8 Stranger
9 Coworker (& none of the above applies)
10 Neighbor (& none of the above applies)
11 Other non-relative

Enter Another Alias -New!
If additional information is known about an involved person subsequent to the initial data entry, use the "Enter Another Alias" button so that both the new and old information can be entered. The new information will add an additional alias to the Alias Resolution Table (ART) for that involved person.

GO TO CRIMINAL PROCEEDINGS (TAB 4)
GO TO CIVIL ACTIONS (TAB 5)
The DET goes to either TAB 4 or TAB 5 by clicking on one of these buttons. All REQUIIRED fields on TAB 3 (for at least one involved person)  must be filled in before advancing to TAB 4 or 5.
Special Instructions: There are no required fields on either TAB 4 or TAB 5. If the DET does not have any information to furnish for criminal proceedings and/or civil actions, the DET simply toggles to the SERVICES SCREEN (TAB 6).
Comment: Prior to sending the entire record to the FVC Database, the DET can toggle back and forth between the various TABS to correct errors/update information. However, once the record is sent to the database, the DET CAN NOT retrieve the record. If an organization wishes to keep track of data that is entered, the organization can ask the DET to print out any or all of the screens prior to sending the incident record to the database.