EFFECTIVE AND OPERATIONAL USE OF CDISC STANDARDS & STUDY METADATA THROUGH SAS LIFE SCIENCE ANALYTICS FRAMEWORK

Similar documents
SDTM-ETL 3.1 New Features

PharmaSUG 2015 Paper SS10-SAS

SDTM-ETL TM. The user-friendly ODM SDTM Mapping software package. Transforming operational clinical data into SDTM datasets is not an easy process.

CDISC Roadmap Outline: Further development and convergence of SDTM, ODM & Co

MOVING THE CLINICAL ANALYTICAL ENVIRONMENT INTO THE CLOUD

Practical application of SAS Clinical Data Integration Server for conversion to SDTM data

Managing Custom Data Standards in SAS Clinical Data Integration

UTILIZING CDISC STANDARDS TO DRIVE EFFICIENCIES WITH OPENCLINICA Mark Wheeldon CEO, Formedix Boston June 21, 2013

Meta-programming in SAS Clinical Data Integration

«How we did it» Implementing CDISC LAB, ODM and SDTM in a Clinical Data Capture and Management System:

Rationale and vision for E2E data standards: the need for a MDR

SDTM, ADaM and define.xml with OpenCDISC Matt Becker, PharmaNet/i3, Cary, NC

Business & Decision Life Sciences

Package R4CDISC. September 5, 2015

USE CDISC SDTM AS A DATA MIDDLE-TIER TO STREAMLINE YOUR SAS INFRASTRUCTURE

Implementing the CDISC standards into an existing CDMS

SAS CLINICAL STANDARDS TOOKIT

CDISC SDTM & Standard Reporting. One System

Automate Data Integration Processes for Pharmaceutical Data Warehouse

Transforming CliniCal Trials: The ability to aggregate and Visualize Data Efficiently to make impactful Decisions

PhUSE Paper CD13

Statistical Operations: The Other Half of Good Statistical Practice

Using SAS Data Integration Studio to Convert Clinical Trials Data to the CDISC SDTM Standard Barry R. Cohen, Octagon Research Solutions, Wayne, PA

XClinical offers an integrated range of software products for CROs, pharmaceutical, medical device and biopharmaceutical companies.

PharmaSUG Paper CD13

Sanofi-Aventis Experience Submitting SDTM & Janus Compliant Datasets* SDTM Validation Tools - Needs and Requirements

SAS Drug Development User Connections Conference 23-24Jan08

Business & Decision Life Sciences What s new in ADaM

SDTM AND ADaM: HANDS-ON SOLUTIONS

End-to-End E-Clinical Coverage with Oracle Health Sciences InForm GTM

Applicant Workflow Hiring Managers

Udo Siegmann member of e3c, CDISC Sen. Dir. Acc. Management PAREXEL

Clinical Data Management (Process and practical guide) Dr Nguyen Thi My Huong WHO/RHR/RCP/SIS

The Development of the Clinical Trial Ontology to standardize dissemination of clinical trial data. Ravi Shankar

How to easily convert clinical data to CDISC SDTM

SDTM Validation Rules in XQuery

Using SAS in Clinical Research. Greg Nelson, ThotWave Technologies, LLC.

ADaM or SDTM? A Comparison of Pooling Strategies for Integrated Analyses in the Age of CDISC

Lessons on the Metadata Approach. Dave Iberson- Hurst 9 th April 2014 CDISC Euro Interchange 2014

WHITE PAPER. CONVERTING SDTM DATA TO ADaM DATA AND CREATING SUBMISSION READY SAFETY TABLES AND LISTINGS. SUCCESSFUL TRIALS THROUGH PROVEN SOLUTIONS

Overview of CDISC Implementation at PMDA. Yuki Ando Senior Scientist for Biostatistics Pharmaceuticals and Medical Devices Agency (PMDA)

ABSTRACT INTRODUCTION. Paper RS08

Dynamic Decision-Making Web Services Using SAS Stored Processes and SAS Business Rules Manager

4. Understanding Clinical Data and Workflow Understanding Surveillance Data Exchange Processes Guide and Worksheet

Paper DM10 SAS & Clinical Data Repository Karthikeyan Chidambaram

What's New in SAS Data Management

Using the SAS XML Mapper and ODS PDF to create a PDF representation of the define.xml (that can be printed)

Bringing Order to Your Clinical Data Making it Manageable and Meaningful

Test Data Management Concepts

Implementing CDASH Standards Into Data Collection and Database Design. Robert Stemplinger ICON Clinical Research

Data Conversion to SDTM: What Sponsors Can Do to Facilitate the Process

PhUSE Metadata Management Project

TRANSFORMING LIFE SCIENCES THROUGH ENTERPRISE ANALYTICS

SAS Add in to MS Office A Tutorial Angela Hall, Zencos Consulting, Cary, NC

Extracting the value of Standards: The Role of CDISC in a Pharmaceutical Research Strategy. Frank W. Rockhold, PhD* and Simon Bishop**

Training/Internship Brochure Advanced Clinical SAS Programming Full Time 6 months Program

Rational Reporting. Module 3: IBM Rational Insight and IBM Cognos Data Manager

Understanding CDISC Basics

Electronic Submission of Regulatory Information, and Creating an Electronic Platform for Enhanced Information Management

Talend Metadata Manager. Reduce Risk and Friction in your Information Supply Chain

Monitoring Clinical Trials with a SAS Risk-Based Approach

Improve your Close Cycle Using Financial Close Manager

Stored Documents and the FileCabinet

Clinical Data Management (Process and practical guide) Nguyen Thi My Huong, MD. PhD WHO/RHR/SIS

Managing and Integrating Clinical Trial Data: A Challenge for Pharma and their CRO Partners

Multivendor Extension User Guide

Single Source: Use of Patient Care Data in Support of Clinical Research. Liora Alschuler, Landen Bain, Rebecca Kush, PhD October 2003

Optimizing Data Quality and Patient Safety with EDC Integration

Did you know? Accenture can deliver business outcome-focused results for your life sciences research & development organization like these:

Case Management Implementation Guide

PharmaSUG Paper AD08

Connections to External File Sources

Q: What browsers will be supported? A: Internet Explorer (from version 6), Firefox (from version 3.0), Safari, Chrome

Terms and Definitions for CMS Administrators, Architects, and Developers

SDTM Validation: Methodologies and Tools

New features in SDTM-ETL v SDTM-ETL TM. New Features in version 1.2

Reporting Enhancements

EMC Documentum Composer

Accenture Accelerated R&D Services: CDISC Conversion Service Overview

PK IN DRUG DEVELOPMENT. CDISC management of PK data. Matteo Rossini Milan, 9 February 2010

Bridging Statistical Analysis Plan and ADaM Datasets and Metadata for Submission

Smart Dataset-XML Viewer: Web Services

Clinical Data Management BPaaS Approach HCL Technologies

FreeForm Designer. Phone: Fax: POB 8792, Natanya, Israel Document2

A white paper presented by: Barry Cohen Director, Clinical Data Strategies Octagon Research Solutions, Inc. Wayne, PA

Implementation of SDTM in a pharma company with complete outsourcing strategy. Annamaria Muraro Helsinn Healthcare Lugano, Switzerland

Pharmaceutical Applications

CDISC and Clinical Research Standards in the LHS

ABSTRACT INTRODUCTION THE MAPPING FILE GENERAL INFORMATION

Integrity 10. Curriculum Guide

Testing Tools using Visual Studio. Randy Pagels Sr. Developer Technology Specialist Microsoft Corporation

ProjectTrackIt: Automate your project using SAS

Learning & Development Brochure

CDISC Journal. Using CDISC ODM to Migrate Data. By Alan Yeomans. Abstract. Setting the Scene

Oracle Data Integrator for Big Data. Alex Kotopoulis Senior Principal Product Manager

REx: An Automated System for Extracting Clinical Trial Data from Oracle to SAS

Using web service technologies for incremental, real-time data transfers from EDC to SAS

Transcription:

EFFECTIVE AND OPERATIONAL USE OF CDISC STANDARDS & STUDY METADATA THROUGH SAS LIFE SCIENCE ANALYTICS FRAMEWORK - PHUSE SDE (MAY2016) STIJN ROGIERS, SENIOR INDUSTRY CONSULTANT, HEALTH & LIFE SCIENCES (GLOBAL PRACTICE)

AGENDA EFFECTIVE AND OPERATIONAL USE OF CDISC STANDARDS AND STUDY METADATA THROUGH SAS LIFE SCIENCE ANALYTICS FRAMEWORK High Level Overview End-to-End flow CDISC Standards and Company CDISC Standards (SDTM/SEND) Study Metadata Define Study Level Metadata Submission Ready Define.XML Internal & External collaboration Data Extraction Automated extraction from ecrf (EDC systems) and ancillary data to SDTM/SEND like data (directly) in Repository SDTM transformation SDTM Mapping through automated learning and code generation Repository Metadata through (Extended) Attributes

END-TO-END SINGLE DATA MANAGEMENT & ANALYSIS ENVIRONMENT eshare Standards IMPORT eshare CDISC STANDARDS DATA MANAGEMENT 1 (Global) Standards Flow Protocol (Study) Metadata Flow 2 CREATE CUSTOMER STANDARDS DEFINE STUDY LEVEL METADATA Specifications CREATE SUBMISSION READY SDTM DEFINE.XML SHARE WITH INTERNAL & EXTERNAL STAKEHOLDERS(LSAF ) Specifications ANALYSIS ENVIRONMENT Analysis Details EDC External / Other Data Sensors/ Wearables EDC DATA EXTRACTION (LSAF + LSAF Extension) Other DATA EXTRACTION (LSAF + LSAF Pull Extension) Event Streaming (SAS Event Stream Process Engine) 4 SDTM Transformation (LSAF + LSAF Extension incl. automated learning) Deliverables (Internal sharing of SDTM data after Structure automated verification) Automated + Manual Review Activities (LSAF + LSAF Extension, SAS Visual Analytics, Pinnacle 21 Out (Open of CDISC), Scope Jreview,...) For Phuse SDE Cambridge Cross-Functional Review Tracking (LSAF + LSAF Extension) 5 6 Final Deliverables Extraction & Transformation Flow Review Flow Customer Legacy Environment High-Performance Exploratory Environment

STANDARDS FLOW eshare Standards IMPORT eshare CDISC STANDARDS DATA MANAGEMENT 1 (Global) Standards Flow Protocol (Study) Metadata Flow 2 CREATE CUSTOMER STANDARDS DEFINE STUDY LEVEL METADATA Specifications CREATE SUBMISSION READY SDTM DEFINE.XML SHARE WITH INTERNAL & EXTERNAL STAKEHOLDERS(LSAF ) Specifications ANALYSIS ENVIRONMENT Analysis Details EDC External / Other Data Sensors/ Wearables EDC DATA EXTRACTION (LSAF + LSAF Extension) Other DATA EXTRACTION (LSAF + LSAF Pull Extension) Event Streaming (SAS Event Stream Process Engine) 4 SDTM Transformation (LSAF + LSAF Extension incl. automated learning) Deliverables (Internal sharing of SDTM data after Structure automated verification) Automated + Manual Review Activities (LSAF + LSAF Extension, SAS Visual Analytics, Pinnacle 21 (Open CDISC), Jreview,...) Cross-Functional Review Tracking (LSAF + LSAF Extension) 5 6 Final Deliverables Extraction & Transformation Flow Review Flow Customer Legacy Environment High-Performance Exploratory Environment

CDISC STANDARDS (1/) Made available by SAS within Life Science analytics Framework for all customers Future Standards: using Life Science Analytics Framework API and stable eshare API (pilot(s) ongoing)

CDISC STANDARDS (2/) Details / Domains / Studies / Properties info

CDISC STANDARDS (/) Studies using this specific Standard already including the Repository location & Context State of Study

CDISC CUSTOMER STANDARDS (1/) Within same Data Standards Module

How? PHUSE SDE CDISC CUSTOMER STANDARDS (2/) Step 1: By Selecting the CDISC Standard (or other Customer Standard) and Exporting into Repository 2 SAS tables will be generated/available for making required updates: Reference_Columns and Reference_Tables

CDISC CUSTOMER STANDARDS (2/) Step 2: Import updated SAS tables as new/updated Customer Standard i.e. Global TA/Indication Study Standard.

STUDY METADATA FLOW eshare Standards IMPORT eshare CDISC STANDARDS DATA MANAGEMENT 1 (Global) Standards Flow Protocol (Study) Metadata Flow 2 CREATE CUSTOMER STANDARDS DEFINE STUDY LEVEL METADATA Specifications CREATE SUBMISSION READY SDTM DEFINE.XML SHARE WITH INTERNAL & EXTERNAL STAKEHOLDERS(LSAF ) Specifications ANALYSIS ENVIRONMENT Analysis Details EDC External / Other Data Sensors/ Wearables EDC DATA EXTRACTION (LSAF + LSAF Extension) Other DATA EXTRACTION (LSAF + LSAF Pull Extension) Event Streaming (SAS Event Stream Process Engine) 4 SDTM Transformation (LSAF + LSAF Extension incl. automated learning) Deliverables (Internal sharing of SDTM data after Structure automated verification) Automated + Manual Review Activities (LSAF + LSAF Extension, SAS Visual Analytics, Pinnacle 21 (Open CDISC), Jreview,...) Cross-Functional Review Tracking (LSAF + LSAF Extension) 5 6 Final Deliverables Extraction & Transformation Flow Review Flow Customer Legacy Environment High-Performance Exploratory Environment

DEFINE STUDY LEVEL METADATA (1/6) Details / Tabulation Standards using Study Tabulation Standard example Study-specific metadata entered in reference_columns for AE, such as origin, algorithms, and codelists further customized from the parent standard, and comments.

DEFINE STUDY LEVEL METADATA (2/6) Select the domain(s) desired and their target location. You will only be able to navigate within the analysis/project s Files folder that was selected for the Study. You can enable versioning and/or select to overwrite existing files. Result: zero-observation datasets have been created for each one in repository. Note: Import / Export feature is for Dataset.XML files (out of scope for this presentation)

DEFINE STUDY LEVEL METADATA (/6) Making use of Multiple Terminology Packages: Controlled Terminology that has already been made available by SAS in the Standards Module may be selected for the study. Many (other) Code Lists may be added by the customer. After you Save the study, the View Resulting Code Lists button will be active. The define.xml file will ONLY pick up and display the codelists that are actually used by a variable in the study.

DEFINE STUDY LEVEL METADATA (4/6) External Code Lists (2 Options): Import assumes you have a dataset in the required structure already populated that you would like to use (import). Create Template will create either a zero-observation dataset with the required structure, or if you select Populate with default entries - screenshot below - it will add the most commonly used external codelists (data dictionaries). This is however NOT submission-ready. There are placeholders that must be either modified or deleted, and the default entries should be reviewed for accuracy for the particular study and modified as needed.

DEFINE STUDY LEVEL METADATA (5/6) Import Template: If a template is used, once it is populated, you will need to Import it into the study. Creating a template does NOT automatically associate the template dataset with the study. The screen shot below shows the external codelists in the Study after they ve been imported.

DEFINE STUDY LEVEL METADATA (6/6) Same principle for Value Level Metadata & Supporting Documents

SUBMISSION READY DEFINE.XML (1/2) Select your study, and then click the Save as Define-XML button. Select the standard (if more than one was associated with the study) and domains to include. Specify the output repository location for the define to be stored + options to overwrite existing, choose encoding, add the stylesheet (always recommended) and set versioning.

SUBMISSION READY DEFINE.XML (2/2) Once it completes, your define.xml file and the stylesheet will appear in the location you specified in the Repository.

SHARE WITH INTERNAL & EXTERNAL STAKEHOLDERS Use Repository to share with Internal & External Stakeholders: For Review For Specifications: e.g. Stats-Programming; DM-CRO;... Make use of Workflow Engine and Notifications (email or within Life Science Analytics Framework)

