Wireless Imaging System

A wireless imaging device including a head unit configured to couple to a scope. The head unit having a housing with an internal cavity configured to receive a battery. The wireless imaging device includes a flexible cable having a proximal end and distal end, the flexible cable coupled to the head unit at the proximal end. The wireless imaging device further includes a light engine having a first end and a second end opposite the first end. The light engine is coupled to the distal end of the flexible cable at the first end and configured to be removably coupled to a scope at the second end such that when the light engine is coupled to the scope, the light engine and the scope are freely rotatable relative to the head unit.

TECHNICAL FIELD

The present disclosure generally relates to a wireless imaging system, and more particularly, a wireless medical imaging system such as arthroscopic and endoscopic devices.

SUMMARY

One embodiment of the present disclosure provides a wireless imaging device having a head unit configured to couple to a scope, the head unit having a housing with an internal cavity configured to receive a battery, a flexible cable having a proximal end and a distal end, the proximal end of the flexible cable being coupled to the head unit, and a light engine having a first end coupled to the distal end of the flexible cable and a second end opposite the first end. The light engine is configured to be removably coupled to a scope at the second end such that when the light engine is coupled to the scope, the light engine and the scope are freely rotatable relative to the head unit.

In some embodiments, the light engine includes a light converter comprising a plurality of phosphor particles volumetrically disposed within a substrate. The light engine may include an optical element and a window such that the light converter is disposed between the optical element and the window of the light engine. In some embodiments, light converter is a disk.

In some embodiments, the head unit includes a first end and a second end opposite the first end, the first end having a planar front face. The planar front face may include a power cable port and a mount, the power cable port being co-planar with the mount and coupled to the flexible cable. The planar front face may be disposed opposite the internal cavity.

In some embodiments, the wireless imaging device further includes a removable battery sized and shaped to be inserted into the internal cavity. The removable battery may include an exposed distal portion that is exposed and flush with the housing when the removable battery is disposed within the internal cavity. The head unit may include a coupling element configured to engage the removable battery when the removable battery is inserted into the internal cavity.

In some embodiments, the head unit includes a mount configured to couple to one or more of C-mount scopes, eye-piece scopes, and direct view scopes.

In some embodiments, the head unit includes a display screen configured to display an image of a target area viewed by the scope.

In some embodiments, the light engine includes a volumetric converter, an optical element, a window, and an opening arranged in series along a central axis. The light engine may include an outer shell, the outer shell configured to maintain the light engine at a temperature under approximately 45° C.

In some embodiments, the wireless imaging device further includes at least one antenna disposed within the head unit, the at least one antenna configured to wirelessly communicate with a remote receiver.

In some embodiments, the light engine includes an illumination source generating a first light having a first wavelength, the first light being converted by a volumetric converter to a second light having a second wavelength different than the first wavelength. In some embodiments, the light engine includes an outer shell and an opening extending at least partially through the outer shell along a central axis.

Another embodiment of the present disclosure provides a wireless imaging device having a head unit configured to couple to a scope, the head unit having a housing with an internal cavity configured to receive a battery, a first end having a planar face including a power cable port and a mount configured to receive a scope, and a second end being opposite the first end and having the internal cavity, a flexible cable having a proximal end and distal end, the proximal end of the flexible cable being coupled to the head unit at the power cable port, and a light engine coupled to the distal end of the flexible cable, the light engine being configured to be removably coupled to the scope such that when the light engine is coupled to the scope, the light engine and the scope are freely rotatable relative to the head unit. The light engine includes a volumetric converter, an optical element, a window, and an opening arranged in series along a central axis. The light engine also includes an illumination source generating a first light having a first wavelength, the first light being converted by the volumetric converter to a second light having a second wavelength different than the first wavelength.

Another embodiment of the present disclosure provides an imaging system having a wireless imaging device having a head unit configured to removable couple to a scope, the head unit including a proximal end and distal end, the proximal end of the head unit including a power cable port coupled to a flexible cable and the distal end of the head unit including an internal cavity configured to receive a battery, the wireless imaging device including a light engine having a first end coupled to the head unit via the flexible cable and a second end opposite the first end configured to couple to the removable scope, wherein the wireless imaging device includes one or more antennas disposed within the head unit, and a receiver disposed remote to the wireless imaging device, the receiver being in wireless communication with the one or more antennas and configured to wirelessly receive imaging data from the one or more antennas.

In some embodiments, the imaging system further includes a display device in communication with the receiver, the display device having a display screen configured to display the imaging data.

DETAILED DESCRIPTION

