SNOMED CT Implementation Approaches. National Resource Centre for EHR Standards (NRCeS) C-DAC, Pune

Similar documents
Terminology Harmonization

Lab Results Interface (LRI) The Flexible Implementation Guide (IG) Standards and Interoperability Framework Initiative (ONC) Ken McCaslin, FHL7

Standards Development

Vocabulary Sharing and Maintenance using HL7Master File / Registry Infrastructure

warwick.ac.uk/lib-publications

Business Architecture in Healthcare

10-CM/PCS Barriers and Opportunities

Integrating the Healthcare Enterprise Patient Care Devices

Interoperability, critical element for an ehealth Strategy

WhamTech SmartData Fabric Healthcare Configurable FHIR REST APIs

Efficiently Sharing All of a Patient s Data With All their Providers Completing the Model

Meaningful Use and the 3M Healthcare Data Dictionary

Presenter(s): Dave Venier. Topic Rosetta Interoperability (C-CDA and IHE) Level 200

Health Information Exchange Content Model Architecture Building Block HISO

Transforming healthcare in disruptive times

The impact of openmedicine findings for standardization

A NOVEL ALGORITHM FOR CLEANICAL ROUTINE USING SYSTEM INTEGRATION OF PACS AND CBIR

Apelon DTS on FHIR. John Gresh, Director of Product Development

Exchanging Patient Demographics Information using ANSI/HL7 v2.8.2

CMS and ehealth. Robert Tagalicod Director, Office of ehealth Standards and Services (OESS)

Workshop 2. > Interoperability <

Using standards to make sense of data

Data Definition, Data Capture, Quality Assurance and Adherence to Informatics Standards (including UDI) in CRNs

Acquiring Experience with Ontology and Vocabularies

Standards for Image & Report Sharing for Tele-radiology & EPR - update on Canada Infoway & US HIE Peter Bak, Ph.D., CMC EHI Live 2012 May 2012

From Integration to Interoperability: The Role of Public Health Systems in the Emerging World of Health Information Exchange

A Linked Data Translation Approach to Semantic Interoperability

The Development of Health Information Standards in Thailand

Developing A Semantic Web-based Framework for Executing the Clinical Quality Language Using FHIR

S&I Framework Initiatives

The Estonian ehealth experience strategy and results. Piret Simmo Estonian ehealth Foundation Standardization manager

The information system architecture in public health

HITSP/IS06. January 25, 2010 Version 2.0. Healthcare Information Technology Standards Panel. Population Perspective Technical Committee.

The GAPS Framework. To develop national healthcare ICT systems, countries need to work on 4 important fundamental topics.

April 25, Dear Secretary Sebelius,

Overview Functionality Maintenance Future

DATA WAREHOUSING. a solution for the Caribbean

Large scale ehealth deployment in Europe: insights from concurrent use of standards

HDD Access. Lessons Learned from the Design, Development and Implementation of

ConCert FAQ s Last revised December 2017

Deliverable 4.4: Final specification of EHR4CR semantic interoperability solutions

The M Data Extractor (MDE) White Paper

INTEROPERABILITY & STANDARDS IN EHEALTH KATRIEN VAN GUCHT PUBLIC

NIST Normative Test Process Document: e-prescribing (erx) Test Tool

Semantic Web and ehealth

Terminology as a Service HL7 AU

Ensuring Quality Terminology Mappings in Distributed SOA Environments

Customer Guidance For Requesting Changes to SNOMED CT

UNDER THE HOOD. API Overview

The SHARPn phenotyping funnel. Phenotype specific patient cohorts

CCG questions: EMIS. SNOMED CT in Primary Care. Updated: 31 th July 2017

Linked Data: Fast, low cost semantic interoperability for health care?

Interoperability driven integration of biomedical data sources

SNOMED Clinical Terms

The use of standard content specifications in a national health interoperability framework

CDX Conformance Profile EMR System Conformance CDA Level 1

Getting Started with Clinical Quality Language: Technical Implementation for Vendors

My Health, My Data (and other related projects) Yannis Ioannidis ATHENA Research Center & University of Athens

Interoperability Specifications and Conformance Testing Services Made Available on the Tukan Platform

LOINC for Claims Attachments

