INTELLIGENT MEDIATION OF MESSAGES IN A HEALTHCARE PRODUCT INTEGRATION PLATFORM

• US 20160028827A1
• Filed: 10/07/2015
• Published: 01/28/2016
• Est. Priority Date: 12/30/2011
• Status: Active Grant

• Current Assignee: General Electric Company
• Original Assignee: General Electric Company
• Inventors: Ahmed, Rizwan, Vijayan, Vishal
• Granted Patent: US 9,766,955 B2
• Time in Patent Office: 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 provision an interface for mediation of messages in an integration platform includes identifying a target healthcare system; identifying configuration rules and protocol requirements for the target healthcare system and comparing to a source healthcare system; defining a configuration for the interface associated with the target healthcare system based on the configuration rules, protocol requirements, and a relationship between the target healthcare system and the source healthcare system; constructing the target healthcare system interface route; creating an interface factory to return implementations of an interface route and configuration; passing the interface factory content to an interface control channel; loading a concrete implementation of the interface route and configuration; initializing the interface route; and instantiating interface endpoints and processors to enable communication between the source healthcare system and the target healthcare system via the interface route.

Claims

1. A method to provision an interface for mediation of messages in a product integration platform, said method comprising:

identifying a target healthcare system, wherein the target healthcare system is a destination for message routing from a source healthcare system;

identifying configuration rules and protocol requirements for the target healthcare system and comparing to the source healthcare system;

defining a configuration for the interface associated with the target healthcare system based on the configuration rules, protocol requirements, and a relationship between the target healthcare system and the source healthcare system;

constructing the target healthcare system interface route;

creating an interface factory to return implementations of an interface route and configuration;

passing the interface factory content to an interface control channel;

loading a concrete implementation of the interface route and configuration;

initializing the interface route; and

instantiating interface endpoints and processors to enable communication between the source healthcare system and the target healthcare system via the interface route.

2. The method of claim 1, further comprising publishing the interface factory to an interface registry.

3. The method of claim 2, wherein the interface sends a message announcing its presence on the platform to a platform manager via a control channel.

4. The method of claim 3, wherein the interface registry is read by a platform manager to initialize messaging services.

5. The method of claim 1, further comprising instantiating intermediate platform endpoints and processors for communication via the interface route.

6. The method of claim 1, wherein the interface factory communicates with an interface message normalizer and a message translator to facilitate communication between the source healthcare system and the target healthcare system via the interface route.

7. The method of claim 1, wherein the configuration for the interface includes one or more message contracts defining what message content the interface expects to receive and what response message the interface expects to send in response to receiving the message content.

8. A system to provision an interface for mediation of messages in a product integration platform, said system comprising:

an integration platform including a processor particularly programmed to;

identify a target healthcare system, wherein the target healthcare system is a destination for message routing; and

identify configuration rules and protocol requirements for the target healthcare system; and

an interface including a processor particularly programmed to;

define a configuration for the interface associated with the target healthcare system based on the configuration rules, protocol requirements, and a relationship between the target healthcare system and the source healthcare system;

construct the target healthcare system interface route;

create an interface factory to return implementations of an interface route and configuration;

pass the interface factory content to an interface control channel;

load concrete implementation of the interface route and configuration;

initialize the interface route; and

instantiate interface endpoints and processors to enable communication between the source healthcare system and the target healthcare system via the interface route.

9. The system of claim 8, wherein the interface is further configured to publish the interface factory to an interface registry.

10. The system of claim 9, wherein the interface sends a message announcing its presence on the platform to a platform manager via a control channel.

11. The system of claim 10, wherein the interface registry is read by a platform manager to initialize messaging services.

12. The system of claim 8, wherein the interface is further configured to instantiate intermediate platform endpoints and processors for communication via the interface route.

13. The system of claim 8, wherein the interface factory communicates with an interface message normalizer and a message translator to facilitate communication between the source healthcare system and the target healthcare system via the interface route.

14. The system of claim 8, wherein the configuration for the interface includes one or more message contracts defining what message content the interface expects to receive and what response message the interface expects to send in response to receiving the message content.

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

identify a target healthcare system, wherein the target healthcare system is a destination for message routing via a platform;

identify configuration rules and protocol requirements for the target healthcare system;

define a configuration for an interface associated with the target healthcare system based on the configuration rules, protocol requirements, and a relationship between the target healthcare system and the source healthcare system;

construct the target healthcare system interface route;

create an interface factory to return implementations of an interface route and configuration;

pass the interface factory content to an interface control channel;

load concrete implementation of the interface route and configuration;

initialize the interface route; and

instantiate interface endpoints and processors to enable communication between the source healthcare system and the target healthcare system via the interface route.

16. The computer-readable storage medium of claim 15, further comprising instructions that, when executed, cause the computing device to publish the interface factory to an interface registry.

17. The computer-readable storage medium of claim 16, wherein the interface sends a message announcing its presence on the platform to a platform manager via a control channel.

18. The computer-readable storage medium of claim 17, wherein the interface registry is read by a platform manager to initialize messaging services.

19. The computer-readable storage medium of claim 15, wherein the interface factory communicates with an interface message normalizer and a message translator to facilitate communication between the source healthcare system and the target healthcare system via the interface route.

20. The computer-readable storage medium of claim 15, wherein the configuration for the interface includes one or more message contracts defining what message content the interface expects to receive and what response message the interface expects to send in response to receiving the message content.