Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

2.3 Workshop "Next Generation Emergency Services" 27th of July

760 views

Published on

2.3 Workshop "Next Generation Emergency Services" 27th of July COncORDE

  • Be the first to comment

  • Be the first to like this

2.3 Workshop "Next Generation Emergency Services" 27th of July

  1. 1. www.episecc.eu www.concorde-project.eu Dr. Alkiviadis Giannakoulias European 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”.
  2. 2. www.episecc.eu www.concorde-project.eu 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
  3. 3. www.episecc.eu www.concorde-project.eu 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
  4. 4. www.episecc.eu www.concorde-project.eu 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
  5. 5. www.episecc.eu www.concorde-project.eu 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
  6. 6. www.episecc.eu www.concorde-project.eu COncORDE’s Principle – Follow the Patient COncORDE – a patient centred approach
  7. 7. www.episecc.eu www.concorde-project.eu 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
  8. 8. www.episecc.eu www.concorde-project.eu 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
  9. 9. www.episecc.eu www.concorde-project.eu COncORDE’s position in the disaster cycle
  10. 10. www.episecc.eu www.concorde-project.eu Map centric
  11. 11. www.episecc.eu www.concorde-project.eu COncORDE rescue application
  12. 12. www.episecc.eu www.concorde-project.eu 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
  13. 13. www.concorde-project.eu www.episecc.eu www.concorde-project.eu Platform technical characteristics
  14. 14. Map COncORDE Architecture EventLogger Business Operations Management Storage management Knowledge base and ontologies External Systems - Hospital information - Cross border organisations - PSAP Persistence layer Cross-cutting services (support) layer UsersManagementAndSecurityPolicy Securitypolicy–exceptionhandling Auditing 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 SemanticsandKnowledge Management Services interface sub-layer Common Field Picture (SITREP) Patient Resource Users Web/Android clients Presentation layer UI Components (Screens) External Data services - Linked data ontologies - Weather web services Business rules Incidenthistoryandplayback Incident Response Team Management Social Media Messaging Supporting Material Management Patient Management Field Devices - Triage - Communication Bridge
  15. 15. Map COncORDE Architecture EventLogger Business Operations Management Storage management Knowledge base and ontologies External Systems - Hospital information - Cross border organisations - PSAP Persistence layer Cross-cutting services (support) layer UsersManagementAndSecurityPolicy Securitypolicy–exceptionhandling Auditing 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 SemanticsandKnowledge Management Services interface sub-layer Common Field Picture (SITREP) Patient Resource Users Web/Android clients Presentation layer UI Components (Screens) External Data services - Linked data ontologies - Weather web services Business rules Incidenthistoryandplayback Incident Response Team Management Social Media Messaging Supporting Material Management Patient Management Field Devices - Triage - Communication Bridge
  16. 16. Map COncORDE Architecture EventLogger Business Operations Management Storage management Knowledge base and ontologies External Systems - Hospital information - Cross border organisations - PSAP Persistence layer Cross-cutting services (support) layer UsersManagementAndSecurityPolicy Securitypolicy–exceptionhandling Auditing 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 SemanticsandKnowledge Management Services interface sub-layer Common Field Picture (SITREP) Patient Resource Users Web/Android clients Presentation layer UI Components (Screens) External Data services - Linked data ontologies - Weather web services Business rules Incidenthistoryandplayback Incident Response Team Management Social Media Messaging Supporting Material Management Patient Management Field Devices - Triage - Communication Bridge Organization Registration User registration Bystander registration
  17. 17. Map COncORDE Architecture EventLogger Business Operations Management Storage management Knowledge base and ontologies External Systems - Hospital information - Cross border organisations - PSAP Persistence layer Cross-cutting services (support) layer UsersManagementAndSecurityPolicy Securitypolicy–exceptionhandling Auditing 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 SemanticsandKnowledge Management Services interface sub-layer Common Field Picture (SITREP) Patient Resource Users Web/Android clients Presentation layer UI Components (Screens) External Data services - Linked data ontologies - Weather web services Business rules Incidenthistoryandplayback Incident Response Team Management Social Media Messaging Supporting Material Management Patient Management Field Devices - Triage - Communication Bridge
  18. 18. Map COncORDE Architecture EventLogger Business Operations Management Storage management Knowledge base and ontologies External Systems - Hospital information - Cross border organisations - PSAP Persistence layer Cross-cutting services (support) layer UsersManagementAndSecurityPolicy Securitypolicy–exceptionhandling Auditing 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 SemanticsandKnowledge Management Services interface sub-layer Common Field Picture (SITREP) Patient Resource Users Web/Android clients Presentation layer UI Components (Screens) External Data services - Linked data ontologies - Weather web services Business rules Incidenthistoryandplayback Incident Response Team Management Social Media Messaging Supporting Material Management Patient Management Field Devices - Triage - Communication 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.
  19. 19. Map COncORDE Architecture EventLogger Business Operations Management Storage management Knowledge base and ontologies External Systems - Hospital information - Cross border organisations - PSAP Persistence layer Cross-cutting services (support) layer UsersManagementAndSecurityPolicy Securitypolicy–exceptionhandling Auditing 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 SemanticsandKnowledge Management Services interface sub-layer Common Field Picture (SITREP) Patient Resource Users Web/Android clients Presentation layer UI Components (Screens) External Data services - Linked data ontologies - Weather web services Business rules Incidenthistoryandplayback Incident Response Team Management Social Media Messaging Supporting Material Management Patient Management Field Devices - Triage - Communication Bridge
  20. 20. Map COncORDE Architecture EventLogger Business Operations Management Storage management Knowledge base and ontologies External Systems - Hospital information - Cross border organisations - PSAP Persistence layer Cross-cutting services (support) layer UsersManagementAndSecurityPolicy Securitypolicy–exceptionhandling Auditing 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 SemanticsandKnowledge Management Services interface sub-layer Common Field Picture (SITREP) Patient Resource Users Web/Android clients Presentation layer UI Components (Screens) External Data services - Linked data ontologies - Weather web services Business rules Incidenthistoryandplayback Incident Response Team Management Social Media Messaging Supporting Material Management Patient Management Field Devices - Triage - Communication Bridge Performs 1st triage and handles sensor data from Bluetooth-enabled medical devices, smoke sensors on the field, CBRNE sensors, etc.
  21. 21. Map COncORDE Architecture EventLogger Business Operations Management Storage management Knowledge base and ontologies External Systems - Hospital information - Cross border organisations - PSAP Persistence layer Cross-cutting services (support) layer UsersManagementAndSecurityPolicy Securitypolicy–exceptionhandling Auditing 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 SemanticsandKnowledge Management Services interface sub-layer Common Field Picture (SITREP) Patient Resource Users Web/Android clients Presentation layer UI Components (Screens) External Data services - Linked data ontologies - Weather web services Business rules Incidenthistoryandplayback Incident Response Team Management Social Media Messaging Supporting Material Management Patient Management Field Devices - Triage - Communication Bridge
  22. 22. Map COncORDE Architecture EventLogger Business Operations Management Storage management Knowledge base and ontologies External Systems - Hospital information - Cross border organisations - PSAP Persistence layer Cross-cutting services (support) layer UsersManagementAndSecurityPolicy Securitypolicy–exceptionhandling Auditing 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 SemanticsandKnowledge Management Services interface sub-layer Common Field Picture (SITREP) Patient Resource Users Web/Android clients Presentation layer UI Components (Screens) External Data services - Linked data ontologies - Weather web services Business rules Incidenthistoryandplayback Incident Response Team Management Social Media Messaging Supporting Material Management Patient Management Field Devices - Triage - Communication 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
  23. 23. Map COncORDE Architecture EventLogger Business Operations Management Storage management Knowledge base and ontologies External Systems - Hospital information - Cross border organisations - PSAP Persistence layer Cross-cutting services (support) layer UsersManagementAndSecurityPolicy Securitypolicy–exceptionhandling Auditing 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 SemanticsandKnowledge Management Services interface sub-layer Common Field Picture (SITREP) Patient Resource Users Web/Android clients Presentation layer UI Components (Screens) External Data services - Linked data ontologies - Weather web services Business rules Incidenthistoryandplayback Incident Response Team Management Social Media Messaging Supporting Material Management Patient Management Field Devices - Triage - Communication Bridge
  24. 24. Map COncORDE Architecture EventLogger Business Operations Management Storage management Knowledge base and ontologies External Systems - Hospital information - Cross border organisations - PSAP Persistence layer Cross-cutting services (support) layer UsersManagementAndSecurityPolicy Securitypolicy–exceptionhandling Auditing 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 SemanticsandKnowledge Management Services interface sub-layer Common Field Picture (SITREP) Patient Resource Users Web/Android clients Presentation layer UI Components (Screens) External Data services - Linked data ontologies - Weather web services Business rules Incidenthistoryandplayback Incident Response Team Management Social Media Messaging Supporting Material Management Patient Management Field Devices - Triage - Communication Bridge Patient centred. Once a new patient is added a workflow (pre-defined business rule) is initiated.
  25. 25. www.episecc.eu www.concorde-project.eu Platform Screens (Web Desktop)
  26. 26. www.episecc.eu www.concorde-project.eu Platform Screens (Web Desktop)
  27. 27. www.episecc.eu www.concorde-project.eu Platform Screens (Web Desktop)
  28. 28. www.episecc.eu www.concorde-project.eu Platform Screens (Web Desktop with Applications)
  29. 29. www.episecc.eu www.concorde-project.eu Map Functionality (Quick Search)
  30. 30. www.episecc.eu www.concorde-project.eu Map Functionality (Alarms)
  31. 31. www.episecc.eu www.concorde-project.eu Map Functionality (Tasks)
  32. 32. www.episecc.eu www.concorde-project.eu 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
  33. 33. www.episecc.eu www.concorde-project.eu Thank You

×