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 |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields  | All
Print Page as PDF
Global: ^PXRMD(801.48

Package: Uncategorized

Global: ^PXRMD(801.48


Information

FileMan FileNo FileMan Filename Package
801.48 REMINDER DIALOG LINK TYPE Uncategorized

Description

Directly Accessed By Routines, Total: 7

Package Total Routines
Clinical Reminders 7 PXRMDLG5    PXRMDLLA    PXRMDLLB    PXRMDLNK    PXRMDRSG    PXRMEXPS    PXRMRPCC    

Accessed By FileMan Db Calls, Total: 1

Package Total Routines
Clinical Reminders 1 PXRMEXU5    

Pointed To By FileMan Files, Total: 1

Package Total FileMan Files
Clinical Reminders 1 REMINDER DIALOG(#801.41)[#801.411211(1)#801.412(14)]    

Pointer To FileMan Files, Total: 3

Package Total FileMan Files
Clinical Reminders 2 REMINDER DIALOG(#801.41)[1]    REMINDER GUI PROCESS(#801.42)[2]    
Uncategorized 1 REMINDER DIALOG FUNCTION FILE(#801.47)[3]    

Fields, Total: 8

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

  • INPUT TRANSFORM:  K:$L(X)>64!($L(X)<3)!'(X'?1P.E) X
  • LAST EDITED:  SEP 02, 2017
  • HELP-PROMPT:  Answer must be 3-64 characters in length.
  • DESCRIPTION:  
    This is the name of the Link Type. This should be a descriptive name to identify what the linking functionality is trying to do.
  • FIELD INDEX:  B (#1672) REGULAR IR LOOKUP & SORTING
    Unique for: Key B (#142), File #801.48
    Short Descr: B cross-reference
    Description: This is the "B" cross-reference redone as a new style cross reference.
    Set Logic: S ^PXRMD(801.48,"B",$E(X,1,64),DA)=""
    Kill Logic: K ^PXRMD(801.48,"B",$E(X,1,64),DA)
    Whole Kill: K ^PXRMD(801.48,"B")
    X(1): LINK NAME (801.48,.01) (Subscr 1) (Len 64) (forwards)
1 ITEM 0;2 POINTER TO REMINDER DIALOG FILE (#801.41) REMINDER DIALOG(#801.41)

  • LAST EDITED:  SEP 02, 2017
  • HELP-PROMPT:  Select a reminder dialog item assigned to the current dialog.
  • DESCRIPTION:  
    This field is used to determine which element in CPRS should be acted on when the user takes an action on this sequence in CPRS.
2 PROMPT 0;3 POINTER TO REMINDER GUI PROCESS FILE (#801.42) REMINDER GUI PROCESS(#801.42)

  • LAST EDITED:  SEP 02, 2017
  • HELP-PROMPT:  Select the prompt to update.
  • DESCRIPTION:  
    This field should only be populated if the action is to be on a prompt assigned to the ITEM field value. If the action is on the ITEM itself then this field should be set to null.
3 FUNCTION 0;4 POINTER TO REMINDER DIALOG FUNCTION FILE FILE (#801.47) REMINDER DIALOG FUNCTION FILE(#801.47)

  • LAST EDITED:  SEP 02, 2017
  • HELP-PROMPT:  Select the function to use with this link value.
  • DESCRIPTION:  
    This field should be set if a function should be applied to the user action in CPRS. If a function is not needed then this field should be set to null.
4 ACTION 0;5 SET
  • 'C' FOR CHECKED;
  • 'UC' FOR UNCHECKED;
  • 'S' FOR SUPPRESS;
  • 'US' FOR UNSUPPRESS;
  • 'V' FOR VALUE;
  • 'R' FOR REQUIRED;
  • 'UR' FOR UNREQUIRED;
  • 'H' FOR HIDE;
  • 'D' FOR DISABLE;
  • 'E' FOR ENABLE;

  • LAST EDITED:  SEP 06, 2017
  • HELP-PROMPT:  Select the type of action that should be apply to the reminder dialog.
  • DESCRIPTION:  
    This field determine what action to take on the Item and/or PROMPT fields assign to this Link Type.
5 DESCRIPTION 1;0 WORD-PROCESSING #801.485

  • DESCRIPTION:  
    This field is used to describe what this Reminder Link entry does.
  • LAST EDITED:  JUN 16, 2015
6 FUNCTION ARGUMENTS 2;0 Multiple #801.486 801.486

  • DESCRIPTION:  
    This multiple stores additional function input arguments. The values store in this multiple are specific to each function.
7 DIALOG SEQUENCES 3;0 Multiple #801.487 801.487

  • DESCRIPTION:  This field identifies the dialog sequences of the element or group containing this link that will cause this link to execute and the dialog sequences of the element or group identified in the ITEM field that are affected
    by this link.
    If this multiple is blank, then all instances of this link will execute and all instances of the element or group identified in the ITEM field are affected by this link. This is considered a many-to-many association.
    If an entry in this multiple only specifies a dialog sequence that contains this link, then that dialog sequence will execute this link and this link will affect all instances of the element or group identified in the ITEM
    field. This is considered a one-to-unspecified many association.
    If an entry in this multiple only specifies a dialog sequence that is affected by this link, then all instances of this link will execute and this link will only affect the instance of the element or group identified in
    the ITEM field that has the specified dialog sequence. This is considered an unspecified many-to-one association.
    If an entry in this multiple specifies both a dialog sequence that contains this link and a dialog sequence that is affected by this link, then only the containing dialog sequence will execute this link and this link will
    only affect the instance of the element or group identified in the ITEM field that has the specified affected dialog sequence. This is considered a one-to-one association.
    To create a one-to-specified many association, there should be many entries in this multiple that all specify the same dialog sequence that contains this link but each entry has a different dialog sequence affected by this
    link.
    To create a specified many-to-one association, there should be many entries in this multiple that all specify the same dialog sequence that is affected by this link but each entry has a different dialog sequence that
    contains this link.
    This multiple may contain multiple one-to-one associations. It can only contain one one-to-many association and only one many-to-one association, regardless of whether the many is specified or not. It cannot store a
    combination of associations. For example, it should not store a many-to-one association along with a one-to-one association.
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields  | All