Configuring Medical Inquiry

Medical Inquiry for Vault MedComms provides a compelling, complete solution for content and case management with no third party integrations needed. Medical inquiry has three core capabilities:

• Ingesting inquiries (via UI and/or API)
• Assembling documents into a response package
• Fulfilling inquiries directly from MedComms

You can manage cases and case contacts, define priority-based service level agreements (SLAs), automatically generate standard response cover letters, assemble electronic response packages, and directly fulfill inquiries via email.

Medical Inquiry Objects

Medical Inquiry contains the following objects to manage data:

• The Case object holds all of the information about an individual request for information and is the parent object to the Case Requests and Case Content User Tasks objects.
• The Case Contact is a subtype of the Person object used to hold information about the person making the inquiry. Using the Case Contact subtype requires that Object Types be enabled on the Person object. Use Medical Inquiry CRM Data Sharing to automatically load case contacts and medical inquiries from Veeva CRM account records and update medical inquiry records in CRM from MedComms.
• The Case Request object holds the individual pieces of information.
• The Case Response object holds all attributes of the response to the inquiry and is the parent object to the Fulfillment Docs and Case Response Email objects.
• The Case Intake object contains fields that correspond to fields on the Case, Case Request, and Case Response objects. If enabled, this allows users who intake inquiries to input information for all three (3) objects from a single Case Intake form.
• The Fulfillment Docs object holds the documents used to respond to an inquiry and, if responding by email, allows you to control the order of documents in the response package.
• The Case Response Email object stores the content of the response email.
• The Case SLA determines the deadline for responding to a request.
• The Person Address object holds contact information for a Case Contact.
• The Adverse Event subtype of the Event object holds information about adverse events.

Configuring Medical Inquiry Objects

MedComms allows you to edit and add to your application data model by customizing standard objects, creating custom objects, and configuring object relationships. You can also configure business rules using lifecycle and workflow options.

Users must have Create and Edit permissions on the object they want to edit in addition to Admin: Configuration: Objects: Create and Edit permissions to create and configure objects.

Configuring Adverse Events

When creating a case, you can also capture core details of associated Adverse Events. To enable this functionality, add a related object section for the Event object to the Case page layout. We recommend entering Adverse Events as the Section Label and filtering the related list by Event Type equals Adverse Event. You can also create events in Business Admin.

Users require the Create, Read, Edit, and Delete permissions on the Adverse Event object type, and the Read permission on Event Gender, Event Outcome, Event Report Type, and Event Reporter Qualification objects.

Generating Individual Case Safety Report Files

To generate E2B(R3) Individual Case Safety Report files, users must have the following permissions:

• Document: Bulk Update
• Operations: Jobs: Read
• Create Document on the Individual Case Safety Report (ICSR) document type

Note that you’ll also need to add the Edit Document and Edit Relationships permissions for the Owner and Editor roles on the Generated and Requires Regeneration states of the Event Generated Document lifecycle.

Configuring Medical Inquiry Cover Letters

You can manage Medical Inquiry cover letter templates in Admin > Business Admin > Documents & Binders. For more information about document templates, see Managing Document Templates.

There are two types of Medical Inquiry cover letter:

• The Medical Inquiry Cover Letter references the related Case object record.
• The Medical Inquiry Case Response Cover Letter references the Case, Case Request and Case Response object records.

Download a sample Medical Inquiry cover letter.

Download a sample Medical Inquiry Case Response Cover Letter.

By default, Vault uses the Medical Inquiry Cover Letter document type. To configure the user action in the Case Response object lifecycle to use the Medical Inquiry Case Response Cover Letter document type:

1. Navigate to Admin > Configuration > Object Lifecycles.
2. Select the Case Response lifecycle.
3. Select the Draft state.
4. Click Edit in the User Actions panel.
5. Select the Medical Inquiry Case Response Cover Letter document type.
6. Select a cover letter template.
7. Click Save.

