Multi-factor Authentication for Remote Patient Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current wireless communication technologies face limitations in transmitting, receiving, and displaying medical patient data efficiently, especially over low-speed, low-bandwidth, and intermittent connections, which are critical for healthcare applications.

Innovation Solution

A computer-implemented method for authenticating a mobile device and its user to access patient data from a clinical information system, involving a data management system that receives logon requests with credentials and technical factors, validates the device and user, and establishes a secure session for data communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multi-factor authentication is implemented for remote access to patient data, then security and reliability are improved, but device complexity and authentication process time increase

Engineering Contradiction:
ImprovesecurityVSAvoidauthentication process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The authentication process is segmented into distinct factors: something the user knows (credentials), something the user has (mobile device), and something inherent to the device (technical factors). This segmentation allows each component to be validated independently, improving security while maintaining manageable complexity through modular validation steps.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary validation of the mobile device using technical factors before establishing the communication session. By pre-validating device authenticity through device identification and other technical characteristics, the system ensures security is established upfront, preventing unauthorized access before data transmission begins.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If patient data is transmitted over wireless connections with low speed and intermittent connectivity, then remote access capability is improved, but data transmission reliability and completeness deteriorate

Engineering Contradiction:
Improveremote access capabilityVSAvoiddata transmission
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The authentication and session establishment process is designed to cushion against potential connection failures by validating all security parameters and establishing the communication framework before actual patient data transmission begins. This preliminary setup ensures that even if intermittent connectivity occurs during data transfer, the secure channel is already established and can resume transmission reliably.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Ease of operation

If mobile devices are used for accessing patient data, then ease of operation and remote access are improved, but risk of unauthorized access and security vulnerabilities increase

Engineering Contradiction:
Improveremote accessVSAvoidunauthorized access risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system introduces an intermediary authentication layer between the mobile device and patient data access. The data management system acts as a mediator that validates both user credentials and device authenticity, preventing direct access to patient data. This intermediary layer maintains ease of operation for authorized users while blocking unauthorized access attempts at the validation stage.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12299635B2Multi-factor authentication for remote access of patient data
Publication Date: 2025.05.13 AIRSTRIP IP HLDG LLC
  • US12299635B2 patent drawing
  • US12299635B2 patent drawing
  • US12299635B2 patent drawing

AI summary

The present disclosure is directed to authenticating a mobile device and a user of the mobile device to receive patient data from a clinical information system of a medical facility. In some implementations, methods include receiving a logon request, the logon request comprising credentials and at least one technical factor, accessing a validation database based on the at least one technical factor, determining that the mobile device is an authorized mobile device based on information provided by the validation database and the at least one technical factor, validating the credentials to ensure that the user is authorized to access patient data provided by the clinical information system, and then, upon determining that the user is authorized to access patient data: establishing a session to communicate patient data between the mobile device and the clinical information system, the data managements system processing the patient data communicated during the session.