Medical Imaging Data Encapsulation for Cross-System Application Launch
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current medical imaging systems face challenges in sharing and manipulating data created in one application within a different system, as existing solutions like DICOM do not allow data embedding with applications, and API-based integration is costly and time-consuming.
Innovation Solution
The method involves data encapsulation, where a Data Processing and Analysis Application (DPAA) trigger is embedded with patient data and exported to a Picture Archiving and Communicating System (PACS), allowing decapsulation and re-launching of the DPAA instance in the foreign environment for manipulation, without requiring common APIs or code-level integration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data is exported using standard formats like DICOM, then data can be transferred between systems, but the ability to manipulate data with native application tools is lost
Solution Approach 1:
The patent embeds a trigger object containing application identification and launch parameters directly within the exported data structure (e.g., DICOM file). This nested trigger allows the receiving system to automatically invoke the native application that created the data, restoring access to original manipulation tools without requiring manual intervention or API integration.
Solution Approach 2:
The trigger object acts as an intermediary between the exported data and the native application. It carries metadata about the originating application and enables the receiving system to bridge back to the original tool, facilitating seamless data manipulation across system boundaries while maintaining standard data exchange formats.
2Ease of operation
If application-specific tools are integrated between systems, then data manipulation capability is maintained, but integration cost and complexity increase significantly
Solution Approach 1:
The patent extracts the essential application identification and launch parameters from the complex application environment and encapsulates them in a lightweight trigger object. This separation allows data to carry its own application context without requiring the receiving system to implement or maintain complex API integrations with the original application.
Solution Approach 2:
Instead of creating deep integrations or copies of application functionality, the patent copies only the essential metadata needed to relaunch the original application (application ID, data identifiers, launch parameters). This minimal copying approach maintains manipulation capability while avoiding the complexity of full application integration.
3Ease of operation
If application-specific protocols are used for data exchange, then native functionality is preserved, but compatibility with other systems decreases
Solution Approach 1:
The trigger object is designed as a universal mechanism that can be embedded within standard data formats like DICOM, which are already widely adopted across medical imaging systems. This single trigger structure can identify and launch different applications, making the solution broadly compatible while preserving native functionality through the standardized container.
Data Source
AI summary
A method and system is provided for data/process sharing. A decapsulating unit is provided and resides on first system where a first application system resides. The decapsulating unit monitors, on the first system, when encapsulated data from a second application system residing on a second system, is present in the first application system. The encapsulated data, once present on the first system, is decapsulated by the decapsulating unit to obtain a trigger corresponding to the second application system and encapsulated in the encapsulated data. The obtained trigger is analyzed and the second application system is launched on the first system based on the trigger.