mechanism for surveillance of violence against women.- Instead, people are often forced to rely on multiple data systems to obtain minimal incidence and prevalence information. This can be problematic when trying to establish incidence and prevalence estimates of VAW, because these data sources are created and maintained for purposes other than monitoring the scope of the problem. For example, police collect information about violence against women for the purpose of apprehending and bringing charges against the perpetrator(s) of the violence, and thus may record few details about the victim. Hospitals collect information primarily for providing optimal patient care and for billing purposes, and thus may record few or no details about the perpetrator of the violence, even if they recognize or record the violence at all (Council on Scientific Affairs, American Medical Association, 1992). Until routine identification and documentation of VAW become part of standard patient care, hospital records may be of limited value for public health surveillance of violence against women. These and other limitations suggest that data from multiple systems are probably needed to arrive at better estimates of the number of women who are victims of violence. However, use of multiple data systems can present logistical challenges and threats to the reliability of the data because, for some incidents, information from the victim will appear in more than one data system (e.g., both police and hospital data), whereas for other incidents victim information will appear in only one data system (e.g., the victim seeks emergency department treatment but does not file a police report). The task of obtaining surveillance information is further complicated by the repetitive nature of some types of VAW, such as intimate partner violence. As a result, it is difficult to determine if the counts obtained reflect the number of individuals affected or the number of incidents of violence. This difficulty is compounded by the necessity of relying on multiple data sources. Police may file and treat each assault separately, even if all incidents were caused by the same perpetrator, whereas hospitals may record repeated incidents in the same patient file. In addition to these logistical challenges, there are social barriers to obtaining accurate VAW surveillance data. These barriers include the taboo nature of the topic; the guilt and shame that inhibit self-identification by victims and perpetrators; and the lack of training, fear of repercussions, and other concerns that inhibit agency personnel from recording reports of VAW in official records, even when cases are identified. Furthermore, only a small fraction of all VAW victims ever seek help from either the criminal justice or the health care system. Recognizing the need to improve the quality of the available data about violence against women, the National Center for Injury Prevention and Control (NCIPC), Centers for Disease Control and Prevention (CDC), initiated a process to begin addressing some of the conceptual and logistical difficulties inherent in the task. To narrow the scope of the task to something more manageable, CDC decided to concentrate on developing data elements for surveillance on one subset of VAW: intimate partner violence. The process involved a consultative procedure to address some of the scientific issues related to definitions and potential data elements that might be appropriate to collect as part of - In this document, the term "surveillance" is used in the public health sense and is defined as the ongoing and systematic collection, analysis, and interpretation of health-related data.# Introduction 1

# INTRODUCTION The Need for Better Data
Violence against women (VAW) incorporates intimate partner violence (IPV), sexual violence by any perpetrator, and other forms of violence against women (e.g., physical violence committed by acquaintances or strangers). Available data suggest that violence against women is a substantial public health problem in the United States. Police data indicate that 3,631 females died in 1996 as the result of homicide (Federal Bureau of Investigation, 1997). Thirty percent of these women were known to have been murdered by a spouse or ex-spouse. Data on nonfatal cases of assault are less easily accessible, but recent survey data suggest that approximately 1.3 million women have been physically assaulted annually and approximately 200,000 women have been raped annually by a current or former intimate partner. Data on lifetime experiences suggest that approximately 22 million women were physically assaulted and approximately 7.8 million women were raped by a current or former intimate partner (Tjaden & Thoennes, 1998). Although these and other statistics (Bachman & Saltzman, 1995;Straus & Gelles, 1990) are sufficient to suggest the magnitude of the problem, some people believe that statistics on VAW under-represent the scale of the problem, and others believe that reports of violence against women are exaggerated.
Much of the debate about the number of women affected by violence has been clouded by the lack of consensus on the scope of the term "violence against women." As indicated by the National Research Council's report on Understanding Violence Against Women, the term has been used to describe a wide range of acts, including murder, rape and sexual assault, physical assault, emotional abuse, battering, stalking, prostitution, genital mutilation, sexual harassment, and pornography (National Research Council, 1996). Researchers have used terms related to violence against women in different ways and have used different terms to describe the same acts. Not surprisingly, these inconsistencies have contributed to varied conclusions about the incidence and prevalence of violence against women.
The lack of consistent information about the number of women affected by violence limits our ability to respond to the problem in several ways. First, it limits our ability to gauge the magnitude of violence against women in relation to other public health problems. Second, it limits our ability to identify those groups at highest risk who might benefit from focused intervention or increased services. Third, it limits our ability to monitor changes in the incidence and prevalence of violence against women over time. This, in turn, limits our ability to monitor the effectiveness of violence prevention and intervention activities. Higher quality and more timely incidence and prevalence estimates have the potential to be of use to a wide audience, including policymakers, researchers, public health practitioners, victim advocates, service providers, and media professionals.
However, obtaining accurate and reliable estimates of the number of women affected by violence is complicated by a number of factors. There is no established and ongoing Introduction 3 surveillance activities. In addition, CDC funded the state health departments in Massachusetts, Michigan, and Rhode Island to pilot test methods, using the most appropriate data sources for each state, for conducting statewide surveillance of IPV among women.

# The Consultative Process
The development of Intimate Partner Violence Surveillance: Uniform Definitions and Recommended Data Elements, Version 1.0 took place through a process spanning several years:
- In 1994, CDC conducted an extensive review of the literature and developed draft definitions and possible data elements to be included in an IPV surveillance system. - These draft documents were discussed in a February 1995 exploratory meeting with consultants experienced in the areas of violence against women and data collection and measurement, and with representatives of the three funded state surveillance pilot projects (Massachusetts, Michigan, and Rhode Island). - The documents were revised and discussed at a March 1995 meeting of the Family and Intimate Violence Prevention Subcommittee of the DHHS Advisory Committee for Injury Prevention and Control. The subcommittee was composed of researchers, practitioners, and victim advocates with expertise in the area of violence against women. - The documents were revised and discussed at a May 1995 meeting with representatives of the three state pilot projects. - The documents were discussed at an October 1995 workshop open to attendees at the CDC-sponsored National Violence Prevention Conference in Des Moines, Iowa. - The documents were discussed at a January 1996 meeting with representatives of the three state pilot projects. - Written feedback was collected from a wide variety of external reviewers who responded to CDC draft documents. - A March 1996 meeting was held with a 12-member panel with expertise in the areas of violence against women and public health surveillance.
At the March 1996 meeting, the panel was charged with two tasks: 1) finalizing a list of data elements that were considered essential for IPV surveillance, and 2) finalizing the definitions to be used in conjunction with the data elements to ensure consistency of meaning. During the panel discussion, however, it became evident that there were no clearly identifiable criteria or procedures for determining which data elements might be most essential. The data elements presented in this report are elements on which the panel thought it would be desirable to collect information, but for which it may or may not be possible to collect information in the context of a surveillance system. The panel also developed conceptual definitions of terms to be used in conjunction with the data elements. It became evident that these definitions might need to be operationalized (i.e., made measurable) in different ways, depending on the source of the data. Given that the pilot surveillance projects in Massachusetts, Michigan, and Rhode Island would each be relying on different data sources, two documents were developed with the understanding that further revisions would be required after the pilot testing by the state projects.

# Introduction 5
(formerly known as the American Society for Testing and Materials) E1238-94: Standard Specification for Transferring Clinical Observations Between Independent Computer Systems (ASTM, 1996).
The Technical Notes at the end of this document provide a detailed description of data types and conventions for addressing missing, unknown, and null data, as well as recommendations for dealing with data elements that are not applicable to selected groups of individuals.

# Notes on the Use of Intimate Partner Violence Surveillance: Uniform Definitions and Recommended Data Elements, Version 1.0
The "Uniform Definitions" are used throughout the "Recommended Data Elements." The definitions are likely to be valuable for a wide range of policymakers, researchers, public health practitioners, victim advocates, service providers, and media professionals seeking to clarify discussions about IPV. However, most terms in the "Uniform Definitions" are defined in only a general sense, and researchers and other users may need to further refine them. Other terms, such as "cohabitation," "dating," and "psychological consequences," were not defined by the expert panel and may need to be defined in subsequent versions of the "Uniform Definitions." A particular issue needing further clarification is the identification of victim and perpetrator in episodes that appear to be mutually violent.
IPV, as specified in the "Uniform Definitions" and used throughout the "Recommended Data Elements," refers to victim/perpetrator relationships among current or former intimate partners. For ease of presentation, the words "current and former" are not always used to qualify the term intimate partner violence but are always implied when the term is used. Note that the document was written to enable data collection for both female and male IPV victims, although initial pilot tests are focused on IPV against women.
As you use the "Recommended Data Elements," keep in mind the following points:
- As with all research on violence against women, ethical and safety issues are paramount. No data should be collected or stored that would in any way jeopardize a woman's safety. Those interested in developing a surveillance system for IPV must be particularly conscious of the need to preserve confidentiality. The issue of confidentiality must be balanced with the need for data linkage across multiple data sources, perhaps through mechanisms such as encryption of unique identifiers.
- Currently the "Recommended Data Elements" contains 50 items. Given that simplicity is an important surveillance system attribute for obtaining high quality data (Centers for Disease Control and Prevention, 1988), and given that recommendations from the three pilot projects and other locations will allow us to distinguish those data elements that might be desirable to collect from those that are possible to collect routinely, this list may eventually be shortened. Desirable data elements that are not feasible to collect as part of a surveillance system will need to be collected in other ways.
- No single agency is likely to collect all of the data elements recommended. As a consequence, it is likely that anyone setting up a surveillance system will need to com-bine data from a number of sources (e.g., health care records and police records) using a relational database (Taylor, 1995). This will allow information on data elements to be gathered from each data source used. The mechanics of how to set up relational databases are not discussed in this document, but information from the three funded state surveillance pilot projects should provide information helpful for developing such databases. A unique identifier will need to be created to allow for linkage across all data sources included. This identifier may or may not be identical to the data element 1.101 Case ID.
- The goals of IPV surveillance are to obtain an estimate of the number of people who are affected by intimate partner violence and to describe the characteristics of people affected, the number and types of IPV episodes, the associated injuries, and other consequences. Counting injuries as part of a surveillance system is a common proxy for estimating the number of people affected. However, the large number of cases in which multiple forms of violence co-occur and the repetitive nature of IPV mean that such a proxy may be less accurate than is desired. To obtain more accurate estimates of the number of people affected by IPV, ultimately we will need to develop some mechanism for linking data, both within and across different data sources, through the use of unique identifiers.
- The recommended data elements include four discrete types of violence: physical violence, sexual violence, threat of physical or sexual violence, and psychological/ emotional abuse. However, one violent episode may contain all four types of violence. A limitation of the present version of the "Recommended Data Elements" is that it will provide a count of episodes involving specific types of violence, but it cannot provide a count of the total number of discrete violent episodes, nor can it provide information about the co-occurrence of different types of violence within all episodes. However, the IPV surveillance system will allow for collection of information about the co-occurrence of different types of violence for the most recent violent episode perpetrated by any intimate partner.
- Each data element is numbered for convenience of presentation and for easy reference. The data elements are not meant to be "administered" as a survey or a questionnaire, but instead are presented as information to be gathered from appropriate data sources in the jurisdictions conducting IPV surveillance. Thus, the elements can be gathered in any order and can be obtained from one or more data sources for any given victim of intimate partner violence. Each data element includes a code set that specifies recommended coding values and instructions for what to do when the data element is not applicable for a particular victim. Obviously, the accuracy and completeness of data collected on IPV victimization depend upon what is documented by the agency providing the information.

