Elysa Jones, Warning Systems, Inc.
Sukumar Dwarkanath, Associate Member <Sukumar_Dwarkanath@sra.com>
This specification is related to:
Declared XML Namespace(s):
This document lists errata for the Emergency Data Exchange Language (EDXL) Hospital AVailability. The level of approval is listed above. Check the “Latest Version” or “Latest Approved Version”location noted above for possible later revisions of this document.
This document was last revised or approved by the Emergency Management Technical Committee on the above date. The level of approval is also listed above. Check the current location noted above for possible later revisions of this document.
Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Emergency Management TC web page at http://www.oasis-open.org/committees/emergency/.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page at
The non-normative errata page for this specification is located at http://www.oasis-open.org/committees/emergency/.
Copyright © OASIS® 1993–2009.
All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other Party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.
OASIS invites any Party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.
The names "OASIS", “Emergency Data Exchange Language,” “Emergency Data Exchange Language Distribution Element,” “Emergency Data Exchange Language Hospital Availability Exchange,” “Emergency Data Exchange Language Resource Messaging,” “EDXL,” “EDXL-DE,” “EDXL-HAVE” and “EDXL-RM” are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please seefor above guidance.
§ All Cardinalities (0..1, 0..*, etc) have been made clearly visible and placed close to the element to which the cardinality applies.
§ "CommentText*" with the asterisk denoting "may use multiple" has been added where needed and removed from HospitalBedCapacityStatus.
§ Removed Cardiology from ServiceCoverageStatus.
§ Deleted DeconCapacity and MorgueCapacity from HospitalFacilityStatus.
o DeconCapacity with sub-elements DeconCapacityStatus, AmbulatoryPatientsDeconCapacity, and NonAmbulatoryPatientsDeconCapacity;
o MorgueCapacity with sub-elements MorgueCapacityStatus, and MorgueCapacityUnits.
o Added ResourceInformationText as a sub-element to HospitalFacility Status.
o Under OrganizationInformation changed the CIQ supporting element OrganizationInfo to correct spelling: OrganisationInfo.
o Added missing element TraumaCenterServicesIndicator.
§ <have:OrganizationGeoLocation>: In Type row, replaced ‘geo-oasis: whereType’ with‘geo-oasis: where’
§ <have:EMSCapacity>: In Comments row, changed reference to Sec 220.127.116.11
§ <have:TriageCode>: In Used In row, deleted ‘TriageCount’
§ <have:TriageCodeValue>: In Used In row. replaced ‘TriageCount’ with ‘TriageCode’
§ <have:EMSAmbulanceStatus>: In Sub Elements row, deleted Sub-Elements Row and ‘CommentText’
§ <have:EMSAirTransportStatus>: In Used In row, inserted Used In row with the following language - HospitalStatus/Hospital/EmergencyDepartmentStatus
§ <have:EMSOffloadStatus>: In Used In row, deleted ‘Offload’
§ <have:EMSOffloadMinutes>: In Used In row, deleted ‘Offload’; inserted ‘HospitalStatus/Hospital’
§ <have:CardiologyIndicator>: In Constraints row, replaced with the following language: “Either <have:Cardiology> OR <have:CardiologySubType> must be used - but must not be used together”
§ <have:CardiologyInvasive>: In Used In row, inserted ‘CardiologyIndicator’
§ <have:OBGYN>: In Definition row, deleted ‘with labor delivery services’
§ <have:SurgeryIndicator>: In Comments row, inserted ‘Surgery Services and Surgical Services are used interchangeably’
§ <have:MorgueCapacity>: In Used In row, deleted ‘DeconCapacity’
§ <have:FacilityStatus>: In Used In row, deleted redundant <HospitalStatus/Hospital>
§ <have:CommentText>: In Usage row, inserted ‘May Use Multiple’
§ <have:LastUpdateTime>: In Constraints row, clarified language to specify that only one <LastUpdateTime> can be used.
§ Clarified language to reflect that the sample is for example purposes only.