NEMSIS - University Of Illinois Chicago

Transcription

NEMSISData DictionaryNHTSA v3.4.0Build 200910EMS Data StandardNational Elements OnlyVersion Date: September 10, 2020Funded byNational Highway Traffic Safety Administration (NHTSA)Office of Emergency Medical Serviceswww.NEMSIS.org

NEMSIS Data Dictionary Version 3.4.0NEMSIS Overview and SummaryThe NEMSIS data dictionary was developed through a collaborative effort with the EMS industry, includingweb-based reviews, public comment periods, focus groups, industry dialogue, topic-focused projects, andconsensus. The National EMS Information System Version 3 represents a major revision from Version 2 releasedin 2005. Adopting a broad perspective, the initiative to move to a 3rd version of the NEMSIS data dictionary wasfueled by the need to improve data quality, enhance our ability to assess EMS performance, augment theflexibility of the standard for state adoption and, to move the NEMSIS standard into the Health Level 7 (HL7)organization for approval as an American National Standards Institute (ANSI) standard.NEMSIS Version 3 Element Configuration from v2.2.1NEMSIS Version 3 Element ConfigurationTotal Elements including the Custom Elements: 585Excluding the Demographic and EMS (ePCR) Custom Elements: 561Published: 09/10/2020www.NEMSIS.orgPage i

NEMSIS Version 3.4.0 Data Dictionary Content**Note: The numbers to the right of the content listed below represent the location for each element on the Sample Page of the DataDictionary (page vi).Data Element Number (1)The NEMSIS Version 3 element numbering system has been revised to improve the informationderived from just the data element number. An example of a data element number is dAgency.01.The data element number begins with either a "d" representing the demographic (agency)section or an "e" representing the EMS PCR section.A one-word descriptor for each section is now included in the data element number.A period separates the section (e.g., dAgency) from the data element number (e.g., 01).National and State Element Indicator (2) (5) (6)National Yes, it is an indication that the data element is required to be collected at the local EMSagency level and submitted to the state.State Yes, it is an indication that the data element is recommended to be collected at the Statelevel.Data Element Name (3)The name of the data element.Data Element Definition (4)The definition of the data element.Version 2 Number (7)The NEMSIS Version 2.2.1 Data Element Number.If the Data Element is new to Version 3.4.0, the Version 2 Number will be blank.Data Structure InformationRecurrence (12)An indication that the data element can have more than one value.Represented by two characters separated by a colon. The configuration includes:0:1 element is not required and can occur only once.0:M element is not required and can repeat multiple times.1:1 element is required and can occur only once.1:M element is required and can repeat multiple times.Usage (8)Indication of when the data element is expected to be collected.Mandatory Must be completed and does not allow for NOT values.Required Must be completed and allows NOT values.Recommended Does not need to be completed and allows NOT values.Optional Does not need to be completed and does not allow for NOT values.NOT Value Characteristics (10)Indication that the data element can have NOT values.NOT Values are used (where permitted) to document that a data element was not applicable,not completed, or not collected by the state.NOT Values are documented as an attribute of an element. It allows the documentation ofNOT value when the real value is not documented.Please reference the NEMSIS White Paper describing the use of NOT Values, PertinentNegatives, and Nill:https://nemsis.org/media/nemsis v3/master/UsageGuides/NEMSIS V3 1 EMSDataSet Pertinent NegNOT Values Accepted (14)Indication of which of the following three NOT values is acceptable.Not all data elements accept NOT values.NOT Values have been condensed in Version 3.Not Applicable The data element is not applicable or pertinent.Published: 09/10/2020www.NEMSIS.orgPage ii

Not Recorded The data element is considered applicable, but was left blank. Thesoftware should auto-populate it with "Not Recorded".Not Reporting The data element is not collected by the EMS agency or state. ThisNOT value does not apply to National elements where Usage is specified as"Required".Pertinent Negative Values (PN) (9) (14)A list of Pertinent Negative Values which can be associated with a data element.Not all data elements accept Pertinent Negative Values.Pertinent Negative Values are documented as "an attribute" of an element. It allows thedocumentation of pertinent negative value in addition to the documentation of "real" value.Please reference the NEMSIS White Paper describing the use of NOT Values, PertinentNegatives, and Nill:https://nemsis.org/media/nemsis v3/master/UsageGuides/NEMSIS V3 1 EMSDataSet Pertinent NegExample of use:Example #1 - Aspirin Administration:If the medication Aspirin is part of the agency protocol for Chest Pain but was notadministered by the responding crew, the reason why should be documented.This is done through the use of Pertinent Negative Values. If the patient took theAspirin prior to the EMS arrival on the scene, the value "Medication AlreadyTaken" should be documented in addition to "Aspirin".Is Nillable (11)Indication that the element can accept a "blank" value.If the element is left "blank", the software must submit an appropriate value of one of the twoattributes: Pertinent Negative or NOT Values.Associated Performance Measure Initiatives (13)Indication that the data element has value in describing, defining, or measuring EMS from aperformance perspective. Performance Measures can be associated with EMS service delivery,patient care, or both. The following service delivery or time-dependent illness/injury performancemeasure topics have been included in NEMSIS Version 3:Airway - Airway ManagementCardiac Arrest - Out of Hospital Cardiac ArrestPediatric - Acute Pediatric CareResponse - EMS Response TimeSTEMI - ST Elevation Myocardial Infarction (STEMI)Stroke - Acute Stroke CareTrauma - Acute Injury/Trauma CareAttributes (14)An attribute provides extra information within an element.For information related to the first three attributes, please see the NEMSIS document 'How to UtilizeNEMSIS V3 "NOT values/pertinent s v3/master/UsageGuides/NEMSIS V3 1 EMSDataSet Pertinent NegativeThe following are possible attributes:PN (Pertinent Negative)8801001 - Contraindication Noted8801003 - Denied By Order8801005 - Exam Finding Not Present8801007 - Medication Allergy8801009 - Medication Already Taken8801013 - No Known Drug Allergy8801015 - None Reported8801017 - Not Performed by EMS8801019 - Refused8801021 - Unresponsive8801023 - Unable to CompletePublished: 09/10/2020www.NEMSIS.orgPage iii

8801025 - Not Immunized8801027 - Order Criteria Not Met8801029 - Approximate8801031 - Symptom Not PresentNV (Not Value)7701001 - Not Applicable7701003 - Not Recorded7701005 - Not ReportingNillable xsi:nil "true"Code Type9924001 ICD-109924003 RxNorm9924005 SNOMED-CTCorrelationIDData Type StringminLength 0maxLength 255DistanceUnit9921001 - Kilometers9921003 - MilesEmailAddressType9904001 - Personal9904003 - WorknemsisCodeData Type StringnemsisElementData Type StringnemsisValueDescriptionData Type StringPhoneNumberType9913001 - Fax9913003 - Home9913005 - Mobile9913007 - Pager9913009 - WorkProcedureGroupCorrelationIDDate Type CorrelationIDStreetAddress2Data Type StringminLength 1maxLength 255TimeStampData Type DateTimeminValue 1950-01-01T00:00:00-00:00maxValue 2050-01-01T00:00:00-00:00Published: 09/10/2020www.NEMSIS.orgPage iv

