1

EMS/Trauma Registry Quarterly Update (June, July, August)August 13, 2013

2

What we will cover today:

Timeline for NTDB & NEMSIS File Implementation

Trauma System Committee Registry Workgroup Recommended Reports

RAC D Project

Improvements Implemented

3

NTDB Implementation

DSHS & Consilience began work on the interface to accept the NTDB compliant file in June

Vendors were invited to work with DSHS and Consilience

Digital Innovations responded to the invitation and volunteered to assist with the technical specifications (XSD, XML) for NTDB including Texas custom fields

Customers will be able to use webservices to report data or will submit the XML file manually (either FTP or attaching the file in Maven, the details are being worked out this week)

4

NTDB Implementation (cont.)

We expect to pilot the NTDB file submission by Oct.

We expect to begin to accept the NTDB file in Jan. 2014

There will be a transition period of several months to allow entities to work with their vendors to submit the NTDB file and DSHS will continue to accept the Legacy file during the transition.

Web data entry users will begin to submit the NTDB data elements in Jan. 2014

5

NEMSIS Implementation

DSHS and Consilience are working on the reference lists for NEMSIS 3.3.2

Zoll responded to the invitation and volunteered to assist with the technical specifications (XSD, XML) for NTDB including Texas custom fields

Customers will be able to use webservices to report data or will submit the XML file manually (either FTP or attaching the file in Maven, the details are being worked out this week)

6

NEMSIS Implementation (cont.)

We expect to pilot the NEMSIS file in March 2014

We expect to begin to accept the NEMSIS file in June 2014

There will be a transition period of several months to allow entities to work with their vendors to submit the NEMSIS file and DSHS will continue to accept the Legacy file during the transition.

Web data entry users will begin to submit the NEMSIS data elements in June 2014

7

Trauma System Committee Registry Workgroup (TSCRW)Recommended Reports

Based on consolidated responses received by OEMS/TS and documented in a Excel table presented at the TSCRW July 10th meeting, DSHS has received feedback on Top 5 Reports from: RAC Chairs,

Cardiac Committee,

TTCF,

TETAF,

Pediatric Committee, and

Injury Committee (received from Injury Committee Aug. 1).

8

TSCRW Reports

Mechanism of Injury (e.g. motor vehicle, submersion, etc.)

Intent of Injury (e.g. suicide)

Volume of records (by month, day of the week, time of day, etc.)

Hospital Designation Application & Survey Report

By Injury Severity, condition at discharge, comorbid conditions, alcohol use, length of stay, geographic location, Hospital Trauma Designation Level, etc.

9

TSCRW Reports Patient Categories

Age (pediatric, geriatric)

Blunt trauma

Penetrating trauma

Traumatic Brain Injury

Falls

10

RAC D Project

July 17, 2013 RAC meeting in Abilene to review survey results and answer questions (Phase I)

One-on-one (one entity and DSHS) customer support session through Go To Meeting are being conducted

Phase II meeting will take place in Sept. in Abilene

In-person provider meetings are being arranged with a limited number of entities and will take place a few days before the Phase II meeting

Phase II meeting is to discuss solutions to non-reporting (how to get providers to report) and solutions to on-going support pertaining on how to us the EMS/Trauma Registry

11

Improvements ImplementedIncident City

EMS Import - Incident City is blank when County = 801 - 851 and City is invalid for that state

12

Improvements ImplementedDestination ID

EMS Roster Import Process- Destination ID (DESTINID) valid value '000911' not saved.

13

Improvements ImplementedHospital Import Errors and Summary

Hospital Roster Import data process - incorrect import errors and summary   

14

Improvements ImplementedSubmission Status Question Package

Submission Status QP_Multiple Iterations for Single File with only 2012 data.

15

Improvements ImplementedIncident City Web Data Entry

When you use the selector to enter your Incident City, the city you enter (Austin) the Run Information / Pre-hosp status is incomplete.   

16

Improvements ImplementedResident Null Values

EMS/Hos Interface - Resident County, State/Country Values - Populate State/County Null Values?

17

Questions & Comments