The Master Data Model for Veteran Care

Developer Documentation » VDM » Oe_rr_Release_Events-100_5

Oe/rr Release Events (100.5)

This file contains the locally-defined events that can release delayed orders within each division. It is strongly recommended that this file not be edited with File Manager. Please use the edit options provided within CPRS.

Global: ^ORD(100.5,

Domain: Non-Clinical

Properties

Label/Field Name Field # Description Datatype Attributes Range
Name
  name
.01 This is the name of the event, used to uniquely identify it in the file;
it is visible in the Event Editor only.
STRING INDEXED
REQUIRED
 
Short Name
  short_name
.1 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.
STRING    
Inactivated
  inactivated
1 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.
DATE-TIME    
Activation History
  activation_history
1.5   OBJECT   Activation_History-100_52
Type Of Event
  type_of_event
2 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.
ENUMERATION INDEXED
REQUIRED
TRANSFER: T
ADMISSION: A
O.R.: O
MANUAL RELEASE: M
DISCHARGE: D
Division
  division
3 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.
POINTER REQUIRED Institution-4
Event Order Dialog
  event_order_dialog
4 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.
POINTER   Order_Dialog-101_41
Order Set/menu
  order_set_menu
5 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.
POINTER   Order_Dialog-101_41
Lapse In #days
  lapse_in_numberdays
6 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.
NUMERIC    
Mas Movement Type
  mas_movement_type
7 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.
POINTER   Mas_Movement_Type-405_2
Display Text
  display_text
8 This field is the name of the event as it will appear to the user in
CPRS.
STRING REQUIRED  
Ordering Parameters Location
  ordering_parameters_location
9 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.
POINTER   Hospital_Location-44
Included Treating Specialties
  included_treating_specialties
10 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.
OBJECT   Included_Treating_Specialties-100_51
Included Locations
  included_locations
11 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.
POINTER   Ward_Location-42
Edit History
  edit_history
12   OBJECT   Edit_History-100_512
Copy Active Orders
  copy_active_orders
13 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).
BOOLEAN   false: 0
true: 1
Parent
  parent
14 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.
POINTER INDEXED Oe_rr_Release_Events-100_5

↑ Return to top

Sub-Files

Activation History (100.52)

ID
Activation_History-100_52

Properties

Label/Field Name Field # Description Datatype Attributes Range
Activation Date/time
  activation_date_time
.01   DATE-TIME INDEXED
REQUIRED
 
Inactivation Date/time
  inactivation_date_time
1   DATE-TIME    

↑ Return to top

Included Treating Specialties (100.51)

ID
Included_Treating_Specialties-100_51

Properties

Label/Field Name Field # Description Datatype Attributes Range
Included Treating Specialties
  included_treating_specialties
.01 This is a treating specialty that can satisfy this event; if defined,
then the patient’s new specialty must match one in this list for any
delayed orders to be released. A specialty may only be included in one
active delay event at a time.

If locations are also defined for this event then both the treating
specialty and the location must match for orders to be released.
POINTER INDEXED
REQUIRED
Facility_Treating_Specialty-45_7
Default
  default
1   BOOLEAN INDEXED true: 1

↑ Return to top

Edit History (100.512)

ID
Edit_History-100_512

Properties

Label/Field Name Field # Description Datatype Attributes Range
Edit History
  edit_history
.01 This field will track when an event was added. It also tracks when
the edit option was used on this event.
DATE-TIME INDEXED
REQUIRED
 
Who Entered/edited
  who_entered_edited
1 This field identifies the person who entered or edited the event POINTER   New_Person-200
Action
  action
2 This field describes whether the event was newly entered or if it
was edited.
ENUMERATION   EDIT: E
NEW: N

↑ Return to top


Document generated on August 31st 2017, 2:55:41 pm