k Kirsten
on

 

Hi,

Got a SUPPAE with the QNAM/QLABEL = AETRTEM /TREATMENT EMERGENT FLAG but the P21 validation rule says 'No Treatment Emergent info for Adverse Event'.

Why does my validation report have hits on this rule?

 

br Kirsten

Forums: SDTM

s Sergiy
on July 2, 2018

Hi Kristen,

SD1141 check looks to all records in AE domain and tries to find their matching records in SUPPAE with the same USUBJID, QNAM='AETRTEM' and IDVARVAL=AESEQ.

So, there are several options what could go wrong:

  • For example, not all AE records have corresponding records in SUPPAE dataset.
  • You have unusual implementation of SUPPAE dataset by using other than AESEQ variable to linked records ( IDVAR != 'AESEQ') 
  • <something else>

Regards,

Sergiy 

 

 

 

j Jozef
on July 3, 2018

As an additional test to find out what might have gone wrong, you can transform the datasets to Dataset-XML format (see https://wiki.cdisc.org/display/PUB/CDISC+Dataset-XML+Resources) and then use the free open-source "Smart Dataset-XML Viewer" (https://sourceforge.net/projects/smart-sds-xml-viewer/files/). If your define.xml is set up correctly, and the SUPPAE records are set up correctly, and you use the option "bring SUPPQUAL data back to original dataset", the software will create the AETRTEM in the AE table view and populate it with the information from SUPPAE.

You can of course also program such a "bring back" in SAS (as you work for SAS ...).
For SUPPxx variables "bringing back" is always a good test - in IT we call this "roundtripping"...

p Pradeep
on August 14, 2018

Dear Sergiy,

I have all AE records have corresponding records in SUPPAE for AETRTEM and I have used AESEQ in IDVAR, this update it is resolving the issue in PMDA checks but it is hitting in FDA checks (SD1097).

 

Regards,

Pradeep

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.