System and method of synchronizing data sets across distributed systems

• US 20050071195A1
• Filed: 03/08/2004
• Published: 03/31/2005
• Est. Priority Date: 09/30/2003
• Status: Abandoned Application

• Current Assignee: Epic Systems Corporation
• Original Assignee: Epic Systems Corporation
• Inventors: Tsiolis, Athanassios K., Thuesen, James, Hansen, Jason L., Cassel, David A., Escher, Timothy W., Peytchev, Vassil D., Michalski, Clifford L.
• Application Number:
  US10/795,634
• Publication Number:
  US 20050071195A1
• Time in Patent Office: Days
• US Class Current: 705/2
• CPC Class Codes: G06F 16/275 Synchronous replication
• 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 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/67 for remote operation
• CPC Class Codes: G16Z 99/00 Subject matter not provided for in other main groups of this subclass

Abstract

A system and method is provided for synchronizing a data set across a distributed, electronic, health record system which includes creating and storing the data set at a first deployment, assigning a unique identifier to the data set, designating the first deployment as a home deployment for the data set, and transmitting a copy of the data set, the unique identifier, and the home deployment designation to a master index server. The method also includes causing the master file index server to transmit the copy of the data set, the unique identifier, and the home deployment designation to the second deployment if it is determined that the data set should be transmitted to the second deployment, and causing the master file index server to synchronize the data set between the first deployment and the second deployment.

Claims

1. An enterprise healthcare information management and synchronization system comprising:

a first deployment and a second deployment;

each deployment including a plurality of data sets stored within one or more data structures;

the plurality of data sets including a first data set;

the first data set having a unique identifier associated therewith;

the first data set stored within one of the one or more data structures at the first deployment and within one of the one or more

data structures at the second deployment;

a master index server operatively coupled to the first deployment and the second deployment via a network;

the master index server adapted to operate as a centralized repository for the first data set; and

the master index server adapted to use the unique identifier to synchronize the first data set between the first deployment and the second deployment.

2. The enterprise healthcare information management and synchronization system of claim 1, wherein the first data set includes a first deployment home assignment which identifies the first deployment as the deployment where the first data set was created.

3. The enterprise healthcare information management and synchronization system of claim 1, wherein the first data set is not assigned a home deployment.

4. The enterprise healthcare information management and synchronization system of claim 1, wherein the plurality of data sets are either master files or category lists, or both.

5. The enterprise healthcare information management and synchronization system of claim 4, wherein the master index server is one of a master file index server or a master category list server.

6. The enterprise healthcare information management and synchronization system of claim 1, wherein the first data set includes data associated with a patient'"'"'s electronic medical record.

7. The enterprise healthcare information management and synchronization system of claim 1, wherein the first deployment has a unique first deployment identifier and the second deployment has a unique second deployment identifier, wherein the unique first deployment identifier and the unique second deployment identifier are used to uniquely identify the deployment when synchronizing the first data set.

8. The enterprise healthcare information management and synchronization system of claim 7, wherein the unique first deployment identifier is further used to indicate to the second deployment a version of software being run at the first deployment.

9. The enterprise healthcare information management and synchronization system of claim 1, wherein the master index server is adapted to:

receive a new data set residing at the first deployment and

broadcast the new data set to the second deployment.

10. The enterprise healthcare information management and synchronization system of claim 9, wherein the master index server is adapted to:

receive a modification to the new data set residing at the first deployment, and

broadcast the modification to the new data set to the second deployment.

11. The enterprise healthcare information management and synchronization system of claim 1, wherein a new data set is created at the first deployment and is stored within one of the one or more data structures at the first deployment as an entry in a category list, the new data set having a unique identifier associated therewith, and wherein the master index server is adapted to:

receive the entry in the category list, and

broadcast the entry in the category list to the second deployment, so that a second entry in a category list is created at the second deployment, the second entry having the same value as the entry in the category list created at the first deployment, the second entry being stored at the second deployment.

12. The enterprise healthcare information management and synchronization system of claim 1, wherein the first deployment is adapted to operate as the master index server when the master index server is unavailable.

13. The enterprise healthcare information management and synchronization system of claim 9, wherein the new data set includes a hibernation status that is assigned based on the deployment in which the new data set was created and one or more rules for assigning the hibernation status.

14. The enterprise healthcare information management and synchronization system of claim 13, further comprising a hierarchical relationship established between the first deployment and the second deployment.

15. The enterprise healthcare information management and synchronization system of claim 14, wherein the first deployment and the second deployment in the hierarchical relationship are each assigned at least one of the following hierarchy levels:

a community level, a neighborhood level, or a deployment level.

