SYSTEM AND METHOD FOR IDENTIFYING AND PAIRING DEVICES

• US 20120221634A1
• Filed: 05/09/2012
• Published: 08/30/2012
• Est. Priority Date: 06/15/2009
• Status: Active Grant

• Current Assignee: Nxstage Medical Incorporated (Fresenius Medical Care AG)
• Original Assignee: Nxstage Medical Incorporated (Fresenius Medical Care AG)
• Inventors: Treu, Dennis M., Albiston, Kevin
• Granted Patent: US 8,909,613 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G16H 20/00 ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
• CPC Class Codes: G16H 40/40 for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: Y10S 707/959 Network
• CPC Class Codes: Y10S 707/967 Peer-to-peer

Abstract

A computer system and method for identifying and pairing devices. The system includes a plurality of remote user interface computers, each having a display device and a user input device and each connected to a first network via a first respective data communication link. The system also includes a plurality of medical devices each having a medical device user interface and a second data communication link adapted to exchange data with the remote user interface computers. The system also includes a database adapted to communicate with the remote user interface computers via a connection to the first network or via a direct connection to one of the remote user interface computers, the database being adapted to store patient medical information including a treatment prescription that includes use of one of the medical devices.

Claims

1-29. -29. (canceled)

30. A system for device identification and pairing comprising:

a plurality of remote user interface computers, each connected to a network via a data communication link;

a plurality of medical devices each connected to the data communication link and adapted to exchange data with the remote user interface computers; and

a database to store patient medical information including a treatment prescription that includes use of at least one of the medical devices,

wherein each remote user interface computer is associated with a patient based on identification and verification information entered by an operator to the remote user interface computer,

wherein, based on the patient identification and verification, the remote user interface computer retrieves the treatment prescription associated with the patient from the database,

wherein, based on the treatment prescription, the remote user interface computer transmits, using the data communication link, verification and pairing signals to a selected medical device that the operator intends to use for treating the patient, and

wherein, when the remote user interface computer receives correct verification and pairing response signals from the selected medical device, a communication link for carrying out the prescribed treatment is established.

31. The system of claim 30, wherein the verification signal includes a signal verifying that the selected medical device is available for use.

32. The system of claim 31, wherein the verification signal includes medical device identification information.

33. The system of claim 32, wherein the medical identification information includes one of a medical device identification number, network address, and serial number.

34. The system of claim 30, wherein the pairing signal includes a request prompting the operator to enter a verification key sequence on the selected medical device.

35. The system of claim 34, wherein the verification key sequence is randomly generated by the remote user interface computer.

36. The system of claim 35, wherein the verification key sequence includes a sequence of buttons to be selected by the operator on the selected medical device.

37. The system of claim 30, wherein the verification response signal includes medical device identification information.

38. The system of claim 37, wherein the medical identification information includes one of a medical device identification number, network address, and serial number.

39. The system of claim 30, wherein the pairing response signal includes a message indicating a sequence of keys actually selected by the operator.

40. The system of claim 39, wherein the sequence of keys actually selected by the operator includes a sequence of buttons actually selected by the operator on the medical device.

41. The system of claim 30, wherein the correct verification and pairing response signals include signals that match the corresponding verification and pairing signals transmitted by the remote user interface computer to the selected medical device.

42. The system of claim 30, further comprising a health care provider computer system in data communication with the remote user interface computer and adapted to retrieve, add, and modify patient medical information stored in the database.

43. The system of claim 42, wherein the health care provider computer system is adapted to monitor patient treatment in real-time as it occurs on the selected medical device that is being used to treat the patient.

44. The system of claim 42, wherein the health care provider computer system is adapted to store and later retrieve the patient treatment process as it occurred on the selected medical device.

45. A method for identifying a medical device and pairing the identified medical device with a remote user interface computer, the method comprising:

receiving at the remote user interface identification information representing the identity of a patient;

verifying the patient identification information using information stored in a database;

receiving, based on verified patient identification information, a prescribed medical treatment regimen from the database;

identifying a selected medical device available for carrying out the prescribed medical treatment;

transmitting, using a data communication link, a pairing signal from the remote user interface computer to the identified medical device;

receiving, using the data communication link, a pairing signal response from the identified medical device;

comparing the pairing signal with the pairing signal response; and

establishing a communication link for carrying out the prescribed treatment based on a result of the comparison.

46. The method of claim 45, wherein the pairing signal includes a signal prompting the operator to enter a sequence of keys on the identified medical device.

47. The method of claim 45, wherein the pairing response signal includes a sequence of keys actually entered by the operator on the identified medical device.

48. The method of claim 47, wherein when the prompted sequence of keys and the actual sequence of keys do not match, the communication link is not established.

49. The method of claim 45, further comprising periodically checking the data communication link between the remote user interface computer and the identified medical device to ensure that a communication connection is maintained.

50. The method of claim 45, further comprising:

determining if a multi-system environment is present;

if a multi-system environment is present, carrying out a first operational sequence including;

displaying patient identification and devices to verify;

for each device to verify;

receiving input from an operator indicating a selected device to verify;

displaying patient identification and a verification key sequence;

receiving key sequence data from the selected device;

verifying the received key sequence data;

indicating that the selected device is verified when the received key sequence data matches the displayed verification key sequence;

displaying a selected device and prompting the operator to retry or change devices when the received key sequence data does not match the displayed verification key sequence;

repeating the first operational sequence until all devices are verified;

if a multi-system environment is not present or if all devices in the multi-system environment have been verified, carrying out a second operational sequence including;

displaying patient identification and verified devices;

exchanging handshake signals with each verified device, respectively; and

initiating the prescribed medical treatment regimen;

when devices are not connected or moved, carrying out a third operational sequence comprising;

displaying a list of available devices connected to a network and not connected to the remote user interface computer;

prompting the operator to retry a connection with one or more devices or to change devices;

receiving input data from the operator indicating whether the operator selected to retry or change devices;

retrying to connect with one or more devices when the operator selects retry; and

performing a pairing and setup parameter test when the operator selects to change devices.