Next Article in Journal
The Effects of Dislocation Dipoles on the Failure Strength of Wrinkled Graphene from Atomistic Simulation
Next Article in Special Issue
Trust Components: An Analysis in The Development of Type 2 Diabetic Mellitus Mobile Application
Previous Article in Journal
Determination of Calorific Value of Mixed Coals by Analysis of Major Elements Using Data Pre-Processing in Laser-Induced Breakdown Spectroscopy
 
 
Font Type:
Arial Georgia Verdana
Font Size:
Aa Aa Aa
Line Spacing:
Column Width:
Background:
Article

M-Healthcare Model: An Architecture for a Type 2 Diabetes Mellitus Mobile Application

Department of Electronics, Information and Communication Engineering, Kangwon National University, Samcheok-si 25913, Republic of Korea
*
Author to whom correspondence should be addressed.
Appl. Sci. 2023, 13(1), 8; https://doi.org/10.3390/app13010008
Submission received: 6 October 2022 / Revised: 12 November 2022 / Accepted: 18 November 2022 / Published: 20 December 2022
(This article belongs to the Special Issue Intelligent Medicine and Health Care)

Abstract

:
Type 2 diabetes mellitus (T2DM) is a metabolic disorder wherein the patients require DM management to keep their blood glucose under proper and regular control. Diabetes mellitus can be managed with the help of technologies, one of which is mobile health. Mobile health is an innovation in telemedicine that utilizes gadgets as a medium to access digitally based health information and services by utilizing electronic devices connected to the Internet. Mobile health services are distinguished based on interactions between users and medical personnel; namely, interactive and non-interactive services. The developed application can integrate Android mobile application software with supporting hardware, such as a glucometer, a wearable band, a heart rate sensor, a treadmill, and an exercise bike. The provided features in this mobile application include the monitoring of medication, food intake, exercise, and sleep. This study’s goal was to create a mobile application architecture for type 2 diabetes mellitus mobile applications. This research focused on developing an architecture for mobile diabetes applications, a hardware block diagram design, and an architecture of sensors for a type 2 diabetes mellitus mobile application.

1. Introduction

1.1. Smart Healthcare Systems

Smart healthcare systems enable users/patients and related parties in the healthcare sector, such as doctors and nurses, to access, collect, and manage medical data and information quickly and accurately, and to assist in recommending or supporting decisions in the healthcare sector. Still in their early stages of development, smart healthcare systems provide several focused service functions in which software and hardware are integrated to optimize the complete service of the smart healthcare system. Several technological developments in the field of smart healthcare systems help to treat patient illnesses and support the optimization of doctors’ health services, whereas, in general, a smart healthcare system’s architecture consists of software and hardware [1]. Challenges and supporting technology in a smart healthcare system are indicators that cannot be abandoned. The need (for various types of disease and services) is increasing every day in terms of both hardware and software technology. This, of course, requires appropriate integration so that service needs can be met, assisted by the development of adequate hardware and software technology. Several related studies apply the principles of smart healthcare systems in responding to existing challenges and needs [2].

1.2. Smart Healthcare Systems

Diabetes mellitus (DM) is a metabolic disorder that leads to high blood sugar levels. In addition to type 2 diabetes, there is also type 1 diabetes. Diabetes causes hyperglycemia because the pancreas cannot produce enough insulin. Under other conditions, the pancreas can produce insulin, but the insulin it produces cannot be used optimally. Both of these conditions can cause blood sugar spikes in diabetics [3].
Diabetes (DM) is generally divided into type 1 diabetes, or insulin-dependent diabetes mellitus; type 2 diabetes, or non-insulin-dependent diabetes mellitus; other types of diabetes mellitus; and gestational diabetes mellitus (Table 1). Type 2 diabetes is a metabolic disorder characterized by hyperglycemia due to insulin resistance and/or deficiency. Patients with type 2 diabetes mellitus (T2DM) need DM management to properly and regularly control their blood glucose levels. Blood sugar levels can increase and decrease in an unstable manner if type 2 DM sufferers do not control their blood sugar levels properly, which can trigger complications [4]. Diabetes mellitus control is carried out using the basic principles of diabetes mellitus control management, including the modification of unhealthy lifestyles to become healthy in the form of diet, physical exercise, and adherence to antidiabetic drug consumption [5].
Self-management is an integral part of diabetes control. Self-care management of diabetes can effectively reduce the risk of DM (Table 2) sufferers having coronary heart complications; in addition, self-care can control normal blood sugar levels, reduce the impact of DM problems, and reduce DM mortality [10,11]. Self-care performed by DM patients includes diet, eating habits, exercise, monitoring blood sugar levels, medication, and diabetic foot care. Efforts to overcome the weakness of self-care management of type 2 DM in controlling blood glucose levels that develop in the community to minimize DM complications can be assisted by utilizing technological developments [12].

1.3. Development Mobile Application

ICT (Information and Communication Technology) is a tool that provides added value by generating high-speed, complete, accurate, transparent, and up-to-date information. The era of information and communication technology is being used to increase the provision of health information. Researchers are trying to innovate to develop diabetes care applications that take advantage of technological developments in providing information for self-care management in controlling blood glucose levels. The diabetes care application is expected to be able to answer the problem as a smart solution to minimize complications that arise in Type 2 diabetes mellitus (T2DM) patients [15].
Android is an operating system for Linux-based mobile devices that appears among other operating systems currently under development with a good set of supported features (Table 3). However, current development operating systems run in a way that prioritizes internally built core applications without taking into account the significant functionality of third-party applications [16]. Therefore, there are restrictions on third-party applications that can capture native mobile data and communicate between processes, and there are restrictions on distributing third-party applications to the platform. An application is a special set of instructions on a computer designed for us to complete certain tasks.

1.4. Previous Research

The Android mobile application’s first development efforts were devoted to managing Type 2 diabetes. At this stage, the research team involved 20 people, consisting of 10 people with diabetes and 10 people without diabetes, in the use of diabetes mobile applications with supporting hardware, namely a wearable band, glucose meter, and treadmill [18]. The results of the initial research were used as reference material for the development of the second stage. At this stage, the researchers evaluated some of the functionality and accessibility of the application by conducting tests involving 40 people, consisting of 20 people with diabetes and 20 people without diabetes. The results of the second stage of research concluded that there was a need for changes and adaptation of applications for users, especially related to user registration for applications and glucometer and wearable band (smartwatch) connectivity with various versions [19]. Previous researchers have conducted preliminary research through two previous studies (Table 4).

2. Analysis

2.1. Application in Healthcare

An application in healthcare is a program created by a user that aims to complete a specific task (Table 5). An application is the storage of data, problems, and work in a container or medium that can be used to implement or implement existing things or problems in a new form without losing the fundamental values of the data, problems, and work itself [20].
The application can be categorized into three groups in its development, namely [21]:
(a)
Desktop applications, namely applications that can only be run on a PC or laptop.
(b)
Web applications, namely applications that are run using a computer or laptop and an internet connection.
(c)
Mobile applications, namely applications that run on mobile devices.

2.2. Mobile Technology and Operating System

A mobile phone is a portable electronic device that functions like a regular phone and can be moved over a wide area. While mobile phones currently use a combination of wireless transmission and traditional telephone circuit switching, packet switching is used in parts of the mobile phone network, especially for Internet access and WAP services [22]. Mobile phones, or “cell phones”, are electronic communication devices that have the same basic functionality as traditional landlines, but they can be carried anywhere (mobile) and do not need to be connected to a phone network using a cable (wireless) [23].
The mobile operating system is the primary software that directly manages and controls the hardware, and also manages and controls other software so that it can function (Table 6). Therefore, the mobile operating system is responsible for manipulating the various features and functions available on mobile devices. tasks, keyboards, WAPs, emails, text message scheduling, synchronization with other applications and devices, music playback, cameras, and control features [24]. In addition to the ability to control mobile phone hardware and software resources such as keyboards, screens, phonebooks, batteries, and network connections, the operating system controls all applications to run consistently and consistently. The operating system needs to be flexible so that software developers can easily create sophisticated new applications [25].

2.3. Telehealth

Telecare is a part of telehealth. Telecare focuses on the therapeutic side, while telemedicine covers the prophylactic, preventive, and therapeutic aspects [26]. One of the functions of telehealth, and a major requirement in providing health services, is patient monitoring and scheduling. The coverage of telehealth, telemedicine, and electronic health (e-health), telecare, and m-health is described by Totten AM et al. [27].

3. Research Methodology

3.1. Research Method

The research was conducted at the Circuit and System Design Laboratory at Kangwon National University. The research was performed by carrying out several systematic stages (Figure 1) in order to produce research reports and products (Mobile Application) that were in accordance with the objectives of the research implementation. The research method included six stages, starting with identification of the problem, setting the research scope, data and information gathering, software development, analysis, and the final report.

3.2. Software Development Methodology

In developing this application, we used the prototype model [28] as an approach to mobile application development. We performed three stages: creating and revising the mockup, conducting customer test drives, and listening to customers. All steps in this prototype model were chosen because they were in accordance with the project being developed, which does not have many stages, and the parties or teams involved can also be maximized in the three existing stages [29,30].

4. Proposed Architecture

4.1. Mobile Application

The development of the architecture (Figure 2) for the Type 2 Diabetic Mellitus Mobile Application is broadly divided into three major parts:
  • Medical Sensor and Exercise Equipment
