article
Mobile health (mHealth) applications transform healthcare for chronic conditions like endometriosis. This paper compares Firebase Firestore, MongoDB, and PostgreSQL for “PainCare”, an mHealth application developed for endometriosis symptom tracking and AI-driven predictive analysis. We evaluated these systems on backend performance (using ApacheJMeter with up to 100 users), application security (MobSF static, Burp Suite dynamic), and Random Forest AI model integration (trained on a <tex xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">$\mathbf{1 0, 0 0 0}$</tex>-instance Kaggle dataset) for endometriosis likelihood prediction. Our findings show PostgreSQL exhibited superior performance and stability under load <tex xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">$(28-32 ~\text{ms}$</tex> avg. response, 0 % error). Firebase enabled rapid development but faced Firestore performance testing limitations due to SSL errors, alongside a critical vulnerability from an exposed API key. All implementations received “Medium Risk” MobSF security scores (Firebase: 50/100, MongoDB: 44/100, PostgreSQL: 48/100), highlighting common weaknesses like debug configurations. MongoDB offered flexibility for the AI integration, where the Random Forest model achieved approximately 63.27 % accuracy. With 63 % accuracy, the AI model cannot be used for clinical diagnosis, but can serve as an awareness or preliminary triage tool, helping direct patients to medical consultation. Future improvements are needed to strengthen its reliability and applicability. This study provides empirical evidence and practical considerations for DBMS selection in AI-enabled mHealth, highlighting the essential relationship between performance, security, AI feasibility, and robust application-level security practices while supporting global smart connectivity for decentralized healthcare systems.
This page summarises published work. The authoritative version sits with the publisher.
DOI: 10.1109/wincom65874.2025.11313464
Is something wrong with this record? Report it or request removal.
Discussion
Have you built on this work, tried to replicate it, or seen it applied in practice? Share what you know. Verified researchers and MARATTO™ domain experts can open a discussion, and any member can reply. Contributions are reviewed before they appear.
No discussion yet. Open the first thread.
New to MARATTO™? Create a free account.