Paper TT09 Using SAS to Send Bulk s With Attachments

Transcription

1 Paper TT09 Using SAS to Send Bulk s With Attachments Wenjie Wang, Pro Unlimited, Bridgewater, NJ Simon Lin, Merck Research Labs, Merck & Co., Inc., Rahway, NJ ABSTRACT In the business world, using s to communicate is a common practice, and more and more business communication relies on s. When you need to communicate your analysis results or data checking findings to numerous recipients on a regular basis, sending bulk s could be a daunting task. With the SAS DATA step combined with SAS Access Method, sending bulk s becomes a breeze. This paper presents an easy and automated approach to send out bulk s with attachments on a scheduled basis (e.g. Weekly, Monthly, etc) using SAS Access Method. SAS configuration and SAS programs will be discussed for the use of this capability. A hypothetical example on how to utilize the Access Method will be presented with detailed step-by-step procedures. The scripts can be modified as necessary to fit your business needs and some discussions on generalizing the script will be explored. This paper is targeted at an intermediate and advanced audience. SAS Version 8.2 or 9.1, Windows XP, Intermediate or Advanced Level Key Words: SAS, DATA step, FILENAME statement, Access Method. INTRODUCTION Sending out bulk s with attachments to multiple recipients on a regular basis from software such as Microsoft Outlook is not an easy task and it is error-prone, since you could easily attached the wrong file to a wrong recipient. With SAS s Access Method of FILENAME statement, you can automate the task with careful planning and simple implementation of SAS code. SAS ACCESS METHOD BASICS In order to use the access method, certain system options need to be configured. The following is the list of related system options: SYS, HOST, PORT, ID, and PW. The following are values that are supported by Access Method for system option SYS: MAPI: Messaging Application Program Interface (interface supported by Windows and Windows NT, which is used by Microsoft Exchange. MAPI is the default.)

2 VIM: Vendor Independent Mail such as Lotus or cc:mail. You can issue the following statement to find out the value for your system: proc options option= sys; The log: 6912 proc options option= sys; 6913 SAS (r) Proprietary Software Release 8.2 TS2M0 SYS=MAPI Used by Access Method and Send menu item to set the interface type with underlying system. NOTE: PROCEDURE OPTIONS used: real time 0.01 seconds cpu time 0.01 seconds Once you find out that your system supports the Access Method, then you can send out s from within a SAS session. To configure your system to send out automatically without being prompted, you can add the following to the SAS configuration file of SASV8.CFG or SASV9.CFG: -EMALSYS SYS VALUE - ID ID VALUE - PW YOURPASSWORD The following are some concrete examples of what goes into the configuration file for different system: For Microsoft Outlook: - SYS MAPI - ID Wenjie.wang@sanofi-aventis.com - PW password For Lotus Notes: - SYS VIM - ID "Stacy Li/X/PH/Novartis" - PW password SYNTAX: FILENAME fileref 'address' < -options>; where:

3 fileref is a valid fileref. is the device-type keyword that indicates that you want to use . 'address' is the valid destination address of the user you want to send mail to. You can specify 'nul' here, and then specify the destination addresses in the options. -options are options that specify the recipients address, subject, and cc recipients address and attachment files, also the system related option such as SYS, EMALID and EMALPW can be specified in here instead of SAS configuration file. You can also specify the -options in the FILE statement inside the DATA step. Options that you specify in the FILE statement override any corresponding options that you specified in the FILENAME statement. In your DATA step, after using the FILE statement to define your fileref as the output destination, use PUT statements to define the body of the message. In your PUT statement, you use directives to specify the message attributes. The following is the list of directives that will change your message attributes:!em_to! addresses!em_cc! addresses!em_subject! Subject!EM_ATTACH! filename.ext Here are the directives that perform actions:!em_send!: sends the message with the current attributes!em_abort!: aborts the current message.!em_newmsg!: clears all attributes of the current message that were set using PUT statement directives. EXAMPLES 1. This is an example to send out a very simple message with an attachment file using FILENAME options to show the usage: filename outmail "wenjie_wang@merck.com" subject="sales Report.doc" cc="simon_lin@merck.com" attach="c:\reports\sales Report.doc"; data _null_; file outmail; put 'Dear team,'; put 'Attached is the sales report for last quarter.';

