Last updated 2/1/2026.

Version history, updates, and known issues.

Background

The IV Infusion Compatibility Auto-Compiler (IVICAC) is a web-based clinical tool designed to streamline complex medication management. By dynamically grouping infusions into compatible configurations, it minimizes unnecessary lumen usage while strictly adhering to safety standards. Whether you are managing high-volume resuscitation or routine maintenance, the tool adapts to real-world bedside workflows through its Stacked and Separated modes. This interface simplifies the cognitive load of compatibility mapping, saves critical time during titration, and enhances patient safety through an intuitive, data-driven compiler.

Why Does the App Suggest Approximately Sets of 3 Max?

While the backtracking algorithm can technically organize up to five medications per line, the Auto-Compiler defaults to a "Rule of Three" safety threshold. This limit reflects clinical evidence that beyond three concurrent infusions, the risk of unpredictable pH shifts and micro-precipitation rises substantially and “ dead-space volume” becomes problematic.

Separated versus Stacked Modes

Separated Mode (Concurrent Safety)

Separated Mode enforces the strictest compatibility rules for scenarios where multiple infusions must run at the same time. In this mode, every single medication within a lumen must be mutually compatible. If any two medications are incompatible or have variable compatibility data, the algorithm will automatically isolate them into different lumens.

For example, if a patient requires Norepinephrine, Vancomycin, and Zosyn concurrently, the compiler will check the compatibility of all three against each other. If the antibiotics are incompatible, they will be assigned to separate lumens regardless of their compatibility with the norepinephrine. This is the preferred mode for patients requiring multiple continuous infusions or simultaneous antibiotic therapy.

Stacked Mode (Sequential Optimization)

Stacked Mode is built for maximizing lumen efficiency by accommodating multiple secondary infusions on a single line. This mode operates on the clinical assumption that secondaries, such as intermittent antibiotics or electrolyte boluses, will be administered sequentially rather than simultaneously. Medications in this mode only need to be compatible with the Primary Infusion or the Saline Carrier, effectively ignoring incompatibility between the secondaries themselves.

For example, a patient receiving Vasopressin along with Potassium Phosphate and Magnesium Sulfate can have all three assigned to one lumen. While the electrolytes are mutually incompatible, they are both compatible with the Vasopressin driver. Since they run at different times, they can safely share the line.

Risk-Averse Output vs. Standard Output

The results are presented in two distinct formats to help you choose the level of clinical caution appropriate for your patient. Risk-Averse Output utilizes the strictest compatibility logic by treating all variable or unknown interactions as incompatible. This ensures the highest safety margin, though it may require more lumens to achieve. Conversely, the Standard Output includes variable compatibilities, which may optimize lumen usage but requires the nurse to verify specific concentration and diluent requirements with the pharmacy department before administration.

Instructions for Use

1. Decide between Stacked or Separated Mode.

2. Medication Selection Begin by selecting all relevant medications from the categorized columns. Note that medications designated as Dedicated Line Required will automatically be isolated into their own lumen regardless of other selections.

3. Configuration Settings Adjust the Max Medications per Lumen to match your physical access. If you are using Stacked Mode, look for the Carrier Fluid toggle which appears when secondaries are selected. Checking this will include a Normal Saline Primary placeholder in your results to reflect a standard piggyback setup. Uncheck it if you are utilizing a medication lock or a protocol that does not require a continuous carrier.

4. Review and Verify Click Compile Groupings to generate your configurations. The Risk-Averse Output treats all variable or unknown data as incompatible for maximum safety. The Standard Output includes variable compatibilities but requires a secondary check with pharmacy for specific concentration or diluent requirements. Always use the provided stats summary to quickly identify the total lumens required for your current setup.

Disclaimer: The IV Infusion Compatibility Auto-Compiler is provided strictly as an educational tool for healthcare professionals. This application is intended to demonstrate the logic of medication grouping and does not constitute medical advice or a formal clinical recommendation. While designed to assist with critical care workflows, the database used by this tool contains limited information regarding specific concentrations and diluents. Users must maintain independent clinical judgment and are required to verify all compatibility groupings with their institutional pharmacy department and hospital protocols before administration. The developer and designer assume no liability for any errors, omissions, or adverse patient outcomes resulting from the use of this software. Final clinical decisions should always align with official hospital policy and the most current evidence-based nursing standards.