Dick Brooks wrote: So what's missing from this picture? All the nitty gritty details about how to conduct e-business with each of these companies. IMO, this is the real challenge; How to "automate" the trading partner setup process for such a large community. Perhaps this is the more important function to be performed by Kepa's "DNS repository concept".
This is exactly what I've been striving for - an automated approach (or at least as automated as possible) way for the providers to create TPAs with our TPAs, payers, employers, and even a couple of CHs. I asked Rachel a couple of weeks back about any existing X12 standards in this area, and she pointed me to the 838 draft transaction which I have been examining and mapping to the trading partner data elements in our transaction generator. It would need a pretty detailed IG, but if the 838 could be incorporated into the Kepa's addressing scheme, or even be a single entry (...edi.anthem.838...) in the name service, then all of the protocols and even routes, addresses, and methods for the various transactions could be discovered, and better yet, be automagically (with some intelligent programming) incorporated into the trading partner library. Just a thought... Dave Minch T&CS Project Manager John Muir / Mt. Diablo Health System Walnut Creek, CA (925) 941-2240
