Data Provenance All Hands Community Meeting February 5, 2015.

Slides:



Advertisements
Similar presentations
Data Provenance Community Meeting January 15, 2015.
Advertisements

S&I Data Provenance Initiative Questions for the HITSC on the S&I Data Provenance Initiative November 18, 2014 Julie Anne Chua, PMP, CAP, CISSP Office.
Standards and Harmonization Data Provenance S&I Framework December 4 th,
Data Provenance Community Meeting December 18, 2014.
Data Provenance All Hands Community Meeting April 30th, 2015.
Data Provenance Initiative Launch April 10 th, 2014 Joy Pritts, JD - Chief Privacy Officer, ONC Julie Chua PMP, CAP, CISSP - Information Security Specialist,
Data Provenance Community Meeting November 13, 2014.
Automate Blue Button Initiative Push Workgroup Meeting January 7, 2013.
Data Provenance Community Meeting December 11, 2014.
Data Access Framework (DAF) All Community Meeting September 4th, 2013.
Data Provenance Information Interchange Sub-Workgroup March 12 th, 2015.
Data Provenance Information Interchange Sub-Workgroup March 19 th, 2015.
Data Provenance Information Interchange Sub-Workgroup March 26 th, 2015.
Data Provenance All Hands Community Meeting February 19, 2015.
Data Access Framework All Hands Community Meeting June 25, 2014.
Data Provenance Community Meeting September 4 th, 2014.
EHR-S Functional Requirements IG: Lab Results Interface Laboratory Initiative.
Data Provenance –Use Case (Discovery) Ahsin Azim Nisha Maharaja Presha Patel 1.
Data Provenance Community Meeting May 1 st, 2014.
Data Segmentation for Privacy Agenda All-hands Workgroup Meeting May 9, 2012.
Dave Iberson-Hurst CDISC VP Technical Strategy
Data Provenance All Hands Community Meeting May 21 st, 2015.
Data Provenance Community Meeting May 22 nd, 2014.
Data Access Framework All Hands Community Meeting June 18, 2014.
Data Provenance All Hands Community Meeting May 7 th, 2015.
Data Provenance Tiger Team May 27 th, 2014 Johnathan Coleman Johnathan Coleman - Initiative Coordinator Lynette ElliottLynette Elliott – Tiger Team Support.
Data Provenance Community Meeting September 25 th, 2014.
Data Provenance –Use Case (Discovery) Ahsin Azim Nisha Maharaja Presha Patel 1.
Data Provenance All Hands Community Meeting April 2 nd, 2015.
Data Provenance Community Meeting August 21st, 2014.
Data Provenance Community Meeting November 6, 2014.
DPROV System Requirements Sub Work Group February 27 th, 2014.
Data Provenance –Use Case (Discovery) Ahsin Azim– Use Case Lead Presha Patel – Use Case Lead 1.
Data Provenance Tiger Team May 9 th, 2014 Johnathan Coleman Johnathan Coleman - Initiative Coordinator Lynette ElliottLynette Elliott – Tiger Team Support.
Data Provenance Community Meeting September 11 th, 2014.
Electronic Submission of Medical Documentation (esMD) Electronic Determination of Coverage (eDoC) Workgroup August 21, 2013.
Data Provenance Tiger Team May 19 th, 2014 Johnathan Coleman Johnathan Coleman - Initiative Coordinator Lynette ElliottLynette Elliott – Tiger Team Support.
Data Provenance –Use Case (Discovery) Ahsin Azim– Use Case Lead Presha Patel – Use Case Lead 1.
Data Provenance Community Kick Off April 24 th, 2014.
Data Provenance All Hands Community Meeting June 11, 2015.
Data Access Framework All Hands Community Meeting 1 November 4, 2015.
Data Access Framework All Hands Community Meeting April 2, 2014.
Data Provenance All Hands Community Meeting April 23rd, 2015.
Data Provenance Tiger Team June 16, 2014 Johnathan Coleman Johnathan Coleman - Initiative Coordinator Lynette ElliottLynette Elliott – Tiger Team Support.
Data Provenance Community Meeting May 15 th, 2014.
Data Provenance All Hands Community Meeting April 9th, 2015.
Data Provenance Community Meeting November 13, 2014.
Data Access Framework All Hands Community Meeting 1 November 18, 2015.
Data Provenance Community Meeting July 17 th, 2014.
Data Provenance Community Meeting November 6, 2014.
Data Access Framework All Hands Community Meeting April 9, 2014.
Structured Data Capture (SDC) All Hands Meeting December 10, 2015.
Data Provenance All Hands Community Meeting May 28 th, 2015.
Data Access Framework All Hands Community Meeting April 16, 2014.
Data Provenance –Use Case (Discovery) Ahsin Azim– Use Case Lead Presha Patel – Use Case Lead 1.
Data Provenance All Hands Community Meeting March 5, 2015.
Data Provenance All Hands Community Meeting February 19, 2015.
Data Provenance All Hands Community Meeting June 18, 2015.
Data Provenance Tiger Team June 2, 2014 Johnathan Coleman Johnathan Coleman - Initiative Coordinator Lynette ElliottLynette Elliott – Tiger Team Support.
Data Provenance All Hands Community Meeting February 26, 2015.
Data ccess Framework All Hands Community Meeting June 11, 2014.
Data Access Framework All Hands Community Meeting 1 May 4, 2016.
Data Access Framework All Hands Community Meeting 1 April 20, 2016.
Data Access Framework All Hands Community Meeting April 16, 2014.
Data Provenance Community Meeting June 19 th, 2014.
Data Access Framework (DAF) All Community Meeting July 31, 2013.
Data Provenance All Hands Community Meeting May 19th, 2016.
Data Access Framework All Hands Community Meeting 1 March 23, 2016.
Data Provenance Tiger Team April 28 th, 2014 Johnathan Coleman Johnathan Coleman - Initiative Coordinator Bob Yencha Bob Yencha – Subject Matter Expert.
Dave Iberson-Hurst CDISC VP Technical Strategy
Presentation transcript:

Data Provenance All Hands Community Meeting February 5, 2015

Meeting Etiquette Please mute your phone when you are not speaking to prevent background noise. – All meetings are recorded. Please do not put your phone on hold. – Hang up and dial back in to prevent hold music. Please announce your name before speaking Use the “Chat” feature to ask questions or share comments. – Send chats to “All Participants” so they can be addressed publicly in the chat, or discussed in the meeting (as appropriate). 2 Click on the “chat” bubble at the top of the meeting window to send a chat.

Agenda TopicTime Allotted Announcements Update on Task Force Recommendations 15 minutes CDISC Operational Data Model Presentation by Sam Hume15 minutes

Announcements Task Force Recommendations Update 4

Updated Candidate Standards #TransactionContent and Structure Terminology and Code Values - DP TransportSecurity 1 a) Start Point sends clinical data with provenance information to End Point *C-CDA *CDA R2 *W3C PROV: PROV-AQ, PROV- CONSTRAINTS, PROV-XML *Personal Health Record System Functional Model *HL7 EHR Records Management and Evidentiary Support (RM-ES) Functional Model, Release 1 *ISO/HL7 EHR System Functional Model Release 2 *HL7 EHR Lifecycle Model (2008) *HL7 Record Lifecycle Event Metadata using FHIR (project underway 2014) *HL7 V.2.x *ISO Health Informatics: Trusted End-to-End Information Flows *HL7 FHIR DSTU Release 1.1 Provenance Resource *HL7 Implementation Guide for CDA® Release 2: Data Provenance, Release 1 – US Realm *HL7 Implementation Guide for CDA®, Release 2: Consent Directives, Release 1 *HL7 EHR Interoperability Model DSTU (2007) *HL7 Implementation Guide for CDA Release 2: Reference Profile for EHR Interoperability DSTU (2008) * CDISC Operational Data Model *HL7 V.2/ V.3 Vocabulary & Terminology Standards *Representation State Transfer (RESTful) *Cross Enterprise Document-Sharing XDS *SOAP *HL7 Implementation Guide: Data Segmentation for Privacy (DS4P), Release 1 * HL7 Health Care Privacy and Security Classification System, Release 1 (HCS) *HL7 Version 3 Standard: Privacy, Access and Security Services (PASS) *HL7 Version 3 Standard: Privacy, Access and Security Services; Security Labeling Service, Release 1 (SLS) *HL7 Implementation Guide for CDA® Release 2: Digital Signatures and Delegation of Rights, Release 1 2 a) Start Point sends clinical data to transmitter with provenance information 2 b) Transmitter send clinical data to end point with provenance information 3 a) Start Point sends clinical data to assembler/composer with provenance information 3 b) Assembler/composer compiles clinical data which is sent to end point with provenance information

