Embodiments of this invention generally relate to systems and methods for wavefront interactive refraction display and more particularly to systems and methods for capturing and displaying eye wavefront interactive refraction data based on the desired refractive state of the patient's eye.
|
1. A method, comprising:
a scanning engine repeatedly collecting data, at a first resolution, indicative of a refractive state of a patient's eye over a period of time;
repeatedly ascertaining a current refractive state of the patient's eye from the repeatedly collected data indicative of the refractive state of the patient's eye;
continuously displaying an indication of the current refractive state of the patient's eye, the displayed indication of the current refractive state being continuously variable with time;
while displaying the indication of the current refractive state of the patient's eye, receiving from a user or the patient a command to capture additional data indicative of the refractive state of the patient's eye; and
in response to the command, the scanning engine capturing additional data, at a second resolution, indicative of the refractive state of the patient's eye, wherein the second resolution is greater than the first resolution; and
ascertaining a final refractive state of the patient's eye from the captured additional data indicative of the refractive state of the patient's eye.
11. A system, comprising:
a patient interface configured to display a target to a patient;
a scanning engine configured to obtain data indicative of a refractive state of a patient's eye;
a display device; and
a processor configured to:
cause the scanning engine to repeatedly collect data, at a first resolution, indicative of the refractive state of the patient's eye over a period of time;
repeatedly ascertain a current refractive state of the patient's eye from the repeatedly collected data indicative of the refractive state of the patient's eye;
cause the display device to continuously display an indication of the current refractive state of the patient's eye, the displayed indication of the current refractive state being continuously variable with time;
while displaying the indication of the current refractive state of the patient's eye, receive from a user or the patient a command to capture additional data indicative of the refractive state of the patient's eye; and
in response to the command, cause the scanning engine to capture additional data, at a second resolution, indicative of the refractive state of the patient's eye, wherein the second resolution is greater than the first resolution; and
ascertain a final refractive state of the patient's eye from the captured additional data indicative of the refractive state of the patient's eye.
2. The method of
3. The method of
4. The method of
receiving a task request from the user or the patient; and
in response to the received task request, providing an indicator of a first patient task to be performed by the patient.
5. The method of
6. The method of
7. The method of
8. The method of
changing a brightness of at least a portion of the target;
changing a color of at least a portion of the target;
changing a clarity of at least a portion of the target;
changing an image of the target; and
changing a size of the target.
9. The method of
receiving a second task request from the user or the patient; and
in response to the received second task request, providing an indicator of a second patient task to be performed by the patient, the second patient task being different than the first patient task.
10. The method of
13. The system of
14. The system of
15. The system of
17. The system of
18. The system of
receive a task request from the user or the patient; and
in response to the received task request, provide an indicator of a patient task to be performed by the patient.
19. The system of
20. The system of
|
This application is a continuation of and claims priority to U.S. patent application Ser. No. 14/996,112, filed on Jan. 14, 2016, Now U.S. Pat. No. 9,713,421 B2 which is a continuation of and claims priority to U.S. patent application Ser. No. 14/199,702, filed Mar. 6, 2014 and issued on Mar. 1, 2016 as U.S Pat. No. 9,271,646, which claims priority to U.S. Provisional Application No. 61/799,764, filed on Mar. 15, 2013, the entire contents of each of which are incorporated herein by reference.
Embodiments of the present invention generally relate to wavefront interactive refraction display and more particularly to systems and methods that capture and display eye wavefront interactive refraction data.
Refractive measurements of the eye should occur with the accommodation of the eye fully relaxed. To accomplish this, aberrometers move an internal visual target to draw the eye to its farthest focus. Then a final refractive measurement is made. When the target is at the optimal position, the target is “fogged” and it always appears slightly fuzzy to the patient. However, sometimes the eye does not respond to the target, and the final refractive measurement can occur with the eye partially accommodated. When this happens, the patient is said to exhibit “instrument myopia” and the target may either appear clear or fuzzy to the patient.
While most people respond reliably to the target inside an aberrometer, some patients persistently exhibit instrument myopia. Repeated measurements can fatigue the eye and the patient can exhibit increasing instrument myopia.
When patients are screened for LASIK treatment, they are measured both with a manifest refraction and with an aberrometer. Typically the manifest refraction is done first, and then the results are entered into the aberrometer software. If the wavefront and manifest refractions agree within some tolerance, the patient may be treated with wavefront guided LASIK. However, if the measurements disagree, the patient can only be treated with standard LASIK, based on the manifest refraction alone.
To ensure the greatest number of patients qualify for wavefront guided LASIK, the aberrometer should minimize instrument myopia, or provide some means to help the doctor to get the patient to relax their accommodation.
Doctors have a number of techniques they can use to coax a patient into relaxing accommodation. For instance, they can distract a patient by telling them to grip a handle, or mentally subtract two numbers. However, when the doctor employs such a technique, a standard measurement follows without any interactive feedback. Consequently the doctor has to wait many seconds to see if the desired effect occurred. If the effect of the coaxing was transitory, the software will still produce a measurement with instrument myopia. Also, coaxing takes time. Prolonged measurement sessions tend to fatigue the eye and often results in the patient showing increasing instrument myopia.
The field of the invention relates to systems and methods for wavefront interactive refraction display and more particularly to systems and methods that capture and display eye wavefront interactive refraction data. In an embodiment, a method for identifying a time for capturing eye refraction data includes sensing a waveform of light passing through a patient's eye over a period of time, wherein the waveform is affected by an optical property of the patient's eye, calculating the refractive state of the patient's eye with the sensed waveform, displaying an indication of the current refractive state of the patient's eye, receiving a command to capture eye refraction data when the desired refractive state of the patient's eye is reached, and capturing eye refraction data.
Further areas of applicability of the present disclosure will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description and specific examples, while indicating various embodiments, are intended for purposes of illustration only and are not intended to necessarily limit the scope of the disclosure.
The present disclosure is described in conjunction with the appended figures:
In the appended figures, similar components and/or features may have the same reference label. Where the reference label is used in the specification, the description is applicable to any one of the similar components having the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.
The ensuing description provides preferred exemplary embodiment(s) only, and is not intended to limit the scope, applicability or configuration of the disclosure. Rather, the ensuing description of the preferred exemplary embodiment(s) will provide those skilled in the art with an enabling description for implementing a preferred exemplary embodiment. It is understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope as set forth in the appended claims.
Wavefronts
A wavefront can be used to describe a wave including, for example, an electromagnetic wave. A wavefront is the locus of points having the same phase, and can be a line or curve in two dimensions, or surface of a wave that is propagating in three dimensions. Wavefront measurements can be used to evaluate the quality of an optical system and/or to identify imperfections in an optical system. In some embodiments, these measurements can be performed by a wavefront sensor which is a device that can measure wavefront aberration in a coherent signal. A Hartmann-Shack system is one embodiment of a wavefront sensor.
With reference now to
Wavefront interactive refraction display 100 includes an eye 102. The eye 102 can be any eye, and can be, for example, a human eye. The eye 102 includes the cornea 104, the lens 106, the retina 108, and the optic nerve 110.
Wavefront interactive refraction display 100 includes a wavefront interactive refractor 112. Wavefront interactive refractor 112 can be configured to generate data identifying a refractive state of the eye 102. In some embodiments, the wavefront interactive refractor 112 can generate data identifying a refractive state of the eye 102 by sensing a wavefront passing through the eye 102 either towards or away from the retina 108. In the embodiment depicted in
As seen in
In some embodiments, the wavefront interactive refractor 112 can comprise a patient interface that can include a patient output device 122 and a patient input device 124. In some embodiments, the patient output device 122 can provide information to the patient and can be, for example, a display and/or a speaker. In some embodiments, the patient output device 122 can provide information to the patient relating to one or several tasks that the patient can complete. In one embodiment, for example, the patient output device 122 can comprise a display with an image that is viewable by the patient.
The patient input device 124 can comprise any feature configured to allow the patient to provide an input to the wavefront interactive refractor 112. In some embodiments, the patient input device 124 can comprise a button, a key, a keypad, a microphone, or a sensor. The patient can, in some embodiments, use the patient input device 124 to complete the task which can include, for example, depressing a button when a specified change in the displayed image occurs.
With reference now to
In some embodiments, the processor 200 can be configured to be embedded in the wavefront interactive refractor 112 and to process full wavefront reconstructions. In some embodiments, this processor 200 can comprise a field programmable gate array (FPGA).
The wavefront interactive refractor 112 can include user interface 202. The user interface 202 communicates information, including outputs, to, and receives inputs from a user. The user interface 202 can include a screen, a speaker, a monitor, a keyboard, a microphone, a mouse, a touchpad, a keypad, and/or any other feature or features that can receive inputs from a user and provide information to a user. In some embodiments, the user interface 202 can provide outputs to, and receive inputs from a user including a doctor. In some embodiments, the user interface 202 can be configured to allow the user including the doctor to control the operation of the wavefront interactive refractor 112, and to specifically control the interaction of the wavefront interactive refractor 112 with the patient.
The wavefront interactive refractor 112 can include a patient interface 204. The patient interface 204 communicates information including outputs to a patient and receives information including inputs from a patient. In some embodiments, the patient interface 204 can communicate information to the patient via a patient visual display. The patient visual display can provide visual data to the patient. In some embodiments, the patient visual display can be generated by the patient output device 122, and specifically in embodiments in which the patient output device 122 comprises a display and/or screen, the patient visual display can be shown to the patient by the display and/or screen In some embodiments, the patient interface 204 can be configured to provide a patient with a task and, in some embodiments, to receive inputs corresponding to the patient completion of the task. The patient interface 204 can comprise a screen, a speaker, a button, monitor, a keyboard, a microphone, a mouse, a touchpad, a keypad, and/or any other feature or features that can receive patient inputs and provide information to the patient.
The wavefront interactive refractor 112 can comprise communication engine 206. The communication engine 206 can allow the wavefront interactive refractor 112 to communicatingly connect with other devices, and can allow the wavefront interactive refractor 112 to send and receive information from other devices. The communication engine 206 can include features configured to send and receive information, including, for example, an antenna, a modem, a transmitter, receiver, or any other feature that can send and receive information. The communication engine 206 can communicate via telephone, cable, fiber-optic, or any other wired communication network. In some embodiments, the communication engine 206 can communicate via cellular networks, WLAN networks, or any other wireless network.
The wavefront interactive refractor 112 includes a scanning engine 208. In some embodiments, for example, the scanning engine 208 can be configured to generate data corresponding to the refraction state of the patient's eye 102. In some embodiments, for example, the scanning engine 208 can be configured to generate the beam 113, and to direct the beam 113 onto the retina 108 of the patient's eye 102. In some embodiments, the scanning engine 208 can be further configured to capture the light rays 114, 116 reflecting off the retina 108 of the patient's eye 102 and passing through the lens 106 and the cornea 104 of the patient's eye 102. In some embodiments, the scanning engine 208 can be configured to generate data corresponding to the wavefront of the light rays 114, 116 and/or of the light passing through the patient's eye 102, which data can be used to determine the refractive state of the patient's eye 102.
In some embodiments, the scanning engine 208 can comprise a camera and can be configured to capture image data of the eye 102. In some embodiments, image data for one or several images captured by the scanning engine 208 can be stored and used to generate a full wavefront reconstruction of the eye 102.
In some embodiments, the scanning engine 208 can include features configured to perform wavefront analysis on the eye 102, which features can include a wavefront sensor. In one embodiment, the wavefront sensor can be an optical capture device which can be any device with light sensing components and can be, for example, a camera and/or scanner. The wavefront sensor can comprise a plurality of photoreceptors which can be, for example, arranged into a matrix of photoreceptors. The wavefront sensor can further comprise an array of lenslets, mirrors, and/or any other features capable of reflecting and/or refracting light. In one embodiment, each lenslet and/or mirror can be associated with the subset of photoreceptors from the matrix of photoreceptors. In one embodiment, for example, each of the lenslets and/or mirrors can be associated with a group of four photoreceptors. In one embodiment, for example, the wavefront sensor can comprise a Hartmann-Shack system.
The wavefront interactive refractor 112 can include memory 210. The memory 210 can include stored instructions that, when executed by the processor 200, control the operation of the wavefront interactive refractor 112. The details of the memory 210 are discussed at greater length below.
As seen in
In some embodiments, the task database 212 can comprise an index of tasks included in the task database. This index can include, for example, data corresponding to the instruction, the stimulus, and/or desired inputs, and/or user instructions to allow the user to facilitate the completion of the task by the patient.
The scan database 214 can comprise information generated by the scanning engine 208 and/or data related to information generated by the scanning engine 208. In some embodiments, for example, the information generated by the scanning engine 208 can include information identifying the refractive state of the eye 102, information tracking the refractive state of the eye 102 as a function of time, information identifying turning points including, for example, maximums and minimums, and/or inflection points in the data tracking the refractive state of the eye 102 as a function of time, task, and/or pupil size. In some embodiments, the scan database 214 can further include information relating to a patient including, for example, information identifying the patient, information associating a patient with information generated by the scanning engine 208, information associating a patient with previously gathered information relating to the refractive state of the eye, and/or any other desired patient information.
With reference now to
The target can be changed in a variety of ways to stimulate relaxation of the eye 102 and to facilitate in generating data relating to the refractive state of the eye 102. In some embodiments, the target 302 can be moved laterally with respect to the patient's eye 102 and in some embodiments, the target 302 can be moved relatively closer to and/or relatively further from the patient's eye 102. In some embodiments, the visual distance to the target 302 can be changed. This can be accomplished by manipulating the wavefront of the target 302 from a first wavefront to a second wavefront, which first wavefront mimics the wavefront of an object located at a first distance from the patient's eye 102 and the second wavefront mimics the wavefront of an object located at a second distance from the patient's eye 102.
In some embodiments, the target 302 can be adjustable so as to have a different size, shape, and/or color. In some embodiments, the brightness, contrast, and/or focus of the target 302 can be changed. In some embodiments, the target 302 can be changed from a first image to a second, and in some embodiments, the image of the target 302 can be changed as many times as desired.
The target 302 can be any desired image and/or object and/or any desired type of image and/or type of object. In some embodiments, the target 302 can comprise a point of light having any desired shape. In some embodiments, the target 302 can comprise, for example, a crosshair as depicted in
As seen in
Patient visual display 300 can, in some embodiments, provide an indicator 306 of the refractive state of the patient's eye 102. In some embodiments, for example, the indicator 306 of the refractive state of the patient's eye 102 can provide an indication of the absolute refractive state of the patient's eye 102 and/or of the relative refractive state of the patient's eye 102. In some embodiments, for example, the indicator 306 of the refractive state of the patient's eye 102 can provide information regarding the refractive state of the patient's eye 102 versus time, the refractive state of the patient's eye 102 versus task, the refractive state of the patient's eye 102 versus pupil size, and/or the refradctive state of the patient's eye 102 versus any other desired and changing parameter.
In some embodiments, the indicator 306 can further comprise an indicator of the size of the pupil of the patient's eye 102 that can be separate from the indicator 306 of the refractive state of the patient's eye 102 and/or integral in the indicator 306 of the refractive state of the patient's eye 102. In some embodiments, for example, this indicator of the pupil size can comprise a plot of pupil size versus time, and in some embodiments, the indicator of the pupil size can comprise a color scheme of the indicator 306 of the refractive state of the patient's eye 102. Thus, in some embodiments, the indicator 306 of the refractive state of the patient's eye 102 can comprise a first color when the pupil is an undesireable size, and a second color when the pupil is a desireable color. In some embodiments, for example, the color scheme can further comprise a third color indicative of the occurrence of a desired change in the pupil size, and a fourth color indicative of the occurrence of an undesired change in the pupil size.
In the embodiment depicted in
The fluctuations in the focus of the eye are known to be divided into two different frequency regimes. These are the low frequency component (LFC) and the high frequency component (HFC). The low frequency component occurs at rates of about 5 hertz or slower and can be thought of as being the change in focus that occurs when a person is observing a visual field under conscious control or awareness. The low frequency changes can vary from far to near focus through the entire range of focus that the eye can achieve. The high frequency component occurs at a faster rate of about 10 hertz or faster and it is associated with small changes in focus. This is also sometimes called focus tremor. The focus tremor is automatic and unconscious. It is thought that these micro-fluctuations are used by the eye to assist the nervous system in achieving a desired focus on a target. It has been reported in the literature that when the eye has approached the extreme ends of its focus range, either the most near or the most far focus, that the amplitude of the HFC becomes diminished. Thus a reduction in HFC can be seen as an indicator of when an eye has reached its most fully relaxed state. So it would be useful for a doctor to be able to view an indicator showing the strength of the HFC. The speed of the HFC can exceed the rate at which a standard computer software will update a display. So it would be beneficial for the software to collect and analyze high speed data, taken for instance at 30 hertz, and then display at a slower rate an indication of the amplitude of the micro fluctuations during a prescribed time period, for instance over 0.2 seconds. Such an metric may simply be the difference between the maximum and minimum values of the spherical equivalent seen during the time period. More sophisticated metrics, such as a root mean square value may be useful as well,
In some embodiments of the wavefront interactive refractor 112, the status indicator 308 can be continually updated to reflect the current refractive state of the patient's eye 102 during the time period in which the scanning engine 208 collects data relating to the refractive state of the patient's eye 102. Thus, the status indicator 308 can, during operation of the scanning engine 208, continually adjust upward down as the refractive state of the patient's eye 102 changes. In one particular embodiment, for example, a more hyperopic refraction can result in the status indicator 308 becoming taller and/or larger, and a less hyperopic refraction can result in the status indicator 308 becoming shorter and/or smaller. In some embodiments, the status indicator 308 can indicate and/or identify a time for capturing data indicating the refractive state of the patient's eye 102 when the status indicator 308 reaches and/or surpasses the goal indicator 310.
The goal indicator 310 can comprise a visual indication of a minimum desired refractive state to be achieved before capturing the refractive state of the eye 102. In some embodiments, the goal indicator 310 can be a specific goal indicator, and in some embodiments, the goal indicator 310 can be a general goal indicator. In embodiments in which the goal indicator 310 is a general goal indicator, the goal indicator can represent a value that is nonspecific to the patient and can, for example, represent an average refractive state of eyes in a population that can, for example, the defined by age, gender, race, health, or any other desired parameter. In some embodiments, the goal indicator 310 can comprise a threshold value associated with the treatment procedure. In some embodiments in which the goal indicator 310 is a specific goal parameter, the goal indicator 310 can be generated based on an aspect of the patient data. In some embodiments, this can include the most desirable refractive state of the patient's eye exhibited over the course of evaluation of the patient's eye 102 with the wavefront interactive refractor 112, the refractive state of the patient's eye 102 that was measured during another and/or previous test such as, the manifest refraction, and/or the refractive state of the patient's eye 102 that was collected during the performance of a specific task. The goal indicator 310 can comprise any feature and/or image that allows the patient and/or user to ascertain whether the current refractive state of the patient's eye 102 is more or less desirable than the threshold and/or level indicated by the goal indicator 310.
With reference now to
As seen in
As also seen in
In some embodiments, the user visual display 400 can comprise a button 408 that allows the user to provide to request the capture of the refractive state of the patient's eye 102. In some embodiments, the button 408 can be a selectable icon located within the user visual display 400, and in some embodiments, the button 408 can comprise any other feature configured to provide an input to the wavefront interactive refractor 112. In some embodiments, a feature of the button can change to identify a time for capturing refractive state data for the patient's eye 102. In some embodiments, for example, these changes can include a change in the size, color, shape, illumination, and/or appearance of the button 408. In some embodiments, for example, the button can be a first color, such as, for example, yellow when refractive state data is first collected, which color can indicate that there is insufficient data to provide trend information relating to the refractive state of the eye 102. In some embodiments, a desired trend in the refractive state data can be indicated by a second color, such as, for example, green, of the button 408, and an undesired trend in the refractive state data can be indicated by a third color such as, for example, red, of the button 408.
With reference now to
As seen in
With reference now to
The embodiment depicted in
With reference now to
After the data indicative of the refractive state of the eye 102 is collected, the process 600 proceeds to block 604 wherein the refractive state of the eye 102 is calculated. In some embodiments, for example, the calculation the refractive state of the eye 102 can include processing the data indicative of the refractive state of the eye 102 with a component of the wavefront interactive refractor 112 such as, for example, the processor 200. In some embodiments, for example, this calculation can be based on a full wavefront reconstruction, and in some embodiments this calculation can be performed using the Zernike slope dot-product, which can provide the sphere, cylinder, and axis of the patient's eye 102.
After the refractive state of the eye 102 is calculated, the process 600 proceeds to block 606 wherein an indicator of the refractive state of the eye 102 is displayed. In some embodiments, for example, this indicator of the refractive state of the eye 102 can comprise the indicator 306 discussed at greater length in
After the indicator of the refractive state of the eye is displayed, the process 600 proceeds to decision state 608 wherein it is determined whether to capture data indicative of the refractive state of the eye 102. In some embodiments, for example, the capture of data indicative of the refractive state of the eye 102 can differ from the collection of data indicative of the refractive state of the eye 102 in that the capture data can comprise a definitive measure of the refractive state of the patient's eye 102. In some additional embodiments, the captured data indicative of the refractive state of the eye 102 can differ from the collected data indicative of the refractive to the eye 102 in that the captured data indicative of the refractive state of the eye 102 is stored.
In some embodiments, the wavefront interactive refractor 112 can receive an indication from the user and/or patient to capture data indicative of the refractive state of the eye. In some embodiments, for example, this indication can be provided to the wavefront interactive refractor with button 408 or any other feature of the user interface 202 and/or patient interface 204 configured to initiate capture of the refractive state of the patient's eye 102. If it is determined not to capture data indicative of the refractive student the eye 102, then the process 600 can return to block 602 and continue the collection of data indicative of the refractive state of the eye.
If it is determined to capture data indicative of the refractive state of the eye 102, then the process 600 proceeds to block 610 wherein data indicative of the refractive state of the eye 102 is captured. In some embodiments, this capture can proceed in the same manner as outlined above with respect to block 602.
In some embodiments, data indicative of the refractive state of the eye 102 can be captured immediately after it is determined to capture data relating to the refractive state of the eye 102, and in some embodiments, a set of data before and/or after it is determined to capture data relating to the refractive state of the eye 102 can be captured. In some embodiments, this data can include the refractive state of the patient's eye 0.5 seconds, 1 second, 2 seconds, 3 seconds, 4 seconds, 5 seconds, 10 seconds, and/or any other or intermediate time before and/or after it is determined whether to capture data relating to the refractive state of the eye 102. In some embodiments, this data can be analyzed to determine the most desired refractive state of the eye 102 in the captured data.
In some embodiments, in contrast to the collection of data indicative of the refractive state of the eye 102, the scanning engine 208 can be configured to operate at a higher resolution and/or with greater accuracy when capturing data indicative of the refractive state of the eye 102 than when collecting data indicative of the refractive state of the eye as discussed to block 602. In some embodiments, for example, the lower resolution of the data gathered by the scanning engine 208 during the collection of data indicative of the refractive state of the eye 102 can facilitate accelerating the calculation of the refractive state of the eye to thereby more quickly update the indicator 306 with data reflecting the current refractive state of the eye 102.
In some embodiments, the data indicative of the refractive state of the eye 102 captured in block 610 can be stored in the memory 210 of the wavefront interactive refractor 112 including, for example, in the scan database 214 of the memory 210 of the wavefront interactive refractor 112. In some embodiments, for example, this captured data can be associated with the patient, the patient's eye, the user, the time and/or date that the data was captured, and/or any other desired information.
After the data indicative of the refractive state of the eye is captured, the process 600 proceeds to block 612 wherein the refractive state of the eye 102 is calculated. In some embodiments, this calculation can be performed in the same manner as described with respect to block 604, but in embodiments in which the resolution and/or accuracy of the captured data indicative of the refractive state of the eye is greater than the resolution and/or accuracy of the collected data indicative of the refractive state of the eye 102, this calculation can likewise provide more accurate and better resolution in the calculation results.
In some embodiments, for example, the calculation the refractive state of the eye can include processing the data indicative of the refractive state of the eye with a component of the wavefront interactive refractor 112 such as, for example, the processor 200. In some embodiments, for example, this calculation can be based on a full wavefront reconstruction, and in some embodiments this calculation can be performed using the Zernike slope dot-product, which can provide the sphere, cylinder, and axis of the patient's eye 102. Is calculated refractive the state of the eye can be stored in the memory 210 of the wavefront interactive refractor 112 including, for example, in the scan database 214 of the memory 210 of the wavefront interactive refractor 112. In some embodiments, for example, this capture data can be associated with the patient, the patient's eye, the user, the time and/or date that the data was captured, and/or any other desired information.
After the refractive state of the eye 102 is calculated, the process proceeds to block 614 wherein an indicator of the refractive state of the eye 102 is provided. In some embodiments this indicator can be provided via the user and/or patient interface 202, 204 or via the communication engine 206 to another device.
With reference now to
After the request for refractive state data collection has been received, the process 700 proceeds to block 704 wherein the collecting of data indicative of the refractive state of the eye 102 is started. In some embodiments, for example, the collection of data indicative of the refractive state of the eye 102 can be continuously performed until the process 700 terminates and/or until an input is received requesting the ending of the collection of that data.
In some embodiments, for example, this data can be collected by the scanning engine 208. In some embodiments, this data indicative of the refractive state of the patient's eye 102 can be collected by measuring a wavefront of light passing through the patient's eye 102. The details of how this wavefront of light can be generated are discussed at greater length above with respect to
After the collecting of data indicative of the refractive state of the eye 102 is started, the process 700 proceeds to block 706 wherein the calculation of the refractive state of the eye 102 is started. In embodiments in which data indicative of the refractive state of the eye 102 is continuously and/or repeatedly collected, the refractive state of the eye 102 can likewise be continuously and/or repeatedly calculated. Advantageously, this continuous and/or repeated calculation of the refractive state of the eye 102 can allow display of more accurate information relating to the current refractive state of the eye 102.
In some embodiments, for example, the calculation of the refractive state of the eye 102 can include processing the data indicative of the refractive state of the eye with a component of the wavefront interactive refractor 112 such as, for example, the processor 200. In some embodiments, for example, this calculation can be based on a full wavefront reconstruction, and in some embodiments this calculation can be performed using the Zernike slope dot-product, which can provide the sphere, cylinder, and axis of the patient's eye 102.
After the calculating of the refractive state of the eye 102 is started, the process 700 proceeds to block 708 wherein an indicator of the wavefront interactive refractor alignment is provided. In some embodiments, for example, this indicator of the wavefront interactive refractor alignment can comprise the alignment indicator 402 depicted in
After the indicator of the alignment of the wavefront interactive refractor 112 has been provided, the process 700 proceeds to block 710 wherein an indicator of the refractive state of the eye 102 is provided. In some embodiments, for example, this indicator of the refractive state of the eye 102 can comprise the indicator 306 discussed at greater length in
After an indicator of the refractive state of the eye 102 is provided, the process proceeds to block 712 wherein a task request is received. In some embodiments, for example, the patient and/or user can request a task to facilitate the achievement of the desired refractive state of the eye 102. In some embodiments, this task can be configured to provide the patient with a distraction so as to encourage relaxation of the accommodation of the eye 102. In some embodiments, the task request can be received by the user interface 202, the patient interface 204, and/or the communication engine 206.
After the task request is received, the process 700 proceeds to block 714 wherein an indicator of the task is provided. In some embodiments, for example, the indicator of the task can comprise a task indicator 304 discussed at length above. In some embodiments, the indicator of the task can be configured to provide information to the patient and/or user relating to the task and how to complete the task. In some embodiments, the indicator of the task can be displayed to the patient via the patient visual display 300 and/or to the user via the user visual display 400.
After the indicator of the task is provided, the process 700 proceeds to block 716 wherein a task input is received. In some embodiments, the task input can comprise an indicator of the performance and/or completion of the task by the patient and/or user. In some embodiments, for example, the task input can be provided to the wavefront interactive refractor 112 via, for example, the user interface 202 and/or the patient interface 204. In some embodiments, for example, the task input can be provided by the patient input device 124.
After the task input has been received, the process proceeds to decision state 718 wherein it is determined if there is an additional task. In some embodiments, this determination can include querying the task database 212 to determine whether all of the tasks have been provided to the patient and/or user. If it is determined that there are additional tasks, then the process can return to block 712. If it is determined that there are no additional tasks, or at any other point in process 700, the wavefront interactive refractor 112 can receive a request to capture data indicative of the refractive state of the eye 102. This request can be provided by the patient and/or user to the wavefront interactive refractor 112 via the user interface 202, the patient interface 204, and/or the communication engine 206.
After the request to capture data indicative of the refractive state of the eye 102 is received, the process 700 proceeds to block 722 wherein data indicative of the refractive state of the eye 102 is captured. In some embodiments, this capture can proceed in the same manner as outlined above with respect to block 704. In some embodiments, in contrast to the collection of data indicative of the refractive state of the eye 102, the scanning engine 208 can be configured to operate at a higher resolution and/or with greater accuracy when capturing data indicative of the refractive state of the eye 102 than when collecting data indicative of the refractive state of the eye 102 as discussed in block 704. In some embodiments, for example, the lower resolution of the data gathered by the scanning engine 208 during the collection of data indicative of the refractive state of the eye 102 can facilitate decreasing the time required for the calculation of the refractive state of the eye 102 which can thereby allow faster updates of the indicator 306 with data reflecting the current refractive state of the eye 102.
In some embodiments, the data indicative of the refractive state of the eye 102 captured in block 722 can be stored in the memory 210 of the wavefront interactive refractor 112 including, for example, in the scan database 214 of the memory 210 of the wavefront interactive refractor 112. In some embodiments, for example, this captured data can be associated with the patient, the patient's eye 102, the user, the time and/or date that the data was captured, and/or any other desired information.
After the data indicative of the refractive state of the eye 102 is captured, the process 700 proceeds to block 724 wherein the refractive state of the eye 102 is calculated. In some embodiments, this calculation can be performed in the same manner as described with respect to block 706, but in embodiments in which the resolution and/or accuracy of the captured data indicative of the refractive state of the eye 102 is greater than the resolution and/or accuracy of the collected data indicative of the refractive state of the eye 102, this calculation can likewise provide more accurate and better resolution in the calculation results.
In some embodiments, for example, the calculation the refractive state of the eye can include processing the data indicative of the refractive state of the eye with a component of the wavefront interactive refractor 112 such as, for example, the processor 200. In some embodiments, for example, this calculation can be based on a full wavefront reconstruction, and in some embodiments this calculation can be performed using the Zernike slope dot-product, which can provide the sphere, cylinder, and axis of the patient's eye 102. Is calculated refractive the state of the eye can be stored in the memory 210 of the wavefront interactive refractor 112 including, for example, in the scan database 214 of the memory 210 of the wavefront interactive refractor 112. In some embodiments, for example, this captured data can be associated with the patient, the patient's eye 102, the user, the time and/or date that the data was captured, and/or any other desired information.
After the refractive state of the eye 102 is calculated, the process 700 proceeds to block 726 wherein an indicator of the refractive state of the eye 102 is provided. In some embodiments this indicator can be provided via the user and/or patient interface 202, 204 or via the communication engine 206 to another device.
With reference now to
The process 800 begins at block 802 wherein the steps discussed in blocks 702 through 710 of
After the task request is received, the process 800 proceeds to block 806 wherein an indicator of the task is provided. In some embodiments, for example, the indicator of the task can comprise a task indicator 304 discussed at length above. In some embodiments, the indicator of the task can be configured to provide information to the patient and/or user relating to the task and how to complete the task. In some embodiments, the indicator of the task can be displayed to the patient via the patient visual display 300 and/or to the user via the user visual display 400.
After the indicator of the task is provided, the process 800 proceeds to block 808 wherein a task input is received. In some embodiments, the task input can comprise an indicator of the performance and/or completion of the task by the patient and/or user. In some embodiments, for example, the task input can be provided to the wavefront interactive refractor 112 via, for example, the user interface 202 and/or the patient interface 204. In some embodiments, for example, the task input can be provided by the patient input device 124.
After the task input has been received, the process 800 proceeds to decision state 810 wherein it is determined if there is an additional task. In some embodiments, this determination can include querying the test database 212 to determine whether all of the tasks have been provided to the patient and/or user. If it is determined that there are additional tasks, then the process can return to block 804.
If it is determined that there are no additional task, then the process 800 can proceed to block 812 and aggregate the collected data indicative of the refractive state of the eye 102. In some embodiments, for example, the aggregation of the collected data indicative of the refractive state of the eye 102 can include ending the collection of data indicative of the refractive state the eye 102, and in some embodiments the collection of data indicative of the refractive state of the eye 102 can continue during the aggregation of the collected data indicative of the refractive state of the eye 102. In some embodiments, for example, in which the collection of data continues after the aggregation of the collected data is started, the aggregation can be, for example, limited to data collected before the start of the aggregation, and in some embodiments, the aggregation may not be limited to any data set, but may rather update as additional data is received.
In some embodiments, the aggregation of the collected data can be performed by a component of the wavefront interactive refractor 112 such as, for example, the processor 200 and/or the memory to 10 including the test database 212 and/or the scan database 214. In some embodiments, for example, collected data indicative of the refractive state of the eye 102 can be retrieved from the memory 210 including, for example, the test database 212 and/or the scan database 214.
After the collected data has been aggregated the process 800 proceeds to block 814 wherein provided task are correlated with the collected data. In some embodiments, this correlation can include providing an indicator in the time sequence of the refractive state of the patient's eye as to the perform task was started and/or when the perform task was completed. In some embodiments, this correlation of the provided tasks with the collected data can further include correlating any detected action performed using the wavefront interactive refractor 112 with the time sequence of the refractive state of the patient's eye 102. This can include, for example, any change to the alignment of the eye 102 with respect to the wavefront interactive refractor 112 and/or any non-task related change to the target 302 and/or to the patient visual display 300.
After the tasks are correlated to the data, the process 800 proceeds to block 816 wherein maximums and minimums in the aggregated data indicative of the refractive state of the eye 102 are identified. In some embodiments, for example, the identification of the one or several maximums and/or minimums can be performed by a component of the wavefront interactive refractor 112 including, for example, the processor 200.
After the minimums and/or maximums in the aggregated data indicative of the refractive state of the eye 102 are identified, the process 800 proceeds to block 818 wherein tasks associated with the minimums and maximums identified. In some embodiments, for example, this can include determining the task associated with the time in which a minimum and/or maximum was achieved and/or determining the task that is temporally most proximate to the time at which a minimum and/or maximum was achieved.
In some embodiments, for example, the calculated minimums and/or maximums associated with the aggregated data indicative of the refractive state of the patient's eye 102 can be compared against the desired refractive state of the patient's eye 102.
After the tasks associated with the minimums and/or maximums identified, the process proceeds to block 820 wherein an indicator of one or several tasks associated with the desired refractive state of the eye 102 is provided. In some embodiments, for example, the identified minimums and/or maximums can be compared to the desired refractive state of the eye 102. This comparison can allow the identification of tasks resulting in a refractive state of the eye 102 that is most desired, meets the desired refractive state of the eye 102, and/or comes closest to meeting the desired refractive state of the eye 102. In some embodiments, this information can be provided to the user and/or patient via, for example, via a component of the user interface 202 such as, for example, the user visual display 400 and/or via a component of the patient interface 204 such as, for example, the patient visual display 300.
In some embodiments, after the tasks associated with minimums and/or maximums identified, this information can be provided to the test database 212. This information can be used to create a task list in the task database 212, which task list is specific to the patient and can be used to facilitate the identification of a time for capturing eye refraction data, and/or for capturing eye refraction data when the eye is in a desired refractive state. In such an embodiment, the process 800 can proceed to block 712 of
With reference now to
With reference now to
The change of the target 302 can be controlled by a component of the wavefront interactive refractor 112 including, for example, the processor 200, and in some embodiments, the change the target 302 can be controlled by the user and/or patient via the user interface 202 and/or the patient interface 204. The list 1000 of changes to the target 302 can include, for example, a change of the target image such as, for example, changing from a crosshair target 302 to a landscape scene target 302, a change of a feature of the target 302, a change of a color of all or a portion of the target 302. In some embodiments, changing the color of the target can simulate motion of the target 302 as different colors of light focus at different distances in the eye 102.
As seen in
In some embodiments, for example, as the focus of the target 302 decreases and/or as the distance to the target 302 increases, the brightness of the target 302 can also be increased to affect a change in the refractive state of the eye 102. As discussed above some pupil sizes can be desired. In such an embodiment, the benefits of increasing the brightness of the target as measured by the increased relaxation of the accommodation of the patient's eye can be weighed against the detriments of increasing the brightness of the target 302 as measured by the decreased pupil diameter.
In some embodiments, the effects of the change in pupil size, such as caused by the change in the brightness of the target 302, can be compensated for in calculating the refractive state of the eye 102. Specifically, for example, the spherical equivalent of the eye 102 varies with pupil diameter, which pupil diameter varies with time. Specifically, in some embodiments, the spherical equivalent of the eye 102 can get very large when the pupil exceeds diameters of, for example, 4 mm, 5 mm, 6 mm or 8 mm. As it may, in some embodiments, be advantageous for the indicator 306 of the refractive state of the eye 102 to display the accomodative state of the eye 102 independent of the size of the pupil, the calculation of the refractive state of the eye 102 can use a corrective aspect to adjust for the varying size of the pupil diameter, especially when the brightness of the target 302 is varied. In some embodiments, for example, this corrective aspect can comprise a Seidel correction that includes the spherical aberration term, and in some embodiments, the calculation can be based on a particular analysis diameter, which diameter can be chosen to be the diameter that provides the best match when comparing the measured refractive state of the eye 102 with the goal parameter associated with the goal indicator 310.
As seen in
A number of variations and modifications of the disclosed embodiments can also be used. Specific details are given in the above description to provide a thorough understanding of the embodiments. However, it is understood that the embodiments may be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
Implementation of the techniques, blocks, steps and means described above may be done in various ways. For example, these techniques, blocks, steps and means may be implemented in hardware, software, or a combination thereof. For a hardware implementation, the processing units may be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described above, and/or a combination thereof.
Also, it is noted that the embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a swim diagram, a data flow diagram, a structure diagram, or a block diagram. Although a depiction may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed, but could have additional steps not included in the figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination corresponds to a return of the function to the calling function or the main function.
Furthermore, embodiments may be implemented by hardware, software, scripting languages, firmware, middleware, microcode, hardware description languages, and/or any combination thereof. When implemented in software, firmware, middleware, scripting language, and/or microcode, the program code or code segments to perform the necessary tasks may be stored in a machine readable medium such as a storage medium. A code segment or machine-executable instruction may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a script, a class, or any combination of instructions, data structures, and/or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, and/or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.
For a firmware and/or software implementation, the methodologies may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. Any machine-readable medium tangibly embodying instructions may be used in implementing the methodologies described herein. For example, software codes may be stored in a memory. Memory may be implemented within the processor or external to the processor. As used herein the term “memory” refers to any type of long term, short term, volatile, nonvolatile, or other storage medium and is not to be limited to any particular type of memory or number of memories, or type of media upon which memory is stored.
Moreover, as disclosed herein, the term “storage medium” may represent one or more memories for storing data, including read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and/or other machine readable mediums for storing information. The term “machine-readable medium” includes, but is not limited to portable or fixed storage devices, optical storage devices, and/or various other storage mediums capable of storing that contain or carry instruction(s) and/or data.
While the principles of the disclosure have been described above in connection with specific apparatuses and methods, it is to be clearly understood that this description is made only by way of example and not as limitation on the scope of the disclosure.
Neal, Daniel R., Raymond, Thomas D., Farrer, Stephen W., Copland, Richard J., Voss, Larry B., Hamrick, Daniel R., Rammage, Ron R., Dixson, John G., Riera, Phillip
Patent | Priority | Assignee | Title |
Patent | Priority | Assignee | Title |
5963300, | Feb 17 1998 | Novartis AG | Ocular biometer |
6413251, | Mar 13 2000 | Memphis Eye & Cataract Associates Ambulatory Surgery Center | Method and system for controlling a digital mircomirror device for laser refractive eye surgery |
6500171, | Mar 13 2000 | Memphis Eye & Cataract Associates Ambulatory Surgery Center | System for generating ablation profiles for laser refractive eye surgery |
WO167977, | |||
WO2012154278, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
May 13 2014 | COPLAND, RICHARD J | Amo Wavefront Sciences, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 043048 | /0481 | |
May 13 2014 | HAMRICK, DANIEL | Amo Wavefront Sciences, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 043048 | /0481 | |
May 13 2014 | RAYMOND, THOMAS D | Amo Wavefront Sciences, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 043048 | /0481 | |
May 13 2014 | FARRER, STEPHEN W | Amo Wavefront Sciences, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 043048 | /0481 | |
May 19 2014 | NEAL, DANIEL | Amo Wavefront Sciences, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 043048 | /0481 | |
May 19 2014 | DIXSON, JOHN | Amo Wavefront Sciences, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 043048 | /0481 | |
May 19 2014 | RIERA, PHILLIP | Amo Wavefront Sciences, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 043048 | /0481 | |
May 19 2014 | RAMMAGE, RON | Amo Wavefront Sciences, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 043048 | /0481 | |
May 22 2014 | VOSS, LARRY B | Amo Wavefront Sciences, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 043048 | /0481 | |
Jul 19 2017 | Amo Wavefront Sciences, LLC | (assignment on the face of the patent) | / | |||
Dec 17 2019 | Amo Wavefront Sciences, LLC | AMO Development, LLC | MERGER SEE DOCUMENT FOR DETAILS | 053803 | /0596 |
Date | Maintenance Fee Events |
May 25 2022 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Date | Maintenance Schedule |
Dec 11 2021 | 4 years fee payment window open |
Jun 11 2022 | 6 months grace period start (w surcharge) |
Dec 11 2022 | patent expiry (for year 4) |
Dec 11 2024 | 2 years to revive unintentionally abandoned end. (for year 4) |
Dec 11 2025 | 8 years fee payment window open |
Jun 11 2026 | 6 months grace period start (w surcharge) |
Dec 11 2026 | patent expiry (for year 8) |
Dec 11 2028 | 2 years to revive unintentionally abandoned end. (for year 8) |
Dec 11 2029 | 12 years fee payment window open |
Jun 11 2030 | 6 months grace period start (w surcharge) |
Dec 11 2030 | patent expiry (for year 12) |
Dec 11 2032 | 2 years to revive unintentionally abandoned end. (for year 12) |