Medical Imaging Data Encoding for Cross-System Application Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current medical imaging systems face difficulties in sharing and manipulating data between different platforms without costly API-based integration or losing the ability to manipulate data in its native environment, due to limitations in existing standards like DICOM.
Innovation Solution
Encoding an application trigger and patient data ID into grayscales, locations, and frequencies of encoding objects or images, allowing for process sharing and communication between systems without the need for API development or code-level integration, using techniques such as barcode encoding and wavelet transforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If DICOM standard is used for data sharing between medical imaging systems, then data transfer is enabled, but the ability to manipulate data in native environment is lost
Solution Approach 1:
The patent embeds the original application executable and patient data within a container file format (such as ZIP or TAR) that can be transferred via DICOM. This nested structure allows the application to be packaged inside the data container, enabling it to be transported alongside the patient data it needs to process, thus maintaining native manipulation capability while achieving cross-system data sharing.
Solution Approach 2:
The patent introduces a container file as an intermediary that holds both the patient data and the application executable. This intermediary structure acts as a bridge between different medical imaging systems, allowing the application to be transported and executed in a different environment without direct API integration, thus solving the contradiction between data sharing and native manipulation.
2Ease of operation
If API-based integration is implemented between medical imaging systems, then application manipulation is enabled, but integration cost and complexity increase
Solution Approach 1:
Instead of implementing complex API integrations between different medical imaging systems, the patent copies the entire application executable and necessary patient data into a portable container file. This copy approach eliminates the need for system-to-system API connections, reducing integration complexity while maintaining full application functionality in the target environment.
Solution Approach 2:
The patent segments the application functionality from the host system by packaging it as a self-contained executable within the container file. This segmentation allows the application to be independently transferred and executed without requiring integration with the target system's APIs, thereby reducing device complexity and integration overhead.
3Adaptability or versatility
If application executable is embedded in container file, then cross-system transfer is enabled, but file size increases
Solution Approach 1:
The container file format used in the patent is designed to be universal and multi-functional, serving both as a data storage container and as a vehicle for application distribution. By using a standard compressed archive format, the system achieves cross-platform compatibility without requiring proprietary formats, which would increase file size and reduce interoperability.
Solution Approach 2:
The patent employs compression algorithms to change the physical parameters of the stored data, reducing the file size of the embedded application executable and patient data. By applying compression during the container creation process, the system minimizes the size increase while maintaining the ability to embed the complete application package for cross-system transfer.
Data Source
AI summary
Methods and system for data/process sharing between different systems. A trigger response unit is deployed on a first system where a first application resides. The trigger response unit is to detect when a representation corresponding to trigger data from a second application is present in the first application. When such a presence is detected, the detected representation corresponding to the trigger data is decoded to obtain a trigger, wherein the representation encodes the trigger corresponding to the second application and information associated with data. Based on the trigger, the first system launches the second application within the first application on the first system by utilizing the trigger data that include a trigger pattern present in a trigger image.