What Makes a Good QC Programmer?

This paper is a discussion of the methods employed by Quality Control (QC) Programmers, when performing QC by means of independent SAS® programming, for the most effective identification and reporting of discrepancies between a SAS Programmer/Analyst (SPA) and QC program set of results, with a given program specification. The discussion concerns both comparing the output of a program, that is SAS data sets, tables, listings, or graphic output…

Design Considerations Used to Develop Clinical Reporting Software

Most drug development organizations have two basic needs.  The first need is to standardize the reporting and second, to streamline the reporting process. SAS-generated reports are a key component of most clinical study reports that are included in a regulatory submission.  The reporting of most clinical data is similar from study to study and therefore can be standardized.  This standardization creates an opportunity for SAS macro-driven reporting. 


A programmer’s life in the broadly collaborative, timeline driven world of clinical research requires the ability to handle a wide variety of situations. While it is (relatively) simple to find good materials to teach a programmer specific SAS skills such as ODS or macro processing, the most challenging issues programmers (and programming teams) often face are not a lack of technical skills but difficulty thriving in unfamiliar situations.

DataCeutics Project Management and Validation Services Expanded at a Leading Boston-based Biotechnology

It was announced today that DataCeutics will manage the validation and documentation of a Leading Boston-based Biotechnology Company’s Software Code Environment (SCE). DataCeutics was chosen to lead this validation of the new SCE over other vendors because of its deep knowledge of SAS, clinical reporting requirements, SAS, documentation standards and company-wide embrace of quality standards.