The incident information tool

Created on Thursday, 24 November 2016

This tool is developed by partner KT and it collects and aggregates all the information provided about the incident. The information consists of the initial dispatch information as provided by PSAP to the system, the SITREPs as entered by the field commander and all the related other information that participants have provided about the incident. To give it a common structure, the general layout of the information concepts follows the METHANE mnemonic for presenting SITREPs. The reason for this choice is that the METHANE mnemonic reports on common concepts that are valid across various health systems, as well as other emergency response agencies, including military, no matter if it is called METHANE or something else.


The incident information tool is quite a complex tool, since it is linked to multiple other tools. For example, some of the (menu) items, such as type of emergency are linked via the semantic module (partner VTT) to historical data, which are interpreted by the knowledge management module and may result in suggestions for specific actions. At the same time the semantic module offers also a self-learning functionality, for the system to learn from its own data gathered. This is particularly important since current incident data are not only presented in many heterogeneous ways, but also very unreliable, as most of them are collected based on subjective reporting and incident reconstruction via review of individual logs and interviews. There is also a link to a (still early stage) DSS prediction tool developed by partner NCSR, which aims to provide predictions of resource needs, again based both on historical data, as well as on self-learning. Obviously, the tool links to the COncORDE map and all its functionalities developed by partner ESRI. It links to the database, which operates all the settings for different access rights and for automated responses and automated rules. As a small example for automated rules, when the incident status message is changed to report end of the incident, then the system no longer offers the option for field role allocation to participants. It is impractical to list here all the examples for the interplay between the database and the incident information tool and it is deemed that a demo would be the most effective way for a stakeholder to grasp all the functionalities that are made available.


The incident information tool also collects all the information provided about the incident from participants that are logged into the incident space. These would include mainly text messages and photos at this point. All this uploaded information is considered under “notifications”, classified and propagated per urgency, recipients and need for action. The notifications tool is developed by partner ESRI, so linking is required. Semantic tags will help direct the information to be displayed in the right context. Linking to semantic tools (VTT) is foreseen.


Further to the incident information tool, it also provides the information on patients in the different stages of the incident. While initially it takes up estimated numbers, as later patients are retrieved and managed, the incident information form starts showing precise real-time data of all patients requiring management. This is enabled via a link to the patient status information tool and the map (partner ESRI). Further, the tool also collects and displays the information on dispatched responders and tagged assets. The information on dispatched responders feeds into the team management tool (Team table).