Medical sensors in the architecture section include supporting devices (inputs) in the form of wearable bands, glucose meters, and heart rate sensors. The exercise equipment consists of a gym cycle and a treadmill. In this section, the device is Bluetooth- and RFID-compatible. In this section, the device will work for the next stage of data acquisition before going to the transmission section.
  • Transmission
Transmission in the architecture section consists of smartphone applications and cloud storage. In this section, the smartphone application receives input data from the Medical Sensor and Exercise Equipment section, which is referred to as the data acquisition process. The processed data are stored in cloud storage, and in this part of the process, the entire process is supported by the Internet network.
  • Information
Information on the architecture is the final part (output), namely the process after the data are processed in the transmission section. The process at this stage is called “real-time exercise data”, where the processed data can be received at the same time by the user (patient) with an Internet connection as network support.

4.2. Hardware Design and Implementation

The hardware design and implementation for the Type 2 Diabetes Mellitus Mobile Applications are written in block diagram format (Figure 3). Eight blocks (Figure 3) consist of RFID, DAQ for Treadmill and Gym Cycle, Heart Rate Sensor, Wearable Band, Glucometer, Signal Integration, Calculation and Memory, Smartphone Application, and Patient. The first five blocks consist of RFID, DAQ for Treadmill and Gym Cycle, Heart Rate Sensor, Wearable Band, and Glucometer, which interact with the Signal Integration, Calculation and Memory block, which in turn send User ID, Exercise Data, Heart Rate, Number of steps, Heart Rate and Blood Glucose Levels, where the data received in the Signal Integration, Calculation, and Memory block will interact with the smartphone application block to send Real-Time Exercise data. The last block is where the patient interacts with the smartphone application block, which is a process of real-time monitoring alerts.

4.3. Sensor

The sensor is one part of the Type 2 Diabetes Mellitus Mobile Application. In Figure 4, the architecture of sensors is clearly described, starting from the deployment of sensors, active sensors taking measurements, reading RFID tags, and entering mobile applications. Then, in the stage of analyzing the measurement, there will be two choices: namely, updating details in storage with normal or above-normal conditions, or storing the updated data in the database and receiving real-time monitoring alerts.

4.4. Sensor User Interface

The user interface (UI) is what the user interacts with as part of an experience (Table 7). UI is not just about colors and shapes; it is about providing users with the right tools to achieve their goals. In addition, UI is more than just buttons, menus, and forms that the user must fill out. When the system and users can interact with each other through commands such as using content and entering data, this is referred to as a user interface. The user interface is one of the most important parts of application development because it relates to the user and can be seen, heard, and touched. At this stage, the researchers developed a user interface related to the appropriate needs and related to the development of the Type 2 Diabetes Mellitus Mobile Application.

5. Testing

Researchers conducted an evaluation stage on the development of a diabetes mobile application for 40 participants who were users of mobile-based diabetes applications (diabetic patients). Evaluation of user acceptance testing for mobile applications (Figure 5) adapted five main factors at the application testing stage (Table 8), which included functionality, ease of use, usefulness, security and privacy, and cost factors. Based on the results of the evaluation using a Likert scale (strongly agree, agree, neutral, disagree, strongly disagree) with an assessment weight of (5, 4, 3, 2, 1), the average value of factor functionality was 4.57, ease of use 4.67, usefulness 4.75, security and privacy 5.0, and cost 4.70. Based on the results of this evaluation, there are two indicators that have an evaluation value with an input value of 3 (neutral), namely the functionality and ease of use factors.

6. Summary and Conclusions

The development of the Type 2 Diabetes Mellitus Mobile Application involves an operational feature that allows an application to run according to specified requirements and can integrate an Android-based mobile application with supporting hardware such as a glucometer, wearable band, heart rate sensor, treadmill, and gym cycle. The provided features in this mobile application include monitoring medication, food intake, exercise, and sleep. Architectural Design for Diabetic Mobile Applications, Hardware Block Diagram Design, and Architecture of Sensors will be useful for the application development team as a benchmark or guideline for what kind of application or product will be produced. Based on the results of the analysis, this study resulted in three proposed architectures: namely, the architecture for mobile applications, the hardware block diagram, and the architecture of sensors, which clearly describe the operational functions that exist in the Type 2 Diabetes Mellitus Mobile Application. On the other hand, the architectural design will support the success rate of application development, so that applications can be useful and optimally utilized both by patients and doctors involved in the treatment of type 2 diabetes (T2DM). This study is also intended to serve as a reference for researchers who are currently conducting or will be conducting research in the field of developing type 2 diabetes mobile applications.

Author Contributions

S.R.J.: project evaluation, methodology, investigation, resources, supervision. W.A.: software developer, functionality evaluation. J.-H.L.: conceptualization, funding acquisition, resources, supervision, writing—original draft, writing—review and editing. All authors have read and agreed to the published version of the manuscript.