Medical Inquiry Lifecycles

Medical Inquiry has four object lifecycles:

• The Case Content User Task lifecycle is used by the Case Content User Task object to mark a task as Open (initial state) or Complete.
• The Case Request Lifecycle creates and tracks new case request records. Newly created case requests begin in the New state.
• The Case Response lifecycle moves a response through the approval process from an initial state of New.
• The Case lifecycle creates and tracks new case records from an initial state of New to a complete state of Completed.

You can modify existing lifecycles, create custom lifecycles, and add custom lifecycle states to create lifecycles that suit your organization’s needs.

Medical Inquiry Workflows

The Case lifecycle uses the Case Assignment workflow to assign an active case to a user for fulfillment. Users can respond to the request, resulting in a state change to Response Sent, which triggers a task to receive confirmation from the case contact to move the case to a final state of Closed. Alternately, users can select Close Case from the Actions menu, which will move the Case to a closed state without confirmation.

The Case Response lifecycle uses the Approve Case Request workflow to assign a task to a medical inquiry approver to review and approve a response package before it’s sent for fulfillment. The case begins in In Approval state and changes to Approved state upon approval. This will also trigger the Cover Letter to move to a steady state and automatically generate a final response package based on the steady state documents. Alternately, the approver can reject the response package and the state will change to Draft. After a user sends a response to the requestor, the state changes to Response Sent. If Vault is unable to deliver the response package email and Email Tracking is enabled, Vault changes the state to Email Bounced and sends a notification with the reason for the failure to the user who sent the response package.

See more about modifying these existing workflows and creating custom workflows.

Configuring Medical Inquiry Emails

You can configure several Medical Inquiry Case Response Email settings in your Vault.

Case Response Emails

By default, Vault sends Case Response emails to the address specified in the Case Contact field on the Case Response object. You can add the Response Contact field to the Case and Case Response objects. When configured, Medical Inquiry users can populate this field to enable Vault to send the Case Response email to that address.

To add the Response Contact field:

1. Navigate to Admin > Configuration > Objects > Case.
2. Click Page Layouts.
3. Click Case Detail Page Layout.
4. Under Details, click Add and select Response Contact.
5. Optional: Move the Response Contact field as necessary.
6. Click Save.
7. Repeat steps 1 - 6 to add the Response Contact field to the Case Response page layout.

Email Tracking

Medical Inquiry allows users to track the delivery status of email response packages and alerts users if delivery fails. Case contacts can reply directly to the MedComms user who sent the response from their email client.

To configure email tracking:

1. Navigate to Admin > Settings > Application Settings > Medical Inquiry.
2. Click Edit.
3. Select the Enable Email Tracking checkbox.
4. To allow case contacts to reply to response package emails, select the Enable Reply To with Email Responses. You cannot select Enable Reply To with Email Responses if Enable Email Tracking is not selected.
5. Click Save.

You can set the Reply To address on the Case Response email. By default, the Reply To address is the email address of the MedComms user performing the Email Response user action. If the Reply To section is added to the Email Case Response page layout, the user can select a Reply To address from a list of Centralized Email Addresses. You must configure the list of available Centralized Email Addresses on the Persons object in the Business Admin menu.

Headers and Footers

By default, Medical Inquiry emails include a Vault header and footer. You can disable the header and footer by navigating to Admin > Settings > Application Settings and selecting the Do not include Vault Email Header and Footer checkbox.

Associated Case Contacts and Colleagues

Associated Case Contacts are additional email addresses related to a Case Contact. An Associated Contact must have a Primary Case Contact assigned to it. You can configure the page layout for the Case Contact object to allow users to add Associated Contacts to from the primary Case Contact’s page. Colleagues are individuals that work at the same pharmaceutical company as the case handler and want to receive case updates.

To add Associated Case Contacts, you’ll need to first configure the Case Contact page layout and add the Associated Case Contacts section.

You can maintain the list of Colleagues, Associated Case Contacts, and Centralized Email Addresses via the Business Admin menu. Navigate to the Persons object, then click Create and select a Person Type.

CC/BCC

While assembling the Case Response, you can add Case Contacts, Associated Contacts, MedComms Users, and Colleagues as CC/BCC recipients. The page layout allows you to choose which of these users can add. To add CC/BCC recipients, you’ll need to first configure the Case Response record page layout and add a related object section for the Case Response Recipient join object.

Configuring From Email Addresses

Vault sends Medical Inquiry emails from a Veeva Vault domain address by default. You can configure Vault to allow users to change the sender email address to one associated with your organization.

Before configuring From email addresses, you must first add one or more Outbound Email Domains.

To configure From email addresses:

1. Navigate to Admin > Configuration > Objects.
2. Click Person and click the Object Types tab.
3. Verify that the From Email Address object type is enabled.
4. Return to Admin > Configuration > Objects.
5. Click Case Response.
6. Click the Page Layouts tab and click Case Response Detail Page Layout.
7. Click Add and select From.
8. Click Save.

You can also define which From email address Vault applies by creating a formula using the RecordByLabel function.

Deleting Case Response Emails

Vault stores case response emails in Case Response Email object records. When configured, Admins and users with the Delete Case Response Emails object action permission can click the Actions menu and select the Delete Email user action to delete the object records. This permission is enabled on the standard System Admin or Vault Owner security profile.

To create the user action:

1. Navigate to Admin > Configuration > Objects > Case Response Email.
2. Click the Actions tab.
3. Click Create.
4. In the Select Action dialog, select Delete Email and click Continue.
5. Optional: Add a description for the user action.
6. Click Save.

Users must have the Delete Case Response Emails object action permission to delete Case Response Email object records.

Configuring the Case Intake Form

The Case Intake form allows users to enter values for fields in the Case, Case Request, and Case Response objects from a single intake form that you can customize to suit your organization’s needs. To enable this, navigate to Admin > Settings > Application Settings > Medical Inquiry and select the Enable Case Intake Form checkbox.

You can edit the Case Intake object to customize the layout and add custom fields to the Case Intake Form. If you have added any custom fields to the Case, Case Request, or Case Response objects, you should also add corresponding fields to the Case Intake object. Vault maps Case Intake fields to the corresponding objects based on the name, plus a prefix that determines which object contains the corresponding field:

• case_ for the Case object
• creq_ for the Case Request object
• cres_ for the Case Response object

For example, Vault pushes data entered into the cres_response_extras__c field on the Case Intake form into the response_extras__c field on a case’s Case Response object record.

Note the following:

• If a field is required on the Case object, it should be required on the Case Intake object. If it is required on the Case Request, or Case Response object, add a validation rule on the Case Intake object to ensure the user populates the field on the Case Intake form.
• If you have changed any of the standard fields that are required by default on the Case, Case Request, or Case Response object, inactivate the corresponding validation rule on the Case Intake object.
• If you use custom Case Response types, add a picklist value to the Case Response Type picklist whose name exactly matches the name of the custom Case Response object type.

Failure to add required custom fields from these objects results in an error when a user saves a new case.

Configuring Automated Email Intake for Medical Inquiries

The Email to Vault feature allows Vault to receive emails directly via an inbound email address and store them as an Email object record. MedComms users can leverage this functionality to automate the Medical Inquiry intake process. Once configured, Vault can receive emails from HCPs and automatically create a new inquiry or add to an existing record.

Before configuring automated intake for Medical Inquiry, ensure that Email Tracking is enabled. You must also configure the Email to Vault feature and create at least one (1) inbound email address for Medical Inquiry where the Email Processor field is set to Medical Inquiry.

Page Layout

To configure automated Medical Inquiry intake, you must first configure the Case Request page layout:

