PharmaSUG Single Day Event
University of North Carolina, Chapel Hill, NC
October 22-23, 2020
e-Submission, CDISC and New Technology – Together Towards Tomorrow
We are pleased to let you know that PharmaSUG’s NC Single-Day-Event (SDE) 2020 is ON SCHEDULE. With our 2020 annual conference having been cancelled, let’s get connected in this 1-day event in NC.
Following PharmaSUG’s tradition, the NC SDE 2020 committee is hard at work planning another fabulous event featuring a day-long oral presentations by renowned speakers in the industry. We have also added a pre-event training seminar on Thursday, October 22.
- Enjoy oral presentations by renowned speakers
- Learn new tips and techniques
- Share best practice with attendees from other companies
- Discuss issues with experts
- Connect with friends and colleagues
- Build relationship with new friends
Please contact our SDE Co-Chairs, Margaret Hung and Matt Becker, at This email address is being protected from spambots. You need JavaScript enabled to view it. if you have any questions, or are interested in volunteering.
Event registration is $95 if registered by October 9, 2020, and $110 after October 9, 2020. The registration fee includes a full breakfast, lunch and two refreshment breaks. Training seminar registration is $190 on or before October 9, 2020, and $240 if registered after October 9.
Cancellation policy – Refund minus a $25 admin fee is allowed if registration is cancelled by September 25. No refund after September 25, unless the event is cancelled by PharmaSUG or the conference venue; otherwise, refunds are allowed at PharmaSUG’s discretion.
Sponsored by:
 |
 | ||||
 |
 | ||||
Thursday, October 22, 2020 All-Day Pre-Conference Seminar
| Time | Presentation (click for abstract) | Presenter (click for bio) |
| 7:30 AM - 8:30 AM | Seminar Registration and Breakfast | |
| 8:30 AM - 4:30 PM | CDISC ADaM – Implementation by Example | Richann Watson, DataRich Consulting |
Friday, October 23, 2020 Single-Day Event
| Time | Presentation (click for abstract) | Presenter (click for bio) |
| 7:30 AM - 9:30 AM | Registration and Breakfast | |
| 8:30 AM - 4:30 PM | Conference Program (in progress) | |
| Common Pinnacle 21 Report Issues: Shall We Document or Fix? | Ajay Gupta, PPD | |
| Next Innovation in Pharma - CDISC Data and Machine Learning | Kevin Lee, Genpact | |
| A Codelist’s Journey From the CDISC Library to a Study Through Python | Mike Molter, PRA Health Sciences | |
| More Traceability: Clarity in ADaM Metadata and Beyond | Richann Watson, DataRich Consulting |
Sponsorship Opportunities
Participating as a sponsor is a great way to market your company's product and services. Download our sponsorship program (PDF, 156K) and application form (Word doc, 63K) for further details. For questions about our sponsorship program, please contact This email address is being protected from spambots. You need JavaScript enabled to view it..
Seminar and Presentation Abstracts
Common Pinnacle 21 Report Issues: Shall We Document or Fix?Ajay Gupta, PPD
Pinnacle 21, also previously known as OpenCDISC Validator, provides great compliance checks against CDISC outputs like SDTM, ADaM, SEND and Define.xml. This validation tool provides a report in Excel or CSV format which contains information as errors, warnings, and notices. At the initial stage of clinical programming when the data is not very clean, this report can sometimes be very large and tedious to review. If the programmer is fairly new to this report s/he might not be aware of some common issues and will have to fully depend on an experienced programmer to pave the road for them. Indirectly, this will add more review time in the budget and might distract the programmer from real issues which affect the data quality. In this presentation, I will discuss some common issues with the Pinnacle 21 report messages created from running against SDTM datasets and propose some solutions based on my experience. Also, I will discuss some scenarios when it is better to document the issue in reviewer’s guide than doing workaround programming. While the author totally agrees that there is no one fit for all solution, my intention is to provide programmers a direction which might help them to find the right solutions for their situation.
Next Innovation in Pharma - CDISC Data and Machine Learning
Kevin Lee, Genpact
The most popular buzz word nowadays in the technology world is “Machine Learning (ML).” Most economists and business experts foresee Machine Learning changing every aspect of our lives in the next 10 years through automating and optimizing processes. This is leading many organizations including drug companies to explore and implement Machine Learning on their own businesses.
The presentation will discuss how Machine Learning can lead the next innovation in pharma with CDISC data. The presentation will start with the introduction of most innovative companies and how they innovate and lead the industry using Machine Learning and data. Then, the presentation will show how pharma should learn from them to innovate using Machine Learning and CDISC data. The presentation will also introduce the basic concept of machine learning and the importance of data.
The presentation will show how CDISC data will be the perfect partner of Machine Learning for the next innovation in pharmaceutical industry. Finally, the presentation will discuss how biometric department can prepare the next innovation and lead this data-driven Machine Learning process in pharmaceutical industry.
A Codelist’s Journey From the CDISC Library to a Study Through Python
Mike Molter, PRA Health Sciences
The publication of the CDISC Library should be every programmer’s dream. The use of PDF-based Implementation Guidelines or even Excel files downloaded from the CDISC website always produced manual, non-automated hiccups to the process of standards implementation. The Library gets us one step closer to automation nirvana. In this presentation I will illustrate a small-scale proof-of-concept web application in which a study team member defines study controlled terminology subsets, not through tedious Excel operations such as copying and pasting, but rather through minimal checkbox selection of controlled terms presented to the user through a browser by an application that knows which codelists are associated with which CDISC variables. We’ll see how just a few lines of Python code can extract from the Library; how a few more can send contents of a codelist to an HTML form; and on the backend, how a few more can process the choices a user made. The purpose of this exercise is not to demonstrate a fully functioning production web application, but rather, to give the reader a sense of what is possible. Knowledge of basic Python objects such as lists and dictionaries is helpful, but not essential.
More Traceability: Clarity in ADaM Metadata and Beyond
Richann Watson, DataRich Consulting
One of the fundamental principles of ADaM is that datasets and associated metadata must include traceability to facilitate the understanding of the relationships between analysis results, ADaM datasets, and SDTM datasets. The existing ADaM documents contain isolated elements of traceability, such as including SDTM sequence numbers, creating new records to capture derived analysis values, and providing excerpts of define.xml documentation.
An ADaM sub-team is currently developing a Traceability Examples Document with the goal of bringing these separate elements of traceability together and demonstrate how they function in detailed and complete examples. The examples cover a wide variety of practical scenarios; some expand on content from other CDISC documents, while others are developed specifically for the Traceability Examples Document. As members of the Traceability Examples ADaM sub-team, we are including in this PharmaSUG paper a selection of examples to show how traceability can bring transparency and clarity to your analyses.
CDISC ADaM – Implementation by Example
Richann Watson, DataRich Consulting
This course will provide a high-level overview of some of basic ADaM concepts. It is assumed that the attendee will have a fundamental knowledge of the different ADaM structures and principles. The primary focus of the course is to illustrate the implementation of some of the concepts found in both the ADaM Implementation Guide (ADaM IG) and the ADaM Structure for Occurrence Data (OCCDS) documents. Items covered include setting up subject level analysis data set (ADSL) for common trial designs and walking through the process of creating a basic data structure (BDS) starting from a simple BDS and building on it to structure a data set that will support one or more analyses. Additionally, the course will demonstrate how to implement some variables that are only found in OCCDS, such as the standardized MedDRA query (SMQ) and customized query (CQ) variables.
Materials: Printed copy of the slides set up for note taking.
SAS Software Packages: N/A
Intended Audience: Individuals who have a knowledge of different ADaM structures and principles
Length and Format: Full-day lecture
Course Outline:
- ADaM Overview
- SDTM vs ADaM
- Fundamental Principles
- High-level overview of data structures
- ADSL
- Illustration of Common Trial Designs
- BDS
- Illustration of a simple BDS
- Build on simple structure by adding additional variables such as
- Analysis Visit Windowing Variables
- Descriptor and Indicator Variables
- Category and Criterion Variables
- OCCDS
- Illustration of a simple AE and CM data set
- Illustration of an OCCDS that does not have coding or a hierarchy
- Build on a simple AE data set by adding additional variables such as
- AEs of Special Interest Variables
- Occurrence Flag Variables
- ADSL