Exemplary embodiments of the present disclosure provide a wireless imaging device. Referring toFIGS.1-10, there is shown a wireless imaging system. The wireless imaging system may include a wireless imaging device, generally designated100. The wireless imaging system may further include a receiver (e.g., receiver400) and a battery charging device (e.g., battery charging device300) configured to charge a battery (e.g., battery108). In use, wireless imaging device (“device”)100is a wireless device that is configured to provide light to a target area and capture images and/or videos from the target area. Device100may be configured for use in different industries and practices such as medicine, dentistry, construction, automotive, aeronautics, or any other type of industry. Device100may be wireless such that it allows for easier maneuverability and portability when using device100. Further, device100being wireless may reduce accidents or mistakes due to the elimination of wires that would serve as a trip or fall hazard.

In some embodiments, device100includes a scope or optical device (e.g., scope150) coupled to a head unit (e.g., head unit102) to aid in visualization. Device100may include a medical scope (e.g., endoscope, arthroscope, bronchoscope). Device100may be configured to work with most standard medical scopes such that the head unit of device100can be coupled to most standard medical scopes without the need for additional adapters or components. Additionally, device100may be configured to allow for the use of adapters to assist device100in coupling to medical scopes. Device100may be configured to be used for endoscopy, arthroscopy, bronchoscopy, gastroscopy, colonoscopy, cystoscopy, or any other type of procedure that requires imaging. However, device100may include a head unit configured to couple to non-medical scopes such as borescopes, fiberscopes, videoscopes, or any other type of scope.

In some embodiments, device100is a wireless medical imaging device. For example, device100may be a wireless medical imaging device that allows a user to diagnose and treat a patient by viewing a target area within a patient. Device100may allow for minimally invasive procedures to be provided more easily due to device100being wireless. For example, device100may be wireless such that no cords are extending from device100to a tower or other device. This results in an operating room (OR) having more usable space as less space is taken up by towers and cables, or it may result in a more efficient or smaller room layout. Device100being wireless may allow for easier maneuverability of device100during use resulting in faster and better treatment of patients. Further, device100being wireless allows for faster set-up time, use time, and break-down time for surgical procedures. Device100being wireless also may decrease the number of individuals required to perform the procedures or assist with performance of the procedures. For example, device100being wireless may reduce the number of nurses or technicians needed to perform the procedure. Additionally, reprocessing, cleaning, and sterilization time may also be reduced due to the lack of wires and the smaller footprint of device100compared to conventional imaging systems. The improvements herein may save considerable time and expenses for the user of device100(e.g., medical provider or hospital).

In some embodiments, the portability and wireless nature of device100allows for device100to be used anywhere without the need for a medical setting. Since device100can be used anywhere and may not require a medical setting, a patient may receive medical care without having to be moved to another location. In some embodiments, device100being wireless allows it to be used at many different locations such as in/out-patient surgical centers, physician offices, nursing homes/long term care facilities, and mobile clinics and surgical centers that can go to a patient directly. For example, a bed-bound patient at a long-term facility who is suffering from an injury could be treated at that facility and rapidly be provided rehabilitation services instead of spending additional time at a hospital operating room or having to suffer from difficult transportation. Further, device100may allow for the creation of mobile diagnostic and surgical suites that could provide minimally invasive surgery next to the homes of their patients thereby decreasing the pre- and post-surgical time, and quickly returning the patient to a comfortable environment. Additionally, due to the compact size and easy portability of device100, device100may allow for the use of advanced imaging and surgical procedures in austere environments that do not have access to modern hospitals such as, for example, developing countries, military operations, or natural disaster areas.

Referring toFIGS.1-4, device100may include head unit102and light source or light engine200. Head unit102of device100may be configured to couple to scope150. In some embodiments, scope150is coupled to head unit102and light engine200. In some embodiments, scope150is a laparoscope, ENT scope, an arthroscope, or any other type of medical imaging scope. Head unit102may be coupled to light engine200via power cable (“cable”)112. In some embodiments, head unit102is configured to receive an image from scope150that is illuminated via light from light engine200. For example, light engine200may be configured to output light that travels through scope150to illuminate a target area. Light from the target area may reflect back through scope150to head unit102.

Head unit102may include one or more cameras and one or more image processing units configured to convert the light received from the target area to an image/video. For example, head unit102may include a camera configured to receive light from the target area via scope150and head unit102may include an image processing unit configured to convert the received light to image/video data. The image/video data may be sent to a remote receiver and the remote receive may be coupled to a display configured to convert the image/video data to one or more images/videos for viewing. In some embodiments, device100includes a display screen for displaying the image/video of the target area. For example, device100may include a display screen disposed on an exterior surface (e.g., housing105) of device100configured to display the image/video of the target area. User interface116may include a display screen configured to display the image/video of the target area. In some embodiments, user interface116is a touchscreen allowing a user to control head unit102and also view images/video of the target area. Alternatively, device100may transmit image/video data to an external display. In some embodiments, device100wirelessly transmits image/video data to an external display.