UUIDUUIDs must be generated using the IETF RFC 4122 standard.RFC 4122 defines four algorithms for UUID generation, any of these four can be used.UUIDs must be represented in canonical form, matching the following 9]{12}VelocityUnit9921001 - Kilometers per Hour9921003 - Miles per HourCode List (16)A list of values associated with the data element. Not all data elements have predefined value sets.Codes for each value:The codes are based on a 7-digit number, in a 2-2-3 pattern (without dashes).The first set of two numbers represent the data section.The second set of two numbers represent the element number.The last set is a 3-digit number for each value beginning at 001; The codes increase inincrements of two (2).Codes are typically sequential (by two) and alphabetical. Some ordering is provided in aneffort to present information based on workflow.Several values and codes reference external standards such as ICD-10, RxNorm, SNOMED,etc. NEMSIS will assist in providing a recommended list of EMS specific values and codesfrom these larger standards for most elements using these external standards.Data Element Editorial Comments (17)Comments are provided to describe additions, changes, clarifications, or additional insight into thedata element.Version 3 Changes Implemented (18)Comments are providing insight into specific Version 3 changes, such as new or revised dataelements.Element Deprecated(19)Elements that are signified as "deprecated" will be removed from a future version of the NEMSISstandard. Their use should now be avoided but will be supported until they are removed from thestandard.Associated Validation Rules (20)A list of national Schematron validation rules associated with the element. Additional validation rulesmay be implemented at the state or local level.Published: 09/10/2020www.NEMSIS.orgPage v

Published: 09/10/2020www.NEMSIS.orgPage vi

Published: 09/10/2020www.NEMSIS.orgPage vii

Table of ContentsDEMDataSet1DEMDataSet Grouping2EMSDataSet3EMSDataSet Grouping4dAgency5dAgency GroupingdAgency.01 - EMS Agency Unique State IDdAgency.02 - EMS Agency NumberdAgency.04 - EMS Agency StatedAgency.05 - EMS Agency Service Area StatesdAgency.06 - EMS Agency Service Area County(ies)dAgency.07 - EMS Agency Census TractsdAgency.08 - EMS Agency Service Area ZIP CodesdAgency.09 - Primary Type of ServicedAgency.11 - Level of ServicedAgency.12 - Organization StatusdAgency.13 - Organizational TypedAgency.14 - EMS Agency Organizational Tax StatusdAgency.15 - Statistical Calendar YeardAgency.16 - Total Primary Service Area SizedAgency.17 - Total Service Area PopulationdAgency.18 - 911 EMS Call Center Volume per YeardAgency.19 - EMS Dispatch Volume per YeardAgency.20 - EMS Patient Transport Volume per YeardAgency.21 - EMS Patient Contact Volume per YeardAgency.25 - National Provider IdentifierdAgency.26 - Fire Department ID figuration28dConfiguration GroupingdConfiguration.01 - State Associated with the Certification/Licensure LevelsdConfiguration.02 - State Certification/Licensure LevelsdConfiguration.03 - Procedures Permitted by the StatedConfiguration.04 - Medications Permitted by the StatedConfiguration.05 - Protocols Permitted by the StatedConfiguration.06 - EMS Certification Levels Permitted to Perform Each ProceduredConfiguration.07 - EMS Agency ProceduresdConfiguration.08 - EMS Certification Levels Permitted to Administer Each MedicationdConfiguration.09 - EMS Agency MedicationsdConfiguration.10 - EMS Agency ProtocolsdConfiguration.11 - EMS Agency Specialty Service CapabilitydConfiguration.13 - Emergency Medical Dispatch (EMD) Provided to EMS Agency Service AreadConfiguration.15 - Patient Monitoring Capability(ies)dConfiguration.16 - Crew Call Sign293031323334373839404144454647

