Skip to main content

AIMI Recommends

AIMI Recommends provides human-in-the-loop oversight at key decision points in an agentic fulfillment workflow. The AIMI Recommends Review Panel is where a human Medical Information specialist reviews all agentic recommendations for an Interaction before committing them to the system. It runs as a utility-bar item on the MIC console and stays available as the specialist moves between subtabs of an Interaction.

A specialist oversees key decision points, choosing which recommendations to accept based on defined business rules and guardrails. How much is reviewed is configurable: the business rules and guardrails decide which decision points call for a specialist, so an organization can require oversight where it needs it.

Screenshot: the AIMI Recommends panel open on an Interaction, showing a stack of recommendation cards. (Suggested path: docs/mic/mic-ai/image/agentic-fulfillment-panel.png)

AIMI Recommends Review Panel

The panel lives in the utility bar of the Medical Information Cloud console, on the open Interaction. It opens on its own when an Interaction has recommendations still awaiting review, and minimizes once every recommendation has been acted on, so outstanding work surfaces without being hunted for. A specialist can also open or minimize it manually from the utility bar at any time.

When the AIMI Tier 1 Agent has finished and returned at least one recommendation, the panel header shows how many recommendations it returned for the Interaction (for example, "3 Recommendations", or "1 Recommendation" when only one is present). Each recommendation appears as a card. While the agent is still working, or when it finishes without recommendations, the panel shows a status message instead of a count.

note

The panel only shows recommendations when an Interaction is open. On a list view, navigation item, or home page the panel shows a "navigate to a Case" placeholder and offers no actions.

Track AIMI Tier 1 Agent processing status

The panel reflects where the AIMI Tier 1 Agent is in reviewing the Interaction, so a specialist can tell "still working" from "finished with nothing to suggest" rather than seeing an ambiguous count. The status updates on its own while the agent runs. No page refresh is needed.

Panel stateWhat it means
Spinner with "AIMI is reviewing this Interaction…"The agent is still processing the Interaction. The panel checks for updates automatically and switches to the result as soon as the agent finishes.
"AIMI reviewed this Interaction - No recommendations found." with a Reviewed on date and timeThe agent finished and had no recommendations for this Interaction. This is distinct from the agent not having run.
A recommendation count and cardsThe agent finished with one or more recommendations. Review them as described below.
"AIMI could not process this Interaction."The agent could not complete its review, for example, no agent is configured for the Interaction, or processing began but never finished (such as an error while running in System Context on an email-to-case Interaction). Recheck your AIMI configuration or contact your administrator.

Add an Interaction summary to the notepad

The panel displays the Interaction Summary first. It is a recommendation to review rather than a record to create:

  1. Open the summary card.
  2. Click Add to Notepad to copy the summary into the Interaction notepad.

Once added, Add to Notepad is hidden so the summary cannot be added twice. Check Source, which opens the originating email, remains available.

Review a recommendation

The panel shows one card per recommendation. Apart from the Interaction Summary, each card is one of the recommendation types: a Request, an Adverse Event, or a Product Quality Complaint (see Recommendation types). A Request recommendation can also include suggested documents, which are reviewed inside the card and are distinct from the recommendation itself (see Work with suggested documents).

note

AE and PQC assessments the agent marks Not Recommended do not appear as cards in the panel; only Recommended assessments surface for review. Declined assessments are still logged and are auditable through the AIMI Insights reports, so a reviewer should not read "no card" as "not assessed."

  1. Click a card to open its details.
  2. Review the agent-generated values.
  3. Use Check Source to open the originating email in a subtab and confirm what the agent based its recommendation on. Check Source is navigation only; it does not accept the recommendation.

Act on a recommendation

While a recommendation is awaiting review, each card offers:

  • Accept and Create, creates the corresponding record (Request, Adverse Event, Product Quality Complaint, or document attachment) and marks the response log Accepted.
  • Reject, records the decision; a rejection rationale is required to confirm. The card is marked Rejected.

After a specialist acts on a recommendation:

  • An Accepted card shows Open Record to jump to the record that was created.
  • A Rejected card shows no action buttons. A decision is final; a rejected recommendation cannot be flipped to accepted.
warning

When an Interaction is closed, the panel locks all actions. Accept, Reject, and Add to Notepad are hidden and document selections become read-only across every recommendation, even those not yet reviewed. Viewing, Check Source, Open Record, and document preview still work.

Work with suggested documents

For a recommended Request, the agent also suggests documents to fulfill it:

  1. Open the Request recommendation card to see the suggested documents and their details.
  2. Click a document name to preview the content version in a subtab (available when the document has a content-version reference).
  3. Select the checkboxes for the documents to attach, then click Accept and Create.

When the Request is accepted, the selected documents are attached to it, and the exact set chosen is recorded. After a Request is reviewed, the full suggested list stays visible but read-only, with the accepted documents checked (or all unchecked if the Request was rejected) so the choice stays visible.