# Configuring the RIM-Medical Connection

The <a href="/en/gr/916478/">RIM-Medical Connection</a>
 is a standard <a href="/en/gr/533581/">Veeva Connection</a>
 that enables organizations with both RIM and Medical Vaults to increase data quality when managing medical content and medical inquiries.

## About the RIM-Medical Connection

The RIM-Medical Connection currently includes the following features:

* **Document Exchange** eliminates manual document transfer between RIM and Medical Vaults by automating <a href="/en/gr/23143/">CrossLink</a>
 document creation in Medical upon approval in RIM. See <a href="/en/gr/916478/#doc-exchange">additional details</a>
 about this feature.
* **Product Data Transfer** automatically aligns product data between the RIM and Medical application families, transferring product, indications, and local product data between Vaults to facilitate common terminology across teams. See <a href="/en/gr/916478/#product-data-transfer">additional details</a>
 about this feature.


### Related Articles & Resources

The RIM-Medical Connection is one of many Veeva-provided standard connections that support and automate business processes between separate Vaults. See <a href="/en/gr/533581/">About Veeva Connections</a>
 for general information about how a connection can work for your organization. 

Veeva Connections leverage Vault Platform's Connection feature, and as such many of the concepts described on this page are covered in greater detail by the below configuration articles for Vault Admins:

* <a href="/en/gr/53358/">Creating & Managing Connections</a>

* <a href="/en/gr/53147/">Creating & Managing Spark Queues</a>

* <a href="/en/gr/57405/">Creating & Managing Vault to Vault Integrations</a>

    * <a href="/en/gr/62154/">Creating & Managing Integration Rules for Connections</a>

    * <a href="/en/gr/58198/">Creating & Managing Reference Lookups for Connections</a>


We also recommend visiting a Veeva Connect community to learn about best practices and interact with the Veeva Vault Product Team:

* RIM: <a class="external-link " href="https://veevaconnect.com/communities/ALLaSExbEAA/about" target="_blank" rel="noopener">Submissions, Publishing and Archive<i class="fa fa-external-link" aria-hidden="true"></i></a> or <a class="external-link " href="https://veevaconnect.com/communities/ALR_0Abp0AA/about" target="_blank" rel="noopener">Registrations<i class="fa fa-external-link" aria-hidden="true"></i></a>
* Medical: <a class="external-link " href="https://veevaconnect.com/communities/ANS96aeVoAA/about" target="_blank" rel="noopener">MedComms<i class="fa fa-external-link" aria-hidden="true"></i></a> or <a class="external-link " href="https://veevaconnect.com/communities/AOoNGV47QAA/about" target="_blank" rel="noopener">MedInquiry<i class="fa fa-external-link" aria-hidden="true"></i></a>


## Configuration Overview

Generally, Vault Admins configuring a connection must first establish the <a href="/en/gr/53358/#Establish_Vault_to_Vault">Vault to Vault connection</a>
. Once the connection is established, the Vault Admin enables some or all of the currently-supported features, including:

* Document Exchange
* Product Data Transfer

To support this process, Veeva delivers standard <a href="/en/gr/57405/#about-integrations-and-integration-points">_Integration Points_</a>
 and <a href="/en/gr/57405/#about-integrations-and-integration-points">_Integration Rules_</a>
 for organizations to update per their specific requirements. This configuration may include <a href="/en/gr/62154/#create-query-rule">_Query Object Rules_</a>
 and <a href="/en/gr/62154/#create-field-rule">_Field Rules_</a>
 (with or without <a href="/en/gr/58198/">reference lookups</a>
).


### Document Exchange Configuration Overview

To enable Document Exchange, a Vault Admin must minimally:

* <a href="/en/gr/23139/#enable-crosslinks">Enable</a>
 CrossLinks in both Vaults
* In RIM: For all document types to be transferred to Medical, <a href="/en/gr/618/#EditingDocTypes">update</a>
 the document type to include the "RIM to Medical Connection" *Document Type Group*.
* In Medical: <a href="/en/gr/58198/#create-reference-lookup">Create</a>
 Document Type reference lookups to map each source RIM document to its target counterpart in Medical. 


### About Product Data Transfer Configuration

Implementing Product Data Transfer is a highly technical process which requires significant requirements analysis and planning, including reconciling any existing records in Medical. Contact your Veeva representative to learn more about the specific configuration steps required to enable this integration.


## Limitations

See <a href="/en/gr/916478/#limitations">About the RIM-Medical Connection</a>
 for limitations users may encounter.