eRecord48eRecord GroupingeRecord.01 - Patient Care Report NumbereRecord.02 - Software CreatoreRecord.03 - Software NameeRecord.04 - Software Version4950515253eResponse54eResponse GroupingeResponse.01 - EMS Agency NumbereResponse.03 - Incident NumbereResponse.04 - EMS Response NumbereResponse.05 - Type of Service RequestedeResponse.07 - Primary Role of the UniteResponse.08 - Type of Dispatch DelayeResponse.09 - Type of Response DelayeResponse.10 - Type of Scene DelayeResponse.11 - Type of Transport DelayeResponse.12 - Type of Turn-Around DelayeResponse.13 - EMS Vehicle (Unit) NumbereResponse.14 - EMS Unit Call SigneResponse.15 - Level of Care of This UniteResponse.23 - Response Mode to SceneeResponse.24 - Additional Response Mode ch72eDispatch GroupingeDispatch.01 - Complaint Reported by DispatcheDispatch.02 - EMD Performed737476eTimes77eTimes GroupingeTimes.01 - PSAP Call Date/TimeeTimes.03 - Unit Notified by Dispatch Date/TimeeTimes.05 - Unit En Route Date/TimeeTimes.06 - Unit Arrived on Scene Date/TimeeTimes.07 - Arrived at Patient Date/TimeeTimes.09 - Unit Left Scene Date/TimeeTimes.11 - Patient Arrived at Destination Date/TimeeTimes.12 - Destination Patient Transfer of Care Date/TimeeTimes.13 - Unit Back in Service Date/Time78798183858789919395ePatient97ePatient GroupingePatient.07 - Patient's Home CountyePatient.08 - Patient's Home StateePatient.09 - Patient's Home ZIP CodeePatient.13 - GenderePatient.14 - Race9899100101102103

ePatient.15 - AgeePatient.16 - Age Units104105ePayment106ePayment GroupingePayment.01 - Primary Method of PaymentePayment.50 - CMS Service Level107108109eScene110eScene GroupingeScene.01 - First EMS Unit on SceneeScene.06 - Number of Patients at SceneeScene.07 - Mass Casualty IncidenteScene.08 - Triage Classification for MCI PatienteScene.09 - Incident Location TypeeScene.18 - Incident StateeScene.19 - Incident ZIP CodeeScene.21 - Incident uation GroupingeSituation.01 - Date/Time of Symptom OnseteSituation.02 - Possible InjuryeSituation.07 - Chief Complaint Anatomic LocationeSituation.08 - Chief Complaint Organ SystemeSituation.09 - Primary SymptomeSituation.10 - Other Associated SymptomseSituation.11 - Provider's Primary ImpressioneSituation.12 - Provider's Secondary ImpressionseSituation.13 - Initial Patient ury GroupingeInjury.01 - Cause of InjuryeInjury.03 - Trauma Center CriteriaeInjury.04 - Vehicular, Pedestrian, or Other Injury Risk Factor133134135136eArrest137eArrest GroupingeArrest.01 - Cardiac ArresteArrest.02 - Cardiac Arrest EtiologyeArrest.03 - Resuscitation Attempted By EMSeArrest.04 - Arrest Witnessed ByeArrest.05 - CPR Care Provided Prior to EMS ArrivaleArrest.07 - AED Use Prior to EMS ArrivaleArrest.09 - Type of CPR ProvidedeArrest.11 - First Monitored Arrest Rhythm of the PatienteArrest.12 - Any Return of Spontaneous CirculationeArrest.14 - Date/Time of Cardiac ArresteArrest.16 - Reason CPR/Resuscitation Discontinued138139141142144145146147148149150152

