Discussion for the Observables Project Group July 25, 2016

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

0 Progress Report on Work for Establishing Mechanisms for Feedback and Analysis on WOISAs /ISRs 9 February 2014 PCT/MIA Quality Subgroup Meeting.
RIT Software Engineering
SE 450 Software Processes & Product Metrics 1 Defect Removal.
Chapter Three Copyright © 2004 John Wiley & Sons, Inc. Problem Definition and the Research Process Copyright © 2004 John Wiley & Sons, Inc. Chapter Three.
Software Compliance: Are we there yet? Looking back and moving forward.
United Nations Economic Commission for Europe Statistical Division Applying the GSBPM to Business Register Management Steven Vale UNECE
Copyright © The Open Group 2011 Your Name Your title 44 Montgomery Street Suite 960 San Francisco, CA USA Tel
© Grant Thornton | | | | | Guidance on Monitoring Internal Control Systems COSO Monitoring Project Update FEI - CFIT Meeting September 25, 2008.
Concept Model for observables, investigations, and observation results For the IHTSDO Observables Project Group and LOINC Coordination Project Revision.
Project Proposal: CTS2 SDK Presentation to OHT Steering Committee.
Problem Definition Chapter 7. Chapter Objectives Learn: –The 8 steps of experienced problem solvers –How to collect and analyze information and data.
Lifecycle of a Requirement in Product Development Scenario RMsis – v Simplify Requirement Management for JIRA.
SNOMED CT A Technologist’s Perspective Gaur Sunder Principal Technical Officer & Incharge, National Release Center VC&BA, C-DAC, Pune.
CI R1 LCO Review Panel Preliminary Report. General Comments –Provide clear definition of the goals of the phase (e.g. inception), the scope, etc. in order.
C-HOBIC FINDINGS VALIDATION - REPORT AND CONSENSUS ACTIVITY Kathryn Hannah, Anne Casey, Zac Whitewood-Moores C-HOBIC.
LOINC and SNOMED CT David Markwell Head of Implementation and Education International Health Terminology Standards Development Organisation 1.
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
University of Wyoming Financial Reporting Initiative Update April 2016.
LOINC – SNOMED Cooperation on Content Overview for Mapping SIG October 2014 Amsterdam, Netherlands.
Mapping International Classification for Nursing Practice (ICNP) and SNOMED CT Submitted by the ICNP Programme Team to IHTSDO Nursing Special Interest.
Substances Redesign Project update for Content Committee February 11, 2015.
Transforming CIMI into SNOMED expressions Source model Target model Model mapping Source file Target file XSLT Issues.
LOINC-SNOMED CT Cooperation Project LOINC terms with component such as “xxx.identified”: Classification and answer list.
LOINC – SNOMED CT Cooperation Project Issue Review Use of “+” and “&” in LOINC Components June 27, 2016.
LOINC – SNOMED CT Cooperation on Content IHTSDO Business Meetings: IPaLM SIG & Observable and Investigation model project April 2016 London, England.
Table core Part file Answer file Group file
LOINC – SNOMED Cooperation on Content
SNOMED CT Content Roadmap July, 2015
LOINC – SNOMED CT Cooperation on Content
Representation of Hypersensitivity, Allergy and adverse reactions in SNOMED CT Bruce Goldberg, MD, PhD.
Kathy Giannangelo, Map Lead
Training Documentation – Replacing GSPR with RFQ 2.0
Software Quality Engineering
SNOMED CT Logic Profile Enhancement Yongsheng Gao, 2017/07/11
SNOMED CT Content Roadmap July, 2015
Information Organization
Scope The scope of this test is to make a preliminary assessment of the fitness of the Draft Observables and Investigation Model (Observables model)
Security SIG in MTS 05th November 2013 DEG/MTS RISK-BASED SECURITY TESTING Fraunhofer FOKUS.
SNOMED CT, Synoptic Observables and Clinical Genomics
Software Quality Engineering
Issue Review Use of “+” in LOINC Components.
SCC P2P – Collaboration Made Easy Contract Management training
LOINC – SNOMED CT Cooperation Project Update
The Software Development Cycle
Drug and Substance Project Update
External Validation of Quality Programs
Problem Definition and the Research Process
Kathy Giannangelo, IHTSDO
Drug and Substance Project Update
IEEE Std 1074: Standard for Software Lifecycle
LOINC – SNOMED CT Cooperation Project Issue Review
LOINC – SNOMED CT Cooperation Project Issue Review
Conducting the performance appraisal
Conducting the performance appraisal
Service Delivery and Support Program Update – April 25, 2018
Office of Education Improvement and Innovation
Management of Change Report Errors to Management.
“Managing your caseload”
IS&T Project Reviews September 9, 2004.
DEVELOPMENTAL LEARNING AND TARGETED TEACHING
CRANDEM: Conditional Random Fields for ASR
Amendment Invoice Task Force Progress Report
RAASP – Solution Options Scenario Comparison
External Validation of Quality Programs
National Clinical Terminology & Information Service Terminology Update
Mapping Data Production Processes to the GSBPM
Status of Exceptional Events Implementation Guidance
Validation by Process Owner Validation by Project Leader
The Software Development Cycle
Presentation transcript:

Discussion for the Observables Project Group July 25, 2016 Review of Feedback from Melissa Mary (bioMerieux) on LOINC – SNOMED CT Cooperation Project phase 3 Alpha release Discussion for the Observables Project Group July 25, 2016

Background Melissa Mary submitted analysis of LOINC – SNOMED CT Cooperation Project phase 3 Alpha release as feedback to IHSDO on 10 June Melissa Mary presented analysis of LOINC – SNOMED CT Cooperation Project phase 3 Alpha release to the Observables PG on 26 June, 2016 Focus on LOINC Term classification with SNOMED CT and suitability for query and/or aggregation Analysis of previous project alpha releases focused on LOINC Part mapping to SNOMED CT concepts and attributes FAS and SSA to comment on analysis in this presentation h

Classification metrics – equivalent LOINC Terms 46 LOINC Terms classified as equivalent 14 result of 1 mismapping in original base file (LOINC Part to SNOMED CT concept map error) 6 result of having similar bacteria identification LOINC Terms mapped similarly and designated fully defined 20 result from duplication within LOINC 6 result from inconsistent/unclear LOINC Terms

Classification metrics – equivalent LOINC Terms: 14 Amphetamine Terms Example: LOINC-28 and LOINC-195

Classification metrics – equivalent LOINC Terms: 14 Amphetamine Terms These 14 equivalencies a result of 1 mismapping in original base file (LOINC Part to SNOMED CT concept map error) Previous solution determined with input from RII and Substance Team: LP COMPONENT Amphetamine mapped to 703842006 | 1- phenylpropan-2-amine (substance) and LP mapped to 703841004 | Substituted amphetamine (substance) Came up during internal review again prior to release and map was changed so both LPs map to 703842006 | 1-phenylpropan- 2-amine (substance) JIRA ticket to clarify with RII – not sure of status. Action: Clarify with RII and remap as appropriate so equivalencies do not occur (JIRA tickets: LOINC-28 and LOINC-195) LOINC-28 and LOINC-195

Classification metrics – equivalent LOINC Terms: 6 bacteria identification Terms

Classification metrics – equivalent LOINC Terms: 6 bacteria identification Terms These 6 equivalencies a result of similar Terms being mapped the same and marked fully defined Previous solution (2014-2015) determined with IHTSDO internal team that these should be equivalent Discussion in April 2016 Business Meeting that these should be mapped with different techniques such as biotyping (264788002), serotyping ( 258075003), phage typing (to be created) Action: Create new typing technique concept and remap these Terms using the technique concepts so equivalencies do not occur (JIRA tickets: LOINC-160, LOINC-173, etc.) LOINC-160, LOINC-173

Classification metrics – equivalent LOINC Terms: 20 duplicate Terms Examples: LOINC-28 and LOINC-195

Classification metrics – equivalent LOINC Terms: 20 duplicate Terms These 20 equivalencies are a result of duplication within LOINC Have been confirmed by RII or are being considered by RII RII plan to deprecate most of the duplicate Parts and Terms For the “unadjusted” Terms, RII has already marked them as discouraged and mapped them to the generic term Action: Remove duplicate Parts and Terms from project files after they are removed from LOINC (JIRA tickets: LOINC-152, LOINC-158, LOINC-149, LOINC-155) Update documentation to include these duplicates until the time they are removed from LOINC Update documentation to explain the status of the “unadjusted” Terms (JIRA ticket: LOINC-187)

Classification metrics – equivalent LOINC Terms: 6 inconsistent/unclear Terms Examples:

Classification metrics – equivalent LOINC Terms: 6 inconsistent/unclear Terms These 6 equivalencies seem to be duplicates at first but are actually unclear Terms within LOINC that can be clarified and improved Have been confirmed by RII or are being considered by RII RII plan to improve existing Parts and Terms Action: Update maps for Parts and Terms in project files after the corrections are made in LOINC (JIRA tickets: LOINC-159, LOINC-117, LOINC-157) Update documentation to reference these issues until the time they are corrected in LOINC

Classification metrics – subClassOf inference Classification deemed consistent overall, with 3 potential errors identified Analyzed two main types of inference: 1. surDefinition Example: increment of test definition of addition of information Challenge, Method, etc. Discussed in previous analysis: RII confirmed that these inferences are correct Action: Update documentation to point this out

Classification metrics – subClassOf inference Analyzed two main types of inference: 2. subClassOf errors: Property hierarchy, e.g. log#/volume is descendant of #/volume Component hierarchy, see example below Action: create JIRA tickets to track issues, discuss with relevant groups (e.g., sent to Ed. Adv. Group)

Improvement of tests query using SNOMED CT ontology Why were Antibacterial antibody Terms included? Why were results of query with SNOMED less than with LOINC? What was the query set for LOINC (all of LOINC or just alpha release set)? Can we see the results of the query? We would like to see more details on the tests performed here. Seeing the results would help us