4 put 'If you have any question, please feel free to call'; put 'Regards,'; put 'Wenjie'; Here is the log: 6934 filename outmail subject="sales Report.doc" attach="c:\reports\sales Report.doc"; 6938 data _null_; 6939 file outmail; 6940 put 'Dear team,'; 6941 put 'Attached is the sales report for last quarter.'; 6942 put 'If you have any question, please feel free to call'; put 'Regards,'; put 'Wenjie'; 6953 NOTE: The file OUTMAIL is: Access Device Message sent To: Cc: Subject: Sales Report.doc Attachments: c:\reports\sales Report.doc NOTE: 13 records were written to the file OUTMAIL. The minimum record length was 0. The maximum record length was 50. NOTE: DATA statement used: real time 3.13 seconds cpu time 0.16 seconds The following is the screen shot from Outlook:

5 2. Another example will show that you can use options in FILE statement to override the options in FILENAME statement. filename outmail data _null_; file outmail subject="sales Report" attach="c:\reports\sales Report.doc"; put 'Dear team,'; put 'Attached is the sales report for last quarter.'; put 'If you have any question, please feel free to call'; put 'Regards,'; put 'Wenjie';

6 Now the following screen shot showed that the option in FILE statement overrode the option in FILENAME statement. 3. A third example will show you how to use the directives in PUT statement: filename outmail ; data _null_; file outmail; PUT '!EM_TO! wenjie_wang@merck.com'; PUT '!EM_SUBJECT! Sales Report '; PUT '!EM_CC! simon_lin@merck.com'; PUT '!EM_ATTACH! c:\reports\sales Report.doc'; put 'Dear team,'; put 'Attached is the sales report for last quarter.'; put 'If you have any question, please feel free to call'; put 'Regards,';

7 put 'Wenjie'; Here is the screen shot: SAS ACCESS METHOD APPLICATION Now that we understand the Access Method basics, we can put them into good use. Think about it, if we only want send one or more files to multiple recipients, we might just do it through Outlook, but situation arises when we need to send out different file to different people based on some results on regular basis, doing so through Outlook is a pain and it is easy to attach the wrong file to the wrong person. With SAS Access Method and careful planning, we can automate the whole process. Let s use a hypothetical example. In a hospital, there are SOPs regarding Residents Notes Writing, which regulates that each attending resident physician needs to write a note for each admission with 24 hours; the notes could be written by his/her assistant or nurse. If he/she didn t write notes within 24 hours for certain admission(s) during the week, at the end of week, he/she will get an with an attachment which shows the admission case with lack of the notes or delayed notes. We can automate the whole

8 process as the e-management tool to increase the SOP compliance rate. We will use macros to accomplish these. In this hospital, the Data Management Department stores the notes file written by doctors and nurses, and patient admission files in Mainframe. The macro will have two parameters called FROM and TO, which denote the report period span, to extract data for the report period. The notes file will have the doctors or nurses employee identification number(ein), notes written time in the form of DDMONYYYY:HH:MM:SS, Admission CaseID, Patient ID and Patient Name; The admission file will have the Attending Physician s EIN, Admission CaseID, admission date and time in the form of DDMONYYYY:HH:MM:SS, and patient name, ward and room and bed information. A permanent dataset called EMP contains all employees information, such as EIN(Employee Identification Number), first name, last name, hire date, address, phone number, etc. The following macro shows the step-by-step implementation: %macro notes_report(from=, to=); %let today=%sysfunc(today(),date9.); /* capture report running date*/ %let from=%upcase(&from); %let to=%upcase(&to); %* Step 1: get the admission file and notes file *; filename admis "\\datam\admission\alladmission.dat"; data admission; informat admission_ dt datetime20.; infile admis LRECL=1024 pad missover; ; if "&from"d < = datepart(admiss ion_dt) <="&to"d then do; adm_ein adm_caseid ward $ room_bed $ patientid PatientName $ ; end; filename notefile "\\datam\notes\allnotes.dat"; data notes; informat notes_dt datetime20.; infile notefile LRECL=1024 pad missover; 31 if "&from"d <= datepart(notes_dt) <="&to"d+1 then do; notes_ein adm_caseid patientid PatientName $ ; end;

