LAMP

Besafe - Healthcare during Emergencies

December 1, 2012 - 17:59 -- Sunil Kumar
Summary: 

 

 

People with chronic disease like Asthma or Diabetes need a stable routine. Interruption to medical supplies and health services may prove life threatening. The The besafe website aims to provide up to date information sourced from the crowd and from emergency response organisations to help both patients and health care workers in the event of an emergency.

 

The Solution is based on the Ushahidi Platform which is written in PHP on the Kohana MVC Web Framework. The solution is currently hosted on the cloud at besafe.crowdmap.com. Work is in progress on  advanced requirements like ability to track stock at emergency care providers , automated checklists, Heat maps, Swiftriver visuslisations from Twitter feeds, Historical data visualisation is being discusssed. 

 

 

 

Why we are working on this problem: 

There is no single reliable system that sources crowd information specifically for patients who need emergency help

What we accomplished during the event: 

 

1.Users can register as members in the system (Patients, healthcare providers like GP, Pharmacies etc.) 2.System Shall be able to receive the information about the disaster (location, Time, nature of disaster, severity etc.) 3.In the event of disaster system shall send Notification to users with information Including emergency contact and check lists 4.System maintains reliable current status information about he health care providers of the particular area ( pharmacies, hospitals, GP etc.) 5.System shall reset the status of the disaster after receiving about the disaster closure 6.System able to search for disaster by location, postcode 7.System able to display useful information like Hospitals and Pharmacies near a disaster Area

Ability to infer if a facility is down (Pharmacy, Hospitals etc)

 
Progress made since the event: 

 

•“Reports” can collect type information like Title, Description, date-Time, Category, Location (MAP Lat and Long), Location Name, News Source Link, Ext Video Link, Upload Photos, First/Last Name, Email,  of report and location of report •Addon Implemented to terminate a disaster event after a date •Reports can be set to Auto Approval in an emergency or moderated by an Admin •“Get Reports” Link  can be used to register emails to receive alerts when a report is submitted in your area . you can select specific categories of reports you want an alert on, or just get alerts for Disasters •Main Page displays a Map with dots indicating reports, Clicking on a dot opens details for the report. •Reports are clustered to act as a crowd sourced “Heat Map” •Categories and subcategories have been defined which help filter the reports that you want to see  - Disasters, Help Wanted, Help Available •Reports can be FILTERd by category and displays real time on the map •Layers of information has been added – VIC Hospitals, VIC Police Stations, Bushfire Hotspots,  ESTA Emergency Markers •Weather warning News feeds for Melbourne, VIC, NSW, Queensland •Checklist Embeded in App as a Page Plugin for Ushahidi to fetch JSON feed from SENSIS API and display it as a KML enabled Layer 
Next steps: 

 

•Fixed defect with iPhone Application Network framework iOS6, bug fix submitted for code merge •Build code to provide an API hook from Ushahidi to external Apps with KML layers in the •Release Ushahidi Plugin for SENSIS Api as an open source contribution from RHOK Melbourne •Enable and test Facebook and Twitter Integration as feed for reports •Enable and test Swiftriver plugin to filter “Buckets” from specific riverIDs •Implement a Heatmap from Government sources if available  
Community help: 

Need Emergency management experts to test the system and suggest improvements

Category: 
Status: 
Programming languages: 
Server requirements: 
Hosted on the cloud at Crowdmap
What RHoK event this project is being submitted for: 
Images and Video: 
Seeking people with skills in: 

Improving public transportation reliability to encourage people reduce their carbon footprint.

December 9, 2011 - 17:46 -- Keshy
Summary: 
  • Managed to achieve a good prototype of a semi-real time tracker
  • Pulled data off the MARTA schedules to be used as our primary dataset.
  • Platform agnostic and user friendly.
  • Involves SMS service and use of smartphone technlogies to cater to a wide section of international population facing this problem
What we accomplished during the event: 
  • A good notion of routes in different countries.
  • A decent working framework to be able to get an idea of approximate time your transport is due in to the stop near you. 
  • A user friendly way of updating information in a crowd sourced framework. 
  • Intelligent route prediction possible once the data sets evolve over time. 
  • SMS service to cater to developing nations. 
  • Potential integration with Google transit as a way to handle deviations from predicted schedules in developed countries. 
Category: 
Status: 
Frameworks: 
Images and Video: 

Auotmated Coordination of Community Sewage Disposal

October 22, 2011 - 04:09 -- estr4ng3d
Summary: 
Background Ezbet Khairallah is an informal settlement in southern Cairo with some 650,000 inhabitants. Like most other slums in Egypt, no infrastructure for water disposal is available. Instead, the dwellers depend on self installed tanks to store wastewater, which require emptying on a regular basis, by means of suction trucks that take the water to the nearest available sewage drain. Problem A part of Ezbet Khairallah does have a sewage network. The few sewers that are available in that area are the drain points of choice for the rest of the inhabitants, trying to get rid of their wastewater for the lowest possible cost. A conflict arises due to the extremely high demand for this resource. Inhabitants will fight for their turn to use the drains. Furthermore, the dwellers of the more fortunate area are extremely inconvenienced due to continued road blockage by sewage trucks, water overflows and foul smell. This leads to even more conflict. Proposed Solution The situation could be significantly enhanced by introducing a form of coordination, such that the drainage points are utilized according to an efficient and fair time schedule, giving equal opportunity to all parties, while observing water level in the network to avoid overflows. Calculating the optimum time and location of disposal will be done using automated software that take in several inputs, including that from water level sensors which will be installed in the network. The turns will be announced to the users in time via SMS text messages. Finally, the performance will be monitored and feedback will be used to further enhance the system and algorithm.
Next steps: 
Required Inputs & Outputs In order for the software to calculate the optimum times, locations, and turns for water disposal, the following site data will be collected and mapped: - number & locations of homes with tanks - frequency of water disposal - road network - locations of sewers This data will be collected using site surveys and interviews with inhabitants. The data will be recorded and analyzed using the software and data model perfected in the openstreetmap.org project. Finally, the system provides two user interfaces: 1.A web interface, showing a map of the area and the current scheduled disposal jobs. This is intended for the better prepared audience among the users themselves (a minority, according to available demographic information), and also for observers, the public, and interested NGOs. 2.An SMS messaging system. This will be the method of choice to notify the inhabitants of when and where they can take their turn to dispose of their wastewater. Text was chosen based on available demographics which indicate low penetration of smart phones.
Category: 
Status: 
Frameworks: 
End user environments: 
What RHoK event this project is being submitted for: 
Images and Video: 
Subscribe to RSS - LAMP
Subscribe to RSS - LAMP