SNOMED CT Vendor Introduction 27 th October 2014 11:30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.

Slides:



Advertisements
Similar presentations
 Implementing terminology requires supporting tools  Tools required are highly dependant on the type of implementation  Covered in this presentation.
Advertisements

Copyright © 2014 Pearson Education, Inc. 1 Managers from across organizations are involved in developing and acquiring information systems Chapter 5 -
Management Information Systems, Sixth Edition
Update on Vocabularies and Value Sets for Meaningful Use Betsy Humphreys, MLS, FACMI Deputy Director National Library of Medicine National Institutes of.
Fundamentals of Information Systems, Second Edition 1 Organizing Data and Information Chapter 3.
CHAPTER 3 DATABASES AND DATA WAREHOUSES. 3-2 STUDENT LEARNING OUTCOMES 1.Describe business intelligence and its role 2.Compare databases and data warehouses.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 4-1.
Information systems and databases Database information systems Read the textbook: Chapter 2: Information systems and databases FOR MORE INFO...
Chapter 4 Relational Databases Copyright © 2012 Pearson Education 4-1.
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:
AUGUST 21, 2014 STANLEY M. HUFF, MD CHIEF MEDICAL INFORMATICS OFFICER INTERMOUNTAIN HEALTHCARE HSPC Meeting Introduction.
The Final Standards Rule John D. Halamka MD. Categories of Standards Content Vocabulary Privacy/Security.
Developing Enterprise Architecture
Managing SNOMED in your system. 2 nd AAHA Software Vendors Summit – April 21, 2009.
The IHTSDO Workbench A Terminology Management Tool John Gutai, IHTSDO May 2011 For OHT.
L/O/G/O Metadata Business Intelligence Erwin Moeyaert.
SNOMED CT Webinar 3 Tom Seabury 26 th September 2011 at 15:00-16:00, repeated on 29th September.
Common Data Elements and Metadata: Their Roles in Integrating Public Health Surveillance and Information Systems Ron Fichtner, Chief, Prevention Informatics.
1 Betsy L. Humphreys, MLS Betsy L. Humphreys, MLS National Library of Medicine National Library of Medicine National Institutes of Health National Institutes.
Chapter 5 Lecture 2. Principles of Information Systems2 Objectives Understand Data definition language (DDL) and data dictionary Learn about popular DBMSs.
Update on Newborn Screening Use Case Advisory Committee on Heritable Diseases in Newborns and Children - Advisory Committee on Heritable Diseases in Newborns.
Project Highlights. New Process Project Report videos available at
Working Together to Advance Terminology Tooling Presentation to OHT Board, Birmingham Jennifer Zelmer & Karen Gibson.
Project Proposal: CTS2 SDK Presentation to OHT Steering Committee.
Physical Database Design Chapter 6. Physical Design and implementation 1.Translate global logical data model for target DBMS  1.1Design base relations.
Survey of Medical Informatics CS 493 – Fall 2004 September 27, 2004.
Terminology and HL7 Dr Colin Price HL7 UK 11 th December 2003.
1/26/2004TCSS545A Isabelle Bichindaritz1 Database Management Systems Design Methodology.
Clinical Document Architecture. Outline History Introduction Levels Level One Structures.
C6 Databases. 2 Traditional file environment Data Redundancy and Inconsistency: –Data redundancy: The presence of duplicate data in multiple data files.
CHAPTER 3 DATABASES AND DATA WAREHOUSES. 2 OPENING CASE STUDY Chrysler Spins a Competitive Advantage with Supply Chain Management Software Chapter 2 –
6.1 © 2010 by Prentice Hall 6 Chapter Foundations of Business Intelligence: Databases and Information Management.
AMIA 2007 Monday, Nov :30-1:30 National Library of Medicine National Institutes of Health U.S. Dept. of Health & Human Services UMLS ® Users Meeting.
Summary Report Project Name: IHTSDO Workbench Brief Project Description: Development of a collaborative tool to allow maintenance of terminology, mapping.
Summary Report Project Name: IHTSDO Workbench Brief Project Description: Development of a collaborative tool to allow maintenance of terminology, mapping.
Query Health Concept-to-Codes (C2C) SWG Meeting #11 February 28,
HIT Standards Committee Clinical Operations Workgroup Jamie Ferguson Kaiser Permanente John Halamka Harvard University February 24, 2010.
HIT Standards Committee Vocabulary Task Force Task Force Report and Recommendation Jamie Ferguson Kaiser Permanente Betsy Humphreys National Library of.
Software Reuse Course: # The Johns-Hopkins University Montgomery County Campus Fall 2000 Session 4 Lecture # 3 - September 28, 2004.
ENGR 1181 College of Engineering Engineering Education Innovation Center Introduction to Technical Communication.
SNOMED CT A Technologist’s Perspective Gaur Sunder Principal Technical Officer & Incharge, National Release Center VC&BA, C-DAC, Pune.
Clinical Quality Workgroup April 10, 2014 Commenting on the ONC Voluntary 2015 Edition Proposed Rule Marjorie Rallins– co-chair Danny Rosenthal –co-chair.
IHTSDO Implementation SIG 10/27/2014 Moon Hee Lee, Principal Silicon Valley Terminology Consulting, USA SNOMED use in the U.S.– examining two organizations.
FROM ONE NOMENCLATURES TO ANOTHER… Drs. Sven Van Laere.
Introduction to Project Management Managing Project Scope Lecture b This material (Comp19_Unit5b) was developed by Johns Hopkins University, funded by.
IHTSDO Education & Implementation Update Dr Linda Bird Implementation Specialist.
Mapping International Classification for Nursing Practice (ICNP) and SNOMED CT Submitted by the ICNP Programme Team to IHTSDO Nursing Special Interest.
Canadian SNOMED CT Strategy October 2012 Draft. Content 1 Background Approach Current State Future State Considerations Action Plan.
‘Implementation of SNOMED CT ’ Oct’ 2012 Denise Downs, Implementation & Engagement Lead.
NHS Connecting for Health is delivering the National Programme for Information Technology Setting and Achieving the NHS Standard for Records Management.
Lab Results Interfaces S&I Framework Initiative Bi-Weekly Initiative Meeting September 12, 2011.
Canadian SNOMED CT® Extensions Challenges & Lessons learned Presentation to Implementation SIG October 2012 Presented by Linda Parisien and Beverly Knight.
Presented for discussion with Implementation SIG Heather Grain.
SNOMED CT Learning Activities Views from the United States Suzy Roy National Library of Medicine Rita Scichilone IHTSDO SNOMED CT Advisory Scheme.
Management Information Systems by Prof. Park Kyung-Hye Chapter 7 (8th Week) Databases and Data Warehouses 07.
SNOMED CT E-Learning October 2014 Status & Planning Update (for ELRG)
LOINC – SNOMED CT Cooperation on Content
Kathy Giannangelo, Map Lead
E-Learning Advisory Group Meeting
Scope The scope of this test is to make a preliminary assessment of the fitness of the Draft Observables and Investigation Model (Observables model)
SNOMED CT E-Learning Status & Planning September Update (for ELRG)
IHTSDO SNOMED CT Tooling
ICD-11 Reference Guide Robert Jakob, WHO.
Terminology and HL7 Dr Colin Price
Undergraduate Courses
Chapter 11: Software Configuration Management
Metadata The metadata contains
Data Warehousing Concepts
National Clinical Terminology & Information Service Terminology Update
Summary Report Project Name: IHTSDO Workbench
Presentation transcript:

SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO

▪ Vendor Introduction: Purpose ▪informative practical introduction to SNOMED CT focused primarily on the needs of EHR vendors and developers ▪Companion to Starter Guide, National Release Center Guide ▪ Audience ▪Providers of EHR systems and related services ▪ Brief: July 2014 ▪Leading officer, Committee: I&E ▪ Current draft ▪13 chapters ▪56 pages ▪23 figures Introduction … people engaged in provision of EHR systems and related services. The document will also be of interest to a broader audience including anyone engaged in designing, developing, procuring, deploying, configuring or managing EHR systems and services. As the word vendor suggests, the primary focus of this document is commercial vendors of products and services but most of its content is equally applicable to not-for-profit enterprises and in-house developers of EHR systems and services.

▪ Document draft held on I&E Committee document store ▪Shared with Implementation SIG attendees ▪This version is not in its review cycle ▪Changes will occur: as a subsequent draft ▪Link: Draft document access Please submit review comments using the online feedback form: Comments on this version close 23-October

▪ Lead officer, Committee: I&E ▪ First informal review: ▪I&E Committee 22 nd September 2014 ▪ Amended in response to informal review comments ▪ First formal review cycle I&E, Tech Committees ▪Initiated 1 st October 2014 ▪Closed 23 rd October 2014 Development

