View source for Using the CTP EmailService Pipeline Stage

This article describes how to configure the CTP EmailService pipeline stage to send emails when studies are processed. The intended audience for this article is CTP administrators configuring pipelines for clinical trials.

The EmailService is a processor stage. For each DicomObject it receives, it stores the identifier of the study (StudyInstanceUID) and the time the object was encountered. If no object is encountered for a study after 10 minutes, the stage considers the study to be complete, and it then sends an email to the recipients identified in the stage's configuration element.

The EmailService is only capable of sending to SMTP email servers.

The recommended way to configure the EmailService into a pipeline is to use the Configuration editor in the Launcher program. 
See [[The CTP Launcher Configuration Editor]] for details.

Like all pipeline stages, the EmailService stage is configured by a single XML element in the config.xml file. The details of the element are described in the [[CTP-The_RSNA_Clinical_Trial_Processor#EmailService|main CTP article]] Although the Configuration Editor obviates the need to edit or even read the XML, the default XML element is shown below for reference: 

<pre>
<EmailService
    name="EmailService"
    class="org.rsna.ctp.stdstages.EmailService"
    root="roots/EmailService"
    script="scripts/EmailService.script"
    smtpServer=""
    username=""
    password=""
    to=""
    from=""
    cc=""
    subject=""
    includeModality="no"
    includePatientID="no"
    includePatientName="no"
    includeStudyDate="no"
    logSentEmails="no"
    quarantine="quarantines/EmailService"/>
</pre>

The emails sent by the stage contain the numbers of objects, series, and images in the study, plus any additional information specified by the <tt><b>include...</b></tt> attributes. 

The placement of the pipeline stage in the pipeline determines whether the additional information will be PHI. To be specific, if the object received has not been de-identified, either before receipt by the pipeline or by a preceding anonymizer in the pipeline itself, then the values included in the emails will be PHI. This may be appropriate in some circumstances, but care must be taken because the email transmission is not secure.

The emails are sent with the mime-type multipart-alternative, and include both plain text and HTML text parts.