Download PDF
Kythera Chooses Veeva Vault to Manage Regulated Content Enterprise-wide and Shaves TMF Reconciliation Time by 40%
Technology Category
- Platform as a Service (PaaS) - Data Management Platforms
Applicable Industries
- Pharmaceuticals
Applicable Functions
- Product Research & Development
- Quality Assurance
Services
- Cloud Planning, Design & Implementation Services
The Challenge
Kythera, a clinical-stage biopharmaceutical company, was facing challenges in managing clinical documents and facilitating business processes for the development of its newest product candidate. The company had 26 studies already on file along with four active clinical studies, resulting in thousands of documents to share, manage, and store. Kythera had been using a patchwork of different document repositories and systems for each functional area, including a file share system for TMF documents and a SharePoint-based system that was difficult to access and use for internal collaborators and external partners. Multiple versions of documents changed hands with no reliable document accountability. The resulting errors slowed study processes and added risk. Exchanging documents by couriers internationally only added to the inefficiency. Kythera’s legacy system was also extremely difficult to manage and update. Without the luxury of a large internal IT team, Kythera required a turnkey system that integrated clinical, regulatory, and medical affairs document management and didn’t require dozens of staff to implement and maintain.
About The Customer
Kythera is a clinical-stage biopharmaceutical company focused on the discovery, development, and commercialization of novel prescription products for the aesthetic medicine market. The company’s objective is to develop prescription products using an approach that relies on the scientific rigor of biotechnology to address unmet needs in a rapidly growing market. Kythera’s initial focus is on facial aesthetics – the market’s largest segment. The company‘s drug for the reduction of sub-mental fat is currently in late-stage clinical development.
The Solution
Kythera chose Veeva’s Vault suite of cloud-based applications to connect its teams from clinical to commercial. Initially, Kythera rolled out Veeva Vault eTMF to manage all of its trial documents and support global collaboration between sponsors, CROs, sites, and investigators with its integrated Investigator Portal. Kythera is also leveraging Veeva Vault QualityDocs to establish a single source of truth for all quality documents, and Veeva Vault MedComms to simplify the global coordination of medical communications. Kythera has established Vault eTMF as its central hub for exchanging documents with CROs, investigator sites, and other clinical partners. Each exchange is tracked by Vault and available via real-time reports that provide visibility into trial status and TMF completeness. The resulting data also provides actionable insights that allow Kythera to proactively improve study processes.
Operational Impact
Quantitative Benefit
Related Case Studies.
Case Study
Case Study: Pfizer
Pfizer’s high-performance computing software and systems for worldwide research and development support large-scale data analysis, research projects, clinical analytics, and modeling. Pfizer’s computing services are used across the spectrum of research and development efforts, from the deep biological understanding of disease to the design of safe, efficacious therapeutic agents.
Case Study
Fusion Middleware Integration on Cloud for Pharma Major
Customer wanted a real-time, seamless, cloud based integration between the existing on premise and cloud based application using SOA technology on Oracle Fusion Middleware Platform, a Contingent Worker Solution to collect, track, manage and report information for on-boarding, maintenance and off-boarding of contingent workers using a streamlined and Integrated business process, and streamlining of integration to the back-end systems and multiple SaaS applications.
Case Study
Process Control System Support
In many automated production facilities, changes are made to SIMATIC PCS 7 projects on a daily basis, with individual processes often optimised by multiple workers due to shift changes. Documentation is key here, as this keeps workers informed about why a change was made. Furthermore, SIMATIC PCS 7 installations are generally used in locations where documentation is required for audits and certification. The ability to track changes between two software projects is not only an invaluable aid during shift changes, but also when searching for errors or optimising a PCS 7 installation. Every change made to the system is labour-intensive and time-consuming. Moreover, there is also the risk that errors may occur. If a change is saved in the project, then the old version is lost unless a backup copy was created in advance. If no backup was created, it will no longer be possible to return to the previous state if and when programming errors occur. Each backup denotes a version used by the SIMATIC PCS 7 system to operate an installation. To correctly interpret a version, information is required on WHO changed WHAT, WHERE, WHEN and WHY: - Who created the version/who is responsible for the version? - Who released the version? - What was changed in the version i.e. in which block or module of the SIMATIC PCS 7 installation were the changes made? - When was the version created? Is this the latest version or is there a more recent version? - Why were the changes made to the version? If they are part of a regular maintenance cycle, then is the aim to fix an error or to improve production processes? - Is this particular version also the version currently being used in production? The fact that SIMATIC PCS 7 projects use extremely large quantities of data complicates the situation even further, and it can take a long time to load and save information as a result. Without a sustainable strategy for operating a SIMATIC PCS 7 installation, searching for the right software version can become extremely time-consuming and the installation may run inefficiently as a result.
Case Study
Drug Maker Takes the Right Prescription
China Pharm decided to build a cloud-based platform to support the requirements of IT planning for the next five to ten years which includes a dynamic and scalable mail resource pool platform. The platform needed to have the following functions: all nodes support redundancy, ensuring service continuity and good user experience, simple and easy-to-use user interfaces for end users and administrators and good compatibility and supports smooth capacity expansion.
Case Study
ELI LILLY ADOPTS MICROMEDIA’S ALERT NOTIFICATION SYSTEM
Pharmaceutical production is subject to a strict set of enforced rules that must be adhered to and compliance to these standards is critically necessary. Due to the efforts of WIN 911’s strategic partner Micromedia, Lilly was able to adopt an alarm notification infrastructure that integrated smoothly with their existing workflows and emergency hardware and protocols. These raw energy sources enable the industrial process to function: electricity, WIN-911 Software | 4020 South Industrial Drive, Suite 120 | Austin, TX 78744 USA industrial steam, iced water, air mixtures of varying quality. Refrigeration towers, boilers and wastewater are monitored by ALERT. Eli Lilly identified 15000 potential variables, but limitations compelled them to chisel the variable list down to 300. This allowed all major alarms to be covered including pressure, discharge, quantity of waste water discharged,temperature, carbon dioxide content, oxygen & sulphur content, and the water’s pH.