Category Archives: Genetic Medicine

Oracle Siebel CRM is the base application behind Oracle’s Siebel CTMS.

Prepackaged OBIEE Applications does not have a module for Clinical Analytics and so there is a need to develop a complete custom OBI application in order to accomplish the requirements. This was untill Oracle has introduced Oracle Clinical Development Analytics (CDA) which is based on OBIEE+

Oracle CDA includes prebuilt data models, prebuilt Extract-Transform-Load programs sourcing from Oracle Clinical / Remote Data Capture and Oracle’s Siebel Clinical Trial Management System

Business Intelligence can be deployed in several Core functions

• Protocol Design and Study Start-Up
• Patient and Investigator Recruitment
• Clinical Trial Management
• Clinical Data Management
• Data Analysis
• Clinical Supplies
• Regulatory and Safety

Nonclinical Use of  Business Intelligence in Clinical Trial
There are a number of ways in which business intelligence as a technology platform can be used to support the pharmaceutical value chain. There is ample evidence to show how business intelligence has been used successfully in a number of areas including:

• Sales and Marketing
• Manufacturing
• Finance
• Human Resources
• Information Services
• Executive and Portfolio Management

Clinical Use  of  Business Intelligence in Clinical Trial
Within clinical research, the strongest use of technology is in pre-clinical research, clinical, statistical programming and supporting other groups such as:

• Data management (patient profiles)
• Medical writing
• Finance
• Project management
• Patient registries and post-marketing surveillance

Without CDA an OBIEE architect needs to understand CRM data model and also the actual business process flow of a CTMS application.It is observed that usually there is a customization to an extent of 25% on the CRM application.

Original Old Article on OBIEE for CTMS which was the only Business Intelligence solutions for Clinical trial management before Oracle announced CDA is Available at http://www.obieetalk.com

Requirements gathering sessions must be interactive with group of SME’s, Team of members from business, project sponsors to mitigate any risk of
slipping the time lines. It is recommended to plan for regular client reviews and approvals of every build to avoid any gaps in the expectations by the client .

At a high level the reporting requirements may include tracking budget and finance, clinical trials, activities, investigators,Initiations, enrollments, expiration’s, terminations. Cross dimensional hierarchies from Program to Protocol to Site to Subject is commonly desired.

Major dimension tables specific to CTMS includes Program, Protocol,Site,Subject, application, Investigator. Other common dimensions include Accounts, Contacts, Activities, Time, Geography,product, etc.

Here is a screen shot of a sample rpd for CTMS

one of the very few interesting article by Microsoft Engineers on Clinical Research Industry. Certainly interesting as it is written by none other than      Les Jordan-CTO, Life Sciences Industry Unit at Microsoft . Microsoft and IBM had much longer and deepr association with Lifescience/Healthcare/Bioinformatics industry than Oracle.

But I love to see microsoft grow beyond Sharepoint for Clinical Research and the BioIT alliance. Also love to ask microsoft what is the current status of some of those applications mentioned in the blog by Les, Especially the Microsoft Clinical Trial Initiation solution

Original article from microsoft website

Interesting how weeks become months when you’re writing and updating blogs.  This CTMS project certainly hasn’t gone away, but it did go on a bit of a hiatus while my “day job” intervened.  Enough excuses.  Mea Culpa.  On to the fun!

As we discussed in the previous post, the key to a clinical trials management system is thinking of it in terms of a project – after all, the people who run the clinical trial think of it in terms of a project, and it is measured in project management terms, so why not treat it that way from an architectural point of view?

A second and equally important “requirement” is one that we are increasingly seeing as an industry trend: having EDC (Electronic Data Capture) functionality and CTMS (Clinical Trials Management System) functionality in the same system, or at the very least having EDC and CTMS closely integrate and interoperate.

The clinical trials world of today is fairly fractured.  Think of all the different systems – often standalone systems – that are used by Life Science organizations:

• EDC – Electronic Data Capture
• CTMS – Clinical Trials Management Systems
• CLIP – Clinical Investigator Portals
• Project – Clinical Trials Project Management
• Analysis – OK, it’s SAS, but how do you get the data there?  What about real-time analytics?
• IRB & DSMB – Outside organizations with their own management systems, like a Click Commerce Research Compliance Automation solution?

What if you could have a system that gets close to doing all of that – or at least being able to manage all of it – through one interface?  How much would that save in training costs, integration costs, and implementation costs?

Well – that’s the vision.  Here’s how we pull it off:

1. Start with Microsoft Office SharePoint Server 2007 and SQL Server 2008 as the foundation to build upon.
2. As discussed in the last post, we’ll use Microsoft Office Project Server as a way to organize the information and provide us with a trial specific taxonomy, along with roll-up of reporting metrics.
3. To cover the EDC aspects, we’ll utilize Microsoft Office Forms Server 2007 – which is a web facing InfoPath solution – to handle data entry and front-ending the workflow for data checks, etc.

EDC forms in Forms Server can even handle digital signatures (with compliance and security being the subject of a future post) inside the InfoPath forms.  This has implications for those organizations that are involved with SAFE BioPharma (worth checking out).

The beauty of all of this is that it is all Web Service enabled, which means that you have easier integration mechanisms with existing analysis and EDC systems:

• SAS – With integration with .NET, SOAP, and Web Services.
• Medidata – We’ve demonstrated use of their Web Services API module that utilizes CDISC.
• Perceptive Informatics – At the DIA annual meeting a couple years ago, we did a demonstration using DataLabs (now Perceptive) and InfoPath integration, using Web Services and about 5 lines of code!
• EHR/EMR Integration – While it is still on the horizon, I think it is getting closer.  Check it out.

Resources to get you started:

• Configuring SharePoint for 21 CFR Part 11 Compliance
• Project Server and Office SharePoint Server 2007 Integration
• Project Server Architecture and Programmability
• InfoPath Forms Server Form Template Authoring
• Microsoft Clinical Trial Initiation solution

Finally – there are other organizations and software vendors that are thinking along these lines.  Check out the following solutions:

• A solution in place in the US Department of Veteran Affairs
• TENALEA – Trans European Network for Clinical Trials Services
• Transenda – An Office & Project based CTMS system
• StreamLogic – A Project Based CTMS system

Next up in this series:

• Using MOSS templates for maintaining Part 11 compliance
• Extranets & Identity Management
• Architecture Diagrams & Screen shots
• Validation and compliance

I had posted last month about the Pegasystem pharmacovigilance solution.

Pega Systems the industry leader in Business Process Management (BPM) software solutions, released a Pharmacovigilance case processing software.

Pega has experience in clinical trial space, specifically in Clinical Trial Management. The solution is designed for rapid deployment to quickly leverage existing adverse event processing rules and requirements and can produce specialized documentation to help ensure compliance in a validated environment.

I have not come across any new updates after that. But apparently Accenture  has acquired Knowledge Rules, Inc., a Philadelphia-based consulting company that focuses exclusively on implementing and integrating business solutions using Pegasystems’ Business Process Management (BPM) software.

Accenture has a very large Pharmacovigilance division serving several large pharmaceutical companies. It would not be very suprising if Accenture roles out the BPM software for their pharmacovigilance services.

I think that is a possibility because Accenture  has announced plans to use the applications for all its Fortune 500 customers.

I would predict that United Health Group could be one of those customers as they are an existing customer of Pega.

Speaking of which Pega sounds like an attractive target Oracle can acquire

Ok, so enough with the acronyms.....

I am going to read this article for the seventh time and get back to you this week.

Yes, Yes.....