Patent ID: 12251535

The foregoing and other objects, features, and advantages of the invention will be apparent from the following more particular description of preferred embodiments herein, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, with emphasis instead being placed upon illustrating the embodiments, principles, concepts, etc.

DETAILED DESCRIPTION AND FURTHER SUMMARY OF EMBODIMENTS

A fluid delivery system includes a fluid pump and a fluid management system. The fluid management system receives input indicating a fluid of a particular type to be delivered to a recipient. The fluid management system maps the particular type of the fluid to a set of parameters to be monitored during delivery of the fluid to the recipient. During delivery of the particular fluid to the recipient, the fluid management system monitors feedback from the recipient for each of the one or more patient parameters in the set. Based on the feedback, the fluid management system provides alerts and/or controls delivery of the fluid to the recipient.

Now, more specifically,FIG.1is an example diagram illustrating a fluid delivery system according to embodiments herein.

As shown, the fluid delivery environment100includes fluid management system110, network190, and fluid pump120. Fluid pump120includes disposable cassette104and fluid pump manager140(controller). Disposable cassette104includes appropriate mechanical components, electrical components, etc., to control a rate of delivering fluid102through the tube155to the recipient in accordance with a fluid delivery order and input from the caregiver109.

Fluid pump manager140of the fluid pump120and/or fluid management system110controls delivery of a respective fluid (such as fluid therapy) to a recipient108in accordance with input from the fluid management system110and/or caregiver109.

More specifically, caregiver109oversees operation of the fluid pump120to deliver the fluid102(stored in the fluid source121) to the recipient108(such as patient). For example, the caregiver109provides connectivity of the fluid source121(storing respective fluid102) to the fluid pump120via tube154. The caregiver109further provides connectivity of the fluid pump120to the recipient108via tube155.

Wireless or wired communication link127-1and network190provide communication connectivity between the fluid pump120and the fluid management system110.

Note that any of the resources as discussed herein can be implemented via hardware, software, or a combination of hardware and software. For example, the fluid pump manager140can be configured as fluid pump manager hardware, fluid pump manager software, or a combination of fluid pump manager hardware and fluid pump manager software; the fluid management system110can be configured as fluid management hardware, fluid manager software, or a combination of fluid manager hardware and fluid manager software; and so on.

FIG.2is an example diagram illustrating management of delivering fluid therapy according to embodiments herein.

As previously discussed, and as more particularly shown inFIG.2, the fluid delivery environment100includes a fluid management system110and fluid pump120. Fluid pump120delivers selected fluid (such as fluid102) to recipient108via tube155.

Embodiments herein include keeping track of one or more patient parameters that pertain to delivery of fluid to recipients.

For example, in processing operation #1, the impact analyzer112of the fluid management system110receives input205indicating which of multiple parameters (such as vital signs or other suitable parameters indicating a health of a patient) pertain to delivery of different types of fluid therapies such as drugs.

In one embodiment, it is desirable to monitor different patient parameters (such as one or more of heart rate, body temperature, blood pressure, respiration rate, blood oxygen saturation level, blood glucose levels, partial thromboplastin time test, cardiac output level, etc.) depending upon the type of fluid being delivered to the recipient108.

Map information150indicates different types of patient parameters most pertinent to the delivery of a corresponding fluid.

FIG.3is an example diagram illustrating a mapping of drug type to a delivery algorithm and corresponding set of one or more delivery parameters according to embodiments herein.

For example, in one embodiment as shown inFIG.3, the map information150indicates that parameters P1and P5are to be monitored during delivery of fluid type #1to a respective recipient. Additionally, map information150indicates a corresponding algorithm170-1pertinent to delivering the fluid type #1. In this example embodiment, assume that the algorithm170-1indicates or includes threshold information associated with the selected parameters P1and P5. The algorithm170-1is operative to monitor received feedback associated with fluid delivery and initiate generation of an alert on the display screen130(or audible alert from a speaker) of the fluid pump120to caregiver109in response to detecting a condition in which the monitored feedback for the one or more parameters fall outside a desired range as further discussed herein during a corresponding fluid delivery to the recipient108.

