2014 NASEMSO Mid-Year DMC Meeting

Transcription

1 2014 NASEMSO Mid-Year DMC Meeting

2 2014 Software Development Representative

3 What we will cover Review and pilot of the NEMSIS Agency Report Overview and review of the NEMSIS TAC V3 reporting tools Description of the Critical Update work Closing of National V2 data collection DMC intersection with NEMSIS TAC 2014 objectives V3 extended data dictionary State transition plans and getting products to the NEMSIS TAC Defining V3 performance measures Addition of suggested lists for ehistory.12 (Current Medications) and ehistory.08 (Medical/Surgical History) Review of 2014 NEMSIS TAC deliverables

4 Available Contractors V2/V3 mapping Schematron file and toolkit Revised wed services instance HL7 epcr CDA

5 DSTU Implementation Poudre Valley EM 20,000 runs/year Saves 5 minutes/record Annually saves 1,667 labor hours At $10/hour = $10,667 per year Cost Base Extract $5,000 + custom work Client/Server Solution $1,500 (multiple hospitals)

6 NEMSIS: EMS Agency Toolkit

7 Local EMS Toolkit Parse on Agency ID Run SAS Script State EMS Submission to NEMSIS host site Delete original xml and parsed data Sent to listed on state list

8

9

10

11

12

13

14

15

16 Ideas for Agency Report Information: Is this the right stuff?! Whom to compare agency data quality? Worried about agency confidentiality? Worried about personnel changes?

17 Overview: V3 Reporting Tools

18 SQL Reporting Services - Fixed

19 SQL Reporting Services - Variable

20 State Reporting Tools

21 NEMSIS Public Dataset

22

23 Ideas for V3 Reporting What are high-value reports? Providing reports or tools? State/Agency/Provider reports? How to get reports under nose? Women s shoes: Sexy vs. Practical? What P measures to use?

24 What Performance Measures?

25 Critical Release Update

26 Minor Revision Definitions No change to underlying XML structure Possible to do an in-place upgrade. May not need reassessment of compliance Not breaking backwards compatibility Major Changes the underlying XML structure Cannot perform an in-place upgrade Potential need for compliance reassessment Breaks backward compatibility Critical Patch Backwards-compatible bug fixes.

27 Critical Patch Off-Cycle Revisions Complete within weeks Major Revision Complete within six months Structural Modifications XML, XSDs - Documentation Validator - Accommodate three active verions ETL - Complete testing of all systems Schematron Warehouse Reporting Tools Compliance

28 2014: NEMSIS Versioning March Version January Version 3.3.4

29 Request for Critical Release Critical Release Spring 2014 (after v3.3.4 Release March 3, 2014) Primary areas of concern raised by EMS stakeholders: I. Pertinent Negative Attributes for various elements: The NASEMSO Data Managers Council (DMC) has recommended adding Pertinent Negative (PN) Attributes to the Primary Impression and Primary Symptom Elements. This recommendation is to make the documentation for the EMS Professional easier based on the limitations of the ICD-10-CM dataset. Elements impacted: A. esituation.11 - Provider's Primary Impression B. esituation.12 - Provider s Secondary Impressions C. esituation.09 - Primary Symptom D. evitals.18 - Blood Glucose Level E. eprocedures.03 - Procedure F. emedications.03 Medications given

30 Definitional Numerations Revision Numbering 3.x Major Number: Significant improvements or changes in functionality 3.3.x Minor Number: Minor feature changes or significant fixes Build# Build Number: informational changes to comments/dictionary

31 A Burning Issue! Closing National V2 data collection

32

33 2014 Objectives IT Features Complete FISMA Compliance Support NEMSIS V3 data processing Complete revision process Publish the 2013 NEMSIS Public Release Research Dataset Develop reporting tools for V3 Complete V2 agency toolkit Develop custom element library Finish NDX-type V3 report Develop NEMSIS benchmark API NEMSIS-compatible air-medical, critical care datasets, mobile integrated healthcare Service Features Support 10 states moving to V3/V2 Redesign of the NEMSIS website Complete NEMSIS Annual publication Revise NEMSIS CDA Software Implementation Calls Integration with National Information Exchange Model (NIEM) NEMSIS-compatible air-medical, critical care datasets, community paramedicine Develop best practices document Support CAD/Med Device workgroups Obtain certificate of confidentiality

34 Possible CDA Implementations 1. Patient Care Report (fwd) Hospital 1. Patient Care Report 3. Patient Outcome Report 5. NEMSIS Dataset State Vehicle 2. Trip Report Agency 4. EMS Incident Report

35 CDA: Next Steps Expand current CDA Include all e elements Build CDA for hospital outcomes Build CDA for EMS billing Is this the right order? Abandoning all-encompassing CDA!

36 Questions