HL7 ODT Diet Tray Instructions

Pharmacy and treatment fields from experience.
HL7 field reference ODT 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

FieldNameRequiredRepeatableTypeTable
ODT.1 Tray Type Yes No CE 0160
ODT.2 Service Period No Yes CE
ODT.3 Text Instruction No No ST

ODT gives diet tray instructions that supplement a dietary order.

Pharmacy/treatment segments split a medication workflow into ordered, encoded, dispensed, administered, component, route, timing, and instruction details.

Be very clear about whether a field describes what was ordered, what the pharmacy dispensed, what was scheduled to be given, or what was actually administered. Those are related, but they are not the same event.

The v2.5.1 structures show ODT in OMD_O03 - OMD - Diet order and ORD_O04 - ORD - Diet order acknowledgment. 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.

ODT-1 Tray Type RequiredR SingleS TypeCE Table0160

ODT-1 qualifies the pharmacy workflow rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.

Use the agreed value set, starting from HL7 table 0160. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.

ODT-2 Service Period OptionalO RepeatableR TypeCE

ODT-2 carries Service Period for this pharmacy workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.

This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.

ODT-3 Text Instruction OptionalO SingleS TypeST

ODT-3 is human-readable context. Keep it useful for display and troubleshooting, but do not hide required workflow logic here unless the implementation guide explicitly says the receiver parses it.

Related links