ADaM

What’s New in Enterprise 3.4

May 17, 2018

With the latest Pinnacle 21 Enterprise 3.4 release, we continue to bring efficiencies to your data standardization and compliance efforts. This release features a number of new enhancements and compliance checks that you have been asking for. This release also marks the formal roll-out of our new customer-centric initiative and a dedicated Customer Success Team.

We recently hosted a webinar presenting the new features. You can watch the video, access the slides, review the Q&A, or read the summary below.


Webinar Video

How does Pinnacle 21 implement ADaM validation checks?

March 9, 2016

Have you ever wondered how Pinnacle 21 implements rules for ADaM validation? Below is a list of commonly asked questions.

  1. Does Pinnacle 21 implement the validation checks published by CDISC?

    Yes, Pinnacle 21 rules are an implementation of CDISC validation checks. In fact, P21's Michael DiGiantomasso and Sergiy Sirichenko are both active members of the CDISC ADaM Compliance subteam. Since 2011, the subteam produced 4 versions of CDISC validation checks, with Pinnacle 21 supporting the industry by releasing 7 updates to the open source rule implementations. This close collaboration between Pinnacle 21 developers, ADaM team core members, and representatives from across the industry is what makes it possible to continuously improve rule definitions and implementations.
  2. Why do the message text and rule counts differ?

    CDISC check definitions are designed to serve as requirements to machine implementation, "a programmable test, written such that an affirmative response represents a failure of the requirement. This text is intended for use as a requirement specification which could be implemented in a variety of programming languages". P21's rule messages and descriptions, on the other hand, are designed for the end user to help them quickly identify and fix the cause of validation issue.

CDISC ADaM Validation Webinar — Recap

June 25, 2015

When CDISC published Version 1.3 of its ADaM Validation Rules, a lot of you wondered what to make of it.

According to CDISC: “Some checks have been reworded for clarification … [and] 75 new checks have been added to cover rules not previously addressed. [These] additional checks cover the addition of checks for Adverse Events (ADAE) and the ADaM Basic Data Structure for Time-to-Event Analyses (BDS-TTE).”

To paint a clear picture of what all this means, and how the industry should respond, Pinnacle 21 hosted a recent webinar on this topic. The webinar — titled, “ADaM Validation Update from OpenCDISC” — provided an overview of these changes, and shared our experience of the most common issues in ADaM submission data observed across the industry.

ADaM Validation Update from OpenCDISC

May 29, 2015

On March 24, 2015, CDISC published Version 1.3 of its ADaM Validation Rules. The release's main goal was to add new business rules for ADAE (Adverse Events) and BDS-TTE (Time-to-Event Analysis), and, at the same time, clean up some of the checks from the prior release.

But these new rules still don’t provide a complete solution. ADaM validation requires the ability to supplement the ADaM rules with sponsor-specific controlled terminology and value level checks ... and the ability to test those checks with the same software used by the FDA.

Through this webinar, we’ll provide an overview of recent changes and share our experience of the most common issues in ADaM submission data observed across the industry. Our speaker will be Pinnacle 21’s Michael DiGiantomasso. Mike serves on the CDISC’s ADaM Validation sub-team and is a Data Fitness Analyst on the FDA JumpStart project.

For your convenience, we’ll be providing this webinar at two different times.

WEBINAR SESSION 1 WEBINAR SESSION 2
Date: Wed, Jun 3, 2015
Time: 9:00 am EDT
(15:00 CEST)
Length: 1 hour
Date: Thu, Jun 4, 2015
Time: 2:00 pm EDT
(11:00 am PDT)
Length: 1 hour
Register Register

In this webinar, we will cover:

  • Review of all ADaM validation rules and categories
  • Overview of datasets recognized by OpenCDISC
  • Adding sponsor-specific CT and VLM checks
  • Common ADaM issues in submission data
  • Rules for the upcoming release of ADaM IG v1.1

Best regards.
OpenCDISC Team

CDISC ADaM Validation Update

January 25, 2015

On March 24, 2015, CDISC published Version 1.3 of its ADaM Validation Rules.

So, what’s changed?

In the simplest terms: the release’s biggest enhancement is the ability to recognize and validate ADAE (Adverse Event Analysis) and BDS-TTE (Time-to-Event Analysis) datasets. CDISC has added 75 new rules in total, and, at the same time, cleaned up some of the checks from the prior release to ensure that their failure criteria is machine-testable.

So, what should concern you?

These published business rules conform to the definition of CDISC’s intention that each rule requirement be broken down into its constituent parts and should be machine-testable. For example, a simple rule which states “C BETWEEN A and B” will be stated as C >= A and C<=B. This normalized model works for business requirement capture … but it can make implementation, testing and human understanding more complicated than they need to be.

Beyond that, these newly enhanced ADaM validation rules still don’t provide a complete solution. Since ADaM IG v1.0, CDISC has been providing mere specifications documents. ADaM validation requires more than that. You need the ability to supplement the ADaM rules with sponsor-specific checks, especially for sponsor defined controlled terminology and value level metadata. And you need to be able to test those checks with the same software used by the FDA.