# Configuring OpenData Clinical

OpenData Clinical allows you to create a clean and compliant directory of clinical trial sites and investigators in your Vault by linking _Institution_-type _Organization_ object records and _Investigator_-type _Person_ object records to OpenData Clinical records.

 <div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: 
Veeva Support must enable OpenData Clinical in your Vault. OpenData Clinical is part of the <a href="/en/gr/44699/">Clinical Operations</a> application family. You must have <a href="/en/gr/40009/">Veeva CTMS</a> and/or <a href="/en/gr/4660/">Veeva eTMF</a> to use OpenData Clinical. Contact your Veeva representative for more information.</p>
    </div>
  </div>
</div>



## Configuration Overview

* Create and configure _Institution_-type _Organization_ object and _Investigator_-type _Person_ object page layouts.
  * Add the _OpenData Clinical_ _Details_ application section to the page layouts.
  * <a href="/en/gr/845621/#hiding-opendata-clinical-managed-fields">Hide OpenData Clinical-managed fields</a>.
  * Add the _Data Change Request_ object section to the page layouts and prevent record creation from the section.
  * Add the _Prior Organization_ object section to the _Institution_-type _Organization_ object page layout and the _Prior Person_ object section to the _Investigator_-type _Person_ object page layout.
  * Add the _Controlled by OpenData Clinical_ column to both the _Location_ section on the _Institution_-type _Organization_ page layout and the _Contact Information_ section on the _Investigator_-type _Person_ page layout.
* Add the _Data Change Request Lines_ object section to the _Data Change Request_ page layout.
* Add the _Prior Contact Information_ object section to the _Contact Information_ object page layout and the _Prior Location_ object section to the _Location_ object page layout.
* Optional: Set the _Data Change Request_ <a href="/en/gr/47850/#Atomic_Security_Actions">Atomic Security action</a> to _Execute_ on the necessary lifecycle states for the _Person_ and _Organization_ lifecycles.
* Optional: Configure a _Data Change Request_ tab under the _Global Directory_ tab.
* Optional: Configure a report and flash report for <a href="/en/gr/845021/#odc-prior-records">_Prior_ records</a> to review daily updates to OpenData Clinical-managed fields.

## Hiding OpenData Clinical-Managed Fields {#hiding-opendata-clinical-managed-fields}

OpenData Clinical manages various fields on <a href="/en/gr/845021/#odc-institution-records">_Institution_-type _Organization_</a> and <a href="/en/gr/845021/#odc-investigator-records">_Investigator_-type _Person_</a> records. These fields are read-only in the _OpenData Clinical Details_ section, and users cannot edit them.

While these fields are read-only in the _OpenData Clinical_ _Details_ section, users can attempt to modify these OpenData Clinical-managed fields when they appear in other sections on the _Institution_ and _Investigator_ page layouts. However, Vault displays an error message when users attempt to save the changes made to the OpenData Clinical-managed fields. To avoid error messages, remove these fields from the page layouts or use <a href="/en/gr/51632/">layout rules</a> to hide the fields.

 <div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: 
The <em>Organization</em> object requires the <em>Organization</em> field, and the <em>Person</em> object requires the <em>Last Name</em> field for the page layouts. Admins cannot remove these fields from the page layouts. We recommend using <a href="/en/gr/51632/">layout rules</a> to prevent users from attempting to edit these fields.</p>
    </div>
  </div>
</div>



## Related Permissions

You can complete all steps in this article and the <a href="/en/gr/845021/">Using OpenData Clinical</a> article with the standard _System Admin_ or _Vault Owner_ profile. If your Vault uses custom security profiles, your profile must have the following <a href="/en/gr/22824/">permissions</a> to work with OpenData Clinical:

| Permission Type | Permission | Controls |
| --- | --- | --- |
| Security Profile | Objects: Person: Investigator: Read, Create, Edit | Allows users to view, create, and edit _Investigator_-type _Person_ records |
| Security Profile | Objects: Person: OpenData ID: Read, Edit | Allows users to view and edit the _OpenData ID_ for _Person_ records |
| Security Profile | Objects: Person: Data Change Request: Execute | Allows users to create Data Change Request submissions for _Person_ records |
| Security Profile | Objects: Person: OpenData Clinical Details: View | Allows users to view the _OpenData Clinical Details_ application section on _Person_ records |
| Security Profile | Objects: Organization: Institution: Read, Create, Edit | Allows users to view, create, and edit _Institution_-type _Organization_ records |
| Security Profile | Objects: Organization: OpenData ID: Read, Edit | Allows users to view and edit the _OpenData ID_ for _Organization_ records |
| Security Profile | Objects: Organization: Data Change Request: Execute | Allows users to create Data Change Request submissions for _Organization_ records |
| Security Profile | Objects: Organization: OpenData Clinical Details: View | Allows users to view the _OpenData Clinical Details_ application section on _Person_ records |
| Security Profile | Objects: Data Change Request: Read, Edit | Allows users to view and edit _Data Change Request_ records |
| Security Profile | Objects: Data Change Request: Cancel Request: Execute | Allows users to cancel Data Change Request submissions |
| Security Profile | Objects: Data Change Request Line: Read, Edit | Allows users to view and edit _Data Change Request Line_ records |
| Security Profile | Objects: Contact Information: Read | Allows users to view _Contact Information_ records |
| Security Profile | Objects: Location: Read | Allows users to view _Location_ records |
| Security Profile | Objects: Prior Person: Read | Allows users to view _Prior Person_ records |
| Security Profile | Objects: Prior Organization: Read | Allows users to view _Prior Organization_ records |
| Security Profile | Objects: Prior Contact Information: Read | Allows users to view _Prior Contact Information_ records |
| Security Profile | Objects: Prior Location: Read | Allows users to view _Prior Location_ records |