| 1 | English French  Notes   Complete/Exclude | 
|---|
| 2 | Enter END DATE/TIME | 
|---|
| 3 | You cannot enter the same values for the beginning and ending times! | 
|---|
| 4 | Enter the maximum number errors to report for every error status. | 
|---|
| 5 | Enter maximum number errors/status | 
|---|
| 6 | If you enter '1000' for the maximum number errors/status... | 
|---|
| 7 | ... The most recent 1000 errors for every error type will be included in the | 
|---|
| 8 | ... report. If two different error types exist, and each error type has | 
|---|
| 9 | ... more than 1000 entries, then 2000 errors will be reported. | 
|---|
| 10 | ... (I.e., 1000 errors per error type.) | 
|---|
| 11 | ... The most recent 1000 errors for the error type you just selected | 
|---|
| 12 | ... will be included in the report. | 
|---|
| 13 | Enter a date/time after | 
|---|
| 14 | Select the report view now.  There are two report views.  Both list the | 
|---|
| 15 | internal entry number from the HL7 Message Administration file (#773) entry, | 
|---|
| 16 | message ID, processing date or time, and logical link.  The two report views | 
|---|
| 17 | differ in the remainder of the information displayed on the report. | 
|---|
| 18 | Select data to display | 
|---|
| 19 | Select the data to be displayed in the last few columns of the report after | 
|---|
| 20 | the IEN, message ID, processing date or time, and logical link. | 
|---|
| 21 | Duplicate Message | 
|---|
| 22 | Duplicate with ien | 
|---|
| 23 | Duplicate with ien | 
|---|
| 24 | Duplicate w/# | 
|---|
| 25 | Incorrect Message Received | 
|---|
| 26 | Incorrect msg. Id | 
|---|
| 27 | Incorrect message ID | 
|---|
| 28 | HL MESSAGE REQUEUER - 3 | 
|---|
| 29 | Selected Message from Logical Link | 
|---|
| 30 | Init Error | 
|---|
| 31 | HLClnt: | 
|---|
| 32 | HLSrv: | 
|---|
| 33 | Listen | 
|---|
| 34 | Openfail | 
|---|
| 35 | Init error | 
|---|
| 36 | Idle | 
|---|
| 37 | SYS$NET | 
|---|
| 38 | Init | 
|---|
| 39 | IN State: | 
|---|
| 40 | Wr-err | 
|---|
| 41 | Retention | 
|---|
| 42 | Check out | 
|---|
| 43 | exceeded retries. LL will | 
|---|
| 44 | keep trying. | 
|---|
| 45 | LLP Exceeded Retry Param | 
|---|
| 46 | Send | 
|---|
| 47 | BHS,FHS | 
|---|
| 48 | Logical Link | 
|---|
| 49 | exceeded Open Retries. | 
|---|
| 50 | HL7.yourdomain.com | 
|---|
| 51 | DNS Lkup | 
|---|
| 52 | VA.GOV | 
|---|
| 53 | HL7. | 
|---|
| 54 | MPI. | 
|---|
| 55 | Op-err | 
|---|
| 56 | Rd-err | 
|---|
| 57 | SYSTEM LINK MONITOR for | 
|---|
| 58 | TO SEND | 
|---|
| 59 | SENT | 
|---|
| 60 | TYPE | 
|---|
| 61 | IOELALL;IOELEOL;IORESET;IORVON;IORVOFF;IOIL;IOSTBM;IOSC;IORC;IOEDEOP;IOINHI;IOINORM;IOUON;IOUOFF;IOBOFF;IOBON | 
|---|
| 62 | -1^Did not pass task number of filer | 
|---|
| 63 | -1^Entry in file #869.3 does not exist | 
|---|
| 64 | -1^Unable to create entry in filer multiple | 
|---|
| 65 | No set logic for file # | 
|---|
| 66 | does not contain a field | 
|---|
| 67 | HLDIE-DEBUG | 
|---|
| 68 | Debug Data Display by FILE,IEN | 
|---|
| 69 | HLDIE-DEBUGX | 
|---|
| 70 | No debug data exists... | 
|---|
| 71 | Enter FILE#: | 
|---|
| 72 | Enter IEN: | 
|---|
| 73 | File & IEN | 
|---|
| 74 | Job# | 
|---|
| 75 | Rtn | 
|---|
| 76 | Debug# | 
|---|
| 77 | Enter #: | 
|---|
| 78 | Files w/Debug Data | 
|---|
| 79 | IENs w/Debug Data for File# | 
|---|
| 80 | Some IENs not displayed (because there were too many)... | 
|---|
| 81 | (The LAST IEN is | 
|---|
| 82 | Debug Data Display by Global Search | 
|---|
| 83 | Search string: | 
|---|
| 84 | Searching... | 
|---|
| 85 | HLDIE-DEBUF | 
|---|
| 86 | Debug Data Display by API Call | 
|---|
| 87 | no data... | 
|---|
| 88 | Rtn: | 
|---|
| 89 | Subrtn: | 
|---|
| 90 | Max#: 20// | 
|---|
| 91 | Enter Date/time (FM): | 
|---|
| 92 | invalid format... | 
|---|
| 93 | Enter # to display: | 
|---|
| 94 | entry not found... | 
|---|
| 95 | HLDIE-DEBUG- | 
|---|
| 96 | Call# | 
|---|
| 97 | Press RETURN to continue, or '^' to exit... | 
|---|
| 98 | HLDIE Debug Utility | 
|---|
| 99 | IOINORM;IOINHI | 
|---|
| 100 | Pre-call: | 
|---|
| 101 | ON[ | 
|---|
| 102 | Select option | 
|---|
| 103 | HLDIE-DEBUGN | 
|---|
| 104 | File [#IEN] | 
|---|
| 105 | DataTM | 
|---|
| 106 | Edtor | 
|---|
| 107 | Collecting data... | 
|---|
| 108 | [No change] | 
|---|
| 109 | debug string. | 
|---|
| 110 | debug string | 
|---|
| 111 | HLDIE- | 
|---|
| 112 | FILE-HLDIE | 
|---|
| 113 | HLDIE $$STORESCR Error | 
|---|
| 114 | An error occurred in $$STORESCR^HLDIEDB2 that must be checked.  The | 
|---|
| 115 | variables that existed at the time of the error are listed below. | 
|---|
| 116 | The error was ' | 
|---|
| 117 | IMPORTANT!!  All debugging was turned off.  Please review the problem, | 
|---|
| 118 | then turn debugging back on. | 
|---|
| 119 | Local Variable List | 
|---|
| 120 | error notification email message. | 
|---|
| 121 | Enter job#: | 
|---|
| 122 | invalid job#... | 
|---|
| 123 | Job | 
|---|
| 124 | Calls | 
|---|
| 125 | HLDIE Debug String Set/Unset Utility | 
|---|
| 126 | When asked for a new debug string, you may take one of the following actions: | 
|---|
| 127 | * Enter RETURN or '^' to exit. | 
|---|
| 128 | * Enter a debug string.  (E.g., '1' or '1^2' or '1^1^1'.) | 
|---|
| 129 | * Enter '@' to delete the debug string, (If a debug string exists). | 
|---|
| 130 | Current DEBUG string = | 
|---|
| 131 | Enter DEBUG string, | 
|---|
| 132 | or RETURN to exit: | 
|---|
| 133 | no changes made.  Exiting... | 
|---|
| 134 | No changes made.  (If you want to stop debugging, enter ' | 
|---|
| 135 | no changes made... | 
|---|
| 136 | stopped all debugging! | 
|---|
| 137 | Control string for HLDIE debugging | 
|---|
| 138 | debugging set... | 
|---|
| 139 | Debug data created by HLDIEDBG routine | 
|---|
| 140 | Kill **ALL** debug data | 
|---|
| 141 | no data will be killed... | 
|---|
| 142 | KILLing all debug data... | 
|---|
| 143 | HLDIE | 
|---|
| 144 | Data logged by LOG~HLDIE | 
|---|
| 145 | AH KILL | 
|---|
| 146 | ACTION STATUS | 
|---|
| 147 | DT/TM | 
|---|
| 148 | DT/TM ACTION | 
|---|
| 149 | DT/TM CREATED | 
|---|
| 150 | DT/TM REVIEWED | 
|---|
| 151 | MSGID ID | 
|---|
| 152 | MSG TYPE | 
|---|
| 153 | MSG EVENT | 
|---|
| 154 | MSG LINK | 
|---|
| 155 | REVIEW STATUS | 
|---|
| 156 | MSG ID | 
|---|
| 157 | UNKNOWN EVENT TYPE | 
|---|
| 158 | UNKNOWN SITE | 
|---|
| 159 | INACTIVE EVENT TYPE | 
|---|
| 160 | ALL APPS | 
|---|
| 161 | ALL STATUSES | 
|---|
| 162 | ALL TYPES | 
|---|
| 163 | Please select the profile you wish to use | 
|---|
| 164 | No profile selected! Try again | 
|---|
| 165 | or hit RETURN to see more | 
|---|
| 166 | You can choose a profile by the number or by it's name. | 
|---|
| 167 | You must enter the number or name of the profile! | 
|---|
| 168 | HL7 EVENT LOG AT SAN FRANCISCO | 
|---|
| 169 | **APPLICATION DATA** | 
|---|
| 170 | S.HLEM EVENT LOG SERVER | 
|---|
| 171 | UNKNOWN EVENT TYPE AT REMOTE SITE: | 
|---|
| 172 | REMOTE EVENT ADDED BY SERVER AT | 
|---|
| 173 | , MAILMAN MESSAGE IEN: | 
|---|
| 174 | Fileman Failed to store remote event: | 
|---|
| 175 | SRVR ERROR | 
|---|
| 176 | HEALTH LEVEL SEVEN | 
|---|
| 177 | MAIL IEN | 
|---|
| 178 | HLEM APP DATA | 
|---|
| 179 | HLEM DISPLAY APPLICATION DATA | 
|---|
| 180 | #   EVENT       DT/TM           APPLICATION    MSG      REVIEW        CNT | 
|---|
| 181 | HLEM DISPLAY ONE EVENT | 
|---|
| 182 | Event ID: | 
|---|
| 183 | Event Type: | 
|---|
| 184 | Count: | 
|---|
| 185 | Descr: | 
|---|
| 186 | Site of Event: | 
|---|
| 187 | DT/TM of Event: | 
|---|
| 188 | DT/TM Reported: | 
|---|
| 189 | Status Information: | 
|---|
| 190 | Urgent: | 
|---|
| 191 | Automated Action: | 
|---|
| 192 | DT/TM: | 
|---|
| 193 | Review Status: | 
|---|
| 194 | Reviewer: | 
|---|
| 195 | Date: | 
|---|
| 196 | HL7 Message Information: | 
|---|
| 197 | Mssg ID: | 
|---|
| 198 | Sending App: | 
|---|
| 199 | Logical Link: | 
|---|
| 200 | Notes: | 
|---|
| 201 | HLEM EVENT HELP | 
|---|
| 202 | NO HELP AVAILABLE! | 
|---|
| 203 | HLEM DISPLAY EVENTS | 
|---|
| 204 | ** Your DUZ is not defined, please report this to your IRM! | 
|---|
| 205 | You need a profile before viewing the HL7 Monitor Event Log,would you like to  create a new profile now | 
|---|
| 206 | NEW PROFILE | 
|---|
| 207 | Incomplete profile couln't be deleted! | 
|---|
| 208 | #    TYPE        DT/TM         APP             MSG      REVIEW         CNT | 
|---|
| 209 | USER PROFILE: | 
|---|
| 210 | Enter the number of the event to display | 
|---|
| 211 | HL7 MONITOR EVENT | 
|---|
| 212 | FAILED TO ADD THE MAILMAN MESSAGE NUMBER TO THE EVENT | 
|---|
| 213 | MAILMAN FAILED TO SEND HL7 LOG EVENT TO REMOTE SERVER | 
|---|
| 214 | HL7 EVENT LOG at | 
|---|
| 215 | MOORE,JIM | 
|---|
| 216 | HL7 EVENT LOG | 
|---|
| 217 | HLEM DISPLAY STATISTICS | 
|---|
| 218 | Year   Month     Day   Hour    Event                                   Count | 
|---|
| 219 | There are no statistics for this profile and date range! | 
|---|
| 220 | Enter the begining date | 
|---|
| 221 | Please enter the earliest date for which you would like to see Event Logging Statistics. | 
|---|
| 222 | January | 
|---|
| 223 | February | 
|---|
| 224 | March | 
|---|
| 225 | April | 
|---|
| 226 | June | 
|---|
| 227 | July | 
|---|
| 228 | August | 
|---|
| 229 | September | 
|---|
| 230 | October | 
|---|
| 231 | November | 
|---|
| 232 | December | 
|---|
| 233 | This routine searches for HL7 protocols with possible errors. | 
|---|
| 234 | Select an EVENT DRIVER Protocol: | 
|---|
| 235 | HL7 Interface Debugger | 
|---|
| 236 | Queued to task number: | 
|---|
| 237 | ** HL7 INTERFACE DEBUGGER ** | 
|---|
| 238 | ACK,ADR,ARD,EDR,ERP,MCF,MFK,MFR,ORF,ORG,ORR,OSR,RAR,RCI,RCL, | 
|---|
| 239 | RDR,RDY,RER,RGR,ROR,RRA,RRD,RRE,RRG,RRI,RSP,RTB,SQR, | 
|---|
| 240 | TBR,VXR,VXX | 
|---|
| 241 | Protocol is UNDEFINED. | 
|---|
| 242 | **PROTOCOL DISABLED** | 
|---|
| 243 | Missing data for all key fields. | 
|---|
| 244 | Version ID is required. | 
|---|
| 245 | Missing Required Sending Application. | 
|---|
| 246 | Broken pointer to App Param (file 771). | 
|---|
| 247 | Missing required Message Type. | 
|---|
| 248 | Broken pointer to Msg Type (file 771.2). | 
|---|
| 249 | For Event Driver-Message Type cannot be an acknowledgement. | 
|---|
| 250 | Broken pointer to Event Type (file 779.001). | 
|---|
| 251 | Event type is required for versions greater than 2.1. | 
|---|
| 252 | Event Driver: | 
|---|
| 253 | Sending Application: | 
|---|
| 254 | Version: | 
|---|
| 255 | Message Type(770.3): | 
|---|
| 256 | Event Driver Error Summary: | 
|---|
| 257 | No Event Driver Errors Found. | 
|---|
| 258 | No Subscribers Found. | 
|---|
| 259 | Subscriber Protocol is UNDEFINED. | 
|---|
| 260 | **SUBSCRIBER PROTOCOL DISABLED** | 
|---|
| 261 | Missing Required Receiving Application. | 
|---|
| 262 | Message Type must be an appropriate response/acknowledgement. | 
|---|
| 263 | Missing Processing Routine and Routing Logic. | 
|---|
| 264 | WARNING-Missing both Logical Link and Routing Logic. Will be local only. | 
|---|
| 265 | For Subscriber: | 
|---|
| 266 | Receiving Application: | 
|---|
| 267 | Message Type (770.11): | 
|---|
| 268 | No Subscriber Errors Found. | 
|---|
| 269 | Application is INACTIVE. | 
|---|
| 270 | REPORT-VARNAME | 
|---|
| 271 | MONITOR-NAME | 
|---|
| 272 | DECLARE called - | 
|---|
| 273 | message is completed | 
|---|
| 274 | HL7 Monitor - | 
|---|
| 275 | Mail message # | 
|---|
| 276 | Turn on/off Event Monitors | 
|---|
| 277 | Recent Checks of the Monitor by Master Job | 
|---|
| 278 | Check-time | 
|---|
| 279 | Event monitor status | 
|---|
| 280 | Press RETURN to continue... | 
|---|
| 281 | Requeue minutes | 
|---|
| 282 | 0 [Immediate Run] | 
|---|
| 283 | Notification mail group | 
|---|
| 284 | Parameter - | 
|---|
| 285 | STATUS-MASTER JOB | 
|---|
| 286 | STATUS-EVENT MONITORING | 
|---|
| 287 | Change ' | 
|---|
| 288 | ... nothing changed ... | 
|---|
| 289 | HL Event Monitor - # | 
|---|
| 290 | -------- Master job status is | 
|---|
| 291 | NOT SET YET | 
|---|
| 292 | -------- Event monitoring status is | 
|---|
| 293 | Unknown last master job run time... | 
|---|
| 294 | Unknown next master job run time... | 
|---|
| 295 | Unknown last master job run... | 
|---|
| 296 | Last master job run was | 
|---|
| 297 | Unknown next master job run... | 
|---|
| 298 | Next run | 
|---|
| 299 | in the future... | 
|---|
| 300 | Monitor description: | 
|---|
| 301 | ' event monitor has completed. | 
|---|
| 302 | Variable List | 
|---|
| 303 | ####################    ####################    #################### | 
|---|
| 304 | ####################    ####################    #################### | 
|---|
| 305 | ####################    ####################    #################### | 
|---|
| 306 | ####################    ####################    #################### | 
|---|
| 307 | ####################    ####################    #################### | 
|---|