Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields  | All
Print Page as PDF
Global: ^ORD(100.5

Package: Order Entry Results Reporting

Global: ^ORD(100.5


Information

FileMan FileNo FileMan Filename Package
100.5 OE/RR RELEASE EVENTS Order Entry Results Reporting

Description

Accessed By FileMan Db Calls, Total: 2

Package Total Routines
Order Entry Results Reporting 2 OREV3    OREVNT    

Pointed To By FileMan Files, Total: 2

Package Total FileMan Files
Order Entry Results Reporting 2 OE/RR RELEASE EVENTS(#100.5)[14]    OE/RR PATIENT EVENT(#100.2)[2]    

Pointer To FileMan Files, Total: 8

Package Total FileMan Files
Registration 3 MAS MOVEMENT TYPE(#405.2)[7]    WARD LOCATION(#42)[#100.511(.01)]    FACILITY TREATING SPECIALTY(#45.7)[#100.51(.01)]    
Kernel 2 INSTITUTION(#4)[3]    NEW PERSON(#200)[#100.512(1)]    
Order Entry Results Reporting 2 OE/RR RELEASE EVENTS(#100.5)[14]    ORDER DIALOG(#101.41)[4, 5]    
Scheduling 1 HOSPITAL LOCATION(#44)[9]    

Fields, Total: 17

Field # Name Loc Type Details
.01 NAME 0;1 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>50!($L(X)<3)!'(X'?1P.E) X
  • LAST EDITED:  MAR 29, 2002
  • HELP-PROMPT:  Answer must be 3-50 characters in length.
  • DESCRIPTION:  
    This is the name of the event, used to uniquely identify it in the file; it is visible in the Event Editor only.
  • DELETE TEST:  .01,0)= I $$CANDEL^OREV1(100.5)
  • CROSS-REFERENCE:  100.5^B
    1)= S ^ORD(100.5,"B",$E(X,1,30),DA)=""
    2)= K ^ORD(100.5,"B",$E(X,1,30),DA)
.1 SHORT NAME 0;10 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>15!($L(X)<1) X
  • LAST EDITED:  DEC 17, 2001
  • HELP-PROMPT:  Answer must be 1-15 characters in length.
  • DESCRIPTION:  
    This field contains a shorter version of the Display Text, to be used for displaying and grouping delayed orders on the Orders tab where space is limited.
1 INACTIVATED 1;1 DATE

  • INPUT TRANSFORM:  S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  SEP 10, 2002
  • HELP-PROMPT:  Enter the date and time this event was (or will be) inactivated.
  • DESCRIPTION:  This field contains the date and time that this event became inactive; once this date/time has passed, this event may no longer be selected for delaying orders, however any orders already delayed for this event will still
    be released when the event occurs. If this date/time is in the future, this event may continue to be selected for delaying orders until this time passes.
  • RECORD INDEXES:  C (#19)
1.5 ACTIVATION HISTORY 2;0 DATE Multiple #100.52 100.52

  • INDEXED BY:  ACTIVATION DATE/TIME & INACTIVATION DATE/TIME (ACT)
2 TYPE OF EVENT 0;2 SET
************************REQUIRED FIELD************************
  • 'A' FOR ADMISSION;
  • 'T' FOR TRANSFER;
  • 'D' FOR DISCHARGE;
  • 'O' FOR O.R.;
  • 'M' FOR MANUAL RELEASE;

  • LAST EDITED:  MAR 11, 2009
  • HELP-PROMPT:  Enter the type of event that should cause delayed orders to be released.
  • DESCRIPTION:  This is the event that should cause delayed orders to be released to the service(s) for action; for OR (Surgery) events, the orders will be released when TIME PAT IN OR (#130,.205) is entered in the Surgery package.
    Orders delayed for Manual Release will not be automatically released by CPRS at all and can only be released via the "Release to Service" action by a user who is authorized to do so. Authorization is controlled by the
    parameter OREVNT MANUAL RELEASE CONTROL, which lets sites choose whether release is controlled by keys or by the parameter OREVNT MANUAL RELEASE or both.
  • CROSS-REFERENCE:  100.5^ADT
    1)= S ^ORD(100.5,"ADT",$E(X,1,30),DA)=""
    2)= K ^ORD(100.5,"ADT",$E(X,1,30),DA)
3 DIVISION 0;3 POINTER TO INSTITUTION FILE (#4)
************************REQUIRED FIELD************************
INSTITUTION(#4)

  • LAST EDITED:  FEB 13, 2002
  • HELP-PROMPT:  Enter the division this event will be used for.
  • DESCRIPTION:  
    This is the division that this event will apply to; for transfers across divisions, this should be the new division that the patient is going to.
4 EVENT ORDER DIALOG 0;4 POINTER TO ORDER DIALOG FILE (#101.41) ORDER DIALOG(#101.41)

  • INPUT TRANSFORM:  S DIC("S")="I $P(^(0),U,4)=""D""" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  MAY 14, 2002
  • HELP-PROMPT:  Enter the dialog to be used to create an order for this event.
  • DESCRIPTION:  This should be the dialog for a generic order requesting this event; if such an order is not necessary for this event, leave this empty. Unlike other delayed orders, the order created by this dialog will become active
    right away when signed and be visible on the Active Orders view as well as with the delayed orders on the Orders tab.
  • SCREEN:  S DIC("S")="I $P(^(0),U,4)=""D"""
  • EXPLANATION:  Only DIALOG type entries may be selected.
5 ORDER SET/MENU 0;5 POINTER TO ORDER DIALOG FILE (#101.41) ORDER DIALOG(#101.41)

  • INPUT TRANSFORM:  S DIC("S")="I $P(^(0),U,4)'=""P""" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  MAY 14, 2002
  • HELP-PROMPT:  Enter the order set/menu to present to the user when delaying orders for this event.
  • DESCRIPTION:  This is a menu or order set containing items that are either necessary or commonly ordered when this event occurs. It will be invoked right away when first placing delayed orders for this event; if an EVENT ORDER DIALOG
    was defined for this event, this order set will be presented to the user immediately following that dialog. You may enter any type of order dialog except prompt types.
  • SCREEN:  S DIC("S")="I $P(^(0),U,4)'=""P"""
  • EXPLANATION:  Select any ORDER DIALOG entry EXCEPT prompt types.
6 LAPSE IN #DAYS 0;6 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>9999)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  OCT 05, 2001
  • HELP-PROMPT:  Type a Number between 1 and 9999, 0 Decimal Digits
  • DESCRIPTION:  This is the number of days to allow orders for this event to remain delayed for a patient. Patient Events are evaluated whenever delayed orders are acted upon or viewed, and if this number of days has passed since delayed
    orders were entered for this event for the patient then the status of all orders delayed for this event will be changed to "lapsed" and the Patient Event itself will be terminated. The orders can no longer be released to
    the service then.
7 MAS MOVEMENT TYPE 0;7 POINTER TO MAS MOVEMENT TYPE FILE (#405.2) MAS MOVEMENT TYPE(#405.2)

  • INPUT TRANSFORM:  D SCR^OREV1 D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  JAN 10, 2002
  • HELP-PROMPT:  For ADT events, enter an MAS Movement Type to further define the event if necessary.
  • DESCRIPTION:  This is an MAS Movement Type that can further define this event; it is optional, but if defined then it must match the patient's movement data to satisfy the event and cause any delayed orders to be released. For example,
    to have delayed orders released when a patient returns from pass enter the movement type of AUTH ABSENCE 96 HOURS OR LESS, or leave this field empty to have the transfer event defined by other criteria such as treating
    specialty or ward location.
  • SCREEN:  D SCR^OREV1
  • EXPLANATION:  You may only select MAS MOVEMENT TYPES that are associated with the TYPE field selected above.
8 DISPLAY TEXT 0;8 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>60!($L(X)<3) X
  • LAST EDITED:  SEP 10, 2002
  • HELP-PROMPT:  Answer must be 3-60 characters in length.
  • DESCRIPTION:  
    This field is the name of the event as it will appear to the user in CPRS.
  • RECORD INDEXES:  C (#19)
9 ORDERING PARAMETERS LOCATION 0;9 POINTER TO HOSPITAL LOCATION FILE (#44) HOSPITAL LOCATION(#44)

  • LAST EDITED:  MAR 05, 2002
  • HELP-PROMPT:  The location specified in this field is the location the release event will use to retrieve its ordering parameters.
  • DESCRIPTION:  Many order dialogs use parameters that depend on location; this field will be used as the default location for retrieving those parameter values when delaying orders to this event. The patient's actual location will be
    saved with the order at the time of its release.
10 INCLUDED TREATING SPECIALTIES TS;0 POINTER Multiple #100.51 100.51

  • DESCRIPTION:  
    These are treating specialties that can satisfy this event; if the patient's new specialty matches one in this list then orders delayed for this event may be released.
11 INCLUDED LOCATIONS LOC;0 POINTER Multiple #100.511 100.511

  • DESCRIPTION:  
    These are ward locations that can satisfy this event; if the patient's new location matches one in this list then orders delayed for this event may be released.
12 EDIT HISTORY 9;0 DATE Multiple #100.512 100.512
13 COPY ACTIVE ORDERS 0;11 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  MAY 13, 2002
  • HELP-PROMPT:  Enter YES if the user should be prompted to copy active orders when writing new delayed orders for this event.
  • DESCRIPTION:  This field determines whether or not the user will be presented with the patient's active orders, which may then be copied to the delayed event being created.
    If this field is set to no then the user will not see the patient's active orders and will not be allowed to copy any current orders.
    If this field is set to yes then the user will be shown the patient's active orders and the user may select orders to be copied to the delayed event. The list of active orders will be presented to the user after the ORDER
    DIALOG for the release event is processed (if it exists) and before the ORDER SET/MENU for the release event is processed (if it exists).
14 PARENT 0;12 POINTER TO OE/RR RELEASE EVENTS FILE (#100.5) OE/RR RELEASE EVENTS(#100.5)

  • LAST EDITED:  AUG 28, 2002
  • HELP-PROMPT:  Enter release event that will be the "parent" event for this event
  • DESCRIPTION:  For release events that have a common trigger event (e.g. same treating specialty or same locations) but require different names or display text a parent-child relationship can be set up. The parent contains the base
    trigger event logic while the child contains the information unique to this event. In a sense, the child events are "synonyms" to the parent event as all childen are related to the parent. When the trigger event occurs
    that would release orders for the parent all the child orders related to that parent are also released.
  • CROSS-REFERENCE:  100.5^DAD
    1)= S ^ORD(100.5,"DAD",$E(X,1,30),DA)=""
    2)= K ^ORD(100.5,"DAD",$E(X,1,30),DA)
Info |  Desc |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields  | All