As further shown, the map information150indicates that parameters P2and P5are to be monitored during delivery of fluid type #2C to a respective recipient. Additionally, map information150indicates a corresponding algorithm170-2pertinent to delivering the fluid type #2(such as Heparin). In this example embodiment, the algorithm170-2indicates or includes threshold information associated with the selected parameters P2and P5.

As further discussed herein, the algorithm170-2can be configured to monitor received feedback associated with fluid delivery and initiate generation of an alert on the display screen130to caregiver109in response to detecting a condition in which the monitored feedback for one or more parameters fall outside a desired range during a corresponding fluid102delivery to the recipient108.

The map information150indicates that parameters P2and P3are to be monitored during delivery of fluid type #3to a respective recipient. Additionally, map information150indicates a corresponding algorithm170-3pertinent to delivering the fluid type #3(such as Morphine). In this example embodiment, assume that the algorithm170-3indicates or includes threshold information associated with the selected parameters P2and P3. As further discussed herein, the algorithm170-3can be configured to monitor received feedback associated with fluid delivery and initiate generation of an alert on the display screen130to caregiver109in response to detecting a condition in which the monitored feedback for one or more parameters fall outside a desired range during a corresponding fluid delivery to the recipient.

Referring toFIG.3and again toFIG.2, in further example embodiments, any suitable entity creates the input205and corresponding map information150based on prior experiences (history) of delivering the different types of fluids to recipients. Additionally, or alternatively, in one embodiment, the input205is based on medical analysis of which of multiple parameters are most important to monitor during a respective type of fluid infusion.

Thus, via map information150, the fluid management system110maps the particular type of the drug (fluid) as specified by the order115to a set of patient parameters to be monitored during delivery of the drug to the recipient108.

In one nonlimiting example embodiment, the fluid type #1maps to parameters P1(respiration rate) and P5(heart rate); fluid type2C maps to parameters P2(such as blood oxygen saturation level) and P5(heart rate); fluid type #3maps to P2(blood oxygen level) and P3(blood pressure); and so on.

Note that the set of patient parameters associated with each fluid therapy includes any suitable information. For example, in one embodiment, the set of patient parameters are pertinent to delivery of the respective fluid therapy such as drug and possible or likely adverse effects to the recipient based on a history of delivering the respective type of drug to other patients.

Note further that the parameters to monitor during delivery of a respective particular type of drug can be determined in any suitable manner. For example, in one embodiment, the set of parameters pertinent to delivery of the particular type of drug are learned from monitoring delivery of the respective type of drug to a population of multiple patients and their reactions to same.

Additionally, or alternatively, as previously discussed, the parameters to be monitored for a given infusion can be determined based on a theoretical study of patient parameters P1, P2, P3, etc., that are most likely to be impacted during delivery of the respective type of drug.

Note further that the parameters monitored by the respective algorithm can vary depending on the embodiment. For example, in one embodiment, the set of patient parameters monitored via the feedback include lab results associated with the recipient108. In accordance with another example embodiment, the set of patient parameters monitored via the feedback include vital signs of the recipient such as one or more of the following: i) P1—respiration rate, ii) P2—blood oxygen level, iii) P3—blood pressure, iv) P4—blood glucose levels, v) P5—heart rate, vi) P6—partial thromboplastin time test, etc.

In processing operation #2ofFIG.2, the impact analyzer112receives or retrieves further input indicating a fluid order115prescribed by a caregiver such as a doctor to the recipient108.

The fluid order115(such as drug order, therapy order, etc.) includes any suitable information.

For example, in one embodiment, the fluid order115indicates an identity (such as name assigned or unique identifier value UIVXY) of the recipient108to which the fluid order115pertains.

Additionally, the fluid order115indicates a particular type of fluid102(such as a drug of a particular type2C) to be delivered from the fluid pump120through the tube155to the recipient108.

In certain instances, the fluid order115includes or specifies delivery instructions such as a rate and/or amount of fluid to be delivered to the recipient108.

