Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Details |  All
Print Page as PDF
Sub-Field: 8992.01

Package: Kernel

ALERT(#8992)-->8992.01

Sub-Field: 8992.01


Information

Parent File Name Number Package
ALERT(#8992) ALERT DATE/TIME 8992.01 Kernel

Details

Field # Name Loc Type Details
.01 ALERT DATE/TIME 0;1 DATE

  • INPUT TRANSFORM:  S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  DEC 15, 1994
  • HELP-PROMPT:  This is the date and time that the alert was generated.
  • DESCRIPTION:  
    This is the date and time when the alert was generated.
    UNEDITABLE
  • CROSS-REFERENCE:  8992.01^B^MUMPS
    1)= Q
    2)= Q
    3)= This cross-reference will prevent a 'B' cross-reference from being built.
.02 ALERT ID 0;2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>50!($L(X)<2) X
  • LAST EDITED:  NOV 10, 1999
  • HELP-PROMPT:  This is the package identification used to identify this particular alert. Answer must be 2-50 characters in length.
  • DESCRIPTION:  This is a field in which the package id passed during alert filing. This id may simply be a package namespace, or it may be a namespace followed by additional data to more accurately identify the type or purpose of the
    alert.
    UNEDITABLE
  • CROSS-REFERENCE:  8992^AXQA^MUMPS
    1)= S ^XTV(8992,"AXQA",X,DA(1),DA)=""
    2)= K ^XTV(8992,"AXQA",X,DA(1),DA)
    This is a cross-reference on the complete XQAID value for this alert, which can be used to identify those individuals who received this particular instance of the alert, and could be used to delete other entries which
    had received the alert.
  • CROSS-REFERENCE:  8992^AXQAN^MUMPS
    1)= S ^XTV(8992,"AXQAN",$P(X,";"),DA(1),DA)=""
    2)= K ^XTV(8992,"AXQAN",$P(X,";"),DA(1),DA)
    This cross-reference may be used to identify those users who received the alert with the application package specified XQAID (the first ";"-piece of the complete XQAID value) for those cases in which the full XQAID
    value may not be known, e.g., an application which was selected by the user without selecting the ALERT ACTION option to process the alert.
.03 MESSAGE TEXT 0;3 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>60!($L(X)<3) X
  • LAST EDITED:  DEC 15, 1994
  • HELP-PROMPT:  This is the text which will be displayed to the user at the time the alert is first shown and when the user selects the alert.nswer must be 3-60 characters in length.
  • DESCRIPTION:  This field contains the text of the message to be presented to the user at the time when he cycles through the menu system the first time after the alert has been filed for the user, and when the user selects the VIEW
    ALERTS option.
    UNEDITABLE
.04 NEW ALERT FLAG 0;4 SET
  • '1' FOR NEW;

  • LAST EDITED:  DEC 15, 1994
  • HELP-PROMPT:  This flag is set when the alert has not been displayed to the user previously.
  • DESCRIPTION:  This flag is used by the alert processing to indicate a new alert which has not previously been presented to the user. After the alert message text has been shown to the user, this flag is cleared and the user must then
    select the VIEW ALERTS option to process the alert.
    UNEDITABLE
.05 ACTION FLAG 0;5 SET
  • 'D' FOR DELETE;
  • 'R' FOR RUN ROUTINE;
  • 'I' FOR IMMEDIATE RUN;

  • LAST EDITED:  DEC 15, 1994
  • HELP-PROMPT:  This flag indicates how the alert should be processed.
  • DESCRIPTION:  
    This flag is optional at the present time, since the need for action processing can be determined by the presence of an option name or a routine name for use during alert processing.
    UNEDITABLE
.06 RESERVED1 0;6 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>60!($L(X)<1) X
  • LAST EDITED:  DEC 15, 1994
  • HELP-PROMPT:  This is a reserved field for future use.
  • DESCRIPTION:  
    This field is reserved for future use by the alert system.
    UNEDITABLE
.07 ENTRY POINT 0;7 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>8!($L(X)<1)!'(X?.UN) X
  • LAST EDITED:  DEC 15, 1994
  • HELP-PROMPT:  This is the tag or entry point into the routine if one is used (it may also hold the name of an option). Answer must be 1-8 characters in length.
  • DESCRIPTION:  While named ENTRY POINT, this is a dual function field. If the next field (#.08, AROUTINE NAME) contains a routine name, this field contains the desired entry point within that routine (this field may also be null,
    indicating that the entry point should be at the top of the routine).  If field #.08 is null, then the contents of this field is interpreted as the name of an option which is to be entered when the alert is processed.
    UNEDITABLE
