Systems and methods for preventing an attack on healthcare data processing resources in a hospital information system

• US 20080209513A1
• Filed: 04/18/2008
• Published: 08/28/2008
• Est. Priority Date: 09/19/2003
• Status: Abandoned Application

• Current Assignee: RPX Clearinghouse LLC (RPX Corporation)
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Sylvain, Dany, Watkins, John, Elliott, Stephen, Graves, Alan Frank, Fitchett, Jeffrey
• Application Number:
  US12/081,684
• Publication Number:
  US 20080209513A1
• Time in Patent Office: Days
• US Class Current: 726/2
• CPC Class Codes: G06Q 90/00 Systems or methods specially adapted for administrative, commercial, financial, managerial or supervisory purposes, not involving significant data processing
• CPC Class Codes: G06Q 99/00 Subject matter not provided for in other groups of this subclass
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• CPC Class Codes: G16Z 99/00 Subject matter not provided for in other main groups of this subclass
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/1441 Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 11/066 Telephone sets adapted for data transmision

Abstract

A system comprising a switching entity disposed between healthcare data processing resources and non-healthcare data processing resources. The switching entity is capable of operation in a first state in which an end user device is communicatively coupled to the healthcare data processing resources to support a healthcare session and a second state in which the end user device is communicatively coupled to the non-healthcare data processing resources to support a non-healthcare session. If the authentication request message is received while the switching entity is operating in the second state and a particular non-healthcare session is in progress, and the selected authentication entity is the healthcare authentication entity, initiating a memory purge at the end user device. Attacks on the healthcare data processing resources, both from the non-healthcare resources directly and via the end user device, are thus prevented.

Claims

1-39. -39. (canceled)

40. An access controller, disposed between healthcare data processing resources and non-healthcare data processing resources, and connectable to an end user device via a communication link, the access controller comprising:

a switching entity capable of operation in a first state in which the end user device is communicatively coupled to the healthcare data processing resources to support a healthcare session and a second state in which the end user device is communicatively coupled to the non-healthcare data processing resources to support a non-healthcare session; and

a control entity for controlling the state in which the switching entity operates.

41. The access controller defined in claim 40, further comprising a session monitoring functional entity operative to:

receive an authentication request message from a user along the communication link;

determine, from the authentication request message, whether the user is claiming to be a healthcare user or a non-healthcare user;

send the authentication request message to a selected one of the healthcare authentication entity and the non-healthcare authentication entity in dependence upon whether it has determined that the user is claiming to be a healthcare user or a non-healthcare user.

42. The access controller defined in claim 41, the session monitoring functional entity being further operative to send to the control entity an indication of the selected authentication entity.

43. The access controller defined in claim 42, the control entity having an operation defined by:

responsive to an indication of successful authentication by a healthcare authentication entity in the healthcare data processing resources, causing the switching entity to operate in the first state.

44. The access controller defined in claim 43, the control entity having an operation further defined by:

responsive to successful authentication by a non-healthcare authentication entity in the non-healthcare data processing resources, causing the switching entity to operate in the second state.

45. The system defined in claim 42, the control entity having an operation defined by:

if the authentication request message is received while the switching entity is operating in the first state, and the selected authentication entity is the non-healthcare authentication entity, then responsive to successful authentication by the non-healthcare authentication entity, causing the switching entity to operate in the second state.

46. The system defined in claim 45, the control entity having an operation defined by:

if the authentication request message is received while the switching entity is operating in the second state, and the selected authentication entity is the healthcare authentication entity, then responsive to successful authentication by the healthcare authentication entity, causing the switching entity to operate in the first state.

47. The system defined in claim 42, the control entity having an operation defined by:

if the authentication request message is received while the switching entity is operating in the second state, and the selected authentication entity is the healthcare authentication entity, initiate a memory purge at the end user device.

48. The system defined in claim 47, the control entity having an operation further defined by:

responsive to successful authentication by the healthcare authentication entity, causing the switching entity to operate in the first state.

49. The system defined in claim 48, the control entity having an operation further defined by:

responsive to successful authentication by the non-healthcare authentication entity, causing the switching entity to operate in the second state.

50. The system defined in claim 47, wherein initiating a memory purge at the end user device comprises:

releasing a command towards the end user device to cause the end user device to purge data loaded into the end user device during the non-healthcare session.

51. The system defined in claim 47, wherein initiating a memory purge at the end user device comprises:

releasing a command towards the end user device to cause the end user device to purge all data loaded into the end user device during the non-healthcare session.

52. The system defined in claim 40, further comprising a session monitoring functional entity operative to:

receive a message indicative of session termination;

send to the control entity a second message indicative of session termination.

53. The system defined in claim 52, the control entity being operative to respond to receipt of the second message to initiate a memory purge at the end user device.

54. The system defined in claim 53, wherein initiating a memory purge at the end user device comprises:

releasing a command towards the end user device to cause the end user device to purge data loaded into the end user device during the non-healthcare session.

55. The system defined in claim 40, the session monitoring functional entity being operative to:

receive a message indicative of session termination;

send to the control entity a second message indicative of session termination.

56. The system defined in claim 55, the control entity being operative to respond to receipt of the second message to initiate a memory purge at the end user device.

57. The system defined in claim 56, wherein initiating a memory purge at the end user device comprises:

releasing a command towards the end user device to cause the end user device to purge data loaded into the end user device during the non-healthcare session.

58. (canceled)

59. (canceled)

60. A computer-readable storage medium containing a program element for execution by a computing device to implement an access controller, said access controller including:

a switching entity capable of operation in a first state in which an end user device is communicatively coupled to healthcare data processing resources to support a healthcare session and a second state in which the end user device is communicatively coupled to non-healthcare data processing resources to support a non-healthcare session; and

a control entity for controlling the state in which the switching entity operates.

61. The computer-readable storage medium defined in claim 60, further including a session monitoring functional entity operative to:

receive an authentication request message from a user along the communication link;

determine, from the authentication request message, whether the user is claiming to be a healthcare user or a non-healthcare user;

send the authentication request message to a selected one of the healthcare authentication entity and the non-healthcare authentication entity in dependence upon whether it has determined that the user is claiming to be a healthcare user or a non-healthcare user.

62-81. -81. (canceled)