CINXE.COM
400-25: OnCore Utilization and APeX Billing Review for Clinical Trials | Campus Administrative Policies
<!DOCTYPE html> <html lang="en" dir="ltr"> <head> <meta charset="utf-8" /> <script async src="https://www.googletagmanager.com/gtag/js?id=UA-1557428-4"></script> <script>window.dataLayer = window.dataLayer || [];function gtag(){dataLayer.push(arguments)};gtag("js", new Date());gtag("set", "developer_id.dMDhkMT", true);gtag("config", "UA-1557428-4", {"groups":"default","anonymize_ip":true,"page_placeholder":"PLACEHOLDER_page_path"});</script> <meta name="Generator" content="Drupal 10 (https://www.drupal.org)" /> <meta name="MobileOptimized" content="width" /> <meta name="HandheldFriendly" content="true" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <link rel="icon" href="/themes/custom/echo/favicon.ico" type="image/vnd.microsoft.icon" /> <link rel="canonical" href="https://policies.ucsf.edu/policy/400-25" /> <link rel="shortlink" href="https://policies.ucsf.edu/node/1491" /> <title>400-25: OnCore Utilization and APeX Billing Review for Clinical Trials | Campus Administrative Policies </title> <link rel="stylesheet" media="all" href="/sites/policies.ucsf.edu/files/css/css_Rajt4_YRQrYvR2MIxCMN_sUteacsI7yJVq5AjzfHLgQ.css?delta=0&language=en&theme=echo&include=eJxljlEOAiEQQy9E4EhkFhoWHRgyA27W02v0Q6M_TfuaNCUzzFj7BWmKhmTmRTMUOXK16ei_H8I1VVicB-hqrogURqROfM6aLPwCZ6dNtLCRwSHt8uUazKjA3qmwbMQuiSJ00UZc73C3isPCS32TvBhukFJRGruFrGsQ-w_xq4-1Pd_vyO_ZLhkP7r9bHQ" /> <link rel="stylesheet" media="all" href="/sites/policies.ucsf.edu/files/css/css__w7sDDiRyjWCJbddL89wyQcxCsvqmisFtsmMRlMtl_0.css?delta=1&language=en&theme=echo&include=eJxljlEOAiEQQy9E4EhkFhoWHRgyA27W02v0Q6M_TfuaNCUzzFj7BWmKhmTmRTMUOXK16ei_H8I1VVicB-hqrogURqROfM6aLPwCZ6dNtLCRwSHt8uUazKjA3qmwbMQuiSJ00UZc73C3isPCS32TvBhukFJRGruFrGsQ-w_xq4-1Pd_vyO_ZLhkP7r9bHQ" /> <link rel="stylesheet" media="all" href="/sites/policies.ucsf.edu/files/css/css_fFrhmlZnn6E9v7vV61mIYCTucHZ5S90imq_4Qhm3_zk.css?delta=2&language=en&theme=echo&include=eJxljlEOAiEQQy9E4EhkFhoWHRgyA27W02v0Q6M_TfuaNCUzzFj7BWmKhmTmRTMUOXK16ei_H8I1VVicB-hqrogURqROfM6aLPwCZ6dNtLCRwSHt8uUazKjA3qmwbMQuiSJ00UZc73C3isPCS32TvBhukFJRGruFrGsQ-w_xq4-1Pd_vyO_ZLhkP7r9bHQ" /> </head> <body class="path-node page-node-type-knowledge-base"> <a href="#main-content" class="visually-hidden focusable skip-link"> Skip to main content </a> <div class="dialog-off-canvas-main-canvas" data-off-canvas-main-canvas> <div class="layout-container"> <header class="header" data-search-and-menu-visibility> <nav aria-label="UCSF" class="universal-header"> <a href="https://www.ucsf.edu">University of California San Francisco</a> <a href="https://giving.ucsf.edu" class="universal-header__give">Give to UCSF</a> </nav> <section class="navbar"> <div id="block-echo-branding" class="block block-system block-system-branding-block"> <a href="/" rel="home" id="logo" title="Campus Administrative Policies homepage" class="navbar__logo"> <img src="/themes/custom/echo/images/logos/policies-logo.svg" alt="Campus Administrative Policies homepage" height="53" width="189"/> </a> </div> <nav aria-label="Main" id="block-echo-main-menu" class="block block-menu menu--main"> <ul class="menu menu--level-1"> <li class="menu__item menu__item--level-1 menu__item--has-children"> <button class="menu__link menu__link--button menu__link--level-1 menu__link--has-children" aria-controls="policies-submenu-1" aria-expanded="false" aria-label="Open/Close Policies submenu" type="button">Policies</button> <ul class="menu menu--level-2" id="policies-submenu-1"> <li class="menu__item menu__item--level-2"> <a href="/policy" class="menu__link menu__link--link menu__link--level-2">Policies Home</a> </li> <li class="menu__item menu__item--level-2"> <a href="/policy/all-campus-administrative-policies" class="menu__link menu__link--link menu__link--level-2" data-drupal-link-system-path="policy/all-campus-administrative-policies">All Policies</a> </li> <li class="menu__item menu__item--level-2"> <a href="/policy/subject-areas" class="menu__link menu__link--link menu__link--level-2" data-drupal-link-system-path="policy/subject-areas">Subject Areas</a> </li> <li class="menu__item menu__item--level-2"> <a href="/search" class="menu__link menu__link--link menu__link--level-2" data-drupal-link-system-path="search">Policies Search</a> </li> </ul> </li> <li class="menu__item menu__item--level-1"> <a href="/policy-tools" class="menu__link menu__link--link menu__link--level-1" data-drupal-link-system-path="node/1451">Policy Tools</a> </li> <li class="menu__item menu__item--level-1"> <a href="/related-resources" class="menu__link menu__link--link menu__link--level-1" data-drupal-link-system-path="node/1446">Related Resources</a> </li> <li class="menu__item menu__item--level-1"> <a href="/updates" class="menu__link menu__link--link menu__link--level-1" data-drupal-link-system-path="node/1481">Updates</a> </li> <li class="menu__item menu__item--level-1"> <a href="/contact" class="menu__link menu__link--link menu__link--level-1">Contact Us</a> </li> </ul> </nav> <div id="global-search-dropdown" class="search--header"> <button class="search-icon" aria-controls="global-search-dropdown-form" aria-expanded=false> Search </button> <div class="search__dropdown"> <form id="global-search-dropdown-form" action="/search" accept-charset="utf-8" method="get" autocomplete="off" class="search"> <label for="header-search-input" class="visually-hidden">Search</label> <input id="header-search-input" type="text" name="search" value="" placeholder=Search... class="search__input"> <div class="focus-outline"> <input type="submit" value="Search" class="search__submit"> </div> </form> </div> </div> <button class="nav-toggle nav-toggle--active btn-alt-inverted" aria-controls="block-echo-main-menu" aria-expanded=false aria-label="Toggle Menu"> Menu <span class="nav-toggle__icon"></span> </button> </section> </header> <main class="l-container"> <a id="main-content" tabindex="-1"></a> <div id="block-echo-breadcrumbs" class="block block-system block-system-breadcrumb-block"> <nav class="l-container-breakout breadcrumb-wrapper" aria-label="Page location"> <ol class="breadcrumb l-container" id='top-breadcrumb'> <li class="breadcrumb-item"> <a href="/">Home</a> </li> <li class="breadcrumb-item"> <a href="/policy">Policies</a> </li> <li class="breadcrumb-item"> 400-25: OnCore Utilization and APeX Billing Review For Clinical Trials </li> </ol> </nav> </div> <div class="layout-content"> <div data-drupal-messages-fallback class="hidden"></div> <div id="block-echo-page-title" class="block block-core block-page-title-block"> <div class="node-owner-group"> <h1 class="page-title"> 400-25: OnCore Utilization and APeX Billing Review for Clinical Trials </h1> <p class="node-owner-group__info"> <span class="node-owner-group__subheading">Questions?</span> <span class="node-owner-group__link">Contact <a href="/contact">Campus Administrative Policies</a><span> </p> </div> </div> <div id="block-echo-content" class="block block-system block-system-main-block"> <article class="node node--type-knowledge-base node--view-mode-full knowledge-base"> <div class="l-basic l-container-offset "> <nav class="l-sidebar knowledge-base__sidebar" aria-label="Table of contents"> <input type="checkbox" id="check"> <label for="check" class="box-shadow knowledge-base__mobile-overview-toggle">In this article</label> <h2 class="l-sidebar knowledge-base__sidebar-title">In this article</h2> <ul class="knowledge-base__nav"> <li> <a href="#field-overview"> Overview </a> </li> <li> <a href="#paragraph-11571"> Purpose </a> </li> <li> <a href="#paragraph-11576"> Definitions </a> </li> <li> <a href="#paragraph-11581"> Policy </a> </li> <li> <a href="#paragraph-11586"> Responsibilities </a> </li> <li> <a href="#paragraph-11591"> Procedures </a> </li> <li> <a href="#paragraph-11596"> References </a> </li> <li> <a href="#paragraph-11566"> </a> </li> <li> <a href="#field-related-sections"> Related Information </a> </li> </ul> </nav> <div class="l-content"> <div class="box-shadow knowledge-base__content background-white"> <h2 id="field-overview">Overview</h2> <div class="node__overview"><p>Requirements to track research study participants and events in OnCore and APeX; expectations for compliance with internal control standards to ensure integrity of billing procedures for clinical trials.</p> </div> <div class="section-panel paragraph paragraph--type--text-block paragraph--view-mode--default" id="paragraph-11571"> <h2>Purpose</h2> <div class="clearfix text-formatted field field--name-field-section-body field--type-text-long field--label-hidden field__item"><p>As of May 7, 2018, UCSF’s single clinical trials management system, OnCore, has been used by research staff to manage study participant enrollment and visit activities for all clinical trials that bill through APeX. OnCore and APeX were integrated to enable research staff to link and track information about studies, participants, and their activities to:</p> <ol> <li>Provide a centralized system of record for participants who are enrolled in clinical trials</li> <li>Support accurate and compliant billing practices for those individuals</li> <li>Enable UCSF to be audit ready with OnCore generating reports across all clinical trials</li> </ol> <p>To ensure standardization of accurate, timely, and complete data for all UCSF clinical trials that bill through APeX, this policy defines the requirements to enter and track research study participants and events within OnCore and APeX. Additionally, this policy outlines expectations for compliance with internal control standards to assure the integrity of billing procedures for clinical trials.</p> </div> </div> <div class="accordion accordion--alt section-panel paragraph paragraph--type--definitions paragraph--view-mode--default" id="paragraph-11576"> <h2>Definitions</h2><dl> <dt class="accordion__title"> <button class="accordion__button" aria-controls="accordion-id-2336" aria-expanded="false" id="accordion-title-2336">OnCore</button> </dt> <dd class="accordion__body" id="accordion-id-2336" aria-labelledby="accordion-title-2336"> <p>A clinical trial management system (CTMS) that supports the management of study activities and participants, research event and visit tracking, Medicare coverage analysis, comprehensive reporting, and electronic data capture.</p> </dd> <dt class="accordion__title"> <button class="accordion__button" aria-controls="accordion-id-2341" aria-expanded="false" id="accordion-title-2341">APeX</button> </dt> <dd class="accordion__body" id="accordion-id-2341" aria-labelledby="accordion-title-2341"> <p>(Advanced Patient-Centered Excellence), UCSF’s electronic Epic-based, Medical Record System (EMR) and electronic health record (EHR) system data dating back to 2012<em>.</em></p> </dd> <dt class="accordion__title"> <button class="accordion__button" aria-controls="accordion-id-651" aria-expanded="false" id="accordion-title-651">Clinical Trial (NIH)</button> </dt> <dd class="accordion__body" id="accordion-id-651" aria-labelledby="accordion-title-651"> <p>The National Institutes of Health defines a clinical trial as "a research study in which one or more human subjects are prospectively assigned to one or more interventions (which may include placebo or other control) to evaluate the effects of those interventions on health-related biomedical or behavioral outcomes."</p> </dd> <dt class="accordion__title"> <button class="accordion__button" aria-controls="accordion-id-2346" aria-expanded="false" id="accordion-title-2346">Charge Review</button> </dt> <dd class="accordion__body" id="accordion-id-2346" aria-labelledby="accordion-title-2346"> <p>Occurs after a study participant is enrolled in OnCore (and has an active enrollment status in OnCore), an encounter is linked in APeX, and a study participant completes a research event. Once all corresponding Hospital Billing (HB) and/or Professional Billing (PB) charges populate, the charges go to a work queue and are reviewed by the Research Revenue Cycle staff before billing can take place. The charges are validated, routed according to the study’s MCA, and billed accordingly, to either the study account, the study participant, or the appropriate insurer/third-party payor.</p> </dd> <dt class="accordion__title"> <button class="accordion__button" aria-controls="accordion-id-2351" aria-expanded="false" id="accordion-title-2351">Medicare Coverage Analysis (MCA)</button> </dt> <dd class="accordion__body" id="accordion-id-2351" aria-labelledby="accordion-title-2351"> <p>An independent review of a research study to determine which clinical procedures and services are billable to the research participant, the appropriate insurer/third-party payor, or the study account. The MCA includes a review of the clinical trial documents, published practice guidelines, and Local Coverage Determinations (LCD) and National Coverage Determinations (NCD) to determine the billing status of items and services that are documented in the research protocol and/or research plan.</p> </dd> <dt class="accordion__title"> <button class="accordion__button" aria-controls="accordion-id-2356" aria-expanded="false" id="accordion-title-2356">CMS National Coverage Decision for Routine Costs in Clinical Trials (310.1)</button> </dt> <dd class="accordion__body" id="accordion-id-2356" aria-labelledby="accordion-title-2356"> <p>Effective for items and services furnished on or after July 9, 2007, Medicare covers the routine costs of qualifying clinical trials, as well as reasonable and necessary items and services used to diagnose and treat complications arising from participation in all clinical trials. Medicare will not cover:</p><p>The investigational item or service (unless covered outside of a research study)</p><p>Items and services provided solely to satisfy data collection and analysis needs and that are not used in the direct clinical management of the patient (e.g., monthly CT scans for a condition usually requiring only a single scan)</p><p>Items and services customarily provided by the research sponsors free of charge for any enrollee in the research study</p><p><a href="https://www.cms.gov/medicare-coverage-database/view/ncd.aspx?NCDId=1&ncdver=2">CMS.gov National Coverage Determination (NCD) Routine Costs in Clinical Trials</a></p> </dd> <dt class="accordion__title"> <button class="accordion__button" aria-controls="accordion-id-2361" aria-expanded="false" id="accordion-title-2361">Encounter</button> </dt> <dd class="accordion__body" id="accordion-id-2361" aria-labelledby="accordion-title-2361"> <p>An encounter in APeX is a clinical contact with a study participant. For example, office visits, admissions, and triage calls are encounters or events. If more than one evaluation or procedure takes place at that event, it is still usually considered one encounter. However, study participants can have multiple encounters in a single day if they visit multiple departments, such as an office visit and subsequent visit to the Infusion Center. In billing applications, charges or other transactions can be associated with encounters.</p> </dd> <dt class="accordion__title"> <button class="accordion__button" aria-controls="accordion-id-2366" aria-expanded="false" id="accordion-title-2366">Linking</button> </dt> <dd class="accordion__body" id="accordion-id-2366" aria-labelledby="accordion-title-2366"> <p>Associating a study participant encounter with the applicable research study and timeline point in APeX. Linking an encounter indicates that some or all of the billable services in that encounter are related to the study protocol (even if they will be paid for by the study participant or the appropriate insurer/third-party payor). A research timeline must also be generated within APeX for each participant, which will create date ranges for expected encounters based on the study protocol. An encounter can be linked to a research study from the participant’s appointment desk, at registration during scheduling or check-in, during admission, or after events are scheduled (by utilizing research reports in APeX). </p> </dd> <dt class="accordion__title"> <button class="accordion__button" aria-controls="accordion-id-2371" aria-expanded="false" id="accordion-title-2371">Research Statement</button> </dt> <dd class="accordion__body" id="accordion-id-2371" aria-labelledby="accordion-title-2371"> <p>A monthly summary of all study participant charges that were posted to a research study account in the previous month. The Research Statement is sent via email to the Primary Billing Contact for the study. These statements are referred to as “ZZ Statements” (for the West Bay) and “XX Statements” (for the East Bay). The hospital charges (HB) and professional fees (PB) are discounted for research in the statement. The total amount posted to the study account is shown on the top of the document (box titled “Hospital and Professional Research Charge”), along with subtotals for each Account Number (as Acct# in Blue).</p> </dd> <dt class="accordion__title"> <button class="accordion__button" aria-controls="accordion-id-2376" aria-expanded="false" id="accordion-title-2376">Primary Billing Contact</button> </dt> <dd class="accordion__body" id="accordion-id-2376" aria-labelledby="accordion-title-2376"> <p>A staff member designated by the Principal Investigator to receive monthly Research Statements for a study. The Primary Billing Contact is identified during the study activation process and is listed as such in the APeX study record.</p> </dd> <dt class="accordion__title"> <button class="accordion__button" aria-controls="accordion-id-2381" aria-expanded="false" id="accordion-title-2381">Timely Filing</button> </dt> <dd class="accordion__body" id="accordion-id-2381" aria-labelledby="accordion-title-2381"> <p>A limited period contractually defined by an insurance carrier for receiving and processing an insurance claim.</p> </dd> </dl> </div> <div class="section-panel paragraph paragraph--type--text-block paragraph--view-mode--default" id="paragraph-11581"> <h2>Policy</h2> <div class="clearfix text-formatted field field--name-field-section-body field--type-text-long field--label-hidden field__item"><p>The following requirements apply to all UCSF clinical trials that bill through APeX:</p> <ol> <li>Participant Registration and Enrollment in OnCore <ul> <li>All study participants must be registered and enrolled on a research study in OnCore within one business day of a scheduled research event.</li> <li>All participants in OnCore must have their enrollment status, date of informed consent, and date on the study recorded within one business day of initial study entry. Any future status changes and the date effective must be entered in OnCore within one day of the status change.</li> </ul> </li> <li>Research Encounter and Order Linking in APeX and Charge Review <ul> <li>Study participants must be enrolled on a research study in OnCore before any linking in APeX can occur.</li> <li>An encounter must be linked to the research study and corresponding timeline point as soon as a research event is scheduled or within one business day of the research event. Once the research event is appropriately linked to a study, a charge review can occur.</li> </ul> </li> <li>Participant Visit Tracking in OnCore <ul> <li>All study participants enrolled on a study in OnCore must have their study visits tracked with a corresponding date of occurrence using the OnCore calendar functionality within one business day of a scheduled research event. This tracking must occur for all visits for the duration of the study.</li> <li>Visit Tracking in OnCore is a critical area for documentation compliance and must be maintained to ensure compliant billing & invoicing for study participants.</li> </ul> </li> <li>Research Statement Billing Review <ul> <li>Once the Research Statement is sent via email from the Research Revenue Cycle unit, the research staff has 30 calendar days to review and reconcile if needed. The research staff’s Primary Billing Contact should review each of the charges detailed for each Account Number to ensure accuracy.</li> <li>Upon review, if any charges are in question by the research staff or contain identified errors, a Service Now ticket must be submitted to the Research Revenue Cycle unit to request review and/or charge correction. This ticket must be submitted within those 30 days to ensure prompt review and anticipated compliance with timely filing for any charges billed to an insurer/third-party payor.</li> <li>If a charge correction is being requested, the Research Statement and a description of the dispute should be attached to the Service Now ticket. The Research Revenue Cycle unit will re-review the account, make any necessary corrections, notify the Primary Billing Contact of the outcome via Service Now, and close the ticket within 30 days.</li> <li>Any potential charge corrections need to be made and reflected correctly in APeX within 30 days from the date of the Research Statement.</li> <li>Requests for charge review and/or corrections that are submitted after 30 calendar days will not be reviewed. </li> </ul> </li> </ol> </div> </div> <div class="section-panel paragraph paragraph--type--text-block paragraph--view-mode--default" id="paragraph-11586"> <h2>Responsibilities</h2> <div class="clearfix text-formatted field field--name-field-section-body field--type-text-long field--label-hidden field__item"><ol> <li>Office of Clinical Trial Activation (OCTA) <ul> <li>Build protocol-specific calendars (and updates through subsequent amendments) in OnCore</li> <li>Provide and manage role-based access to OnCore to ensure that research staff have appropriate access</li> <li>Provide appropriate research staff training (in person and/or through web-based resources) on the OnCore system </li> <li>Provide OnCore help desk support</li> <li>General oversight of OnCore usage and data</li> </ul> </li> <li> <p>Principal Investigator (PI)</p> <p>While responsibility for certain day-to-day management of OnCore utilization may be delegated to administrative or other staff, the PI is responsible for compliance with this policy. For all clinical trials that bill through APeX, it is the responsibility of the PI to:</p> <ul> <li>Submit all applicable new studies and/or amendments for OnCore activation and modification in accordance with the guidance posted on the UCSF website</li> <li>Complete all required APeX and OnCore training prior to scheduling research events </li> <li>Enroll study participants in a research study in OnCore</li> <li>Record study participant enrollment statuses with corresponding dates during the study</li> <li>Ensure that study participant statuses are accurate and up to date during the study</li> <li>Record and link all research-related encounters to the timeline in APeX for study participants</li> <li>Review applicable APeX reports and research-related encounters (upcoming and past) to ensure that all linking and timeline dates are complete and accurate, including edits if needed.</li> <li>Review and verify the billing-related information recorded in the study participant’s electronic health record.</li> <li>Track study participants on the OnCore calendar throughout the study</li> <li>Review OnCore data and reports to ensure that all mandatory fields are complete and accurate</li> <li>Ensure review of Research Statements (by/with the Primary Billing Contact) for billing accuracy and submission of any charge correction requests in a timely and consistent manner.</li> </ul> </li> <li>Research Revenue Cycle <ul> <li>Activate study billing accounts (study builds) in APeX.</li> <li>Ensure study participant charges are reviewed and routed for billing accurately, according to the MCA.</li> <li>Produce and disseminate via email, monthly Research Statements indicating which charges were billed to the study account.</li> <li>Provide charge review and correction support</li> </ul> </li> <li>Office of the Executive Vice Chancellor and Provost, Office of Healthcare Compliance and Privacy, Office of Medical Affairs & Governance, and Audit and Advisory Services are responsible for the enforcement of this policy. </li> </ol> </div> </div> <div class="section-panel paragraph paragraph--type--text-block paragraph--view-mode--default" id="paragraph-11591"> <h2>Procedures</h2> <div class="clearfix text-formatted field field--name-field-section-body field--type-text-long field--label-hidden field__item"><p>The following are detailed procedures for PI and research teams to ensure compliance with this policy:</p> <ul> <li><a href="https://oncore.ucsf.edu/forte-platform-web/login">OnCore: Login</a></li> <li><a href="https://trialactivation.ucsf.edu/oncore-resources">OCTA: OnCore Resources</a></li> <li><a href="https://myapex.ucsf.edu/research">APeX: Research Knowledge Bank</a></li> <li><a href="https://myapex.ucsf.edu/sites/myapex.ucsf.edu/files/images/Link_Encounter_to_Research_Study_RSH_v2_0.pdf">APeX: Link Encounter to Research Study</a></li> <li><a href="https://myapex.ucsf.edu/sites/myapex.ucsf.edu/files/images/Timelines_and_protocols_RSH_09282020_0.pdf">APeX: Research Timelines and Protocols</a></li> <li><a href="https://ucsf.service-now.com/">UCSF Service Now Ticket Submission</a></li> </ul> </div> </div> <div class="section-panel paragraph paragraph--type--text-block paragraph--view-mode--default" id="paragraph-11596"> <h2>References</h2> <div class="clearfix text-formatted field field--name-field-section-body field--type-text-long field--label-hidden field__item"><ul> <li>University of California Policy on Faculty Conduct and the Administration of Discipline (<a href="https://www.ucop.edu/academic-personnel-programs/_files/apm/apm-016.pdf">Academic Personnel Manual 016</a>), Office of the President, Rev. 2022.</li> <li>University of California Policy on Special Services to Individuals and Organizations (<a href="https://www.ucop.edu/academic-personnel-programs/_files/apm/apm-020.pdf">Academic Personnel Manual 020</a>), Office of the President, Rev. 2020.</li> <li><a href="https://policy.ucop.edu/manuals/personnel-policies-for-staff-members.html">University of California Personnel Policies for Staff Members (UC-PPSM)</a> and Personnel Policies for Staff Members <a href="https://policy.ucop.edu/doc/4010411/PPSM-62">62</a>, <a href="https://policy.ucop.edu/doc/4010412/PPSM-63">63</a>, and <a href="https://policy.ucop.edu/doc/4010413/PPSM-64">64</a></li> </ul> </div> </div> <div class="views-element-container"><div role="group" class="view view-meta-byline view-id-meta_byline view-display-id-block_1 js-view-dom-id-273950c06e547c6f1c8180a6071b1c7b7c414101ed0ee406c82159db568062dc"> <div class="view-content"> <div class="meta-byline"><div class="meta-byline-row"><h2 class="meta-byline-title">Subject area</h2><p><a href="/taxonomy/term/2081" hreflang="en">Research</a></p></div><div class="meta-byline-row"><h2 class="meta-byline-title">Policy number</h2><p>400-25</p></div><div class="meta-byline-row"><h2 class="meta-byline-title">Responsible office</h2><p><a href="/taxonomy/term/1966" hreflang="en">Office of the Executive Vice Chancellor and Provost</a></p></div><div class="meta-byline-row"><h2 class="meta-byline-title">Primary content owner</h2><p><a href="/taxonomy/term/2101" hreflang="en">Office of Research</a></p></div><div class="meta-byline-row"><h2 class="meta-byline-title">Effective</h2><p><time datetime="2024-05-22T12:00:00Z" class="datetime">May 22, 2024</time> </p></div><div class="meta-byline-row"><h2 class="meta-byline-title">Reviewed</h2><p><time datetime="2024-05-22T12:00:00Z" class="datetime">May 22, 2024</time> </p></div></div> </div> </div> </div> </div> <section class="background-gray related-text-block l-container"> <div class="related-text-block-section"> <div id="field-related-sections" class="related"> <h2 class="related__title">Related Information</h2> <ul class="related__info"> <li><a href="/policy/650-16" hreflang="en">650-16: Information Security and Confidentiality</a></li> </ul> </div> </div> </section> </div> </div> </article> </div> </div> </main> <footer class="footer"> <a href="/" rel="home" title="Campus Administrative Policies homepage" class="footer__logo"> <img src="/themes/custom/echo/images/logos/policies-logo.svg" alt="Campus Administrative Policies homepage" height="53" width="189"/> </a> <div class="footer__menus"> <nav aria-label="Footer" class="footer__columns"> </nav> </div><nav class="footer__legal" aria-label="Legal Information"> <p class="footer__copyright">© 2024 The Regents of the University of California</p> <ul class="footer__legal-nav"> <li> <a href="https://www.ucsf.edu/accessibility-resources">Accessibility</a> </li> <li> <a href="https://www.ucsf.edu/website-privacy-policy">Privacy Policy</a> </li> <li> <a href="https://websites.ucsf.edu/website-terms-use">Terms of Use</a> </li> <li> <a href="https://websites.ucsf.edu/azlist">A-Z Website List</a> </li> </ul> </nav> </footer> </div> </div> <script type="application/json" data-drupal-selector="drupal-settings-json">{"path":{"baseUrl":"\/","pathPrefix":"","currentPath":"node\/1491","currentPathIsAdmin":false,"isFront":false,"currentLanguage":"en"},"pluralDelimiter":"\u0003","suppressDeprecationErrors":true,"google_analytics":{"account":"UA-1557428-4","trackOutbound":true,"trackMailto":true,"trackTel":true,"trackDownload":true,"trackDownloadExtensions":"7z|aac|arc|arj|asf|asx|avi|bin|csv|doc(x|m)?|dot(x|m)?|exe|flv|gif|gz|gzip|hqx|jar|jpe?g|js|mp(2|3|4|e?g)|mov(ie)?|msi|msp|pdf|phps|png|ppt(x|m)?|pot(x|m)?|pps(x|m)?|ppam|sld(x|m)?|thmx|qtm?|ra(m|r)?|sea|sit|tar|tgz|torrent|txt|wav|wma|wmv|wpd|xls(x|m|b)?|xlt(x|m)|xlam|xml|z|zip"},"user":{"uid":0,"permissionsHash":"8b0c82fd0976c61ca946eb928a0694c6243d71b5847c948f050a493eaa6afd99"}}</script> <script src="/sites/policies.ucsf.edu/files/js/js_Aco2iilEAxNSDcEu_WOumNU4H6LnJPwo7xmDA9q-7kI.js?scope=footer&delta=0&language=en&theme=echo&include=eJxljlEOAiEQQy9E4EhkFhoWHRgyA27W02v0Q6M_TfuaNCUzzFj7BWmKhmTmRTMUOXK16ei_H8I1VVicB-hqrogURqROfM6aLPwCZ6dNtLCRwSHt8uUazKjA3qmwbMQuiSJ00UZc73C3isPCS32TvBhukFJRGruFrGsQ-w_xq4-1Pd_vyO_ZLhkP7r9bHQ"></script> <script type="text/javascript"> /*<![CDATA[*/ (function() { var sz = document.createElement('script'); sz.type = 'text/javascript'; sz.async = true; sz.src = '//siteimproveanalytics.com/js/siteanalyze_8343.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(sz, s); })(); /*]]>*/ </script> </body> </html>