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

Consider the following scenario:

• You use Microsoft BizTalk Server 2006 R2 or Microsoft BizTalk Server 2009 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:


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~

Note: If you use BizTalk Server 2009, the Event Source and Event Category in above events are “BizTalk Server 2009”.

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).

Cumulative update information

BizTalk Server 2009

The hotfix that resolves this issue is included in cumulative update package 2 for BizTalk Server 2009.
For more informationabout how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: To resolve this issue, run the self-extracting MicrosoftEdiXSDTemplatesKb2191569.exe file that is included in Cumulative update package 2 for BizTalk Server 2009 to obtain updated schemas. Then, redeploy the schemas. If you have any custom schemas, apply custom changes to the new schemas.

Note The updated schemas also resolve another issue that occurs when BizTalk Server processes HIPAA messages. For detailed information, see the "More information" section of this article.

BizTalk Server 2006 R2

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  (http://support.microsoft.com/kb/2211420/ ) Cumulative update package 2 for BizTalk Server 2006 R2 Service Pack 1

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

Additionally, the updated schemas that are included in cumulative update package 2 for BizTalk Server 2009 also fix an issue in which the following errors are logged in the Application log. This issue occurs when BizTalk Server receives an HIPAA message.




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: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

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: