Note the circumspect reference on the HIPAAlive Discussion List to what I presume is the WEDI/SNIP ID & Routing project's Healthcare CPP Registry.
William J. Kammerer Novannet, LLC. Columbus, US-OH 43221-3859 +1 (614) 487-0320 ----- Original Message ----- From: "Bruce T LeGrand" <[EMAIL PROTECTED]> To: "HIPAAlive Discussion List" <[EMAIL PROTECTED]> Sent: Friday, 28 June, 2002 10:43 AM Subject: [hipaalive] RE:RE:SECURITY -- New PKWare release has strong *** HIPAAlive! From Phoenix Health Systems/HIPAAdvisory.com *** <SNIP> Do you need a file compression program with encryption or an encryption program with file compression? <END> The answer to this is generic. It does not matter what an individual entity needs. It does matter what the whole varied conglomerate of the industry needs. And this need extends outside of the bounds of HIPAA. With that preface, I'd say we would need complete cross-architecture compatibility, especially if we are to attain the vision of the EDI enabled health care system I keep hearing about. In that scenario, any entity could discover the means to communicate with any other entity. Minimizing the potential for inconsistencies in the data flow would seem to be even more important than discovery. One happens once, the other continues for the duration of the relationship. Whether your product is encryption with supported compression, or compression with supported encryption, what is important is enabling the EDI exchange without demanding similar systems and architectures. discussions on this listserv therefore represent the views of the individual participants, and do not necessarily represent the views of the WEDI Board of Directors nor WEDI SNIP. If you wish to receive an official opinion, post your question to the WEDI SNIP Issues Database at http://snip.wedi.org/tracking/. Posting of advertisements or other commercial use of this listserv is specifically prohibited.
