Based on the data, you are trying to view HL7 data in UE. I have been doing so for 9 years now (I'm in the healthcare field) and UE works just fine. The issue is your end of message delimiter. Usually in HL7 it's hex 1C0D, not 0D0A. If you have UE set to "Save file as input format", it reads the 0D character at the end of each segment and (for display purposes), changes it to 0D0A so that each segment shows up on a different line (very handy I think). However, when it goes to save the file, it changes all the 0D0A combinations back to 0D. But since your messages ALSO end in 0D0A, it changes them as well. My guess is that the application that writes your HL7 messages to a log file changes the 1C0D to a 0D0A so that someone could somewhat view the data in notepad, even though it looks horrendous in notepad. Can you change your application so that is does NOT change the 1C0D characters to 0D0A? If not, you can run a macro on your HL7 files when you first open them that will change the 0D0A to 1C0D, close and reopen the file and viola, UE will not mess with the end of message delimiter any more.
Hope this helps,