Can you provide some actual data example as i did in this post that can more clearly describe the records you have in error ?
Here are some example of actual data. Hope this helps. Subject identifier=XXXXXX AVISIT AVAL AVALC ANRLO ANRHI PARAMCD PARAM Baseline 2 54.36 >54.36 12.2 45.3 VITB9SI Folic acid (Vitamin B9) Subject identifier=YYYYYY AVISIT AVAL AVALC ANRLO ANRHI PARAMCD PARAM Screening 5 <10 45 375 PROLCTSI Prolactin (mIU/L) Baseline 1 5 <10 45 375 PROLCTSI Prolactin (mIU/L) Week 6 5 <10 45 375 PROLCTSI Prolactin (mIU/L) Week 8 5 <10 45 375 PROLCTSI Prolactin (mIU/L) Week 12 5 <10 45 375 PROLCTSI Prolactin (mIU/L)
Hi Pei Lee -
hope your doing well.
I agree with you special sign results should be converted to numeric results for report analysis purpose and AVAL and AVALC wonot match in this scenario. we have a similar results for HBVRNA, ANA titer etc…
Thanks,
Venkata
Hi Team,
Can you please confirm if we have a general rule to handle SDTM Lab values with < > symbols in ADaM (AVAL) so that we dodnot miss considering these values in the Lab table summaries ?
Dear ADaM support team,
We got the following error in our ADLB dataset. For a given value of Analysis Value Numeric (AVAL), all values of Analysis Value Character (AVALC) should be the same for a given PARAMCD |
|---|
The reason for us getting this kind of errors is because we impute undetectable lab test values as below.
if AVALC=‘> nnnn’ then AVAL=nnnn; if AVALC=‘< nnnn’ then AVAL=nnnn/2;
According to the CDISC ADaM IG Version 1.0 Page 27, there must be a one-to-one map between AVAL and AVALC NOT the same between AVAL and AVALC. Could you kindly consider changing the checking algorithm for AVAL & AVALC?
Many thanks in advance,
Pei Lee