Cloud Medical Imaging View Layer Architecture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity and high maintenance effort of existing IT structures in medical facilities for managing and processing medical data, particularly in scaling with increasing data volume and computing power, along with difficulties in integrating new user devices like smartphones and tablets, lead to inefficiencies and increased latency when using cloud solutions.

Innovation Solution

A system with a layered architecture for viewing and processing medical image data, utilizing a view layer, viewmodel layer, model layer, and driver layer, allowing for flexible operation across different devices and data types, with a generic design enabling efficient data processing and display without relying on cloud computing for 2D and 3D image data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional client-server architectures with multiple parallel server systems are used, then data management and processing capabilities are provided, but device complexity and maintenance effort increase significantly

Engineering Contradiction:
Improvedata management capabilityVSAvoidIT infrastructure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent combines multiple parallel server systems (PACS, RIS, HIS, AV systems) into a single cloud-based platform that provides integrated data management and processing capabilities. The cloud server consolidates functions previously distributed across multiple systems, reducing infrastructure complexity while maintaining versatility.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The cloud-based system provides universal access to medical imaging and data processing functions across multiple device types (PCs, smartphones, tablets, PDAs). A single system serves multiple purposes: storing medical images, processing data, providing user interfaces, and supporting various operating systems, eliminating the need for separate specialized systems.

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

2Reliability

If conventional information systems with rigid front-end software are used, then specific data types are managed effectively, but integration of new user devices becomes difficult and costly

Engineering Contradiction:
Improvedata processing reliabilityVSAvoiddevice integration capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system employs dynamic, adaptive front-end software that can automatically adjust to new device types and operating systems. The cloud-based architecture allows the user interface to be rendered differently across devices (smartphones, tablets, PCs) while maintaining consistent data processing reliability through standardized backend protocols and cloud-based rendering services.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The cloud server acts as an intermediary between diverse user devices and the medical imaging data. It provides a standardized interface that translates between different device capabilities and the core data processing functions, enabling reliable data processing across varied devices without requiring separate front-end software for each device type.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If cloud solutions are implemented, then scalability and accessibility improve, but latency increases due to data transmission distances

Engineering Contradiction:
Improvesystem scalabilityVSAvoiddata access latency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system segments data storage and processing functions, keeping frequently accessed medical imaging data in cloud storage while allowing local devices to cache recently used data. The cloud server handles computationally intensive tasks (volume rendering, image processing) while simpler display operations can be performed locally, reducing latency for common operations while maintaining scalability.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP3066596B1System for displaying and editing data for a medical device
Publication Date: 2022.05.11 SIEMENS HEALTHCARE GMBH
  • EP3066596B1 patent drawingFigure 1
  • EP3066596B1 patent drawingFigure 2
  • EP3066596B1 patent drawingFigure 3

AI summary

A system (1) for displaying and editing data for a medical device (2, 2') is specified. The system (1) comprises at least one viewing application (34) for execution on a user appliance (8, 9, 11, 12), which application is set up to display medical image data records (B) that are kept in cloud storage (19) in a public cloud (13). In respect of its component architecture, the viewing application (34) comprises a View layer (52), a ViewModel layer (55), a Model layer (57) and a driver layer (59). In this case, the ViewModel layer (55) is of generic design in the sense that it defines a common set of functions for the display and editing of 2D image data and 3D image data.