Consumer Proxy for Cross-Language Clinical Document Query Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The medical industry faces challenges in sharing and retrieving clinical documents across different datacenters due to incompatible standards, formats, and languages, which hinders seamless communication and data integration.
Innovation Solution
A computer-implemented method and system that translates queries from one language, such as DICOM, into another, like XDS, to facilitate communication between document consumers and databases, using a consumer proxy that processes queries, resolves wildcards, and selects compatible data objects, enabling retrieval of clinical documents across disparate systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple datacenters use different standards and languages for clinical documents, then each datacenter can maintain its own independent system, but document consumers cannot directly communicate with or retrieve data from other datacenters
Solution Approach 1:
The patent introduces a hub system that acts as an intermediary between document consumers and multiple datacenters. The hub receives queries from document consumers, translates them into the appropriate language for each datacenter, and retrieves results. This mediator enables cross-datacenter communication without requiring direct compatibility between datacenters, resolving the contradiction by maintaining independence while enabling interoperability.
2Adaptability or versatility
If data in various datacenters uses different formats (e.g., serial number formats, patient identification numbers), then each datacenter can use its own preferred format, but document consumers cannot directly search and retrieve data using their own format
Solution Approach 1:
The hub system dynamically changes query parameters based on the target datacenter's requirements. It translates patient identification formats, serial number formats, and other data parameters from the document consumer's format into the appropriate format for each datacenter. This parameter transformation enables document consumers to search using their own formats while successfully querying datacenters that use different formats.
3Adaptability or versatility
If a document consumer operates in a first language while a datacenter operates in a second language, then each system can use its own language, but the document consumer cannot directly query the datacenter
Solution Approach 1:
The hub serves as a language intermediary that receives queries in the document consumer's language, translates them into the datacenter's language, executes the query, and translates the results back. This language mediation layer allows systems to maintain their native languages while enabling seamless communication and data retrieval across language barriers.
Data Source
AI summary
A computer implemented method of performing at least one document consumer query using a processor and a memory coupled to the processor, said method comprising the steps of: receiving at least one query for at least one clinical documents in a first query language from at least one document consumer; translating the query into a second query language to obtain a translated query; conducting the translated query in at least one database compatible with the second query language by the processor to obtain a first result; and providing the obtained first result to the document consumer. In some embodiments, the first query language is Digital Imaging and Communications in Medicine (DICOM) language, or the Hypertext Transfer Protocol (HTTP) language, and the second language is Cross-Enterprise Document Sharing (XDS) language.