| [604] | 1 | English French Notes Complete/Exclude
|
|---|
| 2 | The following actions are also available:
|
|---|
| 3 | This list only contains 1 page.
|
|---|
| 4 | Too large. Page #
|
|---|
| 5 | Negative page numbers do not exist.
|
|---|
| 6 | Go to Page (1-
|
|---|
| 7 | Your selection is the current screen.
|
|---|
| 8 | VALM DEMO APPLICATION
|
|---|
| 9 | Prefix:
|
|---|
| 10 | No protocols to list.
|
|---|
| 11 | 'Expand' was last action picked.
|
|---|
| 12 | No Description entered.
|
|---|
| 13 | Package has not been changed.
|
|---|
| 14 | 'VALM DEMO APPLICATION' List Template...
|
|---|
| 15 | VALM DEMO APPLICATION^1^^240^5^14^1^1^Protocol^VALM DEMO MENU^Package Protocol List^2^^1^^^
|
|---|
| 16 | VALM DEMO PRINT^VALM HIDDEN ACTIONS
|
|---|
| 17 | 'VALM WORKBENCH' List Template...
|
|---|
| 18 | VALM WORKBENCH
|
|---|
| 19 | VALM WORKBENCH^1^^240^4^17^1^1^^VALM WORKBENCH^List Manager Workbench^1
|
|---|
| 20 | >>> Protocol file not present in this account.
|
|---|
| 21 | >>> Checking the version of XQOR*...
|
|---|
| 22 | The current version of XQOR* is
|
|---|
| 23 | List Manager requires version
|
|---|
| 24 | or greater.
|
|---|
| 25 | As part of the post-init, version
|
|---|
| 26 | Continue with the installation
|
|---|
| 27 | >>> List Manager installation will not occur.
|
|---|
| 28 | VALM DEMO
|
|---|
| 29 | >>> Will now delete demo protocols...
|
|---|
| 30 | >>> A new set of demo protocols will be added during the install.
|
|---|
| 31 | VALM OPTION DEMO
|
|---|
| 32 | >>> Installing XQOR* routines from VALMXQ* routines...
|
|---|
| 33 | >>> Will determine if package PROTOCOLS refer to 'SDUL'...
|
|---|
| 34 | ...nothing found
|
|---|
| 35 | Entry Action:
|
|---|
| 36 | Exit Action:
|
|---|
| 37 | Header Code:
|
|---|
| 38 | Attached Protocols:
|
|---|
| 39 | >>> List Manager Conversion Analyzer for '
|
|---|
| 40 | List Manager Conversion Analyzer
|
|---|
| 41 | Set-up MUMPS Code
|
|---|
| 42 | >>> Running the '
|
|---|
| 43 | ' List Template.
|
|---|
| 44 | Select 'QUIT' action to the workbench...
|
|---|
| 45 | No compatiable editor for operating system.
|
|---|
| 46 | *** List Template Export Utility ***
|
|---|
| 47 | >>> Exporting LIST TEMPLATES with namespace '
|
|---|
| 48 | >>> Enter the Name of the Package (2-4 characters):
|
|---|
| 49 | >>> Enter Routine Name
|
|---|
| 50 | I am going to create a series of '
|
|---|
| 51 | >>> MAXIMUM ROUTINE SIZE(BYTES):
|
|---|
| 52 | Please enter the package namespace you wish to export:
|
|---|
| 53 | ' List Template...
|
|---|
| 54 | ; List Template Exporter ;
|
|---|
| 55 | has been filed...
|
|---|
| 56 | >>> The system will create a stub routine...
|
|---|
| 57 | ' stub routine...
|
|---|
| 58 | EN ; -- main entry point for
|
|---|
| 59 | HDR ; -- header code
|
|---|
| 60 | This is a test header for
|
|---|
| 61 | INIT ; -- init variables and list array
|
|---|
| 62 | HELP ; -- help code
|
|---|
| 63 | EXIT ; -- exit code
|
|---|
| 64 | EXPND ; -- expand code
|
|---|
| 65 | Template:
|
|---|
| 66 | to the
|
|---|
| 67 | List Manager WorkBench
|
|---|
| 68 | Template Name:
|
|---|
| 69 | Entity Name:
|
|---|
| 70 | Screen Title:
|
|---|
| 71 | List Region
|
|---|
| 72 | Top Margin:
|
|---|
| 73 | Bottom
|
|---|
| 74 | Protocol Information
|
|---|
| 75 | Type of List:
|
|---|
| 76 | Protocol Menu:
|
|---|
| 77 | Print Protocol:
|
|---|
| 78 | Hidden Menu:
|
|---|
| 79 | MUMPS Code Related
|
|---|
| 80 | Expand:
|
|---|
| 81 | Caption Line Information
|
|---|
| 82 | Video
|
|---|
| 83 | Scroll Lock
|
|---|
| 84 | Other Fields
|
|---|
| 85 | OK to Transport?:
|
|---|
| 86 | Use Cursor Control:
|
|---|
| 87 | Allowable Number of Actions:
|
|---|
| 88 | Date Range Limit:
|
|---|
| 89 | Automatic Defaults:
|
|---|
| 90 | >>> LIST REGION
|
|---|
| 91 | Screen Title:
|
|---|
| 92 | Bottom Margin:
|
|---|
| 93 | Entity Name:
|
|---|
| 94 | # of Actions:
|
|---|
| 95 | Print Prot'l:
|
|---|
| 96 | Array Name:
|
|---|
| 97 | >>> Caption Name
|
|---|
| 98 | XQOR WORD PROCESSING^101.11D^
|
|---|
| 99 | -RAPID MODE-
|
|---|
| 100 | -NORMAL MODE-
|
|---|
| 101 | THIS MENU SELECTION;NEXT MENU SELECTION;FINAL SELECTION
|
|---|
| 102 | OE/RR Software is currently being updated. Access temporarily denied.
|
|---|
| 103 | This item is not setup to order from OE/RR
|
|---|
| 104 | ADD ORDERS
|
|---|
| 105 | VAQ*1.5*7
|
|---|
| 106 | Details of this installation may be obtained from the National Patch Module
|
|---|
| 107 | under the entry VAQ*1.5*7 (patch # 7 for version 1.5 of PDX).
|
|---|
| 108 | does not exist ***
|
|---|
| 109 | *** Patch 7 has not been applied to routine
|
|---|
| 110 | *** Installation of VAQ*1.5*7 halted ***
|
|---|
| 111 | Installation of patch number 7 completed
|
|---|
| 112 | VAQ*1.5*15
|
|---|
| 113 | under the entry VAQ*1.5*15 (patch #15 for version 1.5 of PDX)
|
|---|
| 114 | Do you want to run the inits included with this patch ?
|
|---|
| 115 | This patch is accompanied by a set of inits (VAQ2INIT). Running the inits
|
|---|
| 116 | will modify triggers on the Remote Facility field (#.01) of the VAQ - RELEASE
|
|---|
| 117 | GROUP file (#394.82) and the Remote Facility field (#.01) of the Remote
|
|---|
| 118 | Facility multiple (field #10) in the VAQ - OUTGOING GROUP file (#394.83).
|
|---|
| 119 | These triggers did not correctly store the external value of a pointer in the
|
|---|
| 120 | fields they update.
|
|---|
| 121 | You may skip the running of these inits if the inits included with patch
|
|---|
| 122 | VAQ*1.5*12 (which was entered in error) were successfully run.
|
|---|
| 123 | Do you want to update the VAQ - RELEASE GROUP file ?
|
|---|
| 124 | Enter 'YES' if you want the values stored in the Remote Domain field (#.02)
|
|---|
| 125 | of the VAQ - RELEASE GROUP file (#394.82) automatically re-entered. Doing
|
|---|
| 126 | this will ensure that the pointer values contained in this field are stored
|
|---|
| 127 | This step is not neccessary if the values were successfully re-entered
|
|---|
| 128 | during the installation of patch VAQ*1.5*12 (which was entered in error).
|
|---|
| 129 | Do you want to update the VAQ - OUTGOING GROUP file ?
|
|---|
| 130 | of the Remote Facility multiple (field #10) in the VAQ - OUTGOING GROUP file
|
|---|
| 131 | (#394.83) automatically re-entered. Doing this will ensure that the pointer
|
|---|
| 132 | values contained in this field are stored correctly.
|
|---|
| 133 | Installation of patch number 15
|
|---|
| 134 | Updating of VAQ - RELEASE GROUP file (#394.82) was not performed
|
|---|
| 135 | Updating of VAQ - OUTGOING GROUP file (#394.83) was not performed
|
|---|
| 136 | Performing update of triggered values in VAQ - RELEASE GROUP file
|
|---|
| 137 | VAQ-PARSE
|
|---|
| 138 | Local Facility
|
|---|
| 139 | Sending domain closed. Message ignored and deleted.
|
|---|
| 140 | Unable to read first line of message
|
|---|
| 141 | Unable to determine version of PDX used to generate transmission
|
|---|
| 142 | Error occurred while parsing version
|
|---|
| 143 | Unable to queue retransmission (IFN:
|
|---|
| 144 | Unable to complete automatic processing
|
|---|
| 145 | Unable to send results received bulletin
|
|---|
| 146 | Was able to file transaction (IFN:
|
|---|
| 147 | Unable to send Unsolicited PDX received bulletin
|
|---|
| 148 | Unable to acknowledge receipt of Unsolicited PDX
|
|---|
| 149 | Unable to queue acknowledgement for receipt of Unsolicited PDX
|
|---|
| 150 | -1^Error completing receipt of Unsolicited PDX
|
|---|
| 151 | Error occurred while filing
|
|---|
| 152 | (Transaction was not created)
|
|---|
| 153 | Transaction
|
|---|
| 154 | -1^Valid transaction not passed
|
|---|
| 155 | VAQ-XMIT
|
|---|
| 156 | VAQ-AUTOCHK
|
|---|
| 157 | Exact match on name/ssn/dob not found, process manually for potential matches
|
|---|
| 158 | -20^Maximum time & occurrence limits exceeded by
|
|---|
| 159 | PDX Server
|
|---|
| 160 | Unable to queue transmission of results
|
|---|
| 161 | -1^Did not pass reference to transaction array
|
|---|
| 162 | -1^Transaction array did not contain any information
|
|---|
| 163 | Generation of PDX transmission
|
|---|
| 164 | VAQTRN(
|
|---|
| 165 | -1^Could not queue transmission(s)
|
|---|
| 166 | Transaction does not exist
|
|---|
| 167 | Could not determine message type
|
|---|
| 168 | Can not transmit a transaction that is being received
|
|---|
| 169 | Transaction did not contain a domain to transmit message to
|
|---|
| 170 | Domain is closed:
|
|---|
| 171 | Error occurred while building transmission(1)
|
|---|
| 172 | Error occurred while extracting information
|
|---|
| 173 | PDX (V1.5) TRANSMISSION FROM
|
|---|
| 174 | Patient Data eXchange
|
|---|
| 175 | -1^Did not pass work identifier
|
|---|
| 176 | -1^Did not pass transaction work was done with
|
|---|
| 177 | -1^Did not pass a valid transaction
|
|---|
| 178 | -1^Did not pass a valid word identifier
|
|---|
| 179 | -1^Could not create entry in work-load file
|
|---|
| 180 | -1^Unable to create entry in work-load file
|
|---|
| 181 | -1^Did not pass subject of message
|
|---|
| 182 | -1^Did not pass sender of message
|
|---|
| 183 | -1^Did not pass array containing message
|
|---|
| 184 | -1^Did not valid array reference
|
|---|
| 185 | -1^Array did not contain message
|
|---|
| 186 | -1^Did not pass distribution list
|
|---|
| 187 | -1^Distributionl list was empty
|
|---|
| 188 | -1^Could not get stub message
|
|---|
| 189 | UNABLE TO SEND MESSAGES
|
|---|
| 190 | The following message(s) could not be transmitted ...
|
|---|
| 191 | ) Transaction Number:
|
|---|
| 192 | Sent By:
|
|---|
| 193 | Could not be determined (Contact your PDX ADPAC)^Could not be determined (Contact your PDX ADPAC)
|
|---|
| 194 | PDX Request
|
|---|
| 195 | Results from processing an external request
|
|---|
| 196 | Acknowledgment (Contact your PDX ADPAC)
|
|---|
| 197 | Re-transmit (Contact your PDX ADPAC)
|
|---|
| 198 | The following error(s) occurred while generating PDX transmissions ...
|
|---|
| 199 | Global Location: ^VAT(394.61,
|
|---|
| 200 | Unknown^??
|
|---|
| 201 | G.VAQ PDX ERRORS
|
|---|
| 202 | -1^Did not pass valid transaction
|
|---|
| 203 | VAQ-BUL
|
|---|
| 204 | Not listed
|
|---|
| 205 | Could not be determined
|
|---|
| 206 | The following PDX Request requires manual processing ...
|
|---|
| 207 | Transaction number:
|
|---|
| 208 | Requested by:
|
|---|
| 209 | Reason for manual processing:
|
|---|
| 210 | Segments that were over the allowable time & occurrence limits:
|
|---|
| 211 | Requested Maximum Requested Maximum
|
|---|
| 212 | Segment Time Time Occurrence Occurrence
|
|---|
| 213 | G.VAQ MANUAL PROCESSING
|
|---|
| 214 | Process PDX Request for
|
|---|
| 215 | -1^Unable to generate and send bulletin
|
|---|
| 216 | -1^Transaction did not contain results of a request
|
|---|
| 217 | -1^Transaction did not contain a transaction number
|
|---|
| 218 | Uknown
|
|---|
| 219 | Your request for information has been
|
|---|
| 220 | processed and returned
|
|---|
| 221 | Transaction number:
|
|---|
| 222 | *** PATIENT WAS LISTED AS SENSITIVE AT THE REMOTE FACILITY ***
|
|---|
| 223 | *** PATIENT IS LISTED AS SENSITIVE IN YOUR FACILITY ***
|
|---|
| 224 | Requested on:
|
|---|
| 225 | Reason: Patient not found
|
|---|
| 226 | Reason: Requested patient could not be uniquely identified
|
|---|
| 227 | None listed
|
|---|
| 228 | Requested information:
|
|---|
| 229 | Requested data could not be included in notification
|
|---|
| 230 | Transaction did not contain any information
|
|---|
| 231 | Error occurred while getting information from PDX files
|
|---|
| 232 | PDX Rejection for
|
|---|
| 233 | PDX Results for
|
|---|
| 234 | The following error(s) occurred while receiving a PDX transmission ...
|
|---|
| 235 | General Information
|
|---|
| 236 | XMZ:
|
|---|
| 237 | Global Location: ^XMB(3.9,
|
|---|
| 238 | Postmaster Basket: S.VAQ-PDX-SERVER
|
|---|
| 239 | General Error
|
|---|
| 240 | Specific Error(s)
|
|---|
| 241 | Message Number:
|
|---|
| 242 | Note: Each PDX transmission can contain more than one PDX message. Message
|
|---|
| 243 | number X refers to the Xth message within the transmission (not the
|
|---|
| 244 | UNABLE TO PROPERLY RECEIVE TRANSMISSION
|
|---|
| 245 | -1^Transaction was not an Unsolicited PDX
|
|---|
| 246 | The following Unsolicited PDX has been received ...
|
|---|
| 247 | Received on:
|
|---|
| 248 | Sent by:
|
|---|
| 249 | Comments: None listed
|
|---|
| 250 | G.VAQ UNSOLICITED RECEIVED
|
|---|
| 251 | Unsolicited PDX for
|
|---|
| 252 | -1^Did not pass reference to error array
|
|---|
| 253 | ** Purger was stopped before completion **
|
|---|
| 254 | The following PDX Transaction(s) could not be purged ...
|
|---|
| 255 | ** Please remember that PDX Transactions may also **
|
|---|
| 256 | ** have associated data stored in file number 394.62 **
|
|---|
| 257 | PDX TRANSACTIONS COULD NOT BE PURGED
|
|---|
| 258 | -1^Did not pass reference to array of transaction pointers
|
|---|
| 259 | -1^Did not pass message number or reference to output array
|
|---|
| 260 | -1^Valid message number not passed
|
|---|
| 261 | -1^Did not pass a valid pointer to VAQ - TRANSACTION file
|
|---|
| 262 | -1^Transaction is being received, not transmitted
|
|---|
| 263 | -1^Subject of message not passed
|
|---|
| 264 | -1^Could not determine sender of message
|
|---|
| 265 | -1^Could not create stub message
|
|---|
| 266 | -1^Line number not passed
|
|---|
| 267 | Success
|
|---|
| 268 | Killing of bad PDX messages
|
|---|
| 269 | -1^Could not task deletion of message
|
|---|
| 270 | -1^Did not pass pointer to VAQ - TRANSACTION file
|
|---|
| 271 | -1^Could not determine status of message
|
|---|
| 272 | VAQ-RCVE
|
|---|
| 273 | -1^Could not determine message type
|
|---|
| 274 | -1^Could not determine remote transaction number
|
|---|
| 275 | -1^Did not pass message number of reference to array
|
|---|
| 276 | -1^Could not determine facility name
|
|---|
| 277 | -1^Could not determine message status or type
|
|---|
| 278 | -1^Could not determine return address
|
|---|
| 279 | -1^Could not determine destination of message
|
|---|
| 280 | -1^Patient information not contained in VAQ - TRANSACTION file
|
|---|
| 281 | -1^Did not pass segment abbreviation
|
|---|
| 282 | -1^Did not pass location of Extraction Array
|
|---|
| 283 | -1^Did not pass a valid pointer to the VAQ - TRANSACTION file
|
|---|
| 284 | -1^Could not determine type of message to send
|
|---|
| 285 | -1^Equivalent message not available in version 1.0 format
|
|---|
| 286 | -1^Message not required
|
|---|
| 287 | -1^Could not determine remote domain
|
|---|
| 288 | PDX (V1.0) TRANSMISSION FROM
|
|---|
| 289 | VAQ-10
|
|---|
| 290 | -1^Transaction does not require a PDX message in version 1.0
|
|---|
| 291 | -1^Transmission does not have a version 1.0 equivalent
|
|---|
| 292 | PDX*MAS
|
|---|
| 293 | PDX*MPS
|
|---|
| 294 | -1^Message type does not return data
|
|---|
| 295 | -1^Could not determine current domain
|
|---|
| 296 | Request requires user intervention
|
|---|
| 297 | -1^Version 1.0 does not have an equivalent message
|
|---|
| 298 | -1^Could not determine 1.0 status
|
|---|
| 299 | -1^Could not determine 1.0 parent PDX number
|
|---|
| 300 | -1^Transaction did not contain patient's name or SSN
|
|---|
| 301 | -1^Could not determine name of requestor
|
|---|
| 302 | -1^Could not determine current site number
|
|---|
| 303 | #################### #################### ####################
|
|---|
| 304 | #################### #################### ####################
|
|---|
| 305 | #################### #################### ####################
|
|---|
| 306 | #################### #################### ####################
|
|---|
| 307 | #################### #################### ####################
|
|---|
