ADaM

Hi Team,

We are getting AD0018 : variable label mismatch between dataset and ADaM standard for AENDTM and ASTDTM.

The labels are defined as below currently.

VARIABLE       LABEL

AENDTM  : Analysis End Datetime

Is there a way to have AD0221 not fire on the variable ACAT1? We have a purpose for this variable in a BDS structure and the variable is not categorizing an AVAL like the other CAT variables. The rule for AD0221 says: Within a study, All *CATy values must be the same for each unique value of the variable it categorizes within a PARAMCD. [AVAL:AVALCATy], [AVALC:AVALCATy], [BASE:BASECATy], [BASEC:BASECATy], [CHG:CHGCATy], [PCHG:PCHGCATy].  A category may be the same across values.

Hi All,

I have a question about ADaM generation.

An attempt was made to create an ADaM using only SDTM. However, SDTM was generated without some derived variable and ADaM programming team requested the variable without any changes to the SDTM.

So, unfortunately,  we created another DB containing the derived variable. The format of DB is not SDTM.

In the end, ADaM will be generated using SDTM and seperated DB (including derived variable).

Recently one of our programmers cut and paste text from an external document to populate variables.

Here is an example.  I can see that those single quotes pasted in are odd.

Hi,  I have the variables A1HI and A1IND for a dataset ADLB which is CDISC compliant.

I get the pinnacle error AD0352, "None of A1LO, A1HI, A1LOC, or A1HIC variables is present, when A1IND is present" though I can see A1HI in the dataset.

Can you please help to resolve this.

Thank you

Hi all,

I have 2 datasets with the variable: PPFL (which has values Y or N), and the datasets are both "Occurence Data Structure". The datasets are ADAE and ADAEDEV. When I run the Pinnacle 21 validator on the transport files and define, only ADAEDEV  has the Pinnacle 21 message: "PPFL value is not Y or null", with severity = "Reject". ADAE does not have this message, not even as an error. 

Any idea why? Same exact values for PPFL, and the define identifies the datasets as both Occurence Data Structure.

Thanks!!

The AD0046 *DY = 0, issue  is firing when the *DY value has decimal places in it.  Is this a bug?  Or is there a reason why the *DY value should not have decimal places?   Some examples of my *DY value:  10.19028063, 3.59206023 and 6.53251198.

Thanks

SD1230 warning fired in  ADaM which have some missing values in AVAL and BASE. And AVAL and BASE were described as value level in define.xml.

SD1230 finding was appear as below in ADaM validation report (PMDA 1810.3 / Community Version: 3.1.1).

I have the following question,  each subject had multiple paramcd/param assessments at multiple visits,  actual visit window were assigned, when there were multiple visits in a visit window, we would have 2 different analyses, last date, or worst case.  I already had paramcd/param, avisitn/avisit, aval/avalc, basetype, dtype in the dataset, how to hold 2 different results, add new row ? add new column ?  what name can I use ? not parcat1 or avalcat1 or paramtyp. 

thanks

Hi Team,

As per the requirement of our analysis we have created the subperiods for period 2 like PxxSw, PxxSwSDT,  PxxSwSDM , PxxSwEDT and PxxSwETM in ADSL dataset as per ADaM IG 1.1 (Table 3.2.7).

Below are the variable names and Labels in the specification.

Variable Name                         Label