The ORC sequence items of interest to ODS are ORC-1-order control, ORC-2-placer order number, ORC-3-filler order number, TQ1-7/8-quantity/timing, ORC-9-date/time of transaction, ORC-10-entered by, and ORC-11-verified by. For ORC-1-order control, the values may be New (NW), Cancel (CA), Discontinue Order Request (DC), Change (XO), Hold Order Request (HD), and Release Previous Hold (RL). The HD and RL codes could stop service for a specified length of time. TQ1-quantity/timing should be used to specify whether an order is continuous or for one service period only. It is also useful for supplements which are part of a diet but only delivered, say, every day at night.
Example:
|1^QPM^^20010415|.
Seq# | Data Element Name | DataType | Usage | Vocabulary | Cardinality | Item # | Length | C.LEN | Flags |
---|---|---|---|---|---|---|---|---|---|
ODS | |||||||||
1 | Type | ID | R | [1..1] | 00269 | [1..1] | |||
2 | Service Period | CWE | O | [0..10] | 00270 | ||||
3 | Diet, Supplement, or Preference Code | CWE | R | [1..20] | 00271 | ||||
4 | Text Instruction | ST | O | [0..2] | 00272 | 80 | # |
Definition: This field specifies type of diet. Refer To HL7 Table 0159 - Diet Code Specification Type in Chapter 2C, Code Tables, for valid entries.
Definition: When blank, the modifier applies to all service periods. Diet orders, for example, typically apply to all service periods. This field usually specifies supplements. This field allows you to designate a modification for one or more of the service periods during a day by combining service specifications as needed. The service periods will be local CEs, normally numbers. Suggested are:
service 1 | is | breakfast |
service 2 | is | mid-morning snack |
service 3 | is | lunch |
service 4 | is | mid-afternoon snack |
service 5 | is | dinner |
service 6 | is | bedtime snack |
Ex: |1~5| means service 1 and service 5, whatever these are locally defined to be.
Refer to Table 0627 - Service Period in Chapter 2C for valid values.
Definition: This field is the identifier of the ordered item for a patient; it is equivalent to OBR-4-universal service ID in function. Since ODS is a repeating segment, multiple entities get multiple segments. Refer to Table 0628 - Diet, Supplement, or Preference Code in Chapter 2C for valid values.
Example:
|^REG|, |023^^99FD6|, |^NOLACT|, |^TUBEFD|, and |011^HIPRO100^99FD1~123^LOFAT20^99FD1|
In the case where this segment requests a diet supplement, i.e., ODS-1-type = S, this attribute specifies a particular item or class of items. If institutional codes for patient food preferences (P) have been codified, they are also expressed as coded segments; otherwise, the information is passed as a text string in the fourth component of the ODS segment, described below.
Definition: This field defines the specific instructions for dietary. These instructions may address specific patient needs, such as isolation. This field provides the ordering provider's dietary instructions as free text. It can represent the full dietary instruction or indicate supplemental information.