Methods and apparatus for in-process client-side context managers

• US 8,914,485 B2
• Filed: 09/30/2011
• Issued: 12/16/2014
• Est. Priority Date: 09/30/2011
• Status: Active Grant

• Current Assignee: General Electric Company
• Original Assignee: General Electric Company
• Inventors: Herlitz, Sten
• Primary Examiner(s): Barry, Lance L
• Application Number:
  US13/250,270
• Publication Number:
  US 20130086145A1
• Time in Patent Office: 1,173 Days
• Field of Search: 709/223, 707/705, 707/758, 707/781, 707/999.01
• US Class Current: 709/223
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• 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

Methods and apparatus for client-side context managers are disclosed. An example apparatus for use in a healthcare information system includes a primary application implemented on a client device in communication with a server; a secondary application implemented on the client device, wherein the primary application is to be initiated before the secondary application can be initiated; and a context manager integrated into the primary application to execute in connection with the primary application.

Claims

1. A healthcare information system, comprising:

a primary application of the healthcare information system implemented on a client device in communication with a server, the primary application to facilitate launching of a secondary application implemented on the client device, wherein the primary application is required to be initiated before the secondary application can be initiated; and

a context manager integrated into the primary application and to be automatically executed inside a process of the primary application in response to the primary application being initiated, the context manager to provide context information to the secondary application launched via the primary application.

2. A healthcare information system as defined in claim 1, wherein the context manager is to execute in parallel with the primary application.

3. A healthcare information system as defined in claim 1, wherein the primary application comprises an authentication program.

4. A healthcare information system as defined in claim 3, wherein the secondary application requires authentication before launching.

5. A healthcare information system as defined in claim 1, wherein the client device comprises a client workstation associated with a healthcare enterprise.

6. A method for use in a healthcare information system, comprising:

implementing a primary application of the healthcare information system on a client device in communication with a server, the primary application to facilitate launching of a secondary application;

implementing the secondary application on the client device, wherein the primary application is required to be initiated before the secondary application can be initiated; and

in response to an initiation of the primary application, executing a context manager inside a process of the primary application, wherein the context manager is integrated with the primary application, the context to provide context information to the secondary application launched via the primary application.

7. A method as defined in claim 6, wherein executing the context manager inside the process of the primary application comprises executing a first thread associated with the context manager in parallel with a second thread associated with the primary application.

8. A method as defined in claim 6, wherein executing the context manager as part of the primary application comprises the primary application referencing a Dynamically Linked Library file including content related to the context manager.

9. A method as defined in claim 6, wherein the primary application comprises an authentication program.

10. A method as defined in claim 9, wherein the secondary application requires authentication before launching.

11. A method as defined in claim 9, wherein executing the context manager in response to the initiation of the primary application comprises executing the context manager in response to the authentication program verifying an identity of a user.

12. A method as defined in claim 9, wherein executing the context manager in response to the initiation of the primary application comprises executing the context manager in response to a user opening the authentication program.

13. A tangible computer readable medium storing instructions that, when executed, cause a machine to at least:

implement a primary application on a client device of a healthcare information system, the client device in communication with a server, the primary application to facilitate launching of a secondary application;

implement the secondary application on the client device, wherein the primary application is required to be initiated before the secondary application can be initiated; and

in response to an initiation of the primary application, execute a context manager inside a process of the primary application, the context manager integrated with the primary application and to provide context information to the secondary application launched via the primary application.

14. A tangible computer readable medium as defined in claim 13, the instructions to cause the machine to execute the context manager as part of the primary application by executing a first thread associated with the context manager in parallel with a second thread associated with the primary application.

15. A tangible computer readable medium as defined in claim 13, the instructions to cause the machine to execute the context manager as part of the primary application by causing the primary application to reference a Dynamically Linked Library file including content related to the context manager.

16. A tangible computer readable medium as defined in claim 13, wherein the primary application comprises an authentication program.

17. A tangible computer readable medium as defined in claim 16, the instructions to cause the secondary application to require authentication before launching.

18. A tangible computer readable medium as defined in claim 16, the instructions to cause the machine to execute the context manager in response to the initiation of the primary application by causing the context manager to execute in response to the authentication program verifying an identity of a user.

19. A tangible computer readable medium as defined in claim 16, the instructions to cause the machine to execute the context manager in response to the initiation of the primary application by causing the context manager to execute in response to a user opening the authentication program.