# Introduction 7
specifications are new, and field testing is necessary to evaluate them. Systematic field studies are needed to gauge the usefulness of Version 1.0 for IPV surveillance, to identify optimal methods of data collection, and to specify resource requirements for implementation. Prospective users of Version 1.0 are invited to contact CDC to discuss their plans for evaluating or using some or all of the recommended data elements. Lessons learned through field use and evaluation will be a valuable source of input for subsequent revisions, but all comments and suggestions for improving this document are welcome.
As stated earlier, CDC has funded pilot tests of these data elements in Massachusetts, Michigan, and Rhode Island as part of their exploration of surveillance methods, and as a means of assessing the feasibility and utility of collecting this information on women who are IPV victims. We hope that other jurisdictions will also be able to conduct limited pilot tests. After these pilot tests are completed, the document will be revised to incorporate what has been learned. This step will enable us to refine the definitions and reduce the number of recommended data elements to make it more feasible to collect information as part of an IPV surveillance system. Eventually, we hope to develop data elements and definitions for the surveillance of family violence other than IPV (such as child abuse and elder abuse) and other forms of violence against women.

# Perpetrator
Person who inflicts the violence or abuse or causes the violence or abuse to be inflicted on the victim.

# Intimate Partners
Includes:
- current spouses (including common-law spouses)
- current non-marital partners - dating partners, including first date (heterosexual or same-sex)
- boyfriends/girlfriends (heterosexual or same-sex)
- former marital partners - divorced spouses - former common-law spouses - separated spouses - former non-marital partners - former dates (heterosexual or same-sex)
- former boyfriends/girlfriends (heterosexual or same-sex) Intimate partners may be cohabiting, but need not be. The relationship need not involve sexual activities. If the victim and the perpetrator have a child in common but no current relationship, then by definition they fit in the category of former marital partners or former non-marital partners. States differ as to what constitutes a common-law marriage. Users of the "Recommended Data Elements" will need to know what qualifies as a common-law marriage in their state.

# Violence and Associated Terms
Violence is divided into four categories:
- Physical Violence - Sexual Violence - Threat of Physical or Sexual Violence
- Psychological/Emotional Abuse (including coercive tactics) when there has also been prior physical or sexual violence, or prior threat of physical or sexual violence.

# Physical Violence
The intentional use of physical force with the potential for causing death, disability, injury, or harm. Physical violence includes, but is not limited to: scratching, pushing, shoving, throwing, grabbing, biting, choking, shaking, poking, hairpulling, slapping, punching, hitting, burning, use of a weapon (gun, knife, or other object), and use of restraints or one's body, size, or strength against another person. Physical violence also includes coercing other people to commit any of the above acts.
Sex Act (or Sexual Act) Contact between the penis and the vulva or the penis and the anus involving penetration, however slight; contact between the mouth and the penis, vulva, or anus; or penetration of the anal or genital opening of another person by a hand, finger, or other object.

# Abusive Sexual Contact
Intentional touching directly, or through the clothing, of the genitalia, anus, groin, breast, inner thigh, or buttocks of any person against his or her will, or of any person who is unable to understand the nature or condition of the act, to decline participation, or to communicate unwillingness to be touched (e.g., because of illness, disability, or the influence of alcohol or other drugs, or due to intimidation or pressure).

# Sexual Violence
Sexual violence is divided into three categories:
- Use of physical force to compel a person to engage in a sexual act against his or her will, whether or not the act is completed.
- An attempted or completed sex act involving a person who is unable to understand the nature or condition of the act, to decline participation, or to communicate unwillingness to engage in the sexual act (e.g., because of illness, disability, or the influence of alcohol or other drugs, or due to intimidation or pressure).
- Abusive sexual contact.

# Threat of Physical or Sexual Violence
The use of words, gestures, or weapons to communicate the intent to cause death, disability, injury, or physical harm. Also the use of words, gestures, or weapons to communicate the intent to compel a person to engage in sex acts or abusive sexual contact when the person is either unwilling or unable to consent.
Examples: "I'll kill you"; "I'll beat you up if you don't have sex with me"; brandishing a weapon; firing a gun into the air; making hand gestures; reaching toward a person's breasts or genitalia.

# Psychological/Emotional Abuse
Trauma to the victim caused by acts, threats of acts, or coercive tactics, such as those on the following list. This list is not exhaustive. Other behaviors may be considered emotionally abusive if they are perceived as such by the victim. Some of the behaviors on the list may not be perceived as psychologically or emotionally abusive by all victims. Operationalization of data elements related to psychological/ emotional abuse will need to incorporate victim perception or a proxy for it. Although any psychological/emotional abuse can be measured by the IPV surveillance system, the expert panel recommended that it only be considered a type of violence when there has also been prior physical or sexual violence, or the prior threat of physical or sexual violence.- Thus by this criterion, the number of women experiencing acts, threats of acts, or coercive tactics that constitute psychological/emotional abuse may be greater than the number of women experiencing psychological/emotional abuse that can also be considered psychological/emotional violence.

# Violent Episode
A single act or series of acts of violence that are perceived to be connected to each other and that may persist over a period of minutes, hours, or days. A violent episode may involve single or multiple types of violence (e.g., physical violence, sexual violence, threat of physical or sexual violence, psychological/emotional abuse).

# Most Recent Violent Episode Perpetrated by Any Intimate Partner
For victims who have had only one violent intimate partner, the most recent violent episode perpetrated by that intimate partner; for victims who have had more than one violent intimate partner, the violent episode perpetrated most recently, by whichever one of those violent partners committed it. Thus, the most recent violent episode perpetrated by any intimate partner may have been perpetrated by someone other than the victim's current intimate partner. For example, if a woman has been victimized by both her ex-husband and her current boyfriend, questions about the most recent violent episode would refer to the episode involving whichever intimate partner victimized her most recently, not necessarily the one with whom she is currently in a relationship. - At the March 1996 meeting of the 12-member expert panel, participants discussed the importance of capturing these behaviors as one component of IPV. They also recognized that psychological/emotional abuse encompasses a range of behavior that, while repugnant, might not universally be considered violent. The panel made the decision to classify psychological/emotional abuse as a type of violence only when it occurs in the context of prior physical or sexual violence, or the prior threat of physical or sexual violence. The panel suggested that "prior" be operationalized as "within the past 12 months."

# Intimate Partner Violence Surveillance

# Pattern of Violence
The way that violence is distributed over time in terms of frequency, severity, or type of violent episode (i.e., physical violence, sexual violence, threat of physical or sexual violence, psychological/emotional abuse).

# Terms Associated with the Consequences of Violence

# Physical Injury
Any physical damage occurring to the body resulting from exposure to thermal, mechanical, electrical, or chemical energy interacting with the body in amounts or rates that exceed the threshold of physiological tolerance, or from the absence of such essentials as oxygen or heat.

# Disability
Impairment resulting in some restriction or lack of ability to perform an action or activity in the manner or within the range considered normal.

# Psychological Consequences
Consequences involving the mental health or emotional well-being of the victim.

# Medical Health Care
Treatment by a physician or other health care professional related to the physical health of the victim.

# Mental Health Care
Includes individual or group care by a psychiatrist, psychologist, social worker, or other counselor related to the mental health of the victim. It may involve inpatient or outpatient treatment. Mental health care excludes substance abuse treatment. It also excludes pastoral counseling, unless specifically related to the mental health of the victim.

# Substance Abuse Treatment
Treatment related to alcohol or other drug use by the victim.

# Uses
Ensures that entered or accessed records correspond with the proper victim. It also facilitates data linkage for administrative and research purposes.

# Discussion
To protect victim privacy and confidentiality, access to this data element must be limited to authorized personnel. Case ID may be assigned by the agency compiling IPV surveillance data, or it may be an identifier previously assigned by the contributing data source. Case ID may or may not be identical to the identifier created to allow linkage across multiple sources.

# Data Type (and Field Length)
CX -extended composite ID with check digit (20). See Technical Notes.

# Repetition
No.

# Field Values/Coding Instructions
Component 1 is the identifier. Component 2 is the check digit. Component 3 is the code indicating the check digit scheme employed. Components 4-6 are not used unless needed for local purposes.
Enter the primary identifier used by the facility to identify the victim in Component 1. If none or unknown is applicable, then enter "" or unknown in Component 1, and do not make entries in the remaining components. Components 2 and 3 are for optional use when a check digit scheme is employed.
Example, when M11 refers to the algorithm used to generate the check digit: Component 1 = 1234567 Component 2 = 6 Component 3 = M11

# Data Standards or Guidelines
Health Level 7 , Version 2.3 (HL7, 1996).

# Other References
None.

# Uses
Identifies the agency or organization that supplied data for this victim. It will enable linkage of multiple within-agency contacts for the same victim.

# Discussion
No single agency is likely to collect all of the data elements recommended. As a consequence, it is likely that anyone setting up a surveillance system will need to combine data from a number of sources (e.g., health care records and police records) using a relational database. This will allow information on data elements to be gathered from each data source used. The mechanics of how to set up relational databases are not discussed in this document, but information from the three funded state surveillance pilot projects should provide helpful information for developing such databases. A unique identifier will need to be created to allow for linkage across all data sources included. This identifier may or may not be identical to the data element 1.101 Case ID .

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions

# Data Standards or Guidelines
None.

# Other References
None.

# Discussion
It is possible that the victim will have contacts with an agency that precede agency recognition or documentation of IPV victimization or that precede other disclosure of IPV (e.g., women often wait to disclose violence to health care practitioners until they trust and feel comfortable with their providers). This data element reflects the date when the IPV victimization was first documented in the records of the agency providing data to the IPV surveillance system. If documentation of IPV results from routine screening or other disclosure, there may be no specific violent episode related to the date of documentation.
If there has been no agency documentation of IPV victimization prior to the most recent violent episode, then this data element will be identical with 4.103 Date of agency documentation of most recent violent episode .

# Data Type (and Field Length)
TS -time stamp (26).

# Repetition
No.

# Field Values/Coding Instructions
See the definition of TS in the Technical Notes at the end of this document.

