FIX: You cannot use trailing spaces to satisfy minimum field length requirements in BizTalk Server Accelerator for HIPAA 2.0 (837118)



The information in this article applies to:

  • Microsoft BizTalk Server Accelerator for HIPAA 2.0

SYMPTOMS

In Health Insurance Portability and Accountability Act (HIPAA) schemas, some fields have minimum length requirements. HIPAA implementation guides suggest that you can use trailing spaces in a field to satisfy the minimum length requirement. However, when Microsoft BizTalk Server Accelerator for HIPAA parses a field that has trailing spaces included to satisfy the minimum length requirement, BizTalk Server Accelerator for HIPAA rejects the document and you receive an error message that is similar to the following:
An error occurred in BizTalk Server.

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

[0x1449] The data contains a field value ("P") that doesn't meet minimum length requirement for tag "TS837Q1_2010BB_N401__PayerCityName" (minimum length is 2).

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

[0x1441] Document #1 within submission "{9069455D-7562-4675-B5A0-120F7BFE2F97}" 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.

[0x1730] Suspended Queue ID: "{A1EC9D37-F5D0-48F5-9D91-73E996E3384B}"

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next BizTalk Server Accelerator for HIPAA 2.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: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.

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version     Size       File name
   -----------------------------------------------------------------------------------------------
   23-Feb-2004  22:43  2.2.2192.0    381,952  Cishipaaparser.dll
   23-Feb-2004  22:43  2.2.2192.0    481,280  Hipaavalidatedoc.dll
   13-Mar-2004  03:28                104,083  270_v2_wpc_trailingspaceqfe.xml
   13-Mar-2004  03:36                162,277  271_v2_wpc_trailingspaceqfe.xml
   17-Mar-2004  01:36              1,764,966  275_v1_wpc_trailingspaceqfe.xml
   13-Mar-2004  01:47                 86,863  276_v2_wpc_trailingspaceqfe.xml
   13-Mar-2004  03:19                119,044  277_v2_wpc_trailingspaceqfe.xml
   17-Mar-2004  01:28                 96,232  820_v2_wpc_trailingspaceqfe.xml
   17-Mar-2004  00:11                154,957  834_v2_wpc_multiple_trailingspaceqfe.xml
   17-Mar-2004  00:31                154,923  834_v2_wpc_single_trailingspaceqfe.xml
   20-Mar-2004  18:36                163,052  835_v2_wpc_multiple_plbqfe_trailingspaceqfe.xml
   20-Mar-2004  18:38                162,985  835_v2_wpc_single_trailingspaceqfe.xml
   17-Mar-2004  00:50                305,762  837dental_v2_wpc_multiple_trailingspaceqfe.xml
   17-Mar-2004  01:13                305,665  837dental_v2_wpc_single_trailingspaceqfe.xml
   20-Mar-2004  18:06                629,742  837institutional_v2_wpc_multiple_trailingspaceqfe.xml
   19-Feb-2004  21:38                629,645  837institutional_v2_wpc_single_trailingspaceqfe.xml
   01-Mar-2004  22:22                558,371  837professional_v2_wpc_multiple_trailingspaceqfe.xml
   19-Feb-2004  21:53                558,274  837professional_v2_wpc_single_trailingspaceqfe.xml
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

STATUS

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

MORE INFORMATION

For this hotfix to take effect, you must use the updated schemas that are included in the hotfix package. For additional information about the terminology that is used to describe Microsoft product updates, 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


Modification Type:MinorLast Reviewed:10/26/2005
Keywords:kbHotfixServer kbQFE kbHotfixServer kbQFE kberrmsg kbQFE kbfix kbbug KB837118 kbAudDeveloper