.08 AROUTINE NAME 0;8 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>8!($L(X)<2)!'(X?1U.UN) X
  • LAST EDITED:  DEC 15, 1994
  • HELP-PROMPT:  This is the routine name to be called when the alert is selected for processing. Answer must be 2-8 characters in length.
  • DESCRIPTION:  If this field is not null, it contains the name of a routine which is to be used when the alert is processed. If there is also a value in field #.07, that value is used as an entry point into the routine specified in
    this field.
    If this field is null, field #.07 is interpreted as an option name which is to be used when the alert is processed.
    If both this field and field #.07 are null, the alert is processed as an information only alert.
    UNEDITABLE
.09 RESERVED 0;9 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<2) X
  • LAST EDITED:  DEC 15, 1994
  • HELP-PROMPT:  Answer must be 2-30 characters in length.
  • DESCRIPTION:  
    This field is reserved for future use in the alert processing system.
    UNEDITABLE
.1 CAN DELETE WITHOUT PROCESSING 0;10 SET
  • '1' FOR YES;

  • LAST EDITED:  FEB 02, 1999
  • HELP-PROMPT:  A value in this field indicates that the alert may be deleted by the user without having processed it.
  • DESCRIPTION:  This field was added as a flag to identify alerts which the packages indicate may be deleted by the user without processing the alert. The value is optional and is passed by the package which generates the alert if they
    want to give permission for users to be able to delete the alert.  The flag is checked in the code handling user deletion of alerts.  If an alert involves an action (via an option or routine) it may not be deleted by the
    user unless this flag is set.
.13 DAYS FOR SURROGATE 0;13 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>30)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  DEC 15, 1994
  • HELP-PROMPT:  This is the number of days before the alert is forwarded to the recipient's surrogate(s).
    UNEDITABLE
.14 DAYS FOR SUPERVISOR 0;14 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>30)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  DEC 15, 1994
  • HELP-PROMPT:  This is the number of days (1 to 30) to pass before the alert is forwarded to the recipient's supervisor.
    UNEDITABLE
.15 DAYS FOR BACKUP REVIEWER 0;15 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>15)!(X<1)!(X?.E1"."1.N) X
  • LAST EDITED:  JUL 03, 2001
  • HELP-PROMPT:  Enter a number of days (1 to 15) if the alert has not been processed it will be forwarded to the designated BACKUP REVIEWER in the KERNEL SYSTEM PARAMETERS file.
  • DESCRIPTION:  The 'DAYS FOR BACKUP REVIEWER' field contains a number of days, which if exceeded without the alert being processed will cause the alert to be forwarded to the designated 'XQAL BACKUP REVIEWER' in the PARAMETER file with
    a comment indicating that the alert had not been reviewed by the original recipient.
    This forwarding option is in addition to the SUPERVISOR (based on entries for CHIEF in the SECTION/SERVICE file) or e-mail surrogates, and was requested by sites to be able to forward unprocessed alerts to a known,
    interested individual.  This could be someone in Quality Assurance or a specific nurse responsible for handling overdue unprocessed alerts.
1 DATA FOR ALERT 1;E1,245 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>245!($L(X)<2) X
  • LAST EDITED:  DEC 15, 1994
  • HELP-PROMPT:  This character sequence will be returned to the application when the alert is selected. Answer must be 2-245 characters in length.
  • DESCRIPTION:  This field and all following ^-separated fields are processed as a single entity and are returned in the variable XQADATA for use by the application which generated the alert. The package may pass a series of variables
    using any desired separator in the variable XQADATA at the time the alert is setup.  When the alert is processed the value of XQADATA is returned to the application and may be used to establish parameters related to the
    alert without requiring interaction or provision of information by the user.  In this way information related to patient entry number, specific internal numbers for the desired data, etc may be stored and returned.
    UNEDITABLE
2.01 COMMENT FOR DISPLAY 2;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>245!($L(X)<2) X
  • LAST EDITED:  DEC 15, 1994
  • HELP-PROMPT:  This field is entered during forwarding of an alert to a new recipient.
    UNEDITABLE
3.01 GUID FOR GUI 3;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>38!($L(X)<38) X
  • LAST EDITED:  JAN 26, 2000
  • HELP-PROMPT:  Answer must be a GUID - 38 characters in length
  • DESCRIPTION:  This field contains a Globally Unique IDentifier (GUID) which is used to identify the application which should be used in a graphical user interface environment (windows) to process the alert. This application must
    implement the IVAlert interface.  The GUID should be of the form
    {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
    where each x is a hexadecimal digit (0 through 9 or A through F).
3.02 PATIENT 3;2 POINTER TO PATIENT FILE (#2) PATIENT(#2)

  • LAST EDITED:  OCT 12, 2001
  • HELP-PROMPT:  If this is a PATIENT-related alert, this field identifies the PATIENT associated with the alert.
  • DESCRIPTION:  
    This field is a pointer value to the PATIENT file, if the alert is patient related.  It is not a required field for non-patient related alerts.
4 LONG INFO TEXT 4;0 WORD-PROCESSING #8992.04
Info |  Details |  All