1. Navigate to Configuration > Objects > Case Request > Page Layouts.
2. Click Case Request Detail Page Layout.
3. Add the following fields to the page layout: Recipient Email Address, Recipient Email Username, To, From, CC, Sent, Received, Subject, Attachments, Body, Body Text, and Message ID.
4. Click Save.

Object Lifecycles

Next, you’ll need to edit the Case Request and Case object lifecycles.

Case Request Lifecycle

Add the following user actions to the New state with the condition if Source equals Email: Recreate Case Request from Email; Download Original Email and Attachments; Change State to Email Forward; and Change State to Completed. We recommend using the action names as labels.

On the Email Forwarded state, edit the Atomic Security: Fields to change the Default to Read for the following fields: Created By; Created Date; External ID; ID; Last Modified By; Last Modified Date; Lifecycle; Lifecycle State; Name; and Status.

Then, add the following entry actions:

• Always, Change related object lifecycle state, Case, change state to Email Forwarded, set Conditions On Related Records checkbox, condition Include related records in the following lifecycle states, Related Record’s State New
• Always, Change related object lifecycle state, Case, change state to Closed, set Conditions On Related Records checkbox, condition Include related records in the following lifecycle states, Related Record’s State New Follow-Up Email
• Always perform actions Forward Email

Finally, add the entry criteria to Always validate that the Email Forwarding Address field is not blank.

Case Lifecycle

First, change the Editor and Owner role permissions to Edit for the New Follow-Up Email state.

On the New Follow-Up Email state, edit the Atomic Security: Fields to change the Default to Read for the following fields: Closed Date; Created By; Created Date; External ID; ID; Last Modified By; Last Modified Date; Lifecycle; Lifecycle State; Name; Response Sent Date; SLA Status; Status; Target Close Date; and Total Days to Close.

Then, add the following user actions to the New Follow-Up Email state: Change State to In Progress, Workflow Case Assignment Workflow, and Change State to Closed. We recommend entering Change State to In Progress, Assign Case, and Close Case respectively as the labels.

Finally, add the following entry criteria to the Closed state:

• Always validate that the State of Related Record Case Requests No records equal New
• Always validate that the State of Related Record Case Requests No records equal In Progress

By default, when cases receive a follow-up email, Vault updates the Closed Date field to the date when the case returns to the Closed state. If desired, you can configure Vault to retain the original Closed Date.

To configure the Closed Date field, add the following entry actions to the Closed state:

• Perform with conditions, if Closed Date is blank, perform actions Update Record Field, Closed Date, set to value today()
• Perform with conditions, if Response Sent Date is blank, perform actions Update Record Field, Response Sent Date, set to value today()

On the In Progress state, add the following entry actions:

• Always, perform actions Change related object lifecycle state, related object Case Requests, change state to In Progress
• Always, perform actions Update Record Field, field Closed Date, set to value null
• Always, perform actions Update Record Field, field Response Sent Date, set to value null

User Notifications

Vault can send New Email user notifications to either a single region or multiple regions when a new Case Request record is created. If you configure notifications for a single region, Vault sends all New Email notifications to the same user or group. If you configure notifications for multiple regions, Vault sends all New Email notifications to a specific user or group depending on the region defined by the Medical Inquiry inbound email address. For example, Vault sends notifications for inquiries sent to the address mi.uk@vernpharma.veevavault.com to a user or group in the United Kingdom.

Vault sends the user notification to the user or group in the Editor role on the Case, Case Request, and Case Response objects.

Workflow

Before Vault can send the New Email notifications, you need to create a custom New Medical Inquiry Email Received object workflow with a notification step configured as follows:

• Label: Notify Users
• Type: Notification
• Next Steps: End
• Message Template: Medical Inquiry Email Received
• Recipient: Editor

Then, navigate to Configuration > Object Lifecycles > Case Request and, under Event Actions, click Create Record. Add the following event action: perform with conditions, if Source equals Email, perform actions Start Workflow, start workflow New Medical Inquiry Email Received.

