Concept to Codes Approach. Visual Representation PSMA Code 1 Code 2 PSMA Code 1 Code 2 LOINC Code 624-7 Code 6460-0 LOINC Code 624-7 Code 6460-0 SNOMED.

Slides:



Advertisements
Similar presentations
Nationwide Health Information Network Exchange and the SSA Patient Authorization June 18, 2012.
Advertisements

4.01 Targeted s. Considerations for Effective E- mail Marketing Content of message Content of message Recipients of message Recipients of message.
Query Health Concept Mapping Activity November 10, 2011.
Towards a Flexible Integration of Clinical Guideline Systems With Medical Ontologies and Medical Information Systems Gianluca Correndo 1, Paolo Terenziani.
Consistent and standardized common model to support large-scale vocabulary use and adoption Robust, scalable, and common API to reduce variation in clinical.
QIDAM Issues and proposals for a logical model For discussion during HL7 WG Meeting in Jan 2014 Thursday Q3.
CTS2 Terminology Services
VSAC Users’ Forum Thursday, January 15 2:00 – 3:00 PM, EST.
Open Health Tools Distributed Terminology System Presentation Jack Bowie SVP Sales and Marketing Apelon, Inc. 1.
Amy Sheide Clinical Informaticist 3M Health Information Systems USA Achieving Data Standardization in Health Information Exchange and Quality Measurement.
Introduction to openEHR
Companion Guide to HL7 Consolidated CDA for Meaningful Use Stage 2
Query Health Technical WG 9/14/2011. Agenda TopicTime Allocation Administrative Stuff and Reminders11:05 – 11:10 am Summer Concert Series Patterns Discussion11:10.
The Role of Standard Terminologies in Facilitating Integration James J. Cimino, M.D. Departments of Biomedical Informatics and Medicine Columbia University.
Clinical Vocabularies James J. Cimino, M.D. Columbia University.
Rich ElmoreCoordinator Merideth Vida Clinical Alice Leiter Operations “Dragon” Nageshwara Bashyam Technical ONC Annual Meeting: MU Training Day Query Health:
Interactions. 2 Objects communicate with each other by sending messages. Sending a message is another name for a member function call. –Some C++ examples.
Public Health Data Element Standardization - A Framework for Modeling Data Elements Used for Public Health Case Reporting Case Reporting Standardization.
SNOMED CT Denise Downs Knowledge Management & Education Lead Data Standards, Technology Office Department of Health Informatics Directorate.
10/3/2015DRAFT1 Public Health & Clinical LOINC - Jan 28 th 2011 CDC Vocabulary Team Office of Surveillance, Epidemiology and Laboratory Services (OSELS)
آشنایی و کار با سایت غلامرضا حریری عضو هیات علمی دانشگاه علوم پزشکی فسا Gh.Hariri1.
Jara Project: the interoperability in the healthcare enterprise. Juan P. Alejo González Subdirector Sistemas de Información - CIO Servicio Extremeño de.
Our contribution to SNOMED CT implementation Javier Fernández ITServer product manager.
Survey of Medical Informatics CS 493 – Fall 2004 September 27, 2004.
Client Registry An enterprise master patient index (EMPI), or Client Registry manages the unique identity of citizens receiving health services with the.
IntroductionMethods & MaterialsResults Conclusions The Office of Standards and Interoperability (OFTSI) of the Foundation TicSalut, is working on the need.
OpenHIE Improving health for the underserved. The Open Health Information Exchange (OpenHIE) Community: A diverse community enabling interoperable health.
CIDER - Today’s research, Tomorrow’s treatments Lab-2 September 15, 2010 Bijoy George, Program Manager, CBMI
A School of Information Science, Federal University of Minas Gerais, Brazil b Medical University of Graz, Austria, c University Medical Center Freiburg,
Query Health Vendor Advisory Meeting 12/15/2011. Agenda Provide Overview of Query Health Seek Guidance and Feedback on Integration Approaches.
VSAC Users’ Forum Thursday, September 18 2:00 – 3:00 EDT.
Andrew S. Kanter, MD MPH a,b a Millennium Villages Project, Earth Institute, Columbia University, New York, USA b Department of Biomedical Informatics,
CIMI Survey results 1 Presented by Nicholas Oughtibridge.
Query Health Concept-to-Codes (C2C) SWG Meeting #11 February 28,
HIT Standards Committee Clinical Operations Workgroup, Vocabulary Task Force Update on Vocabulary For Stage 2 Jamie Ferguson, Kaiser Permanente Betsy Humphreys,
Bernhard Breil, Benjamin Trinczek, Martin Dugas Dr. Bernhard Breil Portal of Medical Data Models – An open repository of Forms MedInfo 2013, Copenhagen.
Query Health Distributed Population Queries Implementation Group Meeting November 15, 2011.
Query Health Technical WG 11/10/2011. Agenda TopicTime Allocation Administrative Stuff and Reminders2:00 – 2:10 pm Proof of Concept Update2:10 -2:20 pm.
SNOMED CT A Technologist’s Perspective Gaur Sunder Principal Technical Officer & Incharge, National Release Center VC&BA, C-DAC, Pune.
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
Query Health Abstract Model Diagrams. Query Network Community of participants that agree to interact with each other. There will be many networks; requestors.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 4a Basic Health Data Standards Component 9/Unit.
Intrto-1 CSE 5810 Miscellaneous FHIR Slides Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut 371.
HL7-NLM Project Vocabulary Component Member and Contractors Update Orlando, Jan 2005.
Methods We employ the UMLS Metathesaurus to annotate ICD-9 codes to MedDRA preferred terms (PTs) using the three-step process below. The mapping was applied.
All Recurring Key Themes The below list includes themes across many of the different presentations to date. The next 2 slides address how these may be.
C-CDA Scorecard Rubrics Review of CDA R2.0 Smart C-CDA Scorecard Rules C. Beebe.
NAACCR CDA Pilot Project - Overview, Status, and Findings 2009 NAACCR Conference Ken Gerlach, Co-Chair, NAACCR Clinical Data Work Group; Health Scientist,
Presented for discussion with Implementation SIG Heather Grain.
Kathy Giannangelo, Map Lead
Interactions.
SMART Architecture and Application Development Overview
Achieving Semantic Interoperability of Cancer Registries
Our contribution to SNOMED CT implementation Javier Fernández
Leveraging Value Sets from the Value Set Authority Center (VSAC) in a Standards-Based Clinical Data Repository Richard Kiefer1, Luke V. Rasmussen2, Jennifer.
How we use the SNOMED CT to ICD-10 map in the Netherlands
LOCAL EXPERIENCES Innovation practices and experiences related to FIC development and implementation Ariadna Rius Clinical Dictionary for iSalut.
Electronic Health Record
Miscellaneous FHIR Slides

