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 |  Pointer To FileMan Files |  Fields |  ICR |  Found Entries  | All
Print Page as PDF
Global: ^XTV(8992.3

Package: Kernel

Global: ^XTV(8992.3


Information

FileMan FileNo FileMan Filename Package
8992.3 ALERT CRITICAL TEXT Kernel

Description

Directly Accessed By Routines, Total: 1

Package Total Routines
Kernel 1 XQALSUR2    

Pointer To FileMan Files, Total: 1

Package Total FileMan Files
Kernel 1 PACKAGE(#9.4)[.03]    

Fields, Total: 3

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

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<3)!'(X'?1P.E) X
  • LAST EDITED:  JAN 11, 2011
  • HELP-PROMPT:  Enter a string of text which, if present in the message text for an alert, indicates a critical alert. Answer must be 3-30 characters in length. This is not case-sensitive.
  • DESCRIPTION:  This is a string of text which if present in the message text for an alert should be identified as text identifying a critical alert and the alert emphasized in whatever manner available.
    A second field PACKAGE-ID (#.02) may contain the identifier used by a package in the ALERTID when creating an alert. If that field is non-null, an alert will only be marked critical if the PACKAGE-ID value is present in
    the ALERTID for the current alert. This may be used to make critical text package-specific.
    The comparison of the text entered with the text in the alert is NOT case sensitive. Also, if the critical text in the alert is preceded by the word 'NOT', it will not be identified as a critical alert.
  • CROSS-REFERENCE:  8992.3^B
    1)= S ^XTV(8992.3,"B",$E(X,1,30),DA)=""
    2)= K ^XTV(8992.3,"B",$E(X,1,30),DA)
.02 PACKAGE-ID 0;2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<1) X
  • LAST EDITED:  JAN 14, 2011
  • HELP-PROMPT:  Optional. Enter the PACKAGE-ID used when creating alerts that the CRITICAL TEXT should be associated with. Enter 1-30 characters, it is not case-sensitive.
  • DESCRIPTION:  This field is used to specify, if desired, a specific package ID to be associated with the CRITICAL TEXT entered in field #.01. The value entered should be the textual part of the value used for XQAID when creating the
    alert(s) (e.g., OR for Order Entry or TIU for Text Integration Utility). If a non-null value is in this field, alerts containing the CRITICAL TEXT string will only be indicated as critical alerts if they also have text
    matching the PACKAGE-ID as a part of the ALERTID field. Matching of this value will not be case sensitive.
.03 CREATING PACKAGE 0;3 POINTER TO PACKAGE FILE (#9.4) PACKAGE(#9.4)

  • LAST EDITED:  JAN 14, 2011
  • HELP-PROMPT:  Answer with the PACKAGE NAME that is responsible for creating this CRITICAL TEXT entry.
  • DESCRIPTION:  
    This is the package which is responsible for creating this CRITICAL TEXT entry.

Found Entries, Total: 5

CRITICAL TEXT: CRITICAL    CRITICAL TEXT: ABNORMAL IMA    CRITICAL TEXT: POSSIBLE MALIG    CRITICAL TEXT: TESTING-ALERTID-ONLY    CRITICAL TEXT: ABNL IMA    

ICR, Total: 1

ICR LINK Subscribing Package(s) Fields Referenced Description
ICR #6869
  • Imaging
  • Order Entry Results Reporting
  • CRITICAL TEXT (.01).
    Access: Both R/W w/Fileman

    PACKAGE-ID (.02).
    Access: Both R/W w/Fileman

    CREATING PACKAGE (.03).
    Access: Both R/W w/Fileman

    Kernel file used to identify strings of text forCritical Alerts.
    Info |  Desc |  Directly Accessed By Routines |  Pointer To FileMan Files |  Fields |  ICR |  Found Entries  | All