Electronic medical record distribution, systems and methods

• US 10,176,298 B2
• Filed: 02/01/2016
• Issued: 01/08/2019
• Est. Priority Date: 05/13/2010
• Status: Active Grant

• Current Assignee: NXGN Management, LLC. (NextGen Healthcare, Inc.)
• Original Assignee: QSI Management, LLC (NextGen Healthcare, Inc.)
• Inventors: Raggousis, Konstantinos
• Primary Examiner(s): Tomasezewski, Michael
• Application Number:
  US15/012,702
• Publication Number:
  US 20160147950A1
• Time in Patent Office: 1,072 Days
• Field of Search: None
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 50/70 for mining of medical data, e.g. analysing previous cases of other patients
• CPC Class Codes: G16Z 99/00 Subject matter not provided for in other main groups of this subclass
• CPC Class Codes: H04B 7/15 Active relay systems
• CPC Class Codes: H04W 76/12 Setup of transport tunnels

Abstract

Systems and methods for distributing Electronic Medical Records (EMR) from a private practice to authorized mobile devices are presented. EMR data can be exchanged from a private practice with a remote mobile device via an intermediary mobile access service. The service can include one or more servers that tunnel EMR data between the mobile devices and the practice, where a relay server located at the service communicates via an a priori instantiated persistent session with a relay client installed at the practice. The persistent session can be maintained by the relay client thus reducing the burden on the practice to configure or change local network infrastructure.

Claims

1. A method of providing access to a plurality of Electronic Media Record (EMR) databases located within distinctive private networks, the method comprising:

providing access to a mobile access service that is located outside of a first private network and a second private network;

establishing, by a first EMR client located within a first private network, a first persistent session with a mobile access service via an outbound connection, wherein the first EMR client is communicatively coupled with a first EMR database located within the first private network;

establishing, by a second EMR client located within a second private network, a second persistent session with the mobile access service, wherein the second EMR client is communicatively coupled with a second EMR database located within the second private network;

upon receiving an EMR request by the mobile access service, generating a first query and a second query that are distinct from each other, based on information derived from the EMR request;

automatically routing, by the mobile access service, the first query to the first EMR client and the second query to the second EMR client via the first and second persistent sessions, respectively;

obtaining, at the mobile access service, a first EMR result set from the first EMR client via the first persistent session and a second EMR result set from the second EMR client via the second persistent session, the first and second result sets being products of running, by the first and second EMR clients the first and second queries in EMR databases of the first and second private network, respectively; and

generating, by the mobile access service, a final result set based on the first and second result sets.

2. The method of claim 1, further comprising enabling a mobile device to generate an EMR request.

3. The method of claim 2, wherein the EMR request comprises information associated with the mobile device.

4. The method of claim 1, further comprising:

establishing, by the mobile access service, a first data channel within the first persistent session for data exchange with the first EMR client; and

modifying the first data channel, by the mobile access service, based on the information derived from the EMR request.

5. The method of claim 1, further comprising:

establishing, by the first EMR client, a management channel within the first persistent session; and

sending, by the first EMR client to the mobile access service, a message via the management channel notifying the mobile access service that the first EMR client is ready to receive EMR requests.

6. The method of claim 1, further comprising:

upon receiving an EMR request from a mobile device, authenticating, by the mobile access service, the mobile device to access the first database.

7. The method of claim 1, further comprising providing, by the first EMR client, a first set of application programming interface (API) to the mobile access service that enables the mobile access service to construct a query compatible with the first database.

8. The method of claim 7, further comprising providing, by the second EMR client, a second set of API to the mobile access service that enables the mobile access service to construct a query compatible with the second database.

9. An Electronic Record (ER) distribution system that connects ER databases across a first private network and a second private network, the system comprising:

a mobile access service located outside of the first and second private networks, and configured to accept an ER request from a mobile device;

a first ER client located within the first private network and configured to establish a persistent session with the mobile access service via an outbound connection; and

a second ER client located within the second private network and configured to establish a persistent session with the mobile access service via an outbound connection,

wherein the mobile access service is further configured to (1) generate, upon receiving the ER request from the mobile device, a first query and a second query that are distinct from each other, based on information derived from the ER request, and (2) route the first query to the firs ER client and the second query to the second ER client via the first and second persistent sessions, respectively,

wherein the first ER client is further configured to (1) generate a first result set by running the query in a first database located within the first private network, and (2) send the first result set to the mobile access service via the first persistent session,

wherein the second ER client is further configured to (1) generate a second result set by running the query in a second database located within the second private network, and (2) send the second result set to the mobile access service via the second persistent session,

wherein the mobile access service is further configured to generate a final result set based on the first and second result sets.

10. The system of claim 9, wherein the mobile access service is further configured to provide a user interface that enables a user of the mobile device to generate an ER request.

11. The system of claim 10, wherein the ER request comprises information associated with the mobile device and information associated with the user.

12. The system of claim 11, wherein the mobile access service is further configured to:

establish, upon receiving the EM request from the mobile device, a first data channel within the first persistent session for data exchange with the first ER client for the mobile device; and

modify the first data channel based on information derived from the ER request.

13. The system of claim 9, wherein the first ER client is further configured to:

establish a management channel within the first persistent session; and

sending a message to the mobile access service via the management channel to notify the mobile access service that the first client is ready to receive ER requests.

14. The system of claim 9, wherein the mobile access service is further configured to authenticate the mobile device upon receiving the ER request.

15. The system of claim 9, wherein the first ER client is further configured to provide to the mobile access service a first set of application programming interface (API) that enables the mobile access service to construct a query compatible with the first database.

16. The system of claim 9, wherein the second ER client is further configured to provide to the mobile access service a second set of API that enables the mobile access service to construct a query compatible with the second database.