Since 1986 - Covering the Fastest Computers in the World and the People Who Run Them

Language Flags

Tag: FDA

Cloud Sparking Rapid Evolution of Life Sciences R&D

Apr 6, 2011 |

Bruce Maches provides a thorough examination of the complexity and resource requirements of specialized life science applications and what the role (and challenges) will be as cloud continue to enter into the industry. Many life science companies are struggling to afford to internally build, implement, and support much of the required systems and infrastructure but as Maches argues, there are alternatives.

Planning for Validation of Cloud Based Applications

Sep 29, 2010 |

Any life science company looking to validate cloud based systems must adjust its system qualification process to properly prove to any auditor that the application in question is installed, operating correctly while also meeting the users requirements.”

Managing Clinical Trials in the Cloud

Aug 24, 2010 |

To support large scale clinical trials, life science CIOs must deal with the challenges of provisioning and supporting vital hardware and software infrastructure. While there are a number of applications for managing clinical trials many life science companies are looking to cloud based offerings to reduce complexity and cost.

Facilitating Drug R&D by Collaborating in the Cloud

Jun 7, 2010 |

Given the costs and high level of risk it is common for life science companies to work jointly on research efforts. Cloud-based tools are already making this possible while still adhering to the numerous compliance and security requirements from the FDA.

CRM in the Life Sciences: Why the Veeva Announcement Matters

May 11, 2010 |

With the recent FDA rulings governing how sales can interact with doctors, the importance of a CRM system to track the complex customer interactions has never been more critical.

Negotiating IT in the FDA Regulatory Environment

Apr 26, 2010 |

The FDA, like many other regulatory bodies does not issue standards; instead it provides guidelines on what must be done to be considered compliant but not on the execution of how it is accomplished.