Announcement

Collapse
No announcement yet.

Field contains segment name

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

  • Field contains segment name

    I searched in the forum and I didn't find a previous post about my question.
    I tried to process HL7 message (see below) with mirth connect (3.5.0) and a name of a patient like "VICENTE" contains the string "NTE", but I noticed that mirth consider NTE as new segment.

    original HL7:
    PID|1||test||test^VICENTE||19000101|

    Mirth format
    PID|1||test||test^VICE
    NTE||19000101|

    How do I resolve this issue? Thanks.

  • #2
    That can't be true...
    Otherwise, there is a high chance of names ending in NTE, and many Mirth interfaces across the world would fail to parse it.

    You sure you are not missing something? Any transformer script etc. Check carefully.
    HL7v2.7 Certified Control Specialist!

    Comment


    • #3
      I checked carefully, here is attached my config in "Datat type". Note please that I am using HTTP listener to receive HL7 encoded base64 messages then I decode the message then HL7v2. format of the outbound in the first destination format the HL7 with this issue.
      Attached Files

      Comment


      • #4
        Sorry, It was an error from my end, there was a function in the code for some reason that i don't see it now, add some \r before each sgment. my bad

        Comment


        • #5
          The culprit is still out in the open. You might want to fix that function, because from the looks of it, it is not working as expected, creating unnecessary problems for you.
          HL7v2.7 Certified Control Specialist!

          Comment

          Working...
          X