But if the ISA is encrypted won't there be a problem with ... Kepa Zubeldia wrote:
> The ISA interchange is given to a transport mechanism that looks up the > DNS MX record for "acmepipe.alliedTPA.hipaa.net" and finds that there > are multiple routes, some through clearinghouses, another one direct, > and with different preference factors. This route and transport > discovery could be done through UDDI, LDAP, DNS/MX, or other method that > is easy to deploy today (that probably rules UDDI out for now). The > transport discovery mechanism could take care of digital certificates, > telephone numbers, login and password, etc. > > The trick is to keep separate the "address" in the ISA from the route > chosen by the transport layer, because the EDI translator may know the > address but probably does not know the route. > > Then, asthe file with the address in the ISA is delivered to the next > hop, each recipient is free to choose the most efficient route for them, > without even having to touch the ISA at all. This will facilitate the > transfer in between clearinghouses. > ----------- Joe McVerry American Coders Ltd. POBox 97462 Raleigh, NC 27624 USA 919.846.2014 (voice/fax) http://www.americancoders.com Home Of OBOE - an EDI and EDI/XML Translator and xBaseJ - xBase Database Engine For Java
