FROM ONE NOMENCLATURES TO ANOTHER… Drs. Sven Van Laere.

Slides:



Advertisements
Similar presentations
SNOMED Core Structures 2 nd AAHA Software Vendors Summit – April 21, 2009.
Advertisements

Mpeg-21 and Medical data A strategy for Tomorrow ’ s EMR.
Lecture 5 Standardized Terminology and Language in Health Care (Chapter 15)
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 5 Understanding Entity Relationship Diagrams.
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
1 Definitions Value set: A list of specific values, which may – or may not – contain subsets of one or more standard vocabularies, that define or identify:
Terminology in Health Care and Public Health Settings
On Roles of Models in Information Systems (Arne Sølvberg) Gustavo Carvalho 26 de Agosto de 2010.
Chapter 4 The Relational Model.
The Exchange of Retrieval Knowledge about Services between Agents Mirjam Minor Mike Wernicke.
Karen Gibson.  Significant investment in eHealth is underway  Clinical records: ◦ Not only a record for the author ◦ Essential to inform the next person.
SNOMED CT Denise Downs Knowledge Management & Education Lead Data Standards, Technology Office Department of Health Informatics Directorate.
LexEVS 6.0 Overview Scott Bauer Mayo Clinic Rochester, Minnesota February 2011.
HL7 HL7  Health Level Seven (HL7) is a non-profit organization involved in the development of international healthcare.
MPEG-21 : Overview MUMT 611 Doug Van Nort. Introduction Rather than audiovisual content, purpose is set of standards to deliver multimedia in secure environment.
Toolkit for Planning an EHR-based Surveillance Program | HL7 Clinical Document Architecture An Introduction.
CountryData Technologies for Data Exchange SDMX Information Model: An Introduction.
TripCom: Development of a patient summary at European level E. Della Valle, D. Cerizza, D. Foxvog, R. Krummenacher, L. J. B. Nixon, E.
1 st June 2006 St. George’s University of LondonSlide 1 Using UMLS to map from a Library to a Clinical Classification: Improving the Functionality of a.
More and Better Data for Research: U.S. Health Data Content Standards Betsy L. Humphreys Assistant Director for Health Services Research Information National.
Terminology and HL7 Dr Colin Price HL7 UK 11 th December 2003.
HIT Standards Committee Clinical Operations Workgroup Report Jamie Ferguson, Chair Kaiser Permanente John Halamka, Co-chair Harvard Medical School 20 August,
Recent advances in the field of Family Medicine classifications ICPC into WHO-FIC J K Soler Wonca International Classification Committee.
Clinical Document Architecture. Outline History Introduction Levels Level One Structures.
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 5b Health Data Interchange Standards.
Component 3-Terminology in Healthcare and Public Health Settings Unit 17-Clinical Vocabularies This material was developed by The University of Alabama.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
HIT Standards Committee Vocabulary Task Force Task Force Report and Recommendation Jamie Ferguson Kaiser Permanente Betsy Humphreys National Library of.
Lab and Messaging CoP 11/29/2012. Agenda Agenda review Introduction to the Specimen Cross-Mapping Table (Specimen CMT) – Background – Expected uses –
VTSL Enhancing the AAHA & AAEP Diagnostic Subsets 2013 Talbot Symposium Jeff R. Wilcke DVM, MS, DACVCP; Julie M. Green DVM, MS; Suzanne L. Santamaria DVM,
HIT Standards Committee Clinical Operations Workgroup Report on Gaps and Next Steps Jamie Ferguson Kaiser Permanente John Halamka Harvard Medical School.
SNOMED Core Structures NAHLN January 2005 Las Vegas, NV.
A Portrait of the Semantic Web in Action Jeff Heflin and James Hendler IEEE Intelligent Systems December 6, 2010 Hyewon Lim.
© 2005 NORTHROP GRUMMAN CORPORATION 2 11 Jan 06 Northrop Grumman Private / Proprietary Level I Terminology Service Bureau Vision Processes  Procedures.
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.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 4a Basic Health Data Standards Component 9/Unit.
Database Design, Application Development, and Administration, 6 th Edition Copyright © 2015 by Michael V. Mannino. All rights reserved. Chapter 5 Understanding.
Data Models. 2 The Importance of Data Models Data models –Relatively simple representations, usually graphical, of complex real-world data structures.
Terminology Server - Semantics for Medical Documentation and Interoperability / Dortmund © Peter Haas, Robert Mützner / Working Group Med. Informatics.
ITI Infrastructure - Wednesday November 7th, IHE IT infrastructure “Terminology Sharing” Christel Daniel (AP-HP, INSERM, Paris), Ana Esterlich (GIP-DMP),
Mapping International Classification for Nursing Practice (ICNP) and SNOMED CT Submitted by the ICNP Programme Team to IHTSDO Nursing Special Interest.
Essential SNOMED. Simplifying S-CT. Supporting integration with health
NAACCR CDA Pilot Project - Overview, Status, and Findings 2009 NAACCR Conference Ken Gerlach, Co-Chair, NAACCR Clinical Data Work Group; Health Scientist,
Copyright © 2009 by The McGraw-Hill Companies, Inc. All Rights Reserved. McGraw-Hill/Irwin Chapter 2 Clinical Information Standards – Unit 3 seminar Electronic.
3M Health Information Systems 1© 3M All Rights Reserved. 3M Health Information Systems Data Standardization Interoperability.
Canadian SNOMED CT® Extensions Challenges & Lessons learned Presentation to Implementation SIG October 2012 Presented by Linda Parisien and Beverly Knight.
Frequent Criticisms too ambitious recreation of a Textbook of Medicine competing with SNOMED-CT replicates the work done elsewhere: DSM, ICPC, too academic.
A Proposed Approach to Binding SNOMED CT to HL7 FHIR Dr Linda Bird Senior Implementation Specialist.
Assessing SNOMED CT for Large Scale eHealth Deployments in the EU Workpackage 2- Building new Evidence Daniel Karlsson, Linköping University Stefan Schulz,
SNOMED Core Structures RF2
UNIFIED MEDICAL LANGUAGE SYSTEMS (UMLS)
Representation of Hypersensitivity, Allergy and adverse reactions in SNOMED CT Bruce Goldberg, MD, PhD.
Electronic Medical Record (EMR)
SNOMED CT Search & Data Entry
NeurOn: Modeling Ontology for Neurosurgery
Terminology Service Bureau Vision
Achieving Semantic Interoperability of Cancer Registries
WP1: D 1.3 Standards Framework Status June 25, 2015
Cor Loef Philips Healthcare
Networking and Health Information Exchange
Intelligent Agents Chapter 2.
Chapter 2 Database Environment.
Terminology and HL7 Dr Colin Price
A bit more about Read Codes and SNOMED CT
Managing data Resources:
SDMX Information Model: An Introduction
RIDE INTEROPERABILITY WORKSHOP, Brussels 8/12/2006
RIDE INTEROPERABILITY WORKSHOP, Brussels 8/12/2006
Presentation transcript:

FROM ONE NOMENCLATURES TO ANOTHER… Drs. Sven Van Laere

Content Table Actual state Definition of interoperability Mapping Mapping in practice

Actual state – Healthcare with too many standards ICPC-2 ICD LOINC – Different levels ICPC-2 used by GP ICDused forbilling LOINCused for laboratory results

Actual state – No continuity in healthcare Referral GP Hospital

Recap – In the medical history we evolved from free text (60-ies) to structured language Free text Codes Classifications Terminologies Nomenclatures de Lusignan

What should we do?

Definition Antonio Aguilar A state which exists between two application entities when, with regard to a specific task, one application entity can accept and understand data from the other and perform that task in an appropriate and satisfactory manner without the need for extra operator intervention. Interoperability

Definition Antonio Aguilar Interoperability in eHealth for whom? -healthcare companies e.g. vendors of clinical systems, administrative IT systems and medical devices -healthcare providers e.g. GPs, physicians, nurses, technicians, etc. -IT and administrative staff -health authorities and governments

Definition Antonio Aguilar Interoperability levels -functional and syntactic interoperability the ability of two or more systems to exchange information through functionality and defined message structures so that this information is human readable by the receivers e.g. HL7 v2, DICOM -semantic interoperability the ability for information shared by systems to be understood at the level of formally defined domain concepts so that the information is computer processable by the receiving systems e.g. HL7 v3 RIM, SNOMED CT

Mapping How to… Mapping A linkage between a concept from one standard to another standard based on the equivalence between the two concepts

Mapping How to… Mapping rules Consider the place in the hierarchy of a terminology standard Consider the semantics of a concept Consider the relationship with other concepts around a concept

Mapping How to… Manual mapping human knowledge of medical experts, linguists, terminology experts, … Semi-automatic mapping Computer algorithm identifies candidate mappings based on descriptions Human review of the automatic mapping

Variety of standards We know… The principles of mapping now But… How do we deal with the wide variety of standards (ICPC-2, ICD-10, LOINC, NANDA, SNOMED CT,…)

Variety of standards

What RT to choose? Choose most comprehensive SNOMED CT 310,000 concepts Support pre- and post-coordination Still under evaluation Assess-CT project

MAPPING IN PRACTICE…

Refsets Reference set A set of references to SNOMED CT components Simple reference sets are used to distribute SNOMED CT subsets Reference sets may include additional information about referenced components – so they also have other uses

Types of refsets

Simple refset

Simple refset model

Broad range of use Language refset Attribute-value refset Association refset Ordered refset Mapping refsets – Simple mapping – complex mapping …

Language refset refsetId (SCTID) – Identifies the refset – Subtype of | Language type reference set | referencedComponentId(SCTID) – Referes to a description acceptabilityId – Indicates the acceptability of the description for use in the specified language, dialect or use case – Subtype of | Acceptability | | Acceptable | | Preferred |

Attribute-value refset Apply a value from a specified range to a component Can be used for many different purposes – For example, to indicate the reason for inactivation of a particular concept refsetId(SCTID) – Identifies the refset which names the purpose of the added values – Subtype of | Attribute value type reference set| referencedComponentId(SCTID) – Identifies the component to which the value is being applied valueId(SCTID) – The value represented by identifying a concept from a relevant hierarchy

Association refset Represents a set of unordered directed associations of a particular type between components Can be used for many different purposes – For example, to indicate an association between an inactive concept and an active concept that replaces it refsetId (SCTID) – Identifies the refset which names the nature of the association – Subtype of | Association type reference set | referencedComponentId (SCTID) – the source component of the association targetComponentId (SCTID): – the target component of the association

Ordered refset Priority ordering or ordered associations refsetId (SCTID) – Identifies the refset – Subtype of | Ordered type reference set | referencedComponentId (SCTID) – Identifies the component that is included in the ordered list order (Integer) – the sort order – 1 represents the highest priority – Duplicate values are permitted linkedToId(SCTID) – the component that acts as a grouper or hierarchy node, collecting togethera subgroup from within the list

Mapping refset – single mapping Allows representation of simple maps between SNOMED CT concepts and codes in other code systems Usually only appropriate for “one-to-one” mappings refsetId(SCTID) – Identifies the refset – Subtype of | Simple map reference set | referencedComponentId(SCTID) – The concept being mapped mapTarget(String): – The code in the other code system

Mapping refset – complex/extended mapping Enables representation of maps where each concept may map to one or more codes in a target scheme The target code can be selected at run-time from a number of alternate codes using machine readable rules and/or human readable advice

Exercise We are going to make a subset, based on the SNOMED CT browser –

Exercise Navigate in the browser and use the International edition

Exercise Lookup the following concepts: – Open fracture dislocation of knee joint – Open fracture of femoral condyle of femur – Open fracture of patella – Open fracture of tibial condyles What is the similar parent of these 4 concepts?

Open fracture dislocation of knee joint

Open fracture of femoral condyle of femur

Open fracture of patella

Open fracture of tibial condyles

Exercise Lookup the same concepts in the ICD-10 classification – Fill in the file with the found results In the mapping tab find at least one mapping