Tweet
We are required, as the first step in our process, to save the original message to a database, no matter how hideously formatted it is.
For the most part, this works well, except a file I've come across that doesn't seem to get to the preprocessing script. It appears to be a combination of having the message start with "MSH" and not having a 2nd line in the file.
msh_okay.txt - Seems to work fine
msh_bad.txt - Seems to not make it to the preprocessor
xxx_okay.txt - Seems to work fine
I have attached the channel and the 3 files.
I'll continue to run it through the debugger, but any help/hints would be greatly appreciated...
sample.gz (1515 bytes)
Post edited by: jeffkeller, at: 05/03/2007 10:52
Post edited by: jeffkeller, at: 05/03/2007 10:52
For the most part, this works well, except a file I've come across that doesn't seem to get to the preprocessing script. It appears to be a combination of having the message start with "MSH" and not having a 2nd line in the file.
msh_okay.txt - Seems to work fine
MSH|^~\\&|YYY|XXXX^ZZ|AAAA|SOME HOSP|20070413125351||ORU^R01|6543_20070413125351|P |2.2||
MSH|^~\\&|YYY|XXXX^ZZ|AAAA|SOME HOSP|20070413125351||ORU^R01|6543_20070413125351|P |2.2||
XXX|^~\\&|YYY|XXXX^ZZ|AAAA|SOME HOSP|20070413125351||ORU^R01|6543_20070413125351|P |2.2||
I'll continue to run it through the debugger, but any help/hints would be greatly appreciated...
sample.gz (1515 bytes)
Post edited by: jeffkeller, at: 05/03/2007 10:52
Post edited by: jeffkeller, at: 05/03/2007 10:52
Comment