9 %* Step 2: merge the two files to get the admission case which lack *; %* notes or has delayed notes *; %* for each admission, there should have a note associated with it *; proc sort data=admission; by adm_caseid; proc sort data=notes; by adm_caseid; %* merge admission and notes to find the interval between the *; %* admission time and notes time, derive the value for variables: *; %* COMPLIANCE, NOTES, and DELAY *; data allnotes; merge admission(in=a) notes(in=b drop=patientid patientname); by adm_caseid; if a; if intck('hour',admission_dt, notes_dt)>24 then do; notes=1; compliance=0; delay=1; end; else if intck('hour',admission_dt, notes_dt)=. then do; notes=0; compliance=0; delay=.; end; else if.< intck('hour',admission_dt, notes_dt) <=24 then do; notes=1; compliance=1; delay=0; end; format admission_dt notes_dt datetime20.; %* subset the non compliance records *; data noncompli; set allnotes; where delay ne 0; %* Step 3: create a macro to generate a rtf file for each attending *; %* physician who did not write a notes or who had delayed *; %* notes, and in the mean time, populate the *; %* noncompli_ _list table for sending out later on*;

10 proc format; value delayf 1="Delayed Notes".="No Notes"; %macro update_noncompli_ _list( ein=, physician_name=, name=, _address=); filename nocompli "c:\resident supervision\non compliance \Admission_Audit_Report_for_&physician_name._Wkof&to..rtf"; ods listing close; ods rtf file=nocompli bodytitle; title1 "Admission Audit Report For the Week ending at &to. for &name"; title2 "The following is a list of admission which has no notes or delayed notes as of &today"; proc sql; select admission_dt label='admission Date/Time', patientid label='patient ID', patientname label='patient Name', ward label='ward', room_bed label='room and Bed', delay label='reason' format=delayf. from noncompli where adm_ein=&ein; quit; ods rtf close; ods listing; title; %*** Now populate the noncompli_ _list table ***; proc sql; insert into noncompli_ _list values (&ein, "&name", "& _address", "c:\resident supervision\non compliance\admission_audit_ Report_for_&physician_name._Wkof&to..rtf"); quit; %mend update_noncompli_ _list; %* Step 4: find out how many physician is not in compliance *; proc sort data=noncompli out=ein_list(keep=adm_ein rename=(adm_ein=ein)) nodupkey; by adm_ein;

11 proc sort data=data_a.emp out=emp; by ein; data noncompli_ein; merge emp(in=a) ein_list(in=b); by ein; if a and b; %* Step 5:Execute the macro %update_noncompli_ _list to populate*; %* dataset non_compli_ _list used for bulk sending*; proc sql; drop table noncompli_ _list; create table noncompli_ _list (ein num, emp_name char(60), _address char(60), attach_file char(200) ); quit; data _null_; set noncompli_ein; call execute('%update_noncompli_ _list(ein=' ein ', Physician_name=' compress(firstname) '_' compress(lastname) ', name=' compress(firstname) ' ' compress(lastname) ', _address=' compress( _address) ')'); %* Step 6: Send to each non-compliant physician with the *; %* corresponding attachment *; filename my ; data _null_; set noncompli_ _list; file my ; put '!EM_TO!' _address; put '!EM_SUBJECT! Admission Audit Report for ' emp_name; put "Dear Provider " emp_name ":" ;

12 put ; put ; put "According to the medical record, you are either the "; put "inpatient attending physician or the attending in "; put "charge of the ward for the patient(s) listed in the "; put "attached file. "; put "An attending admission note is required by policy "; put "within one calendar day from the time of admission, "; put "but could not be found for the patient(s) listed. "; put "Please place your attending note in system ASAP. "; put "If I am mistaken in contacting you, or the data "; put "included are incorrect in any way, "; put "please contact me by so that I can fix "; put "the problem immediately. "; put "Thank you for your attention. "; put '!EM_ATTACH! ' attach_file; put '!EM_SEND!'; put '!EM_NEWMSG!'; put '!EM_ABORT!'; %mend notes_report; To generate weekly report, just pass in the parameter value for from date and to date in the format of DATE9, this macro will do the rest. To further automate the procedure, you can put it in the Window s scheduler or use cron job in UNIX. CONCLUSION SAS Access Method combined with the powerful language of SAS can turn a lengthy repetitive administrative task into a quick and error-proof job. The macro demonstrated above was developed for specific business need, but it is very flexible to modify and easy to implement to fit your business need. REFFERENCES ---Base SAS Software ---Host Specific Information ---OS/2 Environment (Companion) --- Using Groupware to Distribute SAS Data

13 ACKNOWLEGEMENTS The authors would like to thank our management team for their encouragement and review of this paper. CONTACT INFORMATION Your comments and questions are valued and encouraged. Contact the authors at: Wenjie Wang Pro Unlimited Bridgwater, NJ (908) Simon Lin Merck & Co., Inc. RY34-A320 P.O. Box 2000 Rahway, NJ (732) TRADEMARKS SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. indicates USA registration.