# Using the main menu

Use the main menu to open the main data entry forms for the different data levels. These forms are arranged in hierarchical order, based on hospital-, ward-, and patient-level data.

CDI main menu | ICU main menu | PPS main menu

Table 4: Summary of main menu functions

Button | Actions(s)
Hospital definition | Enter the name and code of a new hospital in the system. You can enter the data for different hospitals (sites) in the same database, e.g. hospitals within hospital trusts or organizations. This also enables national/regional coordinating centres to enter different hospitals data centrally, into a single database. If more than one hospital has been entered, you select individual hospitals here, by double clicking on its name in the Hospitals list.
Ward definition | Define all ward/ICU ID codes (abbreviated names). Optionally and in addition, full ward names can be entered.
ICU definition
Hospital surveys | Enter data from the hospital questionnaire. These data include the hospital’s survey dates (or surveillance year), hospital size and type, and, for the PPS, a number of infection control structure and process indicators.
Hospital surveillance periods / year
Ward PPS data | PPS: Enter the date the PPS was performed and the ward specialty for each ward.
ICU surveillance year | ICU: Enter data that remain constant for the entire ICU surveillance year, e.g. ICU size and specialty.
Patient/CDI /Microbiological data | CDI: For the MINIMAL option: Enter aggregated nominator and denominator data. For the LIGHT option: Enter aggregated nominator and denominator data, and case-based data. For the ENHANCED option: Enter aggregated nominator and denominator data, case-based data, and C. difficile isolate data.
ICU surveillance period/indicators | ICU: Enter the start date and end date of the surveillance period. For the LIGHT option: Enter the denominator data (required). In ICU, optionally enter denominator data in STANDARD surveillance. In ICU, this level also contains the structure and process indicators for HAI prevention.
Patient/Antimicrobial use /HAI data | PPS: For the STANDARD option: Enter each patient’s demographic data and risk factors. For the LIGHT option: Enter demographic data for each patient with at least one HAI (or antimicrobial, in the case of PPS). For both options: Access the healthcare-associated infection form and/or antimicrobial use form from this patient form, through separate buttons.
Data quality check | Analyse the data and report any missing or impossible values, and missing records. These checks go beyond the automatic validation checks that take place when individual records are saved; for example, cross-checks between different data levels.
Reports | Create pre-formatted reports containing patient- or ward-based data related to HAIs and/or antimicrobial usage. This feature enables you to use off-the shelf reports or reports that you customise yourself. Currently only available for the PPS module.
Data export | Export data as (i) raw data (as stored in the HelicsWinNet.mdb access format database), with or without user or validation variables, or as (ii) CSV (comma separated text) files in ECDC’s TESSy CSV format (always without user variables). Export in TESSy CSV format is currently only available for the PPS module.
Data merge | Merge HelicsWin.Net databases; this is useful if you want to consolidate the data from different hospitals, or from different wards within one hospital, into a single database. This application can (i) analyse the data in the other database to ensure that they are consistent with the data being merged; and (ii) if necessary, add user defined prefixes to user IDs to prevent overlapping patient IDs from different hospitals or wards.
Settings | From this form you can: • Change your password; • Specify how HelicsWin.Net sorts lists that contain data values (for example, sorting antimicrobials alphabetically by ATC5 code or alphabetically by antimicrobial agent) • Translate labels on HelicsWin.Net forms This feature enables you to translate labels on data fields and controls, such as tabs and buttons. You can access the text definitions for all the labels on the forms and validation messages and translate them in any language. You can also rename user field labels so that a local or national extra data collection modules can be implemented. The system also checks problems in the translation files, such as an accidental deletion of labels, and automatically fixes inconsistencies; • Reset window sizes to their original values; • Define the level of detail of error logging (for debugging purposes).
Quit | Shut down the programme.

More:

Defining hospitals

HelicsWin.Net v2.2 Online User Guide v20160330
© European Centre for Disease Prevention and Control, 2016
Reproduction is authorised, provided the source is acknowledged