Section - myCares



Cardiac

Arrest

Registry to

Enhance

Survival

CARES

Version 3.0

Data Dictionary

Designed by

Sansio

EMS Division

LAST UPDATED- 12/03/2014

WWW.

Cardiac Arrest Registry to Enhance Survival (CARES)



The CARES Dataset, Version 3.0 is composed of four separate components. 1) A CAD (Computer Aided Dispatch) Dataset provides a standardized set of definitions describing a CAD Event for a Cardiac Arrest event. 2) A First Responder Dataset provides a standardized set of definitions describing a First Responding Agency event for a Cardiac Arrest event. 3) An EMS Dataset provides a standardized set of definitions describing an EMS event. 4) A Hospital Dataset provides a standardized set of definitions describing a Hospital event.

Any implementation of the CARES Version 3.0 dataset must include the use of the EMS dataset, and XML standard.

Information provided in this document includes the following:

← Name of the Data Element

← Definition of the Data Element

← Data Type of the Data Element (many data elements have comments provided to assist in the implementation of a database schema)

← How to deal with missing or incomplete information (See Missing Data or Null Values below)

← What Data Elements are associated with the Data Element

← How the Data Element is related to other National Data Tools such as NHTSA Version 1, NFIRS, and Utstein

← Notes:

o Constraints- the constraints reflected in the fields in this document are meant to correspond to CARES constraints. See the NEMSIS definitions for more detailed element information.

o There may be more than one NEMSIS code mapped to a CARES field in enumerated elements. For instance, more than one NEMSIS code might map to CARES “Other” field as specified in the element definitions.

o If a dateTime field has no time component, such as Date Of Birth, use dateTime format and pass in midnight (all zeroes).

o PLEASE SEE (2013).pdf for detailed clinical descriptions of fields. Use the codes for field values given in this document.

← PARSING NOTES

If an XML file contains a call that already exists in the system, with the same service date and incident number for a given agency (Custom element servicedate and eResponse.03), the file will not parse and none of the records within the XML file will be processed.

Cardiac Arrest Registry to Enhance Survival (CARES) Dataset

Version 3.0 (2012)

Table of Contents

|Header | |

| |General Information |1 |

|CAD Dataset | |

| |CAD Information |13 |

|EMS Dataset | |

| |Call Information |25 |

| |Arrest Information |43 |

| |Resuscitation Information |49 |

| |First Cardiac/ROSC Information |60 |

| |Time Information |65 |

| |Hypothermia Information |80 |

| |EMS Interventions |82 |

|Hospital Dataset | |

| |Hospital Information |96 |

Header - General Information

Agency ID

eCustomConfiguration - AgencyID

Data Format [number]

Definition

The number assigned to this agency within the website.

V2 Element: H01_01

XSD Data Type xs:integer XSD Domain (Simple Type) AgencyID

Multiple Entry Configuration No Accepts Null No

Required in XSD Yes Minimum Constraint 2 Maximum Constraint 15

Field Values

A unique value; no variable list is possible.

Additional Information

● This field must match the agencyid assigned within the website. All data within the import file will be associated to this agency id.

Import Version

eCustomConfiguration - ImportVersion

Data Format [string]

Definition

The version of the import specification used to create this file.

XSD Data Type xs:string XSD Domain (Simple Type) ImportVersion

Multiple Entry Configuration No Accepts Null No

Required in XSD Yes

Field Values

The version is currently 3.0

Form ID

eCustomConfiguration - FormID

Data Format [integer]

Definition

This field is used internally to determine which ‘form’ this data should be imported as.

XSD Data Type xs:integer XSD Domain (Simple Type) FormID

Multiple Entry Configuration No Accepts Null No

Required in XSD Yes

Field Values

This value should always be 90003

Import Method eCustomConfiguration - ImportMethod

Data Format [integer]

Definition

The method to use during the import.

XSD Data Type xs:integer XSD Domain (Simple Type) ImportMethod

Multiple Entry Configuration No Accepts Null No

Required in XSD Yes

Field Values

1 Import

9 Testing – Do Not Import

Software Used to Create This File

eRecord.03

Data Format [string]

Definition

The name of the software used to create this file.

V2 Element: H01_05_01

XSD Data Type xs:string XSD Domain (Simple Type) SoftwareName

Multiple Entry Configuration No Accepts Null No

Required in XSD Yes Minimum Constraint 1 char Maximum Constraint 50 chars

XSD Structure: H01_05_01 is a member of H01_05 Software Structure

Field Values

Software Version

eRecord.04

Data Format [string]

Definition

The version of the software used to create this file.

V2 Element: H01_05_02

XSD Data Type xs:string XSD Domain (Simple Type) SoftwareVersion

Multiple Entry Configuration No Accepts Null No

Required in XSD Yes Minimum Constraint 1 char Maximum Constraint 50 chars

XSD Structure: H01_05_02 is a member of H01_05 Software Structure

Field Values

Developer Contact Last Name

eCustomConfiguration -ContactLastName

Data Format [string]

Definition

The Last Name of the primary developer of the export file.

V2 Element: H01_05_03(just name-split into last/first)

XSD Data Type xs:string XSD Domain (Simple Type) ContactLastName

Multiple Entry Configuration No Accepts Null No

Required in XSD Yes Minimum Constraint 1 char Maximum Constraint 50 chars

XSD Structure: H01_05_03 is a member of H01_05 Software Structure

Field Values

Developer Contact First Name

eCustomConfiguration -ContactFirstName

Data Format [string]

Definition

The First Name of the primary developer of the export file.

V2 Element: H01_05_03 (just name-split into last/first)

XSD Data Type xs:string XSD Domain (Simple Type) ContactFirstName

Multiple Entry Configuration No Accepts Null No

Required in XSD Yes Minimum Constraint 1 char Maximum Constraint 50 chars

XSD Structure: H01_05_03 is a member of H01_05 Software Structure

Field Values

Developer Contact Phone #

eCustomConfiguration -ContactPhone

Data Format [string]

Definition

The phone number of the primary developer of the export file

V2 Element: H01_05_04

XSD Data Type xs:string XSD Domain (Simple Type) ContactPhone

Multiple Entry Configuration No Accepts Null No

Required in XSD Yes Minimum Constraint 1 char Maximum Constraint 50 chars

XSD Structure: H01_05_04 is a member of H01_05 Software Structure

Field Values

Developer Contact Email

eCustomConfiguration -ContactEmail

Data Format [string]

Definition

The email of the primary developer of the export file.

V2 Element: H01_05_05

XSD Data Type xs:string XSD Domain (Simple Type) ContactEmail

Multiple Entry Configuration No Accepts Null No

Required in XSD Yes Minimum Constraint 1 char Maximum Constraint 50 chars

