How to split large ADT thread

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf How to split large ADT thread

  • Creator
    Topic
  • #48182
    Rich Durkee
    Participant

      We have a large number of applications that need ADT information which comes from the infamous SMS flat record. So we translate the SMS ADT message to HL7 format and send it to 18 threads right now and more are coming soon. This logic was created seven years ago with only a few threads needing ADT info but as the years pass and we add more and more threads that receive ADT info, we realize this is not a good situation. We would like to reduce the dependence on this one thread and make the processing more balanced.  

      Would it make sense to take the SMS flat record, translate it into a HL7 message, send that message to three threads possibly in different processes,  and then have each one of those threads send the message to six threads (3 * 6 = our current 18 outbound threads). Many of the threads want the ADT HL7 message tweeked a little so only a few of the messages could be just a pass-through – most have a translate.  

      We don’t seem to be having any problems with this setup right now, but we would like to start planning and implementing a new config for future growth.

      Are we the only one sending ADT messages to so many applications? I am surprised I have not heard any other complaints or comments about this.

      Rich

      Genesys Regional Medical Center

      Grand Blanc, Michigan

    Viewing 4 reply threads
    • Author
      Replies
      • #57923
        Ryan Spires
        Participant

          This may be a bit overkill in your environment, but we have several inbound sms records, though we are now on the GRV3 (hl7 super), we have an inbound site that is used to send the data to muliple “site threads”

          in other words, we have 1 site that all the data comes into for our ADT and orders, and we send that data to multiple site threads. (localhost)

          sms_in —-> cerner_xfer

                    —-> idx_xfer

                    —-> misc_xfer

                    —-> misc2_xfer

          The cerner_xfer would then point to a unused port on localhost

          The cerner site would have a thread listening on that port.

          We have multiple inbound SMS feeds, so we replicate the above  6 or 7 times.

          Then we can break the data into categories that make since.   We currently have a cerner site, an IDX site and several MISC sites.

          It has been suggested that we migrate to a “facility” based scheme, though we have not been able to justify the effort in doing so at this time.

          You could do the same thing in the same site, or there are some that choose to “OVER” the message in a single thread, effectively using both the inbound and outbound side of a single thread.

          inbound —-> middle


          > outbound

          rather than

          inbound


          >local1send       local1recv—->outbound

          One thing I have discovered, is there are many different ways to do different things, not all bad, not all good.  You have to find what way makes the most sense in your environment, remember you have to maintain it 🙂

          Hope that helps, let me know if you need more detail.

          thanks,

          Ryan

        • #57924
          Kathy Zwilling
          Participant

            I am going to use the localhost option for splitting up our ADT site into a site that receives and routes the HL7 messages to 2 other sites that will do data translation and delivery.  

            Does anyone have recommendations for the pdl and acknowledgment scheme to use for the cross site processing?  

            Thank you,

            Kathy Zwilling

          • #57925
            Rich Durkee
            Participant

              I am sending ADT from one site to another. I am using the tcpip protocol on both sending and receiving threads. Also, on the sending threads, Inbound tab, check “Outbound Only”. On the Outbound tab, I have the “Await Replies” box checked and am using hcitpsmsgkill for the “TPS Inbound Reply”. On the receiving thread, Inbound Tab, I have “ackgen”  in the “TPS Inbound Data” box.

              Rich Durkee

            • #57926
              Kathy Zwilling
              Participant

                Rick,

                What does you ackgen tclproc look like, please?

                I am having trouble with engine panics on the sending side when I bring up the receiving side so I am trying to figure out why.

                Thank you!

                Kathy

              • #57927
                Anonymous
                Participant

                  We ran into this same issue some years back. I did do as you suggest and take the inboud flat record and convert it into an HL7 and sent it to 4 seperate process. This improved performance greatly. It worked well the problem came when we upgrade the source ADT system and the maintenance of that translations.

                  I now do not have the middle hl7 type message and go stright to the destination system from the flat record. In looking back the going to the generic HL7 middle solution really did not buy me that much but breaking out to more process did a great deal.

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