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

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.

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.

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.