/** * Hover manager - mouse tracking, overlapping-element grouping, and click dispatch * * Reads (via globals): * SFE.Context - .activeMode (r/w), .actionBar, .uuidMap, * .sortHandlersByPriority, .hoverTracker * SFE.ElementState - .attachEventListener, .removeEventListener * SFE.GenerateClientUuid * SFE.OverlayManager * SFE.startEditing - set by frontend-inline-edit.js * SFE.startCommenting - set by frontend-inline-edit.js * SFE.ManagerData - .postId, .handlers, .permissions * * Exposes: SFE.HoverManager { attachActionBarToElement, findOverlappingGroup } */ (function() { 'use strict'; window.MWP = window.MWP || {}; window.MWP.SFE = window.MWP.SFE || {}; const SFE = window.MWP.SFE; SFE.ManagerData = SFE.ManagerData || {}; /** * Return whether the current user may view pending drafts. * * Comment-only users intentionally receive the normal comment handler for a * block, but must not learn that the block has a pending draft or enter the * draft-preview flow. * * @returns {boolean} True when draft state may be exposed in the UI. */ function canAccessDrafts() { const permissions = SFE.ManagerData.permissions || {}; return !!(permissions.can_publish || permissions.can_draft); } /** * Returns true while a FloatingUiMoveManager-driven UI drag session is active. * * This suppresses hover state churn while the user is repositioning plugin * chrome such as the movable mode toggle bar. * * @returns {boolean} True when a UI drag session is active. */ function isUiDragActive() { return !!( SFE.FloatingUiMoveManager && typeof SFE.FloatingUiMoveManager.isDragActive === 'function' && SFE.FloatingUiMoveManager.isDragActive() ); } /** * Return whether batch editing currently has an active editor surface. * * This mirrors the existing "active session or session still loading" * behavior so hover ownership stays stable from the first editor open. * * @returns {boolean} True when batch editing is effectively active. */ function isBatchEditingActive() { const batchManager = SFE.BatchEditManager || null; if (!batchManager || !SFE.Context.activeEditor) { return false; } return ( (typeof batchManager.isSessionActive === 'function' && batchManager.isSessionActive()) || (typeof batchManager.isEnabled === 'function' && batchManager.isEnabled()) ); } /** * Return whether one pointer coordinate lies within an element's bounds. * * @param {Element|null} element Target element. * @param {number} x Pointer client X coordinate. * @param {number} y Pointer client Y coordinate. * @returns {boolean} True when the point is inside the element box. */ function isPointWithinElementBounds(element, x, y) { if (!(element instanceof Element)) { return false; } const rect = element.getBoundingClientRect(); return ( x >= rect.left && x <= rect.right && y >= rect.top && y <= rect.bottom ); } /** * Return whether two bound elements belong to the same active block family. * * Parent/child relationships inside the active block must remain hoverable, * while unrelated overlapping siblings should be ignored when the pointer is * still inside the active block's own bounds. * * @param {HTMLElement} activeElement Active editor block root. * @param {HTMLElement} candidateElement Candidate bound element. * @returns {boolean} True when the candidate is the active element, one of * its descendants, or one of its ancestors. */ function isWithinActiveElementFamily(activeElement, candidateElement) { if (!(activeElement instanceof HTMLElement) || !(candidateElement instanceof HTMLElement)) { return false; } return ( candidateElement === activeElement || activeElement.contains(candidateElement) || candidateElement.contains(activeElement) ); } /** * Filter hover candidates during batch editing so only the active block and * its parent/child bound relatives can win hover while the pointer remains * inside the active block bounds. * * @param {HTMLElement[]} candidates Candidate editable elements under the pointer. * @param {number} clientX Pointer client X coordinate. * @param {number} clientY Pointer client Y coordinate. * @returns {HTMLElement[]} Filtered candidate elements. */ function filterBatchHoverCandidates(candidates, clientX, clientY) { if (!Array.isArray(candidates) || candidates.length === 0) { return []; } if (!isBatchEditingActive()) { return candidates; } const activeElement = SFE.Context.activeEditor?.element || null; if (!(activeElement instanceof HTMLElement)) { return candidates; } if (!isPointWithinElementBounds(activeElement, clientX, clientY)) { return candidates; } return candidates.filter(candidate => isWithinActiveElementFamily(activeElement, candidate)); } /** * Find every editable element whose overlay directly intersects the starting * element's overlay. * * This deliberately does not recursively expand through intersecting * elements. Recursive expansion turns an overlap chain into one group, so a * full-width block at the top of the viewport can pull in unrelated blocks * farther down the page. Edge contact is also excluded because it does not * produce a shared overlay area. * * @param {HTMLElement} startElement Hovered editable element. * @returns {HTMLElement[]} Directly intersecting elements, sorted for display. */ function findOverlappingGroup(startElement) { const allElements = Array.from(document.querySelectorAll('[data-mwp-sfe-bound="1"]')); const startRect = startElement.getBoundingClientRect(); const groupArray = allElements.filter(element => { if (element === startElement) { return true; } const rect = element.getBoundingClientRect(); return ( startRect.left < rect.right && startRect.right > rect.left && startRect.top < rect.bottom && startRect.bottom > rect.top ); }); // Sort by bottom Y coordinate and physical size groupArray.sort((a, b) => { const aRect = a.getBoundingClientRect(); const bRect = b.getBoundingClientRect(); // Priority 1: Bottom coordinate (the element that ends lowest on the page comes first) if (Math.abs(aRect.bottom - bRect.bottom) > 1) { return bRect.bottom - aRect.bottom; } // Priority 2: Top coordinate (if bottoms are equal, the one that starts higher up is "outermost") if (Math.abs(aRect.top - bRect.top) > 1) { return aRect.top - bRect.top; } // Fallback: DOM order (ancestors first) return a.compareDocumentPosition(b) & Node.DOCUMENT_POSITION_FOLLOWING ? -1 : 1; }); return groupArray; } /** * Attach interactive action bar to a single element */ function attachActionBarToElement(element) { const ctx = SFE.Context; const { attachEventListener, removeEventListener } = SFE.ElementState; const generateClientUuid = SFE.GenerateClientUuid; const overlayManager = SFE.OverlayManager; const hoverTracker = ctx.hoverTracker; const actionBar = ctx.actionBar; const uuidMap = ctx.uuidMap; const sortHandlersByPriority = ctx.sortHandlersByPriority; const handlers = SFE.ManagerData.handlers; const postId = SFE.ManagerData.postId; const isInlineUIEnabled = () => ctx.isInlineUIEnabled !== false; // Clean up old event listeners removeEventListener(element, 'mouseenter', 'mwpSfeShowBar'); removeEventListener(element, 'mouseleave', 'mwpSfeHideBar'); removeEventListener(element, 'mousemove', 'mwpSfeMouseMove'); removeEventListener(element, 'click', 'mwpSfeClick', true); // Clean up old action bar if (element.dataset.mwpSfeBound) { element.querySelectorAll('[data-mwp-sfe-control]').forEach(el => el.remove()); delete element.dataset.mwpSfeBound; } // SKIP nested lists if (element.tagName === 'OL' || element.tagName === 'UL') { const parentList = element.closest('li'); if (parentList) return; } let uuid = element.dataset.mwpSfeUuid; let applicableHandlers = []; // Get handlers from uuidMap if available if (uuid && uuidMap[uuid]) { if (canAccessDrafts() && uuidMap[uuid].is_pending) { element.classList.add('mwp-sfe-status-pending'); } uuidMap[uuid].handlers.forEach(handlerId => { const handler = handlers.find(h => h.id === handlerId); if (handler) applicableHandlers.push(handler); }); } if (!applicableHandlers.length) return; element.dataset.mwpSfeBound = '1'; // Sort handlers by priority const sortedHandlers = sortHandlersByPriority(applicableHandlers); const editHandler = sortedHandlers.find(handler => handler.capability === 'edit') || null; const schemaRuntime = SFE.SchemaRuntime || null; if ( editHandler && schemaRuntime && typeof schemaRuntime.syncPlaceholders === 'function' ) { schemaRuntime.syncPlaceholders(element, editHandler); } if (!uuid) { const primaryHandler = sortedHandlers[0]; const typeCode = primaryHandler.elementTypeCode || element.tagName.toLowerCase(); uuid = generateClientUuid(postId, typeCode, element); element.dataset.mwpSfeUuid = uuid; } // Detect comment-only elements (all handlers are 'comment', no edit handler). // We do NOT touch the element itself - the status is stored on the overlay only. const isCommentOnly = ( sortedHandlers.length > 0 && sortedHandlers.every(h => h.capability === 'comment') ); // Mirror the status onto the element itself so CSS can exclude locked // elements from pointer-events restoration (the same way mwp-sfe-status-pending // is used for draft elements). We keep this as the sole CSS hook - the overlay // data-status attribute remains the authoritative source for JS queries. if (isCommentOnly) { element.classList.add('mwp-sfe-status-comment-only'); } // Add persistent status overlay if (overlayManager) { let status = 'editable'; if (element.classList.contains('mwp-sfe-status-pending')) status = 'pending'; else if (isCommentOnly) status = 'comment-only'; overlayManager.addStatusOverlay(element, status); } // Store handlers and uuid on element for later retrieval element._mwpSfeHandlers = sortedHandlers; element._mwpSfeUuid = uuid; // Use mousemove with elementsFromPoint to detect overlapping elements const mouseMoveHandler = function(e) { if (!isInlineUIEnabled()) { if (overlayManager) overlayManager.hideHover(); actionBar.hide(); hoverTracker.lastHoveredElements = []; hoverTracker.currentGroupId = null; hoverTracker.bottommostElement = null; hoverTracker.isProcessing = false; return; } // Suppress all hover state changes while a save is in progress. if (ctx.isSaving) return; if (isUiDragActive()) return; hoverTracker.currentMousePos = { x: e.clientX, y: e.clientY }; if (hoverTracker.isProcessing) return; hoverTracker.isProcessing = true; requestAnimationFrame(() => { if (isUiDragActive()) { hoverTracker.isProcessing = false; return; } // Preserve the current hover while the pointer crosses the tiny // block-to-action-bar gap. Without this, an overlapping parent block // wins elementsFromPoint() before the pointer can reach the bar. if (actionBar.isPointerInHoverTransferCorridor(e.clientX, e.clientY)) { hoverTracker.isProcessing = false; return; } const elementsAtPoint = document.elementsFromPoint(e.clientX, e.clientY); // If hovering action bar, don't change state const hoveringActionBar = elementsAtPoint.some(el => el.classList.contains('mwp-sfe-inline-actions') || el.closest('.mwp-sfe-inline-actions') ); if (hoveringActionBar) { hoverTracker.isProcessing = false; return; } // Get editable elements const editableElements = elementsAtPoint.filter(el => el.dataset.mwpSfeBound === '1' && !el.classList.contains('mwp-sfe-element-active') && !el.closest('[data-mwp-sfe-control]') ); const batchHoverCandidates = filterBatchHoverCandidates( editableElements, e.clientX, e.clientY ); if (batchHoverCandidates.length === 0) { // No elements - hide hover overlay, and (outside batch) the action bar too if (overlayManager) overlayManager.hideHover(); if (!isBatchEditingActive()) { actionBar.hide(); } hoverTracker.lastHoveredElements = []; hoverTracker.currentGroupId = null; hoverTracker.bottommostElement = null; hoverTracker.isProcessing = false; return; } // When a batch editor is active, pending drafts and comment-only elements // are locked - can't switch to them until the current editor is closed. // Lock status is read from the overlay's data-status via getElementStatus(), // so nothing extra is written to the page element itself. if (isBatchEditingActive()) { const isLocked = el => { const st = overlayManager ? overlayManager.getElementStatus(el) : null; return st === 'pending' || st === 'comment-only'; }; const switchableElements = batchHoverCandidates.filter(el => !isLocked(el)); if (switchableElements.length === 0) { // Only locked elements under cursor - hide hover. // Cursor (not-allowed) and pointer-events are CSS-driven via the // element's status overlay (data-status="pending"/"comment-only"). if (overlayManager) overlayManager.hideHover(); hoverTracker.lastHoveredElements = batchHoverCandidates; hoverTracker.currentGroupId = null; hoverTracker.bottommostElement = null; hoverTracker.isProcessing = false; return; } // Switchable elements in view - show hover. // Cursor is handled by CSS on the status overlay / bound element. if (overlayManager) overlayManager.showHover(switchableElements[0]); hoverTracker.lastHoveredElements = switchableElements; hoverTracker.currentGroupId = switchableElements.map(el => el.dataset.mwpSfeUuid).join(','); hoverTracker.bottommostElement = switchableElements[0]; hoverTracker.isProcessing = false; return; } // Find full overlapping group const overlappingGroup = findOverlappingGroup(batchHoverCandidates[0]); const groupId = overlappingGroup.map(el => el.dataset.mwpSfeUuid).join(','); // Check if we're in the same group if (groupId === hoverTracker.currentGroupId) { // Same group - follow the directly hovered element while keeping // the multi-row action bar open for the existing overlap group. const topElement = batchHoverCandidates[0]; if (overlayManager) { overlayManager.showHover(topElement); } if (overlappingGroup.length > 1 && actionBar.activeBar && actionBar.activeBar._multiElements) { actionBar.setMultiElementHoverAnchor(topElement); const focusIndex = overlappingGroup.indexOf(topElement); if (focusIndex !== -1 && focusIndex !== actionBar.activeBar._currentFocusIndex) { const rows = actionBar.activeBar.querySelectorAll('.mwp-sfe-multi-element-row'); rows.forEach((row, idx) => { row.classList.toggle('mwp-sfe-focused', idx === focusIndex); }); actionBar.activeBar._currentFocusIndex = focusIndex; } } hoverTracker.lastHoveredElements = batchHoverCandidates; hoverTracker.isProcessing = false; return; } // New group - show action bar hoverTracker.currentGroupId = groupId; hoverTracker.bottommostElement = overlappingGroup[0]; // First is bottommost hoverTracker.lastHoveredElements = batchHoverCandidates; if (overlappingGroup.length === 1) { // Single element if (overlayManager) overlayManager.showHover(overlappingGroup[0]); actionBar.show( overlappingGroup[0], overlappingGroup[0]._mwpSfeHandlers, overlappingGroup[0]._mwpSfeUuid ); } else { // Multiple overlapping elements - keep the full group, but anchor // the action bar to the exact element under the pointer. if (overlayManager) overlayManager.showHover(batchHoverCandidates[0]); actionBar.showMultiple(overlappingGroup, batchHoverCandidates[0]); } hoverTracker.isProcessing = false; }); }; attachEventListener(element, 'mousemove', mouseMoveHandler, 'mwpSfeMouseMove'); // Global mousemove to detect leaving all elements const globalMouseMoveHandler = function(e) { if (!isInlineUIEnabled()) return; // Suppress hover-state changes while a save is in progress. if (ctx.isSaving) return; // Always update current mouse position globally // This ensures the delayed timeout in the element handler has accurate position data hoverTracker.currentMousePos = { x: e.clientX, y: e.clientY }; if (isUiDragActive()) return; if (actionBar.isPointerInHoverTransferCorridor(e.clientX, e.clientY)) return; const elementsAtPoint = document.elementsFromPoint(e.clientX, e.clientY); const hasEditableElement = elementsAtPoint.some(el => el.dataset.mwpSfeBound === '1'); const hoveringActionBar = elementsAtPoint.some(el => el.classList.contains('mwp-sfe-inline-actions') || el.closest('.mwp-sfe-inline-actions') ); if (!hasEditableElement && !hoveringActionBar && hoverTracker.lastHoveredElements.length > 0) { if (overlayManager) overlayManager.hideHover(); // In batch mode with an active editor (or while the session is still // loading - isEnabled=true but isSessionActive=false), keep the action // bar visible on the active element - only hide the hover overlay. // Mirrors the dual check used in ElementState.markActive and in the // isBatchEditing() helper above. const bm = SFE.BatchEditManager || null; const batchEditing = !!( bm && SFE.Context.activeEditor && ( (typeof bm.isSessionActive === 'function' && bm.isSessionActive()) || (typeof bm.isEnabled === 'function' && bm.isEnabled()) ) ); if (!batchEditing) { actionBar.hide(); } hoverTracker.lastHoveredElements = []; hoverTracker.currentGroupId = null; hoverTracker.bottommostElement = null; } }; // Attach global handler only once - store reference for later cleanup if (!document.body._mwpSfeGlobalMouseMove) { document.body._mwpSfeGlobalMouseMove = globalMouseMoveHandler; document.body.addEventListener('mousemove', globalMouseMoveHandler); } // Track where the latest pointer press started so close-on-click decisions // can be based on interaction origin (mousedown), not click target. if (!document.body._mwpSfeGlobalMouseDown) { document.body._mwpSfeGlobalMouseDown = function(e) { const ctx = SFE.Context || {}; const activeEl = ctx.activeEditor && ctx.activeEditor.element; const startedInActiveEditor = !!(activeEl && activeEl.contains(e.target)); const startedInControl = !!(e.target && e.target.closest && e.target.closest('[data-mwp-sfe-control]')); const startedInEditable = !!(e.target && e.target.closest && e.target.closest('[data-mwp-sfe-bound="1"]')); document.body._mwpSfeMouseDownMeta = { startedInActiveEditor, startedInControl, startedInEditable }; }; document.body.addEventListener('mousedown', document.body._mwpSfeGlobalMouseDown, true); } // Global click handler: in batch mode, clicking outside the active editing // element (and outside plugin controls) should close that editor and keep // changes - mirroring the behavior of switching to another element. if (!document.body._mwpSfeGlobalClick) { const globalClickHandler = function(e) { const ctx = SFE.Context; const body = document.body; // In preview states we preserve the active editor/session and allow // normal page interaction; outside clicks must never auto-close. if ( ctx.isInlineUIEnabled === false || body.classList.contains('mwp-sfe-active-preview') || body.classList.contains('mwp-sfe-preview-mode') ) { return; } // Comment mode and draft preview are locked - only Cancel/Escape can exit. // Block ALL external clicks unconditionally, regardless of batch state. // (Draft editing is also locked but handled below via draftEditState.) if (ctx.activeMode === 'comment' || ctx.activeMode === 'draft') { if (!e.target.closest('[data-mwp-sfe-control]')) { e.preventDefault(); e.stopImmediatePropagation(); } return; } // Draft editing is also locked (activeEditor IS set in this case, but // draftEditState distinguishes it from a regular editor). if (ctx.draftEditState) return; // Never auto-close the active editor while a save is already in flight. if (ctx.isSaving) return; // Below: batch-only logic - clicking outside active editor saves and closes. const bm = SFE.BatchEditManager || null; if (!bm || !bm.isSessionActive()) return; if (!ctx.activeEditor) return; // Ignore clicks on plugin controls (toolbar, action bar, overlays, etc.) if (e.target.closest('[data-mwp-sfe-control]')) return; // Ignore clicks inside the element currently being edited const activeEl = ctx.activeEditor.element; if (activeEl && activeEl.contains(e.target)) return; // Auto-close is origin-based: only close when the interaction STARTED // outside editor/UI/editable regions. This prevents drag-select releases // from link/file controls from being misclassified as outside clicks. const downMeta = document.body._mwpSfeMouseDownMeta || null; if ( downMeta && ( downMeta.startedInActiveEditor || downMeta.startedInControl || downMeta.startedInEditable ) ) { return; } // Ignore clicks on other editable elements - their own click handler // will call startOrSwitchEditing which switches the active editor. if (e.target.closest('[data-mwp-sfe-bound="1"]')) return; // Clicked outside everything - save changes accumulated so far and // close the editor (restoreOriginal = false → keep edits in dirty map). const didClose = SFE.closeInPlaceEditor( ctx.activeEditor, false, { closeReason: 'outside-click' } ); if (didClose === false) { e.preventDefault(); e.stopImmediatePropagation(); } }; document.body._mwpSfeGlobalClick = globalClickHandler; // Use capture so it fires before element click handlers document.body.addEventListener('click', globalClickHandler, true); } // Dedicated position tracker on document capture phase - fires before any // stopPropagation in the editor tree, keeping currentMousePos accurate // even when the editor absorbs mousemove events during active editing. if (!document._mwpSfePosTracker) { document._mwpSfePosTracker = (e) => { hoverTracker.currentMousePos = { x: e.clientX, y: e.clientY }; }; document.addEventListener('mousemove', document._mwpSfePosTracker, true); } // Click listener const clickHandler = function(e) { if (!isInlineUIEnabled()) return; // Ignore clicks on plugin controls (toolbar, action bar, overlays...) if (e.target.closest('[data-mwp-sfe-control]')) return; // Capture runs from outer -> inner; when a nested editable element was // actually clicked, let its own handler decide and avoid hijacking on // the ancestor. const clickedBound = e.target.closest('[data-mwp-sfe-bound="1"]'); if (clickedBound && clickedBound !== element && element.contains(clickedBound)) { return; } // If this element is the one currently being edited, absorb the click // and stop propagation so ancestor elements (e.g. a Cover block wrapping // a Paragraph block) don't also receive it and try to switch editors. if (element.classList.contains('mwp-sfe-element-active')) { // Media editors should never forward clicks into page/lightbox handlers. if (ctx.activeEditor && ctx.activeEditor.isMediaEditor) { e.preventDefault(); e.stopImmediatePropagation(); return; } // For text/container editors, allow native click/default behavior // (e.g. toggling inside details/accordion blocks). return; } // If this element is an ancestor of the active editor element and the // click landed inside the active editor's DOM subtree, the visible area // at the click coordinates is occupied by the active editor - don't // treat this as a click on the outer (ancestor) element. // Example: clicking inside a Paragraph editor that lives inside a Cover // block should not switch the active editor to the Cover block. const _ctx = SFE.Context; if (_ctx.activeEditor && _ctx.activeEditor.element) { const _activeEl = _ctx.activeEditor.element; if ( element !== _activeEl && element.contains(_activeEl) && _activeEl.contains(e.target) ) { e.stopPropagation(); return; } } const batchManager = SFE.BatchEditManager || null; const batchSessionActive = ( batchManager && typeof batchManager.isSessionActive === 'function' && batchManager.isSessionActive() ); // Block all element-open clicks while a save is in progress. if (ctx && ctx.isSaving) { e.preventDefault(); e.stopImmediatePropagation(); return; } // In single-edit mode, prevent interruption while another element is active. if (!batchSessionActive && document.querySelector('.mwp-sfe-element-active')) { e.preventDefault(); e.stopImmediatePropagation(); return; } // Comment mode and draft mode (preview or editing) must only be exited via // Cancel or Escape - never by clicking another element. // activeMode === 'draft' covers draft PREVIEW (draftEditState is null then). // draftEditState covers draft EDITING (activeMode is cleared by openEditorInternal). if (ctx.activeMode === 'comment' || ctx.activeMode === 'draft' || ctx.draftEditState) { e.preventDefault(); e.stopPropagation(); return; } e.preventDefault(); e.stopImmediatePropagation(); // Block pending draft and comment-only interaction when another editor is active // in a batch session - the user must close the active editor first. // Lock status is read from the overlay's data-status, not the element itself. if (batchSessionActive && SFE.Context.activeEditor) { const _status = overlayManager ? overlayManager.getElementStatus(element) : null; if (_status === 'pending' || _status === 'comment-only') return; } const isPending = element.classList.contains('mwp-sfe-status-pending'); if (isPending) { // Always call loadPendingDraft directly - never route through startEditing/ // batchManager for drafts, as the batch manager ignores the 'draft' mode // and would try to open a regular editor instead. const loadDraft = SFE.DraftManager?.loadPendingDraft || SFE.loadPendingDraft; if (typeof loadDraft === 'function') { loadDraft(null, element, uuid, sortedHandlers); } } else { const editHandler = sortedHandlers.find(h => h.capability === 'edit'); const commentHandler = sortedHandlers.find(h => h.capability === 'comment'); if (editHandler) { ctx.activeMode = 'edit'; SFE.startEditing(element, editHandler, uuid, e, false, ctx.activeMode); } else if (commentHandler) { // Comment-only element: Start commenting directly const bar = actionBar.show(element, sortedHandlers, uuid); if (bar) SFE.startCommenting(bar, element, sortedHandlers, uuid); } } }; // Clear mode ctx.activeMode = null; attachEventListener(element, 'click', clickHandler, 'mwpSfeClick', true); // Store cleanup function on element for potential manual cleanup element._mwpSfeCleanup = () => { removeEventListener(element, 'mousemove', 'mwpSfeMouseMove'); // No need to remove global handler as it's shared }; } SFE.HoverManager = { attachActionBarToElement, findOverlappingGroup }; })(); import { Tooltip, Box } from '@elementor/ui'; import { __ } from '@wordpress/i18n'; import * as PropTypes from 'prop-types'; export const UpgradeTooltip = ( { children, disabled = false, tooltip = false, ...props } ) => { if ( disabled && tooltip ) { return ( { children } ); } return children; }; UpgradeTooltip.propTypes = { children: PropTypes.node.isRequired, disabled: PropTypes.bool, tooltip: PropTypes.bool, }; The 5 Best Chatbot Use Cases in Healthcare – Dlytecollections
The 5 Best Chatbot Use Cases in Healthcare

The 5 Best Chatbot Use Cases in Healthcare

Top 10 Chatbots in Healthcare: Insights & Use Cases in 2023

chatbot use cases in healthcare

The IAB develops industry standards to support categorization in the digital advertising industry; 42Matters labeled apps using these standards40. Relevant apps on the iOS Apple store were identified; then, the Google Play store was searched with the exclusion of any apps that were also available on iOS, to eliminate duplicates. Through chatbots (and their technical functions), we can have only a very limited view of medical knowledge. The ‘rigid’ and formal systems of chatbots, even with the ML bend, are locked in certain a priori models of calculation. Expertise generally requires the intersubjective circulation of knowledge, that is, a pool of dynamic knowledge and intersubjective criticism of data, knowledge and processes (e.g. Prior 2003; Collins and Evans 2007). Therefore, AI technologies (e.g. chatbots) should not be evaluated on the same level as human beings.

Trained in cognitive behavioral therapy (CBT), it helps users through simple conversations. Wysa AI Coach also employs evidence-based techniques like CBT, DBT, meditation, breathing, yoga, motivational chatbot use cases in healthcare interviewing, and micro-actions to help patients build mental resilience skills. Telecom chatbots have modified the way communication service providers interact with customers.

Provide medical information

Another app is Weight Mentor, which provides self-help motivation for weight loss maintenance and allows for open conversation without being affected by emotions [47]. Health Hero (Health Hero, Inc), Tasteful Bot (Facebook, Inc), Forksy (Facebook, Inc), and SLOWbot (iaso heath, Inc) guide users to make informed decisions on food choices to change unhealthy eating habits [48,49]. The effectiveness of these apps cannot be concluded, as a more rigorous analysis of the development, evaluation, and implementation is required.

chatbot use cases in healthcare

Based on the information they provided, we identified 7 use cases for information dissemination (see Figure 2). Today, chatbots offer diagnosis of symptoms, mental healthcare consultation, nutrition facts and tracking, and more. For example, in 2020 WhatsApp collaborated with the World Health Organization (WHO) to make a chatbot service that answers users’ questions on COVID-19. Informative, conversational, and prescriptive healthcare chatbots can be built into messaging services like Facebook Messenger, Whatsapp, or Telegram or come as standalone apps. Acropolium has delivered a range of bespoke solutions and provided consulting services for the medical industry. The insights we’ll share in this post come directly from our experience in healthcare software development and reflect our knowledge of the algorithms commonly used in chatbots.

Scheduling appointments and reminders

For example, in the field of psychology, so-called ‘script theory’ provided a formal framework for knowledge (Fischer and Lam 2016). Thus, as a formal model that was already in use, it was relatively easy to turn it into algorithmic form. These expert systems were part of the automated decision-making (ADM) process, that is, a process completely devoid of human involvement, which makes final decisions on the basis of the data it receives (European Commission 2018, p. 20). Conversely, health consultation chatbots are partially automated proactive decision-making agents that guide the actions of healthcare personnel. From enhancing patient experience and helping medical professionals, to improving healthcare processes and unlocking actionable insights, medical or healthcare chatbots can be used for achieving various objectives. Poised to change the way payers, medical care providers, and patients interact with each other, medical chatbots are one of the most matured and influential AI-powered healthcare solutions developed so far.

chatbot use cases in healthcare

From collecting patient information to taking into account their history and recording their symptoms, data is essential. It provides a comprehensive overview of the patient before proceeding with the treatment. Chatbots will not replace doctors in medicine anytime soon, but they will likely become indispensable tools in patient care as AI continues to undergo major breakthroughs. The healthcare chatbot’s market size was valued at around $211 million as of 2022. With a CAGR of 15% over the upcoming couple of years, the healthcare chatbot market growth is astonishing. Chatbots like Docus.ai can even validate these diagnoses with top healthcare professionals from the US and Europe.

We identified 78 healthbot apps commercially available on the Google Play and Apple iOS stores. Healthbot apps are being used across 33 countries, including some locations with more limited penetration of smartphones and 3G connectivity. The healthbots serve a range of functions including the provision of health education, assessment of symptoms, and assistance with tasks such as scheduling. Currently, most bots available on app stores are patient-facing and focus on the areas of primary care and mental health. Only six (8%) of apps included in the review had a theoretical/therapeutic underpinning for their approach. Two-thirds of the apps contained features to personalize the app content to each user based on data collected from them.

  • This shows that some topics may be embarrassing for patients to discuss face-to-face with their doctor.
  • After the request is understood, the requested actions are performed, and the data of interest are retrieved from the database or external sources [15].
  • Find out where your bottlenecks are and formulate what you’re planning to achieve by adding a chatbot to your system.
  • You probably want to offer customer service for your clients constantly, but that takes a lot of personnel and resources.

Projections indicate that the number of voice chatbots is expected to exceed 8 billion by 2023. But, these aren’t all the ways you can use your bots as there are hundreds of those depending on your company’s needs. This way, you will get more usage out of it and have more tasks taken off your shoulders. And, in the long run, you will be much happier with your investment seeing the great results that the bot brings your company.

These categories are not exclusive, as chatbots may possess multiple characteristics, making the process more variable. Textbox 1 describes some examples of the recommended apps for each type of chatbot but are not limited to the ones specified. Chatbots ask patients about their current health issue, find matching physicians and dentists, provide available time slots, and can schedule, reschedule, and delete appointments for patients.

How Americans View Use of AI in Health Care and Medicine by Doctors and Other Providers – Pew Research Center

How Americans View Use of AI in Health Care and Medicine by Doctors and Other Providers.

Posted: Wed, 22 Feb 2023 08:00:00 GMT [source]

Decreased wait times in accessing health care services have been found to correlate with improved patient outcomes and satisfaction [59-61]. The automated chatbot, Quro (Quro Medical, Inc), provides presynopsis based on symptoms and history to predict user conditions (average precision approximately 0.82) without a form-based data entry system [25]. In addition to diagnosis, Buoy Health (Buoy Health, Inc) assists users in identifying the cause of their illness and provides medical advice [26]. Another chatbot designed by Harshitha et al [27] uses dialog flow to provide an initial analysis of breast cancer symptoms. It has been proven to be 95% accurate in differentiating between normal and cancerous images. A study of 3 mobile app–based chatbot symptom checkers, Babylon (Babylon Health, Inc), Your.md (Healthily, Inc), and Ada (Ada, Inc), indicated that sensitivity remained low at 33% for the detection of head and neck cancer [28].

Based on Gartner’s research, there is a projected 40% increase in the adoption of chatbot technology, with 38% of organizations planning to implement chatbots within the next two years. Join Master of Code on this journey to discover the boundless potential of chatbots and how they are reshaping the way we interact with technology and information. While healthbots have a potential role in the future of healthcare, our understanding of how they should be developed for different settings and applied in practice is limited. There has been one systematic review of commercially available apps; this review focused on features and content of healthbots that supported dementia patients and their caregivers34. To our knowledge, no review has been published examining the landscape of commercially available and consumer-facing healthbots across all health domains and characterized the NLP system design of such apps.

chatbot use cases in healthcare

They can also aid in customer or patient education and provide data about treatments, medications, and other aspects of healthcare. In this article, we share our perspective on how the contemporary chatbot technology can be extended towards a more intelligent, engaging, context-aware, and personalized agent. Furthermore, we underline the importance of contextualization, personalization, and abstraction1 with the use of domain-specific as well as patient-specific knowledge, and present examples of three healthcare applications. If you wish to see how a healthcare chatbot suits your medical services, take a detailed demo with our in-house chatbot experts. Different types of chatbots in healthcare require different advantages, and the strengths of these algorithms are dependent on the training data they are provided.

Which algorithm is used for healthcare chatbot?

It just takes a minute to gauge the details and respond to them, thereby reducing their wait time and expediting the process. Ever since the introduction of chatbots, health professionals are realizing how chatbots can improve healthcare. Let’s dive a little deeper and talk about a couple of the top chatbot use cases in healthcare. It features many tools, such as online doctor consultations, appointment settings, and, most importantly, a symptom checker.

chatbot use cases in healthcare

It revolutionizes the quality of patient experience by attending to your patient’s needs instantly. Emerging trends like increasing service demand, shifting focus towards 360-degree wellbeing, and rising costs of quality care are propelling the adoption of new technologies in the healthcare sector. By harnessing the power of Generative Conversational AI, medical institutions are rewriting the rules of patient engagement. We are witnessing a rapid upsurge in the development and implementation of various AI solutions in the healthcare sector. The use of chatbots in health care presents a novel set of moral and ethical challenges that must be addressed for the public to fully embrace this technology. Issues to consider are privacy or confidentiality, informed consent, and fairness.

AI and ML have advanced at an impressive rate and have revealed the potential of chatbots in health care and clinical settings. AI technology outperforms humans in terms of image recognition, risk stratification, improved processing, and 24/7 assistance with data and analysis. However, there is no machine substitute for higher-level interactions, critical thinking, and ambiguity [93]. Chatbots create added complexity that must be identified, addressed, and mitigated before their universal adoption in health care. Design-wise, ease of development, ease of access, and platform penetration have likely contributed to the prevalence of web-based and social media chatbots. For example, the built-in modules for chatbot design on social media platforms allow for fast and easy development.

Family history collection is a proven way of easily accessing the genetic disposition of developing cancer to inform risk-stratified decision-making, clinical decisions, and cancer prevention [63]. The web-based chatbot ItRuns (ItRunsInMyFamily) gathers family history information at the population level to determine the risk of hereditary cancer [29]. We have yet to find a chatbot that incorporates deep learning to process large and complex data sets at a cellular level.

chatbot use cases in healthcare

In combination with wearable technology and affordable software, chatbots have great potential to affect patient monitoring solutions. With the rapidly increasing applications of chatbots in health care, this section will explore several areas of development and innovation in cancer care. Various examples of current chatbots provided below will illustrate their ability to tackle the triple aim of health care. The specific use case of chatbots in oncology with examples of actual products and proposed designs are outlined in Table 1. Cancer has become a major health crisis and is the second leading cause of death in the United States [18]. The exponentially increasing number of patients with cancer each year may be because of a combination of carcinogens in the environment and improved quality of care.

These bots can also play a critical role in making relevant healthcare information accessible to the right stakeholders, at the right time. The prevalence of cancer is increasing along with the number of survivors of cancer, partly because of improved treatment techniques and early detection [77]. A number of these individuals require support after hospitalization or treatment periods. Maintaining autonomy and living in a self-sustaining way within their home environment is especially important for older populations [79]. Implementation of chatbots may address some of these concerns, such as reducing the burden on the health care system and supporting independent living. Differences in language even within the same country, differences in local information and guidelines, and differences in popularity of different social media platforms across countries may limit the scope of such efforts.

Leave a Reply

Your email address will not be published. Required fields are makes.

GET HELP

COMPANY

+1 832 929 6235

info@dlytecollections.com 

9001 Jones Road, Houston Texas USA

Copyright © 2023. All rights reserved