That is how it should work. Also, you have a fairly good argument here against my idea of being lazy and using standard e-mail as the provider inbox (that is, it may be a bit hard to reliably check whether some notification is already there).
I think (in the fullness of time) we will end up writing a script that accepts RFC838 messages on standard input (that is, it can be run straight from sendmail, fetchmail etc.) and inserted them in the database depending on the format. The question is, what to do with unformatted e-mails. If the sender is a patient, we can match this to their identity.pk, and insert the e-mail text into med_doc, with a fake entry in lab_result (patient e-mails must be tracked, in some ways, that's more important than tracing path.) The problem is unformatted messages from other people (specialists etc.) They still need to be in the EMR, and still need to be tracked, my preference would be to put them in unmatched-results.
Before you ask, spam is a non-issue as we would turf all non-encrypted e-mail to "normal" inbox (as it shouldn't be used for clinical matters anyway)
Ian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