In some embodiments, head unit102is sized and shaped to fit within the hand of user. For example, head unit102may have an ergonomic design that allows head unit102to fit easily in the hand of individual users for extended periods of time without causing discomfort. Head unit102may be configured to offer multiple gripping and holding options. In some embodiments, head unit102allows device100to be lighter in weight compared to traditional imaging devices. For example, head unit102may be 300 grams to 500 grams, 325 grams to 450 grams, or 350 grams to 400 grams. For example, head unit102, and thus device100, being wireless reduces the need for additional wires and cables thereby reducing the overall weight of device100as well as eliminating the effects of wires and cables pulling on head unit102.

With continued reference toFIGS.1-4, head unit102may include housing105. Housing105may comprise the external surface of head unit102. In some embodiments, housing105is comprised of a durable material to allow for more rugged use of device100. For example, housing105may be comprised of a durable polymer, metal, or combination thereof to allow head unit102to be dropped or receive one or more impacts without damaging head unit102. Housing105may be made via molding, casting, reductive processes, and/or an additive process (e.g., 3D printing). Housing105may include internal cavity118, which may be configured to receive battery108. Battery108may be a removable battery configured to be inserted into and removed from internal cavity118.

In some embodiments, internal cavity118is configured to receive battery108in a specific orientation. Internal cavity118may include connecting element119configured to couple battery108to head unit102. In some embodiments, fully inserting battery108into internal cavity118results in coupling battery108to connecting element119. Coupling of battery108and connecting element119may result in battery108being coupled to head unit102and battery108providing power to head unit102. For example, inserting battery108into internal cavity118such that battery108couples to connecting element119may result in battery108providing power to head unit102.

Referring toFIG.1, battery108may include proximal end107and distal end109. Distal end109may be opposite proximal end107. In some embodiments, when battery108is fully inserted into internal cavity118, distal end109may remain exposed. Distal end109being exposed may allow a user to easily grip onto battery108and remove it from internal cavity118to replace, repair, or recharge battery108. In some embodiments, when battery108is fully inserted into internal cavity118, distal end109is flush with housing105to allow a user to comfortably grip head unit102proximate distal end109of battery108during use of device100.

In some embodiments, head unit102includes proximal end101and distal end103. Proximal end101may be opposite distal end103and may include power cable port120and mount115. In some embodiments, each of power cable port120and mount115are opposite internal cavity118. For example, power cable port120and mount115may be disposed on proximal end101, which may be disposed opposite from internal cavity118, which is disposed on distal end103. Proximal end101may include a planar front face. In some embodiments, power cable port120and mount115are disposed on the planar front face such that power cable port120is co-planar with mount115.

In some embodiments, proximal end101is substantially planar such that power cable port120is co-planar with mount115. Power cable port120may be coupled to power cable112thereby coupling power cable112to head unit102. Power cable port120may be coupled to proximal end113of power cable112. In some embodiments, power cable112is fixedly coupled to power cable port120. However, power cable112may be removably coupled to power cable port120.

In some embodiments, proximal end101includes mount115. Mount115may be configured to couple to scope150(e.g., endoscope). In some embodiments, mount115is configured to removably coupled head unit102to scope150. Mount115may be configured to be compatible with different types of coupling mechanisms. For example, mount115may be compatible with C-mount couplers, eye-piece couplers, direct view couplers, or any other type of coupling mechanism. In some embodiments, mount115is configured to allow head unit102to couple to C-mount scopes, eye-piece scopes, direct view scopes, or any other type of scope. Mount115may be configured to couple to and secure scope150to head unit102. Mount115may allow head unit102to be plug-and-play compatible with various types of scopes, such as scope150. For example, during use of device100, a user may couple a first scope to head unit102(e.g., via mount115) and then easily decouple the first scope from head unit102and couple a second scope to head unit102. In some embodiments, scope150includes adjustment mechanism114and scope150is coupled to mount115via adjustment mechanism114. Adjustment mechanism114may assist in securing scope150to head unit102at mount115. In some embodiments, adjustment mechanism114allows scope150to be freely rotated relative to head unit102without disengaging scope150from mount115. In some embodiments, scope150is configured to rotate 360 degrees relative to head unit102and/or mount115to allow a user to achieve the desired orientation and view.

