1. © CDISC 2014 Stetson Line, Team Lead 2 2014 CDISC Intrachange SDTM Rules Sub-team Update.

Slides:



Advertisements
Similar presentations
Monika Kawohl Principal Statistical Programmer Accovion
Advertisements

ADaM Implementation Guide: It’s Almost Here. Are You Ready?
CDASH Initiative: Status Update
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
A Strategic Plan to Address Key Result Areas (KRAs) from the Port Kells Assessment.
PROFESSIONAL GROWTH PLAN UPDATE PROPOSALS COMMITTEE UPDATE MAY 2008
UC5:Assigning of Epoch after treatment discontinuation (NS)
An Introduction to Clinical Data Acquisition Standards Harmonization (CDASH) Loryn Thorburn © 2010 PAREXEL International | Confidential.
“Compliance” for Analysis Data Chris Decker, Vice-President, Life Sciences Practice, d-Wise Technologies Randall Austin, Manager, Data Standards, GlaxoSmithKline.
Project Management Module 3. Keep focused on the timeline Week Prepare for Kick-off Meeting Assign teams Team forming Review and execute.
Guide To UNIX Using Linux Third Edition
Study Data Standardization Plan Kick0ff Meeting 23 July 2014.
STANDARDIZATION It’s Not a Bad Word!. Before Standardization Between 4 Adult Schools, CBET Classes and Offsite Classes, ALL ESL classes had different.
WUSS 2009 CDISC for the Medical Device and Diagnostic Industry: An Update Carey Smoak Team Leader CDISC Device SDTM Sub-team.
Requirements for Standardized Study Data: Update on Guidance Ron Fitzmartin, PhD, MBA Data Standards Program Office of Strategic Programs Center for Drug.
2014 Work Planning Local Program Leadership Team.
Bay Area CDISC Implmentation Network – July 13, 2009 How a New CDISC Domain is Made Carey Smoak Team Leader CDISC SDTM Device Team.
SDTM Validation Rules Sub-team Kickoff Meeting January 24 th, 2014.
SDTM Validation Rules Sub-team CDISC INTRAchange Feb 26 th, 2014.
Dominic, age 8, living with epilepsy SDTM Implementation Guide : Clear as Mud Strategies for Developing Consistent Company Standards PhUSE 2011 – CD02.
© 2011 Octagon Research Solutions, Inc. All Rights Reserved. The contents of this document are confidential and proprietary to Octagon Research Solutions,
RDA Data Foundation and Terminology (DFT) IG: Introduction Prepared for RDA Plenary San Diego, March 9, 2015 Gary Berg-Cross, Raphael Ritz, Co-Chairs DFT.
Overview and feed-back from CDISC European Interchange 2008 (From April 21 st to 25 th, COPENHAGEN) Groupe des Utilisateurs Francophones de CDISC Bagneux.
Quote for today “Sometimes the questions are complicated and the answers are simple” - ?? ????? “Sometimes the questions are complicated and the answers.
Booster/Refresher Training: Implementation Plan Benchmarks of Quality Items # 35 –
Update on SDTMIG v and SDTM v. 1.2 Bay Area User Group Meeting May 2008 Fred Wood Octagon Research Solutions.
Copyright © 2010, SAS Institute Inc. All rights reserved. Implementing, Managing, and Validating a Clinical Standard Using SAS Clinical Standards Toolkit.
Second Annual Japan CDISC Group (JCG) Meeting 28 January 2004 Julie Evans Director, Technical Services.
Standards Analysis Summary vMR – Pros Designed for computability Compact Wire Format Aligned with HeD Efforts – Cons Limited Vendor Adoption thus far Represents.
15th Informal US MedDRA User Group Meeting, October 28, 2011 Slide 1 Double the Impact with Half the Work: Linking MedDRA and WHO Drug Indication coding.
CountryData Technologies for Data Exchange SDMX Information Model: An Introduction.
Second expert group meeting on Draft fiche on delegated act on the European code of conduct on partnership (ECCP) Cohesion Policy
SDTM Validation Delaware Valley CDISC user network Ketan Durve Johnson and Johnson Pharmaceutical Reasearch and Development May 11 th 2009.
US Army Corps of Engineers BUILDING STRONG ® Local Data Requirements and Definitions USACE SDSFIE Training Prerequisites: Creating a Data Dictionary for.
Work Breakdown Structure Kathy S. Schwaig. What is a Work Breakdown Structure (WBS)? A WBS is a logical hierarchy of work packages involved in a project.
WG4: Standards Implementation Issues with CDISC Data Models Data Guide Subteam Summary of Review of Proposed Templates and Next Steps July 23, 2012.
Public Health Reporting Initiative Stage 3 Sprint: Implementation Guide Development Phone: x
WG4: Data Guide/Data Description Work Group Meeting August 29, 2012.
1. © CDISC 2014 SDS ELT Rules Team Update Stetson Line 08 Dec
The IEP: Drafting the IEP (Steps 1, 2, 3, and 4) Southwest Ohio Special Education Regional Resource Center Tuesday, November 7, 2006.
CDISC©2009 February CDISC INTRAchange Carey Smoak Device Team Leader Li Zheng Submission Data Standards Team Member Thurday, April 2, 2009.
ISO Current status of development ​ ​ ISO development process ​1​1.
(Project) RISK MANAGEMENT PROCESS SEPTEMBER 5, 2008.
ITPD ISSUE MANAGEMENT PROCESS SEPTEMBER 5, 2008
1 ISO/PC 283/N 197 ISO Current status of development November 2015.
Discussion - HITSC / HITPC Joint Meeting Transport & Security Standards Workgroup October 22, 2014.
Emerging Technologies Semantic Web and Data Integration This meeting will start at 5 min past the hour As a reminder, please place your phone on mute unless.
Standards Analysis Summary vMR – Pros Designed for computability Compact Wire Format Aligned with HeD Efforts – Cons Limited Vendor Adoption thus far Represents.
Updates on CDISC Activities
Coaching protocol practice Each team select a map (unit) to use for the coaching protocol. Join another person / team not from your grade or department.
How good is your SEND data? Timothy Kropp FDA/CDER/OCS 1.
Croatia: Result orientation within the process of preparation of programming documents V4+ Croatia and Slovenia Expert Level Conference Budapest,
© CDISC 2015 Paul Houston CDISC Europe Foundation Head of European Operations 1 CTR 2 Protocol Representation Implementation Model Clinical Trial Registration.
How Good is Your SDTM Data? Perspectives from JumpStart Mary Doi, M.D., M.S. Office of Computational Science Office of Translational Sciences Center for.
CDISC SDS Oncology Domains: An Orientation to Aid Review & Feedback Barrie Nelson CDISC SDS Oncology Sub Team Lead
Example Presentation: Alignment, Launch & Adoption
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
Accenture Accelerated R&D Standards Metadata Management – version control and its governance Kevin Lee CDISC NJ Meeting at 01/28/2015 We help our Clients.
Roadmap to Enhanced Technical Regulations of WMO
Maintaining the Clinical & Nonclinical Study Data Reviewer’s Guides
MAKE SDTM EASIER START WITH CDASH !
Structure–Feedback on Structure ED-2 and Task Force Proposals
SDTMs in Medical Devices A First Attempt
To change this title, go to Notes Master
WG4: Data Guide/Data Description Work Group Meeting
SDTM and ADaM Implementation FAQ
aCRF Design Manual German CDISC User Group Markus Stoll
ISSUE MANAGEMENT PROCESS MONTH DAY, YEAR
38th Nuclear Safety Standards Committee 37th Radiation Safety Standards Committee 38th Waste Safety Standards Committee Joint Session 26 – 27 November.
Implementation of the SDP
Presentation transcript:

1

© CDISC 2014 Stetson Line, Team Lead CDISC Intrachange SDTM Rules Sub-team Update

© CDISC 2014 Mission SDTM Rules Sub-team Identify business rules in guidance and surface these in a clear, consistent and consumable manner –Distinct from data validation rules, focused on compliance, conformance to guidance –Coordinate with SHARE, other teams on rule definition metadata and methods 3

© CDISC 2014 Rules Sub-Team Target Milestones Q  Sub-team Kickoff /Member orientation/ assignments  SDTM IG v3.2 – DM Rules Pilot Q  SDTM Validation Rules Development Guide  SDTM IG v3.2 – Events Observation Class Rules  SDTM IG v3.2 – Interventions Observation Class Rules Q  SDTM IG v3.2 – Findings Observation Class Rules  SDTM IG v3.2 – Other Special Purpose Domains Rules Q  SDTM IG v3.2 – Trial Design Domains Rules  SDTM IG v3.2 Validation Rules (submitted for public comment)  SDTM Validation Rule Implementation Guide (submitted for public comment) 4

© CDISC 2014 SDTM Rules Meeting Support 5

© CDISC 2014 Rule Metadata Elements Rule ID Rule Condition Comments / Questions / Dispositions IG Section IG Item # IG Text Class Domain Variable 6