# Data Standards or Guidelines
None.
Other References E1744-95 (ASTM, 1995.

# Uses
Can be used to calculate the victim's age, and to distinguish between victims with the same name.

# Discussion
If date of birth is not known, the year can be estimated from the victim's age.

# RACE OF VICTIM Description/Definition
Race of victim.

# Uses
Data on race are used in public health surveillance and in epidemiologic, clinical, and health services research.

# Discussion
For more than 20 years, the Federal government has promoted the use of a common language to promote uniformity and comparability of data on race and ethnicity for population groups. Development of the data standards stemmed in large measure from new responsibilities to enforce civil rights laws. Data were needed to monitor equal access in housing, education, employment, and other areas for populations that historically had experienced discrimination and differential treatment because of their race or ethnicity. The standards are used not only in the decennial census (which provides the data for the "denominator" for many measures), but also in household surveys, on administrative forms (e.g., school registration and mortgagelending applications), and in medical and other research. The categories represent a social-political construct designed for collecting data on the race and ethnicity of broad population groups in the United States.
Race is a concept used to differentiate population groups largely on the basis of physical characteristics transmitted by descent. Racial categories are neither precise nor mutually exclusive, and the concept of race lacks clear scientific definition. The common use of race in the United States draws upon differences not only in physical attributes, but also in ancestry and geographic origins. Since 1977, the Federal government has sought to standardize data on race and ethnicity among its agencies.  , 1997) was developed to meet Federal legislative and program requirements, and these standards are used widely in the public and private sectors. The directive provides five basic racial categories but states that the collection of race data need not be limited to these categories. However, any additional reporting that uses more detail must be organized in such a way that the additional categories can be aggregated into the five basic groups. Although the directive does not specify a method of determining an individual's race, OMB prefers self-identification to identification by an observer whenever possible. The directive states that persons of mixed racial origins should be coded using multiple categories, and not a multiracial category.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
Yes; if the agency providing the data to the IPV surveillance system uses multiple racial categories, the IPV surveillance system also allows for multiple racial categories to be coded.

# Uses
Data on ethnicity are used in public health surveillance and in epidemiologic, clinical, and health services research.

# Discussion
Ethnicity is a concept used to differentiate population groups on the basis of shared cultural characteristics or geographic origins. A variety of cultural attributes contribute to ethnic differentiation, including language, patterns of social interaction, religion, and styles of dress. However, ethnic differentiation is imprecise and fluid. It is contingent on a sense of group identity that can change over time and that involves subjective and attitudinal influences. Since 1977, the Federal government has sought to standardize data on race and ethnicity among its agencies.  , 1997) was developed to meet Federal legislative and program requirements, and these standards are used widely in the public and private sectors.
The directive provides two basic ethnic categories -Hispanic or Latino and Not of Hispanic or Latino Origin -but states that collection of ethnicity data need not be limited to these categories. However, any additional reporting that uses more detail must be organized in such a way that the additional categories can be aggregated into the two basic groups. OMB prefers that data on race and ethnicity be collected separately. The use of the Hispanic category in a combined race/ethnicity data element makes it impossible to distribute persons of Hispanic ethnicity by race and, therefore, reduces the utility of the five basic racial categories by excluding from them persons who would otherwise be included.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions

# Uses
Allows examination of the correspondence between the location of the victim's residence, the perpetrator's residence, and the location of the most recent violent episode perpetrated by any intimate partner, and may have implications for intervention strategies.

# Discussion
Additional information (e.g., street address, zip code) can easily be added as components of this element if data linkage across data sources is desired. However, to protect privacy and confidentiality, access to this level of detail must be limited to authorized personnel. The need for victim safety and confidentiality must be taken into account if the full extended version of this data element is used.
In conjunction with data elements 4.104 City, state, and county of occurrence and 4.305 City, state, and county of residence of perpetrator of most recent violent episode, this data element allows examination of the correspondence between the victim's residence, the perpetrator's residence, and the location of the most recent violent episode.

# Data Type (and Field Length)
XAD -extended address (106).

# Repetition
No.

# Field Values
Component 3 is the city. Component 4 is the state or province. Component 9 is the county/parish code.
Example: Component 3 = Lima Component 4 = OH Component 9 = 019
The state or province code entered in Component 4 should be entered as a twoletter postal abbreviation. The county/parish code should be entered in Component 9 as the 3-digit Federal Information Processing Standards code. See XAD -extended address in the Technical Notes at the end of this document for additional information on other possible components of this data element. The numbering of these components (3, 4, and 9) is consistent with the numbering of components used elsewhere for full XAD coding.

# Data Standards or Guidelines
Health Level 7, Version 2.3 (HL7, 1996).

# Other References
None.
Victim Demographics 31 2.106

# MARITAL STATUS OF VICTIM Description/Definition
Victim's legal marital status at the time when the agency providing data to the IPV surveillance system first documented IPV victimization for this person.

# Uses
Risk of victimization may vary by legal marital status. Marital status may change over the course of a relationship, particularly a violent relationship. For consistency, we recommend recording the victim's marital status at the time the agency providing data to the IPV surveillance system first documented IPV victimization for this person.

# Discussion
Some unmarried partners may be cohabiting. In some states this may qualify as common-law marriage. See also data element 4.108 Cohabitation of victim and perpetrator.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions

# VICTIM'S EXPERIENCE OF IPV
There is variability in how intimate partner violence has been conceptualized, with some researchers combining physical violence, sexual violence, threat of physical or sexual violence, and psychological/emotional abuse, while others treat these as discrete categories. Because prevention strategies for different types of violence may differ, we suggest separating these categories for surveillance purposes.
We recognize, however, that multiple types of violence may occur in a single episode. The IPV surveillance system is designed to record each type of violence that occurs to a given victim, even if multiple types occur within a single episode. Thus, these data elements can provide a count of episodes involving several types of violence, but cannot provide a count of the total number of discrete violent episodes, nor can they provide information about the cooccurrence of different types of violence within each episode. However, data element 4.101 Type(s) of violence in most recent episode does allow collection of such information for the most recent violent episode perpetrated by any intimate partner.

# S E C T I O N PHYSICAL VIOLENCE
Physical violence is the intentional use of physical force with the potential for causing death, disability, injury, or harm. Physical violence includes, but is not limited to: scratching, pushing, shoving, throwing, grabbing, biting, choking, shaking, poking, hair-pulling, slapping, punching, hitting, burning, use of a weapon (gun, knife, or other object), and use of restraints or one's body, size, or strength against another person.
Physical violence also includes coercing other people to commit any of the above acts.
Physical

# Uses
This data element allows differentiation of physical violence from sexual violence, threat of physical or sexual violence, or psychological/emotional abuse.

# Discussion
This data element cannot provide a count of the total number of discrete violent episodes, nor can it provide information about the co-occurrence of different types of violence within each episode. However, data element 4.101 Type(s) of violence in most recent episode does allow collection of such information for the most recent violent episode perpetrated by any intimate partner.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions

# Code Description 0
No known episodes occurred involving physical violence by any intimate partner ever. 1
Physical violence occurred by any intimate partner ever. 9
Unknown if physical violence occurred by any intimate partner ever.
If any episode of physical violence also involved other types of violence (sexual violence, threat of physical or sexual violence, or psychological/emotional abuse), the episode should be recorded in data elements for each of those types of violence, as well as being recorded for physical violence.

# Data Standards or Guidelines
None.

# Other References
None.

# Uses
Provides a measure of the total frequency of episodes involving physical violence by any intimate partner ever.

# Discussion
Recall that the definition of a violent episode is "A single act or series of acts of violence that are perceived to be connected to each other, and that may persist over a period of minutes, hours, or days. A violent episode may involve single or multiple types of violence (e.g., physical violence, sexual violence, threat of physical or sexual violence, psychological/emotional abuse)."

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No. If, for the data element 3.101 Physical violence by any intimate partner ever, there was a response of "0" (No known physical violence occurred by any intimate partner ever) or "9" (Unknown if physical violence occurred by any intimate partner ever), then this data element should not be used.

# Field Values/Coding Instructions
If there has been more than one physically violent intimate partner, the code should reflect the total of all episodes involving physical violence for all of those partners.

# Data Standards or Guidelines
None.

# Other References
None.

# Uses
Provides a measure of the frequency of episodes of physical violence by any intimate partner during the past 12 months.

# Discussion
Recall that the definition of a violent episode is "A single act or series of acts of violence that are perceived to be connected to each other, and that may persist over a period of minutes, hours, or days. A violent episode may involve single or multiple types of violence (e.g., physical violence, sexual violence, threat of physical or sexual violence, psychological/emotional abuse)."

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No. More than 10 episodes occurred involving physical violence by any intimate partner in the 12 months prior to the date the agency providing data to the IPV surveillance system first documented IPV victimization for this person. 9

# Field Values/Coding Instructions
Unknown how many episodes occurred involving physical violence by any intimate partner in the 12 months prior to the date the agency providing data to the IPV surveillance system first documented IPV victimization for this person.
If, for the data element 3.101 Physical violence by any intimate partner ever, there was a response of "0" (No physical violence occurred by any intimate partner ever) or "9" (Unknown if physical violence occurred by any intimate partner ever), then this data element should not be used.
If more than one intimate partner was physically violent in the 12 months prior to the date the agency providing data to the IPV surveillance system first documented IPV victimization for this person, the code for this data element should reflect the total of all episodes involving physical violence for all of those partners.

# Data Standards or Guidelines
None.

# Other References
None.

# Uses
Provides a measure of the frequency of episodes involving physical violence by the perpetrator of the most recent violent episode during the past 12 months.

# Discussion
Although the IPV surveillance system cannot provide information about the co-occurrence of different types of violence within episodes, this data element and other data elements related to the perpetrator of the most recent violent episode do provide information about the past perpetration of each type of violence by a single violent intimate partner. See also the data elements: 3.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions

# Code Description 0
No known episodes occurred involving physical violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode. 1
1-2 episodes occurred involving physical violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode. 2 3-5 episodes occurred involving physical violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode. 3 6-10 episodes occurred involving physical violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode. 4
More than 10 episodes occurred involving physical violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode. 9
Unknown how many episodes occurred involving physical violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode.
If, for the data element 3.101 Physical violence by any intimate partner ever, there is a response of "0" (No physical violence occurred by any intimate partner ever) or "9" (Unknown if physical violence occurred by any intimate partner ever), then this data element should not be used.
The code should only reflect the total of all episodes involving physical violence against the victim by the perpetrator of the most recent violent episode. The perpetrator of the most recent violent episode may have used any type of violence in that episode. Thus, it is possible that person did not perpetrate physical violence in the 12 months prior to the date of the most recent violent episode, even though another intimate partner did perpetrate physical violence against the victim in that same 12-month period.

# Data Standards or Guidelines
None.

# Other References
None.

# S E C T I O N

# SEXUAL VIOLENCE
A sex act (or sexual act) is contact between the penis and the vulva or the penis and the anus involving penetration, however slight; contact between the mouth and the penis, vulva, or anus; or penetration of the anal or genital opening of another person by a hand, finger, or other object.
Abusive sexual contact is intentional touching directly, or through the clothing, of the genitalia, anus, groin, breast, inner thigh, or buttocks of any person against his or her will, or of any person who is unable to understand the nature or condition of the act, to decline participation, or to communicate unwillingness to be touched (e.g., because of illness, disability, or the influence of alcohol or other drugs, or due to intimidation or pressure).
Sexual violence is divided into three categories: (1) Use of physical force to compel a person to engage in a sexual act against his or her will, whether or not the act is completed; (2) An attempted or completed sex act involving a person who is unable to understand the nature or condition of the act, to decline participation, or to communicate unwillingness to engage in the sexual act, e.g., because of illness, disability, or the influence of alcohol or other drugs, or due to intimidation or pressure; (3) Abusive sexual contact.
Sexual

