A guest checks out of a hotel, flies home, and falls ill a week later. Alone, that case tells no one anything. ELDSNet is the European system that notices when a second guest, from a different country, who stayed at the same hotel, falls ill too, and connects two dots that no single building, doctor or nation would ever have joined.

ELDSNet stands for the European Legionnaires’ Disease Surveillance Network. It is coordinated by the European Centre for Disease Prevention and Control (ECDC) and carries out surveillance across the EU/EEA, with collaboration from wider public-health partners where cross-border cases require it [1]. Its job is to collect national Legionnaires’ disease data into one picture, and, the part that makes it distinctive, to catch travel-associated clusters that surface only when patients have already scattered back home.

Why a European layer exists at all

Most Legionnaires’ disease surveillance is national. The UK has its own arrangements, with UKHSA leading for England and the four nations reporting through their own public-health bodies. For that domestic picture, start with how UK Legionnaires’ disease surveillance works. National surveillance works well for a case acquired and treated in the same country.

Travel breaks that model. Someone exposed at a hotel, spa or cruise abroad develops symptoms only after the incubation period, by which time they are home, often in a different country from the source, and from every other guest who was exposed at the same time. The local clinician sees one isolated pneumonia. The hotel sees nothing. The pattern exists only across borders, and only if someone is looking at all the countries at once. That is the gap ECDC’s network was built to close [1].

How ELDSNet actually works

In plain terms, the network does two connected things.

First, it pools national surveillance data from EU/EEA participants. Countries report confirmed Legionnaires’ disease cases to ECDC, which aggregates them into European summaries describing how many cases were reported, how they were acquired (community, travel or healthcare-related), seasonality and species or serogroup where known [1]. This is the routine, statistical layer, the source of the “European figures” you sometimes see referenced.

Second, and more actively, it operates the travel-associated cluster scheme. When a country diagnoses a case in a patient who travelled before becoming ill, it reports the accommodation details into the network. ECDC holds a central record of recent travel-associated cases. The system continuously checks whether more than one case has stayed at the same accommodation within a defined recent window, commonly described as two or more cases linked to the same site within around two years before onset, though you should treat the exact threshold and window as ECDC’s published definition rather than a fixed rule of thumb. When that link is found, a cluster is flagged and the country where the accommodation sits is notified so it can investigate the premises [1].

The point is detection by aggregation. Each country contributes the single cases it sees; the network spots the cluster none of them could see alone. That is what “cross-border outbreak detection” means in practice.

What happens when a hotel gets flagged

When a cluster is identified, the lead is passed to the public-health authority in the country where the accommodation is located. That authority, not ECDC, contacts the site, expects a risk assessment and sampling, and looks for evidence that controls are in place and effective. There are operational timescales for responding and, where a site does not act or cannot show adequate control, for publishing the accommodation’s name on ECDC’s list so other countries and tour operators are aware. Treat those timescales and the publication mechanism as matters to confirm against ECDC’s current procedures rather than memorising a figure, because they have been revised over the years.

For a UK accommodation operator, the trigger could just as easily come the other way: a guest from overseas who stayed with you, returned home, was diagnosed there, and reported the stay. The first you hear of it may be a UK public-health contact acting on a cross-border notification involving ECDC or an overseas public-health authority, routed back through the UK system.

What nobody tells you about travel clusters

The instinct of most accommodation managers is that they would know if their building were making people ill, a cluster of guests complaining, a pattern reception would notice. Travel surveillance turns that assumption inside out, and three things about it genuinely surprise people:

  • You can be flagged with no UK cases and no local signal whatsoever. If both linked guests live abroad and were diagnosed abroad, nobody in your country saw a single case. The cluster exists entirely in ECDC’s cross-border view. Your first warning is the phone call.

  • The two linked cases may have stayed months apart. Because the matching window spans a long recent period rather than the same night, the “cluster” can be two strangers who never overlapped, never met, and visited in different seasons. A persistent, low-level source can connect them across that gap, which is exactly why a single notification is taken seriously rather than dismissed as coincidence.

  • A flag is about the controls you can evidence, not guilt. Being named in a travel cluster does not prove your water system was the source; investigations sometimes find another origin or none at all. But the response is judged on whether you can produce a current risk assessment, monitoring records and disinfection evidence on request. The buildings that come through cleanly are the ones whose paperwork already existed before the call, not the ones that started assembling it afterwards.

How UK data feeds in

