Talk:Good Programming Practice for Clinical Trials

From sasCommunity

Jump to: navigation, search

I would like to know others' opinions about the usefulness of this page.

Also, do you think this might ultimately become part of the GxP guidelines?

--Jmbodart 06:40, 1 October 2008 (EDT)

Note: This page is now ranked 972th in popularity after 1 week (87 views) according to Special:Popularpages.

--Jmbodart 10:50, 7 October 2008 (EDT)

Note: This page is now ranked 121st in popularity after <6 weeks (1,961 views) according to Special:Popularpages. No comments/ edits contributed so far.

--Jmbodart 04:58, 6 November 2008 (EST)

Contents

[edit] Added plans for endorsement of a Good Programming Practise by October 2009

I really do hope that many Pharmaceutical users have added this page on their watch list and that they will contribute. There is no reason why we should not have a Industry Good Programming Practice. As a colleague expressed at PharmaSUG: it would avoid having to go line by line through the Sponsor and Vendor Practices to detect differences.

--Ann Marie Martin 11 November 2008

[edit] Plan for Review of this Draft Guideline

I'm thinking of renaming this page into "Draft Good Programming for Clinical Trials for Public Review" in order to emphasize this is open to comments and suggestions to be posted on this discussion page.

In addition I would like to specify a Review Deadline e.g. end January 2009.

If you are interested to participate to the review of the comments and suggestions, or have any comment about this plan, please drop a note on this page.

--Jmbodart 03:53, 28 November 2008 (EST)

[edit] Russ Lavery's comment after the PhUSE 2008 - Manchester, UK (e-mail sent: Tuesday, October 21, 2008)

Image:RussLaveryCodingSuggestions PhuseV2.pdf 

  Ann Marie 

  We talked for a moment after your panel discussion. 

  I found your programming practices document on the web and liked it a lot. 
  It is much better looking than mine. 

  Here is what I have developed and I offer it as a comment to what is on the web. 
  Feel free to use anything you like. 

  Russ Lavery

[edit] Code for viewlog macro

The text refers to a macro "viewlog" which is not described

--MichelBourgois 10 December 2008

The "viewlog" macro used at UCB scans a log file and creates an ODS HTML summary with the number of occurences of each search string, such as: fatal#error#warning#uninitialized#MERGE statement has more than one data set with repeats of BY values#Note: Missing etc...

It also list the lines containing these search strings (color-coded) together with hyperlinks to the original lines in an HTML copy of the full log. This allows to view the error, warning etc (also color-coded) in full context.

--Jmbodart 09:54, 10 December 2008 (EST)

Retrieved from "http://www.sascommunity.org/wiki/Talk:Good_Programming_Practice_for_Clinical_Trials"
Personal tools
Page Activity