Originally posted by: Margo

I am building XML output from HL7 2.5, and need to pass the MSH segment within the XML I'm building. The receiveing application reads the XML successfully the majority of the time, but occasionally has parser errors. When successfull, the application receives:

<requestOrigin>MSH|^~\&|PCN70^SJH <-- note the "&amp"

when the parser error happens:

<requestOrigin>MSH|^~\&|PCN70^SJH <-- note the lack of "&amp", only the ampersand itself is passed.

Does anyone else have this problem, is there a patch? I'm running 8.1 build 84 on UNIX.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: Margo

> I am building XML output from HL7 2.5, and need to
> pass the MSH segment within the XML I'm building.
> The receiveing application reads the XML
> L successfully the majority of the time, but
> occasionally has parser errors. When successfull,
> the application receives:
>
> <requestOrigin>MSH|^~\&|PCN70^SJH <-- note the
> "&" ||||| The actual text is the "&" followed by "amp" for the escape|||||

Arg! this editor must have a very good parser! :)
>
> when the parser error happens:
>
> <requestOrigin>MSH|^~\&|PCN70^SJH <-- note the lack
> of "&", only the ampersand itself is passed.
>
> Does anyone else have this problem, is there a patch?
> I'm running 8.1 build 84 on UNIX.

#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: janhess

I had to get a patch from support to get escaped exclude characters to work at all. Perhaps you need it.
The patch is user specific so you will need to raise a fault. I believe it is fixed in the service pack.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

I believe I had a similar problem and I resolved it by defining initiators & terminators in the type tree for the value element of <CDATA> & </CDATA>. Then the XML package was passed without parsing.

Jim Divoky
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: thorstenhirsch

I also had this problem when putting XML data into a SOAP envelope. All the characters were transformed to quoted text.

You can specify an "any" element in your xsd with processContents="lax". Then you put the inner XML data into this any element with PACKAGE().
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: thorstenhirsch

Maybe it's sufficient to specify processContents="lax" for you requestOrigin element.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: Margo

Jan,

Do you still have the case number that resulted in the patch? Support would like it so that they can provide me the patch as well, Thanks!
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

Margo,
I had a number of issues with xml. The UK support no's were 485065*EMEATX - dsmapconv fails, 488312*EMEATX - no namespace & 488314*EMEATX - not escaping special cahracters in output.
These might also be useful PMR 20543,019,866 - XML checked via VALIDATE() function fails & PMR 20514,019,866 - VALIDATE() function always seems to return -1
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

Service pack 2 8.1.0.2 is now available. It seems to have cured these problems.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender