As well as the different levels of requirement for each field, data quality issues can be organised by the level which they occur at.
1. File level
File level rejections are validation errors that highlight specific data quality issues which have caused the whole submission file to be rejected or issued a warning message. These checks are made on all the records submitted by the data sender. A rejection would be of the entire submission against the selected reporting period, requiring identified issue(s) to be rectified and a resubmission made. These can be found File-Level Rejects tab
Example: MSDREJ002 - Failed Content Check. Mother's Demographics Table is empty.
2. Table/group level
These compare records within or across multiple tables, leading to rejection of multiple records or a warning message being displayed. Certain records in different tables may be linked by certain keys (such as LocalPatientId). These are considered ‘groups’ and, to protect data integrity, where one record fails validation, any linked records within that ‘group’ will also fail validation. This can be used to check referential integrity between tables or for duplicated records within a table. Rejected records would not progress to post deadline processing. Records with warnings would progress, but data quality would not be as required. These can be found in the Individual table tabs of the TOS.
There are two types of group-level rejections; No valid group submitted and More than one group submitted. “No valid group submitted” errors occur either because records in a table are rejected due to the corresponding records from the parent table being rejected due to a validation error, or because there are no corresponding records submitted in the parent table.
“More than one group submitted” errors will be triggered if duplicate records (records with same values in key columns) are submitted. All duplicate records will be rejected with group-level rejection error.
Example: The MSD001 group will be rejected if there is no valid MSD002 group transmitted for this LOCAL PATIENT IDENTIFIER (EXTENDED (MOTHER)).
3. Record level
Record-level rejections are validation errors that highlight a data issue in a specific column which has caused an error with the whole record. These can be against a single data item or across multiple data items within a single record, leading to either the rejection of the record or a warning displayed. Rejected records would not progress to post deadline processing. Records with warnings would progress, but data quality would not be as required. These can also be found in the Individual table tabs of the TOS.
Example: If PERSON DEATH DATE (MOTHER) is before the PERSON BIRTH DATE (MOTHER) the record will be rejected.
Each data item within the data set specification may have any of the above types of validation.
Please see the validations and warnings in the MSDS v2.0.25 TOS to understand the submission requirements for each table. The “Validation Rules” columns outline the date restrictions, and corresponding messages are shown in the “Error/Warning Messages” column. A description of each table can be found in section 6 of the MSDS v2.0 User Guidance.