eArrest.17 - Cardiac Rhythm on Arrival at DestinationeArrest.18 - End of EMS Cardiac Arrest Event153155eHistory156eHistory GroupingeHistory.01 - Barriers to Patient CareeHistory.17 - Alcohol/Drug Use Indicators157158159eVitals160eVitals GroupingeVitals.01 - Date/Time Vital Signs TakeneVitals.02 - Obtained Prior to this Unit's EMS CareeVitals.03 - Cardiac Rhythm / Electrocardiography (ECG)eVitals.04 - ECG TypeeVitals.05 - Method of ECG InterpretationeVitals.06 - SBP (Systolic Blood Pressure)eVitals.08 - Method of Blood Pressure MeasurementeVitals.10 - Heart RateeVitals.12 - Pulse OximetryeVitals.14 - Respiratory RateeVitals.16 - End Tidal Carbon Dioxide (ETCO2)eVitals.18 - Blood Glucose LeveleVitals.19 - Glasgow Coma Score-EyeeVitals.20 - Glasgow Coma Score-VerbaleVitals.21 - Glasgow Coma Score-MotoreVitals.22 - Glasgow Coma Score-QualifiereVitals.26 - Level of Responsiveness (AVPU)eVitals.27 - Pain Scale ScoreeVitals.29 - Stroke Scale ScoreeVitals.30 - Stroke Scale TypeeVitals.31 - Reperfusion 6177178179180181182183184eProtocols185eProtocols GroupingeProtocols.01 - Protocols UsedeProtocols.02 - Protocol Age Category186187190eMedications191eMedications GroupingeMedications.01 - Date/Time Medication AdministeredeMedications.02 - Medication Administered Prior to this Unit's EMS CareeMedications.03 - Medication GiveneMedications.05 - Medication DosageeMedications.06 - Medication Dosage UnitseMedications.07 - Response to MedicationeMedications.08 - Medication ComplicationeMedications.10 - Role/Type of Person Administering 2eProcedures Grouping203

eProcedures.01 - Date/Time Procedure PerformedeProcedures.02 - Procedure Performed Prior to this Unit's EMS CareeProcedures.03 - ProcedureeProcedures.05 - Number of Procedure AttemptseProcedures.06 - Procedure SuccessfuleProcedures.07 - Procedure ComplicationeProcedures.08 - Response to ProcedureeProcedures.10 - Role/Type of Person Performing the isposition GroupingeDisposition.05 - Destination StateeDisposition.06 - Destination CountyeDisposition.07 - Destination ZIP CodeeDisposition.12 - Incident/Patient DispositioneDisposition.16 - EMS Transport MethodeDisposition.17 - Transport Mode from SceneeDisposition.18 - Additional Transport Mode DescriptorseDisposition.19 - Final Patient AcuityeDisposition.20 - Reason for Choosing DestinationeDisposition.21 - Type of DestinationeDisposition.22 - Hospital In-Patient DestinationeDisposition.23 - Hospital CapabilityeDisposition.24 - Destination Team Pre-Arrival Alert or ActivationeDisposition.25 - Date/Time of Destination Prearrival Alert or 32233eOutcome235eOutcome GroupingeOutcome.01 - Emergency Department DispositioneOutcome.02 - Hospital Disposition236237239eOther240eOther GroupingeOther.05 - Suspected EMS Work Related Exposure, Injury, or Death241242

DEMDataSetPublished: 09/10/2020www.NEMSIS.orgPage 1

LegendDataset Level: N NationalUsage:Attributes:S StateM Mandatory , R Required , E Recommended, or O OptionalN Not Values, P Pertinent Negatives , L Nillable, C Correlation ID, and/or U nfigurationDEMDataSetPublished: 09/10/2020www.NEMSIS.orgPage 2

EMSDataSetPublished: 09/10/2020www.NEMSIS.orgPage 3

LegendDataset Level: N NationalUsage:Attributes:S StateM Mandatory , R Required , E Recommended, or O OptionalN Not Values, P Pertinent Negatives , L Nillable, C Correlation ID, and/or U gency.01 - EMS Agency Unique State IDNSM1:1dAgency.02 - EMS Agency NumberNSM1:1dAgency.04 - EMS Agency isposition1:1eOutcome1:1eOtherEMSDataSetPublished: 09/10/2020www.NEMSIS.orgPage 4

dAgencyPublished: 09/10/2020www.NEMSIS.orgPage 5

