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.

Slides:



Advertisements
Similar presentations
Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 1 Medical.
Advertisements

Query Health Concept-to-Codes (C2C) SWG Summary Outputs
Getting Practical Mapping Strand – reflecting on professional practice John Wardle, Centre for Science Education, Sheffield Hallam University.
Dimensional Modeling.
Review of Criteria for the EAP Disability Category of Intellectual Impairment (II) 2009 DEPARTMENT OF EDUCATION AND TRAINING.
 Implementing terminology requires supporting tools  Tools required are highly dependant on the type of implementation  Covered in this presentation.
IHE Profile Proposal: Dynamic Configuration Management October, 2013.
Query Health Concept Mapping Activity November 10, 2011.
Scope of TOGAF ADM The scope of the four architecture domains of TOGAF align very well with the first four rows of the Zachman Framework, as shown in the.
Breaking down the barriers to collaboration with industry.
Yohanan Spruch - ExLibris Israel Eva Krall - ExLibris Deutschland The Open Archive Initiative in the Scope of Library Systems © 2001.
Copyright Irwin/McGraw-Hill Data Modeling Prepared by Kevin C. Dittman for Systems Analysis & Design Methods 4ed by J. L. Whitten & L. D. Bentley.
VSAC Users’ Forum Thursday, January 15 2:00 – 3:00 PM, EST.
Lessons Learned from Getting Data into STORET: A State’s Perspective Mike Beauchene, State of Connecticut Department of Environmental Protection; Mellony.
Amy Sheide Clinical Informaticist 3M Health Information Systems USA Achieving Data Standardization in Health Information Exchange and Quality Measurement.
Introduction to openEHR
Query Health Concept-to-Codes (C2C) SWG Meeting #10
Systems Engineering in a System of Systems Context
Standards for Internal Control in the Government Going Green Standards for Internal Control in the Federal Government 1.
EleMAP: An Online Tool for Harmonizing Data Elements using Standardized Metadata Registries and Biomedical Vocabularies Jyotishman Pathak, PhD 1 Janey.
University of Sunderland COMM80 Risk Assessment of Systems ChangeUnit 14 The RAMESES Method. COMM80: Risk Assessment of Systems Change Unit 14.
Azara Proprietary & Confidential Overview June 2014 Improving Patient Outcomes through Data.
Unit 16 Procedural Programming
Keeping KUD’s Concise What do your students need to KNOW, UNDERSTAND and DO to master unit content?
Practice Access Improvement Tools and the introduction of National Practice Access Improvement and Innovation Network Susan Bishop and Jennifer Wilson.
Copyright © The Open Group 2011 Your Name Your title 44 Montgomery Street Suite 960 San Francisco, CA USA Tel
Second Annual Japan CDISC Group (JCG) Meeting 28 January 2004 Julie Evans Director, Technical Services.
Discussion of the main data management or database building issues that may be involved in the early stages of designing a new multicentre, clinical trial.
Client Registry An enterprise master patient index (EMPI), or Client Registry manages the unique identity of citizens receiving health services with the.
Supporting Industry Change Planning: Risk, Issue & Milestone Assessment Process Clarifications 04/08/2014.
Supporting Industry Change Planning: Risk & Milestone Assessment Process & Tools 07/07/2014.
University of Sunderland CSEM04 ROSCO Unit 13 Unit 13: Supplementary Slides for the RAMESES Method CSEM04: Risk and Opportunities of Systems Change in.
Business Continuity Program Orientation (insert presentation date) (This presentation is a template that requires adjustments to meet your needs)
Query Health Vendor Advisory Meeting 12/15/2011. Agenda Provide Overview of Query Health Seek Guidance and Feedback on Integration Approaches.
Andrew S. Kanter, MD MPH a,b a Millennium Villages Project, Earth Institute, Columbia University, New York, USA b Department of Biomedical Informatics,
Understanding eMeasures – And Their Impact on the EHR June 3, 2014 Linda Hyde, RHIA.
Concept to Codes Approach. Visual Representation PSMA Code 1 Code 2 PSMA Code 1 Code 2 LOINC Code Code LOINC Code Code SNOMED.
S&I Standards Organization Engagement & Communication Plan DRAFT Standards Support Team 1 September 2011.
Query Health Concept-to-Codes (C2C) SWG Meeting #11 February 28,
NLM Value Set Authority Center Curation and delivery of value sets for eMeasures eMeasures Issues Group (eMIG) May 24, 2012 NLM.
HIT Standards Committee Vocabulary Task Force Task Force Report and Recommendation Jamie Ferguson Kaiser Permanente Betsy Humphreys National Library of.
Metadata By N.Gopinath AP/CSE Metadata and it’s role in the lifecycle. The collection, maintenance, and deployment of metadata Metadata and tool integration.
Veterinary Adaptation of SNOMED-CT ® We don’t have to eat the whole elephant!
© 2005 NORTHROP GRUMMAN CORPORATION 2 11 Jan 06 Northrop Grumman Private / Proprietary Level I Terminology Service Bureau Vision Processes  Procedures.
Description and exemplification use of a Data Dictionary. A data dictionary is a catalogue of all data items in a system. The data dictionary stores details.
HEaTED’s Competency Assessment Toolkit for Technical Staff (CATTS)
Business Intelligence Pathway Method 5 th Meeting Course Name: Business Intelligence Year: 2009.
Shaun Grannis, MD, MS, FAAFP FACMI Biomedical Informatics Scientist Regenstrief Institute / Indiana University The Impact of Interoperability / HIE to.
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
Integrating the Healthcare Enterprise The IHE Process: Developing Standards-based Solutions Kevin O’Donnell Co-chair, IHE Radiology Planning Committee.
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.
supported by the Local Government Association a local government initiative sharing nationally to improve services locally Information.
C-CDA Scorecard Rubrics Review of CDA R2.0 Smart C-CDA Scorecard Rules C. Beebe.
Embedding Professional Standards the SMART way Peter Hartley Ruth Whitfield.
3M Health Information Systems 1© 3M All Rights Reserved. 3M Health Information Systems Data Standardization Interoperability.
LOINC-SNOMED CT Cooperation Project LOINC terms with component such as “xxx.identified”: Classification and answer list.
Presented for discussion with Implementation SIG Heather Grain.
Implementing the NHS dictionary of medicines and devices (dm+d)
Kathy Giannangelo, Map Lead
The Five Secrets of Project Scheduling A PMO Approach
Leveraging Features and Functionality in PeopleSoft 9
Literature review Methods
Education SIG Implementors Curriculum
Mapping SIG Provide a platform for sharing experiences and expertise of mapping and linkages Exploring methods of automated mapping from SNOMED CT to.
Efficient Remediation of Terms Inactivated by Dictionary Updates
How we use the SNOMED CT to ICD-10 map in the Netherlands
Public Health Reporting – S&I Framework CEDD Overview
Move Update Starting the Clock
Agenda Who are we? 1 Introductions Journey so far 2
Data Standardization Interoperability 3M Health Information Systems
Presentation transcript:

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 incorporated into the Technical Expression. 1.All mappings are Purpose and Goal Specific 2.Hierarchy within mappings is important to ensure the concepts are appropriately mapped and can be drilled down to a granular level 3.A centralized Data Dictionary or central Terminology System is used to store mappings and is common practice in many healthcare organizations 4.As Standards such as ICD9, SNOMED CT, LOINC etc. are modified and updated, ongoing maintenance of mappings can be challenging 5.Identifying a Best Match OR Alternate/Default Map is necessary since concepts may not always have an exact map 6.It is important to identify the context of the queries to understand what information is being requested (example - Ordered drug vs. Administered drug) 7.Ongoing maintenance of mappings is very resource intensive and requires dedicated skilled resources such as Clinicians/ Informaticists 8.Many mapping tools and resources are publicly available or accessible that can be leveraged by organizations and further developed, refined, and maintained for use 9.Most Concept Mapping tools maintain data in its original form 1

