Local Transmission Unit for Medical Data Anonymization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for uploading medical data records to cloud repositories lack flexibility and extensibility, requiring significant changes and testing whenever different data sources or formats are used, leading to high costs and inefficiencies.

Innovation Solution

A local transmission unit with a core module and plug-ins allows for the receipt, anonymization, and upload of medical data records to a cloud repository, enabling easy extension of functionality without altering the core module, and providing flexible anonymization based on the needs of associated remote applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If monolith software is used for uploading medical data records to the cloud, then the system is simple in structure, but the flexibility and extensibility are poor, requiring changes and retesting of the whole application whenever new data sources or formats are needed

Engineering Contradiction:
Improveflexibility and extensibilityVSAvoidsoftware architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The software is divided into a core module and separate plug-ins. Each plug-in handles specific data sources or formats, allowing the system to be extended by adding new plug-ins without modifying the core module. This segmentation enables independent development, testing, and deployment of individual functionalities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The core module is designed with universal interfaces that can work with multiple types of data sources and formats through different plug-ins. This allows a single core module to serve multiple purposes and support various remote applications without requiring custom modifications.

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

2Ease of manufacture

If monolith software is used for uploading medical data records, then the system structure is simple, but the testing cost and time increase significantly when changes are needed

Engineering Contradiction:
Improveease of system modificationVSAvoidtesting time and cost
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

By segmenting the software into independent plug-ins, each with a specific function, modifications can be made to individual plug-ins without affecting the core module or other plug-ins. This isolation allows for targeted testing of only the modified components, significantly reducing testing time and cost.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The core module acts as an intermediary between the data sources and the cloud upload functionality. It provides standardized interfaces that plug-ins implement, allowing changes in data sources or formats to be handled by plug-in modifications alone, without requiring changes to the core upload logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If different data formats and sources are supported, then the system becomes more versatile, but the complexity of managing and testing the entire system increases

Engineering Contradiction:
Improvedata source and format compatibilityVSAvoidsystem management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Each data source and format is handled by a dedicated plug-in, which encapsulates the specific logic for that source or format. This segmentation isolates complexity within individual plug-ins while maintaining a simple overall system structure through the standardized core module interface.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each plug-in is self-contained and handles its own data processing and format conversion requirements. The plug-ins independently manage their specific data sources and formats, reducing the need for complex centralized management logic in the core module.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11636929B2Uploading a data record to a cloud repository
Publication Date: 2023.04.25 SIEMENS HEALTHINEERS AG
  • US11636929B2 patent drawing
  • US11636929B2 patent drawing
  • US11636929B2 patent drawing

AI summary

A method and a local transmission unit are for uploading a data record to a cloud data repository. The method includes receiving a medical data record by a local transmission software, the local transmission software including a core module and available plug-ins, each available plug-in being associated with a remote application. The method further includes generating an anonymized data record based on the medical data record by a processing plug-in, the processing plug-in being one of the available plug-ins. Finally, the method includes uploading the anonymized data record to a cloud data repository, the anonymized data record in the cloud data repository being accessible by the remote application associated with the processing plug-in.