@tim-hallbauer
Forum Replies Created
-
AuthorReplies
-
Thanks for the suggestions.
It turned out that there were some old processes that were running ‘in memory’ identified.
HCIENGINE, HCIENGINEWATCH and HCIMONITORD
Once these were killed, the process started.
Tim
Additionally, when I issue the command to stop the process, I get a return that it is not running. When I issue the command to start it I get a message that it’s already running.
We just had another call. Apparently the sending system had multiple interfaces pointing to us running at the same time. They got rid of the unnecessary ones and now it seems to be working????
Thanks for the help.
Tim
James,
It’s just plain with no encoding. Like I said, I ran a Dev inbound saved transaction and a Prod inbound saved transaction through the same code. The Dev worked and the Prod didn’t.
Tim
Charlie,
Don’t know. It’s the one that has always been used and there were no complaints from vendors until now.
I did what you suggested and the proc I had been using didn’t echo the &.
I also tried the hl7Raw_ack and it did. I guess I’ll change to that one.
Thanks,
Tim
We have a Family Practice department that has their own system. I utilize a table with their assigned HIS number to route or kill result transactions to that system. We also utilize another table to route results from resident ordered tests to the attending for co-signature. It works very well and as stated before is easier than changing a list of entries in a TCL proc.
Tim
Keith, Thanks. I was just going to post that I had resolved the issue using something from a post I found. It is very similar to what you suggested.
regsub -all {CD:d*} $msgdata “” newMsg
Tim
Thanks, I tried Daniel’s suggestion and it worked like a charm. I was missing the “?” .
James,
Thanks. Four hops and I was there. I think either their config has something weird / missing, or they aren’t actually listening and think they are. BUT as is usually the case with vendors, it’s up to us to prove it’s on their side
Tim
I had already looked at them and they set to the standard settings. Thanks Russ,
I’ll poke around more. I do agree that the 1 minute disconnect is going to be a problem. I am thinking it has more to do with the firewall/VPN/firewall configurations rather than the Cloverleaf app, but as of yet there hasn’t been a solution. Of course the vendor thinks it’s Cloverleaf. This is also going to be a very low volume connection with a max of ~ 100 transactions per day.
Thanks again,
Tim
Thanks, I have been out of the office for a few days. I’ll run this by them.
Our engine is running on Red Hat Linux. They are on Windows 2003 R2 Second Edition SP2.
When we first started this project, we had firewall issues. The searches I did regarding the problem just kept referencing that the 2 don’t ‘play well together’. We still are having intermittent issues pinging.
What they have me doing now is stopping and starting the outbound connection every half hour. I am assuming that is to try to prevent their side from timing out or going to sleep although they are saying it is to prevent my side from dropping. The configuration of the outbound connection is just like every other one we currently have running without issues. It seems to be working for now.
Before this, my side could be up and have several transactions queued up but not going. If I cycled the connection, sometimes they would go, but more often I would go into an Opening state. I would send them an email and magically a few minutes later we would come up although ‘they didn’t do a thing’. I am not saying they did, but something caused us to connect.
Thanks again. I just looked and the messages coming from our HIS (Cerner) do have the 0D 0A at the end. I will look into removing the 0A.
Thanks Guys, That’s what I thought. It just like all of the other interfaces that we have. I’ll contact them again to se what they say.
-
AuthorReplies
