Patent Grant
11419682
The present disclosure relates generally to medical methods and systems for controlling the deployment of needles through the construction of treatment maps. Embodiments of the present disclosure relate to systems and techniques for providing a user interface for dynamic interactions with fibroid data and treatment data. More specifically, embodiments of the present disclosure relate to user interfaces for dynamically providing a visual representation of information generated by aggregating treatment data from one or more medical articles and generating information.
Current medical treatments of organs and tissues within a patient's body often use a needle or other elongate body for delivery of energy, therapeutic agents or the like. Some methods use ultrasound imaging to observe and identify a treatment target and predict and track the position of the needle relative to the treatment target.
A treatment for uterine fibroids has recently been proposed which relies on the transvaginal or laparoscopic positioning of a treatment device in the patient's uterus. A radiofrequency or other energy or therapeutic delivery needle is deployed from the device into the fibroid, and energy and/or therapeutic substances are delivered in order to ablate or treat the fibroid. To facilitate locating the fibroids and positioning the needles within the fibroids, the device includes an ultrasonic imaging array with an adjustable field of view in a generally forward or lateral direction relative to an axial shaft which carries the needle. The needle is advanced from the shaft and across the field of view so that the needle can be visualized and directed into the tissue and the targeted fibroid.
The systems, methods, and devices described herein each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure, several non-limiting features will now be described briefly.
Embodiments of the present disclosure relate to an interactive treatment mapping and planning system and techniques for inputting and/or receiving fibroid data, generating information from the fibroid and/or treatment data, and displaying visual representations of the treatment data to enable a user to efficiently obtain information in an interactive user interface. The system may include techniques for providing real-time updates detailing ongoing treatment data. Disclosed herein are systems that advantageously provide highly efficient, intuitive, and rapid dynamic interaction with fibroid data and treatment data to enable the user to generate information about the treatment procedure. The systems may include interactive user interfaces that are dynamically updated to provide rapid comparison of multiple fibroids to be treated. Further, treatment information may be automatically sorted, for example, in some embodiments, by the system according to attributes associated with the treatment procedure and rules and/or preferences of the user.
Systems and methods are disclosed for providing a treatment mapping and planning system. The system provides fibroid location on a user interface. The user interface may comprise a map of the fibroids to be treated and/or treatment procedure information and activity at the individual fibroid level. The user may select a fibroid to be treated from the user interface, and the system may prompt the user to provide the system with information about the fibroid. Accordingly, a user may use the systems described herein to more quickly, thoroughly, and efficiently interact with multiple fibroid information and develop an efficient treatment plan based on the various fibroids to be treated. The features and advantages noted above, as well as others, are discussed in further detail below.
In various embodiments, the system creates a representation of the fibroids to be treated, including for example, descriptions of the fibroids, fibroid locations, fibroid type (e.g., intramural, submucosal, subserosal, pedunculated submucosal, pedunculated subserosal), estimated fibroid sizes, and other fibroid information.
In various embodiments, systems and methods are disclosed for aggregating fibroid and/or treatment data points, and generating information about the treatment procedure. For example, the fibroid and/or treatment data points may comprise at least one of a fibroid location, a fibroid size, a fibroid treatment order, or other fibroid information.
In various embodiments, systems and methods are disclosed for aggregating fibroid and/or treatment data points from various data sources. For example, the various data sources may comprise at least one of an input from a user, a user data source, or a third party data source.
In various embodiments, the system provides color coded icons, including order of treatment and other information. The other information may comprise estimated fibroid size, fibroid treatment status, and other fibroid information. Warnings may alert the user to situations in which a mapped fibroid has not been treated.
In various embodiments, system and methods are disclosed for categorizing the fibroid to be treated based on aggregated fibroid information. The categories may be based on fibroid size, order of treatment, fibroid location, fibroid prior treatment status, and other fibroid information. The system may automatically identify a mapped fibroid as one with particular interest to the user based on the categorization and provide the user with a visual representation indicating the fibroid's status. The user may then select and interact with the fibroid.
In various embodiments, data from the treatment devices may be acquired during the treatment procedure. The treatment data may be automatically and dynamically processed interactively in response to user and treatment device inputs, and the processed data is efficiently and compactly presented to a user by the system. Thus, in some embodiments, the user interfaces described herein are more efficient as compared to previous recording methods in which treatment data is not dynamically updated and compactly and efficiently presented to the user in response to use of the treatment devices.
The system may be configured and/or designed to generate user interface data useable for rendering the various interactive user interfaces described. The user interface data may be used by the system, and/or another computer system, device, and/or software program (for example, a browser program) to render the interactive user interfaces. The interactive user interfaces may be displayed on, for example, electronic displays (including, for example, touch-enabled displays).
In various embodiments, systems and methods are disclosed for generating a user interface including a fibroid map. The fibroid map may include a visual representation of information relating to a fibroid. For example, the visual representation may comprise a fibroid icon.
In various embodiments, systems and methods are disclosed for identifying a fibroid using an imaging modality and generating a user interface configured to provide knowledge relating to the identified fibroid.
In various embodiments, systems and methods are disclosed for acquiring data from an imaging modality. For example the data may comprise at least one of a position of the imaging modality, an orientation of the imagining modality, an insertion depth, an insertion angle, a fibroid location, a fibroid size, or other imagine modality information.
In various embodiments, systems and methods are disclosed for aggregating information about a treatment device via a sensor. For example the information may comprise at least one of a position and orientation of the treatment device.
In various embodiments, systems and methods are disclosed for communicating information from a sensor to a mapping system. For example the sensor may communicate information relating to at least one of a position and orientation of a treatment device.
In various embodiments, systems and methods are disclosed for aggregating information relating to an imaging modality through a tracking system. For example the information may comprise at least one of a position, orientation, and motion of the imaging modality.
Design of computer user interfaces that are useable and easily learned by humans is a non-trivial problem for software developers. The present disclosure describes various embodiments of interactive and dynamic user interfaces that are the result of significant development. This non-trivial development has resulted in the user interfaces described herein which may provide significant cognitive and ergonomic efficiencies and advantages over previous methods. The interactive and dynamic user interfaces include improved human-computer interactions that may provide reduced mental workloads, improved decision-making, reduced work stress, reduced procedure time, increased procedure accuracy, increased procedure documentation, and/or the like, for a user. For example, user interaction with the interactive user interface including interactions with fibroid and/or treatment data, among other interactions described herein may provide optimized interactions in comparison to previous methods.
Various embodiments of the present disclosure provide improvements to various technologies and technological fields. For example, existing treatment mapping and planning application technology is limited in various ways, and various embodiments of the disclosure provide significant improvements over such technology. For example, existing treatment mapping and planning application technology is limited since the treatment data that is provided may not be presented efficiently or at all and interactions between the treatment devices and the system is limited or not provided at all. Various embodiments of the present disclosure are inextricably tied to computer technology. In particular, various embodiments rely on aggregation of fibroid and/or treatment data, generating information about a treatment procedure, displaying such data in interactive graphical user interfaces displayed on electronic displays, etc. In some embodiments, treatment data may include information regarding the treatment device(s), the treatment parameters, the day and/or time of treatment, and other information. Such features are intimately tied to, and enabled by, computer technology, and would not exist except for computer technology. For example, the interactions with displayed data described below in reference to various embodiments cannot reasonably be performed by humans alone, without the computer technology upon which they are implemented. Further, the implementation of the various embodiments of the present disclosure via computer technology enables many of the advantages described herein, including more efficient interaction with, and presentation of, various types of electronic data.
Some embodiments of the disclosure are described below in reference to the appended claims, which may serve as an additional summary of the disclosure.
In various embodiments, systems and/or computer systems are disclosed that comprise a computer readable storage medium having program instructions embodied therewith, and one or more processors configured to execute the program instructions to cause the one or more processors to perform operations comprising one or more aspects of the above- and/or below-described embodiments (including one or more aspects of the appended claims).
In various embodiments, computer-implemented methods are disclosed in which, by one or more processors executing program instructions, one or more aspects of the above- and/or below-described embodiments (including one or more aspects of the appended claims) are implemented and/or performed.
In various embodiments, computer program products comprising a computer readable storage medium are disclosed, wherein the computer readable storage medium has program instructions embodied therewith, the program instructions executable by one or more processors to cause the one or more processors to perform operations comprising one or more aspects of the above-and/or below-described embodiments (including one or more aspects of the appended claims).
The following drawings and the associated descriptions are provided to illustrate embodiments of the present disclosure and do not limit the scope of the claims. Aspects and many of the attendant advantages of this disclosure will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
The present disclosure provides improved systems and methods for the treatment of tissues such as uterine fibroids. The systems and methods allow the treating physician to interactively and efficiently access information to assist in the development of a treatment map and plan. Access to such information may facilitate the planning and treatment of targeted tissues and improve the likelihood that proper treatment of a targeted anatomy occurs. The systems and methods provide a user interface for real-time dynamic interactions and feedback regarding treatment data. Such information may allow the physician, if desired, to alter or reassess the treatment plan before and/or during the treatment procedure. The systems and methods provide user interfaces that can dynamically generate a visual representation of information by aggregating treatment data from one or more of the treatment devices and generating useful information.
Feedback or other information is preferably provided visually on a treatment mapping and planning application. The treatment mapping and planning application may generally have graphical user interfaces that include real-time images overlaid by or alongside various objects and fibroid data. In some embodiments, the images may comprise ultrasonic or other imaging screens. An application may further be able to aggregate real-time information gathered from one or more treatment devices and display the information in an interactive manner that provides the user with information. For example, the real-time information may comprise feedback information in response to manipulating the probe and/or activating the needles. The system automatically aggregating the information reduces the need to enter data or commands onto a system controller or display, and can reduce the risk of data being lost altogether.
The application may generate a treatment report including information regarding the fibroid(s), the treatment device, the treatment parameters, the day and/or time of treatment, and other treatment information.
Although certain preferred embodiments and examples are disclosed below, inventive subject matter extends beyond the specifically disclosed embodiments to other alternative embodiments and/or uses and to modifications and equivalents thereof. Thus, the scope of the claims appended hereto is not limited by any of the particular embodiments described below. The structures, systems, and/or devices described herein may be embodied as integrated components or as separate components. For purposes of comparing various embodiments, certain aspects and advantages of these embodiments are described. Not necessarily all such aspects or advantages are achieved by any particular embodiment. Thus, for example, various embodiments may be carried out in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other aspects or advantages as may be taught or suggested herein.
Unless otherwise noted, the systems and methods described herein may be used with any embodiment described and/or contemplated within U.S. Pat. Nos. 8,088,072 and 8,992,427. It will be understood that any of the embodiments described and/or contemplated within U.S. Pat. Nos. 8,088,072 and 8,992,427 can be modified to be used with the systems and methods described herein.
I. Overview
An interactive treatment mapping and planning system enables a user to more quickly, thoroughly, and efficiently aggregate fibroid and/or treatment information from a user and/or data source, construct a fibroid map providing a visual representation of the aggregated fibroid information, generate information from the aggregated information about the fibroid to be treated and/or treatment procedure, develop a treatment plan based on the fibroid and/or treatment procedure information, provide real-time information gathered from treatment devices during the treatment procedure, and allow the user to interact with the treatment data. This and other functionality and advantages are provided via interactive graphical user interfaces, including interactive map interfaces, which are inextricably tied to computer technology.
As mentioned above, the system enables a user to efficiently input and/or compile fibroid data, construct a fibroid map, develop a treatment plan, gather information regarding the treatment procedure, and generate a treatment report. The interactive treatment mapping and planning system may include an interactive user interface in which fibroid and/or treatment data may be displayed on a user interface.
Fibroid data may refer to any type of data and/or information related to the fibroid(s) to be mapped. Fibroid data may also be referred to herein as fibroid data items. A fibroid data item generally includes at least a location associated with a fibroid. The location may be specified by, for example in some embodiments, a designated location selected by the user on a projected image located on or alongside a user interface. In some instances, fibroid data may include other information. For example, the fibroid data may comprise a description of the fibroid, fibroid location, fibroid type (e.g., intramural, submucosal, subserosal, pedunculated submucosal, pedunculated subserosal), estimated fibroid size, fibroid prior treatment status, number of fibroids, fibroid treatment order, and/or other fibroid information. Any combination of different types of fibroid data items may be used in the system simultaneously. Fibroid data items may be from various sources, and may be associated with various types of fibroids. Fibroid data may be obtained from a user, a single database, and/or multiple databases. The single and/or multiple databases from which fibroid data may be obtained may be operated, maintained, and/or owned by various entities. For example, the fibroid data may be obtained from a patient database and/or a hospital records management database.
Treatment data may refer to any type of data and/or information related to the treatment procedure. Treatment data may also be referred to herein as treatment data items. A treatment data item generally includes at least information regarding the treatment device(s), the treatment parameters, the day and/or time of treatment, and/or other treatment information. In some instances treatment data may include other information. For example, the treatment data may comprise fibroid treatment order, treatment time, ultrasound device information (such as ultrasound device serial number), ultrasound transducer angle, ultrasound transducer position, ablation device information (such as ablation device serial number), needle deployment depth, electrode deployment length, ablation data, ablation treatment volume, ablation treatment area, ablation time, ablation temperature, electrode and/or tissue impedance, radiofrequency power, radiofrequency temperature, time-temperature graphs, time-radiofrequency power graphs, and/or other treatment information. Any combination of different types of treatment data items may be used in the system simultaneously. Treatment data items may be from various sources. Treatment data may be obtained from a user and/or treatment device(s) throughout a treatment procedure. For example, the treatment data may be obtained from various treatment devices, such as an ultrasound device and/or an ablation device.
At block 102, various fibroid data may be optionally received by the system from a user input and/or one or more databases and/or data sources (including, for example, from databases maintained by the user or third party entities). As an example of the system receiving various fibroid data, the system may access fibroid data from one or more data sources. The data may comprise computer-readable output from a diagnostic test such as a transcervical uterine ultrasound, a laparoscopic ultrasound, or intrauterine ultrasound. The diagnostic test may be performed prior to or contemporaneously with the operation illustrated in
The data may then optionally be processed by the server at block 104. For example, the fibroid data may be organized by location, type, and/or by any other useful index so as to enable fast searching of the fibroid data.
At block 106, a user interface (and/or user interface data) is generated that displays (and/or is useable to generate and display) a map interface, as described in further detail below. For example, a map interface detailing a constructed fibroid map, as described in further detail below, may be displayed on the user interface. The map interface may be constructed entirely automatically based on the received data, entirely by the user, or a combination thereof. For example, the map interface may auto-populate based on the received data and then be manipulated by the user. In various embodiments, the system creates a visual representation of fibroid data and/or treatment data on the generated user interface, including, for example, descriptions of the fibroids, fibroid locations, fibroid type (e.g., intramural, submucosal, subserosal, pedunculated submucosal, pedunculated subserosal), estimated fibroid sizes, fibroid prior treatment statuses, number of fibroids, fibroid treatment order, and other fibroid information In various embodiments, the system may create a populated fibroid map following a preliminary exploratory procedure, as described below in reference to
At block 108, the user may interact with the user interface of the system in any of the ways described below. For example, the user may import additional data, interact with the map interface, provide various search query criteria, etc. At block 110, the fibroid data may be accessed by the system based on the provided user actions. In various embodiments, the treatment system may access one or more internal and/or external databases in response to user actions. The one or more accessed internal and/or external databases may or may not include the fibroid data described above.
At block 112, the system may develop a treatment plan based on the constructed fibroid map. The treatment plan may be developed manually by the user. In some embodiments, the system may develop the treatment plan automatically based on the fibroid data, as described in further detail below. The user may modify an automatically created treatment plan (e.g., changing the treatment order of the fibroids, selecting to skip treatment of some fibroids, etc.). Some changes may be prohibited or generate an error or warning message. The system may suggest changes to a manually created treatment plan.
At block 114, the user interface may be updated in response to the user's actions. The system may update the user interface following initiation of the treatment procedure. The updated interface may include data acquired from a treatment device. For example, the user interface may display information regarding the treatment device(s), the treatment parameters, the day and/or time of treatment, and other treatment information described herein in further detail. Treatment may be prevented by the system unless the treatment can be linked to a specific fibroid. Fibroid information may be displayed in lists and/or in the map interface, and/or animations may be provided, among other interface updates described below. As indicated by arrow 116, the operation may revert to block 108 such that the user may update and/or input a new action. After reversion, one or more of blocks 106, 108, 110, and/or 112 may be skipped.
At block 118, the system determines whether the treatment procedure has been terminated. The system may determine whether sufficient treatment has been performed prior to terminating the treatment procedure. In some embodiments, the system may not terminate the treatment procedure if the system determines that additional treatment is required. As indicated by arrow 120, if the treatment procedure has not terminated, the operation may continue to update the user interface as the user interacts with the system in any of the various ways described here. If the treatment procedure has terminated, the process proceeds to block 122.
In various embodiments, fibroid and/or treatment data may be received and processed by the system at any time and/or continuously. In an embodiment, treatment data may be updated even as the user is viewing the data on the user interface. For example, the user may use the system to analyze substantially real-time treatment data.
At block 122, the system may generate a report following the termination of the treatment procedure. The report may detail treatment information acquired during the treatment procedure. For example, the report may include information regarding the fibroid(s), the treatment device, the treatment parameters, the day and/or time of treatment, etc. The report is described in further detail below.
The system may generate alerts to the user. Alerts may comprise electronic notifications of changes and/or updates, for example, related to a user's actions. For example, as treatment data is updated in the system, the system may determine new or different fibroid classification, or may determine that user interfaces are or would be updated as a result of the updates. Accordingly, in order that the user may be made aware of these changes in a timely manner, an alert and/or notification may be automatically transmitted, for example, to a device operated by the user. The alert and/or notification can be transmitted at the time that the alert and/or notification is generated or at some determined time after generation of the alert and/or notification. When received by the device, the alert and/or notification can cause the device to display the alert and/or notification via the activation of an application on the device. In some embodiments, the device may comprise a browser, a mobile application, etc. For example, receipt of the alert and/or notification may automatically activate an application on the device, such as a messaging application, a standalone application, or a browser, for example, and display information included in the alert and/or notification. In some embodiments, the standalone application may comprise an interactive treatment mapping and planning system application. An alert may include notification that one or more fibroids was not treated, a treatment parameter may be inconsistent with the estimated fibroid size, there was a problem with the treatment device or a portion thereof (e.g., one or more thermocouples providing inconsistent data), etc.
Embodiments of the disclosure will now be described with reference to the accompanying figures, wherein like numerals refer to like elements throughout. The terminology used in the description presented herein is not intended to be interpreted in any limited or restrictive manner, simply because it is being utilized in conjunction with a detailed description of certain specific embodiments of the disclosure. Embodiments of the disclosure may include several novel features, no single one of which is solely responsible for its desirable attributes or which is essential to practicing the embodiments of the disclosure herein described.
II. Example User Interface and Constructing a Fibroid Map
The fibroid map interface 204 may be located at various portions of the user interface 200. In some embodiments, the fibroid map interface 204 may overlay a portion of the user interface 200 (e.g., as shown in
The user interface 200 and/or fibroid map interface 204 may further comprise several additional icons or buttons to increase the system's functionalities. In some embodiments, the user interface 200 may comprise a fibroid map interface view button 210. When a user engages the view button 210, the system may display the fibroid map interface 204. The system may subsequently remove the fibroid map interface 204 from view when the user again engages the view button 210. In some embodiments, the fibroid map interface 204 may be removed from view when a user engages a fibroid map interface close button 212. In some embodiments, the fibroid map interface may be removed from view or reduced in size upon user actions such as operation of a treatment device.
The user interface 200 and or fibroid map interface 204 may further comprise a treatment report button 214 that, when engaged by the user, causes the system to generate a treatment report 600, 700, discussed in further detail below.
In various embodiments, functionality of the interactive treatment mapping and planning system (as described in reference to the various figures below) may be implemented in one or more software computer modules stored in a memory and executed by one or more hardware processors, as is described below with reference to the example interactive treatment mapping and planning system 800 in
In various embodiments, the user interface 200 of
The user of the system may interact with the user interface 200 by scrolling or panning up, down, and/or side to side; zooming in or out; selecting data items; drawing shapes; performing a search queries; and/or the like. Various user actions may reveal more or less user interface 200 and/or fibroid map interface 204 detail, and/or more or fewer data items.
Prior to initiation of a treatment procedure, the system receives fibroid data. In some embodiments, a user may interact with the user interface 200 and/or fibroid map interface 204 to manually populate the fibroid map interface 204 with fibroid information. The user may review fibroid information based on previously gathered diagnostic results. After locating one or more fibroids through a preliminary ultrasound or other imaging modality exploratory procedure, the user may input the fibroid information into the user interface 200 and/or fibroid map interface 204. The system may automatically populate the fibroid map interface 200 with fibroid information. During the preliminary exploratory procedure, the system may generate fibroid information by aggregating information from a user and/or one or more separate data sources, discussed in further detail below with reference to
Various data items, including fibroid data items, may be represented on the fibroid map interface 204 with icons and/or symbols.
A user may manually populate the fibroid map interface 204 by interacting with a fibroid icon 216 within a fibroid icon selection tray 218. As discussed above, a user may interact with the system through various means. For example, the user may click and drag a fibroid icon 216 to a desired location. For another example, the user may click a fibroid icon 216 and subsequently click a desired location to place the fibroid icon 216 at the location. The user may click a desired location to place the fibroid icon 216 and subsequently click a fibroid icon 216 to place the fibroid icon 216 at the location. When a user places a fibroid icon 216 in one uterus view 206, 208, the system may automatically populate the other uterus view 206, 208 with a fibroid icon 216 at the same location on the uterus. The user may alter the location of the fibroid icon 216 by interacting with the fibroid icon 216. In some embodiments, when a user moves a fibroid icon 216 up or down in a single uterus view 206, 208, the system may automatically move a corresponding fibroid icon 216 in another uterus view 206, 208. As a user moves a fibroid icon 216 left or right in a single uterus view 206, 208, the system may not alter the location of a corresponding fibroid icon 216 in another uterus view 206, 208. This allows the fibroid icon 216 to maintain the representative horizontal location of the fibroid icon 216 on the fibroid map interface 204.
In various embodiments, the system displays each fibroid icon 216 on the fibroid map interface 204 through a particular visual representation. Each fibroid icon 216 may represent a fibroid type associated with a fibroid data item. The fibroid icon 216 may be chosen from a fibroid icon selection tray 218 based on the properties of the fibroid, as discussed in further detail below. The visual representation may be capable of quickly and efficiently providing the user with valuable fibroid information. The system may assign the particular representation to the fibroid data item based on fibroid information generated from the aggregated information. The visual representations of the fibroid icons 216 may be animated to show, among other things, recent activity, such as a change in fibroid treatment status, fibroid treatment order, or other fibroid information.
The fibroid icon 216 may comprise different sizes to represent variations in the estimated fibroid size. For example, as shown in
As shown in
In some embodiments, the user may select (e.g., by clicking on, hovering over, etc.), via the fibroid map interface 204, one or more of the fibroid icons 216 displayed to cause the system to display additional fibroid details. The additional information may be displayed in the fibroid map interface 204 or in a separate portion of the user interface 200. These capabilities can increase user efficiency by granting the user access to fibroid data through the user interface 200.
In some embodiments, the user may further interact with a fibroid icon 216 to alter various other fibroid properties, such as fibroid treatment order (e.g., if the number indicates order of treatment, changing the number), fibroid treatment status (e.g., marking as treated), fibroid location (e.g., as described above), and/or other fibroid information.
In some embodiments, the user interface 200 and/or fibroid map interface 204 may comprise a legend.
Embodiments of the interactive treatment mapping and planning system relate to systems that facilitate the treatment of a fibroid. It will be understood by one of skill in the art that the fibroids described herein this specification may encompass any fibroid, and are not limited to a particular location or type of fibroid. It is to be understood that the term fibroid is to be broadly construed and encompasses any abnormal tissue growth or any other superficial or other conditions or imperfections within the uterus of the patient or otherwise that benefit from ablation treatment. For example, the term fibroid may be used herein to describe ectopic glandular tissue or myometrial found in the muscular wall of the uterus (adenomyosis or uterine endometriosis).
III. Developing a Treatment Plan
At block 112 of
The treatment plan may target a fibroid(s) farthest from serosa prior to a fibroid(s) closest to serosa. The treatment plan may target pedunculated submucosal fibroid(s), submucosal fibroid(s), intramural fibroid(s), subserosal fibroid(s), and lastly pedunculated subserosal fibroid(s), in the order recited.
In some embodiments, the fibroid treatment order may be designed to avoid obscuring of the imaging field 202. Obscuring may arise through a process referred to as outgassing that occurs when steam created during ablation of a fibroid alters the quality of images produced by ultrasound or other imaging modalities. As such, a treatment plan may be developed to avoid outgassing. Several factors may affect the extent to which outgassing occurs during the treatment procedure, such as the mapped fibroid location, the fibroid size, other fibroid information, treatment parameters (e.g., temperature, time, temperature ramping, etc.), etc. In some embodiments, a treatment plan may be developed that treats fibroids located farther within a uterine cavity prior to treating fibroids located closer to the cervix. Alternatively, fibroids located closer to the cervix may be treated before fibroids located farther within the uterine cavity. A treatment plan may be developed to treat fibroids located closer to the surface of the uterine lining as opposed to fibroids located deeper within the uterine walls. Fibroid size may be a factor in determining fibroid treatment order. Embodiments of the interactive treatment planning and mapping system may utilize a combinatorial optimization algorithm to determine an improved or optimal fibroid treatment order subject to treatment constraints and/or treatment parameters (e.g., temperature, time, temperature ramping, reducing or avoiding outgassing, fibroid size, fibroid location, number of fibroids, etc.).
In some embodiments, the imaging field 202, the fibroid map interface 204, or a combination of both may be utilized to determine placement and/or location of the treatment device during the treatment procedure. The interactive treatment planning and mapping system may determine placement and/or location of the treatment device based on fibroid data and treatment data. Several factors may affect the placement of the treatment device, such as the mapped fibroid location, the fibroid size, other fibroid information, treatment parameters (e.g., temperature, time, temperature ramping, etc.), and other information. The user interface may further comprise treatment device placement and/or location indications on the imaging field 202, the fibroid map interface 204, or a combination of both. The indications may instruct the user to place the treatment device in a particular position and/or location during the treatment procedure. Embodiments of the interactive treatment planning and mapping system may utilize a combinatorial optimization algorithm to determine an improved or optimal treatment device location and/or placement subject to treatment constraints and/or treatment parameters (e.g., temperature, time, temperature ramping, reducing or avoiding outgassing, fibroid size, fibroid location, number of fibroids, etc.).
The treatment device, in some instances, may be configured to sense its position and/or orientation in space. The treatment device can transmit its position and/or orientation information to the interactive treatment planning and mapping system. The system may incorporate the position and/or orientation information into the imaging field 202, the fibroid map interface 204, or a combination of both to be displayed to a user. The treatment device may include one or more sensors to measure the position and/or orientation in three-dimensional space of the treatment device. The sensors may communicate the position and/or orientation information to the interactive treatment planning and mapping system, such that a position and/or orientation information of the treatment device can be displayed in the imaging field 202 and/or fibroid map interface 204. In some instances, the treatment device is in the form of an ablation tool comprising a needle, but the treatment device can include other ablation and/or imaging devices, or may only include an imaging device (e.g., for diagnostic uses).
In some embodiments, the treatment device comprises one or more sensors configured to measure an insertion depth of the treatment device during a treatment procedure. The insertion depth can be communicated to the interactive treatment planning and mapping system such that depth of the treatment device can be displayed in the imaging field 202, the fibroid map interface 204, or a combination of both. In some instances, the treatment device is configured to measure an insertion angle of the treatment device during a treatment procedure. The insertion angle information may be transmitted to the interactive treatment planning and mapping system to be displayed in the imaging field 202, the fibroid map interface 204, or a combination of both.
In some embodiments, the treatment device may include one or more sensors configured to determine a device position and/or orientation relative to other objects, such as, for example, a fibroid location, a user, one or more locations on a patient, combinations thereof, and the like. Information corresponding to the sensed position and/or orientation is transmitted to the interactive treatment planning and mapping system. Position and/or orientation information between the treatment device and a fibroid to be ablated may be captured by an external tracking system, such as, by way of non-limiting example, an optical tracking system. The tracking system can be configured to obtain at least one of position, orientation, and motion information of the treatment device used. The information sensed by the tracking system can be transmitted to the interactive treatment planning and mapping system. The system may be configured to receive the information and to display it in the imaging field 202, the fibroid map interface 204, or a combination of both. The position and/or orientation information may be determined by any suitable approaches to measure and determine the position and orientation of an object in three-dimensional space. For example, an optical tracking system and/or inertial sensors (for example, gyroscope sensors and/or accelerometers) can be configured to obtain one or more of position, orientation, and motion information of the treatment device. In some instances, the treatment device may include visual markers that provide placement and/or location indications to a user. For example, the treatment device may be annotated with positional indicators (e.g., depth indications) along at least a portion of the treatment device to orient a user interacting with the treatment device. Indicators may be active (e.g., light-emitting diodes) and/or passive (e.g., optically recognizable patterns).
In some implementations, the treatment device may comprise an alignment system that periodically emits a signal which is may be captured by one or more corresponding receivers. In some embodiments, the one or more receivers may sense the signal from the treatment device directly. The alignment system may comprise a source of electromagnetic radiation and emit a signal comprising electromagnetic radiation. For example, the source may be configured to transmit a signal that is capable of traveling through one or more portions of a patient anatomy to be received by a corresponding receiver located outside of a patient cavity.
The position and/or orientation information transmitted to the interactive treatment planning and mapping system may be used in conjunction with fibroid data so that the locations of the treatment device in the imaging field 202 and/or the fibroid map interface 204 correspond to an actual location of the treatment device relative to one or more fibroids. The ability to obtain position and/or orientation data of the treatment device as the user is performing a treatment or diagnostic procedure can help the user perform a fibroid treatment at an optimal location. For example, during a treatment procedure, the interactive treatment planning and mapping system may instruct a user via the imaging field 202 and/or fibroid map interface 204 to guide the treatment device to an appropriate depth, position, and/or orientation for a therapeutic procedure. In some instances, the movement of the treatment device can be projected on the imaging field 202 and/or fibroid map interface 204 in real-time during the treatment procedure. For example, as the treatment device is moved through a patient cavity, the location of a distal tip of the treatment device can be identified on the imaging field 202 and/or fibroid map interface 204. When the treatment device is positioned in a target location within the patient cavity, the treatment device may be positioned in the target location in the imaging field 202 and/or fibroid map interface 204. Updating A User Interface with Treatment Data
At block 114 shown in
The user interface 200 may further comprise a treatment data interface 222 detailing the elapsed treatment time, treatment time remaining, ablation treatment volume, ablation treatment area, ablation time, ablation temperature, electrode and/or tissue impedance, radiofrequency power, radiofrequency temperature, and/or any other desired treatment data. In some embodiments, the treatment data interface 222 may comprise a power graph 224 illustrating the relationship between time and radiofrequency power. The treatment data interface 222 may comprises a temperature graph 226 illustrating the relationship between time and mapped fibroid temperature.
In various embodiments, fibroid and/or treatment data may be received and processed by the system at any time and/or continuously. As indicated by block 118 in
In various embodiments, the system may provide color coded representations. For example, the system may characterize a fibroid icon 216 into various classifications such as treatment status classifications: untreated, treated, previously treated but recurring fibroid, or untreated with a previous failed treatment attempt. The individual classifications may result in variations in the visual representation of the fibroid icon 216. For example, as shown in
IV. Example Treatment Report
As discussed previously, at block 122 in
The treatment report 600, 700 may detail treatment information acquired during the treatment procedure. For example, the treatment report 600, 700 may include information relating to fibroid location, estimated fibroid size, fibroid treated status, number of fibroids, fibroid treatment order, ultrasound device information (such as ultrasound device serial number), ultrasound transducer angle, ablation device information (such as ablation device serial number), needle deployment depth, electrode deployment length, planned fibroid size, ablation data, ablation data, ablation treatment volume, ablation treatment area, ablation time, ablation temperature, electrode and/or tissue impedance, radiofrequency power, radiofrequency temperature, time-temperature graphs, time-radiofrequency power graphs, ablation safety zone distance, photographs and/or screen shoots of the imaging field, treatment procedure information, time of treatment, treatment length, treatment date, patient data, attending physician and/or nurse, user and/or physician notes, and other fibroid and/or treatment information.
In some embodiments, the treatment report 600, 700 and/or fibroid report(s) 602, 702 may be exported to one or more databases. The system may export the report 600, 700 through wired and/or wireless connections.
V. Exploratory Procedure
The interactive treatment mapping and planning system may incorporate a preliminary exploratory procedure. The system may enable a user to more efficiently aggregate fibroid information during an exploratory procedure, construct a fibroid map providing a visual representation of the aggregated fibroid information, and generate an exploratory report.
At block 902, various fibroid data may be identified during a preliminary exploratory procedure performed via a diagnostic test such as a transcervical uterine ultrasound, laparoscopic ultrasound, or intrauterine ultrasound. The system may receive the fibroid data from the imaging device(s) at block 904.
In some instances, at block 902, diagnostic device placement and/or location data may be identified during a preliminary exploratory procedure. The interactive treatment mapping and planning system may utilize any structure, device, method, or features described herein in relation to the treatment device. For example, the diagnostic device may include one or more sensors to measure the position and orientation in three-dimensional space of the diagnostic device. The diagnostic device can transmit its position and/or orientation information to the interactive treatment planning and mapping system. The system may incorporate the position and orientation information into a user interface to be displayed to a user. The method may end after such automated mapping.
At block 906, a user interface is generated that displays (and/or is useable to generate and display) a fibroid map interface similar to the user interface and fibroid map interface previously described above with reference to
At block 908, the system determines whether the exploratory procedure has terminated. As indicated by arrow 910, if the exploratory procedure has not terminated, the operation may continue to identify additional fibroid(s). For example, with reference to
At block 912, the system may automatically generate an exploratory report following the termination of the exploratory procedure. The report may detail exploratory information acquired during the exploratory procedure. For example, the report may include information regarding the fibroid(s), the imaging device (e.g. an ultrasound transducer), the imaging parameters, the day and/or time of exploratory procedure, and other information. The exploratory report may include an automated and/or manual treatment protocol recommendation (e.g., labeling fibroid icons based on a recommended treatment order rather than the order in which the fibroids were diagnosed).
In various embodiments, the system may export a fibroid data file comprising the constructed fibroid map interface and/or exploratory report. The exploratory report may be readable to automatically populate a fibroid interface map 204.
VI. Implementation Mechanisms
As previously discussed, the interactive treatment mapping and planning system 800 may comprise an imaging device 814 (e.g. an ultrasound transducer or other imaging modality), a display device 816, and an ablation device 818 configured to generate radiofrequency energy for the treatment of an abnormal tissue growth. The treatment system 800 may comprise any embodiment described and/or contemplated within U.S. Pat. No. 8,088,072 (herein referred to as the '072 Patent) and U.S. Pat. No. 8,992,427 (herein referred to as the '427 Patent), incorporated herein by reference in their entireties. It will be understood that any of the embodiments described and/or contemplated within the '072 Patent and the '427 Patent can be modified to be used with the various interactive treatment mapping and planning systems described herein. For example, in some embodiments, FIGS. 1 and 2 of the '427 Patent depict the treatment system 800 illustrated in
The interactive treatment mapping and planning system 800 can include a computing engine 806, a data source 804, an imaging device 814, a display device 816, and an ablation device 818. The system 800 can receive user (e.g., physician) input from one or more user computing devices 802. In an embodiment, the computing device(s) 802 may be any computing devices capable of displaying software applications to a user and receiving input from the user. For example, the computing device(s) 802 may include smartphones, tablets, laptops, and/or other types of computing devices. The computing device(s) 852 may be capable of communicating over a network, for example, to request data from, and/or to provide data to, the components of the system 800. In some embodiments, the data source 804 may include non-transitory computer-readable medium storage for storing fibroid data 811a and/or treatment data 811b.
The computing engine 806 may perform a variety of tasks to implement the operations of the interactive treatment mapping and planning system. The computing engine 806 can include a hardware processor 808, a memory 810 (which can store code modules executed by the processor 808), and a communication interface 812 that communicates information to and/or from other components of the system 800.
The computing engine 806 may include one or more software modules stored in the memory 810 and that, when executed by the processor 808, may, for example, receive fibroid data 811a and/or treatment data 811b from the data source 804, process the received data, generate user interfaces 200 and/or user interface data for display by the display device 816, process inputs from the user received from the computing device 802 or via the user interface (UI) 200 of the display device 816, and/or update the user interface 200. The processor 808 may be programmed to perform embodiments of the methods described with reference to
The computing engine 806 may be in communication with the data source 804. The database 804 may include electronic storage local to the computing engine 806. The data source 804 may be embodied in hard disk drives, solid state memories, and/or any other type of non-transitory, computer-readable storage medium remotely or locally accessible to the computing engine 806. The fibroid data 811a and/or the treatment data 811b may be distributed or partitioned across multiple storage devices, and/or may be combined into a single database.
In various embodiments, the computing engine 806 or data source 804 may be accessible by the user through a web-based viewer, such as a web browser, executed by the user computing device 802 or displayed as the display device 816. The display device 816 may be a computer monitor, a touchscreen, an electronic (e.g., LCD or LED) display, etc. The user interface may be generated by the computing engine 806 and transmitted to the web browser of the user computing device 802 or the display device 816. Alternatively, data necessary for generating the user interface 200 may be provided by the computing engine 806 to the display device 816, where the user interface may be generated for display. The user may interact with the user interface 200 through the web-browser or the display device 816. In an embodiment, the user interface 200 of the interactive treatment mapping and planning system 800 may be accessible through a dedicated software application (rather than a web browser).
The interactive treatment mapping and planning system 800 and other methods and techniques described herein can be implemented by one or more special-purpose computing devices such as the processor 808 and the memory 810. The special-purpose computing devices may be hard-wired to perform the techniques, or may include digital electronic devices such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are persistently programmed to perform the techniques, or may include one or more general purpose hardware processors specially programmed to perform the techniques pursuant to program instructions in firmware, in executable code modules stored in the memory 810, other storage, or a combination. Such special-purpose computing devices may combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the techniques. The special-purpose computing devices may be desktop computer systems, server computer systems, portable computer systems, handheld devices, networking devices or any other device or combination of devices that incorporate hard-wired and/or specialized program logic to implement the techniques described herein. Execution of the sequences of instructions contained in the memory 806 causes the processor(s) 804 to perform the process steps described herein.
VII. Examples
1. A system comprising:
2. The system of Example 1, wherein the processor is programmed to aggregate a plurality of fibroid data records from at least one of:
3. The system of any one of Examples 1-2, wherein the fibroid data record item comprises a fibroid location.
4. The system of any one of Examples 1-3, wherein the fibroid data record item comprises a fibroid size.
5. The system of Example 4, wherein the fibroid size comprises one of:
6. The system of any one of Examples 1-5, wherein the fibroid data record item comprises a fibroid treatment status.
7. The system of any one of Examples 1-6, wherein the fibroid data record item comprises a fibroid treatment order.
8. The system of any one of Examples 1-7, wherein the processor is further programmed to receive user input.
9. The system of Example 8, wherein the user input comprises at least one of:
10. The system of Example 9, wherein the processor is programmed, in response to the user input, to:
11. The system of any one of Examples 8-10, wherein the user input includes export criteria comprising at least one of:
12. The system of Example 11, wherein the processor is programmed, in response to the user input, to:
13. The system of any one of Examples 1-12, wherein the interactive user interface further comprises a legend.
14. The system of any one of Examples 1-13, wherein the visual representation comprises a fibroid icon.
15. The system of Example 14, wherein the visual representation is configured to indicate a warning to the user.
16. The system of any one of Examples 1-15, wherein the processor is programmed to:
17. The system of any one of Examples 1-16, wherein the processor is programmed to:
18. The system of Example 17, wherein the program further programmed to generate a treatment report.
19. A system comprising:
20. The system of Example 19, further comprising the imaging modality, wherein the imaging modality comprises an ultrasound transducer.
21. The system of any one of Examples 19-20, wherein the program instructions further cause the processor to generate an exploratory report.
22. A system comprising:
23. The system of Example 22, wherein the program further programmed to generate a treatment report.
24. The system of any one of Examples 22-23, further comprising an imaging modality, wherein the imaging modality comprises an ultrasound transducer.
25. The system of any one of Examples 22-24, further comprising an ablation device, wherein the ablation device comprises an radiofrequency generator.
26. A method of providing a system for treating a fibroid, the method comprising:
27. The method of Embodiment 26 further comprising instructing a user to determine a fibroid treatment order.
28. The method of any of Examples 26-27, wherein the interactive user interface includes:
29. A system comprising:
30. The system of Example 29, wherein the information comprises at least one of a position of the imaging modality, an orientation of the imagining modality, an insertion depth, an insertion angle, a fibroid location, and a fibroid size.
31. The system of any one of Examples 29-30, wherein the imaging modality comprises a sensor configured to determine at least one of a position and an orientation of the imagining modality.
32. The system of Example 31, wherein the information comprises information representative of at least one of position and orientation of the imaging modality.
33. The system of any one of Examples 31-32, wherein the sensor comprises at least one of an optical tracking system, inertial sensors, and visual markers.
34. The system of any one of Examples 31-33, wherein the imaging modality further comprises an alignment marker configured to emit a signal comprising information representative of at least one of position and orientation of the imaging modality.
35. The system of Example 34, further comprising a receiver configured to receive the signal emitted by the alignment marker.
36. The system of any one of Examples 34-35, wherein the alignment marker comprises a source of electromagnetic radiation.
37. The system of any one of Examples 29-36, further comprising an ablation tool.
38. The system of Example 37, wherein the ablation tool is coupled to the imaging modality.
39. The system of any one of Examples 29-38, further comprising a tracking system configured to at least partially determine at least one of position, orientation, and motion of the imaging modality.
40. The system of any one of Examples 29-39, wherein the processor is configured to generate the interactive user interface using the information received from the imaging modality.
41. The system of any one of Examples 29-40, wherein the visual representation is configured to overlay the interactive fibroid map.
VIII. Additional Examples
Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules stored in memory and executed by one or more computer systems or computer processors comprising computer hardware. The processes and algorithms may be implemented partially or wholly in application-specific circuitry.
The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
The term “comprising” as used herein should be given an inclusive rather than exclusive interpretation. For example, a general purpose computer comprising one or more processors should not be interpreted as excluding other computer components, and may possibly include such components as non-transitory memory, input/output devices, and/or network interfaces, among others. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. In addition, the articles “a,” “an,” and “the” as used in this application and the appended claims are to be construed to mean “one or more” or “at least one” unless specified otherwise.
As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: A, B, or C” is intended to cover: A, B, C, A and B, A and C, B and C, and A, B, and C. Conjunctive language such as the phrase “at least one of X, Y and Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to convey that an item, term, etc. may be at least one of X, Y or Z. Thus, such conjunctive language is not generally intended to imply that certain embodiments require at least one of X, at least one of Y and at least one of Z to each be present.
The processes, methods, and systems may be implemented in a network (or distributed) computing environment. Network environments include enterprise-wide computer networks, intranets, local area networks (LAN), wide area networks (WAN), personal area networks (PAN), cloud computing networks, crowd-sourced computing networks, the Internet, and the World Wide Web. The network may be a wired or a wireless network or any other type of communication network.
Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
Code modules or any type of data may be stored on any type of non-transitory computer-readable medium, such as physical computer storage including hard drives, solid state memory, random access memory (RAM), read only memory (ROM), optical disc, volatile or non-volatile storage, combinations of the same and/or the like. The methods and modules (or data) may also be transmitted as generated data signals (e.g., as part of a carrier wave or other analog or digital propagated signal) on a variety of computer-readable transmission mediums, including wireless-based and wired/cable-based mediums, and may take a variety of forms (e.g., as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). The results of the disclosed processes or process steps may be stored, persistently or otherwise, in any type of non-transitory, tangible computer storage or may be communicated via a computer-readable transmission medium.
The ranges disclosed herein also encompass any and all overlap, sub-ranges, and combinations thereof. Language such as “up to,” “at least,” “greater than,” “less than,” “between,” and the like includes the number recited. Numbers preceded by a term such as “about” or “approximately” include the recited numbers and should be interpreted based on the circumstances (e.g., as accurate as reasonably possible under the circumstances, for example ±5%, ±10%, ±15%, etc.). For example, “about 1” includes “1.” Phrases preceded by a term such as “substantially,” “generally,” and the like include the recited phrase and should be interpreted based on the circumstances (e.g., as much as reasonably possible under the circumstances). For example, “substantially spherical” includes “spherical.” Unless stated otherwise, all measurements are at standard conditions including temperature and pressure.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the invention can be practiced in many ways. As is stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the invention with which that terminology is associated. The scope of the invention should be construed in accordance with the appended claims and any equivalents thereof.
The present application is a continuation of U.S. patent application Ser. No. 16/408,790, filed on May 10, 2019, which is a continuation of International Patent Application No. PCT/US2017/060674, filed on Nov. 8, 2017, which claims priority benefit of U.S. Provisional Patent App. No. 62/421,119, filed Nov. 11, 2016. Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are hereby incorporated by reference under 37 C.F.R. § 1.57. Additionally, each of U.S. Pat. Nos. 8,088,072 and 8,992,427 is incorporated herein by reference in their entirety so as to form a part of the present application.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4289132 | Rieman | Sep 1981 | A |
| 4567896 | Barnea et al. | Feb 1986 | A |
| 4671292 | Matzuk | Jun 1987 | A |
| 4742829 | Law et al. | May 1988 | A |
| 4802487 | Marti et al. | Feb 1989 | A |
| 4869258 | Hetz | Sep 1989 | A |
| 4936281 | Stasz | Jun 1990 | A |
| 5000185 | Yock | Mar 1991 | A |
| 5090414 | Takano | Feb 1992 | A |
| 5190050 | Nitzsche | Mar 1993 | A |
| 5269301 | Cohen | Dec 1993 | A |
| 5315741 | Dubberke | May 1994 | A |
| 5335663 | Oakley et al. | Aug 1994 | A |
| 5372138 | Crowley et al. | Dec 1994 | A |
| 5372587 | Hammerslag et al. | Dec 1994 | A |
| 5456689 | Kresch et al. | Oct 1995 | A |
| 5469853 | Law et al. | Nov 1995 | A |
| 5471988 | Fujio et al. | Dec 1995 | A |
| 5474075 | Goldberg et al. | Dec 1995 | A |
| 5492126 | Hennige et al. | Feb 1996 | A |
| 5527331 | Kresch et al. | Jun 1996 | A |
| 5531676 | Edwards et al. | Jul 1996 | A |
| 5607389 | Edwards et al. | Mar 1997 | A |
| 5649911 | Trerotola | Jul 1997 | A |
| 5662664 | Gordon et al. | Sep 1997 | A |
| 5666954 | Chapelon et al. | Sep 1997 | A |
| 5697897 | Buchholtz et al. | Dec 1997 | A |
| 5730752 | Alden et al. | Mar 1998 | A |
| 5741287 | Alden et al. | Apr 1998 | A |
| 5752518 | Mcgee et al. | May 1998 | A |
| 5769795 | Terwilliger | Jun 1998 | A |
| 5769880 | Truckai et al. | Jun 1998 | A |
| 5800378 | Edwards et al. | Sep 1998 | A |
| 5842994 | Tenhoff et al. | Dec 1998 | A |
| 5853368 | Solomon et al. | Dec 1998 | A |
| 5860974 | Abele et al. | Jan 1999 | A |
| 5863294 | Alden | Jan 1999 | A |
| 5865729 | Meehan et al. | Feb 1999 | A |
| 5873828 | Fujio et al. | Feb 1999 | A |
| 5876340 | Tu et al. | Mar 1999 | A |
| 5876399 | Chia et al. | Mar 1999 | A |
| 5891137 | Chia et al. | Apr 1999 | A |
| 5906615 | Thompson | May 1999 | A |
| 5908385 | Chechelski et al. | Jun 1999 | A |
| 5916198 | Dillow | Jun 1999 | A |
| 5931787 | Dietz et al. | Aug 1999 | A |
| 5957941 | Ream | Sep 1999 | A |
| 5964740 | Ouchi | Oct 1999 | A |
| 5979452 | Fogarty et al. | Nov 1999 | A |
| 5979453 | Savage et al. | Nov 1999 | A |
| 5984942 | Alden et al. | Nov 1999 | A |
| 6002968 | Edwards | Dec 1999 | A |
| 6007499 | Martin et al. | Dec 1999 | A |
| 6032673 | Savage et al. | Mar 2000 | A |
| 6039748 | Savage et al. | Mar 2000 | A |
| 6050992 | Nichols | Apr 2000 | A |
| 6055449 | Navab | Apr 2000 | A |
| 6059766 | Greff | May 2000 | A |
| 6077257 | Edwards et al. | Jun 2000 | A |
| 6080150 | Gough | Jun 2000 | A |
| 6083169 | Hansen | Jul 2000 | A |
| 6126665 | Yoon | Oct 2000 | A |
| 6141577 | Rolland et al. | Oct 2000 | A |
| 6146378 | Mikus et al. | Nov 2000 | A |
| 6146380 | Racz et al. | Nov 2000 | A |
| 6149598 | Tanaka | Nov 2000 | A |
| 6158250 | Tibbals et al. | Dec 2000 | A |
| 6171249 | Chin et al. | Jan 2001 | B1 |
| 6190383 | Schmaltz et al. | Feb 2001 | B1 |
| 6193714 | Mcgaffigan et al. | Feb 2001 | B1 |
| 6211153 | Garnick et al. | Apr 2001 | B1 |
| 6216029 | Paltieli | Apr 2001 | B1 |
| 6238336 | Ouchi | May 2001 | B1 |
| 6241725 | Cosman | Jun 2001 | B1 |
| 6254601 | Burbank et al. | Jul 2001 | B1 |
| 6261234 | Lin | Jul 2001 | B1 |
| 6280441 | Ryan | Aug 2001 | B1 |
| 6296639 | Truckai et al. | Oct 2001 | B1 |
| 6306097 | Park et al. | Oct 2001 | B1 |
| 6306129 | Little et al. | Oct 2001 | B1 |
| 6311084 | Cormack et al. | Oct 2001 | B1 |
| 6314310 | Ben-Haim et al. | Nov 2001 | B1 |
| 6315741 | Martin et al. | Nov 2001 | B1 |
| 6325758 | Carol et al. | Dec 2001 | B1 |
| 6336899 | Yamazaki | Jan 2002 | B1 |
| 6355275 | Klein | Mar 2002 | B1 |
| 6361499 | Bates et al. | Mar 2002 | B1 |
| 6368280 | Cermak et al. | Apr 2002 | B1 |
| 6379348 | Onik | Apr 2002 | B1 |
| 6405732 | Edwards et al. | Jun 2002 | B1 |
| 6419048 | Robinson et al. | Jul 2002 | B1 |
| 6419648 | Vitek et al. | Jul 2002 | B1 |
| 6419653 | Edwards et al. | Jul 2002 | B2 |
| 6419673 | Edwards et al. | Jul 2002 | B1 |
| 6425867 | Vaezy et al. | Jul 2002 | B1 |
| 6432067 | Martin et al. | Aug 2002 | B1 |
| 6443902 | Sasady | Sep 2002 | B1 |
| 6447477 | Burney et al. | Sep 2002 | B2 |
| 6461296 | Desai | Oct 2002 | B1 |
| 6463331 | Edwards | Oct 2002 | B1 |
| 6468228 | Topel et al. | Oct 2002 | B1 |
| 6475152 | Kelly, Jr. et al. | Nov 2002 | B1 |
| 6482203 | Paddock et al. | Nov 2002 | B2 |
| 6485413 | Boppart et al. | Nov 2002 | B1 |
| 6506154 | Ezion et al. | Jan 2003 | B1 |
| 6506156 | Jones et al. | Jan 2003 | B1 |
| 6506171 | Vitek et al. | Jan 2003 | B1 |
| 6507747 | Gowda et al. | Jan 2003 | B1 |
| 6508815 | Strul et al. | Jan 2003 | B1 |
| 6522142 | Freundlich | Feb 2003 | B1 |
| 6526320 | Mitchell | Feb 2003 | B2 |
| 6540677 | Angelsen et al. | Apr 2003 | B1 |
| 6543272 | Vitek | Apr 2003 | B1 |
| 6544176 | Mikus et al. | Apr 2003 | B2 |
| 6550482 | Burbank et al. | Apr 2003 | B1 |
| 6553013 | Jones et al. | Apr 2003 | B1 |
| 6554780 | Sampson et al. | Apr 2003 | B1 |
| 6554801 | Steward et al. | Apr 2003 | B1 |
| 6559644 | Froundlich et al. | May 2003 | B2 |
| 6569159 | Edwards et al. | May 2003 | B1 |
| 6572613 | Ellman et al. | Jun 2003 | B1 |
| 6575969 | Rittman, III | Jun 2003 | B1 |
| 6579298 | Bruneau et al. | Jun 2003 | B1 |
| 6585694 | Smith et al. | Jul 2003 | B1 |
| 6589237 | Woloszko et al. | Jul 2003 | B2 |
| 6589238 | Edwards et al. | Jul 2003 | B2 |
| 6592559 | Pakter et al. | Jul 2003 | B1 |
| 6602251 | Burbank et al. | Aug 2003 | B2 |
| 6610054 | Edwards et al. | Aug 2003 | B1 |
| 6612988 | Maor et al. | Sep 2003 | B2 |
| 6613004 | Vitek et al. | Sep 2003 | B1 |
| 6613005 | Friedman et al. | Sep 2003 | B1 |
| 6623481 | Garbagnati et al. | Sep 2003 | B1 |
| 6626832 | Paltieli et al. | Sep 2003 | B1 |
| 6626854 | Friedman et al. | Sep 2003 | B2 |
| 6626855 | Weng et al. | Sep 2003 | B1 |
| 6632193 | Davison et al. | Oct 2003 | B1 |
| 6635055 | Cronin | Oct 2003 | B1 |
| 6635065 | Burbank et al. | Oct 2003 | B2 |
| 6638275 | Mcgaffigan et al. | Oct 2003 | B1 |
| 6638286 | Burbank et al. | Oct 2003 | B1 |
| 6645162 | Friedman et al. | Nov 2003 | B2 |
| 6645202 | Pless et al. | Nov 2003 | B1 |
| 6652516 | Gough | Nov 2003 | B1 |
| 6654202 | Rea et al. | Nov 2003 | B2 |
| 6660002 | Edwards et al. | Dec 2003 | B1 |
| 6660024 | Flaherty et al. | Dec 2003 | B1 |
| 6662680 | Rocket | Dec 2003 | B2 |
| 6663624 | Edwards et al. | Dec 2003 | B2 |
| 6663626 | Truckai et al. | Dec 2003 | B2 |
| 6666833 | Friedman et al. | Dec 2003 | B1 |
| 6669643 | Dubinsky | Dec 2003 | B1 |
| 6679855 | Horn et al. | Jan 2004 | B2 |
| 6685639 | Wang et al. | Feb 2004 | B1 |
| 6689128 | Sliwa et al. | Feb 2004 | B2 |
| 6692490 | Edwards | Feb 2004 | B1 |
| 6695786 | Wang et al. | Feb 2004 | B2 |
| 6701931 | Sliwa et al. | Mar 2004 | B2 |
| 6705994 | Vortman et al. | Mar 2004 | B2 |
| 6712815 | Sampson et al. | Mar 2004 | B2 |
| 6716184 | Vaezy et al. | Apr 2004 | B2 |
| 6719755 | Sliwa et al. | Apr 2004 | B2 |
| 6728571 | Barbato | Apr 2004 | B1 |
| 6730081 | Desai | May 2004 | B1 |
| 6733458 | Steins et al. | May 2004 | B1 |
| 6735461 | Vitek et al. | May 2004 | B2 |
| 6743184 | Sampson et al. | Jun 2004 | B2 |
| 6746447 | Davison et al. | Jun 2004 | B2 |
| 6764488 | Burbank et al. | Jul 2004 | B1 |
| 6773431 | Eggers et al. | Aug 2004 | B2 |
| 6786870 | Miyaki et al. | Sep 2004 | B2 |
| 6790180 | Vitek | Sep 2004 | B2 |
| 6798716 | Charych | Sep 2004 | B1 |
| 6805128 | Pless et al. | Oct 2004 | B1 |
| 6805129 | Pless et al. | Oct 2004 | B1 |
| 6813520 | Truckai et al. | Nov 2004 | B2 |
| 6832996 | Woloszko et al. | Dec 2004 | B2 |
| 6837887 | Woloszko et al. | Jan 2005 | B2 |
| 6837888 | Ciarrocca et al. | Jan 2005 | B2 |
| 6840935 | Lee | Jan 2005 | B2 |
| 6899712 | Moutafis et al. | May 2005 | B2 |
| 6908433 | Pruter | Jun 2005 | B1 |
| 6921398 | Carmel et al. | Jul 2005 | B2 |
| 6923807 | Ryan et al. | Aug 2005 | B2 |
| 6936048 | Hurst | Aug 2005 | B2 |
| 6938048 | Jilk et al. | Aug 2005 | B1 |
| 6944490 | Chow | Sep 2005 | B1 |
| 6953458 | Loeb | Oct 2005 | B2 |
| 6969354 | Marian | Nov 2005 | B1 |
| 6994706 | Chornenky et al. | Feb 2006 | B2 |
| 7101387 | Garabedian et al. | Sep 2006 | B2 |
| 7160296 | Pearson et al. | Jan 2007 | B2 |
| 7171255 | Holupka et al. | Jan 2007 | B2 |
| 7229401 | Kindlein | Jun 2007 | B2 |
| 7241293 | Davison | Jul 2007 | B2 |
| 7247141 | Makin et al. | Jul 2007 | B2 |
| 7276063 | Davison et al. | Oct 2007 | B2 |
| 7306595 | Ostrovsky et al. | Dec 2007 | B2 |
| 7317988 | Johnson | Jan 2008 | B2 |
| 7331957 | Woloszko et al. | Feb 2008 | B2 |
| 7333844 | Jones et al. | Feb 2008 | B2 |
| 7387628 | Behl et al. | Jun 2008 | B1 |
| 7517346 | Sloan et al. | Apr 2009 | B2 |
| 7549424 | Desai | Jun 2009 | B2 |
| 7771357 | Burbank et al. | Aug 2010 | B2 |
| 7815571 | Deckman et al. | Oct 2010 | B2 |
| 7874986 | Deckman et al. | Jan 2011 | B2 |
| 7918795 | Grossman | Apr 2011 | B2 |
| 7963941 | Wilk | Jun 2011 | B2 |
| 8080009 | Lee et al. | Dec 2011 | B2 |
| 8088072 | Munrow et al. | Jan 2012 | B2 |
| 8157741 | Hirota | Apr 2012 | B2 |
| 8157745 | School | Apr 2012 | B2 |
| 8206300 | Deckman et al. | Jun 2012 | B2 |
| 8216231 | Behl et al. | Jul 2012 | B2 |
| 8221321 | McMorrow et al. | Jul 2012 | B2 |
| 8262574 | Placek et al. | Sep 2012 | B2 |
| 8262577 | Munrow et al. | Sep 2012 | B2 |
| 8287485 | Kimura et al. | Oct 2012 | B2 |
| 8298145 | Deckman et al. | Oct 2012 | B2 |
| 8337434 | Vaezy et al. | Dec 2012 | B2 |
| 8377041 | Frassica et al. | Feb 2013 | B2 |
| 8469893 | Chiang et al. | Jun 2013 | B2 |
| 8506485 | Deckman et al. | Aug 2013 | B2 |
| 8512330 | Epstein et al. | Aug 2013 | B2 |
| 8512333 | Epstein et al. | Aug 2013 | B2 |
| 8540634 | Bruce et al. | Sep 2013 | B2 |
| 8585598 | Razzaque et al. | Nov 2013 | B2 |
| 8622911 | Hossack et al. | Jan 2014 | B2 |
| 8663130 | Neubach et al. | Mar 2014 | B2 |
| 8718339 | Tonomura et al. | May 2014 | B2 |
| 8814796 | Martin et al. | Aug 2014 | B2 |
| 8845559 | Darlington et al. | Sep 2014 | B2 |
| 8900225 | Bar-Tal et al. | Dec 2014 | B2 |
| 8992427 | Munrow et al. | Mar 2015 | B2 |
| 9089287 | Sliwa et al. | Jul 2015 | B2 |
| 9198707 | McKay et al. | Dec 2015 | B2 |
| 9198719 | Murdeshwar et al. | Dec 2015 | B2 |
| 9247925 | Havel et al. | Feb 2016 | B2 |
| 9357977 | Grossman | Jun 2016 | B2 |
| 9439627 | Case et al. | Sep 2016 | B2 |
| 9460563 | Merschon et al. | Oct 2016 | B2 |
| 9510898 | Epstein et al. | Dec 2016 | B2 |
| 9516996 | Diolaiti et al. | Dec 2016 | B2 |
| 9517047 | Grossman | Dec 2016 | B2 |
| 9662166 | Lee et al. | May 2017 | B2 |
| 9808310 | Grossman | Nov 2017 | B2 |
| 9861336 | Munrow et al. | Jan 2018 | B2 |
| 9987080 | Grossman et al. | Jun 2018 | B2 |
| 10058342 | Deckman et al. | Aug 2018 | B2 |
| 10182862 | Grossman et al. | Jan 2019 | B2 |
| 10321951 | Placek et al. | Jun 2019 | B2 |
| 10595819 | Deckman et al. | Mar 2020 | B2 |
| 10856838 | Munrow et al. | Dec 2020 | B2 |
| 10993770 | Hammudi et al. | May 2021 | B2 |
| 20010014805 | Burbank et al. | Aug 2001 | A1 |
| 20010035189 | Dobak et al. | Nov 2001 | A1 |
| 20010051802 | Woloszko et al. | Dec 2001 | A1 |
| 20020002393 | Mitchell | Jan 2002 | A1 |
| 20020022835 | Lee | Feb 2002 | A1 |
| 20020040220 | Zvuloni et al. | Apr 2002 | A1 |
| 20020052600 | Davison et al. | May 2002 | A1 |
| 20020068871 | Mendlein et al. | Jun 2002 | A1 |
| 20020077550 | Rabiner et al. | Jun 2002 | A1 |
| 20020124853 | Burbank | Sep 2002 | A1 |
| 20020156373 | Wakabayashi et al. | Oct 2002 | A1 |
| 20020183735 | Edwards et al. | Dec 2002 | A1 |
| 20030009164 | Woloszko et al. | Jan 2003 | A1 |
| 20030009166 | Moutafis et al. | Jan 2003 | A1 |
| 20030014046 | Edwards et al. | Jan 2003 | A1 |
| 20030028111 | Vaezy et al. | Feb 2003 | A1 |
| 20030032896 | Bosley et al. | Feb 2003 | A1 |
| 20030045768 | Hirooka et al. | Mar 2003 | A1 |
| 20030078502 | Miyaki et al. | Apr 2003 | A1 |
| 20030114732 | Webler et al. | Jun 2003 | A1 |
| 20030130575 | Desai | Jul 2003 | A1 |
| 20030130655 | Woloszko et al. | Jul 2003 | A1 |
| 20030130665 | Pinczewski et al. | Jul 2003 | A1 |
| 20030195420 | Mendlein et al. | Oct 2003 | A1 |
| 20030195496 | Maguire et al. | Oct 2003 | A1 |
| 20030195502 | Garabedian et al. | Oct 2003 | A1 |
| 20030199472 | Al-Hendy et al. | Oct 2003 | A1 |
| 20030216725 | Woloszko et al. | Nov 2003 | A1 |
| 20030216759 | Burbank et al. | Nov 2003 | A1 |
| 20040002699 | Ryan et al. | Jan 2004 | A1 |
| 20040006336 | Swanson | Jan 2004 | A1 |
| 20040030268 | Weng et al. | Feb 2004 | A1 |
| 20040049121 | Yaron | Mar 2004 | A1 |
| 20040054366 | Davison et al. | Mar 2004 | A1 |
| 20040064134 | Xiao et al. | Apr 2004 | A1 |
| 20040082883 | Kohno | Apr 2004 | A1 |
| 20040120668 | Loeb | Jun 2004 | A1 |
| 20040147920 | Keidar et al. | Jul 2004 | A1 |
| 20040153057 | Davison | Aug 2004 | A1 |
| 20040175399 | Schiffman et al. | Sep 2004 | A1 |
| 20040176760 | Qiu | Sep 2004 | A1 |
| 20040193028 | Jones et al. | Sep 2004 | A1 |
| 20040193238 | Mosher et al. | Sep 2004 | A1 |
| 20040199179 | Elliott | Oct 2004 | A1 |
| 20040215182 | Lee | Oct 2004 | A1 |
| 20040230190 | Dahla et al. | Nov 2004 | A1 |
| 20040231772 | Leonard et al. | Nov 2004 | A1 |
| 20040254572 | Mcintyre et al. | Dec 2004 | A1 |
| 20050033108 | Sawyer | Feb 2005 | A1 |
| 20050038340 | Vaezy et al. | Feb 2005 | A1 |
| 20050085718 | Shahidi | Apr 2005 | A1 |
| 20050085730 | Flesch et al. | Apr 2005 | A1 |
| 20050096647 | Steinke et al. | May 2005 | A1 |
| 20050107781 | Ostrovsky et al. | May 2005 | A1 |
| 20050124882 | Ladabaum et al. | Jun 2005 | A1 |
| 20050149013 | Lee | Jul 2005 | A1 |
| 20050159676 | Taylor et al. | Jul 2005 | A1 |
| 20050177209 | Leung et al. | Aug 2005 | A1 |
| 20050197577 | Makin et al. | Sep 2005 | A1 |
| 20050203399 | Vaezy et al. | Sep 2005 | A1 |
| 20050203410 | Jenkins | Sep 2005 | A1 |
| 20050215990 | Govari | Sep 2005 | A1 |
| 20050216039 | Lederman | Sep 2005 | A1 |
| 20050228288 | Hurst | Oct 2005 | A1 |
| 20050255039 | Desai | Nov 2005 | A1 |
| 20050256405 | Makin et al. | Nov 2005 | A1 |
| 20060010207 | Akerman et al. | Jan 2006 | A1 |
| 20060018665 | Shibata et al. | Jan 2006 | A1 |
| 20060058671 | Vitek et al. | Mar 2006 | A1 |
| 20060058680 | Solomon | Mar 2006 | A1 |
| 20060089636 | Christopherson et al. | Apr 2006 | A1 |
| 20060178665 | Sloan et al. | Aug 2006 | A1 |
| 20060184049 | Tsujita | Aug 2006 | A1 |
| 20060189972 | Grossman | Aug 2006 | A1 |
| 20060241368 | Fichtinger et al. | Oct 2006 | A1 |
| 20060264758 | Hossack et al. | Nov 2006 | A1 |
| 20060276811 | Copa et al. | Dec 2006 | A1 |
| 20060287579 | Okada | Dec 2006 | A1 |
| 20070006215 | Epstein et al. | Jan 2007 | A1 |
| 20070016183 | Lee et al. | Jan 2007 | A1 |
| 20070083082 | Kiser et al. | Apr 2007 | A1 |
| 20070112306 | Agnew | May 2007 | A1 |
| 20070161897 | Sasaki et al. | Jul 2007 | A1 |
| 20070161905 | Munrow | Jul 2007 | A1 |
| 20070167808 | Nozaki | Jul 2007 | A1 |
| 20070203486 | Young | Aug 2007 | A1 |
| 20070232913 | Lau et al. | Oct 2007 | A1 |
| 20070239062 | Chopra et al. | Oct 2007 | A1 |
| 20070255267 | Diederich | Nov 2007 | A1 |
| 20080015664 | Podhajsky | Jan 2008 | A1 |
| 20080045793 | Humble et al. | Feb 2008 | A1 |
| 20080147056 | Van et al. | Jun 2008 | A1 |
| 20080188916 | Jones et al. | Aug 2008 | A1 |
| 20080228081 | Becker et al. | Sep 2008 | A1 |
| 20090043295 | Arnal et al. | Feb 2009 | A1 |
| 20090099544 | Munrow et al. | Apr 2009 | A1 |
| 20090118613 | Krugman et al. | May 2009 | A1 |
| 20090131790 | Munrow et al. | May 2009 | A1 |
| 20090171218 | Nygaard et al. | Jul 2009 | A1 |
| 20090287081 | Grossman et al. | Nov 2009 | A1 |
| 20100056926 | Deckman et al. | Mar 2010 | A1 |
| 20100081920 | Whitmore, III | Apr 2010 | A1 |
| 20100160787 | Gorzitze | Jun 2010 | A1 |
| 20100262133 | Hoey et al. | Oct 2010 | A1 |
| 20100286687 | Feldberg et al. | Nov 2010 | A1 |
| 20100305439 | Shai et al. | Dec 2010 | A1 |
| 20110022034 | Wilson et al. | Jan 2011 | A1 |
| 20110028847 | Whitmore, III | Feb 2011 | A1 |
| 20110087100 | Grossman | Apr 2011 | A1 |
| 20110098564 | Larson et al. | Apr 2011 | A1 |
| 20110218444 | Steffen et al. | Sep 2011 | A1 |
| 20110276038 | McIntyre | Nov 2011 | A1 |
| 20110288540 | Wright et al. | Nov 2011 | A1 |
| 20120010479 | Eusemann et al. | Jan 2012 | A1 |
| 20120071794 | Karni | Mar 2012 | A1 |
| 20120165813 | Lee et al. | Jun 2012 | A1 |
| 20120209115 | Tonomura | Aug 2012 | A1 |
| 20120245575 | Epstein | Sep 2012 | A1 |
| 20120266874 | Kawakami | Oct 2012 | A1 |
| 20120271277 | Fischell et al. | Oct 2012 | A1 |
| 20120277737 | Curley | Nov 2012 | A1 |
| 20120289858 | Ouyang et al. | Nov 2012 | A1 |
| 20120316440 | Munrow et al. | Dec 2012 | A1 |
| 20130041259 | Harks et al. | Feb 2013 | A1 |
| 20130085497 | Chang et al. | Apr 2013 | A1 |
| 20130137979 | Deckman et al. | May 2013 | A1 |
| 20130225995 | Hashiguchi et al. | Aug 2013 | A1 |
| 20130281863 | Chiang et al. | Oct 2013 | A1 |
| 20130296699 | Deckman et al. | Nov 2013 | A1 |
| 20130317366 | Hirayama et al. | Nov 2013 | A1 |
| 20140011172 | Lowe | Jan 2014 | A1 |
| 20140180273 | Nair | Jun 2014 | A1 |
| 20140276081 | Tegels | Sep 2014 | A1 |
| 20150094712 | Murdeshwar et al. | Apr 2015 | A1 |
| 20150150497 | Goldchmit | Jun 2015 | A1 |
| 20150173592 | Leeflang et al. | Jun 2015 | A1 |
| 20150257779 | Sinelnikov et al. | Sep 2015 | A1 |
| 20160051221 | Dickhans et al. | Feb 2016 | A1 |
| 20160113621 | Deckman et al. | Apr 2016 | A1 |
| 20160151041 | Lee et al. | Jun 2016 | A1 |
| 20160249878 | Grossman | Sep 2016 | A1 |
| 20160278740 | Negrila et al. | Sep 2016 | A1 |
| 20160310042 | Kesten et al. | Oct 2016 | A1 |
| 20170060674 | Nazari et al. | Mar 2017 | A1 |
| 20170245838 | Munrow et al. | Aug 2017 | A1 |
| 20170245891 | Munrow et al. | Aug 2017 | A1 |
| 20170290626 | Deckman et al. | Oct 2017 | A1 |
| 20170290627 | Deckman et al. | Oct 2017 | A1 |
| 20180042572 | Munrow et al. | Feb 2018 | A1 |
| 20180070916 | Deckman et al. | Mar 2018 | A9 |
| 20180078303 | Grossman | Mar 2018 | A1 |
| 20180132927 | Chen et al. | May 2018 | A1 |
| 20180318026 | Placek | Nov 2018 | A1 |
| 20190133696 | Spero | May 2019 | A1 |
| 20190192217 | Grossman | Jun 2019 | A1 |
| 20190262080 | Hammudi et al. | Aug 2019 | A1 |
| 20200229892 | Munrow et al. | Jul 2020 | A1 |
| 20210000565 | Munrow et al. | Jan 2021 | A1 |
| 20210038341 | Munrow et al. | Feb 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 104812433 | Jul 2015 | CN |
| 1132049 | Sep 2001 | EP |
| 1426011 | Jun 2004 | EP |
| 1649822 | Apr 2006 | EP |
| H07306714 | Nov 1995 | JP |
| H1176254 | Mar 1999 | JP |
| H11508790 | Aug 1999 | JP |
| 2000342587 | Dec 2000 | JP |
| 2001340350 | Dec 2001 | JP |
| 2003144436 | May 2003 | JP |
| 2003534037 | Nov 2003 | JP |
| 2005058584 | Mar 2005 | JP |
| 2005323669 | Nov 2005 | JP |
| 2006513831 | Apr 2006 | JP |
| 2006255405 | Sep 2006 | JP |
| 2006346341 | Dec 2006 | JP |
| 2007144180 | Jun 2007 | JP |
| 2007215672 | Aug 2007 | JP |
| 2007-312798 | Dec 2007 | JP |
| 2007536063 | Dec 2007 | JP |
| 2009526554 | Jul 2009 | JP |
| 2011500164 | Jan 2011 | JP |
| 2011-0188046 | Sep 2011 | JP |
| 2012519037 | Aug 2012 | JP |
| 2012-176239 | Sep 2012 | JP |
| 2012-228286 | Nov 2012 | JP |
| 2013-153883 | Aug 2013 | JP |
| 2015-529114 | Oct 2015 | JP |
| 6343648 | Jun 2018 | JP |
| 2014-0103690 | Aug 2014 | KR |
| WO 199528129 | Oct 1995 | WO |
| WO 199717105 | May 1997 | WO |
| WO 199811834 | Mar 1998 | WO |
| WO 199814169 | Apr 1998 | WO |
| WO 199927837 | Jun 1999 | WO |
| WO 199933394 | Jul 1999 | WO |
| WO 199943366 | Sep 1999 | WO |
| WO 200000098 | Jan 2000 | WO |
| WO 200113782 | Mar 2001 | WO |
| WO 200180723 | Nov 2001 | WO |
| WO 200195819 | Dec 2001 | WO |
| WO 200211639 | Feb 2002 | WO |
| WO 2003005882 | Jan 2003 | WO |
| WO 2003065908 | Aug 2003 | WO |
| WO 2003088833 | Oct 2003 | WO |
| WO 2004002293 | Jan 2004 | WO |
| WO 2004002550 | Jan 2004 | WO |
| WO 2004020011 | Mar 2004 | WO |
| WO 2004035110 | Apr 2004 | WO |
| WO 2004058328 | Jul 2004 | WO |
| WO 2004064658 | Aug 2004 | WO |
| WO 2005110255 | Nov 2005 | WO |
| WO 2006042117 | Apr 2006 | WO |
| WO 2006086234 | Aug 2006 | WO |
| WO 2006089426 | Aug 2006 | WO |
| WO 2007005830 | Jan 2007 | WO |
| WO 2007112144 | Oct 2007 | WO |
| WO 2007124265 | Nov 2007 | WO |
| WO 2007144004 | Dec 2007 | WO |
| WO 2007149595 | Dec 2007 | WO |
| WO 2008016922 | Feb 2008 | WO |
| WO 2008144341 | Nov 2008 | WO |
| WO 2009049082 | Apr 2009 | WO |
| WO 2009158012 | Dec 2009 | WO |
| WO 2010027820 | Mar 2010 | WO |
| WO 2010099481 | Sep 2010 | WO |
| WO 2014009810 | Jan 2014 | WO |
| WO 2014039795 | Mar 2014 | WO |
| WO 2015087203 | Jun 2015 | WO |
| WO 2015110946 | Jul 2015 | WO |
| WO 2017132153 | Aug 2017 | WO |
| WO 2018089523 | May 2018 | WO |
| WO 2018089923 | May 2018 | WO |
| WO 2018201158 | Nov 2018 | WO |
| WO 2018204284 | Nov 2018 | WO |
| WO 2019226452 | Nov 2019 | WO |
| Entry |
|---|
| U.S. Appl. No. 16/408,790, Controlled Treatment of Tissue and Dynamic Interaction With, and Comparison of, Tissue and/or Treatment Data, filed May 10, 2019. |
| Vascular and Interventional Radiology, SRSC; Nonsurgical Treatment of Uterine Fibroids. Available at http://www.drfibroid.com/treatment.htm. Accessed Apr. 11, 2011. |
| Alterovitz, et al. Simulating Needle Insertion and Radioactive Seed Implantation for Prostate Brachytherapy. Medicine Meets Virtual Reality 11, Westwood et al. (Eds.), IOS Press, Jan. 2003, pp. 19-25. |
| Bergamini, et al. Laparoscopic Radiofrequency Thermal Ablation: A New Approach to Symptomatic Uterine Myomas. Am. J. Obstetrics and Gynecology (2005) 192: 768-73. |
| Chopra et al. Radiofrequency ablation of hepatic tumors adjacent to the gallbladder: feasibility and safety. AJR Am J Roentgenol. Mar. 2003;180(3):697-701. |
| CNN.com Health Women. Experimental technique uses lasers to shrink uterine fibroids. Nov. 28, 2000. |
| Extended European Search Report in co-pending European Application No. 17870547.1, dated May 21, 2020 in 10 pages. |
| Hindley, et al. MRI guidance of focused ultrasound therapy of uterine fibroids: Early results. American Journal of Roentgenology, 2004, 183(6): 1173-1719. |
| International Preliminary Report on Patentability in Application No. PCT/US2017/060674, dated May 14, 2019 in 12 pages. |
| International Search Report in Application No. PCT/US2017/060674, dated Jan. 12, 2018 in 19 pages. |
| Kanaoka, et al. Microwave endometrial ablation at a frequency of 2.45 Ghz. A pilot study. J Reprod Med. Jun. 2001; 46(60): 559-63. |
| Law, et al. Magnetic resonance-guided percutaneous laser ablation of uterine fibroids. J Magn Reson Imaging, Oct. 2000; 12(4):565-70. |
| Liu, et al. Catheter-Based Intraluminal Sonography. J. Ultrasound Med., 2004, 23:145-160. |
| Mogami, et al. Usefulness of MR-guided percutaneous cryotherapy. Med. Imaging Technol. 2004, 22(3): 131-6. (English abstract). |
| MSNBC OnLine Articles, About Us: Articles; “Intrauerine Fibroids Can Now Be Treated Nonsurgically” http://www.fibroids.com/news-blog/2004/08/intrauterine-fibroids-can-now-be-treated-nonsurgically/ Aug. 23, 2004. |
| Okamura, et al. Force Modeling for Needle Insertion into Soft Tissue. IEEE Transactions on Biomedical Engineering, Oct. 2001, 10 (51): 1707-1716. |
| RSNA 2000 Explore News Release. Lasers Liquefy Uterine Fibroid Tumors. 11:30 a.m. CST, Monday, Nov. 27, 2000. |
| Senoh, et al. Saline Infusion Contrast Intrauterine Sonographic Assessment of the Endometrium with High-Frequency, Real-Time Miniature Transducer Normal Menstrual Cycle: a Preliminary Report. Human Reproduction, 14 (10): 2600-2603, 1999. |
| Websand, Inc., New treatment options for fibroid tumors, Copyright 2002 by WebSand, Inc. |
| U.S. Appl. No. 12/119,147, Systems and Methods for Deploying Echogenic Components in Ultrasonic Imagining Fields, filed May 12, 2008. |
| U.S. Appl. No. 17/028,596, Methods and Systems for Controlled Deployment of Needles in Tissue, Sep. 22, 2020. |
| U.S. Appl. No. 12/712,969 (8,262,574), Needle and Tine Deployment Mechanism, filed Feb. 25, 2010 (Sep. 11, 2012). |
| U.S. Appl. No. 11/347,018 (U.S. Pat. No. 7,918,795), Method and Device for Uterine Fibroid Treatment, filed Feb. 2, 2006 (Apr. 5, 2011). |
| U.S. Appl. No. 12/973,642 (U.S. Pat. No. 9,808,310), Method and Device for Uterine Fibroid Treatment, filed Dec. 20, 2010 (Nov. 7, 2017). |
| U.S. Appl. No. 15/720,199 (U.S. Pat. No. 9,987,080), Method and Device for Uterine Fibroid Treatment, filed Sep. 29, 2017 (Jun. 5, 2018). |
| U.S. Appl. No. 15/970,428 (U.S. Pat. No. 10,182,862), Method and Device for Uterine Fibroid Treatment, filed May 3, 2018 (Jan. 22, 2019). |
| U.S. Appl. No. 16/221,138, Method and Device for Uterine Fibroid Treatment, filed Dec. 14, 2018. |
| U.S. Appl. No. 11/620,569, Intrauterine Ultrasound and Method for Use, filed Jan. 5, 2007. |
| U.S. Appl. No. 11/620,594 (U.S. Pat. No. 9,357,977), Interventional Deployment and Imaging System, filed Jan. 5, 2007 (Jun. 7, 2016). |
| U.S. Appl. No. 15/150,813 (U.S. Pat. No. 9,517,047), Interventional Deployment and Imaging System, filed May 10, 2016 (Dec. 13, 2016). |
| U.S. Appl. No. 13/667,891 (U.S. Pat. No. 10,058,342), Devices and Methods for Treatment of Tissue, filed Nov. 2, 2012 (Aug. 28, 2018). |
| U.S. Appl. No. 15/628,166, Devices and Methods for Treatment of Tissue, filed Jun. 20, 2017. |
| U.S. Appl. No. 15/634,368, Devices and Methods for Treatment of Tissue, filed Jun. 27, 2017. |
| U.S. Appl. No. 15/824,511, Interventional Deployment and Imaging System, filed Nov. 28, 2017. |
| U.S. Appl. No. 11/409,496 (U.S. Pat. No. 7,815,571), Rigid Delivery Systems Having Inclined Ultrasound and Needle, filed Apr. 20, 2006 (Oct. 19, 2010). |
| U.S. Appl. No. 11/564,164 (U.S. Pat. No. 7,874,986), Methods and Devices for Visualization and Ablation of Tissue, filed Nov. 28, 2006 (Jan. 25, 2011). |
| U.S. Appl. No. 12/973,587 (U.S. Pat. No. 8,506,485), Devices and Methods for Treatment of Tissue, filed Dec. 20, 2010 (Aug. 13, 2013). |
| U.S. Appl. No. 13/484,076 (U.S. Pat. No. 10,595,819), Ablation Device With Articulated Imaging Transducer, filed May 30, 2012 (Mar. 24, 2020). |
| U.S. Appl. No. 14/989,732 (U.S. Pat. No. 10,610,197), Ablation Device With Articulated Imaging Transducer, filed Mar. 15, 2018 (Apr. 7, 2020). |
| U.S. Appl. No. 16/782,477, Ablation Device With Articulated Imaging Transducer, filed Feb. 5, 2020. |
| U.S. Appl. No. 11/775,452 (U.S. Pat. No. 8,298,145), Peri-Capsular Fibroid Treatment, filed Jul. 10, 2007 (Oct. 30, 2012). |
| U.S. Appl. No. 12/119,147, Systems and Methods for Deploying Echogenic Components in Ultrasonic Imaging Fields, filed May 12, 2008. |
| U.S. Appl. No. 12/245,567 (U.S. Pat. No. 8,088,072), Methods and Systems for Controlled Deployment of Needles in Tissue, filed Oct. 3, 2008 (Jan. 3, 2012). |
| U.S. Appl. No. 13/307,304 (U.S. Pat. No. 8,262,577), Methods and Systems for Controlled Deployment of Needles in Tissue, filed Nov. 30, 2011 (Sep. 11, 2012). |
| U.S. Appl. No. 13/589,975, Methods and Systems for Controlled Deployment of Needles in Tissue, filed Aug. 20, 2012. |
| U.S. Appl. No. 15/595,659, Methods and Systems for Controlled Deployment of Needles in Tissue, filed May 15, 2017. |
| U.S. Appl. No. 15/597,511, Methods and Systems for Controlled Deployment of Needles in Tissue, filed May 17, 2017. |
| U.S. Appl. No. 16/841,201, Methods and Systems for Controlled Deployment of Needles in Tissue, filed Apr. 6, 2020. |
| U.S. Appl. No. 17/028,593, Methods and Systems for Controlled Deployment of Needles in Tissue, filed Sep. 22, 2020. |
| U.S. Appl. No. 17/028,596, Methods and Systems for Controlled Deployment of Needles in Tissue, filed Sep. 22, 2020. |
| U.S. Appl. No. 17/376,039, Methods and Systems for Controlled Deployment of Needles in Tissue, filed Jul. 14, 2021. |
| U.S. Appl. No. 12/424,357, Submucosal Fibroid Ablation for the Treatment of Menorrhagia, filed Apr. 15, 2009. |
| U.S. Appl. No. 12/198,861, Ablation Device With Articulated Imaging Transducer, filed Aug. 26, 2008. |
| U.S. Appl. No. 13/023,383 (U.S. Pat. No. 8,206,300), Ablation Device With Articulated Imaging Transducer, filed Feb. 8, 2011 (Jun. 26, 2012). |
| U.S. Appl. No. 12/712,969 (U.S. Pat. No. 8,262,574), Needle and Tine Deployment Mechanism, filed Feb. 25, 2010 (Sep. 11, 2012). |
| U.S. Appl. No. 13/589,956 (U.S. Pat. No. 10,321,951), Needle and Tine Deployment Mechanism, filed Aug. 20, 2012 (Jun. 18, 2019). |
| U.S. Appl. No. 16/417,193, Needle and Tine Deployment Mechanism, filed May 20, 2019. |
| U.S. Appl. No. 12/775,257, Dual Energy Therapy Needle, filed May 6, 2010. |
| U.S. Appl. No. 13/801,782 (U.S. Pat. No. 9,861,336), Method and Systems for Controlled Deployment of Needle Structures in Tissue, filed Mar. 13, 2013 (Jan. 9, 2018). |
| U.S. Appl. No. 15/793,874 (U.S. Pat. No. 10,856,838), Methods and Systems for Controlled Deployment of Needle Structures in Tissue, filed Oct. 25, 2017 (Dec. 8, 2020). |
| U.S. Appl. No. 17/084,141, Methods and Systems for Controlled Deployment of Needle Structures in Tissue, filed Oct. 29, 2020. |
| U.S. Appl. No. 17/232,051, Methods and Systems for Controlled Deployment of Needle Structures in Tissue, filed Apr. 15, 2021. |
| U.S. Appl. No. 13/801,840 (U.S. Pat. No. 8,992,427), Methods and Systems for Controlled Deployment of Needle Structures in Tissue, filed Mar. 13, 2013 (Mar. 31, 2015). |
| U.S. Appl. No. 16/037,548, Disposable Sheath for Ultrasound Probe Mounted on Reusable Needle Structure, filed Jul. 17, 2018. |
| U.S. Appl. No. 16/408,790 (U.S. Pat. No. 10,993,770), Controlled Treatment of Tissue and Dynamic Interaction With, and Comparison of, Tissue and/or Treatment Data, filed May 10, 2019 (May 4, 2021). |
| U.S. Appl. No. 15/811,520, Methods and Systems for Real-Time Planning and Monitoring of Ablation Needle Deployment in Tissue, filed Nov. 13, 2017. |
| U.S. Appl. No. 10/345,635 (U.S. Pat. No. 6,936,048), Echogenic Needle for Transvaginal Ultrasound Directed Reduction of Uterine Fibroids and an Associated Method, filed Jan. 16, 2003 (Aug. 30, 2005). |
| U.S. Appl. No. 11/142,952, Echogenic Needle for Transvaginal Ultrasound Directed Reduction of Uterine Fibroids and an Associated Method, U.S. Appl. No. 11/142,952. |
| U.S. Appl. No. 16/414,040, Methods and Systems for In Situ Exchange, filed May 16, 2019. |
| U.S. Appl. No. 16/666,271, Methods for Monitoring Ablation Progress With Doppler Ultrasound, filed Oct. 28, 2019. |
| Number | Date | Country | |
|---|---|---|---|
| 20210346095 A1 | Nov 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62421119 | Nov 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16408790 | May 2019 | US |
| Child | 17233838 | US | |
| Parent | PCT/US2017/060674 | Nov 2017 | US |
| Child | 16408790 | US |
