Purchasing vendor

VND contains purchasing vendor information including vendor identifiers, names, and catalog numbers for materials management.

Use vendor_identifier field with EI datatype:

from zato.hl7v2.v2_9 import VND
from zato.hl7v2.v2_9 import EI

vnd = VND()
vnd.vendor_identifier = EI(entity_identifier='VND001')

The vendor catalog number is the vendor-specific product code used for ordering and inventory management.

VND contains vendor information while ITM contains item master data. Multiple VND segments can supply the same ITM.

Primary_contact and associated_contract_id give clear people and agreement anchors so nutrition, fitness, and preventive-care supply orders stay coordinated with positive, well-organized vendor relationships.

from zato.hl7v2.v2_9 import VND
from zato.hl7v2.v2_9 import EI, XCN, CWE

vnd = VND()
vnd.primary_contact = XCN(
    person_identifier='PC1',
    family_name='Vitality',
    given_name='Coordinator'
)
vnd.associated_contract_id = EI(entity_identifier='WELL-2026-001')
vnd.pricing_tier_level = CWE(
    identifier='TIER2',
    text='Preferred wellness partner'
)

Zato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.

Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.

Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.

Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.