Iepd analyze Requirements Use Cases for edxl situation reporting messages Draft Version 4

EMS Response Scenario Synopsis

The real-time status of EMS-involved calls and other events, EMS responders, hospitals and other resources upon which EMS and hospitals depend are maintained in databases linked in a network called the emergency medical service resource and events monitoring system (““COMMON SYSTEM OR SHARED DATABASE””). Similar database networks exist for fire, police (i.e.; National Law Enforcement Telecommunications System) and transportation responders, and many of the databases are shared among disciplines. The network is accessed via desk-top computers and mobile-base systems at dispatch centers, hospitals, 1^st responder vehicles and elsewhere.

The “COMMON SYSTEM OR SHARED DATABASE” screen displays a map representing the service area of the particular ambulance, hospital helicopter or other provider monitoring the screen. Labeled icons represent resources or events such as EMS calls. By selecting an icon, one accesses drop down menus and more detailed information about the event or resource.

Scenario Participants:

• 
  County dispatch center / Public Safety Answering Point (PSAP)
  
• 
  Faith Hospital (regional)
  
• 
  Central city Hospital (regional, level 1 trauma center)
  
• 
  Medevac Helicopter service
  
• 
  Fisherville Hospital (community hospital)
  
• 
  Bayport Police Department
  
• 
  Bayport EMS (BEMS) / Health Clinic
  
• 
  Bayport Fire Department
  
• 
  Bayport Coroner
  
• 
  Private Ambulance Services
  
• 
  Hospital Ambulance Services
  
• 
  Private Towing & Recovery Services
  

1. 
   Protocols and mutual aid agreements for communication are in place
   
2. 
   Interoperability communication capability is in place
   
3. 
   Asset Management capabilities are in place
   

NOTE 1: Specify where applicable mobile terminals / laptops used in first responder vehicles

NOTE 2: Consider communication within incident site, between incident and centers/support orgs between centers/support orgs, up the command chain and to the public. Also consider mobile terminals / laptops in 1^st responder vehicles

EMS Response Scenario Time-line

1. 
   (Initially pull from past SWG meetings, presentations, meeting minutes etc. Drive out additional through use case exercise)
   
2. 
   Requirements need to capture multiple orgs / professions coming into the scene, with initial situation information provided, and then expanded, and revised over the course of the incident. Capability is required for providing updated and expanded situation information during the course of a situation / event / incident.
   
3. 
   An Acknowledgment message from each recipient is required to be sent back to the sender of any message regardless of whom or what system originated the message (e.g. AACN, PSAP, dispatcher, 1^st responder unit) and regardless of the type of message sent (e.g. whether the message provided alerts, notifications, situation information or updates to any information), to verify that the content of the message has been received by the recipient system.
   
4. 
   
   

1. 
   “Telematics” / AACN vehicle data (e.g. “on-Star”) – For initial analysis, the scope of situation reporting for this scenario use case is focused on standardization of information-sharing initially initiated by the PSAP. The standard will focus on standardization of information originally sourced from a 911 centers / PSAP out to those who need it, as well as subsequent information sharing among actors as the situation progresses. This does not exclude situation information generated from other sources in other scenarios (such as field reports provided to FEMA and consolidated for decision-maker reporting).
   

1. 
   “Telematics” / AACN vehicle data (e.g. “on-Star”) - For initial analysis, the scope of situation reporting for this scenario use case will NOT be focused on standardization of information FROM the AACN system or citizens/callers TO the PSAP. It is assumed in this use case that the AACN system transmits information to the service provider monitoring / call center, which in turn make a phone call to a PSAP reporting the crash situation. Standardization focus for this use case begins with PSAP information-sharing.
   
   1. 
      It is recognized that a standard is required to allow PSAP’s to directly receive data feeds from such sensors / applications (including vehicle systems like “on-star”, long-haul freight, trains and other devices such as personal health monitors). However, another effort is under discussion to address this requirement. Depending upon the outcome of that discussion, a separate standard may be “plugged into” the Situation Reporting standard. Another option may be for the Situation Reporting standard to take on definition of those requirements / messages to standardize data feed from these device(s).
      
2. 
   Reference use case step 11: The message / signal sent to the light system commanding the light to turn to “green” are out of scope of this standard.
   
3. 
   
   

The following messages / message types were identified in the development of use examples. Each use example may contain one or many messages / message types.

2. 
   An Acknowledgment message from each recipient is required to be sent back to the sender of any message regardless of whom or what system originated the message (e.g. AACN, PSAP, dispatcher, 1^st responder unit) and regardless of the type of message sent (e.g. whether the message provided alerts, notifications, situation information or updates to any information), to verify that the content of the message has been received by the recipient system.
   
3. 
   .
   
4. 
   
   

The following messages identified by other groups for review with the Train Derailment scenario team:

1. 
   “Telematics” data - For initial analysis, data provided by vehicle systems is not in scope of this use case. It is assumed that the vehicle system transmits information to the service provider call center , who in turn make a phone call to a PSAP reporting the derailment situation.

   It is recognized that a standard is required to allow PSAP’s to directly receive data feeds from such sensors / applications (including vehicle systems like “on-star”, long-haul freight, trains and other devices such as personal health monitors). However, another effort is under discussion to address this requirement. Depending upon the outcome of that discussion, a separate standard may be “plugged into” the Situation Reporting standard. Another option may be for the Situation Reporting standard to take on definition of those requirements / messages to standardize data feed from these device(s). In either case, close coordination between these efforts is required.