In some embodiments, adjustment mechanism114is configured to allow a user to adjust and/or control various functions of device100. For example, adjustment mechanism114may allow a user to adjust the focus and/or zoom (e.g., zooming in and out) of the images/videos received by head unit102from scope150. Adjustment mechanism114may also allow a user to adjust the amount of light emitted by scope150to the target area. In some embodiments, during use of device100, a user may hold head unit102with a single hand and use the same hand to adjust adjustment mechanism114. Alternatively, a user may use a different hand to adjust adjustment mechanism114.

Referring toFIGS.1-2, proximal end101may include protrusion110. Protrusion110may be configured to prevent a user's hand from slipping towards scope150. In some embodiments, protrusion110provides an ergonomic resting location for a user's hand or a portion of the user's hand. Protrusion110may include one or more antennas. The one or more antennas may be configured to transmit data (e.g., image/video data, command and control signals, etc.) to a remote receiver and receive information from a remote device. In some embodiments, the one or more antennas are disposed anywhere within head unit102, such as proximate proximal end101, proximate distal end103, and/or between proximal end101and distal end103.

In some embodiments, the one or more antennas are configured to wirelessly communicate with a remote receiver (e.g., receiver400). For example, head unit102may include one or more antennas and head unit102may be configured to wirelessly communicate with a remote receiver via a wireless modality. The wireless modality may be ultrawide band (UWB), Bluetooth, Nearfield communication (NFC), Wi-Fi, Cellular, or any other type of wireless modality. In some embodiments, device100utilizes UWB to communicate with a remote receiver (e.g., receiver400). Device100may further include built in encryption to securely transmit data to the remote receiver. For example, device100may associate the image/video data generated by head unit102with an authentication factor, such as an authentication token. Device100may transmit the image/video data with the authentication factor to a remote receiver (e.g., receiver400). The remote receiver may include an encryption engine configured to authenticate the authentication factor received with the image/video data to ensure that the image/video data was transmitted securely from head unit102. Further, associated the image/video data generated by head unit102with an authentication factor prevents unauthorized users and/or devices from accessing the image/video data.

In some embodiments, during use of device100, other devices, such as other wireless devices, are simultaneously used adjacent to device100, which results in interference. Device100utilizing UWB for wireless communication prevents or minimizes interference from other devices while maintaining the ability to send large packets of data (e.g., image/video data). For example, utilizing UWB communication allows device100to send large sized image/video data containing high resolution images/videos to the remote receiver (e.g., receiver400) for viewing via a display coupled to the receiver, as well as command and control signals. In some embodiments, wireless communication between device100and a remote receiver is configured to act as a cable for coding purposes. This allows for the simplification of communication protocols and debugging of issues during use of device100. In some embodiments, device100is configured to provide low latency communication such that lag is minimized between head unit102receiving data from the target area being viewed by scope150and what is being received by the receiver and displayed to the user via a display screen. Device100providing low latency communication increases the efficiency of procedures during use of device100in addition to reducing injuries, mistakes, or accidents during procedures using device100.

In some embodiments, distal end103is configured to receive battery108via internal cavity118. In some embodiment, head unit102is coupled to battery108to allow device100to be wireless without the need for power lines. Battery108may be rechargeable. In some embodiments, battery108is configured to be removably coupled to head unit102such that battery108is able to be quickly swapped out and replaced with a fully charged battery108. In some embodiments, when battery108is received in internal cavity118of head unit102, all or a portion of distal end109(e.g., a distal portion) may be exposed (e.g., a portion of distal end109not disposed within internal cavity118) is flush with housing105. Head unit102may include locking device117to secure battery108in place when battery108is coupled to head unit102. Locking device117may be configured to allow battery108to be removably coupled to head unit102. For example, locking device117may be configured to engage with a portion of battery108to secure battery108within internal cavity118. A user interact with locking device117, such as disengaging locking device117, to allow for the removal of battery108from internal cavity118. In some embodiments, locking device117allows battery108to be quickly changed and reset in approximately30seconds. Battery108and locking device117reduces the down time during replacing of battery108during use of device100.

Referring toFIG.4, replacing battery108within head unit102results in resetting device100to a base state. For example, when battery108is fully disposed within internal cavity118, battery108may engage with connecting element119. When battery108is at least partially removed from internal cavity118, battery108may no longer engage with connecting element119thereby causing device100to reset and/or enter a base state. Resetting device100to a base state may assist in fixing any errors or issues that arise during use of device100. In resetting device100to a base state, all or most settings of device100may be reset to address any errors or issues that previously arose. In addition, resetting device100ensures that no protected data, such as patient or HIPAA data, is stored locally, and allows for a quick boot-up cycle.

