Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields |  Found Entries |  External References |  Global Variables Directly Accessed |  Local Variables  | All
Print Page as PDF
Global: ^ORD(100.99

Package: Order Entry Results Reporting

Global: ^ORD(100.99


Information

FileMan FileNo FileMan Filename Package
100.99 ORDER PARAMETERS Order Entry Results Reporting

Description

Directly Accessed By Routines, Total: 62

Package Total Routines
General Medical Record - Vitals 19 GMRV SITE FILE EDIT    GMRVOR DGPM    GMRVORADMIT V/M    GMRVORB/P    GMRVORCG    GMRVORCVP    GMRVORHT    GMRVORP CUM REPORT
GMRVORP DISP VITALS    GMRVORP SF511    GMRVORPB/P    GMRVORPO    GMRVORPR B/P    GMRVORPULSE    GMRVORRESP    GMRVORTEMP
GMRVORTPR B/P    GMRVORWT    ^GMRD(120.57    
Order Entry Results Reporting 18 ORB3C1    ^ORD(100.99    CONVERTED PROTOCOLS    HOSPITAL SITE    OR3 PATIENTS TO CONVERT    ORCMEDT1    ORCONV0    ORCONVRT
ORCPOST    ORPFCNVT    ORVOM    ORVOM0    ORX    ORY7    PARAMETER    PROTOCOL SET
SYSTEM PARAMETERS    UNSUCCESSFUL DIALOGS    
Lab Service 7 LR7OB1    LR7OC0    LR7OV2    LRCENDE1    LRDPA    LROR    LROR1    
Kernel 4 XPDINIT3    XPDINIT4    XQORO    ^ORD(101    
VA FileMan 3 DIFROM12    DIPKINI3    DIPKINI4    
Automated Information Collection System 2 IBDEINI3    IBDEINI4    
Surgery 2 SROERR    SROERRPO    
Consult Request Tracking 1 GMRCPOR    
Health Summary 1 GMTSXQ13    
Income Verification Match 1 IVM20E    
List Manager 1 VALMXQ15    
PCE Patient Care Encounter 1 PXIPOST    
Radiology Nuclear Medicine 1 RAORDU    
Registration 1 DGVPP    

Accessed By FileMan Db Calls, Total: 3

Package Total Routines
Automated Information Collection System 1 IBDEINI4    
Order Entry Results Reporting 1 ORCMEDT1    
PCE Patient Care Encounter 1 PXIPOST    

Pointer To FileMan Files, Total: 10

Package Total FileMan Files
Kernel 4 DEVICE(#3.5)[#100.9901(.05), #100.99011(.02), #100.9925(.04), #100.9925(.05), #100.9925(.06), #100.9925(1)]    OPTION(#19)[4]    PACKAGE(#9.4)[#100.9901(.01), #100.995(.01)]    PROTOCOL(#101)[4, #100.99101(.01), #100.99141(.01), #100.9951(.01), #100.99511(.01), #100.9955(.03)]    
Order Entry Results Reporting 3 ORDER(#100)[14]    OE/RR PRINT FORMATS(#100.23)[26, 27, 28, #100.9901(.03), #100.9901(.04), #100.9901(.06), #100.9901(.07), #100.9901(.08)]    DISPLAY GROUP(#100.98)[#100.995(1.1)]    
Registration 1 PATIENT(#2)[3.05, #100.9903(.01)]    
Scheduling 1 HOSPITAL LOCATION(#44)[#100.99011(.01), #100.9925(.01)]    
VA FileMan 1 FILE(#1)[#100.9955(.02)]    

Fields, Total: 58

Field # Name Loc Type Details
.001 NUMBER NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>1)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  MAR 02, 1989
  • HELP-PROMPT:  Type a Number between 1 and 1, 0 Decimal Digits
  • DESCRIPTION:  
    This is the internal number of this file.
    UNEDITABLE
.01 NAME 0;1 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:X[""""!($A(X)=45)!'(X'?1P.E) X
  • LAST EDITED:  JUL 26, 1989
  • HELP-PROMPT:  There can be only one entry.
  • DESCRIPTION:  
    This is an arbitrary name for the single entry in this file.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • CROSS-REFERENCE:  100.99^B
    1)= S ^ORD(100.99,"B",$E(X,1,30),DA)=""
    2)= K ^ORD(100.99,"B",$E(X,1,30),DA)
1 CURRENT ORDER # 0;2 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>9999999999)!(X<0)!(X?.E1"."1N.N) X
  • LAST EDITED:  AUG 13, 1987
  • HELP-PROMPT:  TYPE A WHOLE NUMBER BETWEEN 0 AND 9999999999
  • DESCRIPTION:  
    This is the current order # on the system.
    UNEDITABLE
2 SYSTEM PARAMETERS 1;0 Multiple #100.992 100.992

  • HELP-PROMPT:  Enter the names of the CPU's on your system.
  • DESCRIPTION:  
    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.
3 TREATING SPECIALTY 0;3 SET
  • '0' FOR NOT ASK;
  • '1' FOR ASK;

  • LAST EDITED:  DEC 01, 1987
  • HELP-PROMPT:  Enter 0 to not ask, or 1 to ask for treating specialty when placing orders.
  • DESCRIPTION:  This is a site parameter which controls the prompt for TREATING SPECIALTY when defining patient demographics. If set to NOT ASK, the prompt will not be displayed; and TREATING SPECIALTY will only be defined for the order
    if it can be found.
3.01 OR3 CONVERSION COMPLETE? CONV;1 SET
************************REQUIRED FIELD************************
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  AUG 02, 1997
  • HELP-PROMPT:  Will be entered by conversion as 1 when conversion complete or 0 if in progress.
  • DESCRIPTION:  This field is maintained by the Order Entry/Results Reporting version 3.0 conversion of orders. It will be initialized to 0 at the start of the conversion and updated to 1 when the conversion is complete. It is important
    that this field not be edited.
3.02 OR3 INPATIENT CONVERSION START CONV;2 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  AUG 02, 1997
  • HELP-PROMPT:  This field will contain the date/time the conversion of inpatients started
  • DESCRIPTION:  
    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.
3.03 OR3 INPATIENT CONVERSION STOP CONV;3 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ESTR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  AUG 02, 1997
  • HELP-PROMPT:  This field will contain the time the conversion of orders for inpatients stopped.
  • DESCRIPTION:  
    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.
3.04 OR3 INPATIENT LOCATION UP TO CONV;4 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>50!($L(X)<2) X
  • LAST EDITED:  AUG 06, 1997
  • HELP-PROMPT:  Answer must be 2-50 characters in length.
  • DESCRIPTION:  
    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.
3.05 OR3 INPATIENT DFN UP TO CONV;5 POINTER TO PATIENT FILE (#2) PATIENT(#2)

  • LAST EDITED:  AUG 06, 1997
  • HELP-PROMPT:  This field will contain the inpatient record for which orders are currently being converted.
  • DESCRIPTION:  
    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.
3.06 OR3 BACKGROUND JOB START CONV;6 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  AUG 03, 1997
  • HELP-PROMPT:  This field will contain the time the conversion of orders for patients with recent and future activity started.
  • DESCRIPTION:  This field is maintained by the OE/RR version 3 orders conversion. If the conversion is up to phase 2 (which converts orders for recently seen patients and those scheduled to be seen in the near future), this field will
    contain the date phase 2 of the conversion started.
3.07 OR3 BACKGROUND JOB STOP CONV;7 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  AUG 03, 1997
  • HELP-PROMPT:  This field will contain the time the conversion of orders for recently seen patients completed.
  • DESCRIPTION:  This field is maintained by the OE/RR version 3 orders conversion. If the conversion has completed phase 2 (which converts orders for recently seen patients and those scheduled to be seen in the near future), this field
    will contain the date phase 2 of the conversion completed.
3.08 OR3 BACKGROUND JOB STAGE CONV;8 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>7)!(X<0)!(X?.E1"."1N.N) X
  • LAST EDITED:  OCT 26, 1997
  • HELP-PROMPT:  Type a Number between 0 and 7, 0 Decimal Digits
  • DESCRIPTION:  This field is maintained by the OE/RR version 3 conversion. If the conversion is in the background job, this will keep track of the stage of the background process it is on. Once the background job is complete, this
    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
3.09 OR3 BACKGROUND JOB UP TO CONV;9 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<1) X
  • LAST EDITED:  AUG 06, 1997
  • HELP-PROMPT:  Answer must be 1-30 characters in length.
  • DESCRIPTION:  This field is maintained by the OE/RR orders conversion. If the background job process is running, this will keep track of the last value processed for the current stage. If the background job stops and needs to be
    restarted, this field will allow restart from where the process left off.
3.1 OR3 BACKGROUND JOB TASK CONV;10 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999999999999999)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  AUG 06, 1997
  • HELP-PROMPT:  Type a Number between 1 and 999999999999999, 0 Decimal Digits
  • DESCRIPTION:  This field is maintained by the OE/RR orders conversion. If the conversion is in the background job portion, this field will contain the task number (ZTSK) of the background process job. This will assist in providing the
    status of the job and allowing restart should the job stop.
3.11 OR3 BACKGROUND JOB STOP? CONV;11 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  AUG 06, 1997
  • HELP-PROMPT:  Enter YES to cause the conversion to cleanly stop. Otherwise, enter NO.
  • DESCRIPTION:  Should you wish to stop the background job process for any reason during the OE/RR version 3.0 orders conversion, you can call STOP^OR3CONV and this field will be set to yes. The conversion will check for this field and
    when it finds it set, it will allow the conversion to make a clean stop. RESTART^OR3CONV may be used to restart the task.
3.12 OR3 PATIENTS CONVERTED CONV;12 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999999999999999)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  AUG 15, 1997
  • HELP-PROMPT:  Type a Number between 1 and 999999999999999, 0 Decimal Digits
  • DESCRIPTION:  
    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.
4 ADD MENU DEFAULT 0;9 VARIABLE POINTER PROTOCOL(#101)  OPTION(#19)  

  • LAST EDITED:  MAR 18, 1989
  • HELP-PROMPT:  To define a system wide menu for adding orders, enter that menu here.
  • DESCRIPTION:  This field is the default menu used to add orders. If this field has no entry, then the ORADD menu will be used as the default. This field is for sites that wish to customize the ORADD menu by creating another menu in a
    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.
5 PACKAGE PARAMETERS 5;0 POINTER Multiple #100.995 100.995

  • HELP-PROMPT:  Do not edit these parameters unless instructed to by package release notes.
  • DESCRIPTION:  
    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.
6 SHOW STATUS DESCRIPTION 0;10 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAR 28, 1989
  • HELP-PROMPT:  Enter YES to have the full status description displayed on the detailed order display.
  • DESCRIPTION:  
    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.
7 SHOW PATIENT NAME 0;11 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  AUG 17, 1989
  • HELP-PROMPT:  Enter YES to have the patient name displayed every time a protocol is invoked in OE/RR.
  • DESCRIPTION:  
    This field allows the patient name to be displayed each time an order action is executed after the subheader during ADD NEW ORDERS option.
8 ACTIVE ORDERS CONTEXT HOURS 0;12 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>72)!(X<0)!(X?.E1"."1N.N) X
  • LAST EDITED:  JUL 13, 1991
  • HELP-PROMPT:  Enter the number of hours to include completed, DC'ed, Expired orders in an Active Orders display.
  • DESCRIPTION:  
    This field defines the number of hours that orders remain in the "Current Orders" context after they have been completed.
9 REVIEW ON PATIENT MVMT 0;13 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  OCT 01, 1990
  • HELP-PROMPT:  Enter YES to review patient orders whenever a patient movement or clinic appointmemt occurs.
  • DESCRIPTION:  
    This field allows orders to be reviewed when a patient is transferred or discharged, and when a clinic appointment is made or cancelled.
10 SINGLE USER/SUSPEND FILER 0;4 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JAN 24, 1989
  • HELP-PROMPT:  Do not enter anything in this field.
  • DESCRIPTION:  This is a parameter that can be set for single user systems (PC's) that do not allow multiple jobs to run simultaneously. This is needed since OE/RR uses a background filer. If this field is set to YES then tasks that
    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: @
11 INITIALS ON SUMMARY 0;14 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  NOV 27, 1990
  • HELP-PROMPT:  Enter YES to have the initials of the person who entered the order on the OE/RR summary reports.
  • DESCRIPTION:  
    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.
12 DEFAULT PROVIDER 0;15 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  JAN 10, 1991
  • HELP-PROMPT:  Enter YES to have the attending physician as a default prompt when entering orders.
  • DESCRIPTION:  
    This field allows the attending physician to be prompted as a default when adding new orders.
13 LAST PURGE DATE 0;5 DATE

  • INPUT TRANSFORM:  S %DT="ESTX" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  MAR 06, 1997
  • HELP-PROMPT:  Do not enter anything in this field.
  • DESCRIPTION:  
    This field contains the date that the OE/RR purge utility was last started.
    UNEDITABLE
14 LAST ORDER PURGED 0;6 POINTER TO ORDER FILE (#100) ORDER(#100)

  • LAST EDITED:  MAR 15, 1990
  • HELP-PROMPT:  Do not enter anything in this field.
  • DESCRIPTION:  
    This field contains the last order number purged by the OE/RR purge utility.
    UNEDITABLE
15 ERROR DAYS 0;7 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>15)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  MAR 15, 1989
  • HELP-PROMPT:  Enter the number of days you want OE/RR errors to remain on the system.
  • DESCRIPTION:  
    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.
16 DEBUG 0;8 SET
  • '0' FOR OFF;
  • '1' FOR ON;

  • LAST EDITED:  MAR 18, 1989
  • HELP-PROMPT:  Enter YES to put OE/RR in debug mode.
  • DESCRIPTION:  This field is used by package developers to help debug transaction failures with their package and OE/RR. If this field is turned ON, then transactions are not processed thru the background filer and a message is
    displayed when a transaction fails. This field should be turned OFF at all other times.
17 INSTALLATION FLAG 0;16 DATE

  • INPUT TRANSFORM:  S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  APR 29, 1992
  • HELP-PROMPT:  An entry in this field disables protocols in OE/RR.
  • DESCRIPTION:  
    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.
18 CONFIRM PROVIDER 0;17 SET
  • '0' FOR NO;
  • '1' FOR YES (Default NO);
  • '2' FOR YES (Exclude ORES);
  • '3' FOR YES (Default YES);

  • LAST EDITED:  APR 11, 1996
  • DESCRIPTION:  This field will allow an additional prompt to confirm the provider selection when adding new orders. Entering 2 in this field will exclude holders of the ORES key (providers) from this check. Notice that these parameters
    also control the default presented to the user: 'Are you sure? '
19 SHOW LAB # 0;18 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAY 22, 1996
  • DESCRIPTION:  This field controls the listing of lab orders for holders of the ORES key, after the electronic signature has been entered when entering new orders. If Physicians want to see the lab order # with the order after entering
    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.
20 PACKAGE SITE PARAMETERS 20;0 POINTER Multiple #100.9901 100.9901

  • HELP-PROMPT:  Enter Hospital site parameters here.
  • DESCRIPTION:  
    Here are the package specific parameters that can be modified by the installation site.
21 ELECTRONIC SIGNATURE 2;1 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  FEB 20, 1991
  • HELP-PROMPT:  Enter YES to turn electronic signature functionality on.
  • DESCRIPTION:  This field allows electronic signature functionality to be used. Use of this functionality requires some initial setup before it can be turned on. Users have to be assigned keys that allow them to perform verification
    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.
22 ELECTRONIC RECORD 2;2 SET
  • '0' FOR NO;
  • '1' FOR YES;
  • '2' FOR YES (ALLOW S.O.C.);
  • '3' FOR YES (ALLOW S.O.C & WRITTEN);
  • '4' FOR YES (Exempt Service Entered);

  • LAST EDITED:  MAY 24, 1996
  • DESCRIPTION:  A site can use this field to select 1 of 4 modes for Electronic Signature: 0>No change from current Electronic Signature functionality. 1>Yes All orders must be signed online. Signature on chart is not allowed All
    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.
23 UNSIGNED ORDERS SCREEN 2;3 SET
  • '0' FOR All;
  • '1' FOR Select;

  • LAST EDITED:  FEB 15, 1996
  • DESCRIPTION:  This field controls the type of review screen that is used for new/unsigned orders. Without this parameter, the user has to sign all orders when entering new orders or presented with new /unsigned orders when leaving the
    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.
24 NEW ORDERS DEFAULT - PROVIDER 2;4 SET
  • '0' FOR ACCEPT ORDERS;
  • '1' FOR SIGN & RELEASE;

  • LAST EDITED:  MAR 11, 1996
  • DESCRIPTION:  
    This parameter determines the default prompt for providers when the UNSIGNED ORDERS SCREEN parameter is set to SELECT. The default is ACCEPT ORDERS.
25 HOSPITAL SITE 25;0 POINTER Multiple #100.9925 100.9925

  • HELP-PROMPT:  Enter parameters here for various sites in the hospital (wards, clinics, etc.)
  • DESCRIPTION:  
    This field allows parameters to be set up for each location in the hospital that uses OE/RR.
26 CHART COPY FORMAT 2;6 POINTER TO OE/RR PRINT FORMATS FILE (#100.23) OE/RR PRINT FORMATS(#100.23)

  • LAST EDITED:  APR 18, 1991
  • HELP-PROMPT:  Enter the format for the chart copy.
  • DESCRIPTION:  
    This is the format used when printing chart copies of the orders for the hospital.
27 CHART COPY HEADER 2;7 POINTER TO OE/RR PRINT FORMATS FILE (#100.23) OE/RR PRINT FORMATS(#100.23)

  • LAST EDITED:  APR 18, 1991
  • HELP-PROMPT:  Enter the format for the chart copy header.
  • DESCRIPTION:  
    This is the format used to print the header of the chart copies of orders for the hospital.
28 CHART COPY FOOTER 2;8 POINTER TO OE/RR PRINT FORMATS FILE (#100.23) OE/RR PRINT FORMATS(#100.23)

  • LAST EDITED:  APR 18, 1991
  • HELP-PROMPT:  Enter the format for the chart copy footer.
  • DESCRIPTION:  
    This is the format used to print the footer of the chart copies of orders for the hospital.
29 EXPAND CONTINUOUS ORDERS 2;5 SET
  • '1' FOR EXPAND ON CHART;
  • '0' FOR DON'T EXPAND ON CHART;

  • LAST EDITED:  MAY 17, 1991
  • HELP-PROMPT:  Specify how continuous orders are to appear on the chart copies.
  • DESCRIPTION:  This is a site parameter to enable continuous orders (i.e., orders with a continuous schedule, e.g., QD or Q4H) to be expanded or not on the chart copy. If set to 1 (EXPAND ON CHART) an order for GLUCOSE BLOOD SERUM with
    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
30 STOP DATES FOR GENERIC ORDERS 2;9 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  MAY 09, 1995
  • HELP-PROMPT:  An entry of YES will prompt users for the entry of a stop date to be associated with generic text orders.
  • DESCRIPTION:  
    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.
31 DEFAULT GENERIC STOP DATE 2;10 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>365)!(X<0)!(X?.E1"."1N.N) X
  • LAST EDITED:  OCT 24, 1995
  • HELP-PROMPT:  Type a Number between 0 and 365, 0 Decimal Digits
  • DESCRIPTION:  This field will accept the number of days in the future that will determine the default stop date presented to users when placing generic orders.
    Example: An entry of 5 will cause the stop date presented to users to be 5 days from today.
32 NOTIFICATION TO PHYSICIAN 2;11 SET
  • '0' FOR ALL;
  • '1' FOR INPAT ATTENDING;

  • LAST EDITED:  MAR 12, 1996
  • DESCRIPTION:  This field controls the sending of notifications to attending and primary physicians. Set this field to 0 to have both the attending an primary physicians receive alerts for both inpatients and outpatients. Set this
    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.
  • TECHNICAL DESCR:  
    More codes can be added if the need arises, but will require the routine ORB to be modified.
33 LAST LAB CLEAN-UP # 2;12 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99999999999)!(X<1)!(X?.E1"."2N.N) X
  • LAST EDITED:  MAR 12, 1996
  • HELP-PROMPT:  Type a Number between 1 and 99999999999, 1 Decimal Digit
  • DESCRIPTION:  
    This is the last order number that was processed as part of the Lab order cleanup option.
34 ALLOW DC REASON 2;13 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAR 23, 1996
  • DESCRIPTION:  This field allows the user to enter a reason for entering a DC order. If the reason is DUPLICATE ORDER, then the order is simply DC'ed and no chart copies are printed or notifications sent. If the reason is CHANGE IN
    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.
35 ALLOW DC REASON BACKDOOR 2;14 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  MAR 26, 1996
  • DESCRIPTION:  This field allows the same functionality as the parameter: ALLOW DC REASON for orders DC'ed from the ancillary packages (backdoor).
36 DC OF GENERIC ORDERS 2;15 SET
  • '0' FOR WARD TRANSFER;
  • '1' FOR SPECIALTY TRANSFER;

  • LAST EDITED:  MAR 28, 1996
  • DESCRIPTION:  This field controls the DC'ing of Generic orders. If this field is set to 1, then Generic orders are DC'ed only when a patient's Treating Specialty changes. If set to 0, then the Generic orders are DC'ed when the
    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.
37 LAPSE DAYS 2;16 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>900)!(X<7)!(X?.E1"."1N.N) X
  • LAST EDITED:  MAR 28, 1996
  • HELP-PROMPT:  Type a Number between 7 and 900, 0 Decimal Digits
  • DESCRIPTION:  The Lab Order clean-up utility on the ORE MGR menu looks at this field 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. 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.
38 RESTRICT REQUESTOR 2;17 SET
  • '0' FOR NO;
  • '1' FOR YES (ORELSE);
  • '2' FOR YES (ORELSE & OREMAS);

  • LAST EDITED:  APR 22, 1996
  • DESCRIPTION:  This field allows a site to restrict the selection of providers when adding new orders at the 'Requesting CLINICIAN: ' prompt for holders of the ORELSE and OREMAS key. The restriction being that they cannot select
    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.
39 AUTO UNFLAG 2;18 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  APR 17, 1996
  • DESCRIPTION:  
    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.
101 CONVERTED PROTOCOLS 101;0 POINTER Multiple #100.99101 100.99101

  • DESCRIPTION:  
    This is a list of the protocols for which corresponding entries have been created in the Order Dialog file.
101.41 UNSUCCESSFUL DIALOGS 101.41;0 POINTER Multiple #100.99141 100.99141

  • DESCRIPTION:  
    This is a list of the protocols for which corresponding entries were not successfully created in the Order Dialog file.
200 LAST USER PREFERENCE CONVERTED 200;1 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>9999999)!(X<-1)!(X?.E1"."1N.N) X
  • LAST EDITED:  SEP 15, 1997
  • HELP-PROMPT:  Type a Number between -1 and 9999999, 0 Decimal Digits
  • DESCRIPTION:  
    This field contains the last entry processed in the New Person file #200 when converting Add Orders menus in the post-init of CPRS.
201 CONVERSION COMPLETED 200;2 SET
  • '1' FOR YES;

  • LAST EDITED:  SEP 15, 1997
  • HELP-PROMPT:  Enter YES if the menu conversion is completed.
  • DESCRIPTION:  
    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.
300 OR3 PATIENTS TO CONVERT PTCONV;0 POINTER Multiple #100.9903 100.9903

  • DESCRIPTION:  
    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.

Found Entries, Total: 1

NAME: HOSPITAL    

External References

Name Field # of Occurrence
^%DT 3.02+1, 3.03+1, 3.06+1, 3.07+1, 13+1, 17+1

Global Variables Directly Accessed

Name Line Occurrences  (* Changed,  ! Killed)
^ORD(100.99 - [#100.99] .01(XREF 1S), .01(XREF 1K)

Local Variables

Legend:

>> Not killed explicitly
* Changed
! Killed
~ Newed

Name Field # of Occurrence
>> %DT 3.02+1*, 3.03+1*, 3.06+1*, 3.07+1*, 13+1*, 17+1*
>> DA .01(XREF 1S), .01(XREF 1K)
X .001+1!, .01+1!, .01(XREF 1S), .01(XREF 1K), 1+1!, 3.02+1*!, 3.03+1*!, 3.04+1!, 3.06+1*!, 3.07+1*!
, 3.08+1!, 3.09+1!, 3.1+1!, 3.12+1!, 8+1!, 13+1*!, 15+1!, 17+1*!, 31+1!, 33+1!
, 37+1!, 200+1!
>> Y 3.02+1, 3.03+1, 3.06+1, 3.07+1, 13+1, 17+1
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields |  Found Entries |  External References |  Global Variables Directly Accessed |  Local Variables  | All