EHR Data Security via Blockchain Hashing and De-identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for managing Electronic Health Records (EHRs) face challenges in securing user identification details and preventing data tampering, particularly during transmission and storage, which poses security risks and can lead to false insurance claims.
Innovation Solution
A computer-implemented method that involves sending an identification hash to an API server, de-identifying data, generating record hashes, and storing them on a blockchain to ensure secure management of EHR data, preventing linkage back to the user even if servers are hacked, and verifying data integrity using transaction identifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If user identification details are stored in association with EHR data in a database, then data management and retrieval are simplified, but security risk increases significantly during system hacking or data transmission attacks
Solution Approach 1:
The patent extracts user identification details from the EHR data storage system entirely. Instead of storing identification details in the database alongside medical records, the system uses only de-identified data with unique identifiers. The identification details remain exclusively on the user's device, separated from the centralized database, thereby eliminating the security vulnerability while maintaining data management functionality.
Solution Approach 2:
The patent introduces de-identified data as an intermediary between user identification and medical records. The unique identifier acts as a mediator that links user-specific data to their EHR without storing actual identification details in the database. This intermediary layer enables data retrieval and management while preventing direct access to sensitive identification information.
2Ease of operation
If identification details are transmitted from database to user device or from HSP to database, then data accessibility is improved, but vulnerability to MITM attacks and data theft increases
Solution Approach 1:
The patent removes identification details from the transmission pathway entirely. Only de-identified data with unique identifiers is transmitted between the user device and HSP system. The actual identification details never leave the user's device, eliminating the transmission vectors that hackers could exploit through MITM attacks.
Solution Approach 2:
The patent performs de-identification of data before transmission occurs. By removing or encrypting identification details prior to any data exchange, the system preemptively eliminates the security vulnerability that would exist during transmission, rather than attempting to protect against attacks during the transmission process.
3Productivity
If a centralized database stores EHR data with identification details, then data retrieval and management are efficient, but the system becomes a single point of failure for security breaches
Solution Approach 1:
The patent segments the data storage system into two distinct components: user identification details stored locally on the user's device, and de-identified EHR data stored in the centralized database. This segmentation distributes the security risk, so that even if the centralized database is compromised, the actual identification details remain secure on users' devices, eliminating the single point of failure.
4Ease of operation
If user identification is stored centrally, then insurance claim verification is simplified, but false claims and data tampering risks increase
Solution Approach 1:
The patent uses de-identified data with unique identifiers as an intermediary for insurance claim verification. The system can verify claims and link them to users through the unique identifier without exposing or storing actual identification details in the database. This maintains verification functionality while preventing data tampering, as the identification details remain protected on users' devices and cannot be altered in the centralized system.
Data Source
AI summary
There is provided a computer implemented method for secure management of data generated in an Electronic Health Record (EHR) during an episode of care, for a user, wherein the EHR is being maintained in a medical database (140) comprised within a Healthcare Service Provider (HSP) server (130), the computer implemented method comprising the steps of sending an identification hash corresponding to the user to an Application Program Interface (API) server (150) from a first client device (110a); extracting the data from the HSP server (130) and de-identifying the data to obtain de-identified data at the API server (150); generating a record hash at the API server (150); transmitting the identification hash, the record hash and the de-identified data from the API server (150) to a core server (160); receiving the identification hash, the record hash and the de-identified data at the core server (160) and transmitting the identification hash, the record hash and the de-identified data from the core server (160) to a repository database (170) to generate a record identification; transmitting the de-identified data, the record hash and the record identification from the repository database (170) to the first client device (110a), via the core server (160); generating a data hash by hashing the de-identified data and a plurality of attributes corresponding to the de-identified data; generating at the core server (160) a register package based on the data hash, the identification hash and the record hash; storing the register package, from the core server (160), on to a blockchain (180) to generate a transaction identification; transmitting the data hash and the transaction identification from the core server (160) to the repository database (170); and transmitting the transaction identification and the data hash from the repository database (170) to the first client device (110a), via the core server (160).