Creating a Patient Profile using CDISC SDTM Marc Desgrousilliers, Clinovo, Sunnyvale, CA Romain Miralles, Clinovo, Sunnyvale, CA

Similar documents
Easy CSR In-Text Table Automation, Oh My

Why organizations need MDR system to manage clinical metadata?

Preparing the Office of Scientific Investigations (OSI) Requests for Submissions to FDA

Pharmaceuticals, Health Care, and Life Sciences. An Approach to CDISC SDTM Implementation for Clinical Trials Data

Real Time Clinical Trial Oversight with SAS

An Alternate Way to Create the Standard SDTM Domains

How a Metadata Repository enables dynamism and automation in SDTM-like dataset generation

The Submission Data File System Automating the Creation of CDISC SDTM and ADaM Datasets

Cost-Benefit Analysis of Retrospective vs. Prospective Data Standardization

Lex Jansen Octagon Research Solutions, Inc.

PharmaSUG 2014 PO16. Category CDASH SDTM ADaM. Submission in standardized tabular form. Structure Flexible Rigid Flexible * No Yes Yes

Study Composer: a CRF design tool enabling the re-use of CDISC define.xml metadata

PharmaSUG Paper AD03

Customizing SAS Data Integration Studio to Generate CDISC Compliant SDTM 3.1 Domains

PhUSE Paper SD09. "Overnight" Conversion to SDTM Datasets Ready for SDTM Submission Niels Mathiesen, mathiesen & mathiesen, Basel, Switzerland

START CONVERTING FROM TEXT DATE/TIME VALUES

CDASH Standards and EDC CRF Library. Guang-liang Wang September 18, Q3 DCDISC Meeting

How to write ADaM specifications like a ninja.

CDISC SDTM and ADaM Real World Issues

The Wonderful World of Define.xml.. Practical Uses Today. Mark Wheeldon, CEO, Formedix DC User Group, Washington, 9 th December 2008

How to review a CRF - A statistical programmer perspective

SAS offers technology to facilitate working with CDISC standards : the metadata perspective.

PharmaSUG. companies. This paper. will cover how. processes, a fairly linear. before moving. be carried out. Lifecycle. established.

Examining Rescue Studies

Best Practices for E2E DB build process and Efficiency on CDASH to SDTM data Tao Yang, FMD K&L, Nanjing, China

Figure 1. Table shell

Automate Clinical Trial Data Issue Checking and Tracking

PharmaSUG Paper PO22

CDISC Variable Mapping and Control Terminology Implementation Made Easy

Using Skype to run SAS programs Romain Miralles, Genomic Health, Redwood city, CA

CDASH MODEL 1.0 AND CDASHIG 2.0. Kathleen Mellars Special Thanks to the CDASH Model and CDASHIG Teams

SDTM Attribute Checking Tool Ellen Xiao, Merck & Co., Inc., Rahway, NJ

Material covered in the Dec 2014 FDA Binding Guidances

PhUSE US Connect 2019

From ODM to SDTM: An End-to-End Approach Applied to Phase I Clinical Trials

PharmaSUG Paper PO10

Once the data warehouse is assembled, its customers will likely

Advantages of a real end-to-end approach with CDISC standards

One-PROC-Away: The Essence of an Analysis Database Russell W. Helms, Ph.D. Rho, Inc.

Harmonizing CDISC Data Standards across Companies: A Practical Overview with Examples

Data Science Services Dirk Engfer Page 1 of 5

SDTM Automation with Standard CRF Pages Taylor Markway, SCRI Development Innovations, Carrboro, NC

esubmission - Are you really Compliant?

Module I: Clinical Trials a Practical Guide to Design, Analysis, and Reporting 1. Fundamentals of Trial Design

Planning to Pool SDTM by Creating and Maintaining a Sponsor-Specific Controlled Terminology Database

Clinical Metadata Metadata management with a CDISC mindset

Lex Jansen Octagon Research Solutions, Inc.

Automation of makefile For Use in Clinical Development Nalin Tikoo, BioMarin Pharmaceutical Inc., Novato, CA

esource Initiative ISSUES RELATED TO NON-CRF DATA PRACTICES

Standards Driven Innovation

SAS Drug Development Program Portability

Managing your metadata efficiently - a structured way to organise and frontload your analysis and submission data

It s All About Getting the Source and Codelist Implementation Right for ADaM Define.xml v2.0

The Implementation of Display Auto-Generation with Analysis Results Metadata Driven Method

Tips on Creating a Strategy for a CDISC Submission Rajkumar Sharma, Nektar Therapeutics, San Francisco, CA

ODM The Operational Efficiency Model: Using ODM to Deliver Proven Cost and Time Savings in Study Set-up

Paper DS07 PhUSE 2017 CDISC Transport Standards - A Glance. Giri Balasubramanian, PRA Health Sciences Edwin Ponraj Thangarajan, PRA Health Sciences

OpenCDISC Validator 1.4 What s New?

PharmaSUG China Mina Chen, Roche (China) Holding Ltd.

Global Checklist to QC SDTM Lab Data Murali Marneni, PPD, LLC, Morrisville, NC Sekhar Badam, PPD, LLC, Morrisville, NC

A SAS and Java Application for Reporting Clinical Trial Data. Kevin Kane MSc Infoworks (Data Handling) Limited

SAS Clinical Data Integration 2.4

LST in Comparison Sanket Kale, Parexel International Inc., Durham, NC Sajin Johnny, Parexel International Inc., Durham, NC

Adobe LiveCycle ES and the data-capture experience

Automated Creation of Submission-Ready Artifacts Silas McKee, Accenture, Pennsylvania, USA Lourdes Devenney, Accenture, Pennsylvania, USA

SAS Clinical Data Integration 2.6

FDA XML Data Format Requirements Specification

The Benefits of Traceability Beyond Just From SDTM to ADaM in CDISC Standards Maggie Ci Jiang, Teva Pharmaceuticals, Great Valley, PA

Traceability Look for the source of your analysis results

SAS CLINICAL SYLLABUS. DURATION: - 60 Hours

Doctor's Prescription to Re-engineer Process of Pinnacle 21 Community Version Friendly ADaM Development

An Efficient Solution to Efficacy ADaM Design and Implementation

Organizing Deliverables for Clinical Trials The Concept of Analyses and its Implementation in EXACT

PharmaSUG Paper SP09

A Taste of SDTM in Real Time

Design of Case Report Forms. Case Report Form. Purpose. ..CRF Official clinical data-recording document or tool used in a clinical study

Legacy to SDTM Conversion Workshop: Tools and Techniques

SDD Unleashed - Extending the Capabilities of SAS Drug Development

Submission-Ready Define.xml Files Using SAS Clinical Data Integration Melissa R. Martinez, SAS Institute, Cary, NC USA

Making a List, Checking it Twice (Part 1): Techniques for Specifying and Validating Analysis Datasets

An Efficient Tool for Clinical Data Check

SAS Clinical Data Integration Server 2.1

Improving Metadata Compliance and Assessing Quality Metrics with a Standards Library

SIMPLIFY AND STREAMLINE USING PYTHON

SAS Training BASE SAS CONCEPTS BASE SAS:

Advanced Visualization using TIBCO Spotfire and SAS

CDISC Standards and the Semantic Web

Developing Graphical Standards: A Collaborative, Cross-Functional Approach Mayur Uttarwar, Seattle Genetics, Inc., Bothell, WA

CDISC Standards End-to-End: Enabling QbD in Data Management Sam Hume

Developer Case Study. BlackBerry Streamlines IT Change Request Approval Process. Industry Healthcare

SAS Application to Automate a Comprehensive Review of DEFINE and All of its Components

ABSTRACT INTRODUCTION WHERE TO START? 1. DATA CHECK FOR CONSISTENCIES

PhUSE Giuseppe Di Monaco, UCB BioSciences GmbH, Monheim, Germany

Applying ADaM Principles in Developing a Response Analysis Dataset

When Powerful SAS Meets PowerShell TM

Data Standardisation, Clinical Data Warehouse and SAS Standard Programs

Reviewers Guide on Clinical Trials

Automation of SDTM Programming in Oncology Disease Response Domain Yiwen Wang, Yu Cheng, Ju Chen Eli Lilly and Company, China

An Introduction to Analysis (and Repository) Databases (ARDs)

Creating Define-XML v2 with the SAS Clinical Standards Toolkit 1.6 Lex Jansen, SAS

Transcription:

Creating a Patient Profile using CDISC SDTM Marc Desgrousilliers, Clinovo, Sunnyvale, CA Romain Miralles, Clinovo, Sunnyvale, CA ABSTRACT CDISC SDTM data is the standard format requested by the FDA for clinical trial data submission. CDISC SDTM is the most complete and recognized standard available for clinical data that facilitates FDA submission. In this presentation, we will demonstrate how to leverage the SAS technology to create a detailed patient profile for a new study with no additional programming, once the data has been mapped to CDISC SDTM. Code components created to manipulate data in a standard format can be re-used to create standard reports for another study. In our prototype, we show how to build a customized patient profile reporting system from CDISC SDTM data using a Unix Server. A shell script parses the sponsor s requests, which include the study id, the patient list, SDTM domains, paths for log file and output, the output filename and the format for output. This script calls a SAS program that dynamically generates another SAS program, that is in turn automatically called to create the custom patient profile without requiring manual programming. The output is controlled by ODS, and both PDF and XML Excel formats are supported. This presentation will be very helpful for SAS programmers interested in: Creating highly customized reports without requiring programming Learning new SAS programming skills Using CDISC SDTM as a data middle-tier to improve core re-usability Understanding the structure of a patient profile built around the SDTM model Promoting CDISC benefits within their organization. INTRODUCTION Bio-pharmaceuticals are conducting clinical trials to develop new drugs and medical devices. A trial can cost hundreds of millions of dollars and can last five to ten years. In this high cost and high risk environment, companies are rewarded with huge financial when they bring new products to market. The Biotech industry has introduced a number of innovations to speed up clinical trials. One of them is the use of Electronic Data Capture system (EDC) to collect clinical data. Not only EDC speeds up clinical trials, it also improves the communication between sponsors, sites and patients. The next wave of innovation involves developing and creating modular and reusable tools. With the proliferation of EDC systems, it is not uncommon that multiple systems are used in the same department to manage individual studies. Because of the lack of standardization, each EDC system requires its own technology to organize, collect and store data, making it impossible to share data and tools between similar studies/trials. Data managers develop edit checks, reports and listings to check data consistency and to ensure high quality. Because the database types and structure are different for each study, companies spend a lot of time and money implementing the same type of tools for different systems. Listings and reports programmed for one study are usually not reusable for another study without additional programming. This paper presents a patient profile program developed for one of the top three biotechnology companies that wanted a program that could automatically generate the patient profile for any subject in any trial. This program uses SDTM tables to generate a patient profile for any subject, in any study, without requiring additional programming. 1

CDISC SDTM Study Data Tabulation Model (SDTM) defines a standard structure for human clinical trial data tabulations. It provides a standardized framework for describing the information collected during clinical trials. Variable names and attributes standardization allows for reusable tools and data across multiple trials. STDM benefits the industry by providing more efficient data transfer/sharing, resulting in faster time to market. SDTM generation is the process of transforming collected data to standardized format. Each clinical trial is unique and collected data do not have the same structure. STDM generation eases the process of generating a standardized database. In the paper An excel framework to convert clinical data to CDISC SDTM leveraging SAS technologies, Ale Gicqueau introduced a tool that maps any clinical database to CDISC SDTM. All mapping definitions and rules written in Excel are dynamically converted into a SAS program that performs the SDTM transformation and validation with minimum programming through a series of SAS macros. Using these standardization techniques, it becomes easy to develop reusable tools, such as patient profiles, that can be used with any clinical trial. PATIENT PROFILE Patient profiles are individualized displays of patient data. They offer an opportunity to have a complete picture of the subject s status and to easily identify issues in the database. They are used to track unusual values and relationships within patient data. The FDA does not require that the patient profile be generated and submitted since they can use PPD patient profiles to review the data. However, patient profiles are still useful and can be used as reference by different clinical departments, including biostatistics, data management, safety, clinical operations, and medical writing. They complement the edit checks and listings for data validation and cleaning. Patient profiles offer a great alternative to cross-edit checks, which are sometimes too difficult or too costly to be programmed. Patient profiles are used to make patient safety decisions, help medical writers with patient narratives, and in data review meetings. There are many approaches for generating patient profiles. A lot of them involve a lengthy programming effort. With this program, patient profiles can be generated with no additional programming once the data have been mapped to CDISC SDTM. REQUIREMENTS This program was developed to help clinical teams with their clinical trials. They wanted a program that could automatically generate the patient profile for any subject in any trial without additional programming. It had to use the SDTM tables created by the CDISC mapper. They had some additional requirements: The program should identify the new and updated data since the previous program run. It should allow users to create the patient profile for a specific subject, a set of subjects, or all the subjects. Users should be able to select the domains to display. PROGRAM Patient profiles are created using a shell script and two SAS programs. Users requests are entered in a command line interpreter using different parameters, described in the next paragraph. A shell script reads the command line and parses the parameters passed by the user. This shell script then calls a SAS program passing the command line parameters to the SAS program. Next, the SAS program uses the parameters to dynamically generate a new SAS program that will create the patient profile output, that is controlled by ODS. 2

Figure 1. Program diagram. Patient profiles are created using a shell script to parse a command line. USING THE PATIENT PROFILE Users produce custom patient profiles using a command line. They can use multiple command parameters to customize the output. Some parameters are required for the program to run, while others are optional and allow users to choose the output they want. Required parameter -t ( trial ): Identifies which study to run the patient profile for. Cp_pp t dyonisos This command line is the minimum needed to create the patient profile. It will create the patient profile for all the subjects enrolled in the study named Dyonisos, generating a pdf file named _pp_auto. Users can also select several optional parameters to create a specific report. Optional parameters -r ( report ): Controls the report name 3

Cp_pp t dyonisos r patient_profile_dyonisos This parameter will set the name of the patient profile output file to patient_profile_dyonisos. It also sets the output name in the footer. -d ( domain ): This option allows for selection of any single panel or combination of specified panels. Examples: Cp_pp t dyonisos r patient_profile_dyonisos d mh Cp_pp t dyonisos r patient_profile_dyonisos d "aeex aecm mh" By default, all panels are output in each patient profile -f ( format ): This option allows selection of Microsoft Excel format for the output. Cp_pp t dyonisos r patient_profile_dyonisos f xls By default, the PDF format is automatically selected. -I ( log ): Allows for specification of a directory where the SAS log file will be stored. Cp_pp t dyonisos r patient_profile_dyonisos I /onco/dyonisos/profile/log The specified directory for the SAS log must exist otherwise the default directory will be used. -o ( output ): This option identifies the directory where the patient profile output will be directed to. Cp_pp t dyonisos r patient_profile_dyonisos o /onco/dyonisos/output If the output directory is not specified, the report will appear in the current directory. 4

-p ( panel ): This option allows for selecting a specific subject or set of subjects. Cp_pp t dyonisos r patient_profile_dyonisos p 001004 Cp_pp t dyonisos r patient_profile_dyonisos p "001004 001006" Cp_pp t dyonisos r patient_profile_dyonisos p biostat/pma/selected.csv An external file with a list of subjects can be used with the program. -s ( split ): Creates a separate output for each study subject. Cp_pp t dyonisos r patient_profile_dyonisos sq CONCLUSION This program is a good example of innovation developed to create modular and reusable tools. It generates patient profiles for any subject in any trial as long as the data have been mapped to CDISC SDTM. Highly customized reports are created by simply using a command line, without requiring programming time and cost. CDISC SDTM is used as a data middle tier. It improves code re-usability as there is no need to develop multiple versions of the same program for different studies. SAS programs using SDTM become easy to maintain, validate, and update. Many generic reports can be created using SDTM and implemented quickly for multiple studies. REFERENCES Framework to convert clinical data to CDISC SDTM leveraging SAS technologies, Ale Gicqueau, WUSS 2010. ACKNOWLEDGMENTS We would like to thank Ale Gicqueau for his help in developing this application, as well as the users for their valuable feedbacks. CONTACT INFORMATION Your comments and questions are valued and encouraged. Contact the authors at: Marc Desgrousilliers Clinovo 1208 E. Arques Avenue, suite 114 Sunnyvale, CA 94085 E-mail : marc@clinovo.com Web: http://www.clinovo.com Work Phone: +1 800 987 6007 Romain Miralles Clinovo 1208 E. Arques Avenue, suite 114 Sunnyvale, CA 94085 E-mail : mrom34@gmail.com Web: http://www.clinovo.com SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. indicates USA registration. Other brand and product names are trademarks of their respective companies. 5