In further example embodiments, the fluid management system110communicates the fluid order115over network190and communication link127-1to the fluid pump manager140of the fluid pump120. The fluid pump manager140initiates display of notification132on the display screen130of fluid pump120. The notification132indicates useful information such as the fluid order115and guides the respective caregiver109in a delivery and setup of the fluid pump120to deliver fluid102(such as a particular type of fluid2C as indicated by the fluid order) to the recipient108.

In addition to providing notification of the fluid order115to the fluid pump manager140, in processing operation #3, the impact analyzer112of the fluid management system110analyzes the fluid order115to determine one or more parameters that pertain to delivery of the respective fluid order115to the recipient108.

As previously discussed, the repository180-1stores algorithms170(such as algorithm170-1, algorithm170-2, algorithm170-3, etc.) associated with different types of fluid that can be delivered to a respective recipient. In this example embodiment, the impact analyzer112uses the map information150to map the fluid order115(and fluid type2C) to algorithm170-2and corresponding parameters P2and P5to be monitored while delivering the fluid102(type2C) to the recipient108. As previously discussed, the selected algorithm170-2includes any suitable information facilitating delivery of the fluid as specified by the fluid order115to recipient108.

In processing operation #4, the fluid management system110communicates the selected algorithm170-2, and/or parameters P2and P5, etc., to the fluid pump120and/or feedback analyzer113of fluid management system110. The selected algorithm170-2is configured to monitor the feedback for the multiple patient parameters P2and P5during delivery of drug #2C (fluid) to the recipient108via tube155.

FIG.4is an example diagram illustrating notification of one or more parameters to monitor while delivering a respective fluid to a recipient according to embodiments herein.

In processing operation #5, the fluid pump120receives the algorithm170-2or at least the notification465of parameters P2and P5to be monitored during the delivery of the fluid2C as specified by the fluid order115to the recipient108.

Note again that the selected algorithm170-2can be executed at any suitable one or more location such as fluid management system110, fluid pump120, etc.

In one embodiment, in processing operation #6, the fluid pump manager140initiates display of the parameters P2and P5in notification465on the display screen130for viewing by the caregiver109. This notifies the caregiver109of the relevant parameters to monitor during the infusion as specified by the fluid order115.

Additionally, the fluid pump manager140initiates display of any other information on display screen (or plays back via audio) any guidance associated with infusing the recipient108in accordance with the fluid order115.

Thus, in one embodiment, via information on display screen130or other notifications provided by any suitable entity, the fluid management system110alerts a respective caregiver109during programming of the fluid pump120regarding the set of patient parameters (such as via notification132on the display screen130) to be monitored during delivery of the particular drug #2C to the recipient108. If desired, the respective caregiver109can review and/or select the parameters or corresponding settings of the parameters to be monitored via the algorithm170-2.

In further example embodiments, display of the parameters P2(such as blood saturation) and P5(such as heartbeat rate) notifies the respective caregiver109of the corresponding type of monitor equipment410to retrieve and attach to the recipient108for monitoring purposes.

In further example embodiments, display of the parameters P2(such as blood saturation) and P5(such as heartbeat rate) includes additional information indicating to the respective caregiver109of the expected update frequency for each of the monitored parameters. The update frequency indicates a schedule or timing in the monitor equipment is to provide sample data collected from monitoring each of the parameters P2, P5, etc.

In processing operation #7, the caregiver109sets up monitor equipment410in which to monitor the identified parameters P2and P5. For example, in one embodiment, the monitor410includes equipment to monitor multiple parameters such as heartbeat rate and blood oxygen saturation level.

In further example embodiments, the caregiver configures the monitor410, including any associated equipment as necessary, such that the update rate of the monitored parameters is aligned with the expected update frequency for each parameter.

FIG.5is an example diagram illustrating notification of availability of a report associated with delivery of a fluid according to embodiments herein.

In certain instances, it is useful to notify the caregiver109of any relevant information associated with delivery of the fluid102as specified by the fluid order115to the recipient108.

In further example embodiments, assume that the algorithm170-2or other suitable entity detects availability of pertinent medical information associated with the recipient108and the delivery of the fluid type2C to the recipient108.

