Medical Information Cloud Labs, Spring '26 Release Notes
This topic contains the release notes for the Spring '26 release of the AI Medical Information (AIMI) Labs add-on for Medical Information Cloud. The release notes are organized into these high-level sections:
- Installation and upgrades
- New features
- Updated features
- Hotfixes
- Defect fixes and maintenance
- Metadata changes
- Deprecated and deleted items
- Required pre-install and pre-upgrade actions
- Required post-upgrade actions
Installation and upgrades
AIMI is a Labs add-on installed on top of Medical Information Cloud, unnamespaced (the MAI_ prefix is a naming convention), depending on the mvn-namespaced MIC core. Install AIMI from your organization's standard install URL for the add-on. AIMI requires an Einstein/Agentforce-enabled org and a configured connection to your Agentforce agent.
After installing, complete the configuration described in Set up AIMI, including assigning permission sets, configuring the agent connection assets, and reviewing prompt options.
Complete the steps in the Required pre-install and pre-upgrade actions and Required post-upgrade actions sections below.
New features
AI Medical Information (AIMI) with AIMI Recommends
This release introduces the AIMI Recommends panel for AI Medical Information (AIMI): an Agentforce-powered workflow that automatically reviews email-origin Interactions and presents recommendations to a Medical Information specialist for review. AIMI never writes directly to Medical Information records: every suggestion is stored as an MAI_AIMI_Response_Log__c record and surfaced in the AIMI Recommends utility-bar panel, where a specialist accepts or rejects it. Records are created only on acceptance.
The on-demand Ask AIMI prompt experience is a pre-existing AIMI capability (shipped in Fall '25) and is documented alongside AIMI Recommends for completeness; it is not new in this release.
See AI Medical Information (AIMI) for an overview.
Related work item(s): MIC-4118, MIC-4325
AIMI Recommends panel
A utility-bar panel on the Interaction (Case) workspace shows all AIMI recommendations for the open Interaction as review cards. Specialists open a card, review the AIMI-generated values, Check Source to confirm against the originating email, and then Accept and Create or Reject each recommendation. Accepted cards offer Open Record; rejected cards are final and offer no further action. The panel clears on non-record pages and locks all actions when the Interaction is closed.
See Use the AIMI Recommends panel.
Related work item(s): MIC-4325, MIC-4638, MIC-4661, MIC-4665, MIC-4668, MIC-4673, MIC-4675, MIC-4703, MIC-4707
Request recommendations with suggested documents
AIMI recommends the Request(s) to log for an Interaction, including product, question, category, and sub-category, and suggests documents to fulfill each Request. Document recommendations run through the same search engine as manual Content Search, so results match what a specialist gets running the search by hand. Specialists select which documents to attach; on accept, AIMI creates the Request, attaches the chosen documents, and records exactly which documents were used.
See AIMI recommendation types: Request.
Related work item(s): MIC-4031, MIC-4015, MIC-4116, MIC-4343, MIC-4636, MIC-4660, MIC-4702
Adverse Event (AE) recommendations
AIMI evaluates each Interaction for a potential adverse event and drafts a recommendation, a de-identified clinical case narrative, and the suspect product. The narrative preserves clinical substance, dose, route, symptoms, and the event, while removing identifying detail for a safety reviewer to complete downstream. On accept, AIMI creates an MED_AE_Drug_Information__c record when the recommendation is "Recommended" and a product is resolvable. AIMI resolves the suspect product by matching the product name for the Interaction's country (MED_Country__c).
Related work item(s): MIC-4113, MIC-4340, MIC-4784
Product Quality Complaint (PQC) recommendations
AIMI evaluates each Interaction for a potential product quality complaint and drafts a recommendation and complaint description. On accept, AIMI creates the corresponding PQC record, resolving the product by matching its name for the Interaction's country (MED_Country__c).
Related work item(s): MIC-4114, MIC-4341, MIC-4658, MIC-4784
Interaction Summary
AIMI generates an analyst-ready summary of the Interaction that a specialist can add to the Interaction notepad with one click. The Add to Notepad action is idempotent; it is hidden once the summary has been added.
Related work item(s): MIC-4115, MIC-4623, MIC-4665
AIMI Recommends processing status
The AIMI Recommends panel shows where AIMI is in reviewing an Interaction. While AIMI is working, the panel shows a spinner and "AIMI is reviewing this Interaction…" and updates on its own as soon as AIMI finishes. When AIMI completes with no recommendations, the panel shows an explicit empty state ("AIMI reviewed this Interaction - No recommendations found.") with a Reviewed on timestamp, so a reviewed-but-empty Interaction is distinguishable from one AIMI has not run on. If AIMI cannot complete its review, the panel shows an error message.
See Track AIMI Tier 1 Agent processing status.
Related work item(s): MIC-4659, MIC-4663
AIMI Insights reports
AIMI ships a packaged AIMI Insights report folder as a set of example reports, a starting point Medical Information managers can adapt to monitor AIMI, rather than a validated report set. The folder is shared with the whole organization at View access and contains nine reports on the AIMI Response Log object (MAI_AIMI_Response_Log__c), each with a runtime-selectable date range:
- AIMI Recommendations & Outcomes, the overall funnel of recommendations by type, reviewer decision, and Interaction status, with Accept Rate and % Reviewed.
- AIMI Performance by Product & Topic, accept rates by product and category, with reviewed counts.
- AIMI Response: Ignore Rate, the share of recommendations never reviewed, grouped by case owner.
- AIMI Rejections for Review, a worklist of rejected recommendations with AIMI's proposal and the rejection rationale.
- AIMI Categorization QA, how AIMI classifies Requests, with an "Unclear Rate."
- AIMI Response Logs, a week-over-week matrix of reviewed response logs.
- AIMI Safety Capture & Oversight, AIMI Safety Capture-Rate Trend, and AIMI Safety Declines for Review, adverse-event and product quality complaint oversight, including an "Accepted, Not Filed" guardrail and a declines worklist.
These reports are examples to build on, adapt or replace them to fit how your team reports on AIMI activity.
Related work item(s): MIC-4629, MIC-4784
Updated features
There are no updated features in this release.
Hotfixes
There are no hotfixes in this release.
Defect fixes and maintenance
The following items were fixed during the development of this release.
Fixed items
| Work item(s) | Description | New behavior |
|---|---|---|
| MIC-4637 | Changing Country on an existing email Interaction re-triggered AIMI and appended duplicate response logs. | AIMI skips re-running when the Interaction already has response logs. |
| MIC-4638 | Recommendation count and result labels were always plural. | The panel renders singular labels ("1 Recommendation", "1 Result Found") when only one item is present. |
| MIC-4655 | AIMI category/sub-category suggestions did not handle picklist dependencies. | MAI_GetPicklistValues returns the full controlling-to-dependent picklist map so dependencies are respected. |
| MIC-4658 | AIMI PQC recommendations did not display or populate the complaint. | A new MAI_Complaint__c field captures the complaint and the PQC card displays it. |
| MIC-4661 | The email subject was omitted from AIMI prompt context. | The prompt context now includes the email subject in addition to the body. |
| MIC-4665 | "Add to Notepad" could be triggered repeatedly, duplicating summary content. | The action is hidden once the summary is accepted. |
| MIC-4668 | Review-instructions guidance was too verbose. | Guidance is shortened to concise wording. |
| MIC-4673 | The AIMI Recommends panel persisted on the Interactions list view. | The panel clears on non-record pages. |
| MIC-4675 | A rejected recommendation still offered "Accept and Create", silently flipping the decision. | Accept/Reject are offered only while a recommendation is pending review; a rejected decision is final. |
| MIC-4702 | Suggested documents showed raw picklist API values and had no preview. | Document picklists display labels, and each document offers a content-version preview link. |
| MIC-4703 | AIMI panel actions remained available on a closed Interaction; suggested/accepted documents were stored redundantly. | Actions lock on a closed Interaction; suggested and accepted documents are consolidated onto the Request log. |
| MIC-4707 | The recommendation-card popover could render over the panel header. | The popover positions itself based on available space. |
Metadata changes
This release adds the following metadata. See the Custom metadata types and Page layouts, FlexiPages, and tabs inventories for the declarative items that administrators most often need to verify.
Objects
New objects
| Work item(s) | Object |
|---|---|
| MIC-4322 | MAI_AIMI_Response_Log__c (AIMI Response Log) |
Record types on MAI_AIMI_Response_Log__c: MAI_Request, MAI_Interaction_Summary, MAI_Adverse_Event, MAI_PQC, MAI_Fulfillment (MIC-4331).
New fields
| Work item(s) | Field |
|---|---|
| MIC-4659, MIC-4663 | Case.MAI_AIMI_Orchestration_Status__c (AIMI Orchestration Status, restricted picklist: Pending, Completed, Failed) |
| MIC-4659, MIC-4663 | Case.MAI_AIMI_Orchestration_Completed_At__c (AIMI Orchestration Completed At, Date/Time) |
These fields track the AIMI Tier 1 Agent orchestration lifecycle so the AIMI Recommends panel can show processing, empty, and error states. Read/edit access is granted through MAI_AIMI_Agent_PS and read access through MAI_AIMI_User.
Custom metadata types
New custom metadata types
| Work item(s) | Custom metadata type |
|---|---|
| , | None in this release. |
Pre-existing custom metadata types in the package
| Custom metadata type | First shipped |
|---|---|
MAI_AIMI_Prompt_Option__mdt (AIMI Prompt Option) | Fall '25 (17.0.0) |
MAI_AIMI_Prompt_Option__mdt is part of the AIMI package but was introduced in an earlier release for the Ask AIMI prompt experience. It is not new in this release. AIMI Recommends reuses the same custom metadata type for its Agent-type configuration records (distinguished by the MAI_Config_Type__c field), but the type itself is pre-existing.
New custom metadata records
| Work item(s) | Custom metadata record |
|---|---|
| MIC-4343, MIC-4636 | mvn__Field_Audit_Settings.AIMI_Response_Log_Suggested_Documents |
| MIC-4636 | mvn__Field_Audit_Settings.AIMI_Response_Log_Accepted_Documents |
| MIC-4675 | mvn__Field_Audit_Settings.AIMI_Response_Log_Rejected_Rationale |
MAI_AIMI_Prompt_Option__mdt configuration records ship as setup data so they can be tuned per org. The Agent-type records used by AIMI Recommends (Summarize Interaction, Recommend Product and Question, Recommend Category and Sub-Category, Recommend Product Quality Complaint, Recommend Adverse Event) and the Prompt UI-type records used by Ask AIMI (Detect Adverse Event, Detect Product Quality Complaint) are part of the package's pre-existing setup data, not introduced this release.
Apex classes
New Apex classes
| Work item(s) | Apex class |
|---|---|
| MIC-4116 | MAI_AimiAgentSvc, MAI_AimiAgentQueueable, MAI_AimiInteractionHdlr, MAI_AimiRespLogHdlr |
| MIC-4343, MIC-4660, MIC-4703 | MAI_AimiDocSearchHdlr, MAI_AimiDocSearchMapper, MAI_AimiDocSearchQueueable, MAI_AimiContentSearchCtrl |
| MIC-4325, MIC-4636 | MAI_AgenticFulfillmentCtrl |
| MIC-4015, MIC-4655 | MAI_GetPicklistValues |
| MIC-4116 | MAI_GetContentNotes, MAI_ContentNoteData, MAI_StripHtmlUtil |
Pre-existing Apex classes in the package
| Apex class | First shipped |
|---|---|
MAI_AIMIPromptCtrl, MAI_Utility | Fall '25 (17.0.0), Ask AIMI |
Lightning components
New Lightning components
| Work item(s) | Component |
|---|---|
| MIC-4325 | maiAgenticFulfillment, maiAgenticFulfillmentCard, maiAgenticFulfillmentDetail, maiAgenticFulfillmentDetailCase, maiAgenticFulfillmentDetailRequest, maiAgenticFulfillmentDetailSummary, maiAgenticFulfillmentDocumentList, maiAgenticFulfillmentHelper, maiAgenticFulfillmentRejectionPrompt |
| MIC-4325 | maiAgenticFulfillmentWrapper (Aura utility-bar wrapper) |
Pre-existing Lightning components in the package
| Component | First shipped |
|---|---|
maiAimiPromptComponent, maiAimiPromptModal | Fall '25 (17.0.0), Ask AIMI |
Prompt templates and GenAI assets
New prompt templates
| Work item(s) | Prompt template |
|---|---|
| MIC-4113, MIC-4340 | MAI_Interaction_AE_Recommendation |
| MIC-4031 | MAI_Interaction_Product_And_Question |
| MIC-4114, MIC-4341 | MAI_Interaction_Product_Complaint_Recommendation |
| MIC-4115, MIC-4623 | MAI_Interaction_Summary |
| MIC-4015 | MAI_AIMI_Response_Log_Suggest_Category (the active categorizer; MAI_Request_Suggest_Category also ships but is superseded and unused) |
GenAI topics (plugins): MAI_Request_Management, MAI_Interaction_Management, MAI_Adverse_Event_Recommendation, MAI_Product_Quality_Complaint_Management. GenAI functions and supporting flows are added for each create/get/update step.
Flows
New autolaunched flows persist agent output as response logs and read/update them (MAI_AIMI_Agent_Create_*_Response_Log, MAI_AIMI_Agent_Get_Interaction_Details, MAI_AIMI_Agent_Get_Response_Log, MAI_AIMI_Agent_Update_Response_Log). Separate prompt flows (PromptFlow) supply prompt context (MAI_Interaction_Get_Email_Content, MAI_Interaction_Get_Content_Notes, MAI_Interaction_Get_Request_Details, MAI_Interaction_Get_Available_Products, MAI_Request_Get_Available_Categories).
Permissions
New permission sets
| Work item(s) | Permission set |
|---|---|
| MIC-4331, MIC-4318 | MAI_AIMI_User |
| MIC-4318 | MAI_AIMI_Agent_PS |
| MIC-4343 | MAI_AIMI_Content_Access |
Pre-existing permission sets in the package
| Permission set | First shipped |
|---|---|
MAI_Run_AIMI_Prompt (grants access to run Ask AIMI prompts) | Fall '25 (17.0.0) |
New custom permission: MAI_Agentic_Fulfillment_Access (gates the AIMI Recommends panel).
Page layouts, FlexiPages, and tabs
Five page layouts (one per record type) on MAI_AIMI_Response_Log__c (MIC-4331, MIC-4629), including the Request layout that surfaces the suggested and accepted documents fields; the AIMI_Response_Log_Record_Page FlexiPage; the Medical_Information_Cloud_UtilityBar FlexiPage (adds the AIMI Recommends utility item); and the MAI_AIMI_Response_Log__c custom tab.
Reports and report folders
New report folders
| Work item(s) | Report folder |
|---|---|
| MIC-4629, MIC-4784 | AIMI_Insights (AIMI Insights, shared with the organization at View access) |
New reports
| Work item(s) | Report |
|---|---|
| MIC-4629, MIC-4784 | AIMI_Recommendations_and_Outcomes, AIMI_Performance_by_Product_and_Topic, AIMI_Response_Ignore_Rate_X4H, AIMI_Rejections_for_Review, AIMI_Categorization_QA, AIMI_Response_Logs_PSZ, AIMI_Safety_Capture_and_Oversight, AIMI_Safety_Capture_Rate_Trend, AIMI_Safety_Declines_for_Review |
All nine reports run on MAI_AIMI_Response_Log__c and ship as example reports to build on.
Named credentials and connected app
MAI_AIMI_Named_Cred, MAI_AIMI_External_Cred, MAI_AIMI_EAuth_IDP, and the AIMI_Agent_ECA External Client App connect AIMI to your Agentforce agent.
Deprecated and deleted items
None in this release.
Required pre-install and pre-upgrade actions
Enable Einstein/Agentforce
Enable Einstein and Agentforce (including Prompt Builder) in the org before installing AIMI. AIMI cannot generate recommendations without an Agentforce-enabled org.
Required post-upgrade actions
Configure the AIMI agent connection and permissions
After installing, you must:
- Configure the agent connection assets (
MAI_AIMI_External_Cred,MAI_AIMI_Named_Cred,AIMI_Agent_ECA) with your org-specific endpoint and credentials. - Assign the AIMI permission sets to the appropriate users.
MAI_AIMI_Useralready grants theMAI_Agentic_Fulfillment_Accesscustom permission that gates the panel; grant it separately only for custom profiles that do not useMAI_AIMI_User. - Review
MAI_AIMI_Prompt_Option__mdtrecords and activate the prompts you want to use. - Add the AIMI Recommends utility item to your Medical Information Cloud console app if you use a custom app.
See Set up AIMI for the full procedure.