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 |  Found Entries |  External References |  Global Variables Directly Accessed |  Local Variables |  All
Print Page as PDF
Global: ^GMR(123.5

Package: Consult Request Tracking

Global: ^GMR(123.5


Information

FileMan FileNo FileMan Filename Package
123.5 REQUEST SERVICES Consult Request Tracking

Description

Directly Accessed By Routines, Total: 113

Package Total Routines
Consult Request Tracking 98 ADMINISTRATIVE UPDATE TEAMS    ADMINISTRATIVE UPDATE USERS    ASSOCIATED STOP CODE    GMRC CONSULTS LIST    GMRC101C    GMRC101H    GMRC104    GMRC3P52
GMRCACTM    GMRCADC    GMRCAFRD    GMRCALOR    GMRCAPI    GMRCASV    GMRCASV1    GMRCAU
GMRCCPRS    GMRCDDX    GMRCDIS    GMRCDPCK    GMRCDRFR    GMRCEDT1    GMRCEDT2    GMRCEDT4
GMRCGUIA    GMRCGUIC    GMRCHL7    GMRCHL72    GMRCHL7B    GMRCIR    GMRCISG1    GMRCITST
GMRCIUTL    GMRCMCP    GMRCMSS    GMRCNOTF    GMRCONS1    GMRCONS2    GMRCP50    GMRCP5D
GMRCP85    GMRCPC    GMRCPOS    GMRCPOS1    GMRCPOS2    GMRCPOST    GMRCPR0    GMRCPS
GMRCQCST    GMRCR    GMRCSLDT    GMRCSLM    GMRCSLM1    GMRCSLM2    GMRCSLM4    GMRCSRVS
GMRCSSP    GMRCST    GMRCSTL2    GMRCSTL7    GMRCSTL8    GMRCSTLA    GMRCSTLB    GMRCSTLM
GMRCSTS    GMRCSTSU    GMRCSTU    GMRCSTU1    GMRCSUBS    GMRCT    GMRCTIU    GMRCTIUE
GMRCTU    GMRCU    GMRCUTL1    GMRCUTL2    GMRCXR    GMRCYP15    GMRCYP16    GMRCYP4
GMRCYP42    GMRCYP5    GMRCYP50    GMRCYP68    GMRCYP70    GMRCYP9    IFC SENDING FACILITY    NOTIFICATION BY PT LOCATION
PROCEDURE TYPE    RELATED HOSPITAL LOCATION    RELATED SERVICES    SERVICE TEAM(S) TO NOTIFY    SUB-SERVICE    SYNONYM    UPDATE TEAMS W/O NOTIFICATIONS    UPDATE USER CLASSES W/O NOTIFS
UPDATE USERS W/O NOTIFICATIONS    ^GMR(123.5    
Order Entry Results Reporting 5 ITEMS    ORCHTAB1    ORQQCN2    ^ORD(100.22    ORY26    
Scheduling 5 SDCNSLT    SDEC51    SDEC51A    SDECGMR    SDM2    
Prosthetics 2 RMPREOS    RMPRHL7A    
Functional Independence 1 RMIMV    
Radiology Nuclear Medicine 1 RA148PST    

Accessed By FileMan Db Calls, Total: 36

Package Total Routines
Consult Request Tracking 25 GMRCASV    GMRCASV1    GMRCAU    GMRCCCRA    GMRCEDT4    GMRCFP    GMRCFPA    GMRCHL7B
GMRCHL7H    GMRCIERR    GMRCIUTL    GMRCMSS    GMRCP5D    GMRCPOS    GMRCPS    GMRCPSL3
GMRCPSL4    GMRCQC    GMRCQCST    GMRCSL    GMRCSRVS    GMRCSTS1    GMRCYP16    GMRCYP42
GMRCYP57    
Imaging 4 MAGDHOW4    MAGDHOWE    MAGDRCU1    MAGDTRDX    
Clinical Procedures 1 MDCONUTL    
Order Entry Results Reporting 1 ORMBLDGM    
Prosthetics 1 RMPREOS    
Radiology Nuclear Medicine 1 RA148PST    
Scheduling 1 SDECGMR    
Surgery 1 SRCHL7A    
VistA Integration Adapter 1 VIABRPC    

Pointed To By FileMan Files, Total: 10

Package Total FileMan Files
Consult Request Tracking 5 REQUEST/CONSULTATION(#123)[1#123.02(6)]    GMRC CONSULT MAPPING(#123.033)[#123.0331(.01)]    GMRC PROCEDURE(#123.3)[#123.32(.01)]    REQUEST SERVICES(#123.5)[#123.51(.01)]    CONSULTS PARAMETERS FILE(#123.9)[#123.92(.01)#123.99(.02)]    
Imaging 2 CLINICAL SPECIALTY DICOM & HL7(#2006.5831)[.01]    TELEREADER ACQUISITION SERVICE(#2006.5841)[.01]    
Kernel 1 PROTOCOL(#101)[6]    
Prosthetics 1 PROSTHETIC SUSPENSE(#668)[23]    
Text Integration Utility 1 TIU TEMPLATE(#8927)[.19]    

Pointer To FileMan Files, Total: 14

Package Total FileMan Files
Kernel 6 DEVICE(#3.5)[123.09689]    OPTION(#19)[123.011]    INSTITUTION(#4)[132#123.5134(.01)]    SERVICE/SECTION(#49)[123.07]    PROTOCOL(#101)[123.02123.03123.04#123.5101(.01)]    NEW PERSON(#200)[5123.08123.5135#123.54(1)#123.55(.01)#123.555(.01)]
Order Entry Results Reporting 2 OE/RR LIST(#100.21)[#123.53(.01)#123.54(2)#123.57(.01)#123.58(.01)]    DISPLAY GROUP(#100.98)[123.01]    
Registration 2 WARD LOCATION(#42)[#123.54(.01)]    FACILITY TREATING SPECIALTY(#45.7)[123.06]    
Scheduling 2 CLINIC STOP(#40.7)[#123.5688(.01)]    HOSPITAL LOCATION(#44)[#123.54(.01)#123.56(.01)]    
Authorization Subscription 1 USR CLASS(#8930)[1.06#123.59(.01)]    
Consult Request Tracking 1 REQUEST SERVICES(#123.5)[#123.51(.01)]    

Fields, Total: 47

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

  • INPUT TRANSFORM:  K:$L(X)>63!($L(X)<2)!'(X'?1P.E)!($O(^GMR(123.5,"B",X,0))'="") X
    MAXIMUM LENGTH:   63
  • LAST EDITED:  AUG 20, 2018
  • HELP-PROMPT:  Type a unique name of a service or specialty that can receive consults.
  • DESCRIPTION:  
    This is the Name of a service or specialty which may receive consult/ requests.  This may also be a name which represents a group of services
  • DELETE TEST:  1,0)= S %=$$CHKDEL^GMRCDDX(DA) I $L(%) D EN^DDIOL(%)
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • CROSS-REFERENCE:  123.5^B
    1)= S ^GMR(123.5,"B",$E(X,1,63),DA)=""
    2)= K ^GMR(123.5,"B",$E(X,1,63),DA)
    This is the regular cross-reference for this file allowing look-up by Service Name.
  • CROSS-REFERENCE:  123.5^AC1^MUMPS
    1)= D SETAC^GMRCDDX
    2)= D KILLAC^GMRCDDX
    3)= This cross-reference is what helps maintain the alphabetical look-up of services.
    This cross-reference calls the GMRCDDX routine to set and kill "AC" cross-references that are defined for DD 123.51 (Sub-Service/Specialty multiple),.01 field.  The ACP cross reference helps identify all entries in file
    123.5 which have the service being edited as a child.  For each occurrence as a child, the "AC" cross-reference is updated.
.06 UNRESTRICTED ACCESS 0;6 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JUL 12, 1999
  • HELP-PROMPT:  Enter Y or YES to allow all users to update requests for this service
  • DESCRIPTION:  This field, if set to yes will allow all users to perform the full range of update activities on consult or procedure requests directed to this service. If this field is set to yes, all other fields related to assignment
    of update users are ignored.
    The SERVICE INDIVIDUAL TO NOTIFY and the SERVICE TEAM(S) TO NOTIFY fields will still be used to determine notification recipients for each individual service.
.07 PROCESS PARENTS FOR UPDATES 0;7 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JUL 22, 1999
  • HELP-PROMPT:  Enter YES to have parent services checked for user update authority.
  • DESCRIPTION:  
    This field, if set to YES will cause the parent services of the this service to be screened to determine update authority for a given user.
.08 PROCESS PARENTS FOR NOTIFS 0;8 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JUL 22, 1999
  • HELP-PROMPT:  Enter YES to process parent services for notification recipients.
  • DESCRIPTION:  
    This field, if set to YES will cause the parent services of this service to be processed when determining notification recipients.
1.01 PROVISIONAL DX PROMPT 1;1 SET
  • 'O' FOR OPTIONAL;
  • 'R' FOR REQUIRE;
  • 'S' FOR SUPPRESS;

  • LAST EDITED:  SEP 16, 1999
  • HELP-PROMPT:  Enter a code to determine the restraints placed on the provisional diagnosis prompt when ordering via CPRS.
  • DESCRIPTION:  This field will be used by CPRS to determine how to prompt for the provisional diagnosis when ordering consults for this service. If this field is set to OPTIONAL, the user will be prompted for the provisional diagnosis
    but may bypass answering the prompt. If the field is set to SUPPRESS, the user will not be presented with the provisional diagnosis prompt. If set to REQUIRED, the user must answer the prompt to continue placing the order.
1.02 PROVISIONAL DX INPUT 1;2 SET
  • 'F' FOR FREE TEXT;
  • 'L' FOR LEXICON;

  • LAST EDITED:  SEP 16, 1999
  • HELP-PROMPT:  Enter a code to indicate the type of input allowed by CPRS when entering a provisional diagnosis
  • DESCRIPTION:  This field will determine the method that CPRS will use to prompt the user for input of the provisional diagnosis when ordering. If set to FREE TEXT, the user may type any text from 2-80 characters in length. If set to
    LEXICON, the user will be required to select a coded diagnosis from the Clinical Lexicon.
1.03 RESTRICT DEFAULT REASON EDIT 1;3 SET
  • '0' FOR UNRESTRICTED;
  • '1' FOR ASK ON EDIT ONLY;
  • '2' FOR NO EDITING;

  • LAST EDITED:  NOV 30, 1999
  • HELP-PROMPT:  Choose 0, 1 or 2
  • DESCRIPTION:  If a DEFAULT REASON FOR REQUEST exists for this service this field affects the ordering person's ability to edit the default reason while placing an order.
    0 - UNRESTRICTED
    User will be able to edit the default text at any time.
    1 - ASK ON EDIT ONLY
    User will only be allowed to edit the default reason if the
    order is edited before releasing to the service.
    2 - NO EDITING
    User will not be allowed to edit the default reason at any
    time.
    The value of this field will be ignored if no DEFAULT REASON FOR REQUEST exists for this service.
1.04 NOTIFY SERVICE ON DC 1;4 SET
  • '0' FOR ALWAYS;
  • '1' FOR REQUESTOR ACTION;
  • '2' FOR NEVER;

  • LAST EDITED:  MAR 17, 2000
  • HELP-PROMPT:  Enter one of the codes.
  • DESCRIPTION:  This field controls when members configured to receive notifications for this service in the Consult hierarchy will be alerted to a consult being discontinued.
    0 - ALWAYS
    service update users will receive notification of a discontinue
    regardless of who DC's the order
    1 - REQUESTOR ACTION
    service update users will receive notification of a discontinue only
    if the user discontinuing the consult is not an update user for the
    service
    2 - NEVER
    service update users will never receive notification of a discontinued
    consult
1.05 REPRINT 513 ON DC 1;5 SET
  • '0' FOR ALWAYS;
  • '1' FOR REQUESTOR ACTION;
  • '2' FOR NEVER;

  • LAST EDITED:  MAR 17, 2000
  • HELP-PROMPT:  Enter one of the codes
  • DESCRIPTION:  This field will determine if the SF-513 should reprint to the consulting service when a consult is discontinued.
    0 - ALWAYS
    the SF-513 will always reprint to the SERVICE PRINTER when a consult
    is discontinued
    1 - REQUESTOR ACTION
    the SF-513 will reprint to the SERVICE PRINTER only when a consult is
    discontinued by a user that is not an update user for the service in
    2 - NEVER
    the SF-513 will never reprint to the SERVICE printer regardless of who
    discontinued the consult
1.06 RESULT MGMT USER CLASS 1;6 POINTER TO USR CLASS FILE (#8930) USR CLASS(#8930)

  • INPUT TRANSFORM:  S DIC("S")="I $P(^(0),U,3)" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  APR 04, 2000
  • HELP-PROMPT:  Enter the User Class that may disassociate Medicine Results from a Consult Request
  • DESCRIPTION:  This field defines the Authorization/Subscription User Class that is permitted to disassociate a Medicine result from a Consult request. It is recommended that this function be restricted to a very select group of
    individuals.
    This field invokes IA #3008
  • SCREEN:  S DIC("S")="I $P(^(0),U,3)"
  • EXPLANATION:  Only an active User Class may be selected
1.1 SYNONYM 2;0 Multiple #123.52 123.52

  • DESCRIPTION:  
    This multiple field identifies the commonly known names and abbreviations for the Service named in the .01 Name field.  Synonyms identified here are used in the look-up of services at 'Select Service/Specialty: ' prompts.
1.11 PRINT NAME .1;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>7!($L(X)<1) X
  • LAST EDITED:  APR 23, 1992
  • HELP-PROMPT:  Answer must be 1-7 characters in length.
  • DESCRIPTION:  This is a commonly known Abbreviation for this Service/Specialty. This name is used to build Consult Notifications when a consult/request is ordered in OE/RR.
    If not defined, the NAME (.01) is used.
2 SERVICE USAGE 0;2 SET
  • '1' FOR GROUPER ONLY;
  • '2' FOR TRACKING ONLY;
  • '9' FOR DISABLED;

  • INPUT TRANSFORM:  Q:$G(GMRCSRVC)="" D USAGE^GMRC1235
  • LAST EDITED:  NOV 05, 2009
  • HELP-PROMPT:  Enter '1' if the service is Grouper Only, 2 if the service is to be used for TRACKING Only, and 9 to DISABLE the service.
  • DESCRIPTION:  Whenever a value is defined in the SERVICE USAGE field, the Service entry will NOT be selectable to send consults TO in the OE/RR ordering process.
    Service Usages cause functioning as follows: GROUPER ONLY - Allows a service to be used for grouping other services together for review purposes, and aids in defining the service hierarchy (e.g., ALL SERVICES, INPATIENT
    SERVICES, OUTSIDE SERVICES).  During the order process, a user selecting a grouper only service will be shown the service hierarchy under that service grouper.  A Grouper ONLY service should never be a "TO" Service on a
    consult.
    TRACKING ONLY - Allows a service to be defined in a hierarchy, but will not allow users ordering consults in OE/RR to be able to see or select a service marked for TRACKING ONLY.  (e.g., Psychology may be defined with its
    Service Usage blank, and its Sub-specialty multiple defined with services of which some or all may be "TRACKING ONLY" services.  This hierarchy facilitates the situation when a service, such as Psychology, prefers a common
    location for all related consults to be sent to. A Tracking user at the common location then "Forwards" the request to one of the sub-service TRACKING ONLY services for completion.)
    DISABLED - Disabled services are not selectable for ordering or tracking.
  • TECHNICAL DESCR:  If the SERVICE USAGE value is changed to GROUPER ONLY or DISABLED and the service is defined in RELATED SERVICES to a PROCEDURE in file #123.3, then the PROCEDURES containing the SERVICE in RELATED SERVICES are displayed
    to the user.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
3 DISABLE MESSAGE 0;3 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>80!($L(X)<1) X
  • LAST EDITED:  JUN 13, 1991
  • HELP-PROMPT:  Enter a message that will display if/when this service is DISABLED, 1-80 characters in length.
  • DESCRIPTION:  
    If a service is disabled, a DISABLED message will be displayed on the screen.
5 CREATOR 0;5 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • LAST EDITED:  MAY 28, 1991
  • HELP-PROMPT:  Type in the name of the person creating the new service entry.
  • DESCRIPTION:  
    This field identifies who created the service entry.
10 SUB-SERVICE 10;0 POINTER Multiple #123.51 123.51

  • LAST EDITED:  AUG 20, 2001
  • DESCRIPTION:  This is the set of services or specialties that may be grouped under the Service/Specialty. A member of this sub-service may also be defined to have its own sub-service/specialties. There is no limit to the depth of the
    hierarchy beneath ALL SERVICES.
11 INTERNAL NAME 11;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>80!($L(X)<2) X
  • LAST EDITED:  JAN 31, 2002
  • HELP-PROMPT:  Answer must be 2-80 characters in length
  • DESCRIPTION:  This field holds a name that can be used for internal name-spacing. This name will not be viewable to users when selecting a service. This name may be used to look up entries in the file via VA Fileman and the Setup
    Consult Services option.
  • CROSS-REFERENCE:  123.5^E
    1)= S ^GMR(123.5,"E",$E(X,1,30),DA)=""
    2)= K ^GMR(123.5,"E",$E(X,1,30),DA)
20 ENTRY ACTION 20;E1,245 MUMPS

  • INPUT TRANSFORM:  K:$L(X)>245 X D:$D(X) ^DIM
  • LAST EDITED:  JUL 24, 1991
  • HELP-PROMPT:  ENTER STANDARD MUMPS CODE
  • DESCRIPTION:  
    This field contains MUMPS code that will be executed when someone enters this option for CPRS Detailed and Results displays.
    DELETE AUTHORITY: @
    WRITE AUTHORITY:  @
101 PROCEDURE TYPE 101;0 POINTER Multiple #123.5101 123.5101

  • LAST EDITED:  JUN 28, 2000
123.01 OE/RR DISPLAY GROUP 123;1 POINTER TO DISPLAY GROUP FILE (#100.98) DISPLAY GROUP(#100.98)

  • LAST EDITED:  AUG 21, 1991
  • HELP-PROMPT:  Enter the CPRS display group that this service belongs to.
  • DESCRIPTION:  
    The display group will automatically default to CONSULTS if there is no other display group defined as a sub-group of CONSULTS.
123.011 SERVICE UPDATE OPTION 123;10 POINTER TO OPTION FILE (#19) OPTION(#19)

  • LAST EDITED:  FEB 12, 1992
  • HELP-PROMPT:  Enter the Protocol Action Menu to assign to a user for selecting actions from the Consult/Request screen.
  • DESCRIPTION:  This field provides security by defining who can actually perform tracking activities for a service/specialty's consults, based on the Option used.
    This field works in conjunction with the PROTOCOL ACTION MENU BY OPTION field.  If an option is identified here, and the user selects this option to review consults/requests, the user will be given access to the Protocol
    action menu defined in the PROTOCOL ACTION MENU BY OPTION field.  If this option was not used to access the consult/request tracking data, the user will only see the actions defined in the GMRCACTM USER REVIEW SCREEN
    protocol menu.
123.02 PROTOCOL MENU OF REQUEST ITEMS 123;2 POINTER TO PROTOCOL FILE (#101) PROTOCOL(#101)

  • LAST EDITED:  FEB 25, 1992
  • HELP-PROMPT:  Enter the PROCEDURE to be associated with this service.
  • DESCRIPTION:  This field is being used primarily for the Medicine Package Interface to link the Medicine Service to a Protocol Menu representing the Procedure Types of the Medicine Package. The GMRC MEDICINE PKG INTERFACE option uses
    this entry to determine the service and the type of results the Medicine Personnel may be associating results with.
123.03 PROTOCOL ACTION MENU BY USERS 123;3 POINTER TO PROTOCOL FILE (#101) PROTOCOL(#101)

  • LAST EDITED:  MAY 15, 1992
  • HELP-PROMPT:  Enter GMRCACTM USER REVIEW SCREEN or GMRCACTM SERVICE ACTION MENU to determine what actions can be taken by the user.
  • DESCRIPTION:  This is the Protocol menu of actions in the Protocol file which may be used by users identified in the "Service Individual to Notify," "Service Teams to Notify," and "Update Users w/o Notification" fields for a Service.
    Two generic protocol action menus are exported, GMRCACTM USER REVIEW SCREEN and GMRCACTM SERVICE ACTION MENU.  The GMRCACTM USER REVIEW SCREEN is the default protocol menu of actions which will be used when no other
    protocol is defined.  This default menu of actions contains inquiry only kinds of actions.  The GMRCACTM SERVICE ACTION MENU contains actions which allow the consult/request to be tracked to its final resolution of Denied,
    Discontinued, or Completed.
123.04 PROTOCOL ACTION MENU BY OPTION 123;4 POINTER TO PROTOCOL FILE (#101) PROTOCOL(#101)

  • LAST EDITED:  APR 22, 1992
  • HELP-PROMPT:  Enter the Protocol Action that may be used by a person to perform actions on the Consults screen.
  • DESCRIPTION:  This is the menu of protocol actions in the Protocol File that may be used when the option named in the SERVICE UPDATE OPTION field is the option used to review the consults/requests.
    This field is only used when the IRM service wants to establish security BY SERVICE via site-specific options.
    If neither the PROTOCOL ACTION MENU BY OPTION or the SERVICE UPDATE OPTION are used to specify service security, then the PROTOCOL ACTION MENU BY KEY and SERVICE UPDATE SECURITY KEY are checked to establish the correct
    menu of actions allowed for the user BY SERVICE.
    The "GMRCACTM USER REVIEW SCREEN" protocol menu of actions will be used for all users as a default.  This default menu of actions contains inquiry only kinds of actions.
    Sites that are using the Medicine Package to enter procedure results may specify GMRCACTM MEDICINE PKG MENU as the Protocol Action Menu By Option field and the GMRC MEDICINE PKG INTERFACE option as the Security Update
    Optifor field.  This should only be specified on those services that are linked to a "GMRCR " protocol via the FILE LINK field in the Protocol File.  The exported Medicine sub-services are already defined for use with the
    GMRC MEDICINE PKG INTERFACE option.
    Pharmacy Services should specify GMRCACTM PHARMACY PKG MENU in the Protocol Action Menu By Option field and the GMRC PHARMACY TPN CONSULTS option in the Service Update Option field.
123.06 RELATED TREATING SPECIALTY 123;6 POINTER TO FACILITY TREATING SPECIALTY FILE (#45.7) FACILITY TREATING SPECIALTY(#45.7)

  • LAST EDITED:  MAY 28, 1992
  • HELP-PROMPT:  Enter the related Treating Specialty from the FACILITY TREATING SPECIALTY File.
  • DESCRIPTION:  This field may be defined for use in Fileman reporting
    via the Relational Jumping capabilities.
  • CROSS-REFERENCE:  123.5^C
    1)= S ^GMR(123.5,"C",$E(X,1,30),DA)=""
    2)= K ^GMR(123.5,"C",$E(X,1,30),DA)
    The "C" cross-reference enables look-up of information based on the RELATED TREATING SPECIALTY.  This cross-reference is used to allow an individual to specify a Treating Specialty in the "TO" field when Requesting a
    Consult or Generic Request.
123.07 RELATED SERVICE/SECTION 123;7 POINTER TO SERVICE/SECTION FILE (#49) SERVICE/SECTION(#49)

  • LAST EDITED:  JUL 10, 1991
  • HELP-PROMPT:  Enter the RELATED SERVICE/SECTION from the SERVICE/SECTION File.
123.08 SERVICE INDIVIDUAL TO NOTIFY 123;8 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • INPUT TRANSFORM:  S DIC("S")="I $$ACTIVE^XUSER(+Y)" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  JAN 13, 2000
  • HELP-PROMPT:  Enter the name of the individual in the Service who will receive a default notification of any action taken on a consult.
  • DESCRIPTION:  A user may be identified in this field as having primary responsibility for receiving consults and tracking them through to completion or discontinuance. This individual will receive a "NEW SERVICE CONSULT" notification
    type when a new order is released to the service through CPRS.  The notification will appear in the following format:
    NIVEK,ALP (N8976): New Psychology Consult ordered
    JONES,GEO (J4552): New Psychology consult forwarded - Stat
    The user must have the "NEW SERVICE CONSULT/REQUEST" notification type enabled.
  • SCREEN:  S DIC("S")="I $$ACTIVE^XUSER(+Y)"
  • EXPLANATION:  Only active users may be selected
123.09 SERVICE PRINTER 123;9 POINTER TO DEVICE FILE (#3.5) DEVICE(#3.5)

  • LAST EDITED:  JUL 16, 1991
  • HELP-PROMPT:  Enter the name of the Service/Section's Printing Device, or the nearest Printer.
  • DESCRIPTION:  This field allows the service/specialty to identify a device that will be used for printing Consult Forms (513) 'automatically' at the service when the consult/request order is released by CPRS.
    If the device is not defined, the Consult Form will print at the location where the order was placed, bypassing the electronic relay functionality.  The order text in CPRS for an order to a service with no device is
    prefixed with ">>."  This indicates to the ordering clerks/clinician that the consult form needs manual processing or a call to the service to have the service use the "PS" action to print the service copy.
123.1 SERVICE TEAM(S) TO NOTIFY 123.1;0 POINTER Multiple #123.53 123.53

  • LAST EDITED:  JUN 05, 1992
  • DESCRIPTION:  
    A service can have teams of users associated with the Service.  Any users defined in a team related to the Service will receive Notifications.
123.2 NOTIFICATION BY PT LOCATION 123.2;0 VARIABLE POINTER Multiple #123.54 123.54

  • LAST EDITED:  MAY 15, 1992
  • DESCRIPTION:  A service may send notifications about new consults to an individual or teams, depending on the patient's location. Each hospital/ward location for patients may be defined here. For each location, an individual or
    team(s) may be specified to receive notifications for orders based on the patient's location at the time the order was placed.
123.3 UPDATE USERS W/O NOTIFICATIONS 123.3;0 POINTER Multiple #123.55 123.55

  • DESCRIPTION:  Service users who are able to perform update tracking actions, but DO NOT receive "NEW SERVICE CONSULT" notifications, should be defined here. The update tracking capabilities are based on the Protocol Action Menu by
    Users field.
123.31 UPDATE TEAMS W/O NOTIFICATIONS 123.31;0 POINTER Multiple #123.57 123.57

  • DESCRIPTION:  
    This field will allow teams of users to be assigned as update users. Team members will not receive notifications as a result of the team being entered in this field.
123.33 ADMINISTRATIVE UPDATE USERS 123.33;0 POINTER Multiple #123.555 123.555

  • LAST EDITED:  NOV 29, 1999
  • INDEXED BY:  NOTIFICATION RECIPIENT & ADMINISTRATIVE UPDATE USER (AC)
123.34 ADMINISTRATIVE UPDATE TEAMS 123.34;0 POINTER Multiple #123.58 123.58

  • LAST EDITED:  NOV 29, 1999
  • INDEXED BY:  NOTIFICATION RECIPIENTS & ADMINISTRATIVE UPDATE TEAM (AC)
123.35 UPDATE USER CLASSES W/O NOTIFS 123.35;0 POINTER Multiple #123.59 123.59

  • SCREEN:  I $P(^(0),"^",3)
  • EXPLANATION:  Only active User Classes may be selected
123.4 RELATED HOSPITAL LOCATION 123.4;0 POINTER Multiple #123.56 123.56

  • LAST EDITED:  JUL 10, 1991
123.5 SPECIAL UPDATES INDIVIDUAL 0;4 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • INPUT TRANSFORM:  S DIC("S")="I $$ACTIVE^XUSER(+Y)" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  MAR 13, 2000
  • HELP-PROMPT:  This is the individual who can perform special updates for this particular service.
  • DESCRIPTION:  This individual will have privileges to perform group status updates for this service or any of the entries in the SUB-SERVICE/SPECIALTY field.
    It is recommended that this individual be a responsible service update user or a Clinical Application Coordinator. If given the option GMRCSTSU, the user will be able to choose all requests within a date range that are
    pending, active or both and update the request to discontinued or complete. This will also update the related order in CPRS to the same status.
  • SCREEN:  S DIC("S")="I $$ACTIVE^XUSER(+Y)"
  • EXPLANATION:  Only active users may be selected
124 DEFAULT REASON FOR REQUEST 124;0 WORD-PROCESSING #123.5124

  • DESCRIPTION:  This field will allow a boilerplate of text to be imported into the reason for request when placing consult or procedure orders for this service. If the user places an order using a quick order having boilerplate text,
    that text will supersede any default text stored.
    This field may contain any text including TIU objects. TIU Objects must be enclosed in vertical bars (e.g. |PATIENT NAME| ).
125 PREREQUISITE 125;0 WORD-PROCESSING #123.5125
131 PROSTHETICS SERVICE INT;1 SET
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JUN 15, 2000
  • HELP-PROMPT:  Enter YES if this service is part of the Prosthetics interface.
  • DESCRIPTION:  This field is used to flag those services that are part of the interface between Consult/Request Tracking and the Prosthetics package.
    This field is set by a package option. It is not intended to be modified via VA FileMan.
132 IFC ROUTING SITE IFC;1 POINTER TO INSTITUTION FILE (#4) INSTITUTION(#4)

  • INPUT TRANSFORM:  S DIC("S")="N STA S STA=$$STA^XUAF4(+Y) I STA,STA=+STA,+Y'=$$KSP^XUPARAM(""INST"")" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  FEB 18, 2002
  • HELP-PROMPT:  Enter the VA site that will perform consults directed to this service
  • DESCRIPTION:  
    This field contains the VA facility that will perform consults requested for this service. When a consult for this service is ordered, it will automatically be routed to the VA facility in this field.
  • SCREEN:  S DIC("S")="N STA S STA=$$STA^XUAF4(+Y) I STA,STA=+STA,+Y'=$$KSP^XUPARAM(""INST"")"
  • EXPLANATION:  Only national institution file entries may be selected
133 IFC REMOTE NAME IFC;2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>63!($L(X)<2) X
  • LAST EDITED:  SEP 07, 2001
  • HELP-PROMPT:  Enter the name of the service at the consulting site
  • DESCRIPTION:  This field contains the name of the service that will be requested at the VAMC defined in the IFC ROUTING SITE field.
    Enter the name of the service exactly as it is named at the remote facility. If this name does not match the name of the service at the routing site, the request will fail to be filed at the remote site. This will delay or
    prohibit the performance and processing of this request.
134 IFC SENDING FACILITY IFCS;0 POINTER Multiple #123.5134 123.5134
135 IFC COORDINATOR IFC;3 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • LAST EDITED:  OCT 17, 2001
  • HELP-PROMPT:  Please enter the person that will administer inter-facility consults for this service.
  • DESCRIPTION:  The person entered in this field will have the ability to act on consults that would not otherwise be accessible to other update users for this service. This user will also be able to rectify certain communication failures
    with Inter-facility Consults.
150 ADMINISTRATIVE 30;1 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  FEB 08, 2008
  • HELP-PROMPT:  ENTER 'YES' IF THIS SERVICE IS ADMINSTRATIVE IN NATURE.
  • DESCRIPTION:  Entering 'YES" here will cause any orders placed to this service to have a corresponding entry of 'YES' in the ADMINISTRATIVE field of the REQUEST CONSULTATION FILE, #123. Administrative requests are to be excluded from
    the CONSULTS PERFORMANCE MONITOR report [GMRC RPT PERF MONITOR].
688 ASSOCIATED STOP CODE 688;0 POINTER Multiple #123.5688 123.5688
689 SECONDARY PRINTER 3;1 POINTER TO DEVICE FILE (#3.5) DEVICE(#3.5)

  • LAST EDITED:  JAN 24, 2017
  • HELP-PROMPT:  Enter the secondary printer for FORM 513.
  • DESCRIPTION:  
    This is a second printer that the service can use to print the form 513 when desired.

Found Entries, Total: 14

SERVICE NAME: ALL SERVICES    SERVICE NAME: CARDIOLOGY    SERVICE NAME: CARE COORDINATION HOME TELEHEALTH SCREENING    SERVICE NAME: CONTACT LENS REQUEST    SERVICE NAME: EYEGLASS REQUEST    SERVICE NAME: GASTROENTEROLOGY    SERVICE NAME: HEMATOLOGY    SERVICE NAME: HOME OXYGEN REQUEST    
SERVICE NAME: MEDICINE    SERVICE NAME: PHARMACY SERVICE    SERVICE NAME: PROSTHETICS REQUEST    SERVICE NAME: PULMONARY    SERVICE NAME: RHEUMATOLOGY    SERVICE NAME: SUICIDE HOTLINE    

External References

Name Field # of Occurrence
EN^DDIOL IDUSAGE+1, .01DEL1+1
^DIC 1.06+1, 123.08+1, 123.5+1, 132+1
^DIM 20+1
$$GET1^DIQ IDUSAGE+1
$$CHKDEL^GMRCDDX .01DEL1+1
KILLAC^GMRCDDX .01(XREF 2K)
SETAC^GMRCDDX .01(XREF 2S)
EN^GMRCMER 20(IEN:4), 20(IEN:5), 20(IEN:6), 20(IEN:7), 20(IEN:8)

Global Variables Directly Accessed

Name Line Occurrences  (* Changed,  ! Killed)
^GMR(123.5 - [#123.5] .01+1, .01(XREF 1S), .01(XREF 1K), 11(XREF 1S), 11(XREF 1K), 123.06(XREF 1S), 123.06(XREF 1K)

Local Variables

Legend:

>> Not killed explicitly
* Changed
! Killed
~ Newed

Name Field # of Occurrence
>> % .01DEL1+1*
>> DA .01DEL1+1, .01(XREF 1S), .01(XREF 1K), 11(XREF 1S), 11(XREF 1K), 123.06(XREF 1S), 123.06(XREF 1K)
DIC 1.06+1!*, 123.08+1!*, 123.5+1!*, 132+1!*
DIC("S" 1.06+1*, 1.06SCR+1*, 123.08+1*, 123.08SCR+1*, 123.5+1*, 123.5SCR+1*, 132+1*, 132SCR+1*
>> DIE 1.06+1, 123.08+1, 123.5+1, 132+1
X .01+1!, .01(XREF 1S), .01(XREF 1K), 1.06+1*!, 1.11+1!, 3+1!, 11+1!, 11(XREF 1S), 11(XREF 1K), 20+1!
123.06(XREF 1S), 123.06(XREF 1K), 123.08+1*!, 123.5+1*!, 132+1*!, 133+1!
>> Y IDUSAGE+1, 1.06+1, 123.08+1, 123.5+1, 132+1
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Found Entries |  External References |  Global Variables Directly Accessed |  Local Variables |  All