In some embodiments, device100includes an internal battery disposed within head unit102. The internal battery may provide power to device100when battery108disengages from connecting element119and/or is removed from internal cavity118. The internal battery providing power to device100may prevent device100from resetting or entering a base state when battery108is replaced or removed. This allows for continuous use of device100even when battery108is being replaced or is removed. In some embodiments, device100is configured to allow a user to disengage the internal battery to prevent the internal battery from providing power to device100during replacing and/or removing of battery108. Disengaging the internal battery allows a user to reset device100to a base state when battery108is disengaged from connecting element119and/or when battery108is removed from internal cavity118.

In some embodiments, battery108is configured to provide at least 1 hour of continuous run time for device100. For example, single use of battery108may result in at least 1 hour, 2 hours, 3 hours, 4 hours, 5 hours, or greater than 6 hours of run time of device100. In some embodiments, battery108is configured to provide a runtime of 30 minutes to 600 minutes, 180 minutes to 540 minutes, or 240 minutes to 480 minutes. Battery108may be configured to allow device100to be operated without a battery change/replacement for longer than most surgeries or procedures require. This is due to the power and efficiency of battery108and very efficient electronics of device100, which are designed to ensure longevity of battery108and use of device100. Further, device100may be configured to operate with lower power consumption than traditional imaging devices. For example, device100may require less energy to operate compared to traditional imaging devices. In some embodiments, device100uses 1% to 5% of the total power required by traditional imaging devices. Wireless imaging device system, including device100, receiver400, and battery charging device300, uses 1% to 5% of the total power required by traditional imaging systems. This results in less electricity usage thereby resulting in lower expenses for users of device100(e.g., medical provider or hospital). Further, device100being wireless and portable results in device100having a smaller footprint compared to traditional imaging devices. Device100having a smaller footprint allows for easier cleaning and sterilization of device100compared to traditional imaging devices.

In some embodiments, the reduced power usage of our wireless imaging device system (device100, receiver400, and battery charging device300) also reduces the amount of waste heat generated compared to traditional imaging systems. The waste heat must be removed from the OR, leading to increased power savings. Wireless imaging device system (device100, receiver400, and battery charging device300) reducing the amount of waste heat results in a more efficient imaging system due to decreased electricity usage (heating, ventilation, and air condition).

Referring toFIGS.1and5, head unit102may be coupled to light engine200via power cable112. Light engine200may include first end201and second end203. First end201may be disposed opposite second end203. In some embodiments, light engine200is coupled to power cable112at first end201and is coupled to scope150at second end203. First end201and second end203may be disposed along central axis A-A. In some embodiments, central axis A-A bifurcates light engine200. For example, light engine200may be symmetrical about central axis A-A.

Power cable112may include proximal end113and distal end111. In some embodiments, proximal end113is coupled to head unit102at power cable port120. Distal end111may be coupled to light engine200. Power cable112may be configured to provide power to light engine200. In some embodiments, power cable112is flexible to allow light engine200to rotate relative to head unit102. For example, power cable112being flexible may allow for 360 degrees rotation of light engine200relative to head unit102. In some embodiments, power cable112is configured to be flexible to prevent impeding the rotation of light engine200relative to head unit102. Light engine200may be configured to generate light for illuminating a target area. Light engine200may output light that travels through scope150to the target area.

Light engine200may be configured to generate and output light. Light engine200may include outer shell202. Outer shell202may be comprised of aluminum or another metal or polymer with high heat transfer. In some embodiments, outer shell202serves as a heat sink to dissipate heat generated by light engine200. For example, outer shell202may dissipate heat generated by light engine200to cause light engine200to stay below a temperature that may cause burn injuries, such as below approximately 43.5° C. However, outer shell202may be configured to dissipate heat generated by light engine200to cause light engine200to stay below approximately 45° C., approximately 40° C., approximately 35° C., approximately 30° C., or approximately 25° C. In some embodiments, light engine200is configured to stay below approximately 45° C. (e.g., below 43.5° C.) during extended use of device100(e.g., use exceeding 4 hours). Light engine200, and by extension device100, staying below approximately 40° C. prevents burn injuries to individuals around device100in addition to preventing device100from becoming a fire hazard.

In some embodiments, light engine200includes illumination source204. Illumination source204may be a laser, a light emitting diode (LED), incandescent light sources, or any other type of sources capable of providing illumination. Illumination source204may be coupled to power cable112via circuit board206. In some embodiments, circuit board206is a printed circuit board disposed within outer shell202of light engine200. Circuit board206may be configured to communicate with head unit102via power cable112. In some embodiments, circuit board206controls the amount of light generated by illumination source204and/or the amount of light outputted by light engine200.

