Skip to main content

Custom Responses

Medical Information Cloud Inquiry Management affords the ability to search for and attach custom responses when looking for product content. A custom response is a response that has been approved for delivery in response to an inbound request by a Medical Affairs organization.

Enabling custom responses

To enable custom response, ensure there is an entry within the Document Field Setting (MED_Document_Field_Setting__mdt) custom metadata type for a given segment with these fields populated:

  • Request Document Field - MED_Custom_Response__c

  • Search Field Order - <numeric value> to place the field on the search interface

  • Search Result Order - <numeric value> to place the field on the search result interface

Once enabled the custom response checkbox should appear within the Document Search interface.

Configuring custom responses

In addition to enabling custom response search, the field needs to be mapped to the target attribute within the content management system of choice. Mapping the field ensures the criteria are applied to the correct attributes within the target content management system.

Mapping is accomplished by making an entry within the CMS Field Mapping (not Document Field Settings) custom metadata type with these fields populated:

  • Request Document Field - MED_Custom_Response__c

  • Document Field - the name of the field or attribute within the target CMS. For example, for Veeva Vault a valid option would be custom_response__c.

    Note

    This field must be a checkbox-type field in the CMS/Vault.

    Note

    This field must be a checkbox-type field in the CMS/Vault when working with Medical Information Cloud Content Management. If using a Yes/No picklist, the default value should be set as No, and older documents should be back-filled with No as well.

Configuring action buttons

If the Request quick search component is configured to allow for documentation creation, a "New Custom Response" button will dynamically appear under the search criteria which will launch the Document Wizard.

Viewing custom responses

Once the custom response feature has been enabled and configured correctly, users can indicate within a document search whether or not to include custom responses within the scope of the search. It should be noted that this is an additive change to the search scope and is not a filter of the search scope.

Once a search is initiated including custom responses, users can view custom responses within the results, in addition to the content of the custom response. While visible, custom responses are not able to be added to the request unless explicitly designated for the request.

Attaching custom responses to Requests

For a user to be able to attach a custom response to a given request, the custom response must contain the request number as an attribute within the target content management system. The specific attribute that contains the request number is indicated in the CMS Field Mapping custom metadata type. To map ensure an entry exists with the following fields populated:

  • Request Document Field - MED_Related_Requests__c

  • Document Field - the name of the field or attribute within the target CMS that contains the request number. For example, for Veeva Vault a valid option would be ‘related_requests__c’.

Once mapped and a custom response is marked with the request number within the target CMS, users searching for custom responses on the request in question will be able to both view and attach the content on the request.

Creating custom responses in Requests

A user can also create a custom response directly from a Request record or in a content search component. For more information about this functionality, refer to Custom response and FAQ.