In processing operation #8, in response to detecting the availability of pertinent information such as a relevant report associated with the recipient108and/or delivery of the fluid2C, the fluid pump manager140displays the notification510on the display screen130. The notification510inquires whether the caregiver109would like to know of the relevant report. In one embodiment, the relevant report indicates effects on the recipient108of infusing the recipient108with the fluid #2C or other fluid therapies in the past. This gives the caregiver109a sense of what may occur during the present infusion.

In one embodiment, the repository180-2stores one or more reports190(such as report190-1, report190-2, report190-3, etc.) regarding past delivery of different types of fluids to the recipient108and potentially to other recipients. The reports190can include any suitable information such as, in one embodiment, prior results (such as report190-3) of delivering the same fluid (type2C) or similar therapy to the recipient108.

If the caregiver109responds with a “yes” to notification510, then the fluid pump manager140queries the fluid management system110and corresponding repository180-2for any pertinent reports of delivering the fluid type #2C or any other type of infusions to the recipient108. In processing operation #9, via communications625, the fluid management system110communicates report190-3to the fluid pump manager140for display on the display screen130. Additionally, or alternatively, the report may be audibly played back to the caregiver109.

Thus, in one embodiment, the fluid management system110such as via executed algorithm170-2can be configured to detect relevant report190-3for communication to the caregiver109. Assume that the fluid management system110detects that the reports190stored in repository180-2include a report190-3indicating delivery of the fluid2C to the recipient108, medical information pertinent to delivery of the fluid order115to the recipient, etc.

Via communications625, the fluid management system110communicates the report190-3of prior infusion and/or other information relevant to the current infusion over network190and communication link127-1to the fluid pump manager140for display on the display screen130.

Thus, in one embodiment, via report190-3, the caregiver109can be notified of possible adverse effects (such as indicated by report190-3) prior to administration of the fluid order115to the recipient108. In view of the report190-3, the caregiver109has an option of terminating delivery of the fluid2C as specified by the order115if the report190-3indicates adverse effects on the recipient108. Alternatively, the report190-3may indicate no adverse effects on a prior delivery of the fluid2C to the recipient108.

FIG.6is an example diagram illustrating monitoring one or more parameters and providing corresponding feedback according to embodiments herein.

As further shown in this example embodiment, the monitor system410monitors the parameters P2and P5associated with the delivery of fluid102of fluid order115and communicates corresponding feedback175associated with same to the fluid management system110and, more specifically, the feedback analyzer113. The feedback analyzer113can be disposed at any suitable location. In one embodiment, as an alternative to being disposed in the fluid management system110, the feedback analyzer113and corresponding functionality is disposed in the fluid pump120.

If the fluid pump manager140executes the algorithm170-2(as opposed to the fluid management system110), the fluid management system110forwards the feedback175to the fluid pump manager140or the monitor equipment410can be configured to communicate the feedback175directly to the fluid pump manager140through the network190. Thus, the algorithm170-2can be executed at any suitable location such as the fluid management system110, fluid pump120, etc.

Note that further embodiments herein include the caregiver109or other suitable entity supplying appropriate information to the monitor equipment410to which the feedback175pertains. For example, the caregiver109can be configured to provide unique identifier information associated with the fluid pump120, recipient180, fluid order115, etc. The monitor equipment410uses the information to tag data associated with monitored parameters to the fluid management system110. This ensures that the fluid management system110is aware of a particular fluid delivery to which the feedback175pertains.

In further example embodiments, the feedback analyzer113receives the feedback175from the monitor equipment410prior to start of a respective infusion of the fluid order115. In response to receiving the feedback175, and a notification of the current settings of the parameters P2and P5, the feedback analyzer113or other suitable entity communicates a notification to the fluid pump120indicating the receipt of the feedback175from the monitor equipment410. The notification from the feedback analyzer113indicates (such as on display screen130, via an audio signal, etc.) that the feedback analyzer113currently receives the monitor information produces by the monitor equipment410and that the caregiver109can start the infusion because the feedback analyzer113is receiving the appropriate monitor data from the monitor equipment410.

In one embodiment, via operation #10, the monitor410communicates the feedback175(such as heartbeat rate, blood pressure, etc.) over a data stream via network190to the feedback analyzer113of fluid management system110.

