CN1692366A - Patient medical fluid parameter data processing system - Google Patents

Abstract

A system extrapolates or interpolates patient fluid intake or output parameter values and associated cumulative values over variable time intervals from a reduced set of stored fluid parameter values that affect fluid cumulative volume calculations or fluid intake or output rate calculations. The extrapolation and interpolation functions are applicable to both a drip (continuous) fluid dose and a supplemental (non-continuous, e.g., bolus) fluid dose. A patient medical parameter data processing system provides patient medical parameter data for trend indicative display containing time periods including user selectable patient parameter acquisition time intervals. The system includes an acquisition processor for receiving data identifying, for a continuing infusion, a rate of volume of fluid infusion into a patient, a fluid type identifier, and a start time and start date of said continuing infusion. Further, for a non-continuing infusion, the received data identifies a total volume of fluid infusion, a fluid type identifier, and a time and date of the non-continuing infusion. The data processor determines from the received data a cumulative total volume infusion of a particular fluid into a particular patient over a particular user selectable patient parameter acquisition time interval.

Description

Patient medical fluid parameter data processing system

This is the official application of the provisional application Serial No. 60/413,033 filed September 2, 2002 by A. Alpert.

field of invention

The present invention relates to the processing and display of patient medical information in a network environment, and in particular to assisting in the storage, retrieval and processing of data pertaining to fluid intake and discharge calculations and displays.

Background of the invention

Patient medical parameter data is acquired, organized, stored, and displayed for use in providing clinical patient care in hospitals, clinics, and other healthcare settings. Patient medical parameter data may include vital sign ventilator information, infusion pump data regarding fluid delivery, and other data. The patient medical parameter data is typically displayed on the screen of the patient monitoring device in the form of a trend indicating graph with a time axis. This type of graph is often called a flow graph. Patient monitoring devices are typically located at the patient's bedside or nursing station in a hospital ward or intensive care unit, surgical ward, or other setting, and may be connected to a network, such as the Internet, LAN, WAN, or intranet, for access from local sources such as , sensors attached to the patient) or a remote source (eg, a remotely stored electronic patient record) acquires patient parameter data. The flow diagram is an electronic sequential diagram of patient parameter information that replaces the paper-based flow diagram of vital signs.

