Changes between Version 166 and Version 167 of BluePrint/SAFIRE

Timestamp:

11/29/17 14:12:32 (7 years ago)

Author:

Nuwan Waidyanatha

Comment:

--

BluePrint/SAFIRE

@@ -236 +236 @@
 1. Incident specific SOP check list
 ==== Missing features: ==== 
+'''Prototype'''
 1. manage [wiki:BluePrint/Event event type] specific work flows pre-populated message templates and messages (field-observation, casualty-illness, situation-information, response-resource, resource-messaging and management-summary reports)
 1. Locations selectors using geocodes or other categorical datasets, other than administrative boundaries. 
@@ -243 +244 @@
 1. [http://eden.sahanafoundation.org/wiki/BluePrint/Pictographs Pictographs for reporting incidents] (field and casualty-illness reports)
 1. ​Assigning a Code to the incident (some cases event) - for example, the EOC Commanded would announce that all incidents related to a large event (e.g. earthquake) should use the incident code, which automatically populates the incident and event titles, along with other relevant informaiton, so they don't have to search for it.
+1. CMS to document SOPs (e.g. with FAQs). Example, the caller might ask for the Incident Commander's contact details, the SOP / FAQ would have an answer for it.
+
+'''High Priority'''
+
+
+'''Low Priority'''
+1. Find a location to automatically draw the polygon, possibly using geocodes or other method. As in the [http://eden.sahanafoundation.org/wiki/BluePrint/SAFIRE/UseCases#SearchandRescue SAR example], the incident search area needs to be marked. 
+1. Performance evaluation, would require that the incident report status updates are time-stamped. Currently Eden maintains the time-stamp of the record was last updated. Perhaps we need to have a separate module that can be enabled / disabled to trigger a separate log to maintain the information.