@abe-rastkar
Forum Replies Created
-
AuthorReplies
-
Hi,
I am assuming that you need to extract the list of OBR segments for each ORC segment in your report.
since you are searching the segment list in general, it finds all OBR segments without regard to which ORC they belong to.
the search for the OBR segment should be limited to the OBR’s preceding the next ORC. so if you search for the next OBR one at a time (until you get to the next ORC), rather than using the -all parameter, it should give you the list you need.
The code is correct although the indices may need to be fixed.
index of OBR 23 will give you the 23rd field because the segment name, OBR, has the zero index. So the “set id” field has the index 1, etc.
Should the index of the MSH segment in SEGMENTS be 0 rather than 9?
++++
set fldSep [string index $msg 3]
set SEGMENTS [split $msg r]
set msh8 [lindex [split [lindex $SEGMENTS 0] $fldSep] 7]
set OBR [split [lsearch -inline -regexp $SEGMENTS {^OBR}] $fldSep]
set obr24 [lindex $OBR 24]
if {$msh8 ne “RESULTOUTASCII” && $obr24 ne “HEN”} {
return “{KILL $mh}”
} else {
return “{CONTINUE $mh””
}
July 16, 2012 at 4:17 pm in reply to: Readin PDF files and sending imbedded PDF trough interface #76796We have an interface that receives PDF messages from surgical pathology Coded in MIME embedded in HL7. We send the messages to the EMR system where it is translated back to PDF.
The contents of the variable containing the state 14 message must be cleard as soon as you receive the ACK message (the first thing).
Kamal,
The error that you have listed is caused when the global variable containing your state 14 message is not empty when the engine is trying to store the next message sent in the same variable. The message is sent successfully because this happens in the SEND_OK UPoC. It will put y our message in the error database.
The errors inicating that the that the remote side of the connection was dropped may be related. But not necessarily.
It seems like since you used a comma as the field separator, it picked up both fields as one. the -t represents a separator in the input and the output files. The following is from the man page -t Character Uses the character specified by the Character parameter as the field separator character in the input and the output. Every appearance of the character in a line is significant. The default separator is a space. With default field separation, the collating sequence is that of the sort -b command. If you specify -t, the sequence is that of a plain sort. To specify a tab character, enclose it in single quotation marks.
September 29, 2009 at 7:00 pm in reply to: splitting OBX message and moving the split message into NTE #68055Bala,
It looks like they used the tilde character, ~, instead of a line break. Replace them with a line break.
Mike, use “new line terminated” option in the file format entry of the protocol setup. If the original message is in an outbound queue, we use the OVER message disposition for the copy of the message we want to send to the inbound queue. Then the message can be routed in a normal way to an outbound thread, based on the message TRXID May 15, 2009 at 8:36 pm in reply to: Iterating through table instead of using switch statement #67853Good point, Steve
Abe
Steve Carter wrote:The keyed list works well on a uni-directional table.
May 15, 2009 at 7:06 pm in reply to: Iterating through table instead of using switch statement #67851The tcl script is a goo idea.
I have the same script as a proc except my proc creates a keyed list where the input to the table is the key and the value of the table entry is the keyled list value.
Regarding alerts. It would be good if the alert server could repeat the alert message per a given period if the condition of the alert is not changed. For example if a thread is in opening state, an alert is sent when it is detected. But only once. This proposed change would optionally allow the alert to go off periodically (per configuration) until it is fixed or cancelled. November 15, 2006 at 8:49 pm in reply to: PDL TCP/IP Protocol Properties : ‘Close after write’ #60010Before you change anything you need to find out if the message gets to the recieving system. If it does not, you need to find out where the interrunpt is. (fr example the firewall). How long is it between the first message and the second one? Could the firewall be timing out the message? If the message gets there and the receivin system does not reply, then the problem is in the receiving interface processing.
Nancy,
The quote characters may be needed by the receiving application. If So, then you can insert an escape character before each double quote.
For example,
regsub -all — “”” $str {\”} newstr
Where str is you message or segment.
Abe Rastkar
UMO Health Care
-
AuthorReplies