LegendDataset Level: N NationalUsage:Attributes:S StateD DeprecatedM Mandatory , R Required , E Recommended, or O OptionalN Not Values, P Pertinent Negatives , L Nillable, C Correlation ID, and/or U UUIDdAgency1:1dAgency.01 - EMS Agency Unique State IDNSM1:1dAgency.02 - EMS Agency NumberNSM1:1dAgency.04 - EMS Agency StateNSM1:MdAgency.AgencyServiceGroup1:1dAgency.05 - EMS Agency Service Area StatesNSM1:MdAgency.06 - EMS Agency Service Area County(ies)NSM1:MdAgency.07 - EMS Agency Census TractsNSRN, L1:MdAgency.08 - EMS Agency Service Area ZIP CodesNSRN, L1:1dAgency.09 - Primary Type of ServiceNSM1:1dAgency.11 - Level of ServiceNSM1:1dAgency.12 - Organization StatusNSM1:1dAgency.13 - Organizational TypeNSM1:1dAgency.14 - EMS Agency Organizational Tax StatusNSM1:MdAgency.AgencyYearGroup1:1dAgency.15 - Statistical Calendar YearNSM1:1dAgency.16 - Total Primary Service Area SizeNSRN, L1:1dAgency.17 - Total Service Area PopulationNSRN, L1:1dAgency.18 - 911 EMS Call Center Volume per YearNSRN, L1:1dAgency.19 - EMS Dispatch Volume per YearNSRN, L1:1dAgency.20 - EMS Patient Transport Volume per YearNSRN, L1:1dAgency.21 - EMS Patient Contact Volume per YearNSRN, L1:MdAgency.25 - National Provider IdentifierNSRN, L1:MdAgency.26 - Fire Department ID NumberNSRN, LdAgencyPublished: 09/10/2020www.NEMSIS.orgPage 6

dAgency.01NEMSIS Version 3.4.0.200910CP2StateNationaldAgency.01 - EMS Agency Unique State IDDefinitionThe unique ID assigned to the EMS Agency which is associated with all state licensure numbers andinformation.National ElementYesPertinent Negatives (PN)NoState ElementYesNOT ValuesNoIs NillableNoVersion 2 ElementUsageRecurrenceMandatory1:1Associated Performance Measure InitiativesAirwayCardiac sData TypestringminLength1maxLength50Data Element CommentThis may be the EMS Agency Name or a unique number assigned by the state EMS office. This is required to documentmultiple license types and numbers associated with the same EMS Agency.Published: 09/10/2020www.NEMSIS.orgPage 7

dAgency.02NEMSIS Version 3.4.0.200910CP2StateNationaldAgency.02 - EMS Agency NumberDefinitionThe state-assigned provider number of the responding agencyNational ElementYesPertinent Negatives (PN)NoState ElementYesNOT ValuesNoIs NillableNoVersion 2 ElementD01 01UsageRecurrenceMandatory1:1Associated Performance Measure InitiativesAirwayCardiac sData TypestringminLength1maxLength15Data Element CommentThis is the primary identifier for the entire Demographic Section. Each of the Demographic sections must be associated withan EMS Agency Number. An EMS Agency can have more than one Agency Number within a state. This reflects the ability ofan EMS Agency to have a different number for each service type or location (based on state implementation). The EMSAgency Number in dAgency.02 can be used to auto-populate eResponse.01 EMS Agency Number in the EMS Event section.Published: 09/10/2020www.NEMSIS.orgPage 8

dAgency.04NEMSIS Version 3.4.0.200910CP2StateNationaldAgency.04 - EMS Agency StateDefinitionThe state/territory which assigned the EMS agency number.National ElementYesPertinent Negatives (PN)NoState ElementYesNOT ValuesNoIs NillableNoVersion 2 ElementUsageD01 03RecurrenceMandatory1:1Associated Performance Measure InitiativesAirwayCardiac sPattern[0-9]{2}Data Element CommentThis has been clarified to reflect that it is the state in which the EMS Agency resides and the state associated with the EMSAgency number.GNIS Codes Website: http://geonames.usgs.gov/domestic/download data.htmPublished: 09/10/2020www.NEMSIS.orgPage 9

