Dietary orders, supplements, and preferences

ODS communicates dietary orders, nutritional supplements, and patient food preferences. The type field distinguishes between diets (D), supplements (S), and preferences (P). It appears in diet order messages and is consumed by nutrition and food service systems.

The type_ field uses HL7 table 0159. Common values are D (Diet), S (Supplement), and P (Preference):

from zato.hl7v2.v2_9 import ODS

ods = ODS()

# D = Diet
ods.type_ = 'D'

# S = Supplement
ods.type_ = 'S'

# P = Preference
ods.type_ = 'P'

The diet_supplement_or_preference_code field uses CWE with HL7 table 0628:

from zato.hl7v2.v2_9 import ODS, CWE

ods = ODS()
ods.type_ = 'D'
ods.diet_supplement_or_preference_code = CWE(
    identifier='DAB',
    text='Diabetic',
    name_of_coding_system='HL70628'
)

The service_period field uses CWE with HL7 table 0627 to indicate when the diet applies:

from zato.hl7v2.v2_9 import ODS, CWE

ods = ODS()
ods.service_period = CWE(
    identifier='BRK',
    text='Breakfast',
    name_of_coding_system='HL70627'
)

The text_instruction field is a simple string for additional dietary notes:

from zato.hl7v2.v2_9 import ODS

ods = ODS()
ods.type_ = 'D'
ods.text_instruction = 'No added sugar'

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.