XSD Structure: H01_05_05 is a member of H01_05 Software Structure

Field Values

CAD Dataset

CAD Information

Booklet ID

eCustomConfiguration - BookletID

Data Format [number]

Definition

The ™/HealthEMS™ booklet number associated to this event.

XSD Data Type xs:integer XSD Domain (Simple Type) BookletID

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 5 Maximum Constraint 10

Field Values

A unique value; no variable list is possible.

Additional Information

● This field will most likely be blank. The only uses would be for HealthEMS™ users who choose to fill out the CARES form instead of the HealthEMS™ form and need to enter the HealthEMS™ bookletid on the CARES form to later match to a HealthEMS™ record to retrieve additional information. This field would then help assist that process.

Uses

● This will be used to help auto-match this CAD information to the corresponding EMS information

Data Collector

● This value would be pre-printed on the HealthEMS™ ePCR.

Agency CAD ID

eResponse.04

Data Format [text]

Definition

The CAD-assigned number given to this event

V2 Element: C01_03

XSD Data Type xs:string XSD Domain (Simple Type) AgencyCADID

Multiple Entry Configuration Yes Accepts Null Yes

Required in XSD No Minimum Constraint 0 Maximum Constraint 20

Field Values

● Optional Unique Identifier from CAD System

Additional Information

●

Uses

● Needs to be available for change management. If a record with this ID already exists, the current data will be over-written with this data.

● Also used to tie back to original CAD record in CAD system in case other data is ever needed.

Data Collector

● CAD System

Date of Arrest--CAD

eTimes.02

Data Format [date/time]

Definition

The date the event occurred. Date of Arrest

V2 Element: C01_05

XSD Data Type xs:dateTime XSD Domain (Simple Type) ServiceDate

Multiple Entry Configuration No Accepts Null No

Required in XSD Yes Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

Since this element is not nillable and does not except NV- please pass min value for NO value

|1950-01-01T00:00:0000:00 |

| |

Incident Address

eScene.15

Data Format [string]

Definition

Address where incident occurred

V2 Element: C01_25

XSD Data Type xs:string XSD Domain (Simple Type) IncidentAddress

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 1 Maximum Constraint 50*

Field Values

*CARES maximum constraint on string length=50

Incident City

eScene.17

Data Format [string]

Definition

City where incident occurred

V2 Element: C01_27

XSD Data Type xs:string XSD Domain (Simple Type) IncidentCity

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 0 Maximum Constraint 50 chars

Field Values

● CARES will accept the name of the city and not the code from the list affiliated with this NEMSIS element. Example: Cincinnati

Otherwise, please use the census code from the “State Files with Federal Codes” downloads at



If passing a census code from a state other than your agency’s state, please pass a value in eScene.18 for State.

Incident State ID

eScene.18

Data Format [string]

Definition

State where incident occurred.

V2 Element: C01_29

XSD Data Type xs:string XSD Domain (Simple Type) IncidentStateID

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2 chars Maximum Constraint 2 chars

Field Values

● This can be the 2 character name of the state and not the code from the list affiliated with this NEMSIS element. Example: WA

Incident Zip Code

eScene.19

Data Format [string]

Definition

Zip code where incident occurred.

V2 Element: C01_30

XSD Data Type xs:string XSD Domain (Simple Type) IncidentZip

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 0 Maximum Constraint 10 chars

Field Values

● XXX

Patient First Name

ePatient.03

Data Format [string]

Definition

XXXXXXXXX

V2 Element: C01_31

XSD Data Type xs:string XSD Domain (Simple Type) PatientFName

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 1 Maximum Constraint 50

Field Values

● XXX

Patient Last Name

ePatient.02

Data Format [string]

Definition

XXXXXXXXX

V2 Element: C01_32

XSD Data Type xs:string XSD Domain (Simple Type) PatientLName

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 1 Maximum Constraint 50

Field Values

● XXX

EMS Dataset

Call Information

Date of Arrest/Service Date

eCustomConfiguration - servicedate

Data Format [date/time]

Definition

The date the event occurred. Date of Arrest. If none is passed, it will default to today’s date.

V2 Element: C01_05

XSD Data Type xs:dateTime XSD Domain (Simple Type) ServiceDate

Multiple Entry Configuration No Accepts Null No

Required in XSD Yes Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

Call Number

eResponse.03

Data Format [text]

Definition

The incident number given to this event.

V2 Element: E01_02

XSD Data Type xs:string XSD Domain (Simple Type) CallNumberID

Multiple Entry Configuration No Accepts Null No

Required in XSD Yes Minimum Constraint 0 chars Maximum Constraint 15 chars

Field Values

● A unique value; no variable list is possible.

● The combination of Service Date and Call Number must represent a unique event.

Uses

CARES does not accept Not Values or nil for this field. This must be present in every record.

Booklet ID

eCustomConfiguration - BookletID

Data Format [number]

Definition

The ™ HealthEMS™ booklet number associated to this event.

XSD Data Type xs:integer XSD Domain (Simple Type) BookletID

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 5 Maximum Constraint 10

Field Values

A unique value; no variable list is possible.

Additional Information

● This field will most likely be blank. The only uses would be for HealthEMS™ users who choose to fill out the CARES form instead of the HealthEMS™ form and need to enter the HealthEMS™ bookletid on the CARES form to later match to a HealthEMS™ record to retrieve additional information. This field would then help assist that process.

Uses

● This will be used to help auto-match this information to the corresponding CAD information

Incident Address

eScene.15

Data Format [string]

Definition

Address where incident occurred

V2 Element: E01_04

XSD Data Type xs:string XSD Domain (Simple Type) IncidentAddress

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 1 Maximum Constraint 50 chars

Field Values

*CARES maximum constraint on string length=50

Incident State ID

eScene.18

Data Format [string]

Definition

2-char state value where incident occurred

V2 Element: E01_06

XSD Data Type xs:string XSD Domain (Simple Type) IncidentStateID

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2 chars Maximum Constraint 2 chars

Field Values

● XX

**REQUIRED FIELD IN 2012**

Incident Zip Code

eScene.19

Data Format [string]

Definition

Zip Code where incident occurred

V2 Element: E01_07

XSD Data Type xs:string XSD Domain (Simple Type) IncidentZip

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 0 Maximum Constraint 10 chars

Field Values

● XXX

**REQUIRED FIELD IN 2012**

Patient First Name

ePatient.03

Data Format [string]

Definition

Patient’s first name

V2 Element: E01_08

XSD Data Type xs:string XSD Domain (Simple Type) PatientFName

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 1 Maximum Constraint 50 chars

Field Values

● XXX

Patient Last Name

ePatient.02

Data Format [string]

Definition

Patient’s last name

