Announcement

Collapse

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

Database reader - XML to HL7

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

  • Database reader - XML to HL7

    I have a database table that stores HL7 format transaction. I would like to query that database and send those transactions to a file writer connection.

    I can read the database fine, however when I try to write the result to a file, the encoded message contains "message" before the MSH segment in each record.
    IE: messageMSH

    Is there a reason that message appears at the beginning of each record? How can I fix this?
    Reid Hospital and Healthcare

  • #2
    I am currently have this same situation. I have tried a few mapper steps without success.

    What was your resolution?

    Thanks

    Comment


    • #3
      Which variable are you using to output the encoded message in the File Writer?
      Gerald Bortis | Chief Information Officer | Mirth Corporation

      Comment


      • #4
        Gerald - Thanks for the response. Here is my current workflow (I have removed all mappings and transformations for step three - DB Reader to File Writer).

        1. HL7 messages are written to DB via destination DB Writer.
        2. SQL logic to update and correlate order numbers, etc.
        3. Based upon criteria, HL7 messages are selected from DB and sent to a file writer. This is where I see the extra data in the message. The files that are written (encoded data template) have the 'tablename_columnname' prefixed to the message:

        resultaccession_export_filler_documentMSH|^~\&|OAD D|116|DADD|.......

        Thanks

        Comment

        Working...
        X