Controlled Terminology have you confused? We got you.
When starting a new clinical study and preparing the data collection design, you may ask yourself: How important is Controlled Terminology (CT)? How do I prepare the data collection process to be CDISC compliant and avoid rework for submissions? We often receive questions such as these. Whether you are newer to clinical studies or a seasoned veteran, CT can often be an elusive and confusing topic. Having a better understanding of CT standards and requirements, as well as CT-related issues found in validation checks, can improve your submission data and processes.
P21 Validation Engine Improvements
The P21 Validation Engines are consistently updated and improved upon with insights from our Subject Matter Experts, consultations with regulatory agencies, and findings submitted by our users. Examples include:
AD1012 has been split into two rules: AD1012 and AD1012A. The former checks for custom variables and is a Warning; the later checks for standard variables and is an Error. These rules consider secondary variable names ending in *N or *C, for numeric or character equivalent, respectively.
AD0047 was producing problems for some variables but has already been fixed and patched for over a year.
Not Submitted Annotations
For any information that is on the CRF but not mapped to SDTM, annotate the page and/or field with "NOT SUBMITTED."
(Originally published on October 6, 2020. Last Updated on October 30, 2020)
Effective October 1st, 2020, China’s NMPA will accept CDISC submissions. To support this initiative, Pinnacle 21 has released a new Chinese-language validation engine, available now in both Enterprise and Community. This engine supports datasets with Chinese-encoded characters and displays rule messages and descriptions in Chinese translation.
Versions and Revisions
You need to annotate and submit only the unique forms from the final version of the CRF, provided that they cover all the collected data. Combine all unique pages, e.g., those for clinical data and central review data, into a single acrf.pdf. Here are some example scenarios:
ADaM data are required by the FDA and PMDA, and accepted by China’s NMPA. Agencies often begin reviews with ADaM data validation, which helps them understand the analyses performed and reproduce results.
In the regulatory review process, it's critical to have analysis data that comply with the CDISC ADaM standard. Both the FDA and PMDA require ADaM data, and as they begin reviews, they start with ADaM data validation. ADaM data help these agencies understand the analyses performed and reproduce the results for further validation.
In this webinar, Trevor Mankus covers the more commonly occurring validation rules and some potential reasons why they fired.
In August 2020, we released our new Pinnacle 21 validation engine “FDA (1907.2)” for preparing study data for FDA submissions. It includes the validation rules currently used by FDA’s DataFit, the agency’s implementation of Pinnacle 21 Enterprise.
The previous, outdated version of the validation rules is represented by our “FDA Legacy (1903.1)” engine. It will be available for the next few months until our next release. This window allows you to finalize your ongoing submission preparations.
Tables of Contents and Bookmarks
A table of contents with hyperlinks to bookmarked pages is seen in CDISC's sample aCRF (avaliable in the Define-XML v2.0 download). Both the Metadata Submission Guidelines (MSG) from CDISC and the PDF specifications from the FDA require aCRFs to have hyperlinks to bookmarked pages. The PDF specifications also require a table of contents.
* Required Field