2.3 workshop "next generation emergency services" 27th of july

www.episecc.euwww.concorde-project.eu

Dr. Alkiviadis GiannakouliasEuropean Dynamiics SA

Workshop: "Next Generation Emergency Services"

27 July 2016

This project has received funding from the European Union’s Seventh Framework Programme for research, technological development and demonstration under grant agreement no. 607814 “COncORDE”.


Meeting Objectives

To present a brief outline of the COncORDE project

To provide an overview of the potential outcomes

To present our technical approach and the concept of the web-desktop platform that will be used throught the project


Challenges to be solved by COncORDE

Improves coordination

Fills the gap for a Pan-European solution for Different kinds of emergencies. All Hazards applicability

The COncORDE system is designed with users to ensure high acceptability in operational environment


Challenge 1: Improve Coordination In order to have Interoperability, we first need to ensure (intra-)operability

Organisational Technical

In order to improve Multiagency coordination we need to ensure that there are tools to visualise and document the response at Single agency level

COncORDE focuses on enabling this for the organisations acting at the level of EMS response on the ground

The vision: Prove the concept of improved operability and coordination at Single agency level Apply the same principles to the other agencies – Fire, Police, SAR, Military. All

responder units in emergency follow Incident Command Systems/ICS Establish the common foundation to interlink multiagencies


Challenge 2: Pan-European All Hazards System

A pan-European system is more challenging than a national system (US, Australia)

Numerous debates in every aspect of EMS work across Europe: differences in preferred systems of triage differences in medical protocols country/region specific approaches to first response differences in professional training curricula and many more…

The differences are not likely to be resolved in the near future

A Pan-European All Hazards solution is only possible if it builds on commonalities


COncORDE’s Principle – Follow the Patient

COncORDE – a patient centred approach


The Common “Anatomy” of Emergency Medical Response

Emergency medical response takes place in 5 conceptual spaces …no matter where…no matter what the nature/type/size etc… of the incident

In these 5 spaces the main EMS response actors have clear sets of function/tasks in relation to the patients


What will the system do?• FRAGMENT 1 INFORMATION FROM PSAP/112 AND

FIRST RECEIVER HOSPITALS• FRAGMENT 2 JOIN INCIDENT/EMS• FRAGMENT 3 ESTABLISH COMMAND• FRAGMENT 4 SHARE AND USE INFORMATION

• FRAGMENT 5 STAFF LOCATION AND ROLE VISIBILITY• FRAGMENT 6 INCIDENT/SITREP, PATIENT DATA

UPDATES, URGENT NOTIFICATIONS AND WARNINGS

• FRAGMENT 7 BYSTANDERS• FRAGMENT 8 FIND, TRIAGE, TRACK, RETRIEVE

PATIENTS• FRAGMENT 9 PATIENT MEDICAL TREATMENT,

TRIAGE, NEEDS• FRAGMENT 10 DSS ON MATCHING MULTIPLE

DYNAMIC DATA• FRAGMENT 11 FIRST RECEIVER RESOURCE,

EPIDEMIOLOGY SURVEILLANCE• FRAGMENT 12 FIRST RECEIVER PATIENT TRACKING• EVALUATION


COncORDE’s position in the disaster cycle


Map centric


COncORDE rescue application


Platform Concept• The concept of Web Desktop– Easy access from anywhere through the web interface– Real-time collaboration platform

• The concept of Live Integration Environment– Virtual communities define workspaces for members to use

services/applications that facilitate interaction and processing of content– Instant notifications, content sharing, easy interaction through direct

messaging (Live)

• The generic and custom applications and components– User management, access rights, … (generic)– Patient Triage Application– Integration through a well-defined API– Support for any web-accessible application

www.concorde-project.euwww.episecc.eu

www.concorde-project.eu

Platform technical characteristics

Map

COncORDE Architecture

Even

t Log

ger

Business Operations

Management

Storage management

Knowledge base and

ontologies

External Systems- Hospital information- Cross border

organisations- PSAP