# Uses
Allows differentiation of sexual violence from physical violence, threat of physical or sexual violence, or psychological/emotional abuse.

# Discussion
This data element cannot provide a count of the total number of discrete violent episodes, nor can it provide information about the co-occurrence of different types of violence within each episode. However, data element 4.101 Type(s) of violence in most recent episode does allow collection of such information for the most recent violent episode perpetrated by any intimate partner.
Because the definition of sexual violence includes three distinct categories, the codes allow information to be collected separately for each of the categories.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
Yes, if more than one type of sexual violence occurred.

# Field Values/Coding Instructions
If any episode of sexual violence also involved other types of violence (physical violence, threat of physical or sexual violence, or psychological/emotional abuse), the episode should be recorded in data elements for each of those types of violence, as well as being recorded for sexual violence.
If the response is code "9" (Unknown if any category of sexual violence occurred by any intimate partner ever), then codes "2," "4," and "6" should not be used.

# Data Standards or Guidelines
None.

# Other References
None.

# Uses
Provides a measure of the total frequency of episodes involving sexual violence by any intimate partner ever.

# Discussion
Recall that the definition of a violent episode is "A single act or series of acts of violence that are perceived to be connected to each other, and that may persist over a period of minutes, hours, or days. A violent episode may involve single or multiple types of violence (e.g., physical violence, sexual violence, threat of physical or sexual violence, psychological/emotional abuse)."
Although the definition of sexual violence includes three distinct categories, the codes here combine information across the three categories.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No. More than 10 episodes occurred involving sexual violence by any intimate partner ever. 9

# Field Values/Coding Instructions
Unknown how many episodes occurred involving sexual violence by any intimate partner ever.
If, for the data element 3.201 Sexual violence by any intimate partner ever, there is a response of "0" (No known sexual violence occurred by any intimate partner ever) or "9" (Unknown if any category of sexual violence occurred by any intimate partner ever), then this data element should not be used.
If there has been more than one sexually violent intimate partner, the code should reflect the total of all episodes involving sexual violence for all of those partners.

# Data Standards or Guidelines
None.

# Other References
None.

# Uses
Provides a measure of the frequency of episodes involving sexual violence by any intimate partner during the past 12 months.

# Discussion
Recall that the definition of a violent episode is "A single act or series of acts of violence that are perceived to be connected to each other, and that may persist over a period of minutes, hours, or days. A violent episode may involve single or multiple types of violence (e.g., physical violence, sexual violence, threat of physical or sexual violence, psychological/emotional abuse)."
Although the definition of sexual violence includes three distinct categories, the codes here combine information across the three categories.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No. If, for the data element 3.201 Sexual violence by any intimate partner ever, there is a response of "0" (No known sexual violence occurred by any intimate partner ever) or "9" (Unknown if sexual violence occurred by any intimate partner ever), then this data element should not be used.

# Field Values/Coding Instructions
If more than one intimate partner was sexually violent in the 12 months prior to the date the agency providing data to the IPV surveillance system first documented IPV victimization for this person, the code for this data element should reflect the total of all episodes involving sexual violence for all of those partners.

# Data Standards or Guidelines
None.

# Other References
None.

# Uses
Provides a measure of the frequency of episodes involving sexual violence by the perpetrator of the most recent violent episode during the past 12 months.

# Discussion
Although the IPV surveillance system cannot provide information about the cooccurrence of different types of violence within episodes, this data element and other data elements related to the perpetrator of the most recent violent episode do provide information about the past perpetration of each type of violence by a single violent intimate partner. See also the data elements: 3. Although the definition of sexual violence includes three distinct categories, the codes here combine information across the three categories.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions

# Code Description 0
No known episodes occurred involving sexual violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode. 1
1-2 episodes occurred involving sexual violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode. 2 3-5 episodes occurred involving sexual violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode. 3 6-10 episodes occurred involving sexual violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode. 4
More than 10 episodes occurred involving sexual violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode.
Unknown how many episodes occurred involving sexual violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode.
If, for the data element 3.201 Sexual violence by any intimate partner ever, there is a response of "0" (No known sexual violence occurred by any intimate partner ever) or "9" (Unknown if sexual violence occurred by any intimate partner ever), then this data element should not be used.
The code should only reflect the total of all episodes involving sexual violence against the victim by the perpetrator of the most recent violent episode. The perpetrator of the most recent violent episode may have used any type of violence. Thus, it is possible that person did not perpetrate sexual violence in the 12 months prior to the date of the most recent violent episode, even though another intimate partner did perpetrate sexual violence against the victim in that same 12-month period.

# Data Standards or Guidelines
None.

# Other References
None.

# S E C T I O N THREAT OF PHYSICAL OR SEXUAL VIOLENCE
Threat of physical or sexual violence is the use of words, gestures, or weapons to communicate the intent to cause death, disability, injury, or physical harm. Also the use of words, gestures, or weapons to communicate the intent to compel a person to engage in sex acts or abusive sexual contact when the person is either unwilling or unable to consent.
Examples: "I'll kill you"; "I'll beat you up if you don't have sex with me"; brandishing a weapon; firing a gun into the air; making hand gestures; reaching toward a person's breasts or genitalia.
Threat

# Uses
Allows differentiation of threat of physical or sexual violence from the occurrence of physical violence, sexual violence, or psychological/emotional abuse.

# Discussion
This data element cannot provide a count of the total number of discrete violent episodes, nor can it provide information about the co-occurrence of different types of violence within each episode. However, data element 4.101 Type(s) of violence in most recent episode does allow collection of such information for the most recent violent episode perpetrated by any intimate partner.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions

# Code Description 0
No known threat of physical or sexual violence occurred by any intimate partner ever. 1
Threat of physical or sexual violence occurred by any intimate partner ever. 9
Unknown if threat of physical or sexual violence occurred by any intimate partner ever.
If any episode of threat of physical or sexual violence also involved other types of violence (physical violence, sexual violence, or psychological/emotional abuse), the episode should be recorded in data elements for each of those types of violence, as well as being recorded for threat of physical or sexual violence.

# Data Standards or Guidelines
None.

# Other References
None.

# NUMBER OF EPISODES INVOLVING THREAT OF PHYSICAL OR SEXUAL VIOLENCE BY ANY INTIMATE PARTNER EVER Description/Definition
Number of episodes, ever in the victim's life, involving threat of physical or sexual violence by any intimate partner.

# Uses
Provides a measure of the total frequency of episodes involving the threat of physical or sexual violence by any intimate partner ever.

# Discussion
Recall that the definition of a violent episode is "A single act or series of acts of violence that are perceived to be connected to each other, and that may persist over a period of minutes, hours, or days. A violent episode may involve single or multiple types of violence (e.g., physical violence, sexual violence, threat of physical or sexual violence, psychological/emotional abuse)."

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No. More than 10 episodes occurred involving threat of physical or sexual violence by any intimate partner ever. 9

# Field Values/Coding Instructions
Unknown how many episodes occurred involving threat of physical or sexual violence by any intimate partner ever.
If, for the data element 3.301 Threat of physical or sexual violence by any intimate partner ever, there is a response of "0" (No known threat of physical or sexual violence occurred by any intimate partner ever) or "9" (Unknown if threat of physical or sexual violence occurred by any intimate partner ever), then this data element should not be used.
If more than one intimate partner has threatened physical or sexual violence, the code should reflect the total of all episodes involving threat of physical or sexual violence for all of those partners.

# Data Standards or Guidelines
None.

# Other References
None.

# Uses
Provides a measure of the frequency of episodes involving threat of physical or sexual violence by any intimate partner during the past 12 months.

# Discussion
Recall that the definition of a violent episode is "A single act or series of acts of violence that are perceived by the victim to be connected to each other, and that may persist over a period of minutes, hours, or days. A violent episode may involve single or multiple types of violence (e.g., physical violence, sexual violence, threat of physical or sexual violence, psychological/emotional abuse)."

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No. More than 10 episodes occurred involving threat of physical or sexual violence by any intimate partner in the 12 months prior to the date the agency providing data to the IPV surveillance system first documented IPV victimization for this person. 9

# Field Values/Coding Instructions
Unknown how many episodes occurred involving threat of physical or sexual violence by any intimate partner in the 12 months prior to the date the agency providing data to the IPV surveillance system first documented IPV victimization for this person.
If, for the data element 3.301 Threat of physical or sexual violence by any intimate partner ever, there is a response of "0" (No known threat of physical or sexual violence occurred by any intimate partner ever) or "9" (Unknown if threat of physical or sexual violence occurred by any intimate partner ever), then this data element should not be used.
If more than one intimate partner threatened physical or sexual violence in the 12 months prior to the date the agency providing data to the IPV surveillance system first documented IPV victimization for this person, the code for this data element should reflect the total of all episodes involving threat of physical or sexual violence for all of those partners.

# Data Standards or Guidelines
None.

# Other References
None.

# Uses
Provides a measure of the frequency of episodes involving threat of physical or sexual violence by the perpetrator of the most recent violent episode during the past 12 months.

# Discussion
Although the IPV surveillance system cannot provide information about the cooccurrence of different types of violence within episodes, this data element and other data elements related to the perpetrator of the most recent violent episode do provide information about the past perpetration of each type of violence by a single violent intimate partner. See also the data elements: 3.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions

# Code Description 0
No known episodes occurred involving threat of physical or sexual violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode. 1 1-2 episodes occurred involving threat of physical or sexual violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode. 2 3-5 episodes occurred involving threat of physical or sexual violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode. 3 6-10 episodes occurred involving threat of physical or sexual violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode. 4
More than 10 episodes occurred involving threat of physical or sexual violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode. 9
Unknown how many episodes occurred involving threat of physical or sexual violence by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode.
If, for the data element 3.301 Threat of physical or sexual violence by any intimate partner ever, there is a response of "0" (No known threat of physical or sexual violence occurred by any intimate partner ever) or "9" (Unknown if threat of physical or sexual violence occurred by any intimate partner ever), then this data element should not be used.
The code should only reflect the total of all episodes involving threat of physical or sexual violence against the victim by the perpetrator of the most recent violent episode. The perpetrator of the most recent violent episode may have used any type of violence in that episode. Thus, it is possible that person did not threaten physical or sexual violence in the 12 months prior to the date of the most recent violent episode, even though another intimate partner did threaten physical or sexual violence against the victim in that same 12-month period.

# Data Standards or Guidelines
None.

# Other References
None.

