Skip to main content

Search Content

Overview

Medical Information Cloud's Search Content feature allows users to quickly find and attach relevant content to a Request. Doing so helps create a more holistic package of information for the requester.

Figure 1. Search Content experience
Search Content experience


Two content search Lightning components can be added to the Request record page:

  • MIC - Request Content Search (medRequestQuickSearch) - adds a search bar and button to the Lightning record page.

  • MIC - Inline Content Search (medRequestInlineSearch) - provides the same functionality as the MIC - Request Content Search component without launching a modal. This means that the search fields, filters, and results are all available directly on the Request record page.

Best practices

Komodo Health recommends reviewing the sections below, which provide helpful information to assist you in getting the most out of your Search Content experience.

Using the Search Content modal

The Search Content modal allows you to search for content using specific keywords and/or field values to filter search content results. Keyword searches are case-insensitive. For example, a search for content related to medication doses can be executed using Dosing, dosing, or DOSING, all of which will return the proper results. Keyword searches may include search operators to perform more advanced searches.

To narrow down your search results:

  1. In the Search Content modal, enter/select values for the following fields:

    Note

    The fields below are a standard set and used for example purposes. The actual fields you may see will be dependent upon your organization's configuration.

    • Keyword - select from All searchable fields or Document Number.

    • Type - select the type of content: Internal Document, Medical Information Response, or Reference Document.

    • Subtype - select an option from the dropdown menu. Available options appear based on the type of content selected in the previous field.

      SearchContentModal_V13.png

      Note

      The Subtype field is only enabled when a Type has been selected.

    • Product - search for content based on a single product.

    • Language - search for content in a specific Language.

    • Country - search for content based on Country.

  2. Click Search. A list of results will appear based on the criteria entered above. Results can be sorted by column by clicking the column header.

    SearchContentSearchResultsV13.png

Note

To perform a wider search, leave all fields blank and click Search.

Operators

Using Operators can also assist you in finding specific content. The tables below describe each operator as well as examples of their usage.

Table 116. Search operators

Operator

Description

*

Asterisks match zero or more characters at the middle or end of your search term. For example, a search for Asterisks matches zero or more characters at the middle or end of your search term. For example, a search for john* finds items that start with john, such as john, johnson, or johnny. A search for mi* meyers finds items with mike meyers or michael meyers.

" "

Use quotation marks around search terms to find matches in the order you entered your search terms. A search for Monday meeting finds items that contain Monday meeting in that order.

To include the words “and,” “or,” and “and not” in your search results, surround those words in double quotes. Otherwise, they are interpreted as the corresponding operators.

AND

Finds items that match all the search terms. For example, must be specified because OR is the default operator and is the default operator. However, when searching for articles, documents, and solutions, and. Usually, if an operator is not specified, smith and the word john finds items with both the word john AND smith finds items that match all the search terms.

OR

Finds items with at least one of the search terms. For example, john OR smith finds items with either john or smith, or both words.

AND NOT

Finds items that do not contain the search term. For example, john AND NOT smith finds items that have the word john but not the word smith.

( )

Use parentheses around search terms with logical operators to group search terms. For example, you can search for:

  • (“Bob” AND “Jones”) OR (“Sally” AND “Smith”)— searches for either Bob Jones or Sally Smith.

  • (“Bob”) AND (“Jones” OR “Thomas”) AND Sally Smith— searches for documents that contain Bob Jones and Sally Smith or Bob Thomas and Sally Smith.



Examples

The examples below show how you can use operators to search for specific content.

Table 117. Search Content Examples

Keyword(s)

Search description

dosing guide

This search returns all records whose fields contain both words: dosing and guide, in any location of the text. The order of words in the search term does not matter.

dosing OR guide

This search uses the OR logical operator. It returns records with fields containing the word dosing or records with fields containing the word guide.

dosing AND teenagers

This search uses the AND logical operator. It returns records with fields containing the word dosing and records with fields containing the word teenagers.

dosing AND NOT teenagers

This search uses the AND NOT logical operator. It returns records with fields containing the word dosing but not records with fields containing the word teenagers.

teen*

This is a wildcard search. This search returns all records that have a field value starting with teen.

"dosing guide"

This search returns all records whose fields contain the words dosing guide, in order, in any location of the text.



Configuring custom search content

Users can invoke their own custom search content handlers to be used in either of the content search components. The custom search content handler must be configured within Medical Information Cloud Inquiry Management. To implement a custom search content handler:

  1. Create a custom Apex class that implements the MED_CMSIntfDefinition.MED_CMSIntf interface.

  2. Use MED_CMSSettingAccessor to retrieve field and value mappings from the Medical Information Cloud CMS settings.

    Note

    Create at least one CMS_Connection with the handler class specified in the Handler class field. Input all desired fields and value mappings under the created CMS_Connection.

    Warning

    Do not directly reference custom metadata.

  3. In the Local settings where the custom handler will be used:

    1. Set the CMS Source to Custom

    2. Enter the Handler class name in the Custom Handler field

Configuring search content

There are several field configurations and search options you can set when using either of the search content components, including:

Implementation considerations

To begin, keep these considerations in mind when adding a content search component to Lightning page layouts:

  • Search fields display with labels stacked, even if users select Compact for their Display Density setting.

Document search parameters

The content search components use specific fields to configure document search parameters and result fields. The search parameters the agent selects for document search are configurable per segment. To configure which fields appear in the document search parameters, edit or create the appropriate Document Field Setting record. Table 118, “Document Field Setting fields that configure search fields” lists the Document Field Setting fields that configure the search fields.

To configure which document types are searchable in the document search parameters, utilize the Restrict to picklist values setting on the Document Field Settings custom metadata type. Turning on this setting allows only specified document types and subtypes to be searched. If the type filter is left blank, only the types, subtypes, and classifications specified in the Request Document picklist will be searched.

Table 118. Document Field Setting fields that configure search fields

Field Label

Description

Required

Default Value (Request)

API path to the field on the Request or other object to pull a default value from, e.g., MED_Request__r.Name. This value will be pre-populated in the search fields.

Default Value (Static)

A static value that is set. If Default Value (Request) is configured, this value will not be used.

Hover for Value

The field value is replaced with an image and the value is shown when hovering over the icon.

Link to Viewer

Whether the field should link to the document viewer.

Restrict to Picklist Values

When set to true for a picklist field, a search will be filtered to only values in the picklist if no value is chosen.

✓

Search Field Order

The order that this field should show up in the search parameters section. When populated, this field becomes a search parameter.

✓

Search Result Order

The result column order for this field. When populated, this field displays a result column.

✓



Optional search by Document Number

You can also choose between two search options when using a content search component:

  • All searchable fields – use any of the search criteria fields configured by an administrator. This option is selected in the background by default.

  • Document Number – enter a full or partial document number into the search box to only search the document number and any forced filters. This option must be enabled.

To display these options and enable the ability to select Document Number:

  1. Open the Request page in the Lightning App Builder.

  2. Click on the content search component you are using.

  3. Select the Allow Document Number Search checkbox.

  4. Click Save.

Configuring the Search Content experience for V13

As of V13, users can configure their content search experience to use either the current modal or a dedicated local tab.

To enable the local tab experience:

  1. Navigate to the Request page in the Lightning App Builder.

  2. Click to select the MIC - Request Content Search component.

  3. Check the box next to Enable Content Search as Local Tabs.

  4. Click Save.

MIC_V13_Enable_Content_Search_Tab.png

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.

Custom responses

For information on Custom Responses and configurations, visit Custom Responses.