dAgency.05NEMSIS Version 3.4.0.200910CP2StateNationaldAgency.05 - EMS Agency Service Area StatesDefinitionThe states in which the EMS Agency provides services including the state associated with the EMS AgencyNumber.National ElementYesPertinent Negatives (PN)NoState ElementYesNOT ValuesNoIs NillableNoVersion 2 rn[0-9]{2}Data Element CommentEach state is captured as a group where the EMS agency provides service. The group includes dAgency.05, dAgency.06,dAgency.07, and Agency.08.Element added to document all of the states in which the EMS agency provides services. Each state listed is associated withthe counties, census tracts, and ZIP codes within the EMS Agency Service Area for each state.GNIS Codes Website: http://geonames.usgs.gov/domestic/download data.htmAssociated Validation RulesRule IDLevelMessageâ dAgency.05 ErrorEMS Agency Service Area County(ies) should belong to the state with which it is grouped.â dAgency.06 WarningEMS Agency Census Tracts should belong to a county recorded in EMS Agency Service AreaCounty(ies) in the state with which it is grouped.Published: 09/10/2020www.NEMSIS.orgPage 10

dAgency.06NEMSIS Version 3.4.0.200910CP2StateNationaldAgency.06 - EMS Agency Service Area County(ies)DefinitionThe county(ies) within each state for which the agency formally provides service.National ElementYesPertinent Negatives (PN)NoState ElementYesNOT ValuesNoIs NillableNoVersion 2 ElementD01 04UsageRecurrenceMandatory1:MAssociated Performance Measure InitiativesAirwayCardiac sPattern[0-9]{5}Data Element CommentEach state listed is associated with the counties, census tracts, and ZIP codes within the EMS Agency Service Area for eachstate. County codes are based on ISO/ANSI codes. It is a 5-digit code based on state (2-digit) and county (3-digit).GNIS Codes Website: http://geonames.usgs.gov/domestic/download data.htmAssociated Validation RulesRule IDLevelMessageâ dAgency.05 ErrorEMS Agency Service Area County(ies) should belong to the state with which it is grouped.â dAgency.06 WarningEMS Agency Census Tracts should belong to a county recorded in EMS Agency Service AreaCounty(ies) in the state with which it is grouped.Published: 09/10/2020www.NEMSIS.orgPage 11

