Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Biztalk 2006 XML to HL7 Problem
- This topic has 2 replies, 1 voice, and was last updated 8 years, 3 months ago by
community-content.
-
AuthorPosts
-
-
January 12, 2009 at 11:32 AM #21504
I have a Biztalk application (with HL7 accelerator 1.3) configured to transform an XML file into hl7 format and send along using the MLLP port but I run into the following error:
============================================
A message sent to adapter “MLLP” on send port “MLLPOutput” with URI “127.0.0.1:10000” is suspended.
Error details: There was a failure executing the send pipeline: “BTAHL72XPipelines.BTAHL72XSendPipeline, BTAHL72XPipelines, Version=1.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35” Source: “BTAHL7 2.X Assembler” Send Port: “MLLPOutput” URI: “127.0.0.1:10000” Reason: Serialization errors:
Error # 1
Segment Id: MSH
Sequence Number: 1
Field Number: 9
Error Number: 207
Error Description: Application internal error
Encoding System: HL7nnnn
Alternate Error Number: Z100
Alternate Error Description: The data for the parent entity cannot end with child tag <MSH.9_MessageType>
Alternate Encoding System: HL7-BTA
=======================================
I have a Windows Service monitoring a practice database system and outputting the XML for the appropriate event. Note: Not all HL7 fields are present because this is a “homegrown” database application and simply doesn’t account for many HL7 fields. The XML output looks like this (names changed to protect the innocent):
=========================
<?xml version=”1.0″ encoding=”utf-8″ standalone=”yes”?>
<HL7_MESSAGE_ADT_A08>
<MSH>
<MSH.1>
<Field_Separator>|</Field_Separator>
</MSH.1>
<MSH.2>
<Encoding_Characters>^~\&</Encoding_Characters>
</MSH.2>
<MSH.3>
<Sending_Application>XYZ Database</Sending_Application>
</MSH.3>
<MSH.4>
<Sending_Facility>ABC Physicians Group</Sending_Facility>
</MSH.4>
<MSH.6>
<Receiving_Facility>JKLMNOP</Receiving_Facility>
</MSH.6>
<MSH.7>
<DateTime_of_Message>20090112141346</DateTime_of_Message>
</MSH.7>
<MSH.9>
<MESSAGE_CODE>ADT</MESSAGE_CODE>
</MSH.9>
<MSH.9.1>
<TRIGGER_EVENT>A08</TRIGGER_EVENT>
</MSH.9.1>
<MSH.9.2>
<MESSAGE_STRUCTURE>ADT_A01</MESSAGE_STRUCTURE>
</MSH.9.2>
</MSH>
<PID>
<PID.1>
<Set_ID_-_PID>1</Set_ID_-_PID>
</PID.1>
<PID.2>
<Patient_ID>P12345</Patient_ID>
</PID.2>
<PID.5>
<PID.5.1>
<FIRST_NAME>BETTY</FIRST_NAME>
</PID.5.1>
<PID.5.2>
<LAST_NAME>TESTER</LAST_NAME>
</PID.5.2>
<PID.5.3>
<MIDDLE_NAME />
</PID.5.3>
<PID.5.4>
<SUFFIX_NAME />
</PID.5.4>
</PID.5>
<PID.7>
<DateTime_of_Birth>3/10/1968</DateTime_of_Birth>
</PID.7>
<PID.8>
<Sex>F</Sex>
</PID.8>
<PID.11>
<PID.11.1>
<STREET_ADDRESS1>123 Main Street</STREET_ADDRESS1>
</PID.11.1>
<PID.11.2>
<STREET_ADDRESS2>””</STREET_ADDRESS2>
</PID.11.2>
<PID.11.3>
<CITY>ALBANY</CITY>
</PID.11.3>
<PID.11.4>
<STATE>NY</STATE>
</PID.11.4>
<PID.11.5>
<ZIP_CODE>12345</ZIP_CODE>
</PID.11.5>
</PID.11>
<PID.13>
<Phone_Number_-_Home>(518)555-1212</Phone_Number_-_Home>
</PID.13>
<PID.18>
<Patient_Account_Number>P12345</Patient_Account_Number>
</PID.18>
<PID.19>
<SSN_Number_-_Patient />
</PID.19>
<PID.14>
<Phone_Number_-_Business>””</Phone_Number_-_Business>
</PID.14>
<PID.16>
<Marital_Status />
</PID.16>
<PID.29>
<Patient_Death_Date_and_Time>11/20/2008</Patient_Death_Date_and_Time>
</PID.29>
<PID.30>
<Patient_Death_Indicator>Y</Patient_Death_Indicator>
</PID.30>
</PID>
<PV1>
<PV1.1>
<Set_ID_-_PV1>1</Set_ID_-_PV1>
</PV1.1>
<PV1.2>
<Patient_Class>OUTPATIENT</Patient_Class>
</PV1.2>
<PV1.3>
<Assigned_Patient_Location>Associates in Cardiology</Assigned_Patient_Location>
</PV1.3>
<PV1.4>
<Admission_Type>ABCD</Admission_Type>
</PV1.4>
<PV1.7>
<Attending_Doctor>Dr.John Doe</Attending_Doctor>
</PV1.7>
<PV1.8>
<PV1.8.1>
<FIRST_NAME />
</PV1.8.1>
<PV1.8.2>
<LAST_NAME />
</PV1.8.2>
</PV1.8>
<PV1.9>
<Consulting_Doctor />
</PV1.9>
<PV1.17>
<Admitting_Doctor />
</PV1.17>
<PV1.19>
<Visit_Number>34567</Visit_Number>
</PV1.19>
<PV1.44>
<PV1.44.1>
<ADMIT_DATE>10/30/2008</ADMIT_DATE>
</PV1.44.1>
<PV1.44.2>
<ADMIT_TIME />
</PV1.44.2>
</PV1.44>
<PV1.45>
<Discharge_DateTime />
</PV1.45>
</PV1>
</HL7_MESSAGE_ADT_A08>==============================
So this XML gets mapped in an orchestration to an HL7 2.3.1 multipart message containing BTAHL7Schemas.MSH_24_GLO_DEF and BTAHL7Schemas.ADT_A08_231_GLO_DEF parts. Fairly simple and straightforward. Can anyone give me a push in the right direction? Thank You!
-
January 21, 2013 at 5:08 PM #25972
I'm having a similar issue except with the DG1.3 segment.
-
May 10, 2013 at 6:32 AM #26053
HI,
Go to BTAHL7 Configuration Explorer, go to your party, to to validation tab, then uncheck "Validate body segments" and check "Allow Trailing delimiters"
Thank you
Rahmatullah
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.