Skip to main content
. 2023 Aug 25;24(10):e14127. doi: 10.1002/acm2.14127

TABLE 2.

Comparison between knowledge graph‐based ontology‐specific search solution and the traditional relational database‐based solution from the various oncology data sources.

Comparison metrics Knowledge graph‐based solution Relational database‐based solution
Data integration and interlinking Efficient integration of data from multiple sources and linking through semantic relationships in the knowledge graph Limited ability to integrate and establish relationships between data from different tables in the database
Data discovery and accessibility Enhanced data discoverability and accessibility due to ontology‐based indexing and semantic querying Relatively limited data discoverability and accessibility through traditional SQL queries
Semantic enrichment Relationships among data fields are established and used for searching for the patient cohort. Allows searching for synonym, hyponym terms that is not present in the dataset and gather patient that have similar attributes. Relationships among data fields need to be manually established. Each synonym and hyponym term needs to be manually annotated in the dataset. Limited querying flexibility primarily based on structured SQL queries
Scalability and performance Highly scalable with linking new data from future patient encounters and data from other clinical domains. Is able to handle complex queries due to optimized knowledge graph traversal methods. Performance may degrade with large datasets or complex queries due to table joins and indexing limitations
Data analysis and visualization Enables advanced data analytics, visualization, and identification of trends and patterns in patient outcomes through graph‐based analysis Limited data analysis capabilities and visualization options compared to graph‐based analytics
Data reusability and interoperability Supports data reusability and interoperability by adhering to FAIR principles (findable, accessible, interoperable, and reusable) Relational databases offer limited data reusability and interoperability without additional integration efforts