Release notes
This topic contains the release notes for V16 of Medical Information Cloud. The release notes are organized into these high-level sections:
New features – new features and functionalities to be released in the new version.
Updated features – updated features and functionalities to be released in the new version.
Defect fixes and maintenance – fixed defects and maintenance items within the new version.
Metadata changes – changes to the underlying data models, user permissions, or system configurations to be included within the new version.
Required pre-install & pre-upgrade actions – required actions administrators must take before installing or upgrading to the new version.
As this page is maintained and updated over time to ensure accurate and timely information, Komodo Health recommends referencing the release notes online rather than printing and referencing static versions of the page. The Changelog page lists all notable changes made to this page.
For the release notes from earlier versions of Medical Information Cloud, visit the Archive.
New features
The V16 release of Medical Information Cloud will contain several new features whose functionalities are detailed below. Details about enablement and configuration are included within the product documentation, which will be updated when the release is made available.
New Adverse Event Child Record component
The new MIC - Adverse Event Child Record (medAdverseEventChildRecord) Lightning Web Component will be available for managing the child records of Adverse Event (MED_Adverse_Event__c) records. Currently, users create new Adverse Event child records in a modal, which prevents the users from accessing other information on the parent Adverse Event record. With the new component, users can create new child records directly on the Adverse Event record page and therefore reference any related information on the parent record or on any other child record. Admin users must configure the component for each child object and can specify the fields to appear, the name of the component, and more.
Related work item(s): MIC-4000, MIC-4008
Files Connect with Google Drive
Medical Information Cloud will introduce an integration with Google Drive through Salesforce's Files Connect service that enables users to create, reference, and collaborate on files that are hosted externally. The files can be Microsoft 365 files, Google Drive files, and other text and image files stored in Google Drive up to 6MB in size. Users will also be able to create snapshots of the files to track changes.
Warning
External files created with the Files Connect integration are not supported for fulfillments.
Related work item(s): PLTFM-3034, PLTFM-3037, PLTFM-3075, PLTFM-3096, PLTFM-3107, PLTFM-3108, PLTFM-3109, PLTFM-3116, PLTFM-3127, PLTFM-3136, PLTFM-3149, PLTFM-3162, PLTFM-3168, PLTFM-3193, PLTFM-3201
Updated features
The V16 release of Medical Information Cloud will also contain several improvements and optimizations to existing features and functionalities to better align with customer feedback and provide an enhanced user experience. Unless noted otherwise, all updated features are shipped "off" by default for existing customers and "on" by default for new customers.
Updated Account Search V3
Account Search V3 will be updated to include several enhancements to existing functionalities as well as improvements to the user interface and user experience (UI/UX).
Configure default Quick Search options like account type filters
Both the MIC - Case Accounts (MED_CaseAccounts) component and the MIC - Case Accounts Quick Search (medCaseAccountsQuickSearch) component will have additional default options that admin users can configure, such as the ability to show or hide the Omni Search box, the Country field (which, as described below, is no longer required), the Account record type filters, the Advanced Search fields, and the Restrict toggle. This will enhance the usability of the components, especially the option to let users filter by specific Account record types while searching for an account. Currently, users must first perform an account search before they can filter the search results by account types like HCPs, non-HCPs, or employees. With the new release, users will be able to select an account type in the initial account search as long as the Account Search component is appropriately configured.
Related work item(s): MIC-3923
Secondary information in search results
Users will be able to view secondary, or additional, information about each account in the search results by hovering over or clicking the down arrow to the right of any account. A popover will appear and, by default, show the account's source, credentials, primary language, and specialty for both person accounts and institution accounts. Admin users can configure the fields that should appear as secondary information as well as hide the secondary information popover completely.
Related work item(s): MIC-3938
Country field no longer required
The Country field will no longer be required in Account Search and Account records. Currently, while users can set the Country field to equal None when searching for an account, Account Search will still use an associated Country value, such as that on the related Interaction record, to query for Account records. In the new release, if the Country field is None, null, or empty, then a global (ZZ) account search will be performed. This ensures that users will be able to search for and create accounts without selecting a country. This also means that the Country field can be removed from Account Search layouts. However, if the Country field is removed from a layout, then the State field, which is dependent on the Country field, must also be removed from the layout to avoid any potential errors.
Note
This will be "on" by default, and no steps are required to enable this enhancement.
Related work item(s): MIC-3955
Visual updates on the results table
The results table will have a few visual enhancements, including updated column names, disc-style lists in contact and affiliation columns, highlighted icons for the selected account, and padding between each distinct value in a row. Additionally, the data in each column will no longer appear cut off and will instead automatically wrap to the following line if it does not fit in the default column width. This will improve user readability by ensuring that the data returned by Account Search fits inside the columns in the results table.
Note
This will be "on" by default, and no steps are required to enable this enhancement.
Related work item(s): MIC-3873, MIC-3968
Inactive records excluded from search results
Account Search will automatically exclude Account, Contact Information (MED_Contact_Information__c), and Affiliation (MED_Affiliation__c) records that have a Status (MED_Status__c) value of Inactive to provide users with the most relevant search results. Currently, Account Search returns both active and inactive records, which admin users can revert to in the new release via the Global Setting (mvn__MED_Global_Setting__mdt) custom metadata type. On the new Account Search Excluded Statuses (mvn__MED_Account_Search_Excluded_Statuses__c) field, admin users can configure the statuses that should be excluded, which will subsequently override the new default Account Search behavior of only returning active records. For example, to filter out both inactive and pending Account, Contact Information, and Affiliation records, an admin user must set the Account Search Excluded Statuses field to Inactive,Pending, not just Pending.
Note
This will be "on" by default, and no steps are required to enable this enhancement.
Related work item(s): MIC-3975
Auto-scroll to search results
When users conduct an account search in either the Account Search tab or the Quick Search component, Account Search will automatically scroll down to the results. This will help users more quickly access their desired search results.
Note
This will be "on" by default, and no steps are required to enable this enhancement.
Related work item(s): MIC-3986
Add Fulfillment Files List component to other objects
Admin users will be able to add the MIC - Fulfillment Files List component to the record pages of other objects, such as Adverse Event (MED_Adverse_Event__c), Request (MED_Request__c), and PQC (MED_Product_Quality_Complaint__c) pages. This will allow users to more easily manage fulfillment documents across the Medical Information Cloud product, including checking in/out, finalizing, and deleting documents.
Related work item(s): MIC-4003
E2B updates
Admin users will soon be able to set null values more explicitly without needing to worry about issues with nullFlavors. For example, if a person's initials are UNK, they would be sent as Unknown instead of keeping the valid initials. In V16, Medical Information Cloud will no longer substitute plain nullFlavor values like MSK for the nullFlavor syntax. Instead, these will be allowed as values.
To set a nullFlavor, map a value of nullFlavor_<null flavor value>. The specified value will be set as the special nullFlavor attribute for the attribute.
The MED_E2B_Generate_Button value will be updated from Generate to Yes. Submit AE. The MED_E2B_Generator_Header label value will be changed from E2B (R3) Generator to Submit Adverse Event.
Related work item(s): MIC-3988, MIC-4009
Complete a task for another user on the Task record
Admin users will be able to configure the new ✓ Complete Task button to appear on Task records. This will enable users with the required permissions to complete workflow tasks directly on the Task record on behalf of a task assignee. Currently, if a user wants to complete a task in place of an assignee, the user has to mark the task as complete on the Document record because they cannot do so on the Task record. With the new release, users can complete tasks both on the Task detail page and the Document record page.
Related work item(s): PLTFM-2961
Reassign a task to another user
Users will be able to reassign their workflow tasks to other users without needing administrator access. Currently, users cannot reassign their workflow task unless they have the CM_Admin custom permission or ask another user who has the CM_Admin custom permission. In the new release, users can just be assigned the new CM_Reassign_Task custom permission, which is included in the CM_ReassignTasks permission set.
Related work item(s): PLTFM-2931
Search with multiple characters in picklists and comboboxes
Picklists and comboboxes currently only allow single-character searches. This means that when users enter multiple characters, each character is interpreted as a new search. For example, if a user types fr in a picklist field with language options, the picklist would first scroll to the values that start with f and then scroll to the values that start with r. In the new release, however, every multiple-character search in picklists and comboboxes will be treated as a single filter query. For example, if a user types a fr in a picklist field with language options, the user will be shown values that start with fr, like French.
Note
This will be "on" by default, and no steps are required to enable this enhancement.
Related work item(s): PLTFM-2979
Hide file hosting options in New Document wizard
Each of the file hosting options in the New Document wizard will be able to be hidden via new fields on the MCM Global Setting (mvn__CM_Global_Setting__mdt) custom metadata type. This will enable admins to have greater control over the types of documents that users can create in Medical Information Cloud.
Related work item(s): PLTFM-3034, PLTFM-3094
Track the original document of cloned documents
When a document is cloned, users will be able to use the new Cloned From (mvn__CM_Document__c) field on the Document (mvn__CM_Document__c) object to more easily track the original document.
Related work item(s): PLTFM-3276
Defect fixes and maintenance
Table 7, “Fixed items” details defects and maintenance items identified in V15 that will be fixed in the V16 release.
Work item | Description | New behavior |
|---|---|---|
MIC-2753 | The MIC - Enhanced Record Edit ( | The MIC - Enhanced Record Edit component will use getLayout instead of getRecordUi. |
MIC-3905 | When the G.K.7.r.1 E2B output is generated, a performer tag is missing, resulting in it being missed by safety systems. | A performer tag will be added to G.k.7.r.1/2. |
MIC-3911 | The Account lookup field on an Interaction ( | A validation rule will be added that disallows changing the selected account's contact information. |
MIC-3918 | When there are long or rich text fields in an Account Search query and any single account in the search results has more than 200 related Contact Information ( NoteThis issue impacted V14.1 and was identified in a known issue (K1-131). | The database queries will be optimized to directly fetch Contact Information records instead of Account records with their related Contact Information records, and field permissions on these objects will be updated. These changes will resolve the query error as well as improve Account Search performance. |
MIC-4069 | When users search for an HCP on a new Interaction ( | New Field ( |
MIC-4074 | Users are allowed to add one new note on a closed Interaction ( | Notes on closed interactions will no longer be editable no matter when the interaction was closed, and an error message will be thrown if a user attempts to edit a locked note. |
MIC-4084 | Documents of the Internal Document type and Work Instructions subtype should, but do not, appear in the documents list in the Work Instructions component. This is because the API names of the out-of-the-box picklist values on the Requester Type ( | The API names of the out-of-the-box picklist values on the Requester Type and Complainant Type fields will be corrected, and documents will appear in the Work Instructions component as expected. |
PLTFM-2551 | If a user creates a document without a file and then uploads a rendition for the document, the document’s metadata appear in both the Preview and Details tabs on the Document record page. Additionally, in the Preview tab, the document’s metadata appear below the file preview and therefore overflow outside the file preview component. | When a document has a rendition, the Preview tab will only show the file preview and will not show the document's metadata. The document’s metadata will only appear in the Details tab. |
PLTFM-2996 | When a workflow task is assigned to a user who already has the role that is required to complete the workflow task and then the workflow task is reassigned to another user, the role is taken from the original assignee and granted to the new assignee. This means that the original assignee loses the role they already had. This also means that the original assignee loses access to the document if that was their only role on the document. | If a user is assigned a workflow task that grants them a role they already have and then another user is assigned the workflow task instead, the first assignee will keep their role on the document while the new assignee will also be granted the role to complete the task. |
PLTFM-3072 | Document roles cannot be removed from users with open workflow tasks on documents, even if the document roles are not associated to the open tasks. | Document roles can be removed from a user as long as the document roles are not associated to any of the user’s open tasks on the document or the user is assigned the new CM Delete Document Role With Open Tasks ( |
PLTFM-3076 | The Request Translation button is always available in the Related Documents component, even if customers do not have the integrated language translation service. When users who do not have access to the translation service click the button, a wizard opens without any options. | The Request Translation button will be hidden from the Related Documents component of a document if the Enable Translation Requests ( |
PLTFM-3123 | When a workflow is started and tasks are assigned to multiple users, every user receives notifications about the task assignments, including the tasks that are assigned to other users. | Users will only be notified about tasks that are assigned to themselves. Notifications will no longer be sent for tasks that are assigned to other users. |
PLTFM-3324 |
| Users will be able to set the |
Metadata changes
The following subsections capture the changes against entities in key areas of Medical Information Cloud that will be introduced in the latest release. This list is not exhaustive, as it does not contain changes that are internal to the application and that are not exposed to customers for customization, extension, or integration.
Custom label changes are listed in the table(s) below:
Work item(s) | Custom label(s) |
|---|---|
MIC-3923 | mvn__MED_Basic_Search mvn__MED_Record_Type mvn__MED_Restrict_Search |
MIC-3987 | mvn__MED_Back |
MIC-4000 | MED_Adverse_Event_Related_Record_Deleted_Message MED_Adverse_Event_Related_Record_Deleted_Success MED_Adverse_Event_Related_Record_Saved |
PLTFM-3034, PLTFM-3037, PLTFM-3075, PLTFM-3096, PLTFM-3108, PLTFM-3109, PLTFM-3116, PLTFM-3127, PLTFM-3162, PLTFM-3193, PLTFM-3201 | mvn__CM_Authorize_File_Repository mvn__CM_Copy_Link mvn__CM_Create_Snapshot_Version mvn__CM_Document_New_Version_Snapshot_Email_Body mvn__CM_Document_New_Version_Snapshot_Feed_Body mvn__CM_Document_New_Version_Snapshot_Notification_Body mvn__CM_Document_Version_Snapshot_Log mvn__CM_External_File_Warning mvn__CM_File_Create_Type_Not_Supported mvn__CM_File_Repository_Auth_Close_Message mvn__CM_File_Repository_Auth_Close_Title mvn__CM_File_Repository_Back mvn__CM_File_Repository_Create mvn__CM_File_Repository_Create_New mvn__CM_File_Repository_Loading_More mvn__CM_File_Repository_New_Item mvn__CM_File_Repository_Select mvn__CM_Files_Connect mvn__CM_Files_Connect_Disclaimer mvn__CM_Files_Connect_Document mvn__CM_Files_Connect_Presentation mvn__CM_Files_Connect_Spreadsheet mvn__CM_Files_Connect_Upload_File mvn__CM_Latest_External_File_Warning mvn__CM_Latest_External_File_Warning_Header mvn__CM_Microsoft_Excel mvn__CM_Microsoft_PowerPoint mvn__CM_Microsoft_Word mvn__CM_Missing_File_Repository_Permissions mvn__CM_Missing_Files_Connect_File_Access mvn__CM_New_Snapshot_Version mvn__CM_No_Repositories mvn__CM_Open mvn__CM_Search_File_Repository mvn__CM_Select_From_File_Repository mvn__CM_Selected_File mvn__CM_Snapshot_Current_Version mvn__CM_System_Event_Document_New_Version_Snapshot |
Work item(s) | Custom label | Modification description |
|---|---|---|
MIC-3968 | mvn__MED_Contact_Result_Column_Label_Address | The value will be updated from |
mvn__MED_Contact_Result_Column_Label_Email | The value will be updated from | |
mvn__MED_Contact_Result_Column_Label_Phone | The value will be updated from | |
mvn__MED_Parent_Accounts | The value will be updated from | |
MIC-4009 | MED_E2B_Generate_Button | The value will be updated from |
MED_E2B_Generator_Header | The value will be updated from |
Custom metadata type changes are listed in the tables below:
Table 11, “New custom metadata records”
Note
New custom metadata records are only available via the Medical Information Cloud - Setup plan in the Komodo Install Service.
Work item(s) | Custom metadata type | Field |
|---|---|---|
MIC-3975 | mvn__MED_Global_Setting__mdt | mvn__MED_Account_Search_Excluded_Statuses__c |
PLTFM-3034, PLTFM-3094, PLTFM-3116, PLTFM-3127 | mvn__CM_Global_Setting__mdt | mvn__CM_Files_Connect_Excel_Template__c mvn__CM_Files_Connect_PowerPoint_Template__c mvn__CM_Files_Connect_Word_Template__c mvn__CM_Hide_External_File_Button__c mvn__CM_Hide_Files_Connect_File_Button__c mvn__CM_Hide_M365_File_Button__c mvn__CM_Hide_No_File_Button__c mvn__CM_Hide_Translation_File_Button__c mvn__CM_Hide_Upload_File_Button__c |
Work item(s) | Custom metadata type | Metadata record name |
|---|---|---|
MIC-3938 | mvn__LY_Field__mdt | MED_Account_Source MED_Credentials MED_Primary_Language MED_Specialty |
mvn__LY_Layout_Field__mdt | MED_Secondary_Info_Account_Source_Inst MED_Secondary_Info_Account_Source_Person MED_Secondary_Info_Credentials_Inst MED_Secondary_Info_Credentials_Person MED_Secondary_Info_Primary_Lang_Inst MED_Secondary_Info_Primary_Lang_Person MED_Secondary_Info_Specialty_Institution MED_Secondary_Info_Specialty_Person | |
mvn__LY_Layout_Section__mdt | MED_Account_Secondary_Results_Inst MED_Account_Secondary_Results_Person | |
MIC-4069 | mvn__LY_Field__mdt | MED_Parent_Name |
mvn__LY_Layout_Field__mdt | MED_Search_Result_Parent | |
mvn__LY_Layout_Section__mdt | MED_Results_Affiliation_Person | |
PLTFM-3034, PLTFM-3109 | mvn__SE_System_Event__mdt | CM_Document_New_Version_Snapshot |
mvn__SE_System_Event_Configuration__mdt | CM_Document_New_Version_Snapshot | |
PLTFM-3034, PLTFM-3149 | mvn__CT_Content_Type__mdt | bmp gif jpg png svg tiff zip |
Work item(s) | Custom metadata type | Field | Modification description |
|---|---|---|---|
PLTFM-3034, PLTFM-3109 | mvn__CM_Document_State_Entry_Action__mdt | mvn__CM_Type__c | The New Snapshot Version ( |
Object changes are listed below.
Work item(s) | Object | Field(s) |
|---|---|---|
MIC-4008 | MED_AE_Drug_Information__c | MED_E2B_Product__c MED_Other_Product__c MED_Related_Record_Label__c |
MED_AE_Primary_Source__c | MED_Related_Record_Label__c | |
PLTFM-3034, PLTFM-3168 | mvn__CM_Document__c | mvn__CM_External_Content_Version_Id__c |
PLTFM-3276 | mvn__CM_Document__c | mvn__CM_Cloned_From__c |
Work item(s) | Object | Field | Modification description |
|---|---|---|---|
MIC-4084 | Case | MED_Requester_Type__c | The API names of the out-of-the-box picklist values will have the |
MED_Product_Quality_Complaint__c | MED_Complainant_Type__c |
Permission changes are listed in the table(s) below:
Work item(s) | Permission set |
|---|---|
PLTFM-2931 | CM_ReassignTasks |
Work item | Custom permission |
|---|---|
MIC-4008 | MED_E2B_Submission |
PLTFM-2931 | CM_Reassign_Task |
PLTFM-3072 | CM_Delete_Document_Role_With_Open_Tasks |
Work item | Permission set | Modification description |
|---|---|---|
MIC-4008 | MED_E2B_User | Added the MED_E2B_Submission custom permission. |
Static resources
Static resource changes are listed in the table(s) below:
Work item(s) | Static resource(s) |
|---|---|
PLTFM-3034, PLTFM-3116 | cmExcelTemplate cmPowerPointTemplate cmWordTemplate |
Validation rule
Validation rule changes are listed in the table(s) below:
Table 19, “New validation rules”
Note
New validation rules are only available via the Medical Information Cloud - Setup plan in the Komodo Install Service.
Work item(s) | Object | Validation rule |
|---|---|---|
MIC-4008 | MED_AE_Drug_Information__c | MED_Require_Product |
Required pre-install & pre-upgrade actions
This section includes the required actions administrators must take before installing and upgrading to the Medical Information Cloud V16 release.
Enable Lightning Web Security
Lightning Web Security (LWS) must be enabled to install and upgrade to the Medical Information Cloud V16 release. For instructions, reference Salesforce's documentation on how to Enable Lightning Web Security in an Org.