Efficient Lupus Capturing Data System Based on Model View Controller

Autores

  • Leticia Mendieta UNA
  • Christian E. Schaerer UNA
  • Santiago Gomez UNA
  • Oliver Medina UNA
  • Isabel Acosta UNA
  • Francisco Santacruz UNA
  • Juana Ortellado UNA
  • Gladys Velázquez UNA
  • Clyde Parodi UNA
  • Astrid Paats UNA

Resumo

Systemic lupus erythematosus (SLE) is a chronic autoimmune disease that presents several challenges in research and patient follow-up. One of the main issues is the overlap with regular consultations, which leads to a lack of comprehensive clinical databases. Traditional data capture methods often lack the necessary flexibility and efficiency, resulting in discrepancies that complicate statistical analysis and, in some cases, may invalidate it. This makes it extremely difficult to predict disease progression. To address these challenges, this work explores a robust data capture system grounded in mathematical principles. Such a system is focused on statistical analysis, developing predictive models, and classifying cases requiring early and differentiated care. This work presents a data capture system based on the Model-View-Controller (MVC) design pattern, commonly used in web development[2]. MVC promotes better organization and code management, simplifying maintenance and future updates. It separates responsibilities: the model handles data logic, the view manages presentation, and the controller coordinates interaction. This structure enhances code reuse, simplifies maintenance, and facilitates the addition of new features. It is especially useful for monitoring patients with SLE. Figure 1 shows the system’s interconnection scheme. The MVC-based (LUPUS-Capturing system) efficiently organizes and manages data while optimizing request response times. This is particularly crucial for large volume data applications. Response time is calculated using the standard formula [3]: Tr = Tw + Tp + Tc, where Tr is the response time, Tw is the waiting time, Tp is the processing time, Tc is the transmission or communication time. Table 1 shows the response times of the processed requests, which are broken down into waiting, processing, and transmission times. Response times are observed to be consistent and stable, with low variations in the mean 244.86 ms. Processing is the most significant time consuming (approx. 243.94 ms), while waiting time and transmission time are minimal (approx. in mean 0.159 ms and 0.6825 ms, respectively). Hence, lattice time is not a significant problem. Using the MVC pattern in system development has proven to be an optimal solution to the challenges of monitoring patients with systemic lupus erythematosus (SLE). Efficient response times and flexibility allow continuous system improvement, facilitating SLE patient monitoring and supporting medical research. [...]

Downloads

Não há dados estatísticos.

Referências

R. V. Rochim, A. Rahmatulloh, R. R. El-Akbar, and R. Rizal. “Performance Comparison of Response Time Native, Mobile and Progressive Web Application Technology”. In: Innovation in Research of Informatics (INNOVATICS) 5 (May 2023). doi: 10.37058/innovatics.v5i1.7045.

H. Wang, N. Wang, M. Li, S. Mi, and Y. Shi. “Student Physical Health Information Management Model under Big Data Environment”. In: Scientific Programming 2021 (July 2021), pp. 1–10. doi: 10.1155/2021/5795884.

J. Yang and A. Abraham. “Analyzing the Features, Usability, and Performance of Deploying a Containerized Mobile Web Application on Serverless Cloud Platforms”. In: Future Internet 16 (Dec. 2024), p. 475. doi: 10.3390/fi16120475.

Downloads

Publicado

2026-02-13

Edição

Seção

Resumos