OASIS Emergency Management TC

Join TC     TC Page     Send a comment to this TC

Enabling information exchange to advance incident preparedness and response to emergency situations

Elysa Jones, elysajones@yahoo.com, Chair
Rex Brooks, rexb@starbourne.com, Secretary

Table of Contents


The video "Overview of EDXL Emergency Standards" is now available in both English and Italian. You can access the English version at https://www.youtube.com/watch?v=7eoV5XwZVO8 and the Italian version at https://vimeo.com/234306686?utm_source=email&utm_medium=vimeo-cliptranscode-201504&utm_campaign=29220.

Mert Gencturk from SRDC Corp, a spin-off from the Middle East Technical University, Software Research and Development Center (METU-SRDC) discusses his work on the C2-SENSE Project, a project to a develop a profile-based Emergency Interoperability Framework that exposes the functionalities of C2 Systems, Sensor Systems and other emergency/crisis management systems. The framework uses the OASIS CAP, EDXL SitRep, EDXL RM, EDXL HAVE and EDXL TEP standards. C2-SENSE is a joint project of 8 partners from France (SAFRAN), Austria (AIT), Italy (LUTECH, REGOLA, Innova Puglia, Regione Puglia), Turkey (SRDC) and Poland (PIAP). Watch the full presentation here: https://youtu.be/lDwlAYsshN0: 17 July 2017

HL7 and OASIS Announce Joint Publication of Implementation Guide to Advance Emergency and Disaster Response; 20 Sept 2016

On September 23-24, 2015 the international CAP Workshop was held in Rome. You can access the presentations here. You can access the Final Report here.

On 11 August 2015, the Emergency Management TC approved Emergency Data Exchange Language Situation Reporting (EDXL-SitRep)v1.0 as a Committee Specification Draft/Public Review Draft and arranged for the 60-Day public review.

On 15 October 2015 National Association of State Emergency Medical Service Officials (NASEMSO) signed a resolution calling for Completion and Implementation of a Data Standard for Tracking of Emergency Patients (TEP)

On 04 August 2015, the Emergency Management TC approved Emergency Data Exchange Language Tracking of Emergency Patients (EDXL-TEP) 1.1 as a Committee Specification Draft/Public Review Draft and arranged for the 30-Day Public Review.

On 13 January 2015, the Emergency Management TC approved Emergency Data Exchange Language Hospital AValability Exchange (EDXL-HAVE) 2.0 as a Committee Specification Draft/Public Review Draft and arranged for the 60-Day Public Review.

Visit the Emergency Management Technical Committee (EM-TC) Activities page for more current topics.


The EM-TC creates vendor-neutral and platform agnostic standards for organizations and agencies to more easily exchange emergency information. The EM-TC welcomes participation from members of the emergency management and response community, developers and implementers, and members of the public concerned with disaster management and response.

The Emergency Data Exchange Language (EDXL) is a broad initiative to create an integrated framework for a wide range of emergency data exchange standards to support operations, logistics, planning and finance.

Overview links below are provided for completed OASIS standards only. Non-linked items are works in progress. For most recent versions of all technical work see Technical Work Produced by the Committee

EM-TC standard efforts include:

For more information, see the TC Charter and FAQ


  • EM CAP Profiles SC
    Designs, develops, and releases XML-based standards and specifications as CAP Profiles based on the CAP Standard.
    Provides ongoing maintenance of the CAP standard and related work.
    Ensures the proper use and integration of geographic standards in the development of EDXL standards.
    Researches, analyzes, recommends, and organizes currently available information on implementation challenges and comments regarding the EDXL-HAVE standard.
  • EM Infrastructure Framework SC
    Produces a horizontal intellectual effort predicated on establishing a common set of EM infrastructure standards, regardless of originating industry and/or agency segment. In particular, it provides ongoing maintenance of the EDXL-DE standard and related work.
  • EM Messages and Notification SC
    Addresses procedures and formats for exchanging new and updated information related to functions including public safety, emergency response and homeland security. In particular, it provides ongoing maintenance of the EDXL-RM and EDXL-SitRep standards and related work.
  • EM Reference Information Model SC
    Creates the EDXL-RIM specification to provide a high-level, abstract, information model for the family of EDXL specifications. Provides guidance on extensions and constraints (profiles) and maintains Common Types, EDXL-CIQ and EDXL-GSF.
    Develops the OASIS EDXL-Tracking of Emergency Patients (EDXL-TEP) messaging standard, which assists emergency responders, coordinators and management in the exchange of emergency patient and EMS tracking information, thus increasing the effectiveness of emergency medical management, patient tracking and care, and family notification.
    Develops the OASIS EDXL-Tracking of Emergency Clients (EDXL-TEC) messaging standard to facilitate the tracking of evacuees and other displaced persons during emergencies, disasters, and routine day-to-day incidents, the transport of such emergency clients to shelters, and the repatriation and reunification of emergency clients with their families.
  • EM Adoption SC
    The former EM Adoption SC has migrated to the OASIS Emergency Management Adoption TC

TC Liaisons

On January 1, 2015 Health Level Seven International and OASIS signed a Statement of Understanding formalizing a liaison agreement between the two organizations.

TC Tools and Approved Publications

Technical Work Produced by the Committee

Developers please note: Internet searches may lead to earlier versions of schemas, which may cause confusion, if used as implementation directive.
To ensure that you get the versions that correspond to the published standards, please retrieve them only from the following selection.

  • Common Alerting Protocol 1.2 (EDXL-CAP v1.2, Schema)
  • Warning:

    The current posting for this standard contains the wrong .bmp for the DOM and hence does not reflect one of the submitted changes. The good news is that the normative portion of the document is okay (except bold is missing from MIME type, which would indicate the other change that MIME type is required). The TC is working with the TC Administrator to correct the situation.

    - EDXL-CAP 1.2 Profiles:
  • Common Alerting Protocol 1.1 (EDXL-CAP v1.1) incorporating Errata
  • - EDXL-CAP 1.1 Profile(s):
  • Emergency Data Exchange Language Distribution Element 1.0 (EDXL-DE v1.0)
  • Emergency Data Exchange Language Hospital AVailability Exchange 1.0 (EDXL-HAVE v1.0) incorporating Draft Errata
  • - xsd Schemas:

  • Emergency Data Exchange Language Resource Messaging 1.0 (EDXL-RM v1.0) incorporating Draft Errata
  • - xsd Schemas:

Expository Work Produced by the Committee

External Resources

Although not produced by the OASIS Emergency Management TC, the following information offers useful insights into its work.

Mailing Lists and Comments

emergency: the list used by TC members to conduct Committee work. TC membership required to post. TC members are automatically subscribed; the public may view archives.

emergency-comment: a public mail list for providing input to the OASIS emergency Technical Committee members. Subscribe or view archives.*

emergency-dev: an unmoderated, public mail list that provides an open forum for developers to exchange ideas and information on implementing the emergency OASIS Standard. Subscribe or view archives.*

*To minimize spam, you must subscribe to these lists before posting.

Additional Information

Meeting Schedule:

  • TC Meetings: Regular TC conference calls are held every other Tuesday at 12:00 P.M. EST/EDT
  • Subcommittee Meetings: Please see appropriate subcommittee page for specifics.

In The News: press coverage can be found under the press link.

Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.