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

Need help with header......

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

  • Need help with header......

    What I'm doing is basically using an ADT feed that's already in place, pointing it to mirth, then sending it on to the machine it was originally poining to. I'm planning on setting up another destination to do some other things. I just wanted to get the data through the server. I'm sending raw data via llp. The only difference between the source data and the data sent out is the "^" vs. the ";" right after MSH:
    and it doesn't seem to work. I've tried running a preprocessing script to replace the "^" with the ";" but that doesn's work either. Anyone have any idea what this character does and why I can't make the data send the same way it was recieved?

    Thanks
    Drew


    MSH:;~\&:HBO:A:SUPPLYSCAN:A:200801161253::ADT;A08; 41:1202306:P:2.2:1202306::AL::




    MSH:^~\&:HBO:A:SUPPLYSCAN:A:200801161253::ADT;A08; 41:1202306:P:2.2:1202306::AL::

  • #2
    Re:Need help with header......

    Hi Drew - The first five characters after the MSH in an HL7 message tells you what characters will be used as delimiters to separate the parts of the message. An HL7 message consists of segments, each beginning with three characters (e.g., MSH, EVN, PID, PV1, etc.) and every segment is delimited (i.e., separated from the others) with a carriage return characater (hex 0D). The first character after MSH is usually a "|" (typically called "pipe") and this character will be used to delimit the segments into fields. Looks like your system uses a colon instead of a pipe as the field delimiter. The second character after the MSH is usually a "^" (or "carat") and this is the character that will delimit the parts of a field into components. Looks like your system sends a semicolon as the component delimiter. If you replace the first colon with a carat, then you will have to replace every colon in the message with a carat.

    MSH:;~&:HBO:AUPPLYSCAN:A:200801161253::ADT;A08;41: 1202306:2.2:1202306::AL::

    MSH:^~&:HBO:AUPPLYSCAN:A:200801161253::ADT^A08^41: 1202306:2.2:1202306::AL::

    Most folks who look at HL7 messages all day would expect to see something more like
    MSH|^~\&|HBO|AUPPLYSCANA|200801161253||ADT^A08^41| 1202306|2.2|1202306||AL||

    Hope that helps...don't hesitate to ask more questions if needed.

    Comment

    Working...
    X