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

Truly removing Z segments

  • Filter
  • Time
  • Show
Clear All
new posts

  • Truly removing Z segments

    We are trying to process data that has a ZP1 segment after the PID and before the NK1. delete msg['zp1'] does not work, because mirth has already named the msg as 'ADT-A08.INSURANCE'. And we can't delete ADT-A08.INSURANCE because it includes EVERYTHING that comes after it. (For example, the PV1 segment which comes after the NK1 segment has been made as a child of the ADT-A08.INSURANCE.

    Alternately, is there a way of doing byte-by-byte manipulation of the raw data and stripping out Z segments?

  • #2
    Re:Truly removing Z segments

    Can you post a sample message?

    What you're doing with "delete msg[zp1]" looks right and *should* work.

    Worst case is you can take the whole message as a string in the preprocessor and use javascript to manipulate it as a string.
    Jon Bartels

    Zen is hiring!!!!
    Talented healthcare IT professionals wanted. Engineers to sales to management.
    Good benefits, great working environment, genuinely interesting work.