What is needed is an electronic flow diagram that provides similar or better features and flexibility than the paper flow diagram it replaces. Therefore, electronic flow charts need to enable healthcare professionals to acquire and record parameters related to patient fluid intake and expulsion, including infusion pump data and other information related to fluid delivery. Known systems typically acquire, organize and store fluid-related patient medical parameter data for display in flow charts along with a time axis during corresponding parameter acquisition time intervals. To this end, known systems acquire and store large amounts of patient medical parameter data over a relatively long period of time (eg, the duration of a patient's hospital stay) for relatively short stream image acquisition intervals (eg, 3 minutes to several hours) for display. Typically, at least one patient parameter value is acquired for each acquisition time interval. This leads to the acquisition of a large data set containing redundant data, which requires the allocation of a correspondingly large amount of memory. Additionally, the acquired fluid uptake or outflow data values are used to calculate and display cumulative patient fluid uptake and outflow values. Therefore, if the previously recorded fluid uptake or outflow data values used in this calculation change, a series of subsequent calculated fluid accumulation values for the flow graph display need to be recalculated and updated. Changes in this previous fluid intake or outflow data value occur in response to, for example, a user, such as a nurse, administering a fluid medication and manually logging in a corresponding fluid uptake or outflow value that includes the existing value. The large amount of data involved increases the difficulty involved in recalculating the cumulative uptake or expulsion of fluid over a period of time (or updating the cumulative value over an independent parameter acquisition interval). A system in accordance with the principles of the present invention addresses these and derivative problems.

Summary of the invention

A system extrapolates or interpolates patient fluid intake or discharge parameter values and associated cumulative values over variable time intervals from a reduced set of stored fluid parameter values that affect fluid cumulative usage calculations or fluid intake or discharge rate calculations. This extrapolation and interpolation function applies to drip (continuous) fluid dosages as well as supplemental (discontinuous, eg bolus) fluid dosages. A patient medical parameter data processing system provides patient medical parameter data for a trend indicating display comprising a time period including a user selectable patient parameter acquisition time interval. The system includes an acquisition processor for receiving data identifying, for a continuous infusion, a fluid infusion rate into the patient, a fluid type identifier, and a start time and start date of the continuous infusion. Also, for a discontinuous infusion, the received data identifies the total amount of fluid infused, the fluid type identifier, and the time and date of the discontinuous infusion. A data processor determines from the received data a cumulative total infusion of a particular fluid into a particular patient during a particular user-selectable patient parameter acquisition time interval.

Brief description of the drawings

In the attached picture:

1 is a block diagram of a communication network with various devices including a system for storing a reduced set of fluid parameter values in accordance with the principles of the present invention.

Fig. 2 depicts a flowchart of a method for deriving fluid intake or excretion parameter values and associated cumulative values over variable time intervals from a reduced data set, in accordance with the principles of the present invention.

3 depicts a flowchart of a method for providing a user interface display of fluid intake or expulsion parameter values and associated cumulative values over variable time intervals from a reduced data set, in accordance with the principles of the present invention.

4-10 illustrate user interface display images presenting resulting fluid patient intake usage, cumulative usage, and net fluid balance values over variable time intervals in accordance with the principles of the present invention.

Figure 11 is a block diagram of a server with functionality in accordance with the principles of the invention.

Detailed description of the invention

A system and user interface calculates and displays flow graph trends indicative of patient fluid input and drain data, cumulative fluid information, and identifying net fluid intake or net drain fluid usage over a user-selectable variable time period The data. The system advantageously stores a reduced set of fluid parameter values that affect calculations of cumulative fluid usage or calculations of fluid uptake rates or outflow rates, and to the exclusion of other data. Fluid usage data is dynamically calculated from the reduced data set in response to a command to display a trending flow graph display (including fluid usage data), ie, at display generation runtime. As a result, the user changes or alters the value of past data points in the reduced data (eg, replaces the value of a data point with a value determined to be more accurate) without causing a series of subsequent changes in stored data values. The fluid usage data is dynamically extrapolated and interpolated from the reduced data set for display using a predetermined algorithm in response to a user command to begin display generation. This advantageously eliminates the need to store redundant intermediate fluid usage data values that are insignificant for patient fluid cumulative usage calculations or fluid intake or drainage rate calculations. Dynamic extrapolation and interpolation of usage data prior to flow graph usage data display also eliminates the need to update a large series of stored fluid usage data values in response to user changes to previous fluid usage data values. The system advantageously avoids storing and modifying large amounts of fluid usage data, and supports extrapolation and interpolation of intermediate fluid usage data values for display during user-selectable flow graph acquisition intervals without requiring updates to stored The fluid parameter data set of .

Known flow chart display systems typically establish a minimum time interval for which patient parameters are acquired (Patient Parameter Acquisition Interval) and store data points for each time interval. This results in onerous accumulation, storage, maintenance and processing of large amounts of patient parameter data. Furthermore, in this known system, if the user modifies a previously acquired data value (e.g., fluid usage value) associated with a particular acquisition time interval, a series of subsequent consecutive data values (e.g., cumulative usage value) need to be updated. or net balance data) to reflect the modification. In contrast, a system according to the principles of the present invention extrapolates or interpolates patient fluid uptake or outflow parameter values at variable time intervals and associated Cumulative value. The system advantageously extrapolates and interpolates fluid usage over a user-selectable variable time period using a reduced data set that includes identifying fluid type, changes in fluid usage intake and discharge rates, and replenishment fluid usage (e.g., one-time, non-continuous, supplemental infusion boluses) and associated time-of-occurrence data. Thus, the reduced data set advantageously only stores data on fluid usage intake and discharge rates, changes in usage, and associated identification times when changes occur. Furthermore, the system generates run-time extrapolation and interpolation of new usage data at the display based on the reduced data set, whereby the system readily adapts to changes in historical fluid data values and time periods without involving a series of historically interacting Heavy recalculation and updating of dependent data values. Extrapolation and interpolation of the fluid data is performed using an algorithm and a database incorporating the reduced dataset, and a compatible database interface.

