Clinical Sas Programmer
CurrentPerforming prime and parallel programming for Phase III and IV studies for an Overactive Bladder drug (OAB).Work is performed in UNIX environment using SAS V8 or V9 using batch and interactive SAS as well as via Pfizer's reporting system, CDARS. All work is saved in Pfizer standard directory structure and is checked into RCS for file management purposes. Value add datasets (VADs) are generated via Pfizer system (CDARS). The process requires an extraction from OC and then running CDARS macros to create the standard VAD. In this study many of the VADs are non standard. In those instances it has been largely my responsibility to validate the VADs by writing parallel QC programs. By working to a detailed specification I generate derived endpoint variables and values per Pfizer Data Standards. I also write LOCF and windowing code per Pfizer standards. If I am writing QC code a compare is performed. Whether it is a QC or Primary program data checks are performed using procs Freq and Mean, and sometimes Univariate, as well as special edit checks and reports as needed. TLGs are generated via the CDARS system but about half of the TLG's end up being non standard in this study. By working to detailed non standard specifications I may write the primary programs or I may perform validation by writing parallel QC programs. Procs Means, Freq, Report and SAS/Graph procedures are commonly used. Proc Logistic in conjunction with OCS is often used for regression analysis reports. Compare tools can be used to compare large listings. This requires formatting the QC output exactly to specification. All primary and QC work is documented in detail in a common project tracking file (LoT - List of Tables). QC results and corrective action is documented in the LoT along with many other details. I work closely with statisticians and fellow programmers as needed but I am mostly self sufficient in writing code if the statistical requirements are clearly defined.