The National Violent Death Reporting System - Case abstraction

National Violent Death Reporting System
Coding Manual
Version 3

Additions for NVDRS 3.0 Software

National Center for Injury Prevention and Control
Centers for Disease Control and Prevention

2009

Produced by:
The CDC NVDRS Team

Table of Contents
Topic
Introduction
Victim Weapon and Suspect Variables
New Homicide/Suicide/Undetermined Circumstances
Intimate Partner Violence Module

Section
1
2
3

Page
1
1-1
2-1
3-1

Introduction
This document contains material to update the NVDRS Coding Manual, Version 3, with
coding guidance and reference information for new variables added to Version 3.0 of the
NVDRS software. This information is divided into three sections:
Section 1: Victim Weapon and Suspect Variables details the fields on the new “Weapon
and Suspect” panel of Victim and Victim-Suspect type persons in NVDRS incidents. This
panel replaces both the Person-Weapon Relationship and Victim-Suspect Relationship
components of prior versions of the NVDRS software.
Section 2: New Homicide/Suicide/Undetermined Circumstances details new circumstance
variables that are available for victims with all assigned types of death except unintentional
firearm injuries.
Section 3: Intimate Partner Violence Module details the variables that make up a new
optional data source for the NVDRS software, which may be used to gather data specific to
intimate partner violence. The new IPV data source is in many ways analogous to the
existing Child Fatality Review Module in the NVDRS software, in that it provides data
collectors the capability to collect additional data on a specific type of NVDRS incident.
The material in these additions will be incorporated into the main body of the NVDRS
Coding Manual at its next revision.

Section 1
Victim Weapon and Suspect Variables
Variable Label
Primary weapon that killed victim
Second weapon causing injury
Third weapon causing injury
Total number of NVDRS weapons for this victim
Primary suspect for this victim
Second suspect for this victim
Third suspect for this victim
Victim’s relationship to suspect 1
Victim’s relationship to suspect 2
Suspect was caregiver
History of abuse of victim
Total number of NVDRS suspects for this victim

Variable Name
Weapon1
Weapon2
Weapon3
TotWep
Suspect1
Suspect2
Suspect3
Rela1
Rela2
CareTk
Abuse
TotSusp

Page
1-3
1-3
1-3
1-5
1-7
1-7
1-7
1-9
1-9
1-9
1-13
1-15

Weapon and Suspect

Primary weapon that killed victim: Weapon1
Second weapon causing injury: Weapon2
Third weapon causing injury: Weapon3
Data Sources: CME/PR
NVDRS Name
Weapon1

Weapon 2
Weapon 3

Definition
The weapon responsible for causing the death of the victim, or, if
multiple weapons coded, the weapon causing the most damage to the
victim.
For victims injured by multiple weapons, the weapon causing the
second most damage to the victim.
For victims injured by multiple weapons, the weapon causing the
third most damage to the victim.

Response Options:
NVDRS Weapon Number
Uses
This variable links victims to weapons by identifying the weapon or weapons most
responsible for the death of a victim, and prioritizing them if there is more than one such
weapon.
Discussion
When possible, only weapons that caused a fatal injury to one or more victims should be
entered in NVDRS. In most incidents, it will only be necessary to designate a primary
weapon for each victim—this will be the weapon that caused the fatal injury to the victim.
In incidents where it is not possible to determine the weapon that caused the fatal injury, it is
possible to link up to three weapons to a single victim, ranking them as primary, second and
third. The abstractor will make this ranking by determining which of the weapons inflicted
the most harm to the victim. For example, if a victim was injured in the torso by shots fired
from two handguns, the handgun that resulted in the greater number of wounds to the victim
would be coded as primary.
Note that most weapon types in NVDRS are entered only once, regardless of the number of
physical weapons involved. For instance, any number of knives are coded as a single “sharp
instrument” NVDRS weapon. A victim that was stabbed by multiple knives, or bludgeoned
by multiple blunt objects, will only have a single weapon entered into the NVDRS (as the
Primary Weapon). Decisions about ranking various weapons will only need to be made in
incidents involving multiple firearms (which are entered into the system individually), or a
victim who was injured by multiple weapons of different types (firearm and sharp
instrument, for example).

1-3

Weapon and Suspect
Poisonings will require special handling for a limited time, as each poisonous substance is
currently entered into NVDRS as a separate weapon. If it is impossible to determine from
the data sources which of several poisons was responsible for a victim’s death, register any
one of the poisons entered in the incident as the primary weapon, and do not designate a
second or third weapon. A future change to the NVDRS software will consolidate all
poisons in an incident into a single NVDRS Weapon record, eliminating this situation.
Prior to 2007, abstractors were instructed to enter every weapon that caused harm to a victim
in NVDRS, even if a given weapon did not inflict a fatal wound, so there may be weapons in
older incidents that did not inflict fatal wounds on any victims. These weapons should not
be entered as primary, second or third weapon in these variables. Only code weapons
causing fatal injury to the victim.
In summary:
• If only one NVDRS weapon was responsible for the fatal injury, list it as Primary
Weapon.
• If unable to determine which of two or more NVDRS weapons was responsible for
the fatal injury, attempt to rank them based on which weapon did the most harm.
• If unable to rank weapons, pick one arbitrarily to list as Primary.
Analysis
Name

Label

Table

Type

Weapon1

Primary
weapon
that killed
victim
Second
weapon
causing
injury
Third
weapon
causing
injury

Person

Weapon2

Weapon3

Priority

Primacy

Number

Field
Length
4

LR/LR

CME/PR

Person

Number

4

LR/LR

CME/PR

Person

Number

4

LR/LR

CME/PR

SAS Variable Names by Data Source
CME
WEAPON1
WEAPON2
WEAPON3

1-4

PR
WEAPON1
WEAPON2
WEAPON3

Weapon and Suspect

Total number of NVDRS weapons for this victim: TotWep
Data Sources: CME/PR
NVDRS Name
TotWep

Definition
Total number of NVDRS weapons in this incident contributing to
fatal injury of the victim

Response Options:
Number of weapons
Uses
This variable links victims to weapons by identifying the total number of weapons that
inflicted fatal wounds on a victim.
Discussion
Enter the number of weapons in the NVDRS incident that contributed to the fatal injury of
the victim. If only a primary weapon is designated for this victim, this number will be 1. If a
primary and second weapon are designated, the number will be 2, and if primary, second and
third weapons are designated, the number will be 3. The number may be greater than 3 if
more than three weapons injured the victim, but this will only be true in rare cases.
Note that the number entered should correspond to the number of NVDRS weapon records,
which may differ from the number of physical weapons that caused injury to a victim. For
example, any number of blunt instruments in an incident are coded with a single NVDRS
“blunt instrument” weapon, so if a victim is bludgeoned by three attackers with blunt
instruments, only one NVDRS weapon record would be created, and the response to this field
would be “1.”
Examples
• A victim is shot by four attackers with handguns. The data sources do not indicate which
handgun inflicted the fatal wound. Enter 4 for TotWep.
• A man takes an overdose of prescription medication and shoots himself in the head. The
cause of death on the Death Certificate is a gunshot wound. Only the firearm should be
entered in NVDRS as a weapon, as it was responsible for the fatal injury. Enter 1 for
TotWep.

1-5

Weapon and Suspect

Analysis
Name

Label

Table

Type

TotWep

Total
number of
NVDRS
weapons
for this
victim

Person

Number

SAS Variable Names by Data Source
CME
TOTWEP

1-6

PR
TOTWEP

Field
Length
4

Priority

Primacy

LR/LR

PR/CME

Weapon and Suspect

Primary suspect for this victim: Suspect1
Second suspect for this victim: Suspect2
Third suspect for this victim: Suspect3
Data Sources: CME/PR
NVDRS Name
Suspect1
Suspect2
Suspect3

Definition
Identity of the NVDRS person designated as the primary suspect in
this victim’s death
For victims with multiple suspects, the identity of the NVDRS person
designated as the second suspect in the victim’s death
For victims with multiple suspects, the identity of the NVDRS person
designated as the third suspect in the victim’s death

Response Options:
NVDRS Person Number
Uses
This variable links victims to suspects by identifying the suspect or suspects most responsible
for the death of a victim, and prioritizing them if there is more than one such suspect.
Discussion
These variables allow the system to directly link each victim to as many as three suspects and
capture information on the relationship between them, as well as the relative importance of
each suspect in causing the death of the victim. Unlike NVDRS weapons, it is not necessary
for a suspect to inflict a fatal injury, or any injury at all on a victim. For example, if one
person drives a car and a second person fires a handgun in a drive-by shooting, both of these
persons are NVDRS suspects, and should be entered in the case. Abstractors should refer to
source documents to determine who should be entered as a suspect in any given case. See
“Entering a Case/Data Structure” for additional guidance.
If there is only one suspect for a victim, then that suspect will be the Primary Suspect, and
should be coded in Suspect1.
If there are multiple suspects for a victim, it is possible to link up to three suspects to a
victim, ranked as the primary, second and third suspects. It is not necessary for a suspect to
have personally wounded a victim to be listed here—accomplices such as drivers in drive-by
shootings can be listed, for example. Where there are multiple suspects for a given victim,
the abstractor will need to rank the suspects using the following criteria:
• If it is possible to determine which suspect inflicted the fatal injury, then that suspect
will be the Primary Suspect. Accomplices or other persons that qualify as NVDRS
suspects may be listed in the Second and Third Suspect fields.
• If it is unclear which suspect inflicted the fatal injury, then attempt to rank them based
on which suspect inflicted the greatest harm on the victim, as in the discussion on
designating a Primary Weapon.
1-7

Weapon and Suspect
•

•

•

If it is impossible to determine which suspect inflicted the greatest harm, then attempt
to rank the suspects based on the closeness of their relations to the victim as the
Primary Suspect (e.g., list a sibling ahead of a stranger).
If all victim-suspect relationships are identical (e.g., “Stranger”), attempt to rank the
suspects based on which have the most identifying or demographic information (e.g.,
list a suspect with a partial description ahead of one about which nothing is known).
If it is impossible to designate a Primary Suspect under any of these criteria, select
any one suspect to designate as Primary. This will be a rare occurance, and is not
anticipated to have a significant impact on analysis.

There are never suspects for suicide victims. There will be a suspect for an unintentional
firearm injury victim if another person was responsible for discharging the firearm, but not if
the victim was.
Examples
• In an altercation, two men attack a victim. One man holds the victim down while the
other stabs him with a knife. Both men are listed as suspects in the source documents and
charged with the death. The wielder of the knife would be the Primary Suspect, and the
accomplice would be the Second Suspect.
• A victim is attacked and killed by his brother and a friend of the brother, who was not
known to the victim. If it is not possible to determine who inflicted the fatal injury or the
most damage, the brother would be designated as Primary Suspect, and the friend as
Second Suspect.
Analysis
Name

Label

Suspect1

Primary
Person
suspect for
this victim
Second
Person
suspect for
this victim
Third
Person
suspect for
this victim

Suspect2

Suspect3

Table

SAS Variable Names by Data Source
CME
SUSPECT1
SUSPECT2
SUSPECT3

1-8

PR
SUSPECT1
SUSPECT2
SUSPECT3

Type

Priority

Primacy

Number

Field
Length
4

LR/LR

CME/PR

Number

4

LR/LR

CME/PR

Number

4

LR/LR

CME/PR

Weapon and Suspect

Victim to Suspect relation 1: S1Rela1, S2Rela1, S3Rela1
Victim to Suspect relation 2: S1Rela2, S2Rela2, S3Rela2
Data Sources: CME/PR
NVDRS Name
S1Rela1
S1Rela2
S2Rela1
S2Rela2
S3Rela1
S3Rela2

Definition
Description of relationship of the victim to the first suspect
Description of secondare relationship of the victim to the first suspect
Description of relationship of the victim to the second suspect
Description of secondary relationship of the victim to the second
suspect
Description of relationship of the victim to the third suspect
Description of secondary relationship of the victim to the third suspect

Response Options:
1
Spouse
2
Ex-spouse
3
Girlfriend or boyfriend
7
Ex-girlfriend or ex-boyfriend
8
Girlfriend or boyfriend, unspecified whether current or ex
10 Parent
11 Child
12 Sibling
13 Grandchild
14 Grandparent
15 In-law
16 Stepparent
17 Stepchild
18 Child of suspect’s boyfriend/girlfriend (e.g., child killed by mom’s boyfriend)
19 Intimate partner of suspect’s parent (e.g., teenager kills his mother’s boyfriend)
20 Foster child
21 Foster parent
29 Other family member (e.g., cousin, uncle, etc.)
30 Babysitter (e.g., child killed by babysitter)
31 Acquaintance
32 Friend
33 Roommate (not intimate partner)
34 Schoolmate
35 Current/former work relationship (e.g., co-worker, employee, employer)
36 Rival gang member
44 Other person, known to victim
45 Stranger
50 Victim was injured by law enforcement officer
51 Victim was law enforcement officer injured in the line of duty
88 Suspect is not a suspect for this victim (if entered in the Rela1 field)

1-9

Weapon and Suspect
88 All relevant information about relationship is already provided in Relation 1 (if
entered in the Rela 2 field)
99 Relationship unknown

Uses
Data describing the relationship between the victim and the suspect are useful for developing
and evaluating prevention programs and for characterizing various forms of family and
intimate violence.
Discussion
These variables will be assigned by the abstractor for each suspect designated as primary,
second or third suspect for a given victim.
• Use the following sentence as a guide for selecting the appropriate description of the
relationship: the victim is the ____________ of the suspect. For example, when a parent
kills a child, the relationship is “Child” not “Parent.” (“The victim is the child of the
suspect.”)
• Homosexual relationships should be coded in the same way as heterosexual relationships
(e.g., “Girlfriend” or “Boyfriend”). The homosexual or heterosexual nature of the
relationship will be indicated by the sex of the victim and suspect.
• The classification “babysitter” includes child care providers such as nannies or relatives
of a child other than a parent or guardian.
• For this data element, an acquaintance is someone with or about whom the victim has had
some prior interaction or knowledge. A stranger is someone with whom the victim has
had no prior interaction before the event that culminated in the violent injury.
• Where more than one offender is working in concert in an incident (as in a drive-by
shooter and his or her driver), code the victim’s relationship to each offender. Do not use
88s in the Relationship 1 field in this situation to identify the offender who did not
actually fire the weapon because all offenders working in concert are considered
offenders on the Supplementary Homicide Report and in police reports.
• If the nature of the relationship is unknown, code “Rela1” as “99”. If all relevant
information regarding the relationship is captured in “Rela1”, then code “Rela2” as 88
for: “All relevant information about relationship is already provided in Relation 1 “Not
applicable.” (88 is not a suspect for this vic)??
Examples
• Code the following scenario as “Stranger”: two individuals who do not know each other
play pool together, argue, then one stabs the other.
• Two strangers shoot a victim and three other persons help cover-up the crime by creating
an alibi for the suspects. The three persons who only helped to cover up the crime should
not be loaded in NVDRS. The other two suspects should be loaded as “stranger”.

1-10

Weapon and Suspect
Analysis
Name

Label

Table

S1Rela1

Victim to Suspect
Relation 1
Victim to Suspect
Relation 2
Victim to Suspect
Relation 1
Victim to Suspect
Relation 2
Victim to Suspect
Relation 1
Victim to Suspect
Relation 2

S1Rela2
S2Rela1
S2Rela2
S3Rela1
S3Rela2

Type

Priority

Primacy

Person

Field
Length
Number 2

LR/LR

PR/CME

Person

Number 2

LR/LR

PR/CME

Person

Number 2

LR/LR

PR/CME

Person

Number 2

LR/LR

PR/CME

Person

Number 2

LR/LR

PR/CME

Person

Number 2

LR/LR

PR/CME

SAS Variable Names by Data Source
CME
S1RELA1
S1RELA2
S2RELA1
S2RELA2
S3RELA1
S3RELA2

PR
S1RELA1
S1RELA2
S2RELA1
S2RELA2
S3RELA1
S3RELA2

1-11

Weapon and Suspect

Suspect was caregiver: S1CareTk, S2CareTk, S3CareTk
Data Sources: CME/PR
NVDRS Name
S1CareTk
S2CareTk
S3CareTk

Definition
Was this suspect a caregiver for this victim
Was this suspect a caregiver for this victim
Was this suspect a caregiver for this victim

Response Options:
0
No, Not Collected, Not Available, Unknown
1
Yes
Uses
This variable will help identify deaths resulting from intimate partner abuse, child abuse,
elder abuse, and other forms of caregiver violence.
Discussion
After indicating the relationship for each victim-suspect pair (Rela1 from previous page),
determine whether the offender was a caregiver for the victim. This variable is included
because some definitions of child abuse and elder abuse are based solely on whether the
offender was the victim’s caregiver.
Examples
• a parent who kills his or her child.
• a babysitter who kills his or her charge.
• a nursing home attendant who kills a patient.
• an adult who kills a dependent elderly parent.
Analysis
Name

Label

Table

Type

S1CareTk

Suspect was
caregiver
Suspect was
caregiver
Suspect was
caregiver

Person

S1CareTk
S1CareTk

Priority

Primacy

Checkbox

Field
Length
1

LR/LR

CME/PR

Person

Checkbox

1

LR/LR

CME/PR

Person

Checkbox

1

LR/LR

CME/PR

SAS Variable Names by Data Source
CME
S1CARETK
S2CARETK
S3CARETK
1-12

PR
S1CARETK
S2CARETK
S3CARETK

Weapon and Suspect

History of abuse of victim: S1Abuse, S2Abuse, S3Abuse
Data Sources: CME/PR
NVDRS Name
S1Abuse
S2Abuse
S3Abuse

Definition
History of abuse of victim by this suspect
History of abuse of victim by this suspect
History of abuse of victim by this suspect

Response Options:
0
No, Not Collected, Not Available, Unknown
1
Yes
Uses
These variables will help identify deaths resulting from intimate partner abuse, child abuse,
elder abuse, and other forms of caretaker violence.
Discussion
For each victim-suspect pair in which (1) the offender was a caretaker of the victim or (2) the
offender was a current or ex-intimate partner, indicate whether the data sources document a
history (or suspected history) of abuse of this victim by the suspect.
• The evidence of ongoing abuse may be suspected but not confirmed.
• Abuse can be physical, psychological, sexual or others as long as the source document
refers to ‘abuse’.
Examples
Yes
• Stepparent killed child during an altercation. Family investigated by Child Protective
Services last year.
• Autopsy evidence reported as an indication of previous abuse is enough to endorse the
“Abuse” variable.
No
• Husband shot wife after learning that she was having an affair. No history of previous
police visits to the residence or restraining orders; neighbors indicate no previous
problems.

1-13

Weapon and Suspect

Analysis
Name

Label

Table

Type

S1Abuse

History of
abuse of
victim
History of
abuse of
victim
History of
abuse of
victim

Person

S2Abuse

S3Abuse

Priority

Primacy

Checkbox

Field
Length
1

LR/LR

PR/CME

Person

Checkbox

1

LR/LR

PR/CME

Person

Checkbox

1

LR/LR

PR/CME

SAS Variable Names by Data Source
CME
S1ABUSE
S2ABUSE
S3ABUSE

1-14

PR
S1ABUSE
S2ABUSE
S3ABUSE

Weapon and Suspect

Total number of NVDRS suspects for this victim: TotSusp
Data Sources: CME/PR
NVDRS Name
TotSusp

Definition
Total number of NVDRS persons in the incident who are suspects in
the death of this victim.

Response Options:
Number of NVDRS Suspects
Uses
This variable links victims to suspects by identifying the total number of suspects that are
associated with the death of a victim.
Discussion
Enter the number of suspects (or victim/suspects) in the NVDRS incident that contributed to
the death of the victim. If only a primary suspect is designated for this victim, this number
will be 1. If a primary and second suspect are designated, the number will be 2, and if
primary, second and third suspects are designated, the number will be 3. The number may be
greater than 3 if more than three suspects are involved in the death, but this will only be true
in rare cases.
Examples
• A victim is killed in a drive-by shooting. The car used in the shooting was driven by one
man and the shooter rode in the front passenger seat. Enter 2 for TotSusp.
• A victim is amushed and beaten to death by six rival gang members. Enter 6 for
TotSusp.
Analysis
Name

Label

Table

Type

TotSusp

Total
number of
NVDRS
suspects
for this
victim

Person

Number

Field
Length
4

Priority

Primacy

LR/LR

PR/CME

SAS Variable Names by Data Source
CME
TOTSUSP

PR
TOTSUSP

1-15

Section 2
New Homicide/Suicide/Undetermined
Circumstances
Variable Label
Other addiction
Family stressors
Anniversay of a traumatic event
History of abuse as a child
Eviction/loss of home
Mentally ill suspect
Random violence
Drive-by shooting

Variable Name

Page

OtherAddict
FamStress
TraumaAnniv
AbuseAsChild
Eviction
SusMental
Random
Driveby

2-3
2-4
2-5
2-6
2-7
2-8
2-9
2-11

New Circumstances

Other addiction: OtherAddict
Data Sources: CME/PR
NVDRS Name
OtherAddict

Definition
Person has an addiction other than alcohol or other substance abuse,
such as gambling, sexual, etc.

Response Options:
0
No, Not Available, Unknown
1
Yes
Uses
Can be used to assess the proportion of suicide victims who were identified as having an
addiction not related to substance abuse. The information can be helpful in exploring the role
of these addictions in planning suicide prevention service delivery.
Discussion
Code a victim as “Yes” for “OtherAddict” if the victim was perceived by self or others to
have an addiction not related to substance abuse, and there is some indication that this
addiction may have contributed to the suicide. Such addictions might include gambling or
sexual addictions. The incident narrative should describe the nature of the addiction.
Examples
Yes
• The victim was participating in a rehabilitation program or undergoing therapy for
compulsive gambling.
No
• The victim was noted to travel to casinos and gamble several times a year. No indication
that this behavior was a problem in the victim’s life.
Analysis
Name

Label

OtherAddict Other addiction

Table

Type

Person

Checkbox

Field
Length
1

Priority

Primacy

LR/LR

CME/PR

SAS Variable Names by Data Source
CME
OTHERADDICT

PR
OTHERADDICT

2-3

New Circumstances

Family stressors: FamStress
Data Sources: CME/PR
NVDRS Name
FamStress

Definition
Family stressors appear to have contributed to the suicide

Response Options:
0
No, Not Available, Unknown
1
Yes
Uses
This variable identifies suicides that are related to stresses within the family. Identifying
specific circumstances that appear to play a precipitating role in suicide will help to identify,
develop, and evaluate preventive interventions.
Discussion
Code “FamStress” as “Yes” if at the time of the incident the victim was experiencing
significant problems related to family members or the family home environment. Describe
the nature of these problems in the narrative.
Examples

Analysis
Name

Label

FamStress Family Stressors

Table

Type

Person

Checkbox

SAS Variable Names by Data Source
CME
FAMSTRESS

2-4

PR
FAMSTRESS

Field
Length
1

Priority

Primacy

LR/LR

CME/PR

New Circumstances

Anniversary of a traumatic event: TraumaAnniv
Data Sources: CME/PR
NVDRS Name
TraumaAnniv

Definition
Suicide occurred on or near the anniversary of a traumatic event in
the victim’s life

Response Options:
0
No, Not Available, Unknown
1
Yes
Uses
This variable identifies suicides that may be related to the anniversary of a traumatic
experience in the victim’s life, such as the death of a relative or friend. Identifying specific
circumstances that appear to play a precipitating role in suicide will help to identify, develop,
and evaluate preventive interventions.
Discussion
Code “TraumaAnniv” as “Yes” if at the incident occurred on or near the date of a traumatic
event in the victim’s life, regardless of how far in the past the event was. Indicate the nature
of the event in the incident narrative.
Examples
Yes
• The victim committed suicide ten years to the day after the suicide of her mother.
• The victim survived a plane crash four years ago and committed suicide the evening
before the anniversary.
No
• The victim committed suicide on September 11, 2008, but there is no indication that the
victim was traumatized by the terror attacks of September 11, 2001, or connected with
any of the victims.
Analysis
Name

Label

TraumaAnniv Anniversary of a
traumatic event

Table

Type

Person

Checkbox

Field
Length
1

Priority

Primacy

LR/LR

CME/PR

SAS Variable Names by Data Source
CME
TRAUMAANNIV

PR
TRAUMAANNIV

2-5

New Circumstances

History of abuse as a child: AbuseAsChild
Data Sources: CFR/CME/PR
NVDRS Name
AbuseAsChild

Definition
The victim had a history of abuse (physical, mental or emotional) as a
child

Response Options:
0
No, Not Available, Unknown
1
Yes
Uses
This variable identifies suicides victims that were victims of abuse as children, whether they
are adults or children at the time of the incident, and regardless of whether the abuse is
ongoing or in the past. Identifying specific circumstances that appear to play a precipitating
role in suicide will help to identify, develop, and evaluate preventive interventions.
Discussion
Code “AbuseAsChild” as “Yes” if at the victim had been the victim of child abuse at any
point in the past. The victim may be a child or an adult at the time of the incident, and the
abuse may be ongoing or in the past. Abuse may be physical, psychological or emotional.
Indicate the nature of the abuse in the incident narrative.
Examples
Yes
• Victim had been sexually molested by an older relative twenty years earlier.
• Victim had been placed in foster care by the state due to physical abuse.
Analysis
Name

Label

AbuseAsChild History of
abuse as a child

Table

Type

Person

Checkbox

SAS Variable Names by Data Source
CME
ABUSEASCHILD

2-6

PR
ABUSEASCHILD

Field
Length
1

Priority

Primacy

LR/LR

CME/PR

New Circumstances

Eviction/loss of home: Eviction
Data Sources: CME/PR
NVDRS Name
Eviction

Definition
A recent eviction or other loss of the victim’s home, or the threat of
it, appears to have contributed to the suicide

Response Options:
0
No, Not Available, Unknown
1
Yes
Uses
This variable identifies suicides that are related to loss of housing. Identifying specific
circumstances that appear to play a precipitating role in suicide will help to identify, develop,
and evaluate preventive interventions.
Discussion
Code “Eviction” as “Yes” if at the time of the incident the victim had recently been, was in
the process of being evicted or foreclosed on, or was confronted with an eviction,
foreclosure, or other loss of housing. Describe the situation in the incident narrative.
Examples
Yes
• The victim’s mortgage was in arrears and the lender was threatening foreclosure.
• The victim had been thrown out of his parents’ house, where he had been living since
dropping out of school one year earlier.
• The victim and his wife were arguing about money problems.
No
• The victim had been homeless for two years and sought refuge in shelters when the
weather was especially cold.
Analysis
Name

Label

Table

Type

Eviction

Eviction/loss of
home

Person

Checkbox

Field
Length
1

Priority

Primacy

LR/LR

CME/PR

SAS Variable Names by Data Source
CME
EVICTION

PR
EVICTION

2-7

New Circumstances

Mentally ill suspect: SusMental
Data Sources: CME/PR
NVDRS Name
SusMental

Definition
The suspect’s attack on the victim is believed to be the direct result of
a mental illness

Response Options:
0
No, Not Available, Unknown
1
Yes
Uses
This data element characterizes the precipitants of violent deaths and help to identify trends
in subtypes of violence over time. It will aid in planning and evaluating prevention programs
targeted at specific subtypes of violence.
Discussion
Code “SusMental” as “Yes” if the suspect’s attack on the victim is believed to be the direct
result of the suspect’s mental illness..
Examples
Yes
• A suspect attacks a woman on the street and claims that an angel told him the woman was
one of Satan’s minions
Analysis
Name

Label

SusMental Mentally ill
suspect

Table

Type

Person

Checkbox

SAS Variable Names by Data Source
CME
SUSMENTAL

2-8

PR
SUSMENTAL

Field
Length
1

Priority

Primacy

LR/LR

CME/PR

New Circumstances

Random violence: Random
Data Sources: CFR/CME/PR
NVDRS Name
Random

Definition
The victim was killed by a random act of violence

Response Options:
0
No, Not Available, Unknown
1
Yes
Uses
This data element characterizes the precipitants of violent deaths and help to identify trends
in subtypes of violence over time. It will aid in planning and evaluating prevention programs
targeted at specific subtypes of violence.
Discussion
Code “Random” as “Yes” if the victim was killed by a random act of violence. A random act
is one in which the suspect is not concerned with who is being harmed, just that someone is
being harmed, such as a person who shoots randomly at passing cars from a highway bridge
or opens fire in a crowded shopping mall.
This code should not be used for unsolved homicides.
It should also not be used for cases in which the overall target was chosen intentionally (such
as a white supremacist group opening fire in a daycare center that serves children of color, or
a suspect returning to the job from which he was recently fired and kills several people; while
the actual individuals may have been selected at random, the place was intentionally
targeted).
Examples
Yes
• The suspect intentionally drives his car into a crowded bus stop. There is no indication
that he was deliberately targeting any group as victims.
No
• A victim is found shot to death behind a store. There was no evidence of robbery and no
suspects were identified.
Analysis
Name

Label

Table

Type

Random

Random violence

Person

Checkbox

Field
Length
1

Priority

Primacy

LR/LR

CME/PR

2-9

New Circumstances

SAS Variable Names by Data Source
CME
RANDOM

2-10

PR
RANDOM

New Circumstances

Drive-by shooting: Driveby
Data Sources: CME/PR
NVDRS Name
Driveby

Definition
Suspect was the victim of a drive-by shooting

Response Options:
0
No, Not Available, Unknown
1
Yes
Uses
This data element characterizes the precipitants of violent deaths and help to identify trends
in subtypes of violence over time. It will aid in planning and evaluating prevention programs
targeted at specific subtypes of violence.
Discussion
A drive-by shooting is one in which the suspect or group of suspects drives near an intended
victim or target and shoots while driving, or uses a car to approach and flee the scene of a
homicide, but steps out of the car just long enough to use a weapon.
• Code “Drive-by” even if the actual victim was a bystander and not the intended
victim.
• Drive-by is the mechanism by which the victim was shot; also choose a precipitating
circumstance code to document why the drive-by occurred, if known.
Drive-by shootings must involve a motorized vehicle (e.g., car, motorcycle, truck) and does
not include modes of transportation like bicycles, skateboards, etc.
Examples
Yes
• The victim was asleep in bed and killed by bullets fired by a suspect in a car, who had
intended to shoot out the windows of the house.
No
• The suspects kidnapped the victim in a van and later killed the victim in a house.
Analysis
Name

Label

Table

Type

Driveby

Drive-by shooting

Person

Checkbox

Field
Length
1

Priority

Primacy

LR/LR

CME/PR

SAS Variable Names by Data Source
CME
DRIVEBY

PR
DRIVEBY

2-11

Section 3
Intimate Partner Violence Module
Variable Label
IPV Incident Type
IPV Victim
IPV Perpetrator
Death Certificate
Coroner/Medical Examiner Report
Police Report
SHR or NIBRS Data
Crime Lab Report
Gun Trace Report
Hospital/ED Report
Court or Prosecutor Records
Restraining Order Records
Criminal History Database
DVTRT Report
Newspaper Reports
Other data sources
Evidence of premeditation
Homicide during argument
During child drop-off/pick-up
Warrant issued for suspect
Suspect arrested in this incident
Suspect arrested but fled
Suspect charged as perpetrator
Suspect convicted
Suspect convicted of original charge
Suspect died following incident
Cohabitation status
Relationship length number of units
Unit of time used in relationship length
Breakup or breakup in progress
Breakup length number of units
Unit of time used in breakup length
Children under 18 living at home
Any children not offspring of IPV Perpetrator
Any children not offspring of IPV Victim
Number of children exposed to homicide

Variable Name
IncidType
IPVVict
IPVPerp
Sourc_DC
Sourc_ME
Sourc_PR
Sourc_SHR
Sourc_Lab
Souc_Gun
Sourc_ER
Sourc_DA
Sourc_RO
Sourc_CH
Sourc_DV
Sourc_News
Sourc_Other
Premed
MidstArg
ChildDrop
SWarrant
SArrest
SFled
SusChgP
SConvict
SOriginalP
SDied
Cohabit
RelLegth
RelUnits
RelBrkup
BrkupLgth
BrkupUnit
ChildHome
ChildP
ChildV
ChildSaw

Page
3-4
3-6
3-6
3-8
3-8
3-8
3-8
3-8
3-8
3-8
3-8
3-8
3-8
3-8
3-8
3-8
3-11
3-12
3-14
3-15
3-15
3-15
3-15
3-15
3-15
3-15
3-18
3-19
3-19
3-21
3-21
3-21
3-23
3-23
3-23
3-25

Use of child as shield during event
Child intervened during incident
Restraining order ever
Restraining order at time of incident
Restraining order type
Restraining order issue date
Restraining order served
Persons protected by restraining order
Prior arrest(s)
Type of arrest(s)
Type if other
Prior conviction(s)
Type of conviction(s)
Type if other
Prior IPV arrest(s)
Physical illness
Diagnosis of physical illness
Disability
Disability was physical
Disability was developmental
Disability was sensory
Alcohol use suspected
Drug use suspected
Mental health problem
Mental health diagnosis 1
Mental health diagnosis 2
Mental health diagnosis 3
Other mental health diagnosis
Currently in treatment for mental health problem
Ever treated for mental health problem
Alcohol problem
Other substance abuse problem
Disclosed intent to commit suicide
History of suicide attempts

ChildShield
ChildInterv
RestrainEver
RestrainNow
RestrainType
RestrainDate
RestrainServ
RestrainProt
PArrest
ArrestType
ArrestTypeMemo
PConvict
ConvType
ConvTypeMemo
IPVArr
IPVIllness
IPVIllTxt
IPVDisable
IPVDisPhy
IPVDisDev
IPVDisSens
Intox
IllDrug
IMental
IMDiag1
IMDiag2
IMDiag3
IMenTxt
ITxMen
IHistMental
IAlcoh
ISubst
ISuiInt
ISuicAtt

3-25
3-25
3-27
3-27
3-27
3-27
3-27
3-27
3-30
3-30
3-30
3-30
3-30
3-30
3-33
3-34
3-34
3-34
3-34
3-34
3-34
3-37
3-37
3-39
3-41
3-41
3-41
3-41
3-43
3-43
3-45
3-45
3-47
3-49

IPV Module

IPV Module Background
This IPV Data Module allows states to capture additional information on homicide incidents
classified as intimate partner violence (IPV) incidents. IPV incidents are defined as incidents
in which violence, or the threat of violence, by a person against his or her current or former
intimate partner results in the violent death of one or more people. This may involve cases in
which there is a death of a third party that is directly linked to the intimate partner (IP)
relationship (e.g., the child of the intimate partner, friend of the victim, a bystander).
An intimate partner is defined as a current or former girlfriend/boyfriend, date, or spouse.
This definition includes same-sex partners. The definition of intimate partner includes first
dates. It will be apparent in the Victim-Suspect Relationship variable whether the victim and
suspect were intimate partners or not.

3-3

IPV Module

IPV Incident Type: IncidType
Data Sources: IPV
NVDRS Name
IncidType

Definition
Type of IPV homicide incident

Response Options:
1
Type 1: IPV
2
Type 2: IPV-Related
3
Type 3: IP-Associated
Uses
Used to identify the type of IPV incident associated with the violent death. The information
collected will be helpful in determining the prevalence of different types of IPV incidents
related to homicides.
Discussion
The Incident Type (IncidType) should be determined using police reports or other available
information on the relationship history of the intimate partners. The IPV module is designed
to collect information on intimate partners and the circumstances that contributed to the
violent death. The following categories should be used for coding the incident type:
Type1: IPV: Incidents in which an individual is killed by a current or former intimate partner.
Case Examples
• A woman’s ex-boyfriend walks up to the woman and shoots her on the street.
• A man and woman are out on their first date. They go back to her apartment after the date.
The man tries to force the women into bed and strangles her to death.
• A woman and her lawyer are getting into a car; the woman’s ex-boyfriend walks up to the
woman and shoots her and the lawyer.
Type 2: IPV-Related: Incidents that involve a third party (either as NVDRS victim or
NVDRS suspect) but where the homicide is directly related to violence in the intimate
relationship. For Type 2 incidents, information should be included on the intimate partners
not on the third party involved.
Case Examples
• A woman kills her ex-husband's new wife. The suspect has a history of previously
threatening her ex-husband.
• A man confronted, then killed, another man he believed was having an affair with his
girlfriend. The suspect had a history of physically assaulting his girlfriend and had told her
on multiple occasions that he would kill her if she was ever with anybody else.
• A husband shoots and kills his child while attempting to attack his wife during an argument.

3-4

IPV Module
Type 3: IP-Associated: Incidents that involve a third party (either as NVDRS victim or
NVDRS offender) and that are directly related to an intimate partner relationship, but have
no evidence of violence in the intimate partner relationship. The homicide can be committed
by or against any of the third parties involved but must involve at least one of the intimate
partners as the victim or the suspect. To further clarify, the incident should be included as an
intimate partner-associated death if it does not meet the criteria for Type I or Type II IPV
incidents AND the homicide would not have occurred in the absence of the intimate partner
relationship.
Case Examples
• A man sees another man flirting with his wife in a bar; the two men argue and one stabs the
other to death. No evidence of previous violence or threats between the man and wife.
• A grandmother is murdered by her teenage granddaughter and her granddaughter’s lover
because the grandmother was trying to keep the two young women apart.
• A man shot his landlord to death. In his confession, the suspect stated that the landlord
habitually touched or made sexual comments about his (the suspect’s) wife and that he got
tired of it.

Analysis
Name

Label

IncidType

IPV Incident type

Table
Person

Priority
Field
Length
Number
2
O

Type

Primacy
IPV

SAS Variable Names by Data Source
IPV
INCIDTYPE

3-5

IPV Module

IPV Victim: IPVVict
IPV Perpetrator: IPVPerp
Data Sources: IPV
NVDRS Name
IPVVict
IPVPerp

Response Options:
999999999

Definition
Identification of whether the IPV Victim is the NVDRS Suspect,
Victim, or neither
Identification of whether the IPV Perpetrator is the NVDRS
Suspect, Victim, or neither

Unknown

Uses
Used to identify the roles of the IPV Victim and IPV Perpetrator in the homicide incident.
Discussion
For this module, the terms IPV Victim and IPV Perpetrator are used to identify persons on
whom information is collected as opposed to victim and suspect as are used in the general
NVDRS. These elements identify the role that the IPV Victim and IPV Perpetrator had in the
homicide incident. The definitions for IPV Victim and IPV Perpetrator terms are as follows:
The IPV Victim (IPVVict) is the partner in the intimate relationship who is the target of
violence perpetrated by his/her intimate partner. This person may be the victim, suspect, or
neither in the NVDRS. Intimate partners who are not directly involved in the violent incident
(e.g., they are targets of violence but are not killed during the incident) should be coded as
“other.” In cases of mutually combative violence where the target of the violence cannot be
determined, the IPV victim should be listed as the partner who was killed. Coders should list
the NVDRS identification number for the individual listed as the IPV Victim.
The IPV Perpetrator (IPVPerp) is the partner in the intimate relationship who has committed
violence against his/her intimate partner. This person may be the victim, suspect, or neither
in the NVDRS. Coders should list the NVDRS person identification number for the
individual listed as the IPV Perpetrator.
Case Examples
Analysis
Name

Label

IPVVict
IPV Perp

IPV Victim
IPV Perpetrator

3-6

Table
Person
Person

Priority
Field
Length
Number
2
O
Number
2
O

Type

Primacy
IPV
IPV

IPV Module

SAS Variable Names by Data Source
IPV
IPVVICT
IPVPERP

3-7

IPV Module

Death Certificate: Sourc_DC
Coroner/Medical Examiner Report: Sourc_ME
Police Report: Sourc_Pol
SHR or NIBRS Data: Sourc_SHR
Crime Lab Report: Sourc_Lab
Gun Trace Report: Sourc_Gun
Hospital/ED Report: Sourc_ER
Court or Prosecutor Records: Sourc_DA
Restraining Order Records: Sourc_RO
Criminal History Database: Sourc_CH
DVTRT Report: Sourc_DV
Newspaper Reports: Sourc_News
Other Data Sources: Sourc_Other
Data Sources: IPV
NVDRS Name
Sourc_DC
Sourc_ME
Sourc_Pol
Sourc_SHR
Sourc_Lab
Sourc_Gun
Sourc_ER
Sourc_DA
Sourc_RO
Sourc_CH
Sourc_DV
Sourc_News
Sourc_Othr

Definition
Death certificate used as a data source to complete module
Medical examiner used as a data source to complete module
Police report used as a data source to complete module
SHR or NIBRS data used as a data source to complete module
Crime laboratory data used as a data source to complete module
Gun trace data used as a data source to complete module
Hospital data used as a data source to complete module
Court or prosecutor records used as a data source to complete
module
Restraining order data used as a data source to complete module
Criminal history records data used as a data source to complete
module
Domestic Violence Fatality Review Team data used as a data
source to complete module
Newspapers used as a data source to complete module
Other source used as a data source to complete module

Response Options:
0
Data source used
1
Data source not used
Uses
These variables indicate the various data sources used by the data abstractor in completing
the IPV data module for the incident. Abstractors are able to call on a wide array of
resources in assembling information for the IPV module. This stands in contrast to many
NVDRS variables, which are linked to a single, specific, data source.

3-8

IPV Module
Discussion
Select all of the data sources used by the coder to complete the IPV data module. The
following should be coded as “data source used” if the sources were used the complete the
module: Sourc_DC (death certificate); Sourc_ME (medical examiner, coroner report, or
toxicology report); Sourc_Pol (police report); Sourc_SHR (data from the FBI’s
Supplementary Homicide Reports or National Incident Based Reporting Reports); Sourc_Lab
(crime laboratory reports); Sourc_Gun (gun trace data); Sourc_ER (Hospital records
including hospital discharge and emergency department records); Sourc_DA (prosecution or
court records); Sourc_RO (national or state restraining order databases); Sourc_CH (national
or state criminal history databases); Sour_DVFRT (Domestic Violence Fatality Review
Team report); Sourc_News (newspaper article or other print media source); and Sourc_Othr
(specify any other sources used).

Analysis
Name
Sourc_DC
Sourc_ME

Label

Death Certificate
Coroner/Medical
Examiner Report
Sourc_Pol
Police Report
Sourc_SHR SHR or NIBRS Data
Sourc_Lab
Crime Lab Report
Sourc_Gun Gun Trace Report
Sourc_ER
Hospital/ED Report
Sourc_DA
Court of Prosecutor
Records
Sourc_RO
Restraining Order
Records
Sourc_CH
Criminal History
Database
Sourc_DV
DVTRT Report
Sourc_News Newspaper Reports
Sourc_Othr Other data sources

Person
Person

Priority
Field
Length
Checkbox
1
O
Checkbox
1
O

Person
Person
Person
Person
Person
Person

Checkbox
Checkbox
Checkbox
Checkbox
Checkbox
Checkbox

1
1
1
1
1
1

O
O
O
O
O
O

IPV
IPV
IPV
IPV
IPV
IPV

Person

Checkbox

1

O

IPV

Person

Checkbox

1

O

IPV

Person
Person
Person

Checkbox
Checkbox
Checkbox

1
1
1

O
O
O

IPV
IPV
IPV

Table

Type

Primacy
IPV
IPV

3-9

IPV Module

SAS Variable Names by Data Source
IPV
SOURCDC
SOURCME
SOURCPOL
SOURCSHR
SOURCLAB
SOURCER
SOURCDA
SOURCRO
SOURCCH
SOURCDV
SOURCNEWS
SOURCOTHR

3-10

IPV Module

Evidence of Premeditation: Premed
Data Sources: IPV
NVDRS Name
Premed

Definition
Homicide appears to have involved premeditation or advance
planning

Response Options:
0 No
1 Yes
9 Unknown
Uses
Some homicides appear to have involved premeditation or advance planning whereas others
are more impulsive and erupt spontaneously in the midst of an argument. Because prevention
strategies aimed at planned versus unplanned homicides may differ, this variable helps
differentiate the two groups.
Discussion
Evidence of premeditation includes signs such as the suspect’s lying in wait for the victim(s)
or taking precautions before the incident to avoid discovery. Most state laws differentiate
levels of homicide, with homicide in the first degree, involving premeditation or malice
aforethought, and other homicide charges (homicide in the second degree, voluntary
manslaughter) showing no evidence of premeditation.
Case Examples
Yes
• Suspect arrived at the victim’s house with two handguns and extra clips.
• Suspect was waiting outside the victim’s workplace; when she arrived, he shot her.
• Suspect was aware of when her husband was meeting with his lawyer; she arrived at the
office and shot both.
• Suspect was charged with first degree murder.
Analysis
Name

Label

Premed

Evidence of
premeditation

Table
Person

Priority
Field
Length
Number
1
O

Type

Primacy
IPV

SAS Variable Names by Data Source
IPV
PREMED

3-11

IPV Module

Homicide during argument: MidstArg
Data Sources: IPV
NVDRS Name
MidstArg

Definition
Homicide occurred in the midst of an argument or altercation

Response Options:
0 No
1 Yes
9 Unknown
Uses
Some homicides appear to have involved advance planning whereas others are more
impulsive and erupt spontaneously in the midst of an argument or altercation. This variable
helps differentiate the two groups by identifying homicides that may be spontaneous rather
than planned.
Discussion
It is difficult to ascertain whether a homicide was impulsive; this variable instead captures
objective information about whether a verbal altercation of some sort immediately preceded
the homicide. Although some of these cases may also involve advance planning (e.g., suspect
lies in wait for the victim armed with a weapon and intending to kill him; upon seeing him,
they argue, she produces the weapon and shoots him), the variable is likely to serve as a
rough proxy for more impulsive homicides (see also “Planned” on the previous page). This
information will frequently be unknown. Legally, differentiating homicides involving
premeditation versus those occurring in the “heat of passion” is a major point as this
distinction, in part, informs whether the suspect is charged with homicide in the first degree,
homicide in the second degree, or manslaughter.
Case Examples
Yes
• Husband and wife had been drinking during a party; after the guests left, they began
arguing and wife stabbed husband.
• Victim told suspect that she wanted him out of the apartment; he became angry and beat her
to death.
No
• Victim and sister were sitting in the moving van when victim’s husband pulled alongside
the vehicle and shot her.
• Suspect shot the victim while she was sleeping and then shot himself.

3-12

IPV Module

Analysis
Name

Label

MidstArg

Homicide during
argument

Table
Person

Priority
Field
Length
Number
1
O

Type

Primacy
IPV

SAS Variable Names by Data Source
IPV
MIDSTARG

3-13

IPV Module

During child drop-off/pick-up: ChildDrop
Data Sources: IPV
NVDRS Name
ChildDrop

Definition
Homicide occurred during drop-off or pick-up of children

Response Options:
0 No
1 Yes
9 Unknown
Uses
Relationship breakups can be a trigger for homicide. For couples with children in common
who share custody or have visitation rights, the periods during which one partner drops off or
picks up the children from the other partner can provide opportunities for violence. This
variable identifies homicides that occur during such exchanges.
Discussion
This variable refers to those periods of overlap when one partner is picking up or dropping
off children to or from the other partner or a court-supervised visit.
Analysis
Name

Label

ChildDrop During child pickup/drop-off

Table
Person

SAS Variable Names by Data Source
IPV
CHILDDROP

3-14

Priority
Field
Length
Number
1
O

Type

Primacy
IPV

IPV Module

Warrant issued for suspect: SWarrant
Suspect arrested in this incident: SArrest
Suspect arrested but fled: SFled
Suspect charged as perpetrator: SusChgP
Suspect convicted: SConvict
Suspect convicted of original charge: SOriginalP
Suspect died following incident: SDied
Data Sources: IPV
NVDRS Name
SWarrant
SArrest
SFled
SusChgP
SConvict
SOriginalP
SDied

Definition
Warrant issued for the suspect in this incident
Suspect arrested in this incident
Suspect arrested but fled while on bond or escaped custody
Suspect charged in this incident
Suspect convicted in this incident
Suspect convicted of the original charge
Suspect died following the incident

Response Options:
SWarrant
SArrest
SFled
SOriginal
0 No
1 Yes
7 Not collected in data sources
8 Not applicable
9 Unknown
SusChg
SusPros
SConvict
0 No
1 Yes
3 Pending/In progress
7 Not collected in data sources
8 Not applicable
9 Unknown
SDied
0 No
1 Yes
9 Unknown
Uses

3-15

IPV Module
Information regarding the outcome for suspects in a homicide (i.e., whether they were
arrested, charged, prosecuted, convicted, or subsequent death) is helpful for evaluating law
enforcement and criminal justice system response to violent deaths.
Discussion
These variables originated with the Child Fatality Review module. Code variables with
reference to the the intimate partner who was arrested, charged, prosecuted, etc. as a suspect
for the death). Arrests or prosecution on lesser charges only, such as possession of a firearm
without a license, should not trigger endorsing these variables. If the individual died
following the incident then the other information does not have to be completed.
Warrant issued (SWarrant)—“SWarrant” indicates that a warrant was issued for the arrest of
the suspect in the incident. Code SWarrant as “yes” if a warrant for the suspect’s arrest has
been issued.
Suspect arrested (SArrest)—“SArrest” indicates that the suspect was arrested by law
enforcement. If a suspect is arrested, the arrest record will indicate the criminal statutes the
person is suspected of having violated (e.g., first-degree homicide, second-degree homicide,
etc.). If the suspect has not been arrested, or if the arrest charges do not include perpetration
of the victim’s death, code “SArrest” as “no.” Also code SArrest as “no” if a warrant for the
suspect’s arrest has been issued but the arrest has not yet been made.
Suspect fled (SFled)—“SFled” indicates that the suspect was arrested by law enforcement as
a suspected perpetrator in the victim’s death; however, the suspect fled while on bond or
escaped from custody prior to any closure to the case.
Suspect charged by prosecutor (SusChg)—“SusChg” indicates that a prosecutor such as the
district attorney or federal prosecutor has issued charges against the suspect. These charges
are not to be confused with the initial charges on which law enforcement arrested a suspect.
Rather, they refer to the charges filed by the prosecutor that initiated the prosecution process.
If the records reflect that the suspect is being prosecuted, code “SusChg” as “yes.” Reasons
to endorse “no” include that the case was never presented to prosecutors, the suspect was
administratively released by police prior to charging (which means that the police no longer
consider the person a suspect and s/he can be dropped as a suspect from the incident), or the
prosecutor did not issue charges (because of lack of evidence, witness difficulties, defendant
granted immunity, jurisdictional problem, constitutional defects, or physical evidence
difficulty).
Prosecution of suspect is complete (SusPros)—Examples of completed prosecutions include
cases in which the IPV Victim or Perpetrator suspect pleaded guilty, the prosecutor dropped
the charges, the court convicted or acquitted or dismissed the suspect, or the IPV Perpetrator
or Victim suspect died. If a conviction is entered at the trial court, code the prosecution as
complete even if the suspect has filed an appeal. Code the prosecution as incomplete if the
case has not yet gone to trial or the trial is still underway or if the suspect fled or if the IPV
Perpetrator or Victim suspect and prosecutors are still negotiating the terms of a plea to a
lesser charge.

3-16

IPV Module

Suspect was convicted (SConvict)—If prosecution is complete, “SConvict” indicates whether
the IPV Victim or Perpetrator suspect was convicted as a perpetrator in the victim’s death.
Code “no” if the IPV Perpetrator or Victim was acquitted or the case was dismissed. Also
code “no” if the IPV Perpetrator or Victim was convicted only of lesser charges (e.g., a
weapons charge) but not as a perpetrator in the victim’s death (e.g., convicted of homicide,
murder, or manslaughter). Assume the IPV Perpetrator or Victim has been convicted if
she/he has been sentenced or is awaiting sentencing.
Suspect convicted of original charge (SOriginal)—If the IPV Victim or Perpetrator suspect
was convicted of a lesser charge and not the original charge (e.g., charged with first degree
murder but convicted of second degree), code SOriginal as “no.”
Suspect died during legal proceedings (SDied)—If the IPV Victim or Perpetrator suspect
died at any time during the legal proceedings.
Analysis
Name

Label

SWarrant

Warrant issued for
suspect
SArrest
Suspect arrested in
this incident
SFled
Suspect arrested but
fled
SusChgP
Suspect charged as
perpetrator
SConvict
Suspect convicted
SOriginalP Suspect convicted of
original charge
SDied
Suspect died
following incident

Table

Type

Person

Field
Priority
Length
Number
1
O

Primacy

Person

Number

1

O

IPV

Person

Number

1

O

IPV

Person

Number

1

O

IPV

Person
Person

Number
Number

1
1

O
O

IPV
IPV

Person

Number

1

O

IPV

IPV

SAS Variable Names by Data Source
IPV
SWARRANT
SARREST
SFLED
SUSCHGP
SCONVICT
SORIGINALP
SDIED

3-17

IPV Module

Cohabitation Status: Cohabit
Data Sources: IPV
NVDRS Name
Cohabit

Definition
Cohabitation status of the IPV Perpetrator and IPV Victim at the
time of theincident, i.e., living together in the same household,
irrespective of marital status

Response Options:
0
No
1
Yes
9
Unknown
Uses
This data element indicates whether the IPV Perpetrator and IPV Victim were residing in the
same household at the time of the incident.
Discussion
If indication is provided through police narratives or other data sources that the IPV
Perpetrator and IPV Victim shared a primary residence at the time of the incident, then
“cohabit” should be coded as “yes.” If the IPV Perpetrator and IPV Victim are listed as
having the same address and there is no information contrary about their having separated,
code as “yes” even in the absence of an affirmative statement about cohabitation status. If the
IPV Perpetrator and IPV Victim lived together fairly consistently, but there had been a recent
change of status (e.g., less than 1 week of living in separate households) or they have
separate addresses, then “cohabit” should still be coded as “yes.” For example, if it was
reported that a IPV Victim had been staying with her parents for a few days or the IPV
Victim had a separate mailing address, but primarily resided with the IPV Perpetrator, they
should be coded as cohabitating.
Analysis
Name

Label

Cohabit

Cohabitation status

Table
Person

SAS Variable Names by Data Source
IPV
COHABIT

3-18

Priority
Field
Length
Number
1
O

Type

Primacy
IPV

IPV Module

Relationship length number of units: RelUnit
Unit of time used in relationship length: RelLgth
Data Sources: IPV
NVDRS Name
RelUnit
RelLgth

Definition
Unit of time for IPV Perpetrator and IPV Victim involvement in a
romantic relationship
Length of time the IPV Perpetrator and IPV Victim were involved
in a romantic relationship

Response Options:
RelUnit
1
Years
2
Months
3
Days
4
Hours
9
Unknown
RelLgth
99

Unknown

Uses
These data elements describe the length of the romantic relationship between the IPV
Perpetrator and IPV Victim and can be useful in providing information on the context and
situation surrounding the IPV homicide incident.
Discussion
This variable provides information on the length of time the IPV Perpetrator and IPV Victim
were involved in a romantic relationship. This time period should be estimated from
information drawn from CME or police narrative reports. It should reflect the total time the
couple have been in a relationship and not just, in the case of married couples, the length of
the marriage.
It is coded using a numerical indication of the number of years, months, weeks, and days the
relationship lasted. First the coder should provide information on the unit that best describes
the amount of time of the IPV Perpetrator and IPV Victim relationship in terms of years,
months, or less than 1 month. Indicate the length of the romantic relationship in RelLgth and
the units of measurement for the interval (e.g., hours, days, weeks) in RelUnit. For 2 hours
through 47 hours, use hours; for 48 hours and to 29 days, use days. For 30 or more days, use
months. For 365 or more days, use years. Round to the nearest unit. If relationship length was
noted as a range, use the high end of the range (e.g., 15–29 days, use 29). If relationship
length is not precisely noted, indicate 999 in RelLgth and the applicable unit in RelUnit (e.g.,
“couple dated for a few days” would be 999 in RelLgth and 1 [day] in RelUnit).

3-19

IPV Module

Analysis
Name

Label

RelUnit

Relationship length
number of units
Unit of time used in
relationship length

RelLgth

Table
Person

Field
Priority
Length
Number
1
O

Person

Number

SAS Variable Names by Data Source
IPV
RELUNIT
RELLGTH

3-20

Type

2

O

Primacy
IPV
IPV

IPV Module

Breakup or breakup in progress: RelBrkup
Breakup length number of units: BrkupLgth
Unit of time used in breakup length: BrkupUnit
Data Sources: IPV
NVDRS Name
RelBrkup
BrkupUnit
BrkupLgth

Definition
Indication of a breakup or in-process breakup of IPV Perpetrator
and IPV Victim
Unit of time for IPV Perpetrator and IPV Victim breakup
IPV Perpetrator and IPV Victim relationship breakup length

Response Options:
RelBrkup
0 No, there was no indication of a breakup between the IPV Perpetrator and IPV Victim
1 No, a breakup was threatened by the IPV Perpetrator or IPV Victim but did not happen
2 Yes, a breakup occurred immediately preceding or during the incident
3 Yes, a breakup occurred at some point prior to the incident but not during or immediately
preceding the incident
9 Unknown
BrkupUnit
1 Years
2 Months
3 Weeks
4 Days
5 Hours
8 Not Applicable
9 Unknown
BrkupLgth
88 Not Applicable
99 Unknown
Uses
These data elements describe whether a breakup had occurred or was in process of occurring
and, if so, how long ago the breakup occurred. This information can be used for prevention
efforts in determining key stages of relationships, particularly those with histories of IPV,
when risks for IPV-related homicides may be greatest.
Discussion
These variables provide information drawn from CME or police narrative reports that
provide information whether a breakup occurred between the IPV Perpetrator and IPV
Victim. “RelBrkup” should be coded as “yes” if there is information in the reports indicating
the IPV Perpetrator and IPV Victim had broken up or were in the process of breaking up.
This should include cases in which the partners recently divorced or one of the partners filed
3-21

IPV Module
for divorce or threatened divorce. “BrkupUnit” and “BrkupLgth” time period should be
estimated from information drawn from CME or police narrative reports. It is coded using a
numerical indication of the number of years, months, weeks, and days of how long ago the
breakup occurred. First the coder should provide information on the unit that best describes
the amount of time that has passed since the IPV Perpetrator and IPV Victim breakup in
terms of years, months, or less than 1 month. This is then followed by the number that best
describes the time length of the breakup. If the IPV Perpetrator and IPV Victim relationship
is described as having numerous breakups, the length should be measured using the most
recent breakup. Information on the status of the relationship and timing of relationship
termination may provide insight into precipitating events that may have contributed to the
incident.
Analysis
Name

Label

RelBrkup

Breakup or breakup
in progress
BrkupUnit Unit of time used in
breakup length
BrkupLgth Breakup length
number of units

Person

Priority
Field
Length
Number
1
O

Person

Number

1

O

IPV

Person

Number

2

O

IPV

Table

SAS Variable Names by Data Source
IPV
RELBRKUP
BRKUPUNIT
BRKUPLGTH

3-22

Type

Primacy
IPV

IPV Module

Children under 18 living at home: ChildHome
Number of children under 18 living at home: Child#
Any children not offspring of IPV Perpetrator: ChildP
Any children not offspring of IPV Victim: ChildV
Data Sources: IPV
NVDRS Name
ChildHome
Child#
ChildV
ChildP

Definition
Were any children under age 18 living at the victim’s home at the
time of the incident
How many of children under age 18 were living at the victim’s
home at the time of theincident
Were any of those children not the IPV Perpetrator’s offspring
Were any of those children not the IPV Victim’s offspring

