Rule #1: Maintain the document audit trail<\/h2>\n
An audit trail provides a chronological record of all changes or transactions within a given system or database. Like the audit trail of a bank record that documents the amount and timing of every deposit or withdrawal over time, online IRB review platforms (including Click IRB) record information every time a document is uploaded into a submission form and every time a response to a submission form question is provided (or changed). Maintaining this information is necessary because it documents the history of the submission and it allows the IRB to quickly and easily identify changes from one version of a submission or document to the next.<\/p>\n
While there is programming built into Click IRB that maintains the audit trail \u2018behind the scenes\u2019, the accuracy of that audit trail is only as accurate as the user\u2019s actions. To maintain an accurate audit trail of a document in Click IRB, users must correctly \u2018layer\u2019 revised versions of existing documents. This is done utilizing the \u2018Update\u2019 button adjacent to the existing document.<\/strong><\/p>\n Adding revised documents via the \u2018Add\u2019 option and deleting old versions does not maintain the audit trail; the \u2018Add\u2019 button should only<\/em> be used when adding new documents into the system, not<\/em> previously reviewed documents<\/strong>.<\/p>\n In other words, think of a Click IRB submission as a traditional paper filing cabinet. Each smart form in the submission is one of the drawers and each field on the form, including each document within a field, is a separate file folder in the drawer. In this scenario, the audit trail of a given field or document is maintained in their respective file folder. Every time a field or document is revised, the revised version is added to the field\u2019s\/document\u2019s respective file folder in front of (or on top of) the old version \u2013 this is the equivalent of using the \u2018Update\u2019 button to upload a revised version of a specific document. Whereas, filing a revised document in a brand new folder (hence breaking the audit trail) is the equivalent of using the \u2018Add\u2019 button.<\/p>\n When a document is uploaded into Click IRB, users are given the option to identify a file name.<\/p>\n The name identified in the field then pulls through to the submission form and, later (upon IRB approval) to the submission approval letter. The naming convention used to identify the document should allow reviewers (as well as any individuals that might view IRB approval letters \u2013 e.g., Study Monitors, Food & Drug Administration Inspectors) to quickly and easily identify the type and purpose of the document. This is particularly important when a submission includes a large number of documents (e.g., multiple consent documents and recruitment materials).<\/p>\n Naming conventions should be short (less than 25 characters) but descriptive, and consistent across document versions. For example:<\/p>\n <\/p>\n When no name is assigned to the document, which is often the case, Click IRB will default to the file name of the document. Consequently, study teams should be mindful of the naming convention recommendations above (i.e., consistent and short but descriptive) when they create and\/or modify study document files in their word processing software. In other words, when a document is created by a study team, if the name applied to the document file is appropriately named when the document is saved in MS Word, for example, the appropriate file name will pull into Click IRB automatically when\/if the document name field is left blank in Click IRB.<\/p>\n Similar to document names, Click IRB also gives users the option to identify an alphanumeric version number when a document is uploaded into the system.<\/p>\n A version date, version number or a combination of a version date and number may be entered. The version identified in the field also pulls through to the submission form and approval letter, as with the document name. When the field is left blank, Click IRB will automatically assign a version number each time a revised version of the document is uploaded.<\/p>\n Ideally, the version identified in Click IRB should be consistent with whatever version, if any, is identified in the document itself (e.g., in the document footer). This is particularly true for sponsored research; sponsors and monitors will often require that the approval letter identify the version of an approved document. However, the accuracy of the version that appears in the approval letter is only as accurate as what is entered into the system by the study team.<\/p>\n Ultimately, whichever version method is utilized \u2013 allowing Click IRB to create a default version or identifying a version date consistent with what is identified in the document itself \u2013 it should be consistently applied across all revisions or modifications throughout the life of the research. Inconsistent versioning will result in an unclear document history (e.g., if a protocol is versioned with a date in one insistence [28JAN2021] and a number in a second instance [v.1.4], based on the version formatting, there is no way to determine the chronology of the document).<\/p>\n","protected":false},"excerpt":{"rendered":" Institutional Review Boards (IRBs) conduct their reviews and make determinations based primarily on the documents provided by the study team within a submission (e.g., study protocol, consent documents, recruitment materials,…<\/p>\n","protected":false},"author":36,"featured_media":0,"parent":316,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-2946","page","type-page","status-publish","hentry"],"acf":[],"yoast_head":"\n![\"A](\"https:\/\/www.rochester.edu\/ohsp\/wp-content\/uploads\/2024\/01\/Click-IRB-Consent-form-Update-screenshot-1024x202.png\")
<\/p>\nRule #2: Use consistent, short, but descriptive file naming conventions<\/h2>\n
![\"The](\"https:\/\/www.rochester.edu\/ohsp\/wp-content\/uploads\/2024\/01\/Click-IRB-file-name-field-highlighted-300x227.png\")
<\/p>\n<\/p>\n
\n \nVersion 1<\/th>\n Version 2<\/th>\n<\/tr>\n<\/thead>\n \n Protocol.v1<\/td>\n Protocol.v2<\/td>\n<\/tr>\n \n STUDY1234_Protocol_v1<\/td>\n STUDY1234_Protocol_v2<\/td>\n<\/tr>\n \n Consent_CohortA_v1<\/td>\n Consent_CohortA_v2<\/td>\n<\/tr>\n \n 1234_Consent_05MAR2020<\/td>\n 1234_Consent_11FEB2021<\/td>\n<\/tr>\n<\/tbody>\n
\n <\/table>\n<\/div>\nRule #3: Use consistent versioning methods<\/h2>\n
![\"The](\"https:\/\/www.rochester.edu\/ohsp\/wp-content\/uploads\/2024\/01\/Click-IRB-version-number-field-highlighted-300x227.png\")
<\/p>\n