OASIS Organization for the Advancement of Structured Information Standards Emergency Management Technical Committee (EMTC)

OASIS Organization for the Advancement of Structured Information Standards Emergency Management Technical Committee (EMTC) Emergency Interoperability Consortium January 2016 1. CAP Workshop 2015: Rome, Italy Eliot Christian, Consultant IFRC (International Federation of Red Cross and Red Crescent Societies) 2. EDXL Family of Standards Timothy Grapes, Member, OASIS EMTC Co-Chair HAVE and TEP Sub-Committees 3. Upcoming work Elysa Jones Chair, OASIS EMTC Chair, OASIS Emergency Member Section 2016 Proprietary

WORKSHOP WMO World Meteorological Organization (WMO) Public Weather Services (PWS) Programme The 2015 Common Alerting Protocol (CAP) Implementation Workshop A Presentation for the EIC on January 13, 2015 by Eliot Christian <eliot.j.christian@gmail.com>

WORKSHOP 2015 CAP Implementation Workshop 23-24 September in Rome, hosted by Fire Corps Academy of Italy (Istituto Superiore Antincendi) Co-sponsors: International Federation of Red Cross and Red Crescent Societies (IFRC) International Telecommunication Union (ITU) OASIS standards organization World Meteorological Organization (WMO) Technical meeting among experts (participants did not formally represent organizations) Jan 13, 2015 The 2015 Common Alerting Protocol (CAP) Implementation Workshop 3

WORKSHOP Uncouple CAP Training from CAP Implementation Workshops 125 participants in 2015 for CAP Jump-Start + Workshop WMO alone received Workshop requests from 100 countries, most want Jump Start as they have not implemented CAP An in-country CAP Jump Start would be more effective; typically lasts two days and focuses on the local situations So far, there have been about 20 in-country CAP Jump Starts and about 30 countries have a request outstanding The 2016 CAP Implementation Workshop will not be held jointly with an international CAP Jump Start. Jan 13, 2015 The 2015 Common Alerting Protocol (CAP) Implementation Workshop 4

WORKSHOP Growth in CAP Uptake Likely in 2016, more than half of the world's population will have at least one operational CAP alert feed at the national level (e.g., Argentina, Brazil, Canada, China, India, Indonesia, Mexico, Philippines, and the USA) Likely in 2016, 50+ countries will have at least one national CAP alert feed (MeteoAlarm will make public the CAP alert feeds of its 34 European member countries Some countries (e.g., China, Italy, USA) aggregate hundreds or more of their own CAP alert feeds Jan 13, 2015 The 2015 Common Alerting Protocol (CAP) Implementation Workshop 5

WORKSHOP CAP Alert Feed Aggregators Proliferation of CAP alert feeds underscores the need for alert aggregators that simplify access to CAP alerts International public CAP alert aggregators include The Weather Company, AccuWeather, Samsung, Google Alert Hub, WMO Alert Hub (anticipated), and Federation for Internet Alerts (FIA) Alert Hub (anticipated) Aggregators typically offer enhanced redundancy, security, authenticity, analytics, and speed Jan 13, 2015 The 2015 Common Alerting Protocol (CAP) Implementation Workshop 6

WORKSHOP IFRC Universal App IFRC "Universal App", a mobile apps development platform, offered through IFRC Global Disaster Preparedness Center Facilitates localization of apps for Giving First Aid, Finding Shelter, Hazards alerting, etc. IFRC First Aid app deployed in 70 countries (31 languages) IFRC Hazards app monitors official CAP alert feeds, already deployed in 17 countries (4 languages) IFRC Hazard app will be deployed in all other countries once there are CAP alert feeds available Jan 13, 2015 The 2015 Common Alerting Protocol (CAP) Implementation Workshop 8

WORKSHOP CAP Alert Presentation Guidance Needed CAP standard is silent on how CAP alert should be presented to user devices Public Warning Design Guidelines for FIA Messaging offers some guidance, as does Google Need for more consensus guidance on symbols and colors for common hazards such as floods, earthquakes, and volcanoes FIA will launch a Committee to take action on extending its consensus Guidelines to more hazard types and more languages Jan 13, 2015 The 2015 Common Alerting Protocol (CAP) Implementation Workshop 9

WORKSHOP OASIS EM TC Standards CAP Implementors invited to work with OASIS EM TC (Emergency Management Technical Committee) Noted uptake of EDXL (Emergency Data Exchange Language) standards from OASIS EM TC EDXL Distribution Element (EDXL-DE) can be used to disseminate content of alert messages (but such a message does not qualify as a "CAP alert") EDXL-DE is designed to be a wrapper or envelope for data; includes metadata about to whom and under what circumstances the data is to be sent or received EDXL-DE, EDXL-SITREP (situation reporting) and EDXL-RM (resource messaging) were also noted Jan 13, 2015 The 2015 Common Alerting Protocol (CAP) Implementation Workshop 10

