ADMH, ADCM are classified as "BDS" and ADAE as "ADAM other" instead of "OCCDS" class

https://www.pinnacle21.com/forum/dd0055

Hi Shehal, 

I agrre with you. However, see the following discussion: https://www.pinnacle21.com/forum/dd0055

Regards, 

Sergiy

For validation we are…

For validation we are following official ADaM rules published by CDISC team. There is no formal business rules for OCCDS. Therefore, there is no actual diffrence between ADaM OTHER and OCCDS in terms of validation itself.  

Thanks Sergiy..

Thanks Sergiy for your response, our understanding from above response/disussion is that ADCM, ADMH would be classified under BDS until CDSIC publishes new formal business rules for this class (OCCDS). please confirm..

According to ADaM, BDS…

According to ADaM, BDS datasets must include PARAM/PARAMCD/AVAL variables. This is not the case for common implementations of ADCM, ADMH datasets.

Thanks for the response...but

But, 

still it is not clear to me that why the config file is treating ADCM, ADMH and ADDV as BDS datasets rather than ADaM OTHER, and why it does not recognise ADRACE at all. Please see the attached image of the summary report

Due to ASTDT variable

Hi Snehal, 

I assume that it's due to the use of ASTDT variable in your ADCM dataset. In this case your complain is perfectly valid. Current definition of BDS structure in P21 Validator includes a presence of ASTDT and ASTDTM variables. We are discussing removing these variables from our definition of BDS structure.

Meanwhile, you can manually modify P21C specs by removing highlighted text from validation configuration files. For example, there is a file "ADaM 1.0.xml" in "...\components\config" folder. Open it by any plain text editor and find the following definition of BDS structure on row 2369:

<val:Prototype ItemGroupOID="IG.BDS" KeyVariables="PARAMCD,PARAM,AVAL,AVALC,ADT,ASTDT,ASTDTM,CNSR,CNSDTDSC,EVNTDESC"/> 

Remove highlighted text, save, restart Validator.

Regards, 

Sergiy

Thank you!!

Hi Sergiy,

Thank you for your response, that answers my question. We look forward to an updated configuration file.   

Regards,

Snehal

I tried the solution suggested but not working

Hi Sergiy,

I tried manually removing the ASTDT, ASTDTM from key variables in the ADaM config file but it didn't solve the issue, ADCM, ADMH are getting "unrecognized".  Please refer the above image for the report.

Thanks,

Snehal

I wanted to follow-up on this

Hi Sergiy,

We tried manually editing the ADaM config file by adding configuration for some of the domains (e.g ADCM, ADMH), we edited the current prototyping options and added CM and MH specific variables, then mapped them to "other" custom built configuration/validation rules and it worked fine, we could get these domains classified as "OTHER". Do you have any alternative suggestion to this approach?,

Follow-up question ADCM, ADMH as Occurrence data structure

We have developed our ADCM, ADMH as OCCDS; as per the ADaM IG 1.1 (and ADaM_OCCDS_v1.0). When running through the validator (v2.2.0) we get errors and as I read other posts in this thread I just want you to confirm;

Do we have to update the config file to not treat these datasets as BDS? If yes, can you please guide me exact what to update?

Can we expect an update in the config file for OCCDS datasets in a coming release of Pinnacle validator? I have understood the CDISC team has not yet released any formal business rules for OCCDS.

regards Hanna

CDISC ADaM team has not yet published rules for ADaM 1.1

Hi Hanna, 

The CDISC ADaM team has not yet published rules for ADaM 1.1, but they are working on getting it done by the end of Q2. Once the rules are published, Pinnacle 21 plans to make the config available within 3 month. So end of September is the current estimate, assuming CDISC stays on schedule.

Kind Regards, 

Sergiy

can we expect issue to be fixed in next release (by sep end)

Hi Sergiy,

Assuming CDSIC stays on schedule, can we expect the issues with ADRACE (getting unrecognized), and ADCM/ ADMH /ADDV/ ADMH (OCCDS datasets getting validated as BDS) to be fixed by September end??

Looking forward to your reply.

Thanks,
Snehal

ADaM 1.1.xml file availability

So I've been monitoring the releases for Pinnacle 21 community.. will there be a ADaM.1.1 configuration release?