سامانه پرونده الکترونیکی سلامت ایران (سپاس) Iran Electronic Health Record System
Model ID: Model to represent entire statement including context
RDF Representation of HL7CDA documents
Electronic Health Record Access Control 7
ARCHITECTURE OVERVIEW
Anonymized HL7 message, which would be sent from an LIS to an HIS
National Clinical Terminology & Information Service Terminology Update
1. What is this situation about?
Interoperability with SNOW SHRINE
OHDSI Vocabulary Development and Release Process
Presentation transcript:

Concept to Codes Approach

Visual Representation PSMA Code 1 Code 2 PSMA Code 1 Code 2 LOINC Code Code LOINC Code Code SNOMED CT Code DE Code DE SNOMED CT Code DE Code DE ICD 9 Code Code ICD 9 Code Code ICD 10 Code J 18.9 Code J 18.1 ICD 10 Code J 18.9 Code J 18.1 Vocabulary Standards & Codes: Each standard has multiple ways to represent the same concept. UMLS (Value Set Repository) Clinical Concepts (unique per hospital, larger hospital system might share one) Clinical Concepts (unique per hospital, larger hospital system might share one) Sounds like Rich wants to standardize this portion, the process of mapping from the vocabulary codes to the clinical concepts. A A Question: Is the query on the vocabulary concepts (A) and codes OR the clinical concepts (B)? Depending on this answer the CIM will have to be developed taking this into consideration? B Map Vocabulary Codes to Clinical Concept Dictionary

Visual Representation Query A Clinical Concept to Codes UMLS (Value Set Repository) PSMA Code 1 Code 2 PSMA Code 1 Code 2 LOINC Code A Code B LOINC Code A Code B SNOMED CT Code XYZ Code ABC SNOMED CT Code XYZ Code ABC ICD 9 Code 45 Code 87 ICD 9 Code 45 Code 87 ICD 10 Code 124 Code 89 ICD 10 Code 124 Code 89 Clinical Concepts (unique per hospital, larger hospital system might share one) Clinical Concepts (unique per hospital, larger hospital system might share one) Map Clinical Concept Dictionary to Vocabulary Codes Clinical Concepts Query is Received Query Request based on Clinical Concepts Information Requestor (Role: Query Source) Provider/Provider Organization (Role: Data Source) Clinical Concepts are Mapped from the Clinical Concept to Data in System Data is Identified Data is Formatted to Answer Query Data is mapped to Clinical Concepts Clinical Concepts Query Request is formatted Query Results are Sent to Requestor Query Expression

Query A Workflow Diagram 4 Need for Clinical Query is Defined Query is Created Against Concept Dictionary Query is Expressed in these Concepts Query is Transmitted to Data Sources Results of Query are Obtained Data Source Receives Query Data Source Maps Query Concepts to Local Concepts Data Source Maps Query Concepts to Standard Vocabularies Codes Data Source Maps Standard Vocabulary Codes to Local Concepts Query is Run Against Source’s Data Relevant Results are Returned Using Defined Format Data Source Query Source

Visual Representation Query B Codes to Clinical Concepts UMLS (Value Set Repository) PSMA Code 1 Code 2 PSMA Code 1 Code 2 LOINC Code A Code B LOINC Code A Code B SNOMED CT Code XYZ Code ABC SNOMED CT Code XYZ Code ABC ICD 9 Code 45 Code 87 ICD 9 Code 45 Code 87 ICD 10 Code 124 Code 89 ICD 10 Code 124 Code 89 Clinical Concepts (unique per hospital, larger hospital system might share one) Clinical Concepts (unique per hospital, larger hospital system might share one) Map Vocabulary Codes to Clinical Concept Dictionary Coded Data Query is Received Query Request based on Coded Data Information Requestor (Role: Query Source) Provider/Provider Organization (Role: Data Source) Coded Data are Mapped from the Clinical Concepts Concept is Identified Concept is Formatted to Answer Query Clinical Concepts are Mapped to Coded Data Coded Data Query Request is formatted Query Results are Sent to Requestor Query Expression

Query B Workflow Diagram 6 Need for Clinical Query is Defined Query is Created Against Concept Dictionary Query is Expressed in these Vocabulary Codes Query is Transmitted to Data Sources Results of Query are Obtained Data Source Receives Query Data Source Maps Query Standard Vocabulary Codes to Local Concepts Query is Run Against Source’s Data Relevant Results are Returned Using Defined Format Data Source Query Source Query Concepts are Mapped to Standard Vocabulary Codes