V2 Element: E01_09

XSD Data Type xs:string XSD Domain (Simple Type) PatientLName

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 1 Maximum Constraint 50

Field Values

● XXX

Patient Age

ePatient.15

Data Format [number]

Definition

Patient’s age. Units used in this field are documented in field E01_11 or ePatient.16

V2 Element: E01_10

XSD Data Type xs:integer XSD Domain (Simple Type) PatientAge

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 1 Maximum Constraint 120

Field Values

●

**REQUIRED FIELD IN 2012**

Patient Age Modifier

ePatient.16

Data Format [number]

Definition

Modifier describing age units used in field E01_10

V2 Element: E01_11

XSD Data Type xs:integer XSD Domain (Simple Type) PatientAgeModifier

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

2516001 Days

2516007 Months

2516009 Years

Patient Date of Birth

ePatient.17

Data Format [date/time]

Definition

The patient’s date of birth

V2 Element: E01_12

XSD Data Type xs:dateTime XSD Domain (Simple Type) DateOfBirth

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 1800 Maximum Constraint 2050

Field Values

● Valid date/time. To indicate an unknown DOB, please send 1800-01-01.

If unknown, use DOB_Unknown field.

**DOB Unknown is a REQUIRED FIELD IN 2012**

Patient Gender

ePatient.13

Data Format [number]

Definition

The patient’s gender

V2 Element: E01_13

XSD Data Type xs:integer XSD Domain (Simple Type) PatientGender

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

9906003 Male

9906001 Female

**REQUIRED FIELD IN 2012**

Patient Race/Ethnicity

ePatient.14

Data Format [number]

Definition

The patient’s ethnicity. This field is extended by custom element EthnicityUnknown- code = 8

V2 Element: E01_14

XSD Data Type xs:integer XSD Domain (Simple Type) PatientEthnicity

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

2514003 Asian

2514005 Black or African-American

2514009 Native Hawaiian/Pacific Islander

2514011 White

2514001 American-Indian or Alaskan

2514007 Hispanic or Latino

To pass “Unknown” value, extend this field and pass proper value in custom element EthnicityUnknown.

**REQUIRED FIELD IN 2012**

Patient Ethnicity Other

eCustomConfiguration - EthnicityUnknown

Data Format [number]

Definition

Field used to pass “Other” value for Ethnicity – extended field ePatient.14

V2 Element: None

XSD Data Type xs:integer XSD Domain (Simple Type) EthnicityUnknown

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

8 Unknown

8

EthnicityUnknown

ePat

Fire/First Responder

eCustomConfiguration.FirstResponder

Data Format [string]

Definition

The Fire/First Responder code for this event

V2 Element: E01_15

XSD Data Type xs:string XSD Domain (Simple Type) FirstResponder

Null No

Required in XSD Yes Minimum Constraint 1 Maximum Constraint 15

Field Values

Valid Fire/First Responder Import Value/code set up in CARES. The values are unique to an agency and may comprise of a list of first responder names in the CARES application, or a list that like Transport or Non-transport agency was first to arrive on scene. Lists can be obtained from agency.

**REQUIRED FIELD IN 2012**

Destination Hospital

eDisposition.02

Data Format [number]

Definition

The Destination Hospital code for this event

V2 Element: E01_16

XSD Data Type xs:integer XSD Domain (Simple Type) DestinationHospital

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2 Maximum Constraint 50

Field Values

Valid Destination Hospital Import Value set up in CARES. The values are unique to an agency and may comprise of a list of hospitals in the CARES application, accessed through the code value passed in the import lists can be obtained from agency.

Medical history ***SUPPLEMENTAL***

eHistory.08

Data Format [string]

Definition

The Medical History codes from ICD-10CM. If the value passed equates to “Other” please use custom element MedHistoryOther and extend this field.

V2 Element: E01_17

XSD Data Type xs:string XSD Domain (Simple Type) MedicalHistoryID

Multiple Entry Configuration Yes Accepts Null Yes

Required in XSD No

Field Values

8801015 No (Pertinent Negative)

8801023  Unknown (Pertinent Negative)

C80.1 Cancer

E11.9 Diabetes

I51.9 Heart Disease

E78.5 Hyperlipidemia

I10 Hypertension

N28.9 Renal Disease

J98.9 Respiratory Disease

I63.9 Stroke

To pass “Other” value, extend this field like the example below and pass the value in MedHistoryOther

Medical History Other

eCustomConfiguration - MedHistoryOther

Data Format [integer]

Definition

Field used to pass “Other” value for Medical History Other

V2 Element: None

XSD Data Type xs:integer XSD Domain (Simple Type) MedHistoryOther

Multiple Entry Configuration No Accepts Null Yes

Minimum Constraint 2 Maximum Constraint 2

Required in XSD No

Field Values

99 Other

99

MedHistoryOther

eHist

Medical History Other

eCustomConfiguration - MedicalHistoryOtherStr

Data Format [string]

Definition

Field used to pass a text/string value for Medical History Other.

V2 Element: None

XSD Data Type xs:string XSD Domain (Simple Type) MedicalHistoryOtherStr

Multiple Entry Configuration No Accepts Null Yes

Minimum Constraint 1 Maximum Constraint 50

Required in XSD No

Field Values:

Field used to pass a text/string value for Medical History Other- Should be used with MedHistoryOther field on previous page. This field will not populate unless MedHistoryOther is passed properly.

Incident County ID

eScene.21

Data Format [number]

Definition

FIPS County code where incident occurred

V2 Element: E01_18

XSD Data Type xs:string XSD Domain (Simple Type) IncidentCountyD

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 4 Maximum Constraint 5

Field Values

● 5 digits can be passed with leading zeros up to the county code.

**REQUIRED FIELD IN 2012**

EMS Dataset

Arrest Information

Location Type

eCustomConfiguration - LocationType

Data Format [number]

Definition

Location incident occurred

V2 Element: E02_01

XSD Data Type xs:integer XSD Domain (Simple Type) LocationType

Multiple Entry Configuration No Accepts Null No

Required in XSD No

Field Values

1 Home/Residence

2 Public/Commercial Building

3 Street/Hwy

4 Nursing Home

6 Healthcare Facility

9 Place of Recreation

10 Industrial Place

14 Other

15 Transport Center

**REQUIRED FIELD IN 2012**

Location Type Other

eCustomConfiguration - LocationTypeOther

Data Format [string]

Definition

Use this field if Location Type=14. (Other) to clarify location

V2 Element: E02_05

XSD Data Type xs:string XSD Domain (Simple Type) LocationTypeOther

Multiple Entry Configuration No Accepts Null: Yes

Minimum Constraint: 0 Maximum Constraint: 50

Required in XSD No

Arrest Witnessed

eCustomConfiguration - ArrestWitnessed

Data Format [number]

Definition

A witnessed arrest is one that is seen or heard by another person

V2 Element: E02_02

XSD Data Type xs:integer XSD Domain (Simple Type) ArrestWitnessed

Multiple Entry Configuration No Accepts Null No

Required in XSD No

Field Values

1 Witnessed Arrest

2 Unwitnessed Arrest

**REQUIRED FIELD IN 2012**

Arrest After Arrival of 911 Responder

eCustomConfiguration - ArrestAfterArrivalEMS

Data Format [number]

Definition

Indicates if the patient arrested before or after the arrival of a 911 responder.

V2 Element: E02_03

XSD Data Type xs:integer XSD Domain (Simple Type) ArrestAfterArrivalEMS

Multiple Entry Configuration No Accepts Null No

Required in XSD No

Field Values

1 Yes

2 No

**REQUIRED FIELD IN 2012**

Presumed Cardiac Arrest Etiology

eArrest.02

Data Format [number]

Definition

V2 Element: E02_04

XSD Data Type xs:integer XSD Domain (Simple Type) CardiacEtiology

Multiple Entry Configuration No Accepts Null No

Required in XSD No

Field Values

3002001 Presumed Cardiac Etiology

3002015 Trauma

3002013 Respiratory

3002003 Drowning

3002007 Electrocution

3002011 Other

3002009 Other

3002005 Other

See Custom Element CardiacEtiologyOther on next page on usage of “Other” values

**REQUIRED FIELD IN 2012**

Presumed Cardiac Arrest Etiology Other

eCustomConfiguration - CardiacEtiologyOther

Data Format [string]

Definition

Field used to pass a text/string value for Presumed Cardiac Arrest Etiology Other

V2 Element: None

XSD Data Type xs:string XSD Domain (Simple Type) CardiacEtiologyOther

Multiple Entry Configuration No Accepts Null Yes

Minimum Constraint 1 Maximum Constraint 50

Required in XSD No

Field Values

If value passed for Presumed Cardiac Etiology (eArrest.02) = 3002011 Other, a string /text entry may be passed in CardiacEtiologyOther custom tag. If the value passed in eArrest.02 = 3002009, “Exsanguination” will be automatically saved in our system for this field. If eArrest.02 = 3002005, then “Drug Overdose” will automatically be saved in our system for this field.

If value passed = 3002011, please pass a text value in CardiacEtiologyOther. If value passed in eArrest.02 is 3002009 or 3002005, you may omit the CardiacEtiologyOther tag.

EMS Dataset

Resuscitation Information

Resuscitation Attempted By 911 Responder

(or AED shock given prior to EMS arrival)

eCustomConfiguration - ResusAttemptEMS

Data Format [number]

Definition

Indication of an attempt to resuscitate the patient who is in cardiac arrest. See

V2 Element: E03_01

XSD Data Type xs:integer XSD Domain (Simple Type) ResusAttemptEMS

Multiple Entry Configuration No Accepts Null No

Required in XSD No

Field Values

1 Yes

2 No

**FIELD CHANGED IN 2011**

**REQUIRED FIELD IN 2012**

Who Initiated CPR

eCustomConfiguration - InitiatedCPR

Data Format [number]

Definition

Identifies the initial person to perform CPR.

V2 Element: E03_02

XSD Data Type xs:integer XSD Domain (Simple Type) InitiatedCPR

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Lay Person

2 Lay Person Family Member

3 First Responder (non-transport provider)

4 Responding EMS Personnel

5 Lay Person Medical Provider

8 Not Applicable

**REQUIRED FIELD IN 2012**

Was an AED applied prior to EMS arrival

eArrest.07

Data Format [number]

Definition

XXXXXX

V2 Element: E03_14

XSD Data Type xs:integer XSD Domain (Simple Type) AEDUsedPriorEMS

Multiple Entry Configuration No Accepts Null No

Required in XSD No

Field Values

3007001 No

3007005 Yes, with defibrillation

3007003 Yes, without defibrillation

**NEW FIELD IN 2011**

**REQUIRED FIELD IN 2012**

Who First Applied the AED

CustomConfiguration.WhoFirstAppliedAED

Data Format [number]

Definition Identifies the individual who initially applied/used the AED during the resuscitation.

V2 Element: E03_15

XSD Data Type xs:integer XSD Domain (Simple Type) WhoFirstAppliedAED

Multiple Entry Configuration No Accepts Null Yes

Required in XSD Yes

Field Values

1 Lay Person

2 Lay Person Family Member

3 First Responder (non-EMS)

5 Lay Person Medical Provider

If eArrest.07, Was an AED applied prior to EMS arrival = 3007001 (No), then any value passed in this field will be removed in parsing.

**NEW FIELD IN 2011**

Was AED first applied by Police

eCustomConfiguration - PoliceAED

Data Format [number]

Definition

Identifies the individual who initially applied/used the AED during the resuscitation. Used with WhoFirstAppliedAED if the answer is First Responder (3) and otherwise not answered.

V2 Element: E03_09

XSD Data Type xs:integer XSD Domain (Simple Type) PoliceAED

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

If eArrest.07, Was an AED applied prior to EMS arrival = 3007001 (No), then any value passed in this field will be removed in parsing.

**NEW FIELD IN 2011**

**REQUIRED FIELD IN 2012**

Type of Bystander CPR Provided

eCustomConfiguration - BystanderCPRProvidedID

Data Format [number]

Definition

Describes type of CPR performed by a bystander.

V2 Element: E03_07

XSD Data Type xs:integer XSD Domain (Simple Type) BystanderCPRProvidedID

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Compressions and ventilations

2 Compressions only

3 Ventilations only

**NEW FIELD IN 2011**

Were Dispatcher CPR instructions provided

eCustomConfiguration - CPRInstructionsProvided

Data Format [number]

Definition

Indicates if dispatcher CPR instructions were provided to the caller

V2 Element: E03_08

XSD Data Type xs:integer XSD Domain (Simple Type) CPRInstructionsProvided

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

3 Unknown

**NEW FIELD IN 2011**

Who First Defibrillated the Patient

eCustomConfiguration - FirstDefibPatient

Data Format [number]

Definition

Identifies the individual who was responsible for first defibrillating the patient.

V2 Element: E03_10

XSD Data Type xs:integer XSD Domain (Simple Type) FirstDefibPatient

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Lay Person

2 Lay Person Family Member

3 First Responder (non-EMS)

4 Responding EMS Personnel

5 Lay Person Medical Provider

8 Not Applicable

**NEW FIELD IN 2011**

**REQUIRED FIELD IN 2012**

Did the police first defibrillate the patient

eCustomConfiguration - PoliceDefib

