Announcement

Collapse
No announcement yet.

End-to-end working sample (LLP using TCP to Database)

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

  • End-to-end working sample (LLP using TCP to Database)

    I downloaded Mirth v1.1 and was able to run the Mirth Admininstrator.

    I'm trying to setup Mirth v1.1 to have LLP Listener, receive HL7 messages via TCP, and store the fields (data) in Microsoft SQL Server 2000 database.

    For e.g., Setup LLP listener, receive ADT:A04, process message to store patient's LastName and FirstName in the database Patient table.

    Is there an end-to-end working sample that I could refer to help with this requirement.

    Thanks in advance!

    -NS


  • #2
    Re: End-to-end working sample (LLP using TCP to Database)

    We have a few samples here that we are preparing to upload the file repository next week. I will be sure to include one that meets your requirements.

    Also, be sure to check out the tutorial videos soon. We will post an example that does exactly what you would like.

    Thanks,
    -Chris
    Chris Lang

    Comment


    • #3
      Re: End-to-end working sample (LLP using TCP to Database)

      At the risk of sounding impatient instead of just anxious to really play around with Mirth, can somebody tell me how I would build a segment value into a variable for use in the destination (db insert)?

      I know the videos are coming soon and so forth, but if its easy, a little help in this category could go a long way for me.

      Comment


      • #4
        Re: End-to-end working sample (LLP using TCP to Database)

        Sween -

        The easiest way would be:

        1. Define a new transformer
        2. Add a new transformer step
        3. Inside of your mapper window click on the "HL7 Message Template" tab
        4. Paste a sample HL7 message (pref. one that is similar to the expected incoming messages. Check our file repository for a generic sample)
        5. Click on the HL7 tree and expand out to the data segment you want
        6. Click and drag any data segment to the mapping text area. You must click on an actual value (i.e. the patient's name). This is only a template value that tells Mirth where to look in the message for the data.
        7. Name your variable something meaninful ('name&#039
        8. Go back to the channel screen and your new variable should appear in the variable list.
        9. Drag this variable into your DB insert area in the place you would like it to go in your statement.

        Hope this helps!
        -Chris
        Chris Lang

        Comment


        • #5
          Re: End-to-end working sample (LLP using TCP to Database)

          I've uploaded a sample that addresses both of your questions:

          LLP Listener to Multiple Endpoints Sample Channel

          Import this into your Mirth instance and update the database connection settings, as well as the HL7 template. Please note that this is based on HL7 v2.3.1, so if you're incoming messages are different you might need to adjust the mappings slightly. (Simply paste in the example message from your desired type and re-drag and drop the segments)
          Chris Lang

          Comment


          • #6
            Re: End-to-end working sample (LLP using TCP to Database)

            chris,

            Thank you! I pretty much thought it was that intuitive, but I suspect I may have been blowing it in my sql insert. Anyway, im enlightened to say the least. This has opened my eyes, and many doors... thanks again for taking time out...


            mirth is good stuff.

            Comment


            • #7
              Chris,

              I am facing issue while importing multi message file. It is not allowing me to insert multiple messages into database from single source file.

              Please let me what is wrong with my implementation?


              Regards,
              Tushar Parmar.

              Comment

              Working...
              X
              😀
              🥰
              🤢
              😎
              😡
              👍
              👎