Response Options:
ChildHome
StepChildP
StepChildV
0 No
1 Yes
9 Unknown
Child#
88 Not Applicable
99 Unknown
Uses
These data elements help quantify the potential impact on children of the violent death of a
parent at the hands of the other parent or at the hands of a parent’s intimate partner. This
information can be useful in planning prevention and treatment efforts with children exposed
to such trauma.
Discussion
This set of variables is only for IPV Victims or IPV Perpetrators who are killed by an
intimate partner.
Children <18 at home (ChildHome)—Code “yes” if there were children under age 18 living
in the IPV Victim’s home at the time of the incident.
Number of Children <18 at home (Child#)—Code the number of children under age 18 living
in the IPV Victim’s home at the time of the incident. If a report indicates that children were
living in the home but does not specify their age, it is acceptable to code this variable.
Any children not the IPV Perpetrator’s (ChildV)—Code “yes” if any of the children at home
were not the IPV Perpetrator’s offspring. For example, if the victim had one child with her
3-23

IPV Module
ex-husband (the IPV Perpetrator) and one from a previous or subsequent relationship, code
“yes.”
Any children not the IPV Victim’s (ChildP)—Code “yes” if any of the IPV Perpetrator’s
children at home were not the IPV Victim’s offspring. For example, if the perpetrator had
one child with an ex-spouse (the IPV Victim) and one from a previous or subsequent
relationship, code “yes.”
Because we are attempting to describe the problem of children who are exposed to the
violent death of a parent by a partner, please answer these questions with reference to the
IPV Victim’s or IPV Perpetrator’s children and not with reference to other children who may
be living in the house (such as cousins or neighbors) or witnessed the incident (such as a
passer-by).
Analysis
Name

Label

ChildHome Children under 18
living at home
Child#
Number of children
under 18 living at
home
ChildV
Any children not
offspring of IPV
Victim
ChildP
Any children not
offspring of IPV
Perpetrator

Table
Person

Field
Priority
Length
Number
1
O

Person

Number

2

O

IPV

Person

Number

1

O

IPV

Person

Number

1

O

IPV

SAS Variable Names by Data Source
IPV
CHILDHOME
CHILDNUM
CHILDP
CHILDV

3-24

Type

Primacy
IPV

IPV Module

Number of children exposed to homicide: ChildSaw
Number of children 5 or under exposed to homicide: Child5under
Use of child as shield during incident: ChildShield
Child intervened during incident: ChildInterv
Data Sources: IPV
NVDRS Name
ChildSaw
Child5under
ChildShield
ChildInterv

Definition
Number of children directly exposed to the incident (i.e., saw it,
heard it, or discoveredthe body)
Number of children age 5 or younger who witnessed the incident
Use of child as shield during the incident
Child intervened during the incident

Response Options:
ChildSaw
Child5under
9 Some, but unknown number
99 Unknown
ChildShield
ChildInterv
0 No
1 Yes
9 Unknown
Uses
These data elements help to quantify the potential impact witnessing a violent death on
children and the level of involvement that children may have during the incident, such as
being used as a shield by an adult or attempting to intervene during the incident. This
information can be useful in planning prevention and treatment efforts with children exposed
to such trauma.
Discussion
Children exposed to the homicide (ChildSaw)—Code the number of children (under the age
of 18) who were directly exposed to the homicide. For example, they saw it, they heard it
through the walls, they witnessed the suspect abducting the victim, they were attacked or
threatened during the incident or were used as a shield, or they discovered the body.
Children 5 or younger exposed to the homicide (Child5under)—Code the number of children
(age 5 and younger) who were directly exposed to the homicide. For example, they saw it,
they heard it through the walls, they witnessed the suspect abducting the victim, they were
attacked or threatened during the incident or were used as a shield, or they discovered the
body.

3-25

IPV Module
Children used as shields during the incident (ChildShield)—Code “yes” if a person in the
incident attempted to use a child as a physical shield to prevent or end an attack.
Children who attempted to intervene during the incident (ChildInterv)—Code “yes” if a child
attempted to intervene during the homicide incident. For example, if a child tried to in some
way prevent the IPV Perpetrator from harming the IPV Victim by stepping between them,
made verbal threats, etc.
Analysis
Name

Label

Table

ChildSaw

Number of children
exposed to homicide
Child5under Number of children
5 or under exposed
to homicide
ChildShield Use of child as
shield during
incident
ChildInterv Child intervened
during incident

SAS Variable Names by Data Source
IPV
CHILDSAW
CHILD5UNDER
CHILDSHIELD
CHILDINTERV

3-26

Type

Person

Field
Priority
Length
Number
2
O

Primacy

Person

Number

2

O

IPV

Person

Number

1

O

IPV

Person

Number

1

O

IPV

IPV

IPV Module

Restraining order ever: RestrainEver
Restraining order at time of incident: RestrainNow
Restraining order type: RestrainType
Restraining order issue date: RestrainDate
Restraining order served: RestrainServ
Persons protected by restraining order: RestrainProt
Data Sources: IPV
NVDRS Name
RestrainEver
RestrainNow
RestrainType
RestrainDate
RestrainServ
RestrainProt

Definition
Refers to whether there was ever a restraining order between the
members of the couple (IPV Vict and IPV Perp)
Refers to whether there was a restraining order between the
members of the couple at the time of incident
The type of restraining order in place
The date the restraining order was issued
Indication of whether the restraining order was served
Individual(s) protected by the restraining order

Response Options:
RestrainEver
RestrainNow
0
No
1
Yes
9
Unknown
RestrainType
1
2
3
8
9

Emergency
Temporary
Permanent
No restraining order
Unknown

RestrainDate
Date
RestrainServ
0
1
8
9

No
Yes
No restraining order
Unknown

RestrainProt
1
2

IPV Victim
IPV Perpetrator

3-27

IPV Module
3
8
9
88
99

Both
Other
No restraining order
Not applicable
Unknown

Uses
Restraining orders were developed specifically to protect threatened persons, including
current or former intimate partners. The information collected in this data element will help
in evaluating whether restraining orders are effective in deterring IPV, as well as whether the
timing of restraining orders is related to IPV deaths.
Discussion
RestrainEver Refers to whether there was ever a restraining order between the members of
the couple (IPV Vict and IPV Perp)
RestrainNow Refers to whether there was a restraining order between the members of the
couple at the time of incident
RestrainType The type of restraining order in place
RestrainDate The date the restraining order was issued
RestrainServ Indication of whether the restraining order was served
RestrainProt Individual(s) protected by the restraining order
Code “RestrainNow” as “yes” if a restraining order involving both the IPV Perpetrator and
IPV Victim was issued at the time of the incident. Data sources for this information will
likely vary by state. Some states can utilize statewide restraining order databases, while other
states must rely on contacting county courthouses where the fatal incident took place. The
police report is another possible source for this information. Restraining orders may be
referred to in a number of ways including restraining order, protective order, or by specific
state statute number. Restraining orders that are not abuse prevention orders do not qualify
and should not be included. For example, a restraining order not to spend money from a joint
account filed as part of divorce proceedings should not be included. Information may also be
available on the date that the restraining order was issued and served documentation of the
restraining order should indicate the date on which it was issued. This should be entered with
month, day, and year. The date served may not be as readily available. This information may
be found in police, Domestic Violence Fatality Review Team (DVFRT) report, or court
records. The RestrainServ element only requires a yes, no, or unknown response.
Documentation for the restraining order should also include information on the individual(s)
protected by the order. While most restraining orders will include only one of the partners,
some may also include other child dependents. The information requested for the restraining
orders provides more detail on the timing and coverage of the restraining order and may
provide insight into precipitating events of the incident. If multiple restraining orders exist,
record only the most recent between the intimate partners.

3-28

IPV Module

Analysis
Name

Label

Table

RestrainEver

Restraining order
ever
RestrainNow Restraining order at
time of incident
RestrainType Restraining order
type
RestrainDate Restraining order
issue date
RestrainServ Restraining order
serverd
RestrainProt Persons protected by
restraining order

Type

Person

Field
Priority
Length
Number
1
O

Primacy

Person

Number

1

O

IPV

Person

Number

1

O

IPV

Person

Date

10

O

IPV

Person

Number

1

O

IPV

Person

Number

1

O

IPV

IPV

SAS Variable Names by Data Source
IPV
RESTRAINEVER
RESTRAINNOW
RESTRAINTYPE
RESTRAINSERV
RESTRAINPROT

3-29

IPV Module

Prior arrest(s): PArrestP, PArrestV
Type of arrest(s): ArrestTypeP, ArrestTypeV
Type of arrest(s) if other: ArrestTypePMemo, ArrestTypeVMemo
Prior conviction(s): PConvictP, PConvictV
Type of conviction(s): ConvTypeP, ConvTypeV
Type of conviction(s) if other: ConvTypePMemo, ConvTypeVMemo
Data Sources: IPV
NVDRS Name
PArrestP
PArrestV
ArrestTypeP
ArrestTypeV
ArrestTypePMemeo
ArrestTypeVMemeo
PConvictP
PConvictV
ConvTypeP
ConvTypeV
ConvTypePMemeo
ConvTypeVMemeo

Definition
IPV Perpetrator had prior arrest(s)
IPV Victim had prior arrest(s)
Type of arrests for IPV Perpetrator
Type of arrests for IPV Victim
Test describing other type(s) of arrest for IPV Perpetrator
Test describing other type(s) of arrest for IPV Victim
IPV Perpetrator had prior criminal conviction(s)
IPV Victim had prior criminal conviction(s)
Type of convictions for IPV Perpetrator
Type of convictions for IPV Victim
Test describing other type(s) of conviction for IPV Perpetrator
Test describing other type(s) of conviction for IPV Victim

Response Options:
PArrestP
PArrestV
PConvictP
PConvictV
0
No
1
Yes
9
Unknown
ArrestTypeP
ArrestTypeV
ConvTypeP
ConvTypeV
1
2
3
4
5
6
7
8
9

3-30

Homicide
Robbery
Sexual assault (forcible)
Assault offenses (other than sexual assault)
Property offenses
Weapons offenses
Drug abuse violations
Offenses against family or children
Alcohol-related offenses

IPV Module
10
11
12
99

Restraining order violations
Other (specify)
Other unspecified
Unknown

Uses
These data are used to identify persons who have come to the attention of law enforcement as
suspected criminal offenders. The information collected may be helpful in determining the
extent to which previous arrests, including the types of arrests, are predictors of future acts of
intimate partner violence (IPV).
Discussion
The data elements provide information from state criminal history records. The coder should
first indicate if an arrest or conviction occurred and then indicate the category. If a person
has arrests and/or convictions in more than one category, list the most severe type of offense
(homicide, then sexual assault, other assaults, offenses against family or children, robbery,
property offenses, weapons offenses, drug abuse violations, and alcohol-related offenses). If
this data element is coded from the criminal history records of a specific municipal or county
police department, the variable should be coded “unknown” if no arrest is found, because
these records do not include other law enforcement departments in the state. Definitions for
all Part I and Part II offenses can be found in the UCR handbook (FBI, 2004):
http://www.fbi.gov/ucr/handbook/ucrhandbook04.pdf. Prior arrests or convictions for
homicide offenses include murder/non-negligent manslaughter, negligent manslaughter, and
justifiable homicide. Sex offenses include forcible rape, forcible sodomy, sexual assault with
an object, and forcible fondling. Assault offenses include aggravated assault, simple assault,
and intimidation. Property offenses should include the crimes of burglary, larceny/theft,
fraud, possession of stolen property, embezzlement, and vandalism. Weapons offenses
include the any crimes related to the manufacture, sale, or possession of deadly weapons.
Drug abuse violations are defined as “the violation of laws prohibiting the production,
distribution, and/or use of certain controlled substances and the equipment or devices utilized
in their preparation and/or use.” Offenses against family or children are defined as “unlawful
nonviolent acts by a family member (or legal guardian) that threaten the physical, mental, or
economic well-being or morals of another family member and that are not classifiable as
other offenses, such as assault or sex offenses.” Alcohol-related offenses include driving
under the influence and drunkenness.

3-31

IPV Module

Analysis
Name

Label

Table

Type

PArrestP
PArrestV
ArrestTypeP
ArrestTypeV
ArrestTypePMemeo
ArrestTypeVMemeo
PConvictP

Prior arrest(s)
Prior arrest(s)
Type of arrest(s)
Type of arrest(s)
Type if other
Type if other
Prior
conviction(s)
Prior
conviction(s)
Type of
conviction(s)
Type of
conviction(s)
Type if other
Type if other

Person
Person
Person
Person
Person
Person
Person

Number
Number
Number
Number
Text
Text
Number

Person

Number

1

O

IPV

Person

Number

2

O

IPV

Person

Number

2

O

IPV

Person
Person

Text
Text

50
50

O
O

IPV
IPV

PConvictV
ConvTypeP
ConvTypeV
ConvTypePMemeo
ConvTypeVMemeo

SAS Variable Names by Data Source
IPV
PARRESTP
PARRESTV
ARRESTTYPEP
ARRESTTYPEV
ARRESTTYPEPMEMO
ARRESTTYPEVMEMO
PCONVICTP
PCONVICTV
CONVTYPEP
CONVTYPEV
CONVTYPEPMEMO
CONVTYPEVMEMO

3-32

Field
Priority
Length
1
O
1
O
2
O
2
O
50
O
50
O
1
O

Primacy
IPV
IPV
IPV
IPV
IPV
IPV
IPV

IPV Module

Prior IPV Arrest(s): IPVArrP, IPVArrV
Data Sources: IPV
NVDRS Name
IPVArrP
IPVArrV

Definition
IPV Perpetrator had prior arrest for violence against an intimate
partner
IPV Victim had prior arrest for violence against an intimate
partner

Response Options:
0
No
1
Yes
9
Unknown
Uses
These data elements identify persons who have previously come to the attention of law
enforcement as a suspected IPV Perpetrator of intimate partner violence, whether against the
partner in this incident or any other partner.
Discussion
This variable provides information that is most likely to be included in the police reports.
Some state criminal history databases explicitly identify domestic violence offense, but some
do not, so this variable may be difficult for some states to code. Prior IPV arrests
“IPVArrP/V” should be defined as any UCR Part I crimes—homicide, forcible rape, robbery,
and aggravated assault—or the Part II crime of simple assault when committed against a
former or current intimate partner.
Analysis
Name

Label

IPVArrP
IPVArrV

Prior IPV arrest(s)
Prior IPV arrest(s)

Table
Person
Person

Type

Field
Priority
Length
Number
1
O
Number
1
O

Primacy
IPV
IPV

SAS Variable Names by Data Source
IPV
IPVARRP
IPVARRV

3-33

IPV Module

Physical illness: IPVIllnessP, IPVIllnessV
Diagnosis of physical illness: IPVIllTxtP, IPVIllTxtV
Disability: IPVDisableP, IPVDisableV
Disability was physical: IPVDisPhyP, IPVDisPhyV
Disability was developmental: IPVDisDevP, IPVDisDevV
Disability was sensory: IPVDisSensP, IPVDisSensV
Data Sources: IPV
NVDRS Name
IPVIllnessP
IPVIllnessV
IPVIllTxtP
IPVIllTxtV
IPVDisableP
IPVDisableV
IPVDisPhyP
IPVDisPhyV
IPVDisDevP
IPVDisDevV
IPVDisSensP
IPVDisSensV

Definition
IPV Perpetrator had an acute or chronic physical illness at the
time of the incident
IPV Victim had an acute or chronic physical illness at the time of
the incident
Free text field to indicate diagnosis if IPV Perpetrator was
physically ill at the time of theincident
Free text field to indicate diagnosis if IPV Victim was physically
ill at the time of theincident
IPV Perpetrator had a disability at the time of the incident
IPV Victim had a disability at the time of the incident
IPV Perpetrator’s disability was physical (e.g., paraplegia,
cerebral palsy)
IPV Victim’s disability was physical (e.g., paraplegia, cerebral
palsy)
IPV Perpetrator’s disability was developmental (e.g., mental
retardation)
IPV Victim’s disability was developmental (e.g., mental
retardation)
IPV Perpetrator’s disability was sensory (e.g., blindness,
deafness)
IPV Victim’s disability was sensory (e.g., blindness, deafness)

Response Options:
0 No
1 Yes
9 Unknown
Uses
Useful in identifying the subset of intimate partner homicides that occur in the context of the
IPV Victim’s or IPV Perpetrator’s state of health. The stress of caring for an acutely or
chronically ill individual can be a contributing factor to abusive behavior on the part of the
caregiver. These cases appear to be overrepresented among intimate partner homicides
perpetrated by older suspects.

3-34

IPV Module

Discussion
Physical illness may be acute (e.g., viral gastroenteritis, pneumonia) or chronic (e.g.,
diabetes, asthma, sickle cell anemia). However, if the chronic illness did not impose
increased care demands at the time of the incident, do not code “yes.” For example, if an
individual had a history of asthma, but had no acute exacerbation at the time of the incident,
code “no.” The severity of the illness should not be considered when coding IPVIllnessP/V;
any mention in the record of the individual being physically ill at the time of the incident is
sufficient to warrant coding IPVIllnessP/V as “yes.” Physical disability implies a chronic
physical impairment that has a substantial, long-term effect on the individual’s day-to-day
functioning (e.g., cerebral palsy). Developmental disability implies a chronic cognitive or
developmental deficit that has a substantial, long-term effect on the individual’s day-to-day
functioning (e.g., autism, mental retardation). Sensory disability implies a chronic sensory
deficit that has a substantial, long-term impact on the individual’s day-to-day functioning
(e.g., blindness, deafness). If an individual was not specifically diagnosed with or
documented to have one of the listed disabilities, answer “no.” The information used to
complete this data element may come from medical records and/or autopsy.
Analysis
Name
IPVIllnessP
IPVIllnessV
IPVIllTxtP

Label

Physical illness
Physical illness
Diagnosis of
physical illness
IPVIllTxtV
Diagnosis of
physical illness
IPVDisableP Disability
IPVDisableV Disability
IPVDisPhyP Disability was
physical
IPVDisPhyV Disability was
physical
IPVDisDevP Disability was
developmental
IPVDisDevV Disability was
developmental
IPVDisSensP Disability was
sensory
IPVDisSensV Disability was
sensory

Table
Person
Person
Person

Type

Field
Priority
Length
Number
1
O
Number
1
O
Text
50
O

Primacy
IPV
IPV
IPV

Person

Text

50

O

IPV

Person
Person
Person

Number
Number
Number

1
1
1

O
O
O

IPV
IPV
IPV

Person

Number

1

O

IPV

Person

Number

1

O

IPV

Person

Number

1

O

IPV

Person

Number

1

O

IPV

Person

Number

1

O

IPV

3-35

IPV Module

SAS Variable Names by Data Source
IPV
IPVIllnessP
IPVIllnessV
IPVIllTxtP
IPVIllTxtV
IPVDisableP
IPVDisableV
IPVDisPhyP
IPVDisPhyV
IPVDisDevP
IPVDisDevV
IPVDisSensP
IPVDisSensV

3-36

IPV Module

Alcohol use suspected: IntoxP, IntoxV
Drug use suspected: IllDrugP, IllDrugV
Data Sources: IPV
NVDRS Name
IntoxP
IntoxV
IllDrugP
IllDrugV

Definition
IPV Perpetrator suspected to be under the influence of alcohol at
the time of the incident
IPV Victim suspected to be under the influence of alcohol at the
time of the incident
IPV Perpetrator suspected to be under the influence of an illicit
drug at the time of the incident
IPV Victim suspected to be under the influence of an illicit drug
at the time of the incident

Response Options:
0 No
1 Yes
9 Unknown
Uses
Useful in evaluating the possible role of drugs or alcohol in violent incidents.
Discussion
“Intox” is a current NVDRS variable asked of victims only. In the IPV module it is also
asked of both the IPV Victim and IPV Perpetrator. “IllDrug” is a new variable also asked of
both IPV Victims and Perpetrators.
Alcohol use suspected (“IntoxP/V”)—“IntoxP/V” should be coded “yes” using information
from witness or investigator reports (e.g., police note that the IPV Perpetrator or Victim had
been drinking), circumstantial evidence (e.g., empty six pack scattered around IPV
Perpetrator or Victim), or test results (e.g., police breathalyzer). This variable refers only to
alcohol use and not drug use. Therefore, if a IPV Perpetrator or Victim was said to have been
smoking crack on the day of the incident, but tested negative for alcohol and there is no
evidence of drinking, “Intox” should be coded as “no.” The phrase “in the hours preceding
the incident” can be interpreted relatively broadly. For example, if friends report that a IPV
Perpetrator or Victim was drinking heavily at a party, and returned home that evening and
was killed sometime later that night, “IntoxP/V” should be coded as “yes.” The level of
intoxication is not relevant in coding this variable. If there is no evidence of alcohol use, code
this variable as “no.” Use the “unknown” option only if the source does not have a narrative
that could provide the evidence of intoxication.
Drug use suspected (“IllDrugP/V”)—“IllDrugP/V” should be coded “yes” based on witness
or investigator reports or test results from the IPV Perpetrator or Victim. Illicit drugs include
not only street drugs like heroin, cocaine, marijuana, and methamphetamine, but also illicitly
obtained prescription drugs like oxycodone and substances that are sniffed for their mood-

3-37

IPV Module
altering effects (e.g., sniffing glue, “huffing” gasoline). Prescription drugs believed to be
taken in accordance with the prescription directions should not be included as illicit drug use.
Both “IntoxP/V” and “IllDrugP/V” will include some false positives, since they are not
necessarily based on test results. For a more conservative evaluation of drug and alcohol use
in suspects, use toxicological testing if available.
Analysis
Name

Label

IntoxP

Alcohol use
suspected
Alcohol use
suspected
Drug use suspected
Drug use suspected

IntoxV
IllDrugP
IllDrugV

Table
Person

Field
Priority
Length
Number
1
O

Person

Number

1

O

IPV

Person
Person

Number
Number

1
1

O
O

IPV
IPV

SAS Variable Names by Data Source
IPV
INTOXP
INTOXV
ILLDRUGP
ILLDRUGV

3-38

Type

Primacy
IPV

IPV Module

Mental health problem: IMentalP, IMentalV
Data Sources: IPV
NVDRS Name
IMentalP
IMentalV

Definition
IPV Perpetrator had a mental health problem
IPV Victim had a mental health problem

Response Options:
0 No
1 Yes
9 Unknown
Uses
This variable can be used to examine the role of mental health problems as risk factors both
for suicide and for homicide perpetration and victimization.
Discussion
If the case involves a suicide, this information will be captured in the general NVDRS system
for the suicide victim. Code a person as “yes” for “IMentalP/V” if he or she has been
identified as having a mental health problem. Mental health problems include disorders and
syndromes listed in the DSM-IV (Diagnostic and Statistical Manual of Mental Disorders, 4th
Revision) with the exception of alcohol and other substance disorders (as these are captured
in separate variables). Examples of disorders qualifying as mental health problems include
not only diagnoses such as major depression, schizophrenia, and generalized anxiety
disorder, but developmental disorders (e.g., mental retardation, autism, attention deficit
hyperactivity disorder), eating disorders, personality disorders, and organic mental disorders
such as Alzheimer’s and other dementias. Also indicate “yes” if the person was being treated
for a mental health problem including treatment through involuntary mechanisms such as an
Emergency Order of Detention, even if the nature of the problem is unclear (e.g., “was being
treated for various psychiatric problems”). It is acceptable to endorse this variable on the
basis of past treatment of a mental health problem, unless it is specifically noted that the
problem has been resolved. For example, “IPV Victim or Perpetrator was hospitalized twice
for mental problems,” is adequate basis for coding “IMentalP/V” as “yes.” Code
“IMentalP/V” if a mental health problem is noted even if the timeframe is unclear (as in
“history of depression”), or if the person was seeking mental health treatment or someone
was seeking treatment on his or her behalf (e.g., “family was attempting to have him
hospitalized for psychiatric problems”). “IMentalP/V” should also be coded as “yes” if the
IPV Victim or Perpetrator has a prescription for an antidepressant or other psychiatric
medication. The drug list provided in the training notebook identifies drugs that can be
considered psychiatric medications. We have separate questions for substance use problems.
Therefore, do not include substance abuse as a “current mental health problem.”
Coding “no” (as opposed to “unknown”) means that the record explicitly stated that the
person had no known mental health problems. Code “unknown” if there is no information
about the person’s mental health status or if the information is unclear.

3-39

IPV Module

Case Examples
Yes
• Toxicology report from medical examiner indicates that the IPV Victim or Perpetrator
tested positive for Sertraline (an antidepressant)
• Person had post traumatic stress disorder (PTSD)
• History of depression
• Was under the care of a psychiatrist
No
• Record states “no known mental disorders”
Unknown
• Neighbor indicates that the person was not acting normally.
• Was depressed over a recent break-up.
Analysis
Name

Label

IMentalP

Mental health
problem
Mental health
problem

IMentalV

Table
Person

Field
Priority
Length
Number
1
O

Person

Number

SAS Variable Names by Data Source
IPV
IMENTALP
IMENTALV

3-40

Type

1

O

Primacy
IPV
IPV

IPV Module

Mental health diagnosis 1: IMDiagP1, IMDiagV1
Mental health diagnosis 2: IMDiagP2, IMDiagV2
Mental health diagnosis 3: IMDiagP3, IMDiagV3
Other mental health diagnosis: IMenTxtP, IMenTxtV
Data Sources: IPV
NVDRS Name
IMDiagP1
IMDiagV1
IMDiagP2
IMDiagV2
IMDiagP3
IMDiagV3
IMenTxtP
IMenTxtV

Definition
IPV Perpetrator mental health diagnosis 1
IPV Victim mental health diagnosis 1
IPV Perpetrator mental health diagnosis 2
IPV Victim mental health diagnosis 2
IPV Perpetrator mental health diagnosis 3
IPV Victim mental health diagnosis 3
IPV Perpetrator other mental health diagnosis
IPV Victim other mental health diagnosis

Response Options:
1 Depression/dysthymia
2 Bipolar disorder
3 Schizophrenia
4 Anxiety disorder
5 Post traumatic stress disorder
6 ADD or hyperactivity disorder
7 Eating disorder
8 Obsessive-compulsive disorder
9 Mental retardation
10 Autism
11 Personality disorders
12 Alzheimer’s
88 Not applicable
99 Unknown
Uses
These variables identify the diagnoses of persons who were noted as having a mental health
problem, and whose mental health problem has been assessed by a mental health practitioner.
Discussion
Code up to three diagnoses. If a diagnosis is not on the code list, code “other” and record the
diagnosis in the text field, “IMenTxtP/V.” If the record indicates more than three diagnoses,
note the additional diagnoses in “IMenTxtP/V.” For cases in which the person was noted as
being treated for a mental health problem, but the actual diagnosis is not documented, code
“IMDiagP/V1” as “unknown.” If the person had a mental health problem (“IMentalP/V” =
“yes”), but the nature of the problem has not been diagnosed (e.g., “was hearing voices and
having paranoid delusions; family was attempting to have her committed”), code

3-41

IPV Module
“IMDiagP/V1” as “not applicable” since she/he had not been treated or diagnosed. Do not
attempt to apply a diagnosis based on reading the symptoms. While it is acceptable to code
“mental health problem” based on the IPV Victim’s or Perpetrator’s prescription for a
psychiatric medication, do not infer a specific diagnosis based on the medication.
Analysis
Name
IMDiagP1

Label

Mental health
diagnosis 1
IMDiagV1 Mental health
diagnosis 1
IMDiagP2 Mental health
diagnosis 2
IMDiagV2 Mental health
diagnosis 2
IMDiagP3 Mental health
diagnosis 3
IMDiagV3 Mental health
diagnosis 3
IMenTxtP Other mental health
diagnosis
IMenTxtV Other mental health
diagnosis

Table
Person

Field
Priority
Length
Number
2
O

Person

Number

2

O

IPV

Person

Number

2

O

IPV

Person

Number

2

O

IPV

Person

Number

2

O

IPV

Person

Number

2

O

IPV

Text

Number

50

O

IPV

Text

Number

50

O

IPV

SAS Variable Names by Data Source
IPV
IMDiagP1
IMDiagV1
IMDiagP2
IMDiagV2
IMDiagP3
IMDiagV3
IMenTxtP
IMenTxtV

3-42

Type

Primacy
IPV

IPV Module

Currently in treatment for mental health problem: ITxMentP, ITxMentV
Ever treated for mental health problem: IHistMentalP, IHistMentalV
Data Sources: IPV
NVDRS Name
ITxMentP
ITxMentV
IHistMentalP
IHistMentalV

Definition
IPV Perpetrator currently in treatment for a mental health
problem
IPV Victim currently in treatment for a mental health problem
IPV Perpetrator ever treated for a mental health problem
IPV Victim ever treated for a mental health problem

Response Options:
0 No
1 Yes
9 Unknown
Uses
This variable can be used to assess the proportion of IPV Victims and Perpetrators who were
currently or formerly in mental health treatment. The information can be helpful in planning
and delivering mental health services and in evaluating quality of care.
Discussion
The variable “ITxMentP/V” (current mental health treatment) should be coded “yes” if the
IPV Victim or Perpetrator was in current treatment (that is, had a current prescription for a
psychiatric medication or saw a mental health professional within the past 2 months).
Treatment includes seeing a psychiatrist, psychologist, medical doctor, therapist, or other
counselor for a mental health or substance abuse problem; receiving a prescription for an
antidepressant or other psychiatric medicine (see training notebook for list of psychiatric
drugs); or residing in an inpatient or halfway house facility for mental health problems. The
variable “IHistMentalP/V” indicates whether the IPV Perpetrator or Victim was noted as ever
having received professional treatment for a mental health problem, either at the time of
death or in the past. If an IPV Perpetrator or Victim is in current treatment, by definition
“IHistMentalP/V” (ever in treatment) should be endorsed. If a decedent died as the result of
an overdose from multiple medications and it is not clear whether the medications were his
or her own (as in an IPV Victim or Perpetrator swallowing everything in the family’s
medicine cabinet), the existence of an antidepressant or other psychiatric medication in the
IPV Victim’s or Perpetrator’s bloodstream is not sufficient evidence of mental health
treatment. For IPV Perpetrators and Victims who die by other means than drug overdose
(e.g., shooting, hanging), toxicologic test results indicating the presence of a psychiatric
medication is sufficient evidence of mental health treatment.
Case Examples
Current treatment for mental illness

3-43

IPV Module
Yes
• A recently filled, unopened prescription belonging to the IPV Victim or Perpetrator for an
antidepressant is found in the medicine cabinet.
• In treatment for depression for the last 10 years.
• Released from inpatient care for bipolar disorder a week ago.
No
• Records indicate not in mental health treatment
• Taking St. John’s Wort (nonprescription herb) for depression because of a magazine article
s/he had read.
• Taking sleeping pills for insomnia.
Ever treated for mental illness
Yes
• Several years ago the IPV Victim or Perpetrator was treated for bipolar disorder.
• The IPV Victim or Perpetrator had begun seeing a psychiatrist recently, but had previously
never been in treatment.
Analysis
Name

Label

ITxMentP

Currently in
treatment for mental
health problem
ITxMentV
Currently in
treatment for mental
health problem
IHistMentalP Ever treated for
mental health
problem
IHistMentalV Ever treated for
mental health
problem

SAS Variable Names by Data Source
IPV
ITxMentP
ITxMentV
IHistMentalP
IHistMentalV

3-44

Person

Priority
Field
Length
Number
1
O

Person

Number

1

O

IPV

Person

Number

1

O

IPV

Person

Number

1

O

IPV

Table

Type

Primacy
IPV

IPV Module

Alcohol problem: IAlcohP, IAlcohV
Other substance abuse problem: ISubstP, ISubstV
Data Sources: IPV
NVDRS Name
IAlcohP
IAlcohV
ISubstP
ISubstV

Definition
IPV Perpetrator had alcohol dependence or alcohol problem
IPV Victim had alcohol dependence or alcohol problem
IPV Perpetrator had other illicit or prescription drug abuse
problem
IPV Victim had other illicit or prescription drug abuse problem

Response Options:
0 No
1 Yes
9 Unknown
Uses
Can be used to assess the proportion of IPV Victims and Perpetrators who were identified as
having alcohol, drug, or other substance abuse problems. The information can be helpful in
exploring the role of substance abuse in IPV homicides and planning substance abuse
services delivery.
Discussion
Code “yes” for “IAlcohP/V” or “ISubstP/V” if the IPV Perpetrator or Victim was perceived
by self or others to have a problem with, or to be addicted to, alcohol or other drugs. An IPV
Perpetrator or Victim who is noted as participating in a drug or alcohol rehabilitation
program or treatment—including self-help groups and 12-step programs—should be coded as
“yes” for “ISubstP/V” or “IAlcohP/V” respectively even if the IPV Perpetrator or Victim was
noted as being currently clean and sober. A problem from the past (i.e., 5 years or more ago)
that has resolved and no longer appears to apply should not be coded. “ISubstP/V” can be
endorsed if an IPV Perpetrator or Victim was noted as using illegal drugs (such as heroin or
cocaine), abusing prescription medications (such as pain relievers or Valium), or regularly
using inhalants (e.g., sniffing gas). If the IPV Perpetrator or Victim is mentioned as using
illegal drugs—even if addiction or abuse is not specifically mentioned—code “ISubstP/V” as
“yes.” An IPV Perpetrator or Victim who takes methadone can be assumed to be in treatment
for heroin addiction. The phrase “history of drug abuse” is sufficient to justify endorsing
“ISubstP/V,” unless it is noted that the IPV Perpetrator or Victim is no longer a drug user.
Previously attempting suicide via overdose is not sufficient justification for endorsing
“ISubstP/V” in the absence of other information.
Case Examples
IAlcohP
IAlcohV
Yes

3-45

IPV Module
• CME report indicates the IPV Victim or Perpetrator was in an alcohol rehabilitation
program last year.
• Called AA sponsor the day before the incident.
• Noted in CME report that the IPV Perpetrator or Victim had been drinking a lot lately and
family was concerned.
No
• CME report indicates that 20 years ago the IPV Perpetrator or Victim had trouble with
drugs and alcohol as a teenager, but not since then.
ISubstP
ISubstV
Yes
• CME report indicates that the perpetrator or victim abuses his/her own painkiller
prescription.
• IPV Perpetrator or Victim made regular visits to a methadone clinic.
• IPV Perpetrator or Victim had track marks and drug paraphernalia at his/her apartment.
• IPV Victim or Perpetrator shot him/herself after a fight with spouse over drug use and
mounting debts.
No
• IPV Perpetrator or Victim smoked marijuana occasionally.
• IPV Perpetrator or Victim attempted suicide via medication overdose on two previous
occasions. No evidence of substance use or abuse.
Analysis
Name

Label

IAlcohP
IAlcohV
ISubstP

Alcohol problem
Alcohol problem
Other substance
abuse problem
Other substance
abuse problem

ISubstV

Person
Person
Person

Priority
Field
Length
Number
1
O
Number
1
O
Number
1
O

Person

Number

Table

SAS Variable Names by Data Source
IPV
IAlcohP
IAlcohV
ISubstP
ISubstV

3-46

Type

1

O

Primacy
IPV
IPV
IPV
IPV

IPV Module

Disclosed intent to commit suicide: ISuiIntP, ISuiIntV
Data Sources: IPV
NVDRS Name
ISuiIntP
ISuiIntV

Definition
IPV Perpetrator disclosed to another person intentions to commit
suicide
IPV Victim disclosed to another person intentions to commit
suicide

Response Options:
0 No
1 Yes
9 Unknown
Uses
This variable can be used to identify the subset of IPV homicides for which opportunities to
intervene and prevent the death may have been present. It is also useful for exploring stated
intent as a risk factor for suicide.
Discussion
Code “ISuiIntP/V” as “yes” if the IPV Perpetrator or victim had previously expressed
suicidal feelings to another person, whether explicitly (e.g., “I’m considering killing myself”)
or indirectly (e.g., “I think everyone would be better off without me” or “I know how to put a
permanent end to this pain”). Do not code this variable as “yes” if the IPV Perpetrator or
Victim disclosed his/her intention to kill him/herself only at the moment of the suicide (i.e.,
when there was no opportunity to intervene to stop the suicide). Also, do not endorse this
variable if the IPV Perpetrator or Victim had talked about suicide sometime in the distant
past, but had not disclosed his/her current intent to commit suicide to anyone. When the
police or CME document whether the IPV Perpetrator or Victim stated his/her intent to
commit suicide, they are doing so less for the purpose of documenting a missed opportunity
for intervention and more for the purpose of indicating why the death is being treated as a
suicide and not a potential homicide. Therefore, the records may be unclear about timing. For
example, the record may state, “IPV Perpetrator or Victim has spoken of suicide in the past,”
and it is not entirely clear whether the talk about suicide was only in the past or was related
to the current incident. This will frequently be a gray area for coding. If the record indicates
disclosure of intent in the past but affirmatively states that there was no disclosure for the
current incident, code “ISuiIntP/V” as “no.” If the record indicates disclosure of intent, but is
unclear about the time frame, code “ISuiIntP/V” as “yes.” This will sometimes be incorrect;
however, the specificity to allow precise coding is too often missing in the records to justify
using a narrower interpretation.
Case Examples
Yes
• The IPV Perpetrator or Victim told a spouse that s/he was planning to end his/her suffering
and was going to stop being a burden.

3-47

IPV Module
• The IPV Perpetrator or Victim has mentioned on and off to friends that s/he was
considering suicide; no one thought s/he would do it.
No
• The IPV Perpetrator or Victim has spoken of suicide in the past, but not in the past few
months when things seemed to be going better for him/her.
• Family members were unaware of any suicidal feelings. During a heated argument over
being grounded, the IPV Perpetrator or Victim shouted, “I’m gonna blow my head off, and
it’s your fault.” He left the room and shot himself.
Unknown
• Had previously threatened to kill his family. No further information available on mental
health history.
Analysis
Name

Label

ISuiIntP

Disclosed intent to
commit suicide
Disclosed intent to
commit suicide

ISuiIntV

Table
Person

Field
Priority
Length
Number
1
O

Person

Number

SAS Variable Names by Data Source
IPV
ISuiIntP
ISuiIntV

3-48

Type

1

O

Primacy
IPV
IPV

IPV Module

History of suicide attempts: ISuicAttP, ISuicAttV
Data Sources: IPV
NVDRS Name
ISuicAttP
ISuicAttV

Definition
IPV Perpetrator had a history of attempting to commit suicide
IPV Victim had a history of attempting to commit suicide

Response Options:
0 No
1 Yes
9 Unknown
Uses
This variable is useful for exploring suicide attempts as a risk factor for completed suicides
and as an opportunity for preventive intervention.
Discussion
Code ISuiAttP/V as “yes” if the IPV Perpetrator or Victim was known to have made previous
suicide attempts, regardless of the severity of those attempts.
Analysis
Name

Label

ISuicAttP

History of suicide
attempts
History of suicide
attempts

ISuicAttV

Table

Type

Person

Field
Priority
Length
Number
1
O

Person

Number

1

O

Primacy
IPV
IPV

SAS Variable Names by Data Source
IPV
ISuicAttP
ISuicAttV

3-49