The SD0005 check reports only duplicate records, but it does not provide a reference to original “baseline” records. Therefore it’s quite difficult to perform a diagnostic only with a validation report.
I would recommend to take the original data and sort it by USUBJID and AESEQ. Then look for reported values to ensure that no duplicate records are present.
Please let us know if the false-positive messages do really exist?
Some potential source for this issue could be your validation set-up process. E.g., if you included the same AE file twice, then the validator could consider them as two separate split datasets and combine records from two the same sources before a validation.
OK, I’ve run validation with adding AE two times. That resulted in the same validation report as you sent me. It includes AESEQ dups for all records.
Be careful when adding datasets for validation. When you re-runnig validation within the same session, be sure that you “Clear”-ed datasets used previously.
I just ran an SDTM validation for ver 3.1.2 and got a Duplicate AESEQ error. But this does not seem correct. I looked at the data and for this subject there are no duplicated AESEQ values.