AUTO REGISTRATION OF NETWORK DEVICES

• US 20100023350A1
• Filed: 10/16/2007
• Published: 01/28/2010
• Est. Priority Date: 10/24/2006
• Status: Abandoned Application

• Current Assignee: Koninklijke Philips N.V.
• Original Assignee: Koninklijke Philips N.V.
• Inventors: Simms, Daniel A.
• Application Number:
  US12/446,637
• Publication Number:
  US 20100023350A1
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• 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

Often when a patient is diagnosed with an ongoing or chronic health care condition, it is desirable to prescribe an ongoing treatment regimen to that patient. In this type of environment, a user interface device (12) performs a self registration and patient association over a public or private network (20) to avoid the process of having to be registered and associated in a factory setting. The interface device (12) contacts a registration server (32) over a public or private network (20) and presents factory-configured credentials. The registration server (32) upon proper authentication of the device (12) then directs the device (12) to a configuration server that will associate it with a particular patient or treatment regimen. One the patient'"'"'s treatment is complete, the device (12) can be returned and re associated with another patient, effectively recycling the device (12).

Claims

1. A healthcare system comprising:

at least one registration server connectable to a public or private communications network;

a plurality of configuration processors or servers connected with the public or private communications network;

a plurality of interface devices which interface between the public or private communications network and a display, each interface device being uniquely associated with a specific patient, each interface device including a registration and configuration processor or software which is programmed to;

connect to the registration server via the public or private communication network when it is powered on;

submit validation information to the registration server over the public or private communication network to establish the user interface device as authentic;

receive a registration certificate from the registration server;

connect to a designated one of the configuration servers or processors via the public or private communications network; and

authenticate itself to the configuration processor or server using the registration certificate received from the registration server.

2. The healthcare system as set forth in claim 1, further including:

a programming source that encrypts the programming and sends it to the interface device.

3. The healthcare system as set forth in claim 1, further including:

a configuration server that stores medical records of the patient at a healthcare institution, the medical records associated to a patient to whom the interface device was assigned.

4. The healthcare system as set forth in claim 1, wherein the interface device further includes:

a registration analysis processor that checks the interface device to see if it is already registered.

5. The healthcare system as set forth in claim 1, wherein the configuration processor or server location includes:

an internet protocol memory that contains an internet protocol address of a healthcare institution that has prescribed patient-specific healthcare programming.

6. The healthcare system as set forth in claim 1, wherein interface device further includes:

a non-volatile memory that stores and submits validation information including at least one of a device ID and a root certificate.

7. The healthcare system as set forth in claim 1, wherein the interface device further includes:

a non-volatile memory that stores and submits validation information including factory configuration credentials.

8. The healthcare system as set forth in claim 1, wherein the interface device includes a communications processor that connects with a registration server over a secure sockets layer (SSL) via hypertext transfer protocol (HTTP).

9. The healthcare system as set forth in claim 1, wherein the interface device further includes:

a memory that stores the registration certificate issued by the registration server in the user interface device.

10. A communications system comprising:

at least one registration server connectable to a communications network;

a plurality of configuration processors or servers connected with the communications network;

a plurality of interface devices which interface between the communications network and a display, each interface device being uniquely associated with a specific user, each interface device including a registration and configuration processor or software which is programmed to;

connect to the registration server via the communication network when it is powered on;

submit validation information to the registration server over the communication network to establish the user interface device as authentic;

receive a registration certificate from the registration server;

connect to a designated one of the configuration servers or processors via the communications network, and,

authenticate itself to the configuration processor or server using the registration certificate received from the registration server.

11. An interface device through which patient specific healthcare or other programming information is received via a public or private communications network for display on a display device, the interface device including a registration and configuration processor or software programmed to:

connect to a registration server via the public or private communication network when it is powered on;

submit validation information to the registration server flyover the public or private communication network to establish the user interface device as authentic,

receive a registration certificate from the registration server;

connect to a designated one of a plurality configuration servers or processors via the public or private communications network; and

authenticate itself to the configuration processor or server using the registration certificate received from the registration server.

12. In a medical care giving system in which patient specific healthcare programming is supplied to a patient via user interface device, a method of self-registration and configuration of the user interface device comprising:

connecting the user interface device with a source of electric power, a display, and a public or private communication networks;

connecting the interface device with a registration server via the public or private communications network;

submitting validation information from the interface device to the registration server over the network establishing the user interface device as authentic;

sending a registration certificate from the registration server to the interface device;

connecting the interface device to a designated server or processor via the public or private communications network; and

authenticating the interface device to the server or processor using the registration certificate received from the registration server.

13. The method as set forth in claim 12, further including:

after the user interface device has been configured, sending patient-specific healthcare programming from a program source via the public or private communication network to the configured user interface device, the programming being encrypted to be received in accordance with the configuration of the user interface device.

14. The method as set forth in claim 12, further including:

via the interface device, the public or private communications network, and a configuration server, associating a patient to whom the interface device was assigned with medical records of the patient at the healthcare institution.

15. The method as set forth in claim 12, further including:

prior to connecting to the communications network, the user interface device checking itself to see whether it is already registered.

16. The method as set forth in claim 12, wherein the configuration server location includes an internet protocol address of a healthcare institution that has prescribed the patient-specific healthcare programming.

17. The method as set forth in claim 12, wherein the step of submitting validation information includes submitting at least one of a device ID and a root certificate.

18. The method as set forth in claim 12, wherein the step of submitting validation information includes submitting factory configuration credentials.

19. The method as set forth in claim 12, wherein the step of connecting with a registration server includes connecting to the registration server over a secure sockets layer (SSL) via hypertext transfer protocol (HTTP).

20. The method as set forth in claim 12, further including:

storing the registration certificate issued by the registration server in the user interface device.

21. The method as set forth in claim 12, wherein the registration server archives the registration certificate.

22. The method as set forth in claim 12, further including,

registering measurement devices that are peripheral devices to the user interface device concurrently with the user interface device.

23. A method of registering a medical care user interface device on a network comprising:

connecting the user interface device to a public or private network;

and performing the steps of;

presenting a registration certificate gained from a registration server to a configuration server or processor;

matching the user interface device with a specific patient;

encrypting patient specific programming in accordance with the configuration of the user interface device associated with the patient;

sending the encrypted patient specific programming over the public or private network; and

decrypting the patient specific programming encrypted for the specific patient in accordance with the specific configuration of the user interface device associated with the specific patient.

24. The method as set forth in claim 23 wherein the step of matching includes querying the patient as to his or her identity.