# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | order #(+) | 0;1 | NUMERIC | This is the internal order number of the file. | ||
.02 | object of order(+) | 0;2 | VARIABLE-POINTER | 2, 67 | This is the individual object of the order. Depending on the parent file entry, this would be the Patient, Control Point, etc. | |
.1 | orderable items | .1;0 | MULTIPLE | 100.001 | This multiple contains the items being ordered. | |
.8 | order actions | 8;0 | MULTIPLE | 100.008 | These are the actions taken on this order, including the signature and verification required to release to the service. | |
.9 | order checks | 9;0 | MULTIPLE | 100.09 | This is the list of order checks found for this order. | |
1 | current agent/provider | 0;4 | POINTER | 200 | This is the person who is responsible for the order. | |
2 | dialog(+) | 0;5 | VARIABLE-POINTER | 19, 101, 101.41 | This is the dialog that created this order. | |
3 | who entered | 0;6 | POINTER | 200 | This is the USER who entered the information about the order. | |
4 | when entered | 0;7 | DATE-TIME | This is the date/time of completion of the initiation of the order. | ||
4.5 | responses | 4.5;0 | MULTIPLE | 100.045 | This contains the responses to an order dialog. | |
5 | status | 3;3 | POINTER | 100.01 | This is the status of the order. | |
5.1 | order diagnoses | 5.1;0 | MULTIPLE | 100.051 | These are the the diagnoses associated with this order. | |
6 | patient location | 0;10 | VARIABLE-POINTER | 44 | This is the hospital location from which the order originated. | |
7 | item ordered | 3;4 | VARIABLE-POINTER | 19, 60, 101.41 | This is the variable pointer to the file and item ordered. | |
8 | veiled | 3;8 | SET OF CODES | 1:VEILED 0:UNVEILED | This field is set when creating an order to prevent the order from being displayed on the review screen until the order is complete and accepted. | |
8.1 | type | 3;11 | SET OF CODES | 0:STANDARD 1:EDIT 2:RENEW 4:HOLD 6:DISCONTINUE B:BCMA C:COPY X:TRANSFER P:PACKAGE | This field is used to determine the type of order that is being processed. Different things happen depending on the order type. | |
9 | replaced order | 3;5 | POINTER | 100 | This is the order number of the order which was replaced by this order, either by editing or renewal. | |
9.1 | replacement order | 3;6 | POINTER | 100 | This is the order number of the order that replaces this one, either by edit or renewal. | |
10 | patient class | 0;12 | SET OF CODES | I:INPATIENT O:OUTPATIENT | This is the patient's inpatient classification for this order; an inpatient may have some orders performed on an outpatient basis. | |
11 | treating specialty | 0;13 | POINTER | 45.7 | This is the TREATING SPECIALTY associated with this order. | |
12 | package(+) | 0;14 | POINTER | 9.4 | This is the package creating the order. | |
13 | cost | 0;15 | NUMERIC | This is the cost of filling this order. | ||
14 | signature required | 0;16 | SET OF CODES | 0:NONE 1:ORELSE 2:ORES | This is the OR key required to sign this order. If set to 2, only users with the ORES key will be allowed to sign this order; if set to 1, users with either the ORELSE or ORES keys will be allowed to sign. A 0 or "" indicates that no signature is required. | |
15 | event | 0;17 | POINTER | 100.2 | This is the event that this order's release is/was delayed till. | |
16 | patient appointment | 0;18 | DATE-TIME | This is the appointment date/time for outpatients and is only entered when inpatient medications are ordered for them. | ||
20 | children | 2;0 | MULTIPLE | 100.002 | This field allows a single order or set of orders to be linked to a parent order. | |
21 | start date | 0;8 | DATE-TIME | This is the start date/time of the order. | ||
22 | stop date | 0;9 | DATE-TIME | This is the stop date/time of the order. | ||
23 | to(+) | 0;11 | POINTER | 100.98 | This is the service to which the order is referred. This is used to determine the display group in which the order appears. | |
30 | current action | 3;7 | NUMERIC | This is the item number of the action in the Order Actions multiple that is currently being carried out on this order; it will be used to build the text for the Current Orders list. | ||
31 | date of last activity | 3;1 | DATE-TIME | This is the date/time the order was last updated. | ||
32 | grace days before purge | 3;2 | NUMERIC | This is the number of days to hold an order from the date of last activity. The order in OE/RR may be purged after this date. The default is 30 days. If a package needs the order retained for a period longer than 30 days, this can be specified when the order is created by setting the variable ORPURG to the appropriate number of days before calling FILE^ORX. | ||
33 | package reference | 4;E1,200 | FREE TEXT | This information allows the package to link the order in OR with its more detailed order information in the individual package. It is the package's responsibility to define and determine the structure of this information. | ||
35 | alert on results | 3;10 | POINTER | 200 | This field contains the user who requested to be alerted when results for this order become available. Only lab, radiology, and consult orders will generate results. | |
36 | parent | 3;9 | POINTER | 100 | This is the parent of an order that may have a parent/child relationship. | |
39 | lapsed date/time | 10;1 | DATE-TIME | This field will specify when the order was Lapsed. Lapsing takes place in routine ORTSKLPS and is part of the ORMTIME scheduled option. | ||
51 | service connected condition | 5;1 | BOOLEAN | 1:YES 0:NO | When signing orders, the provider may be asked if this order is for treatment of a service-connected condition; his/her response to this question will be stored in this field. Currently this question is only asked for Outpatient Medications, and the response is passed to that package with the new order. | |
52 | mst | 5;2 | BOOLEAN | 1:YES 0:NO | If a patient has been identified as having been treated for Military Sexual Trauma (MST), then the provider may be asked when signing the order if it is for treatment of a condition related to MST and his/her response to this question will be stored in this field. Currently this question is only asked for Outpatient Medications, and the response is passed to that package with the new order. | |
53 | agent orange exposure | 5;3 | BOOLEAN | 1:YES 0:NO | If a patient has been identified as having been exposed to Agent Orange (AO) during service in Vietnam, then the provider may be asked when signing the order if it is for treatment of a condition related to AO and his/her response to this question will be stored in this field. Currently this question is only asked for Outpatient Medications, and the response is passed to that package with the new order. | |
54 | ionizing radiation exposure | 5;4 | BOOLEAN | 1:YES 0:NO | If a patient has been identified as having been treated for exposure to ionizing radiation (IR) during military service, then the provider may be asked when signing the order if it is for treatment of a condition related to IR and his/her response to this question will be stored in this field. Currently this question is only asked for Outpatient Medications, and the response is passed to that package with the new order. | |
55 | southwest asia conditions | 5;5 | BOOLEAN | 1:YES 0:NO | If a patient has been identified as having been treated for exposure to environmental contaminants (EC) during the Persian Gulf War, then the provider may be asked when signing the order if it is for treatment of a condition related to EC and his/her response to this question will be stored in this field. Currently this question is only asked for Outpatient Medications, and the response is passed to that package with the new order. | |
56 | head and/or neck cancer | 5;6 | BOOLEAN | 1:YES 0:NO | If a patient has been identified as having been treated for head or neck cancer due to nose or throat radium treatments while in the military, then the provider may be asked when signing the order if it is for treatment of head or neck cancer and his/her response to this question will be stored in this field. Currently this question is only asked for Outpatient Medications, and the response is passed to that package with the new order. | |
57 | combat veteran | 5;7 | BOOLEAN | 1:YES 0:NO | When signing orders, the provider may be asked if this order is for treatment of a combat-related condition; his/her response to this question will be stored in this field. Currently this question is only asked for Outpatient Medications, and the response is passed to that package with the new order. | |
58 | shipboard hazard | 5;8 | BOOLEAN | 1:YES 0:NO | ||
61 | nature of dc | 6;1 | POINTER | 100.02 | Orders that are DC'ed because they have been duplicated do not create a DC order, nor is a chart copy or electronic signature notification generated. If this is a CHANGE IN THERAPY, then a DC order is generated that must be signed, and a chart copy of the new DC request is printed. | |
62 | dc'ed by | 6;2 | POINTER | 200 | This is the person who DC'ed this order. | |
63 | dc date/time | 6;3 | DATE-TIME | This is the date/time the order was DC'ed. | ||
64 | dc reason | 6;4 | POINTER | 100.03 | This is the reason this order was DC'ed, i.e. "Patient discharged." | |
65 | dc reason text | 6;5 | FREE TEXT | This is the text of the DC reason. | ||
66 | completed | 6;6 | DATE-TIME | This is the date/time the order was marked as complete. | ||
67 | completed by | 6;7 | POINTER | 200 | This is the person who marked this order as complete. | |
68 | dc event | 6;8 | POINTER | 100.2 | This is the event that automatically discontinued this order. | |
69 | dc original order | 6;9 | SET OF CODES | 1:TRUE 0:FALSE | This field is only accessed by CPRS. This field is set to True if both the original order and the pending renewal order are discontinued. This field is set to False if only the pending renewal order is discontinued. If only the pending renewal order is discontinued, CPRS assigns the original order's status to the status it received from the pharmacy package. | |
71 | results date/time | 7;1 | DATE-TIME | This field contains the date/time that results became available for this order; only Lab, Radiology, and Consult orders have results. | ||
72 | abnormal results | 7;2 | BOOLEAN | 1:YES | This field indicates whether the results for this order were abnormal, or outside of normal ranges. | |
73 | findings | 7;3 | FREE TEXT | This field contains the text of any significant findings for the results of this order. | ||
90 | ba service connected condition | 5.2;1 | BOOLEAN | 1:YES 0:NO | When signing orders, the provider may be asked if this order is for treatment of a service-connected condition; his/her response to this question will be stored in this field. | |
91 | ba military sexual trauma | 5.2;2 | BOOLEAN | 1:YES 0:NO | ||
92 | ba agent orange exposure | 5.2;3 | BOOLEAN | 1:YES 0:NO | ||
93 | ba ionizing radiation exposure | 5.2;4 | BOOLEAN | 1:YES 0:NO | ||
94 | ba southwest asia conditions | 5.2;5 | BOOLEAN | 1:YES 0:NO | ||
95 | ba head and/or neck cancer | 5.2;6 | BOOLEAN | 1:YES 0:NO | ||
96 | ba combat veteran | 5.2;7 | BOOLEAN | 1:YES 0:NO | ||
97 | pfss account reference | 5.5;1 | POINTER | 375 | The PFSS Account Reference field stores the PFSS Account Reference associated with the order. The field is a pointer to the PFSS Account Reference file (#375). | |
98 | ba shipboard hazard | 5.2;8 | BOOLEAN | 1:YES 0:NO |