HL7 IIM Inventory Item Master
HL7 field reference IIM fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| IIM.1 | Primary Key Value - IIM | Yes | No | CWE | |
| IIM.2 | Service Item Code | Yes | No | CWE | |
| IIM.3 | Inventory Lot Number | No | No | ST | |
| IIM.4 | Inventory Expiration Date | No | No | TS | |
| IIM.5 | Inventory Manufacturer Name | No | No | CWE | |
| IIM.6 | Inventory Location | No | No | CWE | |
| IIM.7 | Inventory Received Date | No | No | TS | |
| IIM.8 | Inventory Received Quantity | No | No | NM | |
| IIM.9 | Inventory Received Quantity Unit | No | No | CWE | |
| IIM.10 | Inventory Received Item Cost | No | No | MO | |
| IIM.11 | Inventory On Hand Date | No | No | TS | |
| IIM.12 | Inventory On Hand Quantity | No | No | NM | |
| IIM.13 | Inventory On Hand Quantity Unit | No | No | CWE | |
| IIM.14 | Procedure Code | No | No | CE | 0088 |
| IIM.15 | Procedure Code Modifier | No | Yes | CE | 0340 |
IIM describes an inventory item master record, including identifiers, description, status, manufacturer, and packaging details.
The standard describes IIM this way: The Inventory Item Master segment (IIM) contains information about the stock of product that can be used to fulfill an ordered test/service. All of the fields in this segment describe the test/service and other basic attributes pertaining to Service Item defined within an Other Observation/Service Item master file. This segment is related to centrally stocked or supply management concerns.
Master-file segments update reference data rather than describing a single patient event. They define locations, staff, providers, test catalogs, charge items, inventory items, languages, certificates, and other shared records.
Because many downstream messages depend on this data, small changes here can have large effects. Use stable identifiers, effective dates, action codes, and clear ownership rules instead of treating a master-file feed like a loose spreadsheet export.
The v2.5.1 structures show IIM in MFN_M15 - Inventory item master file notification. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
IIM-1 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
IIM-2 identifies the Service Item Code for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
IIM-3 identifies the Inventory Lot Number for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
IIM-4 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
For effective and end dates, make the boundary rule explicit. Receivers need to know whether the value is inclusive, exclusive, planned, actual, or merely informational.
IIM-5 helps identify the product, software, device, or equipment involved. It is particularly useful when support needs to trace behaviour back to a specific build, lot, instrument, or manufacturer.
IIM-6 places the master-file record in an organization, facility, department, room, bed, or location group. Keep physical location, owning department, and receiving facility separate when the datatype allows it.
IIM-7 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
IIM-8 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
IIM-9 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
IIM-10 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
IIM-11 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
IIM-12 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
IIM-13 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
IIM-14 identifies the Procedure Code for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
The generated panel links this to HL7 table 0088; many real interfaces narrow that list further, so follow the receiver's implementation guide.
IIM-15 is clinical or administrative context for the master-file record. Use the coded value, lifecycle status, and timing fields together so a receiver can decide whether it is new, changed, resolved, cancelled, or historical.
The generated panel links this to HL7 table 0340; many real interfaces narrow that list further, so follow the receiver's implementation guide.