Funding

This research was supported by “Regional Innovation Strategy (RIS)” through the National Research Foundation of Korea (NRF), funded by the Ministry of Education (MOE) (2022RIS-005).

Institutional Review Board Statement

Not applicable.

Informed Consent Statement

Not applicable.

Data Availability Statement

Not applicable.

Conflicts of Interest

The authors declare no conflict of interest.

References

  1. Abd-alrazaq, A.A.; Suleiman, N.; Baagar, K.; Jandali, N.; Alhuwail, D.; Abdalhakam, I.; Shahbal, S.; Abou-Samra, A.; Househ, M. Patients and healthcare workers experience with a mobile application for self-management of diabetes in Qatar: A qualitative study. Comput. Methods Programs Biomed. Update 2021, 1, 100002. [Google Scholar] [CrossRef]
  2. Adu, M.D.; Malabu, U.H.; Malau-Aduli, A.E.; Malau-Aduli, B.S. Mobile application intervention to promote self-management in insulin-requiring type 1 and type 2 diabetes individuals: Protocol for a mixed methods study and non-blinded randomized controlled trial. Diabetes Metab. Syndr. Obes. 2019, 12, 789–800. [Google Scholar] [CrossRef] [PubMed] [Green Version]
  3. Adu, M.D.; Malabu, U.H.; Malau-Aduli, A.E.; Malau-Aduli, B.S. The development of My Care Hub Mobile-Phone App to Support Self-Management in Australians with Type 1 or Type 2 Diabetes. Sci. Rep. 2020, 10, 7. [Google Scholar] [CrossRef] [PubMed] [Green Version]
  4. Höll, B.; Spat, S.; Plank, J.; Schaupp, L.; Neubauer, K.; Beck, P.; Chiarugi, F.; Kontogiannis, V.; Pieber, T.R.; Holzinger, A. Design of a Mobile, Safety-Critical in-Patient Glucose Management System. Stud. Health Technol. Inf. 2011, 169, 950–954. [Google Scholar]
  5. Jeffrey, B.; Bagala, M.; Creighton, A.; Leavey, A.; Nicholls, S.; Wood, C.; Longman, J.; Barker, J.; Pit, S. Mobile phone applications and their use in the self-management of Type 2 Diabetes Mellitus: A qualitative study among app users and non-app users. Diabetol. Metab. Syndr. 2019, 11, 84. [Google Scholar] [CrossRef]
  6. Sultan, A.; Murtaza, K.; Mohammed, A. Mobile Health (m-Health) System in the Context of IoT. In Proceedings of the IEEE 4th International Conference on Future Internet of Things and Cloud Workshops (FiCloudW), Vienna, Austria, 22–24 August 2016; pp. 39–42. [Google Scholar]
  7. Totten, A.M.; Womack, D.M.; Eden, K.B. Telehealth: Mapping the Evidence for Patient Outcomes from Systematic Reviews; Pacific Northwest Evidence-based Practice Center Portland, OR, Technical Briefs, No. 26; Agency for Healthcare Research and Quality: Rockville, MD, USA, 2016; pp. 1–125.
  8. Hasan, A.M.Y.; Alina, S.; Nor, A. The Role of Different Types of Information Systems in Business Organizations: A Review. Int. J. Res. 2014, 1, 1270–1286. [Google Scholar]
  9. Naseer, A.; Muhammad, B.W.; Abdul, H.M. Comparative Analysis of Operating System of Different Smart Phones. J. Softw. Eng. Appl. 2015, 8, 114. [Google Scholar]
  10. Spanakis, E.G.; Chiarugi, F.; Kouroubali, A.; Spat, S.; Beck, P.; Asanin, S.; Rosengren, P.; Gergely, T.; Thestrup, J. Diabetes management using modern information and communication technologies and new care models. Interact. J. Med. Res. 2012, 1, e2193. [Google Scholar] [CrossRef]
  11. Helen, F.N.C.; Jin, J.D.; Terrence, A.J. Content Analysis: First-Time Patient User Challenges with Top-Rated Commercial Diabetes Apps. Telemed. E-Health 2021, 27, 663–669. [Google Scholar]
  12. Gunawardena, K.C.; Jackson, R.; Robinett, I.; Dhaniska, L.; Jayamanne, S.; Kalpani, S.; Muthukuda, D. The Influence of the Smart Glucose Manager Mobile Application on Diabetes Management. J. Diabetes Sci. Technol. 2019, 13, 75–81. [Google Scholar] [CrossRef] [Green Version]
  13. Fernanda, C.F.; Thamiris, L.A.C.; Emerson, P.C.; Adriana, S.P.; Ilka, A.R.; Heloísa, C.T. Mobile applications for adolescents with type 1 diabetes mellitus: Integrative literature review. Acta Paul Enferm. 2017, 30, 565–572. [Google Scholar]
  14. Kumar, D.S.; Prakash, B.; Chandra, B.J.S.; Shrinivas, K.P.; Vanishri, A.; Jom, T.J.; Praveen, K.; Arun, G.; Murthy, M.R.N. Technological innovations to improve health outcome in type 2 diabetes mellitus: A randomized controlled study. Clin. Epidemiol. Glob. Health 2021, 9, 53–56. [Google Scholar] [CrossRef]
  15. Slagle, H.B.G.; Hoffman, M.K.; Caplan, R.; Shlossman, P.; Sciscione, A.C. Validation of a novel mobile phone application for type 2 diabetes screening following gestational diabetes mellitus. mHealth 2022, 8, 21–36. [Google Scholar]
  16. Contreras, I.; Vehi, J. Artificial Intelligence for Diabetes Management and Decision Support: Literature Review. J. Med. Internet Res. 2018, 20, e10775. [Google Scholar] [CrossRef] [PubMed]
  17. Maryam, J.; Asghar, E.; Shekoufeh, A. Developing “Aryan:” Diabetes self-care mobile application. Int. J. Prev. Med. 2019, 10, 59. [Google Scholar]
  18. Lee, J.-H.; Park, J.-C.; Kim, S.-B. Therapeutic Exercise Platform for Type-2 Diabetic Mellitus. Electronics 2021, 10, 1820. [Google Scholar] [CrossRef]
  19. Bults, M.; van Leersum, C.M.; Olthuis, T.J.J.; Bekhuis, R.E.M.; den Ouden, M.E.M. Barriers and Drivers Regarding the Use of Mobile Health Apps Among Patients With Type 2 Diabetes Mellitus in the Netherlands: Explanatory Sequential Design Study. Jmir Diabetes 2022, 7, e31451. [Google Scholar] [CrossRef]
  20. Christian, M.; Isabel, S.; Stephan, M. User Experience Testing of My ePRO App in a Diabetes Mellitus Type 2 Focus Group. Int. J. Clin. Exp. Med Sci. 2022, 11, 8. [Google Scholar]
  21. García, M.F.; Porras, Y.; Richmond, D.; Jensen, M.; Madrigal, M.; Zúñiga, G. Designing a Mobile Application to Support Type 2 Diabetes Mellitus Care in Costa Rica: A Qualitative Exploratory Study. J. Acad. Nutr. Diabet. 2016, 116, A75. [Google Scholar] [CrossRef]
  22. Kebede, M.M.; Pischke, C.R. Popular Diabetes Apps and the Impact of Diabetes App Use on Self-Care Behaviour: A Survey Among the Digital Community of Persons with Diabetes on Social Media. Front. Endocrinol. 2019, 10, 135. [Google Scholar] [CrossRef] [Green Version]
  23. Michael, O.A.; Taiwo, R.H.; Oluwabukola, A.A.; Joseph, F.O. Mobile phone ownership and willingness to receive mHealth services among patients with diabetes mellitus in South-West, Nigeria. Panafrican Med. J. 2020, 37, 29. [Google Scholar]
  24. Park, J.C.; Kim, S.; Lee, J.-H. Self-Care IoT Platform for Diabetic Mellitus. Appl. Sci. 2021, 11, 5. [Google Scholar] [CrossRef]
  25. Więckowska, R.K.; Justyna, D.; Grażyna, D. The usefulness of the nutrition apps in self-control of diabetes mellitus – the review of literature and own experience. Pediatric Endocrinol. Diabetes Metab. 2022, 28, 75–80. [Google Scholar] [CrossRef]
  26. Joshua, S.R. Analysis and Design of Service Oriented Architecture Based in Public Senior High School Academic Information System. IEEE Xplore 2017, 180–186. [Google Scholar]
  27. Zeadally, S.; Siddiqui, F.; Baig, Z.; Ibrahim, A. Smart healthcare Challenges and potential solutions using internet of things (IoT) and big data analytics. Psu Res. Rev. 2020, 4, 93–109. [Google Scholar]
  28. Chomutare, T.; Fernandez-Luque, L.; Årsand, E.; Hartvigsen, G. Features of Mobile Diabetes Applications: Review of the Literature and Analysis of Current Applications Compared Against Evidence-Based Guidelines. J. Med. Internet Res. 2011, 13, e1874. [Google Scholar] [CrossRef] [Green Version]
  29. Pritee, U.S.; Rani, P.T.; Deepak, D.S.; Umesh, J.P. A Literature Review on Android—A Mobile Operating system. Int. Res. J. Eng. Technol. 2021, 8, 1–6. [Google Scholar]
  30. Quy, V.K.; Hau, N.V.; Anh, D.V.; Ngoc, L.A. Smart healthcare IoT applications based on fog computing: Architecture, applications and challenges. Complex Intell. Syst. 2022, 8, 3805–3815. [Google Scholar] [CrossRef]
