# US 2025/0166854 A1 · Automated patient authentication in a health information system using patient identification instrument

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0166854 A1
- Document ID: US20250166854A1
- Status: Published application
- Kind: A1
- Application number: 18/841,157
- Filed: 2023-02-07
- Published: 2025-05-22
- Earliest claimed: 2023-02-07
- Assignees: Medirex Systems Inc.
- Applicants: Medirex Systems Inc.
- Inventors: Stephen NOWAK
- Web page: https://patentgrep.com/patent/US20250166854A1

## CPC

- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G16H 80/00: ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
- G06F 21/44: Program or device authentication
- G16H 10/65: stored on portable record carriers, e.g. on smartcards, RFID tags or CD
- G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
- G16H 40/67: for remote operation
- H04L 9/3234: {involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token (network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853)}
- H04L 2209/80: Wireless
- H04L 2209/88: Medical equipments
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A patient engagement system comprises a database and various modules for communicating with health information systems and user mobile devices. An interface module of the system communicates with a health information system to receive patient information, such as patient registration information and patient medical information, therefrom. A user application module communicates with a user mobile device to receive user information, such as patient authentication information, therefrom. The database can store the patient medical information and user profiles of authenticated patients of the patient engagement system.

## Claims

### Claim 1

A computer-implemented method of authenticating a mobile device of a patient for access to a patient engagement system, the method comprising:
receiving patient registration information from a health information system over a first network;
receiving patient authentication information from the mobile device of the patient over a second network, the patient authentication information obtained from a patient identification instrument issued to the patient by a provider of the health information system;
comparing the patient registration information with the patient authentication information; and
where the patient registration information matches the patient authentication information, generating a confirmation message comprising a verification code or confirmation link and sending the generated confirmation message to the mobile device using contact information;
receiving a communicated confirmation message from the mobile device, wherein the communicated confirmation message includes the verification code or is generated using the confirmation link;
where the verification code in the communicated confirmation message matches the verification code in the generated confirmation message or the communicated confirmation message was generated using the confirmation link, granting the mobile device with access to the patient engagement system.

### Claim 2 (depends on 1)

The method of claim 1, wherein the patient authentication information is obtained by the mobile device reading a visual machine-readable code printed on the patient identification instrument.

### Claim 3 (depends on 2)

The method of claim 2, wherein the patient authentication information is decoded from the visual machine-readable code at the mobile device before the patient authentication information is received at the patient engagement system.

### Claim 4 (depends on 2)

The method of claim 2, wherein the patient authentication information is decoded from the visual machine-readable code at the patient engagement system.

### Claim 5 (depends on 1)

The method of claim 1, wherein the provider of the health information system is a hospital and the patient identification instrument is a hospital wristband.

### Claim 6 (depends on 1)

The method of claim 1, comprising:
where the patient registration information matches the patient authentication information, creating a patient profile of the patient based on the patient registration information, the patient profile including a contact information of the patient obtained from the patient registration information.

### Claim 7

(canceled)

### Claim 8 (depends on 1)

The method of claim 1, wherein the first network is a secure private network and the second network is a public network.

### Claim 9 (depends on 1)

The method of claim 1, wherein the first network is a public network and the second network is the public network.

### Claim 10 (depends on 1)

The method of claim 1, comprising receiving the patient registration information from the health information system over the first network in real-time.

### Claim 11 (depends on 10)

The method of claim 10, comprising retrieving patient registration information from the health information system upon receipt of the patient authentication information.

### Claim 12

A patient engagement system comprising:
an interface module for receiving patient information from a health information system, the patient information including patient registration information and patient medical information;
a user application module for receiving user information and a communicated confirmation message from a mobile device, the user information including patient authentication information, and the communicated confirmation message includes a verification code or is generated using a confirmation link;
a user authentication module for comparing the patient registration information with the patient authentication information and for, where the patient registration information matches the patient authentication information, generating a confirmation message comprising a the verification code or the confirmation link and sending the generated confirmation message to the mobile device using contact information;
a database for storing the patient medical information and the user profile; and a processing module for managing access to the patient medical information based on one or more access rules, the one or more access rules defined at least in part by the user profile.

### Claim 13 (depends on 12)

The patient engagement system of claim 12, wherein the interface module is connected to the health information system by way of a secured application programming interface (API) provided by a provider of the health information system.

### Claim 14 (depends on 12)

The patient engagement system of claim 12, wherein the user application module is connected to the mobile device by way of the internet.

### Claim 15 (depends on 12)

The patient engagement system of claim 12, wherein the database is a cloud-based database residing behind one or more layers of security firewalls.

### Claim 16 (depends on 12)

The patient engagement system of claim 12, wherein the health information system is a hospital information system.

### Claim 17

(canceled)

### Claim 18

(canceled)

### Claim 19 (depends on 1)

The method of claim 1, wherein the mobile device is configured to automatically detect receipt of the generated confirmation message and automatically communicate the communicated confirmation message.

### Claim 20 (depends on 1)

The method of claim 1, wherein the contact information comprises at least one of a telephone number and an email associated with the mobile device.

### Claim 21 (depends on 1)

The method of claim 1, further comprising adjusting a level of authentication required based on at least one of a location of the mobile device, a time of access, and a type of medical information being accessed.

### Claim 22 (depends on 12)

The patient engagement system of claim 12, wherein the mobile device is configured to automatically detect receipt of the generated confirmation message and automatically communicate the communicated confirmation message.

### Claim 23 (depends on 12)

The patient engagement system of claim 12, wherein the contact information comprises at least one of a telephone number and an email associated with the mobile device.
