Patients undergoing LASIK for myopia develop dry eye with compromised tear function at least 6 months after surgery. Women and patients requiring higher refractive correction have an increased risk for developing dry eye.

Introduction The decision to start insulin therapy is often difficult. Determining the barriers against insulin therapy initiation can facilitate care and treatment strategies. The aim of this study was to evaluate the barriers against initiating insulin therapy among patients with diabetes living in Yazd, Iran. Methods This descriptive study was conducted on 214 patients referred to the Diabetes Center of Yazd University of Medical Sciences in 2015. Participants were randomly selected, and then they completed the insulin noncompliance questionnaire (20 questions). The percentage of adherence and the factors contributing to nonadherence to insulin therapy were analyzed using descriptive statistics, the Kruskal–Wallis test, and the Mann–Whitney test. Results The most prevalent reason for insulin therapy refusal was expecting a new method of diabetes treatment (54.7%), followed by requiring someone else to administer the injection (19.2%), fear of needles, cost, traveling (18.7%), and stress/emotional problems (18.2%). Lack of trust in the physician was the least restrictive reason for nonadherence to insulin therapy. Conclusion The most common reason given for insulin therapy refusal was the lack of adequate education. Therefore, specialized educational interventions can help minimize barriers and improve patients’ outcomes.

Previously, we have proposed a computational model for decision-making in crisis situations called C-RPD (Computational Recognition Primed Decision). In this paper, a software development process customized for Crisis Situations Decision-Making Systems (CSDMSs) is proposed. Agile processes can skillfully manage uncertainty in software requirements and some of their features like incremental development can solve some problems in developing CSDMSs. However, these processes do not provide comprehensive solutions for issues like the lack of enough knowledge about CSDMSs, very rapid changes, urgent need to overcome security challenges, high development unpredictability, and the performance test. Extreme Programming (XP) is one of the best and most widely-used agile processes. In this article, a customized version of XP called Crisis Situations Decision-Making Systems Software Development Process (CSDP) is proposed. Standing first and second in five national and international RoboCup rescue agent simulation tournaments from 2006 to 2010 bear witness to the efficiency of the developed software using CSDP. Relying on its characteristics, CSDP has been able to practically tackle the challenges of developing CSDMSs such as the lack of crisis-related knowledge and cumulative nature of crisis-related knowledge, difficulty of extracting knowledge, long development cycle, and sudden and frequent changes in system requirements. INDEX TERMS Agile software development process, crisis management, crisis situations decision-making system, naturalistic decision making, recognition primed decision model, RoboCup rescue simulation agent benchmark.

According to many researchers, Abstraction is the basis of mathematics, computing, counting devices, and computer science and engineering. What is more, all of the above deal with complexity management in some way, and abstraction is the most basic mechanism of complexity management.Generative software development - whether in the sense of empowering humans by machine to create software or in the sense of reusing products - has been and is one of the serious concerns and goals of software engineering. The interesting thing is that in both views of generativity, the main issue is still, in a way, complexity management: whether this complexity management is to achieve diversity and reuse management (Czarnecki’s approach) or to Structuring from existing structures (the approach of Alexander and his followers in an object-oriented society).In this article, we will first look at complexity and its various definitions. The definitions that show, despite the different perspectives on complexity in different disciplines and domains, all point in one direction. We will conclude that complexity is rooted in multiplicity. In the following, we will formally define complexity. In the following discussion, we will look at the generative patterns of software development, and then we will look at the complexity management patterns at seven levels.In this article, the author has tried to maintain a comprehensive approach to complexity and to consider the approaches of different domains to complexity.

No abstract