Field Changes/Transition to NEMSIS 3.4.0

Field Changes

In order to be compliant going forward, the below changes must be implemented now:

  • eScene.17 must be populated with correct GNIS feature_id, not a string. We will be using GNIS going forward, not FIPS. UPDATE 10/2016: Sites that cannot generate GNIS codes may use a new custom element (IncidentCityStr) to pass the city string - 3.3.4 ONLY.
  • eScene.18 must be populated with the proper state ANSI code.
  • As of August 8, 2016, EMS times are now 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.
  • As of August 8, 2016, 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.

Below are changes that will eventually be enforced when myCARES officially moves to 3.4.0. However, all functionality is available now:

  • Incident Number has been expanded to maxLength = 32.
  • 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.
    • For version 3.3.4, if both eArrest.10 and eProcedure.03 = 430189000 exist in a given PatientCareReport, the value in eArrest.10 will be saved in the record.
  • Mechanical CPR Device Used will be accepted in custom element MechCPRDevice or if eProcedure.03 = 429283006 with a PN mapping to "No" in myCARES.
    • For version 3.3.4, if both MechCPRDevice and eProcedure.03 = 429283006 exist in a given PatientCareReport - the value in eProcedure.03 will be saved in the record.
  • ITD Used will be will be accepted in custom element ITD or if eProcedure.03 = 441893003 with a PN mapping to "No" in myCARES.
    • For version 3.3.4, if both ITD and eProcedure.03 = 441893003 exist in a given PatientCareReport - the value in eProcedure.03 will be saved in the record.
  • 12 Lead will be will be accepted in custom element 12Lead or if eProcedure.03 = 268400002 with a PN mapping to "No" in myCARES.
    • For version 3.3.4, if both 12 Lead and eProcedure.03 = 268400002 exist in a given PatientCareReport - the value in eProcedure.03 will be saved in the record.
  • Time of 1st CPR will be accepted in custom element CPRTime (3.3.4) or eArrest.19 (3.4.0).
  • First Arrest Rhythm will be accepted in the custom FirstRhythm (3.3.4) or element eArrest.11 (3.4.0).
    • For version 3.3.4, if both FirstRhythm and eArrest.11 exist in a given PatientCareReport - the value in eArrest.11 will be saved in the record.

Copyright © 2022 MyCares.net. All rights reserved. Unauthorized usage is prohibited. Usage will be monitored.