HL7 INU Messages: Automated Equipment Inventory Update

HL7 INU messages carry inventory updates from laboratory automation equipment to a controlling system — the running tally that tells a controller how much reagent is on board, which consumables remain, what lot numbers are loaded, and when each substance expires. An INU message is the inventory half of an equipment exchange: an instrument (typically an analyzer, a track, or a reagent-handling robot) sends one INU to the controlling laboratory automation manager or middleware with the equipment state in EQU and one or more INV segments reporting the state of each substance on board. This page explains what an INU message represents, the trigger event that carries it, every segment the message can contain and what each one holds, and how an INU update relates to FHIR. Sample content is constructed for illustration with fictional identifiers.

What an INU message represents

An INU message — INU stands for Automated Equipment Inventory Update — communicates the inventory state of a piece of laboratory automation equipment, substance by substance, from the equipment to the controlling system. The core of the message is the pairing of EQU, which identifies the equipment instance and reports its operational state at the moment the inventory was sampled, with one or more INV segments, each of which carries the identifier, status, type, container, lot, active and available quantity, expiration, and manufacturer for a single substance loaded on the equipment. Each INV represents one reagent, calibrator, control, or consumable resident on the instrument.

INU is an unsolicited update message: the equipment issues it on its own initiative when something about the inventory changes — a reagent loaded, a lot exhausted, an expiry crossed, an available volume falling below a threshold. The EQU segment pins the inventory snapshot to a specific equipment instance (EQU-1) at a specific moment (EQU-2) in a known operational state (EQU-3), with the alert level in EQU-5 flagging whether the inventory itself has triggered an alert on the instrument. The sender is the equipment or its instrument-side gateway; the receiver is the controlling system. Because the message carries the inventory state, the substance identifier and status in INV-1 and INV-2, the lot in INV-6, the active and available quantities in INV-7 and INV-8, and the expiry in INV-12 are the fields that drive downstream behaviour.

When an INU message is sent

An INU message is sent whenever the inventory state on a piece of automation equipment changes in a way the controller needs to know about — a new lot loaded, a reagent depleted, a consumable count crossing a low threshold, an expiry reached, a substance retired. It is event-driven and unsolicited: the equipment does not wait to be polled. INU is paired in practice with INR (the inventory request a controller may issue to pull current state) and lives alongside EAC, EAN, and ESU in the Chapter 13 laboratory automation message set.

Trigger event

The INU message type carries a single trigger event:

• INU^U05 – Automated equipment inventory update.

Because INU has one trigger event, the receiver's handling turns on the substance identifier in INV and the equipment instance in EQU — which substance, on which instrument, in which state — rather than on the trigger code in MSH-9.

Integration topology

The diagram shows the instrument pushing an INU inventory update through the integration engine to the controlling laboratory automation manager, which reconciles the snapshot against its inventory store.

{{diagram: instrument / equipment gateway → INU update → integration engine → laboratory automation manager / middleware → inventory store / LIS automation module}}

Typical senders: the equipment itself, an instrument-side gateway, or a track-control system on the automation line.

Typical receivers: laboratory automation manager, laboratory middleware, LIS automation module.

Direction: equipment to controller — the INU travels from the instrument to the controlling system, either unsolicited on an inventory event or as the answer to an INR inventory request.

Segments in an INU message

The INU_U05 message opens with MSH, followed by the equipment detail in EQU, and then carries one or more INVENTORY groups. Each inventory group opens with INV and may carry role context. Cardinality follows HL7 notation: [X] optional, {X} repeating, [{X}] optional and repeating; a bare code is required. Each segment code links to its canonical field-by-field reference.

[ ] = optional, { } = repeating

The inventory group from INV onward repeats, so a single INU message can report the full inventory state of an instrument in one exchange. The canonical segment pages carry the full field-by-field detail.

Sample INU message

Note. Constructed for illustration. Equipment identifiers, substance identifiers, lot numbers, and dates are fictional.

MSH|^~&|ANALYZER01|MERCYGEN|LAB_AUTO_MGR|MERCYGEN|202006150930||INU^U05^INU_U05|MSG00091|P|2.5.1
EQU|ANALYZER01^MERCYGEN^EI|202006150930|IT||N
INV|REAGENT_ALT^Alanine Aminotransferase^L|OK^In Use^HL70383|RG^Reagent^HL70384|CART_A1^MERCYGEN||LOT789456||120^mL|||||202608310000||||ACME Diagnostics
INV|REAGENT_AST^Aspartate Aminotransferase^L|LOW^Low^HL70383|RG^Reagent^HL70384|CART_A2^MERCYGEN||LOT789457||18^mL|||||202608310000||||ACME Diagnostics
INV|CTRL_LVL1^Control Level 1^L|OK^In Use^HL70383|CO^Control^HL70384|VIAL_C1^MERCYGEN||LOT654321||45^mL|||||202607150000||||ACME Diagnostics

What this sample shows