The data stream includes the feedback175as well as information indicating identities such as the recipient108, fluid order115, fluid pump120, etc. The tagging of the feedback175with such information (such as unique identifier value UIVXY, identity of recipient108, etc.) enables the feedback analyzer113to generate, as the fluid order115is being delivered, an appropriate delivery report for storage in the repository180-2.

Note that, in further example embodiments, the monitor410further communicates time stamp information in or with the feedback175. The time stamp information indicates one or more different time slots or times to which the corresponding feedback175pertains.

In still further example embodiments, the fluid pump manager140also communicates feedback176to the fluid management system110(such as specifically to feedback analyzer113) during a respective infusion of the fluid type2C to the recipient108as specified by the fluid order115. As previously discussed, the feedback analyzer113of fluid management system110or other suitable entity executes the algorithm170-2to determine if the infusion (as specified by the fluid order115) should be terminated or if the caregiver109should be alerted based on feedback175(such as vital signs) and feedback176(such as fluid delivery information).

In yet another example embodiment, the feedback analyzer113of fluid management system110or other suitable entity executes the algorithm170-2to determine if the expected feedback parameter was not received within an expected time window and if the caregiver109should be alerted based on lack of feedback175(such as vital signs) or lack of feedback176(such as fluid delivery information).

Thus, during delivery of the particular fluid (such as type2C) as specified by the order115to the recipient108, the selected algorithm170-2executed by any suitable entity monitors feedback175associated with the status of the recipient108for each of the patient parameters P2and P5in the set as well as feedback176associated with the delivery.

In processing operation #11, the feedback analyzer113generates a respective report associated with the execution of the fluid order115and stores the report in repository180-2. The report indicates details of the infusion of fluid order115such as based on the feedback175and the feedback176.

The newly generated report based on the infusion of fluid order115serves as a history of infusing the recipient108with the fluid type2C. This information can be retrieved and reviewed if the caregiver109receives a subsequent order to deliver the same fluid therapy (such as fluid type2C) to the recipient108. Thus, each generated report potentially serves a basis in which to consider during future infusions to the recipient108.

A further example of communicating feedback data175and176to the feedback analyzer113and controlling operation of or providing notifications (such as alerts) associated with the delivery of the fluid order115is shown inFIG.7.

FIG.7is an example diagram illustrating receipt and processing of feedback according to embodiments herein.

In this example embodiment, the monitor equipment410communicates the feedback175to the feedback analyzer113. Additionally, the fluid pump manager140associated with fluid pump120communicates a status of the infusion to the feedback analyzer113such as executed by fluid management system110, fluid pump120, or other suitable entity.

As shown in this example embodiment, feedback175(such as a feedback data stream) includes feedback information175-1, feedback information175-2, . . . , feedback information175-8, and so on. Each of the monitor equipment410and the fluid pump manager140provide a continuous stream of feedback during the infusion into recipient108.

In one embodiment, the monitor equipment410generates each of the instances of feedback information (such as one or more data packets) to include data such as corresponding monitor data for a given sample period, a unique identifier value UIVXY assigned to the recipient108receiving a respective infusion, timing information such as time stamp information indicating a sample period to which the corresponding information pertains, etc. Accordingly, the feedback analyzer113is able to match the feedback175received from the monitor equipment410to the feedback176received from the fluid pump manager140.

As a more specific example, feedback information175-1from the monitor equipment410includes sample data (such as P2-MON-DATA1, P5-MON-DATA1) associated with each of the respective monitored parameters P2and P5assigned for monitoring during the delivery of fluid102associated with the fluid order115. The feedback information175-1further includes timing information indicating a time period, time sample, etc., indicating when the data was collected and/or generated by the monitor equipment410. The data775associated with the feedback175-1includes any suitable information (such as fluid pump identity, monitor equipment identity, fluid order identity, recipient identity, etc.) indicating that the feedback175-1is associated with the infusion of fluid2C as specified by the fluid order115.