The UK point is more careful than “the UK is just another ELDSNet member”. ECDC describes ELDSNet participation as EU Member States plus Iceland and Norway, while also noting collaboration with WHO and public-health authorities of non-EU countries [1]. For a UK duty holder, the practical issue is not the membership label. It is that UKHSA and the four-nation public-health system still need to handle UK cases, UK accommodation notifications and cooperation with overseas authorities where travel history crosses borders [2].

So a UK guest’s case picked up abroad, or a foreign guest’s case linked to a UK hotel, may still move through UK public-health channels in liaison with ECDC or the relevant overseas authority. The exact operational route should be confirmed against current UKHSA and ECDC guidance, because post-EU-exit arrangements and data-access mechanisms can change faster than an operator’s written scheme.

What the published European reports cover is largely descriptive: counts and rates by country, the split between community, travel and healthcare-associated acquisition, seasonal distribution, and the accommodation sites named under the travel scheme. They are a surveillance picture, not a real-time outbreak alarm, useful for understanding patterns, less useful for assuming any single year’s movement means a real change in risk.

This article explains how the surveillance network operates; it is not public-health or legal advice. Any actual cluster notification, sampling decision or enforcement response is led by the relevant public-health authority, and the control of your own water systems should rest on a current, site-specific risk assessment carried out by a competent person rather than on whether a case has ever been linked to your building.

What an accommodation operator should have ready

The traffic value of this topic is not just “what is ELDSNet?”. The useful question is what a hotel, serviced-apartment block or holiday accommodation operator should be able to produce if a travel-linked notification arrives.

  • A current Legionella risk assessment for the accommodation water systems, including showers, spa pools, hot tubs, cooling towers or other aerosol-generating systems where present.
  • The written scheme and monitoring records showing temperature checks, flushing, cleaning, remedial work and review dates. If the enquiry involves a UK property, the records need to make sense to UK public-health officers, not only to the contractor who wrote them.
  • Recent sampling results and the reason for sampling, especially if the site has spa pools, hot tubs or previous remedial work. Pair this with the guide to sporadic cases, clusters and outbreaks so the record does not overreact to one case or underreact to a pattern.
  • A named internal contact who can answer public-health questions while the competent person or water-treatment contractor is mobilised.
  • A habit of reading surveillance figures cautiously. How to read UK Legionnaires’ disease figures explains why a count going up or down is rarely a simple building-risk story.

FAQ

What triggers an ELDSNet travel-associated cluster flag?

A flag is raised when the network links more than one Legionnaires’ case to the same accommodation within a defined recent period, generally described as two or more cases at the same site within around two years before symptom onset, with the precise definition set by ECDC. The cases can be residents of different countries diagnosed independently, which is the whole reason the network exists.

Will a UK hotel be told if it is named in a travel cluster?

Yes. The lead passes to the public-health authority in the country where the accommodation sits, so a flagged UK site is contacted through the UK system. The authority expects a prompt risk assessment, sampling and evidence of effective control, and there are escalation steps, including publication of the site, where a premises does not respond or cannot demonstrate adequate control.

Does one guest falling ill after a stay create a cluster?

Not on its own, a single travel-associated case is recorded and monitored but does not by itself constitute a cluster, which requires a second linked case at the same accommodation within the matching window. That said, a single case can still prompt enquiry, and it is the building’s existing controls and records, not the case count, that determine how comfortable that enquiry is.

How do UK cases interact with the European network?

Through UK national surveillance first, with cross-border notifications handled through UKHSA, the four-nation public-health system and the relevant overseas authority where a UK resident or UK accommodation is involved [2]. Because ECDC describes ELDSNet as an EU/EEA network with non-EU collaboration, a UK operator should check the current operational route rather than assume UK reporting works exactly like EU/EEA member reporting [1].

What to do today

If you run or oversee accommodation, do one thing this week: confirm you could answer an ELDSNet-driven enquiry within the response window without scrambling. Pull your current Legionella risk assessment, the most recent monitoring records and any disinfection certificates, and check they are current and findable by someone who is not you. Detection happens abroad, weeks late, in a system you cannot influence, the only part you control is whether the evidence is already in order when the call comes.

Sources

  1. European Centre for Disease Prevention and Control, “European Legionnaires’ Disease Surveillance Network (ELDSNet)”. https://www.ecdc.europa.eu/en/about-us/partnerships-and-networks/disease-and-laboratory-networks/eldsnet
  2. UK Health Security Agency, “Legionnaires’ disease: surveillance reports and guidance”. https://www.gov.uk/government/collections/legionnaires-disease-guidance-data-and-analysis