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

how difficult can this be????

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

  • how difficult can this be????

    I'm having trouble with a simple File Writer destination (v1.7.1). When I create an HL7 message and send it a text file, I see the return character for the line feed. HL7Browser seems to have problems with it. It doesn't see the line characters which it sees the entire message as a Message Header. What do I have to do to generate a simple HL7 text message from my Destination channel? Below is what I have on my destination File Writer template:
    MSH|^~\&|NextGen|.|TAA||||ORM^O01|1122040823|P|2.1 |||
    PID|1|${Med_Rec_Nbr}|||${Patient_Name}||${DOB}|${S ex}|||
    ORC|NW|${Order_Number}||||||||||34534^Smith^John
    OBR|1|000002008||Spirometry|||||||||

    Do I have to do anything with a transformer or do I have to use some sort of encoding for the HL7Browser to work with the above template? Any help would be appreciated.

    - Marty

  • #2
    Re:how difficult can this be????

    The solution to this problem was this. I scrapped the custom template and dragged and dropped ${message.encodedData} to the destination. I then in turned used transformers on the outgoing channel to map variables to the PID and OCR segments. This resolved my problems. I think all is working....finally...

    - Marty

    Comment

    Working...
    X