When using X12.58 security services, authentication and encryption are done only at the Functional Group (GS/GE envelope) and Transaction Set (ST/SE envelope) levels - the ISA is kept in the clear so intermediaries know where to send the interchange. Note that X12.58 has NOT been addressed in HIPAA at all. If accepted by the payer's translator that would be great - but so far we can't assume either mandated use or acceptance of X12.58.
EDIINT, on the other hand, *does* encrypt the entire EDI Interchange - including the envelope headers (ISA/IEA) - when encryption security services are applied. Since the routing of the EDI Interchange is point-to-point through the Internet, and not via a VAN or Clearinghouse, the sender/receiver ids are not used in routing so no intermediaries (there are none!) need to see the ISA. By the time an EDIINT package encrypts the interchange, it has already gone through all the rigmarole Kepa proposes and has the final destination address available for the SMTP routing or HTTP post. William J. Kammerer Novannet, LLC. +1 (614) 487-0320 ----- Original Message ----- From: "joe mcverry" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, 31 January, 2002 01:06 PM Subject: Re: some history on email addresses and thoughts for a proposal 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
