STANDARD DATA DICTIONARY #8930.8 -- USR ACTION FILE 3/24/25 PAGE 1
STORED IN ^USR(8930.8, (24 ENTRIES) SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA (VERSION 1.0)
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
This file encodes actions which occur in connection with clinical narrative documents.
These actions are referenced by entries in the User Authorization/Subscription file to associate users with actions.
This file contains 2 kinds of actions: those a user is authorized to perform on a document, and those a user subscribes to for a
document. For example, a user is authorized to perform the Signature action, but a user subscribes to ("signs up to receive") a
Notification action.
DD ACCESS: @
RD ACCESS: @
WR ACCESS: @
DEL ACCESS: @
LAYGO ACCESS: @
AUDIT ACCESS: @
IDENTIFIED BY:
"PHRASE": D EN^DDIOL(" "_$$GET1^DIQ(8930.8,+Y,.08),"","?0")
POINTED TO BY: PROCESSING STEP field (#.01) of the PROCESSING STEPS sub-field (#8925.113) of the TIU DOCUMENT DEFINITION File
(#8925.1)
PROCESSING STEPS field (#.01) of the PROCESSING STEPS sub-field (#8925.951) of the TIU DOCUMENT PARAMETERS File
(#8925.95)
ACTION field (#.03) of the USR AUTHORIZATION/SUBSCRIPTION File (#8930.1)
IMPLIED EVENT field (#.01) of the IMPLIED EVENT sub-field (#8930.81) of the USR ACTION File (#8930.8)
CROSS
REFERENCED BY: NAME(B)
8930.8,.01 NAME 0;1 FREE TEXT (Required)
ACTION NAME
INPUT TRANSFORM: K:$L(X)>30!($L(X)<3)!'(X'?1P.E) X
LAST EDITED: FEB 25, 1997
HELP-PROMPT: Please enter the name of the event.
DESCRIPTION: These are names of events which occur in connection with clinical narrative documents. These are
referenced by the User Authorization/Subscription file to associate users with events.
TECHNICAL DESCR: Warning about changing an action name:
Action NAMES are checked when evaluating permissions in CANDO^TIULP. In addition, action NAME:
ATTACH ID ENTRY is checked in input template USR DEFINE AUTHORIZATIONS when action ATTACH ID ENTRY
is entered.
These areas (and possibly other new areas) MUST be updated if the NAME of an action is changed.
CROSS-REFERENCE: 8930.8^B
1)= S ^USR(8930.8,"B",$E(X,1,30),DA)=""
2)= K ^USR(8930.8,"B",$E(X,1,30),DA)
8930.8,.02 EVENT TYPE 0;2 SET
'A' FOR authorization;
'S' FOR subscription;
LAST EDITED: FEB 09, 1995
HELP-PROMPT: Indicate the type of event you are defining.
DESCRIPTION: This file contains two types of events: those a user is AUTHORIZED to perform and those a user
SUBSCRIBES to. For example, a user is authorized to perform the Signature event, but a user
subscribes to ("signs up to receive") a Notification event. This field helps to define the meaning
of an event and its relationship to a user.
8930.8,.03 APPLIES TO 0;3 SET
'DOC' FOR document;
'DEF' FOR definition;
LAST EDITED: FEB 07, 1995
HELP-PROMPT: Indicate whether event applies to documents or their definitions
8930.8,.04 ASSOCIATED PROTOCOL 0;4 POINTER TO PROTOCOL FILE (#101)
LAST EDITED: JAN 09, 1997
HELP-PROMPT: Indicate which Protocol corresponds to this event.
8930.8,.05 USER VERB 0;5 FREE TEXT
INPUT TRANSFORM: K:$L(X)>50!($L(X)<3) X
LAST EDITED: JUN 14, 2001
HELP-PROMPT: Example: In "You cannot SIGN this unsigned document", the user verb is "SIGN". Uppercase, 3-50
characters.
DESCRIPTION: This word or phrase is displayed in explanatory messages when the user is denied authority to
perform the given action. Such a message might read, "You cannot SIGN this unsigned progress
note", where the USER VERB is "SIGN".
The USER VERB must make grammatical sense inserted in a sentence of the form: "You cannot [ ]
this unsigned progress note."
Please use uppercase, 3-50 characters.
8930.8,.06 DOCUMENT VERB 0;6 FREE TEXT
INPUT TRANSFORM: K:$L(X)>40!($L(X)<3) X
LAST EDITED: FEB 15, 2000
HELP-PROMPT: Example: In "An unsigned progress note can BE SIGNED by an author/dictator", the document verb is
"BE SIGNED". Uppercase,3-40 characters.
DESCRIPTION: This word or phrase is used in business rule options when displaying an authorization in sentence
form.
A business rule might read: "An unsigned Progress Note can BE SIGNED by an author/dictator." The
DOCUMENT VERB in this rule is "BE SIGNED".
The DOCUMENT VERB must make grammatical sense inserted in a sentence of the form: "An unsigned
progress note can [ ] by an author/dictator."
Please use uppercase, 3-40 characters.
8930.8,.07 USER VERB MODIFIER 0;7 FREE TEXT
INPUT TRANSFORM: K:$L(X)>30!($L(X)<3) X
LAST EDITED: JUN 14, 2001
HELP-PROMPT: Example: In "You cannot LINK this unsigned note with a request", the user verb modifier is "with a
request". Lowercase, 3-30 characters.
DESCRIPTION: Sometimes, in writing messages to the user denying a permission, the action must be split into two
parts. In such cases, the USER VERB MODIFIER is the second part.
Example: In "You cannot LINK this UNSIGNED PROGRESS NOTE with a request", the USER VERB is "LINK",
and the USER VERB MODIFIER is "with a request".
The USER VERB MODIFIER must make grammatical sense when inserted in:
"You cannot LINK this UNSIGNED PROGRESS NOTE [ ]."
Please use lowercase, 3-30 characters.
If an action has an IDENTIFYING PHRASE or a USER VERB MODIFIER, the business rule ADD or EDIT
action presents the user with a clarifying note about the rule they are creating immediately after
the user enters an action.
8930.8,.08 IDENTIFYING PHRASE 3;1 FREE TEXT
INPUT TRANSFORM: K:$L(X)>50!($L(X)<3) X
LAST EDITED: JUN 01, 2000
HELP-PROMPT: Enter a phrase to help the user distinguish this action from others. 3-50 characters.
DESCRIPTION: This field is NOT required. It is available for use in helping users identify the correct action
when writing business rules. It appears when selecting actions from a list.
For examples, see actions ATTACH TO ID NOTE, and ATTACH ID ENTRY.
If an action has an IDENTIFYING PHRASE or a USER VERB MODIFIER, the business rule ADD or EDIT
action presents the user with a clarifying note about the rule they are creating immediately after
the user enters an action.
8930.8,1 IMPLIED EVENT 1;0 POINTER Multiple #8930.81
LAST EDITED: OCT 11, 1994
DESCRIPTION: Some events imply other events. For example, the ability to Sign a document implies the ability to
View the document. Thus, View is an implied event for the Signature event.
Authorization/Subscription file, the user will be shown implied events for the given event and
asked if they wish to include implied events for the current entry. If so, a copy of the current
entry will be created for each implied event.
8930.81,.01 IMPLIED EVENT 0;1 POINTER TO USR ACTION FILE (#8930.8)
LAST EDITED: OCT 11, 1994
HELP-PROMPT: If this event implies another event, enter the implied event, for example, signature implies
view.
CROSS-REFERENCE: 8930.81^B
1)= S ^USR(8930.8,DA(1),1,"B",$E(X,1,30),DA)=""
2)= K ^USR(8930.8,DA(1),1,"B",$E(X,1,30),DA)
8930.8,2 DESCRIPTION 2;0 WORD-PROCESSING #8930.82
DESCRIPTION: The event description will be used in conjunction with the Authorization/Subscription field to
define what it means to associate users with the event. In most cases, this event description will
suffice to determine the meaning of User Authorization/Subscription file entries.
In rare cases, further description of what an event means when associated with users, document type
and document status will be made in the description field of the User Authorization/Subscription
file. For example, a signature event associated with documents of status completed means a walkup
signature.
This information will be used by persons creating entries in the User Authorization/Subscription
file and by persons assigning users to user classes, when checking what events those user classes
are associated with.
LAST EDITED: SEP 21, 1994
HELP-PROMPT: Enter a description of the event and what it means to associate users with this event.
FILES POINTED TO FIELDS
PROTOCOL (#101) ASSOCIATED PROTOCOL (#.04)
USR ACTION (#8930.8) IMPLIED EVENT:IMPLIED EVENT (#.01)
INPUT TEMPLATE(S):
PRINT TEMPLATE(S):
SORT TEMPLATE(S):
FORM(S)/BLOCK(S):