Chris, Nothing is "automatic", but a provider that designates a clearinghouse as its delivery point would also designate the clearinghouse as its DNS server. A provider that has its own "server" acting as its own delivery point, would have to point its DNS server to the EDI server acting as a delivery point.
Same thing happens today with DNS and email. If I want to get my email to be hosted by my ISP for the domain "kepa.com" then my ISP will also host my DNS server and will point the MX record of the DNS server for kepa.com into the ISP's own mail server. If I want to have my own mail server, either my ISP hosts the DNS for kepa.com and points the MX record to my own mail server, or I host the DNS myself and point it to my own mail server. Since this infrastructure is already in place for MX records, we could as well use it for EDI also. Kepa Christopher J. Feahr, OD wrote: > Speaking of semantics, we should figure out a standard term for the DNS > model that Kepa has suggested. > > Anyway, in that model, if a "small provider" (also needs a definition!) > is able to send a claim (or anything) directly to a payor using the > health plan's "smart EDI address"... will this automatically mean that > the payor will be able to discover the address/route back to the > provider for 271s, 824s, etc.? (I assume that the 835 will require > special handling in a provider-payor agreement) > > Does the provider's EDI address automatically get entered into the "DNS > table" in this proposed model? > > -Chris > > Christopher J. Feahr, OD > http://visiondatastandard.org > [EMAIL PROTECTED] > Cell/Pager: 707-529-2268