WORKSHOP Online Resource References Report of the 2015 CAP Implementation Workshop Presentations at the 2015 CAP Implementation Workshop (includes speaker bio's and portraits) Participants in the 2015 CAP Implementation Workshop (with name, organization & e-mail Selected CAP References (selected by me) Jan 13, 2015 The 2015 Common Alerting Protocol (CAP) Implementation Workshop 11

EDXL was developed by Emergency and Health Practitioners In 2003 the first Practitioner Steering Group (PSG) was formed to address this need Emergency Data Exchange Language (EDXL) Process Practitioner Requirements Draft Requirements Message Design Specification Vendor Reviewed Requirements and Recommendations Internationally Recognized Standard Practitioner Steering Group (PSG) Standards Working Group (SWG) Scenario Teams Emergency Interoperability Consortium (EIC) OASIS Testing and Live Exercises Customers 2016 Proprietary Emergency and Healthcare Practitioners Local, State & Federal Government Industry - Product Providers 13 1/14/2016

Distribution Element Alerts & Warnings Reunification Reunification Track Patient Tracking Patient Patien t Status Incident People Finder (EDXL-TEC) Self- Register Registry Systems Registry Systems & Call-in Centers Shelter In Place Self-Evacuate Register Evacuees Shelters Evacuee Tracking (EDXL-TEC) Hospitals Vehicle Care Giver Which Hospitals are Available? Situation reporting Situation Reporting (EDXL-SitRep) Resources Equipment, Supplies, Teams Field Observation Response Resources Situation Information Casualty & Illness Summary Decision Support 2016 Proprietary

Emergency Data Exchange Language (EDXL) Standards Common Alerting Protocol (EDXL CAP) Emergency alerts, notifications, and public warnings Distribution Element (EDXL DE) - Wrap and route any emergency information (XML and non-xml) Hospital AVailability Exchange (EDXL HAVE) - Medical resource location information. Resource Messaging (EDXL RM) Emergency resource information Situation Reporting (EDXL SitRep) Situation, incident, event and response information Tracking of Emergency Clients (EDXL TEC) Emergency Evacuee tracking and Shelter information Tracking of Emergency Patients (EDXL-TEP) Emergency patient and EMS tracking information 2016 Proprietary 15 1/14/2016

Specification Status Specification Name Status Comments Common Alerting Protocol (CAP) 1.0 1.1 with Errata 1.2 1.2 Errata CAP Profiles Canada United States (IPAWS) Australia Italy Distribution Element (DE) 1.0 Hospital Availability Exchange (HAVE) 2.0 1.0 2.0 Initial release 2004 ITU Recommendation 1303 2006 Current most widely used Work underway in CAP-SC now In country not OASIS product Committee Specification Committee Specification In country not OASIS product Initial release Committee Specification Initial release Public review complete; OS 4Q 2016 Coordination with HL7 underway Resource Messaging (RM) 1.0 Initial release Situation Reporting (SitRep) 1.0 Public Review Draft Underway through 2/18/2016 Tracking of Emergency Clients 1.0 Public Review Draft (TEC) Tracking of Emergency Patients (TEP) 1.0 1.1 Committee Specification Committee Specification; OS 2Q2016 Bi-directional Transformation of OASIS EDXL- TEP (Tracking of Emergency Patients) v1.1 and HL7 v2.7.1 Specification v1.0 1.0 Committee Note, balloted successfully in HL7, final editing stages to be jointly published 2016 Proprietary 16 1/14/2016

Upcoming Relevant Activities CAP Subcommittee work Liaison Activities between OASIS and HL7 regarding TEP and HAVE National Association of State EMS Officials (NASEMSO) Resolution OASIS Cyber Threat Intelligence Technical Committee mutual interest EDXL Mobile Device Subcommittee Consideration Get involved www.oasis-open.org 2016 Proprietary 18 1/14/2016

Moderator Conclusion Questions and Discussion Plans for Upcoming session 19 1/14/2016

Contact Information Elysa Jones Chair, OASIS Emergency Management Technical Committee (EMTC) Phone: 256-694-8702 Email: elysajones@yahoo.com Timothy Grapes Co-Chair HAVE and TEP Sub-Committees Phone: 703-304-4829 Email: grapesco@outlook.com Eliot Christian Consultant, IFRC (International Federation of Red Cross and Red Crescent Societies) Phone: 571-217-9292 Email: eliot.j.christian@gmail.com 20 1/14/2016