Hospital AVailability Exchange (HAVE)
#1

[attachment=6745]
Hospital AVailability Exchange (HAVE)

1. Introduction *
Document Scope and Purpose *
This document specifies the requirements supporting the “EDXL Standard Format for Hospital AVailability Exchange (HAVE)” draft specification. This document is in the format requested by the OASIS Emergency Management Technical Committee (EM-TC) and is provided by the EDXL Project Team. The scope of this document includes requirements for the HAVE draft specification.
Background Information
In a disaster or emergency situation, there is a clear need for hospitals to be able to communicate with each other, and with other members and organizations of the emergency response community. The ability to exchange data with regard to hospitals’ bed availability, status, and capacity enables both the hospitals and the other emergency agencies to respond to emergencies or disaster situations with greater efficiency and speed. In particular, it allows emergency dispatchers and managers to make sound logistics decisions - where to route victims, which hospitals are open and able to offer what services. Many hospitals have expressed the need for, and indeed many are currently using, commercial or self-developed information technology that allows them to publish this information to other hospitals in a region, as well as EOCs, 9-1-1 centers, and EMS responders via various Web-based tools.

Systems that are available today do not record or present data in a standardized format, creating a serious barrier to data sharing between hospitals and emergency response groups. Without data standards, parties of various kids are unable to view data from hospitals in a state or region that use a different system – unless a specialized interface is developed. Alternatively, such officials must get special passwords and toggle between web pages to get a full picture. Other local emergency responders are unable to get the data imported into the emergency IT tools they use (e.g. a 9-1-1 computer-aided dispatch system, or an EOC consequence information management system). They too must get a pass word and go to the appropriate web page. This is very inefficient. A uniform data standard will allow different applications and systems to communicate seamlessly.

Reply

Important Note..!

If you are not satisfied with above reply ,..Please

ASK HERE

So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page
Popular Searches: meaning of the poem i have begrudged the years, availability, do i have any rights in, how do names have power, job interview do i have, have successful phone, how long do abstracts have,

[-]
Quick Reply
Message
Type your reply to this message here.

Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Possibly Related Threads...
Thread Author Replies Views Last Post
  Hospital Management System project uploader 3 5,350 13-04-2015, 10:20 AM
Last Post: seminar report asees
  Telephone exchange project uploader 0 937 12-03-2012, 10:56 AM
Last Post: project uploader
  EXCHANGE RATES & STOCK PRICE seminar paper 0 829 27-02-2012, 03:17 PM
Last Post: seminar paper
  Hospital Management System SIMPLE REPORT seminar paper 0 916 21-02-2012, 01:20 PM
Last Post: seminar paper
  TELEPHONE EXCHANGE seminar paper 0 948 09-02-2012, 03:28 PM
Last Post: seminar paper
  CULTURAL BIASES IN ECONOMIC EXCHANGE seminar paper 0 699 08-02-2012, 12:18 PM
Last Post: seminar paper
  Key Exchange Protocols seminar addict 0 655 24-01-2012, 03:06 PM
Last Post: seminar addict
  Foreign Exchange Management Act [FEMA] smart paper boy 0 2,201 23-08-2011, 10:11 AM
Last Post: smart paper boy

Forum Jump: