Illinois EMS Data Collection Project

1
Illinois EMS Data Collection Project

• EMS Committee
• Information Management Subcommittee
• Assistant Chief Steve Rauter
• Lisle-Woodridge Fire District
• Subcommittee Chairman

2
A CAMEL is a HORSE designed by a COMMITTEE,
Anonymous
EMS
FIRE
Software Vendors
3
Sublime Ridiculous

• 4-part NCR form
• Bubble sheet
• EMS software input session
• NFIRS input session
• Local, regional or system custom reporting

4
History

• IDPH bubble-sheet project
• Grant
• Vendor EMS data systems, Inc.
• Scan-Tron technology
• Consistency, data reliability
• User issues
• Y2K issues

5
National Highway Traffic Safety Administration
(NHTSA)

• 1980s-vintage EMS data codes
• Updated 1993
• 80 (81) data elements identified

The Panel recognizes that the lists which are
included in this dictionary are imperfect, but
definitions of these lists have been debated for
many years without resolution. The lists
included here are intended as a starting point
for a uniform EMS data set which will evolve.
http//www.nhtsa.dot.gov/people/injury/ems/produ
cts.htm
6
Advent of NFIRS Version 5.0

• Upgrade from 1970s-vintage version 4.1
• Modular design
• Module 6 (EMS) is NOT a patient record
• Collection of data distributed
• Module 6 contains many NHTSA data elements (but
  not all)
• Desire to collect data on ALL fire agency
  activity (including EMS, EMS assist, etc.)
• http//www.Nfirs.Fema.Gov/vendorcert.Htm

7
Purpose of NFIRS EMS Module

• The purpose of the EMS Module is to gather basic
  data relating to provision of emergency medical
  care to the community
• Complete when Incident Type Medical Assist
  (311, 321, 322, or 323) is reported in Section C
  of the Basic Module

8
Use of NFIRS EMS Module 6

• The EMS Module is not intended to replace or
  otherwise interfere with state or local EMS
  patient care reporting requirements.
• The data elements in this module should be viewed
  as core elements around which a complete
  patient care report can be built.

9
EMS RMS
Fire RMS
Local EMS System
IDPH
10
Initial Meeting, June 13, 2000

• Met with IDPH, OSFM, IFCA
• Zero impact on OSFM
• OSFM data transfer used as model
• Support from IDPH to change methods
• NFIRS platform, Modules 1 6
• Reduction of redundancy, single-point-of-entry if
  possible
• Higher degree of accuracy with less input time
• Wide range of users and technical capabilities
• Paper-based EMS providers vs. Computerized
• EMS-hospital, system-driven, mandates on
  providers
• Innovative and power users (palm-based, laptop,
  etc.)

11
Principles of Design Level playing field for
vendors Allows for innovative data entry
methods Accommodates paper-only Facilitates
standardization Follows existing Rules
Advocates Single-Point-of-Entry for ALL
reporting requirements.
12
Illinois Data DictionaryIM Subcommittee

• Used NHTSA data elements as basis
• Updated some old terms
• Incorporated bubble sheet
• Deletions, additions
• Incorporated NFIRS V5 elements
• Found many overlaps, same codes
• Found numerous duplications
• Came up with some new data elements
• Looked at current standard of care issues

13
What Others Are Doing..

• Iowa, Idaho, Indiana, Wisconsin
• Commission for the Accreditation of Ambulance
  Services
• Http//www.Caas.Org/
• Commission of Fire Accreditation International
• Http//www.Cfainet.Org/
• JEMS magazine advocacy (editorial)
• Association of Public-Safety Communications
  Officials International (APCO project 36 CAD-RMS
  linkages)
• International Association of Fire Chiefs (IAFC)
• And

14
1999

• Http//www.Nasemsd.Org/report_draft_003.Doc
• Delineation of the absence of a central EMS
  database
• No central database, no linkages
• Lack of organized data, not valid, not reliable,
  barrier to outcome analysis
• No integration between EMS, other system
  entities, and community
• Research efforts are hindered, information
  systems inadequate for generation of useful
  hypotheses, need for multi-source database
  (cardiac research model)

(Paraphrased by A/C Steve Rauter, See link above
for full text.)
15

• EMS education (data-driven education?)
• EMS outcome (treatment effectiveness?)
• EMS research (multi-disciplinary, specialties,
  costs effectiveness?)
• EMS cost reimbursement issues (GRANTS!)
• While national in focus, should not be construed
  to mean a federal system

(Paraphrased by A/C Steve Rauter, See web link
for full text.)
16

• How to get there.
• A National EMS Data Systems should be linked
  with.
• National Electronic Injury Surveillance System
• National Pediatric Trauma Registry
• National Trauma Data Bank
• National Fire Incident Reporting System

(Paraphrased by A/C Steve Rauter, See web link
for full text.)
17
What weve done.

• IFCA, OSFM, IDPH support
• Vendors declined offer to assist (with 2
  exceptions)
• Illinois Data dictionary written edited
• Updated, revised bubble-sheet for paper-based
  data collection (software to be updated)
• A vendor has voluntarily constructed ASCII-based
  State Transaction File Format
• based on NFIRS V 5 transaction format
• Plan for integration of Single-Point-of-Entry
• Dummy Runs constructed, paper print-out run
  sheet
• Paste-up of new bubble sheet, new codes, etc.
• Sample State Transaction File, model for data
  storage

18
Whats next?

• Continue meeting, communications
• Data file rules finalized (9/28/01)
• Re-write of Illinois Data Dictionary
• NFIRS V5 stray data elements included?
• Target by IDPH for a November 2001 publishing
  date for STF specifications
• Vendor testing, certifications
• 3 free trials
• Roll-out plan published
• Legacy preserved, low/little impact

19
Thank You
IFAC EMS Committee Chairman Chief Mike
Hansen Lincolnwood Fire Department mhansen_at_icjia.o
rg IFAC Information Subcommittee
Chairman Assistant Chief Rauter Lisle-Woodridge
Fire District SRauter_at_LWFD.org 630-964-2233