| [604] | 1 | English French Notes Complete/Exclude
|
|---|
| 2 | CHECK 773 AC XREF
|
|---|
| 3 | HL7DevelopmentTeam@med.va.gov
|
|---|
| 4 | LINK (870) CHECKS
|
|---|
| 5 | Environment check OK...
|
|---|
| 6 | Warning
|
|---|
| 7 | Press RETURN to
|
|---|
| 8 | There are inbound queues with un-processed messages. Before patch HL*1.6*109
|
|---|
| 9 | can be installed, the inbound queues must be empty. You may continue loading
|
|---|
| 10 | these patches. But, remember to clear the inbound queues before loading.
|
|---|
| 11 | (To clear the queues, start one or more incoming filer(s) to process the
|
|---|
| 12 | messages until there are no messages in the queue.)
|
|---|
| 13 | incoming filer(s) to process the messages until there are no messages in the
|
|---|
| 14 | queue. Then, try to install patch HL*1.6*109 again.
|
|---|
| 15 | Conversion already run!
|
|---|
| 16 | Post-init will identify all incomplete messages associated with TCP links
|
|---|
| 17 | These incomplete messages were a result of Network errors
|
|---|
| 18 | encountered by the DIRECT CONNECT API.
|
|---|
| 19 | These messages will be removed from the outbound TCP queue.
|
|---|
| 20 | Scanning for incomplete messages...
|
|---|
| 21 | No messages in the outbound TCP queue.
|
|---|
| 22 | Installation of PROTOCOLS not performed
|
|---|
| 23 | Installation of LIST TEMPLATES not performed
|
|---|
| 24 | Running of file conversions not performed
|
|---|
| 25 | Select output device for file conversion:
|
|---|
| 26 | Running of the file conversions not performed
|
|---|
| 27 | FILE CONVERSIONS REQUIRED BY INSTALLATION OF HL7 V1.6
|
|---|
| 28 | ** Running of file conversions could not be queued **
|
|---|
| 29 | ** File conversions will be run interactively **
|
|---|
| 30 | Running of file conversions queued as task number
|
|---|
| 31 | Task will begin execution on
|
|---|
| 32 | - File conversions started on
|
|---|
| 33 | Copying entries from HL7 NON-DHCP APPLICATION PARAMETER file (#770)
|
|---|
| 34 | to HL7 APPLICATION PARAMETER file (#771)
|
|---|
| 35 | ** Conversion halted **
|
|---|
| 36 | ** Unable to lock HL7 APPLICATION PARAMETER file **
|
|---|
| 37 | ** Use the entry point REQUEUE^HLPOST to requeue the file conversions **
|
|---|
| 38 | ** Unable to lock HL7 NON-DHCP APPLICATION PARAMETER file **
|
|---|
| 39 | * Entry number
|
|---|
| 40 | does not have an application name
|
|---|
| 41 | * Unable to copy
|
|---|
| 42 | ** Conversion of files has been asked to stop **
|
|---|
| 43 | Purging data from HL7 MESSAGE TEXT file (#772)
|
|---|
| 44 | Converting newly defined fields in HL7 MESSAGE TEXT file (#772)
|
|---|
| 45 | * Unable to lock entry number
|
|---|
| 46 | - entry not converted
|
|---|
| 47 | does not have a date & time of message
|
|---|
| 48 | - File conversions completed on
|
|---|
| 49 | Do you wish to continue ?
|
|---|
| 50 | Post-init was already run on
|
|---|
| 51 | This post-init has already been run. Answering 'YES' will allow you to
|
|---|
| 52 | selectively re-run portions of the post-init. If you do not want to do
|
|---|
| 53 | this, answer 'NO' (the default response).
|
|---|
| 54 | Do you want to re-install PROTOCOLS ?
|
|---|
| 55 | This package distributes a set of protocols which may have already
|
|---|
| 56 | been installed. Answering 'YES' (the default and recommended response)
|
|---|
| 57 | will re-install these protocols.
|
|---|
| 58 | Do you want to re-install LIST TEMPLATES ?
|
|---|
| 59 | This package distributes a set of list templates which may have already
|
|---|
| 60 | will re-install these list templates.
|
|---|
| 61 | Do you want to re-run the file conversions ?
|
|---|
| 62 | Installation of this package requires that a set of file conversions be
|
|---|
| 63 | run. Answering 'YES' (the default and recommended response) will allow
|
|---|
| 64 | these conversions to be re-run. Answer 'NO' if the file conversions
|
|---|
| 65 | have already run to completion.
|
|---|
| 66 | Starting Pre-Init
|
|---|
| 67 | RESULTS RPT/STATUSCHNG-DATE/TI
|
|---|
| 68 | .01///RESULTS RPT/STATUS CHNG-DATE/TIME
|
|---|
| 69 | Pre-Init Finished
|
|---|
| 70 | S.HL SERVER
|
|---|
| 71 | Missing subscription control number.
|
|---|
| 72 | Missing logical link.
|
|---|
| 73 | Invalid Subscription Control number
|
|---|
| 74 | Invalid Logical Link
|
|---|
| 75 | Invalid logical link
|
|---|
| 76 | Invalid receiving application.
|
|---|
| 77 | Note: You must select a Non-DHCP Application for which an HL7 Device has
|
|---|
| 78 | been defined.
|
|---|
| 79 | HL7 Message Processor for
|
|---|
| 80 | is already tasked.
|
|---|
| 81 | -1^Did not pass valid pointer to Message Text file (#772)
|
|---|
| 82 | Application Reject
|
|---|
| 83 | Application Error
|
|---|
| 84 | Error During Receipt of Acknowledgement Message
|
|---|
| 85 | - Application Reject
|
|---|
| 86 | - Application Error
|
|---|
| 87 | Failed to create an Event in STATUS^HLTF0:
|
|---|
| 88 | Application Error Text:
|
|---|
| 89 | Initial Message in this transaction protocol:
|
|---|
| 90 | Initial Message ID:
|
|---|
| 91 | Logical Link of Initial Message:
|
|---|
| 92 | Inital Message Type:
|
|---|
| 93 | Inital Message Event:
|
|---|
| 94 | HL(772
|
|---|
| 95 | at GENERATE^HLTP entry point
|
|---|
| 96 | at PROCESS^HLTP0 entry point
|
|---|
| 97 | AA,CA
|
|---|
| 98 | at GENACK^HLTP1 entry point
|
|---|
| 99 | at PROCACK^HLTP0 entry point
|
|---|
| 100 | MTP_ETP
|
|---|
| 101 | Missing MSA segment
|
|---|
| 102 | Incorrect sending app.
|
|---|
| 103 | INIT-1
|
|---|
| 104 | INIT-2
|
|---|
| 105 | at CHK^HLTPCK1 entry point
|
|---|
| 106 | Field Separator Missing
|
|---|
| 107 | Invalid Field Separator
|
|---|
| 108 | Encoding Characters Missing
|
|---|
| 109 | Invalid Encoding Characters
|
|---|
| 110 | Invalid Message Header Segment
|
|---|
| 111 | ACK,ADR,MCF,MFK,MFR,ORF,ORR,RRA,RRD,RRE,RRG,TBR
|
|---|
| 112 | MSA Segment Missing
|
|---|
| 113 | AL,NE,ER,SU
|
|---|
| 114 | Invalid accept ack type
|
|---|
| 115 | Invalid application ack type
|
|---|
| 116 | Missing HL7 Version
|
|---|
| 117 | Original Outgoing Message not found
|
|---|
| 118 | Event Protocol pointer (field #772,10) missing
|
|---|
| 119 | Event Type REQUIRED
|
|---|
| 120 | Invalid Event Type
|
|---|
| 121 | Invalid Message Structure Code
|
|---|
| 122 | Missing Sending Application
|
|---|
| 123 | Invalid Message Control ID in MSA Segment
|
|---|
| 124 | Event Protocol not found
|
|---|
| 125 | Invalid Receiving Application for this Event
|
|---|
| 126 | Missing required receiving facility
|
|---|
| 127 | Receiving Facility/App Parameter mismatch.
|
|---|
| 128 | Receiving Facility mismatch.
|
|---|
| 129 | Missing required sending facility
|
|---|
| 130 | Sending Facility/App Parameter mismatch.
|
|---|
| 131 | Unrecognized domain in sending facility
|
|---|
| 132 | Invalid HL7 Processing ID
|
|---|
| 133 | Cannot validate PROCESSING ID
|
|---|
| 134 | Processing ID Mismatch with Event Driver
|
|---|
| 135 | Processing ID Mismatch with Site Parameters
|
|---|
| 136 | Invalid access code
|
|---|
| 137 | Invalid HL7 Version for Receiving Application
|
|---|
| 138 | Event Protocol pointer (field #773,8) missing
|
|---|
| 139 | Event Type Required
|
|---|
| 140 | Unrecognized/ambiguous domain in sending facility
|
|---|
| 141 | HL7 Message
|
|---|
| 142 | Unable to determine receipients for mail message.
|
|---|
| 143 | Unable to transmit HL7 message due to the following Application Error:
|
|---|
| 144 | Non-DHCP
|
|---|
| 145 | Application Name
|
|---|
| 146 | Invalid Non-DHCP Application Name
|
|---|
| 147 | Invalid DHCP Application Name
|
|---|
| 148 | DON'T ADD. COLLECT3~HLUCM003
|
|---|
| 149 | HLUCM
|
|---|
| 150 | HLUCM Data
|
|---|
| 151 | Print Totals Report & Debug Data to Screen
|
|---|
| 152 | OK! No ^TMP(TOTALS,$J) totals report will be printed...
|
|---|
| 153 | No ^TMP($J,
|
|---|
| 154 | ) debug data exists...
|
|---|
| 155 | Press RETURN to restart, or '^' to exit...
|
|---|
| 156 | Debug Data from ^TMP($J,
|
|---|
| 157 | Print raw DEBUG DATA (Y/N): Yes//
|
|---|
| 158 | Print filtered DEBUG DATA (Y/N): Yes//
|
|---|
| 159 | You will be allowed to print report totals (from ^TMP(TOTALS,$J), and/or you
|
|---|
| 160 | may print the debug data (in ^TMP($J,
|
|---|
| 161 | Report Totals from ^TMP(
|
|---|
| 162 | Print REPORT TOTALS (Y/N): Yes//
|
|---|
| 163 | Include subtotals (Y/N): NO//
|
|---|
| 164 | Printing from
|
|---|
| 165 | Enter subscript holding the ^TMP(TOTALS,$J) data:
|
|---|
| 166 | You must pass in the initial subscript and $JOB number...
|
|---|
| 167 | Some entries were not included in the totals. There are 3 possible reasons
|
|---|
| 168 | for entries being excluded: (1) The beginning time of a message or unit is
|
|---|
| 169 | before the report's start time, (2) The number of seconds to transmit the
|
|---|
| 170 | message is over 1799 seconds, and (3) The protocol or namespace doesn't meet
|
|---|
| 171 | Failure Reason
|
|---|
| 172 | Beginning time too early
|
|---|
| 173 | Excessive xmit time
|
|---|
| 174 | Prot/Nmsp mismatch
|
|---|
| 175 | Totals:
|
|---|
| 176 | ZZZ~0
|
|---|
| 177 | DEBUG GLOBAL
|
|---|
| 178 | INVALID START TIME
|
|---|
| 179 | INVALID END TIME
|
|---|
| 180 | END TIME PRECEDES START TIME
|
|---|
| 181 | BOTH NAMESPACES(S) AND PROTOCOL(S) MUST BE PASSED SPECIFICALLY
|
|---|
| 182 | INVALID NAMESPACE PARAMETER
|
|---|
| 183 | INVALID PROTOCOL PARAMETER
|
|---|
| 184 | CAN'T FIND PROTOCOL
|
|---|
| 185 | Display of ^TMP($J,
|
|---|
| 186 | Type Totals
|
|---|
| 187 | Enter text in messages to include and exclude...
|
|---|
| 188 | Restrict # messages: 999//
|
|---|
| 189 | No data exists...
|
|---|
| 190 | No matching entries found...
|
|---|
| 191 | matching entries displayed...
|
|---|
| 192 | entries skipped...
|
|---|
| 193 | Every parent node that includes one of the EXCLUDE values that you enter now
|
|---|
| 194 | will not be included in the entries displayed.
|
|---|
| 195 | Every parent node that doesn't include one of the INCLUDE values that you
|
|---|
| 196 | enter now will not be included in the entries displayed.
|
|---|
| 197 | XTMP-stored Reports
|
|---|
| 198 | Run-time
|
|---|
| 199 | API Call
|
|---|
| 200 | You may choose to print the totals report from stored XTMP data if you like.
|
|---|
| 201 | If so, enter the number of the XTMP report from above now. (Otherwise,
|
|---|
| 202 | press RETURN.)
|
|---|
| 203 | Enter XTMP Report#:
|
|---|
| 204 | STARTandEND
|
|---|
| 205 | TO ID
|
|---|
| 206 | NMSP(
|
|---|
| 207 | HEC
|
|---|
| 208 | VAFC ADMIT
|
|---|
| 209 | VAFC ADT
|
|---|
| 210 | VAFH A
|
|---|
| 211 | VAFH CLIENT A
|
|---|
| 212 | REMOTE RPC^
|
|---|
| 213 | Print T nodes(Y/N): No//
|
|---|
| 214 | Print X nodes(Y/N): No//
|
|---|
| 215 | Print U nodes(Y/N): Yes//
|
|---|
| 216 | No data found. Press RETURN to continue...
|
|---|
| 217 | About to print ^TMP(
|
|---|
| 218 | ,$J) data report. Press RETURN...
|
|---|
| 219 | Total Total Total Main
|
|---|
| 220 | #Chars #Msgs #Sec Sort Sub1 Sub2 Sub3
|
|---|
| 221 | DATA(
|
|---|
| 222 | HL7 DHCP Application Parameters
|
|---|
| 223 | HL7 Non-DHCP Application Parameters
|
|---|
| 224 | HL7 Message Types
|
|---|
| 225 | HL7 Segment Names
|
|---|
| 226 | HL7 Data Types
|
|---|
| 227 | HL7 Version Numbers
|
|---|
| 228 | HL7 Fields
|
|---|
| 229 | Log of HL7 Transmissions in Awaiting or Pending Status
|
|---|
| 230 | EZ,?
|
|---|
| 231 | Log of Failed HL7 Transmissions
|
|---|
| 232 | Select the Non-DHCP Application for which you wish to start/stop the HL7 log
|
|---|
| 233 | of transmissions.
|
|---|
| 234 | You must define an HL7 Device for this Non-DHCP Application before you can
|
|---|
| 235 | start the log.
|
|---|
| 236 | The HL7 log is currently turned
|
|---|
| 237 | Do you want to purge existing log entries
|
|---|
| 238 | Don't
|
|---|
| 239 | (#772,15), is set to 1.
|
|---|
| 240 | queue job
|
|---|
| 241 | start purging
|
|---|
| 242 | , or enter '^' to exit...
|
|---|
| 243 | no task started...
|
|---|
| 244 | HLPDT(
|
|---|
| 245 | Purge HL7 message text on or before
|
|---|
| 246 | queued to run now...
|
|---|
| 247 | Queuing of Purge task failed.
|
|---|
| 248 | NO-LOCK
|
|---|
| 249 | entries purged...
|
|---|
| 250 | Looping through file 773...
|
|---|
| 251 | START-773
|
|---|
| 252 | END-773
|
|---|
| 253 | Looping through file 772...
|
|---|
| 254 | START-772
|
|---|
| 255 | END-772
|
|---|
| 256 | ABORTED-TASKMAN
|
|---|
| 257 | HLUOPT2
|
|---|
| 258 | HLUOPT2 Message Body Deletion
|
|---|
| 259 | HLUOPT1 9999999.999999
|
|---|
| 260 | HLUOPT1
|
|---|
| 261 | As purging jobs run, they record critical information in the ^XTMP global for
|
|---|
| 262 | later review. (This information is updated every two minutes.) You can view
|
|---|
| 263 | purge information now...
|
|---|
| 264 | Option #1 displays all available purging data, for the last job.
|
|---|
| 265 | Option #2 displays the most valuable purging data, but not all data. This
|
|---|
| 266 | option includes data for the last purging job, plus previous puring jobs.
|
|---|
| 267 | Option #3 displays purging times and totals in a graphic representation.
|
|---|
| 268 | Task-Number Start-Time Timestamp Finish-time 772@ 773@ Time-NOW
|
|---|
| 269 | There is no currently running purge job...
|
|---|
| 270 | Any old jobs that exist will be shown above. The current (or last) purge job
|
|---|
| 271 | is shown below. The information on each line will automatically refresh
|
|---|
| 272 | seconds (or whenever you press RETURN.)
|
|---|
| 273 | Note!!
|
|---|
| 274 | Enter '^' when you are ready to exit.
|
|---|
| 275 | Current (or last) purge job...
|
|---|
| 276 | HLUOPT1 9999999.99999
|
|---|
| 277 | Recent purge runs...
|
|---|
| 278 | HLUOPT1 Purging
|
|---|
| 279 | The '^HL(
|
|---|
| 280 | )' lock is already owned by another purge job! So, this
|
|---|
| 281 | purge job cannot be started.
|
|---|
| 282 | Successfully Completed
|
|---|
| 283 | Enter inclusive date up to which to purge SUCCESSFULLY COMPLETED
|
|---|
| 284 | The suggested cutoff date to purge 'Successfully Completed' messages
|
|---|
| 285 | is seven days prior to today.
|
|---|
| 286 | Must be on or before
|
|---|
| 287 | Awaiting Acknowledgement
|
|---|
| 288 | The suggested cutoff date to purge 'Awaiting Acknowledgment' messages
|
|---|
| 289 | is thirty days prior to today.
|
|---|
| 290 | of status (except ERROR status)
|
|---|
| 291 | The suggested cutoff date to purge all messages (except for 'Error' messages)
|
|---|
| 292 | is 90 days prior to today.
|
|---|
| 293 | Do you also want to purge messages with an ERROR status
|
|---|
| 294 | Enter 'Yes' to purge entries whose status is 'error'.
|
|---|
| 295 | If you have reviewed/resolved the cause of the problem of those
|
|---|
| 296 | entries with an 'error' status answer 'Yes'. Otherwise answer 'No'.
|
|---|
| 297 | WARNING: You should have investigated all errors because purging
|
|---|
| 298 | these messages permanently removes them from the system.
|
|---|
| 299 | Enter inclusive date up to which to purge ERROR
|
|---|
| 300 | The suggested cutoff date to purge 'Error' messages
|
|---|
| 301 | Would you like to queue this purge?
|
|---|
| 302 | If run in the foreground, you will see dots and a total count.
|
|---|
| 303 | #################### #################### ####################
|
|---|
| 304 | #################### #################### ####################
|
|---|
| 305 | #################### #################### ####################
|
|---|
| 306 | #################### #################### ####################
|
|---|
| 307 | #################### #################### ####################
|
|---|