Figure 1. Research method.
Figure 1. Research method.
Applsci 13 00008 g001
Figure 2. Proposed architecture for diabetic mobile application.
Figure 2. Proposed architecture for diabetic mobile application.
Applsci 13 00008 g002
Figure 3. Hardware block diagram.
Figure 3. Hardware block diagram.
Applsci 13 00008 g003
Figure 4. Architecture of sensor.
Figure 4. Architecture of sensor.
Applsci 13 00008 g004
Figure 5. User acceptance testing for mobile application.
Figure 5. User acceptance testing for mobile application.
Applsci 13 00008 g005
Table 1. Classification of diabetes mellitus.
Table 1. Classification of diabetes mellitus.
NoDiabetes Mellitus
TypeDescription
1Type 1 [6]Beta cell damage, generally leading to absolute insulin deficiency [3].
2Type 2 [7]It varies from dominant insulin resistance with relative insulin deficiency to dominant insulin secretion defect as a result of insulin resistance [7].
3Other Types [8]
  • Diabetes mellitus is caused by a disease of the exocrine pancreas.
  • Diabetes mellitus due to drugs (e.g., HIV and AIDS therapy or after kidney transplantation, etc.), chemicals, or infections.
  • Diabetes mellitus is caused by immunological disorders.
4Gestational [9]In gestational diabetes mellitus, the diagnosis of DM is made at the time that a patient’s pregnancy is in progress.
Table 2. Risk factors.
Table 2. Risk factors.
NoRisk Factor [13,14]
FactorDescription
1Obesity (overweight)There is a significant link between obesity and blood sugar levels, and the degree of obesity with a body mass index (BMI) > 23, which can lead to an increase in blood glucose levels of up to 200 mg%.
2HypertensionAn increase in blood pressure beyond the normal range of hypertensive patients is closely associated with the improper storage of salt and water, or increased pressure in the body of the peripheral vascular system.
3DyslipidemiaDyslipidemia is a condition characterized by elevated blood fat levels (triglycerides > 250 mg/dl). There is a relationship between an increase in plasma insulin and low high-density lipoprotein (HDL) (<35 mg/dL).
4AgeIndividuals aged > 40 years are susceptible to DM, although it is possible for individuals aged < 40 years to avoid DM. The increase in blood glucose occurs at the age of about 45 years and the frequency increases with age.
5GeneticType 2 DM is thought to be associated with familial aggregation. The empirical risk in the event of Type 2 DM will increase two to six times if there are parents or family members suffering from type 2 DM.
6Alcohol and CigarettesAn individual’s lifestyle is associated with an increase in the frequency of Type 2 DM. Most of this increase is associated with increased obesity and decreased physical activity; other factors associated with the shift from a traditional to a westernized environment, including changes in cigarette and alcohol consumption, also play a role in the increase. Alcohol will interfere with blood sugar metabolism, especially in people with Type 2 DM, so it will complicate regulation and increase blood sugar.
Table 3. Android features.
Table 3. Android features.
NoAndroid Features [17]
FeaturesDescription
1Storage A data store, using SQLite, a lightweight database.
2ConnectivityAndroid not only provides a standard network connection, but also an API that allows apps to connect and interact with other devices using protocols such as Bluetooth, NFC, Wi-Fi P2P, USB and SIP.
3MessagingSupports MMS and SMS
4Media supportMedia support for audio, video, images (MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, GIF), and GSM telephony.
5Hardware supportCamera, GPS, compass and accelerometer.
6Play storeOnline catalog application on smartphones, without using a PC (personal computer) that can download and install applications.
Table 4. Comparison of our previous work.
Table 4. Comparison of our previous work.
NoComparison of our Previous Work
ResearcherFeaturesIoT DevicesParticipant
1Lee, J.-H.
  • Blood glucose levels
  • Physical activities
  • Dosage or injection
  • Wake up and sleeping time
  • Glucometer
  • Wearable band and aerobic exercise equipment
  • Smart medication monitor
  • Wearable band
