English	French	Notes	Complete/Exclude
CHECK 773 AC XREF			
HL7DevelopmentTeam@med.va.gov			
LINK (870) CHECKS			
Environment check OK...			
Warning			
Press RETURN to 			
There are inbound queues with un-processed messages.  Before patch HL*1.6*109			
can be installed, the inbound queues must be empty.  You may continue loading			
these patches.  But, remember to clear the inbound queues before loading.			
(To clear the queues, start one or more incoming filer(s) to process the			
messages until there are no messages in the queue.)			
incoming filer(s) to process the messages until there are no messages in the			
queue.  Then, try to install patch HL*1.6*109 again.			
Conversion already run!			
Post-init will identify all incomplete messages associated with TCP links			
These incomplete messages were a result of Network errors			
encountered by the DIRECT CONNECT API.			
These messages will be removed from the outbound TCP queue.			
Scanning for incomplete messages...			
No messages in the outbound TCP queue.			
Installation of PROTOCOLS not performed			
Installation of LIST TEMPLATES not performed			
Running of file conversions not performed			
Select output device for file conversion: 			
Running of the file conversions not performed			
FILE CONVERSIONS REQUIRED BY INSTALLATION OF HL7 V1.6			
** Running of file conversions could not be queued **			
**  File conversions will be run interactively  **			
Running of file conversions queued as task number 			
Task will begin execution on 			
- File conversions started on 			
Copying entries from HL7 NON-DHCP APPLICATION PARAMETER file (#770)			
to HL7 APPLICATION PARAMETER file (#771) 			
** Conversion halted **			
** Unable to lock HL7 APPLICATION PARAMETER file **			
** Use the entry point REQUEUE^HLPOST to requeue the file conversions **			
** Unable to lock HL7 NON-DHCP APPLICATION PARAMETER file **			
* Entry number 			
 does not have an application name			
* Unable to copy 			
** Conversion of files has been asked to stop **			
Purging data from HL7 MESSAGE TEXT file (#772) 			
Converting newly defined fields in HL7 MESSAGE TEXT file (#772) 			
* Unable to lock entry number 			
  -  entry not converted			
 does not have a date & time of message			
- File conversions completed on 			
Do you wish to continue ? 			
Post-init was already run on 			
This post-init has already been run.  Answering 'YES' will allow you to			
selectively re-run portions of the post-init.  If you do not want to do			
this, answer 'NO' (the default response).			
Do you want to re-install PROTOCOLS ? 			
This package distributes a set of protocols which may have already			
been installed.  Answering 'YES' (the default and recommended response)			
will re-install these protocols.			
Do you want to re-install LIST TEMPLATES ? 			
This package distributes a set of list templates which may have already			
will re-install these list templates.			
Do you want to re-run the file conversions ? 			
Installation of this package requires that a set of file conversions be			
run.  Answering 'YES' (the default and recommended response) will allow			
these conversions to be re-run.  Answer 'NO' if the file conversions			
have already run to completion.			
Starting Pre-Init			
RESULTS RPT/STATUSCHNG-DATE/TI			
.01///RESULTS RPT/STATUS CHNG-DATE/TIME			
Pre-Init Finished			
S.HL SERVER			
Missing subscription control number.			
Missing logical link.			
Invalid Subscription Control number			
Invalid Logical Link			
Invalid logical link			
Invalid receiving application.			
Note:  You must select a Non-DHCP Application for which an HL7 Device has			
been defined.			
HL7 Message Processor for 			
 is already tasked.			
-1^Did not pass valid pointer to Message Text file (#772)			
Application Reject			
Application Error			
Error During Receipt of Acknowledgement Message			
 - Application Reject			
 - Application Error			
Failed to create an Event in STATUS^HLTF0: 			
Application Error Text: 			
Initial Message in this transaction protocol:			
  Initial Message ID: 			
  Logical Link of Initial Message: 			
  Inital Message Type: 			
  Inital Message Event: 			
HL(772			
 at GENERATE^HLTP entry point			
 at PROCESS^HLTP0 entry point			
AA,CA			
 at GENACK^HLTP1 entry point			
 at PROCACK^HLTP0 entry point			
MTP_ETP			
Missing MSA segment			
Incorrect sending app.			
INIT-1			
INIT-2			
 at CHK^HLTPCK1 entry point			
Field Separator Missing			
Invalid Field Separator			
Encoding Characters Missing			
Invalid Encoding Characters			
Invalid Message Header Segment			
ACK,ADR,MCF,MFK,MFR,ORF,ORR,RRA,RRD,RRE,RRG,TBR			
MSA Segment Missing			
AL,NE,ER,SU			
Invalid accept ack type			
Invalid application ack type			
Missing HL7 Version			
Original Outgoing Message not found			
Event Protocol pointer (field #772,10) missing			
Event Type REQUIRED			
Invalid Event Type			
Invalid Message Structure Code			
Missing Sending Application			
Invalid Message Control ID in MSA Segment			
Event Protocol not found			
Invalid Receiving Application for this Event			
Missing required receiving facility			
Receiving Facility/App Parameter mismatch.			
Receiving Facility mismatch.			
Missing required sending facility			
Sending Facility/App Parameter mismatch.			
Unrecognized domain in sending facility			
Invalid HL7 Processing ID			
Cannot validate PROCESSING ID			
Processing ID Mismatch with Event Driver			
Processing ID Mismatch with Site Parameters			
Invalid access code			
Invalid HL7 Version for Receiving Application			
Event Protocol pointer (field #773,8) missing			
Event Type Required			
Unrecognized/ambiguous domain in sending facility			
HL7 Message 			
Unable to determine receipients for mail message.			
Unable to transmit HL7 message due to the following Application Error:			
Non-DHCP			
 Application Name			
Invalid Non-DHCP Application Name			
Invalid DHCP Application Name			
DON'T ADD.  COLLECT3~HLUCM003			
HLUCM 			
HLUCM Data			
Print Totals Report & Debug Data to Screen			
OK! No ^TMP(TOTALS,$J) totals report will be printed...			
No ^TMP($J,			
) debug data exists...			
Press RETURN to restart, or '^' to exit... 			
Debug Data from ^TMP($J,			
Print raw DEBUG DATA (Y/N): Yes// 			
Print filtered DEBUG DATA (Y/N): Yes// 			
You will be allowed to print report totals (from ^TMP(TOTALS,$J), and/or you			
may print the debug data (in ^TMP($J,			
Report Totals from ^TMP(			
Print REPORT TOTALS (Y/N): Yes// 			
Include subtotals (Y/N): NO// 			
Printing from 			
Enter subscript holding the ^TMP(TOTALS,$J) data: 			
You must pass in the initial subscript and $JOB number...			
Some entries were not included in the totals.  There are 3 possible reasons			
for entries being excluded: (1) The beginning time of a message or unit is			
before the report's start time, (2) The number of seconds to transmit the			
message is over 1799 seconds, and (3) The protocol or namespace doesn't meet			
Failure Reason			
Beginning time too early			
Excessive xmit time			
Prot/Nmsp mismatch			
Totals:			
ZZZ~0			
DEBUG GLOBAL			
INVALID START TIME			
INVALID END TIME			
END TIME PRECEDES START TIME			
BOTH NAMESPACES(S) AND PROTOCOL(S) MUST BE PASSED SPECIFICALLY			
INVALID NAMESPACE PARAMETER			
INVALID PROTOCOL PARAMETER			
CAN'T FIND PROTOCOL			
Display of ^TMP($J,			
Type Totals			
Enter text in messages to include and exclude...			
Restrict # messages: 999// 			
No data exists...			
No matching entries found...			
 matching entries displayed...			
 entries skipped...			
Every parent node that includes one of the EXCLUDE values that you enter now			
will not be included in the entries displayed.			
Every parent node that doesn't include one of the INCLUDE values that you			
enter now will not be included in the entries displayed.			
 XTMP-stored Reports 			
Run-time			
API Call			
You may choose to print the totals report from stored XTMP data if you like.			
If so, enter the number of the XTMP report from above now.  (Otherwise,			
press RETURN.)			
Enter XTMP Report#: 			
STARTandEND			
TO ID			
NMSP(			
HEC 			
VAFC ADMIT			
VAFC ADT			
VAFH A			
VAFH CLIENT A			
REMOTE RPC^			
Print T nodes(Y/N): No// 			
Print X nodes(Y/N): No// 			
Print U nodes(Y/N): Yes// 			
No data found.  Press RETURN to continue...  			
About to print ^TMP(			
,$J) data report.  Press RETURN...			
 Total   Total   Total  Main			
#Chars   #Msgs    #Sec  Sort Sub1 Sub2 Sub3			
DATA(			
HL7 DHCP Application Parameters			
HL7 Non-DHCP Application Parameters			
HL7 Message Types			
HL7 Segment Names			
HL7 Data Types			
HL7 Version Numbers			
HL7 Fields			
Log of HL7 Transmissions in Awaiting or Pending Status			
EZ,?			
Log of Failed HL7 Transmissions			
Select the Non-DHCP Application for which you wish to start/stop the HL7 log			
of transmissions.			
You must define an HL7 Device for this Non-DHCP Application before you can			
start the log.			
The HL7 log is currently turned 			
Do you want to purge existing log entries			
Don't			
 (#772,15), is set to 1.			
queue job			
start purging			
, or enter '^' to exit... 			
  no task started...			
HLPDT(			
Purge HL7 message text on or before 			
 queued to run now...			
  Queuing of Purge task failed.			
NO-LOCK			
 entries purged...			
Looping through file 773...			
START-773			
END-773			
Looping through file 772...			
START-772			
END-772			
ABORTED-TASKMAN			
HLUOPT2 			
HLUOPT2 Message Body Deletion			
HLUOPT1 9999999.999999			
HLUOPT1 			
As purging jobs run, they record critical information in the ^XTMP global for			
later review.  (This information is updated every two minutes.) You can view			
purge information now...			
Option #1 displays all available purging data, for the last job.			
Option #2 displays the most valuable purging data, but not all data. This			
option includes data for the last purging job, plus previous puring jobs.			
Option #3 displays purging times and totals in a graphic representation.			
 Task-Number   Start-Time   Timestamp Finish-time     772@     773@     Time-NOW			
There is no currently running purge job...			
Any old jobs that exist will be shown above. The current (or last) purge job			
is shown below.  The information on each line will automatically refresh			
 seconds (or whenever you press RETURN.)			
Note!!			
 Enter '^' when you are ready to exit.			
Current (or last) purge job...			
HLUOPT1 9999999.99999			
Recent purge runs...			
HLUOPT1 Purging			
The '^HL(			
)' lock is already owned by another purge job!  So, this			
purge job cannot be started.			
Successfully Completed			
  Enter inclusive date up to which to purge SUCCESSFULLY COMPLETED			
  The suggested cutoff date to purge 'Successfully Completed' messages			
  is seven days prior to today.			
  Must be on or before 			
Awaiting Acknowledgement			
  The suggested cutoff date to purge 'Awaiting Acknowledgment' messages			
  is thirty days prior to today.			
  of status (except ERROR status)			
  The suggested cutoff date to purge all messages (except for 'Error' messages)			
  is 90 days prior to today.			
  Do you also want to purge messages with an ERROR status			
  Enter 'Yes' to purge entries whose status is 'error'.			
  If you have reviewed/resolved the cause of the problem of those			
  entries with an 'error' status answer 'Yes'.  Otherwise answer 'No'.			
    WARNING: You should have investigated all errors because purging			
             these messages permanently removes them from the system.			
    Enter inclusive date up to which to purge ERROR			
  The suggested cutoff date to purge 'Error' messages			
  Would you like to queue this purge?  			
  If run in the foreground, you will see dots and a total count.			
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
####################	####################	####################	
