Infusion pump with next action indicator tab

Abstract

An infusion pump includes a multi-tab graphical user interface (GUI) that directs a user to the next tab for selection during programming of the infusion pump. The GUI includes tabs corresponding to parameter categories for input (e.g., patient information, medication information, infusion information). When inputting data, an operator (moving from left to right) selects a tab and inputs necessary parameters until all necessary parameters have been input completed. Due to the number of items presented under a particular tab, an operator may not easily see when the operator has entered all necessary parameters and may move to the next tab. Thus, upon completion of the necessary fields, the GUI presents an indicator (e.g., a small triangle) on or near the next tab that guides the operator and accelerates programming when the necessary fields constitute less than the total number of fields.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. application serial number 18 / 106,230, filed on February 6, 2023, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] The present disclosure relates to infusion pumps, and more particularly, to an infusion pump having an indicator tab that identifies the next action to be performed to program the infusion pump. Background Art

[0004] Infusion pumps deliver controlled doses of fluids, such as medications, analgesics, and nutrients, to patients. Infusion pumps are particularly well suited for delivering controlled doses of fluids over long periods of time (e.g., hours or days). Although many infusion pumps are designed for bedside use, there are portable (ambulatory) versions available. Portable infusion pumps allow patients to move around while the infusion pump is in use.

[0005] Syringe pumps and peristaltic pumps are two common types of infusion pumps. A syringe pump depresses a cylinder within a syringe to deliver fluid from the syringe to the patient. A peristaltic pump acts on tubing to control the flow rate of fluid from a bottle or bag through the tubing to the patient. Precise delivery of fluid is desirable for optimizing patient treatment, as there are many fluids where small variations can be critical.

[0006] Infusion pumps are typically set up and programmed by healthcare professionals in a healthcare setting. However, portable infusion pumps can be operated by patients in a home setting. Clear instructions for safe programming and operation of infusion pumps by untrained users are helpful in avoiding operator error. Summary of the Invention

[0007] The example described herein relates to a method and an infusion pump for delivering fluid to a patient. In an example configuration, the infusion pump includes a multi-tabbed graphical user interface (GUI) that guides the user to the next tab for selection during programming of the infusion pump (e.g., by placing an indicator such as a small triangle, arrow, colored square, flashing circle, or other shape / pattern next to the tab). The multi-tabbed GUI includes tabs corresponding to the parameter categories for input (e.g., patient information, medication information, infusion information). The tabs are presented in sequence, wherein the first parameter to be input is accessed by selecting the leftmost tab. When the information is complete, the operator selects a tab (moving from left to right) until all required parameters have been entered. The operator needs to fill in all required parameters for a specific category before moving to the next category. However, due to the number of items presented under a specific tab, it may not be easy for the operator to see when the operator has entered all required parameters under a specific tab and can move to the next tab.

[0008] Therefore, the GUI is adapted to guide the operator to select the next tab by presenting an indicator next to the next tab when all required parameters under the current tab have been entered. In the example configuration, the GUI presents the indicator on or near the next tab once the required fields are completed, even in those cases where the required fields required to complete the step comprise fewer than the total number of fields. By presenting the indicator once the required fields are completed (even when other optional fields have not yet been completed), the operator saves time programming the infusion pump and further prevents the operator from entering additional information that may affect the operation of the infusion pump.

[0009] In an example configuration, an infusion pump includes tubing, a pump motor configured to pump liquid through the tubing, a user interface, a memory, a controller coupled to the memory and the pump motor, and pump programming instructions in the memory. The controller executes the pump programming instructions to configure the infusion pump to present a multi-tabbed graphical user interface (GUI) on the user interface to guide an operator through programming the infusion pump. In the example configuration, each tab of the GUI includes a data field for entering data used for operation of the infusion pump. During programming of the infusion pump, an operator selects a tab of the GUI for data entry and enters data for the selected tab of the GUI. Once all required data for the selected tab of the GUI has been entered, a next tab indicator is presented on or near the next tab of the GUI to guide the operator to select the next tab for entering additional input data. In the example configuration, the selected tab may include at least one optional data field. In this case, the controller may execute additional instructions to present a next tab indicator on or near the next tab of the GUI when all required data for the selected tab has been entered, but data entry into at least one optional data field is not complete. In this configuration, the controller may further execute instructions to shade at least one optional data field in the user interface to indicate that data entry into the shaded at least one optional data field is not required for the selected operating mode of the infusion pump.

[0010] In an example configuration, the next tab indicator may include an icon, such as a triangle, pointing to the next tab for operator data entry or text associated with the next tab. The controller may also present the tabs of the multi-tab GUI from left to right across the extent of the user interface, whereby the respective tabs of the GUI include data fields for data entry of parameters related to medication data, patient data, infusion data, and the like. The user interface may include a touch screen display that, when touched, displays a keyboard in the user interface. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings depict multiple views of one or more embodiments by way of example only and not limitation. In the accompanying drawings, the same reference numerals represent the same or similar elements. The same numerals are used to represent the same or similar elements in multiple views. If there are multiple elements of the same or similar type, letters may be used to distinguish the multiple elements. When referring to multiple elements together or to a non-specific element among the multiple elements, the letter designations may be deleted.

[0012] Figure 1 is a perspective view of an exemplary portable peristaltic infusion pump.

[0013] Figure 2is with Figure 1 A perspective view of an exemplary cartridge with a free-flow prevention clamp for use with a portable peristaltic infusion pump.

[0014] Figure 3 yes Figure 1 A partial perspective view of a portable peristaltic infusion pump showing a cam engaging a free flow prevention clamp when the cassette is coupled to the portable peristaltic infusion pump.

[0015] Figure 4 and Figure 5 yes Figure 1 A cross-sectional view of a portable peristaltic infusion pump showing the pump fingers and the cams used to move the pump fingers.

[0016] Figure 6 An example multi-tab graphical user interface (GUI) including a next tab indicator in an example configuration is shown.

[0017] Figure 7 It shows Figure 1 Flowchart of the operation of a multi-tab GUI for a portable peristaltic infusion pump, wherein the multi-tab GUI directs an operator to the next tab using a next tab indicator in an example configuration.

[0018] Figure 8 is shown configured to implement the Figure 6-7 A functional block diagram of an example general-purpose computer hardware platform depicting its functionality.

[0019] Figure 9 is shown configured to implement the Figure 6-7 Another functional block diagram of a general computer hardware platform illustrating exemplary functionality is shown. DETAILED DESCRIPTION

[0020] In the following detailed description, many specific details are set forth by way of example in order to provide a thorough understanding of the relevant teachings. However, it will be apparent to those skilled in the art that the present teachings can be practiced without these details. In other cases, well-known methods, processes, components, and circuits have been described at a relatively high level without detail to avoid unnecessarily obscuring various aspects of the present teachings. In addition, although described with respect to portable peristaltic infusion pumps for pain management, home care, outpatient infusion, etc., those skilled in the art will understand that the multi-tab graphical user interface (GUI) described herein can be used with various other pump types that require multiple steps to program the pump.

[0021] Figure 1 An exemplary portable peristaltic infusion pump 100 is depicted, and Figure 2An exemplary cassette 102 for use with a portable peristaltic infusion pump 100 is depicted. The portable peristaltic infusion pump 100 includes a receptacle 104 configured to receive the cassette 102. A peristaltic pump 106 within the receptacle 104 acts on a tube 108 extending through a passageway within the cassette 102 to pump fluid from a fluid container (e.g., a bag or bottle, not shown) into a patient. An exemplary free-flow prevention clamp 110 is positioned within the cassette 102 to allow fluid to flow through the tube 108 when the cassette 102 is coupled to the portable peristaltic infusion pump 100 within the receptacle 104 (during which the peristaltic pump 106 controls the flow of fluid through the tube 108), and to selectively shut off the flow of fluid through the tube 108 when the cassette 102 is not coupled to the portable peristaltic infusion pump 100, thereby preventing unintentional fluid flow (e.g., free flow) through the tube 108.

[0022] The portable peristaltic infusion pump 100 includes a user interface 122 for interacting with the portable peristaltic infusion pump 100. The illustrated user interface 122 includes a display 124 (which can be a touch screen) and buttons 126. A user controls the operation of the portable peristaltic infusion pump 100 via the user interface 122. The portable peristaltic infusion pump 100 further includes a housing 128 for housing and supporting components of the portable peristaltic infusion pump 100, such as the peristaltic pump 106, electronics, a power supply, and the like.