20
2Park, J. C.
  • Blood glucose levels
  • Physical activities
  • Food intake
  • Dosage or injection
  • Wake up and sleeping time
  • Glucometer
  • Wearable band and aerobic exercise equipment
  • Smart food tray
  • Smart medication monitor
  • Wearable band
40
Table 5. Application classifications in healthcare.
Table 5. Application classifications in healthcare.
NoApplication Classification
ResearcherClassificationDescription
1I. Contreras Disease Prediction Disease prediction applications are applications that are used to help patients/application users to find out the prediction of diseases, along with the overall results of the diagnosis obtained based on the symptoms felt. This application was developed using certain methods according to the scope of the case study (disease) to be analyzed by calculating all parameters related to the symptoms of the disease. The development of this disease prediction application is useful to help doctors and also provide recommendations to patients/users who have difficulty knowing the disease they are suffering from but only know the symptoms they feel.
2E. G. SpanakisClinical CommunicationA clinical communication application is a development of technology in the health sector that helps achieve a state or health status as a whole, both physically, mentally, and socially. The focus of developing this application is the focus of communications related to health. The database in this application will store and process the existing data so that it can be useful for later use. Several clinical communication applications provide real-time communication services between patients/users and doctors to conduct health consultations. Doctors can collect information about the patient’s health status, or they can access a database to view the patient’s medical history.
3Adu, U. H MedicationThe lack of information about treatment and about drugs is the basis for developing health applications in this field. If it is not handled properly, the patient/customer will self-regulate the drug therapy they receive, which will impact an increase in cases of drug administration errors that are not in accordance with the patient’s needs. A medication health application focuses on education about drug information, assisting in health consultations on drug administration based on symptoms, and viewing the history of purchasing/using drugs stored in the database.
4Lee, J.-H. ExerciseExercise health applications, also called health and fitness applications, are applications that can provide information to users related to health and fitness without limitations of place and time, and cam help users to achieve their health and fitness targets. Some exercise applications provide features to be able to connect applications with other supporting devices to collect health information more comprehensively; for example, connecting applications with treadmills, cycles, smartwatches, or other supporting devices used.
5R. K WięckowskaNutritionA nutrition application is an application that helps patients/users to find out the number of nutritional needs and nutritional status by referring to nutrition and health sciences efficiently, cheaply, and accurately, where each country has different nutritional guidelines. This is very useful because food consumption affects a person’s nutritional status. Good nutritional status or optimal nutritional status occurs when the body gets enough nutrients that are used efficiently, so as to support physical growth, brain development, workability, and general health as much as possible. A nutrition application already has a nutritional value based on a calculated formula (nutritional standards) by accessing the database; the application can find specific numbers (food/beverage) that will be or have been consumed.
Table 6. Mobile operating systems.
Table 6. Mobile operating systems.
NoMobile Operating Systems
Operating System Description
1iOSiOS is a software operating system developed by Apple specifically to support the operation of mobile or handheld devices. iOS is used not only on iPhone phones but also on other Apple handheld devices such as iPad tablets and iPod music players. As a handheld operating system, iOS works the same as Android, developed by Google. Basically, the function of iOS is to design the iPhone so that it can be operated by the user. iOS can create a bridge that connects the interaction between the user and the iPhone hardware. iOS is responsible for interpreting user commands for applications on the iPhone so that you can interact with, move, or activate hardware features. Conveniently, iPhone users can take pictures and videos, listen to music, and make phone calls. This is because the iOS feature successfully receives these commands and interprets them for the iPhone hardware. As Lifewire reports, without iOS, you cannot use the iPhone hardware or its functions. iOS features are generally the same as those on Android, but there are some differences.
2AndroidAndroid is a mobile operating system based on a modified version of the Linux kernel and other open-source software designed primarily for touchscreen mobile devices, such as smartphones and tablets. Android was developed by a consortium of developers known as the Open Handset Alliance, with the participation of Google, a key contributor and commercial marketer. The core of the Android source code is called the Android Open Source Project (AOSP) and is primarily licensed under the Apache license. This allows Android variations to be developed for a variety of other electronic devices, including game consoles, digital cameras, PCs, and other user interface designs. Notable derivatives include Android TV for TV and Wear OS for wearables, both developed by Google. Android source code has been used as the basis for many different ecosystems in the context of its own software suite, Google Mobile Services (GMS), which includes applications such as Gmail, Google Play, and Google Chrome web browsers.
3Windows MobileWindows Mobile is a mobile phone operating system developed by Microsoft but released only for specific markets. The kernel used by Windows Mobile is Windows CE. In the Indonesian market, Windows Mobile is still little known, and it seems that there is not much demand from the general public. At that time, the success of smartphones with Symbian operating systems, from brands such as Nokia, Samsung, and Sony Ericsson, was evident.Originally, Windows Mobile existed in 2000 after Pocket PC 2000, but Pocket PC at that time was not a mobile phone, as it is today, but was generally called a PDA (Personal Digital Assistant). Other than the development of smartphones at the time, the version of Windows Mobile at the time was far from the innovations that have appeared.
4Blackberry OSBlackberry OS is a proprietary cellular working device evolved via RIM (Research in Motion) for the company‘s Blackberry line of hand-held cellphone gadgets. This working device allows for multitasking and enables RIM-exclusive gadgets, such as the track wheel, trackball, and, more commonly these days, the trackpad and touchscreen, to be used in handhelds. The Blackberry platform is possibly well-known for its local support for business communications environments, which enable full Wi-Fi activation and synchronization of email, calendar, tasks, notes, and contacts. These operating system updates can be obtained automatically from Wi-Fi vendors that assist Blackberry in which software is loaded over the air (OTASL). Third-party builders can write software to program the use of the available Blackberry APIs (Application Programming Interface), but applications that use positive capability must be digitally signed.
5Symbian OSSymbian OS was created by Symbian Ltd. It is a descendant of Psion’s EPOC and runs only on ARM processors, but it has x86 ports that are not officially exposed. Symbian OS can perform multithreading, multitasking, and memory-safe operations. Additionally, all programming in Symbian is event-based; that is, if there is no input in the form of a particular activity, the CPU hardware will be idle. Today, Symbian OS is widely used by suppliers of various mobile communication equipment products for different types of products. This operating system has an application programming interface (API) that allows this deviation from the hardware side on which Symbian OS is implemented. The API supports common hardware communication and behavior that can be used with other application objects. This is possible because the API is an application-level-defined interface object that contains procedures and functions (and variables and data structures) that manage or call the kernel and act as links between software and hardware. This API standard helps developers customize their applications so that they can be installed on a variety of mobile phone products.
Table 7. Design user interface.
Table 7. Design user interface.
NoUser Interface of Mobile Application
PageUser InterfaceDescription
1LoginApplsci 13 00008 i001On the login page, the user will fill in data in the form of ID and password (if previously registered), while for new users, the application provides services to register by filling in detailed data or automatically using a Google account.
2Personal InformationApplsci 13 00008 i002Users are asked to enter information about their nickname, sex (male or female), date of birth, height, and weight on the personal information page.
3HomeApplsci 13 00008 i003On the home page, the application briefly displays features that can be explored by users in the form of icon visualization, such as statistics to view the results of health data calculations, Bluetooth connections to devices, surveys, sugar levels, medicine, exercise, and a calendar.
4Register Internet of Things PackApplsci 13 00008 i004Register for the Internet of Things Pack is a page used by users to connect applications used with devices owned by them, such as wearable bands, glucometers, treadmills, etc.
5Monitoring MedicationApplsci 13 00008 i005The medication monitoring page enables users to view or control the medication intake schedule as recommended, or it can be entered manually by the user.
6Monitoring Food IntakeApplsci 13 00008 i006The food intake monitoring page allows users to directly control food intake by making direct adjustments at the specified time, which is divided into three parts, namely breakfast, lunch, and dinner.
7Monitoring ExerciseApplsci 13 00008 i007The exercise monitoring page helps users see the exercise that has been done. The results of the exercise are in the form of current speed, average speed, distance, and heart rate.
8Monitoring SleepApplsci 13 00008 i008The sleep monitoring page is visualized in the form of charts and calendars to make it easier for users to see the results of the evaluation and monitoring of sleep. The total presentation, as well as the average rest and sleep hours of the user concerned, can be seen.
Table 8. Testing factors.
Table 8. Testing factors.
NoTesting Factors
FactorsVariable
1Functionality
  • Quality of Information
  • Core of Function
  • Personalization
