# US 2019/0318815 A1 · Method and system for providing patient data to a patient data server following an offline network condition

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

- Number: US 2019/0318815 A1
- Document ID: US20190318815A1
- Status: Published application
- Kind: A1
- Application number: 16/387,401
- Filed: 2019-04-17
- Published: 2019-10-17
- Earliest claimed: 2018-04-17
- Assignees: T6 Health Systems LLC
- Applicants: T6 Health Systems LLC
- Inventors: Hubert BANDURSKI; Igor MURAVYOV; Lewis COHEN
- Web page: https://patentgrep.com/patent/US20190318815A1

## CPC

- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
- G16H 40/63: for local operation
- H04L 9/0863: {involving passwords or one-time passwords (network architectures or network communication protocols for using one-time keys in a packet data network H04L63/067)}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 67/59: Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- G06F 21/604: {Tools and structures for managing or administering access control systems}
- G06F 2221/2141: Access rights, e.g. capability lists, access control lists, access tables, access matrices
- G16H 15/00: ICT specially adapted for medical reports, e.g. generation or transmission thereof
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- 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 method and corresponding system for providing patient data to a patient data server following an offline network condition are described. In one arrangement, a healthcare information analysis and presentation system includes a client logic device disposed in wireless communication with a patient data server. The healthcare information analysis and presentation system is configured with an offline functionality that stores patient data on the client logic device, even when not wirelessly connected to the patient data server. Further, the healthcare information analysis and presentation system is configured to allow the end user to begin patient data entry for a new patient, to document an existing case, and to resolve conflicting data following an offline network condition, all while preserving and protecting patient's privacy.

## Claims

### Claim 1

In a client logic device, a method for processing patient data, comprising:
detecting an offline network condition between the client logic device and a patient data server;
in response to said detection of the offline network condition, causing said client logic device to prompt a user to provide the client logic device with a user-generated passcode identifier, the user-generated passcode identifier configured to secure patient data stored in the client logic device;
de-identifying protected health information (PHI), if any, associated with patient data stored in the client logic device; and
in response to detecting an online network condition between the client logic device and the patient data server, forwarding patient data associated with at least one patient and a previously assigned medical record number associated with that patient to the patient data server via a network connection.

### Claim 2 (depends on 1)

The method of claim 1 wherein, in response to detecting the offline network condition between the client logic device and the patient data server:
checking a time interval associated with the offline network condition; and
initiating a prompt to a user after expiration of the time interval.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
generating, by a the patient data server, a communication session between said patient data server and an electronic health record (EHR) system of a medical facility to synchronize said received patient data between said patient data server and said EHR system.

### Claim 4 (depends on 3)

The method of claim 3, wherein said step of synchronizing the patient data comprises utilizing said medical record number to identify the patient associated with said patient data.

### Claim 5 (depends on 3)

The method of claim 3, further comprising, prior to detecting said offline network condition, receiving said medical record number.

### Claim 6 (depends on 5)

The method of claim 5, wherein the step of receiving said medical record number comprises:
establishing, by the patient data server, a communication session between said patient data server and said EHR system and receiving said medical record number from said patient data server.

### Claim 7 (depends on 5)

The method of claim 5, wherein the step of receiving said medical record number comprises:
receiving said medical record number via a user interface of said client logic device.

### Claim 8

In a client logic device, a method for processing patient data, comprising:
detecting an offline network condition between said client logic device and a patient data server;
in response to the detection of the offline network condition, causing the client logic device to prompt a user to provide a user-generated access identifier to limit access to said logic device;
storing patient data on said client logic device via a user interface thereof, said patient data comprising a medical record number; and
de-identifying protected health information (PHI), if any, associated with the patient data stored on said client logic device to generate de-identified patient data.

### Claim 9 (depends on 8)

The method of claim 8 wherein, in response to detecting the offline network condition between the client logic device and the patient data server:
checking a time interval associated with the offline network condition; and
initiating a prompt to a user after expiration of the time interval.

### Claim 10 (depends on 8)

The method of claim 8, further comprising:
detecting via said client logic device an online network condition between said client logic device and a patient data server; and
forwarding said de-identified patient data, including said medical record number, stored on said client logic device via said network to said patient data server.

### Claim 11 (depends on 10)

The method of claim 10, further comprising generating a communication session between said patient data server and an electronic health record (EHR) system of a medical facility to synchronize said patient data between said patient data server and said EHR system.

### Claim 12

A method of processing patient data, comprising:
receiving via at least two client logic devices patient data corresponding to a common patient, said patient data comprising a medical record number;
detecting an offline network condition between at least one of said client logic devices (herein “first logic device”) and a patient data server while at least another one of said client logic devices (herein “second logic device”) continues to be in an online network condition relative to the patient data server and forwards said patient data to said patient data server;
causing said first logic device to prompt a user to provide a user-generated access identifier so as to limit access to said first client logic device, thereby securing patient data stored on said first client logic device;
de-identifying protected health information (PHI), if any, associated with patient data stored on the first client logic device;
detecting an online network condition between said first client logic device and said patient data server;
forwarding said de-identified patient data, including said medical record number, from said first client logic device to said patient data server;
resolving conflicts between the de-identified patient data sent to the patient data server by said first client logic device and the patient data sent to the patient data server by said second client logic device based on a time stamp associated with at least one patient data segment so as to generate consolidated patient data on said patient data server.

### Claim 13 (depends on 12)

The method of claim 12, further comprising generating a communication session between said patient data server and an electronic health record (EHR) system of a medical facility to synchronize said consolidated patient data stored on the patient data server and corresponding patient data stored on said EHR system.

### Claim 14

In a patient data server, a method for synchronizing patient data with a patient database, comprising:
detecting an online network condition between a client logic device and the patient data server, the online network condition following an offline network condition;
receiving from the client logic device patient data including a medical record number that identifies a patient associated with the patient data;
identifying patient data, if any, previously stored on the patient data server associated with said received medical record number; and
updating said previous patient data based on said received patient data.

### Claim 15 (depends on 14)

The method of claim 14, wherein updating said previous patient data based on said received patient data comprises updating said previous patient data based on a timestamp.

### Claim 16

A method of accessing a client logic device, comprising:
sending from a patient data server encrypted information associated with a user, including a security token, to a client logic device in communication with the patient data server when the user logs into said patient data server,
detecting an offline network condition between the client logic device and the patient data server, and
decrypting said encrypted information residing on said client logic device to determine whether to provide access to a user attempting to access said client logic device.

### Claim 17 (depends on 16)

The method of claim 16, wherein said information associated with the user is encrypted using the user's password as a key.
