Tags

2012 21CFR Part 11 Acrobat ADAM Balance bigfoot Biometrics Biostatistics Business Process Call CDISC centralised programming change clinical development Code communication computing environments Conference CSS define.pdf define.xml FDA FDA reviewer future of statistical programming GCP global teams Good Clinical Practice Good Programming Practice governance GPP Guidelines IE and Adobe combinations Intro learning culture m5 Macros management motivation Motivational Off-shoring Open Source OpenCDISC Otters Outsourcing owl Patient Centricity People Development PhUSE proc csr programmers Programming Programming Future Proprietary R RCT rdf regulatory Reporting Resourcing reviewer aids Risk SAS SAS Programming SDTM semantic web Social Media Software Specialise Specifications Standards Statistical Programmers Statistical Programming statistical programming languages Statistical Reporting statistics Submission submissions survival System Development Time Management TLFs TMF Trial Master File tv Validation virtual virtual programming virtual teams Work Life work life balance Working Groups

Linked In Icon Twitter Icon Facebook Icon

"In a clear presentation it gave a perfect insight into our struggle with SDTM and legacy data"

GSK

The content of this blog expresses opinions solely of the author and not necessarily those of their employer or PhUSE.

Specifications are everywhere. Datasets are specified, reports are specified, systems are specified and we all have to deal with the specifications. Often enough we have to create them on our own. But how to make good specifications? Less is more, but is it still enough? What level of detail will fit our requirements?
Pages: 1