Persistence layer

Cross-cutting services (support) layer

Use

rs M

anag

emen

t And

Sec

urity

Pol

icy

Secu

rity

polic

y –

exce

ption

han

dlin

g

Audi

ting

Data interface sub-layer

Data conversion Data composition Data mapping Data access

RDBMSFile system

Decision support services

Field Data

Logging and

Triage

Services (applications) layer

Sem

antic

s and

Kn

owle

dge

Man

agem

ent

Services interface sub-layer

Common Field Picture

(SITREP)

Patient

Resource

UsersWeb/Android

clients

Presentation layer UI Components (Screens)

External Data services- Linked data

ontologies- Weather web

services

Business rules

Inci

dent

hist

ory

and

play

back

Incident Response Team Management

Social Media

Messaging

Supporting Material

Management

Patient Management

Field Devices- Triage- Communication

Bridge

Map


Even

t Log

ger

Business Operations

Management

Storage management

Knowledge base and

ontologies


organisations- PSAP

Persistence layer


Use

rs M

anag

emen

t And

Sec

urity

Pol

icy

Secu

rity

polic

y –

exce

ption

han

dlin

g

Audi

ting



RDBMSFile system


Field Data

Logging and

Triage


Sem

antic

s and

Kn

owle

dge

Man

agem

ent



(SITREP)

Patient

Resource

UsersWeb/Android

clients




services

Business rules

Inci

dent

hist

ory

and

play

back


Social Media

Messaging

Supporting Material

Management

Patient Management


Bridge

Organization RegistrationUser registrationBystander registration

Map


Even

t Log

ger

Business Operations

Management

Storage management

Knowledge base and

ontologies


organisations- PSAP

Persistence layer


Use

rs M

anag

emen

t And

Sec

urity

Pol

icy

Secu

rity

polic

y –

exce

ption

han

dlin

g

Audi

ting



RDBMSFile system


Field Data

Logging and

Triage


Sem

antic

s and

Kn

owle

dge

Man

agem

ent



(SITREP)

Patient

Resource

UsersWeb/Android

clients




services

Business rules

Inci

dent

hist

ory

and

play

back


Social Media

Messaging

Supporting Material

Management

Patient Management


Bridge

Map


Even

t Log

ger

Business Operations

Management

Storage management

Knowledge base and

ontologies


organisations- PSAP

Persistence layer


Use

rs M

anag

emen

t And

Sec

urity

Pol

icy

Secu

rity

polic

y –

exce

ption

han

dlin

g

Audi

ting



RDBMSFile system


Field Data

Logging and

Triage


Sem

antic

s and

Kn

owle

dge

Man

agem

ent



(SITREP)

Patient

Resource

UsersWeb/Android

clients




services

Business rules

Inci

dent

hist

ory

and

play

back


Social Media

Messaging

Supporting Material

Management

Patient Management


Bridge

An event is any significant task/activity within COncORDE’s context that should be stored in the database in order to enable the post-event play-back capability for training and analysis purposes. Events include system generated events, users’ actions and all persistency services transactions associated with each event (CRUD).Uses the events list in order to pass a list of bookmarks to the video captured at the PSAP for a specific incident.

Map


Even

t Log

ger

Business Operations

Management

Storage management

Knowledge base and

ontologies


organisations- PSAP

Persistence layer


Use

rs M

anag

emen

t And

Sec

urity

Pol

icy

Secu

rity

polic

y –

exce

ption

han

dlin

g

Audi

ting



RDBMSFile system


Field Data

Logging and

Triage


Sem

antic

s and

Kn

owle

dge

Man

agem

ent



(SITREP)

Patient

Resource

UsersWeb/Android

clients




services

Business rules

Inci

dent

hist

ory

and

play

back


Social Media

Messaging

Supporting Material

Management

Patient Management


Bridge

Map


Even

t Log

ger

Business Operations

Management

Storage management

Knowledge base and

ontologies


organisations- PSAP

Persistence layer


Use

rs M

