Decentralized Health Status Authentication with Offline Zero-Knowledge Proofs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing health status authentication methods rely on central databases, which are vulnerable to attacks and require internet connectivity, lack interoperability, and expose sensitive health data, failing to provide secure, decentralized, and privacy-preserving verification.

Innovation Solution

A decentralized method using certificates and credentials that represent health data, enabling offline verification and zero-knowledge proof, where only necessary information is shared, with real-time management and revocation of credentials based on changing criteria, ensuring privacy and security through cryptographic signatures and peer-to-peer authentication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If central verification using physical or digital certificates is used, then health status authentication can be performed, but large amounts of vulnerable sensitive health data are stored centrally

Engineering Contradiction:
Improveauthentication reliabilityVSAvoiddata vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts sensitive health data from central storage and replaces it with cryptographic proofs (zero-knowledge proofs) that verify health status without exposing actual health information. The verification entity receives only cryptographic evidence rather than raw health data, eliminating the need to store vulnerable sensitive information centrally.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces cryptographic protocols and zero-knowledge proof mechanisms as intermediaries between the user and verification entity. These intermediaries enable verification of health status without direct exposure of sensitive data, acting as a protective layer that prevents data vulnerability while maintaining authentication reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If centralized database verification is used, then health certificates can be verified, but the methods require an internet connection to perform verification

Engineering Contradiction:
Improveverification reliabilityVSAvoidoperational convenience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent performs preliminary actions by pre-computing and storing cryptographic proofs (zero-knowledge proofs) in the user's digital wallet before verification is needed. This allows the verification process to occur offline without requiring internet connection, as all necessary cryptographic evidence is already prepared and stored locally.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates cryptographic copies of health verification evidence that can be stored and transmitted without requiring connection to the original centralized database. The zero-knowledge proof serves as a self-contained cryptographic copy that verifies health status independently of the central system.

Inventive Principle:
Principle #26Copying

3Reliability

If centralized verification systems are used, then health status can be authenticated, but there is a lack of interoperability of digital solutions

Engineering Contradiction:
Improveauthentication reliabilityVSAvoidsystem interoperability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements universal cryptographic protocols and standardized data structures that enable the same verification mechanism to work across different health systems, jurisdictions, and platforms. The zero-knowledge proof framework provides a universal language for health verification that transcends individual system boundaries, enabling interoperability while maintaining authentication reliability.

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

4Reliability

If health data is presented directly for verification, then verification can be performed, but sensitive health data is exposed to verifying entities

Engineering Contradiction:
Improveverification reliabilityVSAvoidprivacy loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent extracts only the essential verification capability from the health data while leaving the sensitive information behind. Through zero-knowledge proofs, the system extracts cryptographic evidence that proves health status without extracting or exposing the actual health information, thereby maintaining verification reliability while preventing privacy loss.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies different information disclosure levels to different parts of the verification process. The cryptographic proof structure allows local quality control where only the necessary verification attribute (health status validity) is revealed, while the sensitive underlying health data remains completely hidden, achieving selective information disclosure.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS20250209149A1A method of digitally authenicating a user's health status
Publication Date: 2025.06.26 SITA ADVANCED TRAVEL SOLUTIONS PTY LTD
  • US20250209149A1 patent drawing
  • US20250209149A1 patent drawing
  • US20250209149A1 patent drawing

AI summary

A method of digitally authenticating a user's health status, the method comprising: sending a certificate representative of health data associated with a user to a verifying entity; the verifying entity carrying out verification on the certificate and, if the certificate is verified, providing a credential based on the verified certificate; and authenticating the user associated with the health data based on the credential.