Error in HL7 send pipeline.

Jens Franck

unread,

Apr 18, 2008, 8:26:01 AM4/18/08

to

Hi,

we are trying to create a HL7 message. The orchestration builds the complete
ORU^01 (v2.4) message with his 3 parts, but we have an error once it is
processed by the HL7 send pipeline. We created the parts of the multipart
message in the right order.

The message assingment part looks like:
HeaderInfo = new System.Xml.XmlDocument();
HeaderInfo.LoadXml("<ns0:MSH_24_GLO_DEF
xmlns:ns0=\"http://microsoft.com/HealthCare/HL7/2X\"><MSH><MSH.2_EncodingCharacters>^~\\&</MSH.2_EncodingCharacters><MSH.3_SendingApplication><HD.0_NamespaceId>SrcApp</HD.0_NamespaceId><HD.1_UniversalId>SrcAppUid</HD.1_UniversalId></MSH.3_SendingApplication><MSH.4_SendingFacility><HD.0_NamespaceId>srcFac</HD.0_NamespaceId><HD.1_UniversalId>srcFacUid</HD.1_UniversalId></MSH.4_SendingFacility><MSH.5_ReceivingApplication><HD.0_NamespaceId>dstApp</HD.0_NamespaceId><HD.1_UniversalId>dstAppUid</HD.1_UniversalId></MSH.5_ReceivingApplication><MSH.6_ReceivingFacility><HD.0_NamespaceId>dstFac</HD.0_NamespaceId><HD.1_UniversalId>dstFacUid</HD.1_UniversalId></MSH.6_ReceivingFacility><MSH.7_DateTimeOfMessage><TS.1>200307092343</TS.1></MSH.7_DateTimeOfMessage><MSH.8_Security>sec</MSH.8_Security><MSH.9_MessageType><CM_MSG.0_MessageType>ORU</CM_MSG.0_MessageType><CM_MSG.1_TriggerEvent>R01</CM_MSG.1_TriggerEvent></MSH.9_MessageType><MSH.10_MessageControlId>msgid2134</MSH.10_MessageControlId><MSH.11_ProcessingId><PT.0_ProcessingId>P</PT.0_ProcessingId></MSH.11_ProcessingId><MSH.12_VersionId><VID_0_VersionId>2.4</VID_0_VersionId></MSH.12_VersionId></MSH></ns0:MSH_24_GLO_DEF>");

FinalORU.MSHSegment = HeaderInfo;
FinalORU.BodySegments = ORUBODY;
FinalORU.ZSegments = "";

FinalORU(BTAHL7Schemas.MSH1) = 124;
FinalORU(BTAHL7Schemas.MSH2) = "^~\\&";
FinalORU(BTAHL7Schemas.ParseError) = false;
FinalORU(BTAHL7Schemas.ZPartPresent) = false;
FinalORU(BTAHL7Schemas.SegmentDelimiter2Char) = true;

//FinalORU(BTAHL7Schemas.Encoding)=65001;

Can anyone give us an idea where we can further look to identifiy the
problem?
We are using BTS 2006 en HL7 accelerator 1.3.

Type gebeurtenis: Fout
Bron van gebeurtenis: BizTalk Accelerator for HL7
Categorie van gebeurtenis: Geen
Gebeurtenis-ID: 4133
Datum: 18/04/2008
Tijd: 11:41:05
Gebruiker: n.v.t.
Computer: IHCPOR32
Beschrijving:
Error happened in header during serialization
Error # 1
Segment Id: MSH
Sequence Number: 1
Field Number: 12
Error Number: 207
Error Description: Application internal error
Encoding System: HL7nnnn
Alternate Error Number: Z100
Alternate Error Description: From current serializer state, tag
<VID_0_VersionId> cannot be valid
Alternate Encoding System: HL7-BTA

Error # 2
Segment Id: MSH
Sequence Number: 1
Field Number: 12
Error Number: 203
Error Description: Unsupported version id
Encoding System: HL7nnnn

Error # 3
Segment Id: MSH
Sequence Number: 1
Field Number: 12
Error Number: 207
Error Description: Application internal error
Encoding System: HL7nnnn
Alternate Error Number: Z100
Alternate Error Description: A text node with value '2.4' was found inside a
complex element. It can only occur within a simple element
Alternate Encoding System: HL7-BTA

Error # 4
Segment Id: MSH
Sequence Number: 1
Error Number: 207
Error Description: Application internal error
Encoding System: HL7nnnn
Alternate Error Number: Z100
Alternate Error Description: The element 'MSH.12_VersionId' has an invalid
structure
Alternate Encoding System: HL7-BTA

Error # 5

Alternate Error Number: 301
Alternate Error Description: Unexpected end of message body found
Alternate Encoding System: HL7-BTA

Error # 6
Segment Id:
Sequence Number: 1
Error Number: 100
Error Description: Segment sequence error (Empty value not allowed for
segment as it has at least one required field)
Encoding System: HL7nnnn

Thanks in advance!
Jens

Eric Stott

unread,

Apr 19, 2008, 7:28:57 PM4/19/08

to

<VID_0_VersionId> is wrong
It should look like this:
...<MSH.12_VersionId><VID.0_VersionId>2.4</VID.0_VersionId></MSH.12_VersionId>...

Eric

http://hl7-info.com

http://blog.hl7-info.com

"Jens Franck" <JensF...@discussions.microsoft.com> wrote in message
news:E7F172C6-CEBB-48A8...@microsoft.com...

Jens Franck

unread,

Apr 21, 2008, 4:50:00 AM4/21/08

to

Thank you Eric!
That was indeed the problem!

"Eric Stott" wrote:

> <VID_0_VersionId> is wrong
> It should look like this:

> ....<MSH.12_VersionId><VID.0_VersionId>2.4</VID.0_VersionId></MSH.12_VersionId>...

Eric Stott

unread,

Apr 21, 2008, 1:30:45 PM4/21/08

to

Glad that it worked!

Eric
http://blog.hl7-info.com
http://hl7-info.com

"Jens Franck" <JensF...@discussions.microsoft.com> wrote in message

news:385AFFBA-5751-482F...@microsoft.com...

Ip@discussions.microsoft.com Ed Ip

unread,

Jul 1, 2008, 9:10:00 PM7/1/08

to

Hi Eric,

I realize this post is a few months old, but hopefully you can help me as
well. I have almost exact same errors as Jens, however, my MSH XML already
read
<MSH.12_VersionId><VID.0_VersionId>2.2</VID.0_VersionId></MSH.12_VersionId>

What am I doing wrong? Any help you can provide will be greatly appreciated!

Thanks.

Ed

HeaderInfo = new System.Xml.XmlDocument();
HeaderInfo.LoadXml("<ns0:MSH_24_GLO_DEF

xmlns:ns0=\"http://microsoft.com/HealthCare/HL7/2X\"><MSH><MSH.2_EncodingCharacters>^~\\&</MSH.2_EncodingCharacters><MSH.3_SendingApplication><HD.0_NamespaceId></HD.0_NamespaceId><HD.1_UniversalId></HD.1_UniversalId></MSH.3_SendingApplication><MSH.4_SendingFacility><HD.0_NamespaceId></HD.0_NamespaceId><HD.1_UniversalId></HD.1_UniversalId></MSH.4_SendingFacility><MSH.5_ReceivingApplication><HD.0_NamespaceId></HD.0_NamespaceId><HD.1_UniversalId></HD.1_UniversalId></MSH.5_ReceivingApplication><MSH.6_ReceivingFacility><HD.0_NamespaceId></HD.0_NamespaceId><HD.1_UniversalId></HD.1_UniversalId></MSH.6_ReceivingFacility><MSH.7_DateTimeOfMessage><TS.1>200307092343</TS.1></MSH.7_DateTimeOfMessage><MSH.8_Security></MSH.8_Security><MSH.9_MessageType><CM_MSG.0_MessageType>ADT</CM_MSG.0_MessageType><CM_MSG.1_TriggerEvent>A08</CM_MSG.1_TriggerEvent></MSH.9_MessageType><MSH.10_MessageControlId></MSH.10_MessageControlId><MSH.11_ProcessingId><PT.0_ProcessingId>P</PT.0_ProcessingId></MSH.11_ProcessingId><MSH.12_VersionId><VID.0_VersionId>2.2</VID.0_VersionId></MSH.12_VersionId></MSH></ns0:MSH_24_GLO_DEF>");

OutboundMsg.MSHSegment = HeaderInfo;
OutboundMsg.BodySegments = Appointment_Msg;
OutboundMsg.ZSegments = "";

OutboundMsg(BTAHL7Schemas.MessageEncoding) = 65001;
OutboundMsg(BTAHL7Schemas.MSH1) = 124;
OutboundMsg(BTAHL7Schemas.MSH2) = "^~\\&";
OutboundMsg(BTAHL7Schemas.ParseError) = false;
OutboundMsg(BTAHL7Schemas.ZPartPresent) = false;
OutboundMsg(BTAHL7Schemas.SegmentDelimiter2Char) = true;

