Medical Imaging Application Integration with File-System Contracts

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current medical imaging platforms struggle with integrating and updating diverse software applications due to limitations in the DICOM format and API-specific integration methods, leading to interoperability issues and complex testing requirements.

Innovation Solution

A method for integrating software applications using a file system-based approach, where applications are designed independently of the platform, utilizing a contract that specifies input and output directories and environment variables, allowing for easy testing and deployment without requiring a specific platform emulator.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the DICOM format and protocol are used for software application integration, then data transmission between imaging appliances and platforms is standardized, but the format is not optimum for generating and sharing reports based on intermediate results and does not allow easy configuration of software applications according to certain contexts

Engineering Contradiction:
Improveadaptability of software application configurationVSAvoidcomplexity of integration method
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (file system with standardized input/output directories and environment variables) between the DICOM data format and the software application configuration. This intermediary enables flexible configuration and report generation without modifying the core DICOM protocol, thus improving adaptability while managing complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The integration method is segmented into distinct components: DICOM data input, file system interface with virtual directories, environment variable configuration, and software application execution. This segmentation allows each component to be independently configured and optimized, improving overall system adaptability.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If API-specific integration methods are used, then access to configuration services is facilitated, but the API is generally specific or dedicated to a given medical imaging platform, requiring application redesign for different platforms

Engineering Contradiction:
Improveease of accessing configuration servicesVSAvoidportability across different platforms
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal integration interface that works across different medical imaging platforms by using standardized file system operations and environment variables. This universal interface allows the same software application to be deployed on different platforms without redesign, achieving portability while maintaining ease of configuration access through the standardized interface.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If software applications are integrated using platform-specific methods, then integration is achieved, but testing requires a test platform provided by the designer, which is not always available or can prove complex or costly

Engineering Contradiction:
Improvereliability of integrationVSAvoidcomplexity of testing requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent uses file system virtual directories that can be mapped to actual directories on any system. This allows creating a copy of the required test environment using standard file operations, eliminating the need for proprietary test platforms while maintaining integration reliability through standardized interfaces.

Inventive Principle:
Principle #26Copying

4Adaptability or versatility

If a medical imaging platform hosts a plurality of software applications to fit a constantly increasing diversity of cases, then the platform can handle more pathologies and organs, but the platform cannot include at all times all the software applications or the most up-to-date versions

Engineering Contradiction:
Improvediversity of cases handledVSAvoidspeed of updating software applications
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements a dynamic software integration model where applications can be added, updated, or removed through standardized file system operations and environment variable configurations. This dynamic approach allows the platform to quickly adapt to new software versions and diverse medical cases without requiring complex reconfiguration, thus improving both versatility and update speed.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20250226081A1Method for integrating and executing an application implemented by a medical imaging platform
Publication Date: 2025.07.10 OLEA MEDICAL
  • US20250226081A1 patent drawing
  • US20250226081A1 patent drawing

AI summary

The invention relates to a method for integrating and executing a software application to be implemented by a medical imaging platform running a file system. Such a method comprises a step of reading an agreement dedicated to a software application, the agreement comprising the access paths for input and/or output directories of the file system in order to write and/or read the values of the input/output data of the software application. The invention further relates to a medical imaging platform suitable for implementing such a method for integrating and executing software applications.