SDTM

Description

Technical support questions about SDTM standard and validation rules

October 27, 2021

Hi guys,

 

In the 2.2.0 version of Pinnacle, xml's with SDTMIG metadata can be found in  the directory <_220\components\config>. For the 3.2 version, we imported this data in SAS and consequently created a SAS dataset including all domains and their metadata.

 

We would also like to do this for SDTMIG 3.3. In the latest Pinnacle version (3.1.2), there is an xml file called 'SDTM-IG 3.3 (FDA)' in <configs\2010.1>. However, the CT codes are not included.

 

Read More
October 21, 2021

Hello,

I am now working on a study where subjects were randomized to use drug A or drug B.

Read More
October 20, 2021

There is not an example in SDTM IG 3.3 what exactly does LBSTREFC should be populated with apart from its label - Reference Result in Standard Format. We already have variables - LBSTRESC & LBSTRESN - Captures values in standard format, along with LBSTNRLO, LBSTNRHI, LBSTNRC - Reference Range values in standard formats. Does LBSTREFC value be copied from LBSTRESC ? If so, then What exactly is purpose of this 'new' expected variable?

Read More
October 20, 2021

I'm getting errors in SQAPMH.
SD0058: Variable appears in dataset, but is not in SDTM model
SD0057: SDTM Expected variable USUBJID not found

Class seems to be recognized as a RELATIONSHIP, but what validation rules are being applied ?
(Are the current validation rules the same as the general SUPPxx??)

We have Pinnacle 21 Community 3.1.2.
This errors are the same for both PMDA (1810.3) and FDA (2010.1) Engines.

Read More
September 7, 2021

We have Pinnacle 21 Community (currently version 3.1.2) installed on a Windows server.

How do we set up to ensure that MedDRA dictionary versions are available for all users without them having to individually install every version and what is the recommended process when a new dictionary version is available?

I have tried changing the Configs and Terminology folder location under Preferences to point to the folder containing the dictionaries but this has no effect.  

Read More
September 2, 2021

Hi, this is MinJi.

In large subjects study (e.g. phase 3), there are some cases in which blank rows in AE/MH/CM eCRF DB were collected.

In this case,  to remove validation findings, can the sponsor delete null MHTERM/AETERM/CMTRT data?

 

Thank you for your help!

 

Best regards,

MinJi

Read More
August 18, 2021

In the SDTM.EC, we have some records with ECTRT = PLACEBO, and ECDOSE = 0 and ECOCCUR = Y, the issue SD1247 was occurred. We are wondering for these records with ECTRT = PLACEBO and ECDOSE = 0, should we manually update ECOCCUR into N after unblinded? Or could we explain this issue?

Read More
July 29, 2021

Hi,

In PINNACLE21Enterprise, I know "P21 2010.1" Engine is useful to varidate PMDA check and FDA check simultaneously; however, in PINNACLE21 training in Japan, the trainer recommended not to use "P21 2010.1" for PMDA submission (i.e. P21E should be run with FDA Engine and PMDA Engine separately)  because some PMDA specific checks can't be fired.

Has it been resolved ?

Thanks.

Read More
July 7, 2021

Hi team,

We have successful enrollment of a participant in a trial under different ARMCD due to multiple protocol amendments. Subject was randomized first under Placebo and successfully completed protocol required procedures. Later study had become open-label and subject has been enrolled into Active drug ARM. As per FDA technical conformance guide, 

Read More
June 28, 2021

Hi,

I have some question about multiple enrollments and multiple screenings.

In 2014, PhUSE WG suggested to update the structure of DM to "One records per SUBJID". However, the FDA and CDISC did not adopt this recommendation and insist that the structure of DM should be maintained as "One records per USUBJID".
So, I want to know the reason why the DM data set must satisfy "One records per USUBJID". How will this help the review process?

 

Kind Regards,

Marnie

Read More
Subscribe to SDTM

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.