# Checking data quality

HelicsWin.Net performs a selected number of automatic validation checks during data entry. These checks do not pick up all possible problems. You are strongly recommended to perform a further level of in-depth checking before creating a report, exporting or merging data. The HelicsWin.Net data quality check function performs these in-depth checks. The checks must be started manually.

The data quality check verifies the internal consistency of all information entered into your database. This verification helps you to identify any problems, in turn greatly reducing the chances of producing inaccurate or inappropriate data outputs, and helping to ensure functional export of your data. As with all such data operations, you are advised to check your final data and ensure that the data make sense.

When you perform a data quality check, HelicsWin.Net produces messages at three severity levels: Error, Warning and Success. A data quality check output is produced, with each message including details of the issue identified.

Table 23: Data quality check messages

Severity | Code | Description
Error | ERR | A fatal inconsistency has been identified in a record or across multiple records. The severity of the inconsistency is such that the data could be misreported, or there could be a failure of a merge, report or export operation. User action: You must locate and fix all such errors before proceeding with any merge, report or export operations.
Warnings | WARN | A significant inconsistency has been detected that indicates that data may be compromised in merge, report or export operations. User action: You must identify the inconsistency and then decide whether the issue identified might invalidate your data.
Success | SUCC | The data quality check found no issues with the record; the check was therefore deemed to be a success. User action: None.

More:

Some types of errors detected

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