Fluid delivery event tracking and transaction management

Patent metadata

Field	Value
Publication number	US-11446437-B2
Application number	US-201916440406-A
Country	US
Kind code	B2
Filing date	Jun 13, 2019
Priority date	Jun 19, 2018
Publication date	Sep 20, 2022
Grant date	Sep 20, 2022

Abstract

A system includes: a fluid delivery pump and a network of multiple record management processing nodes. The fluid delivery pump is in communication with one or more of the record management-processing nodes in the network. At least a first record management processing node receives input indicating a fluid delivery event. The fluid delivery event indicates fluid delivery from the fluid delivery pump to a recipient. The record management-processing node identifies code pertinent to the fluid delivery event; the code includes criteria in which to validate the fluid delivery event. In response to validation of the fluid delivery event as specified by the criteria in the code, a resource such as the record management-processing node triggers a transaction associated with the fluid delivery event.

First claim

We claim:

1. A system comprising:
a first record management processing node in a network of multiple record management processing nodes, the first record management processing node in communication with a fluid delivery device, the first record management processing node operable to:
receive input indicating a fluid delivery event, the fluid delivery event indicating delivery of fluid from the fluid delivery device to a recipient as administered by a caregiver;
update a blockchain record associated with the recipient to indicate the fluid delivery event and an identity of the caregiver;
identify code pertinent to the fluid delivery event, the code indicating criteria in which to validate the fluid delivery event;
trigger a transaction in response to validation of the fluid delivery event as specified by the criteria in the code; and
wherein the transaction includes payment of a fee to the caregiver operating the fluid delivery device to deliver the fluid, the first record management processing node further operable to:

update the blockchain record to indicate the transaction.

2. The system as in claim 1 , wherein the multiple processing nodes are further operable to: receive the input indicating the fluid delivery event and collectively update the blockchain record associated with the recipient.

3. The system as in claim 1 , wherein the validation of the fluid delivery event includes receiving a communication originating from the caregiver authorizing the delivery of fluid.

4. The system as in claim 1 , wherein the multiple processing nodes are further operable to: record the fluid delivery event in the blockchain record.

5. The system as in claim 4 , wherein the blockchain record includes the code indicating the criteria.

6. The system as in claim 4 , wherein the blockchain record specifies a location of the code indicating the criteria.

7. The system as in claim 1 , wherein the multiple processing nodes are further operable to:
receive notification of a unique identifier value assigned to the recipient; and
utilize the unique identifier value to obtain, from the blockchain record, the code applicable to the fluid delivery event.

8. The system as in claim 1 , wherein the network of record management processing nodes includes a second record management processing node, the second record management processing node operable to:
receive the input indicating the fluid delivery from the fluid delivery device to the recipient;
identify the code pertinent to the fluid delivery; and
in parallel with the first processing node, validate the fluid delivery event based on the criteria.

9. The system as in claim 1 , wherein the fluid delivery event is a first event, the first record management processing node further operable to:
receive second input indicating a second event, the second event indicating authorization from the caregiver to administer the delivery of fluid via the fluid delivery device; and
wherein the criteria specifies that the first event and the second event are required to validate the fluid delivery event and trigger the transaction.

10. A method comprising:
receiving input indicating a fluid delivery event, the fluid delivery event indicating delivery of fluid from a fluid delivery device to a recipient as administered by a caregiver;
updating a blockchain record associated with the recipient to indicate the fluid delivery event and an identity of the caregiver;
identifying code pertinent to the fluid delivery event, the code indicating criteria in which to validate the fluid delivery event;
applying the criteria to validate the fluid delivery event;
in response to validation of the fluid delivery event based on the criteria in the code, triggering a transaction associated with the fluid delivery event; and
wherein the transaction includes payment of a fee to the caregiver operating the fluid delivery device to deliver the fluid, the method further comprising: updating the blockchain record to indicate the transaction.

11. The method as in claim 10 further comprising:
receiving the input indicating the fluid delivery event from the fluid delivery device.

12. The method as in claim 10 further comprising:
receiving a communication originating from the caregiver, the communication indicating authorization of the delivery of fluid.

13. The method as in claim 10 further comprising:
recording the fluid delivery event in the blockchain record.

14. The method as in claim 13 , wherein the blockchain record includes the code indicating the criteria.

15. The method as in claim 13 , wherein the blockchain record includes a pointer specifying a location of the code indicating the criteria.

16. The method as in claim 10 further comprising:
receiving notification of a unique identifier value assigned to the recipient; and
utilizing the unique identifier value to obtain the code including the criteria applicable to the fluid delivery event.

17. The method as in claim 10 further comprising:
recording occurrence of the fluid delivery event and transaction in the blockchain record at each of multiple record management processing nodes in a network.

18. The method as in claim 10 , wherein the fluid delivery event is a first event, the method further comprising:
receiving notification of a second event indicating authorization from the caregiver to administer the fluid delivery to the recipient via the fluid delivery device; and
wherein the criteria specifies that the first event and the second event are required to validate the fluid delivery event and trigger the transaction, the transaction being between the recipient and the caregiver.

19. Computer-readable storage hardware having instructions stored thereon for execution, such that the instructions, when executed by computer processor hardware, cause the computer processor hardware to:
receive input indicating a fluid delivery event, the fluid delivery event indicating delivery of fluid from a fluid delivery device to a recipient as administered by a caregiver;
update a block chain record associated with the recipient to indicate the fluid delivery event and an identity of the caregiver;
identify code pertinent to the fluid delivery event, the code including criteria in which to validate the fluid delivery event;
generate a notification in response to validation of the fluid delivery event as specified by the criteria in the code; and
wherein the transaction includes payment of a fee to the caregiver operating the fluid delivery device to deliver the fluid, the computer processor hardware further operative to: update the blockchain record to indicate the transaction.

20. The system as in claim 9 , wherein the transaction includes payment to the caregiver for administering the delivery of fluid to the recipient.

21. The system as in claim 1 , wherein the code is obtained from the blockchain record associated with the recipient.

22. The system as in claim 1 , wherein the input indicating the fluid delivery event originates from the fluid delivery device.

23. The system as in claim 1 , wherein the validation of the fluid delivery event as specified by the code requires receipt of i) first communications originating from the caregiver authorizing the delivery of fluid to the recipient; ii) second communications originating from a pharmacy indicating supply of the fluid to the caregiver; iii) third communications from the fluid delivery device indicating deliver

Assignees

• Ivenix Inc
• Fresenius Kabi Usa Llc

Inventors

• Ambrosina Jesse E
• Gray George W

Classifications

• A61M2005/14208

  with a programmable infusion control system, characterised by the infusion program · CPC title

• A61M2205/3553

  remote, e.g. between patient's home and doctor's office · CPC title

• G06Q20/02

  involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] · CPC title

• G06Q20/389

  Keeping log of transactions for guaranteeing non-repudiation of a transaction · CPC title

• G16H40/00

  ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices · CPC title