[0023] The free-flow prevention clamp 110 includes a first elongated section 112a, a second elongated section 112b, and a clamping section 112c. The housing 130 of the cassette 102 supports the free-flow prevention clamp 110. The clamping section 112c is positioned within the cassette geometry so that when the cassette 102 is received within the receiver 104 of the portable peristaltic infusion pump 100, the clamping section 112c extends through the passageway of the receiving tubing 108. The housing 130 of the cassette 102 can be a rigid plastic or other material capable of supporting the tubing 108 and the free-flow prevention clamp 110.

[0024] The portable peristaltic infusion pump 100 further includes a pair of arcuate cams 114a and 114b. The first arcuate cam 114a is shown in FIG. Figure 1 The portable pump 100 is shown on one side of the receiver, but the second curved cam 114b is hidden and not visible. The pair of curved cams 114a and 114b engage the elongated sections 112a, 112b of the free flow prevention clamp 110 to lift the clamping section 112c. In addition, the portable pump 100 includes a pair of wedge-shaped cams 116a and 116b. The first wedge cam 116a is shown Figure 1 The second wedge cam 116b is hidden from view on one side of the receiver 104. The pair of wedge cams 116a and 116b switches the free flow prevention clamp 110 from the open, manufacturing / shipping state to the operational state, which is described in further detail below.

[0025] The box 102 also includes a first notch 118a in the side wall 132 of the box 102 and a second notch 118b in the opposite side wall 134 of the box 102. In addition, the box 102 includes a touch pad 120 located on the first elongated section 112a, adjacent to the midpoint of the first elongated section 112a and the first notch 118a. The touch pad 120 and the notch 118a together facilitate the operator's finger to engage the first elongated section 112a so that when the box 102 is not received in the receiver 104 of the portable peristaltic infusion pump 100, the clamping section 112c is manually lifted to allow fluid to flow through the tube 108 (e.g., for priming the box 102). The touch pad 120 can be a press-fit piece of rigid plastic. Although the touch pad 120 is shown as being only on the first elongated section 112a, the touch pad 120 can also be provided on the second elongated section 112b.

[0026] Figure 3 The arcuate cams 114a and 114b of the portable peristaltic infusion pump 100 and the peristaltic pump 106 are depicted. The peristaltic pump 106 includes a plurality of pump fingers 300 ( Figure 3 108 ). A flexible barrier 302 separates the pump fingers 300 (and other pump components of the pumping mechanism) from the receptacle 104, which receives the cassette 102 with the tubing 108. The flexible barrier 302 provides a barrier between the fluid delivery device / cassette and the pumping mechanism to prevent fluid from damaging components of the pumping mechanism.

[0027] Figure 4 and Figure 5 FIG2 is a cross-sectional view of the portable peristaltic infusion pump 100 with the cassette 102 inserted into the receiver 104 of the portable peristaltic infusion pump 100. A plurality of cams 304 (six cams 304a-f) supported by a camshaft 306 act on corresponding pump fingers 300a-300f. The cams 304a-304f respectively raise and lower the pump fingers 300a-300f, which engage the tube 108 of the cassette 102 to force fluid through the tube 108. A pump motor 308 rotates the camshaft 306 under the control of a controller 310 via a gearbox 312. As the camshaft 306 rotates, the cams 304a-300f, which are offset from each other in the axial direction, raise and lower the corresponding pump fingers 300a-300f. For example, cam 304a raises and lowers pump finger 300a; cam 304b raises and lowers pump finger 300b, and so on. Figure 8 and Figure 9 As described above, the controller 310 may be a standalone or embedded processor configured to execute instructions to control the operation of the portable peristaltic infusion pump 100 .

