The following variables and labels reported as issues in P21 do not match the SDTM 3.2 IG:
PPSTRESC IG="Character Result/Finding in Standard Format" P21 Config=“Result or Finding in Standard Format”
PCSTRESC IG="Character Result/Finding in Standard Format" P21 Config="“Result or Finding in Standard Format”
When validating ADAM data package in P21E, we could specify the MEDDRA version. But in P21C, there is no place to specify MEDDRA version when validating ADAM data packages. Is there any reason why there is such different setting? Thank you very much.
For Pinnacle 21 community, we could only validate the SAS .xpt datasets and the define.xml. In the future, will Pinnacle 21 community add functionality to include data reviewer's guide, XLS stylesheet, SAP, tables (as reference files for define.xml ARM) in the validation package?
P21E study data packages, once it is created, we could not delete it but can only deactivate it. Is it possible that P21E provides us the functionality that we could delete studies or data packages that are no longer used? Or are there any reasons we could not delete them? For example, for cost traceability concern? Thank you.
Only "Configuration:", "Define.xml:", "Generated:", "CDISC SEND CT Version:" and "Validation Engine Version:" are printed on the sheet "Validation Summary" of Pinnacle21 Validator Report.
In this content, we do not know when the report was executed with which version of the validator, so please add the printed version of the executed validator.
In the blog "Introducing P21 Community 3.0" of May 8, 2019 it was mentioned that "an updated and more detailed CLI documentation will be published in the near future" (see attached screenshot).
When will this become available? The current documentation (P21 website + PharmaSUG paper) is quite limited and does not discuss all available CLI parameters.
Thanks for any update,
Jeroen Den Herder (SGS Life Sciences)
Hi Pinnacle 21 team,
Many programmers in our industry have problems with installation of external software in their working environment. Previously it was not an issue, because nothing was installed. I know it is not your problem, but having a portable version will solve this issue.
I may be wrong, but as I understand you are using Electron now. Electron-builder has a portable target for windows, which should make it easy to generate such package.
* Required Field