TESTING TOOL ERROR – XLT

[Stewart]

Getting an error when testing a translation with a SMAT DB from a different site.

Command output:

MESSAGE 1
Unable to fetch segment ‘MSH’ data
unable to get information on invalid HL7 message ” for parse

 

Topic

[Vince Angulo]

Check to see if you’re testing new line or length encoded.  L/E doesn’t start with MSH, it has a numeric value instead.

[Keith McLeod]

SOunds like you have possibly transferred these files where the segment termination character CR got converted to a CRNL.  The MSH segment goes but all of the other segments are invalid because they become messages without the require MSH segment.  You should see in Hex OD terminating each segment.  You may now be seeing either 0D 0A or simply 0A. Check to see what you have in the file….

[Stewart]

I switched to Length Encoded and the error went away.  Thanks.

[Stewart]

Still getting an error, this time it is related to the message missing the length.  I did check the SMAT DB and the MSH is in the messages.

[Robert Kersemakers]

If you’re testing ‘length encoded’ then each message should be preceded by a 10-digit length. If this is not the case, switch to New Line or EOL.
It all depends on how you saved/resend the message to file from SMATdb.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Stewart]

So the testing tool can only test from a file and cannot test directly from the SMAT DB?  Just to confirm, in order to test XLT’s using the testing tool, I’ll need to first export the message(s) to a file from the SMAT DB, and then run the XLT against the file?

[Robert Kersemakers]

Correct. As far as I know you can’t test directly from the SMAT DB.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Stewart]

Thanks Rob.  That was it.  Once exporting a message to a file I was able to test.

[Author]

Replies