IHTSDO Observables Project Call

Slides:



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

VHA Issue Paper: HL7 Methodology Discussion 11 January 2001 Government Projects SIG.
IBM Software Group ® Design Thoughts for JDSL 2.0 Version 0.2.
Web Services Architecture An interoperability architecture for the World Wide Service Network.
Copyright © 2001 College of American Pathologists Pseudophakic corneal edema Sample Hierarchy for Corneal Edema Idiopathic corneal edema Phakic corneal.
Copyright © 2001 College of American Pathologists Sample Hierarchy for Nasal Septoplasty Hair bearing flap to eyebrow Repair of eyebrow Operation on eyebrow.
Copyright © 2001 College of American Pathologists Sample Hierarchy for Fine Needle Biopsy of Abdominal Wall Mass Tru cut biopsy of lesion of abdominal.
Chapter 5: Project Scope Management
Week 5: Changing behavior– Motivation & coaching
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Copyright © 2001 College of American Pathologists Sample Hierarchy for Hepatitis Chronic viral hepatitis Chronic viral hepatitis C About SNOMED Relationships.
Quantitative Research
Science Inquiry Minds-on Hands-on.
Mrs. Maninder Kaur 1Maninder Kaur
The chapter will address the following questions:
Drawing on Linguistics: Concepts, Metaphors and Colored Pencils Kristen Precht-Byrd.
Dm+d User Guide Information Standards Delivery 1.
HL7 HL7  Health Level Seven (HL7) is a non-profit organization involved in the development of international healthcare.
Concept Model for observables, investigations, and observation results For the IHTSDO Observables Project Group and LOINC Coordination Project Revision.
Chapter 12 View Design and Integration. McGraw-Hill/Irwin © 2004 The McGraw-Hill Companies, Inc. All rights reserved. Outline Motivation for view design.
Software Architecture and Design Dr. Aldo Dagnino ABB, Inc. US Corporate Research Center October 23 rd, 2003.
1 The Theoretical Framework. A theoretical framework is similar to the frame of the house. Just as the foundation supports a house, a theoretical framework.
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 1 DATABASE SYSTEMS Instructor Ms. Arwa Binsaleh.
Logical Model Collaboration Scope, proposal, and next steps.
Agenda: 1/2 Welcome back Final project overview and schedule – Clarification & questions Restriction analysis challenge Samples – gene cloning Homework:
Introduction to the Framework: Unit 1, Getting Readyhttp://facultyinitiative.wested.org/1.
Yr 7.  Pupils use mathematics as an integral part of classroom activities. They represent their work with objects or pictures and discuss it. They recognise.
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
SNOMED CT Family of Languages Dr Linda Bird, IHTSDO Implementation Specialist.
Nursing Occupations Proposed by: Cynthia Lundberg, BSN Judith Warren, PhD, RN.
1 Kyung Hee University Interaction Diagrams Spring 2001.
V7 Foundation Series Vignette Education Services.
Understanding the Value and Importance of Proper Data Documentation 5-1 At the conclusion of this module the participant will be able to List the seven.
Action Research for School Leaders by Dr. Paul A. Rodríguez.
Introduction to XML SSE 3200 Web-based Services Michigan Technological University Nilufer Onder.
1 Representing and Reasoning on XML Documents: A Description Logic Approach D. Calvanese, G. D. Giacomo, M. Lenzerini Presented by Daisy Yutao Guo University.
Stages of Research and Development
COP Introduction to Database Structures
UNIT-IV Designing Classes – Access Layer ‐ Object Storage ‐ Object Interoperability.
Logical Database Design and the Rational Model
Business System Development
LOINC – SNOMED CT Cooperation on Content
UNIFIED MEDICAL LANGUAGE SYSTEMS (UMLS)
Understanding Data Storage
11th HL7 Australia Conference, 13th December 2006
Document Development Cycle
Microsoft Office Access 2010 Lab 2
Scope The scope of this test is to make a preliminary assessment of the fitness of the Draft Observables and Investigation Model (Observables model)
Data Quality Webinar for General Practice
CIMI Semantics Roundup
Conceptual Frameworks, Models, and Theories
Chapter 3 The Relational Database Model
ACTION LEARNING Ian Duncan Action Learning Facilitator
Chapter 6 Normalization of Database Tables
Literacy Content Specialist, CDE
Chapter 4 Entity Relationship (ER) Modeling
Chapter 20 Object-Oriented Analysis and Design
Learning Styles – Honey & Mumford
Understand and Use Object Oriented Methods
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
CIMI Semantic Binding Issue
An Introduction to Software Architecture
Ontology.
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Employee engagement Delivery guide
Entity-Relationship Diagram (ERD)
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
SNOMED CT Diagramming notes
Assessment Objectives...
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Presentation transcript:

IHTSDO Observables Project Call November 26, 2012 Brief introduction to the US VHA LEGO Project (an opportunity to apply the new observables model to the "real world“) Questions on using specific attributes in the new observables model

Brief project introduction Sponsored by US Veteran’s Health Administration (VHA) Explores the feasibility of applying an experimental information model (called the SIM or Simple Integrated Model) to VHA Structured Data Entry Forms. Focused on modeling the multiple-choice questions and answers of the VHA Progress Note Construction Set (PNCS) into simple, consistent, accurate, and complete units, known as LEGOs (Lightweight Expressions of Granular Objects).

Basic LEGO structure in XML <lego> <assertion> <discernible> <concept> <rel> </rel> </concept> </discernible> <qualifier /> <value /> <timing /> <assertionComponents/> </assertion> </lego> SNOMED CT observable entity concepts with nested relationships, similar to a SNOMED CT expression in the compositional grammar Using the new observables model (to avoid obsolescence) Classifiable by extensions to existing SNOMED CT Description Logic (DL)

Work with the Observables Project Group To ensure that the new observables model is correctly and consistently applied to LEGOs. To gain experience with applying the new observables model in the “real world.” To suggest concepts that should be added to SNOMED CT in order to serve as role values. To identify areas where revisions to the new observables model may be warranted.

Modeling non-laboratory observables Many LEGOs must represent non-laboratory observables. Are any additions to the model for such cases currently under discussion? Is there a subset of attributes typically used for modeling non-laboratory observables? PROPERTY TYPE? INHERES IN? INHERENT LOCATION? TOWARDS? Others?

Use of the PROPERTY TYPE attribute Every example in the Observables Style Guide seems to have a PROPERTY TYPE attribute. Is this attribute required? Many LEGO observables do not have an obvious property type such as color or depth. An example is "decubitus ulcer of the left heel.“ In such cases, would "Presence" be an appropriate PROPERTY TYPE? Or would it be preferable to omit the PROPERTY TYPE entirely?

Use of INHERES IN and INHERENT LOCATION attributes Can either of these be used without a Property Type attribute? There are cases where a morphologic abnormality (decubitus ulcer) must be connected to an anatomic site (left heel). Should INHERES IN typically be used with the morphologic abnormality and INHERENT LOCATION be used with the anatomic site?

Use of the TOWARDS attribute The Observables Style Guide says: “This attribute is used to specify the third element of a relational quality, the first two elements being the type of property and the entity in which the quality inheres.” Further clarification of how to use this attribute (especially for non-laboratory observables) would be appreciated…

Discussion of group process going forward Goals from LEGO project perspective Ensure that LEGO modeling reflects current thinking on new observables model Provide feedback to group on difficult use cases encountered during LEGO modeling. Accommodate aggressive deliverable schedule for LEGO production Avoid disrupting work of current Observables Project Group