Native Direct Messaging Implementation

yehster wrote on Tuesday, March 05, 2013:

Thanks to Louis Galterio for obtaining this document from his colleagues at HIMSS
https://docs.google.com/file/d/1fzTrXfKu84kXX4IHiaYbGBj7V-qWeDHxWtc9SGMqGZ62lL_i8xjLRvIFVpGa/edit?usp=sharing

The key point of this is that the minimum required implementation is
that the EHR must support SMTP.
My interpretation is that an acceptable scenario is to use an existing
SMTP server.
So, setup an email address setup for drbowen-secure@bowenmd.com.
When drbowen logs into OpenEMR, it connects to the SMTP server and
acts like an email client. (downloads the messages with POP or IMAP).
OpenEMR at this point would need to know how to process the S-MIME of
each of the messages it grabbed from the server and then present the
contents of the decoded messages.  The receiving end also has to
notify the sender upon delivery.

In order to generate the S-MIME message to send in the first place, I
need to get drbowen’s “public certificate” so I can encrypt the
message meant for him.  So the sender “gets the certificate” encrypts
the message using the certificate and sends an email with the
encrypted stuff as an attachment.