[0028] The controller 310 may include a main controller, such as a dual-core 32-bit processor from NXP (Eindhoven, The Netherlands) (e.g., Model #MCIMX7S5EVM08SC), a microcontroller from NXP (e.g., Model #MKV11Z128VLF7), a pump motor driver from ST Microelectronics (Geneva, Switzerland) (e.g., Model #STSPIN250), and a magnetic encoder from Austrian Microsystems (Premstaetten, Austria) (e.g., Model AS5601-ASOM). The microcontroller receives the pump camshaft revolutions per minute (RPM) corresponding to the infusion rate from the main processor's system control core. The microcontroller generates pulse-width modulated (PWM) motor drive parameters related to the desired camshaft RPM. The microcontroller's PWM output becomes the motor drive input to the pump motor driver, which includes motor drive transistors and protection circuitry. The rotation of the camshaft 306 of the pumping mechanism is measured by the magnetic encoder. At specified time intervals, the encoder output is read by the microcontroller, which uses the encoder value to calculate the speed of the camshaft 306 and the position of the pump rotation. These values ​​are then used to modify the PWM output to maintain the correct camshaft RPM.

[0029] Before operation, require Figure 1-5 The operator of the portable peristaltic infusion pump 100 enters a plurality of parameters to program the portable peristaltic infusion pump 100. During programming the portable peristaltic infusion pump 100 to deliver an infusion to a patient, the operator of the portable peristaltic infusion pump 100 may be required to enter many different types of parameters (e.g., patient information, medication information, infusion parameters, etc.). For example, when using the portable peristaltic infusion pump 100 to infuse one or more medications into a patient, the portable peristaltic infusion pump 100 may be programmed to specify the medication to be infused, patient data, and infusion (flow rate) data.

[0030] like Figure 6 As shown, the user interface 122 of the portable peristaltic infusion pump 100 can include a multi-tab GUI 600 that includes a next tab indicator 610 that guides the operator to enter parameters in an example configuration. Due to the small form factor of the portable peristaltic infusion pump 100, the maximum size of the display (and associated display area) is limited. Therefore, in the example configuration, it is expected that the next tab indicator 610 is a small icon, such as a small triangle, which is placed on or near the next tab to identify the next tab or text associated with the next tab for operator data entry.

[0031] As shown, multiple tabs are presented from left to right across the user interface 122. The first tab 620 provides data entry boxes 620a-620e for entering data specifying a care area (620a), medication name (620b), clinical regulator (620c), medication concentration (620d), infusion regimen (620e), and the like. It should be understood that not all data entry boxes are required for a particular medication or operating mode. In this example, the data entry boxes 620c-620e are shaded to indicate that the information in the data entry boxes 620c-620e is optional and not required for the selected medication or current operating mode.

[0032] The second tab 630 provides a data input box (not shown) for inputting patient data, and the third tab 640 similarly provides a data input box (not shown) for inputting infusion data related to the desired flow rate, the infusion time of the day, and similar information. The fourth tab 650 provides a summary of the input parameters for the operator to check before operating the portable peristaltic infusion pump 100. In addition, different tabs can be provided in other operating modes. It should be understood that the user interface 122 may include a touch screen display 124 that pulls up a keyboard (e.g., AZERTY, QWERTY, QWERTZ, or QZERTY keyboard) when touched. Alternatively, a button (not shown) can be used to call a keyboard for data input.

[0033] Thus, the multi-tab GUI 600 includes multiple tabs (e.g., 620-650) corresponding to parameter categories for input (e.g., medication information, patient information, infusion information) and presented in progressive order. The operator needs to fill in all required parameters for a particular category before moving to the next category.

[0034] Since the operator may be a new user who has not been trained or has insufficient training, the operator may not understand what parameters are required. Therefore, the required parameters can be identified by shading the data input boxes that are optional and do not need to be completed before moving to the next category. In addition, in the example configuration, the operator is further guided to select the next tab by presenting an indicator 610 next to the next tab or text associated with the next tab once all required parameters under the current tab have been entered. Figure 6 As shown, the operator is guided to the next tab 640 for selection by placing an indicator 610, such as a small triangle, next to the next tab 640 once the necessary data for the current tab has been entered. Figure 6In the example shown in FIG. 6 , indicator 610 informs the operator that the operator can transition directly from tab 620 to tab 640 once the required data has been entered in tab 620 and as long as all required patient data has been entered in tab 630. In the example configuration, “next tab” indicator 610 can be a transient graphic that pulses, fades in and out, or otherwise turns on and off to further attract the operator's attention. However, “next tab” indicator 610 can also be static and not transition.

[0035] Figure 7 is a flow chart illustrating programming the portable peristaltic infusion pump 100 using a multi-tab GUI 600 that directs the operator to the next tab using an example configured next tab indicator 610. As described above, the multi-tab GUI 600 is adapted to enable the operator to enter parameters necessary to configure the portable peristaltic infusion pump 100 to deliver an infusion to a patient. Figure 6 In the example shown in FIG, a multi-tab GUI 600 includes tabs 620-650 corresponding to parameter categories for input (e.g., patient information, medication information, infusion information). The tabs 620-650 are presented in sequence, with the first parameter to be input being accessed by selecting the leftmost tab 620. When the information is completed, the operator selects the corresponding tab 620-650 (moving from left to right) until all required parameters are completed.

[0036] The controller 310 of the portable peristaltic infusion pump 100 can be programmed to implement Figure 7 process. Figure 7As shown, the process begins at 700. At 710, the operator can select one of the tabs 620-650 for data entry, typically starting with the leftmost tab. However, the user can start at 720 without selecting a tab 620-650. At 720, the operator enters the necessary data for that tab using, for example, a keyboard that pops up when a tab is selected via button selection via button 126 or touch selection via touchscreen 124. Before moving to the next category, the operator must complete all required parameters for a particular category under a tab 620-650. Due to the number of items under a selected tab, it may not be easy for the operator to determine when all required parameters have been entered for the selected tab and the operator can move to the next tab 620-650. Therefore, at 730, a determination is made as to whether all required data for the selected tab has been entered. After completing the necessary data entry, the operator can repeat the data entry at 730 and change the previously entered parameters. It should be understood that fewer than all data inputs are required as represented by the displayed data input boxes, as some parameters may be optional.

[0037] In the example configuration, data entry begins at the leftmost tab 620, and the selection made at tab 620 affects the options presented to the user at tabs 630, 640, and ultimately tab 650. Depending on the medication selected within tab 620, tab 630 (Patient Data) switches on or off accordingly, as not all medications require detailed patient data. Additionally, the selections made at tabs 620 and 630 determine what parameters are entered at tab 640. The results of the data entry are then summarized at tab 650. In the example configuration, the software enforces a left-to-right data entry order.

[0038] In the example configuration, the tabs are precisely organized to move the operator from one tab to the next, where input from one tab affects what is conveyed and expected in the next tab. The next tab indicator 610 appears simultaneously with the next tab and even becomes activated and therefore selectable by the user. In other words, the operator must complete all required inputs for the first tab 620 before being given access to the next tab (tab 630 or tab 640, depending on the selection at tab 620), then access to the next tab (640), and then access to the last tab 650 to review these selections. The operator can return to the previous tab, but the operator cannot skip back because the tab is gray and unselectable before being enabled for completion.

[0039] Once it is determined at 730 that all required data for the current tab has been entered, an indicator 610 is presented at 740 on the next tab or in text associated with the next tab to guide the operator through data entry. In addition to presenting the next tab indicator 610, this is the first time the next tab is selectable. Until it is determined at 730 that all required data for the current tab has been entered, the next tab is grayed out and unselectable. At 750, a determination is made as to whether all required data for all tabs has been entered. If not, the process returns to 710 to select the next tab for data entry. Note that only one new tab is made available for data entry, and the operator can return to the previous tab. Once all required data for all tabs has been entered, the entered data is confirmed at the review tab 650, and the operator is then given the option to start operation of the portable peristaltic infusion pump 100 at 760. If the user chooses to start the portable peristaltic infusion pump 100, the portable peristaltic infusion pump 100 is operated at 770. Otherwise, the process ends at 780.

[0040] Figure 8 and Figure 9 is shown configured to implement the above-discussed Figure 1-7 A functional block diagram of an example general-purpose computer hardware platform depicting its functionality.

[0041] Specifically, Figure 8 An example computer platform 800 is shown, and Figure 9 An example computer 900 having user interface elements is depicted, such as may be used to implement in a personal computer, the controller 310 of the portable peristaltic infusion pump 100, or other type of workstation or terminal device. It is believed that those skilled in the art are familiar with the structure, programming, and general operation of such computer devices, and thus the drawings should be self-explanatory.

[0042] The example server computer 800 ( Figure 8 ) includes a data communications interface 802 for packet data communications. The server computer 800 also includes a central processing unit (CPU) 804 in the form of circuitry forming one or more processors for executing program instructions. The server platform hardware typically includes an internal communications bus 806, random access memory (RAM) 816, program and / or data storage in read-only memory (ROM) 818, and a mass storage (e.g., disk storage) device 820 for storing various program and data files to be processed and / or transmitted by the server computer 800, although the server computer 800 typically receives programs and data via network communications via the data communications interface 802. In one example, as Figure 8As shown, computer system 800 also includes a video display unit 810 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device 812 (e.g., a keyboard), and a cursor control device 814 (e.g., a mouse), each of which communicates via input / output devices (I / O) 808. The hardware elements, operating system, and programming language of such server computer 800 are conventional in nature and are assumed to be sufficiently familiar to those skilled in the art. Of course, the server functions can be implemented in a distributed manner on multiple similar hardware platforms to distribute the processing load.

[0043] The hardware of a computer-type user terminal device 900 (such as a PC or tablet computer) similarly includes a data communication interface 902, a CPU 904, a main memory including a RAM 916 and a ROM 918, one or more mass storage (e.g., disk) devices 920 for storing user data and various executable programs, an internal communication bus 906, and an input / output device (I / O) 908 (see Figure 9 ).

[0044] As outlined above, aspects of the method for pump control may be implemented on a general purpose computer hardware platform (e.g., as described above with respect to Figure 8 and 9The program aspects of the technology may be considered to be "products" or "articles of manufacture" which are typically in the form of executable code and / or related data carried or embodied on a type of machine-readable medium. "Storage" type media include any or all tangible memories of computers, processors, etc., or their associated modules, such as various semiconductor memories, tape drives, disk drives, etc., which can provide non-transitory storage for software programming at any time. All or part of the software may sometimes be communicated over the Internet or various other telecommunications networks. For example, such communication can enable software to be loaded from one computer or processor to another, for example, from the processor 804 of the system 800 and / or from the controller 310 of the pump 100 to a computer or software of another system (not shown). Thus, another type of medium that can carry software elements includes optical waves, radio waves, and electromagnetic waves, such as those used across physical interfaces between local devices, through wired and optical landline networks, and through various air links. Physical elements that carry such waves (such as wired or wireless links, optical links, etc.) can also be considered to be media that carry software. As used herein, unless limited to one or more of "non-transitory," "tangible," or "storage" media, terms such as computer or machine "readable media" refer to any medium that participates in providing instructions to a processor for execution.

[0045] Thus, machine-readable media can take many forms, including but not limited to tangible storage media or physical transmission media. Non-transitory storage media include, for example, optical or magnetic disks, such as any storage device in any computer. Non-transitory storage media can also include storage media such as dynamic memory, such as the main memory of a machine or computer platform. Tangible transmission media include coaxial cables, copper wire, and optical fiber, including the wires that comprise the bus within a computer system. Carrier transmission media can take the form of electrical or electromagnetic signals or sound or light waves, such as those generated during radio frequency (RF) and light-based data communications. Thus, common forms of computer-readable media include, for example: floppy disks, flexible disks, hard disks, magnetic tape, any other magnetic medium, CD-ROMs, DVDs or DVD-ROMs, any other optical media, punched card stock tape, any other physical storage medium with a pattern of holes, RAM, PROMs and EPROMs, FLASH-EPROMs, any other memory chips or cassettes, cables or links that transmit carrier waves, or any other medium from which a computer can read programming code and / or data. Many of these forms of computer-readable media can involve carrying one or more sequences of one or more instructions to a processor for execution.

[0046] The program instructions for implementing the processes described herein may include software or firmware implementations coded in any desired language. When embodied in a machine-readable medium accessible to a processor of a computer system or device, the programming instructions cause the computer system or device to become a special-purpose machine customized to perform the operations specified in the program executed by the controller 310 of the pump 100.

[0047] While the foregoing has described what is believed to be the best mode and / or other examples, it should be understood that various modifications may be made therein, that the subject matter disclosed herein may be implemented in a variety of forms and examples, and that the teachings may be applied to many applications, only some of which have been described herein. The following claims are intended to claim any and all applications, modifications, and variations that fall within the true scope of the present teachings.

[0048] Unless otherwise indicated, all measurements, values, ratings, positions, sizes, dimensions and other specifications set forth in this specification (including in the appended claims) are approximate and not exact. They are intended to be within a reasonable range consistent with the functions to which they relate and ordinary functions in the art to which they pertain.

[0049] The scope of protection is limited solely by the following claims. When interpreted in light of this specification and the subsequent prosecution history, the scope is intended and should be interpreted to be as broad as consistent with the ordinary meaning of the language used in the claims and to encompass all structural and functional equivalents. Notwithstanding the foregoing, the claims are not intended to include subject matter that does not satisfy the requirements of sections 101, 102, or 105 of the Patent Act, nor should they be construed in such a manner. Any unintended inclusion of such subject matter is hereby disclaimed.

[0050] Except as stated immediately above, nothing stated or shown is intended or should be construed as resulting in any element, step, feature, object, benefit, advantage, or equivalent being dedicated to the public regardless of whether it is recited in the claims.

[0051] It should be understood that the terms and expressions used herein have the common meaning consistent with these terms and expressions of the corresponding investigation and research fields corresponding to them, unless otherwise specified herein. Relational terms such as first and second can be used only to distinguish one entity or action from another entity or action, and do not necessarily require or imply any actual such relationship or order between these entities or actions. The term "comprises", "comprising", "includes", "including" or any other variation thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device comprising a list of elements not only includes those elements, but also can include other elements that are not clearly listed or inherent to such process, method, article or device. In the absence of further constraints, an element preceded by "a" or "an" does not exclude the presence of other identical elements in the process, method, article or device comprising the element.

[0052] An abstract of the disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It should be understood that the abstract will not be used to interpret or limit the scope or meaning of the claims. Additionally, in the foregoing detailed description, it can be seen that various features are grouped together in various embodiments for the purpose of simplifying the disclosure. This approach to the disclosure should not be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as reflected in the following claims, the inventive subject matter lies in less than all the features of a single disclosed embodiment. Accordingly, the following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separately claimed subject matter.

[0053] In addition, in the foregoing detailed description, it can be seen that various features are grouped together in various examples for the purpose of simplifying the present disclosure. This method of disclosure should not be interpreted as reflecting an intention that the claimed examples require more features than those expressly recited in each claim. On the contrary, as reflected in the following claims, the subject matter to be protected lies in less than all the features of any single disclosed example. Therefore, the following claims are hereby incorporated into the detailed description, with each claim standing on its own as separately claimed subject matter.

[0054] While the foregoing describes what is believed to be the best mode and other examples, it should be understood that various modifications may be made and that the subject matter disclosed herein may be implemented in a variety of forms and examples and that they may be used in many applications, only some of which are described herein. The following claims are intended to claim any and all modifications and variations that fall within the true scope of the present concept.

Claims

1. An infusion pump comprising: Tube; a pump motor configured to pump liquid through the tube; user interface; Memory; a controller coupled to the reservoir and the pump motor; as well as pump programming instructions in the memory, wherein the controller is configured to receive the pump programming instructions from the memory and execute the received pump programming instructions, wherein execution of the pump programming instructions by the controller configures the infusion pump to: presenting a multi-tabbed graphical user interface (GUI) on the user interface to guide an operator in programming the infusion pump, each tab of the GUI including a data field for entering data used for operation of the infusion pump; receiving an operator selection of a tab of the GUI for data entry; receiving data input for a selected tab of the GUI; as well as Once all required data input for the selected tab of the GUI has been completed, a next tab indicator is presented on or near the next tab of the GUI and the next tab of the GUI is activated for selection, wherein the next tab indicator guides the operator to select the next tab in order to enter additional input data.

2. The infusion pump according to claim 1, wherein: The selected tab includes at least one optional data field; and wherein the controller executes additional instructions to present the next tab indicator on or near the next tab of the GUI when all required data entry for the selected tab has been completed but data entry into the at least one optional data field has not been completed.

3. The infusion pump according to claim 2, wherein: The controller executes instructions to shade the at least one optional data field in the user interface to indicate that data entry into the at least one shaded optional data field is not required for the selected operating mode of the infusion pump.

4. The infusion pump according to claim 1, wherein: The next tab indicator includes a transient graphic that identifies the next tab for operator data entry.

5. The infusion pump according to claim 4, wherein: The transient graphic is a triangle that points to the next tab or text associated with the next tab to draw the operator's attention to the next tab or the text associated with the next tab.

6. The infusion pump according to claim 1, wherein: The controller executes instructions to present the tabs of the multi-tab GUI from left to right across the extent of the user interface and to make tabs subsequent to the initial tab selectable by the operator once all required data entry for a previous tab of the GUI has been completed.

7. The infusion pump according to claim 6, wherein: The corresponding tabs of the GUI include data fields for data entry of parameters related to medication data, patient data, and infusion data.

8. The infusion pump according to claim 1, wherein: The user interface includes a touch screen display that displays a keyboard in the user interface when the touch screen display is touched.

9. A method for programming an infusion pump, comprising: presenting a multi-tabbed graphical user interface (GUI) on the user interface of the infusion pump to guide an operator in programming the infusion pump, each tab of the GUI including a data field for entering data used for operation of the infusion pump; receiving an operator selection of a tab of the GUI for data entry; receiving data input for a selected tab of the GUI; as well as Once all required data input for the selected tab of the GUI has been completed, a next tab indicator is presented on or near the next tab of the GUI and the next tab of the GUI is activated for selection, wherein the next tab indicator guides the operator to select the next tab in order to enter additional input data.

10. The method according to claim 9, wherein: The selected tab includes at least one selectable data field; as well as Wherein presenting the next tab indicator comprises presenting the next tab indicator on or near the next tab of the GUI when all required data entry for the selected tab has been completed but data entry into the at least one optional data field has not been completed.

11. The method of claim 10, further comprising shading the at least one optional data field in the user interface to indicate that data entry into the at least one shaded optional data field is not required for the selected operating mode of the infusion pump.

12. The method according to claim 9, wherein Presenting the next tab indicator includes presenting a transient graphic identifying the next tab for operator data entry.

13. The method according to claim 12, wherein: Presenting the next tab indicator includes presenting a triangle that points to the next tab or text associated with the next tab to draw the operator's attention to the next tab or the text associated with the next tab.

14. The method according to claim 9, wherein Presenting the multi-tab GUI to the user interface includes presenting the tabs of the multi-tab GUI from left to right across the extent of the user interface, and setting the tabs subsequent to the initial tab to be selectable by the operator once all required data entry for a previous tab of the GUI has been completed.

15. The method according to claim 14, wherein Presenting the multi-tabbed GUI to the user interface includes presenting respective tabs including data fields for data entry of parameters related to medication data, patient data, and infusion data.

16. The method of claim 9, further comprising displaying a keyboard in the user interface when a touch screen display of the user interface is touched.

17. The method according to claim 9, further comprising: When all necessary data for all tabs have been entered, the operation of the infusion pump is started.

18. A non-transitory controller-readable storage medium storing controller-executable instructions for programming an infusion pump, wherein the controller-executable instructions, when executed by a controller of the infusion pump, cause the infusion pump to perform the following operations, the operations comprising: presenting a multi-tabbed graphical user interface (GUI) on the user interface of the infusion pump to guide an operator in programming the infusion pump, each tab of the GUI including a data field for entering data used for operation of the infusion pump; receiving an operator selection of a tab of the GUI for data entry; receiving data input for a selected tab of the GUI; as well as Once all required data input for the selected tab of the GUI has been completed, a next tab indicator is presented on or near the next tab of the GUI and the next tab of the GUI is activated for selection, the next tab indicator guiding the operator to select the next tab in order to enter additional input data.

19. The medium according to claim 18, wherein The selected tab includes at least one optional data field, and the medium also includes instructions stored on the medium that, when executed by the controller, cause the infusion pump to perform the following operations, the operations including: presenting the next tab indicator on or near the next tab of the GUI when all required data input for the selected tab has been completed but data input into the at least one optional data field has not been completed.

20. The medium of claim 19, further comprising instructions stored on the medium that, when executed by the controller, cause the infusion pump to perform operations comprising: The at least one optional data field in the user interface is shaded to indicate that data entry into the at least one shaded optional data field is not required for the selected operating mode of the infusion pump.

Images