{"id":2533,"date":"2015-05-18T13:24:32","date_gmt":"2015-05-18T13:24:32","guid":{"rendered":"http:\/\/www.staging-protocolbuilderpro.kinsta.cloud\/?p=2533"},"modified":"2022-01-13T14:31:25","modified_gmt":"2022-01-13T14:31:25","slug":"common-protocol-development-errors-part-three","status":"publish","type":"post","link":"https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/","title":{"rendered":"Common Protocol Development Errors (Part Three)"},"content":{"rendered":"<div class=\"wpb-content-wrapper\"><p>[vc_row css_animation=&#8221;&#8221; row_type=&#8221;row&#8221; use_row_as_full_screen_section=&#8221;no&#8221; type=&#8221;full_width&#8221; angled_section=&#8221;no&#8221; text_align=&#8221;left&#8221; background_image_as_pattern=&#8221;without_pattern&#8221;][vc_column][vc_empty_space height=&#8221;12px&#8221;][vc_column_text]In the last of this three-part series, we explore common types of information or documentation that may be inconsistent in investigator-initiated protocol submissions to an IRB.<\/p>\n<p>It is a common sentiment among clinical investigators that the process of developing and submitting a human subject research protocol for review and approval by an IRB is onerous, lengthy and complicated. For researchers writing investigated-initiated research, the process may seem like a labyrinth of regulatory and institutional requirements. Generally speaking, most IRB submission errors fall into these categories:<\/p>\n<ul>\n<li>Incomplete submission<\/li>\n<li>Missing documentation<\/li>\n<li>Inconsistent information<\/li>\n<\/ul>\n<p><b>Inconsistent Information<\/b><\/p>\n<p>An IRB submission often requires the same information in multiple locations. Sometimes the study protocol or application contains information that is not consistent from one section of the submission to another. The most common inconsistencies include:<\/p>\n<ul>\n<li>Number of participants to be recruited<\/li>\n<li>Frequency or number of participant visits in the study<\/li>\n<li>Amount that participants will be paid and schedule for payment<\/li>\n<li>Type and frequency of procedures<\/li>\n<li>Specific data that will be collected<\/li>\n<\/ul>\n<p><b>Interchangeable Terminology<\/b><\/p>\n<p>Certain words, including \u201canonymous\u201d and \u201cconfidential\u201d are often used interchangeably when they actually mean different things. <i>Anonymous<\/i> means that there is no link between the participants and the data they provide. <i>Confidential<\/i> means that there <i>is<\/i> a link between participants and the data they provide, but the link will be unknown to everyone except the researchers and parties specified during the consent process.<\/p>\n<p><b>Misaligned Objectives and Endpoints<\/b><\/p>\n<p>In some cases, a researcher with a well-defined research question and clearly stated study objectives may not follow through to reveal adequate endpoints.<\/p>\n<p>Endpoints are the main way that the results of a trial will be assessed. They should be decided in the study design before any patients are enrolled.<\/p>\n<p>For example, perhaps a physician uses a treatment off-label regularly in clinical care, and now wants to conduct a research study to gather data to support the treatment\u2019s use. The researcher provides a protocol that contains detailed procedures, but doesn\u2019t include the plan for assessing the results and determining whether the endpoint is achieved.<\/p>\n<p>An effective clinical trial design results in the reduction of errors and bias. It also provides a high degree of credibility, reproducibility and validity. Having a clear, complete and simple protocol design allows investigators to advance clinical research while protecting human subjects.[\/vc_column_text][\/vc_column][\/vc_row]<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>In the last of this three-part series, we explore common types of information or documentation that may be inconsistent in investigator-initiated protocol submissions to an IRB.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[37],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v22.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Common Protocol Development Errors (Part Three) - Protocol Builder<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Common Protocol Development Errors (Part Three) - Protocol Builder\" \/>\n<meta property=\"og:description\" content=\"In the last of this three-part series, we explore common types of information or documentation that may be inconsistent in investigator-initiated protocol submissions to an IRB.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/\" \/>\n<meta property=\"og:site_name\" content=\"Protocol Builder\" \/>\n<meta property=\"article:published_time\" content=\"2015-05-18T13:24:32+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-01-13T14:31:25+00:00\" \/>\n<meta name=\"author\" content=\"Protocol Builder\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Protocol Builder\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/\",\"url\":\"https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/\",\"name\":\"Common Protocol Development Errors (Part Three) - Protocol Builder\",\"isPartOf\":{\"@id\":\"https:\/\/protocolbuilderpro.com\/#website\"},\"datePublished\":\"2015-05-18T13:24:32+00:00\",\"dateModified\":\"2022-01-13T14:31:25+00:00\",\"author\":{\"@id\":\"https:\/\/protocolbuilderpro.com\/#\/schema\/person\/2050616038a7227c3168a743446f9cca\"},\"breadcrumb\":{\"@id\":\"https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/protocolbuilderpro.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Protocol Development Errors (Part Three)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/protocolbuilderpro.com\/#website\",\"url\":\"https:\/\/protocolbuilderpro.com\/\",\"name\":\"Protocol Builder\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/protocolbuilderpro.com\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/protocolbuilderpro.com\/#\/schema\/person\/2050616038a7227c3168a743446f9cca\",\"name\":\"Protocol Builder\",\"url\":\"https:\/\/protocolbuilderpro.com\/author\/protocol-builder\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Common Protocol Development Errors (Part Three) - Protocol Builder","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/","og_locale":"en_US","og_type":"article","og_title":"Common Protocol Development Errors (Part Three) - Protocol Builder","og_description":"In the last of this three-part series, we explore common types of information or documentation that may be inconsistent in investigator-initiated protocol submissions to an IRB.","og_url":"https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/","og_site_name":"Protocol Builder","article_published_time":"2015-05-18T13:24:32+00:00","article_modified_time":"2022-01-13T14:31:25+00:00","author":"Protocol Builder","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Protocol Builder","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/","url":"https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/","name":"Common Protocol Development Errors (Part Three) - Protocol Builder","isPartOf":{"@id":"https:\/\/protocolbuilderpro.com\/#website"},"datePublished":"2015-05-18T13:24:32+00:00","dateModified":"2022-01-13T14:31:25+00:00","author":{"@id":"https:\/\/protocolbuilderpro.com\/#\/schema\/person\/2050616038a7227c3168a743446f9cca"},"breadcrumb":{"@id":"https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/protocolbuilderpro.com\/common-protocol-development-errors-part-three\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/protocolbuilderpro.com\/"},{"@type":"ListItem","position":2,"name":"Common Protocol Development Errors (Part Three)"}]},{"@type":"WebSite","@id":"https:\/\/protocolbuilderpro.com\/#website","url":"https:\/\/protocolbuilderpro.com\/","name":"Protocol Builder","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/protocolbuilderpro.com\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/protocolbuilderpro.com\/#\/schema\/person\/2050616038a7227c3168a743446f9cca","name":"Protocol Builder","url":"https:\/\/protocolbuilderpro.com\/author\/protocol-builder\/"}]}},"_links":{"self":[{"href":"https:\/\/protocolbuilderpro.com\/wp-json\/wp\/v2\/posts\/2533"}],"collection":[{"href":"https:\/\/protocolbuilderpro.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/protocolbuilderpro.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/protocolbuilderpro.com\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/protocolbuilderpro.com\/wp-json\/wp\/v2\/comments?post=2533"}],"version-history":[{"count":8,"href":"https:\/\/protocolbuilderpro.com\/wp-json\/wp\/v2\/posts\/2533\/revisions"}],"predecessor-version":[{"id":5048,"href":"https:\/\/protocolbuilderpro.com\/wp-json\/wp\/v2\/posts\/2533\/revisions\/5048"}],"wp:attachment":[{"href":"https:\/\/protocolbuilderpro.com\/wp-json\/wp\/v2\/media?parent=2533"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/protocolbuilderpro.com\/wp-json\/wp\/v2\/categories?post=2533"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/protocolbuilderpro.com\/wp-json\/wp\/v2\/tags?post=2533"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}