BizTalk 2010 Error Encountered During Parsing HIPAA 5010 Transactions

Hello,

Last week I was testing the parties after configuration on a BizTalk 2010 server for HIPPA 5010 transactions. I was facing the following error with one of the parties:

Error:

Error encountered during parsing. The X12 interchange with id ’000000001′, with sender id ’9999999 ‘, receiver id ’1111111 ‘ had the following errors:

Error: 1 (Miscellaneous error)

16: Invalid Control Standard Identifier

Error: 2 (Field level error)

SegmentID: ISA

Position in TS: 1

Data Element ID: ISA11

Position in Segment: 11

Data Value: ^

7: Invalid code value

I checked the party settings, everything was looking fine but still I was getting the error.

We know that ISA11 can be used in X12 as a standard identifier or a repetition separator and if we want to use as a repetition separator then we need to check the Envelop value. I did the same but still getting the error.

Then I changed the property of UseIsa11AsRepetitionSeprator value to TRUE, EDI disassembler stage in the pipeline component and it worked.

- Ratikant Pawar

BizTalk Server 2010 – HIPAA – Errata Hotfix

Hello,

After I installed BizTalk 2010 on my server, I was working with HIPAA 5010 transactions. While testing a few transactions in BizTalk I found that the EDI component functionality was not exactly working as it should. The issue is described below.

Error
The trading partner information in the party configuration is entered correctly. For testing the trading partner I used an EDI default pipeline EDI Receive to disassemble my EDI message. When I proceeded to test the EDI file it gave me the below error

“Finding the document specification by message type ‘http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00501_837‘ failed. Verify the schema deployed properly”

I tried to change the party settings for the trading partner but no luck. The same error was shown.

Resolution
After BizTalk server 2010 was installed, I hadn’t installed any hotfixes related to HIPAA 5010 transactions. So I installed the Errata hotfix and the transactions worked smoothly.

Microsoft has released a hotfix which enables support for HIPAA 5010 standards in BizTalk Server 2009/ 2010. This hotfix has HIPAA 5010 schemas that you can build and deploy in your EDI application.