2Ease of Use
  • User Interface Design
  • Efficiency
3Usefulness
  • Usefulness
4Security and Privacy
  • Security and Privacy
  • Authentication
5Cost
  • Cost
Disclaimer/Publisher’s Note: The statements, opinions and data contained in all publications are solely those of the individual author(s) and contributor(s) and not of MDPI and/or the editor(s). MDPI and/or the editor(s) disclaim responsibility for any injury to people or property resulting from any ideas, methods, instructions or products referred to in the content.

Share and Cite

MDPI and ACS Style

Joshua, S.R.; Abbas, W.; Lee, J.-H. M-Healthcare Model: An Architecture for a Type 2 Diabetes Mellitus Mobile Application. Appl. Sci. 2023, 13, 8. https://doi.org/10.3390/app13010008

AMA Style

Joshua SR, Abbas W, Lee J-H. M-Healthcare Model: An Architecture for a Type 2 Diabetes Mellitus Mobile Application. Applied Sciences. 2023; 13(1):8. https://doi.org/10.3390/app13010008

Chicago/Turabian Style

Joshua, Salaki Reynaldo, Wasim Abbas, and Je-Hoon Lee. 2023. "M-Healthcare Model: An Architecture for a Type 2 Diabetes Mellitus Mobile Application" Applied Sciences 13, no. 1: 8. https://doi.org/10.3390/app13010008

APA Style

Joshua, S. R., Abbas, W., & Lee, J. -H. (2023). M-Healthcare Model: An Architecture for a Type 2 Diabetes Mellitus Mobile Application. Applied Sciences, 13(1), 8. https://doi.org/10.3390/app13010008

Note that from the first issue of 2016, this journal uses article numbers instead of page numbers. See further details here.

Article Metrics

Back to TopTop