Method and system for assimilating data from disparate, ancillary systems onto an enterprise system

• US 20030074248A1
• Filed: 03/31/2001
• Published: 04/17/2003
• Est. Priority Date: 03/31/2001
• Status: Abandoned Application

• Current Assignee: PHNS, Inc. (Atos Se)
• Original Assignee: PHNS, Inc. (Atos Se)
• Inventors: Hastings, David, Ragan, Danny J., Braud, Kristopher P.
• Application Number:
  US09/822,013
• Publication Number:
  US 20030074248A1
• Time in Patent Office: Days
• US Class Current: 705/9
• CPC Class Codes: G06Q 10/06314 Calendaring for a resource
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 10/1093 Calendar-based scheduling for persons or groups
• CPC Class Codes: G06Q 10/1097 Task assignment
• 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
• 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: G16H 80/00 ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring

Abstract

The present invention provides a means for an enterprise, such as a health care facility, to receive messages from any one of a plurality of disparate, ancillary vendor applications, convert the vendor information to an enterprise usable form and then store the enterprise information on an enterprise database. The enterprise keeps vendor specific rules for converting each vendor'"'"'s information to enterprise information. Additionally, relational enterprise rules are applied to the enterprise data stored in a enterprise database, so as disparate vendor information is converted to enterprise data, the relationships between that converted enterprise data are checked with the enterprise data stored in the enterprise database. Enterprise data can also be directly entered into the enterprise database from enterprise system clients, the relationships between that enterprise data are also checked with the enterprise data stored in the enterprise database.

Claims

1. A data processing system implemented method for accomplishing an enterprise event based on a unified collection of information realized from a plurality of disparate, ancillary systems comprising:

catching a message, wherein the message was generated by a disparate, ancillary system using a set of content rules and the message conforms to a message standard;

opening the message;

identifying the disparate, ancillary system based on the message;

accessing content conversion rules based on the identity of the disparate, ancillary system;

converting content from the message to enterprise information using the content conversion rules;

retrieving enterprise relationship rules based on the enterprise information;

checking the enterprise information for a relationship with enterprise data based on the relationship rules; and

scheduling an enterprise event based on a relationship between the enterprise information converted from the message and the-enterprise data stored on the enterprise database.

2. The method recited above in claim 1 further comprising:

storing the enterprise information in the enterprise database.

3. The method recited above in claim 1, wherein the enterprise is a health care facility.

4. The method recited above in claim 1 further comprising:

receiving an enterprise request for access to data in the enterprise database;

identifying the portion of enterprise data from information from the enterprise request;

identifying the requestor from the enterprise request;

retrieving enterprise relationship rules based on the identity of the requester;

identifying at least one user with a privilege to the identified portion of enterprise data; and

granting the requester access to the identified portion of enterprise data based on the requester being identified as a user with the privilege to the identified portion of enterprise data.

5. The method recited above in claim 4, prior to granting the requester access to the identified portion of enterprise data the method further comprising:

comparing the identity of at least one user with a privilege to the identified portion with the identity of the requestor; and

returning a warning response to the requestor based on the outcome of the comparison.

6. The method recited above in claim 2 further comprising:

detecting an error in a portion of enterprise data maintained on the enterprise database;

identifying a source disparate, ancillary system, wherein the source disparate, ancillary system is a source for the portion of enterprise data;

locating the portion of enterprise data in the source disparate, ancillary system; and

accessing the source disparate, ancillary system for the portion of enterprise data.

7. The method recited above in claim 6 further comprising:

overwriting the portion of enterprise data maintained on the enterprise database with the portion of enterprise data from the source disparate, ancillary system.

8. The method recited above in claim 1, wherein the enterprise event is an enterprise service, scheduling the enterprise event further comprises:

identifying a recipient for the enterprise service from the enterprise information.

9. The method recited above in claim 8, wherein scheduling the enterprise event further comprises:

