PLEASE DOWNLOAD LATEST DOCUMENTS AT https://beta.mycares.net/cares_xml_upload_docs.jsp -------------- December 2018 -------------- We will map eTimes.03 to Date of Arrest if the custom element servicedate and eArrest.14 are both nil. In this case, the CARES Schematron will produce a WARNING message. -------------- December 2017 -------------- We will now map Not Values 7701001 Not Applicable and 7701003 Not Recorded to the "Unknown" value in myCARES. There is no need to use the custom element "EthnicityUnknown" if you are mapping it using not values in your system. However, we will leave the element there for the time being to accommodate anyone using it. -------------- November 2017 -------------- ---- Was hypothermia care provided in the field ---- Some vendors who submit 3.4.0 files cannot pass a Pertinent Negative in this field (for eProcedure.03) and some states do not collect the data. There is now an agency setting which will default all records to "No" if there is no value passed in the XML or selected and saved in the form. "Yes" can still be passed in a file/saved in the Rev 4 form. ----------- July 2017 ----------- Added Narcan as an answer choice in CARES Rev 4 form. No action needed on part of vendors. Several RXNorm codes will automatically map to this answer choice from eMedications.03. ----------- February 2017 ----------- Presumed Cardiac Etiology, eArrest.02 has been updated in myCARES to reflect all values in NEMSIS, mapping to new values in the myCARES form. If already passing all values in eArrest.02, no action on the part of vendors is necessary. Added FATAL CARES Schematron rules: If NULL or null is passed as a value in the following elements, the file will be rejected: FirstResponder DOB_Unknown Starting in February, the value for WhoFirstAppliedAED Lay Person Medical Provider is changing from "5" to "6". There was an issue in the code and it got copied as the wrong value in the import documentation. The documentation will be updated for vendors that have not yet developed their XML. For existing vendors, we will map the value of "5" to "6" in the myCARES application. No action necessary for vendors already sending data. ----------- January 2017 ----------- Added Other text field in CARES form for Advanced Airway. Does not require any intervention from vendors. We will simply map the following to the Other field: 4003001 Maps to Other radio and Cricothyrotomy Tube to other text field in CARES 4003013 Maps to Other radio and SAD-Other to other text field in CARES 4003015 Maps to Other radio and Tracheostomy Tube to other text field in CARES 4003005 Maps to Other radio and Other-Invasive Airway to other text field in CARES To cut down on FATAL errors, we made the following changes to the schematron: - Allow date or dateTime format for custom element servicedate. - FirstRhythm missing and eArrest.11 nil was causing a fatal error. This condition will now only produce a warning. - Allow missing PoliceAED and PoliceDefib - produce warning. ------------ October 2016 ------------ Added a custom element (to 3.3.4 only) to accommodate vendors who cannot send the GNIS code. Use IncidentCityStr to pass the name of the city. ------- August 2016 ------ Changed all documentation, web pages, and parsing to remap EMS times to NEMSIS elements and create 3 new custom elements for First Responder times. EMS times mapped to eTimes (Previously First Responder times were mapped to eTimes): Time Ambulance dispatched custom element removed (AmbDispatched) and now mapped to eTimes.03 Time Ambulance en route custom element removed (AmbEnRoute) and now mapped to eTimes.05 Time Ambulance arrived at scene custom element removed (AmbArrivedAtScene) and now mapped to eTimes.06 Time Ambulance left scene custom element removed (AmbLeftScene) and now mapped to eTimes.09 Time Ambulance arrived at ED custom element(AmbArrivedAtED) removed and now mapped to eTimes.11 Mappings for eTimes.01 and eTimes.07 stay as is. New custom elements created and FR times remapped: Time First Responder dispatched remapped to new custom element FRDispatched Time First Responder en route remapped to new custom element FREnroute Time First Responder arrived at scene remapped to new custom element FROnscene June 2016 ------ Revamped the XML Data Dictionary Added SOAP web service and file validation to Beta site only Web pages containing information updated and items still in work Feedback welcome eScene.17 must be populated with correct GNIS feature_id, not a string. We will be using GNIS going forward, not FIPS. eScene.18 must be populated with the proper state ANSI code. Incident number has been expanded to maxLength = 32. First Arrest Rhythm will be accepted in eArrest.11 (3.4.0) or the custom FirstRhythm (3.3.4) element. Was Hypothermia Care Provided in the field will be accepted in eArrest.10 (3.3.4) or if eProcedure.03 = 430189000 with a PN mapping to "No" in myCARES. Mechanical CPR Device Used will be accepted in custom element MechCPRDevice or if eProcedure.03 = 429283006 with a PN mapping to "No" in myCARES. ITD Used will be will be accepted in custom element ITD or if eProcedure.03 = 441893003 with a PN mapping to "No" in myCARES. 12 Lead will be will be accepted in custom element 12Lead or if eProcedure.03 = 268400002 with a PN mapping to "No" in myCARES. Time of 1st CPR will be accepted in custom element CPRTime(3.3.4) or eArrest.19 (3.4.0). Custom element servicedate OR eArrest.14 will be accepted for the Date of Arrest. ---------- Changes 12/4/2014 - Updated Data Dictionary - improved descriptions for several elements ("Other" custom elements, Incident County, etc). Changes 08/22/2014 Added optional string element "CardiacEtiologyOther" to pass an etiology (string) other than what is listed in the NEMSIS element eArrest.02. See XML Data Dictionary for more details. Changes 7/3/2013 Clarification on eHistory.08- In order to fix an XML validation issue, use Pertinent Negative value 8801023 for "Unknown" value we have confirmed that the 3.3.2 XSD allows the value of I10 for Hypertension, so please use this value. Changes 6/27/2013 GNIS codes have been updated for IL,CA,MN,TX,GA,PA and WA in the db. Please see XML Data Dictionary for details on eScene.17 Changes 6/06/2013 Clarification on eAirway.02- Advanced Airway successfully placed in the field The logic for the answer choice "No" really means the airway attempt was "Unsuccessful" and that the airway placement was attempted. It does NOT mean that the question was not applicable, not documented, etc. Not Values for this field will not be mapped. eAirway.02 (Was advanced airway placed successfully in the field) is of datetime type. If you pass a date for this greater than the minInclusive value for this element, we will record this as a "Yes" answer. If you pass the minInclusive value of 1950-01-01T00:00:00-00:00 we will record a "No". You must pass a datetime value for eAirway.02 if you are passing any real value for eAirway.03, as it is a followup question (If yes, please specify). The data dictionary has been updated to reflect this. Example: Pass a "No" value: 1950-01-01T00:00:00-00:00 Pass a yes with Combitube value 2013-06-04T00:00:00-08:00 4003007 Changes 5/13/2013 Clarification on eHistory.08- Medical history Use R69 for "Unknown" and 8801015 for "No". Previously, R69 was mapped to both values. Changes 5/10/2013 ****ALL VENDORS*** We improperly had vendors map the incident number to eRecord.01. The Incident Number should be mapped to eResponse.03. This element is already in the XML. We apologize for any inconvenience. **FOR THE BELOW 5/10/13 CHANGES, THIS ONLY AFFECTS VENDORS PASSING HOSPITAL FIELDS (OTHER VENDORS NOT AFFECTED)** The hospital elements were redesigned to permit outcome data from a destination hospital OR a transfer hospital. New elements were added to accommodate transfer hospital data. These elements will be mapped appropriately to the existing hospital fields in the CARES application. The new elements are all custom: - EROutcomeTrans - Hypothermia_Provided_Hosp_Trans - HospOutcomeTrans - HospOutcomeDNRTrans - HospDispositionTrans - NeuroOutcomeTrans To pass data accurately, you must use specific combinations of the existing destination hospital elements plus the transfer elements (if applicable). Please refer to the Hospital section of the XML Data Dictionary for more details. Changes to Documentation (03/19/2013) - For eTimes.02, since this element is optional, is not nillable, and does not except NV- please pass min value for NOT value as follows: 1950-01-01T00:00:0000:00 Changes to XML (03/07/2013) - eDisposition.01 was changed to eDisposition.02. The value passed for this is the CARES defined import value set up for the destination hospital - Formid should be 90003, not 90001 - Medical History (eHistory.08) field was listed as xs:integer in the dictionary, changed to xs:string - Various descriptions in documentation in response to questions/to make things more clear. - Note: found documentation error in data dictionary- Date of Arrest maps to custom element servicedate and not eTimes.02 (which is CAD service date) - First Responder moved to custom element - we will not use eResponse.01 for this field. See FirstResponder custom configuration. - eArrest.08 moved to custom element WhoFirstAppliedAED and made into a required field Changes to XML (12/17/2012) - Incident City redefined from Custom element to NEMSIS eScene.17. - Removed nemsisCode incidences from custom configuration (codes remain the same). - Updated descriptions - "Unknown" answer removed from MyocardialInfarction - Updated Data Dictionary with descriptions - Updated CARES_NEMSISDetails spreadsheet