© CDISC 2014 Rules Production DateRulesParking LotDomainsCumlative Hours 21-Apr DM197 9-Jun AE CE DM DS DV MH MO Jul AE CE CM DM DS DV EC EX MH MO HO SU PR Aug AE CE CM DM DS DV EC EG EX IE IS LB MH MI MO HO SU PC PP PR RS TR TU TIMING Sep AE CE CM DM DS DV EC EG EX IE IS LB MB MH MI MS MO HO SU PC PP PR RS TR TU TIMING meetings 7+ average attendance

© CDISC 2014 Rules Production by Domain Rules 120+ in Draft

© CDISC 2014 Essential ground rules for authoring consistently formed rules  Rule Syntax  Standard Operators /Tokens  Controlled Terminology Document evolution of conventions / best working practices  Currently v1.3 – Mostly refinements in definition of rule scope and hierarchy Rules Development Guide 9

© CDISC 2014 Rules Hierarchy - Rationale All rules are stated uniquely at the highest applicable level of the rule hierarchy possible  Minimizes redundancy and maintenance overhead  Helps drive clarity around core principles and any exceptions to those principles  Aids rule development and review 10

© CDISC 2014 Rules Examples Simple Rule – No Hierarchy 11 Rule IDRuleConditionClassDomainVariable EVT_AE_AESER_01AESER = 'Y'AESCAN = 'Y' or AESCONG = 'Y' or AEDISAB = 'Y' or AEDTH = 'Y' or AESHOSP = 'Y' or AELIFE = 'Y' or AESOD = 'Y' or AESMIE = 'Y' or AECONTRT = 'Y' EVTAEAESER EVT_AE_AESER_02AESER = 'N'AESCAN ^= 'Y' and AESCONG ^= 'Y' and AEDISAB ^= 'Y' and AEDTH ^= 'Y' and AESHOSP ^= 'Y' and AELIFE ^= 'Y' and AESOD ^= 'Y' and AESMIE ^= 'Y' and AECONTRT ^= 'Y' EVTAEAESER

© CDISC 2014 Rules Examples Multiple Domain Rules Rule ID serves as both unique key and pointer to whether additional fields (Class, Domain, Variable) are needed to further refine scope 12 Rule IDRuleConditionClassDomainVariable FND_ALL_--DRVFL_01--DRVFL in ('Y', null) FNDALL--DRVFL FND_ALL_--DRVFL_02--DRVFL = null--STRESC = null or --STAT = 'NOT DONE' FNDALL--DRVFL Rule IDRuleConditionClassDomainVariable INT_MLT_--DOSE_01--DOSE = null--DOSTXT ^= nullINTEX, CM, EC, PR, SU --DOSE INT_MLT_--DOSTXT_01--DOSTXT = null--DOSE ^= nullINTEX, CM, EC, PR, SU --DOSTXT

© CDISC 2014 Rules Examples Multiple Observation Class Rules Notice use of NOT() syntax for excluded domains in last example 13 Rule IDRuleConditionClassDomainVariable MLT_MLT_--OCCUR_01--OCCUR ^= null--PRESP = 'Y' and --STAT ^= 'NOT DONE' EVT,INTMH,CE,HO, CM,EC,PR, SU --OCCUR MLT_MLT_--OCCUR_02--OCCUR = null--PRESP ^= 'Y'EVT,INTMH,CE,HO, CM,EC,PR, SU --OCCUR Rule IDRuleConditionClassDomainVariable MLT_MLT_GEN_01At least one timing variable must exist FND, EVT, INT NOT(IE)GEN

© CDISC 2014 SHARE Team Collaboration SHARE team members on Rules team Ongoing review of SDTM Rules development  Interest in aligning metadata conventions  Preparing for SHARE implementation A. Chow invited to Rules meeting  Discussed feedback on proposed rules  Presented draft CMAP of Rules metadata model  Example conventions – quotes for text values, preceding ‘--’ for domain wildcard in variable naming, categorizing rule types…etc. 14

© CDISC 2014 SHARE Team Draft Rules Model 15

© CDISC 2014 Rules Parking Lot Breakdown 16 Issue/ Observation ClassALLEVTFNDINTSPCTotal ERRATA32218 OTHER TEAMS3115 QUESTION FOR ESCALATION REVISE GUIDANCE RULE METADATA718 VAR GENERALLY NOT USED Total

© CDISC 2014 Thank You Stetson Line President, clinventive