ADaM

Hi,

I received some ADaM datasets, and Pinnacle is throwing the AD0043 error in every dataset.  It turns out that the DTM variables were formatted as "IS8601DT."  I checked the TERMS attribute of the AD0043 rule, and I saw "E8601DT" is valid, which IS8601DT is an alias for.  Is this a false positive, and could the rule be extended to include aliases?

I goe this error message when i tried to validate ADaM datasets:

ID:              AD0053   

Message:    USUBJID value does not exist in the SDTM DM domain     

Description: Unique subject identifier not found in the SDTM Demographics domain. There must be traceability between ADaM and SDTM.

For the above error messsage, why it is generated? Or more general, how OpenCDISC check the traceability between ADaM and SDTM datasets?

Hi,

I am getting the label mismatch error for variable "TRTSEQP", for label='Planned Sequence of Treatments' and "TRTSEQPN" , label='Planned Sequence of Treatments (N)' for ADVS. These variables are created as per ADaM IG 1.0.  Could you please explain why I am getting these mismatch errors, am I missing on anything?

Thanks,

Snehal

Dear sir/madam,

I noticed in the ADaM 1.0.xml configuration file that validation rule AD0018 is not active for the ADAE domain .

Could you fix this by adding the rule in the upcoming version of the config files, cfr below?

Hi,

I noticed there were no P21 issues for non-ascii characters in ADaM datasets. Do you know if non-ascii characters are allowed for ADaM? There are issues that appear in P21 if non-ascii chars are present in SDTM datasets. I am wondering why none are added for ADaM.

Thanks.

one of the study, ADCM dataset has values other than "Y","N", null for TRTFL and TRTFLN but pinnacle21 2.2.0 is not flagging this issue, its working for other domains. 

please can you advice.

Hi,

Dear all,

We recently noticed that rule AD1012 doesn't fire as expected.
For example, no issue is reported when only the numeric (secondary) variable of following variable pairs is present in a BDS dataset:
BMIGR1(N), REGION1(N), TSEQPG1(N), and RACEGR1(N).

Hi there,

I have a question regarding validation of ADaM domains like ADMH, ADCM, ADAE. As per new ADaM_OCCDS_v1.0 released in Feb 2016, ADMH, ADCM, ADAE should come under "OCCDS" class instead of "BDS" class, but when I ran the latest community version of Pinnacle validator (2.2.0) using ADaM 1.0.xml config file,  ADMH and ADCM domains are getting validated under "BDS" class and ADAE under "ADAM other". Why is it so? when can I expect the updated config file for ADaM datasets?

Dear all,

I get error PCHG != (AVAL - BASE)/BASE * 100 for following values:

  AVAL  = 0.049473684200

  BASE  = 0.049484536100

  PCHG = -0.021929881200

In the report I get following details: PCHG, AVAL, BASE : -0.02192988, 0.04947368, 0.04948454.

Is it possible that the validator first rounds AVAL and BASE to 8 decimals before determining PCHG?

Why is this rounding done? It causes false errors in the report. 

Thanks for looking into this.

Jeroen