Forum Replies Created
-
AuthorReplies
-
Thanks Gary – however, it appears that the process to save the files is based on file size. I would like to have this scheduled to occur once a day regardless of file size. July 17, 2009 at 4:25 pm in reply to: Perform a stop and restart of thread after each message #68639The receiving vendor wants this for flow control on their end. It does not make any sense. At this time, the issue is in their court as to a resolution.
In the meantime, I will continue to resend every 2 minutes when an ACK is not received.
July 16, 2009 at 8:02 pm in reply to: Perform a stop and restart of thread after each message #68637They want the socket stopped then started
between result messages.July 16, 2009 at 5:27 pm in reply to: Perform a stop and restart of thread after each message #68633Would it be possible to use a tcl proc that will stop/start the thread after each message is sent or after each ACK is received?
July 16, 2009 at 1:14 am in reply to: Perform a stop and restart of thread after each message #68631I apologized – I am using version 5.3 running on Windows 2003.
I tried this with removing blank NTE’s and it seems to work:
regsub -all — {NTE|d*?||r+} $msg {} msg
Thanks for the input !
Here is an example:
NTE|4||
The ‘4’ could be any number, which may get tricky. I want to be able to only removed the blank NTE’s as shown above and allow the NTE’s with data to continue.
Quick question – Would it be possible to create a condition to only remove the segment if the contents of the segment are empty?
Great topic – quick question: What specific files/directories should be backed up?
With our HIS – we have an account number, for financial purposes, and a MRN number, which identifies the patient. The problem I am seeing is that our ADT is account number driven, and RALS will accept and apply the ADT to the MRN, ignoring the account number. This leads to ADT transactions updating a MRN rather than an account, which is not what we want to occur. We have scenarios where multiple account numbers for the same person (i.e. the same MRN) will exist concurrently within RALS. Any suggestions? Thank you Gary for your response. I actually resolved the issue over the weekend. I found that I had a ‘vista.taf’ file in the root of the site directory. The cleanup instructions stated to remove the vista.taf file from the execdatabases directory, not mentioning that it may be present in other areas. Once I removed all occurrences of the vista.taf file, I was back in business. I still had the error with 2 processes, so I created new ones. March 1, 2007 at 2:48 am in reply to: How to receive an alert when certain message type is found #60683Bryan, Thanks ! It works fantastic. I made a few modifications so that the message will continue regardless of type.
Hello Gary, Look for an IF statement or other condition within the tcl procedure where dipList is evaluated. Here’s an example:
if [cequal $filter “ER”] {
lappend dispList “CONTINUE $mh”
} else {
lappend dispList “KILL $mh”
}
Hope this helps.
The double quotes did the trick, although I thought I tried that before posting. I must have added or removed an extra space. Thanks,
Matt
Thank you, Dirk (Danke sch -
AuthorReplies