A hotfix is available for Microsoft BizTalk Server 2013, Microsoft BizTalk Server 2010, and Microsoft BizTalk Server 2009.This hotfix enables support for Health Insurance Exchange (HIX) EDI transactions 005010x306 (820) and 005010x220 (834). This hotfix includes HIPAA 5010 compliant schemas that you can build and deploy in your BizTalk Electronic Data Interchange (EDI) application.
For BizTalk Server 2010
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:Note
In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Cumulative update information
BizTalk Server 2009
The hotfix that resolves this issue is included in cumulative update package 7 for BizTalk Server 2009.
For more information about how to obtain the cumulative update package, see Cumulative update package 7 for BizTalk Server 2009
BizTalk Server 2013
The hotfix that resolves this issue is included in cumulative update package 2 for BizTalk Server 2013.
For more information about how to obtain the cumulative update package, see Cumulative update package 2 for BizTalk Server 2013
An older version of the transaction 820 schema was previously included with BizTalk Server. Therefore, this hotfix has the same doctype as the existing transaction 820 schema. The new and old transaction 820 schemas cannot coexist in a BizTalk deployment . If both of the transaction 820 schemas have to be used in a BizTalk deployment, you must change the namespace of the new schema so that both schemas can be uniquely identified and used in the BizTalk application. In this case, the new schema has to be treated as a custom schema.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.