Systems and methods for medical data interchange via remote command execution

• US 9,619,621 B2
• Filed: 10/22/2007
• Issued: 04/11/2017
• Est. Priority Date: 10/24/2006
• Status: Expired due to Fees

• Current Assignee: Medapps Incorporated (Abbott Laboratories Incorporated)
• Original Assignee: Medapps Incorporated (Abbott Laboratories Incorporated)
• Inventors: Dicks, Kent, Kent, Ralph, Tripp, Robert, Bartlett, Terry, Crosley, Thomas
• Primary Examiner(s): Flory, Christopher A
• Application Number:
  US11/876,711
• Publication Number:
  US 20080103554A1
• Time in Patent Office: 3,459 Days
• Field of Search: 607 60, 600300, 128903, 705 2
• CPC Class Codes: A61M 5/003 Kits for diabetics
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 15/00 ICT specially adapted for medical reports, e.g. generation or transmission thereof
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: G16H 50/20 for computer-aided diagnosis, e.g. based on medical expert systems

Abstract

A method according to an aspect of the present invention includes receiving data through a wired connection from a medical device, transmitting the data to an intermediary device, formatting a message including the received data for transmission to a medical data server, and receiving a command from the medical data server. Commands from the medical data server can be used for the authentication, configuration, and control of the medical device, intermediary device or another device operating in conjunction with the present invention, as well as to achieve other purposes. This method can be practiced automatically to allow a medical device for a patient or other subject to be monitored without requiring the patient to manually enter information.

Claims

1. A method comprising:

a plurality of medical devices each receiving data through a wired connection via a first communications protocol, wherein the first communications protocol is different for at least two of the data received;

reformatting each of the received data to a second communications protocol that is the same for each of the received data and transmitting the received data to an intermediary device;

the intermediary device formatting a message and transmitting it to a medical data server, wherein the message includes the received data;

the intermediary device receiving a command from the medical data server to alter the operation of at least one of the plurality of medical devices;

the intermediary device reformatting said command for said at least one medical device to create at least one reformatted command; and

said at least one medical device receiving said command from the intermediary device.

2. The method of claim 1, wherein the data is transmitted to the intermediary device using a wireless transmitter, wherein the wireless transmitter transmits the data to the intermediary device using a protocol selected from the group consisting of a Zigbee protocol, a Wibree protocol, an IEEE 802.11 protocol, an IEEE 802.15 protocol, an IEEE 802.16 protocol, an Ultra-Wide band (UWB) protocol, an Infrared Data Association (IrDA) protocol, a Bluetooth protocol, and combinations thereof.

3. The method of claim 1, wherein the data includes an environmental parameter, wherein the environmental parameter includes at least one of a battery charge level, a temperature, a barometric pressure, a code relating to an accessory for the medical device, a data validity measurement, an elapsed time since a previous reading by the medical device, a test result parameter, a signal-to-noise parameter, and a quality of service (QoS) parameter.

4. The method of claim 1, wherein the data is received from the medical device through a connection selected from the group consisting of an optical fiber connection, a tip and sleeve (TS) connection, a tip, ring, and sleeve (TRS) connection, a tip, ring, ring, and sleeve (TRRS) connection, a serial peripheral interface bus (SPI) connection, a universal serial bus (USB) connection, an RS-232 serial connection, an Ethernet connection, a Fire Wire connection, and combinations thereof.

5. The method of claim 1, wherein the medical device is selected from the group consisting of:

a blood glucose meter;

a pacemaker;

a blood pressure monitor;

an insulin pump;

a pulse oximeter;

a halter monitor;

an electrocardiograph;

an electroencephalograph;

a blood alcohol monitor;

an alcohol breathalyzer;

an alcohol ignition interlock;

a respiration monitor;

an accelerometer;

a skin galvanometer;

a thermometer;

a patient geolocation device;

a scale;

an intravenous flow regulator;

a patient height measuring device;

a biochip assay device;

a monitor for biological agents;

a hazardous chemical agent monitor;

an ionizing radiation sensor;

a sphygmomanometer;

a loop recorder;

a spirometer;

an event monitor;

a prothrombin time (PT) meter;

an international normalized ratio (INR) meter;

a tremor sensor;

a defibrillator; and

combinations thereof.

6. The method of claim 1, wherein the formatted message is transmitted from the intermediary device to a medical data server through a wireless network selected from the group consisting of:

a cellular network;

a General Packet Radio Service (GPRS) network;

a wireless Local Area Network (WLAN);

a Global System for Mobile Communications (GSM) network;

a Personal Communication Service (PCS) network;

an Advanced Mobile Phone System (AMPS) network;

a satellite communication network; and

combinations thereof.

7. The method of claim 1, further comprising receiving input from a user, wherein the command is generated in response to interpretation of the input.

8. The method of claim 1, further comprising receiving an authorization code from the medical data server.

9. The method of claim 1, further comprising authenticating the command.

10. The method of claim 9, wherein authenticating the command further comprises decrypting at least part of the command using at least one of:

a public key associated with the medical data server;

a private key associated with a user of the medical device; and

a private key associated with the medical device.

11. The method of claim 1, wherein the command reconfigures a software application running on the intermediary device.

12. The method of claim 1, wherein the command controls the medical device.

13. The method of claim 1, wherein the command includes data from a second medical device for transmission to the medical device.

14. The method of claim 1, further comprising:

receiving, from the medical data server, a request to authenticate access; and

generating an authentication token.

15. The method of claim 14, wherein generating an authentication token further comprises requesting entry of a password through a user interface.

16. The method of claim 14, wherein generating an authentication token further comprises retrieving a previously stored password.

17. The method of claim 14, wherein generating an authentication token further comprises cryptographically encoding a password.

18. The method of claim 14, further comprising transmitting the authentication token to the intermediary device.

19. The method of claim 14, further comprising formatting an authentication message for transmission to the medical data server, wherein the authentication message includes the authentication token.

20. The method of claim 14, further comprising receiving, from the medical data server, a message indicating that authentication failed.

21. The method of claim 1, further comprising requesting a medical device identifier from the medical device.

22. The method of claim 21, wherein receiving data from the medical device further comprises determining a medical device type based at least partially on the medical device identifier.

23. The method of claim 1, wherein the command is based on information received by the medical data server from a second medical device.

24. A method comprising:

a plurality of medical devices each receiving data through a wired connection via a first communications protocol, wherein the first communications protocol is different for at least two of the data received;

reformatting the received data to a second communications protocol, wherein the second communications protocol is the same for each of the received data, and transmitting the received data to an intermediary device;

the intermediary device formatting a message and transmitting it to a medical data server, wherein the message includes the received data;

the intermediary device receiving a command from the medical data server to alter the operation of at least one of the plurality of medical devices;

the intermediary device reformatting said command for said at least one medical device to create at least one reformatted command; and

said at least one medical device receiving said command from the intermediary device; and

encrypting at least one of;

the received data;

a portion of the received data; and

a digest of the received data.

25. The method of claim 24, wherein the encrypting utilizes a key selected from the group consisting of:

a private encryption key associated with the patient;

a private encryption key of a health care provider associated with the patient;

a public encryption key associated with an intended recipient; and

combinations thereof.

26. The method of claim 25, wherein the intended recipient is the medical data server.