{"title":"How to get 10 pounds of data into a 5-pound can – using flyover technique In HTML output","authors":"Daniel K. Downing","doi":"10.1179/175709208X334669","DOIUrl":"https://doi.org/10.1179/175709208X334669","url":null,"abstract":"Abstract When delivering results today, it is more and more common that delivering the output to the screen will be a requirement. Without getting into issues of font size or page orientation, there is generally about one third less horizontal space to work with between a screen and a hardcopy document. However, there is an easy to use technique available that allows for the presentation of more data to the user without requiring them to scroll back and forth. This paper is a guide through the processes necessary to convert static hardcopy output from PROC PRINT to the more flexible PROC REPORT, use flyovers to present descriptive information, thereby reducing the screen real estate consumed, and to package it all in an HTML wrapper. In other words, a way of getting ten pounds of data into a five pound can.","PeriodicalId":253012,"journal":{"name":"Pharmaceutical Programming","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129928410","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Lessons learned: valuable (but hidden) SAS® details","authors":"Dante diTommaso, Benjamin Szilagyi","doi":"10.1179/175709208X334650","DOIUrl":"https://doi.org/10.1179/175709208X334650","url":null,"abstract":"Abstract Sometimes the simplest SAS® task can become unnecessarily complex. Often the complexity of SAS®, itself, is the cause. Crucial details are easily hidden among the thousands of pages of SAS® documentation, technical notes, release updates, etc. The authors demonstrate a collection of SAS® features and techniques that are not well known, somewhat counterintuitive or undocumented, but all are surprisingly useful once learned and mastered. Mysterious SAS® behavior that might have inspired ‘work-arounds’ should now become transparent. Topics include environment settings; system options; and operators, functions and statements from SAS Language®, Macro Language®, SCL® and SAS/Graph®. The authors intend, through this selective review of uncommon techniques, to inspire a general interest in leveraging the power and maximizing the efficiency of programming tools.","PeriodicalId":253012,"journal":{"name":"Pharmaceutical Programming","volume":"162 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127289792","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Workflow: defining, designing and building a programming process and version control system. Part I – history and background","authors":"G. Silva","doi":"10.1179/175709208X334605","DOIUrl":"https://doi.org/10.1179/175709208X334605","url":null,"abstract":"Abstract There are a number of papers discussing the need for version control in the development of programs in the pharmaceutical industry. From simple CVS or RCS command line interfaces to the more complex and graphical tools like Rational Rose, programmers are told: there is a system out there to version your software, so do it! This is an important step in software development, but it is not the ‘be all end all’ for programmers. Since the industry insists on a review (Quality Control or ‘QC’) step to ensure that the specifications of the statisticians are met by the code of the programmers, it makes sense to have that same system allow for the ‘flow’ of validated code from the programmer to the statistician to the production version of the code. This paper discusses the process that was originally used until the company purchased a version control system in 2001– a paper-based system – and the evolution of our workflow from this paper-based system, through a commercial application and into an internal...","PeriodicalId":253012,"journal":{"name":"Pharmaceutical Programming","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126115153","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"A \"Systematic Review\" of PhUSE What PhUSE users made available to the public after two years","authors":"A. Tinazzi","doi":"10.1179/175709208X334597","DOIUrl":"https://doi.org/10.1179/175709208X334597","url":null,"abstract":"So far PhUSE has been an exciting initiative. European Pharmaceutical Software Users now have a place where they can present and share their experience. In the first two PhUSE conferences (2005 and 2006) and in the current one (2007), 273 papers were presented (89 in the 2005, 85 in the 2006 and 99 in 2007) in the following areas: 51 posters 36 application and development 31 technical solutions 22 coder corners 18 coding solutions (2006 and 2007 stream) 17 Statistics & Pharmacokinetics 17 Tutorials","PeriodicalId":253012,"journal":{"name":"Pharmaceutical Programming","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125885447","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"A concept for define.xml generated in SAS","authors":"M. Kawohl, D. Spruck","doi":"10.1179/175709208X334641","DOIUrl":"https://doi.org/10.1179/175709208X334641","url":null,"abstract":"AbstractWhen submitting data to the FDA, a data definition file, describing the structure and contents of the data, is a mandatory deliverable. For data submitted in the CDISC SDTM format the define.xml as published by the CDISC define.xml team is the preferred type of a data definition file. Compared to define.pdf, the previous data definition file format, define.xml is more suitable for providing the different types of metadata required to adequately describe data in the SDTM format. An additional benefit of define.xml is its machine-readability. After Accovion successfully implemented an automated process for define.pdf in SAS®, building a SAS® based automation process for define.xml was the logical consequence. This paper illustrates the process chosen by Accovion to compile all the necessary metadata and build a define.xml as described in the CDISC Case Report Tabulation Data Definition Specification (define.xml) V1.0 Standard. And as this standard will evolve over the next years, it will briefly tou...","PeriodicalId":253012,"journal":{"name":"Pharmaceutical Programming","volume":"55 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121707757","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
S. Leslie, F. Gwadry-Sridhar, P. Thiebaud, B. Patel
{"title":"Calculating medication compliance, adherence and persistence in administrative pharmacy claims databases","authors":"S. Leslie, F. Gwadry-Sridhar, P. Thiebaud, B. Patel","doi":"10.1179/175709208X334614","DOIUrl":"https://doi.org/10.1179/175709208X334614","url":null,"abstract":"AbstractCompliance, adherence, and persistence are outcomes easily measured in pharmacy claims databases. However, these measures are used with differing taxonomies and the calculations are heterogeneous. The results can then lead to spurious interpretations. Therefore, the research community would benefit from a common set of definitions and methods to calculate compliance and persistence. This paper briefly explains the definitions of compliance and persistence based on the guidance from the Medication Compliance and Persistence Special Interest Group of ISPOR, the International Society for Pharmacoeconomics and Outcomes Research, and provides analytic methods that are congruent with the preferred terminology.","PeriodicalId":253012,"journal":{"name":"Pharmaceutical Programming","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130198119","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}