d David
on

 

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.

Here is what the validator report shows:

AESEQ, USUBJID1, EMTP-000006SD0005Duplicate AESEQAESEQ, USUBJID2, EMTP-000006SD0005Duplicate AESEQAESEQ, USUBJID3, EMTP-000006SD0005Duplicate AESEQAESEQ, USUBJID4, EMTP-000006SD0005Duplicate AESEQ

And here is the dataset values

USUBJID AESEQ
EMTP-000006 1
EMTP-000006 2
EMTP-000006 3
EMTP-000006 4
Is something not working correctly?

Thanks

Dave Borbas

Forums: SDTM

s Sergiy
on June 15, 2013

Hi David, 

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?

Regards,

Sergiy 

d David
on June 17, 2013

Hello Sergiy,

 

I think that these false positives may exist see below

STUDYIDDOMAINUSUBJIDAESEQAETERMEMTPAEEMTP-0000061GRADE 2 SYSTEMIC ALLERGIC REACTION EMTPAEEMTP-0000062DYSPNEA EMTPAEEMTP-0000063SWELLING OF TONGUE EMTPAEEMTP-0000064SWELLING OF FACE 

 

I get this error numerous times

I will send you the dataset and validation report so you can see

Thanks

Dave Borbas

d David
on June 18, 2013

Hello Sergiy,

 

Based on your email I thought it would be worth reviewing everything.

 

So I checked the xpt file and noted only 922 records – OK there

 

Then I re-ran validation with my current version (same as before) of OpenCDISC Validator. However this time I did not see the duplicate AESEQ error.

 

Good – not sure what happened here. We can close this issue if it should occur again I will let you know

 

Thank you very much,

s Sergiy
on June 18, 2013

David,

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.

Regards, 

Sergiy

 

s Sergiy
on June 18, 2013

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.

Regards,

Sergiy 

Want a demo?

Let’s Talk.

We're eager to share and ready to listen.

Cookie Policy

Pinnacle 21 uses cookies to make our site easier for you to use. By continuing to use this website, you agree to our use of cookies. For more info visit our Privacy Policy.