• Aucun résultat trouvé

Interoperability of Data Models and Terminology Models : Issues with using the SNOMED CT terminology

N/A
N/A
Protected

Academic year: 2022

Partager "Interoperability of Data Models and Terminology Models : Issues with using the SNOMED CT terminology"

Copied!
1
0
0

Texte intégral

(1)

Interoperability of Data Models and Terminology Models: Issues with using the SNOMED CT terminology

Rahil Qamar S., Ph.D.1, Jay (Subbarao) Kola, M.B.B.S.1, Alan L. Rector, M.D.,Ph.D.1 1 Bio-health Informatics Group, University of Manchester, Manchester, U.K.

Abstract

Work in the field of recording standard, coded data in electronic health records and messages is important to support interoperability of clinical systems. It is also important for reducing medical errors caused by misinterpretation and

misrepresentation of data. Standardisation of structured and unstructured data to one or more terminologies such as SNOMED-CT, or ICD requires the help of various integration procedures. We have previously highlighted issues in data models

(openEHR Archetypes) when mapping to a terminology model (SNOMED CT) [1]. In this paper, we describe issues with terminology models (SNOMED CT) when

aligning the concepts to a data model (openEHR Archetypes).

Terminologies and data models play an important role in building structured EHRs and achieving semantic interoperability. Semantic interoperability requires that all recorded data conforms to some reference terminology in order to interpret and reuse it uniformly in all partaking information systems. In the medical domain,

standardising data is of great significance, as controlling the vocabulary used to record patient data is critical to making EHRs safe for exchange and reuse.

The paper recognises the value of SNOMED CT but demonstrates the difficulties of working with it at an integration level. The difficulties in integration arise primarily due to the semantic gaps in the content of the structured data models and terminology models. The same issues might also arise with data obtained from unstructured sources. Despite the broad coverage that SNOMED offers, there are several concepts that are missing. An efficient process for submission of concepts for inclusion is in need, along with formal rules for post coordination.

We believe that in order to achieve the overall objective of semantic interoperability, it is imperative that both data and terminology models are developed with the aim of being able to integrate their clinical content. It is important that both modeling communities are not only cognizant of each others existence but also work closely with each other to ensure that conformance is built into the systems from conception stage. These conformance or compatibility rules should be extended to all other stages of the modeling process i.e. at design time, data integration time, as well as at run- time. It is only then that true interoperability will be achieved, making it possible to build safer health care systems. Reliable and high quality data in these systems will improve the functioning of all health care units heavily dependent on data, reducing medical errors and ultimately providing safer and better patient care.

Reference

[1] Rahil Qamar, Jay Kola, and Alan Rector. Unambiguous data modeling to ensure higher accuracy term binding to clinical terminologies. AMIA 2007 Annual

Symposium, November 2007. Chicago, U.S.A.

Representing and sharing knowledge using SNOMED

Proceedings of the 3rd international conference on Knowledge Representation in Medicine (KR-MED 2008) R. Cornet, K.A. Spackman (Eds)

50

Références

Documents relatifs

General purpose terminology server software facilitates coordinated use of multiple standard medical terminologies for diverse healthcare applications.. SNOMED CT is

It is clear that any change to the structure or representation forms of SCT may have an impact on reference set (subset) development, use within value-sets, and mapping

Never- theless, the proposed usage of XML Technologies like schema validation which is now used in the current version of the standard is able to check some basic rules as

In chapter 1.4, before our conclusion, we come back to the definitions of what we consider as basic terms of a shared framework based on Model Based Systems Engineering methods,

For each Integration Mechanism used to represent model elements as program code structures, a generic runtime class and bidirectional model/code transformations have to be

In more than one third of cases, the SNOMED CT axiomatic expressions did not align well with the intuitive meaning derived from their Fully Specified Names or synonyms,

Choosing Linked Data principles and Ontologies to make rare disease data link- able at the source was our first design decision, as RDF was designed with the objective of

By embedding semantic technologies into familiar data management tools, the SEEK [1] enables semantic annota- tion of new data and the generation and querying of