Systems and methods for automatically detecting electronic access of files and surfacing contextually relevant content in response thereto

• US 10,360,997 B2
• Filed: 10/27/2017
• Issued: 07/23/2019
• 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,397
• Publication Number:
  US 20180121612A1
• Time in Patent Office: 634 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 detecting healthcare gap information across disparate sources, comprising at least one software-defined sensor configured to monitor web traffic directed to a clinic health record system database at a healthcare clinic provider 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 clinic health record system database, the at least one software-defined sensor operatively connected to the clinic health record system database and a remote micro-services system, wherein the remote micro-services system grants the at least one software-defined sensor a communication session in response to receiving an authenticated HTTPS communication from the at least one software-defined sensor, the at least one software-defined sensor comprising one or more application programming interfaces protected by a firewall, the at least one software-defined sensor further configured to;

receive, from the remote micro-services system and via the communication session, identification information for a list of patients associated with at least one third-party system;

store at least a portion of the identification information at the at least one software-defined sensor;

monitor the clinic health record system database to detect a particular data access trigger event, the particular data access trigger event corresponding to a computing system electronically accessing a particular electronic health record at the clinic health record system database of at least one of the patients included in the list of patients stored at the at least one software-defined sensor; and

in response to detecting the particular data access trigger event, transmit accessed chart data to the remote micro-services system.

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

3. The system of claim 1, wherein the at least one third-party system is a healthcare providing organization.

4. The system of claim 1, wherein the accessed chart data comprises a clinic health record system database identifier and particular electronic health record data.

5. The system of claim 1, wherein the particular data access trigger event comprises one or more events selected from the group comprising opening the particular electronic health record, initiating a prescription order, creating a new electronic health record chart, and digitally signing an encounter note.

6. The system of claim 1, wherein prior to receiving the identification information for the list of patients, the at least one software-defined sensor is configured to transmit a request to the remote micro-services system for the identification information according to predetermined time intervals.

7. The system of claim 1, wherein healthcare gap information is surfaced onto a display by presenting the healthcare gap information in the form of an alert notification.

8. The system of claim 7, wherein the alert notification is presented by sliding the alert notification from outside the display boundaries.

9. The system of claim 1, wherein the at least one micro-services database stores the healthcare data in a normalized canonical format.

10. The system of claim 1, wherein the at least one micro-services database is a NoSQL Key-Value database.

11. A trigger-based method for detecting healthcare gap information across disparate sources, comprising the steps of:

receiving via at least one software-defined sensor operatively connected to a clinic health record system database, from a remote micro-services system, identification information for a list of patients associated with at least one third-party system, wherein the at least one sensor comprises one or more application programming interfaces protected by a firewall and is configured to monitor web traffic directed to the clinic health record system database at a healthcare clinic provider 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 clinic health record system database, wherein the at least one software-defined sensor receives the identification information via a communication session granted by the remote micro-services system in response to receiving an authenticated HTTPS communication from the at least one software-defined sensor;

storing at least a portion of the identification information at the at least one software-defined sensor;

monitoring the clinic health record system database to detect a particular data access trigger event, the particular data access trigger event corresponding to a computing system electronically accessing a particular electronic health record at the clinic health record system database of at least one of the patients included in the list of patients stored at the at least one software-defined sensor; and

in response to detecting the data access trigger event, transmitting accessed chart data to the remote micro-services system.

12. The method of claim 11, wherein the at least one third-party system is an insurance provider.

13. The method of claim 11, wherein the at least one third-party system is a healthcare providing organization.

14. The method of claim 11, wherein the accessed chart data comprises a clinic health record system database identifier and particular electronic health record data.

15. The method of claim 11, wherein the particular data access trigger event comprises one or more events selected from the group comprising opening the particular electronic health record, initiating a prescription order, creating a new electronic health record chart, and digitally signing an encounter note.

16. The method of claim 11, wherein prior to receiving the identification information for the list of patients, the at least one software-defined sensor is configured to transmit a request to the remote micro-services system for the identification information according to predetermined time intervals.

17. The method of claim 11, wherein healthcare gap information is surfaced onto a display by presenting the healthcare gap information in the form of an alert notification.

18. The method of claim 17, wherein the alert notification is presented by sliding the alert notification from outside the display boundaries.

19. The method of claim 11, wherein the at least one micro-services database stores the healthcare data in a normalized canonical format.

20. The method of claim 11, wherein the at least one micro-services database is a NoSQL Key-Value database.