This file contains the information needed to define how to prompt for each order, what values are acceptable, etc.
.01name(+)0;1FREE TEXTThis is the name of the dialog; entries that were converted from the Protocol file will retain the same name. Namespacing is not required, but still encouraged.
2display text0;2FREE TEXTCThe text of this dialog's name as it appears on a menu or subheader.
3disable0;3FREE TEXTThis field disables use of this dialog when it contains text. The text should be a short message explaining why use of this dialog has been disabled, as it will be displayed if this dialog is selected.
4type(+)0;4SET OF CODESP:prompt
Q:quick order
O:order set
This field defines the type of order dialog to be processed. Control will be passed to the OE/RR Dialog Processor for dialog items; menu types are used for displaying and selecting dialog items. Action types will only execute the entry and exit actions, ignoring any items that may exist; these dialogs should not create entries in the Orders file.
5display group0;5POINTER100.98This field determines what display group this dialog has been defined for. It will define which orderable items are selectable with this dialog, as well as what service to send the order to when it is complete.
6signature required0;6SET OF CODES0:NONE
This field indicates what signature will be required for orders created by this dialog, to be considered complete and ready to release to the service for action. If this flag is set to NO and the dialog contains a prompt for item(s) from the Orderable Item file, the order created may still require a signature if any of the items ordered are individually flagged as requiring a signature.
7package0;7POINTER9.4APKGThis is the VISTA package that is intended to receive orders created by this dialog; this is required for creating the HL7 messages to pass the order.
8verify order0;8BOOLEAN1:YES
This field is a flag, which determines if the order created by this dialog will be presented to the user for verification before saving in the Orders file; for most quick orders, this flag should be set to 0 (no).
9ask for another order0;9SET OF CODES0:NO
This field allows the user to add another order from this dialog, when the initial order is accepted and placed; if set to YES, the user will be asked "Add another order?" to allow for either exiting the processor or adding an additional order of the same type. This field can also be set to YES-DON'T ASK to force the processor to automatically drop into prompting for another order without asking first.
10items10;0MULTIPLE101.412This field contains the components for dialogs: Dialogs -> prompts Quick orders -> prompts (completed) Order sets -> dialogs or quick orders Menus -> dialogs, quick orders, or order sets
11data type1;1SET OF CODESD:date/time
R:free text date/time
F:free text
S:set of codes
W:word processing
This is the type of data being prompted for; this field is used to define a call to the reader (^DIR) in most cases.
12domain1;2FREE TEXTThis is a parameter that may be used to further specify the data type. The string stored here should be appropriate for the second ^-piece of DIR(0) when used with the data type field.
13id1;3FREE TEXTThis field may contain a single word identifier which will be stored with the user response in the Orders file #100, where it will be indexed for quick reference to certain values in the order dialog. The following are some examples of values currently in use: START -> Start date/time STOP -> Stop date/time SCHEDULE -> Administration Schedule ORDERABLE -> Orderable Item DRUG -> Dispense Drug CANCEL -> Cancel Future Orders flag COMMENT -> Word processing comments These values must be unique among entries within an order dialog but do not need to be unique across the entire file. Be sure to check the IDs assigned to generic text entries to make sure that all IDs are unique. In order to avoid potential problems it's recommended that you use unique IDs for any local entries that you create.
17validation7;E1,245FREE TEXTThis is MUMPS code that will be executed at the time of releasing an order created with this dialog; dialog responses may be checked again here before releasing the order to the service.
19additional text9;E1,245FREE TEXTThis is MUMPS code that will be executed when order ORIFN created by this dialog is about to be displayed; any string that should be appended to the order text should be returned in Y.
20description2;0WORD-PROCESSINGThis is a description of the dialog and its uses.
21responses6;0MULTIPLE101.416This multiple contains any responses to prompts that have been pre-answered to create a quick order.
30entry action3;E1,245FREE TEXTThis is MUMPS code that will be executed at the top of a dialog, prior to the execution of any prompts; it may perform functions such as listing the recent Radiology exams before ordering a new one, or alerting the user to an existing diet order before making a change.
31quick setup3.1;E1,245FREE TEXTThis is MUMPS code that will be executed in the place of the Entry Action when creating quick orders for this dialog; variables may be set here instead to bypass the usual dependence on specific patient values.
40exit action4;E1,245FREE TEXTThis is MUMPS code that will be executed upon completion of processing the dialog; it is currently used only with dialog-type entries.
51column width5;1NUMERICThis is the width, in characters, for each column in a menu. For example, to have 3 columns on an 80 character device, enter a width of 26.
52mnemonic width5;2NUMERICThis field allows the width of item mnemonics to be varied; the default value is 5.
53path switch5;3BOOLEAN1:YES
This switch allows the user, when traversing back UP the tree of menus and items, to select a new path back down the tree. In other words, the menu is redisplayed when returning to that menu's level in the tree and processing back down the tree is possible from that point. If nothing is selected from the menu, the path continues back up the tree.
54listbox text5;4FREE TEXT
55window form id5;5NUMERICThis field tells the GUI DELPHI code which form to use to process the order dialog. Each number represents a unique form. Following are some of the more common codes and their corresponding form in DELPHI. Form Name Windows Form ID --------- --------------- OD_ACTIVITY 100 OD_ALLERGY 105 OD_CONSULT 110 OD_PROCEDURE 112 OD_DIET_TXT 115 OD_DIET 117 OD_LAB 120 OD_MEDINPT 130 OD_MEDS 135 OD_MEDOUTPT 140 OD_NURSING 150 OD_MISC 151 OD_GENERIC 152 OD_IMAGING 160 OD_VITALS 171 OD_MEDIV 180 OD_TEXTONLY 999
56create parent order5;6BOOLEAN1:YES
This flag indicates whether a parent order should be created to group together all the orders created by this order set; this flag is only valid with SET type order dialogs. If this value is YES, a parent order will be created, and only the parent will be presented on the orders list for display and action; NO will prevent a parent from being created and all orders will be created and displayed independently.
57display subheader5;7BOOLEAN1:YES
This flag indicates whether a subheader is to be displayed for each order in this set as it is processed and placed; this flag is only valid with SET type order dialogs.
58auto-accept quick order5;8BOOLEAN1:YES
This can be set to yes for a quick order so that it can be placed simply by clicking on it in the GUI (no ordering dialog is displayed).
99timestamp99;1FREE TEXTFor menus, this contains the $H time the menu was last compiled for use with the Unwinder utility (^XQOR).

Referenced by 4 types

  1. ORDER (100) -- dialog, item ordered
  2. OE/RR RELEASE EVENTS (100.5) -- event order dialog, order set/menu
  3. DISPLAY GROUP (100.98) -- default dialog
  4. REMINDER DIALOG (801.41) -- finding item