Global: ^ORD(100.99

This is the internal number of this file.

UNEDITABLE

This is an arbitrary name for the single entry in this file.

1)= S ^ORD(100.99,"B",$E(X,1,30),DA)=""

2)= K ^ORD(100.99,"B",$E(X,1,30),DA)

This is the current order # on the system.

UNEDITABLE

This is the name of the system as found in the global node ^%ZOSF("VOL").  An entry should be made here for each CPU system that generates orders.

if it can be found.

that this field not be edited.

This field will be maintained by the OE/RR version 3 conversion.  It will be set to the time the conversion of orders for inpatients started.

This field will be maintained by the OE/RR version 3 order conversion.  It will contain the time the conversion of orders for inpatients completed.

This field will contain the name of the location the conversion is currently up to if still converting orders for current inpatients.  If that step is complete, this field will be blank.

If the OE/RR version 3.0 order conversion is converting orders for inpatients, this field will contain the patient the conversion is currently up to.  If the inpatient order conversion is complete, this field will be null.

contain the date phase 2 of the conversion started.

will contain the date phase 2 of the conversion completed.

field will be deleted.  The stages are:

0.  Populate multiple of patient orders to convert

1.  Current inpatients.

2.  Patients with future scheduled admissions

3.  patients on waiting list

4.  patients with discharges in the last 4 weeks

5.  patients with appointments in last 4 weeks and next 4 weeks

6.  all remaining patients in DPT

7.  orders not associated with DPT

restarted, this field will allow restart from where the process left off.

status of the job and allowing restart should the job stop.

when it finds it set, it will allow the conversion to make a clean stop.  RESTART^OR3CONV may be used to restart the task.

This field will be maintained by the Order Entry/Results Reporting version 3.0 orders conversion.  It will keep a counter of the number of patients that have been converted.

local namespace (ORZADD) so that local changes won't be overwritten when new versions of OE/RR are installed.  When a customized menu structure has been created for local use of OE/RR, it should be put in this field.

Starting with Version II of OE/RR, menus can be set up in file 101 for specific users or groups of users and assigned on an individual basis via the Clinical Coordinators menu.

This field allows each package to define its own set of parameters.  The entries in this multiple field are exported much the same as entries in the PACKAGE File are exported when a package is initialized.

This field allows the description associated with a status to be displayed with the current status of an order when a detailed display is requested.

This field allows the patient name to be displayed each time an order action is executed after the subheader during ADD NEW ORDERS option.

This field defines the number of hours that orders remain in the "Current Orders" context after they have been completed.

This field allows orders to be reviewed when a patient is transferred or discharged, and when a clinic appointment is made or cancelled.

normally are run in the background will run in real time.  For demo/training purposes, not to be used in a production environment.

This field is also used to shut down or suspend the background filer.  The filer needs to be suspended when the ^ORYX global is being moved or a new version of OE/RR is being installed.

DELETE AUTHORITY: @

WRITE AUTHORITY:  @

This field allows the initials of the person who entered the order to be displayed on the OE/RR summary reports.  The initials take up an additional line on the display and are shown just below the Ord'd date time.

This field allows the attending physician to be prompted as a default when adding new orders.

This field contains the date that the OE/RR purge utility was last started.

UNEDITABLE

This field contains the last order number purged by the OE/RR purge utility.

UNEDITABLE

This field tells OE/RR how long to keep the record of failed tasks in the OE/RR ERROR file.  If no entry is put in this field then errors are kept for 2 days.

displayed when a transaction fails.  This field should be turned OFF at all other times.

This field is used during installation to disable OE/RR protocols.  There should only be an entry here during OE/RR installation. The entry is provided by the OE/RR installation process.

also control the default presented to the user: 'Are you sure? '

and signing the orders, this parameter must be set to YES. The Lab Order # is not displayed on the new orders screen.  Only after the order is released to Lab service is the number assigned.  All other users get the

listing regardless of what this parameter is set to.

Here are the package specific parameters that can be modified by the installation site.

steps in the order entry process.  They also have to be given an electronic signature code.  This also has an effect on who can be selected as the person requesting the order.

orders are filed initially with a signature status of Unsigned and a notification for electronic signature is sent to the ordering provider.  2>Yes (Allow S.O.C)  All orders are signed online, but for those cases where an

order is written and signed on the paper chart, you can so specify.  Backdoor orders send a notification for electronic signature and require a signature, unless the order has a Nature of Order set to null.  3>Yes (Allow

S.O.C. & Written)  Is the same as option 2 except that it will allow orders sent from the ancillary packages with a nature of order of Written to be entered without requiring an electronic signature.  4>Yes (Exempt Service

Entered)  Is the same as option 2 except that it will allow orders sent from the ancillary packages that have not defined a nature of order to be entered without requiring an electronic signature.  This is the way

