Development of a Personal Health Information Management Program Using Mobile Biometric Information Measuring Device

Ⅰ. Introduction

The advancement of Internet and smart devices has facilitated information retrieval and use. Accordingly, there has been a rapid growth in services that enable individuals to search for and utilize information on health and diseases directly. In particular, the increase in the number of elderly and chronic patients has increased the burden of healthcare costs on individuals and society. Hence, u-health is being actively studied as an alternative system for personal health management and preventive healthcare for the elderly and those suffering from chronic diseases [1~2]. To improve quality of life, personal health record (PHR) services are required that enable individuals to collect and manage various health and medical information and to maintain health records. A PHR service is a personal health information management service that enables users to confirm their own personal information and medical records, when necessary, and enter such information directly as well [3–5]. In a survey conducted in South Korea on PHR services, 59.8% of the respondents felt that they would choose to use PHR services and 27.8% of the respondents said “Yes” to the question on whether they wanted to use a paid PHR service [6]. PHRs are constructed on the following four types of bases: paper, computer, Internet, and mobile device. Depending on the types of electronic medical recording systems, PHRs are also classified into stand-alone, EMR(Electronic Medical Records)-tethered, and interconnected PHRs [7]. A PHR can be considered an intersection of healthcare information technology and consumer participation in health and well-being. In the promotion of preventive medicine or medical regimens against so-called “modern diseases,” PHRs are being studied as a solution to the healthcare crisis associated with the ever-growing increase in healthcare costs and the demand for better medical and preventive services [8].

This study developed an application and a server program to enable individuals to manage their personal health information conveniently. Data collected from each mobile biometric reader are automatically stored in the server, and users can enter their personal health information using the application. Section 2 shows the app and server configuration diagram, and Section 3 shows the app and server development details.

Ⅱ. App and Server Configuration

Figure 1 presents a flow diagram of the application for personal health information management. An XBee was applied for communication between a sensor board, which measured a user’s pulses, blood oxygen levels, and body temperatures, and the main controller of a body heat keeper, which collected the measurement data. An XBee module has many advantages such as low power consumption, wide device layout, and short latency. Furthermore, as a high-level communication protocol that uses small and low-power digital radios based on IEEE 802.15.4-2003, XBee is the standard for personal wireless local area networks. Moreover, as an XBee is easy to implement and includes the operating/sleep modes, it requires low installation and maintenance costs and ensures stability. As a very small protocol stack is used, an XBee is suitable for transmitting and receiving a small amount of data and has a high node density per network.

Fig. 1.

Flow diagram of the application for personal helth information management

Figure 2 presents a flow diagram of the server that stores, enters, and manages the collected data. Bluetooth communication was used for the mainboard and the application that collected measurement data. For the Bluetooth communication, Bluetooth Classic, which uses a master–slave relationship between devices, was adopted. The Bluetooth low energy (BLE) communication protocol was adopted to solve the issue of the battery draining quickly while being connected in the Bluetooth Classic communication.

Fig. 2.

Flow diagram of the server

The application was implemented in Java and Kotlin, and the server was implemented in C# and WPF(WebSphere Partition Facility). The application was developed using Android Studio, and the server was established using Visual Studio.

The purpose of designing and developing the server was to input and confirm the PHRs. A UI(User Interface) was declared for logger application, and the logger was written. Data parsing was conducted based on a data conversion (App -> PC) protocol.

As for reports, a report UI was configured, and report data were processed.

The server socket was connected to port #1553, and then, the transmission, reception, and connection events were registered and processed. A function was designated for the thread processing of events per second, and the log data were processed every 15 s. A box list for displaying the logs was declared, and the rich box style was fixed with a margin of 0 and a line height of 5 so that data could be inserted into the box list.

While a function thread operates for an actual log writing section, data for logs should be written into the rich box. Accordingly, invoke processing was first performed to execute the UI thread. When the corresponding UI thread execution ended, a particular log folder was designated for the input, output, and storage of data. The data were also processed to be displayed in the rich box. Data received in a hex byte array, which is a syntax for processing received data, were converted into a string. Subsequently, the data thus converted were processed again so that they became available to users. Finally, the graphs and data were processed on the screen. A graphic corresponding to the report UI was processed by applying a chart function. The corresponding graph was processed by designating the position and setting the corresponding (legend) value to a target in white font. The data time was comparatively processed to be added to the list, and the data entering the report were processed so that they could follow a routine at a specific time.

