web stats
Need help - two transactions in one message - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Reply
 
Thread Tools Display Modes
  #1  
Old 05-01-2019, 08:16 AM
MARSHA MARSHA is offline
What's HL7?
 
Join Date: Apr 2019
Posts: 1
MARSHA is on a distinguished road
Default Need help - two transactions in one message

Hi - forgive me I am new. And I have read through the threads here is my issue - I am DESPERATE

When I am receiving a transaction from MIRTH onto another engine, the DATA Layer Message and the Net Layer are receiving two transactions concatenated into one message. The framing characters are coming in as data on the both messages Below I have highlighted both MSH's one in Orange and one in RED.

If you need more information please let me know. I am lost as to how to handle these messages. I have worked with other MIRTH vendors and have never seen this problem.

So I see
VT = Vertical Tab
VT
MSH
PID
PV1
ORM
OBX
OBX etc
VT - vertical tab
VT -
MSH
PID
PV1
ORM
OBX
OBX etc

The receiving engine reads this as one record and the result makes no sense.

Why would MIRTH send two transactions into one data layer


..MSH|^~\&|TMS_W 00010 41 49 7C 54 49 4D 45 4C 45 53 53 7C 57 4D 43 7C AI|TIMELESS|WMC|
00020 57 4D 43 7C 32 30 31 39 30 34 33 30 31 30 33 37 WMC|201904301037
00030 30 38 7C 7C 4F 52 55 5E 52 30 31 7C 33 39 38 34 08||ORU^R01|3984
00040 31 35 30 30 30 30 30 30 32 37 39 36 30 7C 54 7C 1500000027960|T|
00050 32 2E 33 0D 50 49 44 7C 7C 30 30 30 30 30 30 30 2.3.PID||0000000
00060 30 30 37 31 7C 33 39 38 34 31 35 7C 7C 42 52 4F 0071|398415||BRO
00070 57 4E 5E 42 41 42 59 33 7C 7C 32 30 31 38 31 32 WN^BABY3||201812
00080 30 33 7C 46 7C 7C 7C 7C 7C 7C 7C 7C 7C 7C 36 31 03|F||||||||||61
00090 32 37 32 31 32 36 7C 30 0D 50 56 31 7C 7C 7C 4E 272126|0.PV1|||N
000A0 49 43 55 5E 6E 32 34 32 5E 6E 32 34 32 32 43 0D ICU^n242^n2422C.
000B0 4F 42 52 7C 7C 7C 33 39 38 34 31 35 30 30 30 30 OBR|||3984150000
000C0 30 30 32 37 39 36 30 7C 57 41 49 5F 46 45 45 44 0027960|WAI_FEED
000D0 5F 42 41 42 59 7C 7C 7C 32 30 31 39 30 34 33 30 _BABY|||20190430
000E0 31 30 33 37 30 37 7C 7C 7C 6D 61 63 6C 65 6F 64 103707|||macleod
000F0 72 5E 54 69 6D 65 6C 65 73 73 2C 41 64 6D 69 6E r^Timeless,Admin
00100 7C 7C 7C 7C 7C 7C 7C 7C 7C 7C 7C 7C 7C 7C 7C 46 |||||||||||||||F
00110 0D 4F 42 58 7C 31 7C 54 58 7C 42 4D 42 4F 54 5E .OBX|1|TX|BMBOT^
00120 42 6F 74 74 6C 65 20 49 44 7C 7C 44 42 4D 30 30 Bottle ID||DBM00
00130 30 33 5A 49 7C 7C 7C 7C 7C 7C 7C 7C 7C 32 30 31 03ZI|||||||||201
00140 39 30 34 33 30 31 30 33 37 30 37 7C 7C 0D 4F 42 90430103707||.OB
00150 58 7C 32 7C 54 58 7C 42 4D 42 41 53 45 5E 42 61 X|2|TX|BMBASE^Ba
00160 73 65 20 6F 66 20 66 65 65 64 7C 7C 44 54 59 34 se of feed||DTY4
00170 32 37 31 32 34 36 7C 7C 7C 7C 7C 7C 7C 7C 7C 32 271246|||||||||2
00180 30 31 39 30 34 33 30 31 30 33 37 30 37 7C 7C 0D 0190430103707||.
00190 4F 42 58 7C 33 7C 54 58 7C 42 4D 42 41 53 45 4C OBX|3|TX|BMBASEL
001A0 4F 54 4E 4F 5E 4C 6F 74 20 4E 75 6D 62 65 72 7C OTNO^Lot Number|
001B0 7C 7C 7C 7C 7C 7C 7C 7C 7C 7C 32 30 31 39 30 34 ||||||||||201904
001C0 33 30 31 30 33 37 30 37 7C 7C 0D 4F 42 58 7C 34 30103707||.OBX|4
001D0 7C 54 58 7C 42 4D 49 4E 56 56 4F 4C 5E 49 6E 76 |TX|BMINVVOL^Inv
001E0 65 6E 74 6F 72 79 20 56 6F 6C 75 6D 65 20 69 6E entory Volume in
001F0 20 6D 4C 7C 7C 30 7C 7C 7C 7C 7C 7C 7C 7C 7C 32 mL||0|||||||||2
00200 30 31 39 30 34 33 30 31 30 33 37 30 37 7C 7C 0D 0190430103707||.
00210 4F 42 58 7C 35 7C 54 58 7C 42 4D 42 4F 54 51 4E OBX|5|TX|BMBOTQN
00220 54 5E 49 6E 76 65 6E 74 6F 72 79 20 42 6F 74 74 T^Inventory Bott
00230 6C 65 20 43 6F 75 6E 74 7C 7C 30 7C 7C 7C 7C 7C le Count||0|||||
00240 7C 7C 7C 7C 32 30 31 39 30 34 33 30 31 30 33 37 ||||201904301037
00250 30 37 7C 7C 0D 4F 42 58 7C 36 7C 54 58 7C 42 4D 07||.OBX|6|TX|BM
00260 43 41 4C 5E 42 4D 20 43 61 6C 6F 72 69 65 73 7C CAL^BM Calories|
00270 7C 32 30 7C 7C 7C 7C 7C 7C 7C 7C 7C 32 30 31 39 |20|||||||||2019
00280 30 34 33 30 31 30 33 37 30 37 7C 7C 0D 4F 42 58 0430103707||.OBX
00290 7C 37 7C 54 58 7C 42 4D 56 46 45 45 44 56 4F 4C |7|TX|BMVFEEDVOL
002A0 5E 56 6F 6C 75 6D 65 20 46 65 64 7C 7C 31 30 30 ^Volume Fed||100
002B0 7C 7C 7C 7C 7C 7C 7C 7C 7C 32 30 31 39 30 34 33 |||||||||2019043
002C0 30 31 30 33 37 30 37 7C 7C 0D 4F 42 58 7C 38 7C 0103707||.OBX|8|
002D0 54 58 7C 42 4D 55 53 45 52 5E 55 73 65 72 20 56 TX|BMUSER^User V
002E0 65 72 69 66 79 69 6E 67 7C 7C 45 6C 65 63 74 72 erifying||Electr
002F0 6F 6E 69 63 61 6C 6C 79 20 73 69 67 6E 65 64 20 onically signed
00300 62 79 20 41 64 6D 69 6E 20 54 69 6D 65 6C 65 73 by Admin Timeles
00310 73 7C 7C 7C 7C 7C 7C 7C 7C 7C 32 30 31 39 30 34 s|||||||||201904
00320 33 30 31 30 33 37 30 37 7C 7C 0D 4F 42 58 7C 39 30103707||.OBX|9
00330 7C 54 58 7C 42 4D 46 45 45 44 49 4E 46 4F 5E 46 |TX|BMFEEDINFO^F
00340 65 65 64 20 44 65 74 61 69 6C 73 7C 7C 42 6F 74 eed Details||Bot
00350 74 6C 65 20 49 44 3A 20 44 42 4D 30 30 30 33 5A tle ID: DBM0003Z
00360 49 7E 7E 46 65 65 64 20 54 79 70 65 3A 20 44 54 I~~Feed Type: DT
00370 59 34 32 37 31 32 34 36 7E 7E 46 65 65 64 20 63 Y4271246~~Feed c
00380 61 6C 2F 6F 7A 3A 20 32 30 7E 7E 44 6F 6E 6F 72 al/oz: 20~~Donor
00390 20 6D 69 6C 6B 20 6C 6F 74 3A 20 54 68 65 20 4E milk lot: The N
003A0 65 77 20 59 6F 72 6B 20 4D 69 6C 6B 20 42 61 6E ew York Milk Ban
003B0 6B 28 31 31 32 31 32 33 31 32 33 29 7E 7E 45 78 k(112123123)~~Ex
003C0 70 69 72 79 3A 20 32 30 32 30 30 35 30 32 30 30 piry: 2020050200
003D0 30 30 30 30 7E 7E 44 61 74 65 20 54 69 6D 65 20 0000~~Date Time
003E0 53 63 61 6E 6E 65 64 3A 20 32 30 31 39 30 34 33 Scanned: 2019043
003F0 30 31 30 33 37 30 38 7E 7E 7C 7C 7C 7C 7C 7C 7C 0103708~~|||||||
00400 7C 7C 32 30 31 39 30 34 33 30 31 30 33 37 30 37 ||20190430103707
00410 7C 7C 0D 4F 42 58 7C 31 30 7C 54 58 7C 42 4D 42 ||.OBX|10|TX|BMB
00420 4F 54 54 4C 45 45 58 50 5E 42 6F 74 74 6C 65 20 OTTLEEXP^Bottle
00430 45 78 70 69 72 79 7C 7C 30 35 2F 30 32 2F 32 30 Expiry||05/02/20
00440 32 30 20 30 30 3A 30 30 7C 7C 7C 7C 7C 7C 7C 7C 20 00:00||||||||
00450 7C 32 30 31 39 30 34 33 30 31 30 33 37 30 37 7C |20190430103707|
00460 7C 0D 4F 42 58 7C 31 31 7C 54 58 7C 42 4D 4E 4F |.OBX|11|TX|BMNO
00470 54 45 45 4E 54 5E 4E 6F 74 65 20 45 6E 74 65 72 TEENT^Note Enter
00480 65 64 7C 7C 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D ed||------------
00490 2D 2D 2D 2D 2D 2D 2D 2D 20 30 34 2F 33 30 2F 32 -------- 04/30/2
004A0 30 31 39 20 31 30 3A 33 37 2D 2D 2D 2D 2D 2D 2D 019 10:37-------
004B0 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 7C 7C 7C -------------|||
004C0 7C 7C 7C 7C 7C 7C 32 30 31 39 30 34 33 30 31 30 ||||||2019043010
004D0 33 37 30 37 7C 7C 0D 4F 42 58 7C 31 32 7C 54 58 3707||.OBX|12|TX
004E0 7C 42 4D 4E 4F 54 45 45 4E 44 5E 45 6E 64 20 6F |BMNOTEEND^End o
004F0 66 20 4E 6F 74 65 7C 7C 2D 2D 2D 2D 2D 2D 2D 2D f Note||--------
00500 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 20 ---------------
00510 45 6E 64 20 6F 66 20 4E 6F 74 65 20 2D 2D 2D 2D End of Note ----
00520 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D ----------------
00530 2D 2D 2D 7C 7C 7C 7C 7C 7C 7C 7C 7C 32 30 31 39 ---|||||||||2019
00540 30 34 33 30 31 30 33 37 30 37 7C 7C 0D 1C 0D 1C 0430103707||....
00550 0D 0B 0B 4D 53 48 7C 5E 7E 5C 26 7C 54 4D 53 5F ...MSH|^~\&|TMS_
00560 57 41 49 7C 54 49 4D 45 4C 45 53 53 7C 57 4D 43 WAI|TIMELESS|WMC
00570 7C 57 4D 43 7C 32 30 31 39 30 34 33 30 31 30 33 |WMC|20190430103
00580 37 30 38 7C 7C 4F 52 55 5E 52 30 31 7C 33 39 38 708||ORU^R01|398
00590 34 31 35 30 30 30 30 30 30 32 37 39 36 32 7C 54 41500000027962|T
Reply With Quote
  #2  
Old 05-01-2019, 12:29 PM
cory_cole cory_cole is offline
Mirth Guru
 
Join Date: Mar 2012
Posts: 1,277
cory_cole is on a distinguished road
Default

Mirth splits message on the new message character. The problem here is that you have a bunch of other other data in the middle of the message which is destroying the new message character.
Reply With Quote
  #3  
Old 05-01-2019, 06:50 PM
agermano agermano is offline
Mirth Guru
 
Join Date: Apr 2017
Location: Indiana, USA
Posts: 955
agermano is on a distinguished road
Default

Check the transmission settings on the Mirth end.

Before your second message you see the 1C0D bytes that indicate the end of the first message. That is followed by two 0B bytes, when there should only be one. The only way I can figure that mirth would be sending the extra byte is if the default configuration was changed to use 0B0B as the start sequence.

I still wouldn't expect the receiving engine to see the two messages as one, though, since it did get a valid end of message. I can see the second message not being read correctly since it starts with a <VT> before MSH.

Is the receiving engine set up to use MLLP?
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 01:44 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
Mirth Corporation