Linked In Icon Twitter Icon Facebook Icon

"likely to have an impact on my work in the near future"

Organon

With the new Phuse/FDA collaboration another project starts which will be open source (Working Group “Development of Standard Scripts for Analysis and Programming”). Will this project have a chance or are the barriers too high?
Personally I cannot understand discussions about creating standard programs or standard macros. I could only imagine very rare situations where standard programs will make more sense than standard macros.
At this stage in the game, I think we, as sponsors, have finally moved from “if we have to implement standards” to “how we should be implementing standards”. As it turns out, I think we can all agree that the latter is much more challenging. Standards such as CDASH, SDTM and ADaM are available for our implementation pleasure….along with a new set of challenges. Sponsors must take the data models and implementation guides and apply/integrate them into their own processes. Sounds easy enough, no?
People always talk about the “Standards Train.” Get on the standards train, have you missed the standards train?
For efficient working more and more supporting tools like SAS macro systems or graphical tools are bought or developed. But how "good" or "bad" a system is depends on the users. Will the system support the users in their work flow? Will it be more efficient than the established processes? Will the system get accepted? So how to make our users happy to support our systems?
Pages: 1