Feedback information176-1from the fluid pump120or fluid pump manager140includes sample data (such as fluid delivery information785-1) associated with delivery of fluid102to the recipient108as specified by the fluid order115. In one embodiment, the fluid pump120keeps track of the amount, rate, etc., of fluid102(fluid type2C) delivered to the recipient108over time; the fluid delivery information785-1indicates data such as the amount, rate, etc., of fluid102(fluid type2C) delivered to the recipient108for a particular time slot. In further example embodiments, the feedback information176-1further includes timing information indicating a time period, time sample, etc., indicating when the data was collected and/or generated by the fluid pump120. The feedback information176-1includes any suitable information776(such as fluid pump identity, monitor equipment identity, fluid order identity, recipient identity, etc.) indicating that the fluid delivery information785-1is associated with the infusion of fluid2C as specified by the fluid order115.

Feedback information175-2from the monitor equipment410includes sample data (such as P2-MON-DATA2, P5-MON-DATA2) associated with each of the respective monitored parameters P2and P5assigned for monitoring during the delivery of fluid102associated with the fluid order115. The feedback information175-2further includes timing information indicating a time period, time sample, etc., indicating when the data was collected and/or generated by the monitor equipment410. The data775associated with the feedback175-2includes any suitable information (such as fluid pump identity, monitor equipment identity, fluid order identity, recipient identity, etc.) indicating that the feedback information175-2is associated with the infusion of fluid2C as specified by the fluid order115.

Feedback information176-2from the fluid pump120or fluid pump manager140includes sample data (such as fluid delivery information785-2) associated with delivery of fluid102to the recipient108as specified by the fluid order115. In one embodiment, the fluid pump120keeps track of the amount, rate, etc., of fluid102(fluid type2C) delivered to the recipient108over time; the fluid delivery information785-2indicates data such as the amount, rate, etc., of fluid102(fluid type2C) delivered to the recipient108. In further example embodiments, the feedback information176-2further includes timing information indicating a time period, time sample, etc., indicating when the data was collected and/or generated by the fluid pump120. Via information776, the feedback information176-2includes any suitable information (such as fluid pump identity, monitor equipment identity, fluid order identity, recipient identity, etc.) indicating that the fluid delivery information785-2is associated with the infusion of fluid2C as specified by the fluid order115.

FIG.8is an example diagram illustrating generation of a fluid delivery report based on feedback and generation of an alert notification associated with the fluid delivery according to embodiments herein.

As previously discussed, based on the feedback175, via the feedback analyzer113and execution of the algorithm170-2, the fluid management system110provides notifications and/or control associated with delivery of the fluid order115from the fluid pump120to the recipient108.

For example, as previously discussed, the feedback analyzer113executing the algorithm170-2can be configured to communicate one or more alerts to a caregiver109depending on the feedback175.

In yet further example embodiments, controlling delivery of the fluid102associated with fluid order115to the recipient via the algorithm171includes discontinuing delivery of the fluid102to the recipient (such as patient) in response to detecting an adverse impact of delivering fluid102to the recipient108as indicated by the feedback175.

An adverse impact can be detected in a suitable manner. For example, in one embodiment, as previously discussed, the feedback175indicates current detected settings of the monitored one or more parameter. The algorithm171compares the current setting of the monitored setting to a first threshold value associated with the parameter. In one embodiment, if the current setting (such as respiration rate) is above the first threshold value, the algorithm171discontinues delivering the fluid102to the recipient108and sounds an alarm (audio and/or visual) to the caregiver109.

In accordance with another embodiment, if the current setting of the monitored parameter (such as respiration rate) is below a respective second threshold value, the algorithm171discontinues delivering the fluid102to the recipient108and sounds an alarm (audio and/or visual) to the caregiver.

Accordingly, embodiments herein include modifying a delivery routine of delivering the particular fluid102to the recipient108based on comparison of the feedback175to corresponding one or more parameter threshold value settings associated with the algorithm170-2.

If desired, the caregiver109can modify the settings of the threshold values during an operation of programming the fluid pump120with algorithm170-2.

FIG.9is an example diagram illustrating monitoring of the feedback during delivery of a respective infusion according to embodiments herein.

