Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/MedicalEvents/RecordCall.htm

## Recording a Call with Medical Events

To accurately and efficiently capture activities from medical events, users can associate an event to a call, or create a call directly from a medical event. This streamlines call reporting by automatically populating call fields with event information linking the event to the call report, and enables end users to avoid reentering this information and only enter call information specific to individual attendees.

**Who can use this feature?**

* End Users – Browser, iPad
* [Recording a Call from a Medical Event](#Creating)
* Users do not require an additional license

### Configuring Recording Calls from Medical Events for

[![Closed](../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

To configure this feature:

1. Ensure the following features are configured:

   * [Configuring Call Reporting](../Call_Reporting_2/ConfiguringCR.htm)
   * [Configuring Medical Events](Configuring_Medical_Events.htm)
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the appropriate permission set.
4. Select the **Objects** tab.
5. Grant the following permissions:

   | Object | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | call2\_\_v | CRE | event\_\_v | medical\_event\_\_v | Edit |
   | call\_discussion\_\_v | CRE | n/a | medical\_event\_\_v | Read |
   | medical\_event\_\_v | CRE | n/a | * account\_\_v * address\_\_v | Read |
6. Navigate to the **medical\_event\_\_v** object in the permission set.
7. Grant Edit permission to the **Record a Call** action.
8. Add the **medical\_event\_\_v** field to the appropriate layouts of the following objects:

   * call2\_\_v
   * call\_discussion\_\_v
9. Add the following fields to the appropriate **medical\_event\_\_v** layouts:

   * account\_\_v
   * address\_\_v

### Recording a Call from a Medical Event as

[![Closed](../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

Users can create a call from a medical event by selecting the Record a Call button. The call date, event name, and call object type automatically populate based on the medical event.

![](../../Resources/Images/Activities/CallReporting/Advanced/VerteoMedEvent.PNG)

Calls created from a medical event have the following properties:

* The medical\_event\_\_v field on the call references the originating medical event and is read only
* Event attendees display as the default suggested attendees in the Attendees section of the call report. If the Search Users section attribute is enabled, users who are event attendees also display in the Attendees section.

  The parent HCO account of an HCP account must be in the same territory for child accounts to display.
* The call\_date\_\_v field defaults to the value of start\_date\_\_v for the medical event. The call\_datetime\_\_v field is defaulted to 8 A.M. on the start date.
* If [Call Address Dependency](../Call_Reporting_2/Executing/PopulateHeader/AddressDependency.htm) is enabled, the location is set to the preferred location on the user's TSF record for the person account

#### Associating Accounts and Addresses to Medical Events

Users can associate an account and address to a medical event that automatically populates in call reports created from the event. This streamlines call reporting for scenarios where users interact with several different accounts and discuss different products at the same event.

![](../../Resources/Images/Activities/CallReporting/Advanced/MedEvent-Acct.PNG)

When the account\_\_v and address\_\_v fields are placed on the medical\_event\_\_v page layout, the following fields are populated on call reports created from medical events:

* The account\_\_v and address\_\_v fields on the call report are copied from the corresponding fields on the medical event

* The medical\_event\_\_v lookup field on the call report references the originating event and is read only
* If the account\_\_v and address\_\_v fields are populated on a medical event record, the default call object type for the account is used for new calls. If the account does not have a default, the user's default call object type is used.
* If the account\_\_v and address\_\_v fields are not populated on the medical event record, the event\_\_v object type is used for new calls

If configured, [Restricting Calls by Account](../Call_Reporting_2/Restrictions/RcAcct.htm) and [Restricting Calls by Account Object Type](../Call_Reporting_2/Restrictions/RcType.htm) functionality applies to accounts on medical event calls.

#### Associating Existing Calls with Medical Events

Existing calls can be associated with medical events by populating the medical\_event\_\_v lookup field with the appropriate medical event. A filtered list of active events displays. If the desired event is not visible in the list, users can search across all events from the field.

#### Associating Product Discussions or Medical Discussions with Medical Events

Like the medical\_event\_\_v field on the call2\_\_v object, the medical\_event\_\_v field in the Product Discussions and Medical Discussions sections displays a filtered list of active events sorted by start\_date\_\_v in descending order.

To associate a discussion with a medical event, select the appropriate medical event from the medical\_event\_\_v field. Users can search across all medical events from the field.

![](../../Resources/Images/Activities/CallReporting/Advanced/MedicalDiscussion.jpg)

### Related Topics

[Creating Medical Events](Creating.htm)

[Medical Event Attendees](Attendees.htm)

[Call Reporting Overview](../Call_Reporting_2/CallReportingOverview.htm)