This hotfix can be downloaded from http://support.microsoft.com/kb/973415.

  • Extract the hotfix and run the setup.exe application.
  • Restart the BizTalk host instance [system restart is not required].
  • Run the MicrosoftEdiXSDTemplatesKb2510733.exe file form the hotfix folder to extract latest HIPAA 5010 schemas. Save the schemas to the directory.
  • Note: \Program Files (x86)\Microsoft BizTalk Server 2010\XSD_Schema\EDI”

  • Use standard procedure for building and deploying the schemas.
  • This update is available for following transactions:

    Transaction Base Version ST03/GS08 Errata Version ST03/GS08
    270,271 Eligibility benefit Inquiry and Response 005010X279 005010X279A1
    834 Benefit Enrollment 005010X220 005010X220A1
    835 Claim Payment/ Advice 005010X221 005010X221A1
    837 Professional 005010X222 005010X222A1
    837 Institutional 005010X223 005010X223A2
    837 Dental 005010X223 005010X223A2

    Result
    Finally the EDI component worked and I was able to run the transactions without any failures.

    - Soujanya Vangapelli

    WCF SQL Adapter Poll Batching

    Recently we had to implement batching on the WCF SQL adapter.  Part of the reason for this post is whatever I do on the batch property on the settings of adapter it still wants to stream all polled results in one go.  This means BizTalk or AppFabric will wait until all results are received before starting to process them.  If you have 10,000 rows this could be 15-20 mins.

    I came up with a neat solution to prevent this from happening by changing the polling SQL statement.  The below code will select the top 10 records and then update those 10 in a transaction creating the batching that I desire.  To modify the batch of results just change the top statement:

    SELECT top 10 * FROM dbo.Table1 WHERE Status= ‘N’;
    UPDATE dbo.Table1 SET Status= ‘Y’ FROM (SELECT TOP 10 ID FROM dbo.Table1WHERE Status= ‘N’) b JOIN dbo.Table1bx ON b.ID= b.ID

    - John Shaw

    Failed to connect to the SQL database SSODB on SQL Server

    Today in BizTalk land I received the following error when I tried to configure BizTalk Standard on a 64 bit server  ”Failed to connect to the SQL database SSODB on SQL Server”

    After searching other blogs the reason for the issue is because the SQL types are missing.  You need to run 32-bit and 64-bit regasm.exe to get it fixed:

    “C:\Windows\Microsoft.NET\Framework64\v2.0.50727\regasm.exe” “C:\Program Files\Common Files\Enterprise Single Sign-On\SSOSQL.dll”

    “C:\Windows\Microsoft.NET\Framework\v2.0.50727\regasm.exe” “C:\Program Files\Common Files\Enterprise Single Sign-On\SSOSQL.dll”

    Visual Studio isn’t required for the above commands to work.  Not sure if the above will also fix the SQL Server 2008 R2 BizTalk 2009 compatibility issue…

    - John Shaw

    BizTalk 2009 Websphere MQ Communication on Windows 2008 64 bit

    All,

    After spending hours and reading the following blog http://social.msdn.microsoft.com/Forums/en-US/biztalkr2adapters/thread/0544b0cc-2044-499b-a824-5fefde90e77e.   Big thanks to Dejan and Malcolm.

    The fix to get the MQSC adapter working in Windows 2008 64 bit environment with BizTalk perform the following steps:

    -  Install MQ 7.0

    -  Install MQ 7.0.3 Break Fix

    -  Install BizTalk Host Adapters 2.0

    -  Put service account of MQ in the local mqm

    -  Save the below as a reg file and execute.

    John

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{CF8B4D15-5D2B-4c62-90DB-16804D2454B9}]
    @=”MQSC Adapter Class”
    “AppID”=”{401D2C40-DAA9-4a63-8D42-9BF98B04F616}”

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{CF8B4D15-5D2B-4c62-90DB-16804D2454B9}\BizTalk]
    @=”BizTalk”
    “TransportType”=”MQSC”
    “Constraints”=dword:00003d0b
    “ReceiveLocation_PageProv”=”{2DE93EE6-CB01-4007-93E9-C3D71689A280}”
    “TransmitLocation_PageProv”=”{2DE93EE6-CB01-4007-93E9-C3D71689A282}”
    “OutboundProtocol_PageProv”=”{2DE93EE6-CB01-4007-93E9-C3D71689A283}”
    “OutboundEngineCLSID”=”{6811E17F-A4C2-44BB-B4D5-D69962E58E87}”
    “InboundEngineCLSID”=”{538F8B3D-EE7B-4459-A123-45CD5C3B671B}”
    “InboundTypeName”=”Microsoft.BizTalk.Adapter.Mqsc.MqscReceiver, Microsoft.BizTalk.Adapter.MQSC, Version=7.0.2300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, Custom=null”
    “InboundAssemblyPath”=”"
    “OutboundTypeName”=”Microsoft.BizTalk.Adapter.Mqsc.MqscTransmitter, Microsoft.BizTalk.Adapter.MQSC, Version=7.0.2300.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, Custom=null”
    “OutboundAssemblyPath”=”"
    “PropertyNameSpace”=”http://schemas.microsoft.com/BizTalk/2003/mqs-properties
    “ProtocolAlias”=”mqsc://”
    “ReceiveHandlerPropertiesXML”=”<CustomProps><AdapterConfig vt=\”8\”/></CustomProps>”
    “SendHandlerPropertiesXML”=”<CustomProps><AdapterConfig vt=\”8\”/></CustomProps>”
    “ReceiveLocationPropertiesXML”=”<CustomProps><AdapterConfig vt=\”8\”/></CustomProps>”
    “SendLocationPropertiesXML”=”<CustomProps><AdapterConfig vt=\”8\”/></CustomProps>”
    “AliasesXML”=”<AdapterAliasList><AdapterAlias>mqsc://</AdapterAlias></AdapterAliasList>”
    “AdapterMgmtTypeName”=”Microsoft.BizTalk.Adapter.Mqsc.MqscAdapterManagement”
    “AdapterMgmtAssemblyPath”=”C:\\Program Files\\Microsoft BizTalk Adapters for Host Systems 2.0\\system\\Microsoft.BizTalk.Adapter.MQSCAdmin.dll”

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{CF8B4D15-5D2B-4c62-90DB-16804D2454B9}\Implemented Categories]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{CF8B4D15-5D2B-4c62-90DB-16804D2454B9}\Implemented Categories\{7F46FC3E-3C2C-405B-A47F-8D17942BA8F9}]
    @=”"

    - John Shaw

    Nimbo Have Implemented the first HIPAA 5010 Solution on a Microsoft Platform

    Nimbo are pleased to announce that Microsoft have endorsed a press release which documents that Nimbo are the first company to create a HIPAA 5010 upgrade on a Microsoft Platform. Many thanks go to our client, ConnectiCare, for working with us to create such a truly innovative solution.

    The press release is displayed below:

    Nimbo, a leader in Healthcare Channel Modernization solutions for HIPAA 5010 and ICD-10, announced today that ConnectiCare has deployed Nimbo and Microsoft technologies which achieved HIPAA 5010 compliance while modernizing its healthcare transaction processing infrastructure.

    Nimbo deployed a solution which utilized Microsoft BizTalk Server 2009, the BizTalk ESB Toolkit 2.0, Microsoft SQL Server 2008, Microsoft SharePoint Server 2007, and Microsoft Windows Server 2008.

    “ICD-10 codes are nearly 10 times larger than the ICD-9 code set they are replacing, which could place an almost overwhelming burden on practices,” said Hector Rodriguez, U.S. health plans industry technology strategist, Microsoft. “The combination of Microsoft and Nimbo will support a practice’s long-term IT strategies, including administrative simplification and ICD-10 adoption. BizTalk 2009 is vital to this conversion, allowing administrative tasks to be coupled with customer service, medical management and financial processes, which increases efficiencies for plans, providers and patients.”

    “A consistent goal for Nimbo has been to provide innovative and cost-effective solutions for our customers using Nimbo and Microsoft technologies, in an effort to reach HIPAA 5010 compliance. We’re really doing some cutting-edge things here. Our ability to connect any type of system through the use of BizTalk is really quite impressive,” said Ira Bell, Chief Information Officer, Nimbo.

    In addition to being specialists around the HIPAA 4010 to 5010 upgrade and ICD-9 to ICD-10 conversions; Nimbo has developed a useful portal which allows claims to be viewed as they are flowing through the system. The portal was created by combining custom software with SharePoint.

    “By providing an executive dashboard, we are able to deliver real-time information to the right individuals. This creates an immense value for our customers,” said John Shaw, President and CEO, Nimbo.

    To learn more about the Nimbo and Microsoft solution for achieving HIPAA 5010 compliance, please contact: info@nimbo.com

    About Nimbo

    Nimbo delivers IT products and solutions that satisfy the needs of medium and large enterprises. Our expertise includes developing innovative software solutions based on Microsoft .NET technologies and building intranet portals which combine information flow within a company.

    Why Choose Nimbo for your Cloud Computing?

    The cloud computing market is competitive. Here are the main reasons to choose a dedicated, tailored and attentive IT company to service your current business needs:

    1. Assessment. Nimbo will first offer a tailored assessment of your company’s IT needs. This is a review to decide where and how cloud computing can best improve your business. For example, you may need to update your network links prior to assessing the cloud (to attract even more clients); you may need to have a stronger firewall, given you’ll now be connected to far more business entities. Part of this assessment is understanding your current needs in terms of infrastructure: do you host your servers on-premise? What kind and capacity do you use at the moment? What kind of systems does your business use that sit on the infrastructure? How is the integration between the back end databases and the front end systems? What kind of applications does your business primarily use?
    2. Implemetation. Nimbo will then proceed to implementation. This is the restructuring of your current needs with an eye to the IT and business, networking and security needs of the future. One of Nimbo’s expert services is in Microsoft BizTalk, in which they are a Microsoft Gold Partner. Meanwhile, a new invoice-scanning and approval workflow system that he just rolled out uses Microsoft’s BizTalk Server to route information to and from the company’s various on- and off-premise systems. Nimbo can implement these services. BizTalk will manage data that different cloud applications process in different formats, including FTP, various Web services and custom APIs.
    3. Delivery. Nimbo has a proven track record of IT service – specializing in bringing your business comfortably into the cloud on time and on budget. For more information please contact Nimbo at info@Nimbo.com or visit the website at www.Nimbo.com.

    - Ira Bell

    Windows Application Infrastructure Launch Event

    Cloud computing offers a range of benefits, including elastic scale and never-seen-before applications. While you ponder your long-term investment in the cloud, you can harness cloud benefits in your current IT environment now.

    Join Microsoft at May 20 at 8:30 A.M. Pacific Time to learn how your current IT assets can harness the benefits of the cloud on-premises—and can readily connect to new applications and data running in the cloud. Plus, you’ll hear some exciting product announcements, and a keynote on Microsoft’s latest investments in the application infrastructure space aimed at delivering on-demand scalability, highly available applications, a new level of connectivity, and more!

    Launch event address : http://www.appinfrastructure.com/
    - John Shaw