Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

HL7 generates error if text looks like xml tags

  • Filter
  • Time
  • Show
Clear All
new posts

  • HL7 generates error if text looks like xml tags

    The following HL7 generates an error when it is transformed into XML:
    OBX|47|ST|1:RPT^Radiology Report||File ?: Y < Enter>||||||F|

    The "<Enter>" segment should be html encoded before the raw message is transformed into xml, otherwise it generates an error. Then when assembling the message back into HL7, the data should be unencoded. Where is the best spot to ecode/decode the data, and are there any code samples?

    The error is:
    ERROR-300: Transformer error
    ERROR MESSAGE: Error evaluating transformer
    com.webreach.mirth.server.MirthJavascriptTransform erException:
    CHANNEL: RAD - Incoming
    CONNECTOR: sourceConnector
    DETAILS: TypeError: error: </OBX.5.1> does not close tag <Enter>.
    at com.webreach.mirth.server.mule.transformers.JavaSc riptTransformer.evaluateScript(JavaScriptTransform
    at com.webreach.mirth.server.mule.transformers.JavaSc riptTransformer.transform(JavaScriptTransformer.ja va:307)
    at org.mule.transformers.AbstractEventAwareTransforme r.doTransform( 8)
    at org.mule.transformers.AbstractTransformer.transfor m(
    at org.mule.transformers.AbstractTransformer.transfor m(
    at org.mule.transformers.AbstractTransformer.transfor m(
    at org.mule.impl.MuleEvent.getTransformedMessage(Mule
    at org.mule.routing.inbound.SelectiveConsumer.isMatch (
    at org.mule.routing.inbound.InboundMessageRouter.rout e(
    at org.mule.providers.AbstractMessageReceiver$Default InternalMessageListener.onMessage(AbstractMessageR
    at org.mule.providers.AbstractMessageReceiver.routeMe ssage(
    at org.mule.providers.AbstractMessageReceiver.routeMe ssage(
    at com.webreach.mirth.connectors.mllp.MllpMessageRece iver$TcpWorker.processHL7Data(MllpMessageReceiver. java:440)
    at com.webreach.mirth.connectors.mllp.MllpMessageRece iver$TcpWorker.processData(MllpMessageReceiver.jav a:419)
    at com.webreach.mirth.connectors.mllp.MllpMessageRece iver$
    at .java:290)
    at eadPoolExecutor$Worker.runTask(ThreadPoolExecutor. java:650)
    at eadPoolExecutor$ :675)
    at Source)

  • #2
    Re:HL7 generates error if text looks like xml tags

    I don't think you'll have this problem in 1.7.1. If you're using 1.7.0, make sure to enable "Encode Entities" in the message properties. You can locate them under the Message Template tab.
    Chris Ro
    Sr. Software Engineer | Mirth Corporation