Skip to main content

What's New in P21E 6.3.0?

Introducing bi-directional source metadata to SDTM mapping, form specs, spec extensions and more in this iteration of P21 Enterprise

Wendy Young avatar
Written by Wendy Young
Updated over 2 weeks ago

P21E 6.3.0 introduces bi-directional source metadata to SDTM mapping, form specs, spec extensions and other improvements to streamline workflows in P21 Enterprise's foundational and advanced tier Data Exchange and Metadata Repository modules. Check out what a difference 16 New Features, 13 Improvements, 9 Refinements, and 23 Bug Fixes across all P21E modules will make for your team.

To read the complete release notes for P21E 6.3.0, download the file attachment at the bottom of this article. To view the most noticeable changes that impact your user experience, skip the download and check out the Release Highlights below.


Pinnacle 21 introduces bi-directional SDTM mapping, Form specs, and Spec extensions in P21E v6.3.0.

Check out the latest additions and improvements to P21E's advanced modules:

πŸ—ΊοΈ Bi-directional Source Metadata Mapping

Maintaining clear, auditable documentation and traceability from source data to final SDTM variables and ensuring every mapping decision is justified for regulatory compliance is critical. The average study, now comprised of seven different data sources, contains increasingly varied and complex data, and compliance with CDISC SDTM standards is non-negotiable for regulatory submissions to the FDA and PMDA.

So, how do we tackle complexity in mapping? Traditionally done via spreadsheets, mapping SDTM specs has been a slow and error-prone process that delays analysis and submission. Now there’s a better way, built on the principle of β€œdefine once and reuse again and again.”

Ditch the spreadsheets. Create and manage your SDTM mapping specs in a collaborative, purpose-built workspace.

πŸ“ Introducing Form Specs

P21E allows users to create Form Specs at the global or study level. This allows users to reference global Form Specs during the study-level form spec creation process to ensure specs adhere to CDISC Implementation Guidelines or their company specifications.

We have introduced a new Data Package Type named "Form," enabling you to create and build Study-specific Form Specifications from the Metadata > Forms menu.

Regardless of whether a Form Spec is created by extending or by importing a file, P21E provides users the ability to update and add to new Form Specs quickly and easily. Right-clicking in an editable cell provides you with several options to make specific changes manually.

Use the in-cell wizard to grab elements from existing Standard and Study level forms to jumpstart populating Form Specs, add or remove rows, and track and compare edits, deviations, and versions.

And just like the P21E Spec Chat feature, colleagues can chat in specific cells, fostering transparent decision-making and documenting decisions for easy reference.

🎨 Spec Extensions for Complex Study Designs

Using spec extensions, especially in the context of CDISC standards like SDTM, offers significant advantages in clinical research and regulatory submissions when it comes to handling unique data and study designs. Clinical studies can be highly diverse, especially with evolving scientific needs and complex study designs. When standard CDISC domains don't fully capture specific data points or study elements, extensions allow for the inclusion of these unique elements.

P21E’s Spec Extension features ensure novel data is organized and presented in a consistent, standardized way, minimizing ambiguity for regulatory reviewers and reducing the potential for misinterpretation.

By building and maintaining Spec Extensions in P21E, you’ll preserve a clear, automated audit trail. Well-designed extensions, paired with robust documentation, contribute to traceability, ensuring a clear link between collected data, transformations, and final analysis results.

πŸ“ Note: Detailed content for Source Metadata Mapping, Form Specs, and Spec Extensions is only available for customers on P21E v6.1.0 and later. Please contact your Customer Success Manager to learn more about these features.


πŸ”¦ Release Highlights

Foundational P21E

πŸ”§ Configure

  • You now can configure BIMO Data Packages to use Define-XML 2.0 or 2.1.

🎨 Define/Spec Designer

  • The Define/Specification Designers now preserve column preferences when making edits. In addition, when you filter columns on a spec, your filter settings are preserved so that whenever you view the spec again, you do not have to reapply them each time.

  • The "Add a New Define" modal has updated language to help users select the best choice.

  • The columns Assigned Value and Developer Notes have a "Spec" label in the column drop down to identify these as columns for additional context that will not be captured in the define.xml. Also, for Spec and MDR functionality, the columns Assigned Value, Source Variables and Developer Notes have a "Spec" label in the column drop down to identify these as columns for additional context that will not be captured in the define.xml.

  • Spec Extension columns will be labeled with Company label.

🌐 General

  • The order of the Metadata submenu pages has been updated.

πŸ“‹ Metadata

  • When viewing a standard, you can click a link to view the Model Standard and Recommended CT.

  • For BIMO Standards, a Prototype column is included in the Datasets tab.

  • The Base Standard, Standard and CT fields show version and creation date of that Standard and CT for Standards, Terminologies, Data Packages, and Specifications.

πŸ“Š Analytics

  • The Standards Adoption page displays a widget with Project, Study, and Data Package totals.


P21E - Data Exchange

🌐 Miscellaneous

  • P21E's REST API now allows all users (as opposed to only those with the Standard Designer role) to export content which has CDISC as the Publisher.

  • Data Exchange supports ZIP uploads containing both validatable and non-validatable files (e.g., images, .dat). Non-validatable files are passed through automatically, with their status shown in the Validation Report.

πŸ”§ Configure

  • When you create a Data Package and select the "External Vendor" Data Package Type, the Vendor field appears blank.

βœ… Validation

  • When you navigate to the External Vendor Validation Overview page, the Issues and Progress charts are now side by side.

βœ… Issue Management

  • On both Project and Study level issue Management pages, the CT column populates for External Vendor Data Packages. Also, for all records, the CT Column now displays the Name along with the Version configured.

🎨 Spec Designer

  • The Variables tab of a non-CDISC specification now shows a Target Variable column.

  • Pulling SEND or SDTM content into an ADaM spec requires you to populate a value in the "Add to" field. For example, this allows you to grab content from SDTM domain VS and add it to ADaM dataset ADVS.


P21E - Metadata Repository

πŸ” Administer

  • In Settings, on the new Specs tab, Admins can create and configure extended columns for use in SDTM specifications.

🌐 Miscellaneous

  • The P21E RestAPI now supports the retrieval of Form Spec metadata found within P21E.


πŸ“₯ Download Release Notes

Did this answer your question?