Infokiri
| Dokumendiregister | Terviseamet |
| Viit | 8.1-2/24/2570-1 |
| Registreeritud | 06.03.2024 |
| Sünkroonitud | 26.03.2024 |
| Liik | Sissetulev dokument |
| Funktsioon | 8.1 Nakkushaiguste seire, ennetuse ja tõrje korraldamine |
| Sari | 8.1-2 Nakkushaiguste epidemioloogiaalane riigiväline kirjavahetus |
| Toimik | 8.1-2/2024 |
| Juurdepääsupiirang | Avalik |
| Juurdepääsupiirang | |
| Adressaat | ECDC respiratory viruses |
| Saabumis/saatmisviis | ECDC respiratory viruses |
| Vastutaja | Olga Sadikova (TA, Peadirektori asetäitja (1) vastutusvaldkond, Nakkushaiguste epidemioloogia osakond, Gripikeskus) |
| Originaal | Ava uues aknas |
Failid
EpiPulse Event-Based Surveillance
Influenza and other respiratory viruses (IRV) Domain
Ajibola Omokanye, ECDC
05 March 2024
European Centre for Disease Prevention and Control
Agenda
1. Overview of EpiPulse functionality
• Access to IRV domain • EpiPulse Item types
2. Event-based surveillance in EpiPulse
• When and how to post an Event • Role of ECDC Round Table and Communicable Disease Threat Reports • The value of timely positive or negative findings in country replies
3. Review of IRV domain EpiPulse use in 2023
4. Network user experiences and feedback
• What challenges are users facing? • How can we improve the network’s experience with EpiPulse?
2
1. Overview of EpiPulse functionality
What is EpiPulse?
• Online portal for European public health authorities and global partners • Collect, analyse, share, and discuss data for threat detection, monitoring, risk assessment and outbreak response. • Platform integrates indicator-based and event-based surveillance, including molecular typing.
3
1. Overview of EpiPulse functionality
What is EpiPulse?
• Online portal for European public health authorities and global partners • Collect, analyse, share, and discuss data for threat detection, monitoring, risk assessment and outbreak response. • Platform integrates indicator-based and event-based surveillance, including molecular typing.
4
Events, Forum and News sections launched in 2021
1. Overview of EpiPulse functionality
Access to IRV domain
• Several domains exist within EpiPulse
• Access dependent on CCB nomination
• Current users for IRV network:
OCPs / NFPs for Viral Respiratory Diseases from EU/EEA and EU-pre-accession countries
Other users that can invited to specific events (when applicable):
EURL Avian Influenza EFSA WHO Euro DG SANTE (reader)
5
1. Overview of EpiPulse functionality
EpiPulse Item types
There are different Item types to facilitate different activities within the platform:
• Signal
• Events
• Threats
• Long-term monitoring
• Forum
• News
6
Event-based surveillance
ECDC can open:
‘Signals’ (incidents monitored but not assessed as posing a public health risk for the EU/EEA), ‘Events’, ‘Threats’ as well as reclassify a Signal and Event to Threat, if the situation is assessed to pose a public health risk for the EU/EEA and is of concern.
External users can open:
Events – focus of today’s session Forum News
2. Event-based surveillance in EpiPulse
7
When and how to post
• According to their permissions, users can create an Event, a Forum or a News item
• An Event is defined as:
• case(s)/cluster(s)/outbreak(s)/epidemiological situation(s)/incident(s)/public health risk situation(s), • detected in/reported by one or several countries, • that according to your assessment pose (or may pose) a public health risk for the EU/EEA.
ECDC users
ECDC
Epidemic Intelligence monitoring
Algorithms running on indicator-based surveillance data (cases and isolates)
EU/EEA Member States or “partner” countries and institutions
SIGNALS EVENTS THREATS
2. Event-based surveillance in EpiPulse
8
When and how to post
• According to their permissions, users can create an Event, a Forum or a News item
• An Event is defined as:
• case(s)/cluster(s)/outbreak(s)/epidemiological situation(s)/incident(s)/public health risk situation(s), • detected in/reported by one or several countries, • that according to your assessment pose (or may pose) a public health risk for the EU/EEA.
• ECDC assesses all Events, summarising in the Situation Awareness Summary
• Should the Event be of concern within the mandate of ECDC and assessed as posing a public health risk for the EU/EEA, ECDC will re-classify the event as a Threat.
• In such cases, DG SANTE (Health Threats Unit - B2) are granted access to the Situation Awareness Summary but cannot see the initial post nor any comments from stakeholders.
ECDC users
ECDC
Epidemic Intelligence monitoring
Algorithms running on indicator-based surveillance data (cases and isolates)
EU/EEA Member States or “partner” countries and institutions
SIGNALS EVENTS THREATS
2. Event-based surveillance in EpiPulse
9
When and how to post
2. Event-based surveillance in EpiPulse
10
When and how to post
2. Event-based surveillance in EpiPulse
11
When and how to post
2. Event-based surveillance in EpiPulse
12
When and how to post
2. Event-based surveillance in EpiPulse
13
When and how to post
2. Event-based surveillance in EpiPulse
14
When and how to post
Example questions to consider:
1. What is the epidemiological setting for identified cases? (e.g. community, long term care facility)
2. Do cases have known underlying risk factors? (e.g. age, co-morbidities, immunocompromise)
3. What is the vaccination status of cases?
4. Did cases require hospital admission or supportive treatment? (e.g. antivirals, supportive oxygen)?
5. Is there recent travel history or known epidemiological link to travel-related cases, or other cases?
6. Is wider community transmission suspected?
7. Have any specific follow-up or control measures been applied?
8. Are additional lines of epidemiological investigation planned?
9. Is virus isolation and characterisation planned or under way? Are results available?
10. How representative (local, regional, national) is the data/information presented?
11. What is the short- (days/weeks), medium- (months) and long-term (years) trend in cases over time?
12. What challenges are you facing, and what support/information can ECDC/other countries offer?
2. Event-based surveillance in EpiPulse
15
Example workflow for EU/EEA country-initiated Events in EpiPulse
Step 1 - Detection
• Country identifies an Event
Step 2 - Reporting
• Country checks if a related EpiPulse Event already exists → Posts information as a Comment in reply
• If no existing Event, Country creates a new Event to share epidemiological information
• Please check whether the event you are posting meets the EWRS criteria and liaise with your country’s EWRS focal point, if required.
Step 3 - Assessing
• ECDC reviews Event post and responses from other countries
• ECDC prepares Situation Awareness Summary
Step 4 - Notifying
• It may be helpful to include details about some events in ECDC’s Communicable Disease Threat Report
• Where feasible, ECDC will consult with countries to ensure sensitive information is NOT disclosed
2. Event-based surveillance in EpiPulse
* Access to daily/weekly restricted CDTR is limited to nominated Epidemic Intelligence and Preparedness domains 16
Role of ECDC Round Table and Communicable Disease Threat Reports (CDTR)
New IRV Event ECDC IRV team
assessment ECDC Round Table
review Follow-up actions
• Review Event and classification
e.g. Event → Threat SCBTH criteria
• Open to relevant stakeholders
e.g. WHO Euro, EFSA
• Follow-up with countries
• Situation Awareness Summary
- restricted version
- public version
• Follow-up with countries
• Situation Awareness Summary included in CDTR
- Daily restricted - Weekly restricted
- Weekly public
EpiPulse *
ECDC website
2. Event-based surveillance in EpiPulse
17
2. Event-based surveillance in EpiPulse
SCBTH – Serious cross-border threat to health; EU Decision 1082/2013 18
EpiPulse vs EWRS
• EpiPulse and EWRS are complementary platforms.
• Please check if the event you are posting meets EWRS criteria and liaise with your country’s EWRS focal point, if needed.
• Development work is ongoing to harmonise the experience across the two platforms.
EpiPulse EWRS
Owner ECDC European Commission
Objective of the platform Risk assessment Risk management
Notification Biological All hazards SCBTH
Type of notification Informal Formal
2. Event-based surveillance in EpiPulse
19
The value of timely positive or negative findings in country replies
• When an Event is posted by Country A, e.g. observing an atypical outbreak or trend in detections
- Country B may post a response, confirming that they have made similar observations
• It is extremely helpful during ECDC’s assessment to receive timely
- positive findings from other countries
- negative findings from other countries, in particular neighbouring countries
- updates about ongoing investigations
• This facilitates more effective and informed assessment
3. Review of IRV domain EpiPulse use in 2023
20
Examples of effective EpiPulse use
2023-IRV-00002 Severe cases of influenza B among young persons
2023-IRV-00008 Increase in respiratory infections due to Mycoplasma pnemoniae in the EU/EEA during the season 2023/2024
• Original Event post featured comprehensive epidemiological and microbiology information
• Prompt and comprehensive replies from additional countries
• Continuous updates to the Event with additional information
• Use of attachments for visual information
3. Review of IRV domain EpiPulse use in 2023
21
Long-Term Monitoring Forum / News
• Forum provides a place for discussion around any scientific topic
• News provides a space to share other interesting information
• Neither used in 2023
Thank you
Questions?
General EpiPulse feedback and technical issues - [email protected]
IRV-specific issues - [email protected]
|
Tähelepanu! Tegemist on väljastpoolt asutust saabunud kirjaga. Tundmatu saatja korral palume linke ja faile mitte avada. |
To: Operational Contact Points for COVID-19 and Influenza, National Focal Points for Viral Respiratory Diseases
Cc: National Coordinators
Dear network members,
Many thanks to all those that participated in the IRV domain EpiPulse workshop today, and for providing very valuable feedback. Please find attached the slides presented today.
For those unable to participate today, or who had to leave early, we also welcome your IRV domain EpiPulse feedback via the following short survey by 1700 CET Friday 08/03/2024 https://app.sli.do/event/kT4FHXxkvDFw6T4KX7zXgw
Many thanks and best wishes,
The Respiratory Viruses and Legionella group
|
Confidentiality Notice
If you are not the intended recipient of this message, you are hereby kindly requested, to, consecutively, refrain from disclosing its content to any third party, delete it and inform its sender of the erroneous transmittal.
EpiPulse Event-Based Surveillance
Influenza and other respiratory viruses (IRV) Domain
Ajibola Omokanye, ECDC
05 March 2024
European Centre for Disease Prevention and Control
Agenda
1. Overview of EpiPulse functionality
• Access to IRV domain • EpiPulse Item types
2. Event-based surveillance in EpiPulse
• When and how to post an Event • Role of ECDC Round Table and Communicable Disease Threat Reports • The value of timely positive or negative findings in country replies
3. Review of IRV domain EpiPulse use in 2023
4. Network user experiences and feedback
• What challenges are users facing? • How can we improve the network’s experience with EpiPulse?
2
1. Overview of EpiPulse functionality
What is EpiPulse?
• Online portal for European public health authorities and global partners • Collect, analyse, share, and discuss data for threat detection, monitoring, risk assessment and outbreak response. • Platform integrates indicator-based and event-based surveillance, including molecular typing.
3
1. Overview of EpiPulse functionality
What is EpiPulse?
• Online portal for European public health authorities and global partners • Collect, analyse, share, and discuss data for threat detection, monitoring, risk assessment and outbreak response. • Platform integrates indicator-based and event-based surveillance, including molecular typing.
4
Events, Forum and News sections launched in 2021
1. Overview of EpiPulse functionality
Access to IRV domain
• Several domains exist within EpiPulse
• Access dependent on CCB nomination
• Current users for IRV network:
OCPs / NFPs for Viral Respiratory Diseases from EU/EEA and EU-pre-accession countries
Other users that can invited to specific events (when applicable):
EURL Avian Influenza EFSA WHO Euro DG SANTE (reader)
5
1. Overview of EpiPulse functionality
EpiPulse Item types
There are different Item types to facilitate different activities within the platform:
• Signal
• Events
• Threats
• Long-term monitoring
• Forum
• News
6
Event-based surveillance
ECDC can open:
‘Signals’ (incidents monitored but not assessed as posing a public health risk for the EU/EEA), ‘Events’, ‘Threats’ as well as reclassify a Signal and Event to Threat, if the situation is assessed to pose a public health risk for the EU/EEA and is of concern.
External users can open:
Events – focus of today’s session Forum News
2. Event-based surveillance in EpiPulse
7
When and how to post
• According to their permissions, users can create an Event, a Forum or a News item
• An Event is defined as:
• case(s)/cluster(s)/outbreak(s)/epidemiological situation(s)/incident(s)/public health risk situation(s), • detected in/reported by one or several countries, • that according to your assessment pose (or may pose) a public health risk for the EU/EEA.
ECDC users
ECDC
Epidemic Intelligence monitoring
Algorithms running on indicator-based surveillance data (cases and isolates)
EU/EEA Member States or “partner” countries and institutions
SIGNALS EVENTS THREATS
2. Event-based surveillance in EpiPulse
8
When and how to post
• According to their permissions, users can create an Event, a Forum or a News item
• An Event is defined as:
• case(s)/cluster(s)/outbreak(s)/epidemiological situation(s)/incident(s)/public health risk situation(s), • detected in/reported by one or several countries, • that according to your assessment pose (or may pose) a public health risk for the EU/EEA.
• ECDC assesses all Events, summarising in the Situation Awareness Summary
• Should the Event be of concern within the mandate of ECDC and assessed as posing a public health risk for the EU/EEA, ECDC will re-classify the event as a Threat.
• In such cases, DG SANTE (Health Threats Unit - B2) are granted access to the Situation Awareness Summary but cannot see the initial post nor any comments from stakeholders.
ECDC users
ECDC
Epidemic Intelligence monitoring
Algorithms running on indicator-based surveillance data (cases and isolates)
EU/EEA Member States or “partner” countries and institutions
SIGNALS EVENTS THREATS
2. Event-based surveillance in EpiPulse
9
When and how to post
2. Event-based surveillance in EpiPulse
10
When and how to post
2. Event-based surveillance in EpiPulse
11
When and how to post
2. Event-based surveillance in EpiPulse
12
When and how to post
2. Event-based surveillance in EpiPulse
13
When and how to post
2. Event-based surveillance in EpiPulse
14
When and how to post
Example questions to consider:
1. What is the epidemiological setting for identified cases? (e.g. community, long term care facility)
2. Do cases have known underlying risk factors? (e.g. age, co-morbidities, immunocompromise)
3. What is the vaccination status of cases?
4. Did cases require hospital admission or supportive treatment? (e.g. antivirals, supportive oxygen)?
5. Is there recent travel history or known epidemiological link to travel-related cases, or other cases?
6. Is wider community transmission suspected?
7. Have any specific follow-up or control measures been applied?
8. Are additional lines of epidemiological investigation planned?
9. Is virus isolation and characterisation planned or under way? Are results available?
10. How representative (local, regional, national) is the data/information presented?
11. What is the short- (days/weeks), medium- (months) and long-term (years) trend in cases over time?
12. What challenges are you facing, and what support/information can ECDC/other countries offer?
2. Event-based surveillance in EpiPulse
15
Example workflow for EU/EEA country-initiated Events in EpiPulse
Step 1 - Detection
• Country identifies an Event
Step 2 - Reporting
• Country checks if a related EpiPulse Event already exists → Posts information as a Comment in reply
• If no existing Event, Country creates a new Event to share epidemiological information
• Please check whether the event you are posting meets the EWRS criteria and liaise with your country’s EWRS focal point, if required.
Step 3 - Assessing
• ECDC reviews Event post and responses from other countries
• ECDC prepares Situation Awareness Summary
Step 4 - Notifying
• It may be helpful to include details about some events in ECDC’s Communicable Disease Threat Report
• Where feasible, ECDC will consult with countries to ensure sensitive information is NOT disclosed
2. Event-based surveillance in EpiPulse
* Access to daily/weekly restricted CDTR is limited to nominated Epidemic Intelligence and Preparedness domains 16
Role of ECDC Round Table and Communicable Disease Threat Reports (CDTR)
New IRV Event ECDC IRV team
assessment ECDC Round Table
review Follow-up actions
• Review Event and classification
e.g. Event → Threat SCBTH criteria
• Open to relevant stakeholders
e.g. WHO Euro, EFSA
• Follow-up with countries
• Situation Awareness Summary
- restricted version
- public version
• Follow-up with countries
• Situation Awareness Summary included in CDTR
- Daily restricted - Weekly restricted
- Weekly public
EpiPulse *
ECDC website
2. Event-based surveillance in EpiPulse
17
2. Event-based surveillance in EpiPulse
SCBTH – Serious cross-border threat to health; EU Decision 1082/2013 18
EpiPulse vs EWRS
• EpiPulse and EWRS are complementary platforms.
• Please check if the event you are posting meets EWRS criteria and liaise with your country’s EWRS focal point, if needed.
• Development work is ongoing to harmonise the experience across the two platforms.
EpiPulse EWRS
Owner ECDC European Commission
Objective of the platform Risk assessment Risk management
Notification Biological All hazards SCBTH
Type of notification Informal Formal
2. Event-based surveillance in EpiPulse
19
The value of timely positive or negative findings in country replies
• When an Event is posted by Country A, e.g. observing an atypical outbreak or trend in detections
- Country B may post a response, confirming that they have made similar observations
• It is extremely helpful during ECDC’s assessment to receive timely
- positive findings from other countries
- negative findings from other countries, in particular neighbouring countries
- updates about ongoing investigations
• This facilitates more effective and informed assessment
3. Review of IRV domain EpiPulse use in 2023
20
Examples of effective EpiPulse use
2023-IRV-00002 Severe cases of influenza B among young persons
2023-IRV-00008 Increase in respiratory infections due to Mycoplasma pnemoniae in the EU/EEA during the season 2023/2024
• Original Event post featured comprehensive epidemiological and microbiology information
• Prompt and comprehensive replies from additional countries
• Continuous updates to the Event with additional information
• Use of attachments for visual information
3. Review of IRV domain EpiPulse use in 2023
21
Long-Term Monitoring Forum / News
• Forum provides a place for discussion around any scientific topic
• News provides a space to share other interesting information
• Neither used in 2023
Thank you
Questions?
General EpiPulse feedback and technical issues - [email protected]
IRV-specific issues - [email protected]
