Intelligent mediation of messages in a healthcare product integration platform

• US 9,183,064 B2
• Filed: 02/17/2012
• Issued: 11/10/2015
• Est. Priority Date: 12/30/2011
• Status: Active Grant

• Current Assignee: General Electric Company
• Original Assignee: General Electric Company
• Inventors: Ahmed, Rizwan, Vijayan, Vishal
• Primary Examiner(s): Tran, Jimmy H
• Application Number:
  US13/399,534
• Publication Number:
  US 20130173719A1
• Time in Patent Office: 1,362 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

An example method to mediate messages in a product integration platform includes receiving a message request from a source healthcare system where the message request contains a message payload. The example method includes determining an interface to be used to route the message to a target healthcare system. The example method includes creating a platform message based on the message request. The example method includes adapting the platform message into a message format expected by the interface and routing the platform message to the interface.

Claims

1. A computer-implemented method to mediate messages in a product integration platform, said method comprising:

receiving, using a processor in the product integration platform, a message request from a source healthcare system, the message request containing a message payload and formatted according to a source healthcare system format;

determining and deploying, using the processor, an interface to be used to route the message from the source healthcare system to a target healthcare system, the interface selected from among a plurality of interfaces based on the source healthcare system and the target healthcare systems, the interface associated with configuration information specifying a platform message format for the interface and a relationship to the source healthcare system format and a target healthcare system format, the configuration information used to dynamically instantiate the interface between the source healthcare system and the target healthcare system;

creating, using the processor, a platform message based on the message request;

adapting, using the processor, the platform message into the platform message format expected by the interface; and

routing, using the processor, the platform message to the interface for transmission to the target healthcare system, the configuration information associated with the interface providing instructions for converting the platform message to the target healthcare system format.

2. The method of claim 1, further comprising:

determining if a message request in a list of request messages is unprocessed; and

if a message request is unprocessed;

determining a message handler for the request message based on a handle contained in the request message; and

unmarshalling the message payload of the request message.

3. The method of claim 2, further comprising filtering out unwanted message requests based on rules associated with the target healthcare system.

4. The method of claim 1, wherein creating a platform message comprises:

normalizing the message request into a canonical data format; and

adding metadata to the message request indicating the interface to be used in the message routing.

5. The method of claim 1, further comprising enriching the platform message by:

determining if there is a callback service request for the interface to be used in the message routing; and

if there is a callback service request for the interface;

sending a request to at least one of the source healthcare system and an external partner system;

receiving additional content from the at least one of the source healthcare system and external partner system in response to the request; and

adding the additional content to the platform message.

6. The method of claim 1, further comprising:

receiving a platform response message from the interface, wherein the platform response message is in a canonical data format, and wherein the platform response message includes a response message payload;

denormalizing the platform response message into a response message format for the source healthcare system;

marshalling the response message payload; and

sending the response message to the source healthcare system.

7. The method of claim 6, further comprising:

aggregating a plurality of response messages; and

sending the aggregated response messages to the source healthcare system.

8. A system to mediate messages in a product integration platform, said system comprising:

a processor configured to execute instructions to implement the particular system including;

a message acquirer to;

receive a message request from a source healthcare system, the message request containing a message payload and formatted according to a source healthcare system format; and

determine and deploy an interface to be used to route the message from the source healthcare system to a target healthcare system, the interface selected from among a plurality of interfaces based on the source healthcare system and the target healthcare systems, the interface associated with configuration information specifying a platform message format for the interface and a relationship to the source healthcare system format and a target healthcare system format, the configuration information used to dynamically instantiate the interface between the source healthcare system and the target healthcare system;

a message normalizer to;

create a platform message based on the message request; and

adapt the platform message into the platform message format expected by the interface; and

a message router to route the platform message to the interface for transmission to the target healthcare system, the configuration information associated with the interface providing instructions for converting the platform message to the target healthcare system format.

9. The system of claim 8, wherein the message acquirer determines if a message request in a list of request messages is unprocessed;

and

if a message request is unprocessed;

determines a message handler for the request message based on a handle contained in the request message; and

unmarshalls the message payload of the request message.

10. The system of claim 9, wherein the message router splits the list of request messages into separate message requests.

11. The system of claim 9, wherein the message router filters out unwanted message requests based on rules associated with the target healthcare system.

12. The system of claim 8, wherein creating a platform message comprises:

normalizing the message request into a canonical data format; and

adding metadata to the message request indicating the interface to be used in the message routing.

13. The system of claim 8, further comprising a content enricher to enrich the platform message by:

determining if there is a callback service request for the interface to be used in the message routing; and

if there is a callback service request for the interface;

sending a request to at least one of the source healthcare system and an external partner system;

receiving additional content from the at least one of the source healthcare system and external partner system in response to the request; and

adding the additional content to the platform message.

14. The system of claim 8, wherein the message router receives a platform response message from the interface, the platform response message being in a canonical data format, and wherein the platform response message includes a response message payload;

the message normalizer denormalizes the platform response message into a response message format for the source healthcare system; and

the message acquirer marshalls the response message payload and sends the response message to the source healthcare system.

15. The system of claim 14, wherein the message acquirer aggregates a plurality of response messages and sends the aggregated response messages to the source healthcare system.

16. A non-transitory computer-readable storage medium comprising instructions that, when executed, cause a computing device to at least:

receive a message request from a source healthcare system, the message request containing a message payload and formatted according to a source healthcare system format;

determine and deploy an interface to be used to route the message from the source healthcare system to a target healthcare system, the interface selected from among a plurality of interfaces based on the source healthcare system and the target healthcare systems, the interface associated with configuration information specifying a platform message format for the interface and a relationship to the source healthcare system format and a target healthcare system format, the configuration information used to dynamically instantiate the interface between the source healthcare system and the target healthcare system;

create a platform message based on the message request;

adapt the platform message into the platform message format expected by the interface; and

route the platform message to the interface for transmission to the target healthcare system, the configuration information associated with the interface providing instructions for converting the platform message to the target healthcare system format.

17. A non-transitory computer-readable storage medium of claim 16, further comprising instructions that cause the computing device to:

determine if a message request in a list of request messages is unprocessed; and

if a message request is unprocessed;

determine a message handler for the request message based on a handle contained in the request message; and

unmarshall the message payload of the request message.

18. A non-transitory computer-readable storage medium of claim 16, wherein creating a platform message comprises:

normalizing the message request into a canonical data format; and

adding metadata to the message request indicating the interface to be used in the message routing.

19. A non-transitory computer-readable storage medium of claim 16, further comprising instructions that cause the computing device to enrich the platform message by:

determining if there is a callback service request for the interface to be used in the message routing; and

if there is a callback service request for the interface;

sending a request to at least one of the source healthcare system and an external partner system;

receiving additional content from the at least one of the source healthcare system and external partner system in response to the request; and

adding the additional content to the platform message.

20. A non-transitory computer-readable storage medium of claim 16, further comprising instructions that cause the computing device to filter out unwanted message requests based on rules associated with the target healthcare system.

21. A non-transitory computer-readable storage medium of claim 16, further comprising instructions that cause the computing device to:

receive a platform response message from the interface, wherein the platform response message is in a canonical data format, and wherein the platform response message includes a response message payload;

denormalize the platform response message into a response message format for the source healthcare system;

marshall the response message payload; and

send the response message to the source healthcare system.

22. A non-transitory computer-readable storage medium of claim 21, further comprising instructions that cause the computing device to:

aggregate a plurality of response messages; and

send the aggregated response messages to the source healthcare system.