HIPAA Document Failure May Cause the BizTalk Server Receive Functions to Fail (313686)


The information in this article applies to:

  • Microsoft BizTalk Server Accelerator for HIPAA 1.0
This article was previously published under Q313686

SYMPTOMS

When you send an 837 Health Care Claim document (Professional, Dental, or Institutional) that is invalid through the Health Insurance Portability and Accountability Act (HIPAA) parser, BizTalk Server receive functions may fail. When the document fails validation, the parser causes a Microsoft COM+ exception, which causes the BizTalk Server receive function that is used to receive the HIPAA document to fail.

RESOLUTION

To resolve this problem, obtain the latest service pack for BizTalk Accelerator for HIPAA 1.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

321233 How to Obtain the latest BizTalk Accelerator for HIPAA 1.0 Service Pack

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in BizTalk Accelerator for HIPAA 1.0 Service Pack 1a.

MORE INFORMATION

The Application event log may contain information that is similar to the following:
Details:
-----------------------------
The required "TS837Q1_2310B_PRV_RenderingProviderSpecialtyInformation" record was not found in the inbound document.

The value of HL04 is incorrect.

The parser failed to convert the document due to processing errors. See the following messages for details.

Document 4 within submission "{5D005401-5021-4982-BB93-0E9AB63E7283}" was returned as a document that was not valid from the parser component named "BizTalk.ParserHipaaX12.1". The most frequent cause is a document specification that is not valid or else the component was unable to determine the necessary routing fields. Verify that the proper specification is defined for this data.


An error occurred in BizTalk Server.

Details:
------------------------------

The required "TS837Q1_2310B_PRV_RenderingProviderSpecialtyInformation" record was not found in the inbound document.


The value of HL04 is incorrect.

The parser failed to convert the document due to processing errors. See the following messages for details.

Document 9 within submission "{5D005401-5021-4982-BB93-0E9AB63E7283}" was returned as a document that was not valid from the parser component named "BizTalk.ParserHipaaX12.1". The most frequent cause is a document specification that is not valid or else the component was unable to determine the necessary routing fields. Verify that the proper specification is defined for this data.
The Component Object Model (COM) error is as follows:
The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below.
Component Prog ID:
Server Application ID: {6ECD95AC-3C06-4A9B-9D43-4565C1BD3319}
Server Application Name: BizTalk Server Internal Utilities
Exception: C0000005
Address: 0x0518976A
Call Stack:
CISHipaaParser!DllUnregisterServer + 0x5159
CISHipaaParser!DllUnregisterServer + 0x514A
CISHipaaParser!LKRhash::CLKRHashTable::_CalcKeyHash(unsigned long)const + 0x9
CISHipaaParser!CLKRCritSec::IsWriteLocked(void)const + 0x307A
CISHipaaParser!CLKRCritSec::IsWriteLocked(void)const + 0x28F
CISHipaaParser!LKRhash::CLKRLinearHashTable::NumSubTables(void)const + 0x1D31
CISHipaaParser!CLKRCritSec::IsWriteLocked(void)const + 0xEBC
CISHipaaParser!LKRhash::CLKRLinearHashTable::NumSubTables(void)const + 0x1C8C
CISHipaaParser!CLKRCritSec::IsWriteLocked(void)const + 0xEBC
CISHipaaParser!LKRhash::CLKRLinearHashTable::NumSubTables(void)const + 0x1C8C
CISHipaaParser!CLKRCritSec::IsWriteLocked(void)const + 0xEBC
CISHipaaParser!LKRhash::CLKRLinearHashTable::NumSubTables(void)const + 0x1C8C
CISHipaaParser!CLKRCritSec::IsWriteLocked(void)const + 0xEBC
CISHipaaParser!LKRhash::CLKRLinearHashTable::NumSubTables(void)const + 0x1C8C
CISHipaaParser!CLKRCritSec::IsWriteLocked(void)const + 0xEBC
CISHipaaParser!LKRhash::CLKRLinearHashTable::NumSubTables(void)const + 0x14F7
CISHipaaParser!CLKRCritSec::IsWriteLocked(void)const + 0x689
CISHipaaParser!DllUnregisterServer + 0x4279
CISParser!LKRhash::CLKRHashTable::End(void) + 0x2484
CISParser!LKRhash::CLKRHashTable::End(void) + 0x1ED5
CISENGINE!LKRhash::CLKRHashTable::End(void) + 0x1F9B
CISENGINE!GetNewStateEngine(struct IInterchangeStateEngine * *) + 0x10E4
CISENGINE!GetNewStateEngine(struct IInterchangeStateEngine * *) + 0xCD3
CISENGINE!GetNewStateEngine(struct IInterchangeStateEngine * *) + 0x47B
CISENGINE!CFakeLock::ReadOrWriteUnlock(bool) + 0x3D0
RPCRT4!NdrServerInitialize + 0x1E8
RPCRT4!NdrStubCall2 + 0x586
RPCRT4!CStdStubBuffer_Invoke + 0x9E
OLEAUT32!UserEXCEPINFO_free_local + 0x20C4 + 0xFFFFFFF
Modification Type:MinorLast Reviewed:9/23/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix KB313686
©2004 Microsoft Corporation. All rights reserved.