DATA EXTRACTION FLOW eshare Standards IMPORT eshare CDISC STANDARDS DATA MANAGEMENT 1 (Global) Standards Flow Protocol (Study) Metadata Flow 2 CREATE CUSTOMER STANDARDS DEFINE STUDY LEVEL METADATA Specifications CREATE SUBMISSION READY SDTM DEFINE.XML SHARE WITH INTERNAL & EXTERNAL STAKEHOLDERS(LSAF ) Specifications ANALYSIS ENVIRONMENT Analysis Details EDC External / Other Data Sensors/ Wearables EDC DATA EXTRACTION (LSAF + LSAF Extension) Other DATA EXTRACTION (LSAF + LSAF Pull Extension) Event Streaming (SAS Event Stream Process Engine) 4 SDTM Transformation (LSAF + LSAF Extension incl. automated learning) Deliverables (Internal sharing of SDTM data after Structure automated verification) Automated + Manual Review Activities (LSAF + LSAF Extension, SAS Visual Analytics, Pinnacle 21 (Open CDISC), Jreview,...) Cross-Functional Review Tracking (LSAF + LSAF Extension) 5 6 Final Deliverables Extraction & Transformation Flow Review Flow Customer Legacy Environment High-Performance Exploratory Environment

DATA EXTRACTION FLOW (1/4) SAS Clinical Standards Toolkit 1a 1b EDC (Rave) (using REST Service / Proc HTTP) EDC (Inform) (using SOAP Service / Proc SOAP) Ancillary Data (e.g. Lab data) (using Pull Life Science Analytics Framework Extension) ODM.XML 2 non-hierarchical to hierarchical structure Cube.XML Through Libname XML (XML Engine) Pull in SDTM-Like (or SDTM) Datasets from Ancillary Data Providers SAS Datasets 4 Metadata Datasets (per Study Version) Data Datasets (per Study Version) SAS Datasets SDTM-like Datasets (available In Repository)

DATA EXTRACTION FLOW EDC TO ODM.XML (2/4) (example) ODM XML 1..0 Metadata (example) ODM XML 1..0 Data

DATA EXTRACTION FLOW ODM.XML TO CUBE.XML (/4) (Example) Cube XML Metadata (Example) Cube XML Data

SAS Datasets Metadata DATA EXTRACTION FLOW CUBE.XML TO SAS DATSETS (4/4) SAS Datasets Data SAS Datasets SDTM like

SDTM TRANSFORMATION eshare Standards IMPORT eshare CDISC STANDARDS DATA MANAGEMENT 1 (Global) Standards Flow Protocol (Study) Metadata Flow 2 CREATE CUSTOMER STANDARDS DEFINE STUDY LEVEL METADATA Specifications CREATE SUBMISSION READY SDTM DEFINE.XML SHARE WITH INTERNAL & EXTERNAL STAKEHOLDERS(LSAF ) Specifications ANALYSIS ENVIRONMENT Analysis Details EDC External / Other Data Sensors/ Wearables EDC DATA EXTRACTION (LSAF + LSAF Extension) Other DATA EXTRACTION (LSAF + LSAF Pull Extension) Event Streaming (SAS Event Stream Process Engine) 4 SDTM Transformation (LSAF + LSAF Extension incl. automated learning) Deliverables (Internal sharing of SDTM data after Structure automated verification) Automated + Manual Review Activities (LSAF + LSAF Extension, SAS Visual Analytics, Pinnacle 21 (Open CDISC), Jreview,...) Cross-Functional Review Tracking (LSAF + LSAF Extension) 5 6 Final Deliverables Extraction & Transformation Flow Review Flow Customer Legacy Environment High-Performance Exploratory Environment

SDTM TRANSFORMATION Goal Mapping kick-offs each time data (sas datasets / sdtm- like ) are being refreshed in Repository SDTM Mapping Rule to be setup per trial to trigger mapping automation Same as Adaptive Design rules e.g. 0 patients, 60 patients, Mapping through Automated Learning as more Standards are being used greater % re-usability over time less manual interaction for new trials / setup to be done Review required especially at start Code generation (based on pseudo code entry via UI) Already done within SAS Clinical Data Integration Studio Re-using capabilities for Life Science Analytics Extension

REPOSITORY METADATA THROUGH (EXTENDED) ATTRIBUTES

Stijn.Rogiers@sas.com www.linkedin.com/in/stijnrogiers Twitter: @stijnrogiers