Subsumption checking between concept queries in different ontologies based on mutual instances

2006 ◽  
Vol 11 (1) ◽  
pp. 68-72
Author(s):  
Kang Da-zhou ◽  
Lu Jian-jiang ◽  
Xu Bao-wen ◽  
Wang Peng ◽  
Zhou Jin
Keyword(s):  
Subsumption Checking

Symbolic Execution with Abstract Subsumption Checking

2006 ◽  
pp. 163-181 ◽  
Author(s):  
Saswat Anand ◽  
Corina S. Păsăreanu ◽  
Willem Visser
Keyword(s):  
Symbolic Execution ◽  
Subsumption Checking

scholarly journals Efficient Probabilistic Subsumption Checking for Content-Based Publish/Subscribe Systems

2006 ◽  
pp. 121-140 ◽  
Author(s):  
Aris M. Ouksel ◽  
Oana Jurca ◽  
Ivana Podnar ◽  
Karl Aberer
Keyword(s):  
Subsumption Checking

scholarly journals Smashing the strict hierarchy: three cases of clinical decision support malfunctions involving carvedilol

2018 ◽  
Vol 25 (11) ◽  
pp. 1552-1555 ◽  
Author(s):  
Adam Wright ◽  
Aileen P Wright ◽  
Skye Aaron ◽  
Dean F Sittig
Keyword(s):  
Decision Support ◽  
Clinical Decision Support ◽  
Clinical Decision ◽  
Health Record ◽  
Architectural Feature ◽  
Β Blocker ◽  
Clinical Content ◽  
Parent Child Relationships ◽  
Clinical Terminologies ◽  
Subsumption Checking

Abstract Clinical vocabularies allow for standard representation of clinical concepts, and can also contain knowledge structures, such as hierarchy, that facilitate the creation of maintainable and accurate clinical decision support (CDS). A key architectural feature of clinical hierarchies is how they handle parent-child relationships — specifically whether hierarchies are strict hierarchies (allowing a single parent per concept) or polyhierarchies (allowing multiple parents per concept). These structures handle subsumption relationships (ie, ancestor and descendant relationships) differently. In this paper, we describe three real-world malfunctions of clinical decision support related to incorrect assumptions about subsumption checking for β-blocker, specifically carvedilol, a non-selective β-blocker that also has α-blocker activity. We recommend that 1) CDS implementers should learn about the limitations of terminologies, hierarchies, and classification, 2) CDS implementers should thoroughly test CDS, with a focus on special or unusual cases, 3) CDS implementers should monitor feedback from users, and 4) electronic health record (EHR) and clinical content developers should offer and support polyhierarchical clinical terminologies, especially for medications.

Sign in / Sign up

Export Citation Format

Share Document