NEMSIS Version2 NEMSIS Version 3 Purpose of NEMSIS Version 3 Improve Data Quality Schematron Enhance performance assessment Incorporation of performance measures Supports state flexibility Sharepoint, XSD header information Prepare for next step (HL7) Synchronization of clinical content NEMSIS Version 3 Data Dictionary The NEMSIS Version 3 Data Dictionary is a document describing in detail each of the 578 Version 3 Data Elements. The Data Dictionary is a consolidated source of information for each data elements. Brief History of NEMSIS 1973 1997: The Emergency Medical Services System Act was passed to collect standardized data nationwide 1998 2001: NHTSA produces a document, EMS Agenda for the Future and begins to work on a national EMS database 2003 - 2004
Fifty-two states and territories sign a Memorandum of Understanding to collect EMS data and assignment of specific data definitions . A two-year NHSTA is established to develop a coding system for EMS with a detailed National Data Dictionary. Brief History of NEMSIS (Cont) 2004 2005 Database schemas ae developed to create the database and an XML Standard is chosen to move EMS data between local and state level or state and national database level. A uniform EMS Pre-Hospital Dataset data set is developed and a Technical Assistance Center is funded by HRSA (EMSC) and the CDC. The contract is given to the University of Utah School of Medicine (Utah) in partnership with the University of North Carolina. Present Movement to NEMSIS version 3 to improve data quality. NEMSIS Standard Version 3 NEMSIS Version 3 is an EMS industry data standard system comprised of a data dictionary with: 574 data elements; data exchange standard using XML; business logic validation method using Schematron; and automated exchange method using web-services EMS Software that has fully implemented the NEMSIS Version 3
Standard may be tested through the NEMSIS Technical Assistance Center for compliance. Details on NEMSIS Version 3 can be found at www.nemsis.org NEMSIS 3: Performance Measurements Version 3 content has focused on objective performance measurement to better describe and evaluate EMS service delivery and patient care. State and National data elements are based on identified performance measures Changes in NEMSIS 3 N E M S IS N H T S A U n ifo r m P r e H o s p ita l D a ta s e t D e m o g r a p h ic D a ta E le m e n ts E x is tin g ( V e r s io n 2 ) Version 2 . 2 . 1 V e rs io n 3 .0 110 1 3 3 (2 5 % ) 8 6 (7 8 % )
8 6 (6 5 % ) N ew R e tir e d E M S D a ta E le m e n ts E x is tin g ( V e r s io n 2 ) 4 7 (3 5 % ) 2 3 (2 2 % ) 318 4 0 5 (7 5 % ) 2 5 7 (8 1 % ) 2 5 7 (6 3 % ) N ew R e tir e d O v e r a ll T o ta l E x is tin g ( V e r s io n 2 ) 1 4 8 (3 7 % ) 5 7 (1 9 % ) 428 538
3 4 8 (8 1 % ) 3 4 3 (6 4 % ) N ew R e tir e d 1 9 5 (3 6 % ) 8 0 (1 9 % ) Highlights of NEMSIS 3 Changes Customized Data Elements have been enhanced EMS and Response and Transport modes have been enhanced Hospital Outcome Data have been expanded EMS Agency Location and GIS information has been enhanced Compliant, Diagnosis, Injury Cause, and Procedures are now based on ICD-10. Automated Collision Notification Information has been included Challenges Data Quality Goals for NEMSIS NEMSIS Timeline Some NEMSIS Use
Considerations.. Mandatory Fields Local Options for Additional Items Custom Data Elements Null Values Null Value Attributes - Indication that the data element can have null values. Null Values are used (where permitted) to document that a data element was not or could not be completed. Null Values Accepted - Not all data elements can accept null values. Null values for NEMSIS 3 are noted below Not Applicable Not Recorded Not Reported Negative Values Negative Action Values
Negative action values can be associated with a data element, however, not all data elements accept negative action values Use of Null and Negative Values reduces the data quality and should be used accordingly. More information on NEMSIS 3 NOT Values can be found: http://nemsis.org/media/nemsis_v3/master/UsageGuides/NEMSIS_v3_NOT_Values_Us e_Guidance.pdf Not Values NOT Values have been condensed in Version 3 and are summarized below: Not Applicable: The data element is not applicable or pertinent to the EMS event. Not Recorded: The data element is considered applicable to the EMS event, but was left blank. The EMS software should auto-populate it with "Not Recorded". Not Reporting: The data element may not be collected by the EMS agency or state. This NOT value does not apply to National elements where "Usage = Required". Usage Value Descriptions Background The NEMSIS Version 3 standard is comprised of four types of elements identified as Usage Type. Mandatory and required fields collect critical data; null or negative values should be avoided because they diminish the data value and misrepresent actual EMS business operations
Usage Value Definition Descriptions There are 4 types of elements in NEMSIS Version 3 that determine the Usage of each element: Mandatory: These elements are always required and must be filled out in every record and Not Values are not allowed. Required: These elements are always required and they do allow Not Values to be used. Recommended: These elements are optional elements and allow the use of Not Values Optional: These elements are optional and do not allow for Not Values Compliance Vs. Compatibility Ensures Standardization Increases Data Quality Not Controlled by State or LEMSAs Software Company
Product Name Product Version Current Standard Tested Date Compliant Center for Advanced Public Safety RESCUE Submission Aggregator 1.0.0 1.0.1 v3.3.4 v3.4.0 1/20/2015 8/20/2015 CogniTech POLARIS
3.0 RPD v3.3.4 6/12/2014 Consilience Maven 5.x v3.3.4 7/8/2015 Digital I nnovation, I nc DI NEMSIS Aggregator 2014_07 v3.3.4 10/1/2014 ESO Solutions
Health Data Exchange 1.x v3.3.4 10/20/2014 I mageTrend, I nc. ImageTrend Elite 1 1.x v3.3.3 v3.3.4 12/17/2013 11/1/2014 I ntermedix TripTix CDX 4.0
4.0.19 v3.3.3 v3.3.4 1/30/2014 12/15/2014 ZOLL ZOLL Online 1.0 v3.3.4 4/1/2015 Software Company Product Name Product Version Current Standard Tested
Date Compliant 4.0.0.n 4.0.1.n v3.3.3 v3.3.4 2/ 4/ 2014 6/ 12/ 2014 A/ R Concepts, I nc. ARC ePCR Application Data Systems I nc DataforceWeb Fire & EMS 3.1 v3.3.4 8/ 21/ 2015 American Medical Reponse
MEDS 4.0 v3.3.4 3/ 10/ 2015 Beyond Lucid Technologies, I nc. MediView 2014 2014 v3.3.3 v3.3.4 12/17/ 2013 8/ 13/ 2014 emsCharts, I nc emsCharts.com 4
v3.3.4 8/ 21/ 2015 Golden Hour Data Systems Golden Hour Live 2015 v3.4.0 5/7/ 2015 Forte Holdings I nc iPCR v3.6 v3.4.0 8/7/ 2015 I mageTrend, I nc. I mageTrend Elite
1 1 v3.3.3 v3.3.4 5/ 29/ 2014 6/ 10/ 2014 I ntermedix TripTix 4.0 4.0 v3.3.4 6/ 29/ 2015 Source Code 3 LLC Digital Paper 1.0.4 v3.3.4
6/ 10/ 2014 Starwest Tech Zoi 1.0 1.0 v3.3.4 v3.4.0 7/ 24/ 2015 8/ 21/ 2015 WebMedicPro WMP5 1.x v3.3.4 8/ 26/ 2015 ZOLL
ePCR 6.0 v3.3.4 10/10/ 2014 Seeking Compliance Software Company Capabilities Application Received For^ Receive Date A&G Group I nformation Technologies Inc. Collect Data v3.4.0
8/10/ 2015 American Medical Response Collect Data v3.4.0 6/25/ 2015 FI REHOUSE Software Collect Data v3.3.4 8/31/ 2015 Receive & Process Data v3.3.4 6/15/ 2015 MedaPoint, Inc
Collect Data v3.4.0 9/ 1/ 2015 TriTech Software Systems Collect Data v3.3.4 8/25/ 2015 TriTech Software Systems Collect Data v3.4.0 8/25/ 2015 World Advancement of Technology for EMS and Rescue Collect Data
v3.3.4 8/29/ 2014 Lancet Technology, Inc. Pretesting* Start Date Active Testing* * Start Date 6/ 25/ 2015 6/25/ 2015 4/ 29/ 2015 5/5/2015 Passed Compliance
Completion Date NEMSIS 3: Becoming Compliant Compliance Policy Please contact Jorge Rojas at 801.213.3822 or [email protected] or visit: http://nemsis.org/v3/becomingCompliant/compliancePolicy.html NEMSIS 3: Compliance Process NEMSIS version 3 Compliance Process requires that a data system be able to collect, receive, and process data. The documents below are available to assist in your compliance process at the following URL: http://nemsis.org/v3/becomingCompliant/complianceProcess.html Compliance Process & Check List NEMSIS V3 Compliance Application Form Pre-Testing Package v3.4.0 NEMSIS v3 Compliance Document NEMSIS v3.4.0 Pre-Testing Package Pre-Testing Package v3.3.4 NEMSIS v3 Compliance Document (Updated May 5, 2015) NEMSIS v3.3.4 Pre-Testing Package (Updated May 5, 2015) Compliance Testing Schedule There is no official schedule for compliance testing of EMS software products. A software company can submit an application to Jorge Rojas to schedule compliance testing for EMS products. Please reference the NEMSIS V3 Compliance Document on
the v3 Compliance Process page for further details regarding the compliance process. Testing Prerequisites All software seeking NEMSIS V3 compliance must first submit a Demographic and EMS dataset to the NEMSIS v3 web service and pass both the XSD and Schematron validation. For NEMSIS Version 3, the NEMSIS Technical Assistance Center (NEMSIS TAC) is offering compliance testing free-of-charge to software developers. Please contact Jorge Rojas at 801.213.3822 or [email protected] for a compliance application http://nemsis.org/v3/becomingCompliant/complianceTestingSchedule.html Downloadable Resources (1 of 2) The following tools, XSDs, dataset dictionaries, and other helpful resources to help you when developing NEMSIS compliant software: Dataset Dictionaries http://nemsis.org/v3/downloads/datasetDictionaries.html Demographic (Agency) Dataset Schema http://nemsis.org/v3/downloads/demographicDataset.html EMS (PCR/Event) Dataset Schema http://nemsis.org/v3/downloads/emsDataset.html Medical Device Dataset Schema http://nemsis.org/v3/downloads/medicalDevice.html
Downloadable Resources (2 of 2) CAD Dataset Schema http://nemsis.org/v3/downloads/CAD.html Schematron http://nemsis.org/v3/downloads/schematron.html HL7 Products http://nemsis.org/v3/downloads/hl7Products.html Web Services http://nemsis.org/v3/downloads/webServices.html XML File Samples http://nemsis.org/v3/downloads/testCasesXMLSamples.html NEMSIS Archive http://nemsis.org/v3/downloads/v3Archive.html
