Announcement

Collapse
No announcement yet.

Site deployment with other HL7 engines

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Site deployment with other HL7 engines

    Hi all,

    We're trying to connect mirth on site with their existing HL7Connect tool by Kestral.
    Does anyone have experience with doing this before?

    We are attempting to read their ADT feed with our mirth code using a LLP reader.
    On our end, mirth fails to start the inbound channel. System logs shows an exception, error in connecting socket.
    ITS admins on site says they see the same message over on their end as well.

    Any ideas on what we can try?

    Thanks,

    -- Alan

  • #2
    Re: Site deployment with other HL7 engines

    Can you post the full stack trace from the log?

    Thanks,
    -Chris
    Chris Lang

    Comment


    • #3
      Re: Site deployment with other HL7 engines

      Heres the exception trace from the Mirth system log:

      org.mule.providers.FatalConnectException: ReconnectStrategy "org.mule.providers.SingleAttemptConnectionStrateg y" failed to reconnect receiver on endpoint "tcp://10.3.2.16:20055"
      at org.mule.providers.SingleAttemptConnectionStrategy .doConnect (SingleAttemptConnectionStrategy.java:34)
      at org.mule.providers.AbstractConnectionStrategy.conn ect(AbstractConnectionStrategy.java:67)
      at org.mule.providers.AbstractMessageReceiver.start(A bstractMessageReceiver.java :396)
      at org.mule.providers.AbstractConnector.registerListe ner(AbstractConnector.java:518)
      at org.mule.providers.tcp.TcpConnector.registerListen er(TcpConnector.java:389)
      at org.mule.impl.model.AbstractModel.registerListener s (AbstractModel.java:221)
      at org.mule.impl.model.AbstractModel.start(AbstractMo del.java:353)
      at org.mule.MuleManager.start(MuleManager.java:730)
      at org.mule.config.builders.MuleXmlConfigurationBuild er.configure (MuleXmlConfigurationBuilder.java:207)
      at org.mule.config.builders.MuleXmlConfigurationBuild er.configure(MuleXmlConfigurationBuilder.java:194)
      at com.webreach.mirth.server.Mirth.startMule(Mirth.ja va:164)
      at com.webreach.mirth.server.Mirth.restartMule (Mirth.java:147)
      at com.webreach.mirth.server.Mirth.run(Mirth.java:103 )
      Caused by: org.mule.providers.FatalConnectException: ReconnectStrategy "org.mule.providers.SingleAttemptConnectionStrateg y" failed to reconnect receiver on endpoint "tcp://10.3.2.16:20055"
      at org.mule.providers.SingleAttemptConnectionStrategy .doConnect(SingleAttemptConnectionStrategy.java:34 )
      at org.mule.providers.AbstractConnectionStrategy.conn ect(AbstractConnectionStrategy.java:67)
      at org.mule.providers.AbstractMessageReceiver.connect (AbstractMessageReceiver.java:353)
      at org.mule.providers.SingleAttemptConnectionStrategy .doConnect(SingleAttemptConnectionStrategy.java:32 )
      ... 12 more
      Caused by: org.mule.providers.ConnectException: Failed to bind to uri "tcp://10.3.2.16:20055"
      at org.mule.providers.tcp.TcpMessageReceiver.doConnec t(TcpMessageReceiver.java:97)
      at org.mule.providers.AbstractMessageReceiver.connect (AbstractMessageReceiver.java:360)
      at org.mule.providers.SingleAttemptConnectionStrategy .doConnect (SingleAttemptConnectionStrategy.java:32)
      ... 15 more
      Caused by: java.net.BindException: Cannot assign requested address: JVM_Bind
      at java.net.PlainSocketImpl.socketBind(Native Method)
      at java.net.PlainSocketImpl.bind (Unknown Source)
      at java.net.ServerSocket.bind(Unknown Source)
      at java.net.ServerSocket.<init>(Unknown Source)
      at org.mule.providers.tcp.TcpMessageReceiver.createSo cket(TcpMessageReceiver.java:134)
      at org.mule.providers.tcp.TcpMessageReceiver.doConnec t(TcpMessageReceiver.java:95)
      ... 17 more

      {}

      I don&#039;t have access at the moment to the error message in HL7Connect. But when possible I&#039;ll try and post it to this thread as well.

      Thanks,

      -- Alan

      Comment


      • #4
        Re: Site deployment with other HL7 engines

        You are setting up an LLP listener - the IP address should be the ip address of the local interface you want to bind to. Usually 127.0.0.1 if you only have one network interface.

        If you want to send data from Mirth to HL7Connect, you would use a LLP Sender on the destination.

        -Chris
        Chris Lang

        Comment


        • #5
          Re: Site deployment with other HL7 engines

          Ah, ok. Then its a problem of who should establishes the connection / who is acting as server/client.
          So it sounds like in LLP listening mirth actually establishes a port and waits for the sender to connect and then send messages to us.

          With HL7Connect, they are giving us an IP & port to connect to before they send messages to us.
          In that case, what do we use for that in Mirth?

          Side note: We&#039;ve been using mirth-1.3.2, now that I&#039;ve discovered 1.4.0, i&#039;m trying to import our channel to experiment.

          Many thanks.

          -- Alan

          Comment


          • #6
            Re: Site deployment with other HL7 engines

            Alan,
            I retract my previous post here - I checked out the HL7 Connect page for outgoing:

            http://www.hl7connect.com/demos/outdemo1.ksp

            It looks like HL7 Connect needs to be set to "Client" mode to talk to Mirth.

            We will look into allowing Mirth to operate with "Server" mode for 1.5. In the meantime, can you add this issue to the JIRA?

            Thanks,
            -Chris
            Chris Lang

            Comment


            • #7
              Re: Site deployment with other HL7 engines

              Thanks for your reply. I&#039;ll ask the sys-admins to switch to "client" mode in HL7Connect if possible and post the results if any.

              I&#039;ve added this issue to JIRA "MIRTH-299"

              -- Alan

              Comment


              • #8
                Re: Site deployment with other HL7 engines

                It&#039;s icredible the ways of violating MLLP people found

                Comment


                • #9
                  Re: Site deployment with other HL7 engines

                  "The hardest part of interoperability is the whole interoperability part".

                  If every other system in the world followed the standards, Mirth would be much simpler, however we HAVE to work with the systems currently deployed...Catch 22 as we break the standards in the name of interoperability.

                  -Chris
                  Chris Lang

                  Comment


                  • #10
                    Re: Site deployment with other HL7 engines

                    Very true...standards work best when actually followed. Rather difficult otherwise.
                    But our project at the moment is at the mercy of the systems at each site we deploy, as our main task is to just latch on to their feeds.

                    Thanks for the help.

                    Cheers,

                    -- Alan

                    Comment

                    Working...
                    X