Data Format [number]

Definition

Identifies the individual who was responsible for first defibrillating the patient. Used with custom field FirstDefibPatient – Who first defibrillated the patient- value =3 and otherwise not answered.

V2 Element: E03_11

XSD Data Type xs:integer XSD Domain (Simple Type) PoliceDefib

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

**NEW FIELD IN 2011**

**REQUIRED FIELD IN 2012**

Did 911 Responder perform CPR ***SUPPLEMENTAL***

eCustomConfiguration - 911RespCPR

Data Format [number]

Definition

Indicates if 911 responder (BLS and/or ALS) performed CPR.

V2 Element: E03_12

XSD Data Type xs:integer XSD Domain (Simple Type) 911RespCPR

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

EMS Dataset

First Cardiac/ROSC Information

First Arrest Rhythm of Patient

eCustomConfiguration - FirstRhythm

Data Format [number]

Definition

XXXXXX

V2 Element: E04_01

XSD Data Type xs:integer XSD Domain (Simple Type) FirstRhythm

Multiple Entry Configuration No Accepts Null No

Required in XSD No

Field Values

0 Ventricular Fibrillation

1 Ventricular Tachycardia

2 Asystole

3 Idioventricular/PEA

6 Unknown Shockable Rhythm

7 Unknown Unshockable Rhythm

**REQUIRED FIELD IN 2012**

Sustained ROSC (20 consecutive minutes)

Or present at end of EMS care

eCustomConfiguration - SustainedROSC

Data Format [number]

Definition

Return of Spontaneous Circulation (ROSC) is defined as the restoration of a palpable pulse or a

measurable blood pressure

V2 Element: E04_03

XSD Data Type xs:integer XSD Domain (Simple Type) SustainedROSC

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

2 No

3 Yes, but pulseless at end of EMS care (or ED arrival)

4 Yes, pulse at end of EMS care (or ED arrival)

**FIELD CHANGED IN 2011**

**REQUIRED FIELD IN 2012**

End of the Event

eCustomConfiguration - EndOfEvent

Data Format [number]

Definition

The reason that CPR or other resuscitation efforts were discontinued.

V2 Element: E04_04

XSD Data Type xs:integer XSD Domain (Simple Type) EndOfEvent

Multiple Entry Configuration No Accepts Null No

Required in XSD No

Field Values

1 Pronounced in the Field

2 Pronounced in the ED

3 Ongoing Resuscitation in ED

4 Effort ceased due to DNR

**FIELD CHANGED IN 2011**

**REQUIRED FIELD IN 2012**

When did ROSC first occur ***SUPPLEMENTAL***

eCustomConfiguration - ROSCStart

Data Format [number]

Definition

When did sustained ROSC- Return of Spontaneous Circulation (ROSC) is defined as the restoration of a palpable pulse or a measurable blood pressure, first occur

V2 Element: E03_13

XSD Data Type xs:integer XSD Domain (Simple Type) ROSCStart

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Never

2 After Bystander CPR only

3 After Bystander defib shock

4 After EMS CPR only

5 After EMS Defib. shock

6 After ALS

7 Unknown

EMS Dataset

Time Information

Estimated time of arrest ***SUPPLEMENTAL***

eArrest.14

Data Format [date/time]

Definition

Estimated time of arrest

V2 Element: E05_07

XSD Data Type xs:dateTime XSD Domain (Simple Type) TimeOfArrest

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

**REQUIRED FIELD IN 2012**

Time of 1st defibrillatory shock ***SUPPLEMENTAL***

eCustomConfiguration - DefibTime

Data Format [date/time]

Definition

The time the first defibrillation was given

V2 Element: E05_06

XSD Data Type xs:dateTime XSD Domain (Simple Type) DefibTime

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

Time of 1st CPR ***SUPPLEMENTAL***

eCustomConfiguration - CPRTime

Data Format [date/time]

Definition

The time CPR was first given (by anyone)

V2 Element: E05_03

XSD Data Type xs:dateTime XSD Domain (Simple Type) CPRTime

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

No First Responder dispatched ***SUPPLEMENTAL***

eCustomConfiguration - NoFRDisp

Data Format [number]

Definition

Custom field - single checkbox. Indicates that a 911 first responder was not dispatched

V2 Element: E05_08

XSD Data Type xs:integer XSD Domain (Simple Type) NoFRDisp

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 True

Time call received at dispatch center

eTimes.01

Data Format [date/time]

Definition

The time the original call was received

V2 Element: C01_06

XSD Data Type xs:dateTime XSD Domain (Simple Type) CallReceived

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

**REQUIRED FIELD IN 2012**

Time First Responder dispatched

eTimes.03

Data Format [date/time]

Definition

The time the call was dispatched

V2 Element: C01_07

XSD Data Type xs:dateTime XSD Domain (Simple Type) Dispatched

Multiple Entry Configuration No Accepts Null No

Required in XSD No Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

Since this element is not nillable and does not except NV- please pass min value if no mapping to this field

|1950-01-01T00:00:0000:00 |

| |

**REQUIRED FIELD IN 2012**

Time of First Responder en route

eTimes.05

Data Format [date/time]

Definition

XXXXXX

V2 Element: E05_09

XSD Data Type xs:dateTime XSD Domain (Simple Type) FREnRoute

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

**REQUIRED FIELD IN 2012**

Time Ambulance dispatched ***SUPPLEMENTAL***

eCustomConfiguration - AmbDispatched

Data Format [date/time]

Definition

XXXXXX

V2 Element: E05_10

XSD Data Type xs:dateTime XSD Domain (Simple Type) AmbDispatched

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

Time for Ambulance en route ***SUPPLEMENTAL***

eCustomConfiguration - AmbEnRoute

Data Format [date/time]

Definition

XXXXXX

V2 Element: E05_11

XSD Data Type xs:dateTime XSD Domain (Simple Type) AmbEnRoute

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

Time First Responder arrived at scene

eTimes.06

Data Format [date/time]

Definition

The time the EMS vehicle arrived on scene

V2 Element: C01_09

XSD Data Type xs:dateTime XSD Domain (Simple Type) OnScene

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

**REQUIRED FIELD IN 2012**

Time Ambulance arrived at scene ***SUPPLEMENTAL***

eCustomConfiguration - AmbArrivedAtScene

Data Format [date/time]

Definition

XXXXXX

V2 Element: E05_12

XSD Data Type xs:dateTime XSD Domain (Simple Type) AmbArrivedAtScene

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

Time EMS arrived at patient side ***SUPPLEMENTAL***

eTimes.07

Data Format [date/time]

Definition

XXXXXX

V2 Element: E05_13

XSD Data Type xs:dateTime XSD Domain (Simple Type) EMSArrivedAtScene

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

