On 7/24/2003 12:08 PM, JLM deftly typed out: >> I think the only way to implement encryption that provides >> an easy entry point is to host your own "message center" website where you >> can leave messages for the patient and where they can come retrieve said >> messages in a webmail format. The site can then use standard SSL encryption >> already supported by web browsers and the patient need not worry about any >> of the technical aspects. Of course, this is *much* more work for the >> doctor. > > Yes, I agree that is probably the best way to handle it. > > Another way that might work would be to have mail accounts for both doctor > and patients on a server that supports (i.e., requires) full SSL encryption > for both sending and receiving. These accounts would have to be on the same > server, such that messages sent from doctor to patient and vice-versa never > actually travel outside of the mail server via unencrypted protocols. > > I'm just thinking out loud here, so I could be mistaken in assuming that my > idea provides a comparable level of security. Even if it turns out that this > would work, it still would require substantial set-up time and effort. > > Any thoughts?
That would provide the same level of security, but would require that the patient be savvy enough to know whether they were using an SSL-capable email client and how to setup an additional email account in their software. As someone that does end-user support...that is a big deal. -Remo Del Bello -- "What is this talk of 'release'? Klingons do not make software 'releases'. Our software 'escapes' leaving a bloody trail of designers and quality assurance people in its wake." - 8th most commonly uttered Klingon programmer phrase -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
