Significant WVOEMS NEMSIS Version 3 Files Release
While the information contained in this news article was current and accurate when we posted it, it may not necessarily represent current WVOEMS policy or procedure. If you have any questions, please contact our office at 304-558-3956.
Posted: Thursday, January 22, 2015 4:39 PM
West Virginia NEMSIS Version 3 Required Elements By Call Type With DQ and Business Rules (data dictionary), WV NEMSIS v3 Schematron Materials (State Specific Business Rules/Schematron File) and West Virginia NEMSIS v3 Vendor Requirement files have now been officially released.
WV NEMSIS V3 Schematron Materials - With the introduction of NEMSIS Version 3, West Virginia was required by the NEMSIS Technical Assistance center to create a file which would specify the unique West Virginia rules for data submission. This file, written in a specified computer language and to strict standards, will be turned into a programing module and activated within any run reporting software used by an West Virginia Licensed EMS Agencies. The West Virginia file has been validated by the NEMSIS Technical Assistance center and approve for use.
West Virginia NEMSIS v3 Required Elements By Call Type With DQ and Business Rules (data dictionary) -While West Virginia will allow EMS Agencies to report any data element in NEMSIS Version 3, West Virginia is not requiring the reporting of every data element. Also, only a few data fields within NEMSIS Version 3 are required by West Virginia to be reported on every dispatch of an ambulance by a licensed EMS agency. This spreadsheet lists every data field in the following NEMSIS version 3 sections: eRecord, eResponse, eDispatch, eCrew, eTimes, ePatient, ePayment, eScene, eSituation, eInjury, eArrest, eHistory, eNarrative, eVitals, eLabs, eExam, eProtocols, eMedications, eProcedures, eAirway, eDevice, eDisposition, eOutcome, eCustonResults, eOther and eCustomElemet. The spreadsheet indicates under which condition(s) this data element is required. Still further this spreadsheet indicates the effect of each required data element on the West Virginia "Data Quality Score" by ranking each data element as having a High, Medium or Low Data Quality priority. Finally this spreadsheet lists whether or not the file will be rejected if this data field is not supplied or if a "warning" will be supplied to the data entry person. This speed sheet is the specification of the Business Rules and Data Quality requirements implemented within the WV NEMSIS V3 Schematron Materials.
West Virginia NEMSIS v3 Vendor Requirements - West Virginia allows for the submission of run sheets using many different commercially available run sheet packages. To allow this to happen and to still maintain data quality, West Virginia has established that software packages be validated to prove that they capable of supplying the required data correctly and the validation of the installation of that software at the Agency. This document generally specifies the process for software validation that must be followed before an Agency will be allowed to submit required run sheet data.
The West Virginia NEMSIS v3 Required Elements By Call Type With DQ and Business Rules spreadsheet and the West Virginia NEMSIS v3 Vendor Requirements are now available in the WVOEMS Web System at http://www.wvoems.org/data/electronic-patient-care-record . The West Virginia NEMSIS v3 Required Elements By Call Type With DQ and Business Rules spreadsheet and the WV NEMSIS V3 Schematron Materials are available on the NEMSIS West Virginia V3 Progress Report page http://www.nemsis.org/supportv3/stateProgressReports/westVirginia.html .
West Virginia target dates for NEMSIS version 3 implementation remain as follows:
1) February 1 2015- West Virginia Specific Vendor Validation begins.
2) April 1 2015 - West Virginia opens its data system to NEMSIS version 3 data. EMS Agencies will be allowed to submit either NEMSIS version 2 or NEMSIS version 3 data.
3) November 1 2015 - All West Virginia Licensed EMS agencies are expected to submit NEMSIS version 3 compliant data.