Mohsin Kalam’s Blog

December 18, 2007

HIPAA QFE for R2

Filed under: R2 EDI — Mohsin Kalam @ 2:08 pm

For HIPAA documents with equivalent subloops and/or equivalent segments (such as 837 claim documents) the EDI engine in BizTalk Server 2006 R2 would incorrectly generate validation errors when these loops and/or segments were not in the same order as they were in the schema. The HIPAA standard allows equivalent subloops and segments to appear in any order and therefore errors should not be generated in these situations. This fix provides updated HIPAA schemas and modifications to the EDI engine to address this issue.

The QFE can be found at the following link

http://www.microsoft.com/downloads/details.aspx?FamilyId=ED9C18F8-9842-4CBB-BD34-1FCD7D196900&displaylang=en

Thanks

Mohsin Kalam

Advertisements

4 Comments »

  1. Hi

    This isn’t a comment on the post as such, but a request for you to add a link to the RSS feed for your blog to your blog… so we can subscribe via our favorite rss reader.

    Turns out the url of the feed is https://mohsinkalam.wordpress.com/rss – but that doesn’t appear anywhere on your blog 🙂


    eliasen

    Comment by Jan Eliasen — December 25, 2007 @ 12:32 pm

  2. Thanks Eliasen. Will do

    Comment by Mohsin Kalam — January 2, 2008 @ 12:43 pm

  3. Using the schemas from this QFE, I had a number of valid HIPAA documents fail.

    If you agree – It might also be worth mentioning that the schemas(at least 837P and 835 so far) need to have the min occurs property set to zero on subloops where all of the members of that loop are situational (not required). (eg. AMT_TS837Q1_2300_SubLoop and many others)

    Comment by Chris Miller — March 4, 2008 @ 7:14 am

  4. Hi Mohsin,

    I am having the same problem than Chris. When I try to validate some 837P valid files with the schema from this QFE it raises a lot of errors.
    Do we have to modify the schema in this QFE?
    Is there another QFE with the correct schema?

    Thanks.

    Comment by Luis Pandolfi — May 29, 2008 @ 6:36 am


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Create a free website or blog at WordPress.com.

%d bloggers like this: