Ontologies, vocabularies, and data models

Publisher Summary This chapter discusses vocabulary and terminology issues, and challenges related specifically to successful implementation of clinical decision support (CDS) systems. Standard coded data are essential for accurate and reliable execution of decision logic. Coding of data has advantages other than just the execution of the logic. It also makes the maintenance of decision logic easier as the logic references a code rather than referencing all the words that might be used to represent the needed concept. Use of codes makes it possible to translate more easily to different languages. The Arden Syntax does not specify the format of a reference to data in an associated clinical application. Rather, such references are implementation-specific and demarcated by curly braces within the code. The most significant consequence of the curly braces problem is that CDS modules are not readily portable between different systems implementing the Arden Syntax. There are trade-offs between pre- and post-coordinated representations. Alternatives for pre- and post-coordinated representations of data are discussed. Terminology plays an important role in all aspects of the life cycle of decision support programs. The usual life cycle consists of phases with different tools and capabilities needed at some of these different phases.

[1]  C. McDonald,et al.  LOINC, a universal standard for identifying laboratory observations: a 5-year update. , 2003, Clinical chemistry.

[2]  J. Cimino.  Desiderata for Controlled Medical Vocabularies in the Twenty-First Century , 1998, Methods of Information in Medicine.

[3]  Clement J. McDonald,et al.  Development of the Logical Observation Identifier Names and Codes (LOINC) vocabulary. , 1998, Journal of the American Medical Informatics Association : JAMIA.

[4]  C. McDonald,et al.  Logical observation identifier names and codes (LOINC) database: a public use set of codes and names for electronic reporting of clinical laboratory test results. , 1996, Clinical chemistry.

[5]  Kent A. Spackman,et al.  SNOMED clinical terms: overview of the development process and project status , 2001, AMIA.

[6]  D. Lindberg,et al.  The Unified Medical Language System , 1993, Methods of Information in Medicine.

[7]  Ian Horrocks,et al.  The GRAIL concept modelling language for medical terminology , 1997, Artif. Intell. Medicine.

[8]  T A Pryor,et al.  The arden syntax for medical logic modules , 1990, International journal of clinical monitoring and computing.

[9]  Omolola Ogunyemi,et al.  GELLO: An Object-Oriented Query and Expression Language for Clinical Decision Support: AMIA 2003 Open Source Expo , 2003, AMIA.

[10]  T Beale.  The Archetype Definition Language Version 2 (ADL2) , 2006 .

[11]  Betsy L. Humphreys,et al.  Technical Milestone: The Unified Medical Language System: An Informatics Research Collaboration , 1998, J. Am. Medical Informatics Assoc..

[12]  Steven H. Brown,et al.  A semantic normal form for clinical drugs in the UMLS: early experiences with the VANDF , 2002, AMIA.

[13]  Stanley M. Huff,et al.  Detailed Clinical Models for Sharable, Executable Guidelines , 2004, MedInfo.

[14]  Kent A. Spackman,et al.  The SNOMED clinical terms development process: refinement and analysis of content , 2002, AMIA.

[15]  Alan L. Rector.  Defaults, Context, and Knowledge: Alternatives for OWL-Indexed Knowledge Bases , 2004, Pacific Symposium on Biocomputing.

[16]  Stanley M. Huff,et al.  Standards for detailed clinical models as the basis for medical data exchange and decision support , 2003, Int. J. Medical Informatics.

[17]  P M Nadkarni,et al.  QAV: querying entity-attribute-value metadata in a biomedical database. , 1997, Computer methods and programs in biomedicine.

[18]  Samson W. Tu,et al.  Protégé-2000: An Open-Source Ontology-Development and Knowledge-Acquisition Environment: AMIA 2003 Open Source Expo , 2003, AMIA.

[19]  James J. Cimino.  Editorial Comments: Controlled Medical Vocabulary Construction: Methods from the Canongroup , 1994, J. Am. Medical Informatics Assoc..

[20]  Alan L. Rector,et al.  The Interface between Information, Terminology, and Inference Models , 2001, MedInfo.

[21]  Steffen Staab,et al.  What Is an Ontology? , 2009, Handbook on Ontologies.

[22]  Stanley M. Huff,et al.  Integrating Detailed Clinical Models Into Application Development Tools , 2004, MedInfo.

[23]  D. Lindberg,et al.  Building the Unified Medical Language System , 1989 .

[24]  Perry L. Miller,et al.  Application of Information Technology: Organization of Heterogeneous Scientific Data Using the EAV/CR Representation , 1999, J. Am. Medical Informatics Assoc..