Access Tokenization for Secure PII and PHI Data Sharing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems require individuals to repeatedly provide sensitive data such as PII and PHI to service providers, which is tedious, vulnerable to unauthorized access, and prone to user error due to lack of centralized data sources and inconsistent data formats.

Innovation Solution

A data security system that enables tokenized access by allowing individuals to request and manage access tokens through a secure connection, specifying data elements and authorization parameters, which are then used by service providers to securely access stored PII and PHI without direct transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If individuals directly provide sensitive data to service providers, then data access is straightforward, but security vulnerability increases and redundancy occurs

Engineering Contradiction:
Improvedata securityVSAvoiddata provision process
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces a token as an intermediary element that mediates between the individual's sensitive data and the service provider. The token contains encoded information about the data without exposing the actual sensitive data, allowing the service provider to access authorized information while the individual's raw data remains protected. This resolves the contradiction by enabling data provision without direct exposure of sensitive information.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a copy of the essential data access information in the form of a token, which can be transmitted to service providers without transmitting the actual sensitive data. The token is a simplified representation that contains only the necessary authorization information, eliminating the need to repeatedly provide full sensitive data while maintaining security.

Inventive Principle:
Principle #26Copying

2Productivity

If sensitive data is transmitted directly to service providers, then data access is immediate, but unauthorized access risk increases

Engineering Contradiction:
Improvedata access efficiencyVSAvoidunauthorized access vulnerability
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The token serves as a mediator that enables efficient data access while preventing unauthorized access to the actual sensitive data. The service provider can quickly process and validate tokens without handling sensitive information, maintaining productivity while eliminating the vulnerability associated with direct data transmission.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts only the essential authorization information from the sensitive data and places it in the token. This extraction allows service providers to access the necessary information for their functions without receiving or storing the full sensitive data, thereby maintaining access efficiency while reducing exposure to unauthorized access risks.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If individuals repeatedly provide sensitive data to multiple service providers, then each provider gets direct access, but redundancy and user burden increase

Engineering Contradiction:
Improvedata sharing capabilityVSAvoiddata provision time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The token is designed as a universal access mechanism that can be used across multiple service providers. Once an individual generates a token, it can be presented to various authorized service providers without needing to repeatedly provide the underlying sensitive data. This multi-functionality enables versatile data sharing while significantly reducing the time and effort required for repeated data provision.

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

Solution Approach 2:

The patent implements preliminary action by having the individual generate and store the token in advance. This pre-computed token contains all necessary authorization information for future interactions with service providers, eliminating the need for repeated data provision and reducing user burden across multiple data sharing scenarios.

Inventive Principle:
Principle #10Preliminary action

4Ease of operation

If centralized data storage is implemented, then data access is streamlined, but security requirements increase

Engineering Contradiction:
Improvedata access processVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The token acts as an intermediary that enables streamlined data access from centralized storage without compromising security. The service provider interacts with the token rather than directly accessing centralized data repositories, which simplifies the access process while maintaining strong security controls through token validation and verification mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4185977B1Systems and methods for tokenization of personally identifiable information (PII) and personal health information (PHI)
Publication Date: 2026.04.01 MASTERCARD INT INC
  • EP4185977B1 patent drawingFigure 1
  • EP4185977B1 patent drawingFigure 2
  • EP4185977B1 patent drawingFigure 3

AI summary

Described herein is a data security system for enabling tokenized access to sensitive data, including a token provider configured to initiate a secure connection with a remote client computing device of a first data subject, and receive, from the remote client computing device, a request for an access token to provide a service provider with access to sensitive data associated with the first data subject. The request includes a data definition and authorization parameters including a data source identifier. The token provider is also configured to generate the access token that enables access to the sensitive data from the data source, store the access token in a token database, and transmit, to the remote client computing device, a response including the access token and instructions that enable the remote computing device to display the access token to the first data subject or transmit the access token to the service provider.