'backdoor' orders were handled before the changes introduced with this new field (added with patch OR*2.5*46) were added.  As of the release of patch OR*2.5*46 only Pharmacy and Lab have a way of dealing with the nature of

order from the backdoor.  So until the rest of the backdoor interfaces can deal with this, option 4 is the least disruptive method of evolution, and still get the enhancements for notification and signing of verbal orders.

For options 1,2,3 & 4, the default for the prompt "Do you want to mark these orders as 'Signed on Chart'" is changed to NO.

review screen.  Setting this parameter to 1 (Select) will force the use of the standard review screen of unsigned orders.  This 'new' screen allow the user to select the order sign by number, range of numbers or all orders

by entering the keyword "all"

If a site sets the UNSIGNED ORDERS SCREEN parameter to Select, the default prompt for all users will be 'Accept Orders'.  This default can be overridden for physicians (holders of the ORES key), by appropriately setting a

new parameter, NEW ORDERS DEFAULT - PROVIDER to 1 - SIGN & RELEASE.

This parameter determines the default prompt for providers when the UNSIGNED ORDERS SCREEN parameter is set to SELECT.  The default is ACCEPT ORDERS.

This field allows parameters to be set up for each location in the hospital that uses OE/RR.

This is the format used when printing chart copies of the orders for the hospital.

This is the format used to print the header of the chart copies of orders for the hospital.

This is the format used to print the footer of the chart copies of orders for the hospital.

the schedule QD would appear on the chart as:

05/17 11:04  GLUCOSE BLOOD SERUM                            Marcus Welby, MD

LB #805    WC   ROUTINE

05/18 11:04  GLUCOSE BLOOD SERUM                            Marcus Welby, MD

LB #806    WC   ROUTINE

05/19 11:04  GLUCOSE BLOOD SERUM                            Marcus Welby, MD

LB #807    WC   ROUTINE

If instead, the field is set to 0 (DON'T EXPAND ON CHART) the same order would appear as:

05/17 11:04  GLUCOSE BLOOD SERUM     QD                     Marcus Welby, MD 05/19 11:04   LB #805    WC   ROUTINE

This field will be checked to decide whether stop dates should be prompted for when generic text orders are entered through OE/RR.  An entry of YES will cause users to be prompted.

Example: An entry of 5 will cause the stop date presented to users to be 5 days from today.

field to 1 to have only the attending physician receive alerts for only inpatients.  The default is to have both attending and primary physician receive all alerts (0).

In any case the ordering provider will always get the alert.

More codes can be added if the need arises, but will require the routine ORB to be modified.

This is the last order number that was processed as part of the Lab order cleanup option.

THERAPY, then chart copies and notifications are sent.  DC's resulting from a CHANGE IN THERAPY are so noted in the text of the DC order.  The order DC'ed will show the name & title of the user that DC'ed the order.

There are 2 cases where the DC Reason prompt does not apply.  DC'ing any Generic (text) order will not get the DC Reason prompt.  Holders of the ORES key will not get the DC Reason prompt.

patient's Ward Location changes.

The automatic DC'ing of orders only happens when one of the protocols OR GUA DC GEN ORD ON TRANS* are placed on the DGPM MOVEMENT EVENTS protocol.

orders context.  This is used as a default for order clean-up.  A new menu of clean-up utilities (ORE MGR) is being exported with items ORE XREF and ORE LAB ORDER CLEANUP.  The ORE XREF (Clean-up OE/RR Cross References)

option will check cross references in file 100 for accuracy.  The ORE LAB ORDER CLEANUP (Clean-up Lab Orders in OE/RR and Lab files) option will check for inconsistencies between OR/RR and Lab files and attempts to correct

them.  The Lab Order clean-up utility on the ORE MGR menu looks at LAPSE DAYS to decide when to put pending lab orders with old start dates in a lapsed state.  Orders with a Lapsed status (l) are no longer shown in the

current orders context.  Another parameters is being exported called LAST LAB CLEAN-UP.  This holds the last ORIFN that was processed during the last clean-up, and is used as a default number to start with the next time

the option is run.

themselves as the requestor even though they may also hold the PROVIDER key.

1 YES (ORELSE)          -restricts only holders of the ORELSE key.

2 YES (ORELSE & OREMAS) -restricts holders of either key.

This parameter, when set to YES, will automatically cancel the Flag Orders Notification and unflag all orders for a patient when a user process a Flagged Orders Notification.

This is a list of the protocols for which corresponding entries have been created in the Order Dialog file.

This is a list of the protocols for which corresponding entries were not successfully created in the Order Dialog file.

This field contains the last entry processed in the New Person file #200 when converting Add Orders menus in the post-init of CPRS.

This field is a flag to determine if the conversion of the Add Orders menus from the Protocol file to the Order Dialog file is completed.

This multiple will store patients that have not yet been converted by the OE/RR version 3.0 (CPRS) orders conversion.  It is maintained by the conversion and should not be edited or updated.