Map deformation for anatomical mapping

Abstract

The name of the invention of the present disclosure is "map morphing for anatomical mapping". The invention provides a mapping engine. The mapping engine operates to generate an initial visualization of the anatomical structure on the display during the ablation procedure and to generate the catheter at the average location as a profile below the surface within the initial visualization. The mapping engine operates to deform a region of the surface of the initial visualization to the average location to generate a temporary visualization exposing at least a portion of the catheter and to determine whether to maintain the temporary visualization based on ablation events of the ablation procedure.

Description

Technical Field

[0001] The present invention relates to anatomical mapping. More specifically, the present invention relates to the deformation of mapping diagrams for anatomical mapping. Background Art

[0002] Currently, catheter-based radiofrequency (RF) ablation for pulmonary vein isolation is the first-line treatment for atrial fibrillation (AF). RF ablation requires a very accurate mapping diagram.

[0003] For example, during an electrophysiology (EP) procedure, an anatomical mapping diagram of a heart chamber is generated. Fast anatomical mapping (FAM) is an algorithm for establishing such anatomical mapping diagrams based on electrical signals captured by a catheter on the myocardium. The anatomical mapping diagram is used to guide a physician to a desired ablation site. As part of constructing the anatomical mapping diagram (for example, an aspect of generating the anatomical mapping diagram of FAM), technicians sometimes may modify the volume of FAM by performing a manual, time-consuming shaving process for various reasons, including, for example, to present a more anatomically accurate representation, to reveal annotations or anatomical points of interest that may have been obscured by the "shell" of FAM. As part of the EP procedure, labels may be placed throughout the anatomical mapping diagram according to different actions of a physician or operator. For example, corresponding to each ablation event, a label is placed at the ablation site within the anatomical mapping diagram.

[0004] Generally, when FAM continuously collects a volume (for example, when the catheter moves and captures the maximum size, such as when tissue is pushed), the anatomical mapping diagram of FAM may become too large in size. For example, conventional mapping techniques capture entire voxels when matching a threshold. Additional factors for FAM to continuously collect a volume include the continuous acquisition of all cardiac cycles, the patient's respiration, voxel size discretization, and bulging (such as pushing tissue with a catheter). Therefore, during the EP procedure, the depiction of the catheter, labels, and other features may be invisible on the anatomical mapping diagram.

[0005] Shaving is the action of removing voxels (from a volume). After removing (shaving) the voxels, the FAM surface is locally reconstructed again to reflect the shaving effect. Shaving modifies the input (which is voxels) of the FAM reconstruction algorithm (removing a part of it). When used too extensively, shaving can result in an overshaving effect. For example, too much shaving on the input can result in floating catheters and labels, deformed mapping diagrams, and the removal of desired features.

[0006] However, during the EP procedure, a physician may generally have difficulty understanding the relative position between the catheter and the ablation site (for example, as shown by (Annotated). In this regard, conventional mapping techniques can hide the ablation tip of the catheter (i.e., its depiction), for example, through reconstruction during ablation, thereby hindering the physician's position determination, distance estimation, and ablation decision. Similarly, the physician may have difficulty understanding the true tissue location (e.g., in real time and at the site).

[0007] There is a great need for a solution for a faster and more accurate mapping protocol that includes a transformation of the output of the FAM to reveal the catheter, tags, and other hidden features, provides more accurate positioning, and shows the ablation tip. SUMMARY OF THE INVENTION

[0008] According to one or more embodiments, a mapping engine is provided. The mapping engine operates to generate an initial visualization of an anatomical structure on a display during an ablation procedure and generate a catheter at an average position as a contour below a surface within the initial visualization. The mapping engine operates to deform an area of the surface of the initial visualization to generate a temporary visualization, thereby exposing at least a portion of the catheter, and determine whether to maintain the temporary visualization based on ablation events of the ablation procedure.

[0009] According to one or more embodiments, a mapping engine is provided. The mapping engine operates to generate an initial visualization of an anatomical structure that includes one or more tags hidden below a surface of the initial visualization, and deform an area of the surface to expose the one or more tags. The mapping engine operates to deform an area of the surface of each of the one or more tags by automatically selecting a surface point closest to the tag among the one or more tags, calculating a distance between the surface point and the tag, and determining an area of the surface to be deformed based on the distance. The mapping engine operates to produce a temporary visualization on the display based on the deformation of the area.

[0010] According to one or more embodiments, a mapping engine is provided. The mapping engine operates to generate an initial visualization of an anatomical structure on a display, the initial visualization including one or more features hidden below a surface of the initial visualization; and identify a subset of the one or more features according to a set of parameters. The mapping engine operates a deformation algorithm of the mapping engine to deform the surface of the initial visualization to expose the subset of the one or more features by changing one or more areas of the surface corresponding to the subset of the one or more tags.

[0011] According to one or more embodiments, the above exemplary mapping engine embodiments can be implemented as a method, apparatus, system, and / or computer program product. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] A more detailed understanding can be obtained from the following specific embodiments provided by way of example in conjunction with the accompanying drawings, in which like reference numerals in the drawings indicate like elements, and in which:

[0013] Figure 1 depicts an example catheter-based electrophysiological mapping and ablation system in accordance with one or more embodiments;

[0014] Figure 2 is a block diagram of an example system for remotely monitoring and transmitting biometric data in accordance with one or more embodiments;

[0015] Figure 3 is a system diagram of an example computing environment in communication with a network in accordance with one or more embodiments;

[0016] Figure 4 is a block diagram of an example apparatus that can implement one or more features of the present disclosure in accordance with one or more embodiments;

[0017] Figure 5 describes a method in accordance with one or more embodiments;

[0018] Figure 6 describes a visualization in accordance with one or more embodiments;

[0019] Figure 7 depicts a set of diagrams providing an example deformation progression in accordance with one or more embodiments;

[0020] Figure 8 depicts a set of diagrams providing an example deformation progression in accordance with one or more embodiments;

[0021] Figure 9 depicts a set of diagrams providing an example of a deformation process in accordance with one or more embodiments;

[0022] Figure 10 describes a visualization in accordance with one or more embodiments;

[0023] Figure 11 depicts a user interface in accordance with one or more embodiments;

[0024] Figure 12 depicts a method in accordance with one or more embodiments; and

[0025] Figures 13 to 23 depicts a user interface presenting a visualization progression in accordance with one or more embodiments. Detailed Description

[0026] This disclosure relates to a method and / or system for anatomical mapping. More specifically, the method and / or system relates to a mapping engine. The mapping engine is processor-executable code or software that necessarily derives from processing operations performed and used by a medical device equipped to perform and use anatomical mapping and the processing hardware of the medical device. The mapping engine implements anatomical mapping to generate a mapping graph. The mapping engine can perform mapping graph deformation on the mapping graph. For ease of explanation, the mapping engine is described herein with respect to mapping the heart. However, any anatomical structure, body part, organ, or portion thereof can be a target for mapping by the mapping engine described herein.

[0027] According to one or more embodiments, the mapping engine implements anatomical mapping to generate a mapping graph of the heart that includes the endocardial surface of the left atrium (LA). The mapping graph can be a three-dimensional (3D) model or a combination of multiple 3D models. The mapping engine can generate and edit in real time a mapping graph of the heart (e.g., provide real-time or post-processed mapping graph deformation or shape change to the endocardial surface of the 3D model) during an EP procedure (e.g., ablation procedure). As an example, the mapping engine can deform an initially visualized surface (e.g., the output of FAM) to expose tags, catheters, and / or otherwise hidden points, thereby improving the operation and results of anatomical mapping. Thus, the mapping engine improves conventional mapping techniques by reducing clutter on the mapping graph and providing a clear and accurate depiction of tags, catheters, and / or catheter points within the mapping graph. Additionally, one or more advantages, technical effects, and / or benefits of the mapping engine can include providing a mechanism for understanding the relative positions between catheters and ablation sites that would otherwise be unavailable due to limitations of conventional techniques.

