Processing

Please wait...

Settings

Settings

Goto Application

1. WO2020197990 - BLOCKCHAIN SYSTEMS AND METHODS FOR REMOTE MONITORING

Note: Text based on automatic Optical Character Recognition processes. Please use the PDF version for legal matters

[ EN ]

CLAIMS

1. A method for processing data from mobile medical devices, comprising:

i) receiving a network packet, the network packet comprising a first digital signature and a dual payload, a first payload of the dual payload comprising anonymous data, a second payload of the dual payload comprising a second digital signature and a hash;

ii) authenticating the network packet by recovering the dual payload from at least the first digital signature using a member of a list of public keys assigned to authorized data sources;

iii) using the member of the list of public keys to identify a patient;

iv) inserting the anonymous data into a record for the patient in a privacy -compliant database; and

v) pushing the anonymous data to a distributed ledger without any patient identification

information.

2. A method for processing data from mobile medical devices, comprising:

i) receiving a network packet from a mobile medical device, the network packet comprising a dual payload, a first payload of the dual payload comprising anonymous data, a second payload of the dual payload comprising a digital signature and a hash;

ii) authenticating the network packet by verifying the digital signature using a member of a list of public keys assigned to authorized data sources;

iii) using the member of the list of public keys to identify a patient;

iv) inserting the anonymous data into a record for the patient in a privacy -compliant database; and

v) pushing the anonymous data to a distributed ledger without any patient identification

information.

3. The method of claim 1 or claim 2, further comprising: authenticating the hash by the verifying the second digital signature applied to the hash using the member of the list of public keys.

4. The method of claim 1 or claim 2, wherein the member of the list of public keys is assigned to a mobile medical device.

5. The method of claim 1 or claim 2, wherein the anonymous data is pushed to the distributed ledger from a wallet or from a peer in a distributed ledger network.

6. The method of claim 1 or claim 2, wherein the pushing comprises passing instructions and the second digital signature to a peer in a distributed ledger network, the instructions executable by the peer to add the hash to the distributed ledger.

7. The method of claim 6, wherein the pushing further comprises passing a digital signature for the privacy -compliant database applied at least to the instructions and the hash to the peer.

8. The method of claim 7, wherein the digital signature for the privacy -compliant database is applied to at least the instructions, the hash, and the second digital signature.

9. The method of claim 1 or claim 2, wherein the instructions are obtained from the second payload.

10. The method of claim 1 or claim 2, wherein the instructions are obtained from the second digital signature.

11. The method of claim 1 or claim 2, further comprising: authorizing access to at least one of the privacy -compliant database record, a block in a blockchain referencing the hash in the distributed ledger, and the hash in the distributed ledger.

12. The method of claim 2, wherein the mobile medical device gathers and transmit data and the further mobile medical devices are drug delivery devices.

13. The method of claim 1 or claim 2, wherein the authorized data source comprises a sensor or a dispenser.

14. The method of claim 2, wherein the mobile medical device further comprises a mechanical actuator, wherein the authorized data source is activated into a data collection mode by the mechanical actuator.

15. The method of claim 14, wherein the mechanical actuator is configured for operation by the patient.

16. The method of claim 2, wherein the mobile medical device is a nebulizer.

17. The method of claim 1 or claim 2, wherein electronic health records databases are separate from the privacy -compliant database and the distributed ledger.

18. The method of claim 2, wherein the public key is created by a manufacturer of the mobile medical device.

19. The method of claim 1 or claim 2, wherein the second payloads are anonymous, with no patient identification information.

20. The method of claim 1 or claim 2, wherein the second payload comprises a smart contract or reference to a smart contract.

21. The method of claim 2, wherein the digital signature is generated by a key signing chip onboard the mobile medical device.

22. The method of claim 21, wherein the key signing chip comprises a private key, the private key used to generate the digital signature.

23. The method of claim 2, wherein the mobile medical device comprises a device identification code, the device identification code being a member of the list of public keys paired to a private key, the private key used to generate the digital signature.

24. The method of claim 23, further comprises: verifying the digital signature, comprising: passing a series of parameters through one or more predetermined digital signature verification functions, the series of parameters comprising: the ciphertext and a parameter derived from the device identification code.

25. The method of claim 24, wherein the parameter derived from the device identification code is at least a portion of the device identification code.

26. The method of claim 24, wherein the device identification code corresponds to, comprises, or is used to derive a public key, the public key corresponding to a private key used to form the digital signature.

27. The method of claim 1 or claim 2, wherein the anonymous data comprises at least one timestamp and at least one duration-of-use for the mobile medical device.