# S E C T I O N PSYCHOLOGICAL/EMOTIONAL ABUSE
Psychological or emotional abuse involves trauma to the victim caused by acts, threats of acts, or coercive tactics, such as those listed below. This list is not exhaustive. Other behaviors may be considered emotionally abusive if they are perceived as such by the victim. Some of the behaviors on the list may not be perceived as psychologically or emotionally abusive by all victims. Operationalization of data elements related to psychological/emotional abuse will need to incorporate victim perception or a proxy for it. Although any psychological/ emotional abuse can be measured by the IPV surveillance system, the expert panel recommended that it only be considered a type of violence when there has also been prior physical or sexual violence, or the prior threat of physical or sexual violence.- Thus by this criterion, the number of women experiencing acts, threats of acts, or coercive tactics that constitute psychological/emotional abuse may be greater than the number of women experiencing psychological/emotional abuse that can also be considered psychological/emotional violence.
Psychological/emotional abuse can include, but is not limited to:
Humiliating They also recognized that psychological/emotional abuse encompasses a range of behavior that, while repugnant, might not universally be considered violent. The panel made the decision to classify psychological/emotional abuse as a type of violence only when it occurs in the context of prior physical or sexual violence, or the prior threat of physical or sexual violence. The panel suggested that "prior" be operationalized as "within the past 12 months."

# PSYCHOLOGICAL/EMOTIONAL ABUSE BY ANY INTIMATE PARTNER EVER Description/Definition
Occurrence, ever in the victim's life, of psychological/emotional abuse by any intimate partner.

# Uses
Allows differentiation of psychological/emotional abuse from physical violence, sexual violence, or threat of physical or sexual violence.

# Discussion
This data element cannot provide a count of the total number of discrete violent episodes, nor can it provide information about the co-occurrence of different types of violence within each episode. However, data element 4.101 Type(s) of violence in most recent episode, does allow collection of such information for the most recent violent episode perpetrated by any intimate partner.

# PSYCHOLOGICAL/EMOTIONAL ABUSE IN THE PAST 12 MONTHS BY ANY INTIMATE PARTNER Description/Definition
Occurrence of psychological/emotional abuse by any intimate partner (current or former) in the 12 months prior to the date the agency providing data to the IPV surveillance system first documented IPV victimization for this person.

# Uses
Indicates the victim's experience of psychological/emotional abuse over the past 12 months.

# Discussion
Psychological/emotional abuse is frequently pervasive and chronic. Unlike the data elements related to violent episodes involving physical violence, sexual violence, or threat of physical or sexual violence perpetrated by any intimate partner in the past 12 months, this data element specifies if the victim felt psychologically abused, rather than counting the number of episodes that occurred.

# PROPORTION OF TIME VICTIM FELT PSYCHOLOGICALLY/EMOTIONALLY ABUSED IN THE PAST 12 MONTHS BY PERPETRATOR OF MOST RECENT VIOLENT EPISODE Description/Definition
Proportion of time the victim felt psychologically/emotionally abused by the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode.

# Uses
Provides a measure of the extent to which the victim felt psychologically or emotionally abused by the perpetrator of the most recent violent episode during the past 12 months. Can be used as a proxy for the severity of psychological/emotional abuse.

# Discussion
Because psychological/emotional abuse is often pervasive and chronic, this data element indicates the proportion of time the victim felt psychologically/ emotionally abused over the past 12 months, rather than counting the frequency of psychologically or emotionally abusive acts or episodes.
Although the IPV surveillance system cannot provide information about the cooccurrence of different types of violence within episodes, this data element and other data elements related to the perpetrator of the most recent violent episode provide information about the past perpetration of each type of violence by a single violent intimate partner. See also the following data elements: 3.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions
Code Description 0
The victim was known not to feel psychologically/emotionally abused by the perpetrator of the most recent violent episode during the 12 months prior to the date of the most recent violent episode. 1
The victim felt psychologically/emotionally abused by the perpetrator of the most recent violent episode some of the time during the 12 months prior to the date of the most recent violent episode. 2
The victim felt psychologically/emotionally abused by the perpetrator of the most recent violent episode most of the time during the 12 months prior to the date of the most recent violent episode. 3
The victim felt psychologically/emotionally abused by the perpetrator of the most recent violent episode all of the time during the 12 months prior to the date of the most recent violent episode.
It is unknown what proportion of time the victim felt psychologically/ emotionally abused by the perpetrator of the most recent violent episode during the 12 months prior to the date of the most recent violent episode.
If, for the data element 3.401 Psychological/emotional abuse by any intimate partner ever, there is a response of "0" (No known psychological/emotional abuse occurred by any intimate partner ever) or "9" (Unknown if psychological/emotional abuse occurred by any intimate partner ever), then this data element should not be used.
The code should only reflect the proportion of time the victim felt psychologically/ emotionally abused by the perpetrator of the most recent violent episode. The perpetrator of the most recent violent episode may have used any type of violence. Thus, it is possible that person did not perpetrate psychological/emotional abuse in the 12 months prior to the date of the most recent violent episode, even though another intimate partner did perpetrate psychological/emotional abuse of the victim in that same 12-month period.

# Data Standards or Guidelines
None.

# Other References
None.

# S E C T I O N

# MOST RECENT VIOLENT EPISODE PERPETRATED BY ANY INTIMATE PARTNER
A violent episode is a single act or series of acts of violence that are perceived to be connected to each other and that may persist over a period of minutes, hours, or days. A violent episode may involve single or multiple types of violence (e.g., physical violence, sexual violence, threat of physical or sexual violence, psychological/emotional abuse).
For victims who have had only one violent intimate partner, the most recent violent episode perpetrated by any intimate partner refers to the most recent violent episode perpetrated by that intimate partner. For victims who have had more than one violent intimate partner, the most recent violent episode perpetrated by any intimate partner refers to the violent episode perpetrated most recently by whichever one of those violent intimate partners committed it. Thus, the most recent violent episode perpetrated by any intimate partner may have been perpetrated by someone other than the victim's current intimate partner. For example, if a woman has been victimized by both her ex-husband and her current boyfriend, questions about the most recent violent episode would refer to the episode involving whichever intimate partner victimized her most recently, not necessarily the one with whom she is currently in a relationship.

# Uses
Identifies all the types of violence that occurred in the most recent violent episode.

# Discussion
Although the IPV surveillance system cannot provide information about the cooccurrence of different types of violence across multiple violent episodes, this data element, by use of repeated coding, does provide information about each type of violence in the most recent violent episode perpetrated by any violent intimate partner.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
Yes, to record each type of violence. If it is explicitly known that the most recent violent episode did not involve any one type of violence (i.e., physical violence, sexual violence, threat of physical or sexual violence, or psychological/emotional abuse), there is no need to code this information because non-occurrence of that type of violence is implicit in the coding scheme.

# Field Values/Coding Instructions

# Data Standards or Guidelines
None.

# Other References
None.

# DATE OF MOST RECENT VIOLENT EPISODE Description/Definition
Date when the most recent violent episode by any intimate partner ended.

# Uses
Can be used in conjunction with 2.101 Birth date of victim to calculate the victim's age at the time of the most recent violent episode.
This data element can also be used in conjunction with 4.103 Date of agency documentation of most recent violent episode to calculate the length of time between the occurrence of the violent episode and the time of agency contact.

# Discussion
This data element provides information about the recency of the intimate partner violence, regardless of what form the violent episode took (e.g., physical violence, sexual violence, threat of physical or sexual violence, or psychological/emotional abuse).

# S E C T I O N

# CONSEQUENCES TO VICTIM FOLLOWING MOST RECENT VIOLENT EPISODE
Physical injury is any physical damage occurring to the body resulting from exposure to thermal, mechanical, electrical, or chemical energy interacting with the body in amounts or rates that exceed the threshold of physiological tolerance, or from the absence of such essentials as oxygen or heat.
Disability is impairment resulting in some restriction or lack of ability to perform an action or activity in the manner or within the range considered normal.
Psychological consequences involve the mental health or emotional wellbeing of the victim.
Medical health care is treatment by a physician or other health care professional related to the physical health of the victim.

# PHYSICAL CONSEQUENCES TO VICTIM Description/Definition
The physical consequences to the victim attributed to the most recent violent episode, perpetrated by any intimate partner, by the agency providing data to the IPV surveillance system.

# Uses
Documents pregnancy, spontaneous abortion, sexually transmitted disease, HIV infection, physical injuries, disability, or fatality resulting from the most recent IPV episode.

# Discussion
It is conceivable that there are other physical consequences of the violence. This data element documents only those consequences that are recognized.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
Yes, if the victim suffered more than one physical consequence.

# Field Values/Coding Instructions

# MEDICAL CARE RECEIVED BY VICTIM Description/Definition
The medical health care received by the victim following the most recent violent episode perpetrated by any intimate partner.

# Uses
Documents the medical health care received by the victim.

# Discussion
In addition to documenting the victim's medical care, this data element can be used as a proxy for injury severity, but it must be used in conjunction with data element 4.201 Physical consequences to victim to identify those victims who died prior to or during the course of receiving any medical health care.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions
Code Description 0
The victim was known not to have received any medical health care following the most recent violent episode perpetrated by any intimate partner. 1
The victim received outpatient medical treatment (e.g., emergency room or physician office visit), not followed by inpatient medical health care, after the most recent violent episode perpetrated by any intimate partner.
The victim received outpatient medical treatment (e.g., emergency room or physician office visit), followed by inpatient medical health care, after the most recent violent episode perpetrated by any intimate partner. 3
The victim received outpatient medical treatment (e.g., emergency room or physician office visit), unknown if followed by inpatient medical health care, after the most recent violent episode perpetrated by any intimate partner. 4
The victim received no outpatient medical health care (e.g., emergency room or physician office visit), but did receive inpatient medical health care, after the most recent violent episode perpetrated by any intimate partner. 5
Unknown if the victim received outpatient medical health care (e.g., emergency room or physician office visit), but did receive inpatient medical health care, after the most recent violent episode perpetrated by any intimate partner. 9
Unknown if the victim received any medical health care following the most recent violent episode perpetrated by any intimate partner.
If the data element 4.201 Physical consequences to victim was coded "7" (Death occurred or fatal injuries received during most recent violent episode perpetrated by any intimate partner), then this data element should be used to indicate any medical care related to the most recent violent episode that the victim received following the violent episode prior to death. This data type is composed of two parallel triplets, each of which specifies a coded identifier, a corresponding text descriptor, and a designation for the coding system from which the coded identifier is taken. The CE data type permits use of different coding systems to encode the same data. Components 1-3 comprise a triplet for the first code, and Components 4-6 comprise a triplet for the alternate code. For example, in the coding system used in this document, the code "3" (6-10 episodes) for data element 3.202 Number of episodes involving sexual violence by any intimate partner ever is coded:
3^6-10 episodes An entry "" or Unknown in Component 1, without entries in other components, indicates that the value for the entire data element is null or unknown.

