Jonathan Allen thinks it's "...interesting .... that although HIPAA
[claims] full X12 compliance, their ICs are in fact wildly out of
compliance in many ways with X12's own Technical Report on Compliance
with X12."
To the best of my knowledge, transaction sets conforming to the HIPAA
Implementation Guides are fully compliant with X12. Any valid HIPAA
transaction will pass with flying colors through an EDISIM Analyzer
syntax check against the original X12 standard - the ultimate proof of
X12 compliance! There are no instances I know of where HIPAA uses
segments or loops not defined in the base X12 004010 transaction sets,
or uses them out of place, or exceeds max occurrences or lengths, or
mandates code values disallowed by X12, or does anything of that ilk
which normally would make one think of non-compliance.
Jonathan fails to elaborate precisely what HIPAA does that is out of
compliance with X12. Every valid HIPAA transaction set is also a valid
X12 transaction set. A careful reading of Jonathan's statement reveals
that he is merely saying their *implementation guide* is out of some
kind of conformance with an obscure X12 Technical Report ("Compliance in
X12" - X12C/99-197 - published in 1999).
The HIPAA implementation guides fairly well describe valid X12
transaction subsets. If the HIPAA IGs really are *wildly* out of
compliance with this vaunted Technical Report, then perhaps there's
something wrong with the latter and not with the HIPAA guides
themselves.
William J. Kammerer
FORESIGHT Corp.
4950 Blazer Memorial Pkwy.
Dublin, OH USA 43017-3305
+1 614 791-1600
Visit FORESIGHT Corp. at http://www.foresightcorp.com/
"Commerce for a New World"
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
