Healthcare Data Hash Separation for Anonymous Cloud Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing healthcare data management methods fail to ensure security, reliability, and openness due to centralized data storage, which is vulnerable to data breaches, especially with advancements in computer performance like quantum computing.
Innovation Solution
A healthcare data management system that separates personal information and healthcare data by generating hash values, storing them in different databases, and using key hash values to ensure anonymity and secure storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data is centrally stored and managed at one place with simple encryption, then data management is simple and efficient, but security is compromised against quantum computing attacks and centralized data breaches
Solution Approach 1:
The patent divides healthcare data into two separate segments: personal information and healthcare data. Each segment is stored in different locations and protected by different mechanisms. Personal information is hashed and stored separately from the actual healthcare data, so that even if one segment is compromised, the other remains secure. This segmentation resolves the contradiction by maintaining efficient centralized management while improving security through distributed storage of critical components.
Solution Approach 2:
The patent introduces hash values as an intermediary between personal information and healthcare data. The hash value acts as a mediator that links the two without exposing the actual personal information. This intermediary mechanism allows efficient data retrieval and management while preventing direct access to sensitive personal information, thus resolving the security-efficiency contradiction.
2Productivity
If data is centrally stored with simple encryption, then storage and retrieval are efficient, but all data leaks simultaneously when a breach occurs
Solution Approach 1:
By segmenting data into personal information and healthcare data stored in different locations, the patent ensures that a breach of one segment does not necessarily compromise the other. This limits the scope of data leakage, resolving the contradiction between efficient centralized storage and the catastrophic impact of complete data breaches.
Solution Approach 2:
The patent creates a hash copy of personal information that is stored separately from the original data. This copy serves as a reference for data retrieval and validation without containing the actual sensitive information. If a breach occurs, the hash copy can be regenerated or replaced without affecting the stored healthcare data, thus limiting leakage impact while maintaining retrieval efficiency.
3Device complexity
If personal information and healthcare data are stored together, then data management is simplified, but anonymity and security are compromised
Solution Approach 1:
The patent physically and logically separates personal information from healthcare data, storing them in different databases or storage locations. This segmentation increases structural complexity but guarantees anonymity by ensuring that even with access to one segment, the identity cannot be determined without the other segment. The hash linkage maintains manageable complexity while enforcing security.
Solution Approach 2:
The hash value serves as an intermediary that connects personal information to healthcare data without exposing the connection. This intermediary mechanism allows the system to maintain a manageable structure for data retrieval while ensuring anonymity, as the hash does not reveal the original personal information. The contradiction is resolved by using the intermediary to bridge security and manageability requirements.
Data Source
AI summary
Provided are a healthcare data management apparatus and method, and a healthcare data management method, that relate to receiving healthcare data including personal information and healthcare information, storing the personal information and the healthcare information, generating a first personal information hash value corresponding to the personal information, generating a first key hash value corresponding to the personal information hash value, generating a first healthcare hash value on the basis of the first personal information hash value and the first key hash value, and confirming whether the first healthcare hash value is a pre-stored value.