TESSy - The European
Surveillance System
Legionnaires’ disease annual data
Reporting Protocol 2019
ELDSNet
Surveillance data for 2018
February 2019
link to page 3 link to page 3 link to page 3 link to page 3 link to page 4 link to page 4 link to page 4 link to page 4 link to page 5 link to page 5 link to page 5 link to page 5 link to page 6 link to page 7 link to page 7 link to page 7 link to page 7 link to page 7 link to page 8 link to page 8 link to page 9 link to page 11 link to page 15 link to page 15 link to page 16
Contents
Introduction .............................................................................................................. 3
How to use this document .................................................................................................... 3
Finding further information ................................................................................................... 3
Copyright ............................................................................................................................. 3
Reporting to TESSy .................................................................................................... 4
Checking the data collection schedule .................................................................................... 4
Preparing data ..................................................................................................................... 4
Checking metadata ............................................................................................................... 4
Checking your data source profile.......................................................................................... 5
Submitting your data ............................................................................................................ 5
Finalising your submission .................................................................................................... 5
TESSy HelpDesk ................................................................................................................... 5
Changes to current Legionnaires’ disease annual metadata ............................................ 6
Annex 1 Legionnaires’ disease annual metadata ........................................................... 7
Legionnaires’ disease annual metadata set............................................................................. 7
Current record type versions ............................................................................................ 7
Legionnaires’ disease annual metadata change history ........................................................... 7
Recent Legionnaires’ disease annual metadata changes ..................................................... 7
LEGI metadata ..................................................................................................................... 8
Common TESSy variables ................................................................................................. 8
Basic epidemiological variables ......................................................................................... 9
Disease-specific epidemiological variables ....................................................................... 11
LEGIDENOM metadata ........................................................................................................ 15
Common TESSy variables (all mandatory) ....................................................................... 15
Population denominator data (all mandatory) .................................................................. 16
Page 2 of 17
link to page 4 link to page 7
Introduction
This reporting protocol is for the 2019 data call for Legionnaires’ disease annual surveillance data for
2018.
ECDC’s Reporting Protocols are data collection guidelines for reporting countries’ data managers, and
the new Reporting Protocol design is intended to improve user-friendliness by:
Introducing a uniform structure to make it easier for data managers to find data collection
information across different subjects.
Removing information not relevant to data managers.
The Reporting Protocols are supplemented by the
Technical Annex, which contains updated generic
information for each data collection.
Likewise, the Surveillance Protocol will contain some of the generic information previously contained
in the Reporting Protocols.
Because reporting countries’ data managers sometimes play multiple roles, it is sometimes relevant to
distribute subject-specific material together with a Reporting Protocol. To maintain the uniform
structure, this sort of material is now included in the annexes.
How to use this document
This Reporting Protocol provides information for reporting countries’ data managers in three main
sections:
Reporting to TESSy – contains guidelines on how to prepare data for submission to TESSy,
deadlines, subject-specific information (e.g. new changes to metadata), and links to further
information.
Annex 1 – contains:
o The metadata set for the subject(s) covered by this Reporting Protocol.
o A history of metadata changes for the subject(s) covered by this Reporting Protocol.
Annex 2 (omitted from this document) – contains subject-specific material relevant for
distribution with the Reporting Protocol.
Finding further information
Paragraphs denoted by the information icon tell where you can find further information.
Updated links to all the schedules, documentation and training materials mentioned in this Reporting
Protocol are included in the
Technical Annex (see the menu ‘Technical Guidelines and Tools’ when
logged in TESSy), including:
Metadata sets and history.
Tutorials for data transformation using respectively Excel and Access.
TESSy user documentation.
CSV an
d XML transport protocols.
Copyright
© European Centre for Disease Prevention and Control, 2019. Reproduction is authorised, provided
the source is acknowledged.
Page 3 of 17
link to page 4 link to page 4 link to page 4 link to page 5 link to page 5 link to page 5 link to page 6 link to page 7
Reporting to TESSy
This section provides both an overview of the TESSy reporting process and tips on where you can find
useful information.
The overall process is:
1.
Familiarise yourself with the data collection deadlines.
2.
Prepare (export and transform) your data.
3.
Check that your data comply with the metadata.
4.
Check that your data source profile is up-to-date.
5.
Submit your file(s) to TESSy.
6.
Finalise and approve your submission.
Checking the data col ection schedule
An updated link to the current data collections schedule is provided in the
Technical Annex.
Preparing data
After you have exported the data from your national database, you need to ensure that the data are
in a format that TESSy can accept. This applies both to the type of file submitted to TESSy (only CSV
and XML files can be submitted) and to the format of the data in certain fields.
Tutorials covering how you can transform your data to the correct TESSy format using Excel or
Access are available on the TESSy documents website. Information on the file formats is available in
the CSV Transport Protocol and XML Transport Protocol.
Checking metadata
The TESSy metadata define the fields and data formats that are valid as input to TESSy for a given
subject.
As requirements to the data to be shared among TESSy users change, the data changes needed to
support the new requirements are identified and agreed upon between the National Surveillance
Contact Points, the Network Coordination Groups and ECDC’s Disease Experts, and then implemented
as changes to the TESSy metadata.
In order to ensure that your data can be saved correctly in TESSy, you therefore need to check that
your data are correctly formatted according to the most recent metadata set.
Changes to the metadata for the subject of this Reporting Protocol are described in:
Changes to current metadata – changes since the last Reporting Protocol.
Annex 1 Metadata change history – all preceding changes.
It is especially important to focus on:
Field formats
Many fields require that data are formatted in a specific way. For example, dates must be in the
YYYY-MM-DD format; dates in the DD/MM/YYYY format will be rejected.
Coded values
Some fields only permit the use of specific values (coded values). For example,
M,
F,
UNK, or
Other are the
coded values for Gender and any other value in a Gender field will be rejected.
The metadata file contains all the definitions and rules you need to comply with to format your data
correctly for every subject (usually a disease). The file can be downloaded as an Excel file from the
TESSy documents website.
Page 4 of 17
By filtering the fields in the file by subject, you can see the fields required for your subject and the
rules applying to these fields.
The Technical Annex provides an overview of how you work with the metadata file, and the
TESSy user documentation provides in-depth details on metadata.
Checking your data source profile
Before submitting your file(s), please review the profile for your data source(s) in TESSy (go to
Data
Sources), and update the information, if necessary.
Complete and up-to-date data source information for each subject is important for improving
interpretation of data - each surveillance system has different features that need to be taken into
account when comparing data at an international level.
If your data source information is out-of-date and you do not have access rights to update it, please
request your National Focal Point for Surveillance or National Coordinator to do so.
In-depth information on the data source variables is available in the TESSy user documentation.
Submitting your data
Data are submitted through the TESSy web interface (go to
Upload).
The Technical Annex provides an overview of how you submit files to TESSy, and the TESSy user
documentation provides in-depth descriptions of all the upload methods.
Finalising your submission
The compliance of your data with the validation rules in the metadata is checked automatically during
the data upload process.
The result of your upload – i.e. rejected or validated – is displayed immediately after the conclusion
of the check in the
Validation details webpage. Please review the result carefully:
If your file has been rejected, there will be a message explaining each instance of non-
compliance with the metadata that you need to correct.
If your file has been validated, there might be warnings and remarks relating to possible data
quality issues or to potential overwriting of existing records that you should consider.
When you file has been validated and you are satisfied that all corrections have been made, please
ensure prompt approval – unapproved uploads can block for the approval of other uploads.
The TESSy user documentation provides information on reviewing validation results and adjusting
reporting periods to avoid overwriting existing records.
TESSy HelpDesk
Email:
xxxxx@xxxx.xxxxxx.xx
Telephone number:
+46-(0)8-5860 1601
Availability: 9:00 – 16:00 Stockholm time, Monday to Friday (except ECDC Holidays)
Page 5 of 17
link to page 7
Changes to current Legionnaires’ disease annual
metadata
There are no changes to the Legionnaires’ disease annual metadata for the 2019 data call.
The previous metadata changes are described in
Annex 1.
Information on changes to the metadata for other subjects is available on the TESSy
documentation website.
Page 6 of 17
link to page 7 link to page 7
Annex 1 Legionnaires’ disease annual metadata
This section describes:
The Legionnaires’ disease annual metadata set
Changes to the Legionnaires’ disease annual metadata
Legionnaires’ disease annual metadata set
The variables contained in a LEGI record were modelled to capture in disaggregate format what used
to be collected through the EWGLINET annual aggregate dataset tables. The LEGIDENOM record type
only adds population denominator data for the calculation of age-specific incidence rates. These
variables are meant to be working tools to monitor trends, to identify areas for action and increased
surveillance efforts, and to generate hypotheses for further research. The ELDSNet coordination
group and annual network meetings offer opportunity to discuss, and if necessary, revise these
variables. The next intended revision of the LEGI metadata will be for the data call in 2020.
Current record type versions
Table 1 shows the record type versions to be used when reporting 2018 Legionnaires’ disease annual
surveillance data to TESSy.
Table 1: Legionnaires’ disease record version types for 2018 annual datasets
Record
Case-based
record type version
LEGI
LEGI.5
LEGIDENOM
LEGIDENOM.1
Legionnaires’ disease annual metadata change history
Metadata changes prior to 2019 can be found on the TESSy documents website.
Recent Legionnaires’ disease annual metadata changes
Table 2: Implemented general changes to metadata
Year
Subject
Description
2018
LEGI
There were no changes to the Legionnaires’ disease annual metadata for the 2018 data call.
2017
LEGI
There were no changes to the Legionnaires’ disease annual metadata for the 2017 data call.
2016
LEGI
It is no longer mandatory to enter a value for the variable ‘Cluster’.
The variable ‘ClusterID’ has been removed.
The variable ‘LabMethod’ has a mandatory field.
2015
LEGI
Two coded values added to the variable ‘Pathogen’:
NonSG1 =
L. pneumophila non serogroup 1
SAINT = L. sainthelensi
2014
There were no changes to the Legionnaires’ disease annual metadata for the 2014 data call.
Page 7 of 17
LEGI metadata
Common TESSy variables
Record Identifier (mandatory)
Field: RecordId
Coding: Text (max 80 characters)
The record identifier is provided by the Member State. It must be
unique within the national Legionnaires’ disease surveillance system
anonymous.
Record type (mandatory)
Field: RecordType
Coding: LEGI
The record type defines the structure and the format of the data reported. The record types are defined by ECDC
and are related to the subject. Only valid combinations of subject, record type and data source are accepted.
Record type version
Field: RecordTypeVersion
Coding: 5
The version of the record type defines the current structure of the data reported. If the dataset is changed, the
version changes to the next higher integer. The current version of the LEGI record type is 5.
This variable is not mandatory as TESSy concludes the record type version from the metadataset indicated. The
variable RecordTypeVersion allows to override this default.
Subject (mandatory)
Field: Subject
Coding: LEGI
The subject describes the disease dataset to be reported.
Data source (mandatory)
Field: DataSource
Coding: List of surveillance systems
The data source specifies the surveillance system from which the data originates and is generated and
revised/updated by the national contact point for surveillance in each Member State. The descriptions of the
surveillance systems submitted to TESSy should be kept up to date and will be used to assist with data
interpretation.
Reporting country (mandatory)
Field: ReportingCountry
Coding: International organization for standardization (ISO) 3166-1-alpha-2, (two-letter code)
This variable identifies the country reporting the case.
Place of notification
Field: PlaceOfNotification
Coding:
NUTS level
UNK = Unknown
Place of the first notification of the case to a regional authority. Select the most detailed NUTS level possible.
Page 8 of 17
Date used for statistics (mandatory)
Field: DateUsedForStatistics
Coding: yyyy-mm-dd (preferred)
yyyy-Www
yyyy-mm
yyyy-Qq
yyyy
This is the date used by the national surveillance institute/organisation in case reports and official statistics. The
date used for statistics can vary from country to country (for example, date of diagnosis, date of notification).
It is recommended to use the date of onset.
Status
Field: Status
Coding:
NEW/UPDATE
DELETE
The status is used for updating data; the default is New/Update. By choosing ‘Delete’, the selected record (or
batch of data) will be marked as inactive, but will remain in TESSy to reconstruct the data for a given date in the
past.
Basic epidemiological variables
Age (mandatory)
Field: Age
Coding:
Numerical (0-120)
UNK = Unknown
Age of the person in years as reported to the national surveillance system of each Member State.
Gender (mandatory)
Field: Gender
Coding:
F = Female
M = Male
O = Other (for example, transsexual)
UNK = Not known
Gender of the person.
Date of onset (mandatory)
Field: DateOfOnset
Coding:
yyyy-mm-dd (preferred)
yyyy-mm
yyyy-Qq
yyyy
Date of symptom onset. If not known precisely, the date of onset can be estimated.
Validation: Date of onset must be before date of diagnosis which again must be before date of notification.
Date of diagnosis
Field: DateOfDiagnosis
Coding:
yyyy-mm-dd (preferred)
yyyy-Www
yyyy-mm
yyyy-Qq
Page 9 of 17
yyyy
UNK = Unknown
Date of laboratory confirmation.
Validation: Date of onset must be before date of diagnosis which again must be before date of notification.
Date of notification
Field: DateOfNotification
Coding:
yyyy-mm-dd (preferred)
yyyy-Www
yyyy-mm
yyyy-Qq
yyyy
UNK = Unknown
Date of first notification to the national surveillance system.
Validation: Date of onset must be before date of diagnosis which again must be before date of notification.
Place of residence
Field: PlaceOfResidence
Coding:
NUTS level
UNK = Unknown
Place of residence of patient at the time of disease onset. Select the most detailed NUTS level possible.
Outcome (mandatory)
Field: Outcome
Coding:
A = Alive
D = Died
UNK = Unknown
Outcome refers to the patient’s vital status resulting from Legionnaires’ disease. Death should be directly or
indirectly due to Legionnaires’ disease.
If the patient is still ill at the time of reporting, it is recommended to code the outcome as ‘Unknown’.
Classification (mandatory)
Field: Classification
Coding:
CONF = Confirmed
PROB = Probable
This variable indicates the case classification according to the EU case definition.
Validation:
Classification coded as ‘Confirmed’ AND laboratory method not coded as ‘Urinary antigen test’, ‘Culture’
or ‘Fourfold titre rise’ produces the following error message: “A confirmed case can only be reported
when laboratory method is culture, urinary antigen test or fourfold titre rise.”
Classification coded as ‘Confirmed’ AND laboratory method coded as ‘Fourfold titre rise’ (but not in
addition as ‘Urinary antigen test’ or ‘Culture’) AND pathogen not coded as ‘L. pneumophila serogroup 1’
produces the following error message: “Only L. pneumophila serogroup 1 can be reported as a
confirmed case when laboratory method is fourfold titre rise. Other pathogens must be reported as
probable.”
Classification not coded as ‘Confirmed’ AND laboratory method coded as ‘Culture’ produces the following
error message: “If the laboratory method is culture, a case is always classified as confirmed.”
Classification not coded as ‘Confirmed’ AND laboratory method coded as ‘Urinary antigen test’ produces
the following error message: “If the laboratory method is urinary antigen detection, a case is always
classified as confirmed.”
Classification coded as ‘Probable’ AND laboratory method not coded as ‘single high titre’,
‘immunofluorescence’, ‘nucleic acid’ or ‘fourfold titre rise’ produces the following error message: “A
Page 10 of 17
probable case can only be reported when laboratory method is single high titre, immunofluorescence,
nucleic acid or fourfold titre rise”.
Classification not coded as ‘Confirmed’ AND laboratory method coded as ‘Fourfold titre rise’ AND
pathogen coded as ‘L. pneumophila serogroup 1’ produces the following error message: “If the
laboratory method is fourfold titre rise and the pathogen is L. pneumophila serogroup 1, a case is
always classified as confirmed.”
Cases with unknown classification cannot be reported.
Clinical criteria met (mandatory)
Field: ClinicalCriteria
Coding:
Y = Yes
N = No
This variable answers the question of whether the patient’s clinical presentation included pneumonia, that is,
fulfils the clinical criterion of the EU case definition.
Validation: ‘No’ produces the following error message: “The diagnosis of Legionnaires' disease requires a
pneumonia”.
Disease-specific epidemiological variables
Imported (mandatory)
Field: Imported
Coding:
Y = Yes
N = No
UNK = Unknown
Has the patient been outside the reporting country during the incubation period of 2-10 days prior to date of
onset?
Countries/regions visited
Field: ProbableCountryOfInfection
Coding: List of countries
Country/ies the patient has been to during the incubation period of 2-10 days prior to date of onset. More than
one country can be indicated. For technical details on how to report repeatable variables, the user is referred to
the
TESSy transport protocols. Validation:
Reporting a case as imported, but not reporting any probable country of infection produces the
following remark: “Do you know in which country the imported case was infected?
ProbableCountryOfInfection is not reported.”
Reporting a case as not imported, but reporting a probable country of infection other than the country
of reporting produces the following warning: “ProbableCountryOfInfection should not be reported, if the
case is not imported.”
For domestic cases, it is recommended to leave this field blank. ‘Not applicable’ is no longer permitted.
Cluster
Field: Cluster
Coding:
Y = Yes
N = No
UNK = Unknown
Does the case form part of a domestic or international cluster?
Laboratory method (mandatory)
Field: LabMethod
Coding:
URIN = Urinary antigen test
Page 11 of 17
CULT = Culture
FOUR = Fourfold titre rise
SINGLE = Single high titre
NUC = Nucleic acid amplification, e.g. PCR
IMM = Direct immunofluorescence
Laboratory method(s) used to confirm the diagnosis. More than one method can be indicated. For technical
details on how to report repeatable variables, the user is referred to the
TESSy transport protocols .
Cases without any information on the laboratory method used for confirmation cannot be reported.
Pathogen (mandatory)
Field: Pathogen
Coding: SG1 = L. pneumophila serogroup 1
SG2 = L. pneumophila serogroup 2
SG3 = L. pneumophila serogroup 3
SG4 = L. pneumophila serogroup 4
SG5 = L. pneumophila serogroup 5
SG6 = L. pneumophila serogroup 6
SG7 = L. pneumophila serogroup 7
SG8 = L. pneumophila serogroup 8
SG9 = L. pneumophila serogroup 9
SG10 = L. pneumophila serogroup 10
SG11 = L. pneumophila serogroup 11
SG12 = L. pneumophila serogroup 12
SG13 = L. pneumophila serogroup 13
SG14 = L. pneumophila serogroup 14
SG15 = L. pneumophila serogroup 15
SG16 = L. pneumophila serogroup 16
SGMIX = L. pneumophila serogroup mixed
SGUNK = L. pneumophila serogroup unknown
NonSG1 = L. pneumophila non serogroup 1
ANISA = L. anisa
BOZ = L. bozemanii
BRU = L. brunensis
CIN = L. cincinnatiensis
DUM = L. dumoffii
FEE = L. feeleii
JOR = L. jordanis
LONG = L. longbeachae
MAC = L. macaechernii
MIC = L. Micdadei
SAINT = L. sainthelensi
WAD = L. wadsworthii
O = L. other species
UNK = L. species unknown
Legionella species and serogroup confirmed by at least one of the previously indicated laboratory methods.
Monoclonal subtype
Field: MonoclonalSubtype
Coding: ALLN = Allentown (serogroup 1)
ALLNFRAN = Allentown/France (serogroup 1)
Page 12 of 17
BELI = Bellingham (serogroup 1)
BENI = Benidorm (serogroup 1)
CAMB = Cambridge (serogroup 5)
CAMP = Camperdown (serogroup 1)
DALA = Dallas (serogroup 5)
FRAN = France (serogroup 1)
HEY = Heysham (serogroup 1)
KNOX = Knoxville (serogroup 1)
LA = Los Angeles (serogroup 4)
OLDA = OLDA (serogroup 1)
OXF = Oxford (serogroup 1)
OXFOLDA = Oxford/OLDA (serogroup 1)
PHIL = Philadelphia (serogroup 1)
PORT = Portland 4 (serogroup 4)
O = Other
UNK = Unknown
NA = Not applicable
Validation:
Reporting L. pneumophila serogroup 1 and any non-serogroup 1 monoclonal subtype produces the
following error message: “The value given for MonoclonalSubtype is not valid for serogroup 1.” The
same applies to L. pneumophila serogroups 4 and 5.
Reporting L. pneumophila serogroup 1 and coding the monoclonal subtype as Not applicable produces
the following error message: “MonoclonalSubtype cannot be not applicable when serogroup 1 is
selected.” The same applies to L. pneumophila serogroups 4 and 5.
Reporting a monoclonal subtype with any pathogen other than L. pneumophila serogroups 1, 4 and 5
produces the following error message: “MonoclonalSubtype is only applicable for serogroups 1, 4 and 5.
Please code MonoclonalSubtype as not applicable.”
Sequence type
Field: ResultSeqType
Coding: Numerical, 1-9999
Legionella pneumophila sequence type as obtained by using the internationally standardised seven-gene loci
sequence-based typing (SBT) scheme of the European Working Group for Legionella Infections (EWGLI).
Available at:
http://www.hpa-bioinformatics.org.uk/legionel a/legionella_sbt/php/sbt_homepage.php
Setting (mandatory)
Field: Setting
Coding: COMAS = Community (assumed)
COMDE = Community (definite)
NOS = Nosocomial (hospital)
HOTH = Healthcare other
TRAABR = Travel abroad
TRADOM = Domestic travel
O = Other
Unk = Unknown
Setting in which the case most likely acquired Legionnaires’ disease.
As this annual retrospective surveillance does not serve the purpose of immediate detection and control of
sources of Legionnaires’ disease posing a risk to public health, the criteria defining travel-associated cases do not
need to be as strict as in the day-to-day surveillance of travel-associated Legionnaires’ disease. All imported
cases should therefore be reported as associated with travel abroad (TRAABR), regardless of whether the case
stayed in commercial or privately owned accommodation. The same applies to cases associated with domestic
travel (TRADOM). The only exception to this rule should be imported cases probably infected in a hospital abroad
– they should be reported as nosocomial (NOS) as this is epidemiologically more relevant.
Page 13 of 17
Regardless of where they were most likely exposed to Legionella, cases in persons not living in the reporting
country should be notified to their countries of residence and reported to ELDSNet only by the latter to avoid
duplicate reporting.
Environmental investigation
Field: EnvironInvest
Coding: Y = Yes
N = No
UNK = Unknown
Answers the question whether any environmental investigation was carried out. A missing value will be
interpreted as ‘Unknown’.
Legionella found
Field: LegionellaFound
Coding: Y = Yes
N = No
UNK = Unknown
NA = Not applicable
If an environmental investigation was carried out, was Legionella found?
Validation:
Reporting an environmental investigation with LegionellaFound coded as not applicable produces the
following warning: “If an environmental investigation has been performed, LegionellaFound cannot be
reported as not applicable.”
Reporting no environmental investigation with LegionellaFound coded as Yes, No or Unknown produces
the following warning: “If no environmental investigation has been performed, LegionellaFound must be
reported as not applicable.”
Reporting that it was unknown if an environmental investigation was carried out, yet coding
LegionellaFound as Yes, No or Not applicable produces the following warning: “If is is not known if an
environmental investigation has been performed, LegionellaFound must also be reported as unknown.”
Matching isolates
Field: MatchingIsolates
Coding: Y = Yes
N = No
UNK = Unknown
NA = Not applicable
If Legionella was found, were the environmental and clinical isolates matching?
Validation:
Reporting a culture-confirmed case and positive findings of an environmental investigation, yet coding
the Matching isolates variable as Not applicable produces the following warning: “If laboratory method
is culture and Legionella was found (LegionellaFound = Y), matching isolates cannot be reported as not
applicable.”
Reporting a case not confirmed by culture, yet not coding the Matching isolates variable as Not
applicable produces the following warning: “Matching isolates should be reported as not applicable
when lab method is not culture.”
Reporting a case where no Legionella was found in the environmental investigation, yet not coding the
Matching isolates variable as Unknown or Not applicable produces the following warning: “Matching
isolates should be reported as unknown or not applicable when Legionella is not known to have been
found (LegionellaFound ≠ Y).
Page 14 of 17
Reporting no environmental investigation with the Matching isolates variable coded as Yes, No or
Unknown produces the following warning: “If no environmental investigation has been performed,
MatchingIsolates must be reported as not applicable.”
Positive sampling site
Field: SamplingSite
Coding: CTOW = Cooling tower
POOL = Whirlpool / Spa pool
WAT = Water system
WATCOLD = Cold water system
WATHOT = Hot water system
O = Other
Unk = Unknown
NA = Not applicable
Site(s) from which samples were taken that tested positive for Legionella. More than one site can be indicated.
For technical details on how to report repeatable variables, the user is referred to the
TESSy transport protocols. Validation:
Reporting an environmental investigation, yet coding the Sampling site variable as Not applicable
produces the following warning: ”If there was an environmental investigation done, the sampling site
cannot be reported as not applicable.”
Reporting no environmental investigation, yet not coding the Sampling site variable as Not applicable
produces the following warning: ”If there was no environmental investigation done, the sampling site
must be reported as not applicable.”
Reporting that it was unknown if an environmental investigation was carried out, yet not coding the
Sampling site variable as Unknown produces the following warning: ”If it is not known if an
environmental investigation was done, the sampling site must be reported as unknown.”
Reporting that Legionella was found in an environmental investigation, yet coding the Sampling site
variable as Not applicable produces the following warning: ”If Legionella was found, the sampling site
cannot be reported as not applicable.”
LEGIDENOM metadata
This record type provides age-specific population denominator data to calculate incidence rates.
It is
mandatory for countries where Legionnaires’ disease surveillance only covers regional
subsets of the population, that is, where a country’s data source settings do not confirm
national coverage. For countries with data source settings indicating national coverage of
Legionnaires’ disease surveillance, the reporting of LEGIDENOM is not required. Instead,
ECDC will retrieve country and age-specific population denominator data from the Statistical Office of
the European Union (Eurostat).
Common TESSy variables (all mandatory)
Record type
Field: RecordType
Coding: LEGIDENOM
The record type defines the structure and the format of the data reported. The record types are defined by ECDC
and are related to the subject. Only valid combinations of subject, record type and data source are accepted.
Record type version
Field: RecordTypeVersion
Coding: 1
The version of the record type defines the current structure of the data reported. If the dataset is changed, the
version changes to the next higher integer.
Page 15 of 17
Subject
Field: Subject
Coding: LEGIDENOM
Describes the subject of the data to be reported.
Data source
Field: DataSource
Coding: List of surveillance systems
The data source specifies the surveillance system from which the data originates and is generated and
revised/updated by the national contact point for surveillance in each Member State. The descriptions of the
surveillance systems submitted to TESSy should be kept up to date and will be used to assist with data
interpretation.
It is recommended to link the LEGIDENOM record type to the existing data source for LEGI reporting.
Reporting country
Field: ReportingCountry
Coding: International organization for standardization (ISO) 3166-1-alpha-2, (two-letter code)
This variable identifies the country reporting the case.
Date used for statistics
Field: DateUsedForStatistics
Coding: yyyy
Year of reporting.
Status
Field: Status
Coding: NEW/UPDATE
DELETE
The status is used for updating data; the default is New/Update. By choosing ‘Delete’, the selected record (or
batch of data) will be marked as inactive, but will remain in TESSy to reconstruct the data for a given date in the
past.
Population denominator data (all mandatory)
The following variables are age-specific aggregate numbers of the population under surveillance. They serve to
calculate incidence rates.
Denominator: Age 0-19
Field: Denominator00-19
Coding: NUMERICAL
Denominator: Age 20-29
Field: Denominator20-29
Coding: NUMERICAL
Denominator: Age 30-39
Field: Denominator30-39
Coding: NUMERICAL
Denominator: Age 40-49
Page 16 of 17
Field: Denominator40-49
Coding: NUMERICAL
Denominator: Age 50-59
Field: Denominator50-59
Coding: NUMERICAL
Denominator: Age 60-69
Field: Denominator60-69
Coding: NUMERICAL
Denominator: Age 70-79
Field: Denominator70-79
Coding: NUMERICAL
Denominator: Age 80+
Field: Denominator80+
Coding: NUMERICAL
Denominator: Total
Field: DenominatorTotal
Coding: NUMERICAL
Denominator: Age unknown
Field: DenominatorUnk
Coding: NUMERICAL
Page 17 of 17