dAgency.07NEMSIS Version 3.4.0.200910CP2StateNationaldAgency.07 - EMS Agency Census TractsDefinitionThe US census tracts in which the EMS agency formally provides service.National ElementYesPertinent Negatives (PN)NoState ElementYesNOT ValuesYesIs NillableYesRecurrence1:MVersion 2 ElementUsageRequiredAttributesNOT Values (NV)7701001 - Not Applicable7701003 - Not RecordedConstraintsPattern[0-9]{11}Data Element CommentThis data element was added to better document the service area of the EMS Agency. Each state listed is associated with thecounties, census tracts, and ZIP codes within the EMS Agency Service Area for each state.The format of the census tract number must be an 11-digit number, based upon the 2010 census, using the pattern:2-digit State Code 3-digit County Code 6-digit Census Tract Number (no decimal)Example: NEMSIS TAC office (UT, Salt Lake County, Census Tract - located at 295 Chipeta Way, Salt Lake City, UT)49035101400Census Tract Data Website (files and Associated Validation RulesRule IDLevelMessageâ dAgency.06 WarningEMS Agency Census Tracts should belong to a county recorded in EMS Agency Service AreaCounty(ies) in the state with which it is grouped.â NvPn Nil Nv ErrorWhen EMS Agency Census Tracts is empty, it should have a Not Value (Not Applicable, NotRecorded, or Not Reporting, if allowed for the element) or a Pertinent Negative (if allowed for theelement), or it should be omitted (if the element is optional).â NvPn Nv Nil ErrorWhen EMS Agency Census Tracts has a Not Value (Not Applicable, Not Recorded, or NotReporting), it should be empty.â vPn Nv only WarningWhen EMS Agency Census Tracts has a Not Value, no other value should be recorded.Published: 09/10/2020www.NEMSIS.orgPage 12

dAgency.08NEMSIS Version 3.4.0.200910CP2StateNationaldAgency.08 - EMS Agency Service Area ZIP CodesDefinitionThe ZIP codes for the EMS Agency's service area.National ElementYesPertinent Negatives (PN)NoState ElementYesNOT ValuesYesIs NillableYesRecurrence1:MVersion 2 ElementUsageRequiredAssociated Performance Measure InitiativesAirwayCardiac NOT Values (NV)7701001 - Not Applicable7701003 - Not RecordedConstraintsPattern[0-9]{5} [0-9]{5}-[0-9]{4} [0-9]{5}-[0-9]{5} [A-Z][0-9][A-Z] [0-9][A-Z][0-9]Data Element CommentThis data element was added to better document the service area of the EMS Agency. Each state listed is associated with thecounties, census tracts, and ZIP codes within the EMS Agency Service Area for each state.Zip Codes Product Website: 5Commercial/Standard/Overview/Product: USA - 5-digit ZIP Code Database, Commercial EditionAssociated Validation RulesRule IDLevelMessageâ NvPn Nil Nv ErrorWhen EMS Agency Service Area ZIP Codes is empty, it should have a Not Value (Not Applicable,Not Recorded, or Not Reporting, if allowed for the element) or a Pertinent Negative (if allowed forthe element), or it should be omitted (if the element is optional).â NvPn Nv Nil ErrorWhen EMS Agency Service Area ZIP Codes has a Not Value (Not Applicable, Not Recorded, orNot Reporting), it should be empty.â vPn Nv only WarningWhen EMS Agency Service Area ZIP Codes has a Not Value, no other value should be recorded.Published: 09/10/2020www.NEMSIS.orgPage 13

dAgency.09NEMSIS Version 3.4.0.200910CP2StateNationaldAgency.09 - Primary Type of ServiceDefinitionThe primary service type provided by the agency.National ElementYesPertinent Negatives (PN)NoState ElementYesNOT ValuesNoIs NillableNoVersion 2 ElementUsageD01 05RecurrenceMandatory1:1Associated Performance Measure InitiativesAirwayCardiac ArrestPediatricResponseSTEMIStrokeTraumaCode 992001599200179920019Description911 Response (Scene) with Transport Capability911 Response (Scene) without Transport CapabilityAir MedicalALS InterceptHazmatMedical Transport (Convalescent, Interfacility Transfer Hospital and Nursing Home)RescueCommunity ParamedicineCritical Care (Ground)Data Element CommentThe Primary Type of Service is associated with each EMS Agency Number.Published: 09/10/2020www.NEMSIS.orgPage 14

dAgency.11NEMSIS Version 3.4.0.200910CP2StateNationaldAgency.11 - Level of ServiceDefinitionThe level of service which the agency provides EMS care for every request for service (the minimumcertification level). This may be the license level granted by the state EMS office.National ElementYesPertinent Negatives (PN)NoState ElementYesNOT ValuesNoIs NillableNoVersion 2 ElementUsageD01 07RecurrenceMandatory1:1Associated Performance Measure InitiativesAirwayCardiac ArrestPediatricResponseSTEMIStrokeTraumaCode 9170299917031Description2009 Advanced Emergency Medical Technician (AEMT)2009 Emergency Medical Responder (EMR)2009 Emergency Medi

NEMSIS Version 3.4.0 Data Dictionary Content **Note: The numbers to the right of the content listed below represent the location for each element on the Sample Page of the Data Dictionary (page vi). Data Element Number (1) The NEMSIS Version 3 element numbering system has been revised to improve the information derived from just the data .