[0028] Reference Figure 1 , which shows an example system shown as system 10 (e.g., a medical device equipped and / or a catheter-based electrophysiological mapping and ablation system), in which one or more features of the subject matter herein can be implemented according to one or more embodiments. All or part of system 100 can be used to collect information (e.g., biometric data and / or training datasets and / or for implementation (e.g., mapping engine 101), as described herein. In some examples, mapping engine 101 is implemented using processor-executable code or software that is stored on the memory of system 10 and necessarily derives from the processing operations of system 10 or the processing hardware of the system. As described herein, mapping engine 101 can generate a mapping graph (also referred to as visualization) and provide mapping graph deformation or shape change to the mapping graph.

[0029] System 1 shows recorder 11, heart 12, catheter 14, model or anatomical mapping Figure 20 、electrogram Figure 21, spine 22, patient 23, physician 24 (which represents any medical professional, technician, clinician, operator, clinical support specialist, clinical account specialist, healthcare provider, etc.), positioning pad 25, one or more electrodes 26, display device 27, distal end 28, sensor 29, coil 32, patient interface unit (PIU) 30, electrode skin patch 38, ablation energy generator 50, and workstation 55. It should also be noted that each element and / or item of system 10 represents one or more of that element and / or that item. Figure 1 The exemplary implementation of system 10 shown herein embodies the embodiments disclosed herein. The embodiments disclosed in the present invention can be similarly applied using other system components and settings. Additionally, system 10 may include additional components, such as elements for sensing electrical activity, wired or wireless connectors, processing and display devices, or other components.

[0030] System 10 includes a plurality of catheters 14 that are inserted by physician 24 through the patient's vascular system via the skin into the chambers or vascular structures of the heart 12. Generally, a delivery sheath catheter is inserted into the left atrium or right atrium near the desired location in the heart 12. Then, a plurality of catheters can be inserted into the delivery sheath catheter to reach the desired location. The plurality of catheters 14 may include a catheter dedicated to sensing intracardiac electrogram (IEGM) signals, a catheter dedicated to ablation, and / or a catheter dedicated to both sensing and ablation. An exemplary catheter 14 configured for sensing IEGM is shown herein. Physician 24 brings the distal end 28 of catheter 14 into contact with the heart wall for sensing the target site in the heart 12. For ablation, physician 24 similarly brings the distal end of the ablation catheter to the target site for ablation.

[0031] Catheter 14 is an exemplary catheter that includes at least one (and preferably multiple) electrodes 26 that are optionally disposed over a plurality of ridges 22 at the distal end 28 and are configured to sense IEGM signals. Additionally, catheter 14 may also include a sensor 29 that is embedded in or near the distal end 28 for tracking the position and orientation of the distal end 28. Optionally and preferably, the position sensor 29 is a magnetic-based position sensor that includes three magnetic coils for sensing 3D position and orientation. According to one or more embodiments, the shape and parameters of catheter 14 vary based on whether catheter 14 is for diagnostic or ablation purposes, the type of arrhythmia, the patient's anatomy, and other factors that affect catheter maneuverability (e.g., the ability to touch without bending the surface and tracked portion of catheter 14). The shape and parameters of catheter 14 also affect the accuracy of the anatomical mapping. Large spherical single-shot catheters that can ablate pulmonary veins within seconds have become popular, but require guidance from fluoroscopy, CT / MRI, or additional mapping catheters. The operation of the mapping engine 101 addresses the drawbacks of catheter 14 by performing mapping deformation to reveal items of interest (such as catheter 14 during an EP procedure) or labels that might otherwise be hidden, as described herein.

[0032] Sensor 29 (e.g., a location- or magnetic-based sensor) may operate in conjunction with a position pad 25 that includes a plurality of magnetic coils 32 configured to generate a magnetic field within a predefined workspace. The real-time position of the distal end 28 of catheter 14 can be tracked based on the magnetic field generated by position pad 25 and sensed by sensor 29. Details of magnetic-based position sensing techniques are described in U.S. Pat. Nos. 5,539,199, 5,443,489, 5,558,091, 6,172,499, 6,239,724, 6,332,089, 6,484,118, 6,618,612, 6,690,963, 6,788,967, and 6,892,091.

[0033] System 10 includes one or more electrode patches 38 that are positioned to contact the skin of patient 23 to establish a position reference for impedance-based tracking of position pad 25 and electrodes 26. For impedance-based tracking, current is directed toward electrodes 26 and sensed at patches 38 (e.g., electrode skin patches) such that the position of each electrode can be triangulated via patches 38. Details of impedance-based position tracking techniques are described in U.S. Pat. Nos. 7,536,218, 7,756,576, 7,848,787, 7,869,865, and 8,456,182, which are incorporated herein by reference.

[0034] Recorder 11 displays the electrogram captured by electrode 18 (e.g., a surface electrocardiogram (ECG) electrode) Figure 21 and the intracardiac electrogram (IEGM) captured by electrode 26 of catheter 14. Recorder 11 may include pacing capabilities for pacing the heart rhythm and / or may be electrically connected to an independent pacemaker.

[0035] System 10 may include an ablation energy generator 50 adapted to conduct ablation energy to one or more of the electrodes 26 at the distal end 28 of catheter 14 configured for ablation. The energy generated by ablation energy generator 50 may include, but is not limited to, radiofrequency (RF) energy or pulsed field ablation (PFA) energy (including unipolar or bipolar high voltage DC pulses that may be used to effect irreversible electroporation (IRE)), or combinations thereof.

[0036] PIU 30 is an interface configured to establish electrical connectivity between the catheter, electrophysiology equipment, power supply, and workstation 55 for controlling the operation of system 10. The electrophysiology equipment of system 10 may include, for example, a plurality of catheters 14, position pads 25, surface ECG electrodes 18, electrode patches 38, ablation energy generator 50, and recorder 11. Optionally and preferably, PIU 30 additionally includes processing capabilities for performing real-time calculations of the position of the catheter and for performing ECG calculations.

[0037] Workstation 55 includes a memory, a processor unit with a memory or storage device in which appropriate operating software is loaded, and user interface capabilities (e.g., the memory or storage device of workstation 55 stores a mapping engine 101 and the processor unit of workstation 55 executes the mapping engine 101). Workstation 55 (e.g., by utilizing the mapping engine 101) may provide a plurality of functions, optionally including: performing three-dimensional (3D) modeling of the endocardial anatomy and rendering the model or anatomical map Figure 20 (e.g., visualizing) for display on display device 27; on display device 27, displaying, as representative visual markers or images superimposed on the rendered anatomical map Figure 20 the activation sequence (or other data) compiled from the recorded electrograms Figure 21 ; displaying the real-time position and orientation of a plurality of catheters within the heart chambers; and on display device 27, displaying the sites of interest (e.g., where ablation energy has been applied). An article of commerce embodying the elements of system 10 may be purchased as the CARTOTM 3 system from Biosense Webster, Inc., 31A Technology Drive, Irvine, CA 92618. It should be noted that modeling the endocardial anatomy in 3D may include generating its surface as a triangular mesh.

[0038] For example, system 10 may be part of a surgical system (e.g., a system sold by Biosense Webster) that is configured to obtain biometric data (e.g., anatomical and electrical measurements of a patient's organ such as heart 12, as described herein) and perform a cardiac ablation procedure. More specifically, treatment of cardiac conditions such as cardiac arrhythmias typically requires obtaining a detailed map of cardiac tissue, chambers, veins, arteries, and / or electrical pathways. For example, a prerequisite for successful catheter ablation is that the cause of the arrhythmia is accurately located within the chambers of heart 12. Such localization can be accomplished via an electrophysiological study during which electrical potentials are detected and spatially resolved using a mapping catheter (e.g., catheter 14) introduced into the chambers of heart 12. This electrophysiological study (so-called electroanatomical mapping, as described herein according to one or more embodiments of mapping engine 101) thus provides 3D mapping data that can be displayed on display device 27. In many cases, the mapping function (e.g., via mapping engine 101) and the treatment function (e.g., ablation) are provided by a single catheter or a set of catheters such that the mapping catheter also operates as a treatment catheter simultaneously.

[0039]

[0039] Figure 2 is a block diagram of an example system 100 for remotely monitoring and transmitting biometric data (e.g., patient biometrics). In Figure 2 the example shown, system 100 includes a patient biometric monitoring and processing device 102 associated with patient 104, a local computing device 106, a remote computing system 108, a first network 110, a patient biometric sensor 112, a processor 114, a user input (UI) sensor 116, a memory 118, a second network 120, and a transmitter-receiver (i.e., transceiver) 122.

[0040] According to one or more embodiments, the patient biometric monitoring and processing device 102 may be a device that is inside the patient's body (e.g., subcutaneously implantable), such as Figure 1 catheter 14. The patient biometric monitoring and processing device 102 can be inserted into the patient's body via any suitable means, including oral injection, surgical insertion via a vein or artery, an endoscopic procedure, or a laparoscopic procedure.

[0041] According to one or more embodiments, the patient biometric monitoring and processing device 102 may be a device that is outside the patient's body, such as Figure 1The electrode patch 38. For example, as described in more detail below, the patient biometric monitoring and processing device 102 may include an attachable patch (e.g., which is attached to the patient's skin). The monitoring and processing device 102 may also include a catheter, a probe, a blood pressure cuff, a weighing scale, a bracelet or a smartwatch biometric tracker, a glucose monitor, a continuous positive airway pressure (CPAP) machine, or almost any device that can provide input related to the patient's health or biometrics.

[0042] According to one or more embodiments, the patient biometric monitoring and processing device 102 may include both components inside the patient and components outside the patient.

[0043] Figure 2 A single patient biometric monitoring and processing device 102 is shown. However, an exemplary system may include multiple patient biometric monitoring and processing devices. The patient biometric monitoring and processing device may communicate with one or more other patient biometric monitoring and processing devices. Additionally or alternatively, the patient biometric monitoring and processing device may communicate with the network 110.

[0044] One or more patient biometric monitoring and processing devices 102 may acquire biometric data (e.g., patient biometrics, such as electrical signals, blood pressure, temperature, blood glucose level, or other biometric data), and receive at least a portion of the biometric data representing the acquired patient biometrics and additional information associated with the acquired patient biometrics from one or more other monitoring and processing devices 102. The additional information may be, for example, diagnostic information and / or additional information obtained from additional devices such as wearable devices. Each patient biometric monitoring and processing device 102 may process data, including its own biometric data and the data received from one or more other patient biometric monitoring and processing devices 102.

[0045] Biometric data (e.g., patient biometrics, patient data, or patient biometric data) may include one or more of local activation time (LAT), electrical activity, topology, bipolar mapping, reference activity, ventricular activity, dominant frequency, impedance, or other data. The LAT may be a time point corresponding to a threshold activity of local activation calculated based on a normalized initial starting point. The electrical activity may be any applicable electrical signal that can be measured based on one or more thresholds and sensed and / or enhanced based on signal-to-noise ratio and / or other filters. The topology may correspond to the physical structure of a body part or a portion of a body part and may correspond to changes in the physical structure relative to different parts of the body part or relative to different body parts. The dominant frequency may be a frequency or frequency range prevalent at a portion of a body part and may be different in different parts of the same body part. For example, the dominant frequency of the PV of the heart may be different from the dominant frequency of the right atrium of the same heart. The impedance may be a resistance measurement at a given region of a body part.

[0046] Examples of biometric data include, but are not limited to, patient identification data, intracardiac electrocardiogram (IC ECG) data, bipolar intracardiac reference signals, anatomical and electrical measurements, trajectory information, body surface (BS) ECG data, historical data, brain biometrics, blood pressure data, ultrasound signals, radio signals, audio signals, two-dimensional or three-dimensional image data, blood glucose data, and temperature data. Biometric data can generally be used to monitor, diagnose, and treat any number of various diseases, such as cardiovascular diseases (e.g., arrhythmias, cardiomyopathies, and coronary artery diseases) and autoimmune diseases (e.g., type I and type II diabetes). Note that BS ECG data may include data and signals collected from electrodes on the patient's surface, IC ECG data may include data and signals collected from electrodes within the patient's body, and ablation data may include data and signals collected from tissue that has been ablated. Additionally, BS ECG data, IC ECG data, and ablation data, along with catheter electrode positioning data, may be derived from one or more procedural recordings.

[0047] In Figure 2 the network 110 is an example of a short-range network (e.g., a local area network (LAN) or a personal area network (PAN)). Information may be transmitted between the patient biometric monitoring and processing device 102 and the local computing device 106 via the network 110 using any one of a variety of short-range wireless communication protocols (e.g., Bluetooth, Wi-Fi, Zigbee, Z-Wave, near field communication (NFC), ultraband, Zigbee, or infrared (IR)).

[0048] Network 120 can be a wired network, a wireless network, or include one or more wired and wireless networks. For example, network 120 can be a remote network (e.g., a wide area network (WAN), the Internet, or a cellular network). Information can be sent via network 120 using any one of a variety of remote wireless communication protocols (e.g., TCP / IP, HTTP, 3G, 4G / LTE, or 5G / New Radio).

[0049] The patient biometric monitoring and processing device 102 can include a patient biometric sensor 112, a processor 114, a UI sensor 116, a memory 118, and a transceiver 122. The patient biometric monitoring and processing device 102 can continuously or periodically monitor, store, process, and transmit any number of various biometric data via network 110. Examples of biometric data include electrical signals (e.g., ECG signals and brain biometrics), blood pressure data, blood glucose data, and temperature data. Biometric data can be monitored and transmitted for the treatment of any number of various diseases, such as cardiovascular diseases (e.g., arrhythmia, cardiomyopathy, and coronary artery disease) and autoimmune diseases (e.g., type I and type II diabetes).

[0050] The patient biometric sensor 112 can include, for example, one or more sensors configured to sense the type of biometric data. For example, the patient biometric sensor 112 can include electrodes configured to acquire electrical signals (e.g., cardiac signals, brain signals, or other bioelectrical signals), a temperature sensor, a blood pressure sensor, a blood glucose sensor, a blood oxygen sensor, a pH sensor, an accelerometer, and a microphone.

[0051] As described in more detail below, the patient biometric monitoring and processing device 102 can be an ECG monitor for monitoring the ECG signal of the heart (e.g., heart 12). The patient biometric sensor 112 of the ECG monitor can include one or more electrodes for acquiring the ECG signal. The ECG signal can be used for the treatment of various cardiovascular diseases as well as anatomical mapping.

[0052] The transceiver 122 can include a separate transmitter and receiver. Alternatively, the transceiver 122 can include a transmitter and receiver integrated into a single device.

[0053] The processor 114 can be configured to store the biometric data acquired by the patient biometric sensor 112 in the memory 118, and transmit the biometric data across network 110 via the transmitter of the transceiver 122. Data from one or more other patient biometric monitoring and processing devices 102 can also be received by the receiver of the transceiver 122, as described in more detail herein. As an example, Figure 1The mapping engine 101 is processor-executable code or software that can be stored on a memory 118 (as shown) and executed by a processor 114. As another example, the mapping engine 101 can also be stored on and executed on a local computing device 106 and / or a remote computing system 108. Thus, the mapping engine 101 must originate from the processing operations of the system 100 and the processing hardware of the system.

[0054] According to one or more embodiments, the mapping engine 101 operates to generate an initial visualization of an anatomical structure on a display (e.g., display device 27) during an ablation procedure, and generate a catheter (e.g., catheter 14) at an average position as a contour (e.g., sutured beneath the surface) beneath the surface within the initial visualization. The mapping engine 101 operates to deform an area of the surface of the initial visualization to the average position to generate a temporary visualization exposing at least a portion of the catheter and determine whether to maintain the temporary visualization based on ablation events of the ablation procedure.

[0055] According to one or more embodiments, the mapping engine 101 operates to generate an initial visualization of an anatomical structure on a display (e.g., display device 27) that includes one or more labels hidden beneath the surface of the initial visualization, and deform an area of the surface to expose the one or more labels. The mapping engine 101 operates to deform an area of the surface of each of the one or more labels by automatically selecting a surface point closest to the label among the one or more labels, calculating a distance between the surface point and the label, and determining an area of the surface to be deformed based on the distance. The mapping engine 101 operates to produce a temporary visualization on the display based on the deformation of the area.

[0056] According to one or more embodiments, the mapping engine 101 operates to generate an initial visualization of an anatomical structure on a display that includes one or more features hidden beneath the surface of the initial visualization, and identify a subset of the one or more features according to a set of parameters. The mapping engine 101 operates the deformation algorithm of the mapping engine 101 to deform the surface of the initial visualization by changing one or more areas of the surface corresponding to the subset of the one or more labels to expose the subset of the one or more features.

[0057] According to one or more embodiments, the patient biometric monitoring and processing device 102 includes a UI sensor 116, which, for example, can be a piezoelectric sensor or a capacitive sensor configured to receive user input (such as a tap or a touch). For example, in response to the patient 104 tapping or contacting the surface of the patient biometric monitoring and processing device 102, the UI sensor 116 can be controlled to achieve capacitive coupling. Gesture recognition can be implemented via any of various capacitive types, such as resistive-capacitive, surface capacitive, projected capacitive, surface acoustic wave, piezoelectric, and infrared touch. The capacitive sensor can be disposed at a small area or along the length of the surface such that a tap or touch on the surface activates the monitoring device.

[0058] As described in more detail below, the processor 114 can be configured to selectively respond to different tap patterns (such as a single tap or a double tap) of the capacitive sensor (which can be the UI sensor 116), such that different tasks of the patch (such as data acquisition, storage, or transmission) can be activated based on the detected pattern. In some embodiments, when a gesture is detected, an audible feedback can be given to the user from the patient biometric monitoring and processing device 102.

[0059] The local computing device 106 of the system 100 communicates with the patient biometric monitoring and processing device 102 and can be configured to act as a gateway to the remote computing system 108 via a second network 120. For example, the local computing device 106 can be, for example, a smart phone, a smart watch, a tablet computer, or other portable intelligent devices configured to communicate with other devices via the network 120. Alternatively, the local computing device 106 can be a fixed or stand-alone device, such as a fixed base station including, for example, a modem and / or router capabilities, a desktop computer or a laptop computer using an executable program to transmit information between the patient biometric monitoring and processing device 102 and the remote computing system 108 via the radio module of the PC, or a USB dongle. Biometric data can be transmitted between the local computing device 106 and the patient biometric monitoring and processing device 102 via a short-range wireless network 110, such as a local area network (LAN) (such as a personal area network (PAN)), using short-range wireless technology standards (such as Bluetooth, Wi-Fi, ZigBee, Z-wave, and other short-range wireless standards). In some embodiments, the local computing device 106 can also be configured to display the acquired patient electrical signals and information associated with the acquired patient electrical signals, as described in more detail herein.

[0060] In some embodiments, the remote computing system 108 may be configured to receive at least one of the monitored patient biometrics and information associated with the monitored patient via a network 120 that is a remote network. For example, if the local computing device 106 is a mobile phone, the network 120 may be a wireless cellular network, and information may be transmitted between the local computing device 106 and the remote computing system 108 via a wireless technology standard such as any of the wireless technologies described above. As described in more detail below, the remote computing system 108 may be configured to provide (e.g., visually display and / or auditorily provide) at least one of the patient biometrics and associated information to the physician 24.

[0061] Figure 3 FIG. is a system diagram of an example of a computing environment 200 that communicates with the network 120. In some cases, the computing environment 200 is incorporated into a public cloud computing platform (e.g., Amazon Web Services or Microsoft Azure), a hybrid cloud computing platform (e.g., HP Enterprise OneSphere), or a private cloud computing platform.

[0062] As Figure 3 shown, the computing environment 200 includes a computer system 210, which is an example of a workstation 55 of Figure 1 , a local computing device 106 of Figure 2 , and / or a remote computing system 108 of Figure 2 on which the various embodiments described herein may be implemented. As an example, Figure 1 the mapping engine 101 of

[0063] is processor-executable code or software that may be stored on the system memory 231 (as shown) and executed by the processor 220 such that the mapping engine 101 necessarily originates from the processing operations of the computing environment 200 and the processing hardware of that computing environment. Figure 1 The computer system 210 may perform various functions via a processor 220 that may include one or more processors. The functions may include analyzing the monitored biometric data and associated information and providing (e.g., via the display 266) alerts, additional information, or instructions based on thresholds and parameters determined by the physician or algorithm-driven. The functions may include the operation of the mapping engine 101, such as performing mapping graph deformations for anatomical mapping as described herein. As described in more detail herein, the computer system 210 may be used to provide (e.g., via the display 266) a patient information dashboard to the

[0064] As Figure 3As shown, computer system 210 may include a communication mechanism (e.g., bus 221) or other communication mechanisms for transferring information within computer system 210. Computer system 210 also includes one or more processors 220 coupled to bus 221 for processing information. Processor 220 may include one or more CPUs, GPUs, or any other processors known in the art.

[0065] Computer system 210 also includes a system memory 230 coupled to bus 221 for storing information and instructions to be executed by processor 220. System memory 230 may include computer-readable storage media in the form of volatile and / or non-volatile memory, such as read-only system memory (ROM) 231 and / or random access memory (RAM) 232. System memory RAM 232 may include other dynamic storage devices (e.g., dynamic RAM, static RAM, and synchronous DRAM). System memory ROM 231 may include other static storage devices (e.g., programmable ROM, erasable PROM, and electrically erasable PROM). In addition, system memory 230 may be used to store temporary variables or other intermediate information during the execution of instructions by processor 220. Basic input / output system 233 (BIOS) may contain routines for transferring information between elements within computer system 210 (e.g., during the boot process), and this routine may be stored in system memory ROM 231. RAM 232 may contain data and / or program modules that can be immediately accessed by processor 220 and / or are currently being operated on by this processor. System memory 230 may additionally include, for example, an operating system 234, application programs 235, other program modules 236, and program data 237.

[0066] The illustrated computer system 210 also includes a disk controller 240 that is coupled to bus 221 to control one or more storage devices for storing information and instructions, such as hard disk 241 and removable media drive 242 (e.g., floppy disk drive, optical disk drive, tape drive, and / or solid state drive). Storage devices can be added to computer system 210 using appropriate device interfaces (e.g., Small Computer System Interface (SCSI), Integrated Device Electronics (IDE), Universal Serial Bus (USB), or FireWire).

[0067] The computer system 210 may also include a display controller 265 coupled to the bus 221 to control a monitor or display 266, such as a cathode ray tube (CRT) or a liquid crystal display (LCD), to display information to a computer user. The illustrated computer system 210 includes a user input interface 260 and one or more input devices, such as a keyboard 262 and a pointing device 261, for interacting with a computer user and providing information to the processor 220. The pointing device 261 can be, for example, a mouse, a trackball, or a pointing stick, for transmitting direction information and command selections to the processor 220 and for controlling the movement of a cursor on the display 266. The display 266 may provide a touchscreen interface that may allow input to supplement or replace the communication of direction information and command selections by the pointing device 261 and / or the keyboard 262.

[0068] In response to one or more sequences of one or more instructions contained in a memory, such as the system memory 230, being executed by the processor 220, the computer system 210 may perform part or each of the functions and methods described herein. Such instructions may be read into the system memory 230 from another computer-readable medium, such as a hard disk 241 or a removable media drive 242. The hard disk 241 may contain one or more data repositories and data files used by the embodiments described herein. The data repository contents and data files may be encrypted to enhance security. The processor 220 may also be employed in a multiprocessing arrangement to execute one or more sequences of instructions contained in the system memory 230. In alternative embodiments, hardwired circuitry may be used in place of or in combination with software instructions. Accordingly, the embodiments are not limited to any specific combination of hardware circuitry and software.

[0069] As described above, the computer system 210 may include at least one computer-readable medium or memory for storing instructions programmed according to the embodiments described herein (e.g., embodiments of the mapping engine 101) and for containing the data structures, tables, records, or other data described herein. As used herein, the term computer-readable medium refers to any non-transitory tangible medium that participates in providing instructions to the processor 220 for execution. The computer-readable medium may take many forms, including but not limited to non-volatile media, volatile media, and transmission media. Non-limiting examples of non-volatile media include optical discs, solid state drives, magnetic disks, and magneto-optical discs, such as the hard disk 241 or the removable media drive 242. Non-limiting examples of volatile media include dynamic memory, such as the system memory 230. Non-limiting examples of transmission media include coaxial cables, copper wire, and fiber optics, including the wires that make up the bus 221. The transmission media may also take the form of acoustic or light waves, such as acoustic or light waves generated during radio wave and infrared data communications.

[0070] The computing environment 200 may also include a computer system 210 that operates in a networked environment using a logical connection to a local computing device 106 and one or more other devices, such as a personal computer (laptop or desktop computer), a mobile device (e.g., a patient mobile device), a server, a router, a network PC, a peer device, or other common network nodes, and generally includes many or all of the elements described above with respect to the computer system 210. When used in a networked environment, the computer system 210 may include a modem 272 that is used to establish communications over a network 120 (e.g., the Internet). The modem 272 may be connected to the system bus 221 via a network interface 270 or via another suitable mechanism.

[0071] As Figure 2 and Figure 3 shown, the network 120 can be any network or system known in the art, including the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a direct connection or a series of connections, a cellular telephone network, or any other network or medium capable of facilitating communications between the computer system 210 and other computers (e.g., the local computing device 106).

[0072] Figure 4 is a block diagram of an example device 400 in which one or more features of the present disclosure may be implemented. For example, the device 400 may be the local computing device 106. The device 400 may include, for example, a computer, a gaming device, a handheld device, a set-top box, a television, a mobile phone, or a tablet computer. The device 400 includes a processor 402, a memory 404, a storage device 406, one or more input devices 408, and one or more output devices 410. The device 400 may also optionally include an input driver 412 and an output driver 414. It should be understood that the device 400 may include Figure 4 additional components not shown in

[0073] In various alternatives, the processor 402 includes a central processing unit (CPU), a graphics processing unit (GPU), a CPU and a GPU on the same die, or one or more processor cores, where each processor core may be a CPU or a GPU. In various alternatives, the memory 404 is on the same die as the processor 402 or is located separately from the processor 402. The memory 404 includes volatile or non-volatile memory, such as random access memory (RAM), dynamic RAM, or a cache. As an example, Figure 1The mapping engine 101 is processor-executable code or software that can be stored on the memory 404 (as shown) and executed by the processor 402, such that the mapping engine 101 necessarily results from and is executed by the processing operations and the processing hardware of the example device 400.

[0074] The storage device 406 includes fixed or removable storage devices such as hard disk drives, solid state drives, optical discs, or flash drives. The input device 408 includes, but is not limited to, a keyboard, keypad, touch screen, touchpad, detector, microphone, accelerometer, gyroscope, biometric scanner, or network connector (e.g., a wireless local area network card for transmitting and / or receiving wireless IEEE 802 signals). The output device 410 includes, but is not limited to, a display device, speaker, printer, haptic feedback device, one or more lights, antenna, or network connection (e.g., a wireless local area network card for transmitting and / or receiving wireless IEEE 802 signals).

[0075] The input driver 412 communicates with the processor 402 and the input device 408 and allows the processor 402 to receive input from the input device 408. The output driver 414 communicates with the processor 402 and the output device 410 and allows the processor 402 to send output to the output device 410. Note that the input driver 412 and the output driver 414 are optional components, and if the input driver 412 and the output driver 414 do not exist, the device 400 will operate in the same manner. The output driver 414 includes an acceleration processing device (“APD”) 416 that communicates with a display device represented by the output device 410. The APD 416 receives compute commands and graphics rendering commands from the processor 402, processes those compute and graphics rendering commands, and provides pixel output to the display device for display. As described in further detail below, the APD 416 includes one or more parallel processing units to perform computations according to the single instruction multiple data (“SIMD”) paradigm. Thus, although various functions are described herein as being performed by or in conjunction with the APD 416, in various alternative embodiments, the functions described as being performed by the APD 416 are additionally or alternatively performed by other computing devices having similar capabilities that are not driven by the host processor (e.g., the processor 402) and that provide graphics output to the display device. For example, any processing system expected to perform processing tasks according to the SIMD paradigm may perform the functions described herein. Alternatively, computing systems not expected to perform processing tasks according to the SIMD paradigm are expected to perform the functions described herein.

[0076] Now turning to Figure 5 , a method 500 according to one or more exemplary embodiments is shown. The method 500 is an example set of operations of the mapping engine 101 that necessarily results from and is executed by the following:Figure 1 workstation 55, Figure 2 local computing device 106, Figure 2 remote computing system 108, and / or Figure 4 example device 400. Method 500 illustrates an example of how a mapping engine 101 generates and presents a map of an anatomical structure (e.g., one or more 3D models) and how to edit the map (e.g., provide a map deformation of one or more 3D models) during, for example, an EP procedure (e.g., an ablation procedure).

[0077] Method 500 begins at block 520, where the mapping engine 101 generates an initial visualization. The part of generating the initial visualization includes presenting the initial visualization by a display as described herein.

[0078] The initial visualization is a map of an anatomical structure. For example, the initial visualization can be a 3D rendering of a heart chamber and includes a rendering of a catheter within the heart chamber (in its actual position). The initial visualization can be considered a preview or initial view of the heart chamber, which guides the physician 24 to the desired ablation site, thus facilitating an understanding of the real tissue location. It should be noted that due to the 3D geometry of conventional mapping techniques not accurately showing the depth within the space, size understanding is very difficult using conventional mapping techniques. According to one or more embodiments, one or more hidden features can be below the surface of the initial visualization. Additionally, one or more features can include one or more labels (e.g., ), one or more catheters, one or more inner surface points (e.g., points), one or more ultrasound controls, and / or one or more points. Ultrasound profiles can be obtained from an ultrasound catheter or other devices. Given an ultrasound FAN image, several profiles (continuous lines) can be drawn by a user or by an automatic algorithm, typically to mark the boundaries of some anatomical structures (e.g., the tissue of the left atrium while the ultrasound catheter is over the right atrium). These profiles are in 3D space and each profile is in the plane of the FAN from which it is extracted. The profiles are added to the CARTO mapping as anatomical information, similar to other data like CARTO points. Typically, these profiles reflect the boundaries of the anatomical structure, so it is also expected that the mapping surface passes through these profiles. According to one or more embodiments, the mapping engine 101 generates an initial visualization on a display, where the catheter 14 is shown as a profile below the surface within the initial visualization at an average position.

[0079] Figure 6 Visualizations 601, 602, and 603 of a surface 660 of an anatomical structure according to one or more embodiments are depicted. Each visualization 601, 602, and 603 is an example of an initial visualization generated and displayed by the mapping engine 101.

[0080] The visualization 601 can be an example of an initial visualization generated and displayed without exposed results, points, and / or labels. In this regard, the term "initial" of the initial visualization indicates that the 3D rendering of the heart chamber prior to the EP procedure includes all previous results, points, and / or labels (e.g., one or more previous labels 670). For example, one or more labels 670 are located below the surface 660. One or more labels 670 below the surface 660 are further shown in visualizations 602 and 603, which are cross-sectional views into the partition 680 that shows the interior of the anatomical structure (i.e., below the surface 660). According to one or more embodiments, one or more labels 670 can identify one or more previous ablation events from a previous ablation procedure.

[0081] At block 530, the mapping engine 101 identifies one or more hidden features; for example, features below the surface of the initial visualization. As described herein, features can include, but are not limited to, one or more labels, one or more catheters (e.g., catheter 14), one or more inner surface points, and / or one or more points, as well as previous results. According to one or more embodiments, the mapping engine 101 identifies one or more features according to a set of parameters. Examples of the set of parameters include, but are not limited to, maximum distance, maximum length ratio, minimum segmentation length, filter distance, or maximum edge length, as well as the selection of one or more labels, one or more catheters, and / or one or more points.

[0082] As another example, turning Figure 7 , a set of diagrams 701, 702, 703, and 704 is shown that provide an example deformation progression according to one or more embodiments. Each of the diagrams 701, 702, 703, and 704 maintains the same identifier for the same elements. As seen in the first diagram 701 of Figure 7 and referring to block 530, according to one or more embodiments, the mapping engine 101 identifies that the surface 709 hides a feature 712 (e.g., a label) from an external viewpoint (represented by the arrow 713). Additionally, the mapping engine 101 identifies the feature 712 as a feature to be exposed to the external viewpoint. It should be noted that the second diagram 702, the third diagram 703, and the fourth diagram 704 are described in further detail with respect to the progression of the method 500 of Figure 5 herein.

[0083] As another example, turning Figure 8 , a set of diagrams 801, 802, 803, and 804 is shown that provide an example deformation progression according to one or more embodiments. Each of the diagrams 801, 802, 803, and 804 maintains the same identifier for the same elements. As in Figure 8As seen in the first illustration 801 and with reference to frame 530, according to one or more embodiments, the mapping engine 101 identifies that surface 809 hides a set of features 812, 813, and 814 (e.g., labels) from an external viewpoint (represented by arrow 815). Additionally, the mapping engine 101 identifies one or more of the features 812, 813, and 814 as features exposed to the external viewpoint (e.g., based on a set of parameters). It should be noted that the progress of method 500 with respect to Figure 5 is described in further detail with respect to the progress of the second illustration 802, the third illustration 803, and the fourth illustration 804.

[0084] At block 540, the mapping engine 101 deforms the initial visualization. Deforming the initial visualization can include changing the surface, shape, or otherwise manipulating a portion of the initial visualization. The deformation of the initial visualization can be an automatic editing of the initial visualization, for example, performed in real time during an EP procedure (e.g., ablation procedure), and the resulting image can be considered a temporarily altered visualization (i.e., a temporary visualization). Additionally, "real time" can be considered to present the temporary visualization when it is generated on the display such that changes to the "currently displayed" will be presented to the physician 24 only at the deformed region.

[0085] According to one or more embodiments, deforming the initial visualization can change a 3D image or model (e.g., including a surface) to expose aspects (e.g., one or more features) that were originally hidden or covered by other parts of the 3D image or model. The deformation by the mapping engine 101 is a natural change to the geometry of the 3D image or model. As an example, the mapping engine 101 changes one or more regions of the surface of the initial visualization corresponding to one or more features or a subset thereof identified in block 530. In this regard, the mapping engine 101 reduces the surface of the 3D image or model (e.g., the region of the surface is reduced to and thus exposes ).

[0086] The mapping engine 101 utilizes one or more algorithms to perform the deformation. According to one or more embodiments, the one or more algorithms locally deform the initial visualization. Local deformation includes changing the shape of the 3D image or model in a region relative to a feature (e.g., the ablation tip of catheter 14), while the remainder of the 3D image or model remains unchanged. For example, a catheter within the initial visualization may be covered by the outer wall of the initial visualization, and an adjustment to the visualization is required, such as by implementing the removal of a portion of the outer wall to show the deformation of the catheter relative to the inner wall of the initial visualization. Despite the presence of labels in the initial visualization, local deformation enables the display of the catheter. Examples of the one or more algorithms include deformation algorithms.

[0087] According to one or more embodiments, the initial visualization deformation can be performed by the deformation algorithm of the mapping engine 101. The deformation algorithm can include, but is not limited to, the as-rigid-as-possible (ARAP) algorithm or other geometry / mesh processing. Geometry processing includes manipulating a shape in a space of any dimension such that the topology or set of properties of the shape does not change after a smooth transformation has been applied to the shape (e.g., different from shaving which removes layers of the shape and changes the topology). According to one or more embodiments, the mapping engine 101 utilizes the ARAP algorithm to ensure smoothness and natural deformation, both of which are not available in conventional mapping techniques.

[0088] It should be noted that deformation is not shaving. Some shaving techniques require manual, time-consuming work to input electrical signals into the FAM to support the output of the initial visualization. Shaving removes voxels from the acquired volume data. When shaving removes data used to construct the surface, shaving causes a change in the surface. In contrast, deformation does not remove voxels (the input for the surface reconstruction algorithm). Deformation occurs after the initial visualization is generated. In further contrast, deformation implements the triangular mesh of the surface of the initial visualization to contour the surface around features, thereby changing the position / shape / size of the triangles (e.g., changing the vertices of each triangle within a region to expose the feature). As an example, turning Figure 9 , a set of illustrations 901 and 902 provide examples of deformation processing performed by the deformation algorithm of the mapping engine 101 according to one or more embodiments. The first illustration 901 shows a portion of the triangular mesh of the surface. In this regard, the triangular mesh includes a plurality of vertices on the X-Y plane 921, such as vertex 912. When vertex 912 is identified by the mapping engine 101, a set of eight (8) immediately adjacent vertices 930 and a region 940 of surrounding vertices are identified. The second illustration 902 shows an example deformation of the X-Y plane 921 in the -Z direction. For example, the mapping engine 101 moves vertex 912 by pulling vertex 912 and the eight (8) immediately adjacent vertices 930 away from the X-Y plane 921 in the -Z direction. According to one or more embodiments, the mapping engine 101 can move vertex 912 to a label or feature separated from the X-Y plane 921 in the -Z direction. Additionally, the region 940 of surrounding vertices and associated triangles is moved (or stretched) or changed to create a pit or depression in the X-Y plane 921 as viewed from the +Z direction. According to one or more embodiments, the deformation algorithm of the mapping engine 101 can also extend the deformation constraints to a local single-ring neighborhood, thereby allowing individual transformations for the entire ring and preventing shearing when the rings overlap.

[0089] Return to reference Figure 5, the frame 540 includes two example sets of operations for deforming an initial visualization (e.g., generating a temporary visualization on a display based on region-based deformation) by the mapping engine 101. The deformation of the initial visualization may include applying a deformation algorithm to a region of the surface. The deformation of the surface is performed by the deformation algorithm according to the selection of one or more settings (point region factor, minimum distance, maximum distance, smoothing iteration value, maximum iteration value, and / or convergence threshold) as described herein.

[0090] According to one or more embodiments, a first example set of operations 541 of the frame 540 is shown. The first example set of operations 541 includes deforming a region of the surface of the initial visualization to the average position of the catheter to generate a temporary visualization that exposes at least a portion of the catheter. At sub-frame 542, the mapping engine 101 determines the average position of the catheter. The average position may be a calculation of the last three positions of the catheter. Thus, as the catheter moves, the mapping engine 101 may maintain a history of the position of the catheter in memory. At sub-frame 544, the mapping engine 101 automatically selects the surface point closest to the average position. The selection of the surface point enables the mapping engine 101 to "pull" the closest vertex to the average position of the catheter or the center of the end of the catheter. The surface point may be a vertex of a triangle of a triangular mesh. At sub-frame 546, the mapping engine 101 determines the distance between the surface point and the average position. The distance may be measured in millimeters (mm). At sub-frame 548, the mapping engine 101 determines the region of the surface to be deformed based on the distance. The region may be a linear factor of the distance (e.g., 2x, 3x, 4x, or greater). The linear factor may be configurable. For example, if the distance is five (5) mm and the linear factor is 3x, the mapping engine 101 multiplies the distance by the linear factor to calculate a 15 mm radius. The region is then determined to be a circle with a 15 mm radius and centered at the selected surface point from sub-frame 544. According to one or more embodiments, a catheter having multiple electrodes may correspond to an affected region of the surface calculated for each center of each electrode.

[0091] According to one or more embodiments, a second example set of operations 551 of the frame 540 is shown. The second example set of operations 551 includes deforming the surface of the initial visualization by a deformation algorithm of the mapping engine 101 to expose a subset of one or more features by changing one or more regions of the surface corresponding to a subset of one or more features (e.g., labels). At sub-frame 552, the mapping engine 101 automatically determines the surface point closest to the label (for each of the one or more labels). The selection of the surface point enables the mapping engine 101 to pull the closest vertex to the label or the center of the label.

[0092] Return reference Figure 7And as shown in the second illustration 702, a set of surface points 721, 722, and 723 (e.g., vertices of a mesh of the surface 709) are identified on the surface 709. Additionally, the mapping engine 101 selects the surface point that is closest to the feature 712 (in this example, the surface point 722 is selected).

[0093] Return reference Figure 8 And as shown in the second illustration 802, a set of surface points 822, 823, and 824 (e.g., vertices of a mesh of the surface 809) are identified on the surface 809. Additionally, the mapping engine 101 selects the closest surface point for each of the features 812, 813, and 814 (which are the surface points 822, 823, and 824, respectively).

[0094] Return reference Figure 5 For the second example set of operations 551 and the next sub - box 554, the mapping engine 101 calculates the distance between one or more surface points and one or more labels.

[0095] Return reference Figure 7 And as shown in the second illustration 702, the mapping engine 101 determines the distance 725 between the surface point 722 and the feature 712.

[0096] Return reference Figure 8 And as shown in the illustration 802, the mapping engine 101 determines the distances 833, 835, and 837 between the surface points 822, 823, and 824 and the features 812, 813, and 814, respectively.

[0097] Return reference Figure 5 For the second example set of operations 551 and the next sub - box 556, the mapping engine 101 determines the area of the surface to be deformed based on the distances.

[0098] Return reference Figure 7 And as shown in the third illustration 703, the area 734 is determined. For example, the area 734 can be a circle with a radius equal to the distance 739, and the center of the circle coincides with the surface point 722. For example, the area 734 can be a square with half of the side length equal to the distance 739, and the center of the square coincides with the surface point 722. The mapping engine 101 can determine the distance 739. According to one or more embodiments, the distance 739 can be determined by multiplying the distance 725 by a configurable linear factor. Examples of the configurable linear factor include any number in the range between zero (0) and one hundred (100) (e.g., the configurable linear factor can be 3). As shown in the fourth illustration 704, the mapping engine 101 pulls the surface 709 towards the feature 712 such that the feature 712 is exposed. For example, the mapping engine 101 performs geometric processing to move all vertices within the area 734 and stretch all triangles to create a pit or depression 740 that exposes the feature 712.

[0099] Return reference Figure 8 And as shown in the second illustration 802 and the third illustration 803, the region 833 is determined according to the distance 834, the region 835 is determined according to the distance 836, and the region 837 is determined according to the distance 838. It should be noted that the regions 833, 835, and 837 can be of any shape and can be determined relative to the distances 834, 836, and 838 using configurable linear factors. As shown in the fourth illustration 804, the mapping engine 101 pulls the surface 809 to each of the features 812, 813, and 814 such that the features 812, 813, and 814 are exposed. For example, the mapping engine 101 performs geometric processing to move all vertices within the regions 833, 835, and 837 and stretch all triangles to create pits or cavities 841 and channels 843 that expose the features 812, 813, and 814 (which is due to the overlap of the regions 835 and 837).

[0100] According to one or more embodiments, the mapping engine 101 performs minimum deformation by using convergence. Convergence is a minimization energy function for keeping the deformation of the surface minimal. The mapping engine 101 optimizes the minimum deformation by iteratively implementing the energy function, for example, according to Equation 1, where R i is the rotation matrix and v i ′ is the new position:

[0101]

[0102] Go to Figure 10 , which describes the visualization 1000 according to one or more embodiments. The visualization 1000 is the result of the deformation performed by the mapping engine 101. The visualization 1000 can be a temporary visualization. The visualization 1000 shows the progression of the anatomical structure as Figure 6 shown. Thus, the visualization 1000 depicts the "after" state of the anatomical structure, where the regions corresponding to one or more labels 670 are deformed to produce recessed regions 1010 and 1020 that expose one or more labels 670, where before the deformation, the labels 670 were obscured beneath the surface 660.

[0103] Return reference Figure 5For method 500 and next box 560, the mapping engine 101 determines whether to maintain the temporary visualization. According to one or more embodiments, the mapping engine 101 can determine whether to maintain the temporary visualization based on the ablation events of the ablation procedure. For example, when the mapping engine 101 determines that the ablation event has not occurred, the mapping engine 101 can discard the temporary visualization and return to the initial visualization (e.g., once the catheter moves, the pits, channels, ranges, mounds, heaps, or holes caused by the pulling surface return to the original state, and the object can return). Alternatively, when the mapping engine determines that the ablation event has occurred, the mapping engine 101 replaces the initial visualization with the temporary visualization to generate an updated visualization. The updated visualization can be saved and stored.

[0104] At block 580, the mapping engine 101 receives a selection of one or more settings. According to one or more embodiments, the mapping engine 101 receives a selection of one or more settings and updates the initial visualization or the updated visualization.

[0105] Go to Figure 11 , a user interface 1100 according to one or more embodiments is described. The user interface 1100 shows an example of the mapping graph deformation settings enabled by the mapping engine 101. The one or more settings include but are not limited to a selector 1111 for deforming to , a selector 1112 for deforming to an ultrasound (ULS) profile, a selector 1113 for deforming to an ablation catheter, and a selector 1114 for deforming to points. As an example, with respect to selectors 1111 and 1112, the mapping graph deformation settings of the user interface 1100 can include selectors for projection methods with respect to the edge path and the nearest path. In addition, with respect to selectors 1111 and 1112, the mapping graph deformation settings of the user interface 1100 can include a plurality of first fields. For example, the plurality of first fields can receive numerical values in millimeters (mm). The plurality of first fields can correspond to but are not limited to the maximum distance to be mapped, the maximum projection / path length ratio, the minimum projection segmentation length, filter distance, and path maximum edge length. In addition, with respect to selector 1113, the mapping graph deformation settings of the user interface 1100 can include a plurality of second fields. For example, the plurality of second fields can receive numerical values and / or can be selectors. The plurality of first fields can correspond to but are not limited to the maximum distance to be mapped, the number of ablation positions, the sampling period in milliseconds (Ms), the force threshold, and the "touch only" condition. The mapping graph deformation settings of the user interface 1100 can include a deformation algorithm setting 1130. The deformation algorithm setting 1130 can include a plurality of third fields. The plurality of third fields can include but are not limited to the point area factor, the minimum point area distance, the maximum point area distance, the smoothing iteration, the algorithm maximum iteration, and the convergence threshold.

[0106] Now turning to Figure 12 which shows method 1200 according to one or more embodiments. Method 1200 is an example set of operations of the mapping engine 101, which necessarily originates from and is executed by the following: Figure 1 workstation 55 of Figure 2 local computing device 106 of Figure 2 remote computing system 108 of and / or Figure 4 example device 400 of. Method 1200 shows an example of how the mapping engine 101 generates and presents a map of an anatomical structure (e.g., one or more 3D models) and how to edit the map (e.g., provide a map deformation of one or more 3D models). Figures 13 to 23 depicts a user interface presenting the visualization progress according to one or more embodiments. Figures 13 to 23 The user interface of is provided as an example of what a physician or technician sees when method 1200 is implemented by the mapping engine.

[0107] Method 1200 begins at block 1210, where the mapping engine 101 generates an initial visualization. The initial visualization is a map of an anatomical structure as described herein. According to one or more embodiments, the initial visualization may be generated during an EP procedure. The EP procedure may be an ablation procedure, where one or more ablation events occur. At block 1220, the mapping engine 101 presents the initial visualization on a display. Thus, the mapping engine 101 can generate and present the initial visualization on a display during an ablation procedure. The initial visualization is used to guide physician 24 to the desired ablation site. According to one or more embodiments, the initial visualization is generated and displayed as the catheter moves. As an example, the initial visualization is generated and displayed as the catheter moves to and between ablation sites. According to one or more embodiments, the initial visualization may be provided prior to an ablation event of an ablation procedure, such that the physician is guided to the desired ablation site with an easy understanding of the real tissue location. Referring to Figure 13 user interface 1300 is illustrated, which shows an example of the initial visualization 1301 generated and displayed by the mapping engine 101. The initial visualization 1301 is a 3D rendering of the heart. The user interface 1300 includes a catheter 1320 (e.g., Figure 1 catheter 14 of), which is below the surface of the initial visualization 1301. The catheter 1320 may include an ablation tip 1330, which may change color and / or illumination according to the state of the catheter 1320 during an ablation procedure.

[0108] Returning to reference Figure 12 and the next block 1230, the mapping engine 101 determines the catheter position. The catheter position may be Figure 1The average position of catheter 14 during an EP procedure (e.g., during an ablation event of an ablation procedure). The average position can be determined based on one or more positions provided by the catheter and other biometric data. For example, the catheter may move or slide (e.g., in a slight manner) throughout the ablation event. As the catheter moves or slides, the mapping engine 101 may acquire the position and / or other information. When the catheter moves or slides, the position and / or other information is used to determine the average position. In this regard, the mapping engine 101 can provide the physician 24 with a better understanding of the position of the catheter (e.g., catheter position), rather than showing the catheter as a jumping position within the initial visualization. Additionally, surface ECG electrodes can provide the position and / or other information for determining the average position of the catheter.

[0109] According to one or more embodiments, the catheter can be any catheter as described herein, such as a focused catheter that provides force and position. According to one or more embodiments, the average position of the focused catheter can be a calculation by the mapping engine 101 based on the force and position (i.e., position and / or other information) provided by the focused catheter over time. According to one or more embodiments, the average position can be calculated based on catheter positions that meet predefined conditions (e.g., minimum force value, position stability, and / or touch indication). According to one or more embodiments, an ablation catheter having multiple electrodes can be used.

[0110] At block 1240, the mapping engine 101 presents the catheter within the initial visualization. For example, the mapping engine 101 shows the catheter at the average position as a silhouette or a translucent silhouette within the initial visualization.

[0111] According to one or more embodiments, the ablation tip of the catheter can be shown below the surface of the initial visualization. In this regard, the surface of the initial visualization can be translucent, so that the ablation tip and the catheter can be shown at the determined catheter position (e.g., the mapping engine 101 shows the catheter as a translucent silhouette at the catheter position). Additionally, when the catheter position changes due to intentional movement of the catheter, the mapping engine 101 updates the display of the catheter according to the changed catheter position.

[0112] Return reference Figure 13, a catheter 1320 is disposed within an initial visualization 1301. According to one or more embodiments, the catheter 1320 and the ablation tip 1330 of the catheter 1320 may be shown beneath the endocardial surface of the initial visualization 1301. As shown, the endocardial surface may be translucent (e.g., as an outline), such that the ablation tip 1330 and the catheter 1320 can be seen at the determined catheter location on the display. However, the catheter 1320 is not easily understood to be at or near the inner wall. It should be noted that the catheter 1320 within the initial visualization 1301 is "covered" by the outer wall of the initial visualization 1301 and a portion of the outer wall needs to be changed to show the deformation of the catheter 1320 relative to the inner wall of the initial visualization 1320. It should be noted that the mapping engine 101 may expose the catheter 1320 at any time to understand the depth within the space. Additionally, when the catheter position changes due to catheter movement, the mapping engine 101 updates the user interface of the catheter 1320 based on the changed catheter position.

[0113] Return reference Figure 12 and sub-box 1245, the mapping engine 101 enables filtering. According to one or more embodiments, the mapping engine 101 filters out catheter positions that are not relevant to the current position. For example, the movement of the catheter 1320 into the heart chamber can be filtered out from the determination of the average position. Thus, the mapping engine 101 avoids deforming the initial visualization to a miscomputed position. Filtering may also be performed by the mapping engine 101 based on the selection of one or more factors. The one or more factors include but are not limited to force (e.g., the catheter is not in contact with the wall of the anatomical structure, force threshold, and contact indication such as tissue contact), ablation power (e.g., the power can start at a high power of 5 to 10 watts), drag power (e.g., the power can always be on and have varying levels), low power (e.g., ablation within, for example, 20 seconds), and distance (e.g., the distance from the catheter itself or the distance from the surface to the catheter).

[0114] Reference Figure 14 , a user interface 1400 is illustrated, which shows an example of an initial visualization 1401, where the ablation tip 1410 of the catheter 1320 changes color (or is illuminated in another way). The color change indicates that the average position has been determined. Other color changes may indicate that the catheter 1320 is ready for ablation and / or an ablation event has started (but not ended).

[0115] Return reference Figure 12 and next box 1250, the mapping engine 101 deforms or changes the shape of the initial visualization. For example, the deformation enables the physician 24 to see the catheter regardless of the complexity and labels of the initial visualization. The deformation can be achieved before an ablation event, when the catheter is ready for ablation, and / or after an ablation event has started (but before it ends).

[0116] According to one or more embodiments, the mapping engine 101 uses the average position to deform or change the initially visualized shape. In this regard, the initially visualized endocardial surface is deformed to expose the catheter (i.e., the ablation tip is no longer shown as a contour). The deformation of the endocardial surface can be achieved by a "pulling" reconstruction operation. The pulling reconstruction operation includes pulling / acquiring biometric data, using the biometric data to generate a 3D geometry, and software operations to update the initially visualized geometry with the geometry. For example, the pulling reconstruction operation can include acquiring biometric data from the catheter prior to an ablation event. As the catheter moves, the pulling reconstruction operation can be continuous such that the initially visualized geometry can be deformed to show the catheter within the 3D image or model.

[0117] According to one or more embodiments, the mapping engine 101 can utilize one or more algorithms to perform the deformation. Examples of one or more algorithms include the deformation algorithms as described herein to locally deform the initially visualized geometry to the average position.

[0118] At sub - box 1255, the mapping engine 101 applies the deformation algorithm (preferably in real - time), and further deformation can occur when the catheter is stable (e.g., remains in the same position). Once the catheter is ready for ablation and / or stable, the deformation algorithm can be implemented. For example, the mapping engine 101 deforms the initially visualized geometry at the average position to provide a temporary visualization that exposes the catheter at the average position on the display.

[0119] Reference Figure 15 , the user interface 1500 is illustrated, which shows an example of the temporary visualization 1501, where the ablation tip 1510 of the catheter 1320 is exposed by the deformation 1530, while the remaining portion 1540 of the catheter 1320 is shown as a contour. The mapping engine 101 utilizes the ARAP algorithm to ensure the smoothness of the deformation 1530 around the average position. Thus, the catheter 1320 is easily shown to be at or near the inner wall in the temporary visualization 1501.

[0120] According to one or more embodiments, the mapping engine 101 does not wait for tags to appear during the pulling reconstruction operation, and / or the mapping engine 101 utilizes the average catheter position instead of pre - existing tags. In this regard, the mapping algorithm is capable of generating and displaying a temporary visualization before an ablation event occurs. Tags may take time to be displayed. However, in this example, the mapping engine 101 does not wait (proceeds immediately) for tags (e.g., or ablation tags) to appear to achieve the pulling reconstruction operation. In contrast, conventional mapping techniques such as Fast Anatomical Mapping - Electroanatomical (FAM - EA) construct the pull to points / tags, which is too late. As an example, as long as predefined criteria (such as catheter stability, contact force, time, impedance drop, etc.) are met, The ablation site can be objectively annotated.

[0121] According to one or more embodiments, the initial visualization of local deformation may include a temporary visualization within the initial visualization before the end of the ablation event. It should be noted that applying the deformation algorithm may include automatically editing the initial visualization in real time during an EP procedure (e.g., an ablation procedure).

[0122] Reference Figure 16 describes a user interface 1600, which shows an example of the temporary visualization 1601. The temporary visualization 1601 includes the ablation tip 1510 of the further exposed catheter 1320. The mapping engine 101 utilizes the ARAP algorithm to enhance the temporary visualization 1601 to ensure the smoothness of further deformation 1630. It should be noted that the ARAP algorithm may perform one or more smoothing iterations, such as at least two (2) iterations. Subsequently, the ablation tip 1510 of the catheter 1320 is more clearly exposed, while the remaining portion 1640 of the catheter 1320 is shown as a contour. It should be noted that this further deformation may occur when the catheter 1320 is stable (e.g., as indicated by the interface icon identified by arrow 1650) for at least two (2) seconds (e.g., as indicated by the interface icon identified by arrow 1660). Thus, the catheter 1320 is easily shown to be at or near the inner wall.

[0123] Return reference Figure 12 With reference to decision diamond box 1260, the mapping engine 101 determines whether to maintain the temporary visualization. According to one or more embodiments, the mapping engine 101 determines whether to maintain the temporary visualization or revert to the initial visualization. According to one or more embodiments, the mapping engine 101 determines whether to maintain the temporary visualization based on the ablation event of the EP procedure. According to one or more embodiments, the mapping engine 101 may determine whether to maintain the temporary visualization based on the ablation event of the ablation procedure. That is, to determine whether to maintain the temporary visualization, the mapping engine 101 further checks (as indicated by sub - box 1265) whether an ablation event has occurred. If an ablation event has occurred, process 1200 proceeds to box 1270. If an ablation event has not occurred, process 1200 proceeds to box 1280.

[0124] At sub - box 1265, the mapping engine 101 determines that the ablation event occurs after the catheter sends a signal and / or generates a corresponding label. Reference Figure 17, describes a user interface 1700, which shows an example of a temporary visualization 1701. The temporary visualization 1701 includes an ablation tip 1510, a catheter 1320, a deformation 1730, and a label 1771 (represented as a sphere). The label 1771 indicates that the catheter 1320 has performed ablation (e.g., the ablation event has been completed). Since the ablation event has occurred (as indicated by the label 1771), the process 1200 proceeds to block 1270.

[0125] At block 1270, because the ablation event has occurred, the mapping engine 101 uses the label 1771 for ablation to complete the deformation 1730. According to one or more embodiments, when the mapping engine 101 determines the end of the ablation event through the detection of the label, the mapping engine 101 uses the position of the label to locally apply the deformation algorithm. For example, if the ablation event ends with ending, then the final position of is used to deform the mapping diagram to the position. In this regard, the mapping engine 101 presents the deformation of the initial visualization as a temporary visualization (e.g., which can be saved and stored by the mapping engine 101).

[0126] At block 1275, the mapping engine 101 replaces the initial visualization 1701 with the updated visualization 1801, so that further deformation can be performed on the updated visualization 1801. Referring to Figure 18 , describes a user interface 1800, which shows an example of the updated visualization 1801. Therefore, the mapping engine 101 uses the position of the label 1771 indicating the ablation event to apply the deformation to the temporary visualization 1701 to generate the updated visualization 1801. In the updated visualization 1801, the catheter 1320 is shown as a contour and has moved from the position of the label 1771.

[0127] According to one or more embodiments, the initial visualizations 1301 and 1401, the temporary visualization 1701, and the updated visualization 1801 can be saved and stored by the mapping engine 101. According to one or more embodiments, the method 1200 loops through block 1230, block 1240, and the decision diamond block 1260, so that after each ablation event, the visualization is updated using the deformation and label placed at the ablation site. It should be noted that when the catheter 1320 is moving, the new average position can be calculated.

[0128] For example, referring to Figure 19 , the user interface 1900 describes an example of a subsequent temporary visualization 1901, where the ablation tip 1510 of the catheter 1320 is exposed through the deformation 1930, while the remaining part 2040 of the catheter 1320 is shown as a contour. It should be noted that when the mapping engine 101 performs the deformation 1930, the label 1771 is exposed. Additionally, referring toFigure 20 , the user interface 2000 illustrates an example of a subsequent temporary visualization 2001 after a second ablation event has occurred. The subsequent temporary visualization 2101 includes the catheter 1320, the label 1771, and a second label 2072 (represented as a sphere). The label 2072 indicates that the catheter 1320 has performed ablation (e.g., the ablation event has been completed). Since the second ablation event has occurred (as indicated by the second label 2072), the process 1200 proceeds through blocks 1270 and 1275. Additionally, referring Figure 21 , the user interface 2100 illustrates an example of the subsequent temporary visualization 2101, where the ablation tip 1510 of the catheter 1320 is exposed by the deformation 2130, and the remaining portion 2140 of the catheter 1320 is shown as a contour. It should be noted that this further deformation can occur when the catheter 1320 is stable (e.g., as indicated by the interface icon identified by the arrow 2150). Moreover, the ablation tip 2110 of the catheter 1320 can change color (or be illuminated in another way) to indicate that the catheter 1320 is stable and the average position of the catheter 1320 has been determined by the mapping engine 101. Additionally, referring Figure 22 , the user interface 2200 illustrates an example of the temporary visualization 2201. The temporary visualization 2201 includes the catheter 1320, the deformation 2130, the first label 1771, the second label 2072, and a third label 2273. The deformation 2130 is now set to the third label 2273. Since the third ablation event has occurred (as indicated by the third label 2273), the process 1200 proceeds through blocks 1270 and 1275.

[0129] Return to reference Figure 12 and return to the decision block 1260. If the ablation event has not occurred, the process 1200 proceeds to block 1280. At block 1280, the mapping engine 101 reverts to either the initial visualization or a temporary visualization without deformation. When the mapping engine 101 determines that the ablation event has not ended, the temporary visualization (i.e., the deformation of the initial visualization) is discarded. In this regard, the mapping engine 101 deletes or removes the deformation from the initial visualization to end the presentation of the temporary visualization. As another example, the mapping engine 101 deletes or removes any added deformation to revert to the "previous" visualization. According to one or more embodiments, the initial visualization restores the surface to the previous surface shape at that location. It should be noted that the process 1200 can loop (as indicated by the arrow 1281) such that further or alternative deformations can be performed.

[0130] According to one or more embodiments, when the mapping engine 101 determines that the ablation event has not ended, the deformation of the initial visualization is discarded. For example, if the ablation event has not occurred If it ends, the deformation is discarded. In this regard, the mapping engine 101 deletes or removes the deformation from the initial visualization to end the rendering of the temporary visualization.

[0131] Figure 23 The user interface 2300 is illustrated, which shows an example of the final visualization 2301. The final visualization 2301 includes a catheter 1320 and a plurality of labels 2375 shown by a continuous deformation 2381 (e.g., a deformed area of the surface) within the final visualization 2301.

[0132] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of the possible specific implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagram may represent a module, segment, or portion of instructions that includes one or more executable instructions for implementing the specified logical function. In some alternative specific implementations, the functions noted in the blocks may not occur in the order noted in the figures. For example, depending on the functions involved, two consecutive blocks shown may actually be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order. It should also be noted that each block in the block diagram and / or flowchart illustration, and combinations of blocks in the block diagram and / or flowchart illustration, can be implemented by a system based on dedicated hardware that performs the specified functions or actions, or by a combination of dedicated hardware and computer instructions.

[0133] Although the features and elements have been specifically described above, those of ordinary skill in the art will know that each feature or element can be used alone or in any combination with other features and elements. In addition, the methods described herein can be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or a processor. As used herein, a computer-readable medium should not be construed as a transient signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., an optical pulse passing through an optical fiber cable), or an electrical signal transmitted through a wire.

