Home/One Formulary
One Formulary · drug library match · runs in your browser

Does every IV entry match a drug library the pump can program?

An aligned formulary auto-programs safely only when each entry matches a drug library entry, in the right care area, within its dose limits. If it cannot match, the order will not resolve and the pump runs in basic mode with no dose limits, which is the safety software switched off without anyone deciding to. This page reconciles an aligned formulary against a drug library export, care area by care area, and flags every entry that will auto-program with limits, drop to basic mode, or needs a review. It is vendor-neutral: bring an export from any pump vendor and map it to the template. It never recommends a dose. The data here is synthetic and nothing is uploaded.

Align the formularyOne Formulary →
Match the drug libraryLibrary Match
→ Reconcile CPOEClose the Loop → Send to the pumpOrder to Pump

How the match works

Each formulary entry is matched to a drug library entry on four things: the drug, the concentration, the care area, and the dose unit family. The result is one of three verdicts.

auto-programs  A library entry exists in this care area, the concentration and units match, and the formulary limits sit inside the library limits. The order resolves and the pump programs with its dose limits on.

basic mode  No library entry for this drug and concentration in this care area, or the concentration differs, or the dose units differ. The order will not resolve, and the fallback is a manual infusion with no dose limits.

review  The entry exists but the limits disagree, or the library holds an entry no one orders. Not a stopper, but a pharmacy and nursing decision.

Two inputs

Both are loaded with a synthetic sample so you can see the match immediately. Replace either with your own CSV to run it for real.

1. Aligned formulary The output of formulary alignment. Same columns as the One Formulary template.
Using the built-in ICU sample (14 entries).
2. Drug library export Your pump drug library, one row per drug and care area, mapped to the template columns.
Using the built-in synthetic library (per care area).

Nothing leaves this browser. Both files are read on your machine. There is no upload and no storage.

Bring your own drug library

No pump vendor publishes its drug library file format, and the editors are proprietary and go to the customer with the pumps. You do not need any of that. Your hospital owns its own library and can export it from its own editor. Map that export onto these neutral columns and the match runs the same way:

care_area, drug_name, concentration_value, concentration_unit, per_volume_ml, units_only, weight_based, dose_unit, dose_default, dose_soft_min, dose_soft_max, dose_hard_min, dose_hard_max

One row per drug and care area. A concentration-independent entry sets units_only to Y. This is a generic model on purpose, so it adapts to any vendor data set; the pump companies each have their own editor (BD, Baxter, ICU Medical, B. Braun), and each exports differently, but every one of them carries a drug, a concentration, a care area, a dose unit and dose limits, which is all the match needs.

Illustrative limits. The dose limits in the sample library are synthetic and are here to make the match real. Each hospital sets its own, per care area, and this page checks whether the formulary and the library agree, never whether a limit is clinically right.

Drug Library Match, by Daniel Pettus. Part of the AI MedAgent research demonstration. Synthetic data only. Advisory only. Not a medical device. Not clinical decision support. Not for clinical use. Open source under the Apache License 2.0. Standards and vendor documents remain the property of their publishers and are cited, not reproduced.