Xlate: XML to HL7 ( Fatal Error )

Homepage Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Xlate: XML to HL7 ( Fatal Error )

  • Creator
    Topic
  • #50266
    Andre van Olden
    Participant

    Receiving Fatal Error from an Xlate where I am trying to copy data from an XML element to an OBX segment.

    The XML element does contain formatting characters ( line feeds etc.. ) and I need these for the formatted OBX.5.

    If I remove these control characters, the error goes away, but I need the formatting to remain for the display of the OBX in the receiving system.

    Tried compiling the .xsd with Formatting = ON with no success.  Any assistance would be appreciated.

Viewing 5 reply threads
  • Author
    Replies
    • #65391
      Jim Kosloskey
      Participant

      Andre,

      I am no XML expert by any means but isn’t there an escape mechanism in XML to escape control characters (like line feed) in the body of a data element?

      Moreover, if the receiving system is truly parsing HL/7 properly, I would expect the system to choke on unescaped line feeds imbedded in the observation text as that signifies end of segment in HL/7.

      email: jim.kosloskey@jim-kosloskey.com

    • #65392
      Robert Kersemakers
      Participant

      Hi Andre,

      You will need to replace the line feeds coming from your XML with .br for your HL7 in order to save the formatting. As Jim said: a line feed in HL7 means the end of the segment and will give you errors.

      There are only a few escape characters in XML:

      <        <    less than >       >    greater than

      &    &    ampersand

      '    ‘     apostrophe

      "    ”     quotation mark

      Everything else in between start/end tag is considered data, so you can include line breaks etc.

      Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

    • #65393
      Rick Martin
      Participant

      Hi Andre,

      Long time no talk!  Are the embedded characters encoded in the XML like this: ?

      I had posted something about that on this board last year.  In my case, the parser was treating those sequences as actual carriage return/line feeds.  I ended up having to strip them from the XML document before processing.  If you need them in the final document, you will probably have to substititute them with something else prior to processing.

      Rick

    • #65394
      John Hervatin
      Participant

      I have seen receiving systems that don’t like the .br.  Another substitution you could make is a tilde.  Then you will have created repetitions of the OBX-5 field.  Many receivers display each repetion on a separate line, so the tilde acts like a line break.

    • #65395
      Robert Milfajt
      Participant

      There was an excellent explanation of this in another thread.  The problem had to do with Cloverleaf only supporting ISO-8859 and not utf-8 or utf-16.  I cannot remember, but it was version specific.  Can someone dig up a link to that thread, it came out within the last few week.

      Robert Milfajt
      Northwestern Medicine
      Chicago, IL

    • #65396
      Robert Milfajt
      Participant

      Here is the other thread which explains this and the workaround.

      http://clovertech.infor.com/viewtopic.php?t=3006&highlight=utf16

      Hope this helps,

      Robert Milfajt
      Northwestern Medicine
      Chicago, IL

Viewing 5 reply threads
  • The forum ‘Cloverleaf’ is closed to new topics and replies.

Forum Statistics

Registered Users
4,966
Forums
28
Topics
9,106
Replies
33,627
Topic Tags
248