[0134] Examples of computer-readable media include electrical signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, registers, cache memories, semiconductor memory devices, magnetic media (such as internal hard disks and removable disks), magneto-optical media, optical media (such as compact discs (CDs) and digital versatile discs (DVDs)), random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), and memory sticks. A processor associated with software can be used to implement a radio frequency transceiver used in a terminal, a base station, or any host computer.

[0135] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, unless the context clearly dictates otherwise, the singular forms "a", "an" and "the" include plural referents. It should also be understood that the terms "comprises" and / or "comprising", when used in this specification, specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0136] The description of the various embodiments herein is presented for purposes of illustration but is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the embodiments. The terms used herein were chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable other ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A method implemented by a mapping engine, the mapping engine comprising processor executable code stored on a memory and executed by at least one processor, the method comprising: generating a first visualization of the anatomical structure on a display during an ablation procedure; generating on the display the catheter at the average position as a contour beneath the surface within the first visualization; as well as A region of the surface of the first visualization is deformed to the average position to generate a second visualization exposing at least a portion of the conduit.

2. The method according to claim 1, wherein the method comprises: The average position of the catheter is determined and the surface of the first visualization is deformed while determining the average position.

3. The method of claim 1 , wherein the deformation of the region of the surface of the first visualization comprises: automatically selecting a surface point closest to the average position; determining a distance between the surface point and the average position; as well as The area of ​​the surface to be deformed is determined based on the distance. The method of claim 1 , wherein the deformation of the region of the surface of the first visualization comprises applying a deformation algorithm to the region. 5 . The method of claim 1 , wherein the method comprises discarding the second visualization and returning to the first visualization when the mapping engine determines that the ablation event has not occurred. 6 . The method of claim 1 , wherein the method comprises replacing the first visualization with the second visualization to generate an updated visualization when the mapping engine determines that the ablation event has occurred.

7. A method implemented by a mapping engine, the mapping engine comprising processor executable code stored on a memory and executed by at least one processor, the method comprising: generating a visualization of the anatomical structure on a display, the visualization including one or more labels hidden beneath a surface of the visualization; as well as deforming an area of ​​the surface to expose the one or more labels, wherein for each of the one or more labels, wherein the deforming of the surface comprises: automatically selecting a surface point that is closest to a tag among the one or more tags, Calculating the distance between the surface point and the tag, and The area of ​​the surface to be deformed is determined based on the distance. 8 . The method of claim 7 , wherein deforming the area of ​​the surface to expose the one or more labels comprises changing the visualization to generate a temporary visualization.

9. The method of claim 7, wherein the method comprises applying a deformation algorithm to deform the region of the surface.

10. The method of claim 7, wherein the mapping engine identifies the one or more tags based on a set of parameters including a maximum distance to be mapped.

11. The method of claim 7, wherein the mapping engine identifies the one or more tags based on a set of parameters including a filter distance. 12 . The method of claim 7 , wherein the method comprises discarding the temporary visualization when the mapping engine determines that an ablation event has not occurred.

13. The method of claim 8, wherein the method comprises replacing the visualization with the temporary visualization to generate an updated visualization when the mapping engine determines that an ablation event has occurred.

14. A method implemented by a mapping engine, the mapping engine comprising processor executable code stored on a memory and executed by at least one processor, the method comprising: generating a visualization of the anatomical structure on a display, the visualization including one or more features hidden beneath a surface of the visualization; identifying a subset of the one or more features based on the set of parameters; as well as The surface of the visualization is deformed by a deformation algorithm of the mapping engine to expose the subset of the one or more features by altering one or more regions of the surface corresponding to the subset of one or more labels.

15. The method of claim 14, wherein the one or more features include one or more tags, catheters, or one or more points.

16. The method of claim 15, wherein the set of parameters comprises at least a selection of the one or more tags, the catheter, or the one or more points.

17. The method of claim 14, wherein the parameter set comprises a maximum distance, a maximum length ratio, a minimum segmentation length, a filter distance, or a maximum edge length. The method of claim 14 , wherein the deformation algorithm comprises an algorithm that is as strict as possible.

19. The method of claim 14, wherein the deformation of the surface is performed by the deformation algorithm according to a selection of one or more settings, the one or more settings comprising one or more of a point area factor, a minimum distance, a maximum distance, a smoothing iteration value, a maximum iteration value, and a convergence threshold.

Images