Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dev:dvimodule [2008/11/10 09:48]
dominic
— (current)
Line 1: Line 1:
-====== DVI Module ====== 
- 
-// Fatality Management and Disaster Victim Identification // 
- 
- 
-===== Purpose ===== 
- 
-This module is meant to support communication and data management in the handling of dead bodies and the identification of victims after a disaster, in order to ensure that those killed by a disaster get identified and buried individually and in dignity, and the bereaved get the chance to find out about the fates and whereabouts of their beloved ones. 
- 
-{{dev:dvimodule:fm.png|Screenshot}} 
- 
-The most commonly used term for these issues is Disaster Victim Identification (DVI), that's why this module is provisionally named DVI. Another term that came up in the course of the discussion is (Mass) Fatality Management. 
- 
-===== Current Status ===== 
- 
-  * Planning / Draft 
- 
-===== Module Roadmap ===== 
- 
-  * Initial version 
-    * Recovery Report 
-    * Unique Label Generation 
-    * Body Status Tracking (Movements, Procedures, Storage, Identification, Release) 
-    * Basic Identification Data 
-    * Photographs Storage 
-    * Simple Identification Report 
-    * Basic Statistics 
- 
-  * Improvements 
-    * Barcode Labels 
-    * Interactive Mapping of Body Find/Recovery 
- 
- 
-===== Desirable module capabilities ===== 
-{{dev:tracking.png|Body Tracking Flowchart}} 
- 
- 
-==== Body Recovery ==== 
- 
-Immediately after or even at the same time as the rescue operations, body search teams go on inspection of the scene, with the goal to locate, mark and register all dead bodies and body parts (including a medical confirmation that life is extinct, if available). 
- 
-They also evaluate if special measures or equipment for recovery are required, e.g. if the body is under water or slopped with heavy wreckage, or if it is located in hazardous environment (e.g. mines, ongoing hostilities, toxic gas or fluids, danger of collapse, fire, radiation, ...), or if it is potentially infective or the like. 
- 
-Data captured by the search teams can be stored in the database, and the system can produce unique labels to mark the bodies. 
- 
-These data can be searched and sorted by multiple criteria to assign recovery teams to the different locations (depending on their capabilities, capacities and equipment). 
- 
-Subsequently, recovery teams retrieve and wrap the bodies, body parts, and property or other items (that might perhaps later help to clear the identity of the deceased), and remove them from the scene, taking them to the determined collection points (e.g., morgue), where they will be checked in and appropriately stored for further handling, particularly for examination and identification. 
- 
-Bodies may also come from other sources (e.g. first aid points, hospitals, or brought in by volunteer helpers). They all have to be labeled, wrapped and checked in as well. 
- 
-  * Register body 
-  * Retrieve unique body reference label 
-  * Submit initial report (date/place of find, persons involved, sex, age group, state of the body) 
- 
-==== Body movement/handling ==== 
- 
-  * Movements journal 
-  * Procedures journal 
- 
-From there, any movement of a body (or other item) will be observed by its reason, date/time, destination and transport conditions, and recorded in the database until the final release for burial or issuance to relatives. 
- 
-In the same manner, each and every measure taken on a body (e.g. removal of clothing or other items, washing, medical examination, cosmetics, embalming, viewing) and its reason and results are recorded in the database. 
- 
-==== Post-mortem data (PM data) ==== 
- 
-{{dev:dvimodule:bodydata.png|Dead Body Data}} 
- 
-Overview on data about dead body as handled by the module. 
- 
-Special forensic profile data (Autopsy, Fingerprinting, DNA etc.) should not be handled by the Sahana database, but procedure status information and references to examination data may be included. 
- 
-==== Ante-mortem data (AM data) ==== 
- 
-Special AM data for identification purposes (and to find out the possible number of victims), as they can be enquired from relatives, witnesses, missing-person-lists and/or official registries, can also be stored in the database. 
- 
-//This may be an extension to the missing person registry// 
- 
-==== Case management ==== 
- 
-Cases are data structures to handle the individual identification process. Each case represents a single person. 
- 
-In the course of clearing, cases might be merged or reassigned to other cases, until, as possible, for each case the particular identity of the deceased is established. Each merging or reassignment is recorded, as well as opening, closing and reopening of cases. 
- 
-The case management functions provide matching search and sorting by multiple criteria (simple/advanced search). 
- 
- 
- 
-==== Reporting functions ==== 
- 
-  - Case reports 
-    * printout of case data to appropriate DVI forms (at best such as recommended by INTERPOL) 
-  - Statistics 
-    * basic statistics functions (victims count, identification rate, ..) 
-  - Body tracking 
-    * synopsis of all movements/procedures performed on a particular body 
- 
-==== Administration ==== 
- 
-Administration issues include the registration of all participating teams, institutions and other facilities, body storage and viewing sites, etc., as well as the configuration of workflow transitions for cases and bodies. 
  

QR Code
QR Code dev:dvimodule (generated for current page)