Briefing: HL7 Working Group Meeting Update for the VCDE Community Dianne M. Reeves Associate Director, Biomedical Data Standards NCI CBIIT VCDE Meeting.

Slides:



Advertisements
Similar presentations
Integrating the Healthcare Enterprise IHE Overview Keith W. Boone Interoperability Architect, GE Healthcare Co-chair, IHE Patient Care Coordination PC.
Advertisements

EDOS Workgroup Update July 16, 2013 Laboratory Orders Interface Initiative.
EDOS Workgroup Update Laboratory Orders Interface Initiative.
EDOS Workgroup Update June 18, 2013 Laboratory Orders Interface Initiative.
Welcome! HL7 Child Health Work Group Meeting September 16, 2008 Dial In: (866) code:
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
What’s New with CDISC Wayne R. Kubick CDISC CTO.
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
HITSC Clinical Quality Workgroup Jim Walker March 27, 2012.
Longitudinal Coordination of Care (LCC) Workgroup (WG)
Catherine Hoang Ioana Singureanu Greg Staudenmaier Detailed Clinical Models for Medical Device Domain Analysis Model 1.
© 2013 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg.
© 2013 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
S&I Framework Laboratory Initiatives Update June 6, 2013.
SOA Update from The Open Group OMG Technical Meeting 4 December 2006 Dr Christopher J Harding Forum Director Tel Mobile
All Rights Reserved, Duke Medicine 2007 Cardiovascular Data Analysis Model HL7 Balloting (September 22, 2011) Salvatore Mungal Duke Bioinformatics Shared.
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
WHAT IS CQI? Contact the CQI Committee: (360)
EHR Integration – Project Charter slide 1 Goals  Support specification of the already started service specification within HL7 RCRIM –going to ballot.
Update on Newborn Screening Use Case Advisory Committee on Heritable Diseases in Newborns and Children - Advisory Committee on Heritable Diseases in Newborns.
ADC Meeting ICEO Standards Working Group Steven F. Browdy, Co-Chair ADC Workshop Washington, D.C. September, 2007.
HL7 Webinar: Mobile Health Chuck Jaffe Austin Kreisler John Quinn 19 March 2012.
1 Federal Health IT Ontology Project (HITOP) Group The Vision Toward Testing Ontology Tools in High Priority Health IT Applications October 5, 2005.
HL7 HL7  Health Level Seven (HL7) is a non-profit organization involved in the development of international healthcare.
1 Dianne M. Reeves Report: HL7 25 th Annual Plenary and WGM September 11 – 16, 2011 San Diego, California.
1 Health Level Seven (HL7) Report Out Population Science and Structured Documents Workgroup (SDWG) Riki Ohira September 22, 2011.
Toolkit for Planning an EHR-based Surveillance Program | HL7 Clinical Document Architecture An Introduction.
Public Health Vocabulary Services (a) Gautam Kesarinath – CDC NCPHI Associate Director of Technology, (b) Nikolay Lipskiy – CDC SDO & Interoperability.
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.
Clinical Genomics Work Group (HL7) Mukesh Sharma Washington University in St. Louis June 16, 2011.
NIEM Domain Awareness June 2011 Establishing a Domain within NIEM.
CDISC South African User Group (SAUG) 28-Mar-2012 Co-leaders: Dianne Weatherall, Marielle Knott Presenters: Loryn Thorburn Laurent Marais Wouter van Wyk.
Public Health Reporting Initiative: Stage 2 Draft Roadmap.
Clinical Quality Framework cqframework.info All Hands Meeting July 24, am-12:30pm ET.
Networking and Health Information Exchange Unit 6b EHR Functional Model Standards.
EHR-S Functional Requirements IG: Lab Results Interface Laboratory Initiative.
Page 0 10/19/2015 Welcome to the VMCoP Meeting July 21st, 2009.
RCRIM Off-cycle Meeting Barbara Tardiff, Randy Levin and Ed Tripp, co-chairs.
Promise of mHealth and Interoperability in Information System June, 2011 Copyright ©2011 BRAC ICT.
MED INF HIT Integration, Interoperability & Standards ASTM E-31 January 14, 2010 By Imran Khan.
EDOS Workgroup Update May 21, 2013 Laboratory Orders Interface Initiative.
Networking and Health Information Exchange Unit 5b Health Data Interchange Standards.
AHRQ-USHIK: Best Practices & Lessons Learned HIT Standards Committee Vocabulary Task Force J. Michael Fitzmaurice Agency for Healthcare Research and Quality.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 3b National and International Standards Developing.
© 2012 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Data Provenance Tiger Team May 9 th, 2014 Johnathan Coleman Johnathan Coleman - Initiative Coordinator Lynette ElliottLynette Elliott – Tiger Team Support.
A LexWiki-based Representation and Harmonization Framework for caDSR Common Data Elements Guoqian Jiang, Ph.D. Robert Freimuth, Ph.D. Harold Solbrig Mayo.
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.
© 2012 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
CDISC – 17/12/2012 Carine Javierre Nathalie SABIN.
1 CDISC HL7 Project FDA Perspective Armando Oliva, M.D. Office of Critical Path Programs FDA.
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
OSEHRA Interoperability Work Group (OSEHRA IWG) December 16, 2013 Mario G. Hyland Chair and Senior Vice President AEGIS.net, Inc. Interopguy.
EDOS Workgroup Update Laboratory Orders Interface Initiative.
1 An Overview of Process and Procedures for Health IT Collaboration GSA Office of Citizen Services and Communications Intergovernmental Solutions Division.
Data Access Framework All Hands Community Meeting 1 February 10, 2016.
Jonathan L. Elion MD, FACC Co-Chair, IHE Cardiology Planning Committee The Basics of IHE: Concepts and Process.
© 2015 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Labs Early Adoption Program Template Insert the Name of Your Implementation / Organization Here MM/DD/YYYY.
1 The information contained in this presentation is based on proposed and working documents. Health Information Exchange Interoperability Minnesota Department.
eHealth Standards and Profiles in Action for Europe and Beyond
Structured Data Capture (SDC)
Clinical Interoperability Council Working Group (CIC)
PHER Process and documents
Structured Data Capture (SDC)
Health Information Exchange Interoperability
Presentation transcript:

Briefing: HL7 Working Group Meeting Update for the VCDE Community Dianne M. Reeves Associate Director, Biomedical Data Standards NCI CBIIT VCDE Meeting June 16, 2011

HL7 Mission Health Level Seven International (HL7) is the global authority on standards for interoperability of health information technology with members in over 55 countries hl7.org Documents Workgroups Educational Sessions

HL7: Standards HL7 is all about use of standards to provide interoperability in electronic healthcare activities Semantic – understanding of meaning Technical – messaging Process – enable business activities to work together to use the information

HL7 Standards From the HL7 Introduction: HL7 creates standards for the exchange, management and integration of electronic healthcare information HL7 does not create or provide any sort of software. It does provide specifications for interoperable systems

HL7 Membership & Participation Membership is fee-based Participation shapes the direction of the standards under development Membership insures that organizational business needs are represented in the standards that are produced HL7 Working Group meetings Technical committees and Special Interest groups are a chance to meet F2F to work on standards. Also an opportunity to exchange knowledge and ideas.

HL7 Working Groups Working Group meetings held three times yearly Technical committees and Special Interest groups are a chance to meet F2F to work on standards. Provide opportunity to exchange knowledge and ideas. 54 Working groups (Tutorials and workshops) Work is done in Quarters (Q1, Q2, etc.) Agenda planned/published in advance Hosting of one group by another is common

HL7 Products What does HL7 produce? Documents that are reviewed and balloted Informative An Informative Document is the product of a Work Group that is not currently deemed normative, but nonetheless is intended for general publication. It explains or supports the structure of the HL7 Protocol Specifications, or provides detailed information regarding the interpretation or implementation of an HL7 Protocol Specification. Draft Document for Comment Only A Work Group, with the concurrence of the TSC, may submit proposed content or requirements documents, such as a Domain Analysis Model (DAM), to comment-only review. The intent is to gather input from members outside of the Work Group on the viability and clarity of content

HL7 Products Draft Standards for Trial Use (DSTU) Content is balloted by the general membership as the draft of a future standard which will, following a pre-specified period of evaluation and comment (usually 2 years), be expeditiously incorporated into normative standard. DSTU’s require at least two verified implementations that demonstrate the standard’s use. Normative Standard Content is balloted by the general membership and is considered a structural component of the HL7 Standard. Negative ballots must be resolved. Normative Standards are typically registered with ANSI.

HL7 Products ALL HL7 Balloted Standards are introduced first as a DSTU and must show some successful implementations before being advanced as a Normative Standard Balloting is carefully monitored and reflected in the Report Card of each Work group Negative ballots must be reconciled

Clinical Interoperability Council CIC Charter: This Workgroup provides a nexus of communication and bridge to the standards development framework, organizational processes and forums for the clinical community to define content, flow and other domain requirements necessary to the development of robust health data standards. CIC will support decision making practices related to clinical domain requirements developed by this committee. We will also, collaborate and offer support to other working groups when requested.

CIC Activities Collaboration with EHR Workgroup to investigate need for a set of standards for mobile devices, primarily in developing countries with smart phones Finish a survey of clinicians by September 2011 Sponsor project to create a tool that can import to and from EA, using an xls format document typically used by clinicians; not vendor-specific Model Automated eXchange – MAX Reconciliation of Emergency Medical Services (EMS) balloted DAM Sponsorship of ACC-sponsored Cardiology Model v2.0 (v1.0 in caDSR) Compatible with CDISC terminology and standards Slated for Balloting September 2011 Co-Sponsorship of Diabetes project – standards for Type 1 Diabetes Co-Sponsorship of Child Health Anesthesia DAM Sponsorship of TB DAM (will load into caDSR) New Sponsorship of Trauma Data Exchange DAM Exchange of Trauma Registry info, using ICD-10 codes, defined by ACS Assist groups in connecting with Clinical SMEs

CIC Activities Discussion of DAM and DCM construction with Patient Care (PC) Vocabulary constraints Creation of a DAM Process Guide to help CIC develop DAMs Does DAM development require specific terminology(ies)? 1.Evaluate the scope – US vs. International (Universal) 2.If terminology is an open issue, look to RxNorm, LOINC, and SNOMED Other established terminologies like MedDRA do not require change 3.Each Workgroup has a Vocabulary Facilitator to provide support 4.Vocabulary Workgroup offers ability to extend SNOMED Submit Definition, Semantic case, Example and Urgency of need DAM vocabulary requirements are now under discussion Decisions have been made CIC formally voted to partner with NCI to offer requirements for metadata registration for the HL7 community

HL7 Activities Next Working Group meeting: September in San Diego Work group Call Schedule on HL7.org website CIC Work group calls every 4 th Thursday of the month The public is welcome to attend the General CIC business Meeting, and any or ALL of the project team meetings If you heard about an activity in which you have interest, please contact Dianne Reeves at