Light engine200may include holder assembly208, which may be configured to secure illumination source204in place. In some embodiments, holder assembly208acts a heat sink to dissipate heat generated by illumination source204. Holder assembly208may be configured to secure illumination source204in place during movement of light engine200and/or device100.

Illumination source204may be configured to generate and output light210. Illumination source204may output light210having a peak wavelength of 440 nm to 470 nm. In some embodiments, light210is unconditioned light outputted by illumination source204. Light engine200may include optical element212configured to condition, collimate, filter, direct, and/or focus light210outputted by illumination source204. In some embodiments, optical element212includes one or more homogenizing rods configured to collimate and direct light210. Optical element212may be comprised of glass, plastic, or any other type of material to allow optical element212to condition, collimate, filter, direct, and/or focus light210. Optical element212may be configured to direct and/or collimate light210onto converter214. Converter214may be disposed within outer shell202of light engine200and may be configured to convert light210to light218. In some embodiments, light218has a different wavelength than light210.

In some embodiments, light converter or converter214is configured to convert incoming light210to light218, which is outputted by light engine200. Light218may be white light, between 480 nm-770 nm. In some embodiments, converter214is a volumetric spectrum converter comprising phosphor particles. Converter214may include phosphor particles volumetrically disposed within a substrate. In some embodiments, the substrate may be a homogenous composite substrate of non-converting material (e.g., plastic, acrylic, glass, ceramic). The phosphor particles being volumetrically disposed within converter214allows converter214to more efficiently convert light210to light218. In some embodiment, converter214is comprised of a plurality of layers and each layer may have a plurality of phosphor particles volumetrically disposed within. The plurality of layers may form a volumetric spectrum converter. In some embodiments, the plurality of layers are arranged such that each layer is substantially perpendicular to light210. In some embodiments, light210strikes converter214at an angle of 45 degrees to 135 degrees, 65 degrees to 125 degrees, or 75 degrees to 115 degrees.

Converter214may be chosen to convert light from illumination source204to light of another wavelength, for example, narrow or broad spectrum, or non-coherent light. Converter214may be comprised of a converting material that may include, for example, phosphorescent material, florescent material, other radiation converting material, or combinations of these materials. The converting material is volumetrically disposed in a substrate that may include, for example, PMMA, polystyrene, polycarbonate, polyester, copolymers, or blends of a combination of the aforementioned materials to create an effectively homogenous composite. This process may include, for example, extrusion, coating, lamination, blending, mixing, or suspending. In some embodiments, converter214has a thickness of 0.1 mm to 5 mm and a radius of 0.1 mm to 5 mm.

In some embodiments, converter214is a volumetric phosphor disk configured to convert light210to light218. Alternatively, converter214may be a volumetric phosphor sphere, cube, rectangular prism, pyramid, sphere, or any other shape desired. Converter214may be secured within light engine200. For example, converter214may be disposed between optical element212and window219of light engine200. In some embodiments, converter214is a disk secured between optical element212and window219via friction, adhesives, epoxy, fasteners, or any other methods of securing converter214between optical element212and window219. Light218may exit converter214such that light218passes through window219and exits light engine200. Window219may be transparent to allow light218to pass through.

In some embodiments, outer shell202includes opening213that extends at least partially through outer shell202. Opening213may be in optical communication with window219such that light218from converter214passes through window219and out of light engine200via opening213. In some embodiments, opening213extends through outer shell202along central axis A-A. In some embodiments, illumination source204, optical element212, and window219are aligned. For example, illumination source204, optical element212, window219, converter214and opening213may be disposed along central axis A-A of light engine200. In some embodiments, illumination source204, optical element212, window219, converter214and opening213are arranged in series along central axis A-A.

Referring toFIGS.2and5, light engine200may include rings216. Rings216may be configured to assist in coupling light engine200to scope150. For example, scope150may include coupling element122, which may be received by light engine200and secured to light engine200via rings216. In some embodiments, scope150includes coupling element122that is received by rings216of light engine200such that coupling element122and scope150are secured to light engine200. Light engine200may be secured to scope150via coupling element122and scope150such that light engine200and scope150are rotatable relative to head unit102. For example, light engine200and scope150may rotate 360 degrees relative to head unit102.

