Client-Side Login Token Management for Healthcare Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Healthcare data management systems face challenges in providing secure and scalable access to patient data across multiple applications and institutions, with existing solutions being inefficient and unsuitable for multi-tenancy environments.

Innovation Solution

Implementing a client-side login token management system that uses encrypted login tokens, authorization tokens, and session cookies to authenticate and authorize users across various applications and roles, managing these at the client level to enhance security and usability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional server-side session management is used, then security can be maintained, but system complexity and response time increase significantly in multi-tenancy environments

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts session management functionality from the server and implements it client-side using encrypted storage. Login tokens, authorization tokens, and session cookies are stored and managed locally in the user's browser, eliminating the need for complex server-side session tracking mechanisms while maintaining security through cryptographic protection.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces encrypted tokens as intermediaries between the user and the system. These tokens (login tokens, authorization tokens) act as mediators that carry authentication and authorization information without requiring continuous server communication, simplifying the system architecture while maintaining security.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple authentication mechanisms are implemented for different applications and roles, then security is improved, but ease of operation deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements a universal token management system that handles multiple applications and roles through a single set of cryptographic tokens. The same client-side storage mechanism and token structure are used across different applications and role types, providing multi-functional authentication without requiring users to manage separate credentials for each context.

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

Solution Approach 2:

The system automatically manages the complexity of multiple authentication mechanisms through client-side JavaScript that handles token generation, storage, retrieval, and validation. Users benefit from automated authentication across multiple applications and roles without manually configuring or managing the underlying security mechanisms.

Inventive Principle:
Principle #25Self-service

3Reliability

If centralized server-side authentication is used, then security control is maintained, but scalability and performance deteriorate

Engineering Contradiction:
Improvesecurity controlVSAvoidscalability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments authentication and authorization functionality from centralized server control and distributes it to individual client instances. Each user's browser independently manages their own tokens and session state, allowing the system to scale horizontally without increasing server processing loads while maintaining security through cryptographic token validation.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12086228B2Login token management
Publication Date: 2024.09.10 BOSTON SCIENTIFIC CARDIAC DIAGNOSTICS INC
  • US12086228B2 patent drawing
  • US12086228B2 patent drawing
  • US12086228B2 patent drawing

AI summary

Techniques for securing user data in a healthcare data management system are described. A client system receives a request to authenticate a user. A login token relating to an authenticated user is maintained at the client system. A role is selected for the user, and an authorization token relating to the selected role is maintained at the client system. A session for the user is initiated. This includes generating an encrypted session cookie relating to the user and the session, storing the encrypted session cookie at the client system, and periodically updating a timestamp for the session cookie.