HL7 Version 3 Laboratory Result-based Adverse Event Assessment Message Specifications RCRIM Technical Meeting September 18, 2007 Jennifer Neat Project.

Slides:



Advertisements
Similar presentations
Project Quality Plans Gillian Sandilands Director of Quality
Advertisements

Helmut König, Siemens Medical Solutions
Longitudinal Coordination of Care (LCC) Pilots Template Insert the Name of Your Pilot / Organization Here MM/DD/YYYY.
The Public Health Conceptual Data Model HL7 RIM Harmonization May 2000.
Depicting EHRs Immunization capability HL7 WGM – September 11, 2006 Immunization Storyboard project update.
HL7 Version 3 Adverse Event Assessment CMET Specification Jennifer Neat Project Leader, City of Hope August 7, 2007.
RCRIM September 2007 Working Group Meeting Clinical Research Filtered Query Service Tuesday, September 18, 2007 (Q4) Sheraton Hotel Atlanta, GA.
HDF: HL7 Methodology Ioana Singureanu M&M co-chair, HDF Editor Eversolve, LLC.
1 HL7 Jan 2007 Working Group MeetingsPharmacogenomics Update RCRIM TC Philip M. Pochon Covance Enterprise Architecture.
Joint TC Meeting: EHR – RCRIM RCRIM Overview HL7 Working Group Meeting January, 2007 Presented by: Ed Tripp Program Director, eSubmissions Abbott (RCRIM.
CDISC Content to Message HL7 Development Overview Jason Rock
1 HL7 Jan 2010 Working Group MeetingsCTLAB Pharmacogenomics Update JOINT RCRIM and CG Session CTLAB Message Pharmacogenomics Results Overview.
HL7 Working Group Meeting Orlando, Florida 14 January
Regulated Product Submissions R1 Overview January 12 th HL7 WGM Jason Rock
BRIDG Overview Clinical Observation Interoperability March 18, 2008.
Blood Bank V3.
GEORGIA PERF0RMANCE MANAGEMENT FOR EMPLOYEES 2008
FIPA Interaction Protocol. Request Interaction Protocol Summary –Request Interaction Protocol allows one agent to request another to perform some action.
Update on CDISC Terminology Activities RCRIM Vocab Session (Q4) 14 January 2009, Orlando Bron Kisler (CDISC)
SAFER – HEALTHIER – PEOPLE CDC NEDSS Drug Reaction Notification 2 October Page: 1 Notification Messaging to Support FDA Building an HL7 Version.
IRB Determinations 1. AAHRPP Site Visit Results Site visitors observed a real commitment to human subject protections Investigator and research staff.
Capturing and Reporting Adverse Events in Clinical Research
Analysis Concepts and Principles
INTRODUCTION.- PROGRAM EVALUATION
3/18/19990© 1999, Health Level Seven, Inc. Introduction: Vocabulary domains Marital Status –single (never married) –married –divorced –separated “Vocabulary”
THE NEW TEXAS CORE CURRICULUM (OCTOBER 27, 2011).
Unrestricted CBP ITDS CONOPS Trans Border Working Group Boston April 13, 2010.
DCB New Grantee Workshop: Post-Award Administration of Grants Brett Hodgkins Team Leader National Cancer Institute Office of Grants Administration.
Adverse Event/Unanticipated Problems Policy and Procedures November 2007.
Alice Chen, MD, FACP Investigational Drug Branch, CTEP, DCTD National Cancer Institute CTCAE Version 4.
RCRIM Projects: Protocol Representation and CDISC Message(s) January 2007.
Call: Wed, 10/05/11 4-5pm ET Agenda: 4:00 – 4:05 Welcome, Riki Merrick, co-lead [Note: attendance will be taken by livemeeting login] 4:05 – 4:15 Initiative.
Regulated Product Submission HL7 Update Wednesday January 10 th, 2007 Jason Rock
Networking and Health Information Exchange Unit 5b Health Data Interchange Standards.
DCB New Grantee Workshop: Post-Award Administration of Grants Brett Hodgkins Team Leader National Cancer Institute Office of Grants Administration.
The NCI Central IRB Initiative Third Annual Medical Research Summit Washington, D.C. March 2003.
Message Development Framework (MDF) Is a Methodology for building HL7 models Is a description for defining HL7 standard messages Full instruction.
Investigator’s Meeting
CDISC©2009 February CDISC INTRAchange Carey Smoak Device Team Leader Li Zheng Submission Data Standards Team Member Thurday, April 2, 2009.
EHR Standards Project DSTU Basic Observations Professional Service July 05, 2006 Webcast.
Data Segmentation for Privacy November 16 th, 2011.
Title V, Preliminary Completeness Review. What do I need to do?  I need to find out if the application contains the required information.  Initial Title.
RCRIM September 2007 Working Group Meeting eDCI Tuesday, September 18, 2007 (Q4) Sheraton Hotel Atlanta, GA.
How to Start An Industry Sponsored Clinical Trial
Commentary: The HL7 Reference Information Model as the Basis for Interoperability George W. Beeler, Jr. Ph.D. Co-Chair, HL7 Modeling & Methodology.
Public Health Reporting Initiative January 4, 2012.
HL7 Version 3.0 Mini-Tutorial Helen Stevens Senior Project Manager –Web Solutions Office McKessonHBOC - Information Technology Business.
HL7 Version 3 Veli BICER. Agenda HL7 Problems with Version 2.x HL7 Models Use Case Model Information Model Interaction Model Message Model.
The FDES revision process: progress so far, state of the art, the way forward United Nations Statistics Division.
1 CDISC HL7 Project FDA Perspective Armando Oliva, M.D. Office of Critical Path Programs FDA.
Ballot Reconciliation Meeting Notes 1.Ballot Tally & Reconciliation a.CTLaboratory Release 3 / HL7 Version 3 Standard: Periodic Reporting of Clinical Trial.
Subject Registrations Adverse Events Subject Registrations Biospecimens Lab Results IN: 1. Lab Results OUT: 1. Subject Registrations 2. Clinical Notes.
BRIDG Update RCRIM Working Group Meeting Rio de Janeiro 17 May 2010 Julie Evans Senior Director, Technical Services, CDISC Wendy Ver Hoef Senior Analyst,
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
May 2007 CTMS / Imaging Interoperability Scenarios March 2009.
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.
© Copyright IBM 2007DIA ERS SIAC Presentation, January 2008 The HL7 RPS and SPL Standards - A High Level View Terry Hardin Sr. IT Architect Emerging Software.
Labs Early Adoption Program Template Insert the Name of Your Implementation / Organization Here MM/DD/YYYY.
Structured Data Capture (SDC) FHIR SDC Pilots Template
Concepts Statement No. 3 Communication Methods in General Purpose External Financial Reports That Contain Basic Financial Statements Issued: April 2005.
Submission Standards: The Big Picture Gary G. Walker Associate Director, Programming Standards, Global Data Solutions, Global Data Management.
Existing Service Specifications
Clinicaltrials.gov Update
FDA’s IDE Decisions and Communications
Pharmacovigilance in clinical trials
Overview of the FEPAC Accreditation Process
Software Measurement Process ISO/IEC
Clinical Observation Interoperability March 18, 2008
Use of Electronic Tools for the Dissemination of Comments
HL7 Working Group Meeting RCRIM Technical Committee
Presentation transcript:

HL7 Version 3 Laboratory Result-based Adverse Event Assessment Message Specifications RCRIM Technical Meeting September 18, 2007 Jennifer Neat Project Leader, City of Hope Abdul Malik Shakir HL7 Facilitator, Shakir Consulting

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification2 of 22 Introduction Project Scope Develop an HL7 v3 draft standard for trial use messaging specification that supports the unique data requirements for initial laboratory result-based adverse event (AE) assessment information. Objectives Met Evaluated existing message structures and identified the HL7 v3 CT Laboratory Message DSTU as an appropriate structure for laboratory result-based AE assessment messaging specifications Defined an AE Assessment CMET as an optional structure within the revised CT Laboratory Message Identified the AE Assessment CMET vocabulary requirements Identified the required messaging interactions

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification3 of 22 Regulated Studies Domain Summary of Clinical Trial Interactions in the Regulated Studies Domain

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification4 of 22 Project Scope in Context Revised Summary Clinical Trial Interactions to include: AE Assessment Request AE Assessment Response

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification5 of 22 Storyboard Overview Laboratory test results can indicate a patient has experienced/is experiencing an adverse event (AE). For clinical trials mandating use of a grading criteria for assessing laboratory result-based AEs, laboratory test results may be transmitted to an automated AE assessment service. The AE assessment service evaluates the laboratory results subject to quantitative AE assessment, based on the specified grading criteria, such as the National Cancer Institute (NCI) Common Terminology Criteria for Adverse Events v3.0 (CTCAE). An initial / first-level assessment is performed to determine the presence and severity of an AE(s). Upon completion, the laboratory test results and associated AE assessment outcomes are transmitted to a clinical information system within the clinical research environment. Subsequent investigation into the patients condition must be conducted within the clinical research environment in order to determine, in part, the AE reporting requirements.

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification6 of 22 Storyboard CT Laboratory Result-based Adverse Event Assessment (PORT_SN03000x) Narrative A laboratory facility has performed one or more tests on a patient specimen and the results of the testing are available electronically for review and further evaluation within the clinical research environment. A request is sent to an automated AE assessment service to evaluate the laboratory test results. Each test result that is subject to quantitative AE assessment is evaluated for the presence and severity of an adverse event, and the test result is appended with this AE assessment outcome data. The AE assessment service sends a response message containing the original and appended information.

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification7 of 22 Interaction Diagram Purpose The storyboard demonstrates an initial / first-level evaluation of clinical trial laboratory results subject to quantitative adverse event assessment.

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification8 of 22 Interaction Design Elements & Descriptions: Application Roles ClinicalTrial Observation Order Global Placer (PORT_AR03000x) An application that is capable of notifying another application about a significant clinical trial observation event and expects the receiver to take action. Adverse Event Assessment Observation Fulfiller (PORT_AR03000y) An application that is capable of receiving an adverse event (AE) assessment request from a Placer application. The Adverse Event Assessment Observation Fulfiller is responsible for evaluating clinical trial laboratory results and deriving AE assessment outcome data. The fulfiller is also responsible for initiating communication of this data to the Clinical Observation Event Global Tracker. ClinicalTrial Observation Event Global Tracker (PORT_AR010001UV01) The application role includes the behaviors needed to receive and appropriately manage notifications from another system about any change of a Clinical Trial Observation Event. This includes receiving information about status changes of that event and receipt of observation event information once that is available.

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification9 of 22 Interaction Design Elements & Descriptions: Trigger Event Agreed Transmission Criterion Attained – CT (PORT_TE010001UV01) An external event has occurred which marks a condition under which the sender and receiver have agreed that data is to be exchanged. Such events are often defined time points (e.g. end of business day/week/month). In a clinical trial, these may be significant milestones (e.g. subject enrolled; subject completes phase; all subjects complete phase; end of study). CT Laboratory Results Adverse Event Assessment Request (PORT_IN03000x) This interaction supports communication of clinical laboratory results to an AE assessment service. It is expected that the receiving application will initiate the CT Laboratory Results AE Assessment Response interaction (PORT_IN03000y) containing the original clinical laboratory results, in addition to the outcome of the initial / first-level quantitative adverse event assessment. CT Laboratory Results Adverse Event Assessment Response (PORT_IN03000y) This interaction supports communication of clinical laboratory results with the outcome of the initial / first-level quantitative adverse event assessment to a clinical information system within the clinical research environment / study site.

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification10 of 22 Interaction Design Elements & Descriptions: Interactions CT Laboratory Results Adverse Event Assessment Request (PORT_IN03000x) This interaction supports communication of clinical laboratory results to an AE assessment service. It is expected that the receiving application will initiate the CT Laboratory Results AE Assessment Response interaction (PORT_IN03000y) containing the original clinical laboratory results, in addition to the outcome of the initial / first-level quantitative adverse event assessment.

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification11 of 22 Interaction Design Elements: Interactions Contd CT Laboratory Results Adverse Event Assessment Response (PORT_IN03000y) This interaction supports communication of clinical laboratory results with the outcome of the initial / first-level quantitative adverse event assessment to a clinical information system within the clinical research environment / study site.

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification12 of 22 Lab-Based Adverse Event Assessment Domain Analysis Model Current CT-Lab Message Content Proposed New CMET Content

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification13 of 22 BRIDG-Derived Domain Analysis Model

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification14 of 22 Current CT Laboratory Message RMIM

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification15 of 22 CMET Addition to the CT-Laboratory Message

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification16 of 22 Proposed Changes to the CT-Laboratory Message 1.Change datatype of Range.value from PQ to IVL. 2.Add AdverseEventAssessment CMET with an ActRelationship to Base Unitary Result 1.Range.value datatype has been changed from PQ to IVL 2.Add AdverseEventAssessment CMET with an ActRelationship to Base Unitary Result

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification17 of 22 CMET RMIM

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification18 of 22 CMET RMIM Class Definitions AdverseEventAssessment The process of evaluating a clinical finding to detect the presence and severity of an abnormal condition, and assigning the corresponding adverse event category, term, and grade. AssessmentException This class represents one of two possible observation outcomes of an AdverseEventAssessment. It is a message provided to indicate that an adverse event assessment could not be executed or completed and to identify the reason for the failure. AdverseEventGrade This class represents one of two possible observation outcomes of the AdverseEventAssessment. It is the severity of an adverse event based on a specified assessment scale. GradeAnnotation Additional information provided about a grade that must be considered to determine the final grade.

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification19 of 22 Hierarchical Message Description

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification20 of 22 Vocabulary Requirements Vocabulary requirements have been identified in the following areas: External reference to a new code system Common Terminology Criteria for Adverse Events v3.0 (CTCAE): contains the adverse event category, adverse event term and adverse event short term that may be used to describe an adverse event. New value sets for existing domains Adverse Event Assessment Method: provides additional information about the means used to arrive at the assessment result. Adverse Event Assessment Exception: provides the reason an adverse event assessment could not be executed or completed Adverse Event Grade: indicates the level of severity for an adverse event, including the concept of Not Present. Adverse Event Grade Annotation: provides additional information about an adverse event assessment grade, which must be considered before determining the final grade. Focused discussion regarding these vocabulary requirements will be held during the working group meeting. The session is to be determined.

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification21 of 22 Motions RCRIM TC approval for the submission of the following items for RIM harmonization: New code system Common Terminology Criteria for Adverse Events v3.0 (CTCAE) New value sets AdverseEventAssessmentMethod AdverseEventAssessmentException AdverseEventGrade AdverseEventGradeAnnotation RCRIM TC approval for the submission of the following items for inclusion in the January 2008 ballot as a DSTU: Adverse Event Assessment CMET Revised HL7 v3 CT Laboratory Message New application roles ClinicalTrial Observation Order Global Placer Adverse Event Assessment Observation Fulfiller New interactions CT Laboratory Results Adverse Event Assessment Request CT Laboratory Results Adverse Event Assessment Response

September 18, 2007HL7 V3 Lab-Based Adverse Event Assessment Message Specification22 of 22 Next Steps