Referring toFIGS.6A and6B, battery108may be rechargeable and may be recharged using battery charging device300. Battery charging device300may be configured to charge one or more batteries108. In some embodiments, battery charging device300includes one or more grooves302configured to receive battery108. Groove302may be sized and shaped to receive and secure battery108. In some embodiments, groove302receives battery108to allow battery108to rest within battery charging device300while battery108is being charged. Groove302may allow for easy alignment of battery108within battery charging device300to allow a user to easily charge battery108. For example, groove302may allow a user to easily align battery108within battery charging device300to quickly initiate charging of battery108.

Groove302may also prevent damage to battery108when placing battery108within battery charging device300. Groove302may also prevent non-compatible batteries from being used with battery charging device300. In some embodiments, battery charging device300is configured to charge one or more batteries108via inductive charging. For example, placing battery108within groove302of battery charging device300may result in battery108being charged by battery charging device300. Alternatively, battery charging device300is configured to charge one or more batteries108via conductive charging. For example, placing battery108within groove302of battery charging device300causes a battery contact of battery108to contact or abut a charging contact of battery charging device300resulting in battery charging device300charging battery108.

Battery108may also be configured to be easily sterilizable. For example, battery108may be configured to be easily sterilized via one or more vapors, gases, or solutions. In some embodiments, battery108is configured to be sterilizable with a vapor such as vaporized hydrogen peroxide (VHP). In some embodiments, battery108is easily VHP sterilizable after being charged. This simplifies and shortens the reprocessing procedure saving time and money.

In some embodiments, head unit102and/or battery108are configured to be single use. For example, head unit102and/or battery108may be disposable such that after use of head unit102, the user discards one or more of head unit102and battery108. In some embodiments, head unit102and/or battery108are configured to be disposed within a sterilization pouch. For example, prior to use, a user may have to remove head unit102and/or battery108from the sterilization pouch. Head unit102and/or battery108may be pre-sterilized prior to being placed into the sterilization pouch. The sterilization pouch may be configured to keep head unit102and/or battery108sterilized until a user opens and removes head unit102and/or battery108from the sterilization pouch for use.

Referring toFIGS.1-4, head unit102may include user interface116. User interface116may be disposed between proximal end101and distal end103of head unit102. For example, user interface116may be disposed on housing105, such as an external surface of head unit102. In some embodiments, user interface116includes one or more buttons. However, user interface116may be a touchscreen, scrolling wheel, slider, or any other type of user interaction element. In some embodiments, user interface116is located on housing105such that a user can easily access user interface116via one or more fingers during use of device100. For example, a user may grip or hold head unit102using a single hand and may interact with user interface116using fingers of the same hand.

In some embodiments, user interface116may allow a user to control various functions of device100. A user may interact with user interface116via one or more buttons, a touch screen, a scrolling wheel, a slider, or other type of interaction element to allow a user to control various features of device100. For example, a user may interact with user interface116to adjust the zoom, focus, brightness, saturation, resolution, contrast, white balance, and/or exposure level of the image/video generated by head unit102or transmitted by head unit102to an externa display device, such as via a receiver (e.g., receiver400). In some embodiments, user interface116is configured to allow a user to control and/or adjust the amount of light emitted from light engine200and received by head unit102. For example, a user may use user interface116to control the amount of light that is emitted from light engine200and that illuminates the target area. A user may also use user interface116to control the amount of light captured by a camera disposed within head unit102. In some embodiments, user interface116allows a user to capture images and/or videos of the target area and select a storage location (e.g., internal storage, external storage device).

Referring toFIGS.7A-9A, device100may be configured to wirelessly communicate with receiver400. Receiver400may be configured to receive data (e.g., image/video data, command and control signals, etc.) from device100. Receiver400may have a considerably smaller footprint compared to receivers of traditional imaging devices. In some embodiments, receiver400can be scaled in size depending on the desired use and location of use. For example, receiver400may be scaled down to be smaller to allow for easier portability. In some embodiments, receiver400is configured to wirelessly receive encrypted data from head unit102and wirelessly transmit that encrypted data to a display device for viewing images/videos associated with the encrypted data. Alternatively, receiver400may be coupled to an external display device and may transmit the encrypted data to the external display device for viewing images/videos associated with the encrypted data.

Receiver400may include back panel402. Back panel402may include one or more ports406for coupling to one or more devices. For example, back panel402may include one or more ports for coupling to a display device (e.g., display device600). In practice, head unit102of device100is configured to transmit image/video data or command and control signals to receiver400. Head unit102may transmit data (e.g., encrypted data) to receiver400via UWB. In some embodiments, head unit102transmits images or videos of a target area to receiver400. In additional embodiments, head unit102transmits other types of data to receiver400, such as command and control signals. Receiver400may be coupled to a display device to allow one or more users to view the images or videos of the target area captured by head unit102.

