Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: An HIPAA 837 document is suspended unexpectedly in BizTalk Server 2006 R2 if the "REF*G1" data element and the "REF*9F" data element are not adjacent


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You use Microsoft BizTalk Server 2006 R2 to receive and process Health Insurance Portability and Accountability Act (HIPAA) messages.
  • You receive a valid 837 document in BizTalk Server.
  • In this 837 document, the "REF*G1" data element and "REF*9F" element are not adjacent. For example, the data elements in the document resemble the following:
    REF*G1*6666666~
    REF*EA*777-7777~
    REF*9F*888888888~
In this scenario, the 837 document fails the validation and is suspended unexpectedly. Additionally, you receive an error that resembles the following in the Application log:

Event Type: Error
Event Source: BizTalk Server 2006 EDI
Event Category: None
Event ID: 8114
Description:
Error encountered during parsing. The X12 transaction set with id '<transaction set id>' contained in functional group with id '<functional group id>', in interchange with id '<interchange id>', with sender id '<sender id>', receiver id '<receive id>' is being suspended with following errors:

Error: 1 (Segment level error)
SegmentID: REF
Position in TS: 26
7: Segment Not In Proper Sequence

Error: 2 (Segment level error)
SegmentID: REF
Position in TS: 26
2: Unexpected segment

Error: 3 (Field level error)
SegmentID: REF
Position in TS: 26
Data Element ID: REF01__ReferenceIdentificationQualifier
Position in Segment: 1
Data Value: 9F
7: Invalid code value
...

Note�This problem does not occur if the "REF*G1" data element and "REF*9F" element are adjacent in the incoming 837 message. For example,�this problem does not occur if the data elements resemble the following:
REF*G1*6666666~
REF*9F*888888888~
REF*EA*777-7777~

↑ Back to the top


Cause

This problem occurs because the EDI message engine does not process the xs:all type of subloops of HIPAA documents according to the HIPAA standard that is published by Washington Publishing Company (WPC).

↑ Back to the top


Resolution

The hotfix that resolves this problem is included in cumulative update package 2 for BizTalk Server 2006 R2 Service Pack 1.

�For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2211420� Cumulative update package 2 for BizTalk Server 2006 R2 Service Pack 1

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


References

For more information about the description of the SQL Server Agent jobs in BizTalk Server, click the following article number to view the article in the Microsoft Knowledge Base:

919776� Description of the SQL Server Agent jobs in BizTalk Server

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684� Description of the standard terminology that is used to describe Microsoft software updates
For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907� Information about BizTalk Server hotfixes


For more information about the list of Microsoft BizTalk Server hot fixes that are included in BizTalk Server 2006 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
974563� List of Microsoft BizTalk Server hot fixes that are included in BizTalk Server 2006 R2 Service Pack 1

↑ Back to the top


Keywords: KB2191569, kbfix, kbhotfixserver, kbqfe, kbautohotfix

↑ Back to the top

Article Info
Article ID : 2191569
Revision : 1
Created on : 7/8/2010
Published on : 7/8/2010
Exists online : False
Views : 428