Remote respiratory therapy device management

1. A computer system for managing changes in remotely located patient respiratory devices, the computer system comprising:

non-transitory computer readable storage configured to store a plurality of upgrade segments that each include at least one pre-condition and component upgrade data;

a processing system comprising instructions that, when executed by at least one hardware processor, cause the at least one hardware processor to perform operations comprising:

(a) processing at least one electronic message concerning a first patient device that is configured to operate or store firmware or software, the electronic message including identification data for the first patient device;

(b) determining, based on the identification data for the first patient device that is included in the electronic message, as to whether a brokered request for the first patient device is present in a data structure;

(c) based on the determining that there is not the brokered request in the data structure:

(1) retrieving a first upgrade segment of the plurality of upgrade segments,

(2) generating, based on the first upgrade segment, the brokered request and adding the brokered request to the data structure; and

(d) generating an upgrade message based on data included in the first upgrade segment, the upgrade message to be transmitted to the first patient device, the upgrade message configured to be processed by the first patient device to thereby cause application of an upgrade package to be applied to the first patient device that changes the firmware or the software of the first patient device.

2. The computer system of claim 1 , wherein the operations further comprise:

based on determining that the brokered request is not in the data structure, retrieve, from a database and based on the identification data transmitted by the first patient device, device profile data that includes versioning data for one or more components that is associated with the first patient device,

wherein retrieval of the first upgrade segment is further based on the versioning data.

3. The computer system of claim 2 , wherein the plurality of upgrade segments are included in an upgrade specification, wherein the operations further comprise:

parsing through the plurality of upgrade segments until the pre-condition of one of the upgrade segments is matched to the retrieved versioning data of the device profile data for the first patient device.

4. The computer system of claim 1 , wherein the operations further comprise:

retrieving the brokered request from the data structure, wherein the upgrade message is generated further based on retrieval of the brokered request.

5. The computer system of claim 1 , wherein the upgrade message includes data for where an upgrade file is to be acquired by the first patient device.

6. The computer system of claim 1 , wherein the processing system further comprises:

a first computing node with at least one first hardware processor of the at least one hardware processor of the processing system; and

a second computing node with at least one second hardware processor of the at least one hardware processor of the processing system, wherein the first and second computing nodes are configured to communicate, via an electronic data communications network,

wherein the instructions are configured to cause the at least one first hardware processor to perform (b),

wherein the instructions are configured to cause the at least one second hardware processor to perform (1).

7. The computer system of claim 1 , wherein versioning information for the software or firmware of the first patient device is not included in the at least one electronic message.

8. The computer system of claim 1 , wherein the identification data includes a unique identifier that uniquely identifies the first patient device from other individual patient devices.

9. The computer system of claim 8 , wherein the unique identifier identifies a transceiver that is included with the first patient device.

10. The computer system of claim 9 , wherein the transceiver is a cellular transceiver.

11. The computer system of claim 1 , wherein the operations further comprise:

upon successfully updating the first patient device as a result of the upgrade message, removing the brokered request from the data structure.

12. The computer system of claim 1 , wherein the operations further comprise:

receiving an error message regarding how the upgrade package was processed by the first patient device; and

storing, to the non-transitory computer readable storage, data regarding the error message.

13. A non-transitory computer readable medium storing computer executable instructions for use with a computer system that communicates with a respiratory patient device, the respiratory patient device including electronic memory storing firmware or software thereon that is used to control operation of the respiratory patient device, the computer executable instructions including instructions configured to cause the computer system to perform operations comprising:

storing, to computer storage of the computer system, a plurality of upgrade segments that each include at least one pre-condition and component upgrade data;

processing at least one electronic message concerning a first patient device that is configured to operate or store firmware or software, the electronic message including identification data for the first patient device;

determining, based on the identification data for the first patient device that is included in the electronic message, as to whether a brokered request for the first patient device is present in a data structure;

based on the determining that there is not the brokered request in the data structure:

retrieving a first upgrade segment of the plurality of upgrade segments, and

generating, based on the first upgrade segment, the brokered request and adding the brokered request to the data structure; and

generating an upgrade message based on data included in the first upgrade segment, the upgrade message to be transmitted to the first patient device, the upgrade message configured to be processed by the first patient device to thereby cause application of an upgrade package to be applied to the first patient device that changes the firmware or the software of the first patient device.

14. The non-transitory computer readable medium of claim 13 , wherein the operations further comprise:

based on determining that the brokered request is not in the data structure, retrieve, from a database and based on the identification data transmitted by the first patient device, device profile data that includes versioning data for one or more components that is associated with the first patient device,

wherein retrieval of the first upgrade segment is further based on the versioning data.

15. The non-transitory computer readable medium of claim 14 , wherein the plurality of upgrade segments are included in an upgrade specification, wherein the operations further comprise:

parsing through the plurality of upgrade segments until the pre-condition of one of the upgrade segments is matched to the retrieved versioning data of the device profile data for the first patient device.

16. The non-transitory computer readable medium of claim 13 , wherein the operations further comprise:

retrieving the brokered request from the data structure, wherein the upgrade message is generated further based on retrieval of the brokered request.

17. The non-transitory computer readable medium of claim 13 , wherein the upgrade message includes data for where an upgrade file is to be acquired by the first patient device.

18. The non-transitory computer readable medium of claim 13 , wherein the identification data includes a unique identifier that uniquely identifies the first patient device from other individual patient devices.

19. The non-transitory computer readable medium of claim 18 , wherein the unique identifier is an identifier for a transceiver that is included with the first patient device.

20. A method of delivering updates to remotely located respiratory patient devices, the method comprising:

storing, to computer storage of a computer system, a plurality of upgrade segments that each include at least one pre-condition and component upgrade data;

processing, by the computer system, at least one electronic message concerning a first patient device that is configured to operate or store firmware or software, the electronic message including identification data for the first patient device;

determining, based on the identification data for the first patient device that is included in the electronic message, as to whether a brokered request for the first patient device is present in a data structure;

based on the determining that there is not the brokered request in the data structure:

retrieving a first upgrade segment of the plurality of upgrade segments, and

generating, based on the first upgrade segment, the brokered request and adding the brokered request to the data structure; and

generating an upgrade message based on data included in the first upgrade segment, the upgrade message to be transmitted to the first patient device, the upgrade message configured to be processed by the first patient device to thereby cause application of an upgrade package to be applied to the first patient device that changes the firmware or the software of the first patient device.