Single Region Notifications

By default, Vault adds Medical Inquiry Users to the Editor role and Medical Inquiry Approvers to the Viewer role on the Case, Case Request, and Case Response objects.

Multiple Region Notifications

To define multiple regions, you must configure custom sharing rules on the Case, Case Request, and Case Response objects to add the following:

• Medical Inquiry Region X Users in the specified region to the Editor role if Vault generated the Case Request from an email sent to the Region X Medical Inquiry inbound email address. You’ll need to add a rule for each region.
• Medical Inquiry Region X Approvers in the specified region to the Viewer role if Vault generated the Case Request from an email sent to the Region X Medical Inquiry inbound email address. You’ll need to add a rule for each region.

Configuring the Dedicated Medical Inquiry User Interface

The dedicated Medical Inquiry user interface is an alternative to the Case Intake form. They perform the same job, so only one can be enabled at a time.

Once Veeva Support enables the Medical Inquiry user interface on your Vault, you can begin to configure the user interface.

To configure the Medical Inquiry layout:

1. Navigate to Admin > Configuration > Pages.
2. Click Medical Inquiry.
3. Under Layout, click Medical Inquiry Case record.
4. Click Edit.
5. Enter a Label.
6. Click Save.

To configure the Case sections:

1. Under Sections, click Case.
2. Click Edit.
3. Enter a Title.
4. Edit the Case Fields, adding Fields and Field Keys as desired.
5. Click Save.

To configure the Notepad section:

1. Under Sections, click Notepad.
2. Click Edit.
3. Enter a Title.
4. Select a Text, Long Text, or Rich Text field on the Case object for the Notepad.
5. Click Save.

To configure the Case Children:

1. Under Sections, click Case Children.
2. Click Edit.
3. Enter a Title.
4. Edit the Case Child Object Type Data, adding Fields and Field Keys as desired. Select a grandparent Field Key for grandchild objects such as Case Response. This is the name of the field that Vault populates as the grandparent, such as Case.
5. Optional: Add child and grandchild objects. You must add each child or grandchild object separately. For example, add email, phone, standard mail, and fax types of Case Responses separately.
6. Click Save.

To configure the Case Contact section:

1. Under Sections, click Case Contact.
2. Optional: Set the Enable Contact Section checkbox to enable a dedicated Case Contact section. Enabling this section removes the Case Contact field from the Case Children section if previously configured.
3. Click Edit.
4. Enter a Title.
5. Add Case Contact Field Keys as desired.
6. Click Save.

You can also click Reorder to change the order of the records.

Configuring the OpenData Connection

OpenData customers can enable the OpenData Connection, which allows Medical Inquiry users to search OpenData for healthcare professional contact details while creating a Case Contact.

Once the feature is enabled, navigate to Admin > Settings > Application Settings and, under Medical Inquiry, select the Enable OpenData Account Search checkbox.

Next, navigate to the OpenData Connection Authorization record on the connection and enter your OpenData Network credentials.

Configuring the CRM Connection

Veeva CRM customers can enable the CRM Connection, which allows Vault to pull Medical Inquiry records from CRM and close the inquiry in CRM when the case is closed in MedComms. Vault pulls Medical Inquiry records in the Submitted or Saved states that are assigned to the Medical Inquiry Integration User using a scheduled job to create corresponding Case and Case Request records. Then, Vault pushes the status of records in the Closed state back to CRM using a second scheduled job. By default, Vault sends a status update to CRM indicating that the inquiry is closed.

This feature is separate from the CRM Data Sharing feature and does not require you to sync CRM Accounts to MedComms prior to pulling inquiries.

Vault notifies the user initiating the job or the job owner upon failure or completion of the job. You can schedule jobs to run the connection. You can also manually run the pull and push jobs by performing the actions on the integration points.

