From: RolandRB on 25 Jul 2010 13:41 My Spectre Clinical reporting system gets used mostly every working day by a CRO in Munich but they have not reported any bugs in any of the macros for more than six months (last bug reported was 24JAN2010). http://www.datasavantconsulting.com/roland/ The clinical reporting system is a good educational one. It is based on the old Glaxo Wellcome reporting system which was an amalgamation of the reporting macros from Glaxo and Wellcome when they merged. Those days sas code freely flowed from one company to another before the pharma companies got it into their heads that they were somehow software companies and started enforcing copyrights. You might have heard of PhUSE - an organisation for sharing software across the industry. Well, from what I have seen over more than ten years in the industry, there was a lot of "sharing" going on more than ten years ago that might be termed "illegal" now. Things worked better in those days and reporting systems were closer to each other. Just one small step from having a universal reporting system across the industry. These days, it is a mess of different methods. But my Spectre Clinical reporting system is a recreation of that old Glaxo and Wellcome reporting system that has been entirely rewritten and simplified in a form that I believe is more universal. I think the industry needs a universal reporting system to reduce costs and so make drugs more affordable to the public. I consider that I have the solution to that. My system is FREE to everyone. If you want a support contract with me then I will have to charge for it but certainly for ACADEMIC use then I have no interest in supporting it and it will be forever free. All the sas macros I have are public domain software (it is only my Graphical Patient Profiles software that I enforce copyright on). You can be assured that if your use of my software is for study only then I will never enforce copyright on it (nor can I if you read English law).
|
Pages: 1 Prev: Character date to date format in PROC SQL Next: sas problem. |