▪ Draft document ▪13 chapters ▪56 pages ▪23 figures Currently

Chapters Table of Contents 1.Introduction 2.Benefits to Vendors: why implement SNOMED CT 3.Key characteristics of SNOMED CT 4.Accessing SNOMED CT and related IHTSDO services 5.Using SNOMED CT with other standards 6.User experience of SNOMED CT 7.Implementation Strategies 8.Choosing an approach to Implementation 9.SNOMED CT Services 10.EHR design for use with SNOMED CT 11.Customization Extensions and configuration 12.Licensing 13.References

Selected highlights 2.Benefits to Vendors: why implement SNOMED CT

▪ Staged implementation ▪ Relationships and Dependencies ▪ Territories and Languages, language and dialect strategies ▪ Variations around a Basic Configuration – provision of tools and services ▪ Measures of implementation success ▪ Factors which influence implementation success Selected highlights

8.Choosing an approach to Implementation Figure 10 Schematic illustration of an EHR system

Selected highlights 8.Choosing an approach to Implementation

▪ Target Configurations 1 SNOMED CT as a Reference Terminology for Communication 2 SNOMED CT as an indexing system for data retrieval 3 SNOMED CT as a code system for clinical data in the EHR 4 SNOMED CT as an Interface Terminology for EHR data entry 5 SNOMED CT as a dictionary for simple aggregation and analysis of data 6 SNOMED CT as a dictionary for analytics using Description Logic 7 SNOMED CT as a dictionary of rules for Knowledge Linkage 8 SNOMED CT as an Extensible Foundation for Representing Clinical Data 9 Full use of SNOMED CT to deliver all its powerful features in an EHR Choosing an approach to Implementation

▪ Concept identification – unique and persistent ▪ Descriptions and terms ▪ Comprehensive and granular ▪ SNOMED CT expressions ▪ Logical representation of meaning ▪ Meaning based retrieval ▪ Subsets of concepts or descriptions ▪ Mapping to and from other code systems ▪ Extension mechanism ▪ Standard release format with built in versioning ▪ Continuous improvement ▪ Guiding principles for content addition Key characteristics of SNOMED CT

▪ Reviewing SNOMED CT content ▪ Using SNOMED CT for data entry and analysis ▪ Obtaining SNOMED CT release files ▪ Documentation ▪ Education ▪ Tools and Services ▪ Requests for changes and additions Accessing SNOMED CT and related IHTSDO services

▪ World Health Organization classifications: ICD-10 ▪ LOINC (Logical Observation Identifiers Names and Codes) ▪ Clinical Information Modelling Initiative (CIMI) ▪ HL7 message standards, CDA and FHIR Using SNOMED CT with other standards

▪ Include SNOMED CT data within the clinical records storage schema ▪ Mapping from existing data entry templates or message templates to a SNOMED CT equivalent ▪ Introduction of SNOMED CT into the suite of data entry tools ▪ Propagating SNOMED CT changes as part of scheduled product maintenance ▪ Introducing SNOMED CT into the payload of electronic messages ▪ Migrating clinical records between systems in bulk ▪ Replicating existing reports or other outputs but with SNOMED CT EHR design for use with SNOMED CT

▪ Terminology service options ▪ Import, store and update SNOMED CT from release files ▪ General factors applicable to services ▪ Basic services ▪ Search services ▪ Mapping services SNOMED CT Services

Further Questions?

10.EHR design for use with SNOMED CT Include SNOMED CT data within the clinical records storage schema Mapping from existing data entry templates or message templates to a SNOMED CT equivalent Introduction of SNOMED CT into the suite of data entry tools Propagating SNOMED CT changes as part of scheduled product maintenance Introducing SNOMED CT into the payload of electronic messages Migrating clinical records between systems in bulk Replicating existing reports or other outputs but with SNOMED CT 11.Customization Extensions and configuration Drug Extensions Localization of descriptions: Language and dialect preferences Localization of derivatives Queries Ownership 12.Licensing 13.References