harmonizing cdisc submission models and pharmacovigilance
TRANSCRIPT
![Page 1: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/1.jpg)
Harmonizing CDISC Submission Models and Pharmacovigilance
October 11, 2005Edward Helton, Ph.D.
Chief Strategist, Pharmaceutical & Regulatory AffairsSAS Institute, Inc.
![Page 2: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/2.jpg)
Current State
• SDTM developed with raw/observed data in mind• ADaM designed for analysis datasets (includes
derived data)• Some company-specific work has been done to
put derived data into SDTM• Question: How do we create a single model (THE
CDISC model) for submitting all data to FDA?– Raw and derived and metadata– What are the full requirements for such a single model?– What would it take to make this approach reasonable for
pharma industry business process and FDA review process?
![Page 3: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/3.jpg)
CDISC ProjectObjective• To assess the data structure/architecture, resources and
interoperability needed to transform data from legacy data sets (observed, derived and analysis data) into the CDISC SDTM and/or ADaM formats.
• CDISC will perform case studies which demonstrate the effective transformation of legacy data into CDISC SDTM domains and ADaM datasets and their associated metadata.
• A case study/test(or series of studies/tests) would allow CDISC to understand how SDTM might be used for submission of derived data and the specific needs for separate ADaM datasets/programs.
• CDISC wants to repetitively test and learn the very best application of its interoperable standards to meet the industryregulatory data submission requirements.
![Page 4: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/4.jpg)
CDISC Project
• CDISC and PhRMA are building a stronger relationship to solve these problems
• Streamlining and standardizing the data flow for pharma business and submission to FDA will require multiple steps / endeavors
![Page 5: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/5.jpg)
Disclaimer
• The views in this presentation are not necessarily the views/policies of :– the CDISC Board– Eli Lilly and Company– SAS Institute, Inc.– Ed Helton, Dave Christiansen, Wayne
Kubick, and FDA… but they should be.
![Page 6: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/6.jpg)
CDISC Goals-Simply Stated(circa 2001)
A future conversation on data interchange:• anyone: How do you want me to send the
data?• everyone: We are using CDISC version x.y• anyone: I can do that
PS Data = raw, derived, metaPPS Anything said about submission of data to the
FDA could apply to how CROs ‘submit’ data to Sponsors
![Page 7: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/7.jpg)
Some Principles• Minimize redundant data sets and data flows
– Reduce chances of errors and inconsistencies– “Neither seek nor avoid complexity.” (R. A. Fisher)
• Statistical Reviewers need data sets that can be readily analyzable (i.e. minimize programming)– “one PROC away” is desirable
• All Reviewers need derived data– Minimize Reviewers doing programming
• Data is stored in a common way/warehouse using standard formats and content– Facilitates communication for review and regulatory
approval– Support integration across studies/companies– Facilitate automation and use of common tools– Supports traceability from collected to analyzed data
![Page 8: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/8.jpg)
Some Considerations
Scope
PrimaryPurpose
Individual Study/Submission
Integration Across Submissions
Verify Data As Analyzed
Review Data As Reported
![Page 9: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/9.jpg)
Figure 1ASubmission Data Flow – Emerging State
Medical Reviewer
Standard ToolsPatient Profile ViewerWebSDMJMPetc.
RawDataSDTM Subm
issionSA
S Transport
***
Company A
Statistical Reviewer
Pat Y1 Y2 X1 X2
Submission
Derivation Programs*
Analysis Programs*
Pat Y1 Y2 X1 X2
Standard Tools
Custom Pgms
SubmissionSAS Transport
Company B
Company C
ADaM
?
SDTM / JANUS (FDA)
*Structure and process is the discretion of the Sponsor.
![Page 10: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/10.jpg)
Figure 1BSubmission Data Flow – Emerging State
Medical Reviewer
Standard ToolsPatient Profile ViewerWebSDMJMPetc.
RawData
DerivedData
SDTMSubm
issionSA
S Transport
***
Company A
Statistical Reviewer
Pat Y1 Y2 X1 X2
Submission
Derivation Programs*
Analysis Programs*
Pat Y1 Y2 X1 X2
Standard Tools
Custom Pgms
SubmissionSAS Transport
Company B
Company C
ADaM
JANUS (FDA)
*Structure and process is the discretion of the Sponsor.
![Page 11: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/11.jpg)
Some Considerations
Raw / Observed Data Analysis Data
Sets
Pat Y1 Y2 X1 X2 …
What happens in this space is company specific
![Page 12: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/12.jpg)
Some Considerations
Raw / Observed Data
Judgment !
Analysis Data Sets
Pat Y1 Y2 X1 X2 …
How do we capture all these judgments?Text? Code? Machine-readable metadata?
What judgments can be turned into rules?
![Page 13: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/13.jpg)
Some Considerations
Raw / Observed Data
Judgment !
Analysis Data Sets
Pat Y1 Y2 X1 X2 …
What metadata can be captured? These questions are relevant regardless of how derived data are structured in an analysis data set.
What can be standardized? automated?Can metadata help with integration across studies?
![Page 14: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/14.jpg)
Creating THE CDISC Model
THE CDISC Model
Metadata
RawData
DerivedData
DerivationsPrograms
ProtocolMetadataOperational
Database
![Page 15: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/15.jpg)
Creating the CDISC Warehouse
• Companies can more easily build internal warehouses of clinical data using CDISC standard content, structures, metadata
Company X-Y-Z
Compound A
Compound B
Compound C
There is no need to have multiple archives of data (protocol, raw derived and meta) and programs.
![Page 16: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/16.jpg)
Creating the CDISC Submission
FDA or Sponsor
TheCDISC Model
DerivedData
RawData
CommonApplications
Analysis Data Sets
Pat Y1 Y2 X1 X2
Standard ToolsPatient Profile ViewerWebSDMJMPetc.
Medical Reviewer
Statistical Reviewer
Metadata
ProtocolMetadata
Judgment?
![Page 17: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/17.jpg)
What else do we need?
• Can we have a comprehensive/robust enough vocabulary to integrate data across studies easily?– Raw data is hard enough; derived data is … ?
• Can we have comprehensive metadata to describe trial design, judgments and analysis?– Judgments for a single analysis– Judgments for integrated summary across a compound– Judgments for integrated summary across companies
• Some alchemy
![Page 18: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/18.jpg)
Conclusion 1
• CDISC committed to unambiguous communications for submissions– Data structures and content– Derivations, analysis programs
• Levels of complexity / sophistication– For an individual study– For studies across a submission– For submissions across companies
![Page 19: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/19.jpg)
Conclusion 2
• Analysis datasets will not go away– How they are created and documented
may• Can we simplify/streamline
unambiguous communication on analyses – An integrated CDISC model that can
accommodate raw and derived data– Common tools available to create
analysis data sets
![Page 20: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/20.jpg)
Conclusion 3
• Individual companies need to make business decisions about when and how to implement CDISC standards– Embed SDTM into internal systems and
data flows?– How SDTM and ADaM operate with each
other– Create company-specific extensions to
CDISC metadata and/or vocabularies– Etc.
![Page 21: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/21.jpg)
End-to-End Seamless Integration; Semantic Interoperability
Open Data Model - XML based, CDISC compliant
Pharma
Medical & StatisticalReviewers
Approval
Patients
Subject
CDMSOp DB
Investigator
Physician
ODM SDTM
LAB ADaM
![Page 22: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/22.jpg)
![Page 23: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/23.jpg)
Janus Solution Overview
XML Submissions and updates
XML Schemas
CDISC SDTM
Potential Extension:1571/1572 form data
Base JanusData Model
Janus data extensions
Data Load API
FDA Submissions
Source
caBIO/DSAM JDBC 2
User Test Applications
SAS Analytical
Applications
Query Application
Excel w/ caCORE
driver
WebSDMand/or
ToxViewer
Note: elements shown with dashed lines are potential extensions to the proposed project.
Note: elements shown with dashed lines are potential extensions to the proposed project.
Master Subject Index
caDSR EVS
CSM
ODM XMLDefine.XML(HL7 CRF)
caGRID
caBIG
NCI Janus Repository
HL7 RIM
![Page 24: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/24.jpg)
ODM Study BasicDefinitions
MetadataVersion
GlobalVariables
ArchiveLayout
AE
ItemGroupRefFormRefProtocol
Presen-tation
Global/Transfer Metadata Secondary Global Metadata
Study-specific Metadata
Study Level Administration Level
UserItemDefItemRef SignatureDefLocation
CLI Q RangeCheckEQ Role
ERR MUR
Study Data
ConMed Drug_TRT Pharm01Demog PhyEx
AE ConMed Drug_TRTAudit Pharm01Demog PhyEx ClinicalData
ReferenceData
Futu
re D
irect
ion
![Page 25: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/25.jpg)
AERS II RFI Functions
Pre-marketing Risk (*Guid.) Assessment
Risk ( *Guid.) Minimization Action Plan
NDA Clinical Safety Review GRP (*Guid.)
PV Practices & PE (*Guid.)
Assessment1) Safety data
monitoring2) Data Analysis
capabilities3) Data mining
activities4) Report generation5) Automated
monitoring6) Alarm functionality7) Early detection of AE
reaction patterns8) Enhance signal
detection analysis 10) Complex query and
data mining (eg –passive signals of drug-drug interaction, polytherapy, poly pharmacy)
1) Pre clinical tox data and reports
2) Clinical pharmacology and PK
3) Temporal relationships
4) Population diversity5) Drug – drug
interaction6) Demographic
relationships7) Disease interactions
and intercurrentevents
8) Dietary supplements9) Dose effects10) Laboratory safety
data11) Coding12) ICSRs and PSURs
1) Benefit risk management (BRM) plan
2) Tools to minimize and assess risk
3) Strategic safety program
- education- controlled
prescribing- prescription
monitoring4) and re-assessment
of BRM updates5) performance linked
access to laboratory safety data, etc
6) Reminder systems & prompts
7) Is risk- predictable- preventable- reversible- time limited - continuous- cumulative - when risk is highest
1) Establish data quality
2) Standard data content
P R deaths O SAEs F ADOsI AEsL dropoutsE (frequency & count)
3) Laboratory safety data
- central tendency- outliers & - shifts
4) Vital signs5) ECG(waveform)6) Pre-clinical data and
results7) Demography &
extent ofexposure
8) Predictive factors- dose dependency- time dependency-demography
interactions- drug and disease
interactions- exploration of drug-
drug interaction
1) Good reporting practices
-case reports -case series
assessingcausality
-summary descriptive
analysis2) Data Mining
- product & event comb.
-spontaneous reports
- relative risk/odds ratios
- biological effects- controlled safety
findings- marketing
experience- severity
3) Safety SignalInvestigation
4) Signal detection rates and incidence5) Background rates(external data sources)6) PE studies
- safety- registries- surveys- literature
*FDA Guidance
![Page 26: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/26.jpg)
![Page 27: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/27.jpg)
FDA Pharmacovigilance PathPost Market Approval
(PV) Post Market Approval
(5)Quantitative Assessment
Adjusted R AnalysisSTD SafetyDomains in E2B
and STDM
(1)Case Study
(ICSR / Expected Safety Report
(3)Post-Market Approval
AERS (drug v.
pharmacological class)
Observed v. ExpectedAdjusted R Analysis
Target Drug InducedDrug-Drug InducedCo-MurbidityIntercurrent EventDrug x Co-EventMasked / CloakedFalse PositiveSOC / PT
(4)Pre-Market
ApprovalClinical database
(placebo v. active)Observed v. ExpectedAdjusted R Analysis
(2)Case Series(Qualitative Assessment)
Dose / Exposure DemographyLaboratory safety dataBiomarkerDechallenge / ChallengeMechanism
![Page 28: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/28.jpg)
Assessment of the Drug Safety
EpidemiologyData
+Pre-Clinical Safety
Data
Clinical TrialData
MedWatch/SRS/AERS
&Investigators
Reports
PharmacoStatistical Modeling
![Page 29: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/29.jpg)
Predictable Drug Safety
• Dose Linear/Dose Proportional• Across the entire patient population• Good structure/activity relationship• Relational to clearance and metabolism
![Page 30: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/30.jpg)
Unpredictable Drug Safety
• Idiopathic• Idiosyncratic• Iatrogenic
![Page 31: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/31.jpg)
Standards and Systems
• MedDRA• CDISC• MedWatch• AERS• SNOMED
![Page 32: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/32.jpg)
Era of Polytherapy/PolyPharmacy
• Drug/drug interaction• Passive signals
Must have open global databases populated with standard data to intuitively predict untoward effects
![Page 33: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/33.jpg)
DirectedSignal
DetectionData
MiningAND
![Page 34: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/34.jpg)
Data Mining Analytics
MGPS GPS PRR
BCPNN ROR
![Page 35: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/35.jpg)
SRS Databases
SRS/AERS VAERS MAUDE WHO-IDME
![Page 36: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/36.jpg)
Sentinel Considerations of A Signal
• Target Drug Event (drug-event pair)• Drug – Drug Interaction• Co-Morbitity• Intercurrent Event• Passive Signals (Drug/Drug &
Disease/Event)• Masked/Cloaked• False Positive
![Page 37: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/37.jpg)
![Page 38: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/38.jpg)
E2B FDA
CDISCStandard
![Page 39: Harmonizing CDISC Submission Models and Pharmacovigilance](https://reader034.vdocument.in/reader034/viewer/2022051600/627fb659c6fc47366538c9e6/html5/thumbnails/39.jpg)