[Kathy Zwilling]

Ok, thanks alot for both explanations!  That helps alot!

[Kathy Zwilling]

Thank you that explanation.  

It must be that I don’t understand how the split command is working then.  I really anticipated that it would create the list be making an element from each “segement prior to the segment terminator.   It looks like it is also creating an element at the end of the list (empty) for a set of data after the last segment terminator but there is no segment there.   What am I not seeing?

[Kathy Zwilling]

Is it normal to have a CR at the end of the last segment of an HL7 message?

[Kathy Zwilling]

Does anyone know why the split command would generate an empty element at the end of the message?

[Kathy Zwilling]

Thank you!  Tried that and it looks like it is working.

[Kathy Zwilling]

Tim,

I have been having this same issue and found your email.   Has the resolution that you described fixed this for good?

Why the tee command?

Thanks,

Kathy Zwilling

[Kathy Zwilling]

Thanks, Richard!

[Kathy Zwilling]

Richard,

I would be very interested in your Perl script.  Would I be able to get that form you or would you be willing to post it for all of us?

Thank you!

Kathy

[Kathy Zwilling]

The smiley face s/b chr28.

[Kathy Zwilling]

Thanks to Jim Koslosky for helping me with this.  

I had a variable in my tcl code fragment that was not getting initiated so it was storing the contents of the previous message’s NTE and adding to it!  What a relief!

[Kathy Zwilling]

See xlate in a word document file.  Hopefully this looks better.

[Kathy Zwilling]

Thank you!  I will give it a try!

[Kathy Zwilling]

Jim,

Thanks for the response.  Yes, I know I can do this thru the xlate and I have done this but I have a situation where I am not using xlates and looking for a tclproc to be able to do this in a hurry.

Thanks,

Kathy

[Kathy Zwilling]

We started experiencing this same error in the last week and it has occurred 3 times now so I am anxious to find a way to “fix” it.   We are on 5.2 rev. 1.

In our case, the data does stop processing completely like the connections are frozen in the site affected.  All connections are showing “up” and “green” but data is not either coming in or going out.

It seems to me that the monitor daemon has to be related to this because the site that is affected is “frozen” with no data processing and when I stop the Monitor Daemon the data starts to flow.  Note is does not wait for me to start the monitor daemon back up.

This is happened in 3 different sites in the past week so it is not the same site each time.

Any ideas what might be happening?  The messages I am getting are the same as those listed in the email above.

Should I implement a cron to cycle the monitor daemon daily to avoid this?

Thanks for your help!

Kathy Zwilling

[Kathy Zwilling]

Thanks, Jim.   I will give that a try.  I just wanted to make sure there wasn’t some something special there.

[Author]

Replies