Patent Description:
Patients with renal insufficiency may need supporting treatment in the form of dialysis for the removal of waste substances and excess of fluid from the body. Dialysis is a process to remove fluid and waste products from the patient by the use of diffusional or convective transport. Various dialysis techniques with associated dialysis fluids may be differentiated. Which dialysis technique to use, depends on the patient needs, treatment demands and available resources.

In a variety of renal insufficiency treatments, one or more fluids, or liquids, may be supplied to the renal insufficiency treatment system for use during the treatments and one or more fluids may be collected as a part of the treatments. Both the supplied and collected fluids may be stored in one or more reservoirs or containers. These reservoirs/containers may, during the course of treatment of a single patient, need to be replaced as they are either emptied (in the case of fluids supplied as a part of the treatment) or are filled to capacity (in the case of fluids collected as a part of the treatment). Document <CIT> discloses a dialysis machine comprising a plurality of bags each having a corresponding RFID tag containing a bag identifier. Respective receiving stations receive each a bag. A control unit compares the stored configuration of bags concerning a treatment protocol with the configuration of bags once installed. Document <CIT> describes a dialysis machine with a
reader to read information from disposable components to be installed onto the machine and checks that the components are compatible with the selected treatement.

Systems and methods for renal insufficiency treatment that include identifying and associating a solution container with a container support in the systems and methods are described herein.

In one or more embodiments, the systems and methods may associate an identified solution with an identified container support and verify compatibility of that combination with a selected treatment to reduce the likelihood for errors during setup and use of the systems and methods. This may be particularly true for systems/treatments that require an operator to provide and/or replace containers holding specific fluids prior to and during treatment. Each container may need to be positioned at a specific location in the system (e.g., on a scale or support) and/or connected in a specific manner for a specific treatment therapy and failure to ensure that containers provide the correct fluids, are properly located (e.g., on a scale or other support), and/or properly connected may result in insufficient treatment and/or injury to a patient. The systems and methods described herein may reduce the likelihood for such errors in container selection/loading and/or placement on the system by providing for verification that containers holding the correct fluids are provided in the correct locations on a treatment system during setup and/or container replacement.

As described herein, a renal insufficiency treatment system may include one of a blood pump configured to move blood through an extracorporeal circuit during extracorporeal renal insufficiency treatment and a peritoneal dialysis fluid pump configured to deliver dialysis fluid to a patient during a peritoneal renal insufficiency treatment depending on the type of renal insufficiency treatment system (i.e., an extracorporeal blood treatment system would include a blood pump and a peritoneal dialysis system would include a peritoneal dialysis fluid pump). The scope of the present invention is defined by the appended set of claims.

In the following detailed description of illustrative embodiments, reference is made to the accompanying figures of the drawing which form a part hereof, and in which are shown, by way of illustration, specific embodiments which may be practiced. It is to be understood that other embodiments may be utilized and structural changes may be made without departing from (e.g., still falling within) the scope of the disclosure presented hereby.

Exemplary systems and methods including identifying and associating a solution with a container support for use in renal insufficiency treatments shall be described with reference to <FIG>. It will be apparent to one skilled in the art that elements or processes from one embodiment may be used in combination with elements or processes of the other embodiments, and that the possible embodiments of such systems and methods using combinations of features set forth herein is not limited to the specific embodiments shown in the Figures and/or described herein. Further, it will be recognized that the embodiments described herein may include many elements that are not necessarily shown to scale. Still further, it will be recognized that timing and use of the processes described herein may be modified but still fall within the scope of the present disclosure, although certain timings of or use of certain processes may be advantageous over others.

The present disclosure may be described as systems and methods to associate an identified solution with an identified container support and verify compatibility with a selected treatment. For example, an illustrative renal insufficiency treatment system may be configured to scan and/or identify various components of the system (e.g., via indicators such as barcodes, QR codes, identifiers, RFID tags/devices, Near Field Communication (NFC) tags/devices, etc.) to ensure compatibility and compliance for a specific treatment. Specifically, the system may include a sensor (e.g., a scanner, vision system, camera, etc.) that is configured to scan and/or identify indicators associated with solution containers (e.g., bags, reservoirs, syringes, etc.) and container supports (e.g., scales, etc.) used by the system.

These features may assist in tracking and aligning proper concentrations/constituents in solutions that are used during renal insufficiency therapy. For example, an actual concentration being used may be compared with a proposed prescription solution as well as to a selected therapy and expected solutions for that therapy for verification purposes. Further, the renal insufficiency treatment system often already performs multiple calculations to determine fluid flow rates based upon dosage prescriptions and patients body weight, citrate load, post filter hematocrit, etc., therefore, the system may also determine use of the proposed concentrations based upon the prescribed dosages and other treatment parameters.

Further, the sensor may be configured to identify any indicator associated with a solution or support, whether the indicator was previously known or unknown (e.g., using a local or connected database, through information stored within the indicator, etc.). In one or more embodiments, a configuration menu or table may be used to automatically load which solutions citrate concentrations are used and which calcium solutions are used based on the information obtained through the indicator (e.g., using the sensor). Furthermore, in one or more embodiments, a user may input specific conditions associated with a given therapy treatment and the system may verify the applicability of a solution identified by the system. In other words, the system may determine whether selected parameters (e.g., solution type, concentration of calcium or heparin, solution container location, anticoagulation type, etc.) are applicable and appropriate for a specific therapy treatment. In one or more embodiments, this implementation may help prevent errors, may increase safety, and may provide the user with additional data on therapy usages.

An exemplary renal insufficiency treatment system <NUM> depicted in <FIG> may be used to execute, or perform, the exemplary methods and/or processes described herein. In at least one embodiment, the system <NUM> may be a machine for the extracorporeal treatment of blood. The system <NUM> could, for example, alternatively be a blood processing device or a blood component preparation device or other medical apparatus for fluid delivery/collection. In at least one embodiment, the system <NUM> could be a peritoneal dialysis treatment system configured to deliver dialysis fluid to the peritoneal cavity of a patient.

As shown, the exemplary renal insufficiency treatment system <NUM> includes computing apparatus <NUM>. The computing apparatus <NUM> may be configured to receive input from input apparatus <NUM> and transmit output to display apparatus <NUM>.

The treatment apparatus <NUM> of system <NUM> may include any apparatus used by an exemplary renal insufficiency treatment system capable of performing renal insufficiency treatments, such as, e.g., pumps, containers/reservoirs, scales, treatment sets, filters, stoppages sensors, pressure sensors, etc. For example, the treatment apparatus <NUM> may include, in on or more embodiments, one or more elements, or components, of the exemplary extracorporeal blood treatment system described herein with reference to <FIG> or <FIG>.

The exemplary systems, and exemplary methods performed, or used, by such exemplary systems, described herein may be generally referred to as renal insufficiency treatment systems. The general terms "dialysis" and "renal insufficiency treatment" as used herein include peritoneal dialysis as well as hemodialysis, hemofiltration, hemodiafiltration, hemoperfusion, liver dialysis, and therapeutic plasma exchange (TPE), among other similar treatment procedures.

In peritoneal dialysis generally, dialysis fluid is infused into the patient's peritoneal cavity. This cavity is lined by the peritoneal membrane which is highly vascularized. Substances are removed from the patient's blood by diffusion across the peritoneal membrane into the dialysis fluid. Excess fluid (e.g., water) can also be removed by osmosis induced by a hypertonic dialysis fluid (e.g., ultrafiltration).

In extracorporeal blood treatment generally, blood is taken out of the body and exposed to a treatment device to separate substances therefrom and/or to add substances thereto and is then returned to the body. Although extracorporeal blood treatment systems capable of performing general dialysis (as defined above, including TPE) as well as those for infusion of drugs are to be contemplated herein, the illustrative systems may generally be configured to perform continuous renal replacement therapy (CRRT). Additionally, extracorporeal blood treatment systems that perform extracorporeal membrane oxygenation (ECMO), hemoperfusion, liver dialysis, apheresis, TPE, etc. may benefit from the systems, methods, and processes described herein and the present disclosure is not limited to any particular fluid processing system.

Referring to <FIG>, one illustrative embodiment of a renal insufficiency treatment system in the form of an extracorporeal blood treatment system <NUM> is depicted. The system <NUM> includes a housing <NUM> having a computing apparatus <NUM>. The system <NUM> further includes one or more pumps <NUM>, one or more disposable elements <NUM> (e.g., including or part of integrated modules), and one or more sensors <NUM> for use in performing one or more extracorporeal blood treatments. The one or more pumps <NUM> may be used to move liquids through the system as part of a treatment process. Although the pumps <NUM> are depicted in the form of peristaltic pumps, the pumps used in the extracorporeal blood treatment system described herein may be provided in a variety of alternative forms, e.g., piston pumps, pumps for use with syringes, diaphragm pumps, etc. The one or more pumps <NUM> may include one or more dialysate pumps and one or more effluent pumps. The dialysate pumps may be generally described as being on the upstream side of a blood treatment unit (e.g., a filter) on a dialysate circuit, and the effluent pumps may be generally described as being on the downstream side of the blood treatment unit on the dialysate circuit.

The one or more disposable elements <NUM> may be coupled to the system <NUM> for use in performing the extracorporeal blood treatment. The one or more disposable elements <NUM> may include one or more fluid circuits such as, e.g., dialysis or dialysate fluid circuits, blood circuits, etc. and/or one or more blood treatment units such as, e.g., filters, etc. In at least one embodiment, a disposable element <NUM> is a cartridge or integrated unit including a plurality of various parts or portions configured to perform the extracorporeal blood treatment. Additionally, the one or more disposable elements <NUM> may include containers, or vessels, containing, or holding, one or more substances for use in the performance of the extracorporeal blood treatment. For example, a disposable element <NUM> may include a container, or vessel, holding bicarbonate, citrate, calcium, dextrose, glucose, and/or dialysate/dialysis fluid, which may be operatively coupled to the dialysis/dialysate fluid circuit. Further, the disposable elements <NUM> may be described as providing at least a portion of the extracorporeal blood treatment fluid circuit that may be operatively coupled to one or more pumps <NUM> and one or more sensors of the system <NUM> for use in performing extracorporeal blood treatments. As shown, a disposable element <NUM> appears to be coupled to the housing <NUM> of the system <NUM> to, e.g., integrate with the one or more other fluid circuits, pumps <NUM>, and sensors of the system <NUM>.

As described herein, the one or more disposable elements <NUM> may be described as including one or more disposable fluid circuits and one or more blood treatment units operatively coupled to the one or more disposable fluid circuits. The one or more disposable elements <NUM> may be further described as including a blood circuit for receiving, circulating, and returning blood from/to a patient. The blood circuit may include one or more blood lines (e.g., as part of a disposable element). For example, the system <NUM> may include a blood pump configured to move blood through an extracorporeal circuit during extracorporeal blood treatment. Further, the one or more disposable elements <NUM> may be further described as including a dialysis/dialysate circuit operatively coupled, or couplable, to the blood circuit to remove waste from the blood of the patient. The dialysis/dialysate circuit may receive, circulate, and return dialysis/dialysate fluid (e.g., returning dialysis/dialysate fluid including waste). The dialysis/dialysate circuit may include one or more dialysis/dialysate lines (e.g., as part of a disposable element <NUM>). The blood treatment units may be, for example, a plasma filter, a hemodialysis filter, a hemofiltration filter, etc. Generally, the blood treatment units may be referred to as "filters.

Additionally, the extracorporeal blood treatment fluid circuit of the system <NUM> may be described as being completed by a combination of the disposable elements <NUM> and the system <NUM> and may be generally described as defining a blood circuit that removes blood from a patient, for example, via a catheter inserted in a vascular access of the patient, and takes the blood though a blood removal line. Then, the blood may pass through a chamber (e.g., a blood chamber) and, via a return line, may be transported back to the patient.

The treatment system <NUM> also includes, in one or more embodiments, a display <NUM> used to convey information to an operator or user. The display <NUM> may also serve as an input device if, e.g., the display <NUM> is in the form of a touchscreen. Also, although the display <NUM> is depicted as being located in the housing <NUM>, in one or more embodiments, the display <NUM> may be separate from the housing <NUM> of the extracorporeal blood treatment system <NUM>. For example, the display <NUM> may be movably (e.g., swivel, tilt, etc.) attached, or coupled, to a top end of the housing <NUM>.

The extracorporeal blood treatment system <NUM> also includes a plurality of container supports <NUM>. Each of the container supports <NUM> of the plurality of container supports <NUM> may be configured to receive and hold (e.g., support) a solution container <NUM>. The container supports <NUM> may take any suitable shape and form. For example, in one or more embodiments, the container supports <NUM> may include scales <NUM>, a syringe pump <NUM>, etc. The scales <NUM> may be configured to weigh the solution container that the scale <NUM> is supporting (i.e., may be another type of sensor for the system <NUM>). The container support <NUM> may be positioned below a bottom end <NUM> of the housing (e.g., as shown in <FIG>), at least in part because the solution containers <NUM> may typically attach to and hang from the container supports <NUM>. However, the container supports <NUM> may be positioned in any suitable location relative to the housing <NUM>. Further, although the depicted embodiment of extracorporeal blood treatment system <NUM> includes four container supports <NUM> and associated solution containers <NUM>, other embodiments of an extracorporeal blood treatment system as described herein may include one or more container supports <NUM> and associated solution containers <NUM> such as, e.g., as few as two container supports <NUM> and associated solution containers <NUM>, three container supports <NUM> and associated solution containers <NUM>, four or more container supports <NUM> and associated solution containers <NUM>, etc..

In the embodiment shown, the solution containers <NUM> may be in the form of, e.g., flexible polymeric bags configured to hold liquids or a syringe <NUM>. Solution containers <NUM>, however, used in connection with the exemplary extracorporeal blood treatment systems described herein may take any suitable form in which liquids can be stored and weighed by any scale or weighing apparatus, e.g., bottles, tanks, cartons, jugs, etc..

In one or more embodiments, the system <NUM> may provide an indication that a solution container <NUM> attached to a container support <NUM> including a scale <NUM> has passed a selected weight limit as a part of monitoring the status of the solution containers <NUM>. That selected weight limit may, in the case of a solution container <NUM> used to collect liquids from the extracorporeal blood treatment system, be an upper limit such that passing (e.g., reaching and/or exceeding) the selected weight limit is an indication that the solution container <NUM> is reaching or has reached its loading capacity and may need to be replaced with a solution container <NUM> having more capacity to collect liquid. In the case of a solution container <NUM> used to supply liquids to the extracorporeal blood treatment system, the selected weight limit may be a lower limit such that passing (e.g., reaching and/or falling below) the selected weight limit is an indication that the solution container <NUM> is reaching or has reached a level at which the solution container <NUM> may need to be replaced with a fresh solution container <NUM> containing additional liquid to be supplied to the extracorporeal blood treatment system <NUM>.

As shown in <FIG>, the system <NUM> may include an indicator <NUM>, <NUM> associated with (e.g., positioned proximate) each of the solution containers <NUM> and each of the container supports <NUM>, respectively. Each of the indicators <NUM>, <NUM> may represent unique information (e.g., retrieved from a library or database) pertaining to the solution container <NUM> or container support <NUM> for which it is associated. For example, the indicator <NUM> associated with a solution container <NUM> may identify a citrate solution, a replacement solution, a dialysis solution, infusion fluid, etc. and the indicator <NUM> associated with a container support <NUM> may identify a pre-blood pump scale, a dialysate scale, a replacement scale, etc..

Specifically, each solution container <NUM> (e.g., reservoirs, syringes <NUM>, etc.) may include a machine readable solution indicator <NUM> configured to identify solution in the solution container <NUM>. For example, the machine readable solution indicator <NUM> may contain data or information relevant to the solution container <NUM> for which it is associated. Specifically, the data or information from the machine readable solution indicator <NUM> may describe the type of solution or the concentration of a specific solution. The machine readable solution indicator <NUM> may take any suitable form and size. For example, the machine readable solution indicator <NUM> may include a barcode (e.g., Unique Identification Barcode (UDI), etc.), a QR code, RFID tags/devices, Near Field Communication (NFC) tags/devices, visions systems with object recognition software, etc. The machine readable solution indicator <NUM> may be located anywhere on the solution container <NUM> to associate the machine readable solution indicator <NUM> with the solution container <NUM>. In one or more embodiments, the machine readable solution indicator <NUM> may be located on packaging used to store and/or transport the solution container <NUM>.

In one or more embodiments, the solution container <NUM> may include a syringe <NUM> that has an indicator <NUM> to identify the type of solution (e.g., calcium or heparin) contained therein. Similar to other solution containers <NUM> described herein, the indicator <NUM> associated with the syringe <NUM> may be used to compare the solution within the syringe <NUM> (e.g., defining a concentration of calcium or heparin) with the solution expected by the system <NUM> for a specific therapy. Therefore, the actual syringe solution may be compared with the expected syringe solution and verified by the system <NUM>.

Similarly, each container support <NUM> (e.g., scales, syringe pumps <NUM>, etc.) may include a machine readable support indicator <NUM> configured to identify the container support <NUM>. For example, the machine readable support indicator <NUM> may contain data or information relevant to the container support <NUM> for which it is associated. Specifically, the data or information from the machine readable support indicator <NUM> may describe the type of support and, e.g., which type of solution container <NUM> should be supported thereon. The machine readable support indicator <NUM> may take any suitable form and size. For example, the machine readable solution indicator <NUM> may include a barcode (e.g., Unique Identification Barcode (UDI), etc.), a QR code, RFID tags/devices, Near Field Communication (NFC) tags/devices, visions systems with object recognition software, Bluetooth, etc. The machine readable support indicator <NUM> may be located anywhere on the system <NUM> to readily associate the machine readable support indicator <NUM> with the corresponding container support <NUM>. For example, as shown in <FIG>, the machine readable support indicator <NUM> may be physically located on the container support <NUM>. As shown in <FIG>, the machine readable support indicator <NUM> may be located on the housing <NUM> at a location proximate the corresponding container support <NUM>. In one or more embodiments, each machine readable support indicator <NUM> may be located such that it is closer to the corresponding container support <NUM> than any other container support <NUM>.

Further, the system <NUM> may include a sensor <NUM> configured to read one or both of the machine readable solution indicator <NUM> and the machine readable support indicator <NUM>. Thereafter, the sensor <NUM> may transmit the data or information (e.g., one or more signals) read from the indicators <NUM>, <NUM> to the computing apparatus <NUM> to identify the components associated with the read indicators <NUM>, <NUM>. The sensor <NUM> may be any suitable device configured to capture and relay the data or information contained within the indicators <NUM>, <NUM>. For example, the sensor <NUM> may be described as a scanner, a reader, a camera, Near Field Communication (NFC) device, etc..

In one or more embodiments, the computing apparatus <NUM> may interpret the data or information obtained from the indicators <NUM>, <NUM> through a database or library. In one or more embodiments, a user may modify the database or library (e.g., using a template in the system configurations) to include additional or new solution compositions (e.g., with various concentrations of constituents in each of the additional or new solutions). Further, in one or more embodiments, each solution may be associated with a specific part number or portion of an indicator (e.g., barcode, QR code, NFC tag, etc.) that helps to verify the information conveyed by the indicator. Verification of the information (i.e., by using error correction, redundancy, etc.) received from the indicator may be important to help prevent the information from being misread and incorrectly identified.

Additionally, in one or more embodiments, information or data tied to the indicator associated with a solution may also include, e.g., lot numbers, date of manufacturing, expiry date, etc. This information may be utilized by the system to identify the source and lifespan of a particular solution to, e.g., prevent use of an expired product. Verification of this additional information may also be important to avoid misreading and/or erroneously discarding a solution based on this information.

The sensor <NUM> may be described as an input apparatus <NUM> as it pertains to <FIG>. Therefore, the sensor <NUM> may be operably coupled to the computing apparatus <NUM>/<NUM> such that the sensor <NUM> may transmit signals to the computing apparatus <NUM>/<NUM>. Additionally, a connection <NUM> may be provided between the sensor <NUM> and the housing <NUM> to operably couple the sensor <NUM> to the computing apparatus <NUM>/<NUM>. For example, the connection <NUM> may include an electrical connection or a wireless connection.

Further, in one or more embodiments, the sensor <NUM> may be movable relative to the housing <NUM> and, in other embodiments, the sensor <NUM> may be fixed relative to the housing <NUM>. For example, in such embodiments that the sensor <NUM> may be movable relative to the housing <NUM> (and, e.g., only limited in movement by the length of the wired electrical connection or range of the wireless connection), the sensor <NUM> may move to a location and orientation necessary to scan or read the indicators <NUM>, <NUM>. When the sensor <NUM> is fixed relative to the housing <NUM>, the indicators <NUM>, <NUM> may be moved to a location and orientation such that the indicators <NUM>, <NUM> may be scanned or read by the sensor <NUM>. For example, because the solution containers <NUM> are replaceable and, therefore, movable, each solution container <NUM> may be moved to a location to be read or scanned prior to being installed in the system <NUM>. On the other hand, the container supports <NUM> are often fixed or have limited mobility relative to the housing <NUM>. As such, in one or more embodiments, data or information to identify a container support <NUM> may be transmitted to the computing apparatus <NUM> without scanning or reading a machine readable support indicator <NUM>, as will be described later herein.

While the illustrative embodiment of a renal insufficiency treatment system in the form of an extracorporeal blood treatment system <NUM> is depicted and described in connection with <FIG>, one illustrative embodiment of a renal insufficiency treatment system in the form of a peritoneal dialysis system <NUM>' is depicted in <FIG>. The system <NUM>' includes computing apparatus contained in housing <NUM>', pumps <NUM>', a disposable element <NUM>', sensor <NUM>', and a user interface <NUM>' (which may, as described herein, be both a display and an input device (e.g., a touchscreen, etc.)).

The system <NUM>' may include container supports <NUM>' to support containers <NUM>' containing one or more solutions used to prepare a peritoneal dialysis solution in container <NUM>' that is to be delivered to the peritoneal cavity of a patient P to perform peritoneal dialysis. Each of container supports <NUM>' may include an indicator <NUM>' associated with a selected container support <NUM>'. Each of the containers <NUM>' and <NUM>' may include a machine readable solution indicator <NUM>' configured to, e.g., identify a solution in the container <NUM>'/<NUM>'.

The pumps <NUM>' may be used to move liquids through the system as part of a treatment process, including moving solutions from the containers <NUM>' to container <NUM>' and/or from container <NUM>' to the patient P.

System <NUM>' further includes a sensor <NUM>' and connection <NUM>' connecting sensor <NUM>' to a housing <NUM>' of the system <NUM>', the sensor <NUM>' configured to read the machine readable solution indicators <NUM>' on the solution containers <NUM>'/<NUM>' as described herein. The sensor <NUM>' may further be configured to read the machine readable indicators <NUM>' on the container supports <NUM>'to identify the container support <NUM>' as described herein.

As shown in <FIG> and as related to <FIG> and <FIG>, the treatment apparatus <NUM> may be operatively coupled, or connected, to the computing apparatus <NUM>. The treatment apparatus <NUM> operably coupled to the computing apparatus <NUM> may include the pumps <NUM>/<NUM>' and container supports <NUM>/<NUM>' as shown in <FIG> and <FIG>. Further, the input apparatus <NUM> operably coupled to the computing apparatus <NUM> may include the sensor <NUM>/<NUM>'. For example, the computing apparatus <NUM> may be configured to receive one or more signals (e.g., data or information, solution signal, support signal, etc.) from the sensor <NUM>/<NUM>' to identify the solution container <NUM>/<NUM>' and/or the container support <NUM>/<NUM>'.

The computing apparatus <NUM> may be configured to verify solutions prior to therapy in various different ways, for example, as shown in the illustrative methods depicted in <FIG> and <FIG>. For example, as shown in method of <FIG>, the computing apparatus <NUM> may be configured to identify the solution containers <NUM>/<NUM>' and the associated container supports <NUM>/<NUM>', and then identify the possible therapy treatments based on those identified solutions and supports. In other words, at the time of setup, the user may be requested to scan (e.g., using the sensor <NUM>/<NUM>') the indicator <NUM>/<NUM>' associated with a solution container <NUM>/<NUM>' followed by scanning the indicator <NUM>/<NUM>' associated with a container support <NUM>/<NUM>' (or vice versa) upon which the solution container <NUM>/<NUM>' will be supported. The system <NUM> may be configured to provide the user with applicable therapies (e.g., through a display) for that specific solution container <NUM>/<NUM>' positioned on that specific container support <NUM>/<NUM>'.

For example, if the system is an extracorporeal blood treatment system with solution containers <NUM> including dialysate solution were supported on the replacement and dialysate scales or supports <NUM>, the system <NUM> may suggest or display a continuous veno-venous hemodialysis (CVVHD) therapy, and if a solution container <NUM> including citrate solution was supported on the pre-blood pump scale, the system <NUM> may suggest or display citrate-calcium anticoagulation or citrate only anticoagulation.

Specifically, the computing apparatus <NUM> may be configured to identify <NUM> solution in the solution container <NUM>/<NUM>'. In one or more embodiments, the computing apparatus <NUM> may be configured to identify the solution in the solution container <NUM>/<NUM>' based on a solution signal received from the sensor <NUM>/<NUM>' in response to reading the machine readable solution indicator <NUM>/<NUM>' associated with the solution container <NUM>/<NUM>'. In other words, the sensor <NUM>/<NUM>' may read or scan the machine readable solution indicator <NUM>/<NUM>' located on or associated with the solution container <NUM>/<NUM>' and generate a solution signal that may be sent to the computing apparatus <NUM>.

Also, the computing apparatus <NUM> may be configured to identify <NUM> the container support <NUM>/<NUM>'. For example, the computing apparatus <NUM> may be configured to identify <NUM> the container support <NUM>/<NUM>' based on a support signal received by the computing apparatus <NUM>. The support signal may be generated in any suitable way. In one or more embodiments, the support signal may be generated by the sensor <NUM>/<NUM>' reading or scanning the machine readable support indicator <NUM>/<NUM>' associated with the container support <NUM>/<NUM>'. In other words, the container support <NUM>/<NUM>' may be identified (e.g., by the computing apparatus <NUM>) based on the support signal received from the sensor <NUM>/<NUM>' in response to reading the machine readable support indicator <NUM>/<NUM>'.

In other embodiments, the container support <NUM>/<NUM>' may be operably coupled to the computing apparatus <NUM> and configured to provide the support signal to the computing apparatus <NUM> (e.g., without the use of the sensor <NUM>/<NUM>'). In other words, the system <NUM>/<NUM>' may be configured to identify the container support <NUM>/<NUM>' during the process of loading the container support <NUM>/<NUM>' with a solution container <NUM>/<NUM>' (e.g., when replacing the solution container <NUM>/<NUM>'). For example, the container support <NUM>/<NUM>' may be movable between an open configuration and a closed configuration, and the support signals may be generated based on moving the container support <NUM>/<NUM>' between configurations. As shown in <FIG>, container support 130b is in the open configuration and configured to receive a solution container 132b and container support 130a is in the closed configuration with a solution container 132a supported thereon.

In one or more embodiments, the support signals for each container support <NUM>/<NUM>' of the plurality of container supports <NUM>/<NUM>' may be generated by moving each container support <NUM>/<NUM>' between the open configuration and the closed configuration. For example, the support signal may be generated when the container support <NUM>/<NUM>' moves from the closed configuration to the open configuration, the support signal may be generated when the container support <NUM>/<NUM>' moves from the open configuration to the closed configuration, or the support signal may be generated when the container support <NUM>/<NUM>' moves from the closed configuration to the open configuration and back to the closed configuration. Specifically, when the container support <NUM>/<NUM>' is placed in a position to receive a solution container <NUM>/<NUM>' (e.g., when moved to or positioned in an open or unlocked position, etc.), the system <NUM>/<NUM>' may identify that specific container support <NUM>/<NUM>'. In other words, due to an act of opening the container support <NUM>/<NUM>' to receive a solution container <NUM>/<NUM>', the system <NUM>/<NUM>' may associate that container support <NUM>/<NUM>' with the solution container <NUM>/<NUM>' identified immediately before or after the act of opening the container support <NUM>/<NUM>'. As such, this feature may eliminate the need to receive data or information from (e.g., via scanning or reading) an indicator <NUM>/<NUM>' associated with the container support <NUM>/<NUM>' (e.g., because the act of opening or unlocking automatically transmits that data or information). It is noted that, in one or more embodiments, the generation of the support signal may be connected to the container support <NUM>/<NUM>' sensing a solution container <NUM>/<NUM>' loaded thereon (e.g., using a weight sensor).

Further, the method illustrated in <FIG> may include attaching <NUM> the solution container <NUM>/<NUM>' to the container support <NUM>/<NUM>'. In other words, after each of the solution container <NUM>/<NUM>' and the container support <NUM>/<NUM>' are identified, the identified solution container <NUM>/<NUM>' may be attached to the identified container support <NUM>/<NUM>' in an operating position. Thereafter, the computing apparatus <NUM> may be configured to associate <NUM> the solution in the identified solution container <NUM>/<NUM>' with the identified container support <NUM>/<NUM>'. In one or more embodiments, the computing apparatus <NUM> may be configured to associate the identified solution with the identified container support <NUM>/<NUM>' for the first support signal received after the solution signal is received (e.g., by the computing apparatus <NUM>) for the identified solution. In other words, after the solution container <NUM>/<NUM>' is identified by the computing apparatus <NUM>, the next support signal received by the computing apparatus <NUM> associates the identified solution container <NUM>/<NUM>' with the identified container support <NUM>/<NUM>' (e.g., based on the support signal). In other embodiments, the container support <NUM>/<NUM>' may be identified first and the solution signal generated thereafter may associate the identified solution container <NUM>/<NUM>' (e.g., from the solution signal) with the identified container support <NUM>/<NUM>'.

As described herein, the container supports <NUM>/<NUM>' may include a scale <NUM>/<NUM>' configured to weigh a solution container <NUM>/<NUM>' supported on the container support <NUM>/<NUM>'. In one or more embodiments, each container support <NUM>/<NUM>' may be operably coupled to the computing apparatus <NUM> such that the computing apparatus <NUM> is configured to receive a weight signal from each container support <NUM>/<NUM>' that is indicative of a weight of a solution container <NUM>/<NUM>' on the container support <NUM>/<NUM>'. Further, the computing apparatus <NUM> may be configured to associate an identified solution container <NUM>/<NUM>' with an identified container support <NUM>/<NUM>' only if, after identifying a solution and identifying a container support <NUM>/<NUM>', the weight signal is received from the identified container support <NUM>/<NUM>' before a subsequent solution signal or a subsequent support signal is received by the computing apparatus <NUM>. In other words, the computing apparatus <NUM> may confirm that the container support <NUM>/<NUM>' actually received the solution container <NUM>/<NUM>' that was identified (e.g., due to the change in weight).

After associating <NUM> the solution of the identified solution container <NUM>/<NUM>' with the identified container support <NUM>/<NUM>', the method may include querying <NUM> whether any additional solution containers <NUM>/<NUM>' will be added. If more solution containers <NUM>/<NUM>' are yet to be added to the system <NUM>/<NUM>', the method returns to the step of identifying <NUM> the solution in the next solution container <NUM>/<NUM>'. If there are no additional solution containers <NUM>/<NUM>' to add to the system <NUM>/<NUM>', the method proceeds to identifying <NUM> possible therapy treatments. In one or more embodiments, the step of querying <NUM> whether additional solution containers <NUM>/<NUM>' will be added may be shown to the user on the display <NUM>/<NUM>'. In one or more embodiments, the user may respond to the query using an input apparatus <NUM> such as, e.g., keyboard, touchscreen, sensor, etc. For example, in one or more embodiments, the user may scan or read (e.g., using the sensor <NUM>/<NUM>') an indicator <NUM> associated with the next solution container <NUM>/<NUM>' to affirmatively respond that an additional solution will be added, thereby restarting the process of identifying solution containers <NUM>/<NUM>' and container supports <NUM>/<NUM>'.

Therefore, in one or more embodiments, the system <NUM>/<NUM>' may identify and associate one or more pairs of solution containers <NUM>/<NUM>' and container supports <NUM>/<NUM>'. For example, receiving one or more signals from the sensor <NUM>/<NUM>' may include receiving a first pair of consecutive support and solution signals (e.g., from the sensor <NUM>/<NUM>'). While the pair of signals may be described as consecutive, the signals may be received in any suitable order (e.g., support signal first and solution signal second or solution signal first and support signal second). Further, identifying a container support <NUM>/<NUM>' and identifying a solution container <NUM>/<NUM>' may include identifying a first pair of container support <NUM>/<NUM>' and solution container <NUM>/<NUM>' based on the first pair of consecutive support and solution signals. Further yet, associating the identified solution container <NUM>/<NUM>' with the identified container support <NUM>/<NUM>' may include associating the first identified solution container <NUM>/<NUM>' with the first identified container support <NUM>/<NUM>'.

Similarly, the system <NUM>/<NUM>' may identify and associate a second pair of solution containers <NUM>/<NUM>' and container supports <NUM>/<NUM>'. For example, receiving one or more signals from the sensor may include receiving a second pair of consecutive support and solution signals (e.g., from the sensor <NUM>/<NUM>'). Further, identifying a container support <NUM>/<NUM>' and identifying a solution container <NUM>/<NUM>' may include identifying a second pair of container support <NUM>/<NUM>' and solution container <NUM>/<NUM>' based on the second pair of consecutive support and solution signals. Further yet, associating the identified solution container <NUM>/<NUM>' with the identified container support <NUM>/<NUM>' may include associating the second identified solution container <NUM>/<NUM>' with the second identified container support <NUM>/<NUM>'.

Once all of the solution containers <NUM>/<NUM>' and the container supports <NUM>/<NUM>' are identified <NUM>, <NUM> and associated <NUM>, the computing apparatus <NUM> may be configured to identify <NUM> one or more possible treatments based at least in part on the association between the identified solution (e.g., from the identified solution container <NUM>/<NUM>') and the identified container support <NUM>/<NUM>'. Further, in one or more embodiments, the computing apparatus <NUM> may be configured to identify the possible treatments based on any number of pairs (e.g., the first and second pairs as described herein) of associated identified solution containers <NUM>/<NUM>' and identified container supports <NUM>/<NUM>'. In one or more embodiments, the one or more possible treatments may be shown and/or selectable from the display <NUM>/<NUM>'. The computing apparatus <NUM> may be configured to allow the user to make a selection of the desired therapy treatment. For example, the user may use an input device (e.g., using a touchscreen or any other suitable input apparatus <NUM>) of the input apparatus <NUM> that is operably coupled to the computing apparatus <NUM> to make the selection because, for example, the computing apparatus <NUM> may be configured to receive a signal from the input device identifying the selected treatment.

After desired therapy treatment is selected, the computing apparatus <NUM> may be configured to verify <NUM> whether the identified solution container <NUM>/<NUM>' and the identified container support <NUM>/<NUM>' are compatible with the selected treatment to be performed by the system <NUM>/<NUM>'. In one or more embodiments, this verification process may be based at least in part on the association between the identified solution container <NUM>/<NUM>' and the identified container support <NUM>/<NUM>'. If the computing apparatus <NUM> determines that the identified solution container <NUM>/<NUM>' associated with the identified container support <NUM>/<NUM>' is not compatible with the selected treatment, the computing apparatus <NUM> may activate <NUM> an alert apparatus. The alert apparatus may be any suitable alert (e.g., visual, audial, tactile, etc.) that notifies the user of the potential lack of compatibility. The alert apparatus may be located at any position on the system that may assist the user in noticing the alert. For example, the alert apparatus may be shown on the display <NUM>/<NUM>', on the housing <NUM>, proximate the container supports <NUM>/<NUM>', etc. If the computing apparatus <NUM> determines that the identified solution container <NUM>/<NUM>' associated with the identified container support <NUM>/<NUM>' is compatible with the selected treatment, the computing apparatus <NUM> may activate <NUM> a notice that the associated solutions and container supports <NUM>/<NUM>' are compatible with the selected treatment. The notice of compatibility may use the same alert apparatus, however with a different notifier, or may inform the user using something different than the alert apparatus.

As described above, another type of verification process is shown as method <NUM> in <FIG>. For example, the computing apparatus <NUM> may receive input from the user selecting a specific therapy treatment before identifying the solution containers <NUM>/<NUM>' and the associated container supports <NUM>/<NUM>', and then the computing apparatus <NUM> may be configured to determine whether the selected therapy treatment is compatible with the identified solutions and supports. In other words, the user may enter one or more of a prescription, a method of anti-coagulation, prescribed flow rates and expected solutions (e.g., parameters of a specific therapy), and the system <NUM>/<NUM>' may identify whether a specific solution container <NUM>/<NUM>' and a specific container support <NUM>/<NUM>' (e.g., identified through the indicator <NUM>/<NUM>', <NUM>/<NUM>') are in conflict with the users selections.

For example, method <NUM> may include steps that are similar or identical to steps described for method illustrated in <FIG>. However, method <NUM> includes selecting <NUM> a treatment therapy prior to identifying and associating container supports <NUM>/<NUM>' and solution containers <NUM>/<NUM>'. For example, the user may select a desired treatment using an input device (e.g., using a touchscreen or any other suitable input apparatus <NUM>) of the input apparatus <NUM> that is operably coupled to the computing apparatus <NUM>. Thereafter, the computing apparatus <NUM> may be configured to identify <NUM> the container support <NUM>/<NUM>' (e.g., through a machine readable support indicator <NUM>/<NUM>', through movement of the container support <NUM>/<NUM>', etc.) and identify <NUM> solution in the solution container <NUM>/<NUM>' (e.g., through a machine readable solution indicator <NUM>/<NUM>'). The solution container <NUM>/<NUM>' may then be attached <NUM> to the container support <NUM>/<NUM>' and the computing apparatus <NUM> may associate <NUM> the solution in the identified solution container <NUM>/<NUM>' with the identified container support <NUM>/<NUM>'.

Further, the computing apparatus <NUM> may verify <NUM> whether the associated solution container <NUM>/<NUM>' and container support <NUM>/<NUM>' are compatible with the pre-selected therapy treatment. If the associated solution container <NUM>/<NUM>' and container support <NUM>/<NUM>' are not compatible with the selected treatment, an alert apparatus is activated <NUM>. In other words, the system <NUM>/<NUM>' may be configured to display a graphic (e.g., on the graphical user interface) that provides feedback (e.g., through a marking representing a correct matching or incorrect matching) to the user during the process regarding whether the components being used are compatible for a specific therapy. Further, if a conflict arises, the system <NUM>/<NUM>' may request that either one of the parameters of the specific therapy are changed or the specific solution container <NUM>/<NUM>'/container support <NUM>/<NUM>' is changed (e.g., to align the solution container <NUM>/<NUM>' with the prescribed solution). In one or more embodiments, the system <NUM>/<NUM>' may be configured to suggest alterations to correct any conflict. If the associated solution container <NUM>/<NUM>' and container support <NUM>/<NUM>' are compatible with the selected treatment, a notice is activated <NUM> indicating that the associated solution and container support <NUM>/<NUM>' are compatible with the selected treatment. In one or more embodiments in which the remainder of the system is ready, a treatment could be initiated and/or resumed upon confirmation that the associated solution and container support <NUM>/<NUM>' are compatible with the selected treatment.

With reference to <FIG>, the computing apparatus <NUM> used in the renal insufficiency systems described herein may include data storage <NUM> to, e.g., allow for access to processing programs or routines <NUM> and one or more other types of data <NUM> that may be employed to carry out exemplary methods and/or processes (e.g., running pumps, identifying solutions and/or containers, associating solutions with containers, verifying compatibility with selected treatment, running a treatment, determining problems with a treatment, exchanging/changing containers/reservoirs, notifying operators/users of problems, displaying status information, etc.) for use in performing renal insufficiency treatments. For example, the computing apparatus <NUM> may be configured to identify solution containers and container supports, associating the identified solutions and supports, and verifying the compatibility of each with a selected treatment (e.g., described above with respect to <FIG>).

The computing apparatus <NUM> may be operatively coupled to the input apparatus <NUM> and the display apparatus <NUM> to, e.g., transmit data to and from each of the input apparatus <NUM> and the display apparatus <NUM>. For example, the computing apparatus <NUM> may be electrically coupled to each of the input apparatus <NUM> and the display apparatus <NUM> using, e.g., analog electrical connections, digital electrical connections, wireless connections, bus-based connections, etc. As described further herein, an operator may provide input to the input apparatus <NUM> to manipulate, or modify, one or more graphical depictions displayed on the display apparatus <NUM> to select and view various information such as, for example, identified solutions, identified supports, and treatment options/selections as described herein.

Further, various devices and apparatus may be operatively coupled to the computing apparatus <NUM> to be used with the computing apparatus <NUM> to perform one or more renal insufficiency procedures/treatments as well as the functionality, methods, and/or logic described herein. As shown, the system <NUM> may include input apparatus <NUM>, display apparatus <NUM>, and treatment apparatus <NUM> operatively coupled to the computing apparatus <NUM> (e.g., such that the computing apparatus <NUM> may be configured to use information, or data, from the apparatus <NUM>, <NUM>, <NUM> and provide information, or data, to the apparatus <NUM>, <NUM>, <NUM>). The input apparatus <NUM> may include any apparatus capable of providing input to the computing apparatus <NUM> to perform the functionality, methods, and/or logic described herein.

For example, the input apparatus <NUM> may include a touchscreen (e.g., capacitive touchscreen, a resistive touchscreen, a multi-touch touchscreen, etc.), a mouse, a keyboard, a trackball, etc. For example, the input apparatus <NUM> may allow an operator to interact with a graphical user interface including a configuration region for selecting a treatment therapy, which is either based on or verified as compatible with identified solutions and supports as described herein when used in conjunction with the display apparatus <NUM> (e.g., displaying the graphical user interface).

The display apparatus <NUM> may include any apparatus capable of displaying information to an operator, such as a graphical user interface, etc., to perform the functionality, methods, and/or logic described herein. For example, the display apparatus <NUM> may include a liquid crystal display, an organic light-emitting diode screen, a touchscreen, etc. As described further herein, the display apparatus <NUM> may be configured to display a graphical user interface that includes one or more regions such as a configuration for configuring treatment therapies compatible with identified solutions and supports as well as various other regions and areas.

The processing programs or routines <NUM> may include programs or routines for performing computational mathematics, matrix mathematics, standardization algorithms, comparison algorithms, or any other processing required to implement one or more exemplary methods and/or processes described herein. Data <NUM> may include, for example, solution types/concentrations, support types, treatment therapies, patient weight data, container/reservoir mass data, pump data, pump stoppage data, alarm data, fluid data, other flow rates, fluid volumes, heuristics indicative of malfunction, graphics (e.g., graphical elements, icons, buttons, windows, dialogs, pull-down menus, graphic areas, graphic regions, 3D graphics, etc.), graphical user interfaces, results from one or more processing programs or routines employed according to the disclosure herein, or any other data that may be necessary for carrying out the one and/or more processes or methods described herein.

In one or more embodiments, the system <NUM> may be implemented using one or more computer programs executed on programmable computers, such as computers that include, for example, processing capabilities, data storage (e.g., volatile or non-volatile memory and/or storage elements), input devices, and output devices. Program code and/or logic described herein may be applied to input data to perform functionality described herein and generate desired output information. The output information may be applied as input to one or more other devices and/or methods as described herein or as would be applied in a known fashion.

The program used to implement the methods and/or processes described herein may be provided using any programmable language, e.g., a high-level procedural and/or object orientated programming language that is suitable for communicating with a computer system. Any such programs may, for example, be stored on any suitable device, e.g., a storage media, that is readable by a general or special purpose program running on a computer system (e.g., including processing apparatus) for configuring and operating the computer system when the suitable device is read for performing the procedures described herein. In other words, at least in one embodiment, the system <NUM> may be implemented using a computer readable storage medium, configured with a computer program, where the storage medium so configured causes the computer to operate in a specific and predefined manner to perform functions described herein. Further, in at least one embodiment, the system <NUM> may be described as being implemented by logic (e.g., object code) encoded in one or more non-transitory media that includes code for execution and, when executed by a processor, is operable to perform operations such as the methods, processes, and/or functionality described herein.

The computing apparatus <NUM> may be, for example, any fixed or mobile computer system (e.g., a controller, a microcontroller, a personal computer, minicomputer, etc.). The exact configuration of the computing apparatus <NUM> is not limiting, and essentially any device capable of providing suitable computing capabilities and control capabilities (e.g., receiving information from indicator, associating identified components, control of renal insufficiency treatment system (e.g., one or more pumps, etc.), etc.) may be used.

As described herein, a digital file may be any medium (e.g., volatile or non-volatile memory, a CD-ROM, etc.) containing digital bits (e.g., encoded in binary, trinary, etc.) that may be readable and/or writeable by computing apparatus <NUM> described herein. Also, as described herein, a file in user-readable format may be any representation of data (e.g., ASCII text, binary numbers, hexadecimal numbers, decimal numbers, graphically, etc.) presentable on any medium readable and/or understandable by an operator.

In view of the above, it will be readily apparent that the functionality as described in one or more embodiments according to the present disclosure may be implemented in any manner as would be known to one skilled in the art. As such, the computer language, the computer system, or any other software/hardware which is to be used to implement the processes described herein shall not be limiting on the scope of the systems, processes or programs (e.g., the functionality provided by such systems, processes or programs) described herein.

The methods and/or logic described in this disclosure, including those attributed to the systems, or various constituent components, may be implemented, at least in part, in hardware, software, firmware, or any combination thereof. For example, various aspects of the techniques may be implemented within one or more processors, including one or more microprocessors, DSPs, ASICs, FPGAs, or any other equivalent integrated or discrete logic circuitry, as well as any combinations of such components, or other devices.

Such hardware, software, and/or firmware may be implemented within the same device or within separate devices to support the various operations and functions described in this disclosure. In addition, any of the described components may be implemented together or separately as discrete but interoperable logic devices. Depiction of different features, e.g., using block diagrams, etc., is intended to highlight different functional aspects and does not necessarily imply that such features must be realized by separate hardware or software components. Rather, functionality may be performed by separate hardware or software components or integrated within common or separate hardware or software components.

Claim 1:
A renal insufficiency treatment system comprising:
a renal insufficiency treatment apparatus comprising a plurality of container supports;
a plurality of solution containers configured to be supported by the plurality of container supports, wherein each solution container comprises a machine readable solution indicator configured to identify solution in the solution container;
a plurality of machine readable support indicators, wherein each machine readable support indicator of the plurality of machine readable support indicators is associated with and configured to identify one container support of the plurality of container supports;
a sensor configured to read the machine readable solution indicators on solution containers and to read the machine readable support indicators associated with the container support;
computing apparatus comprising one or more processors, the computing apparatus operably coupled to the renal insufficiency treatment apparatus and the sensor, wherein the computing apparatus is configured to:
receive one or more signals from the sensor;
identify a container support of the plurality of container supports based on a support signal received by the computing apparatus, wherein the container support is identified based on the support signal received from the sensor in response to reading the machine readable support indicator associated with the container support;
identify solution in a solution container of the plurality of solution containers based on a solution signal received from the sensor in response to reading the machine readable solution indicator associated with the solution container, the solution signal being received by the computing apparatus;
associate the identified solution with the identified container support;
verify, based at least in part on the association between the identified solution and the identified container support, that the identified solution in the solution container associated with the identified container support is compatible with a selected treatment to be performed by the renal insufficiency treatment system; and
activate an alert apparatus if the identified solution in the solution container associated with the identified container support is not compatible with the selected treatment.