IP Library Granted Patent US 12712062
Granted Patent B2
US 12712062 · App. 17/599,470 · Granted Aug 18, 2026

Storing, controlling, and porting respiratory settings from a remote server

Inventors: Gregory Robert Peake (Sydney, AU); Ryan Mathew Hernandez (Encinitas, CA)
Assignee: ResMed Inc.
G16H20/40A61M16/0003A61M16/024G06F16/245G16H40/63G16H40/67G16H50/30A61M2205/3334A61M2205/3368A61M2205/3584A61M2205/502A61M2205/52A61M2205/609A61M2205/84A61M2209/01A61M2230/04A61M2230/205
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12712062
App. No.
17/599,470
Granted
Aug 18, 2026
Kind
B2
Abstract

Disclosed are systems and methods for automatically porting respiratory therapy settings to a new respiratory therapy device. Currently, when a patient replaces receives a replacement respiratory therapy device, the prescription settings must be manually ported. Accordingly, the inventors have developed technology to automatically, port, translate, and validate therapy settings and modes to a replacement respiratory therapy device.

Claims (70)

1 . A system comprising:

a prescription database with prescription therapy settings referenced to patient account IDs comprising a unique identifier for each patient in the database in communication with a prescription server;

a first respiratory therapy device;

a second respiratory therapy device;

an interface;

a memory containing machine readable medium comprising machine executable code having stored thereon instructions for performing a method;

a control system coupled to the memory comprising one or more processors, the control system configured to execute the machine executable code to cause the control system to:

receive input, from the interface, indicating a patient would like to port prescription therapy settings for the first respiratory therapy device from the first respiratory therapy device to the second respiratory therapy device;

receive, through the interface, an account ID associated with the patient, a hardware identifier associated with the first respiratory therapy device, and a hardware identifier associated with the second respiratory therapy device;

send, to the prescription server, a request comprising the account ID and the hardware identifier associated with the first respiratory therapy device to retrieve the prescription therapy settings for the first respiratory therapy device from the prescription server;

receive, from the prescription server based on the account ID, the prescription therapy settings for the first respiratory therapy device if the hardware identifier is validated; and

store the prescription therapy settings for the first respiratory therapy device in a memory of the second respiratory therapy device.

2 . The system of claim 1 , wherein the receiving, from the prescription server, prescription therapy settings further comprises:

retrieving a respiratory quality indicator referenced to the account ID based on respiratory therapy data output from the first respiratory device;

determining whether the respiratory quality indicator is above a threshold; and

flagging the patient for follow up and denying the request to port the prescription therapy settings if the respiratory quality indicator is below the threshold.

3 . The system of claim 2 , wherein the respiratory quality indicator is an apnea hypopnea index.

4 . The system of claim 1 , wherein the receiving, from the prescription server, prescription therapy settings further comprises:

determining a time window that has expired since the prescription therapy settings were last updated;

determining whether the time window is above a threshold; and

flagging the patient for follow up in a prescription therapy database and denying the request to port the prescription therapy settings if the time window is above the threshold.

5 . The system of claim 1 , wherein the receiving, from the prescription server, prescription therapy settings further comprises:

requesting a set of information from the patient;

evaluating the information to determine whether a significant change has occurred relevant to the patient prescription therapy settings; and

flagging the patient for follow up in a prescription therapy database and denying the request to port the prescription therapy settings if the significant change has occurred.

6 . The system of claim 5 , wherein the set of information includes weight, BMI, muscle tone changes, or any combination thereof.

7 . The system of claim 5 , wherein the set of information comprises audio data received through a microphone, and wherein the audio data is processed to determine whether the patient has a significant change in tone.

8 . The system of claim 5 , wherein the set of information comprises image data of a face that is compared to previously captured image data to identify a significant facial change.

9 . The system of claim 8 , wherein the significant facial change indicates a significant change in BMI.

10 . The system of claim 1 , wherein the receiving, from the prescription server, prescription therapy settings further comprises:

requesting a set of oximeter data output from a pulse oximeter;

processing the oximeter data to determine whether the prescription therapy settings should be updated; and

flagging the patient for follow-up in the prescription therapy database and denying the request to port the prescription therapy settings if the settings should not be updated.