CDISC Operational Data Model Sam Hume February 5 th, 2015

7

© CDISC 2012 The CDISC Operational Data Model and Data Provenance Sam Hume

9 Operational Data Model Vendor neutral XML Schema provides standard syntax for interchange and archive of general Clinical Trials information Defines structure, not content Supports 21 CFR Part 11 compliance and FDA Guidance on Computerized Systems Enables exchange of study metadata and data or updates between systems Archives electronic data at sites and supports remote monitoring 9

10 ODM Use Cases Data transmission from 3 rd party data providers to sponsors Clinical data archiving Automated set up of EDC / CDM systems Clinical data standards metadata repositories Electronic Health Record Integration Submission of SDTM and ADaM metadata and data Proposed replacement for SAS XPT for submissions

ODM Element 11 ODM Study FileOID attributes ClinicalData Association ID ReferenceData

ODM Element 12 ODM Study FileOID attributes ClinicalData Association ID ReferenceData MetaDataData & Audit

SubjectData Element 13 SubjectData Audit Signature InvestigatorRef SiteRef Annotation StudyEventData FormData ItemGroupData ItemData Audit Signature Annotation Audit Signature Annotation ArchiveLayoutRef Audit Signature Annotation SubjectKey

AuditRecord Element 14 ItemData AuditRecord Signature MeasurementUnitRef Annotation IsNull UsedImputationMethod UserRef LocationRef DateTimeStamp ReasonForChange SourceID

ODM & Audit Trail 15 WhatWhyWho When Slide courtesy Dave Iberson-Hurst, Assero Where How ItemDef metadata

16 Traceability and the Audit Trail

Signature Element 17 ItemData AuditRecord Signature MeasurementUnitRef Annotation IsNull UserRef LocationRef DateTimeStamp CryptoBindingManifest SignatureRef Signature also includes the Meaning and Legal Reason for the signature

ODM links to EHR: Retrieve Form for Data Capture (RFD) 18 ODM & XForms ODM Site Sponsor 2. Request Form 1.Form Definition 4. Submit Data 5. Archive Data (eSource!) Offline: Use ODM metadata to create form Form Archiver 3. Enter Data EHR CDM Single Entry Double Use

Automated Setup of EDC/eCRF systems ODM Metadata can be used to configure data collection tools eCRF systems: Numerous vendors using ODM eDiary/ePRO systems –Used ODM for configuration purposes and data transfer EHR systems – Medical form standard for a large EHR and clinical research data model repository of 3,320 medical forms ( 19 ODM XML MetaData

ODM Summary ODM is a mature standard – Nearly 20 years of development – Used by numerous software and service providers – Global use (e.g. US, Europe, Japan) – ODM Certification is available ODM is remarkably flexible – Medical forms repository / EHR integration – Interoperability with HL7 CDA has been demonstrated – Meets requirements for HHS/ONC Structured Data Capture forms –Carries complete audit trail (provenance) information (fulfills 21CFR11 requirements) –Allows for remote monitoring or auditing, including audit trail for traceability from electronic source 20

Next Steps Next All Hands meeting is Thursday, February 5, 2015 –

Support Team and Questions Please feel free to reach out to any member of the Data Provenance Support Team: Initiative Coordinator: Johnathan Coleman: OCPO Sponsor: Julie Chua: OST Sponsor: Mera Choi: Subject Matter Experts: Kathleen Conner: and Bob Yencha: Support Team: – Project Management: Jamie Parker: – Standards Development Support: Perri Smith: and Atanu Sen: – Support: Apurva Dharia: Rebecca Angeles: and Zach May: 22