Recurring Key Themes – Direct impact to Technical Framework The below list includes themes across many of the different presentations to date. The key themes in blue below directly impact the Technical Framework of QH. All others are addressed on the next slide. 1.All mappings are Purpose and Goal Specific 2.Hierarchy within mappings is important to ensure the concepts are appropriately mapped and can be drilled down to a granular level 3.A centralized Data Dictionary or central Terminology System is used to store mappings and is common practice in many healthcare organizations 4.As Standards such as ICD9, SNOMED CT, LOINC etc. are modified and updated, ongoing maintenance of mappings can be challenging 5.Identifying a Best Match OR Alternate/Default Map is necessary since concepts may not always have an exact map 6.It is important to identify the context of the queries to understand what information is being requested (example - Ordered drug vs. Administered drug) 7.Ongoing maintenance of mappings is very resource intensive and requires dedicated skilled resources such as Clinicians/ Informaticists 8.Many mapping tools and resources are publicly available or accessible that can be leveraged by organizations and further developed, refined, and maintained for use 9.Most Concept Mapping tools maintain data in its original form 2

Recurring Key Themes Do not directly impact Technical Framework However, Important to consider While not all key themes on the last slide may directly impact the Technical Framework, it is important to consider some of the key themes seen in the C2C presentation series (in green below) 1.All mappings are Purpose and Goal Specific 2.Hierarchy within mappings is important to ensure the concepts are appropriately mapped and can be drilled down to a granular level 3.A centralized Data Dictionary or central Terminology System is used to store mappings and is common practice in many healthcare organizations 4.As Standards such as ICD9, SNOMED CT, LOINC etc. are modified and updated, ongoing maintenance of mappings can be challenging 5.Identifying a Best Match OR Alternate/Default Map is necessary since concepts may not always have an exact map 6.It is important to identify the context of the queries to understand what information is being requested (example - Ordered drug vs. Administered drug) 7.Ongoing maintenance of mappings is very resource intensive and requires dedicated skilled resources such as Clinicians/ Informaticists 8.Many mapping tools and resources are publicly available or accessible that can be leveraged by organizations and further developed, refined, and maintained for use 9.Most Concept Mapping tools maintain data in its original form 3