In previous iterations of Within the UKRDC, each time a data file failed fails to load , due to validation issues, data integrity issues, or systematic issues within the UKRDC, that file was is recorded as an individual error. If a renal unit sent sends a more up to date file for the same patient, this time passing validation and entering the UKRDC successfully, the original error would will remain in the system, and forever show up as an error to be resolved by the renal unit.
Within the UKRDC dashboard, we are less concerned with the total number of historic errors for a patient. What we really care about is if the most recent file for a patient received from a particular feed failed due to errors or not. If a patient is most recently receiving files rejected due to errors, this means their record may be incomplete. However, if a more recent file succeeds, and that file contains correct and up to date data, their record in the UKRDC is then complete and up to date, and no longer a concern.
For example, let’s take a made-up patient, Benson Dunwoody, whose record being sent to the UKRDC from a renal unit PARK01 via a UKRDC/RDA feed. One day a member of hospital staff mistakenly enters a medication start date as 01/09/0022 instead of 01/09/2022, and a new RDA file with this information is sent to the UKRDC. Our system rejects the file, identifying an issue with the apparent medication start date.
...