This feature must be enabled by Support. Once this feature is enabled, navigate to Admin > Settings > Application Settings and, under Medical Inquiry, select the Sync CRM Inquiries with MedComms checkbox.

This feature can only be enabled when the Medical Inquiry CRM Data Sharing feature is disabled.

To create the Connection, create a CRM Org object with the Medical Inquiry integration selected. Vault provides the initial setup from the CRM Org record. You must enter the CRM Org Type and CRM Org ID fields on applicable CRM Org records. You must also enter a CRM Username.

You must configure the following components to use the CRM Connection:

• Add the Veeva ID and OpenData Healthcare Provider ID fields to the Case Contact object type on the Person object
• Add the Mobile, CRM Org, External ID, and Source fields to the Associated Contact object type
• Update the Email field on the Associated Contact object type to be optional
• On the Person object, clear the Must Be Unique checkbox on the External ID field
• Add the Last CRM Data Share and Source CRM Org fields to the Case object page layout
• Configure the user action and add your CRM Connection credentials

Authorizing the Connection

First, you must configure the action to authorize credentials:

1. Navigate to Admin > Configuration > Objects > Connection Authorization.
2. Click the Actions tab.
3. Click Create.
4. Select Enter Salesforce Connected App Details and click Continue.
5. Optional: Enter a Description.
6. Click Save.
7. Navigate to the Object Type tab.
8. Click the Actions menu.
9. Select Edit Object Type Actions.
10. Add the Enter Salesforce Connected App Details action to the Basic Auth Object Type.
11. Click Save.

Next, add your credentials:

1. Navigate to Admin > Connections > Connection Authorizations.
2. Click the desired authorization or create a new Connection Authorization.
3. Click Edit.
4. Enter your Veeva CRM User Name, then click Save.
5. Click the Actions menu and select Set Password.
6. Enter your CRM password, then click Save.
7. Click the Actions menu and select Enter Salesforce Connected App Details.
8. Enter your Client ID / Connected App Consumer Key and Secret / Connected App Consumer Secret.
9. Click Save.

Configuring Integration Rules

After authorizing the CRM Connection, you must add and configure integration rules to suit your business logic. You can create a single set of inbound integration rules for the integration point.

To configure integration rules:

1. Navigate to Admin > Connections > Integration Rules.
2. Click Create.
3. Enter a Label and a Name.
4. Select a Connection.
5. Select an Integration Point.
6. Click Save.

Field Rules

Next, you must add field rules for each field you want Vault to populate. Field rules should account for the fields you wish to sync from the Medical Inquiry in CRM into Vault. You can specify default values for fields that are excluded from the transfer between applications using a record with only the target object and field populated alongside the type and default value. Vault also applies defaults if the CRM record has no value selected.

Vault limits the Medical Inquiry transfer to the sources used and only pulls the fields for the given query object, the Medical Inquiry record in CRM.

Field Rule Property	Description
Target Object	The object you are using in Vault.
Target Object Field	The object field in Vault for which you are creating the rule.
Label	The label identifying the field rule.
Name	The key identifying the field rule.
Field Default	The value to assign to the field if the field is blank. If you are using a referenced object such as Product, use the ID.
Reference Lookup Type	Supports mapping values in CRM to Vault and Vault to CRM. For example, CRM may return Cholecap in the Product field, which is stored as cholecap__v in Vault.
Reference Lookup	A link to a reference lookup for the matching type. Reference lookups contain a set of values and can be shared. For example, you can use a reference lookup for the Product object in multiple field rules.
Query Object	The object in CRM to which this field rule relates.
Query Field	The field on the object in CRM to which this field relates.
Query Field Type	The field type to which this relates. This property is optional.

Create a Scheduled Pull Job

Next, you must configure the action to authorize credentials:

