Graphical user interface for intravascular plaque load indication
By improving the graphical user interface of the IVUS system and utilizing machine learning to detect plaque burden within blood vessels and generate graphical components, the problem of difficulty in identifying the nature of vascular occlusion and stenosis in existing technologies has been solved, thereby improving the accuracy of stent placement and treatment efficiency.
Patent Information
- Application Number
- CN202480035859.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-03-30
- Filing Date
- 2024-03-29
- Publication Date
- 2026-01-13
AI Technical Summary
Existing IVUS imaging systems lack an effective graphical user interface for conveying information about the nature and extent of vascular occlusion or stenosis, making it difficult for physicians to identify areas with plaque burden below a threshold level, thus affecting the accuracy of stent placement.
An improved graphical user interface is provided, which automatically detects blockages or stenosis in blood vessels by generating and rendering graphical components, including longitudinal views of blood vessels and plaque load indicators, and generates a GUI to display longitudinal views of blood vessels and plaque load information, supporting users to visualize and manipulate information about vascular structures.
It improves physicians' ability to identify areas in blood vessels with plaque load below a threshold level, reduces treatment time, and improves the accuracy and efficiency of stent placement.
Smart Images

Figure CN121335671A_ABST
Abstract
Description
[0001] Cross Reference to Related Applications
[0002] This application claims the benefit of U.S. Provisional Patent Application Serial No. 63 / 455,860, filed March 30, 2023, the disclosure of which is incorporated herein by reference. TECHNICAL FIELD
[0003] The present invention relates generally to intravascular ultrasound (IVUS) imaging systems. In particular, but not exclusively, the present invention relates to improved graphical user interfaces for IVUS imaging systems. BACKGROUND
[0004] Ultrasound devices that can be inserted into a patient’s body have proven diagnostic capabilities for a variety of diseases and conditions. For example, intravascular ultrasound (IVUS) imaging systems have been used as an imaging modality for diagnosing blocked blood vessels and providing information to help medical practitioners select and place stents and other devices to restore or increase blood flow.
[0005] IVUS imaging systems include a control module (having a pulse generator, image acquisition and processing components, and a monitor), a catheter, and a transducer disposed in the catheter. The catheter, containing the transducer, is positioned in a lumen or cavity within or near the region to be imaged, such as a blood vessel wall or patient tissue proximate to a blood vessel wall. The pulse generator in the control module generates electrical pulses, which are delivered to the transducer and converted to acoustic pulses that are transmitted through the patient tissue. The patient tissue (or other structure) reflects the acoustic pulses, and the reflected pulses are absorbed by the transducer and converted to electrical pulses. The converted electrical pulses are delivered to the image acquisition and processing components and converted to an image that can be displayed on the monitor.
[0006] IVUS systems can be used to image blood vessels to determine the presence of obstructions or stenoses within the blood vessels, as well as to determine the nature and extent of the obstructions or stenoses. In addition, IVUS systems can be used to visualize segments of the vasculature that can be difficult to visualize using other intravascular imaging techniques, such as angiography, due to movement (e.g., a beating heart) or obstruction by one or more structures (e.g., one or more blood vessels that are not desired to be imaged). Thus, there is a need for user interfaces, and in particular graphical user interfaces, that convey information related to the nature and extent of obstructions or stenoses of blood vessels from the IVUS system to a user. SUMMARY
[0007] This Summary is provided to introduce a set of concepts in a simplified form that are further described below in the DETAILED DESCRIPTION. This Summary is not intended to necessarily identify key or essential features of the claimed subject matter, nor is it intended to be used to determine the scope of the claimed subject matter.
[0008] Generally, this disclosure provides improvements to computing devices, particularly to IVUS guidance systems, because it provides a graphical user interface arranged to convey the rich information generated by modern IVUS systems. For example, an IVUS system may include machine learning features for processing and analyzing signals generated during IVUS operation. Such information may include the automatic detection of blockages or stenosis within blood vessels (e.g., plaque burden). The improved graphical user interface provided herein includes displaying such information and providing the user with methods to manipulate that information as needed.
[0009] It is important to note that this invention can help physicians identify areas in blood vessels where the plaque load is less than a threshold level (e.g., 50%, etc.). This information can be used to identify stent landing sites (e.g., before percutaneous coronary intervention (PCI)) and to identify improperly placed stents (e.g., after PCI).
[0010] In some embodiments, the present invention may be implemented as a method. The method may include receiving a series of intravascular ultrasound (IVUS) images of a patient's blood vessel, the series of IVUS images comprising multiple frames; for each of the multiple frames, receiving an indication of plaque load in the blood vessel; generating a graphical component including an indication of plaque load relative to a threshold amount; generating a GUI including a longitudinal view of the blood vessel and the graphical component configured to indicate plaque load detected along the longitudinal axis of the blood vessel; and rendering the GUI for display on a monitor.
[0011] In another embodiment of the method, the graphics component is a first graphics component, and the method includes: generating a second graphics component including a longitudinal view of blood vessels; and generating a GUI including the first graphics component and the second graphics component.
[0012] In another embodiment, the method includes generating a GUI by overlaying a first graphical component onto a portion of a second graphical component to indicate plaque load along the longitudinal axis of the blood vessel.
[0013] In another embodiment of the method, the first graphic component includes lines disposed along a portion of the longitudinal axis of the blood vessel.
[0014] In another embodiment, the method includes: identifying whether the patch load is less than a threshold level for each of a plurality of frames; and overlaying lines onto a portion of a second graphic component associated with the frame in the plurality of frames where the patch load is less than the threshold level.
[0015] In another embodiment of the method, the second graphical component includes indications of distal brackets, proximal brackets, minimum region, vascular contour view, and a mirror image of the vascular contour view.
[0016] In another embodiment of the method, the vessel contour view includes a graphical representation of the vessel boundary and the lumen boundary of the vessel along the longitudinal axis.
[0017] In another embodiment of the method, the distal bracket includes one of a plurality of bracket graphical representations selected based on the location of the distal bracket relative to the patch load and threshold level.
[0018] In another embodiment, the method includes: identifying the location of a distal bracket; determining whether the distal bracket is associated with a frame in a plurality of frames where the patch load is less than a threshold level; and selecting a first of a plurality of bracket graphic representations based on the determination that the distal bracket is associated with a frame in a plurality of frames where the patch load is less than a threshold level; or selecting a second of a plurality of bracket graphic representations based on the determination that the distal bracket is not associated with a frame in a plurality of frames where the patch load is less than a threshold level.
[0019] In another embodiment of the method, the proximal bracket includes one of a plurality of graphical representations selected based on the location of the proximal bracket relative to the plaque load and threshold level.
[0020] In another embodiment, the method includes: identifying the location of a proximal bracket; determining whether the proximal bracket is associated with a frame in a plurality of frames where the patch load is less than a threshold level; and selecting a first of a plurality of bracket graphic representations based on the determination that the proximal bracket is associated with a frame in a plurality of frames where the patch load is less than a threshold level; or selecting a second of a plurality of bracket graphic representations based on the determination that the proximal bracket is not associated with a frame in a plurality of frames where the patch load is less than a threshold level.
[0021] In another embodiment, the method includes: generating a third graphics component comprising a cross-sectional view of one of a plurality of frames; and generating a GUI comprising a first graphics component, a second graphics component, and a third graphics component.
[0022] In another embodiment of the method, the GUI includes angiographic images of the blood vessels.
[0023] In some embodiments, the invention may be implemented as a device including a processor coupled to a memory including instructions executable by the processor, the processor being configured to be coupled to an intravascular ultrasound (IVUS) imaging system and configured to execute the instructions, which, when executed, cause the processor to implement the methods of any embodiment of the invention.
[0024] In some embodiments, the present invention may be implemented as at least one machine-readable storage device comprising a plurality of instructions responsive to execution by a processor of an intravascular ultrasound (IVUS) imaging system, the plurality of instructions causing the processor to implement the methods of any embodiment of the present invention.
[0025] In some embodiments, the present invention may be implemented as a computing device for a medical device. The computing device may include: a processor; an interface coupled to the processor for coupling to an intravascular ultrasound (IVUS) device; and a memory coupled to the processor, the memory including instructions executable by the processor, which, when executed, cause the computing device to: receive a series of IVUS images of a patient's blood vessels from the IVUS device, the IVUS images comprising multiple frames; for each of the multiple frames, receive an indication of plaque load in the blood vessel; generate a graphics component including an indication of plaque load relative to a threshold amount; generate a GUI including a longitudinal view of the blood vessel and the graphics component configured to indicate plaque load detected along the longitudinal axis of the blood vessel; and render the GUI for display on a monitor.
[0026] In another embodiment of the computing device, the graphics component is a first graphics component, and when executed by the processor, the instructions further cause the computing device to: generate a second graphics component including a longitudinal view of blood vessels; and generate a GUI including the first graphics component and the second graphics component.
[0027] In another embodiment of the computing device, when executed by the processor, the instructions further cause the computing device to overlay a first graphics component onto a portion of a second graphics component to indicate plaque load along the longitudinal axis of the blood vessel.
[0028] In another embodiment of the computing device, the first graphics component includes lines arranged along a portion of the longitudinal axis of the blood vessel.
[0029] In another embodiment of the computing device, the instructions, when executed by the processor, further cause the computing device to identify whether the patch load is less than a threshold level for each of the plurality of frames; and to overlay lines on portions of a second graphics component associated with the frames in the plurality of frames where the patch load is less than the threshold level.
[0030] In another embodiment of the computing device, the second graphics component includes indications of distal brackets, proximal brackets, a minimum region, a vessel contour view, and a mirror image of the vessel contour view, wherein the vessel contour view includes a graphical representation of the vessel boundary and the lumen boundary of the vessel along the longitudinal axis.
[0031] In another embodiment of the computing device, the distal bracket includes one of a plurality of bracket graphical representations selected based on the location of the distal bracket relative to the patch load and threshold level.
[0032] In another embodiment of the computing device, the instructions, when executed by the processor, further cause the computing device to: identify the location of the far bracket; determine whether the far bracket is associated with a frame in a plurality of frames where the patch load is less than a threshold level; and select a first of a plurality of bracket graphic representations based on the determination that the far bracket is associated with a frame in a plurality of frames where the patch load is less than a threshold level; or select a second of a plurality of bracket graphic representations based on the determination that the far bracket is not associated with a frame in a plurality of frames where the patch load is less than a threshold level.
[0033] In another embodiment of the computing device, the proximal bracket includes one of a plurality of graphical representations selected based on the location of the proximal bracket relative to the plaque load and threshold level.
[0034] In another embodiment of the computing device, the instructions, when executed by the processor, further cause the computing device to: identify the location of the proximal bracket; determine whether the proximal bracket is associated with a frame in a plurality of frames where the patch load is less than a threshold level; and select a first of a plurality of bracket graphic representations based on the determination that the proximal bracket is associated with a frame in a plurality of frames where the patch load is less than a threshold level; or select a second of a plurality of bracket graphic representations based on the determination that the proximal bracket is not associated with a frame in a plurality of frames where the patch load is less than a threshold level.
[0035] In another embodiment of the computing device, the instructions, when executed by the processor, further cause the computing device to generate a third graphics component including a cross-sectional view of one of a plurality of frames; and to generate a GUI including a first graphics component, a second graphics component, and a third graphics component, wherein the GUI includes an angiographic image of a blood vessel.
[0036] In another embodiment, the computing device includes an IVUS imaging apparatus.
[0037] In some embodiments, the present invention may be implemented as at least one machine-readable storage device comprising a plurality of instructions responsive to execution by a processor of an intravascular ultrasound (IVUS) imaging system including an IVUS device, the plurality of instructions causing the IVUS imaging system to: receive a series of IVUS images of a patient’s blood vessel from the IVUS device, the series of IVUS images comprising a plurality of frames; for each of the plurality of frames, receive an indication of plaque load in the blood vessel; generate a graphics component including an indication of plaque load relative to a threshold amount; generate a GUI including a longitudinal view of the blood vessel and the graphics component configured to indicate plaque load detected along the longitudinal axis of the blood vessel; and render the GUI for display on a display.
[0038] In another embodiment of at least one machine-readable storage device, the graphics component is a first graphics component, and the instructions, when executed by a processor, further cause the IVUS imaging system to: generate a second graphics component including a longitudinal view of the blood vessels; generate a GUI including the first graphics component and the second graphics component; and overlay the first graphics component onto a portion of the second graphics component to indicate plaque load along the longitudinal axis of the blood vessels.
[0039] In another embodiment of at least one machine-readable storage device, the first graphics component includes lines disposed along a portion of the longitudinal axis of the blood vessel, and the instructions, when executed by a processor, further cause the IVUS imaging system to: identify whether the plaque load is less than a threshold level for each of the plurality of frames; and to overlay the lines onto a portion of the second graphics component associated with the frames in the plurality of frames where the plaque load is less than the threshold level.
[0040] In another embodiment of at least one machine-readable storage device, the second graphics component includes indications of distal brackets, proximal brackets, a minimum region, a vessel contour view, and a mirror image of the vessel contour view, wherein the vessel contour view includes a graphical representation of the vessel boundary and the lumen boundary of the vessel along a longitudinal axis.
[0041] In another embodiment of at least one machine-readable storage device, the distal bracket includes one of a plurality of bracket graphic representations selected based on the location of the distal bracket relative to plaque load and a threshold level, and the instructions, when executed by a processor, further cause the IVUS imaging system to: identify the location of the distal bracket; determine whether the distal bracket is associated with a frame in the plurality of frames where the plaque load is less than a threshold level; and select a first of the plurality of bracket graphic representations based on the determination that the distal bracket is associated with a frame in the plurality of frames where the plaque load is less than a threshold level; or select a second of the plurality of bracket graphic representations based on the determination that the distal bracket is not associated with a frame in the plurality of frames where the plaque load is less than a threshold level. Attached Figure Description
[0042] To facilitate identification of any discussion of a component or behavior, the highest digit or more digits in the figure references refer to the figure number in which the component is first introduced.
[0043] Figure 1 This illustrates one aspect of the subject matter according to one embodiment.
[0044] Figure 2 This illustrates one aspect of the subject matter according to one embodiment.
[0045] Figure 3A This illustrates one aspect of the subject matter according to one embodiment.
[0046] Figure 3B This illustrates one aspect of the subject matter according to one embodiment.
[0047] Figure 4 An IVUS image visualization system 400 according to an embodiment of the present invention is shown.
[0048] Figure 5A This illustrates one aspect of the subject matter according to one embodiment.
[0049] Figure 5B This illustrates one aspect of the subject matter according to one embodiment.
[0050] Figure 6 This illustrates one aspect of the subject matter according to one embodiment.
[0051] Figure 7 This illustrates one aspect of the subject matter according to one embodiment.
[0052] Figure 8 A logic flow 800 according to one embodiment is shown.
[0053] Figure 9 A computer-readable storage medium 900 according to one embodiment is shown.
[0054] Figure 10 The illustration shows a machine 1000 in the form of a computer system according to an example embodiment, within which a set of instructions can be executed to cause the machine to perform any or more of the methods discussed herein. Detailed Implementation
[0055] The features and technical advantages of the invention have been summarized above, which will facilitate a better understanding of the following detailed description. Those skilled in the art will understand that the disclosed embodiments can be readily used as the basis for modifications or the design of other structures to achieve the same objectives as the invention. The novel features of the invention with respect to its organization and operation, as well as further objects and advantages, will be better understood from the following description when considered in conjunction with the accompanying drawings. However, it should be clearly understood that each of the figures is provided for illustrative and descriptive purposes and is not intended to be a definition of the scope of the invention.
[0056] As noted, this invention relates to IVUS systems and the automated evaluation of IVUS images. In particular, the invention provides a graphical user interface (GUI) arranged to convey information related to IVUS images and lesion evaluation and to provide the user with the ability to manipulate that information. Therefore, an example IVUS imaging system, patient vessels, and a series of IVUS images are described.
[0057] Suitable IVUS imaging systems include, but are not limited to, one or more transducers disposed on the distal end of a catheter configured and arranged for percutaneous insertion into a patient. Examples of IVUS imaging systems with catheters can be found, for example, in U.S. Patent Nos. 7,246,959; 7,306,561; and 6,945,938, and U.S. Patent Application Publication Nos. 2006 / 0100522; 2006 / 0106320; 2006 / 0173350; 2006 / 0253028; 2007 / 0016054; and 2007 / 0038111; all of which are incorporated herein by reference.
[0058] Figure 1 An embodiment of an IVUS imaging system 100 is shown. The IVUS imaging system 100 includes a catheter 102 that can be coupled to a control system 104. The control system 104 may include, for example, a processor 106, a pulse generator 108, and a drive unit 110. The pulse generator 108 generates electrical pulses that can be input to one or more transducers (not shown) disposed in the catheter 102.
[0059] In some embodiments, mechanical energy from the drive unit 110 can be used to drive an imaging core (also not shown) disposed in the conduit 102. In at least some embodiments, electrical signals transmitted from one or more transducers can be input to the processor 106 for processing. In at least some embodiments, the processed electrical signals from one or more transducers can be used to form a series of images, as described in more detail below. For example, a scan converter can be used to map scan line samples (e.g., radial scan line samples, etc.) onto a two-dimensional Cartesian grid, which can be used as the basis for a series of IVUS images displayed to the user.
[0060] In at least some embodiments, processor 106 may also be used to control the operation of one or more other components of control system 104. For example, processor 106 may be used to control at least one of the frequency or duration of electrical pulses transmitted from pulse generator 108, and the rotational rate of the imaging core driven by drive unit 110. Additionally, when IVUS imaging system 100 is configured for automatic pull-back, drive unit 110 may control the speed and / or length of pull-back.
[0061] Figure 2Image 200 shows a patient's blood vessel 202. As described, an IVUS imaging system (e.g., IVUS imaging system 100, etc.) is used to capture a series of images or "records" of a blood vessel, such as blood vessel 202. For example, an IVUS catheter (e.g., catheter 102) is inserted into blood vessel 202, and as catheter 102 is pulled back from distal end 204 to proximal end 206, a record or series of IVUS images is captured. Catheter 102 can be pulled back manually or automatically (e.g., under the control of a drive unit 110, etc.).
[0062] Figure 3A and Figure 3B A two-dimensional (2D) representation of an IVUS image of vessel 202 is shown. For example, Figure 3A IVUS image 300a shows a longitudinal view of an IVUS record depicting blood vessel 202 between proximal 206 and distal 204.
[0063] Figure 3B Image frame 300b is shown, depicting an on-axis (or minor axis or cross-section) view of blood vessel 202 at point 302. In other words, image frame 300b is a single frame or single image from a series of IVUS images that may be captured between distal end 204 and proximal end 206, as described herein. As described above, the present invention provides systems and techniques for processing raw IVUS images to identify regions of interest in a series of IVUS images, such as, for example, start and end points, between which frames of interest are included.
[0064] For example, IVUS image 300a depicts a series of IVUS images of vessel 202 taken between distal end 204 and proximal end 206. IVUS images can be captured at several stages of percutaneous coronary intervention (PCI). That is, IVUS can be used before, during, or after PCI. For example, IVUS can be used before stent implantation to capture images of the state of vessel 202. In such examples, automated evaluation of the images can be performed (e.g., vessel boundary detection, lumen boundary detection, plaque burden detection, keyframe recognition, stent size and parking area recommendation, stent expansion estimation, calcium detection, etc.). It should be understood that this involves a significant amount of information to be conveyed to the user. Furthermore, the prior art does not provide a way to convey this information and the IVUS images (e.g., IVUS images 300a and 300b) in a manner that allows the user to visualize the vascular structure and occlusion or stenosis. Therefore, the advantage provided by the present invention is that the improved GUI provides a better understanding of the physiological structure of the vessel and allows manipulation of the features of the images.
[0065] Figure 4An IVUS image visualization system 400 according to some embodiments of the present invention is illustrated. Generally, the IVUS image visualization system 400 is a system for processing, annotating, and presenting IVUS images. The IVUS image visualization system 400 may be available in commercial IVUS guidance or navigation systems, such as, for example, those available from Boston... Commercial purchase Implemented in a guided system. This invention offers advantages over existing or conventional IVUS navigation systems because the improved GUI reduces the time required for patient treatment. For example, this invention enables implementation in an IVUS navigation system to effectively transmit information about vascular physiological structures to the user and allow the user to manipulate that information, thereby reducing patient treatment time.
[0066] In some embodiments, the IVUS image visualization system 400 may be implemented as part of the control system 104. Alternatively, the control system 104 may be implemented as part of the IVUS image visualization system 400. As depicted, the IVUS image visualization system 400 includes a computing device 402. Optionally, the IVUS image visualization system 400 includes an IVUS imaging system 100 and a display 404.
[0067] The computing device 402 can be any of a variety of computing devices. In some embodiments, the computing device 402 may be incorporated into and / or implemented by the console of the display 404 (e.g., as a desktop computer, etc.). In some embodiments, the computing device 402 may be a workstation or server communicatively connected to the IVUS imaging system 100 and / or the display 404. In other embodiments, the computing device 402 may be provided by a cloud-based computing device, such as a compute-as-a-service system accessible via a network (e.g., the Internet, an intranet, a wide area network, etc.). The computing device 402 may include a processor 406, a memory 408, input and / or output (I / O) devices 410, a network interface 412, and IVUS imaging system acquisition circuitry 414.
[0068] Processor 406 may include circuitry or processor logic, such as, for example, any of a variety of commercial processors. In some examples, processor 406 may include multiple processors, multi-threaded processors, multi-core processors (whether multiple cores coexist on the same die or on separate dies), and / or some other type of multiprocessor architecture, where multiple physically separate processors are linked together in some way by the aforementioned multiprocessor architecture. Additionally, in some examples, processor 406 may include a graphics processing section and may include dedicated memory, multi-threaded processing, and / or some other parallel processing capabilities. In some examples, processor 406 may be an application-specific integrated circuit (ASIC) or a field-programmable integrated circuit (FPGA).
[0069] Memory 408 may include logic, a portion of which includes an array of integrated circuits to form non-volatile memory for persistent storage of data or a combination of non-volatile and volatile memory. It should be understood that memory 408 may be based on any of a variety of technologies. In particular, the array of integrated circuits included in memory 120 may be arranged to form one or more types of memory, such as, for example, dynamic random access memory (DRAM), NAND memory, NOR memory, etc.
[0070] I / O device 410 can be any of a variety of devices for receiving input and / or providing output. For example, I / O device 410 may include a keyboard, mouse, joystick, foot pedal, display, touch-enabled display, haptic feedback device, LED, etc.
[0071] Network interface 412 may include logical and / or features for supporting communication interfaces. For example, network interface 412 may include one or more interfaces operating according to various communication protocols or standards for communication via direct or network communication links. Direct communication may occur via communication protocols or standards described in one or more industry standards (including their successors and variations). For example, network interface 412 may facilitate communication via buses such as, for example, Peripheral Component Interconnect High Speed (PCIe), Non-Volatile Memory High Speed (NVMe), Universal Serial Bus (USB), System Management Bus (SMBus), SAS (e.g., Serial Attached Small Computer System Interface (SCSI)) interfaces, Serial AT Attachment (SATA) interfaces, etc. Additionally, network interface 412 may include logical and / or features for enabling communication via various wired or wireless network standards (e.g., the 802.11 communication standard). For example, network interface 412 may be configured to support wired communication protocols or standards such as Ethernet, etc. As another example, network interface 412 may be configured to support wireless communication protocols or standards, such as, for example, Wi-Fi, Bluetooth, ZigBee, LTE, 5G, etc.
[0072] IVUS imaging system acquisition circuit 414 may include circuitry including custom-made or specially programmed circuitry configured to receive or receive and transmit signals between IVUS imaging systems 100, including IVUS operation, a series of IVUS images, or frames or multiple frames of IVUS images.
[0073] Memory 408 may include instructions 416. During operation, processor 406 may execute instructions 416 to cause computing device 402 to receive (e.g., from IVUS imaging system 100, etc.) a record of “IVUS run” and store the record as an IVUS image in memory 408. For example, processor 406 may execute instructions 416 to receive information elements from IVUS imaging system 100, including indications of IVUS images captured by catheter 102 as it is pulled back from distal 204 to proximal 206, the images including indications of the anatomy and / or structures (including vessel walls and plaques) of vessel 202. It should be understood that IVUS images 418 may include various image formats or even non-image formats or data structures for storing indications of vessel 202. Furthermore, IVUS images 418 include several “frames” or individual images that, when collinearly represented, can be used to form an image of vessel 202, such as, for example, represented by IVUS images 300a and / or 300b.
[0074] This invention provides for generating graphic information elements 420 from an IVUS image 418 and generating a GUI 422 to be displayed on a display 404 based on the graphic information elements 420. The processor 406 may also be configured to execute instructions 416 to generate an evaluation 424 based on the IVUS image 418. This will be described in more detail below. However, typically, evaluations may include vessel boundary detection, lumen boundary detection, plaque load determination, keyframe recognition, distance between keyframes, stent detection, stent expansion estimation, calcium detection, and other evaluations. Therefore, in some embodiments, the graphic information element 420 may be generated based on the IVUS image 418 and the evaluation 424.
[0075] Memory 408 may also include other images 426, such as, for example, angiographic images (e.g., image 200, etc.). In some examples, processor 406 may execute instructions 416 to generate graphic information elements 420 that include indications and evaluations 424 of the other images 426. In some examples, the other images 426 may be linked to or mapped to IVUS image 418, and graphic information elements 420 may be overlaid on a representation of frames of IVUS image 418 or other images 426.
[0076] Figure 5A A GUI 500a, which can be generated according to some embodiments of the present invention, is shown. For example, GUI 500a can be generated as a GUI 422 by an IVUS image visualization system 400 and displayed on a display 404. As depicted, GUI 500a includes several graphical information elements 420, such as menus 502a and 502b, an interactive cross-sectional view 504, an interactive vascular navigation 506, and a long vascular view 508.
[0077] In some embodiments, processor 406 may be configured to execute instructions 416 to generate GUI 500a. As another example, processor 406 may execute instructions 416 to generate GUI 500a in response to an automated plaque load detection process. For example, in some embodiments, IVUS image visualization system 400 may be arranged to automatically detect plaque load of blood vessel 202 represented by calcium in IVUS image 418 (e.g., via machine learning, image classification, etc.).
[0078] Menu 502a may include GUI inputs such as buttons, drop-down menus, and selection icons. Menu 502a may include GUI input options to select measurement and annotation tools, length tools, modification / reset buttons, etc. Menu 502b may include GUI inputs such as buttons, drop-down menus, and selection icons. Menu 502b may include GUI input options to select views related to IVUS images, layout options, annotations, navigation, dynamic review options, computing device status, etc.
[0079] Interactive cross-sectional view 504 may include a cross-sectional view of one of the IVUS images 418 (e.g., a frame, etc.). For example, interactive cross-sectional view 504 may include image frame 300b and evaluation 510, as well as indications of vessel and lumen boundaries. A detailed description of interactive vascular navigation 506 is provided below. However, typically, interactive vascular navigation 506 may include a navigation slider to navigate through IVUS image 418, which is linked to interactive cross-sectional view 504. That is, as the slider moves, the image displayed in interactive cross-sectional view 504 changes to match the position indicated by the slider.
[0080] The long view 508 may include a longitudinal view of a blood vessel (e.g., vessel 202) represented by IVUS image 418. For example, the long view 508 may include a representation of the vessel and lumen contours, as well as an assessment 512. The long view 508 may include a graphical representation of IVUS image 300a. In some embodiments, an assessment 512 may be included to represent plaque load detected along vessel 202. Additionally, the long view 508 may include keyframe markers (e.g., locations that may indicate, for example, the positions of distal and proximal frames, such as distal and proximal keyframes, linearly along a series of IVUS images 418, using brackets, etc.).
[0081] Figure 5BAn example long view 508 of a blood vessel is shown according to some embodiments of the present invention. An IVUS image visualization system 400 is configurable to generate the long view 508 of the blood vessel as a graphical component of a GUI 500a. As depicted, the long view 508 of the blood vessel includes several GUI components (or sub-graphical components) including a central axis 514, a longitudinal boundary contour 516, and a longitudinal boundary contour mirror reflection 518 disposed around the central axis 514. Examples of the longitudinal boundary contours 516 and 518 are given below. However, typically, the longitudinal boundary contour 516 depicts or represents a boundary (e.g., boundary 604, etc.) detected for the IVUS image 418. The longitudinal boundary contour mirror reflection 518 is a mirror reflection of the longitudinal boundary contour 516, thereby providing a more complete visualization of the vessel and lumen contours.
[0082] The long view of the vessel 508 also includes a scale 520 depicting the radius of the detected boundary in the longitudinal boundary contour 516. Additionally, the long view of the vessel 508 includes a proximal bracket end 522, a distal bracket end 524, and a minimum region 528. Each of the brackets is movable via user input (e.g., via I / O device 410). In some examples, the proximal bracket end 522 and the distal bracket end 524 may be automatically positioned at an initial location based on their relevance to the detected lumen size, the location of a stent in the detected vessel 202, etc. Furthermore, in some embodiments, the proximal bracket end 522 and / or the distal bracket end 524 may have one graphical representation when located in a region where the detected plaque load of the vessel 202 is less than a threshold amount (e.g., 50%, etc.), and another different graphical representation when located in a region where the detected plaque load of the vessel 202 is greater than or equal to the threshold amount. For example, the proximal bracket end 522 is depicted with a different graphical representation than the distal bracket end 524. As described above, the positions of the proximal bracket end 522 and the distal bracket end 524 are interactive, as they can be manipulated by the user (e.g., via input and / or output (I / O) devices 410, etc.). Therefore, the processor 406 can execute instructions 416 to dynamically generate the proximal bracket end 522 and / or the distal bracket end 524 based on its manipulation position relative to the detected plaque load and a threshold. For example, if the user moves the proximal bracket end 522 more proximally, such that the proximal bracket end 522 is located in the region specified by the plaque load indicator 530 (e.g., the detected plaque load is less than a threshold amount), the processor 406 can execute instructions 416 to generate a proximal bracket end 522 with a graphical representation similar to the distal bracket end 524. Similarly, if the user moves the distal bracket end 524 closer to the proximal side, such that the distal bracket end 524 is outside the area specified by the plaque load indicator 530 (e.g., the detected plaque load is greater than or equal to a threshold amount), the processor 406 may execute instruction 416 to generate a distal bracket end 524 having a graphical representation similar to the proximal bracket end 522.
[0083] Finally, the long view of the blood vessel 508 includes a graphical indication of the detected plaque burden, shown as a plaque burden indicator 530. Additionally, in some examples, a scale 526 may be enabled (e.g., by default, via an input button selection, etc.) and may measure the distance between brackets (e.g., the proximal bracket end 522 and the distal bracket end 524).
[0084] Figure 6 A GUI 600 that can be generated according to some embodiments of the present invention is shown. For example, GUI 600 may be generated as GUI 422 by IVUS image visualization system 400 and displayed on display 404. In some embodiments, in response to plaque load detected by blood vessel 202, processor 406 may execute instructions 416 to generate graphical information element 420 and GUI 600 based on graphical information element 420.
[0085] As shown in the figure, GUI 600 includes an interactive cross-sectional view 504 and an interactive vascular navigation 506. The interactive cross-sectional view 504 includes a cross-sectional view of frames of IVUS image 418 (e.g., corresponding to the position of slider 602), and various assessments 510, such as indications of boundaries 604 (e.g., vessel boundaries, lumen boundaries, etc.), plaque burden, frame number, pull-back distance, etc. Furthermore, GUI 600 includes interactive vascular navigation 506, which includes an interactive slider 602 that can be used for navigation through the IVUS image 418 presented in GUI 600.
[0086] Additionally, GUI 600 includes a long view of the vessel 508 depicting a longitudinal boundary contour 516 and a mirror reflection of the longitudinal boundary contour 518, as well as a proximal bracket end 522, a distal bracket end 524, and a plaque load indicator 530. As can be seen, the plaque load indicator 530 indicates the region in the vessel 202 represented by IVUS image 418 where the detected plaque load is less than a threshold amount (e.g., 50%). Furthermore, the graphical representation of the proximal bracket end 522 and the distal bracket end 524 may depend on their location relative to the detected plaque load amount and the threshold level. Specifically, as depicted in GUI 600, the proximal bracket end 522 is located in the region in the vessel 202 where the detected plaque load is greater than or equal to the threshold level, and therefore has a first graphical representation (e.g., a straight line with an "X" at the end), while the distal bracket end 524 is located in the region in the vessel 202 where the detected plaque load is less than the threshold level, and therefore has a second graphical representation (e.g., a straight line with a curved end).
[0087] Figure 7A GUI 700 that can be generated according to some embodiments of the present invention is shown. For example, GUI 700 can be generated as GUI 422 by IVUS image visualization system 400 and displayed on display 404. In some embodiments, in response to detecting plaque load on blood vessel 202, processor 406 can execute instructions 416 to generate graphical information element 420 and GUI 700 based on graphical information element 420.
[0088] In addition to the indication of the angiographic image of vessel 202 represented by IVUS image 418, GUI 700 includes graphical elements similar to those in 600. GUI 700 includes image 200, as well as an interactive cross-sectional view 504, an interactive vessel navigation 506, and a long-view vessel view 508. In some examples, graphical indications of distal and proximal keyframes (e.g., proximal bracket end 522 and distal bracket end 524) may be presented on image 200. Furthermore, as shown, interactive vessel navigation 506 includes IVUS image 300a (e.g., the actual IVUS image 418).
[0089] Figure 8 A logical flow 800 for generating a GUI is illustrated according to some embodiments of the present invention. The logical flow 800 may be implemented by an IVUS image visualization system 400, and for clarity, will be described with reference to the IVUS image visualization system 400. However, it is worth noting that the logical flow 800 may also be implemented by an IVUS bootstrapping system different from the IVUS image visualization system 400.
[0090] Logic flow 800 may begin at block 802. In block 802, “Receiving a series of intravascular ultrasound (IVUS) images of a patient’s vessel, the series of IVUS images comprising multiple frames,” a series of IVUS images captured via an IVUS catheter percutaneously inserted into a patient’s vessel may be received. For example, information elements including an indication of IVUS image 418 may be received from IVUS imaging system 100, wherein catheter 102 is percutaneously inserted into vessel 202. IVUS image 418 may include image frames representing images captured as catheter 102 is pulled back from distal end 204 to proximal end 206. Processor 406 may execute instructions 416 to receive information elements including an indication of IVUS image 418 from IVUS imaging system 100 or directly from catheter 102 (as applicable).
[0091] Continuing to box 804, “Receiving an indication of vascular plaque load for each of a plurality of frames,” an indication of vascular plaque load is received for each of the plurality of frames. For example, processor 406 may execute instruction 416 to receive (e.g., from a machine learning model, etc.) an indication of vascular plaque load based on frames of IVUS image 418. Continuing to box 806, “Generating a graphical component including an indication of plaque load relative to a threshold level,” a graphical component including an indication of plaque load relative to a threshold level is generated. For example, processor 406 may execute instruction 416 to generate a plaque load indicator 530 including an indication of regions in vessel 202 where plaque load is detected to be less than a threshold level. As a specific example, processor 406 may execute instruction 416 to generate plaque load indicator 530, which includes lines covering a representation of frames in IVUS image 418 where plaque load is detected to be less than a threshold level (e.g., 50%, etc.).
[0092] Continuing to box 808, "Generate a GUI including a longitudinal view of the blood vessel and graphical components configured to indicate plaque load detected along the longitudinal axis of the blood vessel," the processor 406 may execute instruction 416 to generate a GUI 422 including a longitudinal view of the blood vessel 508 and indicators (e.g., proximal bracket end 522, distal bracket end 524, plaque load indicator 530, etc.). Continuing to box 810, "Render the GUI for display," the processor 406 may render the GUI for display. For example, the processor 406 may execute instruction 416 to generate GUI 422 for display on display 404.
[0093] Figure 9A computer-readable storage medium 900 is shown. The computer-readable storage medium 900 may include any non-transitory computer-readable or machine-readable storage medium, such as optical, magnetic, or semiconductor storage media. In various embodiments, the computer-readable storage medium 900 may include an article of manufacture. In some embodiments, the computer-readable storage medium 900 may store computer-executable instructions 902 executable by circuitry (e.g., processor 106, processor 406, IVUS imaging system acquisition circuitry 414, etc.). For example, the computer-executable instructions 902 may include instructions for implementing operations described with respect to instructions 416, logic flow 800, graphical information element 420, and / or GUI 422. Examples of computer-readable or machine-readable storage media 900 may include any tangible medium capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, and so on. Examples of computer-executable instructions 902 may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, etc.
[0094] Figure 10 A diagram is shown of a machine 1000 in the form of a computer system, within which a set of instructions can be executed to cause the machine to perform any or more of the methods discussed herein. More specifically, Figure 10 The illustration shows a machine 1000 in an example form employing a computer system, within which executable instructions 1008 (e.g., software, programs, applications, applets, applications, or other executable code) cause the machine 1000 to perform any or more of the methods discussed herein. For example, instruction 1008 may cause the machine 1000 to execute... Figure 8 Logic flow 800 Figure 4 Instruction 416. More generally, instruction 1008 enables machine 1000 to generate a GUI with the functions and behaviors described herein before, during, or after a PCI using IVUS. It should be noted that the present invention provides specific and discrete implementations of GUI representation and behavior, which are significant improvements over the prior art. In particular, the present invention provides improvements to computing techniques because the GUI provides better visibility and navigation of IVUS images.
[0095] Instruction 1008 transforms a general, unprogrammed machine 1000 into a specific machine 1000 programmed to perform the described and illustrated functions in a particular manner. In alternative embodiments, machine 1000 operates as a standalone device or is connectable (e.g., networked) to other machines. In a networked deployment, machine 1000 may operate as a server machine or client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. Machine 1000 may include, but is not limited to, server computers, client computers, personal computers (PCs), tablet computers, laptop computers, netbooks, set-top boxes (STBs), PDAs, entertainment media systems, cellular phones, smartphones, mobile devices, wearable devices (e.g., smartwatches), smart home devices (e.g., smart appliances), other smart devices, network devices, network routers, network switches, bridges, or any machine capable of sequentially or otherwise executing instructions 1008 specifying actions to be taken by machine 1000. Furthermore, although only a single machine 1000 is shown, the term "machine" should also be considered as a collection of machines 1000 that individually or jointly execute instructions 1008 to perform any one or more of the methods discussed herein.
[0096] Machine 1000 may include processor 1002, memory 1004, and I / O components 1042, which may be configured to communicate with each other, for example, via bus 1044. In one example embodiment, processor 1002 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an ASIC, a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1006 and processor 1010 that can execute instructions 1008. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") capable of executing instructions simultaneously. Although Figure 10 Multiple processors 1002 are shown, but machine 1000 may also include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.
[0097] Memory 1004 may include main memory 1012, static memory 1014, and memory cell 1016, all of which may be accessed by processor 1002, for example, via bus 1044. Main memory 1004, static memory 1014, and memory cell 1016 store instructions 1008 that embodied one or more of the methods or functions described herein. During execution of instructions 1008 by machine 1000, instructions 1008 may also reside wholly or partially in main memory 1012, static memory 1014, machine-readable medium 1018 within memory cell 1016, at least one of processors 1002 (e.g., within the processor's cache), or any suitable combination thereof.
[0098] I / O component 1042 may include a wide variety of components to receive input, provide output, generate output, transmit information, exchange information, capture measurement results, and so on. The specific I / O component 1042 included in a particular machine will depend on the type of machine. For example, a portable machine, such as a mobile phone, may include a touch input device or other such input mechanism, while a headless server machine may not include such a touch input device. It should be understood that I / O component 1042 may include... Figure 10 Many other components are not shown. The I / O components 1042 are grouped according to function only for the sake of simplicity in the discussion below, and this grouping is by no means limiting. In various example embodiments, the I / O components 1042 may include output components 1028 and input components 1030. Output components 1028 may include visual components (e.g., displays, such as plasma display panels (PDPs), light-emitting diode (LED) displays, liquid crystal displays (LCDs), projectors, or cathode ray tubes (CRTs)), acoustic components (e.g., speakers), haptic components (e.g., vibration motors, resistance mechanisms), other signal generators, and so on. Input components 1030 may include alphanumeric input components (e.g., keyboards, touchscreens configured to receive alphanumeric input, photoelectric keyboards, or other alphanumeric input components), point-based input components (e.g., mice, touchpads, trackballs, joysticks, motion sensors, or other pointing devices), haptic input components (e.g., physical buttons, touchscreens providing position and / or force for touch or touch gestures, or other haptic input components), audio input components (e.g., microphones), and so on.
[0099] In another example embodiment, I / O component 1042 may include biometric component 1032, motion component 1034, environmental component 1036 or position component 1038, and various other components. For example, biometric component 1032 may include components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body posture, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), and identifying a person (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition). Motion component 1034 may include accelerometer components (e.g., accelerometer), gravity sensor components, rotation sensor components (e.g., gyroscope), etc. Environmental component 1036 may include, for example, an illuminance sensor component (e.g., a photometer), a temperature sensor component (e.g., one or more thermometers for detecting ambient temperature), a humidity sensor component, a pressure sensor component (e.g., a barometer), an acoustic sensor component (e.g., one or more microphones for detecting background noise), a proximity sensor component (e.g., an infrared sensor for detecting nearby objects), a gas sensor (e.g., a gas detection sensor for detecting hazardous gas concentrations to ensure safety or measuring pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment. Position component 1038 may include a position sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer for detecting air pressure from which altitude can be derived), an orientation sensor component (e.g., a magnetometer), etc.
[0100] Communication can be implemented using various technologies. I / O component 1042 may include a communication component 1040 operable to connect machine 1000 to network 1020 or device 1022 via coupler 1024 and coupler 1026, respectively. For example, communication component 1040 may include a network interface component or another suitable device interfacing with network 1020. In further examples, communication component 1040 may include wired communication components, wireless communication components, cellular communication components, near field communication (NFC) components, etc. Components (e.g.) (low power consumption) Components and other communication components that provide communication via other means. Device 1022 can be any of another machine or various peripheral devices (e.g., a peripheral device connected via USB).
[0101] Furthermore, the communication component 1040 may detect identifiers or include components operable to detect identifiers. For example, the communication component 1040 may include a radio frequency identification (RFID) tag reader, an NFC smart tag detection component, an optical reader (e.g., for detecting one-dimensional barcodes such as Universal Product Code (UPC) barcodes, multi-dimensional barcodes such as Quick Response (QR) codes, Aztec codes, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D barcodes, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying audio signals from tags). Additionally, various information can be exported via the communication component 1040, such as location via Internet Protocol (IP) geolocation, etc. The location of signal triangulation, the location of NFC beacon signals that can be detected to indicate a specific location, and so on.
[0102] Various memories (i.e., memory 1004, main memory 1012, static memory 1014, and / or the memory of processor 1002) and / or storage units 1016 may store one or more sets of instructions and data structures (e.g., software) that embody or are utilized by any one or more of the methods or functions described herein. These instructions (e.g., instruction 1008) cause various operations to implement the disclosed embodiments when executed by processor 1002.
[0103] As used herein, the terms “machine storage medium,” “device storage medium,” and “computer storage medium” refer to the same thing and are used interchangeably in this invention. The terms refer to one or more storage devices and / or media (e.g., centralized or distributed databases and / or associated caches and servers) that store executable instructions and / or data. Therefore, the terms should be considered accordingly to include, but are not limited to, solid-state memory and optical and magnetic media, including memory internal or external to the processor. Specific examples of machine storage media, computer storage media, and / or device storage media include non-volatile memory, such as semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGAs, and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms “machine storage medium,” “computer storage medium,” and “device storage medium” explicitly exclude carrier waves, modulated data signals, and other such media, at least some of which are covered under the term “signal medium” discussed below.
[0104] In various example embodiments, one or more portions of network 1020 may be an ad hoc network, intranet, extranet, VPN, LAN, WLAN, WAN, WWAN, MAN, the Internet, a portion of the Internet, a portion of PSTN, a common old-style telephone service (POTS) network, a cellular telephone network, a wireless network, etc. The network, another type of network, or a combination of two or more such networks. For example, network 1020 or a portion thereof may include a wireless or cellular network, and coupler 1024 may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile Communications (GSM) connection, or another type of cellular or wireless connection. In this example, coupler 1024 may implement any of a variety of data transmission technologies, such as Single Carrier Radio Transmission (1xRTT), Evolved Data Optimization (EVDO), General Packet Radio Service (GPRS), Enhanced Data Rate Evolution of GSM (EDGE), 3rd Generation Partnership Project (3GPP) (including 3G), 4th Generation Wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High-Speed Packet Access (HSPA), Global Microwave Access Interoperability (WiMAX), Long Term Evolution (LTE) standards, other standards defined by various standards-setting organizations, other remote protocols, or other data transmission technologies.
[0105] Instruction 1008 may be transmitted or received via network 1020 using a transmission medium via a network interface device (e.g., a network interface device included in communication component 1040) and utilizing any of several well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)). Similarly, instruction 1008 may be transmitted or received via a transmission medium via a coupler 1026 (e.g., a peer-to-peer coupler) to device 1022. The terms "transmission medium" and "signal medium" refer to the same thing and are used interchangeably in this invention. The terms "transmission medium" and "signal medium" should be considered to include any intangible medium that can store, encode, or carry instructions 1008 for execution by machine 1000; and include digital or analog communication signals or other intangible media to facilitate communication of such software. Therefore, the terms "transmission medium" and "signal medium" should be considered to include any form of modulated data signal, carrier wave, etc. The term "modulated data signal" refers to a signal whose characteristics are set or altered to encode information in the signal.
[0106] The terms used in this document should conform to their common meaning in the relevant field, or the meaning indicated by their use in the context, unless a clear definition is provided.
[0107] In this document, references to “an embodiment” or “one embodiment” do not necessarily refer to the same embodiment, although they may refer to the same embodiment. Unless the context explicitly requires otherwise, throughout the specification and claims, the words “comprising,” “including,” etc., should be interpreted in an inclusive sense, rather than an exclusive or exhaustive sense; that is, meaning “including but not limited to.” Use of singular or plural terms also includes both singular and plural, unless explicitly limited to one or more. Additionally, the words “this document,” “above,” “below,” and similar terms, when used in this application, refer to the entire application and not any part thereof. When a claim uses the word “or” to refer to a list of two or more items, the word covers all of the following interpretations: any one of the items in the list, all the items in the list, and any combination of the items in the list, unless explicitly limited to one or the other. Any term not explicitly defined herein has its conventional meaning as commonly understood by one of ordinary skill in the art.
[0108] By using real anatomical models, surgical plans can be developed more accurately than those developed through statistical modeling.
[0109] The terms used in this document shall conform to their ordinary meaning in the relevant field, or the meaning indicated by their use in the context, unless a clear definition is provided.
[0110] In this document, references to “an embodiment” or “one embodiment” do not necessarily refer to the same embodiment, although they may refer to the same embodiment. Unless the context explicitly requires otherwise, throughout the specification and claims, the words “comprising,” “including,” etc., should be interpreted in an inclusive sense, rather than an exclusive or exhaustive sense; that is, meaning “including but not limited to.” Use of singular or plural terms also includes both singular and plural, unless explicitly limited to one or more. Additionally, the words “this document,” “above,” “below,” and similar terms, when used in this application, refer to the entire application and not any part thereof. When a claim uses the word “or” to refer to a list of two or more items, the word covers all of the following interpretations: any one of the items in the list, all the items in the list, and any combination of the items in the list, unless explicitly limited to one or the other. Any term not explicitly defined herein has its conventional meaning as commonly understood by one of ordinary skill in the art.
[0111] By using real anatomical models, surgical plans can be developed more accurately than those developed through statistical modeling.
[0112] The terms used in this document shall conform to their ordinary meaning in the relevant field, or the meaning indicated by their use in the context, unless a clear definition is provided.
[0113] In this document, references to “an embodiment” or “one embodiment” do not necessarily refer to the same embodiment, although they may refer to the same embodiment. Unless the context explicitly requires otherwise, throughout the specification and claims, the words “comprising,” “including,” etc., should be interpreted in an inclusive sense, rather than an exclusive or exhaustive sense; that is, meaning “including but not limited to.” Use of singular or plural terms also includes both singular and plural, unless explicitly limited to one or more. Additionally, the words “this document,” “above,” “below,” and similar terms, when used in this application, refer to the entire application and not any part thereof. When a claim uses the word “or” to refer to a list of two or more items, the word covers all of the following interpretations: any one of the items in the list, all the items in the list, and any combination of the items in the list, unless explicitly limited to one or the other. Any term not explicitly defined herein has its conventional meaning as commonly understood by one of ordinary skill in the art.
Claims
1. A method comprising: Receive a series of intravascular ultrasound (IVUS) images of the patient's blood vessels, the series of IVUS images comprising multiple frames; For each of the plurality of frames, an indication of plaque load in the blood vessel is received; Generate a graphical component, the graphical component including an indication of the patch load relative to a threshold amount; Generate a GUI, the GUI including a longitudinal view of the blood vessel and the graphics component configured to indicate plaque load detected along the longitudinal axis of the blood vessel; as well as Render the GUI to display it on the screen.
2. The method according to claim 1, wherein the graphics component is a first graphics component, the method comprising: Generate a second graphics component that includes the longitudinal view of the blood vessels; as well as Generate a GUI that includes the first graphical component and the second graphical component.
3. The method of claim 2, wherein generating the GUI includes overlaying the first graphical component onto a portion of the second graphical component to indicate plaque load along the longitudinal axis of the blood vessel.
4. The method according to any one of claims 2 or 3, wherein the first graphic component comprises lines disposed along a portion of the longitudinal axis of the blood vessel.
5. The method according to claim 4, comprising: For each of the plurality of frames, identify whether the patch load is less than a threshold level; as well as The lines are overlaid on portions of the second graphics component associated with frames in the plurality of frames where the patch load is less than the threshold level.
6. The method of claim 5, wherein the second graphic component includes a distal bracket, a proximal bracket, a minimum region, a vascular contour view, and an indication of a mirror image of the vascular contour view.
7. The method of claim 6, wherein the blood vessel contour view includes a graphical representation of the blood vessel boundary and the lumen boundary of the blood vessel along the longitudinal axis.
8. The method of any one of claims 6 or 7, wherein the distal bracket comprises one of a plurality of bracket graphical representations selected based on the position of the distal bracket relative to the patch load and the threshold level.
9. The method of claim 8, further comprising: Identify the position of the distal bracket; Determine whether the far bracket is associated with a frame in the plurality of frames where the patch load is less than the threshold level; as well as The first of the plurality of bracket graphic representations is selected based on the determination that the far bracket is associated with a frame in the plurality of frames in which the patch load is less than the threshold level; or The second of the plurality of bracket graphic representations is selected based on the determination that the far bracket is not associated with frames in the plurality of frames where the patch load is less than the threshold level.
10. The method of any one of claims 6 to 9, wherein the proximal bracket comprises one of a plurality of graphical representations selected based on the position of the proximal bracket relative to the patch load and the threshold level.
11. The method of claim 10, further comprising: Identify the position of the proximal bracket; Determine whether the proximal bracket is associated with a frame in the plurality of frames where the patch load is less than the threshold level; as well as The first of the multiple bracket graphic representations is selected based on the determination that the proximal bracket is associated with a frame in the multiple frames in which the patch load is less than the threshold level; or The second of the plurality of bracket graphic representations is selected based on the determination that the proximal bracket is not associated with frames in the plurality of frames where the patch load is less than the threshold level.
12. The method according to any one of claims 1 to 11, comprising: Generate a third graphics component that includes a cross-sectional view of one of the plurality of frames; as well as Generate a GUI that includes the first graphical component, the second graphical component, and the third graphical component.
13. The method according to any one of claims 1 to 12, wherein the GUI comprises an angiographic image of the blood vessel.
14. An apparatus comprising a processor coupled to a memory including instructions executable by the processor, the processor being configured to be coupled to an intravascular ultrasound (IVUS) imaging system and configured to execute the instructions, which, when executed, cause the processor to perform the method according to any one of claims 1 to 13.
15. At least one machine-readable storage device comprising a plurality of instructions that, in response to execution by a processor of an intravascular ultrasound (IVUS) imaging system, cause the processor to perform the method according to any one of claims 1 to 13.
Citation Information
Patent Citations
Piezocomposite transducers
US20060100522A1
Electronically scanned optical coherence tomography with frequency modulated signals
US20060106320A1
Systems and methods for three dimensional imaging with an orientation adjustable array
US20060173350A1
Multiple transducer configurations for medical ultrasound imaging
US20060253028A1
Medical imaging device having a forward looking flow detector
US20070016054A1