As one of the socket programming types, TCP(Transmission Control Protocol) communication is referred to as a stream communication protocol. As TCP communication operates only when both sockets are connected, it is also called a connection-oriented protocol. Because the TCP protocol is reliable, data of the transmitting end arrive at the receiving end in order without loss. In addition, the receiving and transmitting ends should be linked to each other in advance, and data should be exchanged in the connection order. Such a connection-oriented type enables reliable communication in which, once both ends are connected to each other, data are delivered from the transmitting end to the socket of destination in order until the connection is terminated. For a reliable TCP connection, it is necessary to understand the method of using libraries and the operating sequence in TCP programming accurately. As Java provides relevant classes in the java.net package to facilitate TCP programming, those classes of the package need to be used appropriately.

The TCP sockets were processed as a group to block Nagle’s algorithm from executing. The corresponding time-out was set to 5 s for initializing the channel. The routine for data processing was changed by processing encode/decode in Korean. Java introduced the concept of socket to network communications. A socket represents the endpoints of a network and provides a reading/writing interface irrespective of how data are actually transmitted. As the network and transport layers are encapsulated, a program can be developed without considering the two layers. Bill Joy developed the socket programming at the University of California, Berkeley. Java integrated the socket as an essential library for portability and cross platform network programming. Socket and server socket classes are provided to support TCP of the TCP/IP(Internet Protocol address) layers. The client attempts a connection to the TCP server by creating a socket object, and the server listens to the TCP connection by creating a socket server object. In turn, the client and the server become connected to each other. When the input and output streams are created using sockets, the TCP socket provides a byte stream communication between two networks, and the socket classes provide methods for reading bytes and for writing bytes. These two methods enable communication between the client and server.

Figure 3 shows a protocol in which data is transferred from APP to a PC.

Fig. 3.

shows a protocol in which data is transferred from APP to a PC.

Among the open sources, com.github.mikephil.charting was used to initialize a line chart and draw a UI. The corresponding line chart was processed to have a specific position and a fixed width/height. UI thread processing was conducted every 2 s using a timer to add data portions to the graphs. An average calculating operation was used to calculate the average data from the data thus added, and the average data obtained were displayed on the screen. Devices have a protocol stack for Bluetooth communication. In general, a protocol, which is a set of rules, needs to be defined for network communications. A protocol stack is a group of protocols that are defined and stacked in layers. When Bluetooth signal packets are transmitted or received, the packets are analyzed or generated through such a protocol stack. Data were processed using a BLE scanner to be executed in the Android Lollipop version or above. The device name and RSSI(Receiver Signal Strength Indicator) were received from the corresponding BLE suite, and the data were processed as received. When the scanned device was correct, the data were transferred to the data processing section. Then, the data were represented by activating the Gatt in BLE. The specific values of BLE data were managed, monitored, and processed in a Gatt server, and the corresponding devices were automatically registered in the Gatt.

Addresses and ports for communication with the server were designated and configured, and various other items, including reconnection, were processed and built as optional items. The socket connection was oriented through the optional items that were built. Figure 4 shows the data parsing processing protocol.

Fig. 4.

data parsing processing

For data transfer, the data were encapsulated, and various information items, such as the corresponding name and medicine information, were designated and managed. The data were processed to be reanalyzed by a protocol designated by the PC. Finally, the data were delivered to a socket that was already connected.

Ⅲ. App. & Server Details of development

Figure 5 depicts the application for recording personal health information that was designed and developed in this study. The application was designed such that biometric data measured using a wearable device could be sent to the main controller through an XBee module, and the corresponding data could be delivered from the main controller to the application through Bluetooth. In addition, the design of the application also allowed each user to enter and manage personal health information directly.

Fig. 5.

PHR application

The application was designed to input the basic personal information and other clinical information of users and to activate emergency stoppage of a body heat keeper. The application could also display the measurement data of body temperature, pulse, blood oxygen, etc.

