English	French	Notes	Complete/Exclude
The following actions are also available:			
This list only contains 1 page.			
Too large. Page #			
Negative page numbers do not exist.			
Go to Page (1-			
Your selection is the current screen.			
VALM DEMO APPLICATION			
Prefix: 			
    No protocols to list.			
'Expand' was last action picked.			
No Description entered.			
Package has not been changed.			
'VALM DEMO APPLICATION' List Template...			
VALM DEMO APPLICATION^1^^240^5^14^1^1^Protocol^VALM DEMO MENU^Package Protocol List^2^^1^^^			
VALM DEMO PRINT^VALM HIDDEN ACTIONS			
'VALM WORKBENCH' List Template...			
VALM WORKBENCH			
VALM WORKBENCH^1^^240^4^17^1^1^^VALM WORKBENCH^List Manager Workbench^1			
>>> Protocol file not present in this account.			
>>> Checking the version of XQOR*...			
The current version of XQOR* is 			
List Manager requires version 			
 or greater.			
As part of the post-init, version 			
     Continue with the installation			
>>> List Manager installation will not occur.			
VALM DEMO 			
>>> Will now delete demo protocols...			
>>> A new set of demo protocols will be added during the install.			
VALM OPTION DEMO			
>>> Installing XQOR* routines from VALMXQ* routines...			
>>> Will determine if package PROTOCOLS refer to 'SDUL'...			
...nothing found			
Entry Action: 			
Exit Action: 			
Header Code: 			
Attached Protocols:			
>>> List Manager Conversion Analyzer for '			
List Manager Conversion Analyzer			
Set-up MUMPS Code			
>>> Running the '			
' List Template.			
     Select 'QUIT' action to the workbench...			
No compatiable editor for operating system.			
*** List Template Export Utility ***			
>>> Exporting LIST TEMPLATES with namespace '			
>>> Enter the Name of the Package (2-4 characters): 			
>>> Enter Routine Name			
I am going to create a series of '			
>>> MAXIMUM ROUTINE SIZE(BYTES): 			
Please enter the package namespace you wish to export: 			
' List Template...			
 ; List Template Exporter ; 			
 has been filed...			
>>> The system will create a stub routine...			
' stub routine...			
EN ; -- main entry point for 			
HDR ; -- header code			
This is a test header for 			
INIT ; -- init variables and list array			
HELP ; -- help code			
EXIT ; -- exit code			
EXPND ; -- expand code			
Template: 			
 to the 			
 List Manager WorkBench 			
Template Name: 			
  Entity Name: 			
 Screen Title: 			
 List Region 			
   Top Margin: 			
Bottom    			
 Protocol Information 			
  Type of List: 			
 Protocol Menu: 			
Print Protocol: 			
   Hidden Menu: 			
 MUMPS Code Related 			
Expand: 			
 Caption Line Information 			
Video			
Scroll Lock			
 Other Fields 			
           OK to Transport?: 			
         Use Cursor Control: 			
Allowable Number of Actions: 			
           Date Range Limit: 			
         Automatic Defaults: 			
>>> LIST REGION			
Screen Title: 			
Bottom Margin: 			
 Entity Name: 			
      # of Actions: 			
Print Prot'l: 			
        Array Name:			
>>>  Caption Name			
XQOR WORD PROCESSING^101.11D^			
 -RAPID MODE-			
 -NORMAL MODE-			
THIS MENU SELECTION;NEXT MENU SELECTION;FINAL SELECTION			
OE/RR Software is currently being updated. Access temporarily denied.			
This item is not setup to order from OE/RR			
ADD ORDERS			
VAQ*1.5*7  			
Details of this installation may be obtained from the National Patch Module			
under the entry VAQ*1.5*7 (patch # 7 for version 1.5 of PDX).			
 does not exist ***			
*** Patch 7 has not been applied to routine 			
*** Installation of VAQ*1.5*7 halted ***			
Installation of patch number 7 completed			
VAQ*1.5*15  			
under the entry VAQ*1.5*15 (patch #15 for version 1.5 of PDX)			
Do you want to run the inits included with this patch ? 			
This patch is accompanied by a set of inits (VAQ2INIT).  Running the inits			
will modify triggers on the Remote Facility field (#.01) of the VAQ - RELEASE			
GROUP file (#394.82) and the Remote Facility field (#.01) of the Remote			
Facility multiple (field #10) in the VAQ - OUTGOING GROUP file (#394.83).			
These triggers did not correctly store the external value of a pointer in the			
fields they update.			
You may skip the running of these inits if the inits included with patch			
VAQ*1.5*12 (which was entered in error) were successfully run.			
Do you want to update the VAQ - RELEASE GROUP file ? 			
Enter 'YES' if you want the values stored in the Remote Domain field (#.02)			
of the VAQ - RELEASE GROUP file (#394.82) automatically re-entered.  Doing			
this will ensure that the pointer values contained in this field are stored			
This step is not neccessary if the values were successfully re-entered			
during the installation of patch VAQ*1.5*12 (which was entered in error).			
Do you want to update the VAQ - OUTGOING GROUP file ? 			
of the Remote Facility multiple (field #10) in the VAQ - OUTGOING GROUP file			
(#394.83) automatically re-entered.  Doing this will ensure that the pointer			
values contained in this field are stored correctly.			
Installation of patch number 15 			
Updating of VAQ - RELEASE GROUP file (#394.82) was not performed			
Updating of VAQ - OUTGOING GROUP file (#394.83) was not performed			
Performing update of triggered values in VAQ - RELEASE GROUP file 			
VAQ-PARSE			
Local Facility			
Sending domain closed.  Message ignored and deleted.			
Unable to read first line of message			
Unable to determine version of PDX used to generate transmission			
Error occurred while parsing version 			
Unable to queue retransmission  (IFN: 			
Unable to complete automatic processing			
Unable to send results received bulletin			
Was able to file transaction (IFN:			
Unable to send Unsolicited PDX received bulletin			
Unable to acknowledge receipt of Unsolicited PDX			
Unable to queue acknowledgement for receipt of Unsolicited PDX			
-1^Error completing receipt of Unsolicited PDX			
Error occurred while filing 			
(Transaction was not created)			
Transaction 			
-1^Valid transaction not passed			
VAQ-XMIT			
VAQ-AUTOCHK			
Exact match on name/ssn/dob not found, process manually for potential matches			
-20^Maximum time & occurrence limits exceeded by 			
PDX Server			
Unable to queue transmission of results			
-1^Did not pass reference to transaction array			
-1^Transaction array did not contain any information			
Generation of PDX transmission			
VAQTRN(			
-1^Could not queue transmission(s)			
Transaction does not exist			
Could not determine message type			
Can not transmit a transaction that is being received			
Transaction did not contain a domain to transmit message to			
Domain is closed: 			
Error occurred while building transmission(1)			
Error occurred while extracting information			
PDX (V1.5) TRANSMISSION FROM 			
Patient Data eXchange			
-1^Did not pass work identifier			
-1^Did not pass transaction work was done with			
-1^Did not pass a valid transaction			
-1^Did not pass a valid word identifier			
-1^Could not create entry in work-load file			
-1^Unable to create entry in work-load file			
-1^Did not pass subject of message			
-1^Did not pass sender of message			
-1^Did not pass array containing message			
-1^Did not valid array reference			
-1^Array did not contain message			
-1^Did not pass distribution list			
-1^Distributionl list was empty			
-1^Could not get stub message			
UNABLE TO SEND MESSAGES			
The following message(s) could not be transmitted ...			
)  Transaction Number: 			
Sent By: 			
Could not be determined (Contact your PDX ADPAC)^Could not be determined (Contact your PDX ADPAC)			
PDX Request			
Results from processing an external request			
Acknowledgment (Contact your PDX ADPAC)			
Re-transmit (Contact your PDX ADPAC)			
The following error(s) occurred while generating PDX transmissions ...			
Global Location: ^VAT(394.61,			
Unknown^??			
G.VAQ PDX ERRORS			
-1^Did not pass valid transaction			
VAQ-BUL			
Not listed			
Could not be determined			
The following PDX Request requires manual processing ...			
  Transaction number: 			
  Requested by: 			
  Reason for manual processing:			
  Segments that were over the allowable time & occurrence limits:			
               Requested    Maximum      Requested      Maximum			
  Segment        Time        Time        Occurrence    Occurrence			
G.VAQ MANUAL PROCESSING			
Process PDX Request for 			
-1^Unable to generate and send bulletin			
-1^Transaction did not contain results of a request			
-1^Transaction did not contain a transaction number			
Uknown			
Your request for information has been 			
processed and returned			
Transaction number: 			
*** PATIENT WAS LISTED AS SENSITIVE AT THE REMOTE FACILITY ***			
*** PATIENT IS LISTED AS SENSITIVE IN YOUR FACILITY ***			
Requested on: 			
Reason: Patient not found			
Reason: Requested patient could not be uniquely identified			
None listed			
Requested information:			
Requested data could not be included in notification			
Transaction did not contain any information			
Error occurred while getting information from PDX files			
PDX Rejection for 			
PDX Results for 			
The following error(s) occurred while receiving a PDX transmission ...			
General Information			
XMZ: 			
Global Location: ^XMB(3.9,			
Postmaster Basket: S.VAQ-PDX-SERVER			
General Error			
Specific Error(s)			
Message Number: 			
Note: Each PDX transmission can contain more than one PDX message.  Message			
      number X refers to the Xth message within the transmission (not the			
UNABLE TO PROPERLY RECEIVE TRANSMISSION			
-1^Transaction was not an Unsolicited PDX			
The following Unsolicited PDX has been received ...			
Received on: 			
Sent by: 			
Comments: None listed			
G.VAQ UNSOLICITED RECEIVED			
Unsolicited PDX for 			
-1^Did not pass reference to error array			
** Purger was stopped before completion **			
The following PDX Transaction(s) could not be purged ...			
**  Please remember that PDX Transactions may also   **			
** have associated data stored in file number 394.62 **			
PDX TRANSACTIONS COULD NOT BE PURGED			
-1^Did not pass reference to array of transaction pointers			
-1^Did not pass message number or reference to output array			
-1^Valid message number not passed			
-1^Did not pass a valid pointer to VAQ - TRANSACTION file			
-1^Transaction is being received, not transmitted			
-1^Subject of message not passed			
-1^Could not determine sender of message			
-1^Could not create stub message			
-1^Line number not passed			
Success			
Killing of bad PDX messages			
-1^Could not task deletion of message			
-1^Did not pass pointer to VAQ - TRANSACTION file			
-1^Could not determine status of message			
VAQ-RCVE			
-1^Could not determine message type			
-1^Could not determine remote transaction number			
-1^Did not pass message number of reference to array			
-1^Could not determine facility name			
-1^Could not determine message status or type			
-1^Could not determine return address			
-1^Could not determine destination of message			
-1^Patient information not contained in VAQ - TRANSACTION file			
-1^Did not pass segment abbreviation			
-1^Did not pass location of Extraction Array			
-1^Did not pass a valid pointer to the VAQ - TRANSACTION file			
-1^Could not determine type of message to send			
-1^Equivalent message not available in version 1.0 format			
-1^Message not required			
-1^Could not determine remote domain			
PDX (V1.0) TRANSMISSION FROM 			
VAQ-10			
-1^Transaction does not require a PDX message in version 1.0			
-1^Transmission does not have a version 1.0 equivalent			
PDX*MAS			
PDX*MPS			
-1^Message type does not return data			
-1^Could not determine current domain			
Request requires user intervention			
-1^Version 1.0 does not have an equivalent message			
-1^Could not determine 1.0 status			
-1^Could not determine 1.0 parent PDX number			
-1^Transaction did not contain patient's name or SSN			
-1^Could not determine name of requestor			
-1^Could not determine current site number			
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
####################	####################	####################