wiki:BluePrintHospitalDatabase

Version 3 (modified by Dominic König, 14 years ago) ( diff )

--

Table of Contents

  1. Introduction
  2. Description
    1. Components
  3. Requirements
    1. Functional Requirements
    2. Deployment Requirements
    3. Interoperability Requirements
  4. Use-Cases
  5. Design
  6. Implementation

BluePrint: Hospital Database

Introduction

The Sahana Eden Hospital Database is an Eden application to provide a global public database for hospital information including:

  • Facility identification
  • Location information
  • Capabilities and capacities
  • Contact information

in aggregation of both, authoritative sources as well as (sanitized) crowd-sourced data.

During emergency response operations, the database can additionally serve as a platform for the exchange of:

  • information on the status, resources and availability of health care facilities

Description

The Hospital Database can be used during emergency response to generate lists, maps and profiles of available health care resources, as well as to identify and locate facilities in supply chain and logistics management. The database can also be used by the hospital facilities themselves as a means to share their information with aid organizations, as well as with other facilities in order to form alliances.

The Hospital Database provides the hospital data to other applications through RESTful webservices, supporting a variety of data formats. Other applications, like AIMS, can consume these webservices to populate their databases, or to use them in other representations (like maps, reports etc).

Components

  • Organization Registry (Governments, NGOs, Health Facility Operators, Service Providers, Crowdsourcing communities)
  • Volunteer Management System
  • Hospital Management System
  • Sahana-Eden Core including:
    • Synchronization
    • Messaging
    • Mapping/GIS

Requirements

Functional Requirements

  • allow anonymous uploads
  • provide de-duplication tools
  • trusted groups (rating system)
  • Advanced search/query options (RESTful)

Deployment Requirements

  • Be able to operate on multiple servers (Mirror/Sync, Load-balancing)

Interoperability Requirements

  • Feeds and web services in various formats

Use-Cases

  • tbd

Design

  • tbd

Implementation

  • Proof-Of-Concept Prototype built at RELIEF-11.2 ("Camp Roberts East")

BluePrints

Note: See TracWiki for help on using the wiki.