Hl7 and the Clinical Genomics Work Group

Slides:



Advertisements
Similar presentations
Depicting EHRs Immunization capability HL7 WGM – September 11, 2006 Immunization Storyboard project update.
Advertisements

HL7 Quality Reporting Document Architecture DSTU
Clinical Genomics Domain Analysis Model Joyce Hernandez Mukesh Sharma.
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.
1 Intermountain Healthcare Clinical Genetics Institute Marc S. Williams, M.D. Director Grant M. Wood Senior IT Strategist Introduction to HL7 Clinical.
1 HL7 Jan 2010 Working Group MeetingsCTLAB Pharmacogenomics Update JOINT RCRIM and CG Session CTLAB Message Pharmacogenomics Results Overview.
HL7 Clinical Genomics and Structured Documents Work Groups CDA Implementation Guide: Genetic Testing Report DRAFT PROPOSAL Amnon Shabo (Shvo), PhD
1 GEOSS Monitoring & Evaluation. 2 1st GEOSS M&E WG meeting outcomes Agreed on 1.the final draft of Terms of Reference for the M&E WG 2.The plan for delivery.
IHIC 2011 – Orlando, FL Amnon Shabo (Shvo), PhD HL7 Clinical Genomics WG Co-chair and Modeling Facilitator HL7 Structured Documents WG.
ELTSS Alignment to Nationwide Interoperability Roadmap DRAFT: For Stakeholder Consideration in response to public comment.
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
Longitudinal Coordination of Care (LCC) Workgroup (WG)
Clinical Genomics Work Group (HL7) Mukesh Sharma Washington University in St. Louis.
Catherine Hoang Ioana Singureanu Greg Staudenmaier Detailed Clinical Models for Medical Device Domain Analysis Model 1.
Quality Improvement/ Quality Assurance Amelia Broussard, PhD, RN, MPH Christopher Gibbs, JD, MPH.
Mpeg-21 and Medical data A strategy for Tomorrow ’ s EMR.
© 2013 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Protocols and the TCP/IP Suite
Electronic Data Interchange (EDI)
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
3/18/19990© 1999, Health Level Seven, Inc. Introduction: Vocabulary domains Marital Status –single (never married) –married –divorced –separated “Vocabulary”
Query Health Business Working Group Kick-Off September 8, 2011.
HL7 Webinar: Mobile Health Chuck Jaffe Austin Kreisler John Quinn 19 March 2012.
HL7 HL7  Health Level Seven (HL7) is a non-profit organization involved in the development of international healthcare.
HITSP’s Scope  The Panel’s mission is to assist in the development of a Nationwide Health Information Network (NHIN) by addressing the standards-related.
1 Health Level Seven (HL7) Report Out Population Science and Structured Documents Workgroup (SDWG) Riki Ohira September 22, 2011.
Standards Analysis Summary vMR – Pros Designed for computability Compact Wire Format Aligned with HeD Efforts – Cons Limited Vendor Adoption thus far Represents.
Clinical Genomics Work Group (HL7) Mukesh Sharma Washington University in St. Louis June 16, 2011.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Networking and Health Information Exchange Unit 6b EHR Functional Model Standards.
Interoperability Framework Overview Health Information Technology (HIT) Standards Committee June 24, 2010 Presented by: Douglas Fridsma, MD, PhD Acting.
Clinical Genomics Joint with RCRIM Amnon Shabo Joyce Hernandez Mukesh Sharma.
DICOM and ISO/TC215 Hidenori Shinoda Charles Parisot.
1 HL7 RIM Barry Smith
MED INF HIT Integration, Interoperability & Standards ASTM E-31 January 14, 2010 By Imran Khan.
Briefing: HL7 Working Group Meeting Update for the VCDE Community Dianne M. Reeves Associate Director, Biomedical Data Standards NCI CBIIT VCDE Meeting.
Examining the Effective Use of HL7v3 Messaging “ Where the Rubber Meets the Road” Introduction for an Open Dialogue on: Issues in Communicating the Real.
1 LS DAM Overview and the Specimen Core February 16, 2012 Core Team: Ian Fore, D.Phil., NCI CBIIT, Robert Freimuth, Ph.D., Mayo Clinic, Elaine Freund,
HL7 v3 Clinical Genomics – Overview The HL7 Clinical Genomics Work Group Prepared by Amnon Shabo (Shvo), PhD HL7 Clinical Genomics WG Co-chair and Modeling.
Networking and Health Information Exchange Unit 5b Health Data Interchange Standards.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 3b National and International Standards Developing.
S&I Integration with NIEM (DRAFT) Standards Development Support June 8, 2011.
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
Introduction to HL7 Version 3 W. Ed Hammond February 25, 2008.
S&I Public Health Education Series: Data Provenance July 9th, 2014 Johnathan Coleman Initiative Coordinator – Data Provenance ONC/OCPO/OST (CTR)
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
HL7 Clinical-Genomics SIG: Tissue-Typing Models and a Reusable Genotype Module HL7 V3 Compliant IBM Research Lab in Haifa together with Hadassah University.
Electronic Submission of Medical Documentation (esMD)
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.
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
CDA Overview HL7 CDA IHE Meeting, February 5, 2002 Slides from Liora Alschuler, alschuler.spinosa Co-chair HL7.
CCD and CCR Executive Summary Jacob Reider, MD Medical Director, Allscripts.
1 LS DAM Overview August 7, 2012 Current Core Team: Ian Fore, D.Phil., NCI CBIIT, Robert Freimuth, Ph.D., Mayo Clinic, Mervi Heiskanen, NCI-CBIIT, Joyce.
International Workshop 28 Jan – 2 Feb 2011 Phoenix, AZ, USA Modeling Standards Activity Team Model-based Systems Engineering (MBSE) Initiative Roger Burkhart.
Informatics for Scientific Data Bio-informatics and Medical Informatics Week 9 Lecture notes INF 380E: Perspectives on Information.
Copyright © 2009 by The McGraw-Hill Companies, Inc. All Rights Reserved. McGraw-Hill/Irwin Chapter 2 Clinical Information Standards – Unit 3 seminar Electronic.
United States Health Information Knowledgebase: An Online Metadata Registry J. Michael Fitzmaurice Agency for Healthcare Research and Quality ANSI HITSP.
Structured Data Capture (SDC)
SNOMED CT Education SIG: Strategic Plan Review
Current Framework and Fundamental Concepts
IHE Eye Care Process and Timeline
Unit 5 Systems Integration and Interoperability
Electronic Health Information Systems
Structured Data Capture (SDC)
, editor October 8, 2011 DRAFT-D
Component 9 - Networking and Health Information Exchange
Component 9 - Networking and Health Information Exchange
Presentation transcript:

Hl7 and the Clinical Genomics Work Group Mukesh Sharma Washington University in St. Louis

Agenda HL7 introduction Reference Information Model Clinical Genomics Work Group Clinical Genomics Work Group Accomplishments Gene Expression DAM Upcoming Activities Useful Links

Health Level 7 HL7 was founded in 1987 and accredited in 1994 by the American National Standards Institute (ANSI). Health Level Seven (HL7), is an all-volunteer, not-for-profit organization involved in development of international healthcare standards. HL7 is also used to refer to some of the specific standards created by the organization (e.g., HL7 v2.x, v3.0, HL7 RIM) standards Source: http://en.wikipedia.org/wiki/HL7

What does the name mean? Health Level 7 symbolizes the seventh layer of the International Standards Organization (ISO) Communications Model: 1. Physical: Connects the entity to the transmission media 2. Data Link: Provides error control between adjacent nodes 3. Network: Routes the information in the network 4. Transport: Provides end-to-end communication control 5. Session: Handles problems that are not communication issues 6. Presentation: Converts the information 7. Application: Provides different services to the applications Source: http://www.hl7.com.au/FAQ.htm

Health Level 7 HL7 and its members provide a framework (and related standards) for the exchange, integration, sharing, and retrieval of electronic health information. v2.x of the standards, which support clinical practice and the management, delivery, and evaluation of health services, are the most commonly used in the world Work Group Meetings/Balloting Cycles 3 times annually January, May, September >700 members attend the meetings. Source: http://en.wikipedia.org/wiki/HL7

