Claims may appear to be lost when a transaction is submitted to the BizTalk Server Accelerator for HIPAA 2.0 (884785)
The information in this article applies to:
- Microsoft BizTalk Server Accelerator for HIPAA 2.0
- Microsoft BizTalk Server 2002
SYMPTOMSClaims may appear to be lost when a transaction is submitted
to the Microsoft BizTalk Server Accelerator for HIPAA 2.0 and one or more of
the claims in the submitted HIPAA transaction
are in error.CAUSEThe claims are not actually lost. Instead, the claims are
put in the suspended queue of the BizTalk Server with the whole transaction. These claims, from the claim in error forward, will not be processed further without administrator intervention.
MORE INFORMATIONWhen a transaction is submitted to a BizTalk HIPAA
Server and you use the multiple version of the schema to
process the interchange, the BizTalk Server Accelerator for HIPAA 2.0 will try
to retrieve and generate all valid claims in the transaction.
The
transaction is processed sequentially. After each claim is generated, it is
processed. When the BizTalk Server Accelerator for HIPAA 2.0 encounters an
error within the transaction, the transaction is suspended and is put in the
suspended queue of the BizTalk Server. When this one error is encountered, a 997 functional acknowledgment
is generated with an AK501 segment of E. This value means "Accepted but Errors Were Noted".
At this point, you must examine the 997 functional acknowledgment and then look for the AK3 segment. The AK3 segment identifies the first claim in the transaction that contains an error. The erroneous claim and all claims that follow the erroneous claim in the transaction are expected to be resubmitted. You can consider the claims that were processed before this point to have been delivered successfully.
| Modification Type: | Major | Last Reviewed: | 9/9/2004 |
|---|
| Keywords: | kbprb kbtshoot KB884785 kbAudDeveloper |
|---|
|