{"aaData": [["PSB VDL START TIME", "
\nDefault number of hours prior to NOW that the VDL will display when \ninitially displayed.\n\n
\nThis is a test of a parameter allowing 1 instance per entity.\n\n
\nThis paramater is set by the users adjusting the IV column width\nIt is stored in the format nnn/nnn/nnn/nnn/nnn/nnn/nnn/nnn/nnn\n\n
\nWhen a PDMP query is ran in the background, this is the number of seconds\nthat should be given for a PDMP query to complete. After this time an\nerror will be returned to the user notifying them that their query timed\nout.\n\n
\nThis parameter controls if the PDMP report should be displayed in the \ndefault system browser.\n\n
\nWhen a PDMP query runs in the background, this parameter defines the\nfrequency (in seconds) that CPRS should check to see if the PDMP query\ncompleted.\n\n
\nThis parameter controls if the PDMP button will show on the CPRS ribbon \n a. Users have to run the query from the toolbar as the PDMP button\n will not be available on the ribbon bar to begin with. Once\n results come back then the button will appear. After button click\n (reviewing the results basically), the button will disappear.\n b. The button will also disappear when user reviews the results from\n the Toolbar instead.\nbar. (Regardless, the PDMP query can be triggered from the Tools menu).\n \n1. Always - This will display the button on the Ribbon bar all the time. \n \n2. Never - This will hide the button from the Ribbon bar permanently. \n \n3. Results Only - This will display the button only when results are\n available.\n\n
\nThis parameter is used to define the frequency (in days) a site performs \nPDMP queries. This will be used on the PDMP review form.\n\n
\nThis parameter controls the max number of characters allowed in the PDMP \nform text box.\n\n
\nThis parameter controls if copy/paste is allowed in the PDMP form text \nbox.\n\n
\nThis parameter controls whether or not the integrated Decision Support\nthe DST/CTB button on the individual consult order/action dialogs.\nTool (DST) or Consult Toolbox (CTB) integrated features of CPRS GUI are\nenabled. \n \nOFF: neither DST or CTB may be launched from within CPRS GUI.\nDST: the Launch DST button will become active.\nCTB: the Open Consult Toolbox button will become active.\n \nThis parameter value overrides the parameter values for enable/disable of \n\n
\nThis parameter will control the amount of time we will wait for the TCP/IP\nconnection to open.\n\n
\nThis parameter is used to determine how long the PDMP report URL should be\ncached for. Setting it to "0" effectively disables the caching of the URL.\n\n
\nThe Microsoft UNC path to the BCMA autoupdate server that will contain\nthe source files for the update.\n\n
\nThis parameter is used to store the entity that patient data was shared \nwith via a PDMP query. This will be used when generating reports.\n\n
\nThis parameter holds the value of the non-production URL used for testing \nDST web-based services.\nthe DST/CTB features within CPRS GUI. The URL value entered should point\nto a development, SQA, or pre-production web environment. The URL should\nspecify the protocol and domain.\nE.g. https://example.test.domain.domain.ext\n \nThis parameter is intended for use by software development and quality \nassurance staff needing to use the DST features within CPRS GUI against\nnon-production web environments. CPRS GUI will use this URL when invoking\n\n
\nThis parameter enables the Open Consult Toolbox button on the Receive\nConsult action dialog in CPRS GUI. A YES value enables the button and\nmakes it visible; NO will keep the button hidden and disabled.\n \nSetting the ORQQCN DST/CTB FEATURE SWITCH parameter to OFF will override\nany setting for this action dialog parameter.\n\n
\nThis parameter enables the Open Consult Toolbox button on the Schedule\nConsult action dialog in CPRS GUI. A YES value enables the button and\nmakes it visible; NO will keep the button hidden and disabled.\n \nSetting the ORQQCN DST/CTB FEATURE SWITCH parameter to OFF will override\nany setting for this action dialog parameter.\n\n
\nThis parameter holds the value of the production URL used by the DST/CTB\nfeatures within CPRS GUI. CPRS GUI will use this URL when invoking these\nweb-based services.\n \nThe URL should specify the protocol and domain.\nE.g. https://example.test.domain.domain.ext\n \nThis parameter value should not ordinarily change outside of a VistA patch\nupdate or possibly VHA national program office guidance.\n\n
\nThis parameter enables the Open Consult Toolbox button on the Cancel\n(Deny) Consult action dialog in CPRS GUI. A YES value enables the button\nand makes it visible; NO will keep the button hidden and disabled.\n \nSetting the ORQQCN DST/CTB FEATURE SWITCH parameter to OFF will override\nany setting for this action dialog parameter.\n\n
\nThis parameter enables the Launch DST/Open Consult Toolbox button on the\nEdit/Resubmit a Consult dialog in CPRS GUI. A YES value enables the button\nand makes it visible; NO will keep the button hidden and disabled.\n \nSetting the ORQQCN DST/CTB FEATURE SWITCH parameter to OFF will override\nany setting for this action dialog parameter.\n\n
\nThis parameter enables the Open Consult Toolbox button on the Discontinue\nConsult action dialog in CPRS GUI. A YES value enables the button and\nmakes it visible; NO will keep the button hidden and disabled.\n \nSetting the ORQQCN DST/CTB FEATURE SWITCH parameter to OFF will override\nany setting for this action dialog parameter.\n\n
\nThis parameter allows the description associated with a status to be\ndisplayed with the current status of an order when a detailed\ndisplay is requested.\n\n
\nThis parameter enables the Open Consult Toolbox button on the Forward\nConsult action dialog in CPRS GUI. A YES value enables the button and\nmakes it visible; NO will keep the button hidden and disabled.\n \nSetting the ORQQCN DST/CTB FEATURE SWITCH parameter to OFF will override\nany setting for this action dialog parameter.\n\n
\nThis parameter enables the Launch DST/Open Consult Toolbox button on the\nAdd Comment to Consult action dialog in CPRS GUI. A YES value enables\nthe button and makes it visible; NO will keep the button hidden and\ndisabled.\n \nSetting the ORQQCN DST/CTB FEATURE SWITCH parameter to OFF will override\nany setting for this action dialog parameter.\n\n
\nThis parameter enables the Open Consult Toolbox button on the Update\nSignificant Findings consult action dialog in CPRS GUI. A YES value\nenables the button and makes it visible; NO will keep the button hidden\nand disabled.\n \nSetting the ORQQCN DST/CTB FEATURE SWITCH parameter to OFF will override\nany setting for this action dialog parameter.\n\n
\nThis parameter enables the Open Consult Toolbox button on the\nAdministratively Complete consult action dialog in CPRS GUI. A YES value\nenables the button and makes it visible; NO will keep the button hidden\nand disabled.\n \nSetting the ORQQCN DST/CTB FEATURE SWITCH parameter to OFF will override\nany setting for this action dialog parameter.\n\n
\nThis parameter enables the Launch DST/Open Consult Toolbox button on the\nOrder a Consult dialog in CPRS GUI. A YES value enables the button and\nmakes it visible; NO will keep the button hidden and disabled.\n \nSetting the ORQQCN DST/CTB FEATURE SWITCH parameter to OFF will override\nany setting for this order dialog parameter.\n\n
\nThis is the path that is appended to the Decision Support Tool (DST) URL\nand is used by CPRS GUI when opening the associated web page for DST.\n\n
\nThis is the path that is appended to the Consult Toolbox (CTB) URL and is\nused by CPRS GUI when opening the associated web page for CTB.\n\n
\nThis will contain a list of Person Class VA codes. This will be used \nto determine if the user is an authorized PDMP user.\n\n
\nThis parameter allows you to turn of entry of Mental Health instruments\nvia the now deprecated Secure Desktop. Setting the parameter to 'Yes'\nwill disable Secure Desktop, even if it is installed on the client.\n\n
\nThis is used to determine which scoring and question text to use for the \nAUDC report. The report format changed with YS*5.01*141.\n\n
\nMailgroup to notify when updates or update errors occur.\n\n
\nThis flag will allow the MoCA instrument in MHA to check for required \ntraining starting September 2020.\n\n
\nThis text is required by the vendor to allow the clinician to affirm that\nthey have taken the required training for any of the MoCA instruments.\n\n
\nThe MoCA attestation dialog will display in MHA after this date.\n\n
\nThis parameter defines the host system default directory where XTMPSIZE.DAT\ncan either be read or written. It must be a directory where the user\nhas read/write privileges.\n\n
\nThis parameter allows the site to control whether or not Vitals will \ndisplay metric values in the first column or the third column on the \nCPRS coversheet and in the panel at the bottom of the Note on the Notes tab. \n \nIf you opt to display metric values in the 1st column, imperial values \nwill display in the third. The reverse is also true. If metric values \nstay in the 3rd column, imperial values will display in the first.\n\n
\n\n\n\n
\nThis value will determine the default option selected for the nature of \norder for a nurse user in CPRS.\n\n
\nThis Parameter is for the CPRS GUI application to enable/disable \nunflagging restrictions on flagged orders. This can be set at the Package,\nSystem, and Division levels.\n\n
\nThis Parameter is for the CPRS GUI application to set up a customized \nmessage to send to users who are unauthorized to unflag an order.\n\n
\n This is the ASU User Class whose members will be excluded from the Add \n Additional Signer List selection in CPRS.\n\n
\nThis parameter allows orders to be reviewed when a patient is transferred\nor discharged, and when a clinic appointment is made or canceled.\n\n
\nThis sets the defaults for surrogate settings in CPRS as 2 pieces\n \n Example:\n -------\n 1,10 = Enabled with a default Stop Date 10 days after the default\n Start Date that is determined by CPRS.\n 0 = Disable use of default date range.\ncomma (,) delimited.\n \n Piece Description\n 1 (Required) Enable/Disable Surrogate Defaults: 1 = enable, 0 = disable\n 2 (Optional) Days to Default Stop Date: When a user enters a new\n surrogate, this is the number of days after the default\n Start Date that the Stop Date will be defaulted. Range\n is from 1 - 30 days. Required if Piece 1 is set to enable.\n\n
\nThis is the number of hours to wait before sending a notification to the \nuser who flagged the order to let them know it was not unflagged.\n\n
\nThis parameter allows the site to switch off tasking of PCE updates from \nCPRS.\n\n
\nThis is the parameter to disable the Identify Required Fields functionality.\nEntering "YES" will disable the functionality to Identify Required Fields\nin CPRS.\n\n
\n When an error occurs and the Exception Logger is enabled (PRT EXCEPTION\n LOGGER), then any file(s) that are older than the number of days set in \n this parameter will be removed from the user's machine.\n\n
\n When this parameter is set to "yes" the application will display a \nName.txt"\n. \n \nType <Enter> to continue or '^' to exit: \n Example: \nC:\\Users\\VHAISPUSER\\AppData\\Local\\ProviderRoleTool.exe\\ProviderRoleTool_16\n136_01_13_16_16\n_43_LOG.TXT\ncustom \n access violation screen to the user as well as logging the error stack \nand \n allowing this to be sent via an email (if PRT EXCEPTION EMAIL is not \nblank)\n. \n The log files are currently stored in the following folder \n "C:\\Users\\USER'S VHAID\\AppData\\Local\\APPLICATION NAME\\Unique Log File \n\n
\n When the Exception Logger is enabled (PRT EXCEPTION LOGGER) the user has \nthe ability to pre populate an email through Microsoft Outlook. If this \nparamater is not empty than the user can email the error log and this \nemail address will be used for the pre population of that email.\n\n
\nThis paramater holds the screen size information for Provider Role Tool\n\n
\nThis parameter defines the number of hours that orders remain in the\n"Active/Current Orders" context after they have been completed.\n\n
\nThe purpose of this parameter is to allow a site to enable/disable the \ndisplay of the patient's caregiver information in the Computerized \nPatient Record System (CPRS) patient inquiry screen. The parameter may be \ndefined at the SYSTEM or DIVISION level. By default, the display will be \nenabled.\n\n
\nThis parameter will identify the last assignment settings used for this \nuser in MHA-WEB. The settings include Ordered By, Interviewer, \nLocation, Administration Date, and associated Consult if applicable.\n\n
\nThis parameter will identify the list of favorite instruments for a user.\n\n
\nThis flag will enable/disable Computerized Adaptive Testing in MHA-Web.\n\n
\nThe API Key is sent on the message header for the UAM Address Validation \nService. Without a valid key, the request is rejected. \n\n
\nThis parameter defines the list of batteries for a user.\n\n
\nThis parameter defines the graphing preference properties for a user.\n\n
\nThis parameter defines the graphing special report configured for each \nuser.\n\n
\nContains Reminder Terms that are used to assigned Radiology Procedures to \na the Breast Cascade file.\n\n
\nThis parameter allows the initials of the person who entered the order to\nbe displayed on the order summary reports. The initials take up an\nadditional line on the display and are shown just below the Ord'd date\ntime.\n\n
\nPlease enter a number from 1-99 for Instance and an email address for \nValue.\n\n
\nThis parameter will determine whether or not the ORMTIME job will \nautomatically define the nature of order for any user without a current \ndefault.\n\n
\nThis paramater contains the full URL for the CAPRI News Server\n\n
\nThis parameter defines the report view preference properties for a user.\n\n
\nThis parameter contains the date/time when the functionality in patch\nDG*5.3*1067 becomes active.\n\n
\nIt will set the device for the Pharmacist Access Report output.\n\n
\nIt will set the email group for the Pharmacist Access Report.\n\n
\nIt will set the device for the logical access report output.\n\n
\nIt will set the email group for the logical access report output.\n\n
\nThis parameter contains the date/time when the functionality in patch\nDG*5.3*1075 becomes active.\n\n
\nThis parameter allows the attending physician to be prompted as a default\nwhen adding new orders.\n\n
\nThis parameter contains the minimum CAPRI GUI/Vista Patch version that is\ncompatible with the server version. List the VistA patch followed with \n.GUIversion#\nFormat: DVBA*2.8*240.1\n\n
\nThis parameter contains the security token for CAPRI Users to send \nClinical Documents to the VBA EFolder\n\n
\nThis parameter checks if the PIV transmission process can be utilized to \ntransmit clinical documents.\n\n
\nThis parameter checks if the proxy transmission process can be utilized \nto transmit clinical documents.\n\n
\nThis parameter will return the PIV URL when the PIV transmission process\nis enabled to transmit clinical documents.\n\n
\nThis parameter will return the proxy URL when the proxy transmission\nprocess is enabled to transmit clinical documents.\n\n
\nThis parameter returns the priority of the transmission method assigned.\n\n
\nThis parameter stores the PIV resource which will be appended to a claims \nevidence URL.\n\n
\nThis parameter stores the proxy resource which will be appended to a \nclaims evidence URL.\n\n
\nThis parameter determines whether prescriptions can be parked.\nThe values of this paramter can be controlled down to the Division entity.\n\n
\nContains the integer value of the last PB sorted column on the VDL\n\n
\nThis points to the default entry in the PX ICE WEB SERVER file (#920.75).\nIt is unncessary to specify this value if there is only one entry in the \nPX ICE WEB SERVER file.\n\n
\nThis parameter will be used to determine which CPT code to automatically\nfile when a skin test reading is recorded. If left blank, a CPT code will\nnot automatically be filed when a skin test reading entry is recorded.\n\n
\nThis parameter determines the sequence sites want the immunization \ncontraindications to appear. Sites do not need to set a sequence for every\ncontraindication. For example, if a site wants to set the "Current Acute\nIllness" contraindication to the top of the list. Sites will set a value\nof 1 for that entry and CPRS will display the rest of the \ncontraindications after the "Current Acute Illness" contraindication.\n\n
\nThis parameter determines the sequence sites want the immunization refusal\nreasons to appear. Sites do not need to set a sequence for every refusal\nreason. For example, if a site wants to set the "PATIENT DECISION" refusal\nreason to the top of the list. Sites will set a value of 1 for that entry\nand CPRS will display the rest of the refusal reasons after the "PATIENT \nDECISION" refusal reason.\n\n
\nThis parameter determines the sequence sites want the immunization \ninformation sources to appear. Sites do not need to set a sequence for\nevery information source. For example, if a site wants to set the\n"HISTORICAL INFORMATION - SOURCE UNSPECIFIED" information source to the\ntop of the list. Sites will set a value of 1 for that entry and CPRS will\ndisplay the rest of the information sources after the "HISTORICAL\nINFORMATION - SOURCE UNSPECIFIED" source.\n\n
\nThis parameter controls whether the system will send an alert when the \nimmunization lot inventory is running low.\n\n
\nThis parameter specifies the maximum number of days of alert data to\ndisplay when viewing processed alerts in CPRS GUI. Allowable values are \nfrom zero up to 30 days. This parameter may be set by individual users \nfrom within CPRS GUI. It corresponds to the "Show Log Data for (days)" \nfield of the Processed Alert Preferences window. That window is opened by\nthe Processed Alert Settings button found on the Notifications tab of the\nOptions window (Tools > Options > Notifications).\n\n
\nThis parameter specifies the maximum number of individual alerts to\ndisplay when viewing processed alerts in CPRS GUI. This parameter may be\nset by individual users from within CPRS GUI. It corresponds to the "Max #\nof records to show" field of the Processed Alert Preferences window. That\nwindow is opened by the Processed Alert Settings button found on the\nNotifications tab of the Options window (Tools > Options > Notifications).\n\n
\nThis parameter allows site to define which note title should be used when \ngenerating a note from the Immunization CoverSheet Pane.\n\n
\nContains the integer value of the last IV sorted column on the VDL\n\n
\nThis is the custom message text for both new and existing CLOZAPINE orders\nand for providers missing the YSCL AUTHORIZED security key and missing a\nDEA#.\n\n
\nThis parameter is used to select the reminder defintion to evaluate when \nentering data for a skin test.\n\n
\nThis parameter is used to select the reminder defintion to evaluate when \nentering data for an immunization.\n\n
\nThis parameter is used to select if the ICE decision support display\nor the Clinical Reminder decision support display is shown when entering \ndata for an immunization.\n\n
\nThis parameter allows a site to select which Immunization can only be \nentered through a Reminder Dialog and not access from the coversheet.\n\n
\nThis parameter let sites define the contact information that will appear \nin the no active immunization message in CPRS.\n\n
\nThis parameter let sites marked location where the CPRS coversheet \nimmunization should mark a diagnosis as a primary diagnosis.\n\n
\nThis parameter will identify a section of text found in the first three\nlines of a safety plan. The health factor categories stored in the YSB \nSAFETY PLAN HF CATEGORY parameter are used to identify the visit which \nregisters the health factors but it cannot identify the note itself. If \nmore than one note was attached to the visit then we need to look at the \ntext found in the note. A note is considered to be a safety plan if any \nof the text strings stored in this parameter are found in the first three \nlines of the note.\n\n
\nThis parameter will identify a section of text found in the first three\nlines of a safety plan. The health factor categories stored in the YSB \nCSRE HF CATEGORY parameter are used to identify the visit which registers\nthe health factors but it cannot identify the note itself. If more than\none note was attached to the visit then we need to look at the text found\nin the note. A note is considered to be a CSRE if any of the text strings\nstored in this parameter are found in the first three lines of the note.\n\n
\nThis is a test of a parameter that allows multiple instances.\n\n
\nUsed by the GUI application to determine if the division is using the CPRS Med Order Button.\n\n
\nThis parameter will define the columns shown and order for the SPP MHA \nDASHBOARD application.\n\n
\nThis parameter will define the Health Factor that is used to indicate that\na Safety Plan was declined. VA-SP REFUSED SAFETY PLANNING\nThis is used by the SPP MH Dashboard to determine the status of the last \ninstance of a Safety Plan.\n\n
\nThis parameter will identify the health factors for a NEW EVALUATION \nfiled by the CSRE reminder dialog. This information will be\nused by MH Dashboard to identify visits that contain CSRE notes.\n\n
\nThis parameter will identify the health factors for an UPDATE TO AN \nEXISTING EVALUATION filed by the CSRE reminder dialog. This information\nwill be used by MH Dashboard to identify visits that contain CSRE notes.\n\n
\nThis parameter will identify the health factor for a Safety Plan for \nquestion:\nOther than mental health providers and counselors, who can you contact \nwho helps take your mind off your problems or helps you feel better?\nAnswer=Veteran describes a lack of social contacts.\n\n
\nThis parameter will identify the health factor for a Safety Plan for \nquestion:\nOther than emtnal health providers and counselors, who can you contact \nwho helps take your mind off your problems or helps you feel better?\nAnswer=Enter contacts here \n(Meaning patient has social contacts)\n\n
\nThis parameter will define the Health Factor that is used to indicate that\na Safety Plan was reviewed. VA-SP SAFETY PLAN REVIEWED\nThis is used by the SPP MH Dashboard to determine the status of the last \ninstance of a Safety Plan.\n\n
\nThis parameter defines how MHA Web interacts with Progress Notes. \nIt is used as a switch to enable/disable creation of progress notes upon \nadministration of an instrument.\n\n
\nThis parameter is for storing the number of records which you wish to \nprocess per execution of a report remote procedure.\n\n
\nThese are parameters related to the Accounts Receivable data extracts \nand pertaining to secure FTP using public/private SSH key pair technology\n\n
\nThis is a site parameter to enable continuous orders (i.e., orders with a\n LB #806 WC ROUTINE\n \n 05/19 11:04 GLUCOSE BLOOD SERUM Marcus Welby, MD\n LB #807 WC ROUTINE\n \nIf this parameter is set to NO, the same order would appear as:\n \n 05/17 11:04 GLUCOSE BLOOD SERUM QD Marcus Welby, MD\ncontinuous schedule, e.g., QD or Q4H) to be expanded or not on the chart\ncopy. If set to YES, an order for GLUCOSE BLOOD SERUM with the schedule\nQD would appear on the chart as:\n \n 05/17 11:04 GLUCOSE BLOOD SERUM Marcus Welby, MD\n LB #805 WC ROUTINE\n \n 05/18 11:04 GLUCOSE BLOOD SERUM Marcus Welby, MD\n\n
\nThis holds the titles of the VHA New Person file that is allowed to send \nClinical Documents to the EFolder via CAPRI GUI\n\n
\nLOCATION INFORMATION FOR VERIFICATION OF CLINICAL DOCUMENTS TO EFOLDER \n\n
\nThis is the maximum number of entries allowed to be stored in the ^DGAUDIT\nglobal which houses the data for DG VAS QUEUE (#46.3).\nThe DG VAS EXPORT Option, which runs as a background task, will check to \nsee if this maximum number of entries has been exceeded. If so, then it \nwill delete the oldest entries in File #46.3 until the number of entries \nno longer exceeds this maximum.\n\n
\nThis is a flag that can be turned on by entering a 1 or off by entering a\n0 to send data via email to the VAS MONITOR GROUP that will write out the\nlocal variables at the time the process is running for the VAS process. \nThis flag is defaulted to 0.\n\n
\nThis is the number of audit records that will be sent in a single \nbatch to the Vista Audit Solution. \n\n
\nThe number of days exceptions logged by the Vista Audit Solution (VAS) \nexport process will remain available before being permanently deleted.\n\n
\n This is the SYSTEM email group where any issues that would arise or \n System type emails would go to alert the Systems team of any errors or \n System issues.\n\n
\nIf the VAS export is unable to successfully write to the VAS REST API, the\nprocess will quit after the maximum number of write attempts is exceeded.\n\n
\nThis parameter will contain the list of admin sites that are selectable \nfor skin tests.\n\n
\nThis parameter definition enables/disables the new RPC routine ORNEWPERS.\n\n
\nThis is the format used when printing chart copies of the orders for the\nhospital.\n\n
\nContains various parameters for Above PAR Reports.\n\n
\nEntering a value of YES will allow a provider with an expired DEA number \nto be able to prescribe controlled substances based on their VA number.\nEntering a value of NO will not allow a provider with an expired DEA \nnumber to be able to prescribe controlled substances. A provider without a\nDEA number will still be able to prescribe controlled substances if they\nhave a VA number entered in VistA.\n\n
\nWhen a Controlled Substance order is being created, this parameter\nlevel. The order of precedence is as follows:\n \n 1 Division DIV [INSTITUTION]\n 2 System SYS [XXX.XXX.DOMAIN.EXT]\nprovides the message displayed if a patient's ZIP code is missing or\nif the ZIP code is invalid.\n \nThe purpose of this message is to provide a point of contact to correct\nthe invalid ZIP code. This message may be set differently for each\nDivision within a multi-divisional facility. A message may also be set\nat the System level. If no message is set at the Division level or at\nthe System level, then a generic message is provided at the package\n\n
\nThis parameter determines if the Patient Missing ZIP Code Message\n parameter is in effect.\n A 'Yes' value means that the Patient Missing ZIP Code Message parameter\n is in effect.\n A 'No' value or a null value means that the Patient Missing ZIP Code \n Message parameter is not in effect.\n\n
\nThis parameter contains the full URL that points to the TeleReader specific site service.\n\n
\nThis parameter allows the site to control the CPRS 'tabs' write access.\nThe control can be at the user, division, system (site), or package level.\nThe tabs that can be defined are: C for Consults, D for Discharge Summary,\nM for Meds, O for orders, P for Problems, or S for Surgery.\n\n
\nThis parameter allows the site to control the CPRS write access for some\nmiscellaneous functions. The control can be at the user, division, or\nsystem (site). The functions that can be defined are: A for Allergies, D\nfor Delayed Orders, E for Encounters, I for Immunizations, R for the\nReminder Editor, and W for Women's Health. The parameter also has a\npackage level but it should not be set by the site.\n\n
\nThis parameter allows a site to control whether or not a user, a division,\nnot overwrite it.\nor the entire system (site) is allowed to write orders by assigning write\nprivilege by order display groups. This parameter is only evaluated if the\nuser has access to the Orders tab based on the parameter settings in the\nparameter OR CPRS TABS WRITE ACCESS. The parameter also has a package\nlevel but IT should not be set by the site.\n \nIf the display group parameter is defined at a higher precedence level, \nthe value will be passed down to the lower level if a lower level does \n\n
\nThis error message tells the CPRS user why they are not allowed to perform\nan attempted action. For example: If write access is restricted and a user\nattempts to create an order.\n\n
\nThe purpose of this parameter is to allow control over whether or not the\nComputerized Patient Record System (CPRS) will pause the processing of\nuser input while Windows messages are being processed. When this doesn't\noccur, access violation errors may happen.\n\n
\nThis is the format used to print the header of the chart copies of orders\nfor the hospital.\n\n
\nThis parameter can be used to simulate as if the site migrated to an \nElectronic Health Record (EHR) system. This will only work in the \ntest/pre-prod account. When set to YES, it will cause the ONEHR^ORACCESS \nAPI to return a "1", as if the site is on EHR. It should only be used for \ntesting purposes.\n\n
\nThis parameter contains the website URL that VistA will access after the \nuser clicks on the MHV button in the CPRS GUI.\n\n
\nThis parameter indicates whether DSSO*2.0*5 has been installed yet in \norder to determine whether to reset the parameters for the Prepopulator \nand the DAT Tracker.\n\n
\nThis parameter indicates whether the task record for a TaskMan task\nshould be deleted. It defaults to 1/"Yes" - the record should be deleted.\n\n
\nThis parameter indicates the number of hours at which scheduled option \n If RESCHEDULING FREQUENCY=1D, that equals 24 hours. Set this\n parameter to 23 hours.\n \n If RESCHEDULING FREQUENCY=2D, that equals 48 hours. Set this \n parameter to 47 hours.\nDSSO APPL TRANS EXT - ALL should be stopped. It is used to prevent more \nthan one scheduled option DSSO APPL TRANS EXT - ALL tasks from running at\nthe same time to avoid adding duplicate rows to the SQL Server table.\n \nTo set this parameter properly, calculate the number of hours in the \nRESCHEDULING FREQUENCY of scheduled option DSSO APPL TRANS EXT - ALL,\nand set this parameter to one hour less than that number of hours.\n Examples: \n\n
\nWhen an option DSSO APPL TRANS EXT - ALL task is stopped by entering\n"999999999999999" into parameter DSSO LAST APPLIANCE TRANSACTION, the\nprevious value of DSSO LAST APPLIANCE TRANSACTION is saved in this\nparameter. On the next start of the option, this parameter DSSO LAST \nAPPLIANCE TRANS will be set to the value in DSSO APPL TRANS RESTART IEN,\nand DSSO APPL TRANS RESTART IEN will be set to 0. Processing will resume\nat the correct IEN.\n\n
\nThis contains the URL used to reach the web page for entering Mental\nhttps://test.mha.domain.ext/assignment/cprs/???/\nHealth Assistant (MHA) assessments via CPRS Reminder Dialogs. The\nformat of the URL for production is (where ??? is the station number):\n \nhttps://mha.domain.ext/assignment/cprs/???/\n \nThe format of the URL for test accounts is (where ??? is the staion\nnumber):\n \n\n
\nThis parameter will save properties of the CPRS Mental Health DLL to \nallow switching from the core version to the web version and back.\n\n
\nThis holds the Client ID value for the CAPRI News Feed\n\n
\nThis is the CAPRI News Feed Tenant ID\n\n
\nThis is the format used to print the footer of the chart copies of orders\nfor the hospital.\n\n
\nThis is the CAPRI News Feed Client Token\n\n
\nThis parameter stores the CAPRI News Feed Token URL\n\n
\n This parameter contains the full URL for the CAPRI News Feed Site ID URL\n\n
\nThis parameter contains the full URL for the CAPRI News Feed Drive ID URL\n\n
\nThis parameter contains the full URL for the CAPRI News Feed File Info URL\n\n
\nThis parameter controls if a system will create a precache image\nduring patient radiology registration exam.\n\n
\nONE-TIME schedule that should be excluded from Start/Stop dates override \nmodifications\nThe schedule can be added for the system and for divisions.\nUsers can remove any schedule by selecting the entry number and then \nentering @ sign.\n\n
\nThis parameter determines which facility is stored as the reporting\nfacility on POC (point of care) results.\n \nDefining a facility with this parameter is optional. If the parameter\nhas been defined, that reporting facility determination overrides\nany reporting facility retrieved by other POC logic.\n\n
\nThis parameter stores whether to filter lab orderable items by the user's \nsigned-in institution. A value of YES will enable filtering, NO will \ndisable filtering.\n\n
\nThe API Key is sent on the message header for the UAM Address Validation\nService. Without a valid key, the request is rejected.\n\n
\nThis is used by the GUI to determine the number of minutes the VDL shall remain idle before shutting down.\n\n
\nThe API Key is sent on the message header for the UAM Address Validation\nService. Without a valid key, the request is rejected.\n\n
\nWhen set to Yes, this parameter adds module information to the exception\nlog for addresses outside of CPRS, such as window's DLLs. It also finds\nthe closest exported function name that's before or at the address. \nExample:\n[7691591E] C:\\WINDOWS\\System32\\user32.dll (Offset 110/$6E, "SendMessageW")\n\n
\nThis parameter definition controls the maximum number of days in the\nfuture for which a consult order may be created in CPRS GUI. The exported\nvalue is 390 days and should not be changed.\n\n
\nThis parameter definition controls the maximum number of days in the\nfuture for which an imaging order may be created in CPRS GUI. The\nexported value is 390 days and should not be changed.\n\n
\nWhen the size of the activity log is greater than 0, CPRS will keep track \nof user actions, so that when an exception occurs the most recent \nactivities will display on the exception log. This will make a \nsignificant impact for developers trying to determine the cause of the \nerror.\n\n
\nWhen the size of the window message activity log is greater than 0, CPRS \nwill keep track of window messages sent to various controls, so that \nwhen an exception error occurs the most recent window messages will \ndisplay on the exception log. This will make a significant impact for \ndevelopers trying to determine the cause of some errors.\n\n
\nCPRS already tracks remote procedure calls (RPCs). This is the number of \nRPC calls that will show on an exception log.\n\n
\nThis parameter holds the alternate division for the system.\n\n
\nThis parameter toggles the use of the new TIUMOBJ routine instead of \nTIULMED* routines for retrieving medication data for TIU Medication \nObjects.\n\n
\nThis parameter allows a custom list of reports, with sequencing, on the\nReports tab.\n\n
\nWhen this parameter is set to "yes", certain MHA VistA application errors \nwill get logged to the VistA error trap. \n\n
\nThis will store the GITHUB Link CAPRI will use to download C&P Worksheet\ntemplates\n\n
\nThis will store the GITHUB token needed by the CAPRI GUI to download the \nDBQ worksheet blank templates\n\n
\nThis is the Application ID for GITHUB usage by the CAPRI GUI application\n\n
\nDate returned by CAPRI GUI for the GITHUB download\n\n
\nThis is the installation ID for GitHub used by the CAPRI GUI\n\n
\nThis is the Sharepoint IEPD info being used by the CAPRI GUI.\n\n
\nPDFs containing invalid characters that need to be replaced\n\n
\nThis parameter stores the URL to the CAPRI Documentation Library that \nholds the user manual, technical manual, and release notes.\n\n
\nThis is array of value(s) for CMT SSN Variances\n\n
\nThis parameter controls whether each cover sheet section is loaded in the\nforeground or background.\n\n
\nValue for display in the CAPRI GUI, 1=CMT or 2=PASCAL.\n\n
\nValue for display in the CAPRI GUI, 1=SSN, 2=SecID, 3=Both, 4=None.\n\n
\nDBQ PDF signature field names to enable CMT PDF signing.\nEach value will start with a letter followed by the equal sign:\nA - Address\nD - Date\nN - Name\nS - Signature\nX - the value is to be skipped on the GUI side\n\n
\nContains list of DBQs that need to skip the conditional logic.\nWill contain "ALL" to skip logic for all DBQs\nWill contain "None" to not skip logic for all DBQs\nWill contain a list of DBQs that will need the logic skipped\n\n
\nThis parameter is storing a 1 to determine that TIU Notes \ntext data should be populated in whole or 0 TIU Notes text\ndata directs to review CAPRI for PDF text document.\n\n
\nCurrently, the text notifying a user that they are attempting to access a \nfrom the server, rather than require a Graphical User Interface change\nwhen it needs to be updated.\nsensitive record is controlled by a Remote Procedure Call (RPC) in the \nRegistration package in Veterans Health Information Systems and \nTechnology Architecture (VistA).\n \nHowever, the prompt for the user - asking them if they wish to continue - \nis not included in that RPC. \n \nThe purpose of this parameter is to make that final prompt be controlled \n\n
\nList of Parent Child field names to be skipped with the conditional \nlogic. \n\n
\nChild field types that need to be reset with conditional formating\n\n
\nThis is a free text parameter to signal to the CAPRI GUI if a new CMT \nIEPD Download is required. Values are 0 (Zero) to determine that one is \nnot required or Date (MM/DD/YYYY) to determine it is required.\n\n
\nConditional Field types that need to be skipped.\n\n
\nThis parameter is used to record the progress and status of the conversion\nof Consult Procedure data from the PROTOCOL file to the GMRC PROCEDURES\nfile.\n\n
\nMax length of characters before word wrap.\nCreated for Clinical Documents Tab display in CAPRI. \n\n
\nParameter to store the remarks field and the fields to skip on the CMT \n DBQ Medical Opinion update.\n\n
\nThis parameter contains information about the Backup Reviewer for \nunprocessed alerts. This person will be sent the alerts for the\nspecified entity that remain unprocessed by the original recipients.\n\n
\nThis is a 'dummy' parameter definition that is used by XPARLIST to get\na list of all entities. The Allowable Entities multiple for this parameter\nshould list all entities defined in PARAMETERS.\n\n
\nThis is the label format to be used when printing labels for this package.\n\n
\nThis is the requisition format to be used when printing requisitions for\nthis package.\n\n
\nThis is the printer that is to be used when printing order copies\nto the service.\n\n
\nThis is the format to be used when printing order copies to the\nservice.\n\n
\nThis is the format to be used for the header portion of the order\ncopy to the service for this package.\n\n
\nThis is the format to be used for the footer portion of the order\ncopy to the service for this package.\n\n
\nThis is the device to which service copies will be printed for the\ncorresponding hospital location. (e.g., if the patient is admitted\nto ward 1A, for which the SERVICE COPY PRINT DEVICE is called P1A,\nfor the IV MEDICATIONS package, then service copies of all of that\npatient's IV orders will be printed to P1A, overriding the SERVICE\nCOPY DEFAULT DEVICE, if one has been defined.\n\n
\nThis is the printer on the ward/clinic/other where the chart copy\n(1) If this parameter is set for Room-Bed, the ORPF PROMPT FOR CHART\n COPY parameter for the corresponding location(s) must be defined.\n The prompt parameter cannot be defined at the Room-Bed level.\n(2) If Room-Bed "device" configurations are needed, the parameter must \n be edited directly through the CPRS Manager Menu / CPRS Configuration\n (IRM) / General Parameter Tools menu. Room-Bed fields are not \n available under the Print/Report Parameters menu. \nshould be printed. If the field PROMPT FOR CHART COPY (i.e. the \nparameter "ORPF PROMPT FOR CHART COPY") is 0 or 2, this printer is\nautomatically used to print the report. If the field PROMPT FOR CHART\nCOPY is 1, the user is asked for device with the entry in this field as a\ndefault.\n \nRoom-Bed Notes:\n \n\n
\nThis is the printer on the ward/clinic/other where the label should\n parameter for the corresponding location(s) must be defined. The\n prompt parameter cannot be defined at the Room-Bed level.\n(2) If Room-Bed "device" configurations are needed, the parameter must \n be edited directly through the CPRS Manager Menu / CPRS Configuration \n (IRM) / General Parameter Tools menu. Room-Bed fields are not \n available under the Print/Report Parameters menu. \nbe printed. If the field PROMPT FOR LABELS (i.e. the parameter "ORPF \nPROMPT FOR LABELS") is 0 or 2, this printer is automatically used to print\nthe labels. If the field PROMPT FOR LABELS is 1, the user is asked for\ndevice with the entry in this field as a default.\n \nRoom-Bed Notes:\n \n(1) If this parameter is set for Room-Bed, the ORPF PROMPT FOR LABELS\n\n
\nThis is the printer on the ward/clinic/other where the requisition\n(1) If this parameter is set for Room-Bed, the ORPF PROMPT FOR\n REQUISITIONS parameter for the corresponding location(s) must be \n defined. The prompt parameter cannot be defined at the Room-Bed level.\n(2) If Room-Bed "device" configurations are needed, the parameter must \n be edited directly through the CPRS Manager Menu / CPRS Configuration \n (IRM) / General Parameter Tools menu. Room-Bed fields are not \n available under the Print/Report Parameters menu. \nshould be printed. If the field PROMPT FOR REQUISITIONS (i.e. the \nparameter "ORPF PROMPT FOR REQUISITIONS") is 0 or 2, this printer is\nautomatically used to print the requisitions. If the field PROMPT FOR\nREQUISITIONS is 1, the user is asked for device with the entry in this\nfield as a default.\n \nRoom-Bed Notes:\n \n\n
\nThis parameter will control the ability to use the release delayed orders \naction if the OREVNT MANUAL RELEASE CONTROL parameter is set to Parameter \nor Both (Parameter and Keys). If set to No or left blank then manual \nrelease will not be allowed. If set to Yes then the manual release \naction my abe used.\n\n
\nThis field allows various levels of user interaction for printing a\nrequisition on the ward for orders.\n \n ENTER 0 for no prompts- requisitions are automatically generated.\n 1 to prompt for requisitions and which printer should be used.\n 2 to prompt for requisitions and automatically print to the\n printer defined in the REQUISITION PRINT DEVICE field.\n * don't print.\n\n
\nThis parameter specifies to the nightly background job ORTASK 24HR SUMMARY\nthat a daily order summary should be queued to the device specified in the\nDAILY ORDER SUMMARY DEVICE field.\n\n
\nThis parameter specifies the device on which the DAILY ORDER SUMMARY should\nbe queued by the nightly scheduled option ORTASK 24 HOUR SUMMARY.\n\n
\nThis parameter specifies to the nightly background job ORTASK 24HR CHART\nCOPIES that a daily Chart Copy summary should be queued to the device\nspecified by the CHART COPY DEVICE field.\n\n
\nThis parameter allows various levels of user interaction for printing a\n label on the ward for orders.\n \n ENTER 0 for no prompts- labels are automatically generated.\n 1 to prompt for labels and ask which printer should be used.\n 2 to prompt for labels and automatically print to the printer\n defined in the LABEL PRINT DEVICE field.\n * don't print.\n\n
\nThis field allows various levels of user interaction for printing a\nchart copy of the orders.\n \n ENTER 0 for no prompts- chart copy is automatically generated.\n 1 to prompt for chart copy and ask which printer should be used.\n 2 to prompt for chart copy and automatically print to the\n printer defined in the CHART COPY PRINT DEVICE field.\n * don't print.\n\n
\nDefault user or team recipients of a notification despite settings in the\nparameter ORB PROCESSING FLAG. These users/teams will always receive the\nnotification, regardless of patient.\n\n
\nDefault recipient devices of a notification despite settings in parameter\nORB PROCESSING FLAG. These devices will always receive the notification,\nregardless of patient.\n\n
\nThe number of minutes to delay between processing OCX time-based events via\nTaskMan. If the parameter is not set, a default of 240 minutes will be \nused. The maximum number of minutes is 100,00 (1667 hours or 69 days).\n\n
\nThis is the format used to print the footer of order requisitions\nfor the hospital.\n\n
\nThis is the format used to print the header of order requisitions\nfor the hospital.\n\n
\nThis parameter is used by order checking to determine if\na patient weighs too much to be safely examined by\nthe CAT Scanner.\n\n
\nThis parameter is used by order checking to determine if\na patient is too tall to be examined by the CAT scanner.\n\n
\nThis parameter is used by order checking to determine if\na patient weighs too much to be safely examined by the MRI scanner.\n\n
\nThis parameter is used by order checking to determine if\na patient is too tall to be safely examined by the MRI scanner.\n\n
\nThis parameter allows lab urgencies to be mapped to OE/RR urgencies.\nIf a lab urgency is not in this list, the OE/RR urgency should be\nROUTINE.\n\n
\nThis parameter defines how access to the manual release action is \nRELEASE parameter controls who is allowed to manually release a delayed \norder. The OREVNT MANUAL RELEASE parameter is distributed with no \nsettings, which effectively denies access to manual release if the \ncontrol parameter is set to P. In order to have the OREVNT MANUAL RELEASE\nparameter control access to the manual release action you must set some\nlevel of the parameter to a positive (YES) value.\n \n3: Both Keys and Parameter - In this setting a check is first made to see \nif the user has either the ORES or ORELSE key. If they do not then a \ncheck is made to see if the user will have access through the parameter \ncontrolled. There are three possible settings:\nsettings. In this setting, if the user does not hold either the ORES or \nORELSE key they could still have access to the action based on your \nparameter settings, which may be more liberal than you'd like. Be sure \nto check your settings.\n \n1: Keys Only - In this setting only holders of the ORES and ORELSE key \nmay manually release a delayed order. This is how the system previously \ncontrolled access to this action. If the OREVNT MANUAL RELEASE CONTROL \nparameter is not set then this will be the default setting.\n \n2: Manual Release Parameter Only - In this setting the OREVNT MANUAL \n\n
\nThis points to a menu in the order dialog file. This menu will be used\nto determine which lab tests appear initially in the lab test list box\nwhen the lab dialog is clicked while an inpatient is selected.\n\n
\nThis parameter lists all the activity orders that may be selected in an\ninpatient context.\n\n
\nThis parameter lists all the patient care orders that may be selected in an\ninpatient context.\n\n
\nThis parameter lists all the patient care orders that may be selected in an\ninpatient context.\n\n
\nThis parameter lists all the patient care orders that may be selected in an\ninpatient context.\n\n
\nThis parameter lists all the patient care orders that may be selected in an\ninpatient context.\n\n
\nThis parameter lists all the patient care orders that may be selected in an\ninpatient context.\n\n
\nThis parameter lists all the patient care orders that may be selected in an\ninpatient context.\n\n
\nThis parameter lists all the patient care orders that may be selected in an\ninpatient context.\n\n
\nThis lists the lab tests that will appear first in the listbox when the\nlab dialog is selected in CPRS-GUI.\n\n
\nThis lists the drugs that will appear first in the listbox when the\ninpatient meds dialog is selected in CPRS-GUI.\n\n
\nThis lists the drugs that will appear first in the listbox when the\noutpatient meds dialog is selected in CPRS-GUI.\n\n
\nThis lists the services from which consults may be requested.\n\n
\nThis is a temporary parameter to make clinic selection quicker.\n\n
\nHealth Summary types that may be displayed by the CPRS GUI should be\nentered here. Only health summaries that do no additional prompting\nmay be selected (i.e., all time and occurrence limits must be already\ndefined). The exception to this is the Adhoc Health Summary (GMTS HS\nADHOC OPTION). The Adhoc is a special case that is handled by\nthe GUI.\n\n
\nThe number of hours backwards in time to look for duplicate lab orders.\nFor example, a value of '24' indicates a lab procedure intended to be\ncollected within 24 hours of the collection of the same lab procedure will \ntrigger an order check indicating duplicate lab order. Note: if the lab\nprocedure has an entry in the parameter OR DUP ORDER DATE RANGE OI, the\nOI parameter takes precedence.\n\n
\nThe number of hours backwards in time to look for duplicate radiology\norders. For example, a value of '24' indicates a radiology/imaging\nprocedure performed within 24 hours of the current order's effective date/\ntime will trigger an order check alerting the user to the duplicate.\n\n
\nThis is the format used when printing work copies of the orders for the\nhospital.\n\n
\nThis is the format used to print the header of the work copies of orders\nfor the hospital.\n\n
\nThis is the format used to print the footer of the work copies of orders\nfor the hospital.\n\n
\nRelease events defined by this parameter will appear first in the list \nbox when the user is writing delayed orders. These commonly used release \nevents will appear above a line with the rest of the available release \nevents appearing below the line.\n \nBefore the list is presented to the user events that are inactive and \nevents that are inappropriate for display (for example, transfer types \nwhen the patient is still an outpatient) will be removed from the list.\n\n
\nThis is the printer on the ward/clinic/other where the work copy\n(1) If this parameter is set for Room-Bed, the ORPF PROMPT FOR WORK\n COPY parameter for the corresponding location(s) must be defined.\n The prompt parameter cannot be defined at the Room-Bed level.\n(2) If Room-Bed "device" configurations are needed, the parameter must \n be edited directly through the CPRS Manager Menu / CPRS Configuration \n (IRM) / General Parameter Tools menu. Room-Bed fields are not \n available under the Print/Report Parameters menu.\nshould be printed. If the field PROMPT FOR WORK COPY (i.e. the \nparameter "ORPF PROMPT FOR WORK COPY") is 0 or 2, this printer is\nautomatically used to print the report. If the field PROMPT FOR WORK COPY\nis 1, the user is asked for device with the entry in this field as a\ndefault.\n \nRoom-Bed Notes:\n \n\n
\nCollections for Saturday's, Sunday's, Holidays, etc. are never skipped\nfor excepted locations.\n\n
\nThis field will allow an additional prompt to confirm the provider\nselection when adding new orders.\nEntering 2 in this field will exclude holders of the ORES key\n(providers) from this check.\nNotice that these parameters also control the default presented to the user:\n'Are you sure? <no -or- yes>'\n\n
\nThis field allows a site to restrict the selection of providers\nwhen adding new orders at the 'Requesting CLINICIAN: ' prompt for\nholders of the ORELSE and OREMAS key. The restriction being that\nthey cannot select themselves as the requestor even though they may\nalso hold the PROVIDER key.\n \n 1 YES (ORELSE) -restricts only holders of the ORELSE key.\n 2 YES (ORELSE & OREMAS) -restricts holders of either key.\n\n
\nThis parameter allows the Order summaries to print in forward\nchronological order.\n\n
\nThis parameter allows the Chart Copy summaries to print in forward\nchronological order.\n\n
\nThis parameter is the number of days that should pass before an order is \npurged. Only orders with a status of discontinued, complete, expired,\ncancelled, changed, and lapsed will be purged.\n\n
\nChart copies may be printed when orders are\n a) released to the service\n b) signed by a clinician (may be after the orders are released)\n\nThis parameter determines at which point the chart copy of orders will \nprint. The chart copy may be printed when the order is released to the \nservice or delayed until the order is actually signed.\n\n
\nThe number of days backwards in time to search for lab orders/results. If\nnot indicated, the default period of 2 days will be used. The\nmaximum number of days is 100,000 or about 220 years. For inpatients.\n\n
\nThis parameter allows the Work Copy summaries to print in forward\nchronological order.\n\n
\nReturns an array of clinical reminders for a patient which can then be used\nfor searches and displays similar to the way they are used in Health \nSummary.\n\n
\nThis is the field as defined at the ^OR(100,ifn,4.5 level in file 100\nto be used to sort requisitions by.\n\n
\nThis is the field as defined at the ^OR(100,ifn,4.5 level in file 100\nto be used to sort labels by.\n\n
\n**Disabled per PSPO #2176**\nThis parameter, when set to YES, will automatically cancel\nthe Flag Orders Notification and unflag all orders for a\npatient when a user process a Flagged Orders Notification.\n\n
\nThis field allows various levels of user interaction for printing a\nwork copy of the orders.\n \n ENTER 0 for no prompts- work copy is automatically generated.\n 1 to prompt for work copy and ask which printer should be used.\n 2 to prompt for work copy and automatically print to the\n printer defined in the WORK COPY PRINT DEVICE field.\n * don't print.\n\n
\nParameter determines if any notification processing will occur. 'E' or\n'Enable' indicates the notifications system is enabled and running. 'D'\nor 'Disabled' indicates the notifications system is disabled and not\nrunning. Can be set at the Institution, System or Package level.\n\n
\nThis indicates if this institution operates at full service during\nfederal holidays.\n\n
\nIf the "copy active orders" field of a release event is set to YES then \nany orders that belong to the display groups listed in this parameter \nwill NOT be presented in the list of orders to copy. This parameter \nallows you to screen certain types of orders from being copied when \nwriting delayed orders.\n\n
\nParameter determines if order checking will log debug messages into\nlocal sys>|<order effective date/time>|<order number>|<filler data>\n \nThe data for non-zero node entries is the information passed from order\nchecking back to OE/RR. It is the order check messages plus other info to\nenhance OE/RR processing. It is in the format:\n^XTMP("ORKLOG",<order check date/time>,<pt id>,<orderable item>,<dlog mode>,\n<user id>,<non-zero>)=\n<order number>^<order check id - 864.5 ien>^<clin danger level>^<message>\n \n^XTMP("ORKLOG". 'Enabled' indicates logging will occur. 'Disabled' will\nprevent logging of messages and delete log file (^XTMP("ORKLOG")).\n \nThe data for zero node entries is the information passed to order checking\nfrom OE/RR. The zero node is in the format:\n^XTMP("ORKLOG",<order check date/time>,<pt id>,<orderable item>,<dlog mode>,\n<user id>,0)=\n<orderable item>|<filler>|<natl id^natl text^natl sys^local id^local text^\n\n\n'Yes' indicates that PKI Digital Signature functionality is enabled.\n\n
\nAnswer YES to this field to prompt with urgency for every test when\nordering through OE/RR. Tests with a forced urgency as defined in the\nLaboratory test file overide this parameter.\n\n
\nThe entry in this field will determine the type of collection that 'Quick\nOrders' will have assigned to them.\nex: Ward Collect (WC), Send Patient (SP) or Lab Collect (LC)\n\n
\nDefault device the user uses for printing BCMA reports from GUI.\n\n
\nThis parameter controls if XUP will set up a ERROR trap for the user.\n\n
\nThis parameter controls if a user when exiting XUP is dropped into VPE or\nright to the ">" prompt.\n\n
\nThis parameter may be used to identify which items should appear on the\n \nAn ampersand may be used in the name portion to identify a letter that\nshould be underlined on the menu for quick keyboard access. For example,\nto underscore the letter H in Hospital Policy, enter &Hospital Policy as\nthe name part.\n \nTo use submenus on the tools menu, you must place special text in the\ncaption and action values. Submenus must have action text SUBMENU ID,\nwhere ID is a unique identifier for the submenu. Menu items belonging to\nthe submenu must specify which submenu they belong to by appending [ID]\ntools menu which is displayed by the CPRS GUI. Each item should contain\nafter the caption. Thus the following entries create a Utilities submenu\nwith 2 child items:\n \n Utilities=SUBMENU 1\n Calculator[1]=calc.exe\n Notepad[1]=notepad.exe\n \nTo create a nested submenu, you create a submenu that belongs to another\nsubmenu s ID. For example, to create a nested submenu belonging the\nabove Utilities submenu, you would do the following:\na name that should be displayed on the menu, followed by an equal sign,\n \n Utility Web Sites[1]=SUBMENU UtilWeb\n MicroSoft Tools[UtilWeb]=http:\\\\www.msdn\n \nWhile submenu IDs at the end of a caption are not displayed on the Tools\nmenu, this is only true if a corresponding menu ID is found. If no Menu\nID is found, the square brackets and included text will appear as part of\nthe caption on the Tools menu. This allows for existing bracketed text\nto remain displayed.\n \nfollowed by the command string used to invoke the executable. This\nIf two submenus share the same menu ID, the second submenu will be\ntreated as belonging to the first menu.\n \nOne point worth noting. If you have a caption of a single dash (or a\nsingle dash followed by a submenu id), it will create a separator line in\nthe menu or submenu. This is not new functionality, but may not have\nbeen previously documented.\n \nFinally, if more than 30 menu items are assigned to the top level menu\n(i.e. they are not part of a submenu), a "More..." submenu will\nstring may also include parameters that are passed to the executable.\nautomatically be created at the top of the Tools menu, with additional\nmenu items spilling into the newly created "More..." submenu. If more\nthan 30 menu items spill into the "More..." submenu, another "More..."\nsubmenu will be created inside the first "More..." submenu, with\nadditional menu items spilling into it, and so on, as needed. Note,\nhowever, that there is a limit of 99 total menu items, since you can only\nenter an integer sequence number from 1-99 when defining the ORWT TOOLS\nMENU parameter.\nSome example entries are:\n \n Hospital Policy=C:\\WINNT\\SYSTEM32\\VIEWERS\\QUIKVIEW.EXE LOCPLCY.DOC\n VISTA Terminal=C:\\PROGRA~1\\KEA\\KEAVT.EXE VISTA.KTC\n\n
\nThis will store the number of hours for the Patient transfer notification timeframe on the BCMA Site Parameters screen.\n\n
\nSelect whether the keyboard display updates after each key press.\n\n
\nThis is the maximum number of days that multiple-continuous orders may be\nplaced. The number may be specific to each hospital location.\n\n
\nThis parameter is used to provide a default Release Event in the event\nlistbox presented when the user clicks on the 'Write Delayed Orders'\nbutton in CPRS GUI.\n\n
\nThis parameter is used to identify a menu in the ORDER DIALOG file that\nwill be used as the list of items that may be selected in the Write Orders\nlistbox of the CPRS GUI when placing orders that are to be delayed until\nthe selected EVENT occurs.\n\n
\nThis is the last date/time the tasked/time-driven notifications were\nprocessed. It is set within routines.\n\n
\nThis parameter records bounds (position & size) information for the forms\nand controls in CPRSChart (Patient Chart GUI). The individual properties\nare comma delimited (left,top,width,height).\n\n
\nThis records the width property for a control in CPRSChart (Patient Chart\nGUI). In particular, it is used for recording the positions of splitter\nbars.\n\n
\nThis records the widths of each column in a grid type control. The column\nwiths are entered from left to right and delimited by commas. For example,\n"50,260,25,78,129".\n\n
\nThis is the time for each phlebotomy collection. The instance value\nmakes each phlebotomy collection entry unique by using the $H value of\nthe collection time.\n\n
\nConversion information for CPRS. No user interaction.\n\n
\nConversion information for CPRS. No user interaction.\n\n
\nContains the list of common inpatient meds for display at the top of the\nMeds listbox in the GUI ordering dialog.\n\n
\nThis parameter determines if clerks (i.e. users holding the OREMAS key)\nare allowed to act on medication orders. If set to YES, a clerk may enter\nnew medication orders or DC these medication orders. Inpatient orders may\nbe released to the Pharmacy as 'Signed on Chart'. Outpatient orders will\nrequire the physician's signature. If set to UNRELEASED ONLY, a clerk may\nonly enter unreleased orders for both Inpatient and Outpatient. If set to\nNO, a clerk is completely prohibited from handling medication orders.\n\n
\nIf set to 'yes', when starting a new note, a check will be made for any \nunresolved consults that the current user can act upon. If any are \nfound, a dialog will be displayed asking if the user would like to see a \nlist of these consults. If set to 'no', this dialog will not be \ndisplayed.\n\n
\nThis defines the default value to be presented when the user gets the\nprompt to mark orders as Signed on Chart; if no value is entered, then\nNO is used as the default.\n\n
\nA value of YES in this parameter will print a page showing 'No Orders'\non an order summary if no orders exists for the patient within the\nspecified parameters.\n \nA value of NO in this parameter will just skip the patient, printing\nnothing when no orders exist for the patient within the specified\nparameters.\n\n
\n***This parameter has been superseded by ORWDX WRITE ORDERS LIST.***\nCurrently, the GUI references only for backward compatibility reasons.\n \nThis parameter is used do list the order dialog names that should appear in\nthe Write Orders list box of the CPRS GUI. This is the list of dialogs that\nshould be used in the inpatient setting.\n\n
\nDESCRIPTION: This Radiology/Nuclear Medicine parameter controls whether\nrestrictions are placed on imaging procedures orderable based on procedure\ntype (possible procedure types are: Detailed, Series, Parent, Broad).\n \nIf this parameter is set to '0', users are allowed to order any imaging\nprocedure regardless of type. If set to '1', users are not allowed to\nselect 'Broad' type imaging procedures. This parameter may be set\ndifferently for each division within a multi-divisional facility.\n\n
\nThis field controls the listing of lab orders for holders of the ORES key,\nafter the electronic signature has been entered when entering new orders.\nOnly after the order is released to Lab service is the number assigned;\nif physicians want to see the lab order # with the order after entering\nand signing the orders, this parameter must be set to YES. All other\nusers get the listing regardless of what this parameter is set to.\n\n
\nContains the list of CT Scan quick orders for display at the\ntop of the procedures listbox in the GUI ordering dialog.\n\n
\nContains the list of common lab orders for display at the top of the Lab\nTests listbox in the GUI ordering dialog.\n\n
\nContains the list of common consult orders for display at the top of the\nConsult Service listbox in the GUI ordering dialog.\n\n
\nContains the list of common procedure orders for display at the top of the\nProcedures listbox in the GUI ordering dialog.\n\n
\nContains the list of common radiology orders for display at the top of the\nprocedures listbox in the GUI ordering dialog.\n\n
\nThis parameter allows a user to create their own aliases for quick orders.\n\n
\nContains the list of Nuclear Med quick orders for display at the\ntop of the procedures listbox in the GUI ordering dialog.\n\n
\nContains the list of Ultrasound quick orders for display at the\ntop of the procedures listbox in the GUI ordering dialog.\n\n
\nDESCRIPTION: This is a Radiology/Nuclear Medicine division parameter\nautomatic attempt fails.\n \nIf there is more than one Imaging Location for the current imaging type\n(examples of imaging types selectable when ordering imaging procedures are\nNuclear Med, Ultrasound, General Radiology, etc.) the automatic attempt\nwill fail and the prompt will appear. If there is only one possible\nImaging Location for the current imaging type, the system will\nautomatically default to that location. This parameter may be set\ndifferently for each division within a multi-divisional facility.\ncontrolling whether the ordering clinician is prompted for an Imaging\nLocation via the 'SUBMIT REQUEST TO' prompt (1 = user should be prompted,\n0 = user should not be prompted). The Imaging Location entered determines\nwhere the Imaging Request form will print (IRM can assign each Imaging\nLocation in the Radiology/Nuclear Medicine package a request printer). If\nthis parameter is set to 0, the Imaging Request form will not be printed.\nIf this parameter is set to 1, the system will first attempt to\nautomatically determine the Imaging Location, then prompt the user if the\n\n
\nContains the list of MRI quick orders for display at the\ntop of the procedures listbox in the GUI ordering dialog.\n\n
\nContains the list of Cardiology (Nuc Med) quick orders for display at the\ntop of the procedures listbox in the GUI ordering dialog.\n\n
\nContains the list of Vascular Lab quick orders for display at the\ntop of the procedures listbox in the GUI ordering dialog.\n\n
\nContains the list of Angio/Neuro quick orders for display at the\ntop of the procedures listbox in the GUI ordering dialog.\n\n
\nContains the list of Mammography quick orders for display at the\ntop of the procedures listbox in the GUI ordering dialog.\n\n
\nThis parameter controls whether each cover sheet section is loaded in the\nforeground or background.\n\n
\nThis parameter disables writing orders and taking actions on orders in the GUI.\n\n
\nSpecifies a date range (in days) for Meds tab display that dictates the \nORDERS parameter accordingly.\nlength of time orders are displayed. The parameter provides strings of \ndelimited ("; ) pieces, the first two of which are always a relative date \nrange. Users can determine the date range of medications that display on \nthe Medications tab through the Tools|Options pull-down menu in CPRS.\n \nThis parameter functions independently of display settings for the \nOrders tab. If you need to alter the display range for expired \nmedication orders on the Orders tab, please adjust the ORWOR EXPIRED \n\n\nContains the list of common inpatient meds for display at the top of the\nMeds listbox in the GUI ordering dialog.\n\n
\nThis defines the default action presented to ORELSE key holders when\nsigning and/or releasing orders; if no value is entered, then 'Release\nw/o Signature' will be used.\n\n
\nThis will be the default value for Pickup in the Outpatient Medications\nGUI ordering dialog.\n\n
\nThis value overrides the user's DTIME only in the case of the CPRS chart,\nWindows version (CPRSChart.exe).\n\n
\nThe number of hours to delay triggering an unverified medication order\nnotification/alert. The maximum number of hours is 10,000.\n\n
\nThe number of hours to delay triggering an unverified order\nnotification/alert. This parameter is used for all types of orders\n(including medication.) The maximum number of hours is 10,000.\n\n
\nThis parameter determines the default action to be presented at the end of\nthe Review New Orders screen; the action 'Next Screen' will be used until\nthe last screen of orders, if there are more than one. If there is no\naction specified here, then 'Sign All Orders' will be used.\n\n
\nThe number of medications used to determine polypharmacy. If the patient\nis taking more than the number of meds indicated by this parameter's\nvalue, polypharmacy exists. This parameter is used by the order check\nPolypharmacy. This parameter accepts values from 0 to 100. \n\n
\nThe number of days to look back in time for patient's most recent\ncreatinine. This value is used in the Glucophage - Lab Results order\ncheck.\n\n
\nA value of YES in this parameter will print a condensed version of\nthe order summary. The report will be continuous from one patient to\nthe next, printing multiple patients on a page, if there is room.\n \nA value of NO will put a page break between patient reports.\n\n
\nContains the list of common imaging orders for display at the top of the\nprocedures listbox in the GUI ordering dialog.\n\n
\nUsed by the M Server and/or Application GUI Server administrator to \nflag all client BCMA processes to stop.\n\n
\nDefault number of hours after NOW that the VDL will display when \ninitially displayed.\n\n
\nDetermines wheter initial Due List View contains continuous \nmedications.\n\n
\nDetermines wether initial Due List View contains PRN medications.\n\n
\nDetermines wether initial Due List View contains One-Time\nmedications.\n\n
\nListing of division specific reasons why a meication is given PRN. Up \nto 100 reasons are allowed.\n\n
\nContains the list of common diet orders for display at the top of the Diet\nComponents listbox in the GUI ordering dialog.\n\n
\nListing of division specific reasons why a medication is held. Up \nto 100 reasons are allowed.\n\n
\nMailgroup to notify when an order is unable to be validated and placed \non the Due List.\n\n
\nDetermines if a user must supply their electronic signature code prior \nto administering any medications.\n\n
\nThis parameter contains the number of minutes before a scheduled \nadministration time is allowed without filing a variance.\n\n
\nThis parameter contains the number of minutes after a scheduled \nadministration time is allowed without filing a variance.\n\n
\nThe number of minutes allowed to elapse between PRN administration and \nentry of PRN Effectiveness.\n\n
\nName of an HFS directory that all BCMA processes will be able to \naccess through ^%ZISH for printing documents.\n\n
\nName of an HFS directory that all BCMA processes will be able to \naccess through ^%ZISH for printing documents.\n\n
\nMailgroup to notify when an unexplained error occurs with the \nsoftware.\n\n
\nMailgroup to notify when a missing dose is requested.\n\n
\nContains the list of common tubefeedingdiet orders for display at the top\nof the Tubefeeding Products listbox in the GUI ordering dialog.\n\n
\nListing of division specific reasons why a medication is refused. Up \nto 100 reasons are allowed.\n\n
\nDetermines if this Division will allow multiple administrations against an\nOn-Call order.\n\n
\nDevice to print to when a missing dose is requested for an Inpatient \nMedications Order.\n\n
\nDetermines wether initial Due List View contains IV Medications.\n\n
\nDetermines wether initial Due List View contains Unit Dose\nmedications.\n\n
\nUsed to flag wether or not to print the blank order requests at the \nbottom of the printed DUE LIST.\n\n
\nDefault device the user uses for printing BCMA reports.\n\n
\nUsed by the client at application startup to ensure that the client \nclock is within a predetermined number of minutes of the server time \nbefore allowing the client to proceed.\n\n
\nListing of division specific injection sites for a medication.\nUp to 100 sites are allowed.\n\n
\nThis parameter is used to identify a menu in the ORDER DIALOG file that\nwill be used as the list of items that may be selected in the Write Orders\nlistbox of the CPRS GUI.\n\n
\nContains the integer value of the last sorted column on the Virtual \nDue List.\n\n
\nContains the list of common IV Fluid orders for display at the top of the\nIV Fluids listbox in the GUI ordering dialog.\n\n
\nThis value is the number of seconds used for the countdown when the\ntimeout notification window appears.\n\n
\nShould spell/grammar checks be enabled in the GUI (1=yes,0=no)\n\n
\nThis parameter defines the BCMA Backup Logical Links that may be \nassociated with a division when there are one or more\ndivisions at a site.\n\n
\nThis parameter is used to store the application:version(s) that are \ncompatible with the current server version of ANRV Patient Reviews. \nInstance format of APPLICATION:VERSION (example: ANRV.EXE:0.0.0.0).\n\n
\nThis parameter controls if the XUSC1 client code records debug info into\nthe ^TMP global.\n\n
\nThis will store the number of hours for the PRN Documentation Timeframe on the BCMA Site Parameters screen.\n\n
\nDetermines wether initial Due List View contains On Call\nmedications.\n\n
\nThis parameter is used by the BCMA Backup system to route messages to a \nhas no logical links associated with it.\n"default" group of HL7 Logical Links that are associated with the BCMA\npackage rather than individual divisions. When the default group is \ndefined all messages will be routed to this group rather than using \ndivision-based groupings under the following conditions:\n \n1. If a call is made to the api, GET^ALPBPARM, and the division parameter \nis not present or null.\n2. If a call is made to the api, GET^ALPBPARM, and the division specified \n\n
\nThis parameter is used by the BCMA Backup system to activate the \nContingency software. If the value is set to NO then no HL7 messages will \nbe sent to the Workstation. This does not affect the workstation \ninitialization option.\n\n
\nThe BCMA Backup Contingency software uses this parameter. During the \nWorkstation initialization process this tell the process how many days of \nhistoric Inpatient Medication Orders to capture. It is based off the fact \nthe order was active during that time.\n\n
\nThe BCMA Backup Contingency software uses this parameter. During the \nWorkstation initialization process this tell the process how many days of \nhistoric Med Log entries of Inpatient Medication Orders to capture.\n\n
\nThis parameter is multi-instance. The instance value contains the name \nBOTTOM MARGIN 0.5\nRIGHT MARGIN 0.25\nFOOTER FONT NAME Courier New\nFOOTER FONT SIZE 10\nFOOTER FONT STYLE fsRegular (fsRegular; fsBold; fsItalic)\nFOOTER TEXT LINES 0\nHEADER FONT NAME Courier New\nHEADER FONT SIZE 10\nHEADER FONT STYLE fsRegular (fsRegular; fsBold; fsItalic)\nHEADER TEXT LINES 5 (Maximum 5 header lines)\nof the page setup attribute that the DRM GUI is expecting.\nPAGE FONT NAME Courier New\nPAGE FONT SIZE 10\nPAGE FONT STYLE fsRegular (fsRegular; fsBold; fsItalic)\nPAGE ORIENT poPortrait (poPortrait; poLandscape)\nPRINT PAGE NUMBER 1 (1=Yes; 0=No)\nPAGE NUMBER HORZ pnCenter (pnLeft; pnCenter; pnRight)\nPAGE NUMBER VERT pnBottom (pnTop; pnBottom)\n \nAs of 7/14/2003 - these are the allowable system defaults:\n \nInstance Value\n-------------------- -----------------------------------------------\nTOP MARGIN 0.5\nLEFT MARGIN 0.25\n\n
\nThis parameter is multi-instance for the purpose of retrieving all the \n csCompanyName free text Sys,Pkg,User\n csDebugMode set of codes (y/n) Sys,Pkg,User\n csDefaultMode soc (y/n) Sys,Pkg,User\n csDefaultPrinter free text Pkg,User\n csDefaultToPrimary soc (y/n) Sys,Pkg\n csDoctorName soc (y/n) Sys,Pkg,User\n csDragonEnabled soc(y/n) Sys\n csExamSequence free text (15:19) Sys,Pkg,User\n csExcessPocket numeric (0:15) Sys,Pkg,User\n csExcessPocketColor numeric (0-9,999,999,999) Sys,Pkg,User\ndefault values for all the CVision parameters.\n csFGMFromGumLine soc (y/n) Sys,Pkg,User\n csFGMWarning free text (0:80) Sys,Pkg,User\n csFurcationWarning numeric (1:4) Sys,Pkg,User\n csMGJWarning numeric (1:10) Sys,Pkg,User\n csMobilityWarning numeric Sys,Pkg,User\n can only be .5,1,1.5,2,2.5\n csNormPocketColor numeric (0-9,999,999,999) Sys,Pkg,User\n csPocketWarning numeric (1:15) Sys,Pkg,User\n csPrintChart soc (y/n) Sys,Pkg,User\n csPrintPatNotes soc (y/n) Sys,Pkg,User\n \n csPrintToothNotes soc (y/n) Sys,Pkg,User\n csPrintTransactions soc (y/n) Sys,Pkg,User\n csShowMGJTrace soc (y/n) Sys,Pkg,User\n csSpeechFeedbackEn soc (y/n) Sys\n csTransDisplay numeric (0-9,999,999,999) Sys,Pkg,User\n csWarnDuplicateTrans soc (y/n) Sys,Pkg,User\n csShowSeqOnStart soc (y/n) Sys,Pkg,User\n csSeqFormSettings free text (0:100) Sys,Pkg,User\nSet of codes type is used instead of the yes/no type as the treatment \nplanning software expects NO=0 and YES=-1.\n \n Instance name Value Entitiy\n ---------------------- -------------------------- ------------\n csApplicationName free text Sys\n\n
\nThis parameter contains the values for the various date range settings \nThe instance has a format of <package> NUMBER OF DAYS\n <package> MAX\n where <package> : = DENT\n LAB\n NOTES\n VISIT\nwithin DRM. The personal preference setup window allows the user to set \ntwo values:\n Number of days back that data will be retrieved from Today\n Maximum number of records to retrieve\n \nThe instance for this parameter is the name of the package\nThe value is the numeric value for those two mentioned above\n \n\n
\nThis parameter determines whether or not a user has administrator \nprivileges to the DRM package.\n\n
\nThis will control the display of the boilerplate prompt within the DRM GUI\n\n
\nThis free text field will control the default tab that is displayed when \non the encounter page. The value must be a value entered as a \nsubcategory-1 from file 228.\n\n
\nIf set to YES, CPRS GUI will display Windows standard printer selection\ndialog instead of the VistA printer selection dialog.\n \nIf set to NO, the standard VistA printer selection dialog will be\ndisplayed, still allowing selection of a Windows printer, but requiring an\nadditional prompt.\n\n
\nEnter the major tab that the DRM GUI should open up in when launched.\n\n
\nThis parameter will control whether or not the user can run the Excel \nextract option within DRM.\n\n
\nEnter the IP address where the DRM listener is running to receive the \nExcel extract. The value should be in the proper syntax to be used in \nthe M open command.\n\n
\nThis is the port number that the DRM 'TCP/IP' listener is listening on.\n\n
\nThe DRM GUI allowed the user to lookup NEW PERSON information similar to \nthe Kernel's Toolbox option. It also allowed the user to edit certain \nfields in the NEW PERSON file for their own record. This parameter will \nallow the site to configure which of these options are available.\n\n
\nThe DRM GUI application has need to occasionally create temporary files. \nThis parameter stores the location for those temporary files. The \ndefault location is c:\\temp\\. The value must be a valid Windows NT path \ndesignation.\n\n
\nThis contains a quick list of cpt codes for an user.\n\n
\nThis contains user's quick list of most commonly used diagnosis codes.\n\n
\nTest filing of large strings (e.g., XML streams) as parameter values.\n\n
\nThis parameter determines who is allowed access to patient data at\nremote sites. The values for this parameter can be controlled down to the\nUSER entity.\n\n
\nThis is a test parameter for integration testing of the HealtheVet \nDesktop Configurator module. It has no use in production applications.\n\n
\nThis is the perspective to which the HealtheVet Desktop should open by \ndefault.\n\n
\nThis identifies the option that lists the perspectives that are initally shown in the HealtheVet Desktop.\n\n
\nThis parameter is used to store a Boolean flag indicating whether or not \nthe user has been given the opportunity to review the notice with respect \nto Section 508 of the Americans with Disabilities Act.\n\n
\nEvents with dates as recent as this date will be added to the Dashboard.\nEvents will be added with dates between MIN DATE and MAX DATE.\n\n
\nEvents with dates as early as this date will be added to the Dashboard.\nEvents will be added with dates between MIN DATE and MAX DATE.\n\n
\nThis parameter allows the Dashboard to save lists of Patient Selection\nsources.\n\n
\nResults with dates as recent as this date will be added to the Dashboard.\nResults will be added with dates between MIN DATE and MAX DATE.\n\n
\nResults with dates as early as this date will be added to the Dashboard.\nResults will be added with dates between MIN DATE and MAX DATE.\n\n
\nUnverified orders with dates as recent as this date will be added to the\nDashboard. Orders will be added with dates between MIN DATE and MAX DATE.\n\n
\nThis is the maximum number of days that 'Lab Collect' orders may be\nplaced. The number may be specific to each hospital location.\n\n
\nUnverified orders with dates as early as this date will be added to the\nDashboard. Orders will be added with dates between MIN DATE and MAX DATE.\n\n
\nText orders with dates as recent as this date will be added to the\nDashboard. Orders will be added with dates between MIN DATE and MAX DATE.\n\n
\nText orders with dates as early as this date will be added to the\nDashboard. Orders will be added with dates between MIN DATE and MAX DATE.\n\n
\nVitals with dates as recent as this date will be added to the Dashboard.\nVitals will be added with dates between MIN DATE and MAX DATE.\n\n
\nVitals with dates as early as this date will be added to the Dashboard.\nVitals will be added with dates between MIN DATE and MAX DATE.\n\n
\nThis is the date that users are expected to begin using the Care Management\napplication; after this date, results data will be accumulated and tracked\nin the Order Acknowledgment file #102.4 for designated users.\n\n
\nThis parameter is used to store a users default parameter settings. Each \nsetting is defined on the client.\n\n
\nThis parameter is used to store the CRC values for the most recent\nversions of executable and libraries. Use the Tools menu on the CPManager\nprogram to calculate the needed CRC Values of the current versions.\n\n
\nThis parameter contains the web address for the Clinical Procedures home\npage. This can be modified to a local address in the event that the pages\nare downloaded to be displayed from a local server location.\n\n
\nThe number of days to keep data from the auto-instruments after\nthe data has been associated with a Clinical Procedures report.\n\n
\nThis parameter controls access to the Clinical Procedures package.\n\n
\nContains the directory specification for the Kernel OPEN^%ZISH call. This\ndirectory should be accessible for read/write operations by all CP users.\n\n
\nThis parameter is used to store the application:versions that are compatible\nwith the current server version of Clinical Procedures. Instance format\nof APPLICATION:VERSION (example: CPMANAGER.EXE:0.0.0.0).\n\n
\nThis parameter contains the name of a network server, share, and path\n(UNC) to a location where Clinical Procedures can put files for pick-up by\nthe Imaging background processor for archiving.\n\n
\nThis parameter stores a list of valid file types and the associated\nextensions of these files.\n\n
\nSet this value to 'Yes' to prevent the client application from verifying\nits CRC Value at startup.\n\n
\nThis parameter contains a message to display to the users when the Clinical\nProcedures application is offline.\n\n
\nSet this value to Yes to allow users of CPUser.exe to attach documents to \nthe transaction that are not created by an instrument.\n\n
\nThis parameter contains the name of a personal quick order list for a\nspecific display group.\n\n
\nThis parameter determines if clerks (i.e. users holding the OREMAS key)\nare allowed to act on non-VA med orders. Enter YES to permit a clerk to\nenter new or DC non-VA med orders and send them to Pharmacy for reports \nand order checks. To prohibit clerks from handling non-VA med orders\nentirely, select NO.\n\n
\nThis parameter lists the reasons and statements for ordering/documenting \na non-VA medication. Non-VA meds include herbals, OTCs (over-the-counter \nmedications) and prescriptions not obtained at VA pharmacies or from VA\nmail delivery services.\n\n
\nNumber of hours back in time to search for expired orders. Also used to \ndetermine number of hours back in time to search for expired med orders if\nthe follow-up action for the Expiring Meds alert does not find expiring\nmeds.\nThis parameter does NOT affect Meds tab display. To alter Meds tab \ndisplay, please adjust the ORCH CONTEXT MEDS parameter accordingly.\n\n
\nValue indicates if the notification/alert can be deleted without \nprocessing. A "yes" value indicates the notification/alert can be deleted\nwithout processing. In the CPRS GUI a"yes" value signifies a selected\nalert can be deleted when the Remove button is clicked. If a\nnotification/alert has a blank value or a "no" value, the\nnotification/alert cannot be deleted without processing.\n\n
\nThis is the default file folder for saving history extract (Excel) data.\n\n
\nThis parameter defines the number of days that a VIC Request with a Card\nPrint Release Status of "H"old is allowed to remain pending before being \ncancelled.\n\n
\nThis value is used by the VIC Background Processing [DGQE BACKGROUND \nPROCESSING] option to determine how many days to retain completed VIC \nrequest transactions in the VIC REQUEST (#39.6) and VIC HL7 TRANSMISSION\nLOG (#39.7) files.\n\n
\nThis parameter controls the DRM user interface to not allow transactions \nto be filed to DAS (file 221). The default date will be 10/31/2004, but \nif the HL7 interface, or the AAC or VA-DSS determines that they are not \nready to turn off DAS, we can change this date.\n\n
\nThis parameter controls whether nurses are allowed to verify orders in the\nGUI. The default value is 0, which allows nurses to verify orders only\nwhen ordering is enabled. To allow nurses to verify orders when ordering\nis disabled, set the value to 1. To never allow the verify actions, set\nthe value to 2.\n \nThis parameter applies to the "Verify" and "Chart Review" on the Actions\nmenu on the Order tab.\n\n
\nThis is the word wrap width for note windows in DRM*Plus. The default \nSYS value is 74\n\n
\nThis parameter is used by the new Dental Treatment Planning software to \ndefault the correct tab to start the user on.\n\n
\nThese parameters determine how the user wants to configure the data \nNEXT APPOINTMENT 1;0;0;0\nNOTE BOILERPLATE 1;0;0;0\nPERIODONTAL EXAM 1;0;0;0\nPLANNED ITEMS 1;0;1;0\nPSR EXAM 1;0;1;0\nTEXT MARKER 1;0;0;0\nTOOTH NOTES 1;0;1;1\nADVERSE EVENTS 1;0;1;0\n \nPosition 1 is whether to include the instance type in the Note,\nobjects in the progress note. 0=No, 1=Yes.\nPosition 2 is whether to include Added items of that type\nPosition 3 is whether to include Modified items of that type\nPosition 4 is whether to include Deleted items of that type\n \nThe default System instance/values are:\nCODE BOILERPLATE 0;0;0;0\nCOMPLETED ITEMS 1;0;0;1\nDENTAL ALERTS 0;0;0;0\nDIAGNOSTIC FINDINGS 1;0;1;0\nHEADNECK FINDINGS 1;0;1;1\n\n
\nThis parameter contains word processing templates that are stuffed into \nthe progress note for the associated ADA codes in the Dental transaction.\n\n
\nThis parameter contains the sequence that the various data type \nPLANNED ITEMS\nCODE BOILERPLATE\nCOMPLETED ITEMS\nNEXT APPOINTMENT\ninformation is put into the progress note. The Value information is the \nINSTANCE value from the DENTV TP NOTE OBJECTS parameter:\n \nHEADNECK FINDINGS\nDIAGNOSTIC FINDINGS\nPSR EXAM\nPERIODONTAL EXAM\nTOOTH NOTES\n\n
\nThis parameter saves the user's preference for adding Dx codes\nto Planned Treatment items.\n\n
\nDetermines the default value for the "Include Comments" check box on the \nreport configuration dialog box of the BCMA GUI Client.\n\n
\nThis will store the number of days the Medication History Report date \nrange will default to in the Report Configuration Dialog box of the BCMA \nGUI Client.\n\n
\nSelect whether the user wants comments associated with previous results to\ndisplay with those results during lab verification process.\n\n
\nThis parameter controls if the RPC Broker records log data \nin ^TMP("XWBDBUG",$J).\n\n\nStatus of Billing Awareness Utilization\n\n
\nThis parameter enables the entry of Billing Awareness data in the sign order CPRS window if value is set to 1. Otherwise the Clinician will not be required to enter Billing Awareness data if value is set to 0.\n\n
\nReturns the relative date to start listing visits for a patient on the \nCover Sheet. For example, 'T-90' will list visits beginning 90 days \nbefore today.\n\n
\nReturns the relative date to stop listing visits for a patient on the \nCover Sheet. For example, 'T+2' will list visits ending two days from \ntoday.\n\n
\nReturns the relative number of days before Today to begin listing \nappointments (0=Today, 1=Today-1 Day, etc.).\n\n
\nReturns the relative number of days from Today to stop listing \nappointments (0=Today, 1=Today+1 Day, etc.).\n\n
\nParameter should be "yes" if site is using the robot RX.\n\n
\nNumber of days from Today when warning is given to user upon selection of\na future appointment for Encounters.\n\n
\nThis parameter is use for a site to active the print now option.\n\n
\nThis parameter determines whether DRM objects are the default display \nwithin DRM Plus.\n\n
\nThis parameter contains the DRM or DRM Plus version that the user has run \nlast. If a new version is detected, then a message will alert the user \nthat there may be changes to their system and where to get further \ninformation.\n\n
\nThis parameter controls which users (other than Admin users) can edit a \npatient's Primary and Secondary Provider settings.\n\n
\nThis parameter identifies which COTS product is being utilized for the \ninventory management system of the site. The current values are:\n \n0 NONE - means no COTS product is being used and the inventory \nmanagement system in use is GIP/IFCAP\n1 DYNAMED - means the DynaMed product is being used\n\n
\nUsed by $$MEDEXP^DGMTSCU4 to derive gross & adjusted medical expense \nvalues.\n\n
\nUsed by $$MEDEXP^DGMTSCU4 to derive gross & adjusted medical expense \nvalues.\n\n
\nUsed by $$MEDEXP^DGMTSCU4 to derive gross & adjusted medical expense \nvalues.\n\n
\nThis parameter may be used to disable the use of windows messaging to\nnotify other applications of CPRS events. Normally, this parameter should\nbe set to 'Yes'. If other applications do not respond appropriately to\nbroadcast messages, this parameter may be set to 'No' to debug these\napplications.\n\n
\nThis parameter will prevent orders from being placed on hold.\n\n
\nUsed by $$MEDEXP^DGMTSCU4 to derive gross & adjusted medical expense \nvalues.\n\n
\nThis parameter is used to set a switch if CIDC related questions should\nbut enhances the limits of the questions for the GUI.\nbe asked. Setting this parameter will effect multiple packages and users,\ntherefore great care should be cautioned when editing this parameter.\nValues are: 0 = Don't ask CIDC related questions for anyone\n 1 = Ask CIDC related questions only if the patient has active\n billable insurance.\n 2 = Ask CIDC questions for all patients.\n \nThis does not over-ride the CPRS switches for how the GUI asks questions,\n\n
\nThis parameter is used to trigger a notification/alert when a specific\nAttending Physician.\nT (Patient Care Teams): deliver notification to the patient's OE/RR Teams \n(personal patient and team lists are evaluated for potential recipients) \nand to devices on an OE/RR team.\nO (Ordering Provider): deliver notification to the provider\nwho placed the order which trigger the notification.\nM (PCMM Team): deliver notification to users/providers linked to the\npatient via PCMM Team Position assignments.\nE (Entering User): deliver notification to the user/provider who \nentered the order's most recent activity.\norderable item is ordered for an inpatient. The notification is \nR (PCMM Primary Care Practitioner): deliver notification to the\npatient's PCMM Primary Care Practitioner.\nS (PCMM Associate Provider): deliver notification to the patient's PCMM\nAssociate Provider.\nC (PCMM Mental Health Treatment Coordinator): deliver notification to the\npatient's PCMM Mental Health Treatment Coordinator.\ndelivered to a user based upon that user's relationship to the inpatient \nas defined by the following codes. Orderable Items can be set up with any\nor all of the following codes:\n \nP (Primary Provider): deliver notification to the patient's Primary\nProvider. \nA (Attending Physician): deliver notification to the patient's \n\n
\nThis parameter is used to trigger a notification/alert when a specific\nAttending Physician.\nT (Patient Care Teams): deliver notification to the patient's OE/RR Teams \n(personal patient and team lists are evaluated for potential recipients) \nand to devices on an OE/RR team.\nO (Ordering Provider): deliver notification to the provider\nwho placed the order which trigger the notification.\nM (PCMM Team): deliver notification to users/providers linked to the\npatient via PCMM Team Position assignments.\nE (Entering User): deliver notification to the user/provider who \nentered the order's most recent activity.\norderable item is ordered for an outpatient. The notification is \nR (PCMM Primary Care Practitioner): deliver notification to the\npatient's PCMM Primary Care Practitioner.\nS (PCMM Associate Provider): deliver notification to the patient's PCMM\nAssociate Provider.\nC (PCMM Mental Health Treatment Coordinator): deliver notification to the\npatient's PCMM Mental Health Treatment Coordinator.\ndelivered to a user based upon that user's relationship to the outpatient \nas defined by the following codes. Orderable Items can be set up with any\nor all of the following codes:\n \nP (Primary Provider): deliver notification to the patient's Primary\nProvider. \nA (Attending Physician): deliver notification to the patient's \n\n
\nThis parameter is used to trigger a notification/alert when a specific\nProvider. \nA (Attending Physician): deliver notification to the patient's Attending\nPhysician.\nT (Patient Care Teams): deliver notification to the patient's OE/RR Teams \n(personal patient and team lists are evaluated for potential recipients) \nand to devices on an OE/RR team.\nO (Ordering Provider): deliver notification to the provider who placed the\norder which trigger the notification.\nM (PCMM Team): deliver notification to users/providers linked to the\npatient via PCMM Team Position assignments.\norderable item is resulted for an inpatient. Results only apply to orders\nE (Entering User): deliver notification to the user/provider who \nentered the order's most recent activity.\nR (PCMM Primary Care Practitioner): deliver notification to the\npatient's PCMM Primary Care Practitioner.\nS (PCMM Associate Provider): deliver notification to the patient's PCMM\nAssociate Provider.\nC (PCMM Mental Health Treatment Coordinator): deliver notification to the\npatient's PCMM Mental Health Treatment Coordinator.\nwhich can be resulted (lab, imaging, consults.)\n \nThe notification is delivered to a user based upon that user's\nrelationship to the inpatient as defined by the following codes.\nOrderable Items can be set up with any or all of the following codes:\n \nP (Primary Provider): deliver notification to the patient's Primary\n\n
\nThis parameter is used to trigger a notification/alert when a specific\nProvider. \nA (Attending Physician): deliver notification to the patient's Attending\nPhysician.\nT (Patient Care Teams): deliver notification to the patient's OE/RR Teams \n(personal patient and team lists are evaluated for potential recipients) \nand to devices on an OE/RR team.\nO (Ordering Provider): deliver notification to the provider who placed \nthe order which trigger the notification.\nM (PCMM Team): deliver notification to users/providers linked to the\npatient via PCMM Team Position assignments.\norderable item is resulted for an outpatient. Results only apply to \nE (Entering User): deliver notification to the user/provider who \nentered the order's most recent activity.\nR (PCMM Primary Care Practitioner): deliver notification to the\npatient's PCMM Primary Care Practitioner.\nS (PCMM Associate Provider): deliver notification to the patient's PCMM\nAssociate Provider.\nC (PCMM Mental Health Treatment Coordinator): deliver notification to the \npatient's PCMM Mental Health Treatment Coordinator.\norders which can be resulted (lab, imaging, consults.)\n \nThe notification is delivered to a user based upon that user's\nrelationship to the outpatient as defined by the following codes.\nAn Orderable Item can be set up with any or all of the following codes:\n \nP (Primary Provider): deliver notification to the patient's Primary\n\n
\nThis parameter is used to trigger a notification/alert when a specific\nAttending Physician.\nT (Patient Care Teams): deliver notification to the patient's OE/RR Teams \n(personal patient and team lists are evaluated for potential recipients) \nand to devices on an OE/RR team. \nO (Ordering Provider): deliver notification to the provider\nwho placed the order which trigger the notification.\nM (PCMM Team): deliver notification to users/providers linked to the\npatient via PCMM Team Position assignments.\nE (Entering User): deliver notification to the user/provider who \nentered the order's most recent activity.\norderable item is expiring for an inpatient. The notification is \nR (PCMM Primary Care Practitioner): deliver notification to the\npatient's PCMM Primary Care Practitioner.\nS (PCMM Associate Provider): deliver notification to the patient's PCMM\nAssociate Provider.\nC (PCMM Mental Health Treatment Coordinator): deliver notification to the\npatient's PCMM Mental Health Treatment Coordinator.\ndelivered to a user based upon that user's relationship to the inpatient \nas defined by the following codes. Orderable Items can be set up with any\nor all of the following codes:\n \nP (Primary Provider): deliver notification to the patient's Primary\nProvider. \nA (Attending Physician): deliver notification to the patient's \n\n
\nThis parameter is used to trigger a notification/alert when a specific\nAttending Physician.\nT (Patient Care Teams): deliver notification to the patient's OE/RR Teams \n(personal patient and team lists are evaluated for potential recipients) \nand to devices on an OE/RR team.\nO (Ordering Provider): deliver notification to the provider\nwho placed the order which trigger the notification.\nM (PCMM Team): deliver notification to users/providers linked to the\npatient via PCMM Team Position assignments.\nE (Entering User): deliver notification to the user/provider who \nentered the order's most recent activity.\norderable item is expiring for an outpatient. The notification is \nR (PCMM Primary Care Practitioner): deliver notification to the\npatient's PCMM Primary Care Practitioner.\nS (PCMM Associate Provider): deliver notification to the patient's PCMM\nAssociate Provider.\nC (PCMM Mental Health Treatment Coordinator): deliver notification to the\npatient's PCMM Mental Health Treatment Coordinator.\ndelivered to a user based upon that user's relationship to the outpatient\nas defined by the following codes. Orderable Items can be set up with\nany or all of the following codes:\n \nP (Primary Provider): deliver notification to the patient's Primary\nProvider. \nA (Attending Physician): deliver notification to the patient's \n\n
\nThis parameter is multi-instance for the purpose of knowing which \niMedConsent soc Y/N System\niMedConsentLoc server location System\nancillary products can be launched from within DRM Plus. It enables, or \nhides, the appropriate buttons for the user. For example, DRM Plus can \nlaunch MiPACS to view dental radiographs, and iMedConsent to get required \nconsent forms.\n \nInstance name Value Entity\n---------------- --------- ----------\nMiPACS soc Y/N System\n\n
\nThese values display for user selection of dental alerts for a patient.\n\n
\nThis parameter is queried by code which activates upon termination of a\nuser. It the parameter is set to 'Y' then whenever a user is terminated,\nhis/her non-shared TIU templates will be deleted. The default setting is\n'N.'\n\n
\nThis parameter contains the default location for the user. The location \nwill display when a user creates a new visit in DRM Plus.\n\n
\nThis parameter holds the application passcode for the CCOW vault.\n\n
\nThis parameter will be used to indicate the date range for the Day of \nStock on Hand report associated with PRC*5.1*83 (CLRS).\n\n
\nThis parameter will be used to indicate the number of days to be used for \nthe inactive range for the Stock Status Report by PRC*5.1*83 (CLRS).\n\n
\nThis parameter will be used to indicate the number of days to be used in \nconnection with the Stock on Hand Report when that report evaluates stock \nlevels retained greater than a certain given period. This parameter is \nassociated with PRC*5.1*83 (CLRS).\n\n
\nThis parameter will be used to indicate the destination directory for \nextracts taken in connection with PRC*5.1*83 (CLRS). These directories \nwould be at the VMS, Windows, Linux, or other operating system level.\n\n
\nThis parameter is used to store the DLL versions that are compatible with\nthe current server version of the Vitals/Measurements application. The\nInstance format is DLL:VERSION.\n \nExample: GMV_VITALSVIEWENTER.DLL:v. 07/21/05 10:34\n\n
\nEnabling this parameter will allow for the transmission of the privacy \nindicator to be included in HL7 messages generated by the Registration \napplication in the PV2 segment. The privacy indicator allows patient to \nopt-out form being listed from facility directories. By including this \ninformation in the HL7 message the information can be communicated to COTS\napplications doing patient directories.\n\n
\nDirection for sorting notifications when displayed in the CPRS GUI. \nDirections include: Forward and Reverse.\n\n
\nThe number of days to archive a notification for a site. If not\nindicated, the default period of 30 days is used. The maximum number of\ndays is 100,000 or about 220 years. This value is passed to the Kernel\nAlert Utility where the actual archiving and deletion of\nalerts/notifications occurs.\n\n
\nUsed as preference of graph default styles and sources.\n5 - min graph height\n6 - (not used)\n7 - max selection\n8 - max selection limit (may be set to at system level to limit \n number of items that users may select for graphing default is 1000)\n \nFiles:\nAdmissions - 405, Allergies - 120.8, Anatomic Pathology - 63AP,\nBlood Bank - 63BB, Exams - 9000010.13, Health Factors - 9000010.23,\nImmunizations - 9000010.11, Lab Tests - 63, Medication, BCMA - 53.79,\nDeletion of this value at the Package level will disable graphing.\nMedication, Inpatient - 55, Medication, Non-VA - 55NVA, \nMedication, Outpatient - 52, Medicine - 690, Mental Health - 601.2,\nMicrobiology - 63MI, Notes - 8925, Orders - 100,\nPatient Education - 9000010.16, Problems - 9000011, Procedures - 9000010.18,\nPurpose of Visit - 9000010.07, Radiology Exams - 70, Registration, DX - 45DX,\nRegistration, OP/Proc - 45OP, Skin Tests - 9000010.12, Surgery - 130,\nTreatments - 9000010.15, Visits - 9000010, Vitals - 120.5\nAlso (for grouping):\nDrug Class - 50.605, Reminder Taxonomy - 811.2\n \nUser settings and public default should use the Graph Settings dialog to\nOptions: \nA - 3D, B - Clear Background, C - Dates, D - Gradient, E - Hints, \nF - Legend, G - Lines, H - Sort by Type, I - Stay on Top, J - Values,\nK - Zoom, Horizontal, L - Zoom, Vertical , M - Fixed Date Range\nchange these values. The structure of this parameter is a | delimited \nstring where the pieces are:\n1 - file listing delimited by ; \n2 - options where the corresponding letter activates that feature\n3 - sort column number (used internally)\n4 - max graphs\n\n
\nThis parameter is used internally to store graph views.\nGraph views are edited using the Define Views dialog.\n\n
\nIndicates if a non-CPRS (non-OERR) alert can be deleted without\nshould only enter that portion of the alert ID which is consistent for all\nalerts of this type. For example, a NOIS alert's ID might actually look\nlike FSC-M,275546. Entering the entire alert ID in this parameter will\nonly allow removal of this specific alert. However if the parameter value\nis FSC, all NOIS alerts can be removed. Other examples of non-OR alert\nIDs include:\n \nNO-ID;17;3040628.131502 [Taskman alert] - use NO-ID in parameter\nTIUERR,3423,1;1450;3040518.125801 [TIU error alert] - use TIUERR\nTIU28907;17;3040720.134827 [TIU alert] - use TIU* in parameter\nprocessing. Enter the alert identifier (or a portion of the alert\n \n*Using TIU will also enable Removing TIUERR alerts. Use TIUERR if you\nonly want to Remove TIUERR alerts.\nidentifier) for each type of alert you want to be able to remove in the \nCPRS GUI via the Remove button. The alert identifier or XQAID can be\nfound in the ALERT ID field of the ALERT file [#8992]. For this parameter\nuse the first few characters of the ALERT ID. For example, to remove NOIS\nalerts enter FSC. You may enter as many alert identifiers as desired. \nPlease note that most alert IDs include information specific to the\npatient or instance which triggered the alert. For this parameter you\n\n
\nThis parameter will control whether or not a user has access to\nthe entered in error functionality available on the cover sheet\nin CPRS GUI.\n\n
\nParameter to tell CPRS if it needs to perform the PFSS functionality.\n\n
\nThis parameter contains a list of ASU user classes who's members are allowed \nto edit public views and settings for graphs. Users that belong to the user\nclass entered at the SYSTEM level have this authority.\n\n
\nUsed to exclude data types from being used by graphing.\nValue is semicolon delimited list of files to be excluded.\n\n
\nThis parameter is used internally to save positions of graph forms.\n\n
\nSet of codes used to determine how a notification will be deleted at a\nsite. Codes include: I (Individual Recipient): delete the notification\nfor an individual recipient when a) that individual completes the\nfollow-up action on notifications with associated follow-up action, b)\nthat individual reviews notifications without follow-up actions. A (All\nRecipients): delete the notification for all recipients when a) any\nrecipient completes the follow-up action on notifications with follow-up\nactions, b) any recipient reviews notifications without follow-up\nactions.\n\n
\nThis parameter determines if Remote patient queries are done automatically\nfor all sites. The values for this parameter can be controlled down to the\nUSER entity.\n\n
\nThis parameter determines if Remote patient queries are done to the HDR.\nThe values for this parameter can be controlled down to the\nUSER entity.\n\n
\nThis parameter is a numeric value containing the number of patients to be \ndisplayed per page.\n\n
\nThis parameter contains the maximum number of patients returned.\n\n
\nA user holding the DGRR PLU Administrator may choose 3 fields to be\ndisplayed by the Patient Lookup application in the search list.\n\n
\nA user holding the DGRR PLU Administrator may choose 3 fields to be\ndisplayed by the Patient Lookup application in the search list.\n\n
\nA user holding the DGRR PLU Administrator may choose 3 fields to be\ndisplayed by the Patient Lookup application in the search list.\n\n
\nA user holding the DGRR PLU Administrator may choose 3 fields to be\ndisplayed by the Patient Lookup application in the search list.\n\n
\nA user holding the DGRR PLU Administrator may choose 3 fields to be\ndisplayed by the Patient Lookup application in the search list.\n\n
\nThe number of days before a notification is forwarded to a recipient's\nnon-existent, the alert/notification will never be forwarded.\nFor this purpose, the supervisor is identified as the recipient's service/\nsection chief.\nsupervisor. The maximum is 30 days. If not indicated or zero, the\nnotification will not be forwarded. For example, if a notification has a\nvalue of 14 for this parameter, it will be forwarded to the supervisor of\neach recipient who hasn't processed the notification after 14 days.\nDetermination of recipients who have not processed the notification and\nwho their supervisors are is made by the Kernel Alert Utility. It will\nnot be forwarded to supervisors of recipients who have processed the\nalert within 14 days. If the value of this parameter is zero or\n\n
\nA user holding the DGRR PLU Administrator may choose 3 fields to be\ndisplayed by the Patient Lookup application in the search list.\n\n
\nA user holding the DGRR PLU Administrator may choose 3 fields to be\ndisplayed by the Patient Lookup application in the search list.\n\n
\nA user holding the DGRR PLU Administrator security key may set this\nparameter. If enabled, the veteran image will be displayed.\n\n
\nThis is a mapping of NPI ID name to the files that hold the data.\n\n
\nPSB VDL PATCH DAYS -\nCoversheet.\n \nThe value of this parameter should be between 7 and 14.\n \nPSB VDL PATCH DAYS is the parameter which determines the number of days a \npatient's GIVEN medication patch will display on the respective Bar\nCode Medication Administration (BCMA) Virtual Due List (VDL) and BCMA \nCoversheet. If this parameter is equal to the "null" value, a GIVEN \nmedication patch will always display on the respective BCMA VDL and BCMA \n\n
\nThis is a USER SPECIFIC PARAMETER.\n \n 7/3/1/3\n \nThis parameter contains 4 column number used to sort each of the 4 \ndifferent Coversheet Views respectively, delimited by the slash \n(/) \ncharacter. First (Medication Overview), Second (PRN Overview), Third (IV\nOverview), and Forth (Expired/Expiring Orders), are the coversheet views \nin sequence. Each view's columns are numbered from left to right. An \nexample parameter setting is:\n\n
\nUSER specific setting for the BCMA Coversheet's "first view" .\n \nSetting numbers are in units of centimeters. \n \n \n THESE NUMBERS MUST BE WHOLE NUMBERS.\n \nThis parameter contains the width of each column viewed via the Bar Code \nMedication Administration Coversheet's "first view" delimited by the \nslash (/). Each "/"-piece of data is per respective column on the \nCoversheet's "first view", numbered from left to right. An \nexample parameter setting is:\n \n 170/20/100/30/11/22/31/44/50\n\n
\nUSER specific setting for the BCMA Coversheet's "second view".\n \nSetting numbers are in units of centimeters. \n \n \n THESE NUMBERS MUST BE WHOLE NUMBERS.\n \nThis parameter contains the width of each column viewed via the Bar Code \nMedication Administration Coversheet's "second view" delimited by the\nslash (/). Each "/"-piece of data is per respective column on the \nCoversheet's "second view", numbered from left to right. An example \nparameter setting is:\n \n 170/20/100/30/11/22/31/44/50\n\n
\nUSER specific setting for the BCMA Coversheet's "third view".\n 170/20/100/30/11/22/31/44/50\n \nSetting numbers are in units of centimeters. \n \n \n THESE NUMBERS MUST BE WHOLE NUMBERS.\n \n \nThis parameter contains the width of each column viewed via the Bar Code \nMedication Administration Coversheet's "third view" delimited by the\nslash (/). Each "/"-piece of data is per respective column on the \nCoversheet's "third view", numbered from left to right. An example \nparameter setting is:\n \n\n
\nUSER specific setting for the BCMA Coversheet's "forth view".\n \n 170/20/100/30/11/22/31/44/50\n \nSetting numbers are in units of centimeters. \n \n \n THESE NUMBERS MUST BE WHOLE NUMBERS.\n \n \n \nThis parameter contains the width of each column viewed via the Bar Code \nMedication Administration Coversheet's "forth view" delimited by \nthe slash (/). Each "/"-piece of data is per respective column on the \nCoversheet's "forth view", numbered from left to right. An example \nparameter setting is:\n\n
\nThe number of days before a notification is forwarded to a recipient's\nthe alert/notification will never be forwarded. For this purpose, the\nsurrogate(s) are identified as the recipient's MailMan surrogate(s).\nsurrogates. The maximum is 30 days. If not indicated or zero, the\nnotification will not be forwarded. For example, if a notification has a\nvalue of 14 for this parameter, it will be forwarded to the surrogates of\neach recipient who haven't processed the notification after 14 days.\nDetermination of recipients who have not processed the notification and\nwho their surrogates are is made by the Kernel Alert Utility. It will\nnot be forwarded to surrogates of recipients who have processed the alert\nwithin 14 days. If the value of this parameter is zero or non-existent,\n\n
\nThis parameter is the name of the mail group containing persons to get \nelectronic mail messages, when a BCMA administration is filed with a \n"null" value in the Action Status field (#.09).\n\n
\nUsed to determine if the Medicine Package has been converted.\n\n
\nThis field holds the name of the server to send e-mail to when a KIDS HFS \nfile is made.\n\n
\nThis value is used by the Patient Record Flags module to control the \nmaximum number of query attempts that are allowed. \n\n
\nThis parameter determines whether or not a user can edit dental patient \neligibility information on the DRM Plus Cover Page.\n\n
\nThis parameter controls whether or not users may add PCE visit 'on the \nfly' within DRM Plus. If set to yes, then no visits can be created and \nthe user must select an existing PCE visit for the dental encounter.\n\n
\nThis parameter controls whether or not the users see the Potential \nDuplicates screen which attempts to synchronize planned and completed \ncare. If set to yes, then no duplicate processing is done. If not \ndefined, or set to no, (the default) then potential dupes will be shown \nto the user for selection/processing.\n\n
\nThis parameter will store the location of the Clinical Logistics Report \nServer in either IP address or DNS Server name form. An error \nnotification will be sent through MailMan if no value is present in this \nparameter when a transfer to the CLRS is attempted.\n\n
\nThis parameter will hold the name of the Microsoft Outlook mail group \nthat should receive Clinical Logistics Report Server activity \nnotifications. The mail group name must be completely and accurately \nentered for this functionality to operate correctly.\n\n
\nThis parameter enables sites to determine the amount of time data will be \ncached and considered valid for ordering checking before that data would \nneed to be refreshed. The value is in minutes and can be set from 0 to \n9999.\n\n
\nThis parameter is used to trigger a notification/alert when a specific\nalert.)\n \nUsers are linked to a patient if the user is the patient's attending\nphysician, primary inpatient provider, PCMM primary care practitioner,\nPCMM associate provider, user is assigned to a position on the patient's\nPCMM primary care team or user shares an OE/RR team with the patient.\nOE/RR teams are linked to a patient if the patient is on the team. (If a\npatient is on a team that has flagged an orderable item, all users on that\nteam become potential alert recipients.) Devices (printers, etc.) are\nlinked to a patient if the device and patient are on the same OE/RR team.\norderable item is ordered for an inpatient.\n \nIf the value for the orderable item flag is "YES", the entity (user,\nteam, device), flagging the orderable item becomes a potential alert\nrecipient for ALL patients. If the value is "NO", the entity (user,\nteam, device), flagging the orderable item only becomes a potential\nalert recipient if that entity is "linked" to the patient. (If a device\nis added to the potential recipient list, it will always receive the\n\n
\nThe value in this parameter shows if a health data repository exists from \nwhich remote data from other VHA facilities and Department of Defense \nmedical facilities is retrieved. This parameter supports the\nVistAOffice application that can work as a stand-alone application.\n\n
\nThis parameter is a threshold value that holds the minimum number of HDR \nread failures for RDI before RDI will go into a state of "OUTAGE" What \nthis means is that when an OUTAGE state is encountered, RDI will no \nlonger perform real time HDR read attempts but will instead display to \nthe user the "Local Data Only" message.\n\n
\nThis parameter is a threshold value that holds the minimum number of \nsuccessfull HDR reads for RDI before RDI will come out of the OUTAGE \nstate. The successfull reads are peformed in a task that is spawned when \nthe OUTAGE state is initiated.\n\n
\nThis parameter represents the number of seconds between the initiation of \nattempts to ping the HDR for a successful read. This pinging takes place \nwhen an OUTAGE state is encountered for RDI.\n\n
\nThis parameter represents the fake ICN that will be used to perform the \nping messages to the HDR when an OUTAGE state is encountered within RDI. \n\n
\nSelect the desired bar code format to produce on the Zebra Label Printer.\n\n
\nThis parameter determines what Theme (i.e., HealtheVet Desktop Theme or \ncurrent Windows Theme) to apply to the Desktop.\n\n
\nReturns an array of reminder categories which can then be used within GUI\nreminder processing.\n\n
\nUsed to flag whether or not to print the Site Number on the labels\ngenerated with the PSBO BL Option. If Yes then the barcode will include\nthe station number - Drug IEN (i.e. 677-263 for drug 263 at station 677)\nIf the answer is No then only the Drug IEN will print (i.e. 263).\n\n
\nThis parameter is used to define the default menu, dialog, or quick order\n that should appear when the user selects New Procedure from the consults\ntab.\n\n
\nThis parameter is used to specify access to personal templates. A setting \nUSER CLASS TIU TEMPLATE ACCESS BY CLASS\nLOCATION TIU PERSONAL TEMPLATE ACCESS\nSERVICE TIU PERSONAL TEMPLATE ACCESS\nDIVISION TIU PERSONAL TEMPLATE ACCESS\nSYSTEM TIU PERSONAL TEMPLATE ACCESS\nof READ ONLY allows the use of personal templates, but does not allow the \ncreation of new personal templates. To restrict template use by USER CLASS,\nuse the TIU TEMPLATE ACCESS BY CLASS parameter. These two parameters work \ntogether, in the following precedence order:\n \nPrecedence Parameter\n---------- ----------------------------\nUSER TIU PERSONAL TEMPLATE ACCESS\n\n
\nThis parameter is used to specify access to personal templates for a \nUSER TIU PERSONAL TEMPLATE ACCESS\nUSER CLASS TIU TEMPLATE ACCESS BY CLASS\nLOCATION TIU PERSONAL TEMPLATE ACCESS\nSERVICE TIU PERSONAL TEMPLATE ACCESS\nDIVISION TIU PERSONAL TEMPLATE ACCESS\nSYSTEM TIU PERSONAL TEMPLATE ACCESS\nspecific user class. A setting of READ ONLY allows the use of personal \ntemplates, but does not allow the creation of new personal templates. \nTo restrict template use by USER, DIVISION or SYSTEM, use the\nTIU PERSONAL TEMPLATE ACCESS parameter. These two parameters work \ntogether, in the following precedence order:\n \nPrecedence Parameter\n---------- ----------------------------\n\n
\nThis parameter is used to trigger a notification/alert when a specific\nalert.)\n \nUsers are linked to a patient if the user is the patient's attending\nphysician, primary inpatient provider, PCMM primary care practitioner,\nPCMM associate provider, user is assigned to a position on the patient's\nPCMM primary care team or user shares an OE/RR team with the patient.\nOE/RR teams are linked to a patient if the patient is on the team. (If\na patient is on a team that has flagged an orderable item, all users on\nthat team become potential alert recipients.) Devices (printers, etc.)\nare linked to a patient if the device and patient are on the same OE/RR\norderable item is ordered for an outpatient.\nteam. \n \nIf the value for the orderable item flag is "YES", the entity (user,\nteam, device), flagging the orderable item becomes a potential alert\nrecipient for ALL patients. If the value is "NO", the entity (user,\nteam, device), flagging the orderable item only becomes a potential\nalert recipient if that entity is "linked" to the patient. (If a device\nis added to the potential recipient list, it will always receive the\n\n
\nThis parameter is used to trigger a notification/alert when a specific\nis added to the potential recipient list, it will always receive the\nalert.)\n \nUsers are linked to a patient if the user is the patient's attending\nphysician, primary inpatient provider, PCMM primary care practitioner,\nPCMM associate provider, user is assigned to a position on the patient's\nPCMM primary care team or user shares an OE/RR team with the patient.\nOE/RR teams are linked to a patient if the patient is on the team. (If\na patient is on a team that has flagged an orderable item, all users on\nthat team become potential alert recipients.) Devices (printers, etc.)\norderable item is resulted for an outpatient. Results only apply to orders\nare linked to a patient if the device and patient are on the same OE/RR\nteam. \nwhich can be resulted (lab, imaging, consults.)\n \nIf the value for the orderable item flag is "YES", the entity (user,\nteam, device), flagging the orderable item becomes a potential alert\nrecipient for ALL patients. If the value is "NO", the entity (user,\nteam, device), flagging the orderable item only becomes a potential\nalert recipient if that entity is "linked" to the patient. (If a device\n\n
\nIndicate if Interactive Reminders are Active. Enter 0 (No) or 1 (Yes).\n\n
\nThis parameter is written and accessed by ORMTIME and related processing.\nNo direct user access is intended.\n\n
\nText to prefix when printing a label on the Zebra Barcode Printer.\n\n
\nThis parameter may be used to identify which items should appear on the \n \nAn ampersand may be used in the name portion to identify a letter that\nshould be underlined on the menu for quick keyboard access. For example,\nto underscore the letter H in Hospital Policy, enter &Hospital Policy as\nthe name part.\ntools menu which is displayed by the BCMA GUI. Each item should contain \na name that should be displayed on the menu, followed by an equal sign, \nfollowed by the command string used to invoke the executable. This \nstring may also include parameters that are passed to the executable.\nSome example entries are:\n \nHospital Policy=C:\\WINNT\\SYSTEM32\\VIEWERS\\QUIKVIEW.EXE LOCPLCY.DOC\nVISTA Terminal=C:\\PROGRA~1\\KEA\\KEAVT.EXE VISTA.KTC\n\n
\nA value of 1 in this parameter will print all orders on the 24 Hour\nfrom which the order was entered, may not have been setup for printing.\n \nA value of 2 will look at the Nature of Order file to determine if the\norder should print on the summary report.\nchart summary report options.\n \nA value of 0 will only print orders that originally printed a chart\ncopy. This is the default value for this parameter. Some sites have\nhad problems with this value, because the Chart Copy Summary may be\ndifferent from the Order Summary report, which prints all orders.\nSome orders don't print a chart copy automatically, because of the\nnature of order the order was given when entered, or because the location\n\n
\nThis parameter determines which remote sites are allowed for remote\nPatient data lookup. This parameter can be especially useful during\ntesting and implementation. Once all sites are implemented, consider\nusing the parameter: ORWRP CIRN SITES ALL\n\n
\nThis parameter will allow access to all remote sites for remote Patient\ndata lookup. It is used in lieu of setting up each site individually with\nthe ORWRP CIRN SITES parameter. Use this parameter when all sites\nhave implemented the Remote Data Views functionality.\n\n
\nThis determines which unsigned orders view that holders of the ORES key\nwill see when exiting a patient's chart; the Package default is to show\nMy Unsigned Orders, i.e. all unsigned orders that the current user either\nplaced or is the responsible provider for. This may also be set to list\nonly those orders placed during the current session, or all unsigned orders\nfor this patient regardless of provider.\n\n
\nThis paramater is set by the users adjusting the columns on the GUI display.\nIt is stored in the format nnn/nnn/nnn/nnn/nnn/nnn/nnn/nnn/nnn.\n\n
\nWhen signing a note in the CPRS GUI, the ORWPCE ASK ENCOUNTER UPDATE\nparameter determines if the user is asked if they want to enter encounter\ninformation. When asked, and this parameter is set to Yes, the primary\nencounter provider will be unable to sign the note until all needed\nencounter information has been entered. Users who are not the primary\nencounter provider will never be forced to enter encounter information\nwhen signing a note.\n\n
\n This parameter overrides the ORWRP HEALTH SUMMARY TYPE LIST by making all\n health summary types available, in alphabetic order.\n\n
\nPSB RPT MAX RANGE is to support the sites ability to limit the range of \ndays a BCMA report will be allowed to process. For example, when this \nparameter is set to 7 , a BCMA report will be able to process data in a \nrange of 7 days such as Jan 1 - Jan 8, 2007. This will assist in \nlimiting the allocation of resources when processing a BCMA report.\n\n
\nWhen signing a note in the CPRS GUI, this parameter is used to determine\nFor the purposes of this parameter:\n 1. Outpatient Encounters include telehealth encounters and inpatients\n being seen at a clinic location.\n 2. Encounter Data Needed is only applicable to Outpatient Encounters.\n \nValid settings for this parameter are:\n 0 = User is Primary Encounter Provider, and Encounter Data is Needed\n 1 = User is Primary Encounter Provider, and it is an Outpatient Encounter\n 2 = User is Primary Encounter Provider\n 3 = Encounter Data is Needed\nunder what conditions to request the user enter encounter information.\n 4 = Outpatient Encounter\n 5 = Always\n 6 = Never\n 7 = Disable - Same as Never but disables the Encounter button\n \nUsers are never asked to enter encounter information if:\n 1. The encounter date is for a date in the future.\n 2. The encounter location is a non-count clinic.\n 3. The encounter is for a scheduled appointment and that appointment \n has been canceled or is a no-show.\n \n\n
\nThis parameter determines how many seconds should elapse between each\nauto-save of a note that is being edited in the GUI.\n\n
\nThis parameter identifies the tab that should be initially displayed when\nCPRS first starts. If ORCH USE LAST TAB is 'no', this tab is also used\nwhenever a new patient is selected.\n\n
\nWhen this parameter is set to yes, CPRS will open to the last selected tab\nwhenever changing patients. When set to no, CPRS will open to the tab\nidentified by ORCH INITIAL TAB.\n\n
\nInteractive Mental Health Reminders are Active. Enter 0 (No) or 1 (Yes).\n\n
\nWhen this parameter is set to yes, web links in the CPRS GUI will be\ndisabled or hidden.\n\n
\nA value of 0 will print all orders with ORDER dates within the selected \ndate range.\n \nA value of 1 will print all orders with START dates within the selected\ndate range.\n \nA value of 2 will print all orders with START dates and orders with any\nACTIVITY within the selected date range.\n\n
\nIf this parameter is set to YES, the window that allows the user to change\na note title will appear whenever the user starts to enter a new note,\neven if they have a default title. If the parameter is set to NO, -and-\nthe user has a default title, that title will be automatically loaded when\na new note is entered.\n\n
\nThis saves the preferred font size for CPRS Chart.\n\n
\nSystem and Division indicate if the order check can be edited by\na user. Valid values include "Yes" and "No". If the value is "Yes", the\norder check can be "Enabled" or "Disabled" by a user. Users do have\naccess to change the order check's ORK PROCESSING FLAG parameter value.\nIf the value is "No", the order check CANNOT be "Enabled" or "Disabled" by\na user. Users do NOT have access to change the order check's ORK\nPROCESSING FLAG parameter value.\n\n
\nThis parameter is used to trigger a notification/alert when a specific\nalert.)\n \nUsers are linked to a patient if the user is the patient's attending\nphysician, primary inpatient provider, PCMM primary care practitioner,\nPCMM associate provider, user is assigned to a position on the patient's\nPCMM primary care team or user shares an OE/RR team with the patient.\nOE/RR teams are linked to a patient if the patient is on the team. (If\na patient is on a team that has flagged an orderable item, all users on\nthat team become potential alert recipients.) Devices (printers, etc.)\nare linked to a patient if the device and patient are on the same OE/RR\norderable item is expiring for an inpatient. \nteam. \n \nIf the value for the orderable item flag is "YES", the entity (user,\nteam, device) flagging the orderable item becomes a potential alert\nrecipient for ALL patients. If the value is "NO", the entity (user,\nteam, device), flagging the orderable item only becomes a potential\nalert recipient if that entity is "linked" to the patient. (If a device\nis added to the potential recipient list, it will always receive the\n\n
\n This parameter is used to trigger a notification/alert when a specific\n alert.)\n \n Users are linked to a patient if the user is the patient's attending\n physician, primary inpatient provider, PCMM primary care practitioner,\n PCMM associate provider, user is assigned to a position on the patient's\n PCMM primary care team or user shares an OE/RR team with the patient.\n OE/RR teams are linked to a patient if the patient is on the team. (If\n a patient is on a team that has flagged an orderable item, all users on \n that team become potential alert recipients.) Devices (printers, etc.)\n are linked to a patient if the device and patient are on the same OE/RR\n orderable item is expiring for an outpatient. \n team. \n \n If the value for the orderable item flag is "YES", the entity (user,\n team, device) flagging the orderable item becomes a potential alert\n recipient for ALL patients. If the value is "NO", the entity (user,\n team, device), flagging the orderable item only becomes a potential\n alert recipient if that entity is "linked" to the patient. (If a device\n is added to the potential recipient list, it will always receive the\n\n
\nDefault Template for Notes;Consults;DC Summ tabs\n\n
\nList of clinics used as a source to get a list of patients\nthat need to have CP studies checked-in. This only applies\nto studies with procedures that have multiple results such\nas Hemodialysis, Respiratory Therapy, and sleep studies.\n\n
\nThis parameter is used to trigger a notification/alert when a specific\nis added to the potential recipient list, it will always receive the\nalert.)\n \nUsers are linked to a patient if the user is the patient's attending\nphysician, primary inpatient provider, PCMM primary care practitioner,\nPCMM associate provider, user is assigned to a position on the patient's\nPCMM primary care team or user shares an OE/RR team with the patient.\nOE/RR teams are linked to a patient if the patient is on the team. (If\na patient is on a team that has flagged an orderable item, all users on\nthat team become potential alert recipients.) Devices (printers, etc.)\norderable item is resulted for an inpatient. Results only apply to orders\nare linked to a patient if the device and patient are on the same OE/RR\nteam. \nwhich can be resulted (lab, imaging, consults.)\n \nIf the value for the orderable item flag is "YES", the entity (user,\nteam, device), flagging the orderable item becomes a potential alert\nrecipient for ALL patients. If the value is "NO", the entity (user,\nteam, device), flagging the orderable item only becomes a potential\nalert recipient if that entity is "linked" to the patient. (If a device\n\n
\nThis parameter contains a list of procedures that will be used\nto auto check-in the CP studies during the procedures request in CPRS.\n\n
\nThis parameter contains a list of ASU user classes who's\nmembers are allowed to edit template fields.\n\n
\nThis parameter allows a custom list of reports, with sequencing, on the\nLabs tab.\n\n
\nThis parameter allows a custom view of the Cover sheet in the CPRS Gui.\n\n
\nThis parameter tracks the progress of the Order Text conversion job,\nqueued off by the post-init for patch OR*3*92.\n\n
\nEnter "Y" or "N" for Yes/No on whether your site selects the appointment\nscheduled for outpatients during the procedure request in CPRS.\n\n
\nThis parameter is used to allow a site to set the number of days that will \nbe searched backwards for a Consult to be associated with a NOTE. A default \nparameter of 365 days will be set at the Package Level.\n\n
\nThis parameter is used and set by the CPRS GUI. Each letter represents\na reminder folder that is visible in the reminders tree.\n\n
\nThis paramater is set by the users adjusting the IVPB column width\nIt is stored in the format nnn/nnn/nnn/nnn/nnn/nnn/nnn/nnn/nnn.\n\n
\nReturns a list of default outside locations for display in a reminder \ndialog.\n\n
\nAllows encounter data to be entered at any time, even when a note is not\nbeing edited.\n\n
\nAllows text generated by a reminder dialog, when processing a reminder,\nto be inserted at the current cursor location instead of at the bottom\nof the note.\n\n
\nContains Reminder Dialogs that are allowed to be used as TIU Templates.\nThis parameter is different than most others in that each level is\ncumulative, so all Reminder Dialogs at the System, Division, Service\nand User levels can be used in Templates.\n\n
\nReturns a list of Reminder Report Templates that are allowed for a\nuser.\n\n
\nIndicates if the New Cover Sheet reminders should be used.\n\n
\nThis parameter is cumulative, so sequence ranges should be assigned.\nValues are in the form of FlagTypeIEN, where Flag indicates\nL:Lock, R:Remove or N:Normal, Type is a 'C' or 'R', indicating\nthat # is the internal entry number of a Category or a Reminder.\n\n
\nIf you have a clinic for multiple procedures, populate this\nparameter with the procedure and associate it to a clinic.\n\n
\nContains TIU Objects that are allowed in the Insert Patient Data Object\ndialog of the Templates Editor, when adding objects to personal\ntemplates. This parameter is cummulative at all levels. If no objects\nare entered in this parameter, all objects will be allowed.\n\n
\nDisables the automatic checkout of encounters that do not have a\ndiagnosis, procedure or provider information.\n\n
\nWhen set to Yes, this parameter prevents the automatic selection\nof a Type of Visit on the Visit Tab of the encounter form.\n\n
\nThis parameter works in conjunction with the \nORQQPX COVER SHEET REMINDERS parameter, acting as another level to\nthe cumulative parameter of User Class, inserted between the User and\nLocation Levels. Each line of the Value word processing field \nrepresents a different reminder or category, and is in the format\nSequence;FlagTypeIEN, where Flag indicates L:Lock, R:Remove or N:Normal, \nType is a 'C' or 'R', indicating that # is the internal entry number \nof a Category or a Reminder.\n\n
\nThis parameter holds the date/time that the Inter-facility Consults \nbackground job last finished running. The parameter is set by the \nbackground job. This parameter is not intended to be modified using\nparameter tools.\n \nIf this parameter becomes delinquent for an extended period, IRM personnel\nwill be alerted that the job is overdue.\n\n
\nThis parameter contains the last start date/time of the Inter-facility \nConsults background job. This parameter will help the system know \nwhether a sufficient amount of time has passed since the last run. If \nthis parameter is set to afuture date/time, the background job will not \nrun until that date /time. The parameter may only be set up to 4 days in \nthe future.\n\n
\nThe number of days to look back in time for patient's most recent lab\nserum creatinine results when Imaging procedures using contrast media are\nordered. This value is used in the Biochem Abnormality for Contrast Media\norder check.\n\n
\nThis parameter contains immunizations that are excluded from the list\nof Other Immunizations displayed in the Encounter Form.\n\n
\nThis parameter contains skin tests that are excluded from the list\nof Other Skin Tests displayed in the Encounter Form.\n\n
\nThis parameter contains patient education topics that are excluded from\nthe list of Other Education Topics displayed in the Encounter Form.\n\n
\nThis parameter contains health factors that are excluded from the list\nof Other Health Factors displayed in the Encounter Form.\n\n
\nThis parameter contains exams that are excluded from the list\nof Other Exams displayed in the Encounter Form.\n\n
\n'Yes' indicates the user can erase all their notifications/alerts.\n\n
\nName of the HFS directory that all Event Capture processes will be able to\naccess through ^%ZISH for printing documents.\n\n
\nShould the Surgery tab be shown in the GUI? ((0=No, 1=Yes)\n\n
\nThis parameter controls the number of days that completed Inter-facility \nConsult transactions are maintained in the IFC MESSAGE LOG (#123.6) file.\n \nCompleted transactions represent Consult activities transmitted to a\nremote facility via HL7 which have been responded to with no error \ncondition.\n\n
\nThis parameter permits users to set Lab test result threshold values that\ndetermine if an alert is sent to them. If a lab test's result is greater\nthan the threshold value, the Lab Threshold Exceeded notification/alert is\ntriggered.\n \nThe Instance (Lab Test;Specimen) must be entered in the format\nLab Test #;Specimen #. Lab Test # is the internal entry number from\nthe LABORATORY TEST file [#60]. Specimen # is the internal entry number\nfrom the TOPOGRAPHY FIELD file [#61].\n\n
\nThis parameter sets the default time and occurrence limits for reports\nfound on the Reports and Labs Tabs in CPRS.\n\n
\nThis parameter sets a default for all reports found on the Reports Tab\nin CPRS. Individual values of this parameter, for each report can be\nset by editing the parameter ORWRP TIME/OCC LIMITS INDV.\n\n
\nThis parameter permits users to set Lab test result threshold values that\ndetermine if an alert is sent to them. If a lab test's result is less\nthan the threshold value, the Lab Threshold Exceeded notification/alert is\ntriggered.\n \nThe Instance (Lab Test;Specimen) must be entered in the format\nLab Test #;Specimen #. Lab Test # is the internal entry number from\nthe LABORATORY TEST file [#60]. Specimen # is the internal entry number\nfrom the TOPOGRAPHY FIELD file [#61].\n\n
\nCOM Object to Activate on CPRS GUI Patient Selection\n\n
\nCOM Objects to activate on order acceptance\n\n
\nThis records the widths of each column on Reports Tab grids. The column\nwiths are entered from left to right and delimited by commas. For example,\n"50,260,25,78,129".\n\n
\n This parameter determines the lookup used to populate the Adhoc Health\n Summary types in CPRS Report Tab, when an Adhoc report is requested.\n\n
\nThe number of days before a notification is forwarded to a recipient's\nzero or non-existent, the alert/notification will never be forwarded.\nbackup alert reviewer. The maximum is 30 days. If not indicated or zero,\nthe notification will not be forwarded. For example, if a notification\nhas a value of 14 for this parameter, it will be forwarded to the backup\nreviewer of each recipient who hasn't processed the notification after 14\ndays. Determination of recipients who have not processed the notification\nand their backup alert reviewer is made by the Kernel Alert Utility. It\nwill not be forwarded to backup reviewers of recipients who have\nprocessed the alert within 14 days. If the value of this parameter is\n\n
\nThis parameter is used to store the application:versions that are compatible\nwith the current server version of Vitals Measurements. Instance format\nis APPLICATION:VERSION (example: VITALS.EXE:0.0.0.0).\n\n
\nThis parameter contains the web address for the Vitals Measurments home\npage. This can be modified to a local address in the event that the pages\nare downloaded to be displayed from a local server location or a site \nwishes to direct user to a local page instead of the national site.\n\n
\nThis parameter is used to store a users default parameter settings. Each \n 'CanvasNormal');\nsetting is defined on the client as follows:\n \n TGMV_UserSetting = (\n usCanvasAbnormal,\n usCanvasNormal);\n \n GMVUSERSETTING: array[TGMV_UserSetting] of string = (\n 'CanvasAbnormal', \n\n
\nThis parameter is used by the BCMA backup system to determine if DOM \npatients are included in the backup. If the value is set to YES, DOM \npatients will be filtered out of the backup and will not be sent to the \nworkstation. If the value is NO or blank, DOM patients will be sent to \nthe backup workstation.\n\n
\nThis parameter controls whether the IFC CLIN ERRORS GROUP at the \nrequesting site is notified immediately of patient information errors at \nthe consulting site. If set to yes, this group will be alerted every \ntime an Unknown Patient error is returned from the consulting site. If \nset to No, this group is only notified if the problem is unresolved after\n5 re-transmissions.\n\n
\nThe number of days after check-in date/time to display the study\nthat has been completed in the CPUser application. Studies that have\nprocedures with multiple or cumulative results are NOT included.\nCumulative and multiple results studies will have a default value of\n365.\n\n
\nThe number of days the completed procedure requests will be\ndisplayed in the CP Check-in screen.\n\n
\nEnter a number from 0 to 365 for the number of days that will be\nused to subtract from today as the start date range of the Encounter\nAppointments. If no value is entered, the default value used\nwill be 200.\n\n
\nFlag used to determine if a notification should be delivered to a user/\nrecipient. Valid values include Mandatory, Enabled or Disabled.\n\n
\nEnter a number from 0 to 365 for the number of days that will be\nused to add to today as the end date range of the Encounter\nAppointments. If no value is entered, the default value used\nwill be 0.\n\n
\nThis parameter is used to store the application:versions that are compatible\nwith the current server version of Hemodialysis. Instance format\nof APPLICATION:VERSION (example: HEMODIALYSIS.EXE:0.0.0.0).\n\n
\nThis parameter is used to store the Hemodialysis application\ndistribution information. The information includes the following:\n1) Date/Time when application first launched.\n2) User Name\n3) System Option Loaded (Y/N)\n4) Workstation of where the application was launched.\n\n
\nif an orderable item for DNR can not be found in the list of orders than \nlook for a text order using this parameter value list.\n\n
\nThis parameter determines whether or not the user only has access to the \nDRM Plus Cover Page. \n\n
\nThis parameter controls whether or not PCE will be automatically updated \nwhen the user deletes transactions in DRM Plus. If set to yes, then the \nsystem will attempt to delete the transactions (CPT codes, ICD-9 codes \nand Providers). If set to no, then the user will be prompted to manually \n'fix' the PCE data.\n\n
\nThis parameter determines the sequence sites want the order DC reasons \nto appear. Sites do not need to set a sequence for every DC Reasons.\nFor example if a site wants to set the "Requesting Physician Cancelled" \nDC Reasons to the top of the list. Sites will set a value of 1 for that\nentry and CPRS will display the rest of the DC Reasons after the\n"Requesting Physician Cancelled" DC reason.\n\n
\nThe number of days backwards in time to search for lab orders/results. If \nnot indicated, the default period of 30 days will be used. The\nmaximum number of days is 100,000 or about 220 years. For outpatients.\n\n
\nThis parameter determines the information that is displayed in the \nAdministration Time Information pop-up or Hover Hint that is displayed \nto the user. The pop-up includes the administration times for the dose \nand the help text defined in this parameter.\n\n
\nThis parameter allows sites to enter generic reason's for flagging \norders that the users can choose in the CPRS GUI.\n\n
\nThe purpose of this parameter is to store the number of days that old \n \nBy lapsing, it is meant that the order is placed in a LAPSED status.\nAlso see the description for parameter OR LAPSE ORDERS DFLT.\norders will be lapsed. This parameter is multi valued with an instance \nterm of DISPLAY GROUPS. Thus the way it works is that you can set \n"Display Group A" so that old orders from this display group will lapse \nin 10 days for instance. Then you could have "Display Group B" set so \nthat those orders would lapse when they are 20 days old. Display groups\nnot individually set by this parameter are affected by the OR LAPSE \nORDERS DFLT parameter.\n \n\n
\nThe purpose of this parameter is to store the number of days that old \norders will be lapsed when those orders are from a DISPLAY GROUP that \ndoes not have parameter OR LAPSE ORDERS set. The default value that is \nset in this parameter will affect all orders that do not have a specific \nDISPLAY GROUP value. Thus if both "Display Group A" and "Display Group \nB" have parameter OR LAPSE ORDERS set for them but "Display Group C" does \nnot, then orders from "Display Group C" will get lapsed in the number of \ndays specified in OR LAPSE ORDERS DFLT.\n\n
\nThis parameter allows sites to set what text they would like for users to \nsee when an inpatient order of Clozapine is made. This drug is generally \nordered in an outpatient setting and thus is subject to the special order \nappropriateness checks. However, when ordered in an inpatient setting \nthese checks are not done. Thus sites should determine a policy to \nhandle this and provide instructions to users based on that policy.\n\n
\nWhen the system automatically changes lab collect orders to ward collect, \nprovides instructions to the user regarding specimen collection for those \nchanged orders.\n\n
\nThis parameter disables the prompt/pop-up that tells the user they must\nenter a Nursing Administration Order manually after entering a VBECS\nBlood order. Disabling this feature is usually done when a Nursing\nAdministration order has been created and added to a VBECS order set.\n\n
\nThis value will determine if CPRS will carry on the text entered in the \nReason for Study field of the Radiology (Imaging) order dialog. By carry \non, it is meant that when one order is entered the value entered in the \nReason for Study field will be held and used again in subsequent \nRadiology orders.\n\n
\nThis parameter controls how long the patient messages window displays\nbefore automatically closing. The default is 5. If the number of seconds\nis set to 0, the window will remain open until the user clicks it closed.\n\n
\nSet of codes indicating default provider recipients of a notification by \nTeams (personal patient and team lists are evaluated for potential \nrecipients) and to devices on an OE/RR team.\n O (Ordering Provider): deliver notification to the provider\nwho placed the order which trigger the notification.\n M (PCMM Team): deliver notification to users/providers linked to the\npatient via PCMM Team Position assignments.\n E (Entering User): deliver notification to the user/provider who entered\nthe order's most recent activity.\n R (PCMM Primary Care Practitioner): deliver notification to the\npatient's PCMM Primary Care Practitioner.\ntheir title or relationship to the patient. Notifications can be set up \n S (PCMM Associate Provider): deliver notification to the patient's PCMM\nAssociate Provider.\n C (PCMM Mental Health Treatment Coordinator): deliver notification to \nthe patient's PCMM Mental Health Treatment Coordinator.\n \nThe providers, physicians and teams must be set up properly and accurately\nfor the correct individuals to receive the notification.\nwith any or all of the following codes:\n \n P (Primary Provider): deliver notification to the patient's Primary\nProvider. \n A (Attending Physician): deliver notification to the patient's Attending\nPhysician.\n T (Patient Care Teams): deliver notification to the patient's OE/RR \n\n
\nThis is used in the VBECS Order Dialog to check for recent orders for a\nType & Screen order. The default is 3 days, but a site can override this\nnumber by setting this parameter to something different.\n\n
\n'Yes' indicates that VBECS functionality is enabled.\n\n
\nMailgroup to notify when an item is documented as not able to be scanned.\n\n
\nThis parameter determines whether the user will be prompted to reimport \nthe Code Boilerplate when going back to the note after clicking 'Back' \nand 'Next'. If NO (or not defined) then the Code BP will be \nautomatically imported, if YES, then the user will be prompted and can \nhave the option of not importing the Code Boilerplate into the note.\n\n
\nThis field changes the background color on the cover page for the \nMonitored Exam field. If the date is older than the number of days in \nthe parameter, then the default color will change to white to highlight \nthe older date.\n\n
\nThis parameter allows a sequence to be assigned to Blood Components\nselectable from VBECS.\n\n
\nThis parameter allows local configuration of the blood component modifiers.\n\n
\nSet of codes indicating the urgency for a notification for a site. The\nurgency is mainly used for sorting in displays. The codes include: 1\n(High): notification is Highly urgent. 2 (Moderate): notification is\nModerately urgent. 3 (Low): notification is of Low urgency.\n\n
\nThis parameter allows local configuration of the Reasons for Request.\n\n
\n'Yes' will show the Legacy (VISTA) blood bank report after\nthe VBECS blood bank report.\n\n
\nThis parameter holds the text to be displayed when the VBECS order dialog\nis selected but the communication links between CPRS and VBECS are down.\nSite-specific directions for initiating blood bank orders are encouraged\nto be put here at the System or Division level.\n\n
\nSet this value to Yes to allow CPUser to use the location of the\nappointment selected during CP study check-in for the workload.\nOtherwise, the hospital location of the CP Definition will be used.\nIf no value is entered, the default value is No.\n\n
\nThis parameter is used to identify the clinic and procedure\nassociation. Each item should be entered with the following format\n \n Clinic internal entry number_";"_Procedure internal entry number\n\n
\nThis parameter definition indicates whether the Olympus device\nis version 7.3.7. The value is Yes/No. The default value\nis "No".\n\n
\nThis parameter will store the user login name for the Clinical Logistics \nReport Server.\n\n
\nThis parameter will store the user login password for the Clinical\nLogistics Report Server.\n\n
\nThis parameter will store the Regional Acquisition Center which will be \npopulated by the station and used to group Purchase Order transactions.\n\n
\nThis parameter will determine if this user is allowed access to the \nconversion utilities in the DocManager GUI.\n\n
\nThe number of days backwards in time to search for lab orders/results. If \nnot indicated, the default period of 30 days will be used. The\nmaximum number of days is 100,000 or about 220 years. For outpatients.\n\n
\nThe parameter controls whether or not the site wants the import image \nfile deleted from the network directory by the VistA Imaging Background \nProcessor after the BP has imported the file. The BP will delete the \nfile if told to do so whether or not it successfully imports the image. \nThe usual exception to this occurs when the BP process does not RWD \nrights to the folder where the image resides.\n\n
\nThis parameter will control whether or not the DocManager GUI application \nshould present the consult signature edit box when completing a consult.\n\n
\nThis will store an individual user's settings for indexing documents\n\n
\nThis parameter controls user access for importing images in DocManager.\n\n
\nALLOWS ENTRY CLERKS ACCESS TO THE GUI EDIT SCREEN.\n\n
\nALLOW ENTRY CLERKS TO VIEW BUFFER LIST TAB DISPLAY.\n\n
\nThis parameter controls whether the group policy fields may be edited.\n\n
\nThis parameter determines how appointments are filtered out in the \npatient update list for ICB.\n 0=not filtered\n 1=filter out checked-in status (this also filters checked-out status)\n 2=filter out checked-out status\n\n
\nThis is the user preference setting for patient update list column sort.\n\n
\nNUMBER OF DAYS BACK TO RETRIEVE APPOINTMENTS LIST.\n\n
\nThe number of days backwards in time to search for radiology/nuclear\nmedicine exams/reports. If not indicated, the default period of 730 days\n(2 years) will be used. The maximum number of days is 100,000 or about\n220 years.\n\n
\nNUMBER OF DAYS BACK FROM TODAY TO RETRIEVE INSURANCE BUFFER ENTRY LIST.\n\n
\nThis is the user preference for setting the buffer list column sort.\n\n
\nLOCATION TEXT DEFAULT WHEN DISPLAYING APPOINTMENTS LIST.\n\n
\nTHIS IS THE DEFAULT DOCUMENT TYPE USED FOR FILING INSURANCE CARD IMAGES TO VISTA IMAGING\n\n
\nENABLES/DISABLES AUDITING OF ADD, UPDATE, DELETE, ACCEPT, AND REJECT \nPROCESSES TO FILE #19625.\n\n
\nFORCE KEYBOARD TO UPPERCASE WHEN ENTERING DATA IN THE EDIT FIELDS.\n\n
\nDisplay mode for ICB screen.\n\n
\nTHIS IS THE STORAGE LOCATION FOR THE INSURANCE CARD IMAGES\n\n
\nCARD IMAGE FILING OPTION.\n\n
\nTHIS INSTRUCTS THE ICB GUI TO USE THE LOCALLY INSTALLED EXCEL\nINTERFACE TO EXPORT THE BUFFER LIST AND PATIENT UPDATE LIST.\n\n
\nPostings\nThis button provides access to patient postings. The single letter\nabbreviation for each type of posting appears on the button, if such a\nposting exists.\n\n
\nContains the maximum number of records to return from the buffer in one \nrpc call. If there are more than the max records, then multiplay rpc \ncalls need to be made.\n\n
\nOCR ACCURACY THRESHHOLD. FOR EXAMPLE, 0.7.\n\n
\nTHIS IS A MULTI-INSTANCE PARAMETER TO CONFIGURE PAGE PRINT SETUP (PER USER).\n\n
\nBACK COLOR FOR REQUIRED EDIT FIELDS.\n\n
\nTHIS IS A MULTI-INSTANCED LIST OF THE ICB EDIT FORM COMPONENTS WHICH THE\nSUPERVISOR CAN SET AS REQUIRED FIELDS.\n\n
\nDEFAULT SOURCE WHEN AUTOMATICALLY ENTERING BUFFER ENTRIES.\n\n
\nThis parameter determines if the ICB system will enable or disable the \nSSN field value display in the policy. 0=No, 1=Yes.\n\n
\nSave the users buffer list filter string.\n\n
\nLIST OF PREFERRED LOCATIONS TO RETRIEVE APPOINTMENTS LIST.\n\n
\nThis parameter determines if the insurance validation logic will check \nthe patient policy exire date field. 0=No, 1=Yes.\n\n
\nDefault preference for patient list source. Valid values include: \nE:PCMM Team List\nT:Team/Personal List\nW:Ward List\nC:Clinic List\nP:Provider List\nS:Specialty List\nM:Combination List\n\n
\nThis parameter contains a special days back value and a list of insurance \ncompanies that should use that value when checking to see if an insurance \nneeds to be verified.\n\n
\nPARAMETER SETTING FOR SENDING VISTA EMAIL NOTIFICATION WHEN CV STATUS \nCHANGES.\n\n
\nFlag REASON if a Buffer entry is rejected.\n\n
\nContains a list of users allowed to run ICB reports.\n\n
\nIndicates (Y/N) whether a buffer entry can be created by entry clerks \nfrom an existing patient policy.\n\n
\nUser configured appointment list date range.\n\n
\nContains the number of days back to check if a patient flagged as "no \ninsurance" is still "no insurance" or now has coverage.\n\n
\nIf the parameter = Yes, then the Exception Report will contain only 1 \npatient per day. If the parameter = No, then the Exception Report will \ncount clerks (or appts) and could have the same patient on the report \nmultiple times for different clinics (appts).\n\n
\nICB ADMIN TOOLS ACCESS CONTROL FOR ADMIN ROLE.\n\n
\nDefault sort order for the patient list. Room/Bed is valid only for \ninpatients list (Ward, Team/Personal Team, Provider, Specialty). \nAppointment Date is valid only for outpatient lists (Clinic) and\nCombination lists. Source is valid only for Combination lists.\n\n
\nThis is the first line of the Anticoagulation Clinic address.\n\n
\nThis is the second line of the Anticoagulation Clinic address.\n\n
\nThis is the (optional) third line of the Anticoagulation Clinic address.\n\n
\nThis is the TIU Document Title that identifies the Anticoagulation\nDischarge Note, which is entered upon the patient's discharge from the\nAnticoagulation clinic.\n\n
\nWard for default list of patients.\n\n
\nThis is the TIU Document Title that identifies the Anticoagulation Interim\nNote, which is entered during the patient's ongoing treatment by the\nAnticoagulation clinic.\n\n
\nThis is the TIU Document Title that identifies the Anticoagulation Initial\nAssessment Note, which is entered for the patient's first visit upon\nenrollment in the Clinic.\n\n
\nThe ALL Patient list, shows everyone scheduled for that team for that day\nAND any patients NOT completed on previous days.\n \nPatients drop off this list as they are completed in the Anticoagulator.\n\n
\nThe complex patient list pulls out these patients so that they are not\nlost on the larger list (they appear on both lists).\n \nPatients drop off this list as they are completed in the Anticoagulator.\n\n
\nTelephone number, with extension if needed, for FAXes to be sent to the\nanticoagulation clinic. For patient letters.\n\n
\nTelephone number, with extension if needed, for patient to contact the\nanticoagulation clinic. For patient letters.\n\n
\nIndicates if Consult Linker will be used. If NO: prompt will not be seen\nto complete consult.\n\n
\nThis is the reference to the Consult Request Service with which Consult\ndata will be associated for the Anticoagulation clinic. It is used only if\nthe linkage with the Consult Package is enabled.\n\n
\nThis is the CPT code for a Complex Telephone Visit (i.e., HC PRO PHONE\nCALL 21-30 MIN (CPT-4 98968), as of 10/2008).\n\n
\nThis is the CPT code for the Initial Office Visit (i.e., ANTICOAG MGMT, \nINIT (CPT-4 99363), as of 10/2008).\n\n
\nTeam/Personal list to be default source of patients.\n\n
\nThis is the CPT code for a Letter to the Patient (i.e., (CPT-4 98966), as\nof 10/2008).\n\n
\nThis is the CPT code for the Orientation Class Visit (i.e., GROUP HEALTH \nEDUCATION (CPT-4 99078), as of 10/2008).\n\n
\nThis is the CPT code for a Simple Telephone Visit (i.e., HC PRO PHONE CALL\n5-10 MIN (CPT-4 98966), as of 10/2008).\n\n
\nThis is the CPT code for Subsequent Anticoagulation Management (i.e.,\nANTICOAG MGMT, SUBSEQ (CPT-4 99364), as of 10/2008).\n\n
\nThis is the stop code for the Anticoagulation Clinic.\n\n
\nThis is the reference to the DSS Unit to which the anticoagulation data\nwill be associated.\n\n
\nThis is the reference to the Lab Test for Hematocrit (HCT) or Hemoglobin \n(Hgb). It will determine whether the Demographics Tab will display the \nmost recent Hematocrit or the last Hemoglobin.\n\n
\nName of medical facility for letter head.\n\n
\nClinic Locations \n \nWith PCE Functions: If you DO use PCE functions, then you will be asked\nfor three clinics, one for face contact (the one on the yellow sheet), one\nfor phone contact, and one that is non count (these are on the PCE form).\nThe "VISIT" location (the ANTICOAG VISIT Clinic Location) should be a\nClinic for FACE to FACE visits. The program does not care if you use the\nsame clinic for both the phone and face to face, but for PCE credit they\nmust be COUNT CLINICS.\n \nThe non-count clinic is used for notes only, when no PCE data is recorded.\n \nWithout PCE Functions: Clinic location you choose is the clinic the note\nwill be associated with. This requires a number from the Hospital\nLocation file. \n \nIf you do NOT use the PCE function, then your site is responsible for\nencounters, etc. The program does NOT care if you use a count or a\nnon-count clinic. \n\n
\nIndicates if interface with PCE will be used. If NO: prompt will not be\nseen to enter PCE information, and the information will not be passed to\nthe Event Capture system.\n\n
\nClinic identified as a default source for patients on Monday.\n\n
\nClinic Locations \n \nWith PCE Functions: If you DO use PCE functions, then you will be asked\nfor three clinics, one for face contact (the one on the yellow sheet), one\nfor phone contact, and one that is non count (these are on the PCE form).\nThe "VISIT" location (the ANTICOAG VISIT Clinic Location) should be a\nClinic for FACE to FACE visits. The program does not care if you use the\nsame clinic for both the phone and face to face, but for PCE credit they\nmust be COUNT CLINICS.\n \nThe non-count clinic is used for notes only, when no PCE data is recorded.\n \nWithout PCE Functions: Clinic location you choose is the clinic the note\nwill be associated with. This requires a number from the Hospital\nLocation file. \n \nIf you do NOT use the PCE function, then your site is responsible for\nencounters, etc. The program does NOT care if you use a count or a\nnon-count clinic. \n\n
\nName of Contact Person (or Clinic) for the "CALL IF QUESTIONS" block on\npatient letters.\n\n
\nTo use the letter programs the Anticoagulator needs to know where to find\nthem. This path is where you put the 2 .rav files (cvisit.rav and\nmappt.rav). Usually placed in the same network file as the the .EXE file\nfor the program for ease of updating, etc.\n \nThis field contains the path up to the slash before the exe. Portland\nexample: \\\\vhaporfpc11\\ClinApps\\DelphiExe\\antiC\\\n\n
\nSigning name to be used in the letter signature blocks.\n\n
\nTitle used in letter signature blocks.\n\n
\nSpecifies the name of the Clinic with which the user may associate the \npatient whose flowsheet is being viewed/entered (3 - 30 characters in \nlength).\n\n
\nClinic Locations \n \nWith PCE Functions: If you DO use PCE functions, then you will be asked\nfor three clinics, one for face contact (the one on the yellow sheet), one\nfor phone contact, and one that is non count (these are on the PCE form).\nThe "VISIT" location (the ANTICOAG VISIT Clinic Location) should be a\nClinic for FACE to FACE visits. The program does not care if you use the\nsame clinic for both the phone and face to face, but for PCE credit they\nmust be COUNT CLINICS.\n \nThe non-count clinic is used for notes only, when no PCE data is recorded.\n \nWithout PCE Functions: Clinic location you choose is the clinic the note\nwill be associated with. This requires a number from the Hospital\nLocation file. \n \nIf you do NOT use the PCE function, then your site is responsible for\nencounters, etc. The program does NOT care if you use a count or a\nnon-count clinic. \n\n
\nThis is the default Pill Strength in milligrams for the Clinic in question\n(e.g., 2.5, 5, or 10). If you do not specify a pill strength, the program \nwill default to 5 mg.\n\n
\nPlease indicate whether time of day will be asked for, and/or included in\n 4 - Lab Procedures as Instructed (pt. will be instructed to\n follow local lab procedures)\nthe instructions in Patient Letters, when specifying the Return for INR\nDate.\n \nThe following values may be selected:\n 0 - None (i.e., no time of day will be asked or included)\n 1 - Time of Day (a specific time will be prompted for & included)\n 2 - Morning (pt. will be instructed to arrive in the morning)\n 3 - Afternoon (pt. will be instructed to arrive in the afternoon)\n\n
\nToll free telephone number, for patient to contact the anticoagulation\nclinic. For patient letters.\n\n
\nThis parameter is used to present the order dialog for a New Medication\non the Meds tab of the CPRS GUI. A separate order dialog can be used\nfor inpatients and outpatients.\n\n
\nPatients with appointment dates as early as this date will be added to the\nClinic List. Patients will be added with appointment dates between START\nDATE and STOP DATE.\n\n
\nThis is the reference to the Quick Order Dialog for the INR (International\n \nFor example, a person taking the anticoagulant ("blood thinner") warfarin\n(brand name: Coumadin) might optimally maintain a prothrombin time (a "pro\ntime" or PT) of 2 to 3 INR. No matter what laboratory checks the\nprothrombin time, the result should be the same even if different\nthromboplastins and instruments are used. This international\nstandardization permits the patient on warfarin to travel and still obtain\ncomparable test results.\nNormalized Ratio) for Prothrombin Times.\n \nINR: International normalized ratio, a system established by the World\nHealth Organization (WHO) and the International Committee on Thrombosis\nand Hemostasis for reporting the results of blood coagulation (clotting)\ntests. All results are standardized using the international sensitivity\nindex for the particular thromboplastin reagent and instrument combination\nutilized to perform the test.\n\n\nThis is the reference to the Quick Order Dialog for Complete Blood Count\n(CBC).\n\n
\nThese are the Indications for care and their associated ICD-9-CM codes.\n\n
\nThis is an Indication for care which will automatically be filed as the \nindication(s) from the list).\nPrimary Indication for each visit to the applicable Clinic.\n \n(e.g., if all visits to a non-licensed provider should be filed with \nV58.61 L/T (CURRENT) USE - ANTICOAG as the primary indication, you can\nspecify that with this parameter. If all visits should also have V58.83 \nENCTR THERAP DRUG MONITOR as an automatic Secondary Indication for care, \nyou can express that by setting the Auto Secondary Indic for Care (ICD-9-\nCM) parameter. The user will still be able to select additional \n\n
\nThis is the whole number of days to look-back when attempting to match the\nAnticoagulation Encounter to a scheduled appointment in the VistA \nScheduling Package.\n \nPlease enter a number between 0 and 7, no decimal digits.\n \nThe default will be one (1) day (i.e., yesterday). A value of zero (0)\nwill restrict the search to begin with today's appointments (i.e.,\nT@00:00).\n\n
\nThis is the whole number of days to look-ahead (into the future) when\nattempting to match the Anticoagulation Encounter to a scheduled\nappointment in the VistA Scheduling Package.\n \nPlease enter a number between 0 and 3, no decimal digits.\n \nThe default will be one (1) day (i.e., tomorrow). A value of zero (0) will\nrestrict the search to end with today's appointments (i.e., T@23:59).\n\n
\nThis parameter contains the minimum CAPRI GUI version that is compatible \nwith the server version. Format: CAPRI GUIv2.7*123*1*A*NOOLD\n\n
\nThis parameter contains the full URL that points to the Health\nInformation Access download web site. The web site contains the latest \nreleased version of CAPRI.\n\n
\nPatients with appointment dates as recent as this date will be added to the\nClinic List. Patients will be added with appointment dates between START\nDATE and STOP DATE.\n\n
\nThis parameter will contain a free text string that contains two pieces\nof data delimited by a semicolon ';'. The two pieces of data are: 1)\n1/0 (Yes/No) to indicate whether or not the text of the result should be\nadded to the note, 2) 1/0 (Yes/No) to enter the text of the result as the\nsignificant finding of the Consult. (If you enter a 0, the note will be\nauto closed with the text inside.)\nExample string: 1;0\n\n
\nThis parameter is used to indicate the note should not be \nadministratively closed with the proxy user CLINICAL, DEVICE PROXY \nSERVICE but the interpreter of the procedure for the MUSE device.\nThe default is "No".\n\n
\nThis parameter indicates that Clinical Procedures will use the note\nfor the text of the result instead of the Significant Finding field in\nConsult.\n\n
\nThis parameter points to a proxy user in the NEW PERSON (#200) file \ncreated for the auto-renewal process. This value is used to populate the \n'entered by' field in the ORDERS (#100) file, and the 'Entry by' field in \nthe PRESCRIPTION (#52) file, and is the proxy user IEN placed in the \nAudioRenewal module User Parameters field 'Host User ID#'. \n\n
\nThis parameter identifies the User Class whose members should have Visible\n"ghost-write" documents on behalf of licensed providers, who in turn must\nreview/sign the content).\n \nIf you discover that the Billing Verification Report at your station \nincludes an unacceptable number of documents entered by users whose work\nshould not be included in the report, you can "filter the noise" by \nidentifying a User Class using this parameter, and making sure that only \nthe people whose work should be reported are added as members to that \nUser Class.\nBlack Character Line Counts reported for the TIU documents which they \nenter (e.g., Contract Transcriptionists).\n \nIf defined, the TIU Billing Verification Report will include documents\nentered by members of this class. If left undefined, the TIU Billing\nVerification Report will include any document entered by a person who is\nneither the author or expected cosigner (which could include in-house\ntranscriptionists, secretaries, technicians, or students, who\n\n
\nUsed to determine if the site wants to transmit the device survey to\nHines. Enter 'Y' for 'YES' to send the survey or 'N' for 'NO' to \nsuppress the transmission.\n\n
\nThe number of days after check-in date/time to display the study\nthat has been completed in the CPUser application. This only\npertains to studies that have procedures with multiple studies.\n\n
\nThis parameter lists the entry or entries from the Hospital Location \ntime range entries.\n \nSequence allows you to map Hospital Location entries in a preferred \norder. When creating an encounter in PCE, EDIS will use the entry with \nthe lowest sequence number to create the visit.\n \nWhen creating the encounter by using the scheduling package to check-in, \nany matches to the list (whether time range or sequence based) will cause \nthe checked-in patient to be added to the display board.\n \nfile (#44) that are used by the Emergency Department. If there are \n**Do not use the same Emergency Department Location for multiple \nDivisions as this may cause unintended consequences adding patients to \nthe display board using scheduling applications.**\nmultiple Hospital Location file entries for the Emergency Department \nthere are two choices when prompted for "Time Range or Sequence":\n \nTime Range allows you to map Hospital Location entries by time of day. \nWhen creating an encounter in PCE, EDIS will match the Hospital Location \nbased on the current time of day. You may enter the time range in \nmilitary time. For example, 0800-1600 or 1800-2400 would be two possible \n\n
\nThis list contains the screen sizes that are selectable for the EDIS \ndisplay board. It generally lists the sizes of LCD or Plasma screens \nthat may be used for the large display.\n\n
\nThis allows a site to select which type of filtering, or screening, that \nshould be applied to the New Person file (200) when selecting nurses in \nEDIS. The default is to screen by presence in the NURS STAFF file (210) \nwith a status of "active". Other options include:\n \n 1: Allow only persons holding the ORELSE key.\n 2: Allow only persons holding the PSJ RNURSE key.\n 3: Allow selection from all entries in the NEW PERSON file (200).\n\n
\nProvider who is basis for building the Provider List of patients.\n\n
\nThis sets a $H timestamp to signal that EDIS RPC's should be logged for \nthe 30 minutes following the timestamp.\n\n
\nThis allows a site to select which scheduling event should trigger an \nautomatic addition of the patient to the board. As of patch EDP*2*20 \nthere is only one event allowed to trigger. \n \n 4: Patient will be added to the board when checked-in\n\n
\nThis parameter maps fully qualified computer names to the display board \nthat they should show. Values must be added or changed via the option\nEDPF BIGBOARD KIOSKS.\n\n
\nThis parameter allows a sequence to be assigned to Diagnostic Tests\nselectable from VBECS.\n\n
\nThis parameter can be used to remove any defaults for Collection Times\nin the VBECS Order Dialog. An entry of YES will set the default to null\nwhen using the VBECS Blood ordering dialog. Quick orders with a default\ndefined in the quick order definition will not be affected by this\nparameter.\n\n
\nThis paramter will switch the location of the Diagnostic and Component\npanels on the VBECS Order Dialog. Set this parameter to YES to see the\nDiagnostic tests panel displayed on the left hand side of the display.\n\n
\nThis parameter controls if a user is allowed to view images\nusing thin client in TeleReader\n\n
\nThis is a multi-instance list of VistA Imaging indexing fields templates.\n\n
\nTreating Specialty used as a source for patients on the Specialty List.\n\n
\nThis parameter holds the date/time that the job responsible for \nsending an initial extract of 1358 transactions to the Online \nCertification System (OLCS) finished running. This parameter is not\nintended to be modified using parameter tools.\n\n
\nEnables the pre-defined Insurance List for selection when using the \n"scan" or "other" option to create a Buffer (355.33) entry in ICB.\n\n
\nICB Buffer create pre-populated selection list of insurance companies.\n\n
\nEnable NO INSURANCE age limit verification. When set, NO INSURANCE \nbuffer entries will not be automatically processed for patients older \nthan the age set in the parameter. For example, 1=65 means check age\nlimit verification (do not process No Insurance) for patients older than\n65.\n\n
\n'Yes' indicates that VBECS Reasons for Request will be sorted Alphabetically.\n\n
\nThis parameter determines the format that Available Units is displayed\n Report - Splits line in 2 if longer than 79 characters.\n Printed Report - Splits line in 2 if longer than 79 characters.\n \nThis parameter was created to address issues found when printing\nthe Blood Bank report in the horizontal format. The option of \ndisplaying/printing Available units vertically has been created.\n \nAs more fields are added to this portion of the report with\nvariable lengths, the length of the line may go beyond the 80\ncharacter limit for printing. This is not as big of an issue in\non the Blood Bank Report and the Patient Information screen on the\nthe Windows display. The Patient Information Screen cannot be \nprinted, so no attempt has been made to split the line when it\ngoes beyond 79 characters. It functions the same when either\nHORIZONTAL or SPLIT HORIZONTAL is selected.\n \nFor both HORIZONTAL display formats the length of the line \nexpands or contracts depending on the column width of each field\nand the length of the longest line. Because of this it is\npossible, though not likely, that the line will not split even\nif SPLIT HORIZONTAL is selected.\nBlood Bank Order Dialog.\n 0:HORIZONTAL - Displays fields across the page, one line per date/time.\n Printed reports splits line if longer than 79 characters.\n 1:VERTICAL - Displays fields down the page in sections per date/time.\n - Printed report looks the same.\n 2:SPLIT HORIZONTAL - \n Patient Information Screen - Same as HORIZONTAL format\n\n
\nEnter 'Yes' to display Location abbreviation instead of Location\nName on Blood Bank Report.\n\n
\nClinic to be default for determining patient list on Tuesdays.\n\n
\nThis will store the number of hours for the Last Injection Site Timeframe \non the BCMA Site Parameters screen.\n\n
\nThis parameter will skip the code that patch 543 uses. If patch\n543 broke the iMedConsent application, this parameter should be\nset to YES. The default is NO.\n\n\n\n
\nHigh Risk Mental Health Patient - Reminder and flag\n\n
\nThis is the name of the Chaplain Consult used in each division of your\nsite.\n\n
\nAllows display of the Orient and Vital Signs tabs in the Admission \nAssessment. These tabs normally only show up in the Data Collection.\n\n
\nRequires cosignatures for nursing students\n\n
\nThis is the number of days back to display the active meds. If you enter\n45 days, for example, the assessment will search for meds that were active\nfrom today to 45 days ago.\n\n
\nAllows each site to determine if they want the nurses to be able to send \nDischarge Planning consults. If you say NO here, the "Discharge Planning \nConsult" button on page 2 of the Discharge Planning tab will be grayed\nout.\n\n
\nThis is the name of the Discharge Planning Consult used in each division\nof your site.\n\n
\nClinic to be default source of Wednesday's patient list.\n\n
\nAllows each site to determine if they want the nurses to be able to send\nHome Care consults. If you say NO here, the "Homne Care Consult" button\non page 2 of the Discharge Planning tab will be grayed out.\n\n
\nThis is the name of the Home Care Consult used in each division of your\nsite.\n\n
\nThis is the name of the Nutrition Consult used in each division of your\nsite.\n\n
\nThis is the name of the Social Work Consult used in each division of your\nsite.\n\n
\nThis is the name of the Speech Consult used in each division of your site.\n\n
\nAllows each site to determine if they want the nurses to be able to send\nTelehealth consults. If you say NO here, the "Telehealth Consult" button\non page 2 of the Discharge Planning tab will be grayed out.\n\n
\nThis is the name of the Telehealth Consult used in each division of your\nsite.\n\n
\nAllows each site to determine if they want the nurses to be able to send\nNurse Restorative consults. If you say NO here, the "Nurse Restorative\nConsult" button on the Musculoskeletal's tab Care Plan page will be grayed\nout.\n\n
\nThis is the name of the Nurse Restorative Consult used in each division of\nyour site.\n\n
\nThis is the name of the Nurse Restorative Consult used in each division of\nyour site.\n\n
\nClinic to be default source of Thursday's patient list.\n\n
\nAllows each site to determine if they want the PCE Tab to display.\n\n
\nThis is the maximum height in inches that the nurses can enter into the \nHeight field on the Vitals tab.\n\n
\nThis is the maximum weight in pounds that the nurses can enter into the\nWeight field on the Vitals tab.\n\n
\nThis is the minimum height in inches that the nurses can enter into the\nHeight field on the Vitals tab.\n\n
\nThis is the minimum weight in pounds that the nurses can enter into the\nWeight field on the Vitals tab.\n\n
\nNumber in minutes that the program will time out.\n\n
\nThis is the Data Name of the PSA (PROSTATE SPECIFIC ANTIGEN) test at your \nsite. This is found in ^DD(63.04), not in the Lab Test file (#60).\n\n
\nAllows each site to determine if they want the nurses to be able to send\nNurse Restorative consults. If you say NO here, the "Nurse Rehab Consult"\nbutton on the Musculoskeletal's tab Care Plan page will be grayed out.\n\n
\nThis is the name of the Rehab Consult used in each division/hospital\nlocation of your site.\n\n
\nAllows each site to determine if they want the nurses to be able to send\nRespiratory consults. If you say NO here, the "Respiratory Consult"\nbutton on page 2 of the Respiratory tab will be grayed out.\n\n
\nClinic to be default source of Friday's patient list.\n\n
\nThis is the name of the Women's Health Consult used in each division of\nyour site.\n\n
\nIf set to yes, adds to words (checked) or (unchecked) to the items in all \nCheckListBoxes in the Care Plan. This is so visually impaired users can \nknow if the boxes are checked or not via JAWS.\n\n
\nAllows each site to determine if they want the nurses to be able to send\nWomen's Health consults. If you say NO here, the "Women's Health Consult"\nbutton on page 2 of the GU tab will be grayed out.\n\n
\n Allows each site to determine if they want the nurses to be able to send\nDiabetes Nurse consults. If you say NO here, the "Diabetes Nurse Consult"\nbutton on page 3 of the GU tab will be grayed out.\n\n
\nThis is the name of the Diabetes Nurse Consult used in each division of\nyour site.\n\n
\nThis is the name of the Wound Care Consult used in each division of your\nsite.\n\n
\nURL for the VA's pressure ulcer site.\n\n
\nAllows nurses to save notes on more than one patient in the assessment and\nre-assessment.\n\n
\nNumber of times that the user can switch tabs or pages before the program \nwill autosave their data. Default is 5. Range can be 5-20.\n\n
\nNumber of minutes of before an autosave will occur. Default is 3. Range\ncan be 3-10.\n\n
\nClinic to be default source of Saturday's patient list.\n\n
\nICB EXCEPTION REPORT PREFERRED LOCATION MULTI-LIST\n\n
\nThis parameter determines the number of days to retain report datain the \nRelease of Information System (DSIR).\n\n
\nThis parameter holds the date that the Release of Information report \ncleanup code was last executed. \n\n
\nThis parameter will contain the saved window position for a user. This is \nso that once a user sets a window location, they will not have to reset \nit upon reopening DRM Plus.\n\n
\nThis parameter permits an administrator to give a non-administrator user \nthe ability to use clean slate functionality.\n\n
\nThis parameter will be used to distinguish how a provider wants the exam \nscreen to function. If yes, the next button throughout the exam template \nwill skip to the next required item, bypassing all optional data.\n\n
\nThis parameter will be used to distinguish how a provider wants the exam \nscreen to function. If yes, the back button throughout the exam template \nwill skip to the previous required item, bypassing all optional data.\n\n
\nThe value stored in this parameter will flag the DRM Plus GUI to \nautomatically display the requirements section found in the exam tab \nelements. The added data provides information on what is required to \ncomplete screens.\n\n
\nClinic to be default source of Sunday's patient list.\n\n
\nThe parameter controls whether or not the site wants the import image \nfile deleted from the network directory by the VistA Imaging Background\nProcessor after the BP has imported the file. The BP will delete the \nfile if told to do so whether or not it successfully imports the image. \nThe usual exception to this occurs when the BP process does not have RWD \nrights to the folder where the image resides.\n\n
\nUsed to designate the default verification method presented to\nthe user when verifying laboratory results in the "CH" subscript\nvia options that use a load/work list. Parameter is associated\nwith the accession area linked to the load/worklist profile\nselected by the user.\n\nParameter can be set at the package or user level. \nUser level takes precedence over division level.\nSite can also force verification by UID only.\n\n
\nAllows the User to select the default setting for "Parse HL7 Message\n" prompt when using OPTION [LA7 PRINT LAB UI MESSAGE].\n \n"LAST" means the User wants the system to keep track of their last\nresponse to this prompt and use that as their default. \n\n
\nAllows the User to select the default setting for "Use Browser to display \nHL7 Message" prompt when using OPTION [LA7 PRINT LAB UI MESSAGE].\n \n"LAST" means the User wants the system to keep track of their last\nresponse to this prompt and use that as their default.\n\n
\nAllows selection of default lab label printer presented to the user when selecting\nthe label device to use to print accession and order labels.\nUser can specify default printer by division.\n\n
\nUsed to designate if the EGFR calculation should calculate the\nEGFR based on a IDMS-traceable method. This parameter is configurable\nat both the package and division level.\n\n
\nUsed to designate if the EGFR calculation should not be performed \non creatinine when executing the delta check EGFR when the\npatient's age is <18 or >70. This parameter is configurable\nat both the package and division level and can be set for\neither or both age cutoffs.\n\n
\nUsed to designate if the EGFR calculation should be suppressed\nwhen the value is >60. If enabled then ">60" is reported in\nlieu of the actual EGFR calculated value. This parameter is\nconfigurable at both the package and division level.\n\n
\nUsed to designate the default verification method presented to\nthe user when verifying laboratory results in the "CH" subscript\nvia options that do not use a load/work list.\nParameter can be set at the package, division or user\nlevel. Division level takes precedence over the package level.\nUser level takes precedence over division level.\nSite can also force verification by UID only.\n\n
\nAllows the user to select the default setting for the "Display \nidentifiers during message selection?" prompt when using OPTION [LA7 \nPRINT LAB UI MESSAGE].\n\n
\nDetermines whether GUI order menus include mnemonics.\n\n
\nReturns the relative date to begin listing appointments for a patient\nacross all clinics. For example, T-30 will begin listing appointments at\nclinics beginning 30 days before now, T will list appointments begin-\nning today.\n\n
\nAfter Anatomic Pathology report is released, this will be the default \nanswer to the "Send an alert" message.\n\n
\nParameter to allow the site/division to indicate which version of SNOMED\nto print or display on Anatomic Pathology reports.\n\n
\nThis parameter holds the name of the default directory\nwhich contains the STS mapping of standard code sets to VistA\nLaboratory system files.\n \nShould be expressed as a full directory specification.\n\n
\nThis parameter holds the number of records to transport per mail message\nwhich contains the STS mapping of standard code sets to VistA\nLaboratory system files. It allows the message size to be adjusted\nto accommodate the various system settings through which the mail\nmessages containing the STS mappings are routed.\n\n
\nThis parameter holds the file specification used to screen which\nfiles is a given directory are presented to the user for loading.\nThese files contain the STS mapping of standard code sets to VistA\nLaboratory system files.\n\n\n
\nThis parameter holds the default when asking the user if they\nwant to specify a specific domain when selecting a facility to\nsend a STS file mapping. It allows the user to override the\nnormal domain associated with an Institution. This is useful when \nsending the mapping to a facility's test system which is usually another\nMailMan domain.\n\n\n
\nThis is the maximum number of days that STS mapping records are kept\nin LAB TRANSPORT MAPPING file (#95.4) before being eligible for purging\nby the Laboratory system task LRTASK NIGHTY.\n\n
\nThis is the value to use for the right margin (column) when formatting\nchemistry/hematology type laboratory reports within a GUI display/client.\n\n\n
\nThis is the value to use for the right margin (column) when formatting\nmicrobiology type laboratory reports within a GUI display/client.\n\n\n
\nReturns the relative date to end listing appointments for a patient at\nall clinics. For example, 'T+30' will not list appointments at the\nclinics after 30 days from now. 'T' will not list appointments later than\ntoday.\n\n
\nThis is the value to use for the right margin (column) when formatting\nanatomic pathology type laboratory reports within a GUI display/client.\n\n\n
\nThis parameter allows the site/division/user to indicate if the ordering\nprovider information should be displayed to the user during microbiology\nresult data entry.\n\n
\nThis parameter holds the name of the directory which contains\nthe processed STS mapping files of standard code sets to VistA\nLaboratory system files.\n \nShould be expressed as a full directory specification.\n\n
\nAllows the package/facility/user to set a default topography presented\nto the user when accessioning specimens into the Laboratory system.\n\n
\nAllows the package/facility/user to set a default collection sample\npresented to the user when accessioning specimens into the Laboratory\nsystem.\n\n\n
\nAllows the package/facility/user to set a default laboratory test presented\nto the user when accessioning specimens into the Laboratory system.\n\n\n
\nAllows package or user to select the default value presented to the user \nwhen building a shipping configuration to the prompt "Exclude previously\nremoved tests from building?"\n\n
\nAllows the user to designate a default performing lab that is\npresented to the user when specifying the performing lab. \nNormally the lab software defaults to the user's institution.\nThis parameter allows the user to specify a different institution.\n\n
\nAllows site/division to indicate when copying surgical case information from\nthe Surgery package during surgical pathology login if a statement is also\nadded to the copied information documenting the source of the copied information.\n\n
\nUsed to allow the user to determine if they want to be prompted\nto send a CPRS alert after editing a microbiology accession.\n \nThe user can indicate:\n 1. They do not want to be asked\n 2. They want to be asked with a default of YES/NO to send an alert.\n\n
\nReturns the relative date to start listing visits for a patient.\nFor example, 'T-90' will list visits beginning 90 days before today.\n\n
\nUsed to allow the user to determine if they want to be prompted\nto send a CPRS alert after editing a Chem/Heme accession.\n \nThe user can indicate:\n 1. They do not want to be asked\n 2. They want to be asked with a default of YES/NO to send an alert.\n\n
\n \nDetermines if the name and address of the:\n 1. Laboratory that is responsible for the report display on the Laboratory report.\n 2. Facility where the report is printed display on the Laboratory report.\n 3. Both names display on the Laboratory report.\n\n\n
\nAllows package or user to select the default value presented to the user \nwhen building a shipping configuration to the prompt "Use default \naccession dates?"\n\n
\nEnter Yes to be prompted for Performing Lab.\nEnter No to not be prompted for Performing Lab.\nThe performing lab is the user's 'Default Performing Laboratory' parameter\nand if the parameter is not set for the user it defaults to the user's\nInstitution (DUZ(2)).\n\n
\nEnter Yes to be prompted for Performing Lab.\nEnter No to not be prompted for Performing Lab.\nThe performing lab is the user's 'Default Performing Laboratory' parameter\nand if the parameter is not set for the user it defaults to the user's\nInstitution (DUZ(2)).\n\n
\nThis data element is used when the User has selected "LAST". This \nsetting keeps track of the User's last response to the prompt.\n\n
\nThis data element is used when the User has selected "LAST". This \nsetting keeps track of the User's last response to the prompt.\n\n
\nUsed when the user has selected "LAST". This setting keeps track of the \nuser's last response to the prompt.\n\n
\nThis parameter is used to control the building of LEDI HL7 result messages\nThe areas are:\n 'CH' = laboratory tests within the "CH" subscript of LAB DATA file (#63).\n 'MI' = laboratory tests within the "MI" subscript of LAB DATA file (#63).\n 'AP' = laboratory tests within the "SP", "CY", and "EM" subscript of LAB\n DATA file (#63).\n \nSelecting "Disabled" disables all sections of laboratory.\nSelecting "Enabled" enables all three main sections ("CH", "MI", and "AP")\non an interface basis for specific messaging partners based on the AGENCY\nassociated with the interface. It allows for the selective\nenabling/disabling of either all result messaging or just result messaging\nin support of specific areas of VistA Laboratory.\n \nIt currently allows for control of the main laboratory areas, also \nreferred to as subscripts or a combination.\n \n\n\nThis parameter is used to control the building of LEDI HL7 order messages\nThe areas are:\n 'CH' = laboratory tests within the "CH" subscript of LAB DATA file (#63).\n 'MI' = laboratory tests within the "MI" subscript of LAB DATA file (#63).\n 'AP' = laboratory tests within the "SP", "CY", and "EM" subscript of LAB\n DATA file (#63).\n \nSelecting "Disabled" disables all sections of laboratory.\nSelecting "Enabled" enables all three main sections ("CH", "MI", and "AP")\non an interface basis for specific messaging partners based on the AGENCY\nassociated with the interface. It allows for the selective\nenabling/disabling of either all order messaging or just order messaging\nin support of specific areas of VistA Laboratory.\n \nIt currently allows for control of the main laboratory areas, also \nreferred to as subscripts or a combination.\n \n\n\nReturns the relative date to end listing visits for a patient.\nFor example, 'T' will not list visits later than today. 'T+30' will not\nlist visits after 30 days from now.\n\n
\nThis parameter controls if a user is allowed to annotate image(s) by checking\nUSER, SERVICE, DIVISION and SYSTEM Levels.\n\n
\nDisplay GUI option Error Lister.\n\n
\nGUI option Global Lister.\n\n
\nGUI option Routine Search.\n\n
\nGUI option Lookups.\n\n
\nGUI option Code Stats.\n\n
\nGUI option Code Evaluator.\n\n
\nGUI option Timing Monitor.\n\n
\nGUI option Timing Monitor.\n\n
\nThis determines if routine collection is done on this day.\n\n
\nGUI option CM Tools Parameters.\n\n
\nDetermine which Environment Check is listed when user signs on:\n \n 0: select (no display)\n 1: HL7\n 2: RUM\n 3: SAGG\n 4: Timing\n\n
\nDisplay GUI option Timing Reports.\n\n
\nThis is incremented to provide a unique session id each time a user signs \ninto EDIS.\n\n
\nThis value overrides the user's DTIME only in the case of the EDIS\napplication.\n\n
\nThis value is the number of seconds used for the countdown when the\ntimeout notification appears.\n\n
\nICB Buffer Reject Reasons\n\n
\nEnter Y (YES) to disable old-style CAPRI logins (default).\nEnter E (ERROR) to disable old-style CAPRI logins and trap attempts.\nEnter N (NO) to leave old-style CAPRI logins enabled.\nEnter L (DEBUG) to leave old-style CAPRI logins enabled but trap attempts.\n\n
\nThis is the URL that CAPRI utilizes to connect to the Virtual VA \nproduction server.\n\n
\nThis is the URL that CAPRI utilizes to connect to the Virtual VA test \nserver.\n\n
\nThis determines if routine collection is done on this day.\n\n
\nThis is the username that CAPRI passes to the Virtual VA web service.\n\n
\nThis is the password that CAPRI passes to Test Virtual VA web service.\n\n
\nThis is the token used to login to the production Virtual VA web service.\n\n
\nThis is the token that is passed to login to the test Virtual VA web \nservice.\n\n
\nThis is the password passed to the Production Virtual VA web service.\n\n
\nEnter the number of days from 1 to 30 to list future appointments for on \nthe nightly Proactive Report.\n\n
\nEnter the number of days from 1 to 30 to list future appointments for on \nthe nightly No Show Report.\n\n
\nOn non-production VistA systems, the text defined by this parameter is \ninserted in the MenuManager prompts. If no text is defined, the \nhard-coded default is " <TEST ACCOUNT>". Suggested alternatives include\n" <LEGACY SYSTEM>"," <CONTINGENCY>", or " <READ ONLY>".\n\n
\nThis is for the ePCS DEA project. It will set the device for the report \noutput.\n\n\n
\nThis parameter allows sites to set what exactly they would like the \nmessage to be that is shown on the signature dialog when a controlled \nsubstance item is checked to be included in signing. This text is \nmandated by the DEA.\n\n
\nThis determines if routine collection is done on this day.\n\n
\nThis parameter determines whether the user will be shown SNOMED CT and \nICD codes when searching for patient problems.\n\n
\nThis parameter allows the routing of the OR PROBLEM LIST NTRT BULLETINS \n(for novel terms which local users are requesting extensions to the \nSNOMED CT standard).\n \nBy default members of the OR CACS mailgroup will receive all Problem List \nNTRT bulletins. This parameter allows routing of requests to mailgroups \nspecific to the division identified by the requestor at log-in.\n\n
\nThis parameter determines the information that is displayed on the popup \ndialog that is presented to the user after successfully linking their PIV \ncard to their VISTA account. Information about contacting an \nadministrative personnel should be included here if they are still unable \nto prescribe controlled substance orders and believe they should have \nthat ability.\n\n
\nMAXIMUM NUMBER OF MESSAGES TO BE INCLUDED IN A DENTAL HL7 BATCH\n\n
\nThe value stored in this parameter will flag the DRM Plus GUI to either \nRequire Radiographs for every exam (or) just periodic/comprehensive exams \nbased on boolean value.\n\n
\nThe DRM Plus GUI application needs to connect to an online document \nlibrary.\n\n
\nThe DRM Plus GUI needs to access an online interactive reporting services \nreport.\n\n
\nThe DRM Plus GUI needs to connect to an online copy of the coding \nstandards.\n\n
\nWhen an Anatomic Pathology (AP) case is accessioned, this parameter will \nhaving any gaps in the accession numbering, however, there is the\npossibility that some accessions might be out of sequence.\n \n'Next Available Sequential Number' - The system will start searching from \nthe last accession number that was logged in, and the next available \nnumber that is found in that accession area will be used as the default \naccession number for the new case being logged in. Choosing this method \nshould better keep the accession numbers in sequence, but there is the \npossibility that some gaps in the numbering might be introduced.\n \ncontrol how the system should assign a default accession number to the \nIf no selection is made, the system will default to 'First Available \nNumber'.\ncase being logged in. (Note: The user will still be able to override the \ndefault, and select a different accession number, if they so choose).\n \n'First Available Number' - The system will start searching from number \none, and the first available accession number that is found in that\naccession area will be used as the default accession number for the new\ncase being logged in. Choosing this method will minimize the likelihood of\n\n
\nThis determines if routine collection is done on this day.\n\n
\nThis field indicates the start date used when the Hospital Location Change \nReport messages were previously generated by TaskMan.\n \nThe purpose of this data is to record the previous start date for the \nreport generated by the TaskMan job.\n\n
\nThis field indicates the end date used when the Hospital Location Change \nReport messages are next generated by the TaskMan option.\n \nCHANGING THIS DATE WILL AFFECT THE INFORMATION REPORTED THE NEXT TIME\nTASKMAN RUNS THE LRJ SYS MAP HL TASKMAN RPT.\nReport messages were previously generated by TaskMan.\n \nThe purpose of this data is to record the previous end date for the \nreport generated by the TaskMan job. It is used to prevent the TaskMan\njob from reporting a Hospital Location change or addition more than once\nand differently than was previously reported.\n \nThis date will be the start date used when the Hospital Location Change\n\n
\nThis field indicates the start date used when the File 60 Audit Report \nmessages were previously generated by TaskMan.\n \nThe purpose of this data is to record the previous start date for the \nreport generated by the TaskMan job.\n\n
\nThis field indicates the end date used when the File 60 Audit Report \nmessages were previously generated by TaskMan.\n \nThe purpose of this data is to record the previous end date for the \nreport generated by the TaskMan job. This date will be the start date \nused when File 60 audit messages are next generated by the TaskMan option.\n \nCHANGING THIS DATE WILL AFFECT THE INFORMATION REPORTED THE NEXT TIME \nTASKMAN RUNS THE File 60 Audit Report.\n\n
\nThis indicates the last start date used when the automatic file \nextractions based on file 60 audits were generated by TaskMan.\n\n
\nThis indicates the end date used when the automatic file extractions \nbased on file 60 audits were generated by TaskMan.\n\n
\nThe purpose of this parameter is to store the number of days before \npending orders will be considered obsolete. When this number of days has\npassed, the order will be canceled in legacy lab and a lapse order status\nupdate will be sent to CPRS.\n\n
\nThis parameter will skip the authentication security that is in patch 62.\n If patch 62 prevents an application from connecting to VistA, then this\n parameter should be set to YES. The default is NO.\n\n\n
\nThis parameter will assign a type to those groups of observations,\nor views, in CLiO that describe an instance of catheter care.\n\n
\nThis parameter holds the current version number of the Virtual Patient\nRecord (VPR) data extract RPC's, in the form V.PP where V is the\npackage version number and PP is the latest patch number.\n\n
\nThis determines if routine collection is done on this day.\n\n
\nThis parameter holds the name of this VistA system, as a hashed base 16\nvalue. It is calculated by a VPR patch post-init and stuffed into the\nSYStem level value, and should NOT be modified.\n\n
\nDevice to print to when a missing dose is requested for a Clinic Order \nmedication.\n\n
\nThis is the URL that CAPRI utilizes to connect to the VLER DAS \ndevelopment channel 3 server.\n\n
\nThis is the URL that CAPRI utilizes to connect to the VLER DAS production \nserver.\n\n
\nThis parameter determines if a terminated user information should be deleted.\n A 'No' value means you do not want to purge the terminated user information.\n This was requested by the OIG when they want all user information preserved.\n A 'Yes' value means to purge the information, which is normal operating procedure.\n\n\n
\nThe EEOB Worklist/Scratch Pad screen within the ERA Worklist option \nprovides the capability to filter the data displayed via the Change View\naction. The Change View action saves the filter preferences by user.\n\n
\nThe AUTO-POST - AWAITING RESOLUTION screen that is generated when\n (e.g.,'R;AE;AEZ') \nNote: The second and third fields of ALL_PAYERS/RANGE_OF_PAYERS are only\n present When the first field is set to 'R' (Range of Payers)\n \nMEDICAL/PHARMACY 1 field: M/P/T/A\nNote: M/P/T/A (M)edical (P)harmacy (T)ricare or (A)ll\n \nSORT 2 fields:N/P/R/U;1/0\nNote: 1st field D=Date/Time ERA Filed, N=Payer Name, P=Amount Posted\n R=Auto Post Reject Reason, R=Unposted Amount\nexecuting the RCDPE AUTO-POST AWAITING RESOLUTION option provides the\n 2nd field H=Highest to Lowest, L=Lowest to Highest\n Null if first field is N or P\ncapability to filter the data displayed via the Change View action. The\nChange View action saves the filter preferences by user.\n \nParameter Instance Possible Value\n \n--------------------------------------------------------------------------\nALL_PAYERS/RANGE_OF_PAYERS 3 fields:A/R;StartWith;GoTo \n\n
\nThe ERA List - Worklist screen within the ERA Worklist option [RCDPE EDI LOCKBOX\n ------------------------------------------------------------------------------\n ERA_POSTING_STATUS 'U':Unposted;'P':Posted;'B':Both\n ERA-EFT_MATCH_STATUS 'N':Not Matched;'M':Matched;'B':Both\n ALL_PAYERS/RANGE_OF_PAYERS 3 fields:A/R;StartWith;GoTo (e.g.,'R;AE;AEZ')\n ERA_AUTO_POSTING 'A':Auto-Posting;'N':Non Auto-Posting;'B':Both\n ERA_CLAIM_TYPE 'M':Medical;'P':Pharmacy;T:Tricare'A':All\n ERA_PAYMENT_TYPE 'Z':Zero;'P':Payment;'B':Both\n AUTO-POST_STATUS 'M':Marked;'P':Partial;'C':Complete;'A':All\n \nNote: The second and third fields of ALL_PAYERS/RANGE_OF_PAYERS are only\nWORKLIST] provides the capability to filter the data displayed via the Change\n present When the first field is set to 'R' (Range of Payers)\nView action. The Change View action allows users to change and save their\nindividual filter preferences.\n \nBelow is a list of the parameter/value pairs (instances) for the Change View \naction, which are stored using this Parameter Definition.\n \n Parameter Instance Possible Value\n\n
\nThese are the Indications for care and their associated ICD-10-CM codes.\n\n
\nThis is an Indication for care which will automatically be filed as the \nindication(s) from the list).\nPrimary Indication for each visit to the applicable Clinic.\n \n(e.g., if all visits to a non-licensed provider should be filed with \nZ79.01 Long term (current) use of anticoagulants , you can specify that\nwith this parameter. If all visits should also have Z51.81 Encounter for \ntherapeutic drug level monitoring as an automatic Secondary Indication for\ncare, you can express that by setting the Auto Secondary Indic for Care\n(ICD-10-CM) parameter. The user will still be able to select additional\n\n
\nThis determines if routine collection is done on this day.\n\n
\nThis is an Indication for care which will automatically be filed as the \nfirst Secondary Indication for each visit to the applicable Clinic.\n \n(e.g., if all visits to a non-licensed provider should be filed with \nV58.83 ENCTR THERAP DRUG MONITOR as the first secondary indication, you\ncan specify that with this parameter, and the user will still be able to\nselect additional secondary indication(s) from the list).\n\n
\nThis is an Indication for care which will automatically be filed as the \nfirst Secondary Indication for each visit to the applicable Clinic.\n \n(e.g., if all visits to a non-licensed provider should be filed with \nZ51.81 Encounter for therapeutic drug level monitoring as the first\nsecondary indication, you can specify that with this parameter, and the\nuser will still be able to select additional secondary indication(s) \nfrom the list).\n\n
\nThis stores the SQL server information so that DocManager Suite can \nconnect to the right SQL server.\n\n
\nThis stores the values for the DocManager configuration file for system \nand user settings.\n\n
\nThis parameter contains settings for the ICB GUI. If installed on an \nexisting system, this parameter will contain the contents of the DSS.ini \nfile for ICB. If DSS.ini did not exist prior to installation, the \npertinent data will be created and stored within this parameter.\n\n
\nThis parameter stores the last IEN found by the ICB process for adding \nnon-ICB buffer entries into the ICB Audit file.\n\n
\nThis parameter is multi-instance for the purpose of knowing which\nancillary products can be launched from within DRM Plus. It enables, or\nhides, the appropriate buttons for the user. For example, DRM Plus can\nlaunch MiPACS to view dental radiographs, and iMedConsent to get required\nconsent forms.\n\n
\nThis is the URL where the Data Warehouse XML is stored.\n\n
\nThis value determines how long the GUI will wait before timing out while \ntrying to connect to the Corporate Data Warehouse.\n\n
\nThis is the URL where the alternate Data Warehouse XML is stored.\n\n
\nThis parameter is used to define the default menu, dialog, or quick order\nthat should appear when the user selects New Consult from the consults\ntab.\n\n
\nThis determines if routine collection is done on this day.\n\n
\nThis parameter contains the URL used to connect to the VA Informatics for \napplication.\nCompensation and Pension (VICAP) system. VICAP is a replacement for the \nAMIS 290 reporting in the AMIE package.\n \nPlacing any value in this parameter has the effect of disabling the AMIS\n290 for the Regional Office [DVBA C RO AMIS 290] and AMIS 290 Report for\nC&P [DVBA C AMIS REPORT] options in VistA, the corresponding AMIS 290 and\nAMIS 290 by Division reports on the CAPRI Reports dialog box, and the AMIS\n290 report on the Consolidated Remote Reports dialog box in the CAPRI GUI\n\n
\n'Yes' will change the way Date Ranges are selected on the Reports\nand Labs Tabs in CPRS, using Radio Buttons to make selections rather\nthan from a list.\n\n
\nThis defines the preferred report to be shown when selecting the Labs Tab.\nThis report also will be the first one listed in the list of reports.\n\n
\nThis is a switch that the CPRS GUI will use to enable specific logic for \nsites that are over the international date line\n\n
\nThis defines the default date value for the CLINICALLY INDICATED DATE \nfor the CID will retain that value. If that quick order should reflect \nthe parameter value, simply remove the current default value for the \nquick order and save the change. The quick order would then default\nto the parameter value.\n(CID) field in consult and procedure orders. This date value can be \nTODAY or greater and must be a relative date (e.g. "TODAY", T+7D, "T+2W").\nPast dates and precise dates are not permitted. The date value may also \nbe a null/empty date, which is set by deleting (via XPAR MENU TOOLS) the\ncurrent value for the parameter (if one is set).\n \nAny new orders in CPRS GUI and new quick orders will default to the \nparameter value. Any quick orders that currently have a default value \n\n
\nThis parameter is used to store the current server version of the CPRS\nMed Order Button (MOB) DLL. This value is used to check against a user's \nclient version.\n\n
\nThis parameter is used to specify the name to use for the YS_MHA_A dll \n\n
\nThis parameter holds the current version number of the eHMP Patient\nRecord (HMP) data extract RPC's, in the form V.PP where V is the\npackage version number and PP is the latest patch number.\n\n
\nThis parameter holds the name of this VistA system, as a hashed base 16\nvalue. It is calculated by a HMP patch post-init and stuffed into the\nSYStem level value, and should NOT be modified.\n\n
\nThis parameter stores a list of parameters used by the HMP middle teir \nand the HMP UI.\nwhenever the schema changes in a way that requires a conversion or \nre-extraction of objects. The fractional piece increments whenever the \nschema is extended.\n\n
\nMultiple instances of this parameter combine to form a list of the display\ngroups shown in the order review screen. Orders are displayed by the\nsequence identified in this list.\n\n
\nThis contains the version number of the HMP schema which describes the\nJSON objects produced by the HMP extracts. The whole number increments\nwhenever the schema changes in a way that requires a conversion or\nre-extraction of objects. The fractional piece increments whenever the\nschema is extended.\n\n
\nThis is the number of seconds that the system will wait before re-queuing\nthe HMP Data Monitor background job.\n\n
\n This parameter contains a list of VPR extract domains and their average\n sizes. The sizes are used in computing the approximate size of an item\n with limiting the freshness calls by size.\n\n
\nMaximum size (megabytes) of all VPR extracts in ^XTMP("VPRFX~*") waiting\n will hang the number of seconds specified by the VPR EXTRACT TASK REQUEUE\n SECS parameter. The maximum check will occur again after the hang time\n has expired.\n \n This limit is needed to insure the ^XTMP global does not get too big\n during initial/resync domain extract processing and cause disk full \n errors.\n to be sent to HMP servers as part of getPtUpdates.\n \n If maximum is reached, patient domain extract TasKman jobs will be\n requeued to a future time, as specified in the VPR EXTRACT TASK REQUEUE\n SECS parameter. At that time, this maximum check will be performed again.\n \n Also, this maximum check occurs when an executing extract job is about to\n start another domain extract. If maximum size has been reached, the job\n\n\nWhen extract task cannot be run because of possible ^XTMP disk concerns,\n Default: 10 (if parameter not set)\n Initialized: 10 (set in post-init during first install)\n this parameter is used to requeue the task to a future date/time or hang\n an extract job currently executing.\n \n ^XTMP disk space frees up as other already generated extracts are sent to\n the various HMP servers.\n \n Allowed Values: 5 to 60 (5 seconds to 1 minute)\n \n\n
\nTHIS PARAMETER IS USED TO EXCLUDE CWAD NOTE TITLES, WHICH ARE MAPPED TO\nTHE SELECTED VHA ENTERPRISE STANDARD TITLES, FROM THE AUTO-DEMOTION\nFUNCTIONALITY.\n\n
\nThe number of days in time to search backwards for consults/requests. If\nnot indicated, the default period of 730 days (2 years) will be used. The\nmaximum number of days is 100,000 or about 220 years.\n\n
\nThis parameter is used to determine whether lab results are sent to the\nauto release process.\n\n
\nContains the list of which contact info for the ordering provider to send \nThe sequence specifies the order and info to check, maximum of 6 allowed.\nOnly the first 2 with a value will be placed in the message as the HL7\nstandard constrains the number of repetitions for this information at 2.\n \nThe value specifies which field from the person's entry in NEW PERSON \nfile (#200) to send in the message.\n \nThese are the fields currently available.\n \nField # Field Name Description\nin a Lab HL7 Order message from the user's corresponding entry in NEW \n \n.131 PHONE (HOME) This is the telephone number for the new\n person.\n \n.132 OFFICE PHONE This is the business/office telephone for the\n new person.\n \n.133 PHONE #3 This is an alternate telephone number where the\n new person might also be reached. \n \nPERSON file (#200).\n.134 PHONE #4 This is another alternate telephone number\n where the new person might also be reached.\n \n.135 COMMERCIAL PHONE This is a commercial phone number.\n \n.136 FAX NUMBER This field holds a phone number for a FAX \n machine for this user. It needs to be a format\n that can be understood by a sending MODEM.\n \n.137 VOICE PAGER This field holds a phone number for an ANALOG\n \n PAGER that this person carries with them.\n \n.138 DIGITAL PAGER This field holds a phone number for a DIGITAL\n PAGER that this person carries with them.\n \n \nThe parameter is distributed pre-configured at the package level as \nfollows:\n \n Sequence Value\nIt can be specified at the system or the individual user level. If\n -------- -----\n 1 OFFICE PHONE\n 2 DIGITAL PAGER\n 3 VOICE PAGER\n 4 PHONE #3\n 5 PHONE #4\n 6 PHONE (HOME)\n 7 COMMERICAL PHONE\n 8 FAX NUMBER\nspecified at the user level it takes precedence and overrides the setting\nat the system level allowing specific users to have their own specific set\nof contacts to send.\n \n\n
\nAllows site to specify the number of days of instrument data to keep in \nLAH global before it's automatically purged by nightly process.\n\n
\nColors for Foreground (FG) or Background (BG) of Screen\n\n\n
\nUse this Parameter to DISENABLE use of the mouse in ScreenMan\nsystem-wide, or for an individual user.\n\n
\nThis activates or deactivates the display of PADE drug balances when \ndoing Dispense Drug lookups in Inpatient Order Entry.\n\n
\nWhen a skin test reading is being recorded, this is the number of days the\nsystem should search back to find a corresponding skin test placement.\n\n
\nMethod for sorting notifications when displayed in the CPRS GUI. Methods\ninclude: by Patient, Message (text), Urgency, Info, Location, Date/Time,\nand Forwarded By/When.\n\n
\nCommon Body sites for all lists. Delimetered by "|" as follows:\n \nExample: text|1|0\n text|1|1\n text|0|1\n \n piece 1 = Site text description\n piece 2 = 1 or 0 for yes or no is an Injection site\n piece 3 = 1 or 0 for yes or no is a Dermal site\n\n
\nThis will store the number of days for the Last Dermal Site History \ntimeframe used by the BCMA GUI Site Parameters application and for \npassing to BCMA RPC PSB GETNINJECTIONSITE.\n\n
\nUsed to designate the default release action presented to the user when\nverifying automated microbiology results in the "MI" subscript via options\nthat use a load/work list. Parameter is associated with the load/worklist\nselected by the user.\n \nParameter can be set at the package or user level. \nUser level takes precedence over package level.\n\n
\nThis parameter controls the behavior of option eHMP Dashboard [HMPMON\nparameter template HMPMON DASHBOARD PKG, accessed through menu option Set \nPackage's Dashboard Auto-update Rate [HMPMON SET PKG DASHBOARD RATE], \nwhich should not be changed at local sites;\n \n2) a system setting that will override the package setting; it can be \ndefined by the local system manager using parameter template HMPMON \nDASHBOARD SYS, accessed hrough menu option Set System's Dashboard \nAuto-update Rate [HMPMON SET SYS DASHBOARD RATE];\n \n3) a user setting that overrides the other two; it is defined by the \nDASHBOARD]. Most of this option's prompts time out normally, but its \ncurrent user using parameter HMPMON DASHBOARD USR, accessed by the \ndashboard action Change Auto-update Rate action within option eHMP\nDashboard [HMPMON DASHBOARD].\n \nIt is usually set to 3 to 30 seconds, but can be set as high as 300 \nseconds to support demonstration or teaching situations. If it is wholly \nabsent, the user's default Vista time-out rate is used.\nAction Prompts control monitoring screens that auto-update the screen when\nthey time out, to provide dashboard functionality for monitoring the \nVista-side eHMP software.\n \nThis parameter ships with three settings:\n \n1) a package default setting, defined by the eHMP development team using\n\n
\nThis parameter defines the host system default directory where XTMPSIZE.DAT\ncan either be read or written. It must be a directory where the user\nhas read/write privileges.\n\n
\nThis parameter is used to turn on the functionality delivered in \nOR*3.0*420. The functionality will display the most recent LAB order \nresults associated with a drug orderable item when selected in the \nPharmacy Ordering Dialog.\n\n
\nThis saves the preferred default font size for the VistA Scheduling \nletters.\n\n
\nDate/time this user last review the patient's orders.\n\n
\nParameter to hold the filter preference set for the Request Manager Grid.\n\n
\nThis parameter is used to store the GUI version that is compatible with the\ncurrent server version on the TIU Mobile Electronic Documentation application.\n\n
\nThis parameter works in conjunction with the ORWRP VISTAWEB\nADDRESS parameter for viewing external remote data using the\nWEB. VistaWeb has been the vehicle for viewing external remote\ndata, but the VA is transitioning to a new vehicle called JLV\n (Joint Legacy Viewer). When a site moves to JLV, this parameter \nvalue will need to be set to "JLV" and the URL will need to be \nupdated to point to the JLV website.\n\n
\nThis parameter is used to store the name of the .dll on the file system \nof the CPRS users of this VistA system.\n\n
\nThis parameter allows sites to set what text they would like the users to \nsee when placing a Return To Clinic Order.\n\n
\nThis parameter determines which Problem selection list the user will be \nshown when adding a new patient problem.\n\n
\nThis parameter holds imaging user preferences by\nUSER, DIVISION and SYSTEM levels.\n\n
\nThis value controls if the Permitted Ward Stock Level is displayed on the\nscreen and reports when nurses enter ON-DEMAND WARD STOCK REQUEST. 1:Yes\ndisplays the Permitted Ward Stock Level and 0:No does not display the\nPermitted Ward Stock Level.\n\n
\nPackage, System, Division indicate the clinical danger level of an order\ncheck. Valid levels include High, Moderate, Low. The clinical danger \nlevel is used in sorting for order check display and prompting for override.\n\n
\nThis parameter contains the full URL that points to the Joint Legacy Viewer for a given patient.\n\n
\nThis parameter allow you to specify a name and location for the Mental\nlike this:\n \n AUX DLL: G:\\Shared\\YS_MHA_AUX.dll\n \nIf you wish to specify a location relative to %PROGRAMFILES%, begin the \nentry with a single "\\". For example, using a different directory and\nname, but remaining in "C:\\Program Files (x86)":\n \n AUX DLL: \\Vista\\TestMHA\\YS_MHA_AUX_new.dll\n \nHealth Assistant AUX DLL. There is no need to use this parameter if the\nRemember to use "\\" and not "/" in the directory path.\nAUX DLL is in the default location. The default location is:\n \n %PROGRAMFILES%\\Vista\\Common Files\\YS_MHA_AUX.dll\n \nIf you wish to specify a different location, or use a different name for \nthe DLL, you may specify it in this parameter. For example, to specify \nnetwork drive "G:" in the Shared directory, you might enter something \n\n
\nThis parameter stores the number of seconds for which chunked dental \nreports will hang every 50,000 records read.\n\n
\nThis parameter stores how many lines are to be returned per execution of \nDental Reports data retreival RPC executions.\n \nIt is set to 200 lines by default.\n\n
\nThis parameter contains the URL to be used for GUDID lookup in the GUI.\n\n
\nThis parameter determines how long the GUI will wait before timing out \nwhile trying to connect to the GUDID lookup.\n\n
\nThe purpose of this parameter is to store the number of months that old \nDrug Audit data will be retained in the DRUG (#50) file. If this value is\nnot set, or set to 0, then all audit data will be retained in the file. \nIf set to a whole number value, this value will be multipled by 30 to\nformulate the date that will be the last date of data stored in the file\n(i.e.: \n2 mos. X 30 = 60, Today's date - 60 will be the lower limit of the data \nstored).\n\n
\nA unique three-digit number to identify this VistA facility for One \nConsult.\n\n
\nAllows package or user to select the default value presented to the user \nwhen building a shipping configuration to the prompt to start a new \nshipping manifest when an open one does not exist.\n\n
\nFlag indicating if an order check should be processed for a certain set of\ncircumstances. An order check can be Enabled or Disabled. Only Enabled\norder checks will be processed.\n\n
\nThis parameter is used to turn on the functionality delivered in \nXU*8.0*679. The parameter will allow a site to only provide the Signature\nBlock edit in the NEW PERSON (#200) file to individuals that have the XU\nSIG BLOCK EDIT security key assigned in their NEW PERSON (#200) file\nentry.\n\n
\nThis parameter is used to turn on or off the display of two comments \nfields for CPRS orders. The display of Flagged Order Comments, and the \nDisplay of Ward Comments. \n\n
\nThe Order Urgency "ASAP" is not desired at all sites. This is where a \nsite designates their desired alternative to the default "ASAP"\nurgency for the\nGive Additional Dose Now order in CPRS.\n\n
\nThis parameter determines the number of days to retain reports.\n\n
\nThis parameter holds the date that the Above PAR report cleanup code was\nlast executed. \n\n
\nThis parameter defined earliest start date for the Above PAR Audit Report\n\n
\nThis parameter determines whether or not a user has administrator \nprivileges to the Above PAR package.\n\n
\nThis parameter determines whether or not a user has Equipment \nadministrator privileges to the Above PAR package.\n\n
\nThis parameter determines whether or not a user has Work Order \nadministrator privileges to the Above PAR package.\n\n
\nThe number of days in time to search backwards for consults/requests. If\nnot indicated, the default period of 730 days (2 years) will be used. The\nmaximum number of days is 100,000 or about 220 years.\n\n
\nThis parameter determines whether or not a user has Inventory \nadministrator privileges to the Above PAR package.\n\n
\nThis parameter determines whether or not a user has Work Order \nTechnician privileges to the Above PAR package.\n\n
\nThis parameter defined the default starting screen for an Inventory User.\n\n
\nThis parameter defines the default starting screen for an Equipment User.\n\n
\nThis parameter defines the default starting screen for a Work Order User.\n\n
\nContains various parameters for Equipment such as would be found in a GUI\n.ini file (# of records to return, default document directory, etc.).\n\n
\nContains various parameters for Inventory such as would be found in a GUI\n.ini file (# of records to return, etc.).\n\n
\nContains various parameters for Equipment that would be normally found in \na .ini file (# of records to return, default document directory, field \ndisplay and edit requirements, etc.).\n\n
\nThis parameter determines whether or not a user is an Equipment \nTechnician to the APAR package\n\n
\nThis parameter defined which function (tab) of APAR the user will start \nin. A system parameter can be set as well in case the user has not yet \nbeen set up.\n\n
\n'Yes' indicates a MailMan bulletin will be sent to the order's Current \nProvider (usually the Ordering Provider) when the order is flagged for\nclarification. This parameter has no effect on the Flagged Orders\nnotification which is also triggered when an order is flagged for\nclarification.\n\n
\nThis parameter determines the number of days to retain audit data in \nAbove PAR.\n\n
\nThis parameter authorizes an Equipment User to use the Bulk-Edit Process\n\n
\nThis parameter determines whether or not a user has the rights to run \nBulk-Edit in Work orders\n\n
\nThis parameter determines whether or not a user has the right to run \nBulk-Edit process in Inventory\n\n
\nThis parameter defines the number of days to keep old bulk-edit session \ndata.\n\n
\nThis parameter authorizes a Work Order User to edit their own open work \norders. If this flag is not set for a user, they are only allowed to add \nnew Work Orders\n\n
\nThis parameter contains all across-the-board Above PAR user settings\n\n
\nThis parameter disables the APAR Equipment interface for a given user\n\n
\nThis parameter disabled the APAR Work Orders interface for a given user\n\n
\nThis parameter disables the APAR Inventory interface for a given user\n\n
\nThe number of days backwards in time to search for lab orders/results. If\nnot indicated, the default period of 2 days will be used. The\nmaximum number of days is 100,000 or about 220 years. For inpatients.\n\n
\nThis parameter disables the APAR ADHOC Reporting interface for a given \nusers\n\n
\nThis parameter disables the APAR Images for the system\n\n
\nThis parameter disables the Barcode interface for the system\n\n
\nThis parameter determines whether or not a user has the right to edit \nInventory Quantities or Adjust On-Hand Values\n\n
\nThis parameter determines whether or not a user has access to the DSIY \nADHOC REPORTING.\n\n
\nThis parameter enables the APAR access to the Item Master File for a \ngiven user\n\n
\nContains various parameters for Inventory Item Master File such as would \nbe found in a GUI .ini file (fields to edit/audit, etc.).\n\n
\nThis parameter enables/disables the Debugging Log for this user\n\n
\nContains various parameters for Vendor such as would be found in a GUI \n.ini file (# of records to return, default document directory, etc.).\n\n
\nThis parameter disables the APAR Purchase Orders interface for a given \nuser\n\n
\nContains the list of common outpatient meds for display at the top of the\nMeds listbox in the GUI ordering dialog.\n\n
\nThis parameter disables the APAR Vendor interface for a given user\n\n
\nThis parameter determines whether or not a user has PO administrator \nprivileges to the Above PAR package.\n\n
\nThis parameter determines whether or not a user has Vendor administrator \nprivileges to the Above PAR package.\n\n
\nThis parameter determines whether or not a user has PO manager privileges \nto the Above PAR package.\n\n
\nThis parameter determines whether or not a user has Vendor manager \nprivileges to the Above PAR package.\n\n
\nThis parameter determines whether or not a user has Vendor user \nprivileges to the Above PAR package.\n\n
\nThis parameter determines whether or not a user has Vendor User \nprivileges to the Above PAR package.\n\n
\nDefines the start screen a user sees in the Purchase Order tab.\n\n
\nThis parameter determines whether or not a user has Purchase Order \ncreation privileges to the Above PAR package.\n\n
\nThis parameter determines whether or not a user has Vendor creation \nprivileges to the Above PAR package.\n\n
\nThe number of hours back in time to look for duplicate orders. For example,\na value of '24' indicates if a duplicate of the orderable item was placed\nwithin the previous 24 hours, an order check indicating duplicate order \nwill occur. A value of '0' (zero) indicates do not check for duplicates -\nduplicate order checking for this orderable item will not occur.\n\n
\nContains DataMiner INI parameters.\n\n
\nContains DataMiner system parameters.\n\n
\nThis parameter determines whether or not a user has administrative \nprivileges to the DataMiner package.\n\n
\nThis parameter determines if a user is a DataMiner Manager.\n\n
\nDataMiner User Parameter\n\n
\nDataMiner User Settings\n\n
\nThis parameter disables the APAR EQ Images for the system\n\n
\nThis parameter disables the APAR WO Images for the system\n\n
\nThis parameter disables the APAR PO Images for the system\n\n
\nThis parameter disables the APAR GIP Images for the system\n\n
\n'Yes' indicates the user can Digitally Sign Schedule II Medication orders.\n\n
\nThis parameter defines the number of minutes to wait before shutdown. It \nwill contain a value of 0,5,10,15,or 20.\n\n
\nThis parameter only applies to a search initiated by Taskman when the\nthat a session is disconnected after verification but before the alert is \nqueued.\noption "Missing AP Alert Search" is defined to run automatically in\nTaskMan. Users may manually run the search using the option "Missing AP\nAlert Search" without affecting the date/time set in this parameter.\n \nThe value for this parameter equals the last date/time that was searched \nin order to find verified Anatomic Pathology cases which did not have an \nalert generated. Some sites are finding that alerts do not generate at \ntimes. The issue cannot be reproduced at will. A suspected cause is \n\n
\nThis the current version of AntiCoagulate.exe.\n\n
\nThis contains the date/time when the re-scoring of instrument\nscoring revision 1). Subsequent runs will likely be for a single\ninstrument with an instance value of "instrumentIEN~revision".\nadministrations done as part of YS*5.01*123 was completed.\n \nIt may also be used subsequently if an instrument needs to be\nre-scored again due to some correction (such as changes to\nscoring keys, choice text, etc.)\n \nEach instance represents a re-scoring run. This initial run for\npatch 123 is represented by "0~1" (re-score all instruments to\n\n
\nThis is the number of hours that the background computation of MHA\nscores should run per day. The tasks re-queues itself each day and\nstops when results for all instruments are recorded.\n\n
\nThis contains the current status of re-indexing the "AC" index of the\nMH RESULTS and MH ANSWERS files.\n\n
\nThis parameter is used to make the two unified action profile menu \nchoices, ("UAP" and "Discharge Meds" available in CPRS under the Views\nMenu. These two menus on the views drop down menu, when activated, allow\nclinicians to use the Unified Action Profile Function.\n\n\nThis parameter is used to store the GUI version that is compatible with the \ncurrent server version on the CRHD shift Change Handoff application\n\n
\nThis parameter is used in determining user security for the APAT \napplication.\n\n
\nParameter determines if any order checking will occur. 'E' or 'Enable'\nindicates order checking is enabled and running. 'D' or 'Disabled'\nindicates order checking is disabled and not running. Can be set at the \nInstitution, System, or Package level.\n\n
\nDefault APAT system location and title indexing values.\n\n
\nParameter to set system settings for a site.\n\n
\nThis parameter contains the number of Prosthetics Suspense items to \nprocess per execution.\n\n
\nThis parameter contains the maximum number of Prosthetic Suspense items\n(file 668) to read before returning data.\n \nMaximum Value = 1000\nDefault Value = 500\n \nMaximum Number of Records Returned = Parameter Value / 2\n\n
\nThis parameter contains the maximum number of Prosthetic 2529-3 records\n(file 664.1) to read before returning data.\n \nMaximum Value = 1000\nDefault Value = 500\n \nMaximum Number of Records Returned = Parameter Value / 2\n\n
\nThis parameter contains the last Record of Pros Appliance/Repair (#660)\nIEN processed by the APAT Appliance Transaction Extract.\n\n
\nThis parameter contains the number of Record of Pros Appliance/Repair \nrecords (#660) to process per run.\n\n
\nThis parameter allows the for the APAT GUI to show the entire Purchase \nCard number.\n\n
\nThis parameter contains the number of Appliance Transactions to return \nfrom the Record of Pros Appliance/Repair (#660) per batch when processing\noption DSSO APPL TRANS EXT - ALL. \n \nSince the Description of Item/Services from the Prosthetic Suspense (#668)\nfile is extracted for each appliance transaction, the size of one extract\nrecord can be up to 10K. Parameter DSSO APPL TRANS PER BATCH defaults\nto 250 for this reason. The upper limit for this parameter is 1000 \ntransactions per batch.\n\n
\nThis defines the preferred menu to select from when adding new orders,\ntypically containing package ordering dialogs, quick (pre-answered) orders,\nor sub-menus.\n\n
\nThis parameter contains the number of seconds for which the HL7 Appliance \nTransaction Extract will hang between batches when processing option \nDSSO APPL TRANS EXT - ALL. Allowed values of this parameter are 1 - 5\nseconds.\n\n
\nThis parameter contains the value for the number of seconds the APAT DAT \nPrePopulator will hang if too many records are being processed. This \nwill allow TaskMan to continue with other processes.\n\n
\nThis parameter stores the value for the number of hours which the APAT \nDAT PrePopulator will run for any single execution.\n\n
\nThis parameter contains the last 660 IEN processed by the APAT DAT\nPrePopulator.\n\n
\nThis parameter contains the value for the number of records that are to \nbe processed by the APAT DAT PrePopulator in a single execution.\n\n
\nThis parameter holds the date from which the APAT DAT PrePopulator will \npopulate data. It is initialized during installation to three years back \nfrom the current date.\n\n
\nThis parameter contains the date on which the Appliance Transaction \nExtract was installed.\n\n
\nThis parameter specifies the fully-qualified server address of the Above\nPar exe at this site. This address is not required and can be blank.\n\n
\nThis parameter specifies the fully-qualified server address of the \nNational DAT Tracker SQL Connection. This address is not required and \ncan be blank.\n\n
\nThis paramater is set by the users adjusting the Unit Dose column width.\nIt is stored in the format nnn/nnn/nnn/nnn/nnn/nnn/nnn/nnn/nnn.\n\n
\nThis parameter indicates the default value of the Receiving Required? \nfield on the detailed purchase order.\n \nAcceptable values are: 1=Yes, receiving is required\n 0=No, receiving is not required\n \nDefault value: 1=Yes - receiving is required\n\n
\nThis parameter indicates whether DSSO 2.0 has been installed yet in \norder to determine whether to reset the parameters for the Prepopulator \nand the DAT Tracker.\n\n
\nThis parameter contains the last Prosthetic Suspense IEN handled by the \nAPAT/EPS Integration task.\n\n
\nThis parameter determines whether or not a user has access to GIP \nInventory functionality through APAT/Above PAR.\n\n
\nThis parameter determines whether this person has the authority to manage \nGIP users through APAT/Above PAR.\n\n
\nThis parameter is used to determine if CPRS should show the other \ninformation panel or not.\n\n
\nThis parameter is used to determine if the other information panel should \nuse colors to help show the urgency of data.\n\n
\nThis parameter is used to determining if CPRS should allow a report box to\nshow if the user clicks on the other information panel.\n\n
\nThis is the Clinical Reminder definition to use to evaluate and determine \nthe text that shows on the other information panel in CPRS.\n\n
\nThis parameter determines how the GUI banner displays patient flags.\n0=No, 1=Yes\n \nIf no value is set, the default behavior is to display patient flags in \nthe banner.\n\n
\nNOTE: This parameter should only be edited with the TIU TEMPLATE CONSULT \nOnce a TIU TEMPLATE is added as a value for this parameter, that template,\nand all template fields used by that template shall be locked for edit in\nthe CPRS GUI Template and Template Field editors. This locking is \nintended to prevent any unwanted changes to the Template or Template \nField content.\n \nFor example, the TIU TEMPLATES associated with non-VA care consults for \nHemodialysis and Peritoneal Dialysis are NON VA CARE HCPS HEMODIALYSIS \nand NON VA CARE HCPS PERITONEAL DIALYSIS. These consults are transmitted \nvia HL7 to the Referral & Authorization System (RAS) database. Any edits \nLOCK option found on the TIU IRM TEMPLATE MGMT menu. This parameter \nto the content of these Templates can cause transmission errors with RAS\nand therefore delay patient care.\nshould never be edited via the General Parameter Tools menu [XPAR MENU \nTOOLS].\n \nValues for this parameter should be TIU TEMPLATE file entries that are \nused for consult services. A template must first be linked to an\nAssociated Consult Service before it may be used in this parameter.\n \n\n
\nThe date stored in this parameter is used to denote the start date of the \ndate range used when searching for pending/active imaging orders. These \norders are included in the pregnancy/lactation unsafe order review\nnotification in the Computerized Patient Record System (CPRS).\nPending/active imaging orders with a start date before this date are\nignored.\n\n
\nThis parameter stores a set of predefined reasons that are presented to \nthe user when he/she is marking a pregnancy or lactation status as \nentered in error.\n\n
\nThis parameter stores website names and hyperlinks that are displayed to \nthe user when he/she right-clicks on the Women's Health panel on the CPRS \ncover sheet.\n\n
\nThis parameter is used to turn on/off Reminder Evaluation of the \ncoversheet when the user complete a Reminder Dialog.\n\n
\nThis parameter contains the email address of the Healthcare Claims \nrequested by either the Austin FSC and/or other national-level guidance.\nProcessing (HCP) support group located at the Austin Financial Services \nCenter (FSC). This email address is used by the CONSULT/REQUEST TRACKING \npackage to send messages to the FSC when an HL7 transmission to the HCP \nencounters an error. The email address in this parameter is added as an \nadditional recipient to the existing message sent to the GMRC HCP HL7 \nMESSAGES VistA mail group.\n \nThis parameter's value should not be changed unless specifically \n\n
\nThis sets the way an application will identify copy/paste text. The \nnumeric values, but are required to be positive if the previous entry is\nset to 1. For example, an entry of "0,0,1,1,65535,0,0,0,0,0,-16777208,\n5000" (B,I,U,HL,HLC,DO,DB,DI,DUL,FCO,FC,CL) would result in copy/paste\ntext being Highlighted in yellow and Underlined while the Difference\nIdentification identifiers would be disabled. The twelfth piece is a \nnumeric value representing the max characters allowed for the difference \nidentifier to operate.\n \n \n Piece Description\navailable selections for the NOTE copy/paste identifiers are Bold (B),\n 1 Bold (Note): 1 = on, 0 = off\n 2 Italicize (Note): 1 = on, 0 = off\n 3 Underline (Note): 1 = on, 0 = off\n 4 Highlight (Note): 1 = on, 0 = off\n 5 Highlight Color (Note): numeric color representation used\n in CPRS gui\n 6 Difference Identifier Toggle (ON/OFF): 1 = on, 0 = off\n 7 Bold (difference identifier): 1 = on, 0 = off\n 8 Italicize (difference identifier): 1 = on, 0 = off\n 9 Underline (difference identifier): 1 = on, 0 = off\nItalicize (I), Underline (UL), Highlight (HL), and Highlight Color (HLC),\n 10 Text Color On (difference identifier): 1 = on, 0 = off\n 11 Text Color (difference identifier): numeric color\n representation used in CPRS gui\n 12 Character Limit (difference identifier): numeric value that\n defines the max characters allowed for the difference\n identifier function to operate.\n \nTo turn off the user visual components for copy/paste tracking, the\nvalue "-1;Visual Disable Override" may be entered without the\nquotations. It must be entered exactly as shown.\nThe difference identifier contains six additional pieces. They are\nDifference Identifier On (DO), Bold (DB), Italicize (DI), Underline\n(DUL), Font Color On (FCO), Font Color (FC), and Character Limit (CL).\nThis data must be entered as 12 comma delimited entries. The first four\npieces, as well as pieces six through ten, are mandatory binary (1 or 0)\nentries. The fifth and eleventh pieces will accept positive or negative\n\n
\nPCMM Team list to be default source of patients.\n\n
\nThis parameter allows sites to designate applications (.exe) that will not\nbe considered copy/paste if encountered in the Windows copy clipboard. This\nfeature allows a site to filter out some applications that utilize the\nWindows copy clipboard as part of their functionality. This will prevent\ntext from being mistakenly identified as copied by the user when the user\ndid not actually copy any text.\n\n
\nThis is the message that will inform the user on who to contact in case of issues with CPRS.\nExample: "your local CPRS help desk" or "your local IRM". \nThis will be used in sentences such as "Please contact your local help desk to obtain the updated version of the DLL" or\n"Please contact your local IRM to obtain the updated version of the DLL"\n\n
\nWhen the Exception Logger is enabled (OR CPRS EXCEPTION LOGGER) the user has the ability to pre populate an email through Microsoft Outlook. \nIf this paramater is not empty than the user can email the error log and this email address will be used for the pre population of that email. \n\n
\nWhen an error occurs and the Exception Logger is enabled (OR CPRS EXCEPTION \nLOGGER), then any file(s) that are older than the number of days set in \nthis parameter will be removed from the user's machine.\n\n
\nWhen this parameter is set to "yes" the application will display a custom \naccess violation screen to the user as well as logging the error stack and \nallowing this to be sent via an email (if OR CPRS EXCEPTION EMAIL is not blank). \nThe log files are currently stored in the following folder \n"C:\\Users\\USER'S VHAID\\AppData\\Local\\APPLICATION NAME\\Unique Log File Name.txt". \nExample: C:\\Users\\VHAISPUSER\\AppData\\Local\\CprsChart.exe\\CPRS_16136_01_13_16_16_43_LOG.TXT\n\n
\nThis parameter allows sites to set what text they would like for users to \nsee when viewing the Release orders screen for an inpatient on writing \ndelayed orders.\n\n
\nThis parameter allows sites to set what help they want to define for the \nuse of the Release orders screen. Value should be a url. If this is \ndefined, when the Release orders screen is loaded a button/link will \ndisplay that when clicked will open the url in the user's default browser.\n\n
\n'Yes' disables the display of the ONE STEP CLINIC ADMIN menu item found\non the ACTION menu on the ORDERS TAB in CPRS.\n'No' will allow the display of the ONE STEP CLINIC ADMIN menu item.\n\n
\nThis parameter is used to map reminder list rules to team lists. This is \nused to automate the process of updating a team list from a reminder list \nrule. \n \nThis parameter should only be edited via the option Automate List Rule to\nUpdate List [ORLP SETUP TEAM LIST FROM REM].\n\n
\nThis parameter is used to control how often a reminder list rule should be\nran to update the team lists.\n \nThis parameter should only be edited via the option Automate List Rule to\nUpdate List [ORLP SETUP TEAM LIST FROM REM].\n\n
\nThis parameter will be set to the last time a reminder list rule was ran\nas part of the process of updating a team list.\n \nThis parameter should not be defined manually, but will be defined by the \ntasked option Update Team List From Reminder List Rule [ORLP TEAM LIST\nFROM REM].\n\n
\nSpecifies a date range (in days) for Meds tab display that dictates the \nORDERS parameter accordingly.\n \nI no value exists for this parameter, then the value found in the \nparameter ORCH CONTEXT MEDS will be used.\nlength of time INPATIENT orders are displayed. The parameter provides strings \nof delimited ("; ) pieces, the first two of which are always a relative date \nrange. Users can determine the date range of medications that display on \nthe Medications tab through the Tools|Options pull-down menu in CPRS.\n \nThis parameter functions independently of display settings for the \nOrders tab. If you need to alter the display range for expired \nmedication orders on the Orders tab, please adjust the ORWOR EXPIRED \n\n\nSpecifies a date range (in days) for Meds tab display that dictates the \nmedication orders on the Orders tab, please adjust the ORWOR EXPIRED \nORDERS parameter accordingly.\n \nI no value exists for this parameter, then the value found in the\nparameter ORCH CONTEXT MEDS will be used.\nlength of time OUTPATIENT and Non/VA orders are displayed.\nThe parameter provides strings of delimited ("; ) pieces,\nthe first two of which are always a relative date range.\nUsers can determine the date range of medications that display on \nthe Medications tab through the Tools|Options pull-down menu in CPRS.\n \nThis parameter functions independently of display settings for the \nOrders tab. If you need to alter the display range for expired \n\n\nThis parameter determines the text to display in CPRS when a discontinue\nis no longer allowed to be signed because the Laboratory has processed\nthe order.\n\n
\nThis parameter is used to control whether the previous Reminder Patient \nList should be overwritten when updaing an OE/RR List.\n \nThis parameter should only be edited via the option Automate List Rule to\nUpdate List [ORLP SETUP TEAM LIST FROM REM].\n\n
\nThis parameter is used to identify segments of text that should be \nexcluded from the mix case functionality within CPRS.\n\n
\nThis parameter allows sites to disable the use of the copy/paste copy\nbuffer. When disabled, the CPRS GUI application will no longer save\ncopy text data to VistA for copy/paste tracking utilization.\n\n
\nThis parameter set the Right Margin value for CPRS Banner.\n\n
\nInterfacility Consult Clinical Errors Mail Group\n\n
\nInterfacility Consult Technical Errors Mail Group\n\n
\nInterfacility Consult non-Clinical and non-Technical Errors Mail Group\n\n
\nInterfacility Consult Tier II Errors Mail Group\n\n
\nThis parameter controls if the PDMP query runs in the background or \nforeground.\n\n
\nThis parameter contains the TIU note title to be used to document PDMP \nqueries.\n\n
\nThis parameter enables/disables the PDMP functionality in CPRS. If \ndisabled, no PDMP queries will be allowed.\n\n
\nThis parameter stores the text that is used when creating the \nauto-generated PDMP note.\n\n
\nThis parameter is used to enable/disable the PDMP delegate feature.\n\n
\nThis will be used by the GUI to build the review form.\n\n