28. A system for remote management of patient compliance, comprising:

a mobile medical device, comprising:

i) a processor;

ii) a non-transitory computer readable memory in communication with the processor;

iii) a data source in communication with the processor;

iv) a reference to predetermined network coordinates stored in the memory;

v) use instructions for treating a medical condition stored in the memory, and

v) program code stored in the memory, the program code executable by the processor to perform data communication operations, the data communication operations comprising:

a) processing signals from the data source to obtain device data;

b) inserting dual payloads and device signatures applied to the dual payloads into network packets, first payloads of the dual payloads comprising at least portions of the device data, second payloads of the dual payloads comprising hashes of the at least portions of the device data and device signatures applied to the hashes; and

c) pushing the network packets to the predetermined network coordinates in response to internally-generated prompts.

29. The system of claim 28, wherein the system further comprises: a computing infrastructure comprising:

i) the predetermined network coordinates;

ii) a privacy -compliant database configured to receive the device data; and

iii) a list of public keys containing a public key for the mobile medical device, the public key for the mobile medical device effective to recover the hashes from the device signatures applied to the hashes; and

iv) at least one access point for communication with a distributed ledger network, the at least access point configured to push instructions to a distributed ledger to add the hashes to the distributed ledger without any patient identification information.

30. The system of claim 29, the computing infrastructure further comprising program code stored in a non-transitory computer readable memory, the program code executable by a processor to perform remote monitoring of the device data received by the privacy -compliant database.

31. The system of claim 30, wherein the remote monitoring comprises: adjusting a schedule for one or more of the pulling, downloading, and processing if the determined risk of readmission exceeds a first threshold; and optionally triggering an intervention protocol if the determined risk of readmission exceeds a second threshold.

32. The system of claim 30, wherein the remotely monitoring further comprises:

a) pulling the hash and the device signature applied to the hash from the distributed ledger; b) authenticating the hash by recovering the hash from at least the device signature applied to the hash;

c) verifying the accuracy of the downloaded at least a portion of the device data against the pulled hash; and

d) processing the at least a portion of the device data in combination with the use

instructions to obtain the at least one patient compliance parameter.

33. The system of claim 32, wherein the at least one patient compliance parameter comprises a measure of patient compliance with the use instructions.

34. The system of claim 33, wherein the at least one patient compliance parameter comprises:

a measure of patient non-compliance with the use instructions,

a cumulative number of missed treatments by the mobile medical device, a cumulative quantity of medication dispensed by the mobile medical device, a probability of readmission of the patient to a healthcare facility to treat the medical condition,

an estimate of an excess readmission rate, or any combination thereof.

35. The system of claim 28, wherein the dual payloads are recovered from the device signatures applied to the dual payloads using a public key.

36. The system of claim 36, wherein the public key is created by a manufacturer of the mobile medical device.

37. The system of claim 28, wherein the mobile medical device further comprises a private key embedded in an onboard key signing chip.

38. The system of claim 37, wherein the communication operations further comprise using the private key to generate the device signatures applied to the hashes.

39. The system of claim 28, wherein the second payloads contains no patient identification information.

40. The system of claim 28, wherein the second payload comprises one or more instructions for inserting the hash into a distributed ledger.

41. The system of claim 40, wherein the one or more instructions are recovered from the device signature applied to the hash.

42. The system of claim 29, wherein the computing infrastructure further comprises:

i) a further processor;

ii) a private key; and

iii) instructions executable by the further processor to use the private key to generate digital signatures applied to the device signatures applied to the hashes.

43. The system of claim 42, wherein the mobile medical device comprises a key signing chip that generates the private key.

44. The system of claim 28, wherein the device data comprises a log of mobile medical device usage data including one or more of time-of-use, frequency of use, and use-duration data for the mobile medical device.

45. The system of claim 44, wherein the log of mobile medical device usage data comprises at least one of time, duration, and frequency of usage of the mobile medical device.

46. The system of claim 28, wherein a first threshold is triggered when the log of mobile medical device usage indicates non-compliant usage, lack of usage, and/or overusage of the mobile medical device by the intended user.

47. The system of claim 28, comprising further mobile medical devices that are drug delivery devices, wherein the mobile medical device gathers and transmit data from the further mobile medical devices.

48. The system of claim 28, wherein the mobile medical device comprises a sensor or a dispenser.

49. The system of claim 49, wherein the mobile medical device comprises a mechanical actuator.

50. The system of claim 49, wherein the mechanical actuator is configured for operation by the patient.

51. The system of claim 28, wherein the mobile medical device is a nebulizer.