| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | order number | 0;1 | NUMERIC | This field is merely the sequence order in which the diets were ordered and has no further meaning. | ||
| 1 | diet1 | 0;2 | POINTER | 111 | This is the first diet modification selected from the Diets (111) file. | |
| 2 | diet2 | 0;3 | POINTER | 111 | This is the second diet modification selected from the Diets (111) file. | |
| 3 | diet3 | 0;4 | POINTER | 111 | This is the third diet modification selected from the Diets (111) file. | |
| 4 | diet4 | 0;5 | POINTER | 111 | This is the fourth diet modification selected from the Diets (111) file. | |
| 5 | diet5 | 0;6 | POINTER | 111 | This is the fifth diet modification selected from the Diets (111) file. | |
| 6 | withhold | 0;7 | SET OF CODES | N:NPO X:NO ORDER P:PASS | This field, if not null, indicates that an NPO type of order was entered. | |
| 7 | type of service | 0;8 | SET OF CODES | T:TRAY C:CAFETERIA D:DINING ROOM | This field indicates the type of service requested for this diet order. It is not present for NPO orders. When this order becomes effective, this type of service will become the current type of service and will be the default for future orders. | |
| 8 | date/time effective | 0;9 | DATE-TIME | This is the date/time when this diet order takes effect. | ||
| 9 | date/time expires | 0;10 | DATE-TIME | This field indicates the date/time when this order is to expire. If null, the order is 'open-ended' and will not expire until superceded by another order. | ||
| 10 | clerk | 0;11 | POINTER | 200 | This field is the person actually entering the order. | |
| 10.5 | date/time ordered | 0;12 | DATE-TIME | This is the date/time the order was actually entered and may bear little relationship the effective and/or expiration date/times of the actual order. | ||
| 11 | comment | 1;1 | FREE TEXT | This is a comment field for any specialized comments concerning this diet order. | ||
| 12 | production diet(+) | 0;13 | POINTER | 116.2 | This is a pointer to the Production Diet (116.2) file and is the outcome of the 'diet recoding' algorithm which is based upon the diet modifications selected. It is not present for NPO types of orders. | |
| 13 | oe/rr order | 0;14 | POINTER | 100 | This field contains a pointer the the OE/RR file order corresponding to this order. | |
| 14 | current oe/rr status | 0;15 | POINTER | 100.01 | This field contains the current OE/RR status as passed to OE/RR. It is a pointer to the OE/RR Status file (100.01). | |
| 15 | last review date/time | 0;16 | DATE-TIME | This is the date/time that the diet order was last reviewed if necessary. (Reviews are based upon the coded Production Diet). Further reviews are based upon this last review date/time. | ||
| 16 | review clerk | 0;17 | POINTER | 200 | This is a pointer to File 200 of the person entering the review. | |
| 17 | cancelled date/time | 0;18 | DATE-TIME | This field contains the Date/Time when the NPO was cancelled. | ||
| 18 | cancelling clerk | 0;19 | POINTER | 200 | This field contains the user who cancelled the NPO and is captured automatically at the time of cancellation. | |
| 19 | individual pattern | 2;1 | FREE TEXT | This field is the individual meal pattern for the patient which contains three strings of codes, each code separated by a space contains the internal number of the recipe category and the quantity separated by a comma for the three meals, breakfast, noon, and evening, each separated by a semicolon. The meal pattern will take precedence over the diet pattern entered in the Diet Pattern file (111.1). | ||
| 20 | pattern clerk | 3;1 | POINTER | 200 | This is a pointer to File 200 of the person entering the patient's individual Diet Pattern. | |
| 21 | date/time pattern entered | 3;2 | DATE-TIME | This field contains the Date/Time when the Diet Pattern was entered. |
Error: Invalid Global File Type: 115.02