Graph Database Clinical Decision Support System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current medical reporting systems face challenges with free-text reports being non-machine-readable, non-standardized, and prone to errors, while structured reports require complex ontology expansions and are difficult to implement in electronic health record applications, hindering clinical decision-making and workflow efficiency.

Innovation Solution

A method and system that extract medical concepts and relations from structured reports, integrate them into a graph database, weight their relevance, and provide recommendations to users for composing report templates and structured medical reports, utilizing graph database technology to support data-based clinical decision-making.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If free-text reports are used, then reporting flexibility and physician autonomy are improved, but machine-readability and standardization deteriorate

Engineering Contradiction:
Improvereporting flexibilityVSAvoidmachine-readability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system segments the report generation process into structured modules with predefined templates for different anatomical regions and findings. Physicians select and fill in standardized sections rather than writing free-text, ensuring machine-readability while maintaining flexibility through modular assembly of report components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary layer of structured templates and decision support tools between the physician's clinical observations and the final report. This intermediary structure enables automatic extraction of key findings and structured data while preserving physician autonomy in clinical judgment.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If structured reports with medical ontologies are used, then machine-readability and standardization are improved, but system complexity and implementation difficulty worsen

Engineering Contradiction:
ImprovestandardizationVSAvoidontology complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements structured reporting with essential medical ontologies for key findings and anatomical structures, rather than attempting to incorporate complete ontology systems. This partial implementation achieves sufficient standardization for clinical decision-making while avoiding the overwhelming complexity of comprehensive ontology integration.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system pre-configures report templates with commonly used medical terminologies and structured formats for specific clinical scenarios. This preliminary structuring reduces the complexity burden during actual reporting, as the heavy lifting of standardization is done in advance rather than during clinical workflow.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If comprehensive medical ontologies are expanded to include new concepts and relations, then semantic interoperability and knowledge coverage are improved, but implementation effort and time required worsen

Engineering Contradiction:
Improveontology coverageVSAvoidexpansion effort
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system automatically extracts medical concepts, relations, and key findings from structured reports and uses this extracted data to dynamically expand and update the ontology knowledge base. This self-service approach allows continuous improvement of ontology coverage without requiring manual curation efforts, as the system learns from actual clinical reporting data.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback loops where extracted medical concepts from reported cases are fed back into the ontology expansion process. This continuous feedback mechanism enables automatic adaptation and growth of the medical ontology based on real-world clinical usage patterns, reducing the need for manual expansion efforts.

Inventive Principle:
Principle #23Feedback

4Measurement precision

If manual extraction and structuring of medical concepts is performed, then accuracy of concept representation is improved, but processing time and workload worsen

Engineering Contradiction:
Improveconcept extraction accuracyVSAvoidreporting efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The system replaces manual mechanical extraction of medical concepts with automated natural language processing and information extraction algorithms. These computational methods automatically identify and structure medical concepts, relations, and key findings from clinical reports, maintaining high accuracy while eliminating the time-consuming manual workload.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system performs self-service automatic extraction of medical concepts from structured reports using built-in NLP capabilities. This automated process accurately identifies medical entities, relations, and key findings without requiring manual intervention, thereby maintaining precision while significantly improving reporting efficiency and reducing physician workload.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20240221952A1Data-based clinical decision-making utilising knowledge graph
Publication Date: 2024.07.04 QMEDIFY
  • US20240221952A1 patent drawing
  • US20240221952A1 patent drawing
  • US20240221952A1 patent drawing

AI summary

A method, a computer system, and a computer program product are provided for supporting data-based clinical decision-making. Medical concepts and relations between medical concepts contained in a structured medical report and/or a template for such reports are extracted. The template and/or the structured medical report comprise a data structure representing the medical concepts and relations between these medical concepts. These extracted medical concepts and relations between the medical concepts are then integrated into a graph database and weighted according to their relevance. Based on the weights one or more recommendations for actions a user may take when composing report templates and/or structured medical reports are inferred and presented to the user.