| Literature DB >> 35573899 |
Shadi Atalla1, Saad Ali Amin1, M V Manoj Kumar2, Nanda Kumar Bidare Sastry3, Wathiq Mansoor1, Ananth Rao1.
Abstract
Multi-morbidity is the presence of two or more long-term health conditions, including defined physical or mental health conditions, such as diabetes or schizophrenia. One of the regular and critical health cases is an elderly person with a multi-morbid health condition and special complications who lives alone. These patients are typically not familiar with advanced Information and Communications Technology (ICT), but they are comfortable using smart devices such as wearable watches and mobile phones. The use of ICT improves medical quality, promotes patient security and data security, lowers operational and administrative costs, and gives the people in charge to make informed decisions. Additionally, the use of ICT in healthcare practices greatly reduces human errors, enhances clinical outcomes, ramps up care coordination, boosts practice efficiencies, and helps in collecting data over time. The proposed research concept provides a natural technique to implement preventive health care innovative solutions since several health sensors are embedded in devices that autonomously monitor the patients' health conditions in real-time. This enhances the elder's limited ability to predict and respond to critical health situations. Autonomous monitoring can alert doctors and patients themselves of unexpected health conditions. Real-time monitoring, modeling, and predicting health conditions can trigger swift responses by doctors and health officials in case of emergencies. This study will use data science to stimulate discoveries and breakthroughs in the United Arab Emirates (UAE) and India, which will then be reproduced in other world areas to create major gains in health for people, communities, and populations.Entities:
Keywords: autonomous tools; health; multi-morbidity; old age patients; real-time
Year: 2022 PMID: 35573899 PMCID: PMC9096249 DOI: 10.3389/frai.2022.865792
Source DB: PubMed Journal: Front Artif Intell ISSN: 2624-8212
Figure 1How the internet usage gap has stopped since the outbreak of the pandemic.
Figure 2Wearable sensor networks.
Figure 3Evolutionary prototyping methodology.
KPIs for autonomous tool for monitoring multi-morbidity health conditions in UAE and India.
|
|
|
|
|---|---|---|
| Milestones on time% | Budget variance (planned vs. actual) | Customer complaints |
| Estimate to project completion | Budget iterations | Change requests |
| Adjustments to schedule | Planned value | Billable utilization |
| Planned vs. actual hours | Net promoter score | Return on investment (ROI) |
Figure 4The system model.
Figure 5ML application.
Stakeholder analysis matrix.
|
|
|
|
|
|
|
|
|
|---|---|---|---|---|---|---|---|
| End-Users: | Phone, email address | High | High | Interact with the system on a day-to-day basis. | Agree for user interface design and functionalities to implement the new system | Reluctant to use the systems | Weekly round-table discussions |
| Health care authorities | Phone, email, website, address | High | High | Monitoring health conditions of the patients | Integration with the healthcare systems | Refuse to integrate new system with the health care system | Monthly round-table discussions |
| Doctors and health officials in case of emergencies. | Phone, email address | High | High | Monitoring health conditions of the patients | Identify system feature and accepted criteria | Reluctant to use the systems | Monthly round-table discussions |
| Application integrators | Phone, email address | High | High | Develop, test, integrate maintain functional system | Support the life cycle of the system | Daily round-table discussions |
Figure 6Gantt chart of project milestones.
Proposed project yearly plan.
|
|
|
|
|---|---|---|
| 1st year | 1–2 | 1. A team of 5 members will refine the research proposal; allocate responsibilities for each member, one to organize data, 3 to do literature review; 5th to organize the delivery of Objective 1 |
| 2.Two young researchers with MS and fresh PhDs to train them in problem identification, literature review, hypothesis setting, Data Science tools being used, the process of Platform development. | ||
| 3–6 | 3.Define the application use cases and requirements | |
| 4. A defined subset of use cases of the solution. | ||
| 5. Complete literature review | ||
| 6. Refine framework for the platform | ||
| 7–12 | 7. Develop the mobile application with basic decision-making algorithms. | |
| 8. Integrate the Mobile App with described components: personal sensor network, medical devices, and wearables. | ||
| 2nd year | 1–4 | 1.Young researchers and the team (TEAM) to prepare draft paper for internal presentation in a research forum. Obtain feedback from forum peers. |
| 2.Revise the draft with the feedback | ||
| 3.Complete logistics for presenting the paper in 1st International Symposium. | ||
| 4.Refine framework for the Big Data platform | ||
| 5–8 | 5. Present the paper in the Bangalore Ecosystem for Health Research (BEHR) symposium | |
| 6. Obtain feedback from symposium participants | ||
| 7. Incorporate feedback to publish the symposium proceedings | ||
| 8. Disseminate the research results technically to the local UAE and Indian community through social media channels. | ||
| 9. Integrate the Mobile App with the BigData Platform | ||
| 9–12 | 10. Submit the proceedings to a peer-reviewed journal | |
| 11. Develop proof of concept based on the overall Solution infrastructure | ||
| 12. Refine the AT tools for commercial. | ||
| 3rd year | 1–2 | 1. A team of 5 members will refine objective 3 of the research proposal; allocate responsibilities for each member, one to organize data, 2 to do literature review; 4th to organize the delivery of Objective 3 and 4 |
| 2.2 young researchers to train them in problem identification, literature review, hypothesis setting, Machine learning tools being used, process of Autonomous Tool (AT) integration the ML models with the solution platform. | ||
| 3–6 | 3. Complete collection of existing publicly available and/or UAE and Indian data. | |
| 4. Refine the literature review with a focus on machine learning. | ||
| 5. Refine framework for the AT for the integration ML model. | ||
| 6. Set Hypotheses and goals. | ||
| 7–12 | 7. Integrate the AT | |
| 8. Run experiments with in-sample data | ||
| 9. Validate the AT using test data or validation data | ||
| 10. Start preliminary analysis on initial results | ||
| 11. Apply AT on the population: researchers themselves and their relatives | ||
| 12. Get feedback from the population on the merit and demit of using the AT for improving their health. | ||
| 13. Use the feedback as additional data and feed to the AT tools | ||
| 14. See the improvements in the results | ||
| 15. Iterate the cycle 11–14 three times to cover at least the sample number of patients in the local population to get a decent response. | ||
| 13. Conduct community forums to disseminate the iterated results | ||
| 4th year | 1–4 | 1.Young researchers and the team (TEAM) to prepare draft of the second paper for internal presentation in a research forum. Obtain feedback from forum peers. |
| 2. Revise the draft with the feedback | ||
| 3. Complete logistics for presenting the paper in 2nd DS- I UAE and India Symposium | ||
| 5–8 | 4. Present the paper in the Bangalore Ecosystem for Health Research (BEHR) symposium | |
| 5. Obtain feedback from symposium participants | ||
| 9–12 | 6. Incorporate feedback to publish the symposium proceedings | |
| 7. Submit the proceedings to a peer-reviewed journal | ||
| 5th year | 1–4 | 1. The Team members will refine objective 4 of the research proposal; allocate responsibilities for each member, one to commercialize the tool by patenting its data, 2 to Disseminate in non-technical; 2 to organize the delivery of the exploitation plan |
| 5–8 | 2. Disseminate in a non-technical manner the research results to the local UAE and Indian community through social media channels | |
| 3. Preparation of an initial exploitation plan and maintenance of the plan including the identification of relevant results and the corresponding target groups. | ||
| Involvement of the external user in the planned demonstration phase | ||
| 9–12 | 4. Compare Clinical data collected and generated by the platform with clinical from other sources to ensure the validity of the approach | |
| 5. Joined proofs of concept with external user and health data sources provider. | ||
| 6. Closure of the research project with a summary of lessons learned and experiences gained by the TEAM for future |
WB, Work Breakdown; Description: (M—Month; PM—Project Month).
Project work breakdown structure.
|
|
|
|
|
|
|---|---|---|---|---|
|
|
| 5 | M1 | M60 |
| D0.1 | Administrative project management | 5 | M1 | M60 |
| D0.2 | Impact management | 5 | M1 | M60 |
|
| Cases requirements gathering and literature review | |||
| D1.1 | Use cases and user requirements | 7 | M3 | M6 |
| D1.2 | Use cases of the proposed solution | 7 | M3 | M6 |
| D1.3 | Objective 1 and 2 literature review | 4 | M3 | M6 |
| D1.4 | Refine framework for the platform | 4 | M3 | M6 |
|
| Platform development and implementation | |||
| D2.1 | Mobile application with basic decision-making algorithms. | 5 | M7 | M12 |
| D2.2 | Integrate the Mobile App with medical devices, and wearables | 5 | M7 | M12 |
| D2.3 | Refine framework for The BigData Platform | 5 | M13 | M17 |
| D2.4 | Integrate the Mobile App with the BigData Platform | 5 | M18 | M21 |
| D2.5 | Develop proof of concept based on the overall solution infrastructure | 5 | M22 | M24 |
|
| Machine Learning and Autonomous Tool (AT) integration | |||
| D3.1 | Literature review with focus on machine learning | 7 | M23 | M24 |
| D3.2 | Data identification and collection | 7 | M25 | M28 |
| D3.3 | Refine framework for the AT for the integration ML model | 7 | M25 | M28 |
| D3.4 | Set hypotheses and goals | 7 | M29 | M36 |
| D3.5 | Building data models | 7 | M29 | M36 |
|
| Integration and testing | |||
| D4.1 | Integrate the Machine learning Model with the Platform | 5 | M37 | M40 |
| D4.2 | Run testing scenarios | 7 | M41 | M60 |
|
| Evolution, dissemination evolution exploitation | |||
| D5.1 | Preparation of an initial exploitation plan and maintenance | 7 | M49 | M51 |
| D5.2 | Platform evaluation and validation | M13 | M56 | |
| D5.3 | Publication and commercialization | 7 | M13 | M60 |
| D5.4 | Disseminate in non-technical manner | 7 | M52 | M60 |