Patent Grant
9675319
Various systems are available to aid a healthcare provider to guide a medical device in a patient or to provide user viewing an object with additional information. The systems can provide image guidance cues to aid the healthcare provider or user, and can also provide additional information for the users benefit.
Implementations disclosed herein provide systems, methods, and apparatus for generating images facilitating medical device insertion into tissue by an operator and other guidance tasks. Certain embodiments pertain to a free-hand medical device guidance system. The system can provide the healthcare provider manual control over the medical device, while making the spatial relationships between the target, medical device and U/S image more intuitive via a visual display. Using this visual feedback, the operator can adjust the medical device's position, orientation, or trajectory. Certain of the contemplated embodiments can be used in conjunction with systems described in greater detail in U.S. patent application Ser. No. 13/014,587, filed Jan. 26, 2011, entitled SYSTEMS, METHODS, APPARATUSES, AND COMPUTER-READABLE MEDIA FOR IMAGE MANAGEMENT IN IMAGE-GUIDED MEDICAL PROCEDURES; U.S. patent application Ser. No. 13/753,274, filed Jan. 29, 2013, entitled MULTIPLE MEDICAL DEVICE GUIDANCE (the '274 Application); U.S. patent application Ser. No. 14/212,933, filed Mar. 14, 2014, entitled MEDICAL DEVICE GUIDANCE; U.S. patent application Ser. No. 14/872,930, entitled AFFECTED REGION DISPLAY, filed Oct. 1, 2015; and U.S. patent application Ser. No. 14/968,445, filed Dec. 14, 2015, entitled SURGICAL GUIDANCE INTERSECTION DISPLAY; each of which is hereby incorporated herein by reference in its entirety.
The system can aid a healthcare provider in guiding one or more medical devices through the tissue of the patient and/or placing the medical devices, and can be used for treatment of tumors, fibroids or cysts, with bipolar radiofrequency medical device ablation, multiple microwave medical devices, electroporation, and/or electrochemotherapy systems, etc. It can also be used for nerve or muscle stimulation or sensing (electrodes in the spine, brain). The system can be used during open surgery, laparoscopic surgery, endoscopic procedures, biopsies, and/or interventional radiology procedures.
The system can be used in conjunction with live intraoperative ultrasound (U/S), pre-operative or intra-operative CT, or any cross-sectional medical imaging modality (e.g. MRI, OCT, etc.). In addition, the system can use a variety of techniques to determine the position and/or orientation of one or more medical devices. For example, the system can use the NDI Aurora magnetic system, the Ascension MedSafe system, NDI Polaris optical system, etc. In some embodiments, a position sensor can be embedded inside, or affixed to each medical device, at the tip, along the shaft, and/or on the handle. Sensors can be built into the medical devices or attached after manufacturing, as described in greater detail in U.S. application Ser. No. 14/212,184, filed Mar. 14, 2014, entitled SENSOR MOUNT, incorporated herein in its entirety.
Each medical device can be associated with one or more sensors, which can continually, or repeatedly, report position and/or orientation, or a single sensor can be used for all the medical devices. In embodiments where one sensor is used, the healthcare provider can attach the sensor to the particular medical device that she is intentionally repositioning, and then, once she has placed that medical device, she can remove the sensor and attach it to the next medical device she is repositioning. In some embodiments, the medical devices can be manipulated by the healthcare provider. In certain embodiments, the system can be used with a robotic manipulator, where the robot controls the medical devices.
In some embodiments, the handles of medical devices can have push-button switches, to allow the user to select a medical device, indicate a tissue target, etc. The handle can also have an indicator light to indicate to the users which medical device is selected. Finally, the handle can have an encoder to detect how much length of electrode has been exposed by the user, and report this information to the guidance system and therapeutic generator.
Image Guidance Systems
In some embodiments, the position sensing unit 106 can track medical devices 112, 114 within an area or volume, which can also be referred to as a tracked region or position sensing region, and provide data to the image guidance unit 104. The medical devices 112, 114 can include invasive medical devices, such as, but not limited to, biopsy needles, ablation needles, surgical needles, nerve-block needles, or other needles, electrocautery device, catheters, stents, laparoscopes or laparoscopic cameras, ultrasound transducers, or other instruments that enter a part of the body, and non-invasive medical devices that do not enter the body, such as, but not limited to, ultrasound transducers, probes, or other external imaging devices, etc. The medical devices 112, 114 can also include medical imaging devices that provide or aid in the selection or generation of medical images for display. In some embodiments, the medical imaging device can be any device that is used to select a particular medical image for display or generate medical images. The medical imaging devices can include invasive medical devices, such as laparoscopic cameras or invasive ultrasound transducers, and non-invasive medical devices, such as external ultrasound transducers.
Although only two medical devices 112, 114 are shown in
Information about and from multiple surgical systems 108 and attached medical devices 112 (and additional medical devices not shown) can be processed by image guidance unit 104 and shown on display 102. These and other possible embodiments are discussed in more detail below. It will be understood that any combination of the display objects, image guidance cues, etc., described herein can be displayed concurrently, or simultaneously. Further, reference to displaying objects “concurrently” and/or “simultaneously” is to be interpreted broadly and may refer to displaying objects in such a way that to a human observer the objects are visible at the same time.
Imager 110 can be communicatively coupled to image guidance unit 104. In some embodiments, imager 110 can be coupled to a second display unit (not shown). The second display unit can display imaging data from imager 110. The imaging data displayed on display 102 and displayed on second display unit can be the same or different. In some embodiments, the imager 110 can be an ultrasound machine 110, the medical device 114 can be a movable imaging unit, such as an ultrasound transducer 114 or ultrasound probe 114, and the second display unit can be a display associated with the ultrasound machine 110 that displays the ultrasound images from the ultrasound machine 110. In some embodiments, a movable imaging unit 114 can be communicatively coupled to image guidance unit 104. The movable imaging unit 114 can be useful for allowing a user to indicate what portions of a first set of imaging data are to be displayed. For example, the movable imaging unit 114 can be an ultrasound transducer 114, a needle or other medical device, for example, and can be used by a user to indicate what portions of imaging data, such as a pre-operative CT scan, to show on a display 102 as image 150. Further, in some embodiments, there can be a third set of pre-operative imaging data that can be displayed with the first set of imaging data.
In some embodiments, a navigation system 101 comprises a display 102 and a position sensing unit 106 communicatively coupled to image guidance unit 104. In some embodiments, position sensing unit 106, display 102, and image guidance unit 104 are coupled to the stand 118. Image guidance unit 104 can be used to produce images 150 that are displayed on display 102. The images 150 produced on display 102 by the image guidance unit 104 can be determined based on ultrasound or other visual images from the first medical device 112 and second medical device 114.
In the illustrated embodiment, the image 150 includes a 2D viewing area 152 and a 3D viewing area 154 (which can also be referred to as a virtual 3D space) each of which includes various display objects. In the 2D viewing area, some or all of the display objects can be displayed as 2D objects. However, it will be understood that some of the display objects in the 2D viewing area can be displayed as 3D objects. In the 3D viewing area 154, some or all of the display objects are displayed as 3D objects. Furthermore, the display objects in the 3D viewing area can be displayed in a perspective based at least in part on a point-of-view location. In the illustrated embodiment, the display objects include an image region 156 with an image or image slice 157, a virtual medical device 158 corresponding to the first medical device 112, a virtual imaging device 160 corresponding to the second medical device 114, trajectory indicator 164, and affected region indicator 206. It will be understood that any combination of the aforementioned display objects can be displayed in the 2D viewing area and/or 3D viewing area as desired.
As a non-limiting example, if the first medical device 112 is an ablation needle 112 and the second medical device 114 is an ultrasound probe 114, then images 150 produced on display 102 can include the images, or video, from the ultrasound probe 114 (non-limiting example: image slice 157) combined with other medical display objects and image guidance cues, such as projected medical device drive (non-limiting example: trajectory indicators 164) or projected ablation volume 213, determined based on the emplacement of ablation needle 112. If the first medical device 112 is an ultrasound probe 112 and the second medical device 114 is a laparoscopic camera 114, then images 150 produced on display 102 can include the video stream from the laparoscopic camera 114 combined with ultrasound data superimposed on the laparoscopic image. More medical devices can be added to the system 101. For example, the system 101 can include an ultrasound probe, ablation needle, laparoscopic camera, stapler, cauterizer, scalpel and/or any other medical device or medical device. The system 101 can also process and/or display collected data, such as preoperative CT scans, X-Rays, MRIs, laser scanned 3D surfaces etc.
The term “emplacement” as used herein is a broad term and may refer to, without limitation, position and/or orientation or any other appropriate location information. The term “pose” as used herein is a broad term encompassing its plain and ordinary meaning and may refer to, without limitation, position and orientation or any other appropriate location information. In some embodiments, the imaging data obtained from one or both of medical devices 112 and 114 can include other modalities such as a CT scan, MRI, open-magnet MRI, optical coherence tomography (“OCT”), positron emission tomography (“PET”) scans, fluoroscopy, ultrasound, or other preoperative, or intraoperative 2D or 3D anatomical imaging data. In some embodiments, medical devices 112 and 114 can also be scalpels, implantable hardware, or any other device used in surgery. Any appropriate surgical system 108 or imager 110 can be communicatively coupled to the corresponding medical instruments 112 and 114.
As noted above, the images 150 produced can also be generated based on live, intraoperative, or real-time data obtained using the second medical device 114, which is communicatively coupled to imager 110. The term “real-time” as used herein is a broad term and has its ordinary and customary meaning, including without limitation instantaneously or nearly instantaneously. The use of the term real-time can also mean that actions are performed or data is obtained with the intention to be used immediately, upon the next cycle of a system or control loop, or any other appropriate meaning. Additionally, as used herein, real-time data can be data that is obtained at a frequency that would allow a healthcare provider to meaningfully interact with the data during surgery. For example, in some embodiments, real-time data can be a medical image of a patient that is updated one time per second. In some embodiments, real-time data can be ultrasound data that is updated multiple times per second.
The medical devices 112, 114 can be communicatively coupled to the position sensing unit 106 (non-limiting example: sensors embedded or coupled to the medical devices 112, 114 can be communicatively coupled with the position sensing unit 106). The position sensing unit 106 can be part of imager 110 or it can be separate. The position sensing unit 106 can be used to determine the emplacement of first medical device 112 and/or the second medical device 114. In some embodiments, the position sensing unit 106 can include a magnetic tracker and/or one or more magnetic coils can be coupled to medical devices 112 and/or 114. In some embodiments, the position sensing unit 106 can include an optical tracker and/or one or more visually-detectable fiducials can be coupled to medical devices 112 and/or 114. In some embodiments, the position sensing unit 106 can be located below the patient. In such embodiments, the position sensing unit 106 can be located on or below the table 120. For example, in embodiments where the position sensing unit 106 is a magnetic tracker, it can be mounted below the surgical table 120. Such an arrangement can be useful when the tracking volume of the position sensing unit 106 is dependent on the location of the position sensing unit 106, as with many magnetic trackers. In some embodiments, magnetic tracking coils can be mounted in or on the medical devices 112 and 114.
In some embodiments, the position sensing unit can determine one or more x, y, z coordinates and/or the quaternions (non-limiting examples: yaw, pitch, and/or roll) of tracking sensors associated with one or more of the medical devices 112, 114. In certain cases, the position sensing unit can determine the one or more x, y, z coordinates of the tracking sensors with respect to a position sensing coordinate system, as described in greater detail below. In some embodiments, the position sensing unit 106 can be an electromagnetic measurement system (non-limiting example: NDI Aurora system) using sensor coils for tracking sensors attached to the first and/or second medical devices 112, 114. In some embodiments, the position sensing unit 106 can be an optical 3D tracking system using fiducials for tracking sensors. Such optical 3D tracking systems can include the NDI Polaris Spectra, Vicra, Certus, PhaseSpace IMPULSE, Vicon MX, InterSense IS-900, NaturalPoint OptiTrack, Polhemus FastTrak, IsoTrak, or Claron MicronTracker2. In some embodiments, the position sensing unit 106 can each be an inertial 3D tracking system comprising a compass, accelerometer, tilt sensor, and/or gyro, such as the InterSense InertiaCube or the Nintendo Wii controller, mechanical tracking system, camera-based tracking system, radar-based tracking system, etc. In some embodiments, the position sensing unit 106 can be attached to or affixed on the corresponding medical device 112 and 114.
In some embodiments, the position sensing units 106, can include sensing devices such as the HiBall tracking system, a GPS device, or signal emitting device that would allow for tracking of the position and/or orientation (non-limiting example: emplacement) of the tracking sensor (also referred to as an emplacement sensor). In some embodiments, a position sensing unit 106 can be affixed to either or both of the medical devices 112, 114. The medical devices 112 or 114 can be tracked by the position sensing unit 106. A room coordinate system reference, such as the display 102 can also be tracked by the position sensing unit 106 in order to determine the emplacements of the medical devices 112, 114 with respect to the room coordinate system. Devices 112, 114 can also include or have coupled thereto one or more accelerometers, which can be used to estimate movement, position, and location of the devices. In some embodiments, the position sensing unit 106 can be an Ascension Flock of Birds, Nest of Birds, driveBAY, medSAFE, trakSTAR, miniBIRD, MotionSTAR, pciBIRD, or Calypso 2D Localization System and tracking sensors attached to the first and/or second medical devices 112, 114 can be magnetic tracking coils.
The term “tracking sensor” (also referred to as an emplacement sensor), as used herein, is a broad term encompassing its plain and ordinary meaning and includes without limitation all types of magnetic coils or other magnetic field sensing devices for use with magnetic trackers, fiducials or other optically detectable markers for use with optical trackers, such as those discussed above and below, or other sensors, such as accelerometers, gyroscopes, etc. In some embodiments, the tracking sensors can be implemented using optical position sensing devices, such as the HiBall tracking system and the position sensing unit 106 can form part of the HiBall tracking system. Tracking sensors can also include a GPS device or signal emitting device that allows for tracking of the position and/or orientation of the tracking sensor. In some embodiments, a signal emitting device might include a radio-frequency identifier (RFID). In such embodiments, the position sensing unit 106 can use the GPS coordinates of the tracking sensors or can, for example, triangulate the radio frequency signal being emitted by the RFID associated with tracking sensors. The tracking systems can also include one or more 3D mice. Furthermore, the system 101 can use the emplacement data associated with the tracking sensors (non-limiting example: received from the tracking sensors or from the position sensing unit 106) to determine other emplacement information, including, but not limited to the emplacement of a trajectory, an image plane, image region, imaged region, and/or one or more intersections, etc. In some cases, the tracking sensors can output the emplacement data, which can be used by the tracker to determine the emplacement of the tracking sensor. In certain cases, the tracker tracking the tracker sensors determines the emplacement of the tracking sensors without data being output from the tracking sensors. The determined emplacement information can be used to generate and display various image guidance cues, such as, but not limited to, the intersection indicator 210, the trajectory indicator 164, a variance volume, a shaded region, the image region 156 with the image slice 157, etc.
In some embodiments, the imaged region can correspond to the tissue or region that is imaged (area and/or volume) by the medical device 114. In some cases, the image plane can correspond to the plane at which the medical device 114 acquires an image and/or a plane in the virtual 3D space that is associated therewith. In certain cases, the image region can correspond to the region (area and/or volume) at which the medical device 114 acquires an image and/or to a region in the virtual 3D space associated therewith. For example, in some cases, image data acquired by the medical device 114 in the medical device's image region can be mapped to a corresponding virtual image region in the virtual 3D space. The image region may also be referred to as an image slice and/or image slab. Furthermore, in some embodiments, the image region can include at least a portion of the image plane.
The emplacement of the image plane, image region (area and/or volume), and/or imaged region can also be determined based at least in part on the operating parameters of the medical device 114. For example, the operating parameters can indicate what portion of the medical device 114 will capture an image (non-limiting example: emit ultrasonic waves), as well as the dimensions of the image region and/or imaged region (non-limiting examples: height, width, and/or depth of the image that will be acquired), as well as the image region.
Images 150 can be produced based on intraoperative or real-time data obtained using first medical device 112, which is coupled to first surgical system 108. In the illustrated embodiment of
In some embodiments, the display 102 displays 3D images to a user, such as a healthcare provider. Stereoscopic 3D displays separate the imagery shown to each of the user's eyes. This can be accomplished by a stereoscopic display, a lenticular auto-stereoscopic display, or any other appropriate type of display. The display 102 can be an alternating row or alternating column display. Example alternating row displays include the Miracube G240S, as well as Zalman Trimon Monitors. Alternating column displays include devices manufactured by Sharp, as well as many “auto-stereoscopic” displays (non-limiting example: Philips). In some embodiments, Sony Panasonic 3D passive displays and LG, Samsung, and/or Vizio 3D TVs can be used as well. Display 102 can also be a cathode ray tube. Cathode Ray Tube (CRT) based devices, can use temporal sequencing, showing imagery for the left and right eye in temporal sequential alternation. This method can also be used by projection-based devices, as well as by liquid crystal display (LCD) devices, light emitting diode (LED) devices, organic LED (OLED) devices, liquid crystal on silicon (LCOS) devices, DLP devices, virtual retinal display (MicroVision) devices, or the like.
In certain embodiments, the display 102 can be a head mounted display (HMD) worn by the user in order to receive 3D images from the image guidance unit 104. In such embodiments, a separate display, such as the pictured display 102, can be omitted. The 3D graphics can be produced using underlying data models, stored in the image guidance unit 104 and projected onto one or more 2D planes in order to create left and right eye images for a head mount, lenticular, or other 3D display. The underlying 3D model can be updated based on the relative emplacements of the various devices 112 and 114, as determined by the position sensing unit(s) 106, and/or based on new data associated with the devices 112 and 114. For example, if the second medical device 114 is an ultrasound probe, then the underlying data model can be updated to reflect the most recent ultrasound image. If the first medical device 112 is an ablation needle, then the underlying model can be updated to reflect any changes related to the needle, such as power or duration information. Any appropriate 3D graphics processing can be used for rendering including processing based on OpenGL, Direct3D, Java 3D, etc. Whole, partial, or modified 3D graphics packages can also be used, such packages including 3DS Max, SolidWorks, Maya, Form Z, Cybermotion 3D, VTK, Slicer, or any others. In some embodiments, various parts of the needed rendering can occur on traditional or specialized graphics hardware. The rendering can also occur on the general CPU, on programmable hardware, on a separate processor, be distributed over multiple processors, over multiple dedicated graphics cards, or using any other appropriate combination of hardware or technique.
One or more components, units, devices, or elements of various embodiments can be packaged and/or distributed as part of a kit. For example, in one embodiment, an ablation needle, one or more tracking sensors, 3D viewing glasses, and/or a portion of an ultrasound wand can form a kit. Other embodiments can have different elements or combinations of elements grouped and/or packaged together. Kits can be sold or distributed separately from or with the other portions of the system 101.
One will readily recognize that there are numerous other examples of image guidance systems 101 which can use, incorporate, support, or provide for the techniques, methods, processes, and systems described herein.
Depicting Medical Devices
It can often be difficult to discern the content of a 3D scene from a 2D depiction of it, or even from a 3D depiction of it. Therefore, various embodiments herein provide image guidance that can help the healthcare provider better understand the scene, relative emplacements or poses of objects in the scene and thereby provide improved image guidance.
With continued reference to
Some models of medical devices have markings such as bands around the shaft (to indicate distance along the shaft), and a colored region 203 near the tip to indicate from where the radio frequency or microwave energy is emitted in the case of an ablation probe. Healthcare providers performing medical device procedures are often familiar with these markings and can use them to help understand the spatial relationship between the medical device and anatomy. In some embodiments, the make and model of the medical device 112 is known to the image guidance system 101 and the virtual medical device 158 displayed in display 102 can resemble medical device 112. The features of medical devices that can be rendered in the scene include the overall shape (diameter, cross sectional shape, curvature, etc.), color, distance markers, visuals or echogenic fiduciary markers, the state of deployable elements such as tines, paddles, anchors, resection loops, stiffening or steerable sleeves, temperature, radiation, light or magnetic field sensors, lens, waveguides, fluid transfer channels, and the like.
The type of medical device being used can be input into the image guidance system 101, can be a system default, can be detected by a camera or other device, can be received as data from an attached medical device, such as surgical system 108, or the information can be received in any other appropriate manner. Displaying on display 102, a virtual medical device 158 that resembles the medical device 112 can help healthcare providers associate the image guidance data with the real world and can provide more familiar guidance information to a healthcare provider, thereby further aiding the healthcare provider in the guidance task. For example, the healthcare provider can see the familiar markings on the medical device 158 being displayed on the display 102 and therefore be familiar with the distance and relative placement of the displayed medical device 158 with respect to other data, such as a tumor 212 or ablation volume 213 seen in a rendered ultrasound image slice 152, 157. This knowledge of relative placement of items being displayed can help the healthcare provider move the medical device 112 into place.
Consider an embodiment in which the virtual medical device 158 in the display 102 is an ablation needle depicting the portion of the needle that will perform the ablation, for example, the portion that emits the radio or microwave energy. If the display 102 also includes ultrasound data, then the doctor can be able to find the tumor 212 she wishes to ablate by moving the ultrasound probe around until she spots the tumor 212. In various embodiments, she will be able to see the displayed ultrasound data and its location relative to the displayed medical device with the markings. She can then drive the medical device until she sees, on display 102, that the emitter-portion of the medical device encompasses the tumor in the ultrasound, also seen on display 102. When she activates the ablation, she can then be more certain that she has ablated the correct portion of the tissue. Various embodiments of this are discussed below.
It will be understood that an image slice or image slab can also refer to image data received from an imaging device, such as an ultrasound transponder. In some embodiments, the image data can correspond to a cross-section of tissue having a certain thickness. In some instances, the imaging device can compact the image data, and/or treat the image data as 2D data, such that there is no perceived thickness. In certain embodiments, when the image slice is displayed in a 3D view, the system 101 can treat the image slice as a 2D or quasi 2D object. In such embodiments, the system 101 can cause the image slice to have little to no perceptible thickness. Accordingly, in certain embodiments, when the image slice is oriented orthogonally or perpendicularly with respect to the point-of-view location (or point-of-view plane), the system 101 can cause the display to display nothing or a line having a relatively small thickness, such as a few pixels, etc. In some cases, the number of pixels used to display the relatively small thickness of the image slice can correspond to the size of the display. For example, more pixels can be used for a larger display and fewer pixels can be used for a smaller display, etc.
Other embodiments can track and display other types of instruments and their features. For example, a healthcare provider may want to track one or more of a scalpel, a biopsy, a cauterizer (including an electrocauterizer and Bovies), forceps, cutting loops on hysteroscopes, harmonic sheers, lasers (including CO2 lasers), etc. For example, in various embodiments, the following devices can be tracked and various aspects of their design displayed on display 102: Olympus™ OES Pro Hystero-Resectoscope, SonoSurg Ultrasonic Surgical System Olympus™ GF-UC 160 Endoscope Wallus™ Embryo Transfer Catheter AngioDynamics® NanoKnife™, VenaCure™ laser, StarBurst, Uniblade, Habib® Resector Bovie™ Electrodes, Covidien Evident™, Cool-Tip™ Ablation Antennas, Opti4™ Electrodes Microsulis MEA (microwave endometrial ablation), Acculis Halt™ Medical System Optimed BigLumen Aspiration Catheter Optimed Optipure Stent Central venous catheterization introducer medical device (such as those made by Bard and Arrow).
Once tracked, a healthcare provider is able to see image guidance data on display 102 that will allow her to know the relative pose, location, or emplacement of the tracked instrument(s) with respect to one another or with respect to imaging data and will be able to see, on display 220, the features of the instrument rendered in the scene.
Depicting Medical Device Placement, Trajectory, and Other Image Guidance Cues
In certain procedures, the system 101 can provide image prediction information related to the medical devices as image guidance cues. In the context of scalpel movement, this can be the location that the scalpel will hit if a healthcare provider continues to move the scalpel in a particular direction. In the context of ablation or biopsies, this can be the projected medical device placement if it is driven along its central axis, which is also referred to herein as a longitudinal axis.
In some embodiments, to implement the trajectory indicators 164, the image guidance system 101 can draw a number of rings about the axis of the medical device shaft, extrapolated beyond its tip, as depicted in
The rings can, in some embodiments, be spaced at regular (non-limiting examples: 0.5, 1, or 2 cm) intervals to provide the healthcare provider with visual or guidance cues regarding the distance from the medical device tip to the targeted anatomy. In some embodiments, the spacing of the rings can indicate other aspects of the data, such as the drive speed of the medical device, the density of the tissue, the distance to a landmark, such as the ultrasound data, or any other appropriate guidance data or property. In some embodiments, the rings or other trajectory indicators can extend beyond the medical device tip, by a distance equal to the length of the medical device-shaft. This way, the user knows if the medical device is long enough to reach the target—even before the tip enters the patient. That is, in some embodiments, if the rings do not reach the target with the tip still outside the body, then the tip will not reach the target even when the entire length shaft is inserted into the body.
Other display markers can be used to show trajectory, such as a dashed, dotted, or solid line, transparent medical device shaft, point cloud, wire frame, etc. In some embodiments, three-dimensional rings can be used and provide depth cues and obscure little of the ultrasound image. Virtual rings or other virtual markers can be displayed semi-transparently, so that they obscure less of the ultrasound image than an opaque marker would.
Other prediction information can also be displayed as image guidance cues. For example, if a scalpel is being tracked by the image guidance system 101, then a cutting plane corresponding to the scalpel can be displayed (not pictured). Such a cutting plane can be coplanar with the blade of the scalpel and can project from the blade of the scalpel. For example, the projected cutting plane can show where the scalpel would cut if the doctor were to advance the scalpel. Similar prediction information can be estimable or determinable for cauterizers, lasers, and numerous other medical devices.
Furthermore, the data from two or more devices can be combined and displayed based on their relative emplacements or poses. For example, the rendered image slice 157 can be displayed on the image plane (non-limiting example: in the image region) with respect to the virtual medical device 158 on the display 102 in a manner that estimates the relative emplacements or poses of the medical imaging device 114 and the medical device 112. The image guidance cues associated with the virtual medical device 158, including the affected region indicator 206 and trajectory indicators 164, are shown spatially located with the rendered ultrasound image slice 157 on display 102.
In addition, the display 102 can include another image guidance cue in the form of an intersection indicator 210 that indicates where the virtual ablation medical device 158 (and/or its axis and/or its trajectory) intersects the ultrasound image slice 157. In some embodiments, the intersection indicator 210 can be displayed before the medical device is inserted, thereby allowing the healthcare provider to see where the medical device will intersect the image, or imaged region. As will be described in greater detail below, in some cases, due to uncertainties related to the emplacement of the medical devices, the system 101 can use a variance parameter to determine and display the intersection indicator 210.
In the illustrated embodiment, a tumor 212 appears in the ultrasound image, or rendered ultrasound image slice 157, and the virtual ablation needle 158 is shown driven through the tumor 212. As described in greater detail in U.S. application Ser. No. 14/872,930 (the '930 Application), incorporated herein by reference in its entirety, the displayed affected region (or affected region indicator) 206 can indicate what region or volume would be affected when the medical device 112 is operated. In the illustrated embodiment, the displayed affected region 206 can estimate where ablation would occur if the tissue were ablated at that time. As can be seen, in the illustrated embodiment, the displayed affected region 206 appears to cover the tumor displayed in the ultrasound image.
Various embodiments can include any combinations of the graphics described above and/or other graphics or image guidance cues. For example, in some embodiments, data related to a single medical device (such as an ablation needle, ultrasound probe, etc.) can be presented in more than one manner on a single display. Consider an embodiment in which device 112 is an ablation needle and device 114 is an ultrasound transducer. As mentioned previously, as the medical devices are displayed in a virtual 3D space, with the display 102 acting as a window into the virtual 3D space, if a healthcare provider orients medical imaging device 114 such that it is perpendicular to the point-of-view or point-of-view location (non-limiting example: perpendicular to the screen), the perspective view of the ultrasound image slice 157 would show only the edge and the contents of the ultrasound image slice 157 would not be visible. In some embodiments, the image guidance system 101 can track the healthcare provider's head using an emplacement sensor and/or a position sensing unit. In some embodiments, such as, when the head of a user is tracked, the healthcare provider can then move her head to the side, so that she sees the ultrasound image from a different point of view location.
In some embodiments, the image guidance system 101 can concurrently display a 2D view 152 of the ultrasound image with the 3D depiction 154, so that the ultrasound image is always visible, regardless of the emplacement in which the healthcare provider holds the medical imaging device 114. The 2D view 152 of the ultrasound data can be similar to what a healthcare provider is accustomed to seeing with traditional ultrasound displays. This can be useful to provide the healthcare provider with imaging to which she is accustomed and allows a healthcare provider to see the ultrasound data regardless of the then-current emplacement of the ultrasound probe with respect to the user.
In some embodiments, the 2D view 152 of an ultrasound image is depicted in the upper right corner of the monitor (though it can be placed in any location). In some embodiments, the guidance system 101 can automatically (and continually) choose a corner in which to render the 2D view 152 of the ultrasound image, based on the 3D position of the medical devices in the rendered scene. For example, ablation needle 112 can be held in the healthcare provider's left hand and the medical device shaft is to the left of the 3D view of the ultrasound image slice, so that the 2D view 152 of the ultrasound image in the upper right corner of display 102 does not cover any of the 3D features of the medical device (or vice-versa). If the medical device were held in the healthcare provider's right hand (and to the right of the ultrasound image slice 157, the virtual medical device shaft would appear on the right side. To prevent the 2D view 152 in the corner of display 102 from covering the medical device shaft, the system 101 can automatically move it to a corner that would not otherwise be occupied by graphics or data.
In some embodiments, the system 101 attempts to avoid having the 2D view 152 of the ultrasound image quickly moving among corners of the display in order to avoid overlapping with graphics and data in the display. For example, a function f can be used to determine which corner is most suitable for the 2D ultrasound image to be drawn in. The inputs to f can include the locations, in the screen coordinate system, of the displayed medical device tip, the corners of the 3D view of the ultrasound image, etc. In some embodiments, f's output for any given point in time is independent of f's output in the previous frames, which can cause the ultrasound image to move among corners of the display rapidly. In some embodiments, the image guidance system 101 will filter f's output over time. For example, the output of a filter g, for any given frame, could be the corner, which has been output by f the most number of times over the last n frames, possibly weighting the most recent values for f most heavily. The output of the filter g can be used to determine in which corner of display 102 to display the 2D ultrasound image and the temporal filtering provided by g can allow the 2D view 152 of the ultrasound image display to move more smoothly among the corners of the display 102.
In some embodiments, other appropriate virtual information and/or image guidance cues can be overlaid on the 2D view 152 of the ultrasound image as well as the 3D view 154. Examples include: an indication of the distance between the medical device's tip and the point in the plane of the ultrasound image that is closest to the medical device tip; the cross section or outline of the ablation volume that intersects with the ultrasound slice; and/or the intersection point, box, outline, etc. between the virtual medical device's axis and the ultrasound image plane.
Furthermore, it will be understood that other image guidance cues can be generated and displayed on the display as described in greater detail in the '274 Application, previously incorporated herein by reference. For example, the system 101 can generate and/or display graphical indicators that help indicate the spatial relationship between a medical device and an ultrasound image plane (non-limiting example: graphical image plane indicators) or other plane indicators to indicate the relative positions of the virtual medical device(s) and ultrasound image, features of interest, annotations, foundational plane indicators, foundational plane intersection indicators, other graphical indicators, approximate medical device location indicators, etc. As described in greater detail above and in the '274 Application, the various image guidance cues can be generated based at least in part on the emplacement information of the medical devices used with the system 101.
Referring now to
Displays 252, 254 can allow the displayed content 253, 255 to be seen clearly without glare or interference due to light from the world in the region beyond the displays 252, 254. In certain embodiments, displays 252, 254 occupying less than the entire field of view of the wearer can allow the wearer to view the virtual content 253, 255 while also viewing the real environment in the portion of the wearer's field of view unoccupied by displays 252, 254, such as through transparent portions 256, 258 of the HMD 250.
In some embodiments, the imaging systems described herein can display virtual image content on the displays 252, 254 using a location offset with respect to the location of corresponding objects. For example, rather than displaying and/or augmenting content that is directly in front of the displays 252, 254 and/or the HMD 250, the displays 252, 254 can display and/or augment objects that are located elsewhere, such as below, above, or to the side of the displays 252, 254 and/or the HIVID 250. In the illustrated embodiment, the virtual medical devices 158, 160 can be displayed with a vertical offset relative to the medical devices 112, 114 (or the position sensing region) so as to allow a wearer of the HIVID 250, such as a surgeon, to simultaneously view the virtual medical devices 158, 160 on the displays 252, 254 and the patient 116 with real medical devices 112, 114 located below the HMD 250.
In certain embodiments, if the wearer rotates their head down or up, the display objects on the displays 252, 254 can shift up or down, respectively, relative to the displays 252, 254 (or the wearer's field of view). In some embodiments, the wearer rotates their head right or left, the displays 252, 254 can shift to the left or right, respectively, relative to the displays 252, 254 (or the wearer's field of view). Thus, the system 101 can cause the display objects in the displays 252, 254 to mimic the behavior of real objects located at a particular location at which a person is looking (or oriented), or offset from a particular location at which a person is looking (or oriented). Accordingly, in some embodiments, the system 101 can cause the displays 252, 254 to display display objects (non-limiting examples: virtual medical devices 158, 160) based at least in part on the emplacement of corresponding objects (non-limiting examples: medical devices 112, 114) relative to tracked displays 252, 254, or the emplacement of corresponding objects with an offset relative to tracked displays 252, 254.
The offset can be predetermined based on a dimension or preference of an individual wearer prior to use, or based on a default such as an average height or dimension of an expected wearer, or dynamic based on data received during use. An example offset can be a distance equal or approximately equal to the vertical distance between a wearer's elbow and the wearer's eye (non-limiting example: in the range of 0.5 m to 1 m), a measured distance between the HIVID 250 and the medical devices 112, 114, etc. Non-limiting embodiments of methods for implementing the offset are described in greater detail with reference to
The HMD 250 can be implemented with any of the imaging systems described with reference to
Coordinate Systems
A position sensing coordinate system 180 can be used to determine the emplacement of various objects within a position sensing region. For example, in some embodiments, the position sensing coordinate system 180 can refer to the coordinate system 180A used by a magnetic tracker (not shown) tracking objects within a magnetic field volume, or to the coordinate system 180B used by an optical tracker 196 tracking objects within a volume. In some cases, multiple position sensing coordinate systems 180 can be used together. For example, a magnetic position sensing coordinate system 180A can be used in conjunction with a magnetic tracker tracking sensor coils within a position sensing region that are coupled to medical devices and an optical position sensing coordinate system 180B can be used in conjunction with an optical tracker tracking a fiducial coupled to an HIVID or a user, or to an optical tracker analyzing an image captured by an image sensor. It will be understood that any combination of the tracker systems and position sensing coordinate systems 180 can be used as desired. For example, in some cases, a single position sensing coordinate system 180 can be used to track tracking sensors associated with one or more medical devices and/or tracking sensors associated with a user or HIVID. Similarly, a different position sensing coordinate system 180 can be used for each tracking sensor, or any combination thereof.
Room coordinate systems 182 can be used to determine the emplacement of objects within a room, such as an operating room. For example, the room coordinate system 182 can be used to determine or identify the relative emplacement of the position sensing unit, medical devices, tracking sensors, user, display, etc. relative to each other within a room.
A 3D scene coordinate system 184, which may also be referred to as a 3D volume or scene graph coordinate system, can be used to determine the emplacement of display objects within a virtual 3D scene. In some cases, the 3D scene coordinate system 184 can identify the relative emplacement of virtual objects within the 3D scene. In certain embodiments, the virtual objects can correspond to real objects, such as to medical devices 112, 114 and/or to computer-generated objects, such as such as trajectory cues 164, ablation volume 213, etc.
A display coordinate system 186 can be used to determine the emplacement of display objects for display on the display 102 and/or displays 252, 254. For example, the display coordinate system 186 can be used to determine the emplacement of virtual medical devices, medical image data streams, image guidance cues, and the like, within a display 102 and/or displays 252, 254. In some embodiments, the display coordinate system 186 can be used to determine how the objects within the 3D scene are to be displayed on the display 102 and/or displays 252, 254. For example, the display coordinate system 186 can be used to determine the point-of-view location, or eye point, relative to the 3D scene (or 3D volume coordinate system 184) or scene graph for viewing the contents of the 3D scene. As mentioned above, multiple display coordinate systems 186 can be used. For example, left-eye, right-eye, and/or center-eye display coordinate systems 186 can be used to display different perspective of the display objects within a 3D scene, such as when a 3D display and/or a HIVID is being used.
A medical image coordinate system 194 can be used in conjunction with medical images used and/or processed by the system. As described previously, the medical images can be ultrasound images, CT image, MRI, images, etc. The images can be different sizes or shapes. For example, one ultrasound can output an image having one size and shape while a different ultrasound can output an image having a different size and/or shape. Similarly, CT, MRI, and ultrasound images may have different sizes and shapes. Accordingly, the medical image coordinate system can be used to identify the particular size and shape of the medical image being used and/or processed by the system 101.
It will be understood that fewer, more, or different coordinate systems can be used as desired. For example, in some embodiments, the 3D scene coordinate system 184 can be omitted or combined with display coordinate system 185 and/or the position sensing coordinate system 180. Furthermore, in some cases, one or more tracking sensor coordinate systems 188A, 188B, medical device coordinate systems 190A, 190B, virtual medical device coordinate systems 192A, 192B, or other objects etc., can have their own coordinate system. The coordinate systems for the tracking sensors, medical devices, and/or virtual medical devices can be used to identify the dimensions of the sensor/device/object and relationship of the sensor/device/object to other sensor/device/object or other coordinate systems. For example, a medical device coordinate system (or virtual medical device coordinate system) can identify the dimensions of a corresponding medical device or virtual medical device, as well as the emplacement of a tracking sensor relative to the medical device (or vice versa). Similarly, a medical imaging device coordinate system can identify the dimensions of the corresponding medical imaging device (or virtual medical imaging device) and/or an emplacement of a medical image relative to the medical imaging device (non-limiting example: the emplacement of an ultrasound image relative to the corresponding ultrasound transducer), or vice versa. The system 101 can use various coordinate systems to determine the emplacement of a portion or the entire object with respect to each other and with respect to the other coordinate systems.
The system 101 can use the various coordinate systems to determine emplacement of objects relative to each other and determine how to display the display objects on a display, such as the display 102 and/or the displays 252, 254. As a non-limiting example, to display a virtual rendering of an ultrasound transducer 160 and ultrasound image stream 157 on display 102 and/or displays 252, 254, the system 101 can determine the emplacement of a magnetic tracking sensor coupled to the ultrasound transducer 114 within a magnetic position sensing coordinate system 180. Using a magnetic tracking sensor coordinate system 188B, the system 101 can determine the location of each portion of the magnetic tracking sensor within the magnetic position sensing coordinate system 180. The system 101 can also determine the emplacement of each portion the ultrasound transducer 114 within the magnetic position sensing coordinate system by mapping the ultrasound transducer coordinate system 190B to the magnetic tracking sensor coordinate system 188B (or vice versa) and/or to the magnetic position sensing coordinate system 180.
In addition, the system 101 can map each portion of the ultrasound image 157 corresponding to the ultrasound transducer 114 to the magnetic position sensing coordinate system 180 by mapping an ultrasound image coordinate system 194 to the ultrasound transducer coordinate system 190B, the magnetic tracking sensor coordinate system 188B, and/or to the magnetic position sensing coordinate system 180.
To display the virtual ultrasound transducer 160 and ultrasound image slice 157, the system 101 can map the various objects from the magnetic position sensing coordinate system 180 to a room coordinate system 182, which can identify the relative emplacement of the position sensing coordinate system 180 to a display. The system can then map data to the 3D scene coordinate system 194 and/or the display coordinate system 186. For 3D viewing, the system 101 can map the objects to multiple display coordinate systems 186, such as left-eye and/or right-eye coordinate systems.
With continued reference to the non-limiting example, the system 101 can determine an emplacement of an optical tracking sensor corresponding to a user within an optical position sensing coordinate system 180B. The emplacement of the optical tracking sensor within the optical position sensing coordinate system 180B can be mapped to the room coordinate system 182, the 3D scene coordinate system 184, and/or the display coordinate systems 186 for display. In this way the system 101 can determine the emplacement of the ultrasound transducer 114 and ultrasound image slice 157 relative to the user and display a virtual rendering of the ultrasound transducer 160 and ultrasound image slice 157 within the 3D scene relative to the determined emplacement of the user.
Although the non-limiting example has been described as mapping the various objects and coordinate systems, to a position sensing coordinate system 180, the room coordinate system 182, the 3D scene coordinate system 184, and to display coordinate systems 186, it will be understood that the one or more of the objects or coordinate systems can be mapped directly or indirectly to any other coordinate system. For example, the medical device image can be mapped directly to a left-eye display coordinate system 186, etc. Thus, any of the real or virtual objects described herein may be represented, detected, or imaged in any coordinate system, and conversion between the various coordinate systems can be performed in components of the system such as image guidance unit 104, position sensing unit 106, imager 110, the HMD 250, or other components.
Furthermore, it will be understood that once the system 101 determines an emplacement of a medical device in one coordinate system, such as a position sensing coordinate system 180, the system 101 can determine the emplacement of a corresponding virtual medical device in a different coordinate system, such as the 3D scene coordinate system 184 or the screen coordinate system 186, by mapping the coordinates of the first coordinate system to the coordinates of the second coordinate system, or vice versa. Accordingly, references made herein to determining an emplacement of the medical device can also refer to determining an emplacement of a virtual medical device corresponding to the medical device, or vice versa. Similarly, references made herein to determining an emplacement of an object (non-limiting example: medical image) relative to the medical device can also refer to determining the emplacement of the object relative to a corresponding virtual medical device.
Head Mounted Display
In some embodiments, the HIVID 250 can include fewer or more displays. For example, in some cases the HIVID 250 can include one display. The single display can be configured for a left-eye view, right-eye view, monocular view, and/or can be centered with respect to the left eye, right eye, between the eyes, or some other location. Similarly, the HIVID 250 could include more than two displays. For example, a third display could be used to display additional information, such as a non-perspective view of the ultrasound image, similar to 2D view 152 of
With respect to
With respect to
With respect to
In some embodiments, the support structure 260 can include one or more hinges, such as at locations 263, 265, or gear 267, to enable a wearer 264 to manually change the location of the display 251 within her field of view based on personal preference and/or comfort.
In various embodiments, the display 251 can be sized and/or located so as to occupy a desired portion of the wearer's field of view. A typical human field of view can span approximately 180°−200° (approximately 110° for each eye) horizontally and 135° vertically. In certain embodiments, the display 251 can occlude a portion of the field of view large enough to provide useful content to the viewer, but small enough to allow the wearer to view objects in the world around the wearer through the unoccluded space surrounding the display 251.
In certain embodiments, such as when the displays 251 are opaque, the display(s) 251 can occlude a region of between approximately 10°−50° horizontally, leaving at least 130° unoccluded horizontally. For example, the display(s) 251 can occlude approximately (±a few degrees) 10°, 15°, 20°, 25°, 30°, 35°, 40°, 45°, or 50° of a wearer's horizontal field of view. The field of view occluded by the display(s) can be centered with respect to the user's field of view, centered with respect to the right eye or left eye of the user, or not centered. In certain embodiments, the occluded field of view can be split up, such that one portion of the occluded field of view is centered over, or otherwise occludes, the left eye field of view and another portion of the occluded field of view is centered over, or otherwise occludes, the right eye field of view. In some embodiments, the display(s) 251 can occlude between approximately 35°−135° horizontally. However, it will be understood that other sizes can be used such that the display occludes <35° or >135° horizontally
In addition, in some embodiments, the display(s) 251 can occlude between 14°−110° vertically, such that at least 25° are unoccluded vertically. For example, the display(s) 251 can occlude approximately (±a few degrees) 10°, 20°, 30°, 40°, 50°, 60°, 70°, 80°, 90°, 100°, or 110° of a wearer's vertical field of view. The field of view occluded by the display(s) can be centered with respect to eye level, centered below eye level, or centered above eye level. However, it will be understood that other sizes can be used such that the display occludes <14° or >110° vertically. In addition, it will be understood that the vertical size of the display(s) can be combined with any combination of the horizontal size of the displays.
It will be understood that the HIVID 250 can include fewer, more, or different components as desired. For example, in some embodiments, the HIVID 250 can the display(s) 251 can be attached directly to frame 262 without a support structure 260, or only one display 251 can be included as part of the HIVID 250.
The displays 252, 254 can display stereoscopic images for right eye and left eye viewing, as described in greater detail above. In the illustrated embodiment, the displays 252, 254 are opaque and occlude approximately 26° horizontally and approximately 15° vertically of a wearer's field of view. However, as described above, the displays 252, 254 can be sized to occlude different amounts of a wearer's field of view and can be placed in a variety of locations (non-limiting examples: above eye level, below eye level, to the left or right, etc.). However, although the illustrated embodiment of
The earpieces 268 and nose pad 270 can support the HIVID 250 on the head of a wearer. In some embodiments, the frame 266 can be a frame 266 designed for medical use, such as to receive surgical or dental loupes, or can be any other type of eyeglass frame 266. The space within the frame 266 in the wearer's field of view can be empty, or can include transparent lenses 272 to allow the wearer to observe her surroundings. In some implementations, transparent lenses 272 can provide the advantage of eye protection, such as in surgical and/or dental applications where the wearer can be exposed to airborne biological matter or other hazards.
The enclosure 274 can enclose processing circuitry used to display images on the displays 252, 254. For example, the enclosure 274 can enclose a processor, memory, battery, image sensor, a communication device, one or more emplacement sensors and/or a tracker system, etc. However, it will be understood that the enclosure 274 can enclose fewer or more components as desired. For example, the emplacement sensors and/or a tracker system may be located exterior to the enclosure 274, etc.
The communication device can be used to communicate data to and from other components of the guidance system 101. For example, the communication device can send and/or receive the medical images from the medical imager and the tracking sensor data. The communication device can communicate the data via a wired or wireless communication protocol, such as Bluetooth, Wi-Fi, cellular, Ethernet, USB, etc. In some embodiments, the communication device includes an antenna for wireless communication.
The processor can be implemented using a microprocessor, microcontroller, field programmable gate array, or the like and can process the data received by the communication device or generated at the HMD 250, and perform any one or any combination of the various functions, methods, or routines described herein, similar to the image guidance unit 104 and/or position sensing unit 106, described previously with reference to
The memory can store non-transitory computer-readable instructions that when executed by the processor cause the processor to perform the various functions, methods, and routines described herein. The battery can be used to provide the HIVID 250 with electrical power in order to process the data and display the images on the displays 252, 254. In some embodiments, such as when the HIVID 250 receives electrical power from an external source the battery can be omitted.
The image sensor 271 can be used to image the area in front of the HIVID 250. In some embodiments, the image sensor 271 can be used as a tracking sensor or tracker system to determine the emplacement of the wearer or HIVID 250 relative to the other components of the guidance system 101.
The one or more emplacement sensors or tracker systems can be used to determine the emplacement of the wearer or HIVID 250 relative to the other components of the guidance system 101. The emplacement sensor or tracker system can be located within the enclosure 274 or exterior to the enclosure. In some embodiments, the emplacement sensor is located elsewhere on a user, such as on a band around the head or clipped to a jacket of the user, etc. In certain embodiments, the emplacement sensor or tracker system associated with the HMD 250 can use a different coordinate system than the emplacement sensors associated with the medical devices 112, 114. However, it will be understood that in some cases, the emplacement sensors associated with the HIVID 250 or user and the emplacement sensors associated with the medical devices 112, 114 can use the same coordinate system.
The HIVID 250 can include fewer or more components as desired. For example, in some embodiments, such as when the data from the various emplacement sensors and medical devices is processed outside the HMD 250, the HIVID 250 can omit the enclosure 274 and/or some of the components enclosed within the enclosure.
Orbital Mode
Consider an embodiment in which a surgeon is wearing the HIVID 250 while performing a surgical procedure on a patient 116 with an ablation needle 112 and an ultrasound probe 114, while being assisted by 3D virtual image content as described above. The surgeon, standing at the patient's side, may desire to view the image slice 157 and a virtual medical device 158 at a different angle, such as to improve the surgeon's awareness of the location of the medical device 112 within the body of the patient. For example, the surgeon may wish to view the virtual image content from a location near the head of the patient 116 (non-limiting example: from a view angle approximately 90 degrees from the current view angle). The orbital view mode can permit the surgeon to change the viewing angle, or perspective view, of the virtual image content by rotating her head, rather than moving relative to the patient 116. In the reference frame of the wearer of an HIVID 250, the orbital view mode can cause the displayed virtual object to appear to “orbit” the wearer's head while maintaining its position in the center of the wearer's field of view. In the reference frame of a display 252, 254 of the HIVID 250, the virtual object can remain stationary, but can rotate in the direction opposite the rotation of the wearer's head and the HMD 250.
In some embodiments, rotation of the tracking sensor associated with the user about an axis can cause the objects within the virtual 3D scene to rotate about a similar axis in an opposite direction. For example, for the sake of simplicity, consider an embodiment in which the coordinate system for a user is: x-axis is left-right, y-axis is up-down, and z-axis is forward-backward (origin at the center of the user's head) and the coordinate system for a display object is x-axis is left-right, y-axis is up-down, and z-axis is into/out of the display (origin at the center of the object). If a user turns their head to the right (rotates about the user y-axis in a clockwise manner), then the objects within the virtual 3D scene can rotate to the left (rotate about the display object y-axis in a counter-clockwise manner), or the viewing angle can move to the right relative to the origin of the virtual 3D scene. From the perspective of a room coordinate system, the object can orbit around the user's head while maintaining its orientation. In this way, if an image slice is edge-on or approximately edge-on and the user wants to see the right side of the image slice, the user can rotate their head to the left. Similarly, if the user wants to see the left side of an edge-on image slice, the user can turn their head to the right (rotation of head about the user y-axis in a counter-clockwise direction causes the content of the virtual 3D scene to rotate about the display object y-axis in a clockwise manner).
The orbital mode can work with any axis. For example, if the user wants to see to the bottom of an object in the virtual 3D scene she can look up or if the user wants to see to the top of an object in the 3D scene she can look down (rotation of head about x-axis in one direction causes the contents of the virtual 3D scene to rotate about the x-axis in the opposite direction).
With reference to
Based on the determined orientation change of the HIVID 250, the orientation of the contents of the virtual 3D scene, specifically the virtual medical devices 158, 160 and the image slice 157 within the displays 252, 254 have rotated clockwise such that a larger portion of the image slice 157 is visible and the virtual needle 158 which was seen pointing to the wearer's right in
In certain embodiments, the orbital mode can be specific to one or more display objects within the 3D scene or to the 3D scene as a whole. For example, based on the rotation of the user, the medical image and/or one or more virtual medical devices can rotate alone or in combination. It will be understood that the orbital mode can also be configured such that the objects within the virtual 3D scene rotate about a different axis and/or in the same direction as axis of rotation and direction of rotation of the tracking sensor.
Furthermore, in some embodiments, the rotation of the display objects can be delayed for a predetermined time period, such as 500 ms. It will be understood that the predetermined time period can be greater than or less than 500 ms. Following the delay, the display objects can move to the new emplacement. In some embodiments, the display objects can lag behind the movement and/or rotate at a rate that is slower than the rotation of the wearer.
Perspective Zoom Mode
In some embodiments, the zoom, magnification, or similar quality of a displayed image can be determined based at least in part on the orientation of an image slice 157 or a virtual medical device 160 associated with the image slice 157, relative to a point-of-view location.
As a non-limiting example, the image slice 157 can be an ultrasound image slice. A user can position the ultrasound transducer 114 parallel to a point-of-view plane (such that the entire ultrasound image slice is visible on the display similar to a non-perspective view of the ultrasound image slice). In such an orientation, the ultrasound image slice 157 can fill a majority of each display 252, 254 (or display 102). However, when the orientation of the ultrasound image slice 157 within the displays 252, 254 changes (non-limiting examples, the user rotates the medical device 114 towards perpendicular to the point-of-view plane or if the user rotates the ultrasound transducer 114 or rotates her head in an orbital view mode as described above), less of the ultrasound image slice 157 may be visible and the content of the ultrasound image slice 157 can be more difficult to view due to foreshortening.
In such a scenario, the system 101 can increase the size of the displayed image slice 157 based at least in part on the detected change in size of the displayed image slice 157 due to the change in orientation. In some embodiments, the system 101 can zoom in such that the width of the image slice 157 in at least one location within the display fills a substantially constant fraction of the width of each display 252, 254 (or display 102). For example, the system 101 can determine that the pixel width of the ultrasound image slice 157 changed from 500 pixels to 300 pixels due to the change in orientation. As such, the system 101 can increase the overall size of the image slice 157 to take up more space on the displays 252, 254 (or display 102). For example, the system 101 can increase the size of the image slice 157 so that its width at a particular point is 500 pixels (or greater) or at least larger than 300 pixels. When increasing the width of the image slice 157, the system 101 can maintain the aspect ratio of the image slice 157 such that the height of the image slice 157 is increased in relation to the increase of the width of the image slice 157. Accordingly, the system 101 can increase the size of the image slice 157 while maintaining its shape (and perspective).
Similarly, the system 101 can use a change in height of the image slice 157 to adjust the size of the image slice 157. For example, the system 101 can enlarge the image slice 157 such that the height of the image slice 157 in at least one location maintains a relatively constant height or relatively constant fraction of the height of the displays 252, 254. Any combination of the height or width of the image slice 157 can be used as desired.
In various embodiments, the aspect ratio of the image slice 157 can cause the height of the image to exceed the vertical or horizontal dimension of the displays 252, 254 when enlarged. Where the perspective zoom setting results in a vertical dimension of image slice 157 exceeding the height of displays 252, 254, the image slice 157 can remain vertically centered within the displays 252, 254, or the displays 252, 254 can remain centered on a selected location within the image slice 157, such as a location of a tumor or other targeted structure. In certain embodiments, the system 101 can increase the size of the image slice 157 based on the size of the displays 252, 254. For example, the system 101 can increase the size of the image slice 157 while maintaining a view of the entire image slice 157 within the displays 252, 254. As a non-limiting example, the system 101 can enlarge the image slice 157 such that at least two points of the image slice 157 are proximal to the edge of the display area, such as within a few pixels of the edge of the display area.
Furthermore, the system 101 can use the image slice 157 in combination with one or more additional display objects to determine the amount of enlargement. For example, the system 101 can use a size of the image slice in combination with the virtual medical device 160 to determine the amount by which they are to be enlarged. In this way, the system 101 can enlarge the image slice 157 while maintaining the display of other display objects. Any one or any combination of the aforementioned embodiments can be used as desired.
With reference to
Multiple Users
In some embodiments, each of the users 402, 404, 406 can have an unobstructed view of the patient 408 and view the 3D scene on the HMDs 250 from their own point of view. In certain embodiments, the view of the patient 408 can be obstructed depending on the location of the users 402, 404, 406 with respect to the patient. As a non-limiting example, if the user 402 sees the front side of a 3D rendering of the ultrasound probe 410 and of a rendering of the ultrasound image corresponding to the ultrasound probe 410 on his HIVID 250A, the user 406 can view the back side of the 3D rendering of the ultrasound probe 410 and of the rendering of the ultrasound image corresponding to the ultrasound probe 410 on his HIVID 250C. Similarly, the user 404 can have an approximate edge-on view of the ultrasound image corresponding to the ultrasound probe 410 on his HMD 250B. Each user having their own view of the 3D scene based on their emplacement in the environment 400 enables interaction between the users in a shared physical and virtual space.
In some scenarios, the patient 408 can also use a HMD 250. For example, in a physical therapy environment, the physical therapist and patient could both wear their own HMD 250, and as the physical therapist uses an ultrasound probe to show the patient a muscle injury, the physical therapist and patient could see the injury from their own point of view.
It will be understood that different users cans also see a different view using different display technologies. For example, one user can use a TV with a view configured for her location in the room, whereas a second user could wear a tracked HIVID 250 that would show her the 3D scene from her own point of view.
Flow Diagrams
At block 502, the system 101 receives first emplacement data associated with a first emplacement sensor and/or a medical device. The first emplacement data can be generated by the first emplacement sensor and/or by a position sensing unit. In some embodiments, the first emplacement sensor can be associated with the medical device. For example, the first emplacement sensor can be associated with and/or attached to an ultrasound transducer, needle, etc., as described above.
At block 504, the system 101 determines an emplacement of a medical image based at least in part on received first emplacement data and an offset. The medical image can be an intra-operative and/or real-time medical image, such as a live ultrasound or intra-operative CT scan, or can be a pre-operative image, such as a pre-operative CT or MRI scan image. A real-time medical image (or real-time medical imaging stream) can refer to a medical image (or real-time medical imaging stream) received in real-time. The medical image received in real-time can correspond to a live image, such as a live ultrasound image generated by an ultrasound or other image, such as a pre-operative or intra-operative CT image or MRI image that is communicated in real-time.
In some embodiments, the system 101 can use the first emplacement data and one or more characteristics of the first emplacement sensor or associated medical device (or a corresponding virtual medical device) to determine the emplacement of the medical image. For example, the characteristics may indicate an emplacement of the medical image relative to the first emplacement sensor or associated medical device (or virtual medical imaging device).
Using this information, the system 101 can determine the emplacement of the medical image relative to the first emplacement sensor and/or associated medical device (or virtual medical imaging device). For example, the system 101 can use a known relationship between the first emplacement data and the emplacement of the medical image (non-limiting example: the medical image begins 2 cm. away from the of the first emplacement data location in a particular direction and ends 5 cm. away) and/or use a known relationship between the emplacement of the first emplacement sensor and/or associated medical device (or virtual medical imaging device) and the emplacement of the medical image (non-limiting examples: the medical image begins 4 cm. from the tip of the medical device (or virtual medical imaging device) and ends at the tip of the medical device (or virtual medical imaging device), or the medical image extends 2 cm. in either direction from the ends of the first emplacement sensor).
In addition, in certain embodiments, the system 101 can determine the emplacement of the medical image in one or more coordinate systems and/or by mapping the first emplacement data, from one coordinate system to a second coordinate system. For example, the first emplacement data may be received with respect to a first coordinate system, such as a position sensing coordinate system, and then mapped to a second coordinate system, such as a 3D scene coordinate system and/or a screen coordinate system. The emplacement of the medical image can be determined with respect to one or more of the coordinate systems. For example, the emplacement of the medical image can be determined after the first emplacement data has been mapped to the second coordinate system, such as the 3D scene coordinate system and/or the screen coordinate system, or the emplacement of the medical image can be determined for the first coordinate system, such as the position sensing coordinate system, and then mapped to the 3D scene coordinate system and/or the screen coordinate system.
In certain embodiments, the system 101 can also use an offset to determine the emplacement of the medical image for viewing. For example, the system 101 can determine an initial emplacement of the medical image in the 3D scene coordinate system and/or the screen coordinate system, and then apply an offset to the initial emplacement and/or the system 101 can determine an initial emplacement of the medical image in the position sensing coordinate system and apply an offset to the initial emplacement prior to mapping the emplacement of the medical image in the position sensing coordinate system to the 3D scene coordinate system and/or the screen coordinate system.
The offset can be made in one, or a combination of, coordinate systems, and/or with respect to one, or a combination of, axes. In certain embodiments, the offset can be made along a y-axis (up/down) of the position sensing coordinate system, the 3D scene coordinate system and/or the screen coordinate system. For example, the system 101 can adjust the y-coordinate (up/down coordinate) of the determined emplacement of the medical image (or the first emplacement sensor) in the position sensing coordinate system by the offset amount. When mapped to the 3D scene coordinate system and/or the screen coordinate system, the system 101 can use the adjusted emplacement. As yet another example, the system 101 can adjust the y-coordinate (up/down coordinate) of the determined emplacement of the medical image (or the first emplacement sensor) in the 3D scene coordinate system and/or the screen coordinate system by the offset amount. Any combination of the above-referenced examples can be used as desired. Furthermore, it will be understood that the offset can be made in any one or any combinations of the coordinate systems and with reference to any one or any combination of the axes. For example, the adjustment can be made along any one or any combination of the x-axis, y-axis, or z-axis.
Furthermore, the offset can be a predetermined offset and/or a dynamic offset. In some embodiments, a predetermined offset can be used. For example, the system 101 can use a static offset based on an average height of males and/or females or average distance between elbows and hands, the height of the user, a distance between the user's elbow and eyes, expected location of a user with respect to the imaged volume, etc. In certain embodiments, the system 101 can use a dynamic offset, such as a determined emplacement of the HMD 250 relative to one or more emplacement sensors, position sensing region, and/or position sensing unit coordinate system. For example, the system 101 can determine the emplacement of the HIVID 250 relative to a medical device or imaged area and adjust the offset such that the medical image is always in view on the displays of the HIVID 250. With continued reference to the example, if the wearer crouches down or turns to the side, the system 101 can determine the change in relative emplacement between the HIVID 250 and the medical device or imaged area and adjust the offset such that the medical image remains in view in substantially the same emplacement.
In addition, it will be understood that the offset described herein with reference to the medical image can be applied to any one or any combination of the objects to be displayed and/or to all contents of the virtual 3D scene. In some embodiments, the offset can be applied to some objects to be displayed but not others.
At block 506, the system 101 can cause a display to display a view of a virtual 3D scene including a perspective rendering of the medical image based at least in part on the determined emplacement of the medical image. As described above, the perspective view or rendering the medical image can be determined and displayed based at least in part on a point-of-view location. The point-of-view location can be a fixed point-of-view location or a dynamic point-of-view location. For example, the point-of-view location can be with respect to a set location in front of the display and/or can be based on a tracked location of the display, the HIVID, or the user. In some embodiments, the point-of-view location is determined based at least in part on the relative emplacement of the HIVID or user with respect to the position sensing region or imaged volume, or the emplacement of the HIVID within a position sensing coordinate system. In embodiments, in which the point-of-view location is based on a tracked location, the system 101 can enable the user to view different perspective views of the virtual 3D scene based on the changing emplacement of the tracked object (HIVID, user) relative to the medical devices 112, 114 or the position sensing region.
It will be understood that the various blocks described herein can be implemented in a variety of orders, and that the system 101 can implement one or more of the blocks concurrently and/or change the order, as desired. For example, the system 101 can concurrently receive the emplacement data from different sources, concurrently receive the medical image, or receive the data in any order. Similarly, the system 101 can concurrently determine the emplacement of the medical image and/or one or more virtual medical devices, etc.
Furthermore, it will be understood that fewer, more, or different blocks can be used as part of the routine 500. For example, the routine 500 can include blocks for receiving emplacement data associated with additional emplacement sensors or medical devices, determining emplacements of one or more medical devices, corresponding virtual medical devices, other display objects, displays, and/or users. In some embodiments, the routine 500 can include determining an emplacement of a medical device associated with the medical image and determining the emplacement of the medical image based at least in part on the determined emplacement of the medical device (or corresponding virtual medical device), and display the virtual medical device concurrently with the medical image. Furthermore, the system 101 can determine and display a variety of image guidance cues, such as trajectory indicators, affected region indicators, as described above.
In certain embodiments, the system 101 can determine multiple emplacements for the medical image. For example, the system 101 can determine the emplacement for the medical image for a right-eye view and a left-eye view of a stereoscopic display, such for the HIVID 250. In this way, each display for the HIVID 250 can display the medical image from a slightly different perspective corresponding to a right-eye view and a left-eye view, etc.
In some embodiments, the routine 500 can further include any one or any combination of blocks 508, 510, and/or 512. At block 508, the system 101 can receive second emplacement data associated with a second emplacement sensor and/or a second medical device. The second emplacement data can be generated by the second emplacement sensor and/or by the position sensing unit. In some embodiments, the second emplacement sensor can be associated with the second medical device. For example, the second emplacement sensor can be associated with and/or attached to an ultrasound transducer, needle, etc.
At block 510, the system 101 can determine an emplacement of a virtual medical device based at least in part on the received second emplacement data and an offset. The system 101 can determine the emplacement for the virtual medical device similar to the manner in which the system 101 determines the emplacement of the medical image as described above with reference to block 504. In some embodiments, the offset for the virtual medical device can be the same as the offset for the medical image. In certain embodiments, the offset for the virtual medical device can be different from the offset for the medical image.
At block 512, the system 101 can include the medical image in the virtual 3D scene and cause the stereoscopic display to concurrently display a perspective rendering of the virtual medical device based at least in part on the determined emplacement of the virtual medical device, similar to the display of the medical described above with reference to block 506. In some embodiments, the display of the virtual medical device can be based at least in part on dimensions of a corresponding real medical device (non-limiting examples: size, shape, or other appearance).
At block 602, the system 101 receives emplacement data associated with a first emplacement sensor or first medical device with respect to a first coordinate system. At block 604, the system 101 receives emplacement data associated with a second emplacement sensor or second medical device with respect to the first coordinate system. The first emplacement data and second emplacement data can be generated by the first emplacement sensor and second emplacement sensor, respectively, and or by a position sensing unit tracking the first emplacement sensor and the second emplacement sensor. In some embodiments, the first emplacement sensor is associated with the first medical device and the second emplacement sensor is associated with the second medical device. For example the emplacement sensors can be attached to the respective medical device and/or embedded within the respective medical device, etc. The first coordinate system can correspond to a coordinate system associated with the position sensing unit that is tracking the first and second emplacement sensors.
At block 606, the system 101 can receive third emplacement data associated with a third emplacement sensor or third object with respect to a second coordinate system. The third emplacement sensor can be associated with a user. For example, the third emplacement sensor can be an emplacement sensor associated with an HIVID or other device attached to the user. The third emplacement data can be generated by the third emplacement sensor and/or by a position sensing unit tracking the third emplacement sensor. In some embodiments, the second coordinate system can be different from the first coordinate system, such as when one position sensing unit is tracking the first and second emplacement sensors and a different position sensing unit is tracking the third emplacement sensor. For example, in some embodiments, a magnetic position sensing unit can track the first and second emplacement sensors and an optical position sensing unit can track the third emplacement sensor. In certain embodiments, such as when the same position sensing unit is tracking the first, second, and third emplacement sensors, the first and second coordinate system can be the same coordinate system. As described previously, in embodiments in which the first and second coordinate systems are different, the system 101 can map coordinates from one coordinate system to the other coordinate system and vice versa.
At block 608, the system 101 can determine an emplacement of a first virtual medical device with respect to a third coordinate system based at least in part on the received first emplacement data, an offset, and the third emplacement data. In some embodiments, the third coordinate system can be a coordinate system associated with a 3D stereoscopic display.
In some embodiments, the system 101 can use the first emplacement data and/or characteristics of the first emplacement sensor relative to a medical device to determine the emplacement of the virtual medical device. For example, the characteristics may indicate an emplacement of the medical device relative to the first emplacement sensor. Using this information, the system 101 can determine the emplacement of the virtual medical device corresponding to the medical relative to the first emplacement sensor.
Furthermore, in certain embodiments, the system 101 can determine the emplacement of the virtual medical device in the third coordinate system by mapping the first emplacement data from the first coordinate system to the third coordinate system. For example, the first emplacement data can be received with respect to a position sensing coordinate system and then mapped to a 3D scene coordinate system and/or a screen coordinate system.
Using the mapping of the first emplacement data from the first coordinate system to the third coordinate system, the system 101 can determine the emplacement of the virtual medical device. In some embodiments, the system 101 can map the first emplacement data to the third coordinate system and then determine the emplacement of the virtual medical device and/or determine the emplacement of a medical device corresponding to the virtual medical device in the first coordinate system and then map the emplacement of the medical device to the third coordinate system. For example, the system 101 can determine the emplacement of a needle in a position sensing coordinate system (the first coordinate system for this example) based at least in part on the first emplacement data and then map the determined emplacement of the needle to a 3D scene coordinate system and/or a screen coordinate system (the third coordinate system for this example). The emplacement of the needle mapped to the 3D scene coordinate system and/or the screen coordinate system can correspond to the emplacement of the virtual needle in the 3D scene coordinate system and/or screen coordinate system. With continued reference to the example, the system 101 can map the first emplacement data from the position sensing coordinate system to the 3D scene coordinate system and/or screen coordinate system and then based on dimensions of the needle, determine the emplacement of the virtual needle in the 3D scene coordinate system and/or screen coordinate system.
Furthermore, the system 101 can use the third emplacement data to determine the emplacement of the virtual medical device in the third coordinate system. In some embodiments, the third emplacement data can be used to determine the point-of-view location for the user, or the perspective from which the virtual medical device (or contents of the virtual 3D scene) is to be displayed to the user. In this way, as the user moves from side to side, the view of the virtual medical device (or contents of the virtual 3D scene) can change, similar to the way in which the view of an object changes as a person walks around the object.
At block 610, the system 101 can determine an emplacement of a second virtual medical device with respect to the third coordinate system based at least in part on the received second emplacement data, the offset, and the third emplacement data. Similar to the determination of the first virtual medical device as described in greater detail above with reference to block 608, the system 101 can determine the emplacement for the second virtual medical device with respect to the third coordinate system.
At block 612, the system 101 can receive a real-time medical image stream associated with the second virtual medical device. For example, the medical image stream can be a stream of ultrasound images obtained from an ultrasound transducer connected to the second emplacement sensor and/or can be a stream of CT images registered with the patient and received based at least in part on the emplacement of a medical device relative to the patient.
At block 614, the system 101 can determine an emplacement of the real-time medical image stream with respect to the third coordinate system based at least in part on the received second emplacement data, the offset, and the third emplacement data. As described in greater detail above with reference to block 504 of
At block 616, the system 101 can cause a display to display a rendered view of a virtual 3D scene including the first virtual medical device, the second virtual medical device, and the real-time medical image stream, as described in greater detail above. In certain embodiments, the contents of the virtual 3D scene can be displayed concurrently. In some embodiments, the system 101 generates two views of the virtual 3D scene for different perspectives for display on the display. One view can be a right-eye view and the other can be a left-eye view.
In some embodiments, the system can display the virtual 3D scene using the third coordinate system. For example, the third coordinate system can refer to a display coordinate system. In certain embodiments, the system can map the content of the virtual 3D scene from a third coordinate system to fourth and fifth coordinate systems before displaying. For example, the third coordinate system can refer a 3D scene coordinate system and the fourth and fifth coordinate systems can refer to left-eye, right-eye stereoscopic display coordinate systems.
It will be understood that the various blocks described herein can be implemented in a variety of orders. The system 101 can implement one or more of the blocks concurrently and/or change the order, as desired. For example, the system 101 can concurrently receive the first, second, and/or third emplacement data, concurrently receive additional emplacement data, concurrently receive the medical image stream, or receive the data in any order. Similarly, the system 101 can concurrently determine the emplacement of the virtual medical devices and/or medical image stream as desired.
Furthermore, it will be understood that fewer, more, or different blocks can be used as part of the routine 600. For example, the routine 600 can include blocks for receiving emplacement data associated with additional emplacement sensors, blocks for determining emplacements of virtual objects associated with the additional emplacement sensors in any of various coordinate systems, and blocks for causing additional virtual objects to be displayed. Furthermore, the system 101 can determine the emplacement for, and cause the display to display, a variety of image guidance cues, such as trajectory indicators, affected region indicators, as described above.
In some embodiments, the system 101 can determine the emplacement of the various virtual medical devices, and medical image stream in additional coordinate systems. For example, the system 101 can determine the emplacement of display objects for a stereoscopic view, including a left-eye view and a right-eye view, and cause multiple one or more displays to display the stereoscopic views.
Although described herein as determining emplacement of medical devices and virtual medical device, and displaying virtual 3D scenes including virtual medical devices and other image guidance cues for medical device guidance, it will be understood that the disclosure herein is not limited to medical device guidance, but can be used in a variety of applications. For example, the HMD with displays that include an opaque portion can be used in other settings or environments where it is desirable to see the environment around the opaque displays. Similarly, displaying a virtual 3D scene using an offset can be used in applications in which a user desires to see an object in real life while concurrently viewing a virtual rendering of the object or cues relevant to the object.
Example Embodiments
Various example embodiments of the disclosure can be described in view of the following clauses:
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.
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof means any connection or coupling, either direct or indirect, between two or more elements; the coupling or connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or” in reference to a list of two or more items, covers all of the following interpretations of the word: any one of the items in the list, all of the items in the list, and any combination of the items in the list. Likewise the term “and/or” in reference to a list of two or more items, covers all of the following interpretations of the word: any one of the items in the list, all of the items in the list, and any combination of the items in the list.
Depending on the embodiment, certain operations, acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (non-limiting example: not all are necessary for the practice of the algorithms). Moreover, in certain embodiments, operations, acts, functions, or events can be performed concurrently, non-limiting examples: through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.
The various illustrative logical blocks, modules, routines, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or as a combination of electronic hardware and executable software. To clearly illustrate this interchangeability, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, or as software that runs on hardware, depends upon the particular application and design constraints imposed on the overall system 101. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.
Moreover, the various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by a machine, such as a processor device, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A processor device can be a microprocessor, but in the alternative, the processor device can be a controller, microcontroller, or combinations of the same, or the like. A processor device can include electrical circuitry configured to process computer-executable instructions. In another embodiment, a processor device includes an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A processor device can also be implemented as a combination of computing devices, non-limiting examples: a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Although described herein primarily with respect to digital technology, a processor device may also include primarily analog components. For example, some or all of the signal processing algorithms described herein may be implemented in analog circuitry or mixed analog and digital circuitry. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.
The elements of a method, process, routine, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor device, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of a non-transitory computer-readable storage medium. An exemplary storage medium can be coupled to the processor device such that the processor device can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor device. The processor device and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor device and the storage medium can reside as discrete components in a user terminal.
Further, the processing of the various components of the illustrated systems can be distributed across multiple machines, networks, and other computing resources. In addition, two or more components of a system can be combined into fewer components. Various components of the illustrated systems can be implemented in one or more virtual machines, rather than in dedicated computer hardware systems and/or computing devices.
Virtualization technologies allow a single physical computing device to host one or more instances of a virtual machine, which virtual machine instance appears to a user as an independent computing device. With virtualization, the host computing device can create, maintain, delete, or otherwise manage virtual machines instances in a dynamic manner. In turn, users can request computing resources, including single computing devices or a configuration of networked computing devices, and be provided with virtual machine instances that provide the requested computing resources.
An instance of a virtual machine may be configured to provide specific functionality. For example, a virtual machine instance may be associated with different combinations of software applications and operating systems or operating system configurations to enable a virtual machine to provide different desired functionalities, or to provide similar functionalities more efficiently.
Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the invention can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further implementations of the invention.
These and other changes can be made to the invention in light of the above Detailed Description. While the above description describes certain examples of the invention, and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the invention disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the invention with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the invention encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the invention under the claims.
To reduce the number of claims, certain aspects of the invention are presented below in certain claim forms, but the applicant contemplates the various aspects of the invention in any number of claim forms. For example, while only one aspect of the invention may be recited as a means-plus-function claim under 35 U.S.C sec. 112(f) (AIA), other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. Any claims intended to be treated under 35 U.S.C. §112(f) will begin with the words “means for”, but use of the term “for” in any other context is not intended to invoke treatment under 35 U.S.C. §112(f). Accordingly, the applicant reserves the right to pursue additional claims after filing this application, in either this application or in a continuing application.
Disjunctive language such as the phrase “at least one of X, Y, or Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (non-limiting examples: X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.
Unless otherwise explicitly stated, articles such a “a” or “an” should generally be interpreted to include one or more described items. Accordingly, phrases such as “a device configured to” are intended to include one or more recited devices. Such one or more recited devices can also be collectively configured to carry out the stated recitations. For example, “a processor configured to carry out recitations A, B and C” can include a first processor configured to carry out recitation A working in conjunction with a second processor configured to carry out recitations B and C.
While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it can be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As can be recognized, certain embodiments described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. The scope of certain embodiments disclosed herein is indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
The previous description of the disclosed implementations is provided to enable a person skilled in the art to make or use the present invention. Various modifications to these implementations will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other implementations without departing from the spirit or scope of the invention. Furthermore, although described above with reference to medical devices and procedures, it will be understood that the embodiments described herein can be applied to other systems in which non-medical objects are tracked and non-medical image streams are received, and virtual representations are displayed on a display and/or systems in which multiple objects are displayed on a display within a virtual space, such as within a virtual 3D space. Thus, the present invention is not intended to be limited to the implementations shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
The present application claims priority benefit to U.S. Provisional Application No. 62/296,440, which is hereby incorporated herein by reference in its entirety. 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 incorporated by reference under 37 CFR 1.57 and made a part of this specification.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3556079 | Omizo | Jan 1971 | A |
| 4058114 | Soldner | Nov 1977 | A |
| RE30397 | King | Sep 1980 | E |
| 4249539 | Vilkomerson et al. | Feb 1981 | A |
| 4294544 | Altschuler et al. | Oct 1981 | A |
| 4390025 | Takemura et al. | Jun 1983 | A |
| 4407294 | Vilkomerson | Oct 1983 | A |
| 4431006 | Trimmer et al. | Feb 1984 | A |
| 4567896 | Barnea et al. | Feb 1986 | A |
| 4583538 | Onik et al. | Apr 1986 | A |
| 4620546 | Aida et al. | Nov 1986 | A |
| 4671292 | Matzuk | Jun 1987 | A |
| 4839836 | Fonsalas | Jun 1989 | A |
| 4862873 | Yajima et al. | Sep 1989 | A |
| 4884219 | Waldren | Nov 1989 | A |
| 4899756 | Sonek | Feb 1990 | A |
| 4911173 | Terwilliger | Mar 1990 | A |
| 4945305 | Blood | Jul 1990 | A |
| 5076279 | Arenson et al. | Dec 1991 | A |
| 5078140 | Kwoh | Jan 1992 | A |
| 5078142 | Siczek et al. | Jan 1992 | A |
| 5095910 | Powers | Mar 1992 | A |
| 5109276 | Nudelman et al. | Apr 1992 | A |
| 5158088 | Nelson et al. | Oct 1992 | A |
| 5161536 | Vilkomerson et al. | Nov 1992 | A |
| 5193120 | Gamache et al. | Mar 1993 | A |
| 5209235 | Brisken et al. | May 1993 | A |
| 5249581 | Horbal et al. | Oct 1993 | A |
| 5251127 | Raab | Oct 1993 | A |
| 5261404 | Mick et al. | Nov 1993 | A |
| 5265610 | Darrow et al. | Nov 1993 | A |
| 5271400 | Dumoulin et al. | Dec 1993 | A |
| 5307153 | Maruyama et al. | Apr 1994 | A |
| 5309913 | Kormos et al. | May 1994 | A |
| 5323002 | Sampsell et al. | Jun 1994 | A |
| 5371543 | Anderson | Dec 1994 | A |
| 5383454 | Bucholz | Jan 1995 | A |
| 5394875 | Lewis et al. | Mar 1995 | A |
| 5411026 | Carol | May 1995 | A |
| 5433198 | Desai | Jul 1995 | A |
| 5433739 | Sluijter | Jul 1995 | A |
| 5443489 | Ben-Haim | Aug 1995 | A |
| 5446798 | Morita et al. | Aug 1995 | A |
| 5447154 | Cinquin et al. | Sep 1995 | A |
| 5452024 | Sampsell | Sep 1995 | A |
| 5457493 | Leddy et al. | Oct 1995 | A |
| 5474073 | Schwartz et al. | Dec 1995 | A |
| 5476096 | Olstad et al. | Dec 1995 | A |
| 5483961 | Kelly et al. | Jan 1996 | A |
| 5488431 | Gove et al. | Jan 1996 | A |
| 5489952 | Gove et al. | Feb 1996 | A |
| 5491510 | Gove | Feb 1996 | A |
| 5494039 | Onik et al. | Feb 1996 | A |
| 5503152 | Oakley et al. | Apr 1996 | A |
| 5505204 | Picot et al. | Apr 1996 | A |
| 5515856 | Olstad et al. | May 1996 | A |
| 5517990 | Kalfas et al. | May 1996 | A |
| 5526051 | Gove et al. | Jun 1996 | A |
| 5526812 | Dumoulin et al. | Jun 1996 | A |
| 5529070 | Augustine et al. | Jun 1996 | A |
| 5531227 | Schneider | Jul 1996 | A |
| 5532997 | Pauli | Jul 1996 | A |
| 5541723 | Tanaka | Jul 1996 | A |
| 5558091 | Acker et al. | Sep 1996 | A |
| 5568811 | Olstad | Oct 1996 | A |
| 5570135 | Gove et al. | Oct 1996 | A |
| 5579026 | Tabata | Nov 1996 | A |
| 5581271 | Kraemer | Dec 1996 | A |
| 5588948 | Takahashi et al. | Dec 1996 | A |
| 5608468 | Gove et al. | Mar 1997 | A |
| 5608849 | King, Jr. | Mar 1997 | A |
| 5611345 | Hibbeln | Mar 1997 | A |
| 5611353 | Dance et al. | Mar 1997 | A |
| 5612753 | Poradish et al. | Mar 1997 | A |
| 5625408 | Matsugu et al. | Apr 1997 | A |
| 5628327 | Unger et al. | May 1997 | A |
| 5629794 | Magel et al. | May 1997 | A |
| 5630027 | Venkateswar et al. | May 1997 | A |
| 5647361 | Damadian | Jul 1997 | A |
| 5647373 | Paltieli et al. | Jul 1997 | A |
| 5660185 | Shmulewitz et al. | Aug 1997 | A |
| 5662111 | Cosman | Sep 1997 | A |
| 5699444 | Palm | Dec 1997 | A |
| 5701898 | Adam et al. | Dec 1997 | A |
| 5701900 | Shehada et al. | Dec 1997 | A |
| 5726670 | Tabata et al. | Mar 1998 | A |
| 5728044 | Shan | Mar 1998 | A |
| 5758650 | Miller et al. | Jun 1998 | A |
| 5766135 | Terwilliger | Jun 1998 | A |
| 5784098 | Shoji et al. | Jul 1998 | A |
| 5792147 | Evans et al. | Aug 1998 | A |
| 5793701 | Wright et al. | Aug 1998 | A |
| 5797849 | Vesely et al. | Aug 1998 | A |
| 5807395 | Mulier et al. | Sep 1998 | A |
| 5810008 | Dekel et al. | Sep 1998 | A |
| 5817022 | Vesely | Oct 1998 | A |
| 5820554 | Davis et al. | Oct 1998 | A |
| 5820561 | Olstad et al. | Oct 1998 | A |
| 5829439 | Yokosawa et al. | Nov 1998 | A |
| 5829444 | Ferre et al. | Nov 1998 | A |
| 5851183 | Budiolz | Dec 1998 | A |
| 5870136 | Fuchs et al. | Feb 1999 | A |
| 5891034 | Bucholz | Apr 1999 | A |
| 5920395 | Schulz | Jul 1999 | A |
| 5961527 | Whitmore, III et al. | Oct 1999 | A |
| 5967980 | Ferre et al. | Oct 1999 | A |
| 5991085 | Rallison et al. | Nov 1999 | A |
| 6016439 | Acker | Jan 2000 | A |
| 6019724 | Gronningsaeter et al. | Feb 2000 | A |
| 6048312 | Ishrak et al. | Apr 2000 | A |
| 6064749 | Hirota et al. | May 2000 | A |
| 6091546 | Spitzer | Jul 2000 | A |
| 6095982 | Richards-Kortum et al. | Aug 2000 | A |
| 6099471 | Torp et al. | Aug 2000 | A |
| 6108130 | Raj | Aug 2000 | A |
| 6122538 | Sliwa, Jr. et al. | Sep 2000 | A |
| 6122541 | Cosman et al. | Sep 2000 | A |
| 6160666 | Rallison et al. | Dec 2000 | A |
| 6167296 | Shahidi | Dec 2000 | A |
| 6181371 | Maguire, Jr. | Jan 2001 | B1 |
| RE37088 | Olstad et al. | Mar 2001 | E |
| 6216029 | Paltieli | Apr 2001 | B1 |
| 6241725 | Cosman | Jun 2001 | B1 |
| 6245017 | Hashimoto et al. | Jun 2001 | B1 |
| 6246898 | Vesely et al. | Jun 2001 | B1 |
| 6248101 | Whitmore, III et al. | Jun 2001 | B1 |
| 6261234 | Lin | Jul 2001 | B1 |
| 6341016 | Malione | Jan 2002 | B1 |
| 6348058 | Melkent et al. | Feb 2002 | B1 |
| 6350238 | Olstad et al. | Feb 2002 | B1 |
| 6352507 | Torp et al. | Mar 2002 | B1 |
| 6379302 | Kessman et al. | Apr 2002 | B1 |
| 6385475 | Cinquin et al. | May 2002 | B1 |
| 6442417 | Shahidi et al. | Aug 2002 | B1 |
| 6447450 | Olstad | Sep 2002 | B1 |
| 6456868 | Saito et al. | Sep 2002 | B2 |
| 6470207 | Simon et al. | Oct 2002 | B1 |
| 6471366 | Hughson et al. | Oct 2002 | B1 |
| 6477400 | Barrick | Nov 2002 | B1 |
| 6478793 | Cosman et al. | Nov 2002 | B1 |
| 6503195 | Keller et al. | Jan 2003 | B1 |
| 6511418 | Shahidi et al. | Jan 2003 | B2 |
| 6517485 | Torp et al. | Feb 2003 | B2 |
| 6518939 | Kikuchi | Feb 2003 | B1 |
| 6527443 | Vilsmeier | Mar 2003 | B1 |
| 6529758 | Shahidi | Mar 2003 | B2 |
| 6537217 | Bjærum et al. | Mar 2003 | B1 |
| 6545706 | Edwards et al. | Apr 2003 | B1 |
| 6546279 | Bova et al. | Apr 2003 | B1 |
| 6551325 | Neubauer et al. | Apr 2003 | B2 |
| 6570566 | Yoshigahara | May 2003 | B1 |
| 6575969 | Rittman, III et al. | Jun 2003 | B1 |
| 6579240 | Bjaerum et al. | Jun 2003 | B2 |
| 6587711 | Alfano et al. | Jul 2003 | B1 |
| 6591130 | Shahidi | Jul 2003 | B2 |
| 6592522 | Bjaerum et al. | Jul 2003 | B2 |
| 6594517 | Nevo | Jul 2003 | B1 |
| 6597818 | Kumar et al. | Jul 2003 | B2 |
| 6604404 | Paltieli et al. | Aug 2003 | B2 |
| 6616610 | Steininger et al. | Sep 2003 | B2 |
| 6626832 | Paltieli et al. | Sep 2003 | B1 |
| 6652462 | Bjaerum et al. | Nov 2003 | B2 |
| 6669635 | Kessman et al. | Dec 2003 | B2 |
| 6676599 | Torp et al. | Jan 2004 | B2 |
| 6689067 | Sauer et al. | Feb 2004 | B2 |
| 6695786 | Wang et al. | Feb 2004 | B2 |
| 6711429 | Gilboa et al. | Mar 2004 | B1 |
| 6725082 | Sati et al. | Apr 2004 | B2 |
| 6733458 | Steins et al. | May 2004 | B1 |
| 6764449 | Lee et al. | Jul 2004 | B2 |
| 6766184 | Utzinger et al. | Jul 2004 | B2 |
| 6768496 | Bieger et al. | Jul 2004 | B2 |
| 6775404 | Pagoulatos et al. | Aug 2004 | B1 |
| 6782287 | Grzeszczuk et al. | Aug 2004 | B2 |
| 6783524 | Anderson et al. | Aug 2004 | B2 |
| 6827723 | Carson | Dec 2004 | B2 |
| 6863655 | Bjaerum et al. | Mar 2005 | B2 |
| 6873867 | Vilsmeier | Mar 2005 | B2 |
| 6875179 | Ferguson et al. | Apr 2005 | B2 |
| 6881214 | Cosman et al. | Apr 2005 | B2 |
| 6895268 | Rahn et al. | May 2005 | B1 |
| 6915150 | Cinquin et al. | Jul 2005 | B2 |
| 6917827 | Kienzle, III | Jul 2005 | B2 |
| 6923817 | Carson et al. | Aug 2005 | B2 |
| 6936048 | Hurst | Aug 2005 | B2 |
| 6947783 | Immerz | Sep 2005 | B2 |
| 6968224 | Kessman et al. | Nov 2005 | B2 |
| 6978167 | Dekel et al. | Dec 2005 | B2 |
| 7008373 | Stoianovici et al. | Mar 2006 | B2 |
| 7033360 | Cinquin et al. | Apr 2006 | B2 |
| 7072707 | Galloway, Jr. et al. | Jul 2006 | B2 |
| 7077807 | Torp et al. | Jul 2006 | B2 |
| 7093012 | Olstad et al. | Aug 2006 | B2 |
| 7110013 | Ebersole et al. | Sep 2006 | B2 |
| 7171255 | Holupka et al. | Jan 2007 | B2 |
| 7209776 | Leitner | Apr 2007 | B2 |
| 7245746 | Bjaerum et al. | Jul 2007 | B2 |
| 7248232 | Yamazaki et al. | Jul 2007 | B1 |
| 7261694 | Torp et al. | Aug 2007 | B2 |
| 7313430 | Urquhart et al. | Dec 2007 | B2 |
| 7331932 | Leitner | Feb 2008 | B2 |
| 7351205 | Szczech et al. | Apr 2008 | B2 |
| 7379769 | Piron et al. | May 2008 | B2 |
| 7385708 | Ackerman et al. | Jun 2008 | B2 |
| 7392076 | Moctezuma de la Barrera | Jun 2008 | B2 |
| 7398116 | Edwards | Jul 2008 | B2 |
| 7466303 | Yi et al. | Dec 2008 | B2 |
| 7480533 | Cosman et al. | Jan 2009 | B2 |
| 7505809 | Strommer et al. | Mar 2009 | B2 |
| 7588541 | Floyd et al. | Sep 2009 | B2 |
| 7652259 | Kimchy et al. | Jan 2010 | B2 |
| 7662128 | Salcudean et al. | Feb 2010 | B2 |
| 7678052 | Torp et al. | Mar 2010 | B2 |
| 7728868 | Razzaque et al. | Jun 2010 | B2 |
| 7797032 | Martinelli et al. | Sep 2010 | B2 |
| 7798965 | Torp et al. | Sep 2010 | B2 |
| 7833168 | Taylor et al. | Nov 2010 | B2 |
| 7833221 | Voegele et al. | Nov 2010 | B2 |
| 7846103 | Cannon, Jr. et al. | Dec 2010 | B2 |
| 7876942 | Gilboa | Jan 2011 | B2 |
| 7889905 | Higgins et al. | Feb 2011 | B2 |
| 7912849 | Ohrn et al. | Mar 2011 | B2 |
| 7920909 | Lyon et al. | Apr 2011 | B2 |
| 7962193 | Edwards et al. | Jun 2011 | B2 |
| 7976469 | Bonde et al. | Jul 2011 | B2 |
| 8023712 | Ikuma et al. | Sep 2011 | B2 |
| 8038631 | Sanghvi et al. | Oct 2011 | B1 |
| 8041413 | Barbagli et al. | Oct 2011 | B2 |
| 8050736 | Piron et al. | Nov 2011 | B2 |
| 8052636 | Moll et al. | Nov 2011 | B2 |
| 8066644 | Sarkar et al. | Nov 2011 | B2 |
| 8073528 | Zhao et al. | Dec 2011 | B2 |
| 8086298 | Whitmore, III et al. | Dec 2011 | B2 |
| 8135669 | Olstad et al. | Mar 2012 | B2 |
| 8137281 | Huang et al. | Mar 2012 | B2 |
| 8147408 | Bunce et al. | Apr 2012 | B2 |
| 8152724 | Ridley et al. | Apr 2012 | B2 |
| 8167805 | Emery et al. | May 2012 | B2 |
| 8216149 | Oonuki et al. | Jul 2012 | B2 |
| 8221322 | Wang et al. | Jul 2012 | B2 |
| 8228028 | Schneider | Jul 2012 | B2 |
| 8257264 | Park et al. | Sep 2012 | B2 |
| 8296797 | Olstad et al. | Oct 2012 | B2 |
| 8340379 | Razzaque et al. | Dec 2012 | B2 |
| 8350902 | Razzaque et al. | Jan 2013 | B2 |
| 8482606 | Razzaque et al. | Jul 2013 | B2 |
| 8554307 | Razzaque et al. | Oct 2013 | B2 |
| 8585598 | Razzaque et al. | Nov 2013 | B2 |
| 8641621 | Razzaque et al. | Feb 2014 | B2 |
| 8670816 | Green et al. | Mar 2014 | B2 |
| 8690776 | Razzaque et al. | Apr 2014 | B2 |
| 8831310 | Razzaque et al. | Sep 2014 | B2 |
| 9107698 | Razzaque et al. | Aug 2015 | B2 |
| 9282947 | Razzaque et al. | Mar 2016 | B2 |
| 9364294 | Razzaque et al. | Jun 2016 | B2 |
| 9398936 | Razzaque et al. | Jul 2016 | B2 |
| 20010007919 | Shahidi | Jul 2001 | A1 |
| 20010016804 | Cunningham et al. | Aug 2001 | A1 |
| 20010041838 | Holupka et al. | Nov 2001 | A1 |
| 20010045979 | Matsumoto et al. | Nov 2001 | A1 |
| 20020010384 | Shahidi et al. | Jan 2002 | A1 |
| 20020032772 | Olstad et al. | Mar 2002 | A1 |
| 20020049375 | Strommer et al. | Apr 2002 | A1 |
| 20020077540 | Kienzle, III | Jun 2002 | A1 |
| 20020077543 | Grzeszczuk et al. | Jun 2002 | A1 |
| 20020105484 | Navab et al. | Aug 2002 | A1 |
| 20020135673 | Favalora et al. | Sep 2002 | A1 |
| 20020138008 | Tsujita et al. | Sep 2002 | A1 |
| 20020140814 | Cohen-Solal et al. | Oct 2002 | A1 |
| 20020156375 | Kessman et al. | Oct 2002 | A1 |
| 20020198451 | Carson | Dec 2002 | A1 |
| 20030040743 | Cosman et al. | Feb 2003 | A1 |
| 20030073901 | Simon et al. | Apr 2003 | A1 |
| 20030135119 | Lee et al. | Jul 2003 | A1 |
| 20030163142 | Paltieli et al. | Aug 2003 | A1 |
| 20030164172 | Chumas et al. | Sep 2003 | A1 |
| 20030231789 | Willis et al. | Dec 2003 | A1 |
| 20040034313 | Leitner | Feb 2004 | A1 |
| 20040078036 | Keidar | Apr 2004 | A1 |
| 20040095507 | Bishop et al. | May 2004 | A1 |
| 20040116810 | Olstad | Jun 2004 | A1 |
| 20040147920 | Keidar | Jul 2004 | A1 |
| 20040152970 | Hunter et al. | Aug 2004 | A1 |
| 20040181144 | Cinquin et al. | Sep 2004 | A1 |
| 20040215071 | Frank et al. | Oct 2004 | A1 |
| 20040238732 | State et al. | Dec 2004 | A1 |
| 20040243146 | Chesbrough et al. | Dec 2004 | A1 |
| 20040243148 | Wasielewski | Dec 2004 | A1 |
| 20040249281 | Olstad | Dec 2004 | A1 |
| 20040249282 | Olstad | Dec 2004 | A1 |
| 20040254454 | Kockro | Dec 2004 | A1 |
| 20050010098 | Frigstad et al. | Jan 2005 | A1 |
| 20050085717 | Shahidi | Apr 2005 | A1 |
| 20050085718 | Shahidi | Apr 2005 | A1 |
| 20050090742 | Mine et al. | Apr 2005 | A1 |
| 20050111733 | Fors et al. | May 2005 | A1 |
| 20050159641 | Kanai | Jul 2005 | A1 |
| 20050182316 | Burdette et al. | Aug 2005 | A1 |
| 20050192564 | Cosman et al. | Sep 2005 | A1 |
| 20050219552 | Ackerman et al. | Oct 2005 | A1 |
| 20050222574 | Giordano et al. | Oct 2005 | A1 |
| 20050251148 | Friedrich | Nov 2005 | A1 |
| 20060004275 | Vija et al. | Jan 2006 | A1 |
| 20060020204 | Serra et al. | Jan 2006 | A1 |
| 20060036162 | Shahidi et al. | Feb 2006 | A1 |
| 20060052792 | Boettiger et al. | Mar 2006 | A1 |
| 20060058609 | Olstad | Mar 2006 | A1 |
| 20060058610 | Olstad | Mar 2006 | A1 |
| 20060058674 | Olstad | Mar 2006 | A1 |
| 20060058675 | Olstad | Mar 2006 | A1 |
| 20060100505 | Viswanathan | May 2006 | A1 |
| 20060122495 | Kienzle | Jun 2006 | A1 |
| 20060184040 | Keller et al. | Aug 2006 | A1 |
| 20060193504 | Salgo et al. | Aug 2006 | A1 |
| 20060229594 | Francischelli et al. | Oct 2006 | A1 |
| 20060235290 | Gabriel et al. | Oct 2006 | A1 |
| 20060235538 | Rochetin et al. | Oct 2006 | A1 |
| 20060241450 | Da Silva et al. | Oct 2006 | A1 |
| 20060253030 | Altmann et al. | Nov 2006 | A1 |
| 20060253032 | Altmann et al. | Nov 2006 | A1 |
| 20060271056 | Terrill-Grisoni et al. | Nov 2006 | A1 |
| 20060282023 | Leitner | Dec 2006 | A1 |
| 20060293643 | Wallace et al. | Dec 2006 | A1 |
| 20070002582 | Burwell et al. | Jan 2007 | A1 |
| 20070016035 | Hashimoto | Jan 2007 | A1 |
| 20070032906 | Sutherland et al. | Feb 2007 | A1 |
| 20070073155 | Park et al. | Mar 2007 | A1 |
| 20070073455 | Oyobe et al. | Mar 2007 | A1 |
| 20070078346 | Park et al. | Apr 2007 | A1 |
| 20070167699 | Lathuiliere et al. | Jul 2007 | A1 |
| 20070167701 | Sherman | Jul 2007 | A1 |
| 20070167705 | Chiang et al. | Jul 2007 | A1 |
| 20070167771 | Olstad | Jul 2007 | A1 |
| 20070167801 | Webler et al. | Jul 2007 | A1 |
| 20070225553 | Shahidi | Sep 2007 | A1 |
| 20070239281 | Gotte et al. | Oct 2007 | A1 |
| 20070244488 | Metzger et al. | Oct 2007 | A1 |
| 20070255136 | Kristofferson et al. | Nov 2007 | A1 |
| 20070270718 | Rochetin et al. | Nov 2007 | A1 |
| 20070276234 | Shahidi | Nov 2007 | A1 |
| 20080004481 | Bax et al. | Jan 2008 | A1 |
| 20080004516 | DiSilvestro et al. | Jan 2008 | A1 |
| 20080030578 | Razzaque et al. | Feb 2008 | A1 |
| 20080039723 | Suri et al. | Feb 2008 | A1 |
| 20080051910 | Kammerzell et al. | Feb 2008 | A1 |
| 20080091106 | Kim et al. | Apr 2008 | A1 |
| 20080114235 | Unal et al. | May 2008 | A1 |
| 20080161824 | McMillen | Jul 2008 | A1 |
| 20080200794 | Teichman et al. | Aug 2008 | A1 |
| 20080208031 | Kurpad et al. | Aug 2008 | A1 |
| 20080208081 | Murphy et al. | Aug 2008 | A1 |
| 20080214932 | Mollard et al. | Sep 2008 | A1 |
| 20080232679 | Hahn et al. | Sep 2008 | A1 |
| 20080287794 | Li et al. | Nov 2008 | A1 |
| 20080287805 | Li | Nov 2008 | A1 |
| 20080287837 | Makin et al. | Nov 2008 | A1 |
| 20090024030 | Lachaine et al. | Jan 2009 | A1 |
| 20090118724 | Zvuloni et al. | May 2009 | A1 |
| 20090131783 | Jenkins et al. | May 2009 | A1 |
| 20090137907 | Takimoto et al. | May 2009 | A1 |
| 20090234369 | Bax et al. | Sep 2009 | A1 |
| 20090312629 | Razzaque et al. | Dec 2009 | A1 |
| 20100045783 | State et al. | Feb 2010 | A1 |
| 20100198045 | Razzaque et al. | Aug 2010 | A1 |
| 20100208963 | Kruecker et al. | Aug 2010 | A1 |
| 20100268072 | Hall et al. | Oct 2010 | A1 |
| 20100268085 | Kruecker et al. | Oct 2010 | A1 |
| 20100298705 | Pelissier et al. | Nov 2010 | A1 |
| 20100305448 | Dagonneau et al. | Dec 2010 | A1 |
| 20100312121 | Guan | Dec 2010 | A1 |
| 20100331252 | Hamrick | Dec 2010 | A1 |
| 20110043612 | Keller et al. | Feb 2011 | A1 |
| 20110046483 | Fuchs | Feb 2011 | A1 |
| 20110046486 | Shin et al. | Feb 2011 | A1 |
| 20110057930 | Keller | Mar 2011 | A1 |
| 20110082351 | Razzaque et al. | Apr 2011 | A1 |
| 20110130641 | Razzaque et al. | Jun 2011 | A1 |
| 20110201915 | Gogin et al. | Aug 2011 | A1 |
| 20110201976 | Sanghvi et al. | Aug 2011 | A1 |
| 20110230351 | Fischer et al. | Sep 2011 | A1 |
| 20110237947 | Boctor et al. | Sep 2011 | A1 |
| 20110238043 | Kleven | Sep 2011 | A1 |
| 20110251483 | Razzaque et al. | Oct 2011 | A1 |
| 20110274324 | Clements et al. | Nov 2011 | A1 |
| 20110282188 | Burnside et al. | Nov 2011 | A1 |
| 20110288412 | Deckman et al. | Nov 2011 | A1 |
| 20110295108 | Cox et al. | Dec 2011 | A1 |
| 20110301451 | Rohling | Dec 2011 | A1 |
| 20120035473 | Sanghvi et al. | Feb 2012 | A1 |
| 20120059260 | Robinson | Mar 2012 | A1 |
| 20120071759 | Hagy et al. | Mar 2012 | A1 |
| 20120078094 | Nishina et al. | Mar 2012 | A1 |
| 20120108955 | Razzaque et al. | May 2012 | A1 |
| 20120143029 | Silverstein et al. | Jun 2012 | A1 |
| 20120143055 | Ng et al. | Jun 2012 | A1 |
| 20120165679 | Orome et al. | Jun 2012 | A1 |
| 20120259210 | Harhen et al. | Oct 2012 | A1 |
| 20130030286 | Alouani et al. | Jan 2013 | A1 |
| 20130044930 | Li et al. | Feb 2013 | A1 |
| 20130079770 | Kyle, Jr. et al. | Mar 2013 | A1 |
| 20130132374 | Olstad et al. | May 2013 | A1 |
| 20130151533 | Udupa et al. | Jun 2013 | A1 |
| 20130178745 | Kyle et al. | Jul 2013 | A1 |
| 20130249787 | Morimoto | Sep 2013 | A1 |
| 20140016848 | Razzaque et al. | Jan 2014 | A1 |
| 20140078138 | Martin et al. | Mar 2014 | A1 |
| 20140142426 | Razzaque | May 2014 | A1 |
| 20140180074 | Green | Jun 2014 | A1 |
| 20140275810 | Keller et al. | Sep 2014 | A1 |
| 20140343404 | Razzaque et al. | Nov 2014 | A1 |
| 20160117857 | State et al. | Apr 2016 | A1 |
| 20160166334 | Razzaque | Jun 2016 | A1 |
| 20160166336 | Razzaque | Jun 2016 | A1 |
| 20160196694 | Lindeman | Jul 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 427 358 | May 1991 | EP |
| 1955284 | Aug 2008 | EP |
| S63-290550 | Nov 1988 | JP |
| H07-116164 | May 1995 | JP |
| 2005-058584 | Mar 2005 | JP |
| 2005-323669 | Nov 2005 | JP |
| 2009-517177 | Apr 2009 | JP |
| WO 9605768 | Feb 1996 | WO |
| WO 9715249 | May 1997 | WO |
| WO 9717014 | May 1997 | WO |
| WO 9926534 | Jun 1999 | WO |
| WO 0139683 | Jun 2001 | WO |
| WO 03032837 | Apr 2003 | WO |
| WO 03034705 | Apr 2003 | WO |
| WO 03105289 | Dec 2003 | WO |
| WO 2005010711 | Feb 2005 | WO |
| WO 2007019216 | Feb 2007 | WO |
| WO 2007067323 | Jun 2007 | WO |
| WO 2007067323 | Sep 2007 | WO |
| WO 2008017051 | Feb 2008 | WO |
| WO 2009063423 | May 2009 | WO |
| WO 2009094646 | Jul 2009 | WO |
| WO 2010057315 | May 2010 | WO |
| WO 2010096419 | Aug 2010 | WO |
| WO 2011014687 | Feb 2011 | WO |
| WO 2012169990 | Dec 2012 | WO |
| WO 2013116240 | Aug 2013 | WO |
| Entry |
|---|
| U.S. Appl. No. 11/828,826, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks and any other potentially relevant documents, Jul. 26, 2007, Keller et al. |
| U.S. Appl. No. 15/041,868, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks and any other potentially relevant documents, Feb. 11, 2016, Fuchs et al. |
| U.S. Appl. No. 15/068,323, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks and any other potentially relevant documents, Mar. 11, 2016, Razzaque et al. |
| U.S. Appl. No. 15/182,346, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks and any other potentially relevant documents, Jun. 14, 2016, Razzaque et al. |
| U.S. Appl. No. 15/199,711, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks and any other potentially relevant documents, Jun. 30, 2016, Razzaque. |
| U.S. Appl. No. 15/175,981, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks and any other potentially relevant documents, Jul. 7, 2016, Razzaque et al. |
| “3D Laparoscope Technology,” http://www.inneroptic.com/tech—3DL.htm, copyright 2007 InnerOptic Technology, Inc. printed Sep. 19, 2007, 2 pages. |
| “Cancer Facts & Figures 2004,” www.cancer.org/downloads/STT/CAFF—finalPWSecured.pdf, copyright 2004 American Cancer Society, Inc., printed Sep. 19, 2007, 60 pages. |
| “David Laserscanner <-Latest News <- Institute for Robotics and Process Control <- Te . . . ,” http://www/rob.cs.tu-bs.de/en/news/david, printed Sep. 19, 2007, 1 page. |
| “Laser scanned 3d model Final” video, still image of video attached, http://www.youtube.com/watch?v+DaLglgmoUf8, copyright 2007 YouTube, LLC, printed Sep. 19, 2007, 2 pages. |
| “Olympus Endoscopic Ultrasound System,” www.olympusamerica.com/msg—section/download—brochures/135—b—gfum130.pdf, printed Sep. 20, 2007, 20 pages. |
| “Point Grey Research Inc.—Imaging Products—Triclops SDK Samples,” http://www.ptgrey.com/products/triclopsSDK/samples.asp, copyright 2007 Point Grey Research Inc., printed Sep. 19, 2007, 1 page. |
| “Robbins, Mike—Computer Vision Research—Stereo Depth Perception,” http://www.compumike.com/vision/stereodepth. php, copyright 2007 Michael F. Robbins, printed Sep. 19, 2007, 3 pages. |
| “RUE, Registered Ultrasound-Endoscope,” copyright 2007 InnerOptic Technology, Inc., 2 pages. |
| Advertisement, “Inspeck 3DC 3D Capturor,” Inspeck 3DC 3D Capturor (www.inspeck.com), 1998. |
| Advertisement, “Virtual 3D High Speed Non-Contact Surface Perception,” Virtual 3-D Technologies Corporation (www.virtual3dtech.com)., Dec. 21, 1998. |
| Advertisements, “Virtuoso,” Visual Interface, Inc. (www.visint.com), Dec. 21, 1998. |
| Akka, “Automatic Software Control of Display Parameters for Stereoscopic Graphics Images,” SPIE vol. 1669: Stereoscopic Displays and Applications III, pp. 31-38 (1992). |
| Ali et al., “Near Infrared Spectroscopy and Imaging to Probe Differences in Water Content in Normal and Cancer Human Prostate Tissues,” Technology in Cancer Research & Treatment; Oct. 2004; 3(5):491-497; Adenine Press. |
| Aylward et al., Analysis of the Parameter Space of a Metric for Registering 3D Vascular Images, in W. Niessen and M. Viergever (Eds.): MICCAI 2001, LNCS 2208, pp. 932-939, 2001. |
| Aylward et al., Registration and Analysis of Vascular Images, International Journal of Computer Vision 55(2/3), 123-138, 2003. |
| Aylward, et al., Intra-Operative 3D Ultrasound Augmentation, Proceedings of the IEEE International Symposium on Biomedical Imaging, Washington, Jul. 2002. |
| Azuma et al., “Improving Static and Dynamic Registration in an Optical See-Through HMD,” Paper Presented at SIGGRAPH '94 Annual Conference in Orlando, FL, 17 pages (1994). |
| Azuma, “A Survey of Augmented Reality,” Presence: Teleoperators and Virtual Environments 6, 4:1-48 (Aug. 1997). |
| Badler et al., “Simulating Humans: Computer Graphics, Animation, and Control,” Oxford University Press (1993). |
| Bajura, Michael et al., “Merging Virtual Objects with the Real World: Seeing Ultrasound Imagery within the Patient,” Computer Graphics, Proceedings of SIGGRAPH 1992, vol. 26(2), pp. 203-210, available from www.cs.unc.edu/˜fuchs/publications/MergVirtObjs92.pdf, printed Sep. 20, 2007, 8 pages. |
| Benavides et al., “Multispectral digital colposcopy for in vivo detection of cervical cancer,” Optics Express; May 19, 2003; 11(1 0) Optical Society of America; USA. |
| Beraldin, J.A. et al., “Optimized Position Sensors for Flying-Spot Active Triangulation Systems,” Proceedings of the Fourth International Conference on a 3-D Digital Imaging and Modeling (3DIM), Banff, Alberta, Canada, Oct. 6-10, 2003, pp. 334-341, NRC 47083, copyright 2003 National Research Council of Canada, http:/iit-iti.nrc-cnrc.gc.ca/iit-publications-iti/docs/NRC-47083.pdf, printed Sep. 19, 2007, 9 pages. |
| Billinghurst, M. et al., Research Directions in Handheld AR; Int. J. of Virtual Reality 5(2),51-58 (2006). |
| Blais, F., “Review of 20 Years of Range Sensor Development,” Journal of Electronic Imaging, 13(1): 231-240, Jan. 2004, NRC 46531, copyright 2004 National Research Council of Canada, http://iit-iti.nrc-cnrc.gc.ca/iit-publications-iti/docs/NRC-46531.pdf, printed Sep. 19, 2007, 14 pages. |
| Bouguet, Jean-Yves, “Camera Calibration Toolbox for Matlab,” www.vision.caltech.edu/bouguetj/calib—doc, printed Sep. 20, 2007, 5 pages. |
| Buxton et al.; “Colposcopically directed punch biopsy: a potentially misleading investigation,” British Journal of Obstetrics and Gynecology; Dec. 1991; 98:1273-1276. |
| Caines, Judy S. et al. Stereotaxic Needle Core Biopsy of Breast Lesions Using a Regular Mammographic Table with an Adaptable Stereotaxic Device, American Journal of Roentgenology, vol. 163, No. 2, Aug. 1994, pp. 317-321. Downloaded from www.ajrorline.org on Jul. 10, 2013. |
| Cancer Prevention & Early Detection Facts & Figures 2004; National Center for Tobacco-Free Kids; 2004; American Cancer Society; USA. |
| Cantor et al., “Cost-Effectiveness Analysis of Diagnosis and Management of Cervical Squamous Intraepithelial Lesions,” Diagnostic Strategies for SILs; Feb. 1998; 91(2):270-277. |
| Catalano et al. “Multiphase helical CT findings after percutaneous ablation procedures for hepatocellular carcinoma.” Abdom. Imaging, 25(6),2000, pp. 607-614. |
| Chiriboga et al., “Infrared Spectroscopy of Human Tissue. IV. Detection of Dysplastic and Neoplastic Changes of Human Cervical Tissue Via Infrared Microscopy,” Cellular and Molecular Biology; 1998; 44(1): 219-229. |
| Crawford, David E. et al., “Computer Modeling of Prostate Biopsy: Tumor Size and Location—Not Clinical Significance—Determine Cancer Detection,” Journal of Urology, Apr. 1998, vol. 159(4), pp. 1260-1264, 5 pages. |
| Deering, Michael “High Resolution Virtual Reality.” Proceedings of SIGGRAPH '92, Computer Graphics, 26(2), 1992, pp. 195-202. |
| Depiero et al., “3-D Computer Vision Using Structured Light: Design, Calibration and Implementation Issues,” The University of Tennessee, pp. 1-46, (1996). |
| Dodd, G.D. et al. “Minimally invasive treatment of malignant hepatic tumors: at the threshold of a major breakthrough.” Radiographies 20(1),2000, pp. 9-27. |
| Drascic et al., “Perceptual Issues in Augmented Reality,” SPIE vol. 2653: Stereoscopic Displays and Virtual Reality Systems III, pp. 123-134 (Feb. 1996). |
| Dumoulin, C.L. et al, Real-Time Position Monitoring of Invasive Devices Using Magnetic Resonance, Magnetic Resonance in Medicine, vol. 29, Issue 3, Mar. 1993, pp. 411-415. |
| Fahey et al., “Meta-analysis of Pap Test Accuracy; American Journal of Epidemiology,” 1995 141(7):680-689; The John Hopkins University School of Hygiene and Public Health; USA. |
| Foxlin et al., “An Inertial Head-Orientation Tracker with Automatic Drift Compensation for Use with HMD's,” Proceedings of the 1994 Virtual Reality Software and Technology Conference, Aug. 23-26, 1994, Singapore, pp. 159-173 (1994). |
| Fronheiser et al., Real-Time 3D Color Doppler for Guidance of Vibrating Interventional Devices, IEEE Ultrasonics Symposium, pp. 149-152 (2004). |
| Fuchs, Henry et al. “Augmented Reality Visualization for Laparoscopic Surgery,” Proceedings of Medical Image Computing and Computer-Assisted Intervention (MICCAI) 1998, pp. 934-943, available from www.cs.unc.edu/˜fuchs/publications /AugRealVis—LaparoSurg98.pdf, printed Sep. 20, 2007, 10 pages. |
| Fuchs, et al.: “Optimizing a Head-Tracked Stereo Display System to Guide Hepatic Tumor Ablation,” Departments of Computer Sciences and Radiology, and School of Medicine, University of North Carolina at Chapel Hill; InnerOptic Technology, Inc. 2008. |
| Fuchs, et al.: “Virtual Environments Technology to Aid Needle Biopsies of the Breast,” Health Care in the Information Age, Ch. 6, pp. 60-61, Presented in San Diego, Jan. 17-20, 1996, published by IOS Press and Ohmsha Feb. 1996. |
| Fuhrmann A. et al., Comprehensive calibration and registration procedures for augmented reality; Proc. Eurographics Workshop on Virtual Environments 2001,219-228 (2001). |
| Garrett, William F. et al., “Real-Time Incremental Visualization of Dynamic Ultrasound Volumes Using Parallel BSP Trees, ”Proceedings of IEEE Visualization 1996, pp. 235-240, available from www.cs.unc.edu/˜andrei/pubs/1996—VIS—dualBSP—Mac.pdf, printed Sep. 20, 2007, 7 pages. |
| Georgakoudi et al., “Trimodal spectroscopy for the detection and characterization of cervical precancers in vivo,” American Journal of Obstetrics and Gynecology; Mar. 2002; 186(3):374-382; USA. |
| StereoMirror Technology Webpage, http://www.planar.com/products/flatpanel—monitors/stereoscopic/ (Printed Dec. 29, 2011). |
| Herline et al., Surface Registration for Use in Interactive, Image-Guided Liver Surgery, Computer Aided Surgery 5:11-17 (2000). |
| Holloway, R.; Registration Error Analysis for Augmented Reality; Presence: Teleoperators and Virtual Environments 6(4), 413-432 (1997). |
| Hornung et al., “Quantitative near-infrared spectroscopy of cervical dysplasia in vivo,” Human Reproduction; 1999; 14(11):2908-2916; European Society of Human Reproduction and Embryology. |
| Howard, M.D., et al.: “An Electronic Device for Needle Placement during Sonographically Guided Percutaneous Intervention”, Radiology 2001; 218:905-911. |
| InnerAim Brochure; 3D Visualization Software for Simpler, Safer, more Precise Aiming, Published no earlier than Apr. 1, 2010. |
| InVision System Brochure; A “GPS” for Real-Time 3D Needle Visualization & Guidance, Published no earlier than Mar. 1, 2008. |
| InVision User Manual; Professional Instructions for Use, Published no earlier than Dec. 1, 2008. |
| Jacobs, Marco C. et al., “Managing Latency in Complex Augmented Reality Systems,” ACM SIGGRAPH Proceedings of the Symposium of Interactive 3D Graphics 1997, pp. 49-54, available from www.cs.unc.edu/˜us/Latency//ManagingRelativeLatency.html, printed Sep. 20, 2007, 12 pages. |
| Jolesz, Ferenc A, M.D., et al. MRI-Guided Laser-Induced Interstitial Thermotherapy: Basic Principles, SPIE Institute on Laser-Induced Interstitial Thermotherapy (L1TT), Jun. 22-23, 1995, Berlin, Germany. |
| Kadi, A Majeed, et al., Design and Simulation of an Articulated Surgical Arm for Guiding Sterotactic Neurosurgery, SPIE vol. 1708 Applications of Artificial Intelligence X: Machine Vision and Robotics (1992). Downloaded from: http://proceedings.spiedigitallibrary.org/ on Jul. 11, 2013. |
| Kanbara et al., “A Stereoscopic Video See-through Augmented Reality System Based on Real-time Vision-Based Registration,” Nara Institute of Science and Technology, pp. 1-8 (2000). |
| Kato, Amami, et al., A frameless, armless navigational system for computer-assisted neurosurgery, Journal of Neurosurgery, vol. 74, No. 5, May 1991, pp. 845-849. |
| Keller et al., “What is it in Head Mounted Displays (MDs) that really make them all so terrible?,” pp. 1-8 (1998). |
| Lass, Amir, “Assessment of Ovarian Reserve,” Human Reproduction, 2004, vol. 19(3), pp. 467-469, available from http://humrep.oxfordjournals.orgcgi/reprint/19/3/467, printed Sep. 20, 2007, 3 pages. |
| Lee, et al., “Modeling Real Objects Using Video See-Through Augmented Reality,” Proceedings of the Second International Symposium on Mixed Reality, ISMR 2001, pp. 19-26 (Mar. 14-15, 2001). |
| Lee et al., “Modeling Real Objects Using Video See-Through Augmented Reality,” Presence, 11(2):144-157 (Apr. 2002). |
| Leven et al., DaVinci Canvas: A Telerobotic Surgical System with Integrated, Robot-Assisted, Laparoscopic Ultrasound Capability, in J. Duncan and G. Gerig (Eds.): MICCAI 2005, LNCS 3749, pp. 811-818, 2005. |
| Levy, et al., An Internet-Connected, Patient Specific, Deformable Brain Atlas Integrated into a Surgical Navigation System, Journal of Digital Imaging, vol. 10, No. 3. Suppl. 1 (Aug.), 1997: pp. 231-237. |
| Livingston, Mark A. et al., “Magnetic Tracker Calibration for Improved Augmented Reality Registration,” Presence: Teleoperators and Virtual Environments, 1997, vol. 6(5), pp. 532-546, available from www.cs.unc.edu/˜andrei/pubs/1997—Presence—calibr.pdf, printed Sep. 20, 2007, 14 pages. |
| Matsunaga et al., “The Effect of the Ratio Differenceof Overlapped Areas of Stereoscopic Images on each Eye in a Teleoperalion,” Stereoscopic Displays and Virtual Reality Systems VII, Proceedings of SPIE, 3957:236-243 (2000). |
| Meehan, Michael et al., “Effect of Latency on Presence in Stressful Virtual Environment,” Proceedings of IEEE Virtual Reality 2003, pp. 141-148, available from http://www.cs.unc.edu/˜eve/pubs.html, printed Sep. 20, 2007, 8 pages. |
| Milgram et al., “Adaptation Effects in Stereo due to Online Changes in Camera Configuration,” SPIE vol. 1669-13, Stereoscopic Displays and Applications III, 17 pages (1992). |
| Mitchell et al., “Colposcopy for the Diagnosis of Squamous Intraepithelial lesions: A metaanalysis,” Obstetrics and Gynecology; Apr. 1998; 91(4):626-631. |
| Nakamoto et al., 3D Ultrasound System Using a Magneto-optic Hybrid Tracker for Augmented Reality Visualization in Laparoscopic Liver Surgery, in T. Dohi and R. Kikinis (Eds.): MICCAI 2002, LNCS 2489, pp. 148-155, 2002. |
| Nordstrom et al., “Identification of Cervical Intraepithelial Neoplasia (CIN) Using UV-Excited Fluorescence and Diffuse-Reflectance Tissue Spectroscopy,” Lasers in Surgery and Medicine; 2001; 29; pp. 118-127; Wiley-Liss, Inc. |
| Ohbuchi et al. “An Incremental Volume Rendering Algorithm for Interactive 3D Ultrasound Imaging”, UNC-CH Computer Science Technical Report TR91-003, (1991). |
| Ohbuchi et al., “Incremental Volume Reconstruction and Rendering for 3D Ultrasound Imaging,” Visualization in Biomedical Computing, SPIE Proceedings, pp. 312-323, (Oct. 13, 1992). |
| Ohbuchi, “Incremental Acquisition and Visualization of 3D Ultrasound Images,” Ph.D. Dissertation, UNC-CH Computer Science Technical Report TR95-023, (1993). |
| Pogue, Brian W. et al., “Analysis of acetic acid-induced whitening of high-grade squamous intraepitheliallesions,” Journal of Biomedical Optics; Oct. 2001; 6(4):397-403. |
| Raij, A.B., et al., Comparing Interpersonal Interactions with a Virtual Human to Those with a Real Human; IEEE Transactions on Visualization and Computer Graphics 13(3), 443-457 (2007). |
| Raz et al, Real-Time Magnetic Resonance Imaging-Guided Focal Laser Therapy in Patients with Low-Risk Prostate Cancer, European Urology 58, pp. 173-177. Mar. 12, 2010. |
| Robinett et al., “A Computational Model for the Stereoscopic Optics of a Head-Mounted Display,” SPIE vol. 1457, Stereoscopic Displays and Applications II, pp. 140-160 (1991). |
| Rolland et al., Towards Quantifying Depth and Size Perception in Virtual Environments, Presence: Teleoperators and Virtual Environments, Winter 1995, vol. 4, Issue 1, pp. 1-21 and 24-49. |
| Rosenthal, Michael et al., “Augmented Reality Guidance for Needle Biopsies: An Initial Randomized, Controlled Trial in Phantoms,” Proceedings of Medical Image Analysis, Sep. 2002, vol. 6(3), pp. 313-320, available from www.cs.unc.edu/˜fuchs/publications/AugRealGuida—NeedleBiop02.pdf, printed Sep. 20, 2007, 8 pages. |
| Rosenthal, Michael et al., “Augmented Reality Guidance for Needle Biopsies: A Randomized, Controlled Trial in Phantoms,” Proceedings of MICCAI 2001, eds. W. Niessen and M. Viergever, Lecture Notes in Computer Science, 2001, vol. 2208, pp. 240-248, available from www.cs.unc.edu/˜us/AugmentedRealityAssistance.pdf, printed Sep. 20, 2007, 9 pages. |
| Screenshots from video produced by the University of North Carolina, produced circa 1992. |
| State et al., “Case Study: Observing a Volume Rendered Fetus within a Pregnant Patient,” Proceedings of IEEE Visualization 1994, pp. 364-368, available from www.cs.unc.edu/˜fuchs/publications/cs-ObservVolRendFetus94.pdf, printed Sep. 20, 2007, 5 pages. |
| State et al., “Interactive Volume Visualization on a Heterogeneous Message-Passing Multicomputer,” Proceedings of 1995 Symposium on Interactive 3D Graphics, 1995, pp. 69-74, 208, available from www.cs.unc.edu/˜andrei/pubs/1995—I3D—vol2—Mac.pdf, printed Sep. 20, 2007. |
| State et al., “Simulation-Based Design and RapidPrototyping of a Parallax-Free, Orthoscopic Video See-Through Head-Mounted Display,” Proceedings of International Symposium on Mixed and Augmented Reality (ISMAR) 2005, available from www.cs.unc.edu/˜andrei/pubs/2005—ISMAR—VSTHMD—design.pdf, printed Sep. 20, 2007, 4 pages. |
| State et al., “Stereo Imagery from the UNC Augmented Reality System for Breast Biopsy Guidance” Proc. Medicine Meets Virtual Reality (MMVR) 2003 (Newport Beach, CA, Jan. 22-25, 2003). |
| State et al., “Superior Augmented Reality Registration by Integrating Landmark Tracking and Magnetic Tracking,” ACM SIGGRAPH Computer Graphics, Proceedings of SIGGRAPH 1996, 10 pages (Aug. 1996). |
| State et al., “Technologies for Augmented Reality Systems: Realizing Ultrasound-Guided Needle Biopsies,” Proc. SIGGRAPH 96 (New Orleans, LA, Aug. 4-9, 1996). In Computer Graphics Proceedings, Annual Conference Series, 1996, ACM SIGGRAPH, pp. 439-446. |
| State, Andrei “Exact Eye Contact with Virtual Humans.” Proc. IEEE International Workshop on Human Computer Interaction 2007 (Rio de Janeiro, Brazil, Oct. 20, 2007), pp. 138-145. |
| State, et al.: Contextually Enhanced 3D Visualization for Multi-Born Tumor Ablation Guidance, Departments of Computer Science and Radiology, and School of Medicine, University of North Carolina at Chapel Hill; InnerOptic Technology, Inc. 2008, Chapel Hill, NC, pp. 70-77. |
| Symons et al., “What are You Looking at? Acuity for Triadic Eye Gaze,” J. Gen. Psychology 131(4), pp. 451-469 (2004). |
| Takacs et al., “The Virtual Human Interface: A Photorealistic Digital Human,” IEEE Computer Graphics and Applications 23(5), pp. 38-45 (2003). |
| Takagi et al., “Development of a Stereo Video See-through HMD for AR Systems,” IEEE, pp. 68-77 (2000). |
| Takayama et al., “Virtual Human with Regard to Physical Contact and Eye Contact,” Entertaining Computing 2005, LNCS, vol. 3711, pp. 268-278 (2005). |
| Ultraguide 1000 System, Ultraguide, www.ultraguideinc.com, 1998. |
| Van Staveren et al., “Light Scattering in Intralipid—10% in the wavelength range of 400-1100 nm,” Applied Optics; Nov. 1991; 30(31):4507-4514. |
| Viola et al., “Alignment by Maximization of Mutual Information,” International Journal of Computer Vision, vol. 24, No. 2, pp. 137-154 (1997). |
| Viola, Paul A., Alignment by Maximization of Mutual Information, Ph.D. Dissertation, MIT-Artificial Intelligence Laboratory Technical Report No. 1548 (Jun. 1995), 156 pages. |
| Ware et al., “Dynamic Adjustment of Stereo Display Parameters,” IEEE Transactions on Systems, Many and Cybernetics, 28(1):1-19 (1998). |
| Watson et al., “Using Texture Maps to Correct for Optical Distortion in Head-Mounted Displays,” Proceedings of the Virtual Reality Annual Symposium '95, IEEE, pp. 1-7 (1995). |
| Welch, Hybrid Self-Tracker: An Inertial/Optical Hybrid Three-Dimensional Tracking System, University of North Carolina Chapel Hill Department of Computer Science, TR 95-048 (1995). |
| Yinghui et al., Real-Time Deformation Using Modal Analysis on Graphics Hardware, GRAPHITE 2006, Kuala Lumpur, Malaysia, Nov. 29-Dec. 2, 2006. |
| Zitnick et al., “Multi-Base Stereo Using Surface Extraction,” Visual Interface Inc., (Nov. 24, 1996). |
| “Sony Introduces Head-Mounted Display for Endoscopic Surgery” (Jul. 23, 2013), retrieved Sep. 27, 2016, 5 pages, available at http://www.medgadget.com/2013/07/sony-introduces-head-mounted-display-for-endoscopic-surgery.html. |
| “Sony Introduces ‘head-mount image processing unit’ for endoscopic image display” (Jul. 23, 2013), retrieved Sep. 27, 2016, 14 pages, available at http://www.sony.net/SonyInfo/News/Press/201307/13-085E/index.html. |
| Number | Date | Country | |
|---|---|---|---|
| 62296440 | Feb 2016 | US |
