Efficient Transfer of Patient Data

Patent metadata

Field	Value
Publication number	US-2025210160-A1
Application number	US-202418980962-A
Country	US
Kind code	A1
Filing date	Dec 13, 2024
Priority date	Dec 21, 2023
Publication date	Jun 26, 2025
Grant date	—

Abstract

A method includes receiving patient data attributes of patient data collected by the medical device and an indication of a destination computer for the patient data. The method includes generating, based at least on data processing capabilities of the destination computer and the patient data attributes of the patient data, a set of transmission parameters for the medical device to adhere to when sending any of the patient data. The method includes sending, by the server, the set of transmission parameters to the medical device. The method includes receiving, by the server, at least a subset of the patient data from the medical device in response to sending the set of transmission parameters to the medical device. The subset of the patient data is in compliance with the set of transmission parameters. The method includes providing the subset of the patient data to the destination computer.

First claim

1 . A server comprising:
a memory; and a processor coupled to the memory, the processor configured to:
receive, from a medical device, patient data attributes of patient data collected by the medical device and an indication of a destination computer for the patient data;
generate, based at least on data processing capabilities of the destination computer and the patient data attributes of the patient data, a set of transmission parameters for the medical device to adhere to when sending any of the patient data;
send the set of transmission parameters to the medical device;
receive at least a subset of the patient data from the medical device in response to sending the set of transmission parameters to the medical device, wherein the subset of the patient data is in compliance with the set of transmission parameters; and
provide the subset of the patient data to the destination computer.

2 . The server of claim 1 , wherein the patient data attributes comprise at least one of data formats of the patient data, a data size of the patient data, quality of service parameters associated with sending the patient data to the server, available communication mediums for sending the patient data to the server, a prioritization metric associated with at least some of the patient data, a fidelity metric for sending at least some of the patient data, a time range for sending at least some of the patient data, or an urgency metric for delivering the patient data to the destination computer.

3 . The server of claim 1 , wherein the set of transmission parameters indicates the subset of the patient data and a communications means for sending the subset of the patient data.

4 . The server of claim 3 , wherein the communications means for sending the subset of the patient data corresponds to a cellular communications means or an Institute of Electrical and Electronics Engineers (IEEE) 802.11 communications means.

5 . The server of claim 1 , wherein, in response to a determination that a first format of data is not compatible with the data processing capabilities of the destination computer, the set of transmission parameters indicates to the medical device to bypass transmission of patient data having the first format.

6 . The server of claim 1 , wherein the processor is further configured to:
send a query to the destination computer in response to receiving the patient data attributes and the indication of the destination computer from the medical device, wherein the query includes a request for the data processing capabilities of the destination computer; and receive an indication of the data processing capabilities of the destination computer in response sending the query.

7 . The server of claim 1 , wherein the processor is further configured to:
periodically send a query to destination computer, wherein the query includes a request for the data processing capabilities of the destination computer; and receive an indication of the data processing capabilities of the destination computer in response sending each query.

8 . The server of claim 1 , wherein the data processing capabilities of the destination computer indicate an availability of the destination computer to receive the patient data, an amount of available storage at the destination computer, and different formats of data that are able to be processed by the destination computer.

9 . The server of claim 1 , wherein the medical device comprises a defibrillator or a patient monitoring device.

10 . A method comprising:
receiving, by a server and from a medical device, patient data attributes of patient data collected by the medical device and an indication of a destination computer for the patient data; generating, based at least on data processing capabilities of the destination computer and the patient data attributes of the patient data, a set of transmission parameters for the medical device to adhere to when sending any of the patient data; sending, by the server, the set of transmission parameters to the medical device; receiving, by the server, at least a subset of the patient data from the medical device in response to sending the set of transmission parameters to the medical device, wherein the subset of the patient data is in compliance with the set of transmission parameters; and providing, by the server, the subset of the patient data to the destination computer.

11 . The method of claim 10 , wherein the patient data attributes comprise at least one of data formats of the patient data, a data size of the patient data, quality of service parameters associated with sending the patient data to the server, available communication mediums for sending the patient data to the server, a prioritization metric associated with at least some of the patient data, a fidelity metric for sending at least some of the patient data, a time range for sending at least some of the patient data, or an urgency metric for delivering the patient data to the destination computer.

12 . The method of claim 10 , wherein the set of transmission parameters indicates the subset of the patient data and a communications means for sending the subset of the patient data.

13 . The method of claim 12 , wherein the communications means for sending the subset of the patient data corresponds to a cellular communications means or an Institute of Electrical and Electronics Engineers (IEEE) 802.11 communications means.

14 . The method of claim 10 , wherein, in response to a determination that a first format of data is not compatible with the data processing capabilities of the destination computer, the set of transmission parameters indicates to the medical device to bypass transmission of patient data having the first format.

15 . The method of claim 10 , further comprising:
sending, by the server, a query to the destination computer in response to receiving the patient data attributes and the indication of the destination computer from the medical device, wherein the query includes a request for the data processing capabilities of the destination computer; and receiving, by the server, an indication of the data processing capabilities of the destination computer in response sending the query.

16 . The method of claim 10 , further comprising:
periodically sending, by the server, a query to destination computer, wherein the query includes a request for the data processing capabilities of the destination computer; and receiving, by the server, an indication of the data processing capabilities of the destination computer in response sending each query.

17 . The method of claim 10 , wherein the data processing capabilities of the destination computer indicate an availability of the destination computer to receive the patient data, an amount of available storage at the destination computer, and different formats of data that are able to be processed by the destination computer.

18 . The method of claim 10 , wherein the medical device comprises a defibrillator or a patient monitoring device.

19 . A non-transitory computer-readable medium comprising instructions that, when executed by a processor within a server, causes the processor to perform operations comprising:
receiving, from a medical device, patient data attributes of patient data collected by the medical device and an indication of a destination computer for the patient data; generating, based at least on data processing capabilities of the destination computer and the patient data attributes of the patient data, a set of transmissio

Assignees

• Physio Control Inc

Inventors

• Frolov Alexander
• Duke Steven Barry
• Padmanabha Seshadri K
• Rutzer Mark
• Stewart David B
• Drew Kevin
• Killebrew Mark G
• Skelton Dennis M

Classifications

• G16H40/67

  for remote operation · CPC title

• H04L67/12

  specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title

• G16H10/60 Primary

  for patient-specific data, e.g. for electronic patient records · CPC title