Figure 6 presents examples of data that can be input using the application. Figure 6 (a) depicts the items of user information on the page of User. Basic user information such as ID, name, height, weight, and age can be entered. Figure 6 (b) depicts the items entered by the user on the page of Disease Info. This page is designed to enable the input of items such as the user’s diseases, the medical date, medicines in use, and exercise.

Fig. 6.

Configuration of the application (a) User, (b) Disease Info

Figure 7 presents examples of the data that are measured by the wearable device and are sent to the application. Figure 7 (a) depicts the information on the page of Body Temp. The current and average temperatures of the user are displayed using numerical values and the graph.

Fig. 7.

Configuration of the application (a) Body Temp (b) Blood Oxygen and (c) Pulse

Figure 7 (b) depicts the information displayed on the page of Blood Oxygen. The blood oxygen level of the user is shown in real time. Figure 7 (c) presents information corresponding to the user’s pulse. In other words, the heart rate of the user is displayed using numerical values and the graph in real time.

Figure 8 depicts the server program that stores and manages personal health information. When data are delivered from the application to the server, the patient information, body temperatures, blood oxygen levels, and pulses can be checked on the PC. The server was also designed to let each patient enter and directly check their own information. In particular, the server was designed to display data clearly by date on graphs clearly.

Fig. 8.

PC configuration

Ⅳ. Conclusion

This study designed and developed an application and a server for collecting, analyzing, storing, and managing personal health data that are either measured through a wearable device or manually entered by each user.

The application and the server were configured as follows. Pulses, blood oxygen levels, body temperatures, and other data, which are measured through a wearable device in real time, were sent to the application via Bluetooth communication. Next, the data were transmitted to and stored in the server through a smart device in which the application was installed. The design of the application also enabled each user to enter their personal information and other disease and medicine information. Considering the system linkage with medical institutions, the disease and medicine information were designed to be entered both into the application and the server. If more users wearing mobile biometric readers can manage their personal information by themselves with the help of such a health information management program, it is expected that medical institutions could provide faster and more accurate diagnostic and treatment services.

Acknowledgments

This paper is that revised and supplemented the research results supported by the Small and Medium Business Promotion Agency (S2759360) in 2019.

References

• Yoo B S, Kim D H, Cho K R, Kim S H, Oh S J, Cho J S, "u-DailyCare : Design of a Health Management System for Chronic Illness Patients," Communications of the Korean Institute of Information Scientists and Engineers, Vol. 38, No. 1, pp. 146-149, 2011.
• Kim D H, Kim S H, Cho K R, Cho J s, "u-DailyCare : Design and Implementation of prevention and Management Sevice for chronic and Adult disease," Communications of the Korean Institute of Information Scientists and Engineers, Vol. 39, No. 1, pp. 197-199, 2012.
• Park Y M, Oh Y H, "A Study on The Integration of Healthcare Information Systems based on SOA for PHR services," Journal of the Institute of Electronics Engineers of Korea, pp. 29-35, 2011.
• Park Y M, "A Study on Medical Information System based on P2P for PHR Service," Journal of Advanced Information Technology and Convergence, Vol. 11, No. 12, PP. 123~132, 2013. [https://doi.org/10.14801/kiitr.2013.11.12.123]
• Lee M K, Hwang H J, "Design of Secure Personal Health Record Management Systems," Journal of Advanced Information Technology and Convergence, Vol. 13, No. 8, pp. 71-80, 2015. [https://doi.org/10.14801/jkiit.2015.13.8.71]
• Kim S Y, Kim H R, Bae J B, Kim Y, “The Consumers' perceptions and reguirements for personal health records in Korea,” JKorSoc MedInformatics, Vol. 15, PP. 273~284, 2009. [https://doi.org/10.4258/jksmi.2009.15.3.273]
• Heo Y, Yang J S, Park K H, Cha S J, Choi D J, Hwang K H, "PD issue report: personal health record (PHR) service technology and industry trends," Korea Evaluation Institute of Industrial Technology, 11(4):71, 91-4, 2013.
• Miller H D, Yasnoff W A, Burde H A, "Personal health records: the essential missing element in 21st century healthcare," J Healthc Inf Manag, 47:166-7, 2009.