--
A message sent to adapter "FILE" on send port "WEPI_HL7_Output" with URI
"C:\Documents and Settings\BizTalk\My Documents\BizTalk\OUT\%MessageID%.hl7"
is suspended.
Error details: There was a failure executing the send pipeline:
"PMA.DataStaging.BizTalk.Common.Pipeline.BTAHL72XSendPipeline,
PMA.DataStaging.BizTalk.Common, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=98aa237effaeb9c1" Source: "BTAHL7 2.X Assembler" Send Port:
"WEPI_HL7_Output" URI: "C:\Documents and Settings\BizTalk\My
Documents\BizTalk\OUT\%MessageID%.hl7" Reason: Serialization errors:

Error # 1
Segment Id: MSH
Sequence Number: 1
Field Number: 12
Error Number: 207
Error Description: Application internal error
Encoding System: HL7nnnn
Alternate Error Number: Z100
Alternate Error Description: From current serializer state, tag

<VID.0_VersionId> cannot be valid
Alternate Encoding System: HL7-BTA

Error # 2
Segment Id: MSH
Sequence Number: 1
Field Number: 12
Error Number: 203
Error Description: Unsupported version id
Encoding System: HL7nnnn

Error # 3
Segment Id: MSH
Sequence Number: 1
Field Number: 12
Error Number: 207
Error Description: Application internal error
Encoding System: HL7nnnn
Alternate Error Number: Z100

Alternate Error Description: A text node with value '2.2' was found inside a

complex element. It can only occur within a simple element
Alternate Encoding System: HL7-BTA

Error # 4
Segment Id: MSH
Sequence Number: 1
Error Number: 207
Error Description: Application internal error
Encoding System: HL7nnnn
Alternate Error Number: Z100
Alternate Error Description: The element 'MSH.12_VersionId' has an invalid
structure
Alternate Encoding System: HL7-BTA

Error # 5

Alternate Error Number: 301
Alternate Error Description: Unexpected end of message body found
Alternate Encoding System: HL7-BTA

Error # 6
Segment Id:
Sequence Number: 1
Error Number: 100
Error Description: Segment sequence error (Empty value not allowed for
segment as it has at least one required field)
Encoding System: HL7nnnn

MessageId: {901079FF-BB57-4DEC-8B9D-0438DC9438C7}
InstanceID: {205BD092-CE91-462C-9F2A-BEAFD93070C8}

For more information, see Help and Support Center at

Daniel S

unread,

Jul 2, 2008, 12:03:18 PM7/2/08

to

Hello Ed,

What version of the HL7 Accelerator are you using? If you are using
version 2.0, then you want to use:

<VID_0_VersionId>

if you are using version 1.3, as Jens, then use:

<VID.0_VersionId>

Let us know if this helps.

Daniel Sepp

On Jul 1, 6:10 pm, Ed Ip <Ed I...@discussions.microsoft.com> wrote:
> Hi Eric,
>
> I realize this post is a few months old, but hopefully you can help me as
> well. I have almost exact same errors as Jens, however, my MSH XML already
> read
> <MSH.12_VersionId><VID.0_VersionId>2.2</VID.0_VersionId></MSH.12_VersionId>
>
> What am I doing wrong? Any help you can provide will be greatly appreciated!
>
> Thanks.
>
> Ed
>
> HeaderInfo = new System.Xml.XmlDocument();
> HeaderInfo.LoadXml("<ns0:MSH_24_GLO_DEF

> xmlns:ns0=\"http://microsoft.com/HealthCare/HL7/2X\"><MSH><MSH.2_EncodingCharacters>^~\\&</MSH.2_EncodingCharacters><MSH.3_SendingApplication><HD.0_NamespaceId></HD.0_NamespaceId><HD.1_UniversalId></HD.1_UniversalId></MSH.3_SendingApplication><MSH.4_SendingFacility><HD.0_NamespaceId></HD.0_NamespaceId><HD.1_UniversalId></HD.1_UniversalId></MSH.4_SendingFacility><MSH.5_ReceivingApplication><HD.0_NamespaceId></HD.0_NamespaceId><HD.1_UniversalId></HD.1_UniversalId></MSH.5_ReceivingApplication><MSH.6_ReceivingFacility><HD.0_NamespaceId></HD.0_NamespaceId><HD.1_UniversalId></HD.1_UniversalId></MSH.6_ReceivingFacility><MSH.7_DateTimeOfMessage><TS.1>200307092343</TS.1></MSH.7_DateTimeOfMessage><MSH.8_Security></MSH.8_Security><MSH.9_MessageType><CM_MSG.0_MessageType>ADT</CM_MSG.0_MessageType><CM_MSG.1_TriggerEvent>A08</CM_MSG.1_TriggerEvent></MSH.9_MessageType><MSH.10_MessageControlId></MSH.10_MessageControlId><MSH.11_ProcessingId><PT.0_ProcessingId>P</PT.0_ProcessingId></MSH.11_ProcessingId><MSH.12_VersionId><VID.0_VersionId>2.2</VID.0_VersionId></MSH.12_VersionId></MSH></ns0:MSH_24_GLO_DEF>");

Ed Ip

unread,

Jul 2, 2008, 2:28:06 PM7/2/08

to

Hi Daniel,

I'm using 2.0 and <VID_0_VersionId> worked. But now I have new errors that
doesn't give much clue. For now, I'm trying to save the HL7 out as a file.
Any ideas?

Thanks for your help!

Ed

A message sent to adapter "FILE" on send port "WEPI_HL7_Output" with URI
"C:\Documents and Settings\BizTalk\My Documents\BizTalk\OUT\%MessageID%.hl7"
is suspended.
Error details: There was a failure executing the send pipeline:
"PMA.DataStaging.BizTalk.Common.Pipeline.BTAHL72XSendPipeline,
PMA.DataStaging.BizTalk.Common, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=98aa237effaeb9c1" Source: "BTAHL7 2.X Assembler" Send Port:
"WEPI_HL7_Output" URI: "C:\Documents and Settings\BizTalk\My
Documents\BizTalk\OUT\%MessageID%.hl7" Reason: Serialization errors:
Error # 1

Alternate Error Number: 301

Alternate Error Description: Unexpected end of message body found
Alternate Encoding System: HL7-BTA

Error # 2

Segment Id:
Sequence Number: 1
Error Number: 100
Error Description: Segment sequence error (Empty value not allowed for
segment as it has at least one required field)
Encoding System: HL7nnnn

MessageId: {736A365F-D8CA-4067-AC5E-152A1DB2382E}
InstanceID: {5598AB0E-6DA9-46DF-8191-8DE3E9BC72D1}

Daniel S

unread,

Jul 2, 2008, 5:09:53 PM7/2/08

to

Hi Ed. Good to hear we got the first problem figured out!

So, the first error appears to be an extra carriage-return/line-feed
at the end of the document. There is a setting for Allow Trailing
Delimiters which you can set at ________________ or you can remove it
from your file. After this, I would test again...the second error I
wouldn't worry about yet.

Daniel Sepp
Neudesic, LLC

Daniel S

unread,

Jul 2, 2008, 5:16:55 PM7/2/08

to

Sorry...hit the Send button a little too fast...let's try again:

So, the first error appears to be an extra carriage-return/line-feed
at the end of the document. There is a setting for Allow Trailing

Delimiters which you can set at BTAHL7 Configuration Explorer
for the party you are using or you can remove it

Daniel Sepp
Neudesic, LLC

> > InstanceID: {5598AB0E-6DA9-46DF-8191-8DE3E9BC72D1}- Hide quoted text -
>
> - Show quoted text -

Ed Ip

unread,

Jul 2, 2008, 7:16:02 PM7/2/08

to

I have "Allow Trailing Delimiters" on, but still doesn't work. Just to
clarify, the BTAHL72XSendPipeline is getting the data from an orchestration
(i.e. message enrichment). With that said, is the carriage-return scenario
still true? If so, where/what am I stripping the CRLF from?

Thanks!

Daniel S

unread,

Jul 3, 2008, 11:31:54 AM7/3/08

to

Hi Ed,

Ok...so we've got the party configured to allow trailing delimiters
(and I'm assuming you have the party configured to match the MSH 5.1
in the message)...so the next thing is to check the pipeline setting
on your MLLP send port. If you click the "..." by the pipeline, you'll
get the properties...and the only property there is is
"TrailingDelimitersAllowed", which be default is False. Change this
and try again.

Let me know if it still isn't working.

Thanks,
Daniel Sepp
Neudesic, LLC

Ed Ip

unread,

Jul 3, 2008, 1:59:15 PM7/3/08

to

No luck...setting "TrailingDelimitersAllowed" to true didn't work either. :(
BTW, it's a File send port, does that matter?

Thanks.

Ed

Daniel S

unread,

Jul 3, 2008, 5:11:11 PM7/3/08

to