# CX -extended composite ID with check digit
Components:
^^^ This data type is used for certain fields that commonly contain check digits (e.g., internal agency identifier indicating a specific person, such as a patient or client). Component 1 contains an alphanumeric identifier. The check digit entered in Component 2 is an integral part of the identifier but is not included in Component 1. Component 3 identifies the algorithm used to generate the check digit. Component 4, , is the unique name of the system that created the identifier. Component 5, , is a code for the identifier type, such as MR for medical record number (see Table 0203 in HL7, Version 2.3). Component 6, , is the place or location where the identifier was first assigned to the individual (e.g., University Hospital).

# NM -numeric
An entry into a field of this data type is a number represented by a series of ASCII numeric characters consisting of an optional leading sign (+ or -), one or more digits, and an optional decimal point. In the absence of a + or -sign, the number is assumed to be positive. Leading zeros, or trailing zeros after a decimal point, are not meaningful. The only nonnumeric characters allowed are the optional leading sign and decimal point. A data element of this type is string data that contains the date and time of an event. YYYY is the year, MM is the month, and DD is the day of the month. Missing values are values that are either not sought or not recorded. In a computerized system, missing values should always be identifiable and distinguished from unknown or null values. Typically, no keystrokes are made, and as a result alphanumeric fields remain as default characters (most often blanks) and numeric fields are identifiable as never having had entries.

# TS -time stamp
Unknown values are values that are recorded to indicate that information was sought and found to be unavailable. Various conventions are used to enter unknown values: the word "Unknown" or a single character value (9 or U) for the CE -coded element data type; 99 for two or more unknown digits for the TS -time stamp data type; and 9 or a series of 9s for the NM -numeric data type. Note: the use of Unknown, U, and 9s in this document to represent values that are not known is an arbitrary choice. Other notations may be used for unknown value entries.
Null values are values that represent none or zero or that indicate specific properties are not measured. For alphanumeric fields, the convention of entering "" in the field is recommended to represent none (e.g., no telephone number), and the absence of an inquiry requires no data entry (e.g., not asking about a telephone number results in missing data). For numeric fields, the convention of entering 8 or a series of 8s is recommended to denote that a measurement was not made, preserving an entry of zero for a number in the measurement continuum. Note: the use of "" and 8s in this document to represent null values is an arbitrary choice. Other notations may be used for null value entries.
Null or unknown values in multicomponent data types (i.e., CE, CX, and XAD) are indicated in the first alphanumeric component. For example, in an XAD data type, "" or Unknown would be entered in the  component to indicate there was no address or that the address was not known, and no data would be entered in the remaining components.
Data Elements and Components That Are Not Applicable. Data entry is not required in certain fields when the data elements or their components do not pertain (e.g., victim's pregnancy status would not be applicable to male victims). Skip patterns should be used as needed to reduce data entry burdens.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions

# Code Description 0
No known psychological/emotional abuse occurred by any intimate partner ever. 1
Psychological/emotional abuse occurred by any intimate partner ever. 9
Unknown if psychological/emotional abuse occurred by any intimate partner ever.
If any episode of psychological/emotional abuse also involved other types of violence (physical violence, sexual violence, or threat of physical or sexual violence), the episode should be recorded for each of those types of violence, as well as being recorded for psychological/emotional abuse.

# Data Standards or Guidelines
None.

# Other References
None.
Data Type (and Field Length) .

# Repetition
No.

# Field Values/Coding Instructions

# Code Description 0
No known psychological/emotional abuse occurred by any intimate partner in the 12 months prior to the date the agency providing data to the IPV surveillance system first documented IPV victimization for this person. 1
Psychological/emotional abuse occurred by any intimate partner in the 12 months prior to the date the agency providing data to the IPV surveillance system first documented IPV victimization for this person. 9
Unknown if psychological/emotional abuse occurred by any intimate partner in the 12 months prior to the date the agency providing data to the IPV surveillance system first documented IPV victimization for this person.
If, for data element 3.401Psychological/emotional abuse by any intimate partner ever, there is a response of "0" (No known psychological/emotional abuse occurred by any intimate partner ever) or "9" (Unknown if psychological/emotional abuse occurred by any intimate partner ever), then this data element should not be used.

# Data Standards or Guidelines
None.

# Other References
None.

# Data Type (and Field Length)
TS-time stamp (26).

# Repetition
No.

# Field Values/Coding Instructions
Year, month, and day are entered in the format YYYYMMDD. For example, the date June 7, 1999, would be encoded as 19990607. See also TS in the Technical Notes at the end of this document.
Data Standards or Guidelines E1384-96 (ASTM, 1996 and Health Level 7, Version 2.3 (HL7, 1996).

# Other References
None.

# Details of Most Recent Violent Episode

# DATE OF AGENCY DOCUMENTATION OF MOST RECENT VIOLENT EPISODE Description/Definition
The date when the most recent violent episode perpetrated by any intimate partner was first documented by the agency providing data to the IPV surveillance system.

# Uses
Can be used in conjunction with data element 2.101 Birth date of victim to calculate the victim's age at the time of agency documentation of IPV victimization after the most recent violent episode perpetrated by any intimate partner.
Some research suggests that there may be a substantial delay between the occurrence of a violent episode and agency contact related to the violent episode. This data element allows measurement of the length of the delay between the violent episode and the agency documentation following that episode. It can be compared with data element 4.102 Date of most recent violent episode to calculate the length of time between the time the violent episode ended and the time of agency documentation.

# Discussion
Data element 1.103 Date of first agency documentation records the date when the agency providing data to the IPV surveillance system first documented IPV victimization for this person, whereas data element 4.103 Date of agency documentation of most recent violent episode records agency documentation of the most recent violent episode.
If there has been no agency documentation of IPV victimization prior to the most recent violent episode, then this data element will be identical with 1.103 Date of first agency documentation.

# Data Type (and Field Length)
TS-Time Stamp (26).

# Repetition
No.

# Field Values/Coding Instructions
See the definition of TS in the Technical Notes at the end of this document.

# Data Standards or Guidelines
None.
Other References E1744-95 (ASTM, 1995.

# Uses
Allows examination of the correspondence between the location of the victim's residence, the perpetrator's residence, and the location of the most recent violent episode perpetrated by any intimate partner, and may have implications for intervention strategies.

# Discussion
Additional information (e.g., street address, zip code) can easily be added as components of this element if data linkage across data sources is desired. However, to protect privacy and confidentiality, access to this level of detail must be limited to authorized personnel. Surveillance system users who do not convert street address to census block groups or encrypt addresses need to be aware that they may be acquiring the victim's street address when they acquire the street address of the place of occurrence of the most recent violent episode perpetrated by any intimate partner. The need for victim safety and confidentiality must be taken into account if the full extended version of this data element is used.
In conjunction with data elements 2.105 City, state, and county of victim's residence and 4.305 City, state, and county of residence of perpetrator of most recent violent episode, this data element allows examination of the correspondence between the victim's residence, the perpetrator's residence, and the location of the most recent violent episode.

# Data Type (and Field Length)
XAD -extended address (106).

# Repetition
No.

# Field Values/Coding Instructions
Component 3 is the city. Component 4 is the state or province. Component 9 is the county/parish code.
The state or province code entered in Component 4 should be entered as a twoletter postal abbreviation. The county/parish code should be entered in Component 9 as the 3-digit Federal Information Processing Standards code. See XAD -extended address in the Technical Notes at the end of this document for additional information on other possible components of this data element. The numbering of these components (3, 4, and 9) is consistent with the numbering of components used elsewhere for full XAD coding.

# Details of Most Recent Violent Episode 75

# Data Standards or Guidelines
Health Level 7, Version 2.3 (HL7, 1996).

# Other References
None.
Intimate Partner Violence Surveillance

# VICTIM'S PREGNANCY STATUS Description/Definition
The victim's pregnancy status at the time of the most recent violent episode perpetrated by any intimate partner.

# Uses
May assist in determining differential risk.

# Discussion
There is a growing literature about the association of violence and pregnancy, but it is as yet unclear if pregnancy increases or decreases the risk of violence.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions
Code Description 0
Victim was not pregnant at the time of most recent violent episode. 1
Victim was pregnant at the time of most recent violent episode. 9
Unknown if victim was pregnant at the time of most recent violent episode.
If data element 2.102 Sex of victim is "male," this data element should not be used.

# Data Standards or Guidelines
None.

# Other References
None.

# Details of Most

# NUMBER OF PERPETRATORS Description/Definition
Whether one or multiple perpetrators were involved in the most recent violent episode perpetrated by any intimate partner.

# Uses
Violent episodes involving more than one perpetrator may differ from violent episodes involving only one perpetrator.

# Discussion
None.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions
Code Description 1
The most recent violent episode perpetrated by any intimate partner involved one perpetrator.
The most recent violent episode perpetrated by any intimate partner involved two or more perpetrators. 9
Unknown number of perpetrators were involved in most recent violent episode perpetrated by any intimate partner.

# Data Standards or Guidelines
None.

# Other References
None.
Intimate Partner Violence Surveillance

# RELATIONSHIP OF VICTIM AND PERPETRATOR Description/Definition
The victim's relationship to the perpetrator at the time of the most recent violent episode perpetrated by any intimate partner.

# Uses
Allows examination of other data elements in the context of the relationship between the victim and perpetrator.

# Discussion
This data element is not designed to capture information about perpetrators other than the intimate partner who perpetrated the most recent violent episode.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions

# Code Description 1
In the most recent violent episode perpetrated by any intimate partner, the victim was the spouse of the perpetrator. 2
In the most recent violent episode perpetrated by any intimate partner, the victim was the common-law spouse of the perpetrator. 3
In the most recent violent episode perpetrated by any intimate partner, the victim was the divorced spouse of the perpetrator. 4
In the most recent violent episode perpetrated by any intimate partner, the victim was the former common-law spouse of the perpetrator. 5
In the most recent violent episode perpetrated by any intimate partner, the victim was the separated spouse or separated common-law spouse of the perpetrator. 6
In the most recent violent episode perpetrated by any intimate partner, the victim was the girlfriend or boyfriend of the perpetrator. 7
In the most recent violent episode perpetrated by any intimate partner, the victim was the former girlfriend or former boyfriend of the perpetrator. 8
In the most recent violent episode perpetrated by any intimate partner, the victim was a date of the perpetrator. 9
In the most recent violent episode perpetrated by any intimate partner, the victim was a former date of the perpetrator.
If the victim's relationship to the perpetrator has changed over time (e.g., girlfriend, wife, then ex-wife), the data element would be coded to reflect the victim's relationship to the perpetrator at the time of the most recent episode of violence. If there was more than one perpetrator (see data element 4.106 Number of perpetrators), code data on the victim's relationship to the intimate partner who perpetrated the most recent violent episode.

# Details of Most Recent Violent Episode 79 1
The code set on the previous page can include current and former same-sex partners. This data element, in conjunction with the data elements 2.102 Sex of victim and 4.302 Sex of perpetrator of most recent violent episode, can be used to identify same-sex and heterosexual relationships.
The code set above is limited to categories of intimate partner violence. If the IPV surveillance system is expanded to include violence by perpetrators other than intimate partners, the code set will also need to be expanded.

# Data Standards or Guidelines
None.

# Other References
None.
Intimate Partner Violence Surveillance

# COHABITATION OF VICTIM AND PERPETRATOR Description/Definition
The victim and the perpetrator's cohabitation status at the time of the most recent violent episode perpetrated by any intimate partner.

# Uses
Violent episodes involving intimate partners may differ depending on whether the victim and the perpetrator are living together.

# Discussion
Some cohabiting partners are not married (i.e., they may be separated, divorced, single, or widowed) or are in common-law marriages. See also data element 2.106 Marital status of victim.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions
Code Description 0
Victim was known not to be cohabiting with the perpetrator at the time of the most recent violent episode perpetrated by any intimate partner. 1
Victim was cohabiting with the perpetrator at the time of the most recent violent episode perpetrated by any intimate partner. 7
Unknown if victim was cohabiting with the perpetrator at the time of the most recent violent episode perpetrated by any intimate partner.
If there was more than one perpetrator (see data element 4.106 Number of perpetrators), code data on the victim's cohabitation status with the intimate partner who perpetrated the most recent violent episode.

# Data Standards or Guidelines
None.

# Other References
None.

# Details of Most Recent Violent Episode

# LENGTH OF INTIMATE RELATIONSHIP Description/Definition
The time between the most recent violent episode perpetrated by any intimate partner and the time when the victim and perpetrator first became intimate partners, specified in months.

# Uses
Some literature suggests that violence between intimate partners may increase in frequency and severity over time. This data element can be used in conjunction with data elements 4.110 Length of time relationship had been violent and 4.111 Pattern of violence in the past 12 months.

# Discussion
This data element is designed to measure how long it has been since the victim and perpetrator first became intimate partners. Although the nature of a relationship may change (e.g., from a dating relationship to a marriage, from a marriage to a divorce, or an on-again/off-again relationship with multiple breakups), this data element focuses on the entire length of time that has elapsed since intimacy began (although not necessarily when sexual intimacy began). The data element does not focus on the length of time the partners have been in the most recent stage of the relationship (e.g., the time they have been divorced or married).

# Data Type (and Field Length)
NM -numeric (4).

# Repetition
No.

# Field Values/Coding Instructions

# Code Description 0001
Less than 1 month XXXX Months 9999 Unknown
For partial months, round to the nearest number of months. For half months, round to the closest even number of months. Convert years to months by multiplying by 12 and then rounding if necessary, and add to the number of months in any partial year. For example, 5 1/2 years = (5.5 x 12) = 66 months; 4 years and 3 months = (4 x 12) + 3 = 48 + 3 = 51 months; 3 1/2 months is rounded to 4 months.
If there was more than one perpetrator (see data element 4.106 Number of perpetrators), code data on the victim's length of intimate relationship with the intimate partner who perpetrated the most recent violent episode.

# Data Standards or Guidelines
None.

# Other References
None.

# LENGTH OF TIME RELATIONSHIP HAD BEEN VIOLENT Description/Definition
The length of time, in months, between the most recent violent episode perpetrated by any intimate partner and the first violent episode that involved the same partner.

# Uses
Can be compared with 4.109 Length of intimate relationship and 4.111 Pattern of violence in the past 12 months.

# Discussion
The length of time a relationship has been violent may be related to characteristics of the violent episode. For example, some literature suggests that violence between intimate partners may increase in frequency and severity over time.

# Data Type (and Field Length)
NM-numeric (4).

# Repetition
No.

# Field Values/Coding Instructions

# Code Description 0001
Less than 1 month XXXX Months 9999 Unknown
For partial months, round to the nearest number of months. For half months, round to the closest even number of months. Convert years to months by multiplying by 12 and then rounding if necessary, and add to the number of months in any partial year. For example, 5 1/2 years = (5.5 x 12) = 66 months; 4 years and 3 months = (4 x 12) + 3 = 48 + 3 = 51 months; 3 1/2 months is rounded to 4 months.
If there was more than one perpetrator (see data element 4.106 Number of perpetrators), code data on the length of time the relationship had been violent between the victim and the intimate partner who perpetrated the most recent violent episode.

# Data Standards or Guidelines
None.

# Other References
None. Pattern of violence with the perpetrator of the most recent violent episode in the 12 months prior to the date of the most recent violent episode.

# Details of Most

# Uses
Specifies whether the pattern of violence with the perpetrator of the most recent violent episode had changed in the past 12 months.

# Discussion
Some literature suggests that violence between intimate partners may increase in frequency or severity over time, or that the types of violence used by perpetrators may change. As presently written, this data element measures whether changes in patterns of violence have occurred, but does not document the details of the change. Interested surveillance system users may wish to create additional data elements to document the nature of these changes in pattern.
Recall that pattern of violence is defined as "The way that violence is distributed over time in terms of frequency, severity, or type of violent episode (i.e., physical violence, sexual violence, threat of physical or sexual violence, psychological/ emotional abuse)."

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions

# Code Description 0
This was the only known violent episode committed by the perpetrator of the most recent violent episode. 1
There was no change in the pattern of violence during the 12 months prior to the date of the most recent violent episode. 2
The pattern of violence changed during the 12 months prior to the date of the most recent violent episode. 9
Unknown if the pattern of violence changed during the 12 months prior to the date of the most recent violent episode.
If there was more than one perpetrator (see data element 4.106 Number of perpetrators), code data on the pattern of violence with the intimate partner who perpetrated the most recent violent episode.

# Data Standards or Guidelines
None.

# Other References
None.
Intimate Partner Violence Surveillance

# NUMBER OF CHILDREN IN VICTIM'S HOME Description/Definition
The number of children under age 18 who were living in the victim's home at the time of the most recent violent episode perpetrated by any intimate partner.

# Uses
Designed to collect information on the number of children living in the home of IPV victims, regardless of whether the children witnessed specific episodes of violence.

# Discussion
The literature suggests that children exposed to violence in the family are at increased risk of victimization or perpetration of IPV as adolescents or adults.

# Data Type (and Field Length)
NM -numeric (2).

# Repetition
No.

# Field Values/Coding Instructions

# Data Standards or Guidelines
None.

# Other References Data Standards or Guidelines
None.

# Other References
None.
Intimate Partner Violence Surveillance

# PSYCHOLOGICAL CONSEQUENCES TO VICTIM Description/Definition
The psychological consequences to the victim attributed to the most recent violent episode, perpetrated by any intimate partner, by the agency providing data to the IPV surveillance system.

# Uses
Research demonstrates links between IPV and serious mental health consequences such as depression and suicide.

# Discussion
None.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions

# Code Description 0
It is known that there are no psychological consequences to the victim that are attributable to the most recent violent episode perpetrated by any intimate partner. 1
Psychological consequences to the victim are attributable to the most recent violent episode perpetrated by any intimate partner. 9
Unknown if there are psychological consequences to the victim attributable to the most recent violent episode perpetrated by any intimate partner.
If the data element 4.201 Physical consequences to victim was coded "7" (Death occurred or fatal injuries received during most recent violent episode perpetrated by any intimate partner), then this data element should be used to indicate psychological consequences related to the most recent violent episode that the victim experienced following the violent episode but before death.

# Data Standards or Guidelines
None.

# Other References
None.

# Data Standards or Guidelines
None.

# Other References
None.

# Consequences to

# Uses
Research demonstrates links between IPV and serious mental health consequences such as depression and suicide.

# Discussion
None.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions
Code Description 0
The victim was known not to have received mental health care (excluding substance abuse treatment) after the most recent violent episode perpetrated by any intimate partner. 1
The victim received outpatient mental health care (excluding substance abuse treatment), not followed by inpatient mental health care, after the most recent violent episode perpetrated by any intimate partner. 2
The victim received outpatient mental health care (excluding substance abuse treatment), followed by inpatient mental health care, after the most recent violent episode perpetrated by any intimate partner. 3
The victim received outpatient mental health care (excluding substance abuse treatment), unknown if followed by inpatient mental health care, after the most recent violent episode perpetrated by any intimate partner. 4
The victim received no outpatient mental health care (excluding substance abuse treatment), but did receive inpatient mental health care, after the most recent violent episode perpetrated by any intimate partner. 5
Unknown if the victim received outpatient mental health care (excluding substance abuse treatment), but did receive inpatient mental health care, after the most recent violent episode perpetrated by any intimate partner. 9
Unknown if the victim received any mental health care (excluding substance abuse treatment) following the most recent violent episode perpetrated by any intimate partner.

# 92 Intimate Partner Violence Surveillance
If the data element 4.201 Physical consequences to victim was coded "7" (Death occurred or fatal injuries received during most recent violent episode perpetrated by any intimate partner), then this data element should be used to indicate any mental health care related to the most recent violent episode that the victim received following the violent episode but prior to death.

# Data Standards or Guidelines
None.

# Other References
None.

# Consequences to

# SUBSTANCE ABUSE TREATMENT RECEIVED BY VICTIM Description/Definition
The substance abuse treatment received by the victim following the most recent violent episode perpetrated by any intimate partner.

# Uses
Research demonstrates links between substance abuse and IPV victimization.

# Discussion
None.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
Yes, if victim received more than one type of treatment for substance abuse.

# Field Values/Coding Instructions
Code Description 0
The victim was known not to have received substance abuse treatment following the most recent violent episode perpetrated by any intimate partner. 1
The victim received treatment for alcohol abuse following the most recent violent episode perpetrated by any intimate partner. 2
The victim participated in Alcoholics Anonymous (AA) following the most recent violent episode perpetrated by any intimate partner. 3
The victim received treatment for drug abuse following the most recent violent episode perpetrated by any intimate partner. 4
The victim participated in Narcotics Anonymous (NA) following the most recent violent episode perpetrated by any intimate partner. 9
Unknown if the victim received any substance abuse treatment following the most recent violent episode perpetrated by any intimate partner.
If the data element 4.201 Physical consequences to victim was coded "7" (Death occurred or fatal injuries received during most recent violent episode perpetrated by any intimate partner), then this data element should be used to indicate any substance abuse treatment related to the most recent violent episode that the victim had received following the violent episode but prior to death.

# Data Standards or Guidelines
None.

# Other References
None.
Intimate Partner Violence Surveillance

# DEATHS RELATED TO EPISODE Description/Definition
All deaths associated with the most recent violent episode perpetrated by any intimate partner.

# Uses
Incidents involving one or more deaths may be different from those that do not involve any fatalities.

# Discussion
None.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
Yes, if more than one death occurred as a result of the most recent violent episode. Death of someone else resulted from the most recent violent episode perpetrated by any intimate partner. 9

# Field Values/Coding Instructions
Unknown if any deaths resulted from the most recent violent episode perpetrated by any intimate partner.
If the data element 4.201 Physical consequences to victim was coded "7" (Death occurred or fatal injuries received during most recent violent episode perpetrated by any intimate partner), then this data element must, at a minimum, be coded as "1" (Victim's death by homicide).

# Data Standards or Guidelines
None.

# Other References
None.

# S E C T I O N PERPETRATOR OF MOST RECENT VIOLENT EPISODE
A perpetrator is a person who inflicts the violence or abuse or causes the violence or abuse to be inflicted on the victim.
A violent episode is a single act or series of acts of violence that are perceived to be connected to each other and that may persist over a period of minutes, hours, or days. A violent episode may involve single or multiple types of violence (e.g., physical violence, sexual violence, threat of physical or sexual violence, psychological/emotional abuse).
For victims who have had only one violent intimate partner, the most recent violent episode perpetrated by any intimate partner refers to the most recent violent episode perpetrated by that intimate partner. For victims who have had more than one violent intimate partner, the most recent violent episode perpetrated by any intimate partner refers to the violent episode perpetrated most recently by whichever one of those violent intimate partners committed it. Thus, the most recent violent episode perpetrated by any intimate partner may have been perpetrated by someone other than the victim's current intimate partner. For example, if a woman has been victimized by both her ex-husband and her current boyfriend, questions about the most recent violent episode would refer to the episode involving whichever intimate partner victimized her most recently, not necessarily the one with whom she is currently in a relationship.

# Uses
Can be used to calculate the perpetrator's age.

# Discussion
None.

# Data Type (and Field Length)
TS-time stamp (26).

# Repetition
No.

# Field Values/Coding Instructions
Year, month, and day of birth are entered in the format YYYYMMDD. For example, a birth date of August 12, 1946, would be encoded as 19460812.
See method recommended under TS-time stamp in the Technical Notes at the end of this document for estimating age of perpetrator of the most recent violent episode.
If date of birth is not known, it can be estimated from the perpetrator's age. (See also Technical Notes at the end of this document.)
If there was more than one perpetrator (see data element 4.106 Number of perpetrators), code data on the victim's intimate partner who perpetrated the most recent violent episode. E1384-96 (ASTM, 1996 and Health Level 7, Version 2.3 (HL7, 1996).

# Data Standards or Guidelines

# Other References
None.
Intimate Partner Violence Surveillance 4.302

# SEX OF PERPETRATOR OF MOST RECENT VIOLENT EPISODE Description/Definition
Sex of the perpetrator of the most recent violent episode.

# Uses
Allows identification of the gender of the perpetrator, and can be used to identify same-sex and heterosexual relationships.

# Discussion
None.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions

# Data Standards or Guidelines
CDC HISSB Common Data Elements Implementation Guide. 

# Other References
None.

# Perpetrator of Most Recent Violent Episode

# RACE OF PERPETRATOR OF MOST RECENT VIOLENT EPISODE Description/Definition
Race of the perpetrator of the most recent violent episode.

# Uses
Data on race are used in public health surveillance and in epidemiologic, clinical, and health services research.

# Discussion
For more than 20 years, the Federal government has promoted the use of a common language to promote uniformity and comparability of data on race and ethnicity for population groups. Development of the data standards stemmed in large measure from new responsibilities to enforce civil rights laws. Data were needed to monitor equal access in housing, education, employment, and other areas for populations that historically had experienced discrimination and differential treatment because of their race or ethnicity. The standards are used not only in the decennial census (which provides the data for the "denominator" for many measures), but also in household surveys, on administrative forms (e.g., school registration and mortgagelending applications), and in medical and other research. The categories represent a social-political construct designed for collecting data on the race and ethnicity of broad population groups in the United States.
Race is a concept used to differentiate population groups largely on the basis of physical characteristics transmitted by descent.  , 1997) was developed to meet Federal legislative and program requirements, and these standards are used widely in the public and private sectors. The directive provides five basic racial categories but states that the collection of race data need not be limited to these categories. However, any additional reporting that uses more detail must be organized in such a way that the additional categories can be aggregated into the five basic groups. Although the directive does not specify a method of determining an individual's race, OMB prefers self-identification to identification by an observer whenever possible. The directive states that persons of mixed racial origins should be coded using multiple categories, and not a multiracial category.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
Yes; if the agency providing the data to the IPV surveillance system uses multiple racial categories, the IPV surveillance system also allows for multiple racial categories to be coded.

# Other References
Core Health Data Elements (National Committee on Vital and Health Statistics, 1996).

# Discussion
Ethnicity is a concept used to differentiate population groups on the basis of shared cultural characteristics or geographic origins. A variety of cultural attributes contribute to ethnic differentiation, including language, patterns of social interaction, religion, and styles of dress. However, ethnic differentiation is imprecise and fluid. It is contingent on a sense of group identity that can change over time and that involves subjective and attitudinal influences. Since 1977, the Federal government has sought to standardize data on race and ethnicity among its agencies.  , 1997) was developed to meet Federal legislative and program requirements, and these standards are used widely in the public and private sectors.
The directive provides two basic ethnic categories -Hispanic or Latino and Not of Hispanic or Latino Origin -but states that collection of ethnicity data need not be limited to these categories. However, any additional reporting that uses more detail must be organized in such a way that the additional categories can be aggregated into the two basic groups. OMB prefers that data on race and ethnicity be collected separately. The use of the Hispanic category in a combined race/ethnicity data element makes it impossible to distribute persons of Hispanic ethnicity by race and, therefore, reduces the utility of the five basic racial categories by excluding from them persons who would otherwise be included.

# Repetition
No.

# Data Type (and Field Length)
CE -coded element (60).  , 1997).

# Field Values/Coding Instructions

# Other References
Core Health Data Elements (National Committee on Vital and Health Statistics, 1996).

# Uses
Allows examination of the correspondence between the location of the victim's residence, the perpetrator's residence, and the location of the most recent violent episode perpetrated by any intimate partner, and may have implications for intervention strategies.

# Discussion
Additional information (e.g., street address, zip code) can easily be added as components of this element if data linkage across data sources is desired. However, to protect privacy and confidentiality, access to this level of detail must be limited to authorized personnel. Surveillance system users who do not convert street address to census block groups or encrypt addresses need to be aware that they may be acquiring the victim's street address when they acquire the perpetrator's street address. The need for victim safety and confidentiality must be taken into account if the full extended version of this data element is used.
In conjunction with data elements 2.105 City, state, and county of victim's residence and 4.104 City, state, and county of occurrence, this data element allows examination of the correspondence between the victim's residence, the perpetrator's residence, and the location of the most recent violent episode.

# Data Type (and Field Length)
XAD -extended address (106).

# Repetition
No.

# Field Values
Component 3 is the city. Component 4 is the state or province. Component 9 is the county/parish code.
The state or province code entered in Component 4 should be entered as a twoletter postal abbreviation. The county/parish code should be entered in Component 9 as the 3-digit Federal Information Processing Standards code. See XAD -extended address in the Technical Notes at the end of this document for additional information on other possible components of this data element. The numbering of these components (3, 4, and 9) is consistent with the numbering of components used elsewhere for full XAD coding.

# 104 Intimate Partner Violence Surveillance
If there was more than one perpetrator (see data element 4.106 Number of perpetrators), code data on the victim's intimate partner who perpetrated the most recent violent episode.

# Data Standards or Guidelines
Health Level 7, Version 2.3 (HL7, 1996).

# Other References
None.
Perpetrator of Most Recent Violent Episode 105 4.306

# ALCOHOL USE BY PERPETRATOR OF MOST RECENT VIOLENT EPISODE Description/Definition
Proportion of time the perpetrator of the most recent violent episode uses alcohol in conjunction with violence or abuse.

# Uses
Documents the association of alcohol use and violence.

# Discussion
None.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions
Code Description 0
The perpetrator of the most recent violent episode never uses alcohol in conjunction with violence or abuse. 1
The perpetrator of the most recent violent episode rarely uses alcohol in conjunction with violence or abuse. 2
The perpetrator of the most recent violent episode uses alcohol in conjunction with violence or abuse some of the time.
The perpetrator of the most recent violent episode uses alcohol in conjunction with violence or abuse most of the time. 4
The perpetrator of the most recent violent episode always uses alcohol in conjunction with violence or abuse. 8
The perpetrator of the most recent violent episode uses alcohol in conjunction with violence or abuse, but the proportion of time is unknown. 9
Unknown if the perpetrator of the most recent violent episode uses alcohol in conjunction with violence or abuse.
If there was more than one perpetrator (see data element 4.106 Number of perpetrators), code data on the victim's intimate partner who perpetrated the most recent violent episode.

# Data Standards or Guidelines
None.

# Other References
None.
Intimate Partner Violence Surveillance 4.307

# DRUG USE BY PERPETRATOR OF MOST RECENT VIOLENT EPISODE Description/Definition
Proportion of time the perpetrator of the most recent violent episode uses drugs (other than alcohol) in conjunction with violence or abuse.

# Uses
Documents the association of drug use and violence.

# Discussion
None.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
No.

# Field Values/Coding Instructions
Code Description 0
The perpetrator of the most recent violent episode never uses drugs (other than alcohol) in conjunction with violence or abuse. 1
The perpetrator of the most recent violent episode rarely uses drugs (other than alcohol) in conjunction with violence or abuse. 2
The perpetrator of the most recent violent episode uses drugs (other than alcohol) in conjunction with violence or abuse some of the time.
The perpetrator of the most recent violent episode uses drugs (other than alcohol) in conjunction with violence or abuse most of the time. 4
The perpetrator of the most recent violent episode always uses drugs (other than alcohol) in conjunction with violence or abuse. 8
The perpetrator of the most recent violent episode uses drugs (other than alcohol) in conjunction with violence or abuse, but the proportion of time is unknown. 9
Unknown if the perpetrator of the most recent violent episode uses drugs (other than alcohol) in conjunction with violence or abuse.
If there was more than one perpetrator (see data element 4.106 Number of perpetrators), code data on the victim's intimate partner who perpetrated the most recent violent episode.

# Data Standards or Guidelines
None.

# Other References
None.

# Perpetrator of Most

# Uses
Severity and likelihood of injury and other serious consequences may be associated with weapon use.

# Discussion
As presently written, "7" (Another type of weapon was used by the perpetrator in the most recent violent episode) designates weapons used other than those explicitly named in codes 1-6. Interested surveillance system users may wish to record information about additional weapon types.

# Data Type (and Field Length)
CE -coded element (60).

# Repetition
Yes; if more than one weapon was used.

# Field Values/Coding Instructions
Code Description 0
It is known that no weapons or bodily force was used by the perpetrator in the most recent violent episode. 1
Bodily force was used by the perpetrator in the most recent violent episode.
A blunt object was used by the perpetrator in the most recent violent episode.
A cutting or piercing instrument was used by the perpetrator in the most recent violent episode. 4
A long gun (e.g., shotgun, rifle) was used by the perpetrator in the most recent violent episode.
A handgun was used by the perpetrator in the most recent violent episode. 6
A firearm, type unknown, was used by the perpetrator in the most recent violent episode. 7
Another type of weapon was used by the perpetrator in the most recent violent episode. 9
Unknown if a weapon or bodily force was used by the perpetrator in the most recent violent episode.
If there was more than one perpetrator (see data element 4.106 Number of perpetrators), code data on the weapon used by the intimate partner who perpetrated the most recent violent episode.

# Data Standards or Guidelines
None.

# Other References
None.