anag

emen

t And

Sec

urity

Pol

icy

Secu

rity

polic

y –

exce

ption

han

dlin

g

Audi

ting



RDBMSFile system


Field Data

Logging and

Triage


Sem

antic

s and

Kn

owle

dge

Man

agem

ent



(SITREP)

Patient

Resource

UsersWeb/Android

clients




services

Business rules

Inci

dent

hist

ory

and

play

back


Social Media

Messaging

Supporting Material

Management

Patient Management


Bridge

Performs 1st triage and handles sensor data from Bluetooth-enabled medical devices, smoke sensors on the field, CBRNE sensors, etc.

Map


Even

t Log

ger

Business Operations

Management

Storage management

Knowledge base and

ontologies


organisations- PSAP

Persistence layer


Use

rs M

anag

emen

t And

Sec

urity

Pol

icy

Secu

rity

polic

y –

exce

ption

han

dlin

g

Audi

ting



RDBMSFile system


Field Data

Logging and

Triage


Sem

antic

s and

Kn

owle

dge

Man

agem

ent



(SITREP)

Patient

Resource

UsersWeb/Android

clients




services

Business rules

Inci

dent

hist

ory

and

play

back


Social Media

Messaging

Supporting Material

Management

Patient Management


Bridge

Map


Even

t Log

ger

Business Operations

Management

Storage management

Knowledge base and

ontologies


organisations- PSAP

Persistence layer


Use

rs M

anag

emen

t And

Sec

urity

Pol

icy

Secu

rity

polic

y –

exce

ption

han

dlin

g

Audi

ting



RDBMSFile system


Field Data

Logging and

Triage


Sem

antic

s and

Kn

owle

dge

Man

agem

ent



(SITREP)

Patient

Resource

UsersWeb/Android

clients




services

Business rules

Inci

dent

hist

ory

and

play

back


Social Media

Messaging

Supporting Material

Management

Patient Management


Bridge

• Order of evacuation of patients to the field• Allocation of patients to FRs• Prediction of incident’s demand for resources• Allocation of EMS to incidents• Allocation of tasks to available actors on the field

Map


Even

t Log

ger

Business Operations

Management

Storage management

Knowledge base and

ontologies


organisations- PSAP

Persistence layer


Use

rs M

anag

emen

t And

Sec

urity

Pol

icy

Secu

rity

polic

y –

exce

ption

han

dlin

g

Audi

ting



RDBMSFile system


Field Data

Logging and

Triage


Sem

antic

s and

Kn

owle

dge

Man

agem

ent



(SITREP)

Patient

Resource

UsersWeb/Android

clients




services

Business rules

Inci

dent

hist

ory

and

play

back


Social Media

Messaging

Supporting Material

Management

Patient Management


Bridge

Map


Even

t Log

ger

Business Operations

Management

Storage management

Knowledge base and

ontologies


organisations- PSAP

Persistence layer


Use

rs M

anag

emen

t And

Sec

urity

Pol

icy

Secu

rity

polic

y –

exce

ption

han

dlin

g

Audi

ting



RDBMSFile system


Field Data

Logging and

Triage


Sem

antic

s and

Kn

owle

dge

Man

agem

ent



(SITREP)

Patient

Resource

UsersWeb/Android

clients




services

Business rules

Inci

dent

hist

ory

and

play

back


Social Media

Messaging

Supporting Material

Management

Patient Management


Bridge

Patient centred. Once a new patient is added a workflow (pre-defined business rule) is initiated.


Platform Screens (Web Desktop)


Platform Screens (Web Desktop with Applications)


Map Functionality (Quick Search)


Map Functionality (Alarms)


Map Functionality (Tasks)


System Validation• 2 sets of large scale pilots

• M30 pilot 1 consisting of 2 different large scale scenarios

• Evaluation and improvements

• M36 pilot 2 repeating the 2 different large scale scenarios and evaluation


Thank You

2.3 workshop "next generation emergency services" 27th of july

Presentations & Public Speaking