• No results found

CDISC SDTM & Standard Reporting. One System

N/A
N/A
Protected

Academic year: 2021

Share "CDISC SDTM & Standard Reporting. One System"

Copied!
31
0
0

Loading.... (view fulltext now)

Full text

(1)

CDISC SDTM

&

Standard Reporting

One System

(2)

Authors/Contributors

{ Merck & Co., Inc.

z Ram Radhakrishnan, Manager, Statistical Information Systems

z Thomas W. Dobbins, Ph.D., Executive Director, Biostatistics and Statistical Information

Systems

z Paul DeLucca, Ph.D., Associate Director, Biostatistics and Statistical Information Systems

z Susan Neidlinger, Manager, Statistical Computing

(3)

Authors/Contributors

{

Nth Analytics

z Michael Todd, President

z Anne Russotto, Project Manager

z T. Richard Garrity, Software Architect

(4)

Merck Background

{ Biostatistics and Statistical Information Systems (BASIS)

z Statistics Organization in Clinical Development Programs

z Provides statistical and programming support for the design, analysis, and reporting of

clinical trials data for approved drugs

z Results used in publications and promotions

{ Some support for Registration (sNDAs)

(5)

Legacy Process

{

Data in disparate databases and structures

{

Multiple versions/sets of programs to generate Tables and Listings

(T&Ls)

{

Distinct processes for Analysis &

Reporting (A&R)

(6)

Legacy Process

Data 1 Data 1

Data 1

Data Project

Programs

Reports

Project 1

Data

Project Programs

Reports

Project 2

… etc.

(7)

Legacy Process

(continued)

{

Challenges:

z Combining and reporting data across studies

z Inefficient Process:

{ Resource burden of maintaining multiple reporting tools, programs, validation, etc.

{ Sub-optimal process for response to

requests for additional Strategic Analyses

z e.g. sub group analyses with classifications and covariates

(8)

BASIS A&R Vision

{

“One-step away from knowledge”

statistical analysis and reporting

process

(9)

BASIS A&R Strategic Goal

{

A common (SAS-based) platform

{

A Structured Data Model

{

Access to all clinical trial data independent of time, place, database, or compound

{

One-step away access to data for

statistical analysis and reporting to

any level of complexity

(10)

Vision & Strategic Goal Implementation

{ Unified A&R Environment

{ Standard SAS Dataset Model

z Independent of Data Source/System

z Define a structured analysis data model

z Metadata-driven

{ All derivations at dataset level

z Standardized by Therapeutic Area

{ but allows for customization

z Standard Code and Template Library to generate datasets, T&Ls

(11)

New A&R Process Advantages

{

Easy to combine data across studies

{

Unified (integrated) A&R process

{

Reusable, standard code for datasets and T&Ls

{

Easy to maintain, validate, and

update

(12)

New A&R Process Advantages

{

Optimal process for addressing additional requests for strategic analyses

{

Proactively anticipate and plan for additional requests

{

Easily respond to unanticipated

requests

(13)

Nth Analytics Solution

{

Part I - An ETL Process to generate CDISC SDTM+ datasets

{

Part II – A Generic Table System to generate standard Merck reports

from the SDTM+ datasets

(14)

Nth Analytics Solution

{

ETL procedure to create CDISC SDTM datasets

z Maps source data into SDTM domains

z Provides an automated method for

specifying data sources and algorithms

z Provides all information required for the FDA-mandated “DEFINE.PDF”

(15)

Why Choose SDTM?

{ SDTM adoption approaching critical mass

{ Standard data structure simplifies reporting

{ Merck is adopting CDISC standards

{ Issues:

z SDTM structures exclude derived variables

z ADaM not finalized

z Need to include all variables collected

(16)

What About ADaM?

{

ADaM is an evolving standard

z not finalized in Aug 2004

z adoption would have been premature

{

Some ADaM principles were applied:

z Build on SDTM structures

z One PROC away

z SAS dates, not ISO dates

z Numeric codes for sorting

(17)

Special Considerations

{

In determining a solution, there were some special considerations:

z Studies not intended for submission

z Full CDISC compliance not critical

{ Unless studies are included in a submission

z Focused reporting objectives

(18)

Possible Implementation Strategies

{ Parallel method

z develop SDTM and analysis data simultaneously

{ Retrospective method

z develop analysis data first, then derive SDTM from the analysis data

{ Linear method

z develop SDTM first, then create analysis data from SDTM

(19)

Hybrid Method

(20)

Hybrid Method - Advantages

{ Analysis file programs are useful to reviewer and as documentation

{ Encourages standardization of analysis datasets

{ Variables or records in SDTM that need statistical input can be obtained from analysis files

{ Derived records or supplemental variables can be easily added to SDTM if needed or desired

z Disposition events

z Population flags

(21)

Possible Implementation Strategies (cont.)

{

Hybrid method

z “SDTM+ conforms to standards but may not be complete with respect to variables or records that need clinical or statistical input or other permitted variables”

z “May contain non-SDTM variables needed for analysis”

(22)

SDTM+ to SDTM Final – Submission Ready

{

Changes related to submission:

z Drop non-SDTM variables

{ automated process because these variables are flagged in metadata

z Create trial design datasets

z Create RELREC, SC, SUPPQUAL

z Create ISO dates/times

{ SAS formats make this easy to automate

(23)

Preparing for Submission

{

The SDTM+ datasets are the source for ADaM datasets

{

Easily convert SDTM+ to

submission-ready SDTM datasets

{

Documentation = mapping table

{

Standalone submission-ready

programs built-in

(24)

Nth Analytics Solution - Reporting

{

STDM+ simplifies reporting

{

Generic Table System

z Calling programs use SAS Macros to

generate standard reports from SDTM+

z Achieves standardization, and is easy for programmers to use

(25)

Implementation Methodology

M e ta d a ta

E T L P ro c e s s

A E C M D M

D S

D a ta M H

D B M S E x tra c t

A G E C A T G N A g e c a t x g e n d e r

P a tie n t C h a r.

C lin ic a l A E b y S O C C lin . A E S u m m a ry C o n M e d S u m m a ry

P rio r M e d S u m . D is p o s itio n P ts . b y In v .

C lin . A E s (lis tin g ) P T D IS P

B A S E C H A R

P T IN V T R T

C A E S O C C A E S U M M

C O N T C N T P R IC N T

C A E L S T

S e c o n d a ry D ia g . S E C D IA G

P ro je c t 1

M e ta d a ta

P ro je c t 2

D B M S E x tra c t

S D T M + D a ta s e ts

R e p o rt M a c ro s S td . R e p o rts

(26)

Nth Analytics Solution

{

Why this approach worked for Merck

z Did not disrupt existing clinical trial systems

z It can be applied to legacy data

z Minimal rework

{ only metadata will change for each study

(27)

Nth Analytics Solution

{

Why this approach worked for Merck (cont.)

z Table driven metadata provides automatic documentation

z Effort to produce subsequent SDTM files is minimized

{ only study-specific situations require additional coding

(28)

Merck - Implementation

{

Tool has been installed and used for 8 studies in 3 Therapeutic Areas

z Multiple eDC versions with different structures

{

Currently being used in 5 ongoing studies

z 2 CRO studies

z 2 eDC systems

(29)

Adoption with New Studies

{

Minor customization for new studies

z Mapping table process

z Macros

z Preprocessing code allows for further customization

(30)

Merck - Benefits

{

Increased efficiency by over 50%

z Reduced programming time, resources

z Limited validation effort

{ standards

{ single reporting system

{

All T&Ls delivered within 5-10 days

from DB lock

(31)

Merck Benefits -

(continued)

{

Consistency in A&R ground rules

{

Standard data exchange protocol

z transparent and portable

{

Timely response for Strategic

Analyses and ad hoc requests

References

Related documents

The SDTM variables listed in the CDISC variable column are assigned values as specified in the Expression column.. The Expression column may contain any valid SAS assignment or a

• 'Mapping file - working version' folder: This folder contains the working version of the mapping file (tmpmapping.xls). Any changes to the mapping rules should be done in

One way to think of it, is that the SDTM standard is for presenting study data using Clinical Data Interchange Standards Consortium (CDISC) compliant specifications, and the

The SDTM metadata mapping tool allows users to manage and document the mapping of study data to CDISC SDTM domains and it produces text files containing SAS source code to be used as

remaining CDISC checks are more specialized, but can be done with 6 condensed checks or less. Overall, a duration of 4 weeks is recommended for the programming of all SDTM and

• Evaluate if the structure is CDISC complaint and Helsinn SDTM requirements are fullfilled. – SAS programming: PROC IMPORT of

Some team members thought the SDTM variables should be copied over if used in the analysis and maintain all attributes, while other members thought variables from SDTM should be

– Manage a spectrum of SDTM implementations – ADaM best build upon SDTM, not on ‘raw’ data. SDTM –