Corneal biomechanical properties in vernal keratoconjunctivitis and its subtypes: a preliminary study

International Ophthalmology(2022)

Cited 1|Views5
No score
Abstract
Purpose To explore the corneal biomechanical properties (CBPs) of patients with vernal keratoconjunctivitis (VKC) and the discrepancies among three subtypes of VKC including palpebral, limbal, and mixed forms. Methods Forty eyes of 20 VKC patients and twenty eyes of ten non-VKC patients were included in this case–control study. Patients with VKC were further divided into three subtypes (six patients in Palpebral form, five patients in limbal form, and nine patients in mixed form). The CBPs of all patients were obtained from the Corneal Visualization Scheimpflug Technology (Corvis ST). Results First applanation (A1) length, Ambrosio relational thickness in horizontal (ARTh), and stiffness parameter at first applanation (SP-A1) were significantly lower in the VKC group while A1 velocity was significantly higher in the VKC group ( p < 0.05), compared to the non-VKC group. Furthermore, A1 velocity presented a positive correlation with disease course ( p < 0.05). In addition, VKC patients of limbal form had lower central corneal thickness (CCT), SP-A1, and higher deformation amplitude ratio (DA ratio), compared to the other two subtypes ( p < 0.05). Besides, patients in limbal form had higher A1 velocity, integrated radius, and corneal biomechanical index (CBI) compared with mixed form, and lower A1 length than palpebral form ( p < 0.05). Conclusions The corneas of VKC patients were softer and more protruded compared with the control group, and the property of steepness was closely related to disease course. VKC patients in limbal form were more inclined to be keratoconus than the other two subtypes due to their CBPs` discrepancies.
More
Translated text
Key words
Vernal keratoconjunctivitis,Corneal biomechanical properties,Corvis ST,Keratoconus
AI Read Science
Must-Reading Tree
Example
Generate MRT to find the research sequence of this paper
Chat Paper
Summary is being generated by the instructions you defined