In some embodiments, receiver400is configured to receive images/video data in real time, with low latency, and is configured to cause display device600to display the images/videos to allow a user to view the illuminated target area in real time, with low latency. Display device600may be configured to generate display700. Display700may be in color (FIG.8), black and white (FIGS.9A and9B), or grey scale.

In some embodiments, receiver400causes display device600to display and generate display700. For example, receiver400may receive image/video data from head unit102and may transmit the image/video data to display device600for displaying of images/videos associated with the image/video data. Display700may be configured to display image706, which may be an image received by scope150, and processed and transmitted to receiver400by head unit102. For example, image706may be an image of the target area where scope150is viewing. In some embodiments, display700is configured to generate and display images or videos. Display700may include power indicator702to indicate the power level of battery108. Display700may include signal indicator704to indicate the strength of the wireless connection between head unit102and receiver104. For example, signal indicator704may indicate the strength of the UWB connection between head unit102and receiver104.

In some embodiments, display700includes brightness indicator708. Brightness indicator708may indicate the brightness level of image706. In some embodiments, brightness indicator708indicates the lux of light218from light engine200. For example, a user may use user interface116to adjust the lux of light engine200, thereby controlling the brightness of light218, resulting in image706being brighter or dimmer. The increase in brightness may be illustrated via brightness indicator708.

Display700may include function indicator710. In some embodiments, function indicator710is a white balance function indicator to indicate the activation of a white balance function. For example, display700may have a low brightness level resulting in image706being faint or having low brightness making it difficult to ascertain the features of the target area viewed by scope150. In some embodiments, user interface116is used to increase the brightness of display700. For example, a user may use user interface116to increase the brightness of display700resulting in brightness indicator708showing an increase in the brightness level of image706. In some embodiments, brightness indicator708may indicate the change to the sensitivity to the image or video sensor disposed within head unit102. This may indicate how bright an image is outputted by head unit102. For example, a user may use user interface116to increase the brightness of image706resulting in a change to the sensitivity of the image or video sensor of head unit102. An increase in the brightness of image706results in a change to brightness indicator708.

Additionally, display700may have colors that are incorrectly displayed making it difficult to ascertain the features of the target area viewed by scope150. Function indicator710may indicate that a white balance function is being applied to image706resulting in white objects in image706appearing brighter or more color accurate to assist the user in seeing features of image706.

In some embodiments, display700is configured to digitally zoom into image706. For example, a user may use user interface116to zoom in and zoom out of image706via display700. In some embodiments, display700is configured to automatically zoom in or out based on the contents of image706. A user may use user interface116or display700to digitally zoom in and zoom out of image706.

Referring toFIGS.7A-7B and10, receiver400may be configured to couple with mounting bracket500. Mounting bracket500may be configured to allow receiver400to couple to a display (e.g., display device600) such that receiver400is secured to a display device. For example, mounting bracket500may be coupled to bottom404of receiver400and mounting bracket500may further be coupled to display device600to couple receiver400to display device600. Mounting bracket500may include one or more arms504and coupling mechanism502. Coupling mechanism502may be configured to couple to receiver400(e.g., bottom404of receiver400). Arm504may be configured to assist mounting bracket500in coupling to display device600. In some embodiments, coupling of arm504to display and coupling mechanism502to receiver400results in receiver400being coupled to and secured to display device600. In some embodiments, mounting bracket400has two arms504. However, mounting bracket500may have one arm, three arms, four arms, or greater than four arms. In some embodiments, coupling arms504are intended to interface with a VESA mount, or other mounting standard, on the back of a display device600.

In some embodiments, mounting bracket500is configured to couple to receiver400and to the back of display device600such that receiver400is disposed on top of display device600. Receiver400being coupled to display device600such that it sits on top of display device600results in receiver400and the display having an overall smaller footprint and results in a less bulky configuration. Further, receiver400being disposed on top of display device600reduces the amount of cluttering and loose cords. In some embodiments, display device600is a portable display to allow for the use of receiver400, and device100, at any location.

It will be appreciated by those skilled in the art that changes could be made to the exemplary embodiments shown and described above without departing from the broad inventive concepts thereof. It is understood, therefore, that this invention is not limited to the exemplary embodiments shown and described, but it is intended to cover modifications within the spirit and scope of the present invention as defined by the claims. For example, specific features of the exemplary embodiments may or may not be part of the claimed invention and various features of the disclosed embodiments may be combined. The words “front”, “back”, “inward” and “outward” designate directions in the drawings to which reference is made. Unless specifically set forth herein, the terms “a”, “an” and “the” are not limited to one element but instead should be read as meaning “at least one”.