Project Managment

Introduction

In the countries with a lot of disasters there must be some kind of Disaster Management System. In most third world countries unfortunately that is just not the case. When it is, it is for after the disaster happens only, which is too late. It would be much better if the system works for both before and after disasters.

Project Description

The module that this group will be working on is called Disaster Medical Records. It is useful for managing patient data during rescue/first aid operation. It is vital especially for countries which have lots of natural disasters but lack any patient data collection system to be able to help them as quickly and efficiently as possible. It could be used for virtually any country; of course they could customize it to their own specifications. This module will include some very important features such as tag, photograph, triage status, relevant diagnoses, and statistics. It will be able to communicate this information with the hospitals, for more serious patients who need to be transferred to hospital. The data will be placed on secure servers with 24x7 back-up. The information will be permanent until the person dies.

Requirements

Entrypoint A - Triage Zone:

• Tag Label Assignment / Label Handling (Barcode, QR?, RFID?)
• Photograph
• Classification (Age Group, Sex)
• Triage Status

Entrypoint B - First Aid / Treatment Zone:

• Patient Tracking
• Personal Data / Contact Data
• Vital Values
• Relevant Diagnoses / Classification
• Emergency Interventions
• Emergency Lab Data (if applicable)

Reporting Point - Regular Hospital Admission:

• Patient Tracking
• Patient Registration
• Reporting
• Data Transfer to other Medical Record Systems
• Statistics

Tasks

user case

The device will have the capability to include data such as picture for proper identification, personal information & classification, contact information, registration type, health status before and after the disaster, and vital values. So let's say a disaster strikes one of the islands of Indonesia. People are waiting in line for registration. Of course the registration priority should be given to those with worse conditions first. So there could be two kiosks. One for severe cases, and one for others. Each equipped with devices that have this module loaded on it. The devices could be connected to the internet, but they also could store the information internally in case there wasn't any internet connection. So that it could be uploaded to the database later. Also the devices will be secure and encrypted so if stolen no information could be taken from them. It will self destruct by removing all the information if someone tried to break the encryption, possibly after uploading the data first. It should have GPS so that it could be found if lost or stolen. Also the volunteers who are at the disaster sites and taking the wounded and dead off the disaster site must be equipped with this device because obviously those can't form any lines. Anyway, after they are registered, meaning that all the information is taken into the device, they will be given triage values based on their health status. First of all can they be treated at the shelter or not. Is it just something like a headache? Or is it something serious like a heart attack. Since there are never as many doctors as needed at the disaster site, this device also includes some pre loaded treatments for known symptoms. So that volunteers could enter the symptoms and get the response from the device for the best way to treat a patient. This is important especially for non serious cases that a doctor visit is not really necessary. This way the doctor could see those that really need a doctor. Though even for serious cases, it is useful since it could facilitate the doctor's treatment. In third world countries, their resources is very limited. So you don't want to over crowd the hospital. It could be the only hospital near the disaster site with limited supplies and if everyone was to go there it could make the hospital unable to treat patient as quickly and efficiently as possible, and perhaps, they might not even be able to accept any more patients at all. So, it is vital to make sure as many people are treated at the shelter as possible. And only those truly in need will get to the hospital. The information collected from the shelter must be also accessible to the hospital so that there won't be any time wasted for duplicates. Also the device must be able to collect and process whatever information required for future statistics. Now, as you can see after a few years quite a few information will be collected in this database which could be very useful for future disasters. Of course some information should be always updated even when there is no disaster. Like the contact information. And whether the person is immigrated to a different country or diseased or not. In those cases their information perhaps should be removed after a period of time.

Design

This is a simple diagram of the final module.

Quality Control

To ensure quality control we made three set of survey question. One for each stage. Beginning, middle, and end. We used question pro and Kwiksurveys because their free version had limitations, so by utilizing both we were able to make a kind of surveys we wanted.

This is the first question asked from the stakeholders in the beginning.

This survey is like the one above except this time made by Kwiksurveys.

This survey was also asked in the beginning but from some of the people that this module is being created for.

This survey was asked in the middle of project.

And this is the last survey created right after the module was finished.

Tasks

While you can make the Gantt chart by even pen and paper, however it is much better to use some kind of project management software. There are quite a few out there, but we are already familiar with Linux and Libre suit. So we used ProjectLibre.

Time Table

Scroll up and view tasks tab for time information.

Time Table