Secure Data Access Layer With Anonymization for Centralized Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for storing personal data in the healthcare sector face challenges in integrating existing applications efficiently, managing complex data access rules, and ensuring data security, particularly when transitioning from local to central data management.

Innovation Solution

A system comprising an interface, authentication module, and data access module that manages access through a REST API, anonymizes data as needed, and supports both SQL and non-SQL databases, allowing existing applications to communicate via ODBC or JDBC drivers, with centralized data access control and offline/anonymization capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If central data management is implemented, then data security and access control are improved, but system complexity and integration difficulty increase

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

Solution Approach 1:

The patent introduces a data access module as an intermediary layer between client applications and target databases. This module handles authentication, authorization, and data access requests centrally, improving security without requiring applications to implement complex compliance algorithms locally. The intermediary abstracts the complexity from clients while maintaining secure centralized control.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The data access module serves multiple functions: authentication, authorization, data querying, anonymization, and support for multiple database types (SQL and non-SQL). This universal approach consolidates what would otherwise be separate complex systems into a single manageable component, improving security while controlling overall system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If existing applications are re-implemented for central data management, then data access control is improved, but integration time and cost increase

Engineering Contradiction:
Improveaccess controlVSAvoidintegration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The data access module acts as a mediator that allows existing applications to access centralized data without re-implementing them. Applications communicate through standard interfaces (ODBC, JDBC, REST API) with the access module handling authentication and authorization. This eliminates the need for time-consuming application reimplementation while maintaining robust access control.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system creates virtual copies or views of data in target databases that can be queried by existing applications through standard interfaces. Instead of re-implementing applications, the system provides compatible access layers that replicate the necessary functionality, reducing integration time while maintaining security control.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If data is made available to multiple groups and applications, then data utility is improved, but data protection and privacy risks increase

Engineering Contradiction:
Improvedata availabilityVSAvoidprivacy risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent implements different data access qualities for different users and applications through the authentication and authorization module. Sensitive data can be anonymized or restricted for certain groups while remaining accessible to others. This local differentiation allows maximum data utility while minimizing privacy risks through targeted protection.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system performs preliminary anonymization of sensitive data fields before making data available to applications. By preparing and anonymizing data in advance, the system enables broad data sharing while pre-mitigating privacy risks, allowing multiple groups to access data without exposing sensitive information.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If comprehensive data management rules are enforced, then data compliance is improved, but system complexity and implementation difficulty increase

Engineering Contradiction:
ImprovecomplianceVSAvoidimplementation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The data access module serves as an intermediary that enforces data management and compliance rules centrally. Instead of requiring each application to implement complex compliance logic, the access module handles authentication, authorization, and data access control, simplifying implementation while maintaining comprehensive compliance.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system provides self-service functionality where the data access module automatically handles compliance requirements through built-in authentication and authorization mechanisms. Applications simply need to provide valid credentials, and the system automatically enforces compliance rules without requiring complex implementation in each application.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12547756B2Systems and methods for secure data storage
Publication Date: 2026.02.10 ROCHE DIAGNOSTICS OPERATIONS INC
  • US12547756B2 patent drawing
  • US12547756B2 patent drawing
  • US12547756B2 patent drawing

AI summary

A system for securely storing data, such as sensitive personal data, including an interface configured with a REST API, an authentication module, at least one target database for storing the data, and a data access module which is configured to receive requests from a client computer by means of the interface, query data from the at least one target database in response to the received request, determine whether the client computer and/or the user has permission to query, and generate a response data set to respond to the request and transmit it to the client computer, wherein at least some data of the response data set is anonymised if restricted authentication is determined.