In this example embodiment, the graph991includes signal901derived from feedback176and corresponding fluid delivery information785(such as fluid delivery information785-1,785-2, etc.). Signal901generated by the feedback analyzer113or other suitable entity represents a progress of the delivering fluid102as indicated by the fluid order115over time. In other words, signal901indicates a percentage of completing the respective infusion (fluid order115) over time as indicated by the feedback176.

In further example embodiments, note that the monitor equipment410, fluid pump120, and the fluid management system110are synchronized to the same clock such that the feedback analyzer113is able to correlate the received infusion data from fluid pump120to the settings of monitored parameters P2and P5.

Further in this example embodiment, based on the received feedback175and corresponding parameter P2monitor data provided by the monitor equipment410, the feedback analyzer113produces/tracks P2-signal910in graph992. In one embodiment, the P2-signal910represents a blood oxygen level associated with the recipient108over time during the infusion. The feedback analyzer113tracks and compares P2-signal910(as derived from P2-MON-DATA in feedback175) indicating the blood oxygen level associated with monitored parameter P2of recipient108to the P2-threshold level. In response to detecting that the signal910falls below the P2-threshold level as implemented by the algorithm170-2between T5and T6(such as at around time T5A), the feedback analyzer113generates a respective first alert (ALERT #1) to the caregiver109such as via communications over network190and display of a respective message on the display screen130or audio alert indicating that the blood oxygen level of the recipient108has fallen below the P2-threshold level during infusion. The caregiver109may decide to discontinue the infusion based on the received alert.

Further in this example embodiment, based on the received feedback175and corresponding P5monitor data, the feedback analyzer113produces P5-signal in graph993. The P5-signal represents a heartbeat rate (pulse) associated with the recipient108over time during the infusion. The feedback analyzer113tracks and compares P5-signal920(as derived from P5-MON-DATA) indicating heartbeat rate (pulse) associated with monitored parameter P5of recipient108to threshold level P5-threshold level. In response to detecting that the signal920raises above the P5-threshold level (such as90beats per minute) as implemented by the algorithm170-2between T7and T8(such as at time T7A), the feedback analyzer113generates a respective second alert (ALERT #2) to the caregiver109such as via display of a respective message on the display screen130or audible alert indicating that the blood oxygen level of monitor P2has fallen below the P2-threshold level. The caregiver109may decide to discontinue the infusion based on the received alerts.

Assume in this example embodiment that, at or around time T8, the caregiver109discontinues delivery of the infusion as indicated by the fluid order115in response to receiving the multiple alerts.

In further example embodiments, note that the feedback analyzer113can be configured to generate a respective control command in response to detecting one or more alerts (such as ALERT #1and/or ALERT #2). In one embodiment, the command communicated to the fluid pump120terminates delivery of the infusion as specified by the fluid order115.

FIG.10is an example block diagram of a computer device for implementing any of the operations as discussed herein according to embodiments herein.

In one embodiment, fluid management system110includes one or more computer systems similar to computer system1050to execute management application/process associated with the fluid management system110, fluid pump manager140, etc. As shown, computer system1050of the present example includes an interconnect1011, a processor1013(such as one or more processor devices, computer processor hardware, etc.), computer readable storage medium1012(such as hardware storage to store data), I/O interface1014, and communications interface1017.

Interconnect1011provides connectivity amongst processor1013, computer readable storage media1012, I/O interface1014, and communication interface1017. I/O interface1014provides connectivity to a repository1080and, if present, other devices such as a playback device, display screen, input resource1092, a computer mouse, etc.

Computer readable storage medium1012(such as a non-transitory hardware medium) can be any hardware storage resource or device such as memory, optical storage, hard drive, rotating disk, etc. In one embodiment, the computer readable storage medium1012stores instructions executed by processor1013.

Communications interface1017enables the computer system1050and processor1013to communicate over a resource such as network190to retrieve information from remote sources and communicate with other computers. I/O interface1014enables processor1013to retrieve stored information from repository1080.

As shown, computer readable storage media1012is encoded with controller application140-1(e.g., software, firmware, etc.) executed by processor1013. Management application140-1can be configured to include instructions to implement any of the operations as discussed herein.

During operation of one embodiment, processor1013(e.g., computer processor hardware) accesses computer readable storage media1012via the use of interconnect1011in order to launch, run, execute, interpret or otherwise perform the instructions in management application140-1stored on computer readable storage medium1012.

Execution of the management application140-1produces processing functionality such as management process140-2in processor1013. In other words, the management process140-2associated with processor1013represents one or more aspects of executing management application140-1within or upon the processor1013in the computer system1050.

Those skilled in the art will understand that the computer system1050can include other processes and/or software and hardware components, such as an operating system that controls allocation and use of hardware resources to execute management application140-1.

In accordance with different embodiments, note that computer system may be any of various types of devices, including, but not limited to, a wireless access point, a mobile computer, a personal computer system, a wireless device, base station, phone device, desktop computer, laptop, notebook, netbook computer, mainframe computer system, handheld computer, workstation, network computer, application server, storage device, a consumer electronics device such as a camera, camcorder, set top box, mobile device, video game console, handheld video game device, a peripheral device such as a switch, modem, router, or in general any type of computing or electronic device. In one non-limiting example embodiment, the computer system1050resides in fluid delivery system100. However, note that computer system1050may reside at any location or can be included in any suitable one or more resources in network environment to implement functionality as discussed herein.

Functionality supported by the different resources will now be discussed via flowcharts inFIG.11. Note that the steps in the flowcharts below can be executed in any suitable order.

FIG.11is a flowchart1100illustrating an example method according to embodiments. Note that there will be some overlap with respect to concepts as discussed above.

In processing operation1110, the fluid management system110receives input such as a fluid order115indicating a fluid therapy of a particular type to be delivered to a recipient108.

In processing operation1120, the fluid management system110maps the particular type of the fluid (such as particular fluid type2C) to a set of patient parameters (P2and P5) to be monitored during delivery of the fluid102(fluid of particular type2C) to the recipient108.

In processing operation1130, during delivery of the particular fluid typical2C to the recipient108, the fluid management system110monitors feedback175from the recipient108for each of the patient parameters P2and P5in the set.

In processing operation1140, based on the feedback175, the fluid management system110controls delivery of the particular type of fluid2C (fluid102) to the recipient108.

Note again that techniques herein are well suited for use in management of fluid delivery systems. However, it should be noted that embodiments herein are not limited to use in such applications and that the techniques discussed herein are well suited for other applications as well.

Based on the description set forth herein, numerous specific details have been set forth to provide a thorough understanding of claimed subject matter. However, it will be understood by those skilled in the art that claimed subject matter may be practiced without these specific details. In other instances, methods, apparatuses, systems, etc., that would be known by one of ordinary skill have not been described in detail so as not to obscure claimed subject matter. Some portions of the detailed description have been presented in terms of algorithms or symbolic representations of operations on data bits or binary digital signals stored within a computing system memory, such as a computer memory. These algorithmic descriptions or representations are examples of techniques used by those of ordinary skill in the data processing arts to convey the substance of their work to others skilled in the art. An algorithm as described herein, and generally, is considered to be a self-consistent sequence of operations or similar processing leading to a desired result. In this context, operations or processing involve physical manipulation of physical quantities. Typically, although not necessarily, such quantities may take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared or otherwise manipulated. It has been convenient at times, principally for reasons of common usage, to refer to such signals as bits, data, values, elements, symbols, characters, terms, numbers, numerals or the like. It should be understood, however, that all of these and similar terms are to be associated with appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, as apparent from the following discussion, it is appreciated that throughout this specification discussions utilizing terms such as “processing,” “computing,” “calculating,” “determining” or the like refer to actions or processes of a computing platform, such as a computer or a similar electronic computing device, that manipulates or transforms data represented as physical electronic or magnetic quantities within memories, registers, or other information storage devices, transmission devices, or display devices of the computing platform.

While this invention has been particularly shown and described with references to preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present application as defined by the appended claims. Such variations are intended to be covered by the scope of this present application. As such, the foregoing description of embodiments of the present application is not intended to be limiting. Rather, any limitations to the invention are presented in the following claims.