An alignment tool is only as good as the order that reaches the pump. This page takes an aligned continuous-infusion order set, the kind One Formulary passes with no blocking or major findings, and builds the exact HL7 messages that carry one order to an infusion pump gateway and the pump's answer back. Every message is labeled for what is standard, what is representative, and what the standard leaves out. It never recommends a dose. The patient is synthetic and nothing is sent anywhere.
Two sets are built in. Each row is a formulary entry after alignment: one concentration per drug and care area, a national standard concentration, an accepted dose unit, hard and soft limits, a complete titration order sentence where the drug is titratable, and a one-to-one link between an order sentence and a pump library entry. Both sets score zero blocking and zero major findings in One Formulary.
| Drug | Concentration | Care area | Dose unit | Soft | Hard | Titration | Order → library |
|---|
Illustrative limits. The soft and hard limits shown are synthetic and are here to make the messages complete. Each hospital sets its own through its dose error reduction software. This page checks structure, never clinical values.
Pick an order and a synthetic patient. The page assembles the full round trip a bedside auto-program would generate. Nothing is calculated for a patient; the dose you enter is carried into the order exactly as typed.
Confirmed against the source documents. The message types and their fields are the published ones: the infusion order is RGV^O15^RGV_O15 and its acknowledgment RRG^O16^RRG_O16 (IHE Devices Technical Framework Rev 10.0, Communicate Infusion Order [PCD-03], HL7 v2.6); the pump's periodic report is ORU^R01^ORU_R01 (Communicate PCD Data [PCD-01], DEC); the infusion event report is ORU^R42^ORU_R01 (Communicate Infusion Event Data [PCD-10], IPEC). The Delivery Start event carries 680^MDC_EVT_PUMP_DELIV_START^MDC under 188773^MDC_DEV_EVENT_COND^MDC, from the IPEC supplement's own sample message.
Representative, and to be validated before any real use. The patient–device association step is not an IHE transaction at all: the Devices Technical Framework places patient-device association out of scope, so in practice that binding is created by a barcode scan of the patient wristband and the pump or channel at the bedside. It is shown here so the round trip is complete, marked out of scope. The MDC nomenclature codes in the observation rows, other than the two Delivery Start codes above, are shown by their mnemonic; their numeric REFIDs must be confirmed against IEEE 11073-10101 and the current Rosetta Terminology Mapping value set before a message goes near a device.
The drug library does not travel in the order. A pump's dose limits live in its own library, versioned by care area profile, and nothing in the order transaction guarantees the pump will accept what it is sent. The order sentence and library-entry identifiers are carried here as an implementation reference, not as a field the framework mandates.
No flow in mL/hr is computed. A production DEC message also reports the volumetric flow. Deriving it from a dose needs the concentration and, for weight-based orders, the patient weight, so this page reports the ordered rate with its concentration basis rather than a computed number, to avoid implying a dose calculation.
IHE Devices Technical Framework Rev 10.0, Final Text, 4 November 2024, Volumes 1 and 2 (PCD-03, PCD-01). · IHE Patient Care Device Infusion Pump Event Communication (IPEC) supplement, Rev 1.4, and PCD TF Rev 9.0 Final Text (PCD-10). · HL7 Version 2.6, Chapter 4, Order Entry. · ISO/IEEE 11073-10101 nomenclature and the IHE Rosetta Terminology Mapping value set. · ASHP Standardize 4 Safety, Adult Continuous Infusion Standards, June 2026 revision. · ISMP Guidelines for Optimizing Safe Implementation and Use of Smart Infusion Pumps, 2020.
Order to Pump, 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; source in the aimedagent repository. Standards documents remain the property of their publishers and are cited, not reproduced.