Skip to main content

Glossary

The glossary defines key terminology that the Medical Information Cloud product utilizes.

Glossary

Account

A record that stores information about a person or business. This includes Name, Title, and historical interactions. Accounts can be:

  • Health Care Professionals (HCP), e.g. doctors and pharmacists

  • Non-HCPs, e.g. consumers and payers

  • Employees, e.g. sales representatives and medical science liaisons (MSL)

  • Institutions, e.g. hospitals and pharmacies

Adverse Event (AE)

A record that stores information on perceived unintended or unfavorable symptoms of a product.

Case

See Interaction.

Chatter

An application to collaborate, communicate, and share information about a Medical Information Cloud Content Management document. All Chatter content for a document is posted to the document's Chatter feed. You can use the Chatter publisher to contribute to the feed. If Chatter is enabled for system events, system event notifications automatically post to a document's Chatter feed when the system events occur.

Dashboard

A collection of reports that you can view on the same page. Each chart on a dashboard represents a different reportMedical Information Cloud supports standard Salesforce dashboard functionality.

DocGen Packages (DDPs)

Packages that contain the configuration and templates that tell Nintex DocGen, a third-party service, how to generate documents in your Salesforce environment. Medical Information Cloud Inquiry Management uses Dynamic Document Packages to generate Fulfillment Packages and create snapshots of Medical Information Cloud Inquiry Management records. In addition, Dynamic Document Packages make these Medical Information Cloud Inquiry Management buttons work: Generate Fulfillment, Generate Snapshot, and Send to Safety.

Document

A fundamental object of Medical Information Cloud Content Management consisting of metadata. A document can have many associated document versions, and each document version can have a different file associated with it.

Document Activity

The history of a Medical Information Cloud Content Management document version. There are two types of history:

Electronic signature

A code that you must enter to verify your identity when completing a Medical Information Cloud Content Management task.

Fulfillment

A record that stores the written response you send via email, fax, or mail to an Account. With a Fulfillment record, you can create a package of information to send via email, mail, or fax to the account that submitted the inquiry. The Fulfillment Package includes a cover letter and all the documents used to answer the account's questions.

When you give an Account a verbal response, you do not create a Fulfillment. Fulfillments are only used for written responses.

Institution

The place where a Requester works. You can associate an Account record that captures workplace information with an Interaction. For example, if a Requester works at General Hospital, you would associate the Account record for General Hospital with the Interaction.

Interaction

A record that stores the Requester's contact information and information about how and when the Requester reached out to the contact center. Every Interaction has at least one Request associated with it.

Interaction is a Salesforce Case, just relabeled. For that reason, there are references to the Case object in code and declarative configuration throughout the Medical Information Cloud product and documentation.

Interaction QA

A record that captures and stores QA review scores for how well the parent Interaction record was handled and documented. Multiple Interaction QA records can be associated with a single Interaction record.

Medical Information Cloud

A product through which you can record and manage medical information inquiries from healthcare professionals and consumers as well as manage the creation, modification, and distribution of medical content in a globally compliant, cloud-based interface that is built on the powerful Salesforce platform.

The Medical Information Cloud product contains two modules:

Medical Information Cloud Content Management

A regulated content management module that is part of the Medical Information Cloud product. With Medical Information Cloud Content Management, you can manage the creation, modification, distribution, and security of medical content through the use of features, such as:

Medical Information Cloud Inquiry Management

An inquiry management module designed to help you record and manage medical information inquiries from health care professionals (HCPs) (e.g. doctors and pharmacists), non-HCPs (e.g. consumers and payers), and employees (e.g. sales representatives and medical science liaisons). With Medical Information Cloud Inquiry Management, you can find medical content, create custom Fulfillment Packages, search for existing inquiries and responses, and submit Adverse Events and Product Quality Complaints.

Komodo Health offers two versions of the Medical Information Cloud Inquiry Management module, each designed with a specific version of the Salesforce user experience in mind:

Medical Information Cloud Inquiry Management Classic

A version of the Medical Information Cloud Inquiry Management module that supports the Salesforce Classic user experience.

Warning

In line with Salesforce's deprecation of Classic, the Medical Information Cloud Classic user experience was deprecated in V10, and several Classic items used by the Medical Information Cloud Inquiry Management module in V10 were deprecated in V11. As support for the Classic user experience, and the deprecated items have been removed:

  • The deprecated items should no longer be used.

  • All Medical Information Cloud Classic product documentation will be removed from this knowledge base when V13 goes into production.

For more information, visit Release notes.

Medical Information Cloud Inquiry Management Core

Features that pertain to both Medical Information Cloud Inquiry Management Lightning and Medical Information Cloud Inquiry Management Classic. These features tend to be shared user interface components and server-based processes or batch jobs that function similarly across Medical Information Cloud Inquiry Management versions.

Medical Information Cloud Inquiry Management Lightning

A version of the Medical Information Cloud Inquiry Management module that supports the Salesforce Lightning user experience and that makes heavy use of the Salesforce Lightning Service Console, an enhanced user experience that allows users to view multiple records and their related records on the same screen and quickly work through assigned tasks and records.

Nintex DocGen

A third-party service that Medical Information Cloud Inquiry Management uses to generate documents, such as snapshots and Fulfillment Packages in your Salesforce environment.

Product Quality Complaint (PQC)

A record that stores information related to a potential quality issue of a product. The issue may be related to manufacturing, stability and release testing, dose preparation, storage, or distribution.

Referred By

The person who reaches out to the contact center on behalf of someone else. You can associate an Account record that captures the Referred By's information to an Interaction. For example, if a sales representative calls on behalf of a healthcare professional, you would associate the sales representative's Account record with the Interaction.

Report

Presents data that you specify in visually understandable formats. Medical Information Cloud Content Management supports standard Salesforce reporting for all Medical Information Cloud Content Management objects, such as Document, Document Version, Workflow Instance, Workflow Instance Stage, and Workflow Instance Document.

Request

A record that stores information about a Requester's inquiry and the response that you provide. If a person calls and asks several questions, you will log one Interaction with several Requests.

Requester

The person receiving information via a verbal response or a Fulfillment Package in response to an inquiry posed to the contact center. You can associate an Account record that captures the Requester's information to an Interaction. For example, if a doctor reaches out to the contact center with a question, you would associate the doctor's Account record with the Interaction.

Roles

The function or capacity in which a user or group of users can act in Medical Information Cloud Content Management. By themselves, roles do not provide users or groups of users permission to perform actions. Only when they are combined with document states and permissions do they grant access to documents. The four system roles are approver, owner, reviewer, and viewer.

Snapshot

A PDF file that contains an overview of an Interaction and all related Request, Fulfillment, Adverse Event, and Product Quality Complaint records or an overview of one related record. Nintex, a third-party service, assembles the individual portions of data from the Interaction and associated child records into a single PDF document that you can download and/or email from within the Medical Information Cloud Inquiry Management module.

System Events

System events are identifiable system actions, such as the creation of a document, the status change of a document, and the end of a workflow. Significant Medical Information Cloud Content Management system events are output to channels depending on the configuration.

Task

To-do items assigned to users to progress a Medical Information Cloud Content Management document through a workflow.

Workflow

A document process in Medical Information Cloud Content Management. When a document enters a workflow, it progresses through a series of stages as tasks are completed.

Work Instructions

A component that renders a preview of relevant, internal documentation files in a document viewer. Configured parameters determine the list of documents that you can view in the component. For example, the available documents may change as you move throughout the application and/or enter data, such as the name of a product and/or the type of Requester, into the application. The component appears in a collapsible window that you can launch from the utility bar from anywhere within the application.