Managing Communications to and from a Handset Device Controlling a Therapeutic Product Delivery Device

• US 20160339176A1
• Filed: 01/30/2015
• Published: 11/24/2016
• Est. Priority Date: 01/30/2014
• Status: Active Grant

• Current Assignee: Insulet Netherlands B.V. (Insulet Corporation)
• Original Assignee: Cellnovo Limited (Cellnovo Group SA)
• Inventors: Martin, Anthony, Shapley, Julian, Powell, Matthew, Jones, Mark
• Granted Patent: US 10,272,200 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: A61B 5/002 Monitoring the patient using a local or closed circuit, e.g. in a room or building A61B5/0017 takes precedence
• CPC Class Codes: A61B 5/0022 Monitoring a patient using a global network, e.g. telephone networks, internet
• CPC Class Codes: A61B 5/1118 Determining activity level
• CPC Class Codes: A61B 5/14532 for measuring glucose, e.g. by tissue impedance measurement
• CPC Class Codes: A61B 5/4839 combined with drug delivery
• CPC Class Codes: A61M 2205/3389 Continuous level detection A61M2205/3393 takes precedence
• CPC Class Codes: A61M 2205/3553 remote, e.g. between patient's home and doctor's office
• CPC Class Codes: A61M 2205/3569 sublocal, e.g. between console and disposable
• CPC Class Codes: A61M 2230/005 Parameter used as control input for the apparatus
• CPC Class Codes: A61M 2230/201 Glucose concentration
• CPC Class Codes: A61M 5/142 Pressure infusion, e.g. using pumps
• CPC Class Codes: A61M 5/1723 using feedback of body parameters, e.g. blood-sugar, pressure measurement of body parameters A61B5/00
• CPC Class Codes: G16H 20/17 delivered via infusion or injection
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

A communication method of managing communications to and from a handset device controlling a therapeutic product delivery device is described. The method comprises transmitting, to a server, at least part of a unique identifier for a handset device for controlling a therapeutic product delivery device, and patient information regarding a user to be associated with the handset device, and at the server, associating the handset device with the patient information, generating a handset specific code, and transmitting the handset specific code to the user. At the handset device, a manual input of the handset specific code is received, and the future transmission of data from the handset device to the server carried out in association with the handset specific code. In this way, the server can be sure that the user is in possession of the handset (because the user received the code via the secure portal, and was required to manually input it to the handset), and can therefore be confident that communications received in association with that code are associated with the correct user and handset.

Claims

1. A communication method of managing communications to and from a handset device controlling a therapeutic product delivery device, comprising the steps of:

transmitting, to a server, at least part of a unique identifier for a handset device for controlling a therapeutic product delivery device, and patient information regarding a user to be associated with the handset device;

at the server, associating the handset device with the patient information, generating a handset specific code, and transmitting the handset specific code to the user;

at the handset device, receiving a manual input of the handset specific code; and

transmitting data from the handset device to the server in association with the handset specific code.

2. A communication method according to claim 1, wherein the patient information comprises the user'"'"'s country of residence, and wherein the server is responsive to the receipt of the handset specific code to establish a routing to a medical data server associated with the patient'"'"'s country of residence.

3. A communication method according to claim 2, wherein the routing is established by providing the handset device with the IP address of the medical data server, and wherein the handset device is operable to drop the connection to the server and reattach to the medical data server at the indicated IP address.

4. A communication method according to claim 2, wherein the handset device is operable to transmit medical data regarding the user to the medical data server.

5. A communication method according to claim 2, wherein the server is responsive to the receipt of the handset specific code to provide customer support information to the handset device, the handset device being responsive to receipt of the customer support information to update the customer support information for display at the handset.

6. A communication method according to claim 1, wherein the unique identifier is an International Mobile station Equipment Identity.

7. A communication method according to claim 4, wherein the medical data comprises one or more of the activity of or settings for the therapeutic product delivery device, carbohydrate input information and blood glucose readings.

8. A communication method according to claim 2, wherein the handset is automatically configured in dependence on the patient'"'"'s country of residence.

9. A communication method according to claim 1, wherein the patient information comprises a medical facility, clinic, healthcare professional or medical insurance company the user is associated with, and the handset is automatically configured in dependence on the medical facility, clinic, healthcare professional or medical insurance company associated with the user.

10. A communication method according to claim 1, wherein if the server identifies in response to the unique identifier that the handset device is already associated with another user, the server is operable to cancel the association between the handset device and the other user.

11. A communication method according to claim 1, wherein the unique identifier for the handset device is pre-stored at the server in advance of the patient information being transmitted to the server.

12. A system for managing communications to and from a handset device controlling a therapeutic product delivery device, the system comprising:

a server, for receiving at least part of the unique identifier for the handset device, and patient information regarding a user to be associated with the handset device, the server being operable to associate the handset device with the patient information, generate a handset specific code, and transmit the handset specific code to the user; and

a handset device, for receiving a manual input of the handset specific code transmitting data from the handset device to the server in association with the handset specific code.

13. A system according to claim 12, wherein the patient information comprises the user'"'"'s country of residence, and wherein the server is responsive to the receipt of the handset specific code to establish a routing to a medical data server associated with the patient'"'"'s country of residence.

14. A communication method for managing communications to and from a handset device controlling a therapeutic product delivery device, comprising the steps of:

transmitting, to a server, at least part of a unique identifier for a handset device for controlling a therapeutic product delivery device, and communication information specifying whether or not data from the handset device is to be communicated to the server;

at the server, entering a data accepting state or a non-data accepting state in relation to the handset in response to the communication information, generating a handset code, and transmitting the handset code to the user;

at the handset device, receiving a manual input of the handset code and in response to the handset code entering a data transmitting state or a non-data transmitting state consistent with the communication information.

15. A communication method for managing communications to and from a handset device controlling a therapeutic product delivery device, comprising the steps of:

transmitting, to a server, at least part of a unique identifier for a handset device for controlling a therapeutic product delivery device, and an unassign request for the handset device;

at the server, in response to the unassign request, entering a non-data accepting state in relation to the handset, generating a handset code, and transmitting the handset code to the user;

at the handset device, receiving a manual input of the handset code and in response to the handset code erasing medical information relating to the user from the handset device.

16. (canceled)