Hierarchical Database Association Metadata for Reliable Record Matching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database management systems face inefficiencies and reliability issues in executing database operations due to direct user-provided instructions that can compromise data integrity, leading to frequent re-execution of operations.

Innovation Solution

A database association management platform enables end users to provide record relationship instructions through a sequence of RSI, RSE, RSNI, and NSC instructions, enforcing hierarchical matching logic to ensure data integrity and automate efficient cross-record association.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If direct user-provided instructions are used for database operations, then ease of operation is improved, but data integrity and reliability deteriorate

Engineering Contradiction:
Improveease of operationVSAvoiddata integrity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces an intermediary layer (the database management system with hierarchical matching logic) between the user and the database operations. User-provided instructions are processed through this intermediary that enforces data association rules, ensuring that operations maintain data integrity while still allowing user control. The system mediates between user intent and database state changes.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by pre-defining hierarchical matching logic and data association rules before user operations are executed. The database management system prepares the operational framework with enforced constraints, so that when users provide instructions, the reliability safeguards are already in place to prevent integrity violations.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If hierarchical matching logic is enforced to ensure data integrity, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improvedata integrityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the database management system into distinct functional components: hierarchical matching logic, data association rule enforcement, and operational execution. This segmentation allows each component to handle specific aspects of data integrity, making the overall complex system more manageable and maintainable while ensuring reliability through specialized handling of each concern.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system employs dynamic hierarchical matching logic that adapts to different data types and relationships. The matching logic is not rigid but dynamically adjusts based on the specific database schema and data associations, allowing the system to maintain reliability without requiring overly complex static structures for every possible scenario.

Inventive Principle:
Principle #15Dynamics

3Reliability

If frequent validation and enforcement of data association rules are performed, then data integrity is improved, but productivity decreases

Engineering Contradiction:
Improvedata integrityVSAvoidoperation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs validation准备工作 in advance by pre-compiling data association rules and hierarchical matching criteria. Before executing user operations, the system prepares the validation framework, so that during actual operation execution, the integrity checks can be performed more efficiently without excessive overhead, balancing reliability with productivity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The hierarchical matching logic and data association rule enforcement are integrated continuously into the database operation workflow rather than being applied as separate batch validations. This continuous integration allows validation to occur naturally during the course of normal operations, reducing the need for separate validation steps that would interrupt productivity.

Inventive Principle:
Principle #20Continuity of useful action

4Productivity

If automated matching logic is used for cross-record association, then productivity is improved, but measurement precision deteriorates

Engineering Contradiction:
Improveoperation efficiencyVSAvoidmatching accuracy
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The patent implements feedback mechanisms where the results of automated matching are continuously evaluated against hierarchical matching logic and data association rules. The system uses feedback from validation results to refine and adjust matching operations, ensuring that productivity gains from automation do not compromise the precision of cross-record associations.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

An intermediary validation layer is introduced between automated matching logic and final record association. This intermediary ensures that while automated processes provide efficiency, the precision of matching is maintained through enforced hierarchical rules that act as a quality control mechanism on the automated outputs.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20260072907A1Database management systems using hierarchically-enforced database association metadata
Publication Date: 2026.03.12 OPTUM INC
  • US20260072907A1 patent drawing
  • US20260072907A1 patent drawing
  • US20260072907A1 patent drawing

AI summary

Various embodiments of the present invention provide methods, apparatuses, systems, computing devices, computing entities, and/or the like for facilitating efficient and effective execution of database management operations. For example, various embodiments describe generating data associated with a database association management platform that enables an end user to generate/maintain database association metadata for a database using a sequence of record relationship instructions, such as a sequence comprising at least one of record-structure inclusion (RSI) instructions, record-structure exclusion (RSE) instructions, record-structure non-inclusion (RSNI) instructions, record-structure non-exclusion (RSEI) instructions, and new structure creation (NSC) instructions. As another example, various embodiments describe performing hierarchical database record aggregation/matching by defining hierarchically-differentiated tiers of a cross-record matching logic, for example by defining a superseding/referential hierarchical matching logic that may be generated based at least in part on manually-entered record relationship instructions as reflected in the database association metadata