Systems and methods for tracking data across disparate computing systems via a distributed architecture

• US 10,553,307 B2
• Filed: 10/27/2017
• Issued: 02/04/2020
• Est. Priority Date: 10/27/2016
• Status: Active Grant

• Current Assignee: Snaps Solutions, LLC
• Original Assignee: Snaps Solutions, LLC
• Inventors: Connely, IV, Robert Emmitt, Castleton, Bryant Paul, Tropauer, James, Mathur, Saurabh
• Primary Examiner(s): Nguyen, Tran N
• Application Number:
  US15/796,406
• Publication Number:
  US 20180121614A1
• Time in Patent Office: 830 Days
• CPC Class Codes: G06F 16/26 Visual data mining; Browsing structured data
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06Q 10/0633 Workflow analysis
• CPC Class Codes: G06Q 40/08 Insurance
• CPC Class Codes: G16B 20/10 Ploidy or copy number detection
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 20/00 ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
• CPC Class Codes: G16H 20/10 relating to drugs or medications, e.g. for ensuring correct administration to patients
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: G16H 50/30 for calculating health indices; for individual health risk assessment
• CPC Class Codes: H04L 63/02 for separating internal from external traffic, e.g. firewalls
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: 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
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04W 12/02 Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]

Abstract

Systems and methods for surfacing contextually relevant data into the workflow of a third party system are discussed herein. The system implements a near-real-time method of detecting activity corresponding to particular electronic health records associated with particular patients in third-party systems using specifically configured software systems. A cloud-based micro-services architecture is communicably coupled to the third-party systems and is operable to transmit contextually relevant data to the third-party system in response to particular detected activities, such as accessing a patient'"'"'s electronic health record. The contextually-relevant data is identified by comparing electronic health record data from various third-party systems, each third-party system associated with the particular patient, to determine gaps in the records. The contextually relevant data is transmitted to the third-party system and visually integrated into the third-party system'"'"'s pre-existing clinical workflow.

Claims

1. A system for tracking patient information across a plurality of disparate third-party computing systems, comprising:

one or more software-defined sensors connected to the plurality of disparate third-party computing systems, each of the one or more software-defined sensors configured to monitor web traffic directed to health record system databases at the plurality of disparate third-party computing systems to detect data access trigger events comprising health record Hypertext Transfer Protocol Secure (“

HTTPS”

) communications associated with electronic access to electronic health records stored within the health record system databases, the one or more software-defined sensors comprising one or more APIs protected by a firewall for electronically communicating information included in the electronic health records between the plurality of disparate third-party computing systems; and

a remote micro-services system in operative communication with the one or more software-defined sensors, wherein the remote micro-services system grants the one or more software-defined sensors a communication session in response to receiving an authenticated HTTPS communication from the one or more software-defined sensors, the remote micro-services system comprising one or more processors configured to;

receive a request from a first software-defined sensor associated with a first third-party computing system, via the communication session granted in response to the authenticated HTTPS communication, to receive electronic health record information corresponding to a particular patient identifier associated with a particular patient, the first third-party computing system associated with a particular system identifier;

match the particular patient identifier with corresponding electronic health record information and corresponding member information;

store the particular patient identifier and corresponding member information associated with the electronic health record information; and

upon receiving additional healthcare information from a second software-defined sensor associated with a second third-party computing system associated with a second particular system identifier, transmit at least a portion of the additional healthcare information and member information to a surfacing application at the first third-party computing system to be presented as an alert on a display, the alert selectable by a user at the surfacing application and comprising one or more indicators corresponding to the at least a portion of the additional healthcare information, wherein a complete record of additional healthcare information is in an unsurfaced state while the alert is surfaced, whereby in response to the user selecting the alert, the complete record of additional healthcare information replaces the alert on the display.

2. The system of claim 1, wherein at least one of the plurality of disparate third-party computing systems is an insurance provider.

3. The system of claim 1, wherein the electronic health record information is normalized in a canonical format.

4. The system of claim 1, wherein the additional healthcare information comprises healthcare gap information.

5. The system of claim 1, wherein the one or more processors operate in approximately real-time.

6. The system of claim 1, wherein the particular patient identifier comprises Medicaid identification numbers.

7. The system of claim 1, wherein the one or more third-party computing-system identifier comprise National Provider Identifier (NPIs).

8. A computer-implemented method for tracking patient information across a plurality of disparate third-party computing systems, comprising the steps of:

receiving, at a remote micro-services system in operative communication with one or more software-defined sensors configured to monitor web traffic directed to health record system databases at the plurality of disparate third-party computing system to detect data access trigger events comprising health record Hypertext Transfer Protocol Secure (“

HTTPS”

) communications associated with electronic access to electronic health records stored within the health record system databases, a request from a first software-defined sensor associated with a first third-party computing system to receive electronic health record information corresponding to a particular patient identifier associated with a particular patient, the first third-party computing system associated with a particular system identifier and wherein the request is received via a communication session granted by the remote micro-services system to the first software-defined sensor in response to receiving an authenticated HTTPS communication from the first software-defined sensor;

matching the particular patient identifier with corresponding electronic health record information and corresponding member information;

storing the particular patient identifier and corresponding member information associated with the electronic health record information; and

upon receiving additional healthcare information from a second software-defined sensor associated with a second third-party computing system associated with a second particular system identifier, transmitting at least a portion of the additional healthcare information and member information to a surfacing application at the first third-party computing system to be presented as an alert on a display, the alert selectable by a user at the surfacing application and comprising one or more indicators corresponding to the at least a portion of the additional healthcare information, wherein a complete record of additional healthcare information is in an unsurfaced state while the alert is surfaced, whereby in response to the user selecting the alert, the complete record of additional healthcare information replaces the alert on the display.

9. The method of claim 8, wherein at least one of the plurality of disparate third-party computing systems is an insurance provider.

10. The method of claim 8, wherein the electronic health record information is normalized in a canonical format.

11. The method of claim 8, wherein the additional healthcare information comprises healthcare gap information.

12. The method of claim 8, wherein the one or more processors operate in approximately real-time.

13. The method of claim 8, wherein the particular patient identifier comprises Medicaid identification numbers.

14. The method of claim 8, wherein the one or more third-party computing-system identifier comprise National Provider Identifier (NPIs).