1. Navigate to Operations > Job Definitions and click Create Job.
2. Enter a Title and a Name.
3. Under Type, select SDK Job.
4. Under Job, select com.veeva.vault.app.medical.medicalinquiry.crmorg.jobs.CRMOrgMedicalInquiryPullSchedulingJob (Medical Inquiry (CRM Connection Inquiry Pull)).
5. Define a schedule.
6. Select a Job Owner.
7. Select Active in the Status drop-down.
8. Click Save.

Create a Scheduled Push Job

Then, you must configure a second action to authorize credentials:

1. Navigate to Operations > Job Definitions and click Create Job.
2. Enter a Title and a Name.
3. Under Type, select SDK Job.
4. Under Job, select com.veeva.vault.app.medical.medicalinquiry.crmorg.jobs.push.CRMOrgMedicalInquiryPushJob (Medical Inquiry (Inquiry Push Job) - NA Commercial Org).
5. Define a schedule.
6. Select a Job Owner.
7. Select Active in the Status drop-down.
8. Click Save.

Create a Local Connection

The scheduled job requires a connection to allow Vault to read data from the CRM Org and Connection objects.

To create a new connection:

1. Enter a Name.
2. Enter medcomms_local as the API Name.
3. Under Connection Type, select Local.
4. Enter a Description.
5. Select an Authorized Connection User. This is the user with permission to to run the scheduled job.

Next, add an action to run the job:

1. Navigate to Configuration > Objects > Integration > Actions.
2. Select Create.
3. Add the Execute Medical Inquiry Pull job.

Related Permissions

Users must have a security profile that grants Admin: Objects: Create and Edit permissions on the Case, Case Request, Case Response, Case SLA, Fulfillment Document, Case Contact, and Person Address objects to perform common Medical Inquiry tasks. The configuration migration package provides the Medical Inquiry User and Medical Inquiry Approver security profiles as examples.

You can complete all steps in this article with the standard System Admin or Vault Owner security profile. If your Vault uses custom security profiles, your profile must grant the following permissions:

Type	Permission Label	Controls
Security Profile	Admin: Configuration: Objects: Create	Ability to create new Vault objects.
Security Profile	Admin: Configuration: Objects: Edit	Ability to make changes to Vault objects.
Security Profile	Admin: Configuration: Object Lifecycles: Create	Ability to create new object lifecycles.
Security Profile	Admin: Configuration: Object Lifecycles: Edit	Ability to make changes to existing object lifecycles.
Security Profile	Admin: Configuration: Object Workflows: Create	Ability to create new object workflows.
Security Profile	Admin: Configuration: Object Workflows: Edit	Ability to make changes to existing object workflows.
Security Profile	Admin: Configuration: Outbound Email Domains: Read	Ability to view the Outbound Email Domains page.
Security Profile	Admin: Configuration: Outbound Email Domains: Create, Edit, Delete	Ability to create, edit, and delete Outbound Email Domains.
Security Profile	Admin: Pages: All Configuration	Ability to configure the Medical Inquiry user interface.
Security Profile	Object: Case: Create, Read, Edit, Delete	Ability to create, read, edit, and delete Case object records in the dedicated Medical Inquiry user interface.
Security Profile	Object: Case Contact: Create, Read, Edit, Delete	Ability to create, read, edit, and delete Case Contact object records in the dedicated Medical Inquiry user interface.
Security Profile	Object: Case Request: Create, Read, Edit, Delete	Ability to create, read, edit, and delete Case Request object records in the dedicated Medical Inquiry user interface.
Security Profile	Object: Event: Create, Read, Edit, Delete	Ability to create, read, edit, and delete Event object records in the dedicated Medical Inquiry user interface.
Security Profile	Object: Case Response: Create, Read, Edit, Delete	Ability to create, read, edit, and delete Case Response object records in the dedicated Medical Inquiry user interface.
Security Profile	Pages: Medical Inquiry: Medical Inquiry: View	Ability to view and use the dedicated Medical Inquiry user interface. This permission is necessary for Medical Inquiry Users.