{"id":596,"date":"2018-05-01T16:27:06","date_gmt":"2018-05-01T21:27:06","guid":{"rendered":"http:\/\/waife.com\/home\/?p=596"},"modified":"2018-05-05T16:31:43","modified_gmt":"2018-05-05T21:31:43","slug":"is-information-technology-always-the-solution-for-clinical-research-problems","status":"publish","type":"post","link":"http:\/\/waife.com\/home\/is-information-technology-always-the-solution-for-clinical-research-problems\/","title":{"rendered":"Is information technology always the solution for clinical research problems?"},"content":{"rendered":"<p><u><\/u>After decades of dragging its feet, the biopharma clinical development world is finally embracing the adoption of information technology in support of clinical development. The industry as a whole has overcome the problems of operating in a regulated environment, fear of change, inadequate budgeting and unclear software governance.<\/p>\n<p>Whst is ironic now is how far to the other end the pendulum has swung, in the acceptance and reliance on technology as the solution to most any clinical development operations problem.\u00a0Do any of the following sound familiar?<\/p>\n<ul>\n<li><span style=\"color: #000000;\"><strong>Problem<\/strong>: We should be doing more vendor oversight.<\/span><\/li>\n<li><span style=\"color: #000000;\"><strong>Solution<\/strong>: Let\u2019s get a new CTMS system.<\/span><\/li>\n<\/ul>\n<ul>\n<li><span style=\"color: #000000;\"><strong>Problem<\/strong>: We should be doing Risk Based Monitoring.<\/span><\/li>\n<li><span style=\"color: #000000;\"><strong>Solution<\/strong>: Let\u2019s get RBM software<strong>.<\/strong><\/span><\/li>\n<\/ul>\n<ul>\n<li><span style=\"color: #000000;\"><strong>Problem<\/strong>: We should be collecting more real-time personalized patient data.<\/span><\/li>\n<li><span style=\"color: #000000;\"><strong>Solution<\/strong>: Let\u2019s implement mHealth.<\/span><\/li>\n<\/ul>\n<p>While the implementation of these tools can be part of a solution to the operational issues we have, they do not represent the entirety of the solution \u2013 and that is precisely where the frustration with technology stems from. Users and executives alike have the unrealistic expectation that the tool itself will solve the problem.\u00a0 But in reality, it is the way you adapt to and use the tool that is the primary factor in achieving a solution. Indeed, implementing a new software application may not be the most important step you need to take.<\/p>\n<p>Most sports activities provide a telling analogy, where in any given competition, the athletes by and large all use the exact same equipment.\u00a0 In tennis, most players use the exact same racquet.\u00a0 In baseball, there is very little difference between the bats, gloves, and shoes worn.\u00a0 The same goes for hockey, basketball, skiing. Indeed in basketball everyone <strong><em>has<\/em><\/strong>to use the same ball.<\/p>\n<p>The equipment itself has progressed over the years, which gives athletes today an edge compared to previous generations. \u00a0For example, you would be hard-pressed to find any professional tennis player using a wooden racquet today.\u00a0 But why are some athletes more successful than others? It is definitely not the equipment.\u00a0 I can go out and buy the exact same racquet as Rafael Nadal or Roger Federer, but that will not allow me play tennis at their level.\u00a0 Their success is a combination of raw talent, practice, determination, conditioning and, yes, taking advantage of the technology (their racquets) to complement their game, by leveraging that technology to highlight their strengths and minimize their weaknesses.<\/p>\n<p>And you do see even top athletes change equipment when things are going bad for them. Very rarely does this make a difference in their performance. Their performance improves when they have correctly diagnosed the technique, attitude and skill deficiencies applied to using the tools.<\/p>\n<p>This same example holds for biopharma and the use of information technology.\u00a0 Many biopharmas use the same piece of technology (or very similar technology) for data collection, a CTMS, safety reporting, an eTMF, etc., and yet some companies (or projects within companies) are more successful in clinical development than others.\u00a0 Like sports, the spectrum of success and optimization lies in how the organizations use those tools.\u00a0 Are they taking full advantage of the functionality that supports their goals?\u00a0Have they adapted the tool to fit within their organization?\u00a0 Have they defined their processes to limit duplication of effort and optimize workflows?\u00a0Technology provides the means to help us get there more easily and efficiently, but it will not get us there on its own. It\u2019s the environment around the technology which is the key to solving the operational issues that confront us every day.<\/p>\n<p>Another obstacle biopharma tends to trip over is a reliance on the developer of the information technology to provide guidance on how to use it.\u00a0 This is not fair to the developer nor is it fair to ourselves.\u00a0 Technology vendors are, for the most part, technology specialists, by definition.\u00a0 They are not clinical research and development specialists, and don\u2019t market themselves as such. So, why do we ask them for help in using their tools when the questions we ask are fundamentally operational, and not technological?\u00a0 Most vendors will, of course, be happy to try and help you, as it is their system you are using and they have a vested interest in ensuring your satisfaction, but this relationship often ends badly and unnecessarily so. Our sports analogy teaches us again: Roger Federer does not enlist someone from Wilson to be his coach nor does Tiger Woods ask someone at Nike to help him work out his drive and short game.\u00a0 Instead, such professionals enlist the help of specialists who are experts in the sport they are playing so that they can get the advice they need to win.<\/p>\n<p>When confronted with your next clinical development operational issue, think back to the analogies from other industries and by all means buy, enlist, or lease the appropriate information technology that will help you address the problem. \u00a0But if you want to be successful, be sure to devote enough time, attention and money to defining how to optimally use that technology within your individual organizations.<\/p>\n<p>For the arrow to hit the target, the archer has to be the one to get it there.<\/p>\n<p>For further discussion or assistance on this topic, reach out to Waife &amp; Associates, Inc. at\u00a0<a href=\"http:\/\/www.waife.com\/\">www.waife.com<\/a>, or email me directly at\u00a0<a href=\"mailto:shevel@waife.com\">shevel@waife.com<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>After decades of dragging its feet, the biopharma clinical development world is finally embracing the adoption of information technology in support of clinical development. The industry as a whole has overcome the problems of operating in a regulated environment, fear of change, inadequate budgeting and unclear software governance. Whst is ironic now is how far to the other end the pendulum has swung, in the acceptance and reliance on technology as the solution to most any clinical development operations problem.\u00a0Do any of the following sound familiar? Problem: We should be doing more vendor oversight. Solution: Let\u2019s get a new CTMS system. Problem: We should be doing Risk Based Monitoring. Solution: Let\u2019s get RBM software. Problem: We should be collecting more real-time personalized patient data. Solution: Let\u2019s implement mHealth. While the implementation of these tools can be part of a solution to the operational issues we have, they do not represent the entirety of the solution \u2013 and that is precisely where the frustration with technology stems from. Users and executives alike have the unrealistic expectation that the tool itself will solve the problem.\u00a0 But in reality, it is the way you adapt to and use the tool that is the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[50,4,54],"tags":[],"class_list":["post-596","post","type-post","status-publish","format-standard","hentry","category-recent-columns","category-recent-news","category-recent-postings"],"_links":{"self":[{"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/posts\/596","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/comments?post=596"}],"version-history":[{"count":2,"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/posts\/596\/revisions"}],"predecessor-version":[{"id":598,"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/posts\/596\/revisions\/598"}],"wp:attachment":[{"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/media?parent=596"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/categories?post=596"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/tags?post=596"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}