Immutable Electronic Health Record Storage Without Mining

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database systems lack true immutability for recording database operations, as they either lose historical changes or require costly and resource-intensive blockchain 'mining' for immutable storage.

Innovation Solution

A system utilizing a blockchain-based immutable data storage protocol with a transaction blockchain API, formatting module, and messaging module to serialize and store data operations, including metadata, without the need for costly mining systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If blockchain 'mining' systems are used for immutable storage, then data integrity and immutability are improved, but resource consumption and cost increase significantly

Engineering Contradiction:
Improvedata integrityVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts the essential function of immutable storage from the resource-intensive mining process. By separating the data storage function from the consensus mechanism, the system achieves immutability through cryptographic hashing and distributed ledger technology without requiring energy-consuming mining operations. The core immutability function is extracted and implemented through deterministic block chaining with cryptographic proofs.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent replaces expensive, resource-intensive mining operations with cheaper alternative mechanisms. Instead of using computational power to secure the network, the system uses cryptographic signatures, distributed validation, and economic incentives that are less resource-consuming. The consensus is achieved through lighter-weight mechanisms that maintain security without the high energy costs of proof-of-work mining.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

2Ease of operation

If traditional database update operations are used, then ease of operation is improved, but data immutability deteriorates as historical changes are lost

Engineering Contradiction:
Improvedata update capabilityVSAvoidhistorical change history
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent applies preliminary action by creating an immutable copy of the data state before any update operation occurs. The system captures the pre-update state, creates a cryptographic hash of it, and stores this hash in the blockchain before the update is applied. This preliminary capture of the original state enables both easy updates and complete historical tracking, as each update creates a new chain of cryptographic proofs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying to maintain immutability while allowing updates. Instead of modifying existing records in place, the system creates copies of data states and chains them cryptographically. Each update generates a new copy with a reference to the previous state through hashing, creating an immutable audit trail while allowing the current state to be easily updated. This copying mechanism preserves historical information without restricting operational flexibility.

Inventive Principle:
Principle #26Copying

3Reliability

If database operation logging is enabled, then data recovery capability is improved, but the logging is not truly immutable and can be altered

Engineering Contradiction:
Improvedata recovery capabilityVSAvoidimmutability of operation history
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent merges the data storage function with the audit trail function into a single immutable structure. Instead of maintaining separate databases for data and separate logs for operations, the system combines them into a unified blockchain where each block contains both the data state and cryptographic proof of the operation that produced it. This merging ensures that the operation history is as immutable as the data itself, providing true data recovery capability with guaranteed immutability.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a composite data structure that combines mutable application data with immutable cryptographic proofs. The blockchain records contain a composite of the current data state, the operation that produced it, and cryptographic hashes linking to previous states. This composite structure ensures that both the data and its operational history share the same immutability properties, making tampering with either equally difficult and providing robust data recovery capability.

Inventive Principle:
Principle #40Composite materials

Data Source

PatentUS12399906B2System and method of immutable electronic health record data storage
Publication Date: 2025.08.26 TECHNOLOGIES IP LLC
  • US12399906B2 patent drawing
  • US12399906B2 patent drawing
  • US12399906B2 patent drawing

AI summary

A system and method of immutable electronic health record data storage is presented. The present disclosure provides for a system integrated into a practical application with meaningful limitations to provide a system having an ‘immutable data storage protocol’ used to capture database operations on an immutable ledger. The protocol can consist of one or more ‘operation codes.’ The immutable electronic health record data storage system can provide a blockchain, transaction blockchain API, a blockchain writer API, a formatting module, and a messaging module, among others, that can format, process, and store data according to an immutable data storage protocol.