Loupe System
20210341748 · 2021-11-04
Inventors
Cpc classification
G02C3/003
PHYSICS
A61B90/08
HUMAN NECESSITIES
A61B90/30
HUMAN NECESSITIES
International classification
G02C3/00
PHYSICS
Abstract
A head strap (120) for medical loupe glasses is provided, comprising two tubes (130, 132) of flexible wipe-clean material and a magnet (134, 136) located on each tube, the magnets (134, 136) being connectable by magnetic forces to effect securement.
Claims
1. A head strap for medical loupe glasses, comprising two tubes of flexible wipe-clean material and a magnet located on each tube, the magnets being connectable by magnetic forces to effect securement.
2. The head strap of claim 1, wherein the head strap has a smooth outer surface, preferably wherein the flexible wipe-clean material is silicone.
3. The head strap of claim 1, wherein the magnets are moveable.
4. The head strap of claim 3 wherein the magnets are located on toggles slidable over the tubes.
5. The head strap of claim 1, further comprising a connector block for connecting the two tubes, preferably wherein the weight of the connector block is adjustable.
6. The head strap of claim 5, wherein the connector block comprises two connectable parts, preferably wherein the two parts are removably connectable.
7. The head strap of claim 6, wherein the two parts comprise corresponding pegs and holes to facilitate connection.
8. The head strap of claim 6, further comprising a stopper on the end of each tube, configured to anchor the tubes in the connector block.
9. The head strap of claim 8, wherein the toggles, connector block and stoppers can be disconnected from the tubes and subsequently reconnected.
10. The head strap of claim 8, wherein the stoppers have flared ends.
11. The head strap of claim 10, wherein the connector block comprises cavities configured to accommodate and anchor the flared ends of the stoppers.
12. The head strap of claim 1, wherein the magnets have flat faces, preferably wherein the magnets have disc-shaped faces.
13. The head strap of claim 4, wherein the magnets are located on an external face of the toggles, that face being parallel to the tube.
14. The head strap of claim 4, wherein each toggle comprises a hole configured to accommodate the tube, and a dimension of the toggle parallel to the tube is reduced in the region of the hole.
15. The head strap of claim 1, wherein the tubes are configured to attach to temple arms of loupes and comprise a textured internal surface to engage with temple arms of loupes.
16. A loupe system comprising: a loupe; and a head strap, comprising two tubes of flexible wipe-clean material and a magnet located on each tube, the magnets being connectable by magnetic forces to effect securement.
17. The loupe system of claim 16, wherein the magnets are located on toggles slidable over the tubes.
18. The loupe system of claim 16, wherein the loupe comprises temple arms having curved and broadening ends, and the head strap further comprises a textured internal surface configured to engage the temple arms.
19. The loupe system of claim 16, wherein the loupe comprises one or more magnification lenses, and the head strap further comprises a connector block, wherein the weight of the connector block is configured to counterbalance the one or more magnification lenses.
20. The loupe system of claim 16, wherein the loupe comprises one or more magnification lenses and a head light, and the head strap further comprises a connector block, wherein the weight of the connector block is configured to counterbalance the combined weight of the one or more magnification lenses and the head light.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0090] The present disclosure will become more fully understood from the detailed description and the accompanying drawings.
[0091] One or more aspects will now be described, by way of example only and with reference to the accompanying drawings having like-reference numerals, in which:
[0092]
[0093]
[0094]
[0095]
[0096]
[0097]
[0098]
[0099]
[0100]
[0101]
[0102]
[0103]
[0104]
[0105]
[0106]
[0107]
[0108]
[0109]
[0110]
[0111] In the drawings, reference numbers may be reused to identify similar and/or identical elements.
DETAILED DESCRIPTION
[0112] In the preferred embodiment the dentist or surgeon disinfects their head strap by wiping with a disinfect wipe. The user then attaches the head strap to a pair of loupes which the dentist of surgeon owns, purchased from one of the many manufacturers selling such items. The user then adjusts the fitting of the head strap by moving the magnets inside the head strap silicone tubes. Once adjusted the user places the loupes on the head, with the loupes resting on the bridge of the nose and the loupe temples resting over the ears of the user. The head strap is passed over the head and using a simple hand motion the head strap is tightened by pushing the magnets together. The user is then free, with two hands, to continue with his work.
[0113] Reference is made to
[0114] In step 1, the dentist or surgeon disinfects the head strap 20 by wiping the outer smooth silicone surface 30 and 32 and aluminum connector block 38 with a readily available disinfectant wipe, or by boiling the head strap 20 in water for 3 to 4 minutes. The head strap is easy to clean because the uniform construction of the head strap means there are no sharp edges to catch either the wipe or other foreign objects such as hair and also because the head strap is made from silicone material. Silicone is quick-drying, non-porous and hypoallergenic and is 35 times more hygienic than nylon and therefore the head strap is highly more hygienic than a pair of nylon or cotton retainers.
[0115] In step 2, if this is the first time that the user is wearing the head strap they will adjust the size of the head strap by moving the Neodymium N52 magnets 34 and 36 located inside the silicone tubes up or down by a gentle squeeze to ensure the distance between the ends of the head strap 26 and 28 and the magnets 36 and 38 is approximately the distance between the ears 22 and 24 and the back of the head.
[0116] The disc shaped magnets 36 and 38 have been designed with dimensions of 8 mm diameter and 5 mm width, which sit inside the silicon tubing 30 and 32 which has an internal diameter of 4 mm. This combination of sizes has been found to be optimal to allow the magnets to move without slipping. The magnets 34 and 36 have flat faces to ensure there are no ‘pinch points’ which can wear excessively when the magnets are constantly connected and reconnected.
[0117] In step 3, the user attaches the ends of the head strap 26 and 28 to the loupes 12 by inserting the ends of the temples 18 into the ends of the head strap 26 and 28 using a push and twisting motion until tight. The inside of the ends of the silicone tubing 26 and 28 have been designed with a textured internal surface 40 so that the silicone both grips more to the surface of the temples arms using the raised surface elements and also at the same time allows for the silicone material to stretch between the raised surface elements to accommodate as many different sizes and styles of loupe temple arms as possible.
[0118] Once the head strap 20 is attached to the loupes 12, in step 4, the user guides the temples of the loupes 18 either side of the head 10 and over the ears 22 and 24 and the nose bridge of the loupes 14 sit on the user's nose Whilst guiding the loupes the user ensures that the head strap 20 is placed over the head 10.
[0119] In step 5, once the loupes are comfortable on the ears 22 and 24 and nose 14, the user grasps the magnets 34 and 36 and pushes them together behind the head until the magnets come together due to their magnetic attraction. If the head strap is found to be too loose or tight on their first use, the user can pull the magnets 34 and 36 apart and slide them up or down further inside the silicone tube 30 and 32 as required to readjust the size and then ‘click’ them together again.
[0120] During the dental or surgical procedure, the user can view in detail the area to be examined using the loupe magnification lenses 16. If the user needs to move their head from side to side, or up and down, the loupe strap 20 ensures that the loupes 12 remain stable on the nose and ears 22 and 24 and do not slip so much that the view down the magnification lenses 16 is not straight or distorted, or that the loupes 12 do not fall due to their weight and unbalanced nature and potentially break.
[0121] In an alternative embodiment, where heavier or larger loupes 12 are required, the aluminum connector block 38 can be replaced with an alternative heavier weighted block to counterbalance the weight of the loupes on the nose, and over the ears 22 and 24 to ensure a more stable sitting of the loupes 12 on the head 10.
[0122] Once the user has completed their dental or surgical procedure, the user can pull the magnets 34 and 36 apart to loosen the loupes, and the loupes can be taken on the face in a forward motion, with the head strap 20 passing over the head 10.
[0123] In the first embodiment, as illustrated in
[0124]
[0125]
[0126]
[0127]
[0128] The connector block 138 as described could be use in conjunction with magnet provided internally or externally to the head strap. If used with the second embodiment, in which the magnets are located on toggles slidable over the tubes, it is possible for the connector block 138 to be disconnected and removed, and the stoppers 140 and toggles 134 and 136 removed also. This can allow the straps to be removed completely and thoroughly cleaned and/or replaced.
[0129] It should be understood that the present invention has been described above purely by way of example, and modifications of detail can be made within the scope of the invention.
[0130] Each feature disclosed in the description, and (where appropriate) the claims and drawings may be provided independently or in any appropriate combination.
[0131] Reference numerals appearing in the claims are by way of illustration only and shall have no limiting effect on the scope of the claims.
CONCLUSION
[0132] The foregoing description is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. The broad teachings of the disclosure can be implemented in a variety of forms. Therefore, while this disclosure includes particular examples, the true scope of the disclosure should not be so limited since other modifications will become apparent upon a study of the drawings, the specification, and the following claims. In the written description and claims, one or more steps within a method may be executed in a different order (or concurrently) without altering the principles of the present disclosure. Similarly, one or more instructions stored in a non-transitory computer-readable medium may be executed in different order (or concurrently) without altering the principles of the present disclosure. Unless indicated otherwise, numbering or other labeling of instructions or method steps is done for convenient reference, not to indicate a fixed order.
[0133] Further, although each of the embodiments is described above as having certain features, any one or more of those features described with respect to any embodiment of the disclosure can be implemented in and/or combined with features of any of the other embodiments, even if that combination is not explicitly described. In other words, the described embodiments are not mutually exclusive, and permutations of one or more embodiments with one another remain within the scope of this disclosure.
[0134] Spatial and functional relationships between elements (for example, between modules, circuit elements, semiconductor layers, etc.) are described using various terms, including “connected,” “engaged,” “coupled,” “adjacent,” “next to,” “on top of,” “above,” “below,” and “disposed.” Unless explicitly described as being “direct,” when a relationship between first and second elements is described in the above disclosure, that relationship can be a direct relationship where no other intervening elements are present between the first and second elements, but can also be an indirect relationship where one or more intervening elements are present (either spatially or functionally) between the first and second elements.
[0135] The phrase “at least one of A, B, and C” should be construed to mean a logical (A OR B OR C), using a non-exclusive logical OR, and should not be construed to mean “at least one of A, at least one of B, and at least one of C.” The term “set” does not necessarily exclude the empty set—in other words, in some circumstances a “set” may have zero elements. The term “non-empty set” may be used to indicate exclusion of the empty set—in other words, a non-empty set will always have one or more elements. The term “subset” does not necessarily require a proper subset. In other words, a “subset” of a first set may be coextensive with (equal to) the first set. Further, the term “subset” does not necessarily exclude the empty set—in some circumstances a “subset” may have zero elements.
[0136] In the figures, the direction of an arrow, as indicated by the arrowhead, generally demonstrates the flow of information (such as data or instructions) that is of interest to the illustration. For example, when element A and element B exchange a variety of information but information transmitted from element A to element B is relevant to the illustration, the arrow may point from element A to element B. This unidirectional arrow does not imply that no other information is transmitted from element B to element A. Further, for information sent from element A to element B, element B may send requests for, or receipt acknowledgements of, the information to element A.
[0137] In this application, including the definitions below, the term “module” can be replaced with the term “controller” or the term “circuit.” In this application, the term “controller” can be replaced with the term “module.” The term “module” may refer to, be part of, or include: an Application Specific Integrated Circuit (ASIC); a digital, analog, or mixed analog/digital discrete circuit; a digital, analog, or mixed analog/digital integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); processor hardware (shared, dedicated, or group) that executes code; memory hardware (shared, dedicated, or group) that stores code executed by the processor hardware; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-chip.
[0138] The module may include one or more interface circuits. In some examples, the interface circuit(s) may implement wired or wireless interfaces that connect to a local area network (LAN) or a wireless personal area network (WPAN). Examples of a LAN are Institute of Electrical and Electronics Engineers (IEEE) Standard 802.11-2020 (also known as the WWI wireless networking standard) and IEEE Standard 802.3-2018 (also known as the ETHERNET wired networking standard). Examples of a WPAN are IEEE Standard 802.15.4 (including the ZIGBEE standard from the ZigBee Alliance) and, from the Bluetooth Special Interest Group (SIG), the BLUETOOTH wireless networking standard (including Core Specification versions 3.0, 4.0, 4.1, 4.2, 5.0, and 5.1 from the Bluetooth SIG).
[0139] The module may communicate with other modules using the interface circuit(s). Although the module may be depicted in the present disclosure as logically communicating directly with other modules, in various implementations the module may actually communicate via a communications system. The communications system includes physical and/or virtual networking equipment such as hubs, switches, routers, and gateways. In some implementations, the communications system connects to or traverses a wide area network (WAN) such as the Internet. For example, the communications system may include multiple LANs connected to each other over the Internet or point-to-point leased lines using technologies including Multiprotocol Label Switching (MPLS) and virtual private networks (VPNs).
[0140] In various implementations, the functionality of the module may be distributed among multiple modules that are connected via the communications system. For example, multiple modules may implement the same functionality distributed by a load balancing system. In a further example, the functionality of the module may be split between a server (also known as remote, or cloud) module and a client (or, user) module. For example, the client module may include a native or web application executing on a client device and in network communication with the server module.
[0141] Some or all hardware features of a module may be defined using a language for hardware description, such as IEEE Standard 1364-2005 (commonly called “Verilog”) and IEEE Standard 1076-2008 (commonly called “VHDL”). The hardware description language may be used to manufacture and/or program a hardware circuit. In some implementations, some or all features of a module may be defined by a language, such as IEEE 1666-2005 (commonly called “SystemC”), that encompasses both code, as described below, and hardware description.
[0142] The term code, as used above, may include software, firmware, and/or microcode, and may refer to programs, routines, functions, classes, data structures, and/or objects. Shared processor hardware encompasses a single microprocessor that executes some or all code from multiple modules. Group processor hardware encompasses a microprocessor that, in combination with additional microprocessors, executes some or all code from one or more modules. References to multiple microprocessors encompass multiple microprocessors on discrete dies, multiple microprocessors on a single die, multiple cores of a single microprocessor, multiple threads of a single microprocessor, or a combination of the above.
[0143] The memory hardware may also store data together with or separate from the code. Shared memory hardware encompasses a single memory device that stores some or all code from multiple modules. One example of shared memory hardware may be level 1 cache on or near a microprocessor die, which may store code from multiple modules. Another example of shared memory hardware may be persistent storage, such as a solid state drive (SSD), which may store code from multiple modules. Group memory hardware encompasses a memory device that, in combination with other memory devices, stores some or all code from one or more modules. One example of group memory hardware is a storage area network (SAN), which may store code of a particular module across multiple physical devices. Another example of group memory hardware is random access memory of each of a set of servers that, in combination, store code of a particular module.
[0144] The term memory hardware is a subset of the term computer-readable medium. The term computer-readable medium, as used herein, does not encompass transitory electrical or electromagnetic signals propagating through a medium (such as on a carrier wave); the term computer-readable medium is therefore considered tangible and non-transitory. Non-limiting examples of a non-transitory computer-readable medium are nonvolatile memory devices (such as a flash memory device, an erasable programmable read-only memory device, or a mask read-only memory device), volatile memory devices (such as a static random access memory device or a dynamic random access memory device), magnetic storage media (such as an analog or digital magnetic tape or a hard disk drive), and optical storage media (such as a CD, a DVD, or a Blu-ray Disc).
[0145] The apparatuses and methods described in this application may be partially or fully implemented by a special purpose computer created by configuring a general purpose computer to execute one or more particular functions embodied in computer programs. Such apparatuses and methods may be described as computerized apparatuses and computerized methods. The functional blocks and flowchart elements described above serve as software specifications, which can be translated into the computer programs by the routine work of a skilled technician or programmer.
[0146] The computer programs include processor-executable instructions that are stored on at least one non-transitory computer-readable medium. The computer programs may also include or rely on stored data. The computer programs may encompass a basic input/output system (BIOS) that interacts with hardware of the special purpose computer, device drivers that interact with particular devices of the special purpose computer, one or more operating systems, user applications, background services, background applications, etc.
[0147] The computer programs may include: (i) descriptive text to be parsed, such as HTML (hypertext markup language), XML (extensible markup language), or JSON (JavaScript Object Notation), (ii) assembly code, (iii) object code generated from source code by a compiler, (iv) source code for execution by an interpreter, (v) source code for compilation and execution by a just-in-time compiler, etc. As examples only, source code may be written using syntax from languages including C, C++, C#, Objective C, Swift, Haskell, Go, SQL, R, Lisp, Java®, Fortran, Perl, Pascal, Curl, OCaml, JavaScript®, HTML5 (Hypertext Markup Language 5th revision), Ada, ASP (Active Server Pages), PHP (PHP: Hypertext Preprocessor), Scala, Eiffel, Smalltalk, Erlang, Ruby, Flash®, Visual Basic®, Lua, MATLAB, SIMULINK, and Python®.