Compare TPN Compounding Software: MyTotalMix vs Alternatives

Vendor-neutral vs. device-bundled TPN systems

MyTotalMix runs the whole parenteral nutrition workflow. It starts with the physician's prescription, moves to pharmacist verification with automated ESPGHAN dose-limit checks, and ends with the 2-in-1 or 3-in-1 formula going to the compounder over barcode. The point is that it stays a vendor-neutral software layer. It plugs into the compounders and label printers the pharmacy already operates. It also runs standalone, without a HIS integration - orders can be entered directly in the system, and HIS integration is possible over API and arranged individually with each hospital. Baxter Abacus works differently: it is the calculation and compounding software Baxter ships with its ExactaMix compounders (including the current ExactaMix Pro). B. Braun (the APEX compounder paired with Clinus/EasyComp software) and Fresenius Kabi (KabiHelp Pro) follow a similar closed model, selling software together with a specific device line as one package. BD is the exception here: Cato is standalone workflow software that integrates over HL7 with robots from multiple manufacturers (including ARxIUM RIVA, Grifols Kiro, Loccioni Apoteca, and Fresenius PharmaHelper), which puts it architecturally closer to the vendor-neutral model than to device-bundled systems - a different product from MyTotalMix, but a similar vendor-neutral premise. The difference between MyTotalMix and device-bundled systems is mostly architectural: on one side, standalone software; on the other, software tied to buying a particular hardware line.

Software-only or compounder-bundled?

Device-bundled systems bring real upside. One vendor, one service contract, integration tested at the factory. They come with the trade-off you would expect from that model: the pharmacy tends to be locked to one manufacturer's device line, and replacing or growing the compounder fleet usually drags the software along with it. MyTotalMix goes the other way. The software is not pinned to one hardware manufacturer, so a hospital can keep the compounders it already owns and pick its hardware vendor separately from its software vendor. Across tenders and fleet growth, that leaves room to move. In practice it means integration over barcode, OAuth label print services, CSV import and export, and an HIS API, rather than one manufacturer's closed protocol. Vendor-neutral matters most where a hospital runs a mixed equipment fleet or would rather not commit to a single vendor for years.

MyTotalMix vs. device-bundled compounding software

This comparison sits at the category level, not a specific software version. Device-bundled feature sets vary by manufacturer and compounder model.

When to choose MyTotalMix vs. a compounder-bundled system

The right call comes down to procurement strategy, and the feature list is only the second question. A compounder-bundled system like Baxter Abacus can be a solid fit when the hospital is standardizing on one manufacturer's device line, values the simplicity of a single service contract, and has no near-term plan to switch hardware vendors. MyTotalMix earns its place where a pharmacy wants to stay independent. It runs compounders from more than one manufacturer, keeps hardware tenders separate from software, needs ESPGHAN dose limits mapped to its own clinical protocols, and expects the full audit trail and RBAC that larger organizations require. When purchasing flexibility and a clean fit with what the pharmacy already has (HIS, printers, compounders) come first, a software-first approach is a strong fit.