HL7 VND Segment: Purchasing Vendor

The VND (Purchasing Vendor) segment was introduced in HL7 v2.7 and identifies the vendor that supplies an inventory item. VND is typically used alongside an IIM Inventory Item Master segment to record who an item is purchased from, the vendor's catalog number, and whether the vendor is the primary supplier for that item.

Purpose

VND tells the receiver where an inventory item is sourced from. It groups together:

A Set ID (VND-1) that orders multiple vendors against the same item.
A Vendor Identifier (VND-2) — typically a corporate identifier in the sender namespace.
The Vendor Name (VND-3) and the Vendor Catalog Number (VND-4) used for ordering.
A Primary Vendor Indicator (VND-5) that flags the preferred source for the item.

A single item may have multiple VND segments — one per approved supplier — with exactly one of them marked as the primary vendor.

Used in

VND appears in supply-chain and materials-management messages, including:

Inventory item master updates that publish supplier relationships alongside IIM.
Specimen shipment and inventory transfer messages — see INV (specimen/inventory shipment update) — when receivers need to know which vendor originally supplied the items in a shipment.
Purchasing and reorder triggers, where the primary vendor flag determines the default supplier for automated POs.

Within an INV / SSU-style message, VND follows the IIM segment for the item it describes.

Field-by-field reference

The table below lists each VND field in segment order. The "Seq" column is the HL7 field position used in pipe-delimited messages (e.g. VND-2 is Vendor Identifier). Data types link to their HL7 v2.8.1 reference page. "R" marks fields the HL7 standard requires; "O" marks optional fields. "Repeat = Y" means the field may carry multiple repetitions separated by ~.

Seq	Name	Data Type	Length	Req	Repeat	Table #	Description
VND-1	Set ID - VND	si	—	R	—	—	Sequence number of the VND segment
VND-2	Vendor Identifier	ei	—	O	—	—	Unique identifier for the vendor
VND-3	Vendor Name	st	—	O	—	—	Human-readable vendor or supplier name
VND-4	Vendor Catalog Number	ei	—	O	—	—	Vendor's catalog number for the item
VND-5	Primary Vendor Indicator	cne	—	O	—	[HL70532]	Coded flag marking primary supplier status

Most-used fields

VND is a small segment, and four fields do almost all of the work:

VND-1 Set ID — the only required field; orders vendor entries for an item.
VND-2 Vendor Identifier — the durable join key into the buyer's supplier master.
VND-4 Vendor Catalog Number — the part number used when reordering.
VND-5 Primary Vendor Indicator — read by purchasing systems to pick the default supplier for automated POs.

Version differences (2.7 to 2.8.2)

VND was introduced in HL7 v2.7 as part of the Materials Management chapter.
v2.7.1 and v2.8 left the field list unchanged; the Primary Vendor Indicator vocabulary (HL70532) was clarified.
v2.8.1 (this page) keeps the 5-field structure with VND-5 typed as CNE so values must be drawn from a controlled vocabulary.
v2.8.2 carries the segment forward without structural changes.

Common mistakes

Omitting VND-1 Set ID when multiple vendors are reported, which collapses the list on the receiver.
Putting a free-text supplier name into VND-2 instead of a structured EI identifier. VND-2 expects an ID + namespace; the human-readable name belongs in VND-3.
Marking more than one VND segment as primary for the same item — purchasing systems will pick non-deterministically.
Treating VND-4 as a sender-internal SKU. It is the vendor's catalog number, not the buyer's part number; mixing the two causes failed POs.
Sending VND without a preceding IIM segment when the receiver needs item context. VND on its own has no item to attach to.

Examples

Minimal VND — only the required Set ID:

VND|1

Fully-populated VND identifying a primary vendor for an item:

VND|1|VEND-44021^VORRO_VND|Acme Medical Supply Co.|ACME-CAT-99812^ACME_CAT|Y^Yes^HL70532

Annotated breakdown of the populated example:

VND|                                                  -- Segment ID
  1                                                   -- VND-1 Set ID - VND (SI)
  | VEND-44021^VORRO_VND                              -- VND-2 Vendor Identifier (EI)
  | Acme Medical Supply Co.                           -- VND-3 Vendor Name (ST)
  | ACME-CAT-99812^ACME_CAT                           -- VND-4 Vendor Catalog Number (EI)
  | Y^Yes^HL70532                                     -- VND-5 Primary Vendor Indicator (CNE)

In-context excerpt 1 — two VND segments attached to an IIM under a shipment, with the primary vendor first:

MSH|^~&|VORRO_INV|WAREHOUSE_W|VORRO_INV|HOSPITAL_H|20260610161200||SSU^U03^SSU_U03|7783|P|2.8.1
SHP|SHP-2026-000843^VORRO_SHIP|CARRIER-7783^UPS|DELIVERED^Delivered^HL70905|20260610155900||N^Normal^HL70177||1
PAC|1|PKG-7783-01^VORRO_PKG||1|CARTON^Carton^HL70908|INTACT^Intact^HL70544
IIM|ITEM-55102^VORRO_ITEM|Sterile gauze 4x4|Box of 100||40|EA
VND|1|VEND-44021^VORRO_VND|Acme Medical Supply Co.|ACME-CAT-99812^ACME_CAT|Y^Yes^HL70532
VND|2|VEND-44095^VORRO_VND|MedSource Distributors Inc.|MSD-77410^MSD_CAT|N^No^HL70532

In-context excerpt 2 — a single primary vendor recorded against a specimen-collection item in an inventory shipment update:

MSH|^~&|VORRO_LIS|LAB_A|VORRO_LIS|LAB_B|20260610081500||SSU^U03^SSU_U03|7784|P|2.8.1
SHP|SHP-2026-000844^VORRO_SHIP|CARRIER-7784^FEDEX|IN_TRANSIT^In Transit^HL70905|20260610081500||STAT^Stat^HL70905||1
PAC|1|PKG-7784-01^VORRO_PKG||1|COOLER^Insulated cooler^HL70908|INTACT^Intact^HL70544|REFRIGERATE^Keep refrigerated 2-8C^HL70549
IIM|ITEM-55103^VORRO_ITEM|Blood collection tube EDTA|Box of 50||20|EA
VND|1|VEND-44210^VORRO_VND|LabSource Worldwide|LSW-CT-EDTA-50^LSW_CAT|Y^Yes^HL70532

FHIR mapping

No segment-level ConceptMap is published in the v2-to-FHIR IG for VND. Conceptually, a VND carrying vendor identification and catalog data aligns with a FHIR Organization (role: supplier) referenced from InventoryItem or SupplyDelivery.supplier:

VND-2 Vendor Identifier → Organization.identifier.
VND-3 Vendor Name → Organization.name.
VND-4 Vendor Catalog Number → an extension on InventoryItem or a Catalog resource entry keyed by Organization.
VND-5 Primary Vendor Indicator → an extension or a rank element on the vendor reference.

Implementers building bridges should agree on a project-specific mapping rather than expecting a standard ConceptMap.

Engine considerations

VND segments are grouped under the preceding IIM. Engines that lose segment grouping when re-serialising will detach vendors from items; preserve order or carry an explicit grouping marker.
Validate VND-5 against table HL70532 — receivers that treat any non-empty value as "primary" will mis-route automated POs.
When more than one VND segment is present for an item, enforce "exactly one primary" at the engine boundary rather than downstream.
VND-2 and VND-4 are both EI — keep their namespace components distinct (sender's vendor master versus the vendor's own catalog) so they never get swapped during transformation.

How Vorro parses and produces VND

Vorro's HL7 v2 parser builds a typed model of VND directly from the HAPI v2.8.1 structure definitions, exposing all 5 fields by name (VND-1, VND-2.1, etc.). Common workflows include:

Joining VND-2 Vendor Identifier against the supplier master so inbound inventory updates carry resolved supplier names regardless of what was sent in VND-3.
Enforcing the "single primary vendor" rule per IIM at parse time and raising a structured exception when violated.
Producing outbound VND segments from purchasing records, automatically populating VND-5 from the supplier's primary flag in the source system.
Validating VND-5 against the configured HL70532 vocabulary so out-of-table values are rejected before the message leaves the engine.

Sources

← Back to HL7 v2 Guide