Time Ambulance left scene ***SUPPLEMENTAL***

eCustomConfiguration - AmbLeftScene

Data Format [date/time]

Definition

XXXXXX

V2 Element: E05_14

XSD Data Type xs:dateTime XSD Domain (Simple Type) AmbLeftScene

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

Time Ambulance arrived at ED ***SUPPLEMENTAL***

eCustomConfiguration - AmbArrivedAtED

Data Format [date/time]

Definition

XXXXXX

V2 Element: E05_15

XSD Data Type xs:dateTime XSD Domain (Simple Type) AmbArrivedAtED

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

EMS Dataset

Hypothermia Information

Was hypothermia care provided in the field

eArrest.10

Data Format [number]

Definition

XXXXXX

V2 Element: E06_01

XSD Data Type xs:integer XSD Domain (Simple Type) HypoProvided

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

9923003 Yes

9923001 No

**REQUIRED FIELD IN 2011**

Section E07

EMS Dataset

EMS Interventions

Mechanical CPR device used ***SUPPLEMENTAL***

eCustomConfiguration - MechCPRDevice

Data Format [number]

Definition

Indicates if a mechanical CPR device was used during the course of resuscitation at the ED

V2 Element: E07_01

XSD Data Type xs:integer XSD Domain (Simple Type) MechCPRDevice

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

Mechanical CPR device used detail ***SUPPLEMENTAL***

eCustomConfiguration - MechCPRDeviceID

Data Format [number]

Definition

Associated with MechCPRDevice, if yes, specify which device was used

V2 Element: E07_02

XSD Data Type xs:integer XSD Domain (Simple Type) MechCPRDeviceID

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Load-Distributing Band (AutoPulse)

2 Active Compression Decompression (LUCAS™ Device)

3 Mechanical Piston

4 Other

Automated CPR feedback device used ***SUPPLEMENTAL***

eCustomConfiguration - CPRFeedbackDevice

Data Format [number]

Definition

Indicates if CPR Feedback device was used

V2 Element: E07_03

XSD Data Type xs:integer XSD Domain (Simple Type) CPRFeedbackDevice

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

Advanced airway successfully placed in the field ***SUPPLEMENTAL***

eAirway.02

Data Format [number]

Definition

This field maps to a xs:dateTime NEMSIS field eAirway.02. To use eAirway.03, you must pass a datetime value in this field. If the exact time is not known, pass servicedate with midnight. The logic for the answer choice "No" really means the airway attempt was "Unsuccessful" and that the airway placement was attempted.

It does NOT mean that the question was not applicable, not documented, etc. Not Values for this field will not be mapped.

eAirway.02 (Was advanced airway placed successfully in the field) is of datetime type. If you pass a date for this greater than the minInclusive value for this element, we will record this as a "Yes" answer. If you pass the minInclusive value of 1950-01-01T00:00:00-00:00 we will record a "No".

V2 Element: E07_04

XSD Data Type xs:dateTime XSD Domain (Simple Type) AdvAirway

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

Examples:

Pass a "No" value:

1950-01-01T00:00:00-00:00

Pass a “Yes” with Combitube value

2013-06-04T00:00:00-08:00

4003007

| |

Advanced airway successfully placed in the field detail ***SUPPLEMENTAL***

eAirway.03

Data Format [number]

Definition

To use this field, you must pass a datetime value for eAirway.02

V2 Element: E07_05

XSD Data Type xs:integer XSD Domain (Simple Type) AdvAirwayID

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

4003007 Combitube

4003009 King airway

4003011 LMA

4003003 Oral/Nasal ET

4003001 Other

4003013 Other

4003015 Other

4003005 Other

ITD used ***SUPPLEMENTAL***

eCustomConfiguration - ITD

Data Format [number]

Definition

Was an ITD device used during resuscitation.

V2 Element: E07_06

XSD Data Type xs:integer XSD Domain (Simple Type) ITD

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

ITD used detail ***SUPPLEMENTAL***

eCustomConfiguration - ITDID

Data Format [number]

Definition

If the device is used during resuscitation, the method of how it was used should be indicated. If ITD=Yes, then indicate method.

V2 Element: E07_07

XSD Data Type xs:integer XSD Domain (Simple Type) ITDID

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Bag valve mask

2 Endotracheal tube

3 Combitube

4 King Airway

5 LMA

6 Oral/Nasal ET

7 Other

Were drugs administered ***SUPPLEMENTAL***

eCustomConfiguration - DrugAdministration

Data Format [number]

Definition

Describes drugs that were administered during ED resuscitation.

V2 Element: E07_08

XSD Data Type xs:integer XSD Domain (Simple Type) DrugAdministration

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

Were drugs administered detail ***SUPPLEMENTAL***

eMedications.03

Data Format [number]

Definition

To pass “Other”- refer to custom element MedicationOther, all other codes are from RXNorm.

V2 Element: E07_09

XSD Data Type xs:integer XSD Domain (Simple Type) DrugAdministrationID

Multiple Entry Configuration Yes Accepts Null Yes

Required in XSD No

Field Values(RXNorm)

317361 Epinephrine 0.1mg/ml

1223 Atropine

703 Amiodarone

36676 Sodium Bicarbonate

237653 Dextrose

6387 Lidocaine

11149 Vasopressin

To pass “Other” medication, correlate this element to custom element in the group tag.

Were drugs administered detail - Other

eCustomConfiguration - MedicationOther

Data Format [string]

Definition

Field used to pass “Other” value for Medication (eMedication.03)

V2 Element: None

XSD Data Type xs:string XSD Domain (Simple Type) MedicationOther

Multiple Entry Configuration No Accepts Null Yes

Minimum Constraint 3 Maximum Constraint 3

Required in XSD No

Field Values

099 Other

099

MedicationOther

eMed

Vascular access ***SUPPLEMENTAL***

eCustomConfiguration - VascularAccessID

Data Format [number]

Definition

Describes which, if any, devices were inserted into a vein, which permits administration of intermittent or continuous infusion of parenteral solutions or medications

V2 Element: E07_10

XSD Data Type xs:integer XSD Domain (Simple Type) VascularAccessID

Multiple Entry Configuration Yes Accepts Null Yes

Required in XSD No

Field Values

1 No IV

2 IV

3 IO

12 Lead ***SUPPLEMENTAL***

eCustomConfiguration - 12Lead

Data Format [number]

Definition

Indicates use of a 12 Lead- An 12 lead electrocardiogram (ECG) is a recording of the electrical activity of the heart using specific wires (leads) place on the chest wall and extremities

V2 Element: E07_11

XSD Data Type xs:integer XSD Domain (Simple Type) 12Lead

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

STEMI ***SUPPLEMENTAL***

