CMI — Insurance Data Sharing Requirements v2.15 min read
The tables below define the display, labelling, and behavioural requirements for the Insurance Data Sharing consents in the LFI Consent Management Interface (CMI). See the User Experience page for interactive wireframes of the dashboard and detail pages.
The LFI CMI shares the same structure and consent-type logic as the TPP CMI for Insurance Data Sharing, with the differences noted below. Adjustments to the requirements below are permitted provided the customer can always clearly understand what consents they have granted. Any adjustments must be documented in your CX certification submission.
Dashboard — tabs
Paused is not a valid status in the LFI CMI. It is a TPP-local concept that is not reflected in the API Hub.The dashboard must present Insurance Data Sharing consents across two tabs.
AwaitingAuthorization, Authorized, or Suspended.Rejected, Expired, or Revoked.Dashboard — filters
A filter panel must be available on the dashboard. The following three filters are required:
Status labels
Consent statuses must be translated from their API values into user-friendly labels before display.
AuthorizedAwaitingAuthorizationRevokedSuspendedExpiredRejectedConsent type labels
Data SharingDashboard — card content
Each Insurance Data Sharing consent card on the dashboard must show the following fields.
1 Policy Connected or 2 Policies ConnectedData SharingDetail page
Selecting a consent on the dashboard opens its detail page. The detail page presents the same information the customer saw at the time they gave consent — the permissions, policies, and conditions that defined what they agreed to. In addition to all fields shown on the dashboard card, the detail page must show a truncated Consent ID with a copy button (format: f47ac10b...d479).
Additional sections
Permissions field — e.g. Policy details, Premium details, Claim detailsConfirmation screen
When the customer selects Revoke, replace the detail view with a single confirmation screen that includes: a title, a description of the impact of the action on the service, a Confirm button, and a Go back button.
Stop sharingConfirm stop sharingOnce a customer confirms the action, the change must take effect immediately — there must be no delay between confirmation and the consent reflecting its new state. The LFI must update the consent status via the Consent Manager API.