identifying an enterprise department responsible for administering the performance of enterprise services to the recipient based on the identity of the recipient for the enterprise service and the enterprise data.

10. The method recited above in claim 8, wherein scheduling the enterprise event further comprises:

identifying an enterprise service person responsible for performance the enterprise service based on the identity of the recipient the enterprise service and the enterprise data.

11. The method recited above in claim 8, wherein scheduling the enterprise event further comprises:

identifying an enterprise service person responsible for performance the enterprise service and an enterprise department responsible for administering the performance of enterprise services to the recipient based on the identity of the recipient the enterprise service and the enterprise data.

12. The method recited above in claim 9, wherein scheduling the enterprise event further comprises:

establishing a scheduling time for performance of the enterprise service; and

notifying the enterprise department responsible for administering the performance of enterprise services to the recipient of the scheduling time.

13. The method recited above in claim 10, wherein scheduling the enterprise event further comprises:

establishing a scheduling time for performance of the enterprise service; and

notifying the service person responsible for performance the enterprise service of the scheduling time.

14. The method recited above in claim 11, wherein scheduling the enterprise event further comprises:

establishing a scheduling time for performance of the enterprise service; and

notifying the enterprise service person responsible for performance the enterprise service and the enterprise department responsible for administering the performance of enterprise services to the recipient of the scheduling time.

15. The method recited above in claim 14, wherein notifying further comprises:

updating an enterprise web page with the scheduling time for performance of the enterprise service.

16. The method recited above in claim 15, wherein notifying further comprises:

accessing notification information for enterprise service person from the enterprise data;

selecting a transmission medium based on notification criteria in the notification information; and

trnasmitting a message using the transmission medium based on the notification information.

17. The method recited above in claim 16, wherein the transmission medium is a telephone, the notification information includes a telephone number, and the message is an oral notification.

18. The method recited above in claim 16, wherein the transmission medium is a pager, the notification information includes a pager telephone number, and the message is a text notification.

19. The method recited above in claim 15, wherein scheduling the enterprise event further comprises:

receiving an acknowledgment from the enterprise service person that the scheduling time for performance of the enterprise service has been received by the enterprise service person.

20. The method recited above in claim 19, wherein scheduling the enterprise event further comprises:

notifying the enterprise department responsible for administering the performance of enterprise services to the recipient that the enterprise service person responsible for administering acknowledges the scheduling time for performance of the enterprise service.

21. The method recited above in claim 1, wherein the enterprise event is an enterprise function, scheduling the enterprise event further comprises:

identifying an enterprise user responsible for executing the enterprise function from the enterprise information.

22. The method recited above in claim 21, wherein scheduling the enterprise event further comprises:

retrieving enterprise relationship rules based on the identity of the enterprise user;

identifying at least one user with a privilege to the enterprise function; and

granting the enterprise user access to the enterprise function based on the enterprise user being identified as a user with the privilege to the enterprise function.

23. The method recited above in claim 22 wherein scheduling the enterprise event further comprises:

updating an enterprise web page with at least a portion of the enterprise information a tool to perform the enterprise function.

24. The method recited above in claim 23 wherein the at least a portion of the enterprise information is a document and the tool to perform the enterprise function is an electronic signature tool.

25. The method recited above in claim 24 wherein the tool to perform the enterprise function further includes a document editing feature.

26. The method recited above in claim 25 wherein the editing feature of the tool to perform the enterprise function requires a separate privilege.

27. The method recited above in claim 22 wherein the enterprise user is one of a physician, an intern and a resident and the enterprise is a health care facility.

28. The method recited above in claim 24 wherein scheduling the enterprise event further comprises:

receiving an acknowledgment from the enterprise user that document has been electronically signed by the enterprise user.

29. The method recited above in claim 25 wherein scheduling the enterprise event further comprises:

receiving an acknowledgment from the enterprise user that document has been electronically edited and electronically signed by the enterprise user.

30. The method recited above in claim 24 wherein scheduling the enterprise event further comprises:

faxing a copy of the signed document to a destination based on the enterprise data.

31. A data processing system for accomplishing an enterprise event based on a unified collection of information realized from a plurality of disparate, ancillary systems comprising:

means for catching a message, wherein the message was generated by a disparate, ancillary system using a set of content rules and the message conforms to a message standard;

means for opening the message;

means for identifying the disparate, ancillary system based on the message;

accessing content conversion rules based on the identity of the disparate, ancillary system;

means for converting content from the message to enterprise information using the content conversion rules;

means for retrieving enterprise relationship rules based on the enterprise information;

means for checking the enterprise information for a relationship with enterprise data based on the relationship rules; and

means for scheduling an enterprise event based on a relationship between the enterprise information converted from the message and the enterprise data stored on the enterprise database.

32. The system recited above in claim 31 further comprising:

means for storing the enterprise information in the enterprise database.

33. The system recited above in claim 31, wherein the enterprise is a health care facility.

34. The system recited above in claim 31 further comprising:

means for receiving an enterprise request for access to data in the enterprise database;

means for identifying the portion of enterprise data from information from the enterprise request;

means for identifying the requestor from the enterprise request;

means for retrieving enterprise relationship rules based on the identity of the requester;

means for identifying at least one user with a privilege to the identified portion of enterprise data; and

means for granting the requestor access to the identified portion of enterprise data based on the requester being identified as a user with the privilege to the identified portion of enterprise data.

35. The system recited above in claim 34 further comprising:

means for comparing the identity of at least one user with a privilege to the identified portion with the identity of the requestor; and

means for returning a warning response to the requestor based on the outcome of the comparison.

36. The system recited above in claim 32 further comprising:

means for detecting an error in a portion of enterprise data maintained on the enterprise database;

means for identifying a source disparate, ancillary system, wherein the source disparate, ancillary system is a source for the portion of enterprise data;

means for locating the portion of enterprise data in the source disparate, ancillary system; and

means for accessing the source disparate, ancillary system for the portion of enterprise data.

37. The system recited above in claim 36 further comprising:

means for overwriting the portion of enterprise data maintained on the enterprise database with the portion of enterprise data from the source disparate, ancillary system.

38. The system recited above in claim 31, wherein the enterprise event is an enterprise service, the means for scheduling the enterprise event further comprises:

means for identifying a recipient for the enterprise service from the enterprise information.

39. The system recited above in claim 38, wherein the means for scheduling the enterprise event further comprises:

means for identifying an enterprise department responsible for administering the performance of enterprise services to the recipient based on the identity of the recipient for the enterprise service and the enterprise data.

40. The system recited above in claim 38, wherein the means for scheduling the enterprise event further comprises:

means for identifying an enterprise service person responsible for performance the enterprise service based on the identity of the recipient the enterprise service and the enterprise data.

41. The system recited above in claim 38, wherein the means for scheduling the enterprise event further comprises:

means for identifying an enterprise service person responsible for performance the enterprise service based on the identity of the recipient the enterprise service and the enterprise data; and

means for identifying an enterprise department responsible for administering the performance of enterprise services to the recipient based on the identity of the recipient the enterprise service and the enterprise data.

42. The system recited above in claim 39, wherein the means for scheduling the enterprise event further comprises:

means for establishing a scheduling time for performance of the enterprise service; and

means for notifying the enterprise department responsible for administering the performance of enterprise services to the recipient of the scheduling time.

43. The system recited above in claim 40, wherein the means for scheduling the enterprise event further comprises:

means for establishing a scheduling time for performance of the enterprise service; and

means for notifying the service person responsible for performance the enterprise service of the scheduling time.

44. The system recited above in claim 41, wherein the means for scheduling the enterprise event further comprises:

means for establishing a scheduling time for performance of the enterprise service; and

means for notifying the enterprise service person responsible for performance the enterprise service and the enterprise department responsible for administering the performance of enterprise services to the recipient of the scheduling time.

45. The system recited above in claim 44, wherein the means for notifying further comprises:

means for updating an enterprise web page with the scheduling time for performance of the enterprise service.

46. The system recited above in claim 45, wherein the means for notifying further comprises:

means for accessing notification information for enterprise service person from the enterprise data;

means for selecting a transmission medium based on notification criteria in the notification information; and

means for trnasmitting a message using the transmission medium based on the notification information.

47. The system recited above in claim 46, wherein the transmission medium is a telephone, the notification information includes a telephone number, and the message is an oral notification.

48. The system recited above in claim 46, wherein the transmission medium is a pager, the notification information includes a pager telephone number, and the message is a text notification.

49. The system recited above in claim 45, wherein the means for scheduling the enterprise event further comprises:

means for receiving an acknowledgment from the enterprise service person that the scheduling time for performance of the enterprise service has been received by the enterprise service person.

50. The system recited above in claim 49, wherein the means for scheduling the enterprise event further comprises:

means for notifying the enterprise department responsible for administering the performance of enterprise services to the recipient that the enterprise service person responsible for administering acknowledges the scheduling time for performance of the enterprise service.

51. The system recited above in claim 31, wherein the enterprise event is an enterprise function, the means for scheduling the enterprise event further comprises:

means for identifying an enterprise user responsible for executing the enterprise function from the enterprise information.

52. The system recited above in claim 41, wherein the means for scheduling the enterprise event further comprises:

means for retrieving enterprise relationship rules based on the identity of the enterprise user;

means for identifying at least one user with a privilege to the enterprise function; and

means for granting the enterprise user access to the enterprise function based on the enterprise user being identified as a user with the privilege to the enterprise function.

53. The system recited above in claim 52 wherein the means for scheduling the enterprise event further comprises:

means for updating an enterprise web page with at least a portion of the enterprise information a tool to perform the enterprise function.

54. The system recited above in claim 53 wherein the at least a portion of the enterprise information is a document and the tool to perform the enterprise function is an electronic signature tool.

55. The system recited above in claim 54 wherein the tool to perform the enterprise function further includes a document editing feature.

56. The system recited above in claim 55 wherein the editing feature of the tool to perform the enterprise function requires a separate privilege.

57. The system recited above in claim 52 wherein the enterprise user is one of a physician, an intern and a resident and the enterprise is a health care facility.

58. The system recited above in claim 54 wherein the means for scheduling the enterprise event further comprises:

means for receiving an acknowledgment from the enterprise user that document has been electronically signed by the enterprise user.

59. The system recited above in claim 55 wherein the means for scheduling the enterprise event further comprises:

means for receiving an acknowledgment from the enterprise user that document has been electronically edited and electronically signed by the enterprise user.

60. The system recited above in claim 54 wherein the means for scheduling the enterprise event further comprises:

means for faxing a copy of the signed document to a destination based on the enterprise data.

61. A computer readable storage medium storing program instructions for execution on a data processing system which when executed cause the data processing system to perform a method for accomplishing an enterprise event based on a unified collection of information realized from a plurality of disparate, ancillary systems, the method comprising:

catching a message, wherein the message was generated by a disparate, ancillary system using a set of content rules and the message conforms to a message standard;

opening the message;

identifying the disparate, ancillary system based on the message;

accessing content conversion rules based on the identity of the disparate, ancillary system;

converting content from the message to enterprise information using the content conversion rules;

retrieving enterprise relationship rules based on the enterprise information;

checking the enterprise information for a relationship with enterprise data based on the relationship rules; and

scheduling an enterprise event based on a relationship between the enterprise information converted from the message and the enterprise data stored on the enterprise database.

62. The system recited above in claim 61 further comprising:

storing the enterprise information in the enterprise database.

63. The system recited above in claim 61, wherein the enterprise is a health care facility.

64. The system recited above in claim 61 further comprising:

receiving an enterprise request for access to data in the enterprise database;

identifying the portion of enterprise data from information from the enterprise request;

identifying the requester from the enterprise request;

retrieving enterprise relationship rules based on the identity of the requester;

identifying at least one user with a privilege to the identified portion of enterprise data; and

granting the requester access to the identified portion of enterprise data based on the requester being identified as a user with the privilege to the identified portion of enterprise data.

65. The system recited above in claim 64 further comprising:

comparing the identity of at least one user with a privilege to the identified portion with the identity of the requester; and

returning a warning response to the requester based on the outcome of the comparison.

66. The system recited above in claim 62 further comprising:

detecting an error in a portion of enterprise data maintained on the enterprise database;

identifying a source disparate, ancillary system, wherein the source disparate, ancillary system is a source for the portion of enterprise data;

locating the portion of enterprise data in the source disparate, ancillary system; and

accessing the source disparate, ancillary system for the portion of enterprise data.

67. The system recited above in claim 66 further comprising:

overwriting the portion of enterprise data maintained on the enterprise database with the portion of enterprise data from the source disparate, ancillary system.

68. The system recited above in claim 61, wherein the enterprise event is an enterprise service, scheduling the enterprise event further comprises:

identifying a recipient for the enterprise service from the enterprise information.

69. The system recited above in claim 68, wherein scheduling the enterprise event further comprises:

identifying an enterprise department responsible for administering the performance of enterprise services to the recipient based on the identity of the recipient for the enterprise service and the enterprise data.

70. The system recited above in claim 68, wherein scheduling the enterprise event further comprises:

identifying an enterprise service person responsible for performance the enterprise service based on the identity of the recipient the enterprise service and the enterprise data.

71. The system recited above in claim 68, wherein for scheduling the enterprise event further comprises:

identifying an enterprise service person responsible for performance the enterprise service based on the identity of the recipient the enterprise service and the enterprise data; and

identifying an enterprise department responsible for administering the performance of enterprise services to the recipient based on the identity of the recipient the enterprise service and the enterprise data.

72. The system recited above in claim 69, wherein scheduling the enterprise event further comprises:

establishing a scheduling time for performance of the enterprise service; and

notifying the enterprise department responsible for administering the performance of enterprise services to the recipient of the scheduling time.

73. The system recited above in claim 70, wherein scheduling the enterprise event further comprises:

establishing a scheduling time for performance of the enterprise service; and

notifying the service person responsible for performance the enterprise service of the scheduling time.

74. The system recited above in claim 71, wherein scheduling the enterprise event further comprises:

establishing a scheduling time for performance of the enterprise service; and

notifying the enterprise service person responsible for performance the enterprise service and the enterprise department responsible for administering the performance of enterprise services to the recipient of the scheduling time.

75. The system recited above in claim 74, wherein notifying further comprises:

updating an enterprise web page with the scheduling time for performance of the enterprise service.

76. The system recited above in claim 75, wherein notifying further comprises:

accessing notification information for enterprise service person from the enterprise data;

selecting a transmission medium based on notification criteria in the notification information; and

transmitting a message using the transmission medium based on the notification information.

77. The system recited above in claim 76, wherein the transmission medium is a telephone, the notification information includes a telephone number, and the message is an oral notification.

78. The system recited above in claim 76, wherein the transmission medium is a pager, the notification information includes a pager telephone number, and the message is a text notification.

79. The system recited above in claim 75, wherein scheduling the enterprise event further comprises:

receiving an acknowledgment from the enterprise service person that the scheduling time for performance of the enterprise service has been received by the enterprise service person.

80. The system recited above in claim 79, wherein scheduling the enterprise event further comprises:

notifying the enterprise department responsible for administering the performance of enterprise services to the recipient that the enterprise service person responsible for administering acknowledges the scheduling time for performance of the enterprise service.

81. The system recited above in claim 61, wherein the enterprise event is an enterprise function, scheduling the enterprise event further comprises:

identifying an enterprise user responsible for executing the enterprise function from the enterprise information.

82. The system recited above in claim 81, wherein scheduling the enterprise event further comprises:

retrieving enterprise relationship rules based on the identity of the enterprise user;

identifying at least one user with a privilege to the enterprise function; and

granting the enterprise user access to the enterprise function based on the enterprise user being identified as a user with the privilege to the enterprise function.

83. The system recited above in claim 82 wherein scheduling the enterprise event further comprises:

updating an enterprise web page with at least a portion of the enterprise information a tool to perform the enterprise function.

84. The system recited above in claim 83 wherein the at least a portion of the enterprise information is a document and the tool to perform the enterprise function is an electronic signature tool.

85. The system recited above in claim 84 wherein the tool to perform the enterprise function further includes a document editing feature.

86. The system recited above in claim 85 wherein the editing feature of the tool to perform the enterprise function requires a separate privilege.

87. The system recited above in claim 82 wherein the enterprise user is one of a physician, an intern and a resident and the enterprise is a health care facility.

88. The system recited above in claim 84 wherein scheduling the enterprise event further comprises:

receiving an acknowledgment from the enterprise user that document has been electronically signed by the enterprise user.

89. The system recited above in claim 85 wherein scheduling the enterprise event further comprises:

receiving an acknowledgment from the enterprise user that document has been electronically edited and electronically signed by the enterprise user.

90. The system recited above in claim 84 wherein scheduling the enterprise event further comprises:

faxing a copy of the signed document to a destination based on the enterprise data.

91. A health care information service layer comprising:

a message conversion rules memory for storing vendor specific rules for converting vendor specific message format to health care level format;

an automated interface gateway (AIG) catcher, said AIG catcher comprising a logical port for receiving vendor specific messages, a logical communications port for communicating, a logical memory connection for operationally connecting to the message conversion rules memory and executable logic for opening a vendor specific message generated by a vendor specific application running on a remote system, extracting information contained in a vendor specific message, identifying a remote system based on information in a vendor specific message, communicating with said message conversion rules memory via said logical memory connection and for retrieving vendor specific rules based on an identity of a remote system, converting information contained in a vendor specific message from vendor specific message format using vendor specific rules, and communicating converted health care level information via said logical communications port;

an health care level memory for storing health care level relationship rules and for storing health care level information;

an health care level server, said health care level server comprising a logical port for receiving health care system level messages, a logical memory connection for operationally connecting to the health care level memory and executable logic for opening a health care level message, extracting health care level information contained in a health care level message, communicating with said health care level memory via said logical memory connection and for retrieving health care level relationship rules, checking health care level information for a relationship with other health care level data based on the health care level relationship rules, scheduling health care level event based on a relationship between health care level information from a health care level message and health care level information from said health care level memory and communicating health care level messages via said logical communications port; and

a web server operationally connected to said enterprise server, said web server containing executable logic for receiving health care level messages, converting health care level messages to information packets of a mark up language and communicating information packets to a remote web client.

92. The health care information service layer recited above in claim 91 wherein said health care level memory further comprises:

a health care level privilege database containing privilege rules for accessing health care level information.

93. The health care information service layer recited above in claim 91 wherein said health care level memory further comprises:

a vendor database access database containing rules for accessing a remote system'"'"'s vendor database.

94. The health care information service layer recited above in claim 91 wherein said health care level memory further comprises:

a health care level function containing an electronic signature tool.

95. The health care information service layer recited above in claim 91 wherein said health care level memory further comprises:

a health care level function containing an automatic faxing tool.

96. The health care information service layer recited above in claim 91 wherein said health care level memory further comprises:

a health care level function containing an notification tool for notifying health care level users of the occurrence of a health care level event.