1 is an exemplary block diagram of a communications network incorporating a server 20 hosting an executable application 19 that provides a trend-indicating user interface display (referred to as a flow graph) of patient parameters that Parameters include the identified acquisition interval. Flowgrams can display different types of parameters related to, for example, intravenous fluids, drip-administered medications, blood products, blood pressure, ventilation, vital signs, blood oxygen concentration, and infusion pump fluid delivery. Specific parameters contain different pieces of data that are important to describe a specific fluid. Also, hospitals typically use different practices regarding the data included for each parameter and the manner in which that data is displayed. The system executed by the application 19 advantageously stores a reduced set of fluid parameter data for use in display generation run time, calculation and display of stream maps over user-selectable variable time periods patient fluid input and output data, accumulated Fluid information and data identifying net input or net drain fluid balance usage.

In an alternative embodiment, the executable application providing the flow graph user interface may reside on another processing device in any part of the network shown in FIG. 1 . The communication network 1 (FIG. 1) is represented by an IP (Internet Protocol) compliant network having a hierarchy of local area networks and wide area networks interconnected together. It should be noted that although the exemplary hospital or medical network is an IP compatible network, other types of networks that use other computing protocols such as, for example but not limited to, X.25, Frame Relay, IBM SNA, etc., such as but It is not limited to an optical network or a wireless network, as is readily understood by those skilled in the art. Furthermore, although the exemplary network described is a hierarchical network, this is not a requirement of the present invention. Any type of network architecture that provides a communication link between devices over a network may be used.

As shown in FIG. 1 , the first level of an exemplary hierarchical network 1 includes a medical interface bus (MIB) 2 . MIB is a well-known medical industry standard for connecting medical devices together in a local fashion. As shown in Figure 1, MIB 2 is typically used to interconnect medical equipment in a nursing ward (such as a patient room in a nursing station), to manage the care of a particular patient, and to monitor that particular patient. A variety of medical devices can be connected via the MIB 2; examples shown in FIG. The MIB 2 is typically connected to a secondary LAN network 3 via an interface docking station (IDS) device 12 for interfacing to an Ethernet-compatible LAN network 3. LAN3 may be, for example, a wireless LAN commercially available from Siemens Medical System. Depending on the size of the institution, this higher level LAN 3 is typically, though not necessarily, used by other care units, such as specific departments in a hospital, such as intensive care units or surgery units, among others.

Although not shown in Figure 1, more than one MIB can be connected to the second level LAN 3, whereby more than one patient can be monitored or provided with care via the LAN 3. In addition, medical devices can be connected directly to a higher-level LAN 3 . For example, as shown in FIG. 1, the ventilator 6b and the anesthesia system 22 are directly connected to the LAN 3 without using the MIB. Furthermore, the LAN 3 can be interconnected to the hospital LAN backbone 4 which is also Ethernet compatible. The backbone network 4 provides communication connections between various departments in a hospital or a medical institution; for example, it connects a hospital management system 15 with a laboratory system 17 . In addition, the hospital LAN 4 has a remote access gateway 11 that provides remote, secure access to various systems and devices in the network 1 from, for example, a remote doctor's office 23 or a remote care location 24 via, for example, the Internet 29. Alternatively, the remote site may also directly access the remote access gateway 19 through, for example, a dial-up telephone port, ADSL, or other type of dedicated connection. As known in the art, the remote access gateway 11 may also be a part of the server 20 to be described below, rather than exist independently.

According to the principles of the present invention, executable application program 19 (or a plurality of application programs in another embodiment) resides on the central server on LAN 3, is used for collecting and processing from peripheral medical device or is connected to LAN 3 or Data of the facilities of the hospital LAN 4, these data include, for example, laboratory results provided by the laboratory system 17 connected through the HL7 interface. Using, for example, ASTM messaging, server 20 may obtain additional medical parameter data, including additional laboratory results obtained from any number of medical devices, such as the medical device shown in FIG. 1 . The retrieved medical parameters related to a given patient, including laboratory test results, are retrieved from medical devices on the network 1 for any of the monitors 5a, 5b or PCs 26 and 39 or at any level of the network of FIG. Display and control on other display host devices. Those skilled in the art can readily recognize that since all the different levels of LANs (e.g., 3 or 4), and the remote sites in FIG. 1 are interconnected, server 20 can reside on any level of network 1 . An example of server 20 is the Chart Assist server commercially available from Siemens Medical System. The server may host a computer system such as a Microsoft Windows operating system. The application 19 provides a user interface trending display (flow graph) of patient parameters comprising time periods including user selectable acquisition intervals. The user-selectable acquisition time intervals represented by the columns in the flow diagram encompass the time period during which the patient parameters are acquired (typically 3 minutes to 4 hours or another user-selectable time interval).

