© University of Manchester Creative Commons Attribution-NonCommercial 3.0 unported 3.0 license Quality Assurance, Ontology Engineering, and Semantic Interoperability.

Slides:

Advertisements

Similar presentations

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

Advertisements

Dr. Leo Obrst MITRE Information Semantics Information Discovery & Understanding Command & Control Center February 6, 2014February 6, 2014February 6, 2014.

Catalogue, synthesise Templates, forms, data sets used in real, diverse health settings Formal representation of clinical business object REQUIREMENTS.

Consistent and standardized common model to support large-scale vocabulary use and adoption Robust, scalable, and common API to reduce variation in clinical.

Common Terminology Services 2 (CTS2)

1 Software Engineering Lecture 11 Software Testing.

Using the Semantic Web to Construct an Ontology- Based Repository for Software Patterns Scott Henninger Computer Science and Engineering University of.

Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,

2006 Ontopia AS1 Towards an Ontology Design Methodology Initial work Lars Marius Garshol CTO, Ontopia TMRA

How can Computer Science contribute to Research Publishing?

Distributed Database Management Systems. Reading Textbook: Ch. 4 Textbook: Ch. 4 FarkasCSCE Spring

3/18/19990© 1999, Health Level Seven, Inc. Introduction: Vocabulary domains Marital Status –single (never married) –married –divorced –separated “Vocabulary”

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:

Fundamentals of ISO.

DITA and Topic Maps Bringing the Pieces Together Topic Maps Conference 2008, Oslo Joe Gelb President, Suite Solutions.

ICS-FORTH May 25, The Utility of XML Martin Doerr Foundation for Research and Technology - Hellas Institute of Computer Science Heraklion, May.

Unit 11.2b: Data Quality Attributes Data Quality Improvement Component 12/Unit 11 Health IT Workforce Curriculum Version 1.0/Fall

Metadata Standards and Applications 5. Applying Metadata Standards: Application Profiles.

Proficiency Approach in Teaching Chinese

9 th Open Forum on Metadata Registries Harmonization of Terminology, Ontology and Metadata 20th – 22nd March, 2006, Kobe Japan. Commonalities and Differences.

Managing Software Quality

SC32 WG2 Metadata Standards Tutorial Metadata Registries and Big Data WG2 N1945 June 9, 2014 Beijing, China.

Unit 11C: Data Quality Attributes Data Quality Improvement This material was developed by Johns Hopkins University, funded by the Department of Health.

Requirements Analysis

Profiling Metadata Specifications David Massart, EUN Budapest, Hungary – Nov. 2, 2009.

University of Dublin Trinity College Localisation and Personalisation: Dynamic Retrieval & Adaptation of Multi-lingual Multimedia Content Prof Vincent.

Artificial intelligence project

A Case Study of ICD-11 Anatomy Value Set Extraction from SNOMED CT Guoqian Jiang, PhD ©2011 MFMER | slide-1 Division of Biomedical Statistics & Informatics,

Nancy Lawler U.S. Department of Defense ISO/IEC Part 2: Classification Schemes Metadata Registries — Part 2: Classification Schemes The revision.

Survey of Medical Informatics CS 493 – Fall 2004 September 27, 2004.

DL.org All WGs Meetings, Rome, May 2010 Quality Interoperability Approaches, case studies and open issues DL.org Quality Working Group Rome, 28 th.

Terminology and HL7 Dr Colin Price HL7 UK 11 th December 2003.

CDL-Flex Empirical Research

ISO 9001:2008 to ISO 9001:2015 Summary of Changes

Terminology and documentation*  Object of the study of terminology:  analysis and description of the units representing specialized knowledge in specialized.

Metadata and Versioning VIF workshop 22 nd April

BAA - Big Mechanism using SIRA Technology Chuck Rehberg CTO at Trigent Software and Chief Scientist at Semantic Insights™

Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.

EuroRec Seal 2010 Dr. J. Devlies, ProRecSarajevo, August 31th 2009 The EuroRec Seal 2010 Dr. Jos Devlies, EuroRec Sarajevo, August 31 st 2009.

Proposals on standardisation process in ESS, The Hague_ ESS net Preparation of Standardisation 1 Proposals on standardisation process.

Proposed NWI KIF/CG --> Common Logic Standard A working group was recently formed from the KIF working group. John Sowa is the only CG representative so.

10/24/09CK The Open Ontology Repository Initiative: Requirements and Research Challenges Ken Baclawski Todd Schneider.

OWL Representing Information Using the Web Ontology Language.

Of 33 lecture 1: introduction. of 33 the semantic web vision today’s web (1) web content – for human consumption (no structural information) people search.

Issues in Ontology-based Information integration By Zhan Cui, Dean Jones and Paul O’Brien.

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.

© University of Manchester Creative Commons Attribution-NonCommercial 3.0 unported 3.0 license Lexically Suggest, Logically Define: QA of Qualifiers &

Ontology Evaluation, Metrics, and Metadata in NCBO BioPortal Natasha Noy Stanford University.

Approach to building ontologies A high-level view Chris Wroe.

1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.

Ontologies for Terminologies, Knowledge Representation & Software: Benefits & Gaps (“Don’t make the tea”) (Only a part of Knowledge Representation) Alan.

SNOMED CT A Technologist’s Perspective Gaur Sunder Principal Technical Officer & Incharge, National Release Center VC&BA, C-DAC, Pune.

1 Integration of data sources Patrick Lambrix Department of Computer and Information Science Linköpings universitet.

© University of Manchester Creative Commons Attribution-NonCommercial 3.0 unported 3.0 license Quality Assurance, Ontology Engineering, and Semantic Interoperability.

Instance Discovery and Schema Matching With Applications to Biological Deep Web Data Integration Tantan Liu, Fan Wang, Gagan Agrawal {liut, wangfa,

Semantic Interoperability in GIS N. L. Sarda Suman Somavarapu.

Chapter 6 Guidelines for Modelling. 1. The Modelling Process 1. Modelling as a Transformation Process 2. Basic Modelling Activities 3. Types of Modelling.

ISWG / SIF / GEOSS OOSSIW - November, 2008 GEOSS “Interoperability” Steven F. Browdy (ISWG, SIF, SCC)

Ontologies COMP6028 Semantic Web Technologies Dr Nicholas Gibbins

SNOMED-CT Vocabulary Standard (Certification) Review Final Recommendations VCDE-WS bi-monthly meeting | 2 Oct 2008 Review Team: Christopher Chute Brian.

UNIFIED MEDICAL LANGUAGE SYSTEMS (UMLS)

SNOMED CT Search & Data Entry

Models & Modelling Heather Leslie Sebastian Guard Heather Grain

Fundamentals of ISO.

Chair of Tech Committee, BetterGrids.org

, editor October 8, 2011 DRAFT-D

The role of metadata in census data dissemination

Presentation transcript:

© University of Manchester Creative Commons Attribution-NonCommercial 3.0 unported 3.0 license Quality Assurance, Ontology Engineering, and Semantic Interoperability wrt Terminologies & Ontologies Alan Rector BioHealth Informatics Group School of Computer Science & Northwest Institute of BioHealth Informatics University of Manchester, Manchester M13 9PL

© University of Manchester Creative Commons Attribution-NonCommercial 3.0 unported 3.0 license 2 End-to-end preservation of meaning ►Faithful transmission of information ►The same actions/decisions/treatment where-ever the patient is treated ►Decisions based on the largest pool of research data possible Decisions on Input / output Decisions on output / input

© University of Manchester Creative Commons Attribution-NonCommercial 3.0 unported 3.0 license 3 Aspects of Artifacts for Faithful Interoperability wrt terminologies / ontologies ►Competence / coverage - ►does it provide the information? can it answer the relevant questions? Identify value sets? Constrain what is legal? What can be said where? ►Correctness ►with regards to what gold standard? ►Usability - ►can it be used by authors? end users? rearchers? …? ►Reliability ►do users always enter / understand information the same way? the same user? different users? different locales? ►is it always bound to documents / EHRs in the same way? ►Robustness - what errors are introduced in the face of the unexpected / incorrect use? How likely are different types of incorrect usage? ►technical? ►human factors?

© University of Manchester Creative Commons Attribution-NonCommercial 3.0 unported 3.0 license 4 Faithfulness & QA at all levels ►Pragmatic ‣ are the same decision taken by all interoperating systems / users? ‣ does everyone use it the same way? (inter-rater reliability)? ‣ do users use it as intended - rater-author consensus? ►Semantic / Ontological ‣ are the intended meanings explicit? correct? attributed to authorities? ‣ do users understand the implications of their entries? queries? Logical / Software -Are the inferences and answers to queries as intended? -Does the logical model match the intended semantics? -What extra-logical representation is needed? How can it be validated? -Is it logically self consistent ? Does extralogical operations conform to spec? ‣ Lexical / linguistic -Are ID and Naming conventions observed? synonyms adequate? -Do labels reflect clinical discourse intuitively? Are they misleading? -Are multilingual/multi-cultural issues addressed? Validated? Anomalies public? -* Syntactic -Does the data model connect properly? - …

© University of Manchester Creative Commons Attribution-NonCommercial 3.0 unported 3.0 license 5 QA methods for terminologies / ontologies Human FactorsOntological / Logical / Software Pragmatic End-to-end decision testing inter-rater reliability / repeatability Corpus studies for content coverage Metadata for: provenance, editorial status, versioning & localisation, known issues, mappings, links to external resources, guidelines, … Semantic / Ontological Specification of questions to be asked / answered Authoritative consultation Consistency with external sources Textual definitions & paraphrases Analysis of definitions & hierarchies Logical / Software Challenge testing Usability studies Language generation for user friendly validation of logical structure Logical definitions & descriptions Correctness of inferences, logical hierarchies, & query answering Logical consistency Schema / pattern / criteria conformance testing (unit testing; regression testing) Connectivity testing Lexical / Linguistic Corpus studies for language: synonyms anaphora, variants, … Comprehension studies Back translation studies Language generation Text mining Lexicon structure

© University of Manchester Creative Commons Attribution-NonCommercial 3.0 unported 3.0 license 6 Potential actions ►Establish collaboratory for practical testing of interoperability of each component against agreed competencies ►Technical ►Human factors ►End-to-end ►Resource groups to address specific known issues in key vocabularies and standards ►SNOMED, LOINC, ICD, … ►Support Interworking of ICD-11 & SNOMED