The INU^U05 in MSH-9 marks an automated equipment inventory update. EQU identifies the equipment instance ANALYZER01 at 202006150930, in equipment state IT (idle) in EQU-3, with no alert in EQU-5. Three INV segments follow, one per substance: an ALT reagent in container CART_A1 on lot LOT789456, 120 mL available, expiring 202608310000; an AST reagent in container CART_A2 on lot LOT789457, status LOW, only 18 mL available — the substance status in INV-2 is what tells the controller to plan a reload; and a Level 1 control in vial VIAL_C1 on lot LOT654321, 45 mL available, expiring 202607150000. Every substance reports its manufacturer in INV-16 as ACME Diagnostics.

Working with INU messages

Read the substance status in INV-2 before the quantity

INV-2 reports the substance status — OK in use, LOW, EX expired, RC recalled, DE depleted. The status is the field that should drive controller behaviour, not the raw quantity in INV-8: a substance can be flagged LOW well before it is empty, or RC despite holding plenty of volume. Read INV-2 first and treat INV-7 and INV-8 as the supporting numbers behind the status.

Match the inventory container in INV-4 to the physical slot

INV-4 carries the inventory container identifier — the cartridge, vial, or rack position the substance occupies on the instrument. The same substance can appear in two INV segments for two cartridges on the same instrument; reconcile on the container identifier rather than collapsing on the substance identifier alone, or two cartridges of the same reagent will be reported as one.

Track lot numbers in INV-6 across messages

INV-6 carries the substance lot number. When a lot changes — a fresh cartridge swapped in — the equipment sends a new INU and the controller's inventory store should record the new lot against the container in INV-4. Downstream result validation and recall handling both turn on the lot, so lot changes need to be persisted, not just observed.

Watch the expiration date in INV-12

INV-12 carries the expiration date/time for the substance. An instrument may continue to report OK in INV-2 for a substance whose expiry has passed if it has not yet been used; the controller should treat expiry as a parallel gate to status and refuse to dispatch work against an expired substance, regardless of the status field.

Vendor variance. The codes used in INV-2 for substance status and in INV-3 for substance type are partly site- and vendor-defined. Some instruments publish a rich vocabulary covering low, depleted, expired, recalled, blocked, and in-use; others report only in-use and depleted and lean on the quantity in INV-8 for everything else. Confirm a partner's field usage and status vocabulary against their interface specification rather than assuming the base standard.

FHIR equivalent

An automated equipment inventory update corresponds, conceptually, to a FHIR SupplyDelivery that references the reported substance as a Substance resource, with a MessageHeader at the head of a Bundle when carried as a messaging exchange.

There is, however, no published mapping to lean on. The HL7 v2-to-FHIR Implementation Guide provides no message map for INU_U05, and laboratory inventory data sits largely outside FHIR's clinical resource scope — FHIR's strengths are clinical and administrative data rather than instrument-level reagent and consumable inventory. A FHIR representation produced from an INU message is therefore composed manually, taking the equipment instance from EQU and the substance identifier, lot, quantity, and expiry from INV into the SupplyDelivery and Substance resources. In most production integrations the INU stays on the v2 channel.

Common pitfalls

Pitfall. Driving controller behaviour from INV-8 instead of INV-2. The substance status is the field that flags LOW, EX, or RC; treating the available quantity as the source of truth misses recalls and expiries that the status field reports cleanly.

Pitfall. Collapsing INV segments on the substance identifier and losing the container in INV-4. The same reagent can occupy two cartridges on one instrument, and merging them on INV-1 reports half the on-board inventory.

Pitfall. Trusting INV-2 and ignoring INV-12. An instrument can report a substance as OK past its expiry if it has not been used since the cutoff. Treat expiration as a parallel gate to status.

How Vorro handles INU messages

Vorro routes each INU update from the reporting instrument to the controlling system, reconciles every INV on the inventory container in INV-4 as well as the substance identifier in INV-1, persists lot numbers from INV-6 against the container so result validation and recall handling have the lot they need, treats the substance status in INV-2 as the primary signal and the expiry in INV-12 as a parallel gate, surfaces the equipment alert level from EQU so an inventory-driven alert is visible alongside the substance detail, and, where a FHIR destination is configured, maps the update to a SupplyDelivery referencing a Substance — composed manually, since the v2-to-FHIR Implementation Guide publishes no map for this message.

Related messages

• INR — the automated equipment inventory request a controller issues to pull current inventory state from an instrument; the INU is its natural counterpart.
• EAC — the automated equipment command that issues an instruction to the same equipment whose inventory the INU reports.
• EAN — the automated equipment notification that the equipment raises when it needs the controller's attention, including inventory-driven alerts.

Sources

• HL7 v2-to-FHIR IG — message maps index — confirms no message map for INU_U05
• HL7 v2-to-FHIR IG — segment maps index — confirms no published ConceptMap for the EQU or INV segments
• HL7 Messaging Standard Version 2.5.1 product brief