Electronic health record sharing using hybrid architecture

• US 8,650,045 B2
• Filed: 09/02/2010
• Issued: 02/11/2014
• Est. Priority Date: 09/02/2010
• Status: Active Grant

• Current Assignee: Medical Management International Incorporated (Mars Incorporated)
• Original Assignee: Medical Management International Incorporated (Mars Incorporated)
• Inventors: Baldock, Daniel James, Svinenko, Vadim Georgiovich, Marshall, Kerri E., Calhoun, Karen
• Primary Examiner(s): Cobanoglu, Dilek B
• Application Number:
  US12/874,896
• Publication Number:
  US 20120059668A1
• Time in Patent Office: 1,258 Days
• Field of Search: 705/2, 705/3, 705/51, 707/103, 380/28, 704/270, 713/193
• US Class Current: 705/3
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS

Abstract

Electronic health record sharing is provided using a hybrid architecture. A centralized architecture provides centralized service including a search service and a token ownership service. A decentralized architecture comprises electronic health record locations. Electronic health records are created at locations and patient identifying information is stored at the centralized architecture. The centralized service manages ownership of electronic health records using ownership tokens comprising unique electronic health record identifiers and unique location identifiers. A current electronic health record owner location is authorized to view and/or edit the electronic health record. Ownership is transferred via the sending location, receiving location, and centralized service.

Claims

1. A method, implemented at least in part by a computing device, for controlling access to electronic health records using a hybrid architecture, the method comprising:

obtaining, by a first location from a token ownership service of a centralized service, an ownership token comprising;

a unique electronic health record (EHR) identifier identifying an EHR of a patient; and

a unique location identifier identifying a second location, wherein the second location currently owns the EHR, wherein the second location currently stores the EHR, and wherein the first location and the second location are different physical locations;

sending, from the first location directly to the second location, a request to transfer the EHR stored at the second location;

receiving, at the first location directly from the second location, the EHR; and

obtaining, by the first location from the token ownership service and from the second location, ownership of the EHR, wherein the ownership is obtained, at least in part, using a pessimistic lock, and wherein obtaining ownership is required before the first location is authorized to make changes to the EHR;

wherein the centralized service is part of a centralized architecture, and wherein the first location and the second location are part of a distributed architecture separate from the centralized architecture; and

wherein the EHR is stored at one or more locations within the distributed architecture, wherein the EHR is owned at no more than one location within the distributed architecture at any given time, and wherein the EHR is not stored at the centralized architecture.

2. The method of claim 1 wherein the obtaining the unique EHR identifier and the unique location identifier comprises:

sending, from the first location to a search service of the centralized service, a search request, wherein the search request comprises patient identifying information;

receiving, by the first location from the search service based on a lookup performed by the search service using the patient identifying information, the unique EHR identifier and the unique location identifier.

3. The method of claim 1 wherein the obtaining ownership of the EHR comprises performing a three-way transaction among the first location, the second location, and the token ownership service to commit ownership change from the second location to the first location.

4. The method of claim 3 wherein performing the three-way transaction comprises:

if the EHR is locked for editing at the second location, denying ownership change from the second location to the first location; and

if the EHR is not locked for editing at the second location, allowing ownership change from the second location to the first location.

5. The method of claim 1 wherein the receiving the EHR comprises:

receiving, by the first location from the second location, a compressed EHR package comprising patient information, medical information, and financial information for the patient.

6. The method of claim 1 wherein the request to transfer the EHR is sent from the first location to the second location via a peer-to-peer network connection between the first location and the second location, and wherein the EHR is received at the first location from the second location via the peer-to-peer network connection.

7. The method of claim 1 wherein the centralized architecture stores patient identifying information related to the patient, wherein the patient identifying information is a subset of patient information stored in the EHR.

8. The method of claim 1 further comprising, after obtaining, by the first location, ownership of the EHR:

receiving, at the first location from a third location, a request for the EHR; and

sending, from the first location directly to the third location, a read-only copy of the EHR;

wherein ownership of the EHR remains at the first location, and wherein the third location is not authorized to make changes to the EHR.

9. A system, comprising one or more computing devices, for controlling access to electronic health records using a hybrid architecture, the system comprising:

a token ownership service as part of a centralized service of a centralized architecture, the token ownership service configured for;

storing an ownership token, wherein the ownership token comprises;

a unique electronic health record (EHR) identifier identifying an EHR of a patient; and

a unique location identifier, associated with the unique EHR identifier, identifying a first location, of a plurality of locations, wherein the first location currently owns the EHR of the patient; and

transferring ownership of the EHR from the first location to a second location of the plurality of locations, wherein the transferring ownership comprises changing the unique location identifier of the ownership token to the second location, wherein transfer of ownership is required before the second location is authorized to make changes to the EHR, and wherein the first location and the second location are different physical locations; and

a search service as part of the centralized service of the centralized architecture, the search service configured for;

storing patient identifying information of the patient, wherein the patient identifying information is associated with the unique EHR identifier of the patient, and wherein the patient identifying information is a subset of patient information stored in the EHR; and

responding to a search request by looking up the ownership token based on at least some of the patient identifying information;

wherein the centralized architecture provides the centralized service to the plurality of locations, wherein the plurality of locations are part of a distributed architecture, wherein the distributed architecture is separate from the centralized architecture, and wherein the EHR is not stored at the centralized architecture; and

wherein the EHR is stored at one or more of the plurality of locations within the distributed architecture, and wherein the EHR is owned at no more than one location within the distributed architecture at any given time.

10. The system of claim 9 wherein the search service is further configured for:

receiving the search request from the second location of the plurality of locations, wherein the search request comprises the at least some patient identifying information;

looking up the ownership token based on the received patient identifying information; and

sending the unique EHR identifier and the unique location identifier, based on the ownership token lookup, to the second location.

11. The system of claim 9 wherein the token ownership service is further configured for:

receiving a request from the second location of the plurality of locations to transfer ownership of the EHR to the second location;

transferring ownership of the EHR from the first location to the second location using a three-way transaction involving the first location, the second location, and the token ownership service.

12. The system of claim 9 wherein the token ownership service is further configured for:

transferring ownership of the EHR from the first location to the second location the plurality of locations using, at least in part, a pessimistic lock of the ownership token.