Dave Frenkel says "[t]he ebXML schema has received some interesting
press for being extremely complex. X12 always received complaints for
being so generic and I think ebXML is having the same issues for keeping
all parties happy."
Hopefully, the complexity of the ebXML framework will be hidden from the
typical corporate end-user by easy-to-use software. Though Dave may be
referring to the ebXML Business Process (BP) schema and Core Components
specifications, the more relevant aspects of ebXML for HIPAA remain the
Messaging Services, CPP and Registry-Repository - at least while X12 EDI
is mandated.
I can envision a day when all you have to do is dump HIPAA standard X12
transactions and interchanges into a "funnel," and the messages will be
correctly, securely and safely routed to the intended recipients -
directly over the Internet. The recipient's DUNS, HIN, Tax ID,
national provider ID - or whatever - would be extracted from the ISA .
This unique ID could then be used for look-up in an ebXML
Registry-Repository via UDDI for obtaining the Collaboration-Protocol
Profile (CPP) whence addressing and certificates can be found.
After the HIPAA payload is encrypted, it would be wrapped up in the
ebXML Messaging Services packaging and sent on its way via HTTP or SMTP,
directly to the recipient or via an intermediary like a VAN or
Clearinghouse. And all without the mess or fuss of maintaining trading
partner profiles as you do today with EDIINT packages.
Of course, you have to consider that Dad was the one who predicted
everyone would have a picture phone back at the 1964 World's Fair. And
at the 1939 World's Fair, Grampa prognosticated World Peace and said
everyone would be flying around in helicopter cars by the 1970s.
Say, why wasn't there a "1989" World's Fair?
William J. Kammerer
FORESIGHT Corp.
4950 Blazer Pkwy.
Dublin, OH USA 43017-3305
+1 614 791-1600
Visit FORESIGHT Corp. at http://www.foresightcorp.com/
"accelerating time-to-trade"