16. The enterprise healthcare information management and synchronization system of claim 1, further comprising a change authorization mechanism adapted to ensure that only authorized changes are made to the plurality of data sets.

17. The enterprise healthcare information management and synchronization system of claim 16, wherein the first data set is a master file and wherein the change authorization mechanism is further adapted to:

check a home deployment for the master file when a change is made to the master file at a current deployment, and

prevent communication of the change to the master index server if the current deployment is not the master file'"'"'s home deployment.

18. The enterprise healthcare information management and synchronization system of claim 16, wherein the first data set is a category list and wherein the change authorization mechanism is further adapted to:

check a home deployment for the category list when an attempt to change the category list is made at a current deployment, and

prevent the attempted change to the category list if the current deployment is not the category list'"'"'s home deployment.

19. A method of synchronizing a data set across a distributed, electronic, health record system, the distributed, electronic, health record system comprising at least a first deployment, a second deployment and a master index server operatively coupled to the first and second deployments, the method comprising:

creating the data set at the first deployment;

storing the data set at the first deployment;

assigning a unique identifier to the data set;

designating the first deployment as a home deployment for the data set;

transmitting a copy of the data set, the unique identifier, and the home deployment designation to the master index server;

determining if the master file index server should transmit the copy of the data set to the second deployment;

causing the master file index server to transmit the copy of the data set, the unique identifier, and the home deployment designation to the second deployment if it was determined that the data set should be transmitted to the second deployment;

causing the master file index server to synchronize the data set between the first deployment and the second deployment.

20. The method of claim 19, comprising tracking the data set between the first deployment and the second deployment with the use of the unique identifier.

21. The method of claim 19, wherein creating the data set at the first deployment comprises creating one of the following at the first deployment:

a master file or a category list.

22. The method of claim 19, comprising causing an existing deployment in the distributed, electronic, health record system to function as the master index server when the master index server is unavailable.

23. The method of claim 22, comprising causing the second deployment to function as the master index server when the master index server is unavailable.

24. The method of claim 19, comprising causing the master file index server to synchronize a set of data associated with a patient'"'"'s electronic medical record between the first deployment and the second deployment.

25. The method of claim 19, comprising assigning the first deployment a unique first deployment identifier and assigning the second deployment a unique second deployment identifier, and using the unique first deployment identifier and the unique second deployment identifier to uniquely identify a deployment when synchronizing the data set.

26. The method of claim 25, comprising using the unique first deployment identifier to indicate to the second deployment a version of software being run at the first deployment.

27. The method of claim 19, comprising receiving at the master index server a modification to the data set, and broadcasting the modification to the data set to the second deployment.

28. The method of claim 19, comprising:

storing the data set within a data structure at the first deployment as an entry in a category list;

receiving at the master index server the entry in the category list; and

broadcasting the entry in the category list to the second deployment, so that a second entry in a category list is created at the second deployment, the second entry having the same value as the entry in the category list created at the first deployment.

29. The method of claim 19, comprising assigning a hibernation status to the data set based on the deployment in which the data set was created and one or more rules for assigning the hibernation status.

30. The method of claim 29, comprising establishing a hierarchical relationship between the first deployment and the second deployment.

31. The method of claim 30, comprising assigning the first deployment and the second deployment in the hierarchical relationship at least one of the following hierarchy levels:

a community level, a neighborhood level, or a deployment level.

32. The method of claim 19, comprising ensuring that only authorized changes are made to the plurality of data sets.

33. The method of claim 32, comprising:

checking a home deployment for the data set when the data set is a master file and when a change is made to the master file at a current deployment; and

preventing communication of the change to the master index server if the current deployment is not the master file'"'"'s home deployment.

34. The method of claim 32, comprising:

checking a home deployment for the data set when the data set is a category list and when an attempt to change the category list is made at a current deployment; and

preventing the attempted change to the category list if the current deployment is not the category list'"'"'s home deployment.

35. An enterprise healthcare information management and synchronization system comprising:

a first deployment and a second deployment;

the first deployment including a data set stored within a first data structure, wherein the data set includes;

a unique identifier associated therewith;

a hibernation status that is assigned based on the deployment in which the data set was created and a rule for assigning the hibernation status;

a master index server operatively coupled to the first deployment and the second deployment via a network; and

the master index server adapted to use the first unique identifier to synchronize the data set between the first deployment and the second deployment.

36. The enterprise healthcare information management and synchronization system of claim 35, further comprising a hierarchical relationship established between the first deployment and the second deployment.

37. The enterprise healthcare information management and synchronization system of claim 36, wherein the first deployment and the second deployment in the hierarchical relationship are each assigned at least one of the following hierarchy levels:

a community level, a neighborhood level, or a deployment level.