Health Level 7 HL7 is one of several American National Standards Institute (ANSI) -accredited Standards Developing Organizations (SDOs) operating in the healthcare arena. HL7 has been adopted by several national SDOs outside the U.S. 36 countries These SDOs are not accredited by ANSI. ISO adopted HL7 as a centre of gravity in international standardization and accredited HL7 as a partnering organization for mutual issuing of standards. The first mutually published standard was ISO/HL7 21731:2006 Health informatics—HL7 version 3—Reference information model—Release 1 Source: http://en.wikipedia.org/wiki/HL7

What is the Reference Information Model (RIM)? The Reference Information Model (RIM) is the cornerstone of the HL7 Version 3 development process. It is a shared model between all the domains (clinical data) from which all domains create their messages. The RIM and the vocabulary domains are the bases for the semantic specification of message elements. Current version 2.3.1 Available at http://www.hl7.org/implement/standards/rim.cfm Graphics in folder rim0231g http://www.hl7.org/implement/standards/rim.cfm

Infrastructure (communications) RIM v2.3.1 Entities Roles Acts Infrastructure (communications) Partic-ipation http://www.hl7.org/implement/standards/rim.cfm graphics in package rim0231g

The HL7 Clinical Genomics (CG) Work Group Established as a SIG in 2003 Mission To enable the standard use of patient-related genetic data such as DNA sequence variations and gene expression levels, for healthcare purposes (‘personalized medicine’) as well as for clinical trials & research Work Products and Contributions to HL7 Processes The Work Group will collect, review, develop and document clinical genomics use cases in order to determine what data needs to be exchanged. The WG will review existing genomics standards formats such as BSML (Bioinformatics Sequence Markup Language), MAGE-ML (Microarray and Gene Expression Markup Language), LSID (Life Science Identifier) and other. This group will recommend enhancements to and/or extensions of HL7's normative standards for exchange of information about clinical genomic orders and observations. In addition, Clinical Genomics will seek to assure that related or supportive standards produced by other HL7 groups are robust enough to accommodate their use in both research and clinical care use. The group will also monitor information interchange standards developed outside HL7, and attempt harmonization of information content and representation of such standards with the HL7 content and representation.

CG Work Group Leadership (Co-Chairs) Joyce Hernandez Merck & Co. Inc. Kevin Hughes MD   Partners HealthCare System, Inc. Amnon Shabo, PhD IBM Mollie Ullman-Cullere   Partners HealthCare System, Inc.

Formal Relationships with Other HL7 Groups CG Work Group coordinates with a large number of other Work Groups in order to accomplish its mission. Strongest relationships are with Orders and Observation Clinical Statement Clinical Decision Support Regulated Clinical Research Information Management Patient Care Electronic Health Records Modeling and Methodology Structured Documents

Accomplishments Focus on V2 and V3 genetic and genomics data models V3 Genetic Models Single Gene (Genetic Locus) Common Message Elements (CMET) Draft Standard for Trial Use – May 2005 (Revised May 2006) Multiple Gene (Genetic Loci) CMET Draft Standard for Trial Use – Jan 2007 Unified Full Genetic Variation CMET Draft Standard for Trial Use – Jan 2008 Normative – Jan 2010 V3 Pedigree Topic - Family History Normative – May, 2007

Accomplishments Genetic Variation V2 message Developed for clinical practice to carry findings from a lab to a physician, genetic councilor, etc. Subset of full V3 model, focus on interpretive, not raw (sequence) data Genetic Variation V3 Reduced CMET Companion to V2 message Gene Expression Model Intended for V2 and V3 implementation Domain Analysis Model balloted Sept 2009, currently in Ballot May 2010

CG Gene Expression Domain Analysis Model-Diagram