FIG. 2 shows the functions performed by the executable application program 19 in the form of a flowchart. After starting at step 201, as shown in step 202, the application 19 establishes communication with a device on the network. This is accomplished, for example, using the IP protocol and the known IP device addresses for each device on the network 1 (FIG. 1), in combination with any higher application layer protocols, as is known in the art. Once the communication between the server 20 and the other devices is established, in step 204 the application 19 begins to acquire the parameters being monitored, laboratory results and settings selected for the various devices. As mentioned earlier, laboratory results can be obtained through the HL7 interface with LIS17, or through ASTM or MIB point of care (POC) medical devices as shown in Figure 1. Fluids and other parameters can also be obtained through the user data entry. Types of monitored patient parameters acquired include blood pressure parameters, respiration or ventilation parameters, vital sign parameters, blood oxygen concentration indicative parameters, infusion pump parameters for fluid delivery, continuous infusion drip related parameters, non-continuous bolus Infusion-related parameters and other fluid-related parameters.

Medical data and laboratory results may be acquired continuously, periodically, or aperiodically, and may be associated with a given patient for storage in a relational database 25 in the server 20 . The database 25 may be of a type for storing related data, such as Microsoft SQL Server. Additionally, the application 19 may obtain patient parameter data and patient data including medical laboratory results first logged and stored in, for example, the laboratory system 17 of FIG. 1 . Also, the application 19 may retrieve the healthcare provider's registered medical records for display. In step 206, the application 19 identifies and stores a reduced set of acquired fluid-related patient parameter data that affects fluid intake or discharge rate calculations or fluid cumulative usage calculations and does not include Calculation of unrelated fluid parameter data. For continuous infusion, the reduced fluid-related patient parameter data set includes: fluid infusion rate into the patient, fluid type identifier, and start time and start date of the continuous infusion. Similarly, for a non-continuous infusion (eg, supplemental bolus infusion volume), the reduced data set includes: total fluid infusion volume, fluid type identifier, and time and date of the non-continuous infusion. In step 210, the application 19 uses the reduced data set (by interpolation and extrapolation) to determine the fluid volume infusions, cumulative total volume infusions, and net fluid volume infusions for a particular fluid into that particular patient over a particular user-selected time period. Infusing fluid balance, the time period includes one or more user-selectable patient parameter acquisition time intervals. User-selected time periods can include: minutes, one hour, time intervals of hours, one day, and one work shift period. Also, in another embodiment, the application 19 also interpolates or extrapolates the usage infusion rate.

In step 210 , the application 19 determines fluid usage related data using an extrapolation and interpolation algorithm using input data including the continuous infusion fluid data and the non-continuous infusion fluid data of the reduced data set stored in step 206 . An exemplary algorithm is as follows. In this algorithm, the input value for continuous infusion is the rate of fluid infusion volume into the patient, and the input value for discontinuous infusion (replenishment or bolus infusion volume) is the value of the total fluid infusion volume. Also, in this algorithm, the input value time is the time at which the input value (fluid infusion rate value or fluid infusion total amount value) is entered. Set the fluid infusion rate at a specific time, for example, 1000 cc of saline at a rate of 250 cc/hr starting on February 12, 2002 at 11:00 AM. The amount of fluid used for supplements or boluses into or out of the patient is also associated with a specific infusion or outflow time, for example, a 100cc drug injection at 11:00 am on February 13, 2002, or a 10:00 recorded emptying of 1000cc of fluid out of container. Also, fluid discharge rates are indicated by negative rates. The algorithm stores the non-continuous infusion total usage value separately from the continuous dosage infusion value obtained using the usage rate data so that these different items can be displayed separately in different display modes.