11 . The system of claim 1 , wherein the prescription therapy settings are received over a cellular antenna connected to the first respiratory therapy device.

12 . The system of claim 1 , wherein the prescription therapy settings are received over a Bluetooth or Wi-Fi connection to a mobile device connected to the first respiratory therapy device.

13 . The system of claim 1 , wherein the prescription therapy settings are encrypted from the prescription server to the first respiratory therapy device.

14 . The system of claim 1 , wherein the prescription therapy settings comprise minimum pressure, maximum pressure, and a therapy mode.

15 . The system of claim 1 , wherein the receiving, through the interface, an account ID associated with the patient's account and a serial number associated with the second respiratory therapy device, further comprises:

displaying a code on a display of the first respiratory therapy device;

requesting, on the interface, the code to be entered; and

only receiving the general and prescription therapy settings of the code is validated.

16 . The system of claim 1 , wherein the receiving the prescription therapy settings further comprises translating the prescription therapy settings by a predetermined translation factor based on a difference between the first and second respiratory therapy device.

17 . A system comprising:

a prescription database with prescription therapy settings referenced to patient prescription IDs comprising a unique identifier for each patient in the database in communication with a prescription server;

a patient database with general patient data referenced to a set of patient account IDs in communication with a patient server;

a first respiratory therapy device;

an interface;

a memory containing machine readable medium comprising machine executable code having stored thereon instructions for performing a method;

a control system coupled to the memory comprising one or more processors, the control system configured to execute the machine executable code to cause the control system to:

receive input, from the interface, indicating a patient would like to port prescription therapy settings from a second respiratory therapy device;

receiving, through the interface, an account ID associated with the patient and a serial number associated with the second respiratory therapy device;

sending, to the patient server, a request comprising the account ID and the serial number to retrieve the prescription therapy settings for the second respiratory therapy device from the prescription server;

receiving, from the patient server based on the prescription ID, prescription therapy settings for the second respiratory therapy device if the serial number is validated set from the prescription server; and

storing the prescription therapy settings for the second respiratory therapy device in a memory of the first respiratory therapy device.

18 . The system of claim 17 , wherein storing the prescription therapy settings in a memory of the second respiratory therapy device further comprises storing the prescription therapy settings for a single usage session.

19 . The system of claim 18 , wherein the single usage session comprises deleting the prescription therapy settings in the memory of the second respiratory therapy device after a certain time window has expired.

20 . The system of claim 18 , wherein the single usage session comprises deleting the prescription therapy settings in the memory of the second respiratory therapy device after the respiratory therapy device has been powered off.

21 . The system of claim 18 , wherein the single usage session comprises deleting the prescription therapy settings in the memory of the second respiratory therapy device after 24 hours.

22 . The system of claim 18 , wherein the single usage session comprises deleting the prescription therapy settings in the memory of the second respiratory therapy device after a notification that the patient has checked out of an associated hotel.

23 . A method comprising:

receiving, at a prescription server from a patient computing device, a request to port prescription therapy settings to a respiratory therapy device comprising an account ID associated with the patient and a serial number associated with the respiratory therapy device;

receiving at the prescription server, a query for a prescription database for the account ID and the serial number to retrieve a set of prescription therapy settings from the prescription database;

processing, with the prescription server, the serial number to determine whether it is validly associated with the account ID; and

sending, to the respiratory therapy device, the set of prescription therapy settings referenced to the account ID if the serial number is validated.

24 . The method of claim 23 , wherein the prescription therapy settings include treatment pressure referenced to a date of prescription, a prescribing doctor, a prescribed mode of therapy, a prescribed type, model, and serial number of respiratory therapy device, or any combination thereof.

25 . The method of claim 23 , further comprising determining whether the prescription is adequate on the respiratory therapy device.

26 . The method of claim 25 , further comprising determining a new prescription is required for the patient, if the prescription is not adequate on the respiratory therapy device.

27 . The method of claim 23 , further comprising determining whether the patient is in possession of the respiratory therapy device.

28 . The method of claim 23 , further comprising adjusting the prescription therapy settings from another respiratory therapy device currently being used by the patient to the respiratory therapy device.

29 . The method of claim 23 , wherein the prescription server is configured to predict mappings between respiratory therapy devices for particular types of patients based on patient data.