System and method for providing patient record synchronization in a healthcare setting
First Claim
Patent Images
1. An enterprise healthcare information management system comprising:
- a first deployment and a second deployment;
each deployment including data stored within a data structure, the data at least relating to a data entity of the enterprise healthcare system and each deployment operable for autonomous management of the data stored within its respective data structure;
a communication network communicatively coupling the first and second deployments; and
each deployment having a data correspondence functionality facilitating reconciliation, manipulation, modification or synchronization of data stored in the data structures of either of the first and second deployments.
1 Assignment
0 Petitions
Accused Products
Abstract
A system provides an information sharing architecture that allows physically separate healthcare information systems, called “deployments,” to share and exchange information. The collection of these participating deployments is referred to as the “Community,” and systems within the Community sometimes store records for patients in common. The system allows participants in the Community to share information on data changes to these patients, and to reconcile concurrent and conflicting updates to the patient'"'"'s record.
-
Citations
101 Claims
-
1. An enterprise healthcare information management system comprising:
-
a first deployment and a second deployment;
each deployment including data stored within a data structure, the data at least relating to a data entity of the enterprise healthcare system and each deployment operable for autonomous management of the data stored within its respective data structure;
a communication network communicatively coupling the first and second deployments; and
each deployment having a data correspondence functionality facilitating reconciliation, manipulation, modification or synchronization of data stored in the data structures of either of the first and second deployments. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14)
-
-
15. An electronic patient health record system comprising:
-
a plurality of deployments, each deployment being configured to at least one of logically retain a first electronic patient health record and physically retain a second electronic patient health record, wherein the first and second patient health records comprise patient health record data; and
a network communicatively coupling the plurality of deployments such that patient health record data from a requested patient health record is communicated from a first deployment of the plurality of deployments to a second deployment of the plurality of deployments at the request of the second deployment;
wherein for each patient health record retained within the electronic patient health record system there is specified a home deployment of the plurality of deployments, the home deployment at least logically associated with patient health records assigned thereto. - View Dependent Claims (16, 17, 18, 19, 20)
-
-
21. A method of communicating patient medical record data within an electronic patient health record system, the electronic patient health record system comprising a plurality of deployments, each deployment being operable to at least one of logically and physically retain patient health record data corresponding to patient health records, the plurality of deployments begin communicatively coupled by a network, the method comprising:
-
for each patient medical record, specifying a corresponding home deployment of the plurality of deployments;
determining the home deployment for a requested patient health record;
communicating from a requesting deployment a request to the home deployment corresponding to the requested patient health record data and the corresponding patient health record; and
communicating to the requesting deployment the requested patient health record data. - View Dependent Claims (22, 23, 24, 25)
-
-
26. An enterprise healthcare information management system comprising:
-
at least a first deployment and a second deployment;
the first deployment having a first data structure with a first data structure configuration for storing data therein and the second deployment having a second data structure with a second data structure configuration, different from the first data structure configuration, for storing data therein, the data at least relating to a data entity of the enterprise healthcare system and each deployment operable for autonomous management of the data stored within its respective data structure;
a version skew deployment; and
a communication network communicatively coupling the first, second and version skew deployments, wherein the version skew deployment is configured to physically retain patient medical records at a highest current version level of the enterprise healthcare information management system.
-
-
27. Within an enterprise healthcare information management system having at least one deployment, the deployment including data stored within a data structure, the data at least relating to a data entity of the enterprise healthcare system and the deployment being operable for autonomous management of the data stored within the data structure, a data record corresponding to the data entity comprising:
-
a first portion of the data record identifying a generation of the data record; and
a second portion of the date record identifying an update history of the data record. - View Dependent Claims (28, 29, 30, 31, 32, 33)
-
-
34. A method of managing data within a healthcare information management system, the healthcare information management system comprising at least one deployment, the deployment including data stored within a data structures the data at least relating to a data entity of the enterprise healthcare system and the deployment being operable for autonomous management of the data stored within the data structure, a data record corresponding to the data entity and having a first portion identifying a generation of the data record and a second portion of the data record identifying an update history of the data record;
- the method comprising the steps of;
receiving at a deployment of the healthcare information system a data record for a data entity;
updating at the deployment the data record; and
correspondingly incrementing the generation to a current generation and the update history table to reflect the updating deployment and the current generation. - View Dependent Claims (35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46)
- the method comprising the steps of;
-
47. An enterprise healthcare information management system comprising:
-
at least a first deployment and a second deployment;
the first deployment having a first data structure with a first data structure configuration for storing data therein and the second deployment having a second data structure with a second data structure configuration, different from the first data structure configuration, for storing data therein, the data at least relating to a data entity of the enterprise healthcare system and each deployment operable for autonomous management of the data stored within its respective data structure;
a communication network communicatively coupling the first and second deployments; and
each deployment having a data mapping functionality, the data mapping functionality operable to reconcile data stored in one of the first deployment and the second deployment for use in the other of the first deployment and the second deployment upon communication of data from the other deployment to the one deployment. - View Dependent Claims (48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59)
-
-
60. An enterprise healthcare information management system comprising:
-
at least a first deployment and a second deployment;
each deployment including data records stored within a data structure, each data record relating to a data entity of the enterprise healthcare system and each deployment operable for autonomous management of the data records stored within its respective data structure;
a communication network communicatively coupling the first and second deployments;
each data record having a first data portion and a second data portion; and
wherein responsive to a request by the second deployment to receive a data record, the first deployment is operable to synchronously communicate the first data portion and to asynchronously communicate the second data portion via the network. - View Dependent Claims (61, 62, 63, 64)
-
-
65. A method of communicating patient health record data within an electronic patient health record system, the electronic patient health record system comprising a plurality of deployments, each deployment being operable to at least one of logically retain and physically retain patient health record data, the plurality of deployments being communicatively coupled by a network, the patient health record having a first portion and a second portion, the method comprising the steps of:
-
receiving a request at the first deployment to communicate a patient health record to the second deployment;
responsive to the request, synchronously communicating the first portion of the requested patient health record and asynchronously communicating the second portion of the requested patient health record. - View Dependent Claims (66, 67, 68, 69, 70, 71)
-
-
72. A method of communicating patient health record data within an electronic patient health record system, the electronic patient health record system comprising a plurality of deployments, each deployment being operable to at least one of logically and physically retain patient health record data corresponding to patient health records, the plurality of deployments begin communicatively coupled by a network, the method comprising:
-
requesting at a first deployment a patient health record from a second deployment;
communicating the requested patient health record from the second deployment to the first deployment;
establishing a subscription for updates to the patient health record data; and
communicating responsive to the subscription update patient health record data from the second deployment to the first deployment. - View Dependent Claims (73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84)
-
-
85. An enterprise healthcare information management system comprising:
-
at least a first deployment and a second deployment;
each deployment including data records stored within a data structure, each data record relating to a data entity of the enterprise healthcare system and each deployment operable for autonomous management of the data records stored within its respective data structure;
a notification broker deployment; and
a communication network communicatively coupling the first, second and notification broker deployments, wherein the notification broker deployment is configured to manage subscribe communication of data record updates.
-
-
86. A method of communicating patient health record data within an electronic patient health record system, the electronic patient health record system comprising a plurality of deployments, each deployment being operable to at least one of logically and physically retain patient health record data corresponding to patient health records, the plurality of deployments begin communicatively coupled by a network, the method comprising:
-
determining an update to patient health record data within a patient health record;
determining the existence of at least one deployment subscribing to the patient health record; and
communicating the update to the at least one deployment responsive a trigger criteria. - View Dependent Claims (87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101)
-
Specification