Note:  Juan Esparza, the EMSTARS Business Analyst, is the single point of contact for all startup related issues for both software vendors and EMS providers.  Please route all questions, concerns, problems, or suggestions through Juan.

The following ePCR solutions and vendors have been verified as EMSTARS Compliant:

1. Documed Systems Intl. Inc.
   Emergency-Pro, Version 4.0

2. Sansio (Formerly ScanHealth)
   HealthEMS™, Version 4.1

3. Zoll Data Systems
   RescueNet TabletPCR, Version 4.0.2.81

4. emsCharts
   emsCharts, emsCharts Pocket, emsCharts Mobile, Version 2.2

5. Ortivus
   Sweet Billing & Field Data with NEMSIS Export Module, Version 5.3

6. Healthware Solutions
   EMS Solution Suite, Version 5.7

7. Intermedix
   EMS 2006, Version 1.0

8. EMS Consultants
   Automated Run Tracking (ART) , Version 6.2

9. ACS-Firehouse
   Firehouse Software, Version 7.0

10. Code 3 Software
    EMS Express, Version 1.0

11. Golden Hour Data Systems
    GH Live, Version 1.8

The following ePCR solutions are currently in process for verification (deadline was April 30 and they have clients planned for July startup):

1. Zoll Data Systems
   FireRMS, Version 4.3

2. ImageTrend
   EMS State Bridge, Version 3.8

3. AeroMed Software
   WinAMS, Version 7.1

The following ePCR solutions are pending; their vendors have been in contact with the Data Unit, but have not begun submitting test records yet (deadline was April 30 and they have clients planned for July startup):

1. Air Methods Corp.
   Air Methods Proprietary Software

The following software vendors have been in contact with the Data Unit and plan to complete their compliance testing later this year:

1. Emergency Technologies, Inc.
   Visual EMS, Version 5.3 [estimate by September 2008]

2. OPEN Incorporated
   SafetyPAD, Version 2.7 [estimate by December 2008]

3. Medusa Medical Technologies, Inc.
   Siren ePCR, Version 2.xx and 3.xx

4. FirePrograms Software
   FirePrograms, Version 10

The following software vendors have clients who have committed to participate in the program, but the Data Unit has not had any recent communication with these vendors and cannot verify their readiness status; none have begun the compliance testing process:

1. New World Systems
   Aegis MSP Fire Records, Version 7.9.49

2. Sungard Public Sector
   Fires Management, Version 6.0

3. CISCO Software
   CISCO EMS

If you are considering the purchase of new or replacement software products, please begin by visiting NEMSIS Technical Assistance Center to view all of the compliant software solutions.

The Bureau also maintains a list of software vendors who either have clients in Florida or have expressed an interest in the EMSTARS Program.  However, please note that this is not intended to be a comprehensive list of all solution providers and the Bureau does not advocate nor endorse any software products.

What Does EMSTARS Compliance Mean?

The NEMSIS Technical Assistance Center (TAC) employees a rigorous testing program to verify compliance of EMS software products.  Through their review and validation of XML files and software documentation, the TAC verifies compliance to the National Highway Traffic Safety Administration’s (NHTSA)  2.2.1 Dataset.  These products are then considered NEMSIS Compliant.  If an EMS provider agency is in the market for new, or replacement, Electronic Patient Care Reporting (ePCR) software, they should choose from those that have been verified as NEMSIS Compliant.  The EMSTARS Compliance process is not meant to replace this testing; only to supplement it.

It is not within the statutory authority of the Bureau of EMS to formally evaluate or certify software products.  However, we have implemented a method to verify that exported files comply with EMSTARS criteria as defined in the Florida EMS Data Dictionary.  This verification of exported ePCR files, called an “extract”, is not a certification or endorsement of any particular software product.  The verification process does not assess the functional features of any product and does not guarantee it will meet the needs of any provider agency.

The process evaluates extracts (explained in Verification Steps), containing actual electronic ePCR files that were created by the EMTs and Paramedics from a licensed Florida provider agency, in the delivery of patient care.  Each record is tested based on the data elements, field values, validation rules, and other information contained within the Florida EMS Data Dictionary.  The process does not address any specifics regarding configuration, features, or options; only that the extract complied with EMSTARS criteria and passed the pertinent validation rules.

Software vendors need only submit extracts for compliance testing with one Florida client provider agency.  Once a software vendor has successfully verified their product is capable of producing an EMSTARS compliant extract, they may market their product(s) as such, with the understanding that each agency has different needs and may require slightly different configurations to meet those needs.

While it is necessary that a software product’s extract has been verified prior to beginning normal, routine EMSTARS reporting, compliance verification is not required before the software may be purchased by Florida provider agencies.  Testing is arranged between the Data Unit and the software vendors and the timeline is based on the project schedule.  If the software you own, or are considering, has not yet completed the process, it may be merely an issue of timing.  You may contact the Data Unit at any time regarding scheduling and deadlines for software vendors.

Since the compliance process relies on actual “live” records, it cannot test or verify every possible EMS response scenario and the associated validation rules.  The process is designed to identify as many issues as possible in advance, acknowledging that some validation issues may remain until an agency has transitioned to normal, routine reporting.  The software vendors are asked to work closely with the Data Unit and their clients during this transition period.

In summary, EMSTARS compliance means simply that a file extract from the software vendor has been verified against the documented compliance criteria.  There has been no testing or verification of a software product’s functionality or capabilities, other than the file extract that was produced.  As always, EMS provider agencies are free to purchase any solution that meets their needs, and the project team will work with all providers and software vendors to ensure verification of compliance in a timely manner.  Please forward any questions, concerns, or issues to Juan Esparza.

Verification Criteria

NEMSIS CERTIFICATION:  The software must be certified as NEMSIS compliant at either the Silver or Gold level

EMSTARS CONFIGURATION:  The software must be configured^**1 with data elements, field values, and validation rules specified in the Florida EMS Data Dictionary and utilize the EMSTARS XML Schema to produce a file extract that meets the EMSTARS validation criteria

TEST SITE:  The software vendor must install or upgrade one of their client EMS providers with their compliant software; this will serve as the vendors test site for extract verification

FILE EXTRACT VALIDATION:

1. Complete an sFTP Account Request Form

2. Send a test demographic XML file to test against the XSD

3. Send a test demographic XML file to test against Content Validation Rules

4. Send a test events XML file with no personally identifiable information with 5 to 10 records to test against the XSD

5. Send a test events XML file with no personally identifiable information with 5 to 10 records to test against the content validation rules

6. The final step is to send a 100 record file with “live” patient care reports representing various call types and dispositions

   1. These event records must have been collected by agency personnel using the actual software version for which you are seeking verification.

   2. Sending backup records or “test data” will not be sufficient.

   3. This process will need to be repeated until the file extract validates 100%

Note:  All software products are required to be verified as EMSTARS compliant by April 30^th, 2008.  We recommend you commence with steps 1 – 3 no later than April 1^st to allow sufficient time for the full validation process.

^**1 These configuration and mapping requirements are the responsibility of the vendor, not of the EMS provider agency.

Juan Esparza, the EMSTARS Business Analyst, is the single point of contact for all startup related issues for both software vendors and EMS providers.  Please route all questions, concerns, problems, or suggestions through Juan.