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 |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Found Entries  | All
Print Page as PDF
Global: ^USR(8930.8

Package: Authorization Subscription

Global: ^USR(8930.8


Information

FileMan FileNo FileMan Filename Package
8930.8 USR ACTION Authorization Subscription

Description

Directly Accessed By Routines, Total: 7

Package Total Routines
Authorization Subscription 6 USR27    USR30    USRAEDT    USRLFF    USRPS23    USRPS24    
Text Integration Utility 1 TIULP    

Pointed To By FileMan Files, Total: 4

Package Total FileMan Files
Authorization Subscription 2 USR AUTHORIZATION/SUBSCRIPTION(#8930.1)[.03]    USR ACTION(#8930.8)[#8930.81(.01)]    
Text Integration Utility 2 TIU DOCUMENT DEFINITION(#8925.1)[#8925.113(.01)]    TIU DOCUMENT PARAMETERS(#8925.95)[#8925.951(.01)]    

Pointer To FileMan Files, Total: 2

Package Total FileMan Files
Authorization Subscription 1 USR ACTION(#8930.8)[#8930.81(.01)]    
Kernel 1 PROTOCOL(#101)[.04]    

Fields, Total: 10

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

  • 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)
.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.
.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
.04 ASSOCIATED PROTOCOL 0;4 POINTER TO PROTOCOL FILE (#101) PROTOCOL(#101)

  • LAST EDITED:  JAN 09, 1997
  • HELP-PROMPT:  Indicate which Protocol corresponds to this event.
.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.
.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.
.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.
.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.
1 IMPLIED EVENT 1;0 POINTER Multiple #8930.81 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.
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.

Found Entries, Total: 24

NAME: DICTATION    NAME: ENTRY    NAME: VERIFICATION    NAME: SIGNATURE    NAME: COSIGNATURE    NAME: VIEW    NAME: RELEASE FROM TRANSCRIPTION    NAME: EDIT RECORD    
NAME: UNSIGNED NOTIFICATION    NAME: UNCOSIGNED NOTIFICATION    NAME: PRINT RECORD    NAME: DELETE RECORD    NAME: COPY RECORD    NAME: SEND BACK    NAME: AMENDMENT    NAME: MAKE ADDENDUM    
NAME: IDENTIFY SIGNERS    NAME: REASSIGN    NAME: CHANGE TITLE    NAME: LINK WITH REQUEST    NAME: ATTACH TO ID NOTE    NAME: ATTACH ID ENTRY    NAME: LINK TO FLAG    NAME: EDIT COSIGNER    
Info |  Desc |  Directly Accessed By Routines |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Found Entries  | All