Nope....FILE send port doesn't matter. In fact it will make the
debugging a little easier. Have you tried just using the PassThrough
send port? If so, could you post the XML that came out?

Also, are you just setting up the message enrichment tutorial?

Thanks,
Daniel Sepp
Neudesic, LLC

> > > Thanks!- Hide quoted text -

Tom Canter - Neudesic

unread,

Jul 4, 2008, 3:46:46 PM7/4/08

to

Ed,
I would recommend that you look at the suspended message.
A number of things can go wrong with this error.
This is telling you that beyond the "last" Segment it recognized,
there is a required segment remaining.

"Segment sequence error (Empty value not allowed for segment as it has
at least one required field) "

So, you have either a missing required Segment (say a PID Segment) or
a Segment that is empty (NTE|) that has required fields in the
segment.
Another possibility is that the parser does not recognize any parts of
the message, and so all of the content is rejects.

Finally, open the suspended message and save off the multipart Body
component and then in your project, open the XML file you just saved.
In the properties of the message, select the Schema property and
browse to the Body schema it should be using and do a Validate on the
message.

ACTION: Inspect the suspended message and inspect it segment by
segment, make sure that the segments are reasonably formed (not empty)
and that all the required segments per the specification
NOTE: Do not assume your upstream supplier has the segments correct,
and make sure the message body you have built is correct, just because
the system doesn't error on it. Validation only occurs at the Send
Pipeline.

Tom

Ed Ip

unread,

Jul 7, 2008, 12:00:01 PM7/7/08

to

Tom,

Great suggestion. I have validated the body output against the schema and
there were indeed a few issues. However, I am still receive the same error
messages.

Below is the BodySegments with sensitive info replaced with X's. I've
indented the text for readability, the original output is all in one line.

Thanks.

Ed

