Transcription
EMSISNHTSA Version 2.2Data Dictionary(Nebraska Minimum Data Set)WWW.NEMSIS.ORG2005.12
IntroductionThe EMS data set is a subset of the information required to describe a complete EMS event. The complete andaccurate documentation of clinical care is important to the EMS system, EMS personnel, and the patient. Theinformation collected by the EMS providers is valuable for public health officials to identify the risk factors thatresult in disease and injuries. Once the risk factors are identified prevention and control strategies are developto enhance the lives of Nebraskans.Why is it necessary to have a “Nebraska Data Dictionary”? There are over 400 emergency medical services inNebraska. Various methods and systems for EMS data collection are used by these services. In order to makeNebraska’s EMS patient care data accurate and comparable, including the ability to evaluate and improve theperformance of EMS it is crucial to determine a uniform minimum data set. Sufficient detail about each dataelement must also be included to justify its inclusion in the minimum data set.Nebraska EMS and Trauma Rules and Regulations provide the bases for the Nebraska data elements containedin the Nebraska data dictionary. The entire dictionary will be known as Nebraska’s EMS Data Set.The NEMSIS (National Emergency Medical Services Information System) data element definitions are used togive definition to the data elements contained in the Nebraska EMS Data Set. By using the NEMSIS datadefinitions Nebraska will be consistent with the Nation.The EMS Program recognizes that the lists that are included in this dictionary are not perfect; however theyprovide a starting point for EMS data to evolve.
Table of ContentsEMSDatasetNumberNEMSIS Data ent Care Report Number4.A124E2.1EMS Agency Number4.A129E2.2Incident #4.A130E2.5Primary Roll of Unit20133E2.6Type of Dispatch Delay21134E2.7Type of Response Delay21135E2.8Type of Scene Delay21136E2.9Type of Transport Delay21137E4.1Crew Member ID12154E4.2Crew Member Role155E4.3Crew Member Level156E5.1Incident or Onset Date/TimeE5.4Unit Notified by Dispatch Date/Time33.A & B1584.C161E5.5Unit Enroute Date/Time4E5.6Unit Arrived on Scene Date/Time54.D163E5.9Unit Left Scene Date/Time154.E.1166E5.10Patient Arrived at Destination Date/Time164.E.2167E5.11Unit Back in Service Date/Time17E6.1Last Name11.A172E6.2First Name11.A173162168E6.3Middle D183E6.13Ethnicity18E6.14Age11.E185E6.15Age Units11.E186E8.7Incident Location Type143.F237E8.11Incident Address2241E8.12Incident City2242E8.13Incident County2243E8.14Incident State2244E8.15Incident Zip Code2E9.5Chief Complaint Narrative6251E9.6Duration of Chief Complaint6252E9.7Time Units of Chief Complaint6253E9.8Secondary Chief Complaint6254E9.9Duration of Secondary Complaint6255E9.13Primary Symptom6259E9.14Other Associated Symptoms6260E10.1Cause of Injury1843.C3.E245265
E10.3Mechanism of Injury3.E268E10.8Use of Occupant Safety tasetNumberNEMSIS Data ElementStateEMSR/RE10.9Airbag DeploymentE11.9Date/Time Resuscitation Discontinued22285E12.1Barriers to Patient Care21289E12.8Medication Allergies8296E12.9Environmental/Food Allergies8297E12.10Medical/Surgical History8298E12.11Medical History Obtained From8299E12.12Immunization History8300E12.13Immunization Date8301E12.14Current Medications8302E12.15Current Medication Dose8303E12.16Current Medication Dosage Unit8304E12.17Current Medication Administration Route8305E12.20Pregnancy8308E14.1Date/Time Vital Signs Taken7312E14.2Obtain Prior to this Units EMS Care13313E14.4SBP (Systolic Blood Pressure)74.F.1315E14.5DBP (Diastolic Blood Pressure)74.F.1316E14.6Method of Blood Pressure7E14.7Pulse Rate7E14.10Pulse Rhythm7E14.11Respiratory Rate7E14.12Respiratory Effort7E14.15GCS Eye234.F.4326E14.16GCS Verbal234.F.4327E14.17GCS Motor234.F.43283174.F.23183214.F.3322323E14.18GCS Qualifier234.F.4329E14.19Total GCS (Glasgow Coma Score)234.F.4330E14.27RTS (Revised Trauma Score)244.F.5338E14.28Pediatric Trauma Score244.F.5339E18.1Date/Time Medication AdministeredE18.2Medication Administered Prior to this Units EMS CareE18.39, 25, 263809, 13381Medication Given9, 25, 26382E18.4Medication Administered Route9, 25, 26383E18.5Medication Dosage9, 25, 26384E18.6Medication Dosage Units9, 25, 26385E18.7Response to Medication9386E18.9Medication Crew Member ID9388E18.10Medication Authorization9389E19.1Date/Time Procedure Performed Successfully9392E19.2Procedure Performed Prior to this Units EMS Care13393E19.3Procedure94.F.6394
EMSDatasetNumberNEMSIS Data e of Procedure Equipment9395E19.5Number of Procedure Attempts9396E19.6Procedure Successful9397E19.7Procedure Complication9398E19.8Response to Procedure9, 10399E19.9Procedure Crew Members ID9400E19.12Successful IV Site9403E19.13Tube Confirmation9404E20.1Destination/Transferred To, Name11407E20.10Incident/Patient Disposition20E20.16Reasoning for Choosing Destination19E20.17Type of Destination19423E21.1Event Date/Time10425E21.5AED, Pacing, or CO2 Mode10429E21.8Type of Shock10432E21.9Shock or Pacing Energy10433E21.10Total Number of Shocks Delivered10434E21.11Pacing Rate104354164.B422
Section E00Common EMS ValuesSection E00Common EMS Values2005 NHTSA Uniform PreHospital Dataset V.2.20Page 121 of 463
COMMON NULL VALUESE00Data Format [combo] single-choiceDefinitionThese values are to be used in each of the Demographic and EMS Data Elements described in this document which havebeendefined to accept the E00 Null Values. Please include these variables in the implementation of the NHTSA Version 2 Dataset.Field Values-25 Not Applicable-15 Not Reporting-5 Not Available-20 Not Recorded-10 Not KnownAdditional Information For any collection of data to be of value and reliably represent what was intended, a strong commitment must be made toensure the correct documentation of incomplete data . The described data integrity method must be followed with theNHTSA dataset For data elements being electronically stored in a database or moved from one database to another usingXML, the indicated values should be applied when a data element is empty or contains a null value. Not Applicable: (Code -25) At the time of an EMS patient care report documentation, information requested was “NotApplicable” to the EMS or patient event. This indicates that it is unnecessary to document mechanism or injury relatedinformation on a patient who was not traumatized Not Available: (Code -5) At the time of an EMS patient care report documentation, information was “Not Available” to EMSpersonnel. This documents that needed information did exist but the EMS personnel was unsuccessful in their attempt toobtain it Not Known: (Code -10) At the time of an EMS patient care report documentation, information was “Not Known” to patient,family, and EMS personnel. This documents that there was an attempt to obtain information but it was unknown by allparties involved Not Recorded: (Code -20) If an EMS documentation or information system has an empty field or nothing is recorded in anydata element of the NHTSA dataset, code “-20” should be inserted into the database and/or XML for that data elementindicating that the EMS Patient Care Report did not have a value for that specific data element when the EMS event orpatient encounter was documented Not Reporting: (Code -15) If an EMS documentation or information system is not using any of the "National" data elementsof the NHTSA dataset, code “-15” should be inserted into the database and/or XML for that data element.Section E00Common EMS Values2005 NHTSA Uniform PreHospital Dataset V.2.20Page 122 of 463
Section E01Record InformationSection E01Record Information2005 NHTSA Uniform PreHospital Dataset V.2.20Page 123 of 463
PATIENT CARE REPORT NUMBERNational ElementData Format [text]E01 01DefinitionThe unique number automatically assigned by the EMS agency for each patient care report (PCR). This is a unique numberto theEMS agency for all of time.XSD Data Typexs:stringMultiple Entry Configuration NoRequired in XSD YesXSD Domain (Simple Type) PatientCareReportNumberAccepts NullNoMinimum Constraint 3Maximum Constraint 32Field ValuesA unique value; no variable list is possible.Additional Information Not Nullable. A unique value must be provided to create a unique record ID within a databaseUses A component of the EMS Medical Record: Patient Care Report Agency number (E02 01), agency state (D01 03),unit call sign (E02 12), patient number (E01 01) and date (E05 04)combine to create a unique identifierData Collector EMS agency or may be electronically provided through the 911 or dispatch centerOther Associated ElementsE01 01 Patient Care Report NumberReferences in NHTSA Version 1Desirable Element 23Patient Care Record NumberReferences to Other Databases NFIRS 5.0 EMS Module; Title: Patient Number; Unique NumberState Regulations Nebraska Trauma Regulation 4.ASection E01Record Information2005 NHTSA Uniform PreHospital Dataset V.2.20Page 124 of 463
Section E02Unit/ Agency InformationSection E02Unit/ Agency Information2005 NHTSA Uniform PreHospital Dataset V.2.20Page 128 of 463
EMS AGENCY NUMBERNational ElementData Format [text]E02 01DefinitionThe state-assigned provider number of the responding agencyXSD Data Typexs:stringMultiple Entry Configuration NoRequired in XSD YesXSD Domain (Simple Type) EMSAgencyNumberAccepts NullNoMinimum Constraint 3Maximum Constraint 15Field ValuesA unique value; no variable list is possible.Additional Information Not Nullable. A unique value must be provided to create a unique record ID within a database Same as EMS Agency Number (D01 01)Uses A component of the EMS Medical Record: Patient Care Report Agency number (E02 01), agency state (D01 03),unit call sign (E02 12), patient number (E01 01) and date (E05 04)combine to create a unique identifier Allows data to be sorted by the EMS Agency Important for grouping and comparing EMS Agencies in Benchmarking and Quality Management When linked to D01 02 provides the Agency name on the EMS Medical Record: Patient Care ReportData Collector Typically generated by the State EMS Regulatory Office. Collected by the EMS agency or auto-generated by the EMSagency specific software.Other Associated ElementsE01 01 Patient Care Report NumberReferences to Other Databases NFIRS 5.0 EMS Module;Title: FDID; State assigned Fire Department ID numberState Regulations Nebraska Trauma Regulation 4.ASection E02Unit/ Agency Information2005 NHTSA Uniform PreHospital Dataset V.2.20Page 129 of 463
INCIDENT NUMBERE02 02Data Format [text]DefinitionThe incident number assigned by the 911 Dispatch SystemXSD Data Typexs:stringMultiple Entry Configuration NoRequired in XSD NoXSD Domain (Simple Type) IncidentNumberAccepts NullYesMinimum Constraint 2Maximum Constraint 15Field Values-25 Not Applicable-5 Not Available-10 Not Known Relevant Value for Data Element & Patient CareUses Component of the EMS Agency 911 or Dispatch information which serves as a link to identify and report other DispatchinformationData Collector 911 or Dispatch Center and electronically or verbally transmitted to the EMS agencyOther Associated ElementsE00Common Null ValuesE01 01 Patient Care Report NumberReferences in NHTSA Version 1Essential Element 21Incident NumberReferences to Other Databases NFIRS 5.0 EMS Module; Title: Incident Number; Unique number for each IncidentState Regulations Nebraska Trauma Regulation 4.ASection E02Unit/ Agency Information2005 NHTSA Uniform PreHospital Dataset V.2.20Page 130 of 463
PRIMARY ROLE OF THE UNITNational ElementData Format [combo] single-choiceE02 05DefinitionThe primary role of the EMS service which was requested for this specific EMS incident.XSD Data Typexs:integerMultiple Entry Configuration NoRequired in XSD YesXSD Domain (Simple Type) PrimaryRollOfTheUnitAccepts NullNoField Values60 Non-Transport70 Supervisor65 Rescue75 TransportUses A component of the EMS Medical Record: Patient Care Report Allows data to be sorted by the role of the responder Provides descriptive data on EMS call volume and service providedData Collector EMS agency or may be electronically provided through the 911 or dispatch centerOther Associated ElementsE01 01 Patient Care Report NumberSection E02Unit/ Agency Information2005 NHTSA Uniform PreHospital Dataset V.2.20Page 133 of 463
TYPE OF DISPATCH DELAYNational ElementData Format [combo] multiple-choiceE02 06DefinitionThe dispatch delays, if any, associated with the dispatch of the EMS unit to the patient encounterXSD Data Typexs:integerMultiple Entry Configuration YesRequired in XSD YesXSD Domain (Simple Type) TypeOfDispatchDelayAccepts NullYesField Values-25-108090100110120Not ApplicableNot KnownCaller (Uncooperative)Language BarrierNo Units AvailableOtherTechnical Failure (Computer, Phone etc.)-15-58595105115Not ReportingNot AvailableHigh Call VolumeLocation (Inability to Obtain)NoneScene Safety (Not Secure for EMS)Uses Allows data to describe the status of Dispatch issuesData Collector 911 or Dispatch Center and electronically or verbally transmitted to the EMS agencyOther Associated ElementsE00Common Null ValuesE01 01 Patient Care Report NumberReferences in NHTSA Version 1Desirable Element 56Factors Affecting EMS Delivery of CareState Regulations Nebraska EMS Regulation 21Section E02Unit/ Agency Information2005 NHTSA Uniform PreHospital Dataset V.2.20Page 134 of 463
TYPE OF RESPONSE DELAYNational ElementData Format [combo] multiple-choiceE02 07DefinitionThe response delays, if any, of the unit associated with the patient encounterXSD Data Typexs:integerMultiple Entry Configuration YesRequired in XSD YesXSD Domain (Simple Type) TypeOfResponseDelayAccepts NullYesField Values-25-10125135145155165175185Not ApplicableNot KnownCrowdDistanceHazMatOtherStaff DelayVehicle CrashWeather-15-5130140150160170180Not ReportingNot le FailureUses Allows data describe Vehicle Failures and Vehicle Crashes Allows data to describe the status of Response issuesData Collector EMS personnelOther Associated ElementsE00Common Null ValuesE01 01 Patient Care Report NumberReferences in NHTSA Version 1Desirable Element 56Factors Affecting EMS Delivery of CareState Regulations Nebraska EMS Regulation 21Section E02Unit/ Agency Information2005 NHTSA Uniform PreHospital Dataset V.2.20Page 135 of 463
TYPE OF SCENE DELAYNational ElementData Format [combo] multiple-choiceE02 08DefinitionThe scene delays, if any, of the unit associated with the patient encounterXSD Data Typexs:integerMultiple Entry Configuration YesRequired in XSD YesXSD Domain (Simple Type) TypeOfSceneDelayAccepts NullYesField Values-25-10190200210220230240250260Not ApplicableNot KnownCrowdDistanceExtrication 20 min.Language BarrierOtherStaff DelayVehicle CrashWeather-15-5195205215225235245255Not ReportingNot cVehicle FailureUses Allows data describe Vehicle Failures and Vehicle Crashes Allows data to describe the status of Scene issuesData Collector EMS personnelOther Associated ElementsE00Common Null ValuesE01 01 Patient Care Report NumberReferences in NHTSA Version 1Desirable Element 56Factors Affecting EMS Delivery of CareState Regulations Nebraska EMS Regulation 21Section E02Unit/ Agency Information2005 NHTSA Uniform PreHospital Dataset V.2.20Page 136 of 463
TYPE OF TRANSPORT DELAYNational ElementData Format [combo] multiple-choiceE02 09DefinitionThe transport delays, if any, of the unit associated with the patient encounterXSD Data Typexs:integerMultiple Entry Configuration YesRequired in XSD YesXSD Domain (Simple Type) TypeOfTransportDelayAccepts NullYesField Values-25-10265275285295305315325Not ApplicableNot KnownCrowdDistanceHazMatOtherStaff DelayVehicle CrashWeather-15-5270280290300310320Not ReportingNot le FailureUses Allows data describe Vehicle Failures and Vehicle Crashes Allows data to describe the status of Transport issuesData Collector EMS personnelOther Associated ElementsE00Common Null ValuesE01 01 Patient Care Report NumberReferences in NHTSA Version 1Desirable Element 56Factors Affecting EMS Delivery of CareState Regulations Nebraska EMS Regulation 21Section E02Unit/ Agency Information2005 NHTSA Uniform PreHospital Dataset V.2.20Page 137 of 463
Section E04Unit/ PersonnelInformationSection E04Unit/ Personnel Information2005 NHTSA Uniform PreHospital Dataset V.2.20Page 153 of 463
CREW MEMBER IDE04 01Data Format [text]DefinitionThe State Certification/Licensure ID number assigned to the crew memberXSD Data Typexs:stringXSD Domain (Simple Type) CrewMemberIDMultiple Entry Configuration Yes, via structureAccepts NullYesRequired in XSD NoMinimum Constraint 2Maximum Constraint 15XSD Structure: E04 01, E04 02, E04 03 are all members of the E04 Unit Personnel Information structureField Values-25 Not Applicable-5 Not Available-10 Not Known Relevant Value for Data Element & Patient CareAdditional Information A multiple entry configuration to allow all crew members to be entered Linked to State/Licensure ID Number (D07 02) List box created from the State/ Licensure ID Number (D07 02) which could display the Personnel’s Names as associatedwith D08 01, D08 02, and D08 03 for easy data entryUses A component of the EMS Medical Record: Patient Care Report Associates an EMS event with specific EMS personnel Useful for reporting EMS personnel statistics related to EMS events and evaluation of EMS personnel performanceData Collector EMS personnelOther Associated ElementsE00Common Null ValuesE04 02 Crew Member RoleE01 01 Patient Care Report NumberE04 03 Crew Member LevelReferences in NHTSA Version 1Essential Element 26Essential Element 27Desirable Element 28Crew Member One NumberCrew Member Two NumberCrew Member Three NumberState Regulations Nebraska EMS Regulation 12Section E04Unit/ Personnel Information2005 NHTSA Uniform PreHospital Dataset V.2.20Page 154 of 463
CREW MEMBER ROLEE04 02Data Format [combo] single-choiceDefinitionThe role of the crew member during transport of this call. Driver is defined as the driver during the time of patient transport or during the response if there was not transport required. Primary Patient Care Giver is defined as the individual responsible for the patient care during the transport of the patient, orif notransport, the individual responsible for the assessment and treatment of the patient on scene. Secondary Patient Care Giver is defined as the individual assisting the Primary Patient Care Giver. Third Patient Care Giver is defined as the individual assisting in the Primary and Secondary Patient Care Givers.XSD Data Typexs:integerXSD Domain (Simple Type) CrewMemberRoleMultiple Entry Configuration Yes, via structureAccepts NullYesRequired in XSD NoXSD Structure: E04 01, E04 02, E04 03 are all members of the E04 Unit Personnel Information structureField Values-25-5585595Not ApplicableNot AvailablePrimary Patient CaregiverThird Patient Caregiver-10580590600Not KnownDriverSecondary Patient CaregiverOtherUses A component of the EMS Medical Record: Patient Care Report Associates an EMS event with specific EMS personnel Useful for reporting EMS personnel statistics related to EMS events and evaluation of EMS personnel performanceData Collector EMS personnelOther Associated ElementsE00Common Null ValuesE04 01 Crew Member IDSection E04E01 01 Patient Care Report NumberE04 03 Crew Member LevelUnit/ Personnel Information2005 NHTSA Uniform PreHospital Dataset V.2.20Page 155 of 463
CREW MEMBER LEVELE04 03Data Format [combo] single-choiceDefinitionThe functioning level of the crew member during this EMS patient encounter.XSD Data Typexs:integerXSD Domain (Simple Type) CrewMemberLevelMultiple Entry Configuration Yes, via structureAccepts NullYesRequired in XSD NoXSD Structure: E04 01, E04 02, E04 03 are all members of the E04 Unit Personnel Information structureField Values-25-5640609061106112Not ApplicableNot AvailableOther Healthcare 45610061116120Not KnownStudentOther Non-Healthcare ProfessionalEMT-IntermediateNurseFirst ResponderAdditional Information Could be auto-filled using Crew Member ID (E04 01) and connecting to State/ Licensure ID Number (D07 02) to obtainPersonnel’s Highest Level of Certification/ Licensure for Agency (D07 05) This list can be edited by each state to account for additional certification/ licensure levels as defined in (D04 01) andPersonnel’s Highest Level of Certification/ Licensure for the Agency (D07 05)Uses A component of the EMS Medical Record: Patient Care Report Associates an EMS event with specific EMS personnel Useful for reporting EMS personnel statistics related to EMS events and evaluation of EMS personnel performanceData Collector EMS personnelOther Associated ElementsE00Common Null ValuesE04 01 Crew Member IDE01 01 Patient Care Report NumberE04 02 Crew Member RoleReferences in NHTSA Version 1Essential Element 29Essential Element 30Desirable Element 31Crew Member One TypeCrew Member Two TypeCrew Member Three TypeReferences to Other Databases NFIRS 5.0 EMS Module, Title: Highest Level of Provider on Scene by Fire Department, Pick-List: First Responder 1,EMT-B (Basic) 2, EMT-I (Intermediate) 3, EMT-P (Paramedic) 4, Other Health Care Provider, IncludeDoctors, Nurses O, No Care Provided N NFIRS 5.0 EMS Module; Title: Initial Level of FD Provider; Pick-List: First Responder 1, EMT-B (Basic) 2, EMT-I(Intermediate) 3, EMT-P (Paramedic) 4, Other Health Care Provider, Includes Doctors, Nurses, etc. O,No Training NSection E04Unit/ Personnel Information2005 NHTSA Uniform PreHospital Dataset V.2.20Page 156 of 463
Section E05TimesSection E05Times2005 NHTSA Uniform PreHospital Dataset V.2.20Page 157 of 463
INCIDENT OR ONSET DATE/TIMEE05 01Data Format [date/time]DefinitionThe date/time the injury occurred, or the date/time the symptoms or problem startedXSD Data Typexs:dateTimeMultiple Entry Configuration NoRequired in XSD NoXSD Domain (Simple Type) DateTimeAccepts NullYes, but null value is blank or emptyMinimum Constraint 1990Maximum Constraint 2030Field Values Relevant Value for Data Element & Patient CareAdditional Information If the date/time is electronically stored within a database or transmitted via XML as a “tick”, the referenced variables mayalso be usedUses Important to identify when the clinical event started to better analyze EMS resource utilization and outcomes Provides descriptive information on the use of the EMS agencyData Collector 911 or Dispatch Center and electronically or verbally transmitted to the EMS agencyOther Associated ElementsE01 01 Patient Care Report NumberReferences in NHTSA Version 1Desirable Element 06Desirable Element 07Onset DateOnset TimeReferences to Other Databases NFIRS 5.0 Basic Module 1; Title: Incident Date; Date Field defined as YYYYMMDD or blankState Regulations Nebraska Trauma Regulation 3.A & BSection E05Times2005 NHTSA Uniform PreHospital Dataset V.2.20Page 158 of 463
UNIT NOTIFIED BY DISPATCH DATE/TIMENational ElementData Format [date/time]E05 04DefinitionThe date the responding unit was notified by dispatchXSD Data Typexs:dateTimeMultiple Entry Configuration NoRequired in XSD YesXSD Domain (Simple Type) DateTimeAccepts NullNoMinimum Constraint 1990Maximum Constraint 2030Field Values Relevant Value for Data Element & Patient CareAdditional Information If the date/time is electronically stored within a database or transmitted via XML as a “tick”, the referenced variables mayalso be used Not Nullable. A unique value must be provided to create a unique record ID within a databaseUses A component of the EMS Medical Record: Patient Care Report Allows data to be sorted based on EMS agency time intervals Allows data to describe EMS agency time intervalsData Collector 911 or Dispatch Center and electronically or verbally transmitted to the EMS agencyOther Associated ElementsE01 01 Patient Care Report NumberReferences in NHTSA Version 1Essential Element 11Essential Element 12Date Unit NotifiedTime Unit NotifiedState Regulations Nebraska EMS Regulation 3 Nebraska Trauma Regulation 4.CSection E05Times2005 NHTSA Uniform PreHospital Dataset V.2.20Page 161 of 463
UNIT EN ROUTE DATE/TIMENational ElementData Format [date/time]E05 05DefinitionThe date/time the unit responded; that is, the time the vehicle started movingXSD Data Typexs:dateTimeMultiple Entry Configuration NoRequired in XSD YesXSD Domain (Simple Type) DateTimeAccepts NullYes, but null value is blank or emptyMinimum Constraint 1990Maximum Constraint 2030Field Values Relevant Value for Data Element & Patient CareAdditional Information If the date/time is electronically stored within a database or transmitted via XML as a “tick”, the referenced variables mayalso be usedUses A component of the EMS Medical Record: Patient Care Report Allows data to be sorted based on EMS agency time intervals Allows data to describe EMS agency time intervalsData Collector 911 or Dispatch Center and electronically or verbally transmitted to the EMS agencyOther Associated ElementsE01 01 Patient Care Report NumberReferences in NHTSA Version 1Essential Element 13Time Unit RespondingState Regulations Nebraska EMS Regulation 4Section E05Times2005 NHTSA Uniform PreHospital Dataset V.2.20Page 162 of 463
UNIT ARRIVED ON SCENE DATE/TIMENational ElementData Format [date/time]E05 06DefinitionThe date/time the responding unit arrived on the scene; that is, the time the vehicle stopped movingXSD Data Typexs:dateTimeMultiple Entry Configuration NoRequired in XSD YesXSD Domain (Simple Type) DateTimeAccepts NullYes, but null value is blank or emptyMinimum Constraint 1990Maximum Constraint 2030Field Values Relevant Value for Data Element & Patient CareAdditional Information If the date/time is electronically stored within a database or transmitted via XML as a “tick”, the referenced variables mayalso be usedUses A component of the EMS Medical Record: Patient Care Report Allows data to be sorted based on EMS agency time intervals Allows data to describe EMS agency time intervalsData Collector 911 or Dispatch Center and electronically or verbally transmitted to the EMS agencyOther Associated ElementsE01 01 Patient Care Report NumberReferences in NHTSA Version 1Essential Element 14Time of Arrival at SceneState Regulations Nebraska EMS Regulation 5 Nebraska Trauma Regulation 4.DSection E05Times2005 NHTSA Uniform PreHospital Dataset V.2.20Page 163 of 463
UNIT LEFT SCENE DATE/TIMENational ElementData Format [date/time]E05 09DefinitionThe date/time the responding unit left the scene (started moving)XSD Data Typexs:dateTimeMultiple Entry Configuration NoRequired in XSD YesXSD Domain (Simple Type) DateTimeAccepts NullYes, but null value is blank or emptyMinimum Constraint 1990Maximum Constraint 2030Field Values Relevant Value for Data Element & Patient CareAdditional Information If the date/time is electronically stored within a database or transmitted via XML as a “tick”, the referenced variables mayalso be usedUses A component of the EMS Medical Record: Patient Care Report Allows data to be sorted based on EMS agency time intervals Allows data to describe EMS agency time intervalsData Collector 911 or Dispatch Center and electronically or verbally transmitted to the EMS agencyOther Associated ElementsE01 01 Patient Care Report NumberReferences in NHTSA Version 1Essential Element 16Time Unit Left SceneState Regulations Nebraska EMS Regulation 15 Nebraska Trauma Regulation 4.E.1Section E05Times2005 NHTSA Uniform PreHospital Dataset V.2.20Page 166 of 463
PATIENT ARRIVED AT DESTINATION DATE/TIMENational ElementData Format [date/time]E05 10DefinitionThe date/time the responding unit arrived with the patient at the destination or transfer pointXSD Data Typexs:dateTimeMultiple Entry Configuration NoRequired in XSD YesXSD Domain (Simple Type) DateTimeAccepts NullYes, but null value is blank or emptyMinimum Constraint 1990Maximum Constraint 2030Field Values Relevant Value for Data Element & Patient CareAdditional Information If the date/time is electronically stored within a database or transmitted via XML as a “tick”, the referenced variables mayalso be usedUses A component of the EMS Medical Record: Patient Care Report Allows data to be sorted based on EMS agency time intervals Allows data to describe EMS agency time intervalsData Collector 911 or Dispatch Center and electronically or verbally transmitted to the EMS agencyOther Associated ElementsE01 01 Patient Care Report NumberReferences in NHTSA Version 1Essential Element 17Time of Arrival at DestinationState Regulations Nebraska EMS Regulation 16 Nebraska Trauma Regulation 4.E.2Section E05Times2005 NHTSA Uniform PreHospital Dataset V.2.20Page 167 of 463
UNIT BACK IN SERVICE DATE/TIMENational ElementData Format [date/time]E05 11DefinitionThe date/time the unit back was back in service and available for response (finished with call, but not necessarily back inhomelocation)XSD Data Typexs:dateTimeMultiple Entry Configuration NoRequired in XSD YesXSD Domain (Simple Type) DateTimeAccepts NullNoMinimum Constraint 1990Maximum Constraint 2030Field Values Relevant Value for Data Element & Patient CareAdditional Information If the date/time is electronically stored within a database or transmitted via XML as a “tick”, the referenced variables mayalso be usedUses A component of the EMS Medical Record: Patient Care Report Allows data to be sorted based on EMS agency time intervals Allows data to describe EMS agency time intervalsData Collector 91
NEMSIS NHTSA Version 2.2 Data Dictionary (Nebraska Minimum Data Set) WWW.NEMSIS.ORG 2005.12 . Introduction . Number NEMSIS Data Element State EMS R/R State Trauma R/R Page Number E10.9 Airbag Deployment 3.G 274 E11.9 Date/Time Resuscitation Discontinued 22 285 E12.1 Barriers to Patient Care 21 289 .
