Secure Diagnostic Data Integration via RAM Buffering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing methods for storing and integrating data from diagnostic devices are inefficient and prone to errors, as they often require labor-intensive manual entry and use of unsecured intermediate devices, which can lead to data breaches and violate privacy laws.

Innovation Solution

A system and method for securely integrating device data from diagnostic devices into a backend database server, using a native application to pair with external devices, establish a secure connection, and transfer data without permanent storage on the user device, ensuring data privacy and compliance with regulations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual data entry and intermediate devices are used to transfer diagnostic data, then data can be transferred between devices, but the process becomes time-consuming and error-prone

Engineering Contradiction:
Improvedata transfer efficiencyVSAvoidtime for manual data entry
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent replaces manual mechanical data entry processes with automated electronic data transfer. The diagnostic device directly transmits data to the database server through a secure connection established via pairing mechanism, eliminating the need for manual copying and pasting of results between different systems.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system enables self-service data transfer where the diagnostic device automatically initiates and completes the data transmission process without requiring manual intervention. The automated pairing and data transfer mechanisms allow the system to serve itself by directly connecting to the database server and uploading results automatically.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If intermediate devices are used to store diagnostic data temporarily, then data can be transferred later, but the risk of data breaches and privacy violations increases

Engineering Contradiction:
Improveflexibility in data transfer timingVSAvoiddata breach risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts and eliminates the intermediate device from the data transfer chain entirely. Instead of using portable devices or temporary storage locations that pose security risks, the system establishes a direct secure connection between the diagnostic device and the database server, removing the harmful intermediate step from the process.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a secure connection mechanism as an intermediary that enables direct trust between the diagnostic device and database server. This secure channel acts as a controlled mediator that allows data transfer without requiring physical intermediate devices, thereby maintaining flexibility while eliminating security risks.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If manual data entry is used to input diagnostic results into the database, then data can be entered into the system, but the chances of reporting errors increase

Engineering Contradiction:
Improvesimplicity of data entry processVSAvoidaccuracy of data entry
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent replaces manual mechanical data entry with automated electronic data transmission. The diagnostic device directly pushes data to the database server through programmed interfaces, eliminating human error in data transcription while maintaining ease of operation through automated processes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system incorporates feedback mechanisms where the database server receives and validates data directly from the diagnostic device. This automated feedback loop ensures data accuracy by eliminating manual intervention points where errors could occur, while the process remains simple through automated verification.

Inventive Principle:
Principle #23Feedback

4Ease of operation

If data is stored on portable devices or unsecured locations, then data can be accessed and transferred, but privacy protection laws may be violated

Engineering Contradiction:
Improveaccessibility of stored dataVSAvoidprivacy violation risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent extracts data storage from portable and unsecured locations and consolidates it in a secure, centralized database server. This removes the harmful element of unsecured storage while maintaining accessibility through authorized network access, thereby complying with privacy protection laws.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a secure connection and authorized access mechanism as an intermediary between users and the database. This controlled access layer allows data to remain accessible for authorized operations while preventing unauthorized access, thus protecting privacy rights and complying with legal requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11017116B2Secure integration of diagnostic device data into a web-based interface
Publication Date: 2021.05.25 ONSITE HEALTH DIAGNOSTICS LLC
  • US11017116B2 patent drawing
  • US11017116B2 patent drawing
  • US11017116B2 patent drawing

AI summary

A method of securely integrating device data from an external device with a user device may include implementing a local data call function of a remote application through a native application of the user device such that the remote application receives device data without the device data being permanently stored on the user device; validating the device data with the remote application according to data elements of the device data and a first set of local fields; requesting a first authorization to integrate the device data; associating a first data control element with the data elements according to a first request result; requesting a second authorization to integrate the device data; and populating storage fields that are maintained by a backend and associated with the first control data element, with the data elements according to a second request result.