<ns1:ADT_A08_22_GLO_DEF
xmlns:ns2="http://microsoft.com/HealthCare/HL7/2X/2.2/DataTypes"
xmlns:ns0="http://microsoft.com/HealthCare/HL7/2X/2.2/Segments"
xmlns:ns1="http://microsoft.com/HealthCare/HL7/2X"
xmlns:ns3="http://microsoft.com/HealthCare/HL7/2X/2.2/Tables">
<EVN_EventType>
<EVN_1_EventTypeCode>A08</EVN_1_EventTypeCode>
<EVN_2_DateTimeOfEvent>
<TS_0_TimeOfAnEvent>20080608003100000</TS_0_TimeOfAnEvent>
</EVN_2_DateTimeOfEvent>
</EVN_EventType>
<PID_PatientIdentification>
<PID_1_SetIdPatientId>1</PID_1_SetIdPatientId>
<PID_2_PatientIdExternalId>
<CK_PAT_ID_0_PatientId />
</PID_2_PatientIdExternalId>
<PID_3_PatientIdInternalId>
<CM_PAT_ID_0_PatientId />
</PID_3_PatientIdInternalId>
<PID_4_AlternatePatientId />
<PID_5_PatientName>
<PN_0_FamiliyName>XXXXX</PN_0_FamiliyName>
<PN_1_GivenName>XXXXX</PN_1_GivenName>
<PN_2_MiddleInitialOrName />
</PID_5_PatientName>
<PID_6_MotherSMaidenName />
<PID_7_DateOfBirth>
<TS_0_TimeOfAnEvent>20041114</TS_0_TimeOfAnEvent>
</PID_7_DateOfBirth>
<PID_8_Sex>M</PID_8_Sex>
<PID_9_PatientAlias>
<PN_0_FamiliyName />
</PID_9_PatientAlias>
<PID_10_Race />
<PID_11_PatientAddress>
<AD_0_StreetAddress>1111 XXXXX ST</AD_0_StreetAddress>
<AD_1_OtherDesignation />
<AD_2_City>XXXXXXX</AD_2_City>
<AD_3_StateOrProvince>VA</AD_3_StateOrProvince>
<AD_4_ZipOrPostalCode>12345</AD_4_ZipOrPostalCode>
</PID_11_PatientAddress>
<PID_12_CountyCode />
<PID_13_PhoneNumberHome>(111)555-3108</PID_13_PhoneNumberHome>
<PID_14_PhoneNumberBusiness />
<PID_15_LanguagePatient />
<PID_16_MaritalStatus>S</PID_16_MaritalStatus>
<PID_17_Religion />
<PID_18_PatientAccountNumber>
<CK_PAT_ID_0_PatientId>0123456789</CK_PAT_ID_0_PatientId>
</PID_18_PatientAccountNumber>
<PID_19_SocialSecurityNumberPatient>000-00-0000</PID_19_SocialSecurityNumberPatient>
</PID_PatientIdentification>
<PV1_PatientVisit>
<PV1_1_SetIdPatientVisit>1</PV1_1_SetIdPatientVisit>
<PV1_2_PatientClass>B</PV1_2_PatientClass>
</PV1_PatientVisit>
<GT1_Guarantor>
<GT1_1_SetIdGuarantor>1</GT1_1_SetIdGuarantor>
<GT1_2_GuarantorNumber />
<GT1_3_GuarantorName>
<PN_0_FamiliyName>XXXX</PN_0_FamiliyName>
<PN_1_GivenName>XXXXXXX</PN_1_GivenName>
<PN_2_MiddleInitialOrName />
</GT1_3_GuarantorName>
<GT1_5_GuarantorAddress>
<AD_0_StreetAddress>1111 XXXXXXX ST</AD_0_StreetAddress>
<AD_1_OtherDesignation />
<AD_2_City>XXXXXXXXX</AD_2_City>
<AD_3_StateOrProvince>VA</AD_3_StateOrProvince>
<AD_4_ZipOrPostalCode>12345</AD_4_ZipOrPostalCode>
</GT1_5_GuarantorAddress>
</GT1_Guarantor>
<IN1_Insurance>
<IN1_1_SetIdInsurance>1</IN1_1_SetIdInsurance>
<IN1_2_InsurancePlanId />
<IN1_3_InsuranceCompanyId />
<IN1_4_InsuranceCompanyName>XXXXXXXXXXXXxxx</IN1_4_InsuranceCompanyName>
<IN1_5_InsuranceCompanyAddress>
<AD_0_StreetAddress>XXXXXx</AD_0_StreetAddress>
<AD_1_OtherDesignation>PO BOX xxxxx</AD_1_OtherDesignation>
<AD_2_City>XXXXXXXXX</AD_2_City>
<AD_3_StateOrProvince>VA</AD_3_StateOrProvince>
<AD_4_ZipOrPostalCode>12345</AD_4_ZipOrPostalCode>
</IN1_5_InsuranceCompanyAddress>
<IN1_6_InsuranceCompanyContactPers>
<PN_0_FamiliyName />
<PN_1_GivenName />
</IN1_6_InsuranceCompanyContactPers>
<IN1_7_InsuranceCompanyPhoneNumber />
<IN1_8_GroupNumber>OD0012345</IN1_8_GroupNumber>
<IN1_9_GroupName />
<IN1_10_InsuredSGroupEmployerId />
<IN1_11_InsuredSGroupEmployerName />
<IN1_12_PlanEffectiveDate>20071217</IN1_12_PlanEffectiveDate>
<IN1_13_PlanExpirationDate>20241231</IN1_13_PlanExpirationDate>
<IN1_14_AuthorizationInformation>
<CM_AUI_0_AuthorizationNumber />
</IN1_14_AuthorizationInformation>
<IN1_15_PlanType />
<IN1_16_NameOfInsured>
<PN_0_FamiliyName>RIMON</PN_0_FamiliyName>
<PN_1_GivenName>XXXXXXXXXX</PN_1_GivenName>
</IN1_16_NameOfInsured>

<IN1_17_InsuredSRelationshipToPatient>F</IN1_17_InsuredSRelationshipToPatient>
<IN1_18_InsuredSDateOfBirth>XXXXXXXX</IN1_18_InsuredSDateOfBirth>
<IN1_19_InsuredSAddress>
<AD_0_StreetAddress />
</IN1_19_InsuredSAddress>
<IN1_20_AssignmentOfBenefits />
<IN1_21_CoordinationOfBenefits />

<IN1_22_CoordinationOfBenefitsPriority>1</IN1_22_CoordinationOfBenefitsPriority>
<IN1_23_NoticeOfAdmissionCode />
<IN1_24_NoticeOfAdmissionDate />
<IN1_25_ReportOfEligibilityCode />
<IN1_26_ReportOfEligibilityDate />
<IN1_27_ReleaseInformationCode />
<IN1_28_PreAdmitCertificationPac />
<IN1_29_VerificationDateTime>
<TS_0_TimeOfAnEvent />
</IN1_29_VerificationDateTime>
<IN1_30_VerificationBy>
<CN_PERSON_0_IdNumber />
</IN1_30_VerificationBy>
<IN1_31_TypeOfAgreementCode />
<IN1_32_BillingStatus />
<IN1_33_LifetimeReserveDays />
<IN1_34_DelayBeforeLifetimeReserveDays />
<IN1_35_CompanyPlanCode />
<IN1_36_PolicyNumber>Y1234567890</IN1_36_PolicyNumber>
<IN1_37_PolicyDeductible />
<IN1_38_PolicyLimitAmount />
<IN1_39_PolicyLimitDays />
<IN1_40_RoomRateSemiPrivate />
<IN1_41_RoomRatePrivate />
<IN1_42_InsuredSEmploymentStatus>
<CE_0066_0_Identifier />
</IN1_42_InsuredSEmploymentStatus>
<IN1_43_InsuredSSex>U</IN1_43_InsuredSSex>
</IN1_Insurance>
</ns1:ADT_A08_22_GLO_DEF>

Ed Ip

unread,

Jul 7, 2008, 2:58:02 PM7/7/08

to

Wow...I'm not sure if I should be upset or embarrassed. But I figured it
out. While everyone's advice has helped me chip away at the problem, the
root of it all is in my MSHSegment. I copied and pasted from the Message
Enrichment tutorial with MSH_24_GLO_DEF, but it should really have been
MSH_25_GLO_DEF.

Amazing what a single digit can do to your hair. Regardless, thanks for all
the help!!

Mittapally@discussions.microsoft.com Ramakrishna Mittapally

unread,

Jul 17, 2008, 6:11:04 PM7/17/08

to

Hi Ed,

I am also facing the same kind of issue, I have BizTalk 2006 and HL7 1.3
installed in my system. I could not find MSH_25_GLO_DEF schema, may be this
is because i do not have R2 installed in my system.

I am using Customized schemas ( i.e I changed the namespace in
ADT_A31_23_GLO_DEF.xsd , Datatypes_23.xsd,Segments_23.xsd and
tablevalues_23.xsd )

Can any one help me getting out these errors using MSH_24_GLO_DEF as MSH
segment instead of MSH_25_GLO_DEF? Or is there any bug fix available for
BizTalk 2006?

Here are the errors that i am getting in HL7 Send pipeline:

Alternate Error Number: 301
Alternate Error Description: Unexpected end of message body found
Alternate Encoding System: HL7-BTA

Error # 2
Segment Id:
Sequence Number: 1
Error Number: 100

Error Description: Segment sequence error (Empty value not allowed for

segment as it has at least one required field)

Encoding System: HL7nnnn

Error # 3
Segment Id: EVN_EventType

Sequence Number: 1
Field Number: 1

Error Number: 102
Error Description: Data type error
Encoding System: HL7nnnn

Error # 4
Segment Id: PID_PatientIdentification
Sequence Number: 1
Field Number: 2
Error Number: 20

Eric Stott

unread,

Jul 18, 2008, 8:46:55 AM7/18/08

to

I am sure you can hack your way into getting 2.5 schemas out there, but it
is not officially supported until 2.0.

"Ramakrishna Mittapally" <Ramakrishna Mitta...@discussions.microsoft.com>
wrote in message news:C5121851-7304-4AE3...@microsoft.com...

Tom Canter - Neudesic

unread,

Jul 18, 2008, 9:20:06 AM7/18/08

to

Ramakrishna,
I'm not convinced that you have the same problem. The error message is
the same, but I think it is because of different reasons.
You have Errors after the Error # 100.
Please validate the XML Message against the XML Schema.

Thanks,
Tom

crreddy

unread,

Mar 16, 2011, 4:22:32 AM3/16/11

to

Jens Franck wrote on 04/18/2008 08:26 ET :
> Hi,
>
> we are trying to create a HL7 message. The orchestration builds the complete
> ORU^01 (v2.4) message with his 3 parts, but we have an error once it is
> processed by the HL7 send pipeline. We created the parts of the multipart
> message in the right order.
>
> The message assingment part looks like:
> HeaderInfo = new System.Xml.XmlDocument();
> HeaderInfo.LoadXml("<ns0:MSH_24_GLO_DEF
>

xmlns:ns0="http://microsoft.com/HealthCare/HL7/2X"><MSH><MSH.2_EncodingCharacters>^~&</MSH.2_EncodingCharacters><MSH.3_SendingApplication><HD.0_NamespaceId>SrcApp</HD.0_NamespaceId><HD.1_UniversalId>SrcAppUid</HD.1_UniversalId></MSH.3_SendingApplication><MSH.4_SendingFacility><HD.0_NamespaceId>srcFac</HD.0_NamespaceId><HD.1_UniversalId>srcFacUid</HD.1_UniversalId></MSH.4_SendingFacility><MSH.5_ReceivingApplication><HD.0_NamespaceId>dstApp</HD.0_NamespaceId><HD.1_UniversalId>dstAppUid</HD.1_UniversalId></MSH.5_ReceivingApplication><MSH.6_ReceivingFacility><HD.0_NamespaceId>dstFac</HD.0_NamespaceId><HD.1_UniversalId>dstFacUid</HD.1_UniversalId></MSH.6_ReceivingFacility><MSH.7_DateTimeOfMessage><TS.1>200307092343</TS.1></MSH.7_DateTimeOfMessage><MSH.8_Security>sec</MSH.8_Security><MSH.9_MessageType><CM_MSG.0_MessageType>ORU</CM_MSG.0_MessageType><CM_MSG.1_TriggerEvent>R01</CM_MSG.1_TriggerEvent></MSH.9_MessageType><MSH.10_MessageControlId>msgid2134</MSH.10_MessageControlId><MSH.11_ProcessingId><PT.0_ProcessingId>P</PT.0_ProcessingId></MSH.11_ProcessingId><MSH.12_VersionId><VID_0_VersionId>2.4</VID_0_VersionId></MSH.12_VersionId></MSH></ns0:MSH_24_GLO_DEF>");

>
> FinalORU.MSHSegment = HeaderInfo;
> FinalORU.BodySegments = ORUBODY;
> FinalORU.ZSegments = "";
>
> FinalORU(BTAHL7Schemas.MSH1) = 124;

> FinalORU(BTAHL7Schemas.MSH2) = "^~&";

> FinalORU(BTAHL7Schemas.ParseError) = false;
> FinalORU(BTAHL7Schemas.ZPartPresent) = false;
> FinalORU(BTAHL7Schemas.SegmentDelimiter2Char) = true;
>

> //FinalORU(BTAHL7Schemas.Encoding)e001;

Hi,

Environment: Biztalk 2010, HL7 Acc 2.0, VS 2010
Requirement: ORU^R01 message of version 2.5.1 and the version is not
supported
by HL7 Acc 2.0
WorkAround: Purchased "Hl7_63.mdb" access database from HL7
organization, generated ORU_R01_251_GLO_DEF.xsd, segments_251.xsd,
tablevalues_251.xsd and datatypes_251.xsd schemas from the database.

Was trying to create message as usual throught orchestration ( MSHSegment +
BodySegment +Zsegment)

Added, 2.5.1 value to Table104 of tablevalues_251.xsd too and header message
is
as follows....
<ns0:MSH_25_GLO_DEF

xmlns:ns0="http://microsoft.com/HealthCare/HL7/2X"><MSH><MSH.2_EncodingCharacters>^~\&</MSH.2_EncodingCharacters><MSH.3_SendingApplication><HD.0_NamespaceId>GDBSIS</HD.0_NamespaceId></MSH.3_SendingApplication><MSH.4_SendingFacility><HD.0_NamespaceId>GDBSIS</HD.0_NamespaceId></MSH.4_SendingFacility><MSH.5_ReceivingApplication><HD.0_NamespaceId>PartyName</HD.0_NamespaceId></MSH.5_ReceivingApplication><MSH.6_ReceivingFacility><HD.0_NamespaceId>Raj</HD.0_NamespaceId></MSH.6_ReceivingFacility><MSH.7_DateTimeOfMessage><TS.2>"
+ msgDateTime.ToString("yyyyMMddHHss") +

"</TS.2></MSH.7_DateTimeOfMessage><MSH.8_Security>sec</MSH.8_Security><MSH.9_MessageType><CM_MSG.0_MessageType>ORU</CM_MSG.0_MessageType><CM_MSG.1_TriggerEvent>R01</CM_MSG.1_TriggerEvent></MSH.9_MessageType><MSH.10_MessageControlId>"
+ msgID.ToString("N") +

"</MSH.10_MessageControlId><MSH.11_ProcessingId><PT.0_ProcessingId>P</PT.0_ProcessingId></MSH.11_ProcessingId><MSH.12_VersionId><VID_0_VersionId>2.5.1</VID_0_VersionId></MSH.12_VersionId></MSH></ns0:MSH_25_GLO_DEF>

Error Message: Error happened in header during serialization Error # 1 Segment
Id: MSH Sequence Number: 1 Field Number: 12 Error Number: 203 Error

Description:
Unsupported version id Encoding

Note: If I give 2.5 as version id instead of 2.5.1, it creating ORU message

Please let me know, if any once faced such error / resolved it.

Thanks in advance