M403 ehealth Interoperability Overview

Interoperability. Doug Fridsma, MD PhD President & CEO, AMIA

P1752 Working Group Meeting

(60 min) California State Updates

Using OpenEHR platform and HL7/IHE interoperability

Information Architecture. It s utility with the NHS landscape. Presented by Richard Kavanagh, Head of

Use Cases for Argonaut Project -- DRAFT Page

CPRD Aurum Frequently asked questions (FAQs)

Beyond Regional Health Information Exchange in China: A Practical and Industrial-Strength Approach

Jena based Implementation of a ISO Metadata Registry. Gokce B. Laleci & A. Anil Sinaci

Examples for best practices in ehealth

Developing A Semantic Web-based Framework for Executing the Clinical Quality Language Using FHIR

Models of Uses & Models of Meaning. Alan Rector. ode.org protege.stanford.org

Setup of Direct Messaging Address and Referring Provider

24/18/2014 ICAAP 11 Bangkok, Thailand 22 November 2013

HL7 s Vision for 2016 & Beyond

HEDIS 2018 Volume 2 Value Set Directory User Manual Version

Semantic-sensitive extraction of EHR data to support adverse drug event reporting

Health Information Exchange - A Critical Assessment: How Does it Work in the US and What Has Been Achieved?

Towards Ease of Building Legos in Assessing ehealth Language Technologies

SNOMED CT, FHIR, and more

Discuss and finalize recommendations on Entity-Level Provider Directories (ELPDs):

Organizational Track 1 p.m.-2 p.m. Maintenance and Updating Margo Imel, RHIT, MBA Terminology ManagerMapping, SNOMED, International Pat Wilson, RT

Exchanging Patient Demographics Information using ANSI/HL7 v2.8.2

... user-friendly explanations for HL7, SNOMED, DICOM, XML, BDT

Comparing Approaches to Measuring the Adoption and Usability of Electronic Health Records: Lessons Learned from Canada, Denmark and Finland

Implementing a Document Standard: Perspectives on Adoption, Interoperability, and Utilization

IPS. New Orleans WGM Q3 SDWG

CDA- RE-GENERATION AND INTEGRATION FOR HEALTH INFORMATION EXCHANGE BASED ON CLOUD COMPUTING SYSTEM

Electronic Health Records with Cleveland Clinic and Oracle Semantic Technologies

Semantic interoperability, e-health and Australian health statistics

Boubacar Sow Miyagi University

Quality Data Model (QDM)

Robert Snelick, NIST Sheryl Taylor, BAH. October 11th, 2012

Guidance on the use of CodeableConcept

HL7 s Common Terminology Services Standard (CTS)

CPRD Aurum Frequently asked questions (FAQs)

Curation of Large Scale EHR Data for Use with Biobank Samples

ICT sebagai pemacu bisnes dalam perkhidmatan penjagaan kesihatan yang berkualiti dan bersepadu

HHS/CMS Unified Agenda - NPRM

Transcription:

SNOMED CT Implementation Approaches National Resource Centre for EHR Standards (NRCeS) C-DAC, Pune

SNOMED CT with no Health Record SNOMED CT is a powerful modern clinical terminology Comprehensive scope and support for detailed information A code system providing standard representation of clinical meanings A global reference terminology with multilingual term support A polyhierarchy with ontological features that enable inference SNOMED CT is designed for use in electronic health records On its own SNOMED CT does nothing! SNOMED CT is a component that delivers value when implemented as part of an electronic health record

Health Records with no SNOMED CT Making health records electronic A significant step forward Improves communication Increases availability of relevant information but it is only a partial solution; the real challenge is Making health records meaningful Identifying significant facts in oceans of data Enabling effective meaning-based retrieval Linking the EHR to authoritative clinical knowledge SNOMED CT represents clinical information meaningfully as part of a well-designed EHR

Benefits to Vendors: why implement SNOMED CT STRATEGIC BENEFITS Staying Competitive and Relevant to the Market Selling into International Markets Meeting Clinician Expectations Supporting Standards Retaining Existing Customers PRACTICAL BENEFITS Common Terminology Ease of Adoption Enhanced User Interfaces Enhanced Analytics Using Clinical Data to Meet External Reporting Requirements Integration of Third Party Products

Integration Approaches SNOMED CT can be integrated as: A code system An interface terminology An indexing system A common terminology A dictionary To store clinical information To capture and display clinical information To retrieve clinical information To communicate in a meaningful way To integrate heterogeneous data To query, analyze and report To link health records to knowledge resources

EHR System Design

A Reference Terminology for Data Integration Benefits Patient data may be integrated from a variety of structured and unstructured sources, including hospital health record systems and mobile devices Patient data coded in a consistent way can be used for analytics, querying, decision support or displaying to the user Correlations between data from disparate sources can be made using SNOMED CT s defining relationships

An Indexing System for Data Retrieval Benefits Supports research and analysis in a local system or shared data warehouse Supports use of SNOMED CT for analysis and reporting For identification of cohorts of patients for research studies For exploration of data in support of clinical process review To improve the user experience of longitudinal record review Zero or minimal disruption to run-time processes

A Code System for Clinical Data in the EHR Benefits No change to terms that clinicians are used to seeing in the user interface Patient data stored using SNOMED CT concepts Communication using shared meaning Can utilize internationally developed mappings such as the mappings to ICD-9 and ICD-10 SNOMED CT is available for direct use in electronic communications Standardized integration with decision support rules

An Interface Terminology For EHR Data Entry Benefits Standardized descriptions in the user interface No mapping required between interface terms and codes stored in patient record Supports enhanced techniques for data entry, search and display e.g. searching over synonyms of the same concept Patient data stored using SNOMED CT concepts Readily available master reference data e.g. allergen list

For Simple Aggregation And Analysis of Data Benefits Supports the use of SNOMED CT for analysis and reporting purposes, such as: To improve the user experience For exploration of data in support of clinical process review For identification of patients for research studies Can utilize internationally developed mappings such as the mappings to ICD-9 and ICD-10 Standardized descriptions in the user interface Patient data stored using SNOMED CT concepts Communication using shared meaning

Full Use of SNOMED CT Benefits This system combines all the benefits identified for the preceding approaches.

Enhancing EHR Design with SNOMED CT Include SNOMED CT data for Storing clinical records 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 Replicating existing reports or other outputs but with SNOMED CT

Data Entry using SNOMED CT

Constrain searches by Concept and Description status

Constrain searches by super type ancestors (e.g. Disease)

Constrain search to avoid multiple hits on the same concept

Order shortest matching terms first

Order preferred term matches before synonyms

Distinguish identical terms of different concepts

Using SNOMED CT with other standards World Health Organization classifications: ICD-10 Develop and assure maps and links between SNOMED CT and WHO Classifications like SNOMED CT to ICD-9-CM and SNOMED CT to ICD-10 maps LOINC (Logical Observation Identifiers Names and Codes) One result of this will be alignment of the attributes of laboratory tests. This will enable LOINC and SNOMED CT to be used together in a consistent and interoperable manner. Clinical Information Modelling Initiative (CIMI) HL7 message standards, CDA and FHIR Enabling effective use of SNOMED CT in HL7 message

Key to Successful Integration of SNOMED CT Careful planning and understanding key objectives Ease and effectiveness of data entry and display Consistent representation of stored clinical information Methods and approach to effective communication Optimisation of retrieval, analysis and reuse

SNOMED in Action Annaswamy Mudaliar General Hospital, Bangalore (HealthStore HIS developed by CSoft Technologies Pvt. Ltd.) ehealth Kerala Project (JK Technologies) Death Note Form, AIIMS New Delhi (AIIMS) Hyderabad, Telangana (Generation 5 esushrut) District Hospital, Kingkoti Area Hospital, Malakpet Gandhi Hospital, Secunderabad NIMS Panjagutta HealthQik ehospital (NIC Tripura) in-progress Manorama Infosolution Pvt. Ltd. in-progress SNOMED CT Implementation Status IMPLEMENTED-AND-LIVE 9 IMPLEMENTED 3 IN-PROGRESS 16 IN-PLANNING-STAGES 5 0 2 4 6 8 10 12 14 16 18

References Vendor Introduction to SNOMED CT

Thank You nrc-help@cdac.in