INTELLIGENT MEDIATION OF MESSAGES IN A HEALTHCARE PRODUCT INTEGRATION PLATFORM

• US 20170371722A1
• Filed: 08/16/2017
• Published: 12/28/2017
• Est. Priority Date: 12/30/2011
• Status: Abandoned Application

• Current Assignee: General Electric Company
• Original Assignee: General Electric Company
• Inventors: Ahmed, Rizwan, Vijayan, Vishal
• Application Number:
  US15/678,393
• Publication Number:
  US 20170371722A1
• Time in Patent Office: Days
• 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

Example systems and methods to mediate messages in a product integration platform are disclosed and described. An example method includes receiving a request message from an integration platform, the request message being received in a canonical data format. The example method includes denormalizing the request message into an interface request message format, the interface request message format corresponding to a message format implemented by an interface. The example method includes translating the request message from the interface request message format into a target healthcare system format, the target healthcare system format corresponding to a message format implemented by a target healthcare system, wherein the interface is associated with the target healthcare system. The example method includes sending the request message to the target healthcare system.

Claims

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

receiving a request message from an integration platform, the request message being received in a canonical data format;

denormalizing the request message into an interface request message format, the interface request message format corresponding to a message format implemented by an interface;

translating the request message from the interface request message format into a target healthcare system format, the target healthcare system format corresponding to a message format implemented by a target healthcare system, wherein the interface is associated with the target healthcare system; and

sending the request message to the target healthcare system.

2. The method of claim 1, further including:

receiving a response message from the target healthcare system;

translating the response message from the target healthcare system into an interface response message format;

normalizing the interface response message into a platform message, wherein the platform message is in a canonical data format; and

sending the platform response message to the integration platform.

3. The method of claim 1, wherein the interface includes a message endpoint tailored to a workflow associated with the interface encapsulating messaging and protocol translation for communication with the target healthcare system.

4. The method of claim 1, wherein the interface provides an interface configuration that defines message contracts defining first message content that the interface expects to receive from the integration platform and defines second message content that the interface expects to send to the target healthcare system in response to the received first message content.

5. The method of claim 4, wherein the interface configuration is loaded from an interface properties file.

6. The method of claim 4, wherein denormalizing the request message includes obtaining a message payload from the request message and determining that the message payload is consistent with the first message content.

7. The method of claim 6, wherein translating includes translating the request message from the interface request message format into the target healthcare system format using an integration framework transmogrifier.

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

a message normalizer to receive a request message from an integration platform, the request message being received in a canonical data format and to denormalize the request message into an interface request message format, the interface request message format corresponding to a message format implemented by an interface; and

a message translator to translate the request message from the interface request message format into a target healthcare system format and to send the request message to the target healthcare system, the target healthcare system format corresponding to a message format implemented by a target healthcare system, wherein the interface is associated with the target healthcare system.

9. The system of claim 8, wherein the message translator is to receive a response message from the target healthcare system and translates the response message from the target healthcare system into an interface response message format;

and the message normalizer is to normalize the interface response message into a platform message, wherein the platform message is in a canonical data format and sends the platform response message to the integration platform.

10. The system of claim 8, wherein the interface includes a message endpoint tailored to a workflow associated with the interface encapsulating messaging and protocol translation for communication with the target healthcare system.

11. The system of claim 8, wherein the interface is to provide an interface configuration that defines message contracts defining first message content that the interface expects to receive from the integration platform and defines second message content that the interface expects to send to the target healthcare system in response to the received first message content.

12. The system of claim 12, wherein the interface configuration is to be loaded from an interface properties file.

13. The system of claim 12, wherein the message normalizer is to denormalize the request message includes obtaining a message payload from the request message and determining that the message payload is consistent with the first message content.

14. The system of claim 13, wherein the message translator is to translate the request message from the interface request message format into the target healthcare system format using an integration framework transmogrifier.

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

receive a request message from an integration platform, the request message being received in a canonical data format;

denormalize the request message into an interface request message format, the interface request message format corresponding to a message format implemented by an interface;

translate the request message from the interface request message format into a target healthcare system format, the target healthcare system format corresponding to a message format implemented by a target healthcare system, wherein the interface is associated with the target healthcare system; and

send the request message to the target healthcare system.

16. The storage medium of claim 15, further comprising instructions that cause the computing device to:

receive a response message from the target healthcare system;

translate the response message from the target healthcare system into an interface response message format;

normalize the interface response message into a platform message, wherein the platform message is in a canonical data format; and

send the platform response message to the integration platform.

17. The storage medium of claim 15, wherein the interface includes a message endpoint tailored to a workflow associated with the interface encapsulating messaging and protocol translation for communication with the target healthcare system.

18. The storage medium of claim 15, wherein the interface provides an interface configuration that defines message contracts defining first message content that the interface expects to receive from the integration platform and defines second message content that the interface expects to send to the target healthcare system in response to the received first message content.

19. The storage medium of claim 18, wherein denormalizing the request message includes obtaining a message payload from the request message and determining that the message payload is consistent with the first message content.

20. The storage medium of claim 19, wherein translating includes translating the request message from the interface request message format into the target healthcare system format using an integration framework transmogrifier.