Given the "up in the air" aspects of HIPAA TCS error
reporting, I wonder whether or not the HIPAA transaction certification
engines that are out there today come "out of the box" configured so that they
won't "let through" a transaction if it's missing a
HIPAA-required field that is optional per X12...given the
obvious competence of the folks who are working the HIPAA effort, and the
fact that some of those folks use the WEDI SNIP testing levels 1-6 model, I'd
assume the answer is that they won't "let through" these
transactions...but we all know the dangers of assuming...perhaps
some certification engines do and some don't...
More relevant to this week's discussion is the same
question applied to transactions managers that generate 997s in response to
submitted 837s...Rachel pointed out that "... the 997
can be kludged to report guide syntax errors, such as missing mandatory
segment or element..." (Thank you
Rachel!) I wonder if the transactions managers that are being billed as
"HIPAA-ready" currently come kludged (configured?) to do the appropriate
HIPAA-specific mandatory data element error reporting...(I'm not asking about
the inter-segment dependency errors, just the black-and-white HIPAA-mandated,
X12-optional).
Sounds like there won't be a 997 or 824 IG before the 10/16/03
deadline, so what we have today is what we have...And the 997 is what everyone
is reading as the standard if they're only looking at the IGs and addenda, which
is all that they're required by law to look at...
Cynthia Korman, Principal
Strategic System Solutions, LLC 973 394-9529 [EMAIL PROTECTED] www.healthcare-systems.com
********************************************************************** To be removed from this list, send a message to: [EMAIL PROTECTED] Please note that it may take up to 72 hours to process your request. ===================================================== The WEDI SNIP listserv to which you are subscribed is not moderated. The discussions on this listserv therefore represent the views of the individual participants, and do not necessarily represent the views of the WEDI Board of Directors nor WEDI SNIP. If you wish to receive an official opinion, post your question to the WEDI SNIP Issues Database at http://snip.wedi.org/tracking/. Posting of advertisements or other commercial use of this listserv is specifically prohibited. |
Title: RE: questions on the appropriate way to reply when there are error in a transaction request
- compliance with x12 vs. HIPAA IG Cynthia Korman
- RE: compliance with x12 vs. HIPAA IG Bill Chessman
- RE: compliance with x12 vs. HIPAA IG Augustine, Mike
- RE: Compliance with x12 vs. HIPAA IG Cynthia Korman
- RE: Compliance with x12 vs. HIPAA IG Rachel Foerster
- Re: Compliance with x12 vs. HIPAA IG Kepa Zubeldia
- RE: Compliance with x12 vs. HIPAA IG Barton, Joe
- Re: Compliance with x12 vs. HIPAA IG William J. Kammerer
- RE: Compliance with x12 vs. HIPAA IG Rachel Foerster
- RE: Compliance with x12 vs. HIPAA IG Barton, Joe
- RE: Compliance with x12 vs. HIPAA IG Rachel Foerster
- Re: Compliance with x12 vs. HIPAA I... Cynthia Korman
- Re: Compliance with x12 vs. HIPAA I... David A. Feinberg, C.D.P.
- RE: Compliance with x12 vs. HIP... Rachel Foerster