CG Gene Expression Domain Analysis Model-Details Subpackages Array Design Classes e.g Array, ArrayDesign, ArrayGroup, Reporter etc. Common Classes Identifiable, OntologySource, OntologyTerm etc. Data DataFile, DataMatrix, Image, ImageAcquistion etc. Design Element DesignElement, DimensionElement etc. Experiement Definition GenomicProtocol, LabExperiment, NormalizationTypes, ProtocolParameter etc. Relationship Relationships between: Samples, Arrays and Data Bio-Specimen Diagrams Classes e.g BioSpecimen, Bio-Specimen-Characteristics, Specimen Handling etc.

Clinical Genomics Domain Analysis Model-Terminology Terminology: definitions from NCI EVS team for a number of terms needed for genetic sample type entries nDNA (Nuclear DNA) pDNA (plasmid DNA) RNA (Ribonucleic acid) RNAP (RNA polymerase) mRNA (Messenger Ribonucleic Acid) snRNA (Small nuclear RNA) miRNA (microRNA) ssRNA (single-stranded RNA) dsRNA (double-stranded RNA) snoRNA (small nucleolar RNA) tRNA (Transfer RNA) hnRNA (heterogeneous nuclear RNA) RNP (Ribonucleoprotein) snRNP (small nuclear ribonucleoproteins)

CG Gene Expression Domain Analysis Model-Ballot Model available at http://www.hl7.org/v3ballot/html/domains/uvcg/uvcg_GeneExpressionDAM.htm#POCG_DO000000UV-GeneExpressionDam-ic Comments due May 9, 2010 Under review by IRWG (ICR WS) Model will be expanded in future to include Genetic Variations

Upcoming Activities Cytogenetic Lab Results Project Scope statement being prepared Model would consider classes from caBIO Gene Expression Domain Analysis Model Ballot reconciliation

Useful links HL7.org http://www.hl7.org/ HL 7 Wiki http://wiki.hl7.org/index.php?title=Main_Page Clinical Genomics Wiki http://wiki.hl7.org/index.php?title=CG HL7 Standards http://www.hl7.org/implement/standards/index.cfm HL7v3 Ballot Site http://www.hl7.org/v3ballot/html/welcome/environment/index.htm

Questions?

Additional slides

What does the name mean? Health Level 7 symbolizes the seventh layer of the International Standards Organization (ISO) Communications Model: 1. Physical: Connects the entity to the transmission media 2. Data Link: Provides error control between adjacent nodes 3. Network: Routes the information in the network 4. Transport: Provides end-to-end communication control 5. Session: Handles problems that are not communication issues 6. Presentation: Converts the information 7. Application: Provides different services to the applications HL7 isn't just Level 7 any more! After years of implementing HL7 v2.x, HL7 standard developers realized it was virtually impossible to develop a comprehensive standard without including other levels of the International Organization for Standardization (ISO) Open Systems Interconnect (OSI) Model. Today, work groups exist for XML, Security, Modeling & Methodology, Arden Syntax, CCOW and Vocabulary (http://www.hl7.org/v3ballot/html/welcome/environment/index.htm)

HL7 v3.0 HL7 V3, like V2.x, is a standard for exchanging messages among information systems that implement healthcare applications. However, V3 strives to improve the V2 process and its outcomes. The original process for defining HL7 messages was established in 1987 and has served well. The development principles behind HL7 V3 lead to a more robust, fully specified standard. New capabilities offered in Version 3 include: Top-down message development emphasizing reuse across multiple contexts and semantic interoperability Representation of complex relationships Formalisms for vocabulary support Support for large scale integration Solving re-use and interoperability across multiple domain contexts A uniform set of models Expanded scope to include community medicine, epidemiology, veterinary medicine, clinical genomics, security, etc. From 1997

HL7 Development Framework: HDF The basis for the specification of a messaging standard is a Reference Information Model (RIM) that completely covers the domain being addressed. The RIM and the vocabulary domains are the bases for the semantic specification of message elements. The Domain Information Model (DIM ) defines the information content for a specific area of expertise or interest. The DIM represents one group’s view of the world. A proper subset of the RIM, called Refined Message Information Model (R-MIM) is used to express the information content for one or more related messages. The R-MIM provides one method of controlling optionality. The Hierarchical Message Description (HMD) specifies a set of messages based of one R-MIM. A message type is specified in one HMD. Source: http://healthinfo.med.dal.ca/HL7Intro/