38. The enterprise healthcare information management and synchronization system of claim 37, wherein the master index server is adapted to route the data set to the second deployment when the data set is assigned the community level.

39. The enterprise healthcare information management and synchronization system of claim 35, wherein the data set comprises a first deployment home assignment which identifies the first deployment as the deployment where the data set was created.

40. The enterprise healthcare information management and synchronization system of claim 35, wherein the master index server is further adapted to operate as a centralized repository for the data set.

41. A method of synchronizing a data set between a first deployment and a second deployment in an enterprise healthcare information management and synchronization system, the method comprising:

storing the data set in a data structure at the first deployment;

assigning a unique identifier to the data set;

assigning a hibernation status to the data set based on the deployment in which the data set was created and a rule for assigning the hibernation status;

receiving a copy of the data set, the unique identifier, and the hibernation status at a master index server, the master index server being operatively coupled to the first deployment and the second deployment via a network;

transmitting a copy of the data set and the unique identifier from the master index server to the second deployment when it is determined that the data set should be transmitted to the second deployment.

42. The method of claim 41, comprising establishing a hierarchical relationship between the first deployment and the second deployment.

43. The method of claim 42, comprising assigning to the first deployment and the second deployment in the hierarchical relationship at least one of the following hierarchy levels:

a community level, a neighborhood level, or a deployment level.

44. The method of claim 43, comprising routing the data set to the second deployment when the data set is assigned the community level.

45. The method of claim 41, comprising assigning the data set a first deployment home assignment to identify the first deployment as the deployment where the data set was created.

46. The method of claim 41, comprising synchronizing the data set between the first and second deployments.

47. The method of claim 41, comprising transmitting a copy of the hibernation status from the master index server to the second deployment when the data set is transmitted to the second deployment.

48. The method of claim 41, comprising designating the first deployment as a home deployment for the data set.

49. An enterprise healthcare information management and synchronization system comprising:

a first deployment and a second deployment;

the first deployment including a data set that is stored within a first data structure, and the second deployment including a copy of the data structure stored within a second data structure, wherein;

the data set includes a unique identifier associated therewith;

the data set includes a first deployment home assignment which identifies the first deployment as the deployment where the first data set originated;

a master index server operatively coupled to the first deployment and the second deployment via a network;

the master index server adapted to use the unique identifier to synchronize the data set between the first deployment and the second deployment; and

a change authorization mechanism to check the home deployment for the data set when an attempt to change the data set is detected, to ensure that only authorized changes are made to the data set.

50. The enterprise healthcare information management and synchronization system of claim 49, wherein the data set is a master file and wherein the change authorization mechanism is adapted to check the home deployment for the master file when an attempt to change the master file is detected at a current deployment, and prevent communication of a completed change to the master file from being sent to the master index server if the current deployment is not the master file'"'"'s home deployment.

51. The enterprise healthcare information management and synchronization system of claim 49, wherein the data set is a category list and wherein the change authorization mechanism is adapted to check the home deployment for the category list when an attempt to change the category list is detected at a current deployment, and prevent the attempted change to the category list if the current deployment is not the category list'"'"'s home deployment.

52. The enterprise healthcare information management and synchronization system of claim 49, wherein the data set includes a hibernation status that is assigned based on the deployment in which the first data set was created and a rule for assigning the hibernation status.

53. The enterprise healthcare information management and synchronization system of claim 49, comprising a hierarchical relationship established between the first deployment and the second deployment.

54. The enterprise healthcare information management and synchronization system of claim 53, wherein the first deployment and the second deployment in the hierarchical relationship are each assigned at least one of the following hierarchy levels:

a community level, a neighborhood level, or a deployment level.

55. A method of synchronizing a master file between a first deployment and a second deployment in an enterprise healthcare information management and synchronization system, the method comprising:

creating and storing the master file in a memory at the first deployment, and storing a copy of the master file in a memory at the second deployment;

assigning a unique identifier to the master file;

storing the unique identifier assigned to the master file in the memories at the first and second deployments;

designating the first deployment as a home deployment for the master file;

linking a master file index server to the first and second deployments;

checking the home deployment for the master file when a change is made to the master file at a current deployment;

preventing the change to the master file from being sent to the master file index server and broadcast to the first deployment if the current deployment is the second deployment; and

sending the change to the master file to the master file index server for broadcasting to the second deployment if the current deployment is the first deployment.

56. The method of claim 55, comprising establishing a hierarchical relationship between the first deployment and the second deployment.

57. The method of claim 56, comprising assigning to the first deployment and the second deployment in the hierarchical relationship at least one of the following hierarchy levels:

a community level, a neighborhood level, or a deployment level.