algorithm:

Initially, the current infusion volume and volume infusion rate are zero (eg, corresponding to the beginning of the patient's hospital stay).

For each input value (from the first to the last in the time period for which fluid usage data will be calculated)

if the input value is in the current time interval then

Calculate usage for the interval up to the input time using the current rate

Add the usage to the total usage for the interval

if the input has a rate change

Make this input rate the current rate

end if

if the input has a pill size

Add that bolus amount to the amount for that interval

end if

else if the input value time is after the current interval

Use the current rate to calculate usage about the current interval to the end of the interval

Add this amount to the total usage for that interval

while the input value time is after the current interval

Increment current interval (and output to display buffer)

Use the current rate to calculate usage for the interval

Store usage for that interval

end while

Use the current rate to calculate usage for the current interval up to this input time

Add the usage to the total usage for the interval

if the input has a rate change

Make this input rate the current rate

end if

if the input has a pill size

Add that bolus amount to the amount for that interval

end if

end if

next input value

end of algorithm

The application 19 uses this algorithm to create cumulative fluid infusion (and drain) usage data and inflow (and outflow) of fluids for a user-selectable period of time (such as the entire patient's hospital stay) including one or more parameter capture intervals. ) net balance data for fluid infusion of fluid. The algorithm processes data in a reduced dataset accumulated for independent parameter acquisition time intervals (eg, one hour). The algorithm uses, for example, a change in fluid infusion or drain rate or a change in input or drain dosage over the time period of the hospitalization under examination, and the time of the change. In step 212 (FIG. 2), the user further selects a portion of the created data for display and inspection in selectable display modes. Specifically, in step 212, the application 19 begins generating data representing a flow graph image showing a trend indicating display and indicating the fluid dosage infusion, infusion, and flow of a particular fluid into a particular patient for a user-selected portion of time. Cumulative gross infusion and net infusion fluid balances.

In response to user selection of a second time period comprising one or more acquisition time intervals, in steps 210 and 212, the application 19 uses the reduced data set to automatically determine and display the time period for entering a particular patient during the second time period. Another infusion volume, cumulative gross infusion, and net balance infusion of the specified fluid. The user can use a Microsoft Windows compatible PC 26 as shown in Figure 1 or a Windows NT compatible PC 39, or any other processing device capable of running a menu generating program such as a web browser program (such as Microsoft Internet Explorer or Netscape Navigator, etc.), with to view flow charts, medical parameters, and laboratory result information associated with a given patient. That is, as long as a communication connection to the server 20 and the application 19 is established, the user can use a web browser on any processing device to make a request and view the information acquired and stored in the database 25 . This is advantageous because, for example, a physician can obtain access to flow charts or laboratory test results, eg, from a remote physician's office 23, without having to access a dedicated terminal. Of course, the user may simply use the keyboard and/or mouse or any other user interface device to select or require the user to log on to the user's computer, as is known in the art. The application 19 is thus able to organize and format the medical data to be compatible with eg HTML (Hypertext Markup Language) programming language for displaying the data on a web browser. The application 19 also responds to eg HTTP (Hypertext Transfer Protocol) commands originating from the user's web browser to make requests. The process of FIG. 2 ends at step 214 .

3 depicts a flowchart of a method for providing a user interface to present derived fluid patient parameters. After starting in step 221, in step 223 the application 19 receives flow chart configuration and user login data identifying the fluid parameters to be displayed, the display mode and the time period for displaying the selected fluid parameters. The application 19 obtains fluid usage data, cumulative gross infusion data, and net balance infusion usage data for a particular fluid into a particular patient in response to receiving the data. In step 225, the application 19 begins generating data representative of at least one displayed image showing the resulting dosage data, cumulative total dosage infusion data, or A trend indicator for net balance infusion usage data is displayed. Specifically, the application program 19 starts generating data representing FIGS. 4-10.

The display image of FIG. 4 shows the patient's total fluid input and output volume 403 and fluid rate 407 in various hours (parameter acquisition time intervals) over a period of time (01:00 to 08:00, item 405). The application 19 counts fluid usage at 1 minute intervals. The display image of FIG. 5 shows patient net (input minus drain) fluid balance usage 410 accumulated hourly 410 , per work shift period 413 , and daily 415 and presented over a period of time ( 23:00 to 09:00, Item 417) in the separate hourly parameter Get Time Interval column. The application 19 counts fluid usage at 1 minute intervals. Presentation of the cumulative fluid balance in a graphical format, eg, the cumulative net fluid balance by hour in window portion 420, advantageously enables a clinician to perform an expedited assessment of the patient's fluid status.

6-10 illustrate a series of flow graph display images illustrating user editing of the fluid input rate and the resulting recalculation of the cumulative total fluid usage, and updating of the display image to reflect the recalculated value. FIG. 6 shows a flow graph display image indicating fluid dosage 425 , fluid input rate 428 and fluid usage 430 for a drug drug determined at hourly intervals. Figure 7 shows a flow graph display image indicating the net fluid usage input per hour 433, per work shift time period 436 and per day 439 and per hour 441, Net fluid input balance per work shift time period 443 and per day 445 . Figures 9 and 10 show flow graph display images corresponding to the images of Figures 6 and 7, respectively, but including fluid data recalculated according to user-altered fluid dose and fluid input rate data. Specifically, FIG. 9 shows that fluid dose 480, fluid input rate 483, and fluid usage are indicated in accordance with recalculation of fluid data in response to changes in fluid dose, rate, and usage that occurred during the intermediate time interval (08:00). The flow graph of Figure 6 shows 485 images. Similarly, FIG. 10 shows the flow graph display image of FIG. 9 following a recalculation of fluid data in response to a change in fluid input rate occurring in an intermediate time interval (09:00). Specifically, FIG. 10 indicates the recalculated net fluid usage inputs per hour 491 , per work shift time period 493 , and daily 495 and hourly 497 , per work shift time period for IV medications determined at hourly intervals. Net fluid input balance for periods 499 and 501 per day. Also, the user begins generating menu 459 of FIG. 8 to log in or modify fluid data identifying the fluid in item 467 and to accept or cancel the entry using menu bar 470 . In particular, the menu 459 is used to modify or register the fluid input or output rate 463 , the fluid input or output amount 465 and the dosage 460 .

In step 225 (FIG. 3), the application 19, responsive to the display mode selected in step 223, begins generating data representing a flow graph display image of the fluid parameter (eg, as illustrated in FIG. 4). The fluid flow map images of Figures 4 and 5 illustrate different display images. In a different display mode, the application 19 generates a fluid flow diagram incorporating two columns. The first column shows the time (representing the relevant time interval), while the second column shows the accumulated fluid usage during the corresponding time interval. The fluid usage value is calculated from the flow rate of fluid input or output. In this display mode, discrete supplemental (bolus) fluid usage is not considered. Individual time intervals are presented in separate flow graph rows, and fluid usage values for individual time intervals are not included in the accumulation of fluid usage values for subsequent time intervals.

In a different display mode, the application 19 generates a fluid flow diagram incorporating three columns. The first column includes time values representing time intervals (e.g., hourly intervals), the second column represents the total fluid usage accumulated over the corresponding time interval, and the third column (called the parameter instance) identifies the fluids involved. Dosage values are calculated from fluid input or output flow rates and from discrete make-up (bolus) fluid usage. The individual time intervals are presented in a single flow graph row, and the fluid usage values for the individual time intervals contribute to the accumulation of fluid usage values for subsequent time intervals, whereby the fluid usage values are cumulative. An additional stream graph column has been added to the alternate shift display mode to show the accumulated fluid usage over the duration of the work shift at the facility. The duration and start time of the work shift time period are configurable by the user. During work shifts, fluid usage rolls up in a similar way to time intervals (e.g., hourly usage), but at the end of the shift, the fluid rollup value is reset to zero, and the new shift's first Hours have cumulative fluid usage for a single hour. Similarly, in another display mode (the Days display mode), an additional flow graph row is added to show the accumulated fluid usage over a separate 24-hour period, with each new day's The first hour has a single hour cumulative fluid usage. The process of FIG. 3 ends at step 231 .

FIG. 11 shows a block diagram of an exemplary embodiment of a server 20 ( FIG. 1 ) for generating data for configuring and presenting flow graph trend indication displays, and for managing, Organize, search and update databases 25 containing patient medical information. The executable application program and processor operative to execute instructions for implementing the various functions described herein include: an executable application program 19 for performing flow graph related processing; and a communication processing module 2502 obtained from Patient data of monitoring parameters assigned to a given patient are collected and this information collated for storage in database 25 . The navigation organization processor 2504 operates in conjunction with the web browser and display builder software to organize and prioritize parameters for display to the user when navigating through the selection of various applications by the user via the user interface. The name server processor 2506 associates a unique identifier (ID) with each node connected to the system network and each patient in the system in order to track and update patient information throughout the system. Input/output data and control signals are used for communication between the various processors, also for interfacing with database 25 and search engine 23, and for interfacing with the network via communication line 2510.

The fluid data export and display systems, images and processes presented in Figures 1-11 are not exclusive. Other display images, systems and processes are available in accordance with the principles of the present invention to achieve the same goals. Although the invention has been described with reference to specific embodiments, it should be understood that the embodiments and variations shown and described herein are for illustration purposes only and can be appreciated by those skilled in the art without departing from the scope of the invention. Various modifications are possible. The data extrapolation and interpolation system can be extended to other applications that store heavy parameter data volumes.

Claims (22)

1. A patient medical parameter data processing system for providing patient medical parameter data for trend indication display, the trend indication display includes a time period including a user-selectable patient parameter acquisition time interval, the system comprising: an acquisition processor for receiving data that identifies, For continuous infusion, (a) the rate of fluid infusion volume into the patient, the fluid type identifier, and the start time and start date of said continuous infusion, and For discontinuous infusions, (b) the total amount of fluid infused, the fluid type identifier, and the time and date of the discrete infusion; and A data processor for determining, from said received data, a cumulative total infusion of a particular fluid into a particular patient during a particular user-selectable patient parameter acquisition time interval. 2. The data processing system of claim 1, comprising a generator for generating data representing an image showing a trend-indicating display of at least one of: (a) fluid usage infusion, (b) net balance of fluid infusion, and (c) access to said particular patient The cumulative total amount of the specific fluid infused. 3. The data processing system of claim 1, wherein responsive to user selection of a second acquisition time interval different from said particular user-selectable acquisition time interval, The data processor automatically determines from the received data another cumulative total infusion of the particular fluid into the particular patient during the second acquisition time interval. 4. The data processing system of claim 1, wherein The data processor automatically determines from the received data a cumulative total infusion of the particular fluid into the particular patient over a time period comprising a plurality of user selectable patient parameter acquisition intervals. 5. The data processing system of claim 1, wherein Responsive to user commands and data entry, for said particular fluid and said particular patient, the entry data includes: dosage infusion data values, fluid identifiers, and at least one of (i) continuous dosage into the patient the rate of fluid infusion, and the start time and date of start of said continuous dose of fluid infusion, and (ii) the total discrete dose of fluid infusion, and the time and date of said discrete dose of fluid infusion, The data processor uses the log data for determining a cumulative total infusion of the particular fluid into the particular patient during a particular user-selectable patient parameter acquisition time interval. 6. The data processing system of claim 1, wherein The data processor stores the received data comprising a reduced set of fluid parameter data affecting the fluid cumulative usage calculation and excluding storage of fluid parameter data not relevant to the fluid cumulative usage calculation. 7. The data processing system of claim 6, wherein The reduced set of fluid parameter data contributes to fluid uptake or outflow rate calculations and does not include fluid parameter data not relevant to fluid uptake or outflow rate calculations. 8. The data processing system of claim 1, wherein The data processor determines a cumulative total infusion of a particular fluid into a particular patient over a time period comprising a plurality of user-selectable patient parameter acquisition intervals. 9. The data processing system of claim 1, wherein the data processor uses the received data to interpolate at least one of the following, of a specific fluid entering a specific patient at a specific time (a) Cumulative Total Infusion, and (b) Fluid infusion rate. 10. The data processing system of claim 1, wherein The continuous infusion comprises at least one of (a) drip drug fluid infusion and (b) constant rate pump fluid infusion, and The discontinuous infusion comprises at least one of (i) bolus, (ii) fluid infusion by injection and (iii) a single manually administered fluid infusion, and the discontinuous infusion is substantially shorter than the continuous infusion Instilled time periods are administered. 11. The data processing system of claim 1, wherein The received data includes a reduced received fluid-related patient parameter data set that affects a fluid cumulative usage calculation. 12. A patient medical parameter data processing system for providing patient medical parameter data for trend indication display, the trend indication display includes a time period including a user-selectable patient parameter acquisition time interval, the system comprising: an acquisition processor configured to receive fluid-related patient parameter data; data processor for identifying a reduced set of received fluid-related patient parameter data that affects the fluid cumulative usage calculation, and The reduced set of identified fluid-related patient parameter data is stored excluding fluid parameter data not relevant to the fluid cumulative usage calculation. 13. The data processing system of claim 12, wherein The data processor determines from the reduced set of identified fluid-related patient parameter data a cumulative total infusion of a particular fluid into a particular patient during a particular user-selectable patient parameter acquisition time interval. 14. The data processing system of claim 13, wherein The data processor automatically determines the cumulative total infusion in response to a user command to access a fluid parameter trend indicating display image. 15. The data processing system of claim 12, wherein The reduced identified fluid-related patient parameter data set includes: For continuous infusion, (a) the rate of fluid infusion volume into the patient, the fluid type identifier, and the start time and start date of said continuous infusion, and For discontinuous infusions, (b) the total amount of fluid infused, the fluid type identifier, and the time and date of the discrete infusion; and 16. A user interface system for providing patient medical parameter data for a trend indicating display comprising a user selectable time period, the system comprising: an acquisition processor for receiving data related to a user-selected time period, for a continuous infusion, the received data identifying a fluid infusion rate into the patient, a fluid type identifier, and a start time and start date of the continuous infusion, a data processor for determining, from said received data, a cumulative total infusion of a particular fluid into a particular patient during said user-selected time period; and a display generator for commencing generation of data representing an image showing a trend indicating display and indicating said cumulative total infusion of a particular fluid into a particular patient over said user-selected time period. 17. The user interface system of claim 16, wherein For a discontinuous infusion, the received data includes data identifying a total amount of fluid infused, a fluid type identifier, and a time and date of the discontinuous infusion. 18. The user interface system of claim 16, wherein The user-selected time period includes at least one of (a) patient parameter acquisition time intervals, (b) multiple patient parameter acquisition time intervals, (c) one hour, (d) hourly intervals, and (e) Work shift periods. 19. The user interface system of claim 16, wherein The received data includes a reduced received fluid-related patient parameter data set that affects a fluid cumulative usage calculation. 20. A method for providing patient medical parameter data for a trend indicating display comprising a time period including a user selectable patient parameter acquisition time interval, the method comprising the steps of: receive data that identifies, For continuous infusion, (a) the rate of fluid infusion volume into the patient, the fluid type identifier, and the start time and start date of said continuous infusion, and For discontinuous infusions, (b) the total amount of fluid infused, the fluid type identifier, and the time and date of the discrete infusion; and From the received data, a cumulative total infusion of a particular fluid into a particular patient over a particular user-selectable patient parameter acquisition time interval is determined. 21. A method for providing patient medical parameter data for a trend indicating display comprising a time period including a user selectable patient parameter acquisition time interval, the method comprising the steps of: receiving fluid-related patient parameter data; identifying a reduced set of received fluid-related patient parameter data that affects the fluid cumulative usage calculation, and The reduced set of identified fluid-related patient parameter data is stored excluding fluid parameter data not relevant to the fluid cumulative usage calculation. 22. A method for providing a trend indicating display of patient medical parameter data comprising a user selectable time period, the method comprising the steps of: receiving data related to a user-selected time period, for a continuous infusion, the received data identifying a rate of fluid infusion into the patient, a fluid type identifier, and a start time and date for the continuous infusion, from said receiving data, determining a cumulative total infusion of a particular fluid into a particular patient during said user-selected time period; and Generating data representing an image showing a trend indicating display and indicating said cumulative total infusion of a particular fluid into a particular patient over said user-selected time period is initiated.

Images