CODE FOR PATIENT CARE DEVICE CONFIGURATION

• US 20150371005A1
• Filed: 03/15/2013
• Published: 12/24/2015
• Est. Priority Date: 02/08/2013
• Status: Active Grant

• Current Assignee: Baxter Corporation Englewood (Baxter International Inc.)
• Original Assignee: Baxter Corporation Englewood (Baxter International Inc.)
• Inventors: SCHNEIDER, Dennis I.
• Granted Patent: US 11,075,012 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G16H 20/17 delivered via infusion or injection
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 70/40 relating to drugs, e.g. their side effects or intended usage

Abstract

Configuration output for use in configuring a patient care device for administration of a therapy to a patient. The configuration output may include at least one code. The code may be used in the verification and/or indication of at least one configuration data component used in the configuration of the patient care device to be used to administer a therapy to a patient. Additionally, a check code for validation of the entry of the code and/or check code may be provided.

Claims

1. A method for generation of a configuration output for a therapy order corresponding with a therapy to be administered to a patient using a patient care device (140), comprising:

receiving a therapy order that includes a therapy description corresponding to a therapy to be administered to a patient;

generating a configuration output for the therapy order for use in configuration of the patient care device for administration of the therapy;

wherein at least a first portion of the configuration output comprises a first part that is at least partially generated based on a portion of the therapy description; and

wherein a second portion of the configuration output comprises a first code that is at least partially generated based on the first portion.

2. The method of claim 1, wherein the generating step is at least partially completed in a computer-automated manner.

3. The method of claim 1, wherein the therapy comprises administration of an IV fluid to a patient using an infusion device.

4. The method of claim 3, wherein the therapy order comprises a dose order including a dose description corresponding to the IV fluid to be administered.

5. The method of claim 4, wherein the dose description includes one or more attributes of the IV fluid to be administered.

6. The method of claim 1, wherein the first portion is at least partially based on at least a portion of a configuration protocol of the patient care device.

7. The method of claim 6, wherein the first portion comprises a second code.

8. The method of claim 7, wherein the second code is at least partially generated based on a portion of the therapy description.

9. The method of claim 8, wherein the first code is at least partially generated based on the second code.

10. The method of claim 9, wherein the first part comprises plain text values corresponding to the configuration protocol of the patient care device.

11. The method of claim 10, wherein the configuration protocol comprises one or more configuration data input components.

12. The method of claim 10, wherein the first portion comprises a second part that includes the second code.

13. The method of claim 12, wherein each one of the first code and the second code comprise one or more human-readable digits comprising an ASCII printable character.

14. The method of claim 7, wherein the second code is indicative of the corresponding therapy description.

15. The method of claim 14, wherein the second code is indicative of a pre-stored therapy data set at the patient care device that corresponds to the corresponding therapy description.

16. The method of claim 7

wherein the first portion is based at least in part on at least a portion of each of the therapy description and the configuration protocol.

17. The method of claim 16, wherein the first portion at least partially corresponds to one or more configuration data components of the configuration protocol, a data input sequence of the configuration protocol, and at least one configuration parameter form of the configuration protocol.

18. The method of claim 7, wherein the configuration protocol comprises at least one of the following types of data:

data indicative of a location of the patient within a patient care facility;

data indicative of one of a predetermined plurality of therapy types;

data indicative of at least one drug;

data indicative of therapy concentrations;

data indicative of an administration rate; and

data indicative of an administration amount.

19. The method of claim 7, wherein the first portion comprises plain text values corresponding to the configuration protocol of the patient care device.

20. The method of claim 7, wherein for a given therapy description, one of a plurality of predeterminable second codes is generatable in the generating step.

21. The method of claim 20, wherein each of the plurality of predeterminable second codes are different.

22. The method of claim 20, wherein each one of the plurality of predeterminable second codes is generatable in corresponding relation to a different one of a plurality of time periods.

23. The method of claim 22, wherein the plurality of time periods correspond to a defined number of doses.

24. The method of claim 22, wherein, during a given one of the plurality of time periods, one of the plurality of predeterminable second codes is generatable in corresponding relation to a therapy order.

25. The method of claim 24, wherein the therapy order corresponds to a patient, and wherein the one of the plurality of predeterminable second codes is stored in corresponding relation to the patient.

26. The method of claim 25, wherein the one of the plurality of predeterminable second codes is receivable from the patient care device used to administer the therapy to the patient and data regarding the patient care device used to administer the therapy to the patient is stored in corresponding relation with the patient.

27. The method of claim 1, wherein the first portion and the first code are entered at the patient care device by a user.

28. The method of claim 27, wherein the first portion corresponds to a configuration protocol of the patient care device, and wherein the first code is used at the patient care device to verify the first portion entered by the user.

29. The method of claim 27, wherein the first portion comprises a second code, and wherein the first code is used at the patient care device to validate the second code entered by the user.

30. The method of claim 29, wherein the first code and the second code comprise one or more ASCII printable characters.

31. The method of claim 30, wherein the first code and the second code comprise alpha-numeric codes.

32. The method of claim 1, further comprising:

generating a label for affixing to a receptacle containing the IV fluid, said label comprising the configuration output.

33. The method of claim 1, wherein data corresponding to the therapy description comprise an input for an algorithm utilized to generate the first code.

34. The method of claim 33, wherein a corresponding algorithm is stored at the patient care device.

35. The method of claim 34, wherein the corresponding algorithm is operable to produce a comparison code for comparison to the first code for analysis of the first portion.

36. The method of claim 34, wherein the corresponding algorithm is operable to decipher the first code for analysis of the first portion.

37. A system for generation of a configuration output, comprising:

an order entry interface operable to receive a therapy order that includes at least a portion of a therapy description corresponding to a therapy to be administered to a patient using a patient care device; and

a configuration output generator, in operative communication with the order entry interface; and

a configuration output that is generated by the configuration output generator that comprises;

a first portion that comprises a first part that is at least partially generated based on a portion of the therapy description, and

a second portion that comprises a first code that is at least partially generated based on the first portion.

38. The system of claim 37, wherein the patient care device comprises:

a user interface for receipt of the first portion and the second portion by way of manual entry by a user.

39. The system of claim 38, wherein the therapy comprises administration of an IV fluid to a patient using the patient care device.

40. The system of claim 38, wherein the patient care device further comprises an infusion pump.

41. The system of claim 40, wherein the therapy order comprises a dose order including a dose description corresponding to the IV fluid to be administered using the infusion pump.

42. The system of claim 41, wherein the configuration output comprises a label.

43. The system of claim 42, wherein the label is applied to a receptacle containing the IV fluid.

44. The system of claim 43, wherein the patient care device is operable to verify the entry of the first portion based on the second portion.

45. The system of claim 43, wherein the first portion comprises a second code.

46. The system of claim 45, wherein the first portion comprises a second part comprising the second code.

47. The system of claim 46, wherein the first part comprises plain text values corresponding to the therapy description.

48. The system of claim 46, wherein the patient care device is operable to verify the entry of the plain text values based on the second code, and wherein the patient care device is operable to validate the second code based on the first code.

49. The system of claim 45, wherein the second code is indicative of one or more configuration data components for use in configuring the patient care device.

50. The system of claim 49, wherein the patient care device (140) is in operative communication with a pre-stored therapy data set to access configuration data components indicated by the second code.

51. The system of claim 37, wherein the order entry interface is executed by a processor in operative communication with a memory.

52. The system of claim 51, wherein the memory stores non-transitory computer readable data corresponding to the execution of the order entry interface.

53. The system of claim 37, wherein the configuration output generator is executed by a processor in operative communication with a memory.

54. The system of claim 53, wherein the memory stores non-transitory computer readable data corresponding to the execution of the configuration output generator.