eCustomConfiguration - STEMI

Data Format [number]

Definition

Indicates a myocardial infarction with ST elevation

V2 Element: E07_12

XSD Data Type xs:integer XSD Domain (Simple Type) STEMI

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

3 Unknown

STEMI detail ***SUPPLEMENTAL***

eCustomConfiguration - STEMIID

Data Format [number]

Definition

Custom Field associated with STEMI. If yes, please select location of anatomical region of the heart that has developed myocardial necrosis

V2 Element: E07_13

XSD Data Type xs:integer XSD Domain (Simple Type) STEMIID

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Anterior

2 Inferior

Hospital Dataset

Hospital Information

Passing Destination hospital and Transfer Hospital data

Hospital information in an import may provide outcome data for either a destination or a transfer hospital the following ways. The hospital form fields are interdependent and must follow the below logic.

Transfer with Complete or Partial Hospital Outcome Data from Transfer Hospital:

Destination Hospital Elements and Data (no other element values will be parsed)

• EROutcome must = 4 (Transferred)

• Hypothermia_Provided_Hosp can be answered

• Transfer_hospitalid or Transfer_hospital should be answered

Transfer Hospital Elements and Data

• If EROutcomeTrans= 5, the following elements can contain values:

o HospOutcomeTrans can be answered

o HospOutcomeDNRTrans can be answered

o If HospOutcomeTrans or HospOutcomeDNRTrans=2, the following fields may contain values

HospDispositionTrans

NeuroOutcomeTrans can be answered if there is a value for HospDispositionTrans

Hospital Data for Destination Hospital ONLY:

Destination Hospital Elements and Data

• EROutcome must not = 4 (Transferred)

• Hypothermia_Provided_Hosp can be answered

• HospOutcome can be answered

• HospOutcomeDNR can be answered

• eOutcome.02 can be answered if ER or HospOutcome= Discharged Alive

• eArrest.13 can be answered if ER or HospOutcome= Discharged Alive and eOutcome.02 contains a value

• Transfer_hospitalid or Transfer_hospital should be answered only if HospOutcome or HospOutcomeDNR = transferred

• if HospOutcome or HospOutcomeDNR = transferred, eOutcome.02 and eArrest.13 will not be parsed

Transfer Hospital Elements and Data

• None of these elements for transfer hospital will be parsed

Emergency Room Outcome (Destination Hospital)

eCustomConfiguration - EROutcome

Data Format [number]

Definition

The final disposition of the patient from the emergency department.

Usage Notes:

This element is used for the destination hospital only.

See EROutcomeTransfer element if value = 4 (Transferred). If value=4, please use the Transfer Hospital fields. You may pass values for Hypothermia_Provided_Hosp for the Destination Hospital and should pass either Transfer_hospitalId or Transfer_Hospital values, but values passed in the following elements will not be parsed:

• HospOutcome

• HospOutcomeDNR

• eOutcome.02

• eArrest.13

V2 Element: H01_01

XSD Data Type xs:integer XSD Domain (Simple Type) EROutcome

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1. Resuscitation terminated in ED

4. Transferred to another acute care facility from the ED

5 Admitted to hospital

**FIELD CHANGED IN 2011**

Was hypothermia care initiated/continued in the hospital (Destination Hospital)

eCustomConfiguration - Hypothermia_Provided_Hosp

Data Format [number]

Definition

Was hypothermia care initiated or continued in the destination hospital

V2 Element: H01_06

XSD Data Type xs:integer XSD Domain (Simple Type) Hypothermia_Provided_Hosp

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

**REQUIRED FIELD IN 2011**

Hospital Outcome (Destination Hospital)

eCustomConfiguration - HospOutcome

Data Format [number]

Definition

The final disposition of the patient from the hospital. See HospOutcomeDNR if value =4 (Patient made DNR).

Usage Notes:

If the value passed is 3 (Transferred to another acute care hospital) or the value passed is 4 and HospOutcomeDNR is 3 (Transferred to another acute care hospital), any values passed for eOutcome.02 and eArrest.13 are not parsed. The Transfer hospital must enter in these values manually.

V2 Element: H01_02

XSD Data Type xs:integer XSD Domain (Simple Type) HospOutcome

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Died in the hospital

2 Discharged Alive

3 Transferred to another acute care hospital

4 Patient made DNR

11 Not yet determined

**FIELD CHANGED IN 2011**

Patient made DNR Detail (Destination Hospital)

eCustomConfiguration - HospOutcomeDNR

Data Format [number]

Definition

Custom field associated with Hospital Outcome (HospOutcome). If Patient made DNR (code=4), identify hospital outcome

Usage Notes:

If HospOutcome value passed is 3 (Transferred to another acute care hospital) or the value passed is 4 and HospOutcomeDNR is 3 (Transferred to another acute care hospital), any values passed for eOutcome.02 and eArrest.13 are not parsed. The Transfer hospital must enter in these values manually.

V2 Element: H01_08

XSD Data Type xs:integer XSD Domain (Simple Type) HospOutcomeDNR

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Died in the hospital

2 Discharged alive

3 Transferred to another acute care hospital

8 Not yet determined

**NEW FIELD IN 2011**

Discharge From the Hospital (Destination Hospital)

eOutcome.02

Data Format [number]

Definition

Discharge status from the hospital for Destination Hospital ONLY

Usage Notes:

This element’s value is only recorded if the HospOutcome or HospOutcomeDNR value = “Discharged Alive”

V2 Element: H01_03

XSD Data Type xs:integer XSD Domain (Simple Type) HospDisposition

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

01 Home/Residence

62 Rehabilitation facility

03 Skilled nursing facility/Hospice

51 Skilled nursing facility/Hospice

**REQUIRED FIELD IN 2012**

Neurological Outcome at Discharge From Hospital (Destination Hospital)

eArrest.13

Data Format [number]

Definition

Discharge status from the hospital for Destination Hospital ONLY

Usage Notes:

This element’s value is only recorded if the HospOutcome or HospOutcomeDNR value = “Discharged Alive” and eOutcome.02 contains a value.

V2 Element: H01_04

XSD Data Type xs:integer XSD Domain (Simple Type) NeuroOutcome

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

3013001 Good Cerebral Performance (CPC 1)

3013003 Moderate Cerebral Disability (CPC 2)

3013005 Severe Cerebral Disability (CPC 3)

3013007 Coma, vegetative state (CPC 4)

**FIELD CHANGED IN 2011**

Emergency Room Outcome (Transfer Hospital)

eCustomConfiguration - EROutcomeTrans

Data Format [number]

Definition

The final disposition of the patient from the emergency department for the Transfer Hospital ONLY.

Usage Notes:

This element is used for the transfer hospital and is only used if the EROutcome value for destination hospital = 4.

XSD Data Type xs:integer XSD Domain (Simple Type) EROutcomeTrans

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1. Resuscitation terminated in ED

4 Transferred to another acute care facility from the ED

5 Admitted to hospital

Hospital Outcome (Transfer Hospital)

eCustomConfiguration - HospOutcomeTrans

Data Format [number]

Definition

The final disposition of the patient from the hospital for the Transfer Hospital ONLY.

Usage Notes:

If the HospitalOutcomeTrans value passed is 3 (Transferred to another acute care hospital) or the value passed is 4 and HospOutcomeDNR is 3 (Transferred to another acute care hospital), any values passed for NeuroOutcomeTrans and HospDispositionTrans are not parsed. The Transfer hospital must enter in these values manually.

See follow-up question HospOutcomeDNRTrans if value =4 (Patient made DNR).

XSD Data Type xs:integer XSD Domain (Simple Type) HospOutcomeTrans

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Died in the hospital

2 Discharged Alive

3 Transferred to another acute care hospital

4 Patient made DNR

11 Not yet determined

**FIELD CHANGED IN 2011**

Patient made DNR Detail (Transfer Hospital)

eCustomConfiguration - HospOutcomeDNRTrans

Data Format [number]

Definition

Custom field associated with Hospital Outcome (HospOutcomeTrans =4)

NOTES: If HospOutcomeTrans value passed is 3 (Transferred to another acute care hospital) or the value passed is 4 and HospOutcomeDNRTrans is 3 (Transferred to another acute care hospital), any values passed for NeuroOutcomeTrans and HospDispositionTrans are not parsed. The Transfer hospital must enter in these values manually.

XSD Data Type xs:integer XSD Domain (Simple Type) HospOutcomeDNRTrans

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Died in the hospital

2 Discharged alive

3 Transferred to another acute care hospital

8 Not yet determined

**NEW FIELD IN 2011**

Discharge From the Hospital (Transfer Hospital)

eCustomConfiguration - HospDispositionTrans

Data Format [number]

Definition

Discharge status from the hospital for Transfer Hospital ONLY

Notes:

This element’s value is only recorded if the HospOutcomeTrans or HospOutcomeDNRTrans value = “Discharged Alive”

XSD Data Type xs:integer XSD Domain (Simple Type) HospDispositionTrans

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

01 Home/Residence

62 Rehabilitation facility

03 Skilled nursing facility/Hospice

51 Skilled nursing facility/Hospice

**REQUIRED FIELD IN 2012**

Neurological Outcome at Discharge From Hospital (Transfer Hospital)

eCustomConfiguration - NeuroOutcomeTrans

Data Format [number]

Definition

Discharge status from the hospital for Transfer Hospital ONLY

Usage Notes:

This element’s value is only recorded if the HospOutcomeTrans or HospOutcomeDNRTrans value = “Discharged Alive” and HospDispositionTrans contains a value.

XSD Data Type xs:integer XSD Domain (Simple Type) NeuroOutcomeTrans

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

3013001 Good Cerebral Performance (CPC 1)

3013003 Moderate Cerebral Disability (CPC 2)

3013005 Severe Cerebral Disability (CPC 3)

3013007 Coma, vegetative state (CPC 4)

**FIELD CHANGED IN 2011**

Was hypothermia care initiated/continued in the hospital (Transfer Hospital)

eCustomConfiguration - Hypothermia_Provided_Hosp_Trans

Data Format [number]

Definition

Was hypothermia care initiated or continued in the transfer hospital ONLY

XSD Data Type xs:integer XSD Domain (Simple Type) Hypothermia_Provided_Hosp_Trans

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

**REQUIRED FIELD IN 2011**

Transfer To Hospital

eCustomConfiguration - Transfer_hospitalid

Data Format [number]

Definition

Hospital code patient was transferred to (CARES code)

V2 Element: H01_05

XSD Data Type xs:integer XSD Domain (Simple Type) Transfer_hospitalid

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

Must be a valid hospital import value set up in

Transfer To Hospital - Detail

eCustomConfiguration - Transfer_hospital

Data Format [number]

Definition

If the hospital code patient was transferred to (CARES code) is not available, then this string would be the name of the hospital. See Transfer_hospitalid custom element.

V2 Element: H01_05

XSD Data Type xs:integer XSD Domain (Simple Type) Transfer_hospital

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

If the hospital (import value) patient was transferred to (CARES code) is not available, then this string would be the name of the hospital

Was the final diagnosis acute myocardial infarction ***SUPPLEMENTAL***

eCustomConfiguration - MyocardialInfarction

Data Format [number]

Definition

Hospital data- Was the final diagnosis acute myocardial infarction

V2 Element: H01_09

XSD Data Type xs:integer XSD Domain (Simple Type) MyocardialInfarction

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

Coronary Angiography Performed ***SUPPLEMENTAL***

eCustomConfiguration - CoronaryAgiography

Data Format [number]

Definition

Hospital data- Was a Coronary Angiography Performed

V2 Element: H01_10

XSD Data Type xs:integer XSD Domain (Simple Type) CoronaryAngiography

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

3 Unknown

Coronary Angiography Date/Time ***SUPPLEMENTAL***

eCustomConfiguration - CoronaryAngiographyDateTime

Data Format [date/time]

Definition

Hospital data- If Coronary Angiography Performed is yes, provide date and time

V2 Element: H01_11 and H01_12

XSD Data Type xs:dateTime XSD Domain (Simple Type) CoronaryAngiographyDate

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No Minimum Constraint 2000 Maximum Constraint 2050

Field Values

● Valid date/time

Was a cardiac stent placed ***SUPPLEMENTAL***

eCustomConfiguration - CardiacStent

Data Format [number]

Definition

Hospital data- Was a cardiac stent placed

V2 Element: H01_13

XSD Data Type xs:integer XSD Domain (Simple Type) CardiacStent

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

3 Unknown

CABG performed ***SUPPLEMENTAL***

eCustomConfiguration - CABGPerformed

Data Format [number]

Definition

Hospital data- was a CABG performed

V2 Element: H01_14

XSD Data Type xs:integer XSD Domain (Simple Type) CABGPerformed

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

3 Unknown

Was an ICD placed and/or scheduled ***SUPPLEMENTAL***

eCustomConfiguration - ICDPlaced

Data Format [number]

Definition

Hospital data- Was an ICD placed and/or scheduled

V2 Element: H01_15

XSD Data Type xs:integer XSD Domain (Simple Type) ICDPlaced

Multiple Entry Configuration No Accepts Null Yes

Required in XSD No

Field Values

1 Yes

2 No

3 Unknown

Index

|Data Element |Number |Page |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download