System and method for brokering requests for collaboration

• US 20060178893A1
• Filed: 12/30/2004
• Published: 08/10/2006
• Est. Priority Date: 12/30/2004
• Status: Abandoned Application

• Current Assignee: Cerner Innovation, Inc. (Oracle Corporation)
• Original Assignee: Cerner Innovation, Inc. (Oracle Corporation)
• Inventors: McCallie, David P. Jr., Finn, Christopher S., Crooks, Steven S., O'Larte, David J.
• Application Number:
  US11/027,483
• Publication Number:
  US 20060178893A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06Q 99/00 Subject matter not provided for in other groups of this subclass
• 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
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

A system and associated methods facilitate brokering on behalf of a particular clinician of requests for an electronic collaboration session that originate from another entity. According to one method of the invention, inbound messages are received by a brokering system, and then converted into a format suitable for screening. Each inbound message relates to a request of collaboration with the particular clinician. Converted messages are then screened according to certain rule settings of the system to reach a particular result. Based on the result of the screening, a response is generated to the converted message that includes invoking a specific rule action. The rule actions may be configured to accomplish a range of automated functions, and the brokering system allows the particular clinician to specify a particular level of presence for collaboration.

Claims

1. A method in a computer system of brokering an inbound message on behalf of a particular clinician, the inbound message requesting collaboration with the particular clinician, the method comprising:

receiving the inbound message requesting collaboration;

converting the inbound message into a format suitable for screening;

screening the converted message according to clinical rule settings to reach a particular result; and

generating a response to the converted message based on the result of the screening, the response including invoking a specific rule action.

2. The method of claim 1, wherein the specific rule action invoked includes notifying the particular clinician of the inbound message.

3. The method of claim 2, wherein a client device having certain communication capabilities is associated with the particular clinician, and wherein notifying the clinician of the inbound message includes generating one or more of a visual and audible indication on the client device.

4. The method of claim 1, wherein the inbound message is transmitted from a requesting entity for receipt by the computer system, and wherein invoking a specific rule action includes notifying the requesting entity of whether the particular clinician is accessible for collaboration.

5. The method of claim 1, wherein a client device having certain communication capabilities is associated with the particular clinician, and wherein the specific rule action invoked is based on fact-based data relied upon by the clinical rule settings, the fact-based data including at least one of a clinician-selected availability status, a location of the client device, and a communication capability of the client device of the particular clinician.

6. The method of claim 5, further comprising receiving from the client device the clinician-selected availability status of the client device and editing the clinical rule settings based on the received clinician-selected availability status.

7. The method of claim 5, further comprising receiving from the client device the communication capabilities of the client device and editing the clinical rule settings based on the received communication capabilities without input from the particular clinician.

8. The method of claim 5, wherein the specific rule action invoked includes forwarding a notification of the inbound message to a particular third party.

9. The method of claim 8, wherein screening the converted message according to clinical rule settings to reach a particular result includes:

examining the content of the converted message; and

determining, based on the converted message content and in accordance with the clinical rule settings, whether the particular third party is a qualifying entity for selection to receive the notification of the inbound message.

10. The method of claim 5, wherein the method is performed on a server operating in proxy for the client device.

11. The method of claim 5, wherein the communication capabilities of the client device are determined by the configuration of the client device and the current location of the client device.

12. The method of claim 5, wherein the location of the client device is determined by one of a GPS or LAN-based positioning systems.

13. The method of claim 1, wherein the method is performed on a client device having certain communication capabilities and being associated with the particular clinician as one of an active process and an on-demand process.

14. The method of claim 13, wherein the on-demand process awakens upon receipt of the inbound message.

15. The method of claim 1, wherein the inbound message includes target context and clinical context, and wherein the specific rule action invoked includes performing an action based on the particular target context and clinical context.

16. The method of claim 15, wherein the target context comprises a patient identifier and the clinical context includes clinical data pertinent to a patient associated with the patient identifier.

17. The method of claim 15, wherein the steps of the method are performed without input from the particular clinician.

18. The method of claim 15, wherein the inbound message is transmitted from a requesting entity, the method further comprising notifying at least one of the particular clinician and the requesting entity of the specific rule action invoked.

19. The method of claim 15, wherein the inbound message contains a request and the action performed includes one of approving and disapproving of the request.

20. The method of claim 19, further comprising editing of information in the clinical rule settings based on input received from the particular clinician, wherein the approving or disapproving of the request is at least partially based on the edited information.

21. The method of claim 1, wherein the clinical rule settings include gating rules and customized rules, at least one of the gating rules and customized rules relying upon fact-based data.

22. The method of claim 21, wherein the step of screening the converted message according to clinical rule settings to reach a particular result includes invoking a rules engine to process information contained in the converted message, which comprises:

comparing information in the converted message against the gating rules and fact-based data of the clinical rule settings; and

if the information in the converted message compares favorably to the gating rules and the fact-based data, then comparing information in the converted message against the customized rules.

23. The method of claim 22, wherein the inbound message is transmitted from a requesting entity, and wherein if the information in the converted message does not compare favorably to the gating rules and the fact-based data, then the specific rule action invoked includes notifying the requesting entity that the particular clinician is not accessible for collaboration.

24. The method of claim 21, further comprising editing of the customized rules based on input received from at least one of the particular clinician and a health care institution.

25. The method of claim 21, wherein the fact-based data relied upon by the gating rules includes a schedule for the particular clinician, the schedule dictating a likely location for the particular clinician.

26. A computer system having a processor, a memory and an operating environment, the computer system operable to execute the method as recited in claim 1.

27. A computer-readable medium containing instructions for executing the method of claim 1.

28. A computer system for performing brokering on behalf of a particular clinician of inbound messages requesting collaboration, comprising:

a message handling component for receiving an inbound message and converting the inbound message into a format suitable for screening;

a rule engine component for screening the converted message according to clinical rule settings to reach a particular result; and

a responder component for invoking a specific rule action based on the particular result reached.

29. The computer system of claim 28, further comprising a notifier component for notifying the clinician of the inbound message.

30. The computer system of claim 28, further comprising an editor component for editing the clinical rule settings.

31. The computer system of claim 28, wherein the clinical rule settings include gating rules and customized rules, at least the gating rules relying upon fact-based data.

32. The computer system of claim 31, wherein the rule engine component screens the converted message by comparing information in the converted message against the gating rules and fact-based data of the clinical rule settings, and if the information in the converted message compares favorably to the gating rules and the fact-based data, then comparing information in the converted message against the customized rules.

33. The computer system of claim 31, wherein the editor component including a status editor for editing the fact-based data and a rule editor for editing information within the customized rules.

34. The computer system of claim 31, wherein the fact-based data include the availability status and communication capabilities of a client device associated with the particular clinician, the system being adapted to receive communication signals from and transmit communication signals to the client device.

35. The computer system of claim 31, wherein the clinical rule settings are stored in a rules database and the fact-based data are stored in a fact database.

36. The computer system of claim 28, further comprising an orchestrator component for coordinating the flow of information between at least the message handling component and the rule engine component.

37. The computer system of claim 36, further comprising a notifier component for notifying the clinician of the inbound message, the orchestrator component providing the notifier component with information regarding the inbound message.

38. The computer system of claim 36, wherein the orchestrator component coordinates the flow of information between the rule engine component and the responder component.

39. The computer system of claim 28, wherein a client device having certain communication capabilities is associated with the particular clinician, and wherein at least the message handling component, the rule engine component and the responder component of the system are located on a server operating in proxy mode for the client device.

40. The computer system of claim 28, wherein the particular result reached by the rule engine component is based on target context and clinical context contained in the inbound message.

41. The computer system of claim 28, wherein the inbound message contains a request, the specific rule action invoked by the responder component includes one of approving and disapproving of the request.

42. A computer system for performing brokering on behalf of a particular clinician of inbound messages requesting collaboration that originate from specific entities, comprising:

a message handling component for receiving an inbound message and converting the inbound message into a format suitable for screening;

a rule engine component utilizing clinical rule settings and fact-based data about the particular clinician to screen the converted message to reach a particular result;

a responder component for invoking a specific rule action based on the particular result reached;

a notifier component for notifying the particular clinician of the inbound message; and

an editing component for editing the fact-based data.

43. The computer system of claim 42, wherein the clinical rule settings include gating rules and customized rules, at least the gating rules relying upon fact-based data.

44. The computer system of claim 43, wherein the rule engine component screens the converted message by comparing information in the converted message against the gating rules and fact-based data of the clinical rule settings, and if the information in the converted message compares favorably to the gating rules and the fact-based data, then comparing information in the converted message against the customized rules.

45. The computer system of claim 44, wherein if the information in the converted message does not compare favorably to the gating rules and the fact-based data, then the responder component invokes a specific rule action that includes notifying the requesting entity that the particular clinician is not accessible for collaboration.

46. The computer system of claim 43, wherein the editor component including a status editor for editing the fact-based data and a rule editor for editing information within the customized rules.

47. The computer system of claim 42, wherein the fact-based data about the particular clinician include the availability status and communication capabilities of a client device associated with the particular clinician, the system being adapted to receive communication signals from and transmit communication signals to the client device.

48. The computer system of claim 42, wherein the clinical rule settings are stored in a rules database and the fact-based data are stored in a fact database.

49. The computer system of claim 42, further comprising an orchestrator component for coordinating the flow of information between the message handling component and the rule engine component, and for providing the notifier component with information regarding the inbound message.

50. The computer system of claim 49, wherein the orchestrator component coordinates the flow of information between the rule engine component and the responder component.

51. The computer system of claim 42, wherein a client device having certain communication capabilities is associated with the particular clinician, and wherein at least the message handling component, the rule engine component and the responder component of the system are located on a server operating in proxy mode for the client device.

52. The computer system of claim 42, wherein the particular result reached by the rule engine component is based on target context and clinical context contained in the inbound message.

53. The computer system of claim 42, wherein the inbound message contains a request, the specific rule action invoked by the responder component includes one of approving and disapproving of the request.