CARES Schematron Rules - NEMSIS 3.5.0

myCARES Schematron Rules - NEMSIS 3.5.0

We are currently developing a CARES-specific schematron. The schematron results are available via the File Upload Validation Report in the respective myCARES account.

Below is a list of current schematron ERROR/FATAL errors available for and in test on myCARES Beta. [FATAL] violations will trigger file rejection and are usually due to an incorrect format or value passed in an element. Because the file would fail at database level in these cases, we are now rejecting them before further parsing. Please check back often for updates.

You can access the current 3.5.0 myCARES Schematron here or refer to the below.

  • Date of Arrest is required - eArrest.14 must be present with a valid date value. If these are not present, the value of eTimes.03 will be used. Missing eArrest.14 will produce a [WARNING] while improper value will produce a [FATAL] error.
  • Custom elements AgencyID and FormID (this value is 90004 for 3.5.0) must be present with a value - will produce a [FATAL] error if missing or nil.
  • The following NEMSIS elements are required by CARES and must be present with a value (no NV/nil, except where noted). Except where noted, these are [ERROR] or [WARNING] level:
    • Incident Number (eResponse.03) [FATAL] value required- file will fail in parsing without this.
    • Incident Address (eScene.15)
    • Incident County (eScene.21)
    • Incident City (eScene.17)
    • Incident State (eScene.18)
    • Incident Zip (eScene.19)
    • Location Type (eScene.09)
    • eScene.03 and eScene.24 - First Responder is required or pass eScene.24 = No or eScene.24 N/A
    • Patient Last Name (ePatient.02)
    • Patient First Name (ePatient.03)
    • Either Patient Age (ePatient.15/16) or Date of Birth (ePatient.17)
    • Destination Hospital (eDisposition.02) if End of Event is Pronounced Dead in ED or Ongoing Resuscitation in ED
    • Patient Gender (ePatient.13)
    • Patient Ethnicity (ePatient.14)
    • Arrest Witness Status (eArrest.01 and eArrest.04)
    • Presumed Cardiac Arrest Etiology (eArrest.02)
    • Resuscitation Attempted By 911 Responder (or AED shock given prior to EMS) (eArrest.03, eArrest.07, eArrest.20, eArrest.22)
    • Was an AED applied prior to EMS Arrival (eArrest.07)
    • Was Hypothermia provided in the field (eArrest.10)
    • First Arrest Rhythm of Patient (eArrest.11)
    • Sustained ROSC (20 consecutive minutes), or present at end of EMS care (eArrest.12)
    • End of Event (either eArrest.16 = DNR and eArrest.18 not nil or vice versa)
    • Who Initiated CPR (eArrest.20) Value or NV = 7701001 is allowed
    • Who First Applied the AED (eArrest.21)
    • Who First Defibrillated the Patient (eArrest.22)
  • If used, the following optional custom elements must contain the proper value/format (can be omitted or nil). All of the below will constitute a [FATAL] violation, meaning the file will be rejected:
    • BystanderCPRProvidedID
    • CPRInstructionsProvided
    • 911RespCPR
    • ROSCStart
    • DefibTime
    • FRDispatched
    • FREnroute
    • FROnscene
    • MechCPRDeviceID
    • CPRFeedbackDevice
    • DrugAdministration
    • ITDID
    • VascularAccessID
    • STEMI
    • EROutcome
    • Hypothermia_Provided_Hosp
    • HospOutcome
    • HospOutcomeDNR
    • EROutcomeTrans
    • HospOutcomeTrans
    • HospOutcomeDNRTrans
    • HospDispositionTrans
    • NeuroOutcomeTrans
    • Hypothermia_Provided_Hosp_Trans
    • MyocardialInfarction
    • CoronaryAngiography
    • CoronaryAngiographyDateTime
    • CardiacStent
    • CABGPerformed
    • ICDPlaced
    • HypoNotInitiatedHosp
    • DischargeDeathDateTime
    • TimeSusRosc

Test data sent to the Beta server should not contain any PHI.


STRATEGIC PARTNERS

SPONSORS

Copyright © 2015 MyCares.net. All rights reserved. Unauthorized usage is prohibited. Usage will be monitored. Powered by Stryker.