Health Management Application Integration System

Abstract

This invention relates to a health management application integration system comprising a server, a clinic terminal, and a user terminal. The clinic terminal is communicatively connected to the server, and the server includes an appointment module, a health diary module, and a consultation progress module. This allows the user terminal to upload appointment information and health diary records to the server. The clinic terminal generates an appointment confirmation message based on the appointment information, which the server then sends to the user terminal as an appointment confirmation message. The user terminal is communicatively connected to the server to receive and display consultation progress information. In this way, users can upload health diaries, make appointments, and check consultation progress without switching between multiple applications.

Description

Technical Field

[0001] An integrated system, particularly a health management application integrated system. Prior Technology

[0002] Currently, health management applications (APPs) provided for personal use have relatively limited functions, mainly focusing on measuring and recording specific health indicators such as blood pressure, weight, and blood sugar. These applications are usually designed to achieve specific health management goals, and their functions are relatively limited. Although such applications can provide basic health monitoring functions, they are not fully integrated into the user's overall medical process, lacking a coherent service flow to assist patients in real-time management during their medical visits.

[0003] Furthermore, traditional registration systems typically rely on in-person queuing or telephone appointments, which have many shortcomings. When inquiring about and making appointments, users usually need to register by phone or in person at the clinic, which is not only time-consuming but also involves uncertain waiting times and issues such as clinic schedules not being updated in a timely manner. Moreover, while waiting in person, users cannot keep track of the doctor's treatment progress in real time, easily misjudging the time and arriving at the clinic too early or too late, causing unnecessary waiting. Even if users check the progress using the registration number displayed on-site, there may be a discrepancy between the displayed information and the actual situation, further exacerbating the inconvenience for users.

[0004] While another clinic app offers online appointment booking, the health management app and the clinic app are separate applications, requiring users to switch between them, which is inconvenient. This separate system prevents users from centrally viewing their appointments, health records, and consultation progress, increasing operational complexity and reducing the overall user experience.

[0005] Therefore, there is a need to strengthen the integration of health management application functions.

[0006] Furthermore, existing appointment tracking systems are typically limited to displays within the clinic, preventing patients from receiving real-time updates outside the clinic. While some clinics provide screens to display queue numbers and their corresponding appointment progress, this information is often not fully synchronized with reality, especially during the waiting period. Because the doctor's treatment schedule is uncertain, patients find it difficult to accurately predict the optimal time to arrive at the clinic, easily leading to excessively long waits or arriving late. Moreover, most of these systems cannot be integrated with other aspects of the patient's health management information, failing to provide a comprehensive health service experience.

[0007] In other words, there is a need to strengthen the integration of online and offline information. Summary of the Invention

[0008] In view of this, the main objective of the present invention is to provide a health management application integration system, in order to improve the inconvenience of users having to switch between different digital tools and to strengthen the integration of online and offline services.

[0009] This invention includes a health management application integration system, and the health management application integration system includes: One user client; A server, which communicates with the client, and includes: A reservation module; wherein, when the user terminal generates reservation information, the user terminal uploads the reservation information to the reservation module, and the reservation module stores the reservation information; A health diary module; wherein, when the user terminal generates a health diary record, the user terminal uploads the health diary record to the health diary module, and the health diary module stores the health diary record. A clinic terminal includes: A clinic's electronic device is connected to the server. When the clinic's electronic device receives the appointment information, it determines whether to generate an appointment confirmation message. If the clinic's electronic device generates the appointment confirmation message, it transmits the appointment confirmation message to the server. When the reservation module receives the reservation confirmation information, it sends a reservation success notification to the user's terminal.

[0010] This integrated health management application system can generate new services through its modules. For example, through the appointment module, users can directly select their desired doctor and appointment time on their mobile device and view available appointment options in real time. Furthermore, through the health diary module, users can directly record their health diary entries on their mobile device. In this way, users can book appointments and record their health diaries within the same application, eliminating the need to switch between multiple applications and providing a convenient user experience.

[0011] Furthermore, the present invention also includes another health management application integration system, and the health management application integration system further includes: A server, comprising: The consultation progress module stores consultation progress information; A clinic includes: A clinic electronic device is communicatively connected to a server; wherein, when the clinic electronic device generates a call number, the clinic electronic device uploads the call number to the consultation progress module of the server; wherein, when the consultation progress module receives the call number, the consultation progress module updates the consultation progress information according to the call number. A clinic display device is communicatively connected to the server to receive and display consultation progress information; and A user terminal connects to the server to receive and display the consultation progress information.

[0012] Because this health management application integrates a consultation progress module, patients can view their consultation progress online through the user interface and offline through the clinic's display device. Both the user interface and the clinic display device receive the consultation progress information from the server. This eliminates any discrepancies between online and offline information, thus providing a comprehensive health service experience. Simple Explanation of the Diagram

[0013] Figure 1: Block diagram of the health management application integration system of the present invention. Figure 2: Schematic diagram of the modules in the server of the health management application integration system of the present invention. Figure 3A: Schematic diagram of the login screen of the clinic display device of the health management application integration system of the present invention. Figure 3B: Schematic diagram of the entry screen of the clinic display device of the health management application integration system of the present invention. Figure 3C: Schematic diagram of the background check-in display of the clinic electronic device in the health management application integration system of the present invention. Figure 4A: Schematic diagram of the reservation screen of the reservation module of the health management application integration system of the present invention. Figure 4B: Schematic diagram of the appointment screen of the appointment module of the health management application integration system of the present invention. Figure 4C: A schematic diagram of the appointment module of the health management application integration system of the present invention completing an appointment. Figure 5: Schematic diagram of the health diary module of the health management application integration system of the present invention. Figure 6: Schematic diagram of the shared circle module screen of the health management application integration system of the present invention. Figure 7A: Schematic diagram of the clinic map screen of the health management application integration system of the present invention. Figure 7B: Schematic diagram of the collection module screen of the health management application integration system of the present invention. Figure 7C: Schematic diagram of clinic information screen of the health management application integration system of the present invention. Figure 8: A block diagram of another embodiment of the health management application integration system of the present invention. Implementation

[0014] Please refer to Figures 1 and 2. The health management application integration system of the present invention is executed on a user terminal 1, a clinic terminal 2, and a server 3. For example, the server 3 is a computer host or a server host.

[0015] The server 3 includes a reservation module 307 and a health diary module 309. When the client 1 generates reservation information, the client 1 uploads the reservation information to the reservation module 307, which stores the reservation information. When the client 1 generates health diary record information, the client 1 uploads the health diary record information to the health diary module 309, which stores the health diary record information.

[0016] In addition, the clinic terminal 2 includes a clinic electronic device 21, and the clinic electronic device 21 is communicatively connected to the server 3.

[0017] When the clinic's electronic device 21 receives the appointment information, it determines whether to generate an appointment confirmation message. If the clinic's electronic device 21 generates the appointment confirmation message, it transmits the appointment confirmation message to the server 3. When the appointment module 307 receives the appointment confirmation message, it transmits an appointment success notification message to the user terminal 1.

[0018] For example, the user terminal 1 is a mobile device or a computer host, which can be a mobile phone, a tablet computer, or a laptop computer. The clinic electronic device 21 is a mobile device or a computer host, which can be a mobile phone, a tablet computer, or a laptop computer.

[0019] This integrated health management application system combines online functions and optimizes existing systems. New services can be added through module expansion. For example, through the appointment module 307, users can directly select their desired doctor and appointment time on their mobile device and view available appointment options in real time. Furthermore, through the health diary module 309, users can directly record their health diary on their mobile device. This allows users to book appointments and record health diaries within a single application, eliminating the need to switch between multiple applications and providing a convenient user experience.

[0020] In this embodiment, the health management application integration system of the present invention further includes a business middle platform 31 and a technology middle platform 32.

[0021] Please refer to Figure 2. The business platform 31 further includes a consultation progress module 301, a digital check-in module 302, a clinic scrolling text module 303, an advertising module 304, a clinic information module 305, a doctor module 306, an appointment module 307, a vaccine information module 308, a health diary module 309, a statistical analysis module 310, a health information module 311, a sharing circle module 312, a push notification module 313, and a collection module 314.

[0022] The clinic terminal 2 further includes a clinic display device 22 that is communicatively connected to the server 3. Furthermore, the clinic display device 22 is a monitor or a television.

[0023] The consultation progress module 301 stores consultation progress information. When the clinic's electronic device 21 generates a call number, it uploads the call number information to the consultation progress module 301 on the server. When the consultation progress module 301 receives the call number information, it updates the consultation progress information accordingly. The clinic display device 22 is communicatively connected to the server 3 to receive and display the consultation progress information. The user terminal 1 is communicatively connected to the server 3 to receive and display the consultation progress information.

[0024] Referring to Figure 3A, in an embodiment of the present invention, the clinic display device 22 is communicatively connected to the server 3 and displays a clinic login screen. The clinic login screen includes clinic ID information 201, PIN code input information 202, and navigation information 203. The clinic ID information 201 allows clinic staff to enter a clinic account on the clinic display device 22. The PIN code input information 202 allows clinic staff to enter a PIN code on the clinic display device 22. The navigation information 203 connects to a clinic entry screen.

[0025] For example, clinic staff install a clinic display device application (APP) on the clinic display device 22, and the clinic display device 22 runs the clinic display device application to connect to the server 3. When the clinic display device 22 connects to the server 3, the clinic display device 22 displays the clinic login screen. Then, the clinic staff can enter the clinic account as "2208" in the clinic code information 201, and then enter the PIN code as "2234" in the PIN code information 202. Finally, the clinic staff can click the go information 203 to connect to the clinic entry screen.

[0026] Please refer to Figure 3B. In an embodiment of the present invention, the clinic entry screen includes a clinic information 3011, a check-in information 3021, a scrolling marquee information 3031, and an advertising information 3041.

[0027] The clinic display device 22 is connected to the consultation progress module 301 of the server 3 to receive consultation room information and display the consultation room information 3011 of the clinic entry screen based on the consultation room information. For example, the consultation room information 3011 includes information on the currently seeing doctor, consultation room number, consultation number, and consultation status. For example, the currently seeing doctor is "Dr. Xie", the consultation room number is "Second Consultation", the consultation number is "No. 13", and the consultation status is "Patient missed, currently up to No. 30".

[0028] The digital check-in module 302 displays a two-dimensional barcode. The clinic display device 22 is connected to the digital check-in module 302 of the server 3 to receive check-in information. When a user scans the check-in information 3021 through the mobile device to send the check-in data to the digital check-in module 302 of the server 3, when the digital check-in module 302 receives the check-in information, the digital check-in module 302 sends the check-in information to the clinic electronic device 21 of the clinic terminal 2, and the check-in information 3021 is displayed by the clinic display device 22.

[0029] Please refer to Figure 3C. For example, when a user scans the check-in information 3021 through the check-in option 412 on the mobile device to complete the check-in procedure, the back-end system of the clinic's electronic device 21 will display a user appointment information 3051. The user appointment information 3051 displays, for example: Date: 12 / 19 (Thursday) evening, Appointment number: 035, Appointment consultation time: 20:50, Doctor / Pharmacist: Song Ci, Check-in: 20:42, Name / ID number: Gao Xiaoyi / E12653****, Gender: Male, Year of birth: 63, Function: Detailed, Initial consultation: Initial consultation.

[0030] The clinic display device 22 is connected to the clinic scrolling module 303 of the server 3 to receive scrolling information, and the clinic display device 22 displays the scrolling information 3031 of the clinic entry screen based on the scrolling information. For example, the scrolling information 3031 displays, for example: "Welcome to the clinic to download the application starting today."

[0031] The advertising module 304 displays either a video advertisement or an image advertisement. The clinic display device 22 connects to the advertising module 304 of the server 3 to receive the advertising information, and displays the advertising information 3041 on the clinic's entry screen based on the advertising information. For example, the advertising information 3041 may display: "Mobile Registration APP, completely redesigned and officially launched."

[0032] Furthermore, the user terminal 1 has a user application (APP) installed on it. When the user terminal 1 executes the user application, it connects to the server 3. In this embodiment, the physician module 306 stores physician information, background consultation information, and patient data analysis information. The physician information includes a physician resume, a work schedule, physician information sharing, and satisfaction feedback. The background consultation information provides currently booked appointment information. The patient data analysis information consists of data collected and processed by the physician based on patient conditions, resulting in multiple patient records.

[0033] Furthermore, users can access physician information through the physician module 306 on the server 3 via the user terminal 1. For example, users can click on the physician's profile picture in the physician module 306 through their mobile device to obtain more physician information, such as: physician resume, specialties, and consultation hours. This physician information can be updated by the clinic's electronic device 21 on the clinic terminal 2 to ensure data accuracy.

[0034] Please refer to Figures 4A and 4B. When the client 1 executes the clinic appointment function of the client application, the client 1 connects to the server 3, and the client 1 displays the appointment clinic information 401, appointment date information 402, appointment time information 403 and selected doctor information 404 provided by the appointment module 307.

[0035] When the user terminal 1 generates the appointment information, it uploads the appointment information to the appointment module 307 of the server 3. When the appointment module 307 receives the appointment information, it transmits the appointment information to the clinic electronic device 21. When the clinic electronic device 21 receives the appointment information, it determines whether to generate an appointment confirmation message. If the clinic electronic device 21 generates the appointment confirmation message, it transmits the appointment confirmation message to the server 3. When the appointment module 307 receives the appointment confirmation message, it sends an appointment success notification message to the user terminal 1. In this way, the user can make a clinic appointment by generating the appointment information through the user terminal 1, and the doctor can also confirm and respond to the user's appointment through the clinic electronic device 21.

[0036] For example, as shown in Figures 4A and 4B, when the client 1 displays the appointment clinic information 401, appointment date information 402, appointment time slot information 403, and selected doctor information 404, the user can make an appointment by selecting these options from the information displayed on the client 1. Then, as shown in Figure 4B, when the user has made their selection, the client 1 generates and displays the appointment information 405. This appointment information includes details such as the clinic name, appointment date, appointment time slot, appointment number, and doctor, allowing the user to confirm the appointment details. Then, once the user confirms that the appointment details are correct, the user can log in by clicking the "Member Login" option 406 and entering their username and password. The user can then upload the appointment information to the appointment module 307 on the server. Alternatively, the user can enter the patient's name, date of birth, and ID number in the fields below the appointment information 405, and then click the "Next" option 407 to upload the appointment information to the appointment module 307 on server 3. Generally, if the user has pre-registered their membership information, they can log in directly through the "Member Login" option 406. After logging in, the user can directly enter the patient's name, date of birth, and ID number in the fields without needing to re-enter them.

[0037] Please refer to Figure 4C. When a user completes a clinic appointment using the application on the mobile device, the mobile device displays an appointment clinic item 408, an appointment time item 409, an attending physician item 410, an appointment list item 411, a scan code check-in option 412, an add to calendar option 413, and a cancel appointment option 414.

[0038] For example, the appointment clinic item 408 shows, for instance: Weight Testing Center Clinic; Appointment time item 409: 2024 / 12 / 19 (Thursday) evening appointment; Doctor item 410: Song Ci; Appointment list item 411: Gao Xiaoyi; Check-in number: 035; Appointment time: 20:50; Estimated check-in time: 20:40; Latest check-in time: 20:50. When the user completes the appointment, they can select the "Add to Calendar" option 413 to add the appointment information to the calendar reminder on the mobile device. When the user wishes to cancel the appointment, they can select the "Cancel Appointment" option 414 to cancel the appointment. Furthermore, when the user arrives at the clinic, they can use the application on the mobile device to select the "Scan to Check In" option 412 to scan the check-in information 3021 displayed on the clinic's display device 22 to complete the check-in process.

[0039] The vaccine module 308 stores multiple vaccine information entries, which include a vaccine overview, a target population, and a note.

[0040] For example, when client 1 executes a vaccine query function of the client application, client 1 connects to server 3 and generates vaccine query information, and client 1 uploads the vaccine query information to the vaccine module 308 of server 3. When the vaccine module 308 receives the vaccine query information, the vaccine module 308, based on the vaccine query information, queries one of the vaccine information entries corresponding to the vaccine query information from the multiple vaccine information entries, and transmits the queried vaccine information entry to client 1.

[0041] Please refer to Figure 5. The health diary module 309 stores reminder setting information, which includes a reminder time and a reminder content. When the health diary module 309 determines that the current time is the same as the reminder time, the health diary module 309 transmits the reminder content to the user terminal 1, and the user terminal 1 displays the reminder content to remind the user to drink water, measure blood pressure, or measure blood sugar, etc.

[0042] Furthermore, after a user completes actions such as drinking water, measuring blood pressure, or measuring blood sugar, the user can generate a health diary record by operating the user terminal 1. When the user terminal 1 generates the health diary record, it uploads the health diary record to the health diary module 309 on the server 3. When the health diary module 309 receives the health diary record, it stores the health diary record.

[0043] For example, when client 1 executes the health diary function of the client application, client 1 displays a water drinking record item 501, a blood pressure measurement item 502, and a blood glucose measurement item 503. The water drinking record item 501 provides a water drinking record area, a water drinking plan area, and a personal information area. The water drinking record area allows users to view their daily water drinking records and check whether they have met their set daily water drinking goals. The water drinking record information allows users to set the amount of water consumed and the type of beverage. The water drinking plan area allows users to set their daily water drinking goals, water drinking reminders, a target amount for a time interval, and a reminder start and end time. The personal information area allows users to input personal information, such as: biological sex, height, weight, pregnancy status, and average daily exercise. When the user inputs this personal information and saves it in the personal information area, the personal information area receives the personal information and calculates a daily recommended water intake to indicate whether to update the daily water drinking goal.

[0044] For example, users can record their water intake information through the mobile device; for instance, drinking 300 ml of tea corresponds to recording 285 ml of water. Users can set daily reminders for this water intake plan, such as: reminder interval: 1 hour, reminder start time: 8:00 AM, target amount for interval: 200 ml. Users can also input their personal information into the personal information area, such as: gender: male, height: 170 cm, weight: 70 kg, average daily exercise: 20 to 40 minutes. The personal information area will then display the user's recommended daily water intake of 3050 ml and remind the user to update the daily water intake target in the water intake plan to 3050 ml.

[0045] The blood pressure recording module 502 provides a blood pressure recording area and a blood pressure reminder setting area. This module provides users with daily blood pressure recording information and blood pressure reminder notifications. The blood pressure recording area allows users to input daily blood pressure information, recording time, and a remarks field, and provides reference blood pressure and heart rate ranges. The reminder setting area allows users to set morning and evening reminder times.

[0046] For example, users can record blood pressure information through the mobile device, such as: systolic pressure: 120, diastolic pressure: 60, heart rate: 80, recording time: 2024-11-21 / 10:00, remarks: 10 minutes after exercise. Users can set the blood pressure measurement time through the blood pressure reminder setting area, such as: morning reminder time: 8:00, evening reminder time: 22:00.

[0047] The blood glucose recording module 503 provides a blood glucose recording area and a blood glucose reminder setting area. This module provides users with daily blood glucose recording information and blood glucose reminder notifications. The blood glucose recording area allows users to input daily blood glucose information, a measurement period, a recording time, and a remarks field, and provides a reference blood glucose range. The reminder setting area allows users to set reminder times before and after breakfast, before and after lunch, before and after dinner, and before bedtime.

[0048] For example, users can record blood glucose information through the mobile device, such as: blood glucose: 60, measurement time: before breakfast, recording time: 2024-11-21 / 10:00, remarks: forgot to eat breakfast. Users can set blood glucose measurement time through the blood glucose reminder setting area, such as: before breakfast: 10:00 and after breakfast: 10:30.

[0049] Furthermore, the health information module 311 of server 3 provides users with access to health checkup information and vaccine information, and categorizes them according to usage status into a group category, a situation category, and a popular vaccine section. The health information module 311 stores multiple health information records.

[0050] For example, when client 1 generates a health query, client 1 uploads the health query to the health information module 311 of server 3. When the health information module 311 receives the health query, it retrieves a corresponding health information from among the multiple health information entries and transmits the retrieved health information to client 1.

[0051] Furthermore, when the user selects to view the health checkup information and the vaccination information, the health information module 311 stores the corresponding health checkup information and the vaccination information, and transmits the health checkup information and the vaccination information to the user terminal 1, which then displays the health checkup information and the vaccination information. For example, the health checkup information and the vaccination information include a target group area, a subsidy explanation area, a demographic area, a project cycle area, a remarks area, a sharing information area, a health setting reminder area, a data reference area, and a recommended clinic area.

[0052] This health reminder system includes a reminder subject, a reminder time, a clinic or pharmacy category, and a reminder message. The reminder subject includes a prescription refill label, an appointment label, and a medication administration label; users can use these labels or manually enter text into the reminder subject. The reminder time allows users to add the desired date and time. The clinic or pharmacy category allows users to select the name of the clinic they wish to be reminded of. The reminder message is for users to manually enter the desired reminder message.

[0053] This population classification is divided into children, adolescents, and adults. This situational classification is divided into vaccines for overseas travel, routine checkups, prenatal checkups for pregnant women, and checkups for young children. This popular vaccine category is divided into influenza vaccines, hepatitis B vaccines, and shingles vaccines.

[0054] For example, a user can connect to the health information module 311 on the server through the client 1 to query the child category and view the health check information and vaccination information of the child category stored in the health information module 311. The health check information and vaccination information may include, for example: "Seasonal flu vaccine", "Target group: Children aged nine and above who have not been vaccinated against the flu", "Subsidy description: Publicly funded, Group: Children (0-10 years old), Program cycle: 1. One dose for the first dose 2. One dose per year thereafter", "Remarks: Individuals with underlying diseases".

[0055] In addition, the health diary module 309 further includes a weight record item 504 and a medical record item 505. The weight record item 504 allows the user to record weight information and provides the Body Mass Index (BMI) and BMI range. The medical record item 505 displays the user's recent medical records.

[0056] For example, users can record their weight information through the mobile device, such as: height: 180cm, weight: 80kg, BMI: 24.6, normal range: 18.5 ≤ BMI < 24. Users can also select the medical record item 505 through the mobile device to display medical record information, such as: disease classification: acute sinusitis, medical institution: Sunshine ENT Clinic.

[0057] In addition, users can input health data through the user terminal 1, and the user terminal 1 can upload the health data to the statistical analysis module 310 of the server 3. The statistical analysis module 310 can convert the health data into a visual chart, provide change data, and display anomalies after comparison with standard values ​​such as age and gender.

[0058] For example, when a user generates health data information through the user terminal 1, when the user terminal 1 transmits the health data information to the statistical analysis module 310 in the server 3, the statistical analysis module 310 receives the health data information, generates statistical analysis information based on the health data information, and transmits the statistical analysis information to the user terminal 1.

[0059] Please refer to Figure 6. The sharing circle module 312 provides users with the ability to share content information. This shared content information includes water intake records, blood pressure records, blood glucose records, and medical records to the user who wishes to share. For example, when the user terminal 1 executes the sharing circle function of the user application, the user terminal 1 displays at least one sharer's information 601. The user must first select the sharer's information 601 corresponding to the sharer to be shared, then select the shared content information to be shared, and finally send a sharing request to the sharing circle module 312 of the server 3. When the sharing circle module 312 receives the sharing request, it transmits the shared content information to the sharer's mobile device.

[0060] For example, the client 1 includes a first user device 11 and a second user device 12, and the first user device 11 and the second user device 12 are respectively connected to the server 3. The user uses the first user device 11, while the sharer uses the second user device 12, that is, the second user device 12 is the sharer's mobile device.

[0061] Furthermore, when a user wants to invite others to become new sharers, the user can do so by selecting the "Send Share Code" option 602 displayed on the first user device 11 of the user terminal 1. When the user selects the "Send Share Code" option 602, the user needs to select the content information to be shared. Then, the first user device 11 sends the sharing request to the sharing circle module 312 of the server 3. When the sharing circle module 312 receives the invitation request, it generates sharing connection information. In this embodiment, the sharing connection information is a digital sharing code and a two-dimensional barcode. Next, the sharing circle module 312 transmits the sharing connection information to the first user device 11. The first user device 11 then displays the sharing connection information. The sharer can directly scan the two-dimensional barcode or enter the sharing link information of the first user device 11 with the digital sharing code through the second user device 12 to connect to the sharing circle module 312 of the server 3. The second user device 12 can read and display the shared content information through the sharing circle module 312.

[0062] For example, when a user generates the shared content information and the shared connection information through the first user device 11 of the user terminal 1, the first user device 11 uploads the shared content information and the shared connection information to the sharing circle module 312 in the server 3. When the second user device of the user terminal 1 receives the shared connection information, the second user device 12 transmits a user account to the sharing circle module 312 through the shared connection information. The second user device 12 can then read and display the shared content information through the sharing circle module 312. When the sharing circle module 312 transmits the shared connection information to the second user device 12, the sharing circle module 312 further transmits the sharer's user account to the first user device 11.

[0063] The push notification module 313 stores at least one set reminder list. Users can also connect to the push notification module 313 through the user terminal 1 to set a custom reminder. The clinic terminal 2 can push information to specific patients through the push notification module 313, such as: medical orders, health education information, health check-up services, clinic out-of-pocket services, and reminders for the next health check-up (blood test), etc. In addition, the push notification module 313 can combine pharmacy reminders to send prescription information to the user terminal 1.

[0064] For example, clinic 2 generates a medication collection information and uploads it to the push notification module 313 of server 3. When push notification module 313 receives the medication collection information, it generates a medication collection reminder based on the information and sends it to user terminal 1, reminding the user to pick up the prescription medication from the pharmacy.

[0065] Referring to Figures 7A, 7B, and 7C, when client 1 executes the bookmark function of the client application, client 1 connects to server 3 and generates a clinic query. The clinic information module 305 of server 3 stores multiple clinic information entries. As shown in Figure 7A, when client 1 generates the clinic query, it uploads the query to the clinic information module 305 of server 3. When clinic information module 305 receives the query, it retrieves the corresponding clinic information entry from the multiple entries and sends it to client 1. For example, when a user connects to the clinic information module 305 of server 3 through client 1 and selects the desired clinic information, clinic information module 305 sends the corresponding clinic information, such as: OX Dental Clinic, OO City, XX District, OXO Street, 0th Floor, Clinic, Dental.

[0066] The collection module 314 allows users to save clinic information. For example, a user can save the selected clinic information to the collection module 314 through the client 1. In other words, the collection module 314 can store multiple saved clinic information entries. As shown in Figure 7B, the user can access the multiple saved clinic information entries by connecting to the collection module 314 through the client 1, and the client 1 displays a clinic name 701, a clinic address 702, a clinic information 703, and a relative distance 704 from the multiple clinic information entries. Furthermore, the user can also click on one of the clinic information entries to view its detailed content, as shown in Figure 7C. The detailed content of the clinic information includes an overview area 705, an operating hours area 706, a doctor introduction area 707, and a latest news area 708.

[0067] The overview area 705 displays a clinic type, medical specialties, an address, a telephone number, and a service offered. For example, overview area 705 may display: "Clinic type: Clinic", "Medical specialties: No specialties", "Address: No. 123, Qixian Rd., Yancheng District, Kaohsiung City", "Telephone: 07-5326288" and "Service offered: Outpatient medical care".

[0068] The business hours section 706 displays the clinic's hours and the doctor's hours. For example, the business hours section 706 displays: "Clinic hours: Monday, December 9th, 6:00-12:00; Doctor's hours: Li Shizhen, Yuan Qu, and Pharmacy in the morning."

[0069] The physician introduction section 707 displays a physician's information. This physician information includes a physician's work schedule, a specialty, and educational background. For example, the physician introduction section 707 displays, for instance: "Physician's work schedule: Tuesdays, Specialty: Oral cancer, throat cancer, and Educational Background: Doctoral program at the Institute of Brain Science, Yangming Medical University."

[0070] The latest news section 708 displays the latest news information, such as: "Clinic Connect briefing is coming! First launch in December, welcome to try it out."

[0071] For example, a user can select one of the clinic's information entries through the client 1, thereby generating a "add to favorites" entry, and upload the "add to favorites" entry to the favorites module 314 in the server 3. When the favorites module 314 receives the "add to favorites" entry, it searches for the corresponding clinic entry from the multiple clinic entries based on the "add to favorites" entry, and sends the added clinic entry to the client 1.

[0072] In addition, the technology platform 32 further includes an identity verification module 315, an authorization module 316, a push notification module 317, a voice call module 318, a reminder module 319, a membership module 320, and a QR code recognition module 321.

[0073] The 315 authentication module is used to verify the safety of people logging into the system and to prevent hacker intrusion.

[0074] For example, when a user generates login information through the client 1, the client 1 uploads the login information to the authentication module 315 in the server 3. When the authentication module 315 receives the login information, it determines whether to generate identity verification information based on the login information. If the authentication module 315 generates the identity verification information, it transmits the identity verification information to the server 3. When the authentication module 315 receives the identity verification information, it sends an identity verification success notification to the client 1.

[0075] The authorization module 316 provides third-party identity verification services to ensure the authenticity of the user's identity. After logging in via the mobile device, user terminal 1 uses the authorization module 316 to ensure that the user can use the authorized functions. For example, after logging into an application via the mobile device, a regular user can use the application's related functions. After logging into the backend of the clinic's electronic device 21, the clinic administrator can use the clinic's activated functions. In addition, clinic administrators are divided into system administrators and project administrators, and corresponding authorized functions will be granted according to their different identities.

[0076] The push module 317 transmits push information to the client 1. For example, the user connects to the push module 317 in the server 3 through the client 1, and the push module 317 transmits the push information to the client 1.

[0077] The voice call module 318 is used to provide voice call functionality. For example, a clinic doctor can generate a voice call information through the clinic's electronic device 21, and the clinic's electronic device 21 further uploads the voice call information to the voice call module 318 in the server 3. When the voice call module 318 receives the voice call information, it transmits the call information to the clinic's display device 22, allowing the clinic's display device 22 to call the numbers according to the voice call module 318.

[0078] The reminder module 319 is used to provide reminder notifications to the user terminal 1. For example, a clinic doctor can generate a reminder notification through the clinic's electronic device 21, and the clinic's electronic device 21 can further upload the reminder notification to the reminder module 319 in the server 3. When the reminder module 319 receives the reminder notification, it transmits the reminder notification to the user terminal 1 so that the user can view the reminder notification.

[0079] The membership module 320 provides users with the option to register as members. For example, a user can upload registration information to the membership module 320 on the server via the mobile device. When the membership module 320 receives the registration information, it generates a registration success message and sends it to the user's device 1, allowing the user to confirm the successful registration.

[0080] The barcode scanning module 321 provides one- or two-dimensional barcode information. For example, a user can scan the two-dimensional barcode information using the mobile device to communicate with the barcode scanning module 321 on the server 3 and display the barcode information.

[0081] Referring to Figure 8, another embodiment of the present invention further includes a domestic helper care device 4, which is communicatively connected to the server 3. The server 3 further includes a daily care record module 322 and a custom check reminder module 323.

[0082] The daily care record module 322 is used by caregivers to record the daily health data of the person being cared for and then send it to the employer. When the domestic helper care device 4 generates daily health information, it uploads the daily health information to the daily care record module 322 on the server 3. When the daily care record module 322 receives the daily health information, it identifies whether the data is abnormal, and if it is abnormal, it sends an alert message to the user terminal 1.

[0083] For example, caregivers record their daily health data and upload it to the daily care record module 322 on server 3 so that the owner can view the caregiver's daily health data at any time. When the data recorded by the caregiver is abnormal, the daily care record module 322 sends an alert message to the owner.

[0084] Furthermore, when the daily care record module 322 is activated, the domestic helper care device 4 must first confirm the master-slave relationship with the employer's main account by scanning the two-dimensional barcode information generated by the user terminal 1. All health records belong to the main account.

[0085] The custom check reminder module 323 allows the main account to customize daily check items, such as medication and exercise, and set reminders at specific times to help monitor the health of the elderly.

[0086] For example, when the user terminal 1 generates a check reminder message, the user terminal 1 uploads the check reminder message to the custom check reminder module 323 of the server 3. When the custom check reminder module 323 receives the check reminder message, the custom check reminder module 323 sends a check reminder to the domestic helper care device 4.

[0087] Furthermore, another embodiment of the present invention also provides a multilingual setting. For example, when the caregiver is a foreigner, they can switch languages ​​to operate the application (APP).

[0088] The following describes another embodiment of the present invention, detailing the functions of recording, generating, and sharing daily health data, as well as the operation of caregiver records:

[0089] The data entry and verification test system performs functional tests to verify the accuracy of the daily health data entry and the data verification mechanism. It tests the accuracy of manual input and device-synchronized data on the user terminal 1, and checks whether the server 3 correctly processes and stores data verification.

[0090] The report generation test system verifies whether the generated health data report and its visualization charts meet expectations. It tests the format, content, and accuracy of the data analysis in the health data report. It ensures that the server-side 3 can generate both periodic and real-time reports.

[0091] The data sharing function test is to test the functionality of the sharing module 312 to ensure that the generated shared content information and shared connection information can correctly authenticate identity and share data.

[0092] The caregiver record and alert function test examines the daily care record module 322 to verify the accuracy of the daily health data entered by the domestic helper care device 4 and the effectiveness of the abnormality alert function. It checks whether the daily care record module can immediately send an alert message to the main account when the daily health data is abnormal. The test also examines the setting of the check reminder information and the effectiveness of the on-time reminders in the custom check reminder module 323.

[0093] A multilingual support test system tests the multilingual settings function in server 3 to ensure that the interface and functions of different language versions can be displayed and operated correctly by users with different language backgrounds.

[0094] The above description is merely an embodiment of the present invention and is not intended to limit the present invention in any way. Although the present invention has been disclosed above by way of embodiment, it is not intended to limit the present invention. Any person skilled in the art can make some modifications or alterations to the above-disclosed technical content to create equivalent embodiments without departing from the scope of the technical solution of the present invention. Any simple modifications, equivalent changes and alterations made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solution of the present invention shall still fall within the scope of the technical solution of the present invention.

[0095] 1: User end 11: First User 12: Second user 2: Clinic side 21: Clinic Electronic Devices 22: Clinic display device 201: Clinic Code Information 202: Enter PIN code information 203: Go to Information 3: Server 31: Business Platform 32: Technology Platform 301: Consultation Progress Module 302: Digital Check-in Module 303: Clinic Scrolling Module 304: Advertising Module 305: Clinic Information Module 306: Physician Module 307: Reservation Module 308: Vaccine Information Module 309: Health Diary Module 310: Statistical Analysis Module 311: Health Information Module 312: Shared Circle Module 313: Push Notification Module 314: Collection Module 315: Identity Verification Module 316: Authorized Module 317: Push Module 318: Voice Calling Module 319: Reminder Module 320: Member Module 321: QR code identification module 322: Daily Care Record Module 323: Custom Inspection Reminder Module 3011: Clinic Information 3021: Registration Information 3031: Scrolling News 3041: Advertising Information 3051: User Reservation Information 4: Domestic Helper Care Device 401: Clinic Appointment Information 402: Appointment Date Information 403: Appointment Time Information 404: Select Doctor Information 405: Appointment Information 406: Member login option 407: Next Step Options 408: Clinic Appointment Program 409: Appointment Time Item 410: Doctor Consultation Program 411: Appointment List Item 412: Scan QR code to check in option 413: Added calendar option 414: Cancel appointment option 501: Water Drinking Record Project 502: Blood Pressure Measurement Items 503: Blood Glucose Measurement Items 504: Weight Record Item 505: Medical Record Items 601: Sharer Information 602: Send Share Code Option 701: Clinic Name 702: Clinic Address 703: Clinic Information 704: Relative Distance 705: Overview Area 706: Business Hours Area 707: Doctor Introduction Area 708: Latest News Section

Claims

1. A health management application integration system, comprising: a user terminal; a server communicatively connected to the user terminal, and comprising: an appointment module; wherein, When a user terminal generates an appointment request, the user terminal uploads the appointment request to the appointment module, which stores the appointment request; a health diary module; wherein, when the user terminal generates a health diary record, the user terminal uploads the health diary record to the health diary module, which stores the health diary record. The health diary module also stores reminder setting information, which includes a reminder time and a reminder content; a clinic terminal, comprising: a clinic electronic device communicatively connected to the server; wherein, when the clinic electronic device receives the appointment request, the clinic electronic device determines whether to generate an appointment confirmation message, and when the clinic electronic device generates the appointment confirmation message, the clinic electronic device transmits the appointment confirmation message to the server; wherein, when the appointment module receives the appointment confirmation message, the appointment module transmits an appointment success notification message to the user terminal; When the health diary module determines that the current time is the same as the reminder time, the health diary module sends the reminder content to the user's terminal, and the user's terminal displays the reminder content.

2. The health management application integration system as described in claim 1, wherein, The server further includes: a health information module storing multiple health information records; wherein, when the user client generates a health query, the user client uploads the health query information to the health information module of the server; wherein, when the health information module receives the health query information, the health information module, based on the health query information, queries one of the health information records corresponding to the health query, and transmits the queried health information record to the user client.

3. The health management application integration system as described in claim 1, wherein, The client includes a first user device and a second user device; wherein the first user device and the second user device are respectively communicatively connected to the server; wherein the server further includes a sharing circle module; wherein when the first user device of the client generates shared content information and a shared connection information, the first user device uploads the shared content information and the shared connection information to the sharing circle module of the server; wherein when the second user device of the client receives the shared connection information, the second user device connects to the sharing circle module through the shared connection information, transmits a user account to the sharing circle module, and the second user device reads and displays the shared content information through the sharing circle module; wherein when the sharing circle module transmits the shared content information to the second user device, the sharing circle module further transmits the user account to the first user device.

4. The health management application integration system as described in claim 1, wherein, The server further includes: a push notification module; wherein, when the clinic generates a medication collection information, the clinic device uploads the medication collection information to the push notification module of the server; wherein, when the push notification module receives the medication collection information, the push notification module generates a medication collection reminder based on the medication collection information, and the push notification module transmits the medication collection reminder to the user terminal.

5. The health management application integration system as described in claim 1, wherein, The server further includes: a collection module that stores multiple clinic information records; wherein, when the user client generates a collection information record, the user client uploads the collection information record to the collection module of the server; wherein, when the collection module receives the collection information record, the collection module searches for one of the clinic information records corresponding to the collection information record from the multiple clinic information records based on the collection information record, and transmits the collection information record to the user client.

6. The health management application integration system as described in claim 1 further includes: a domestic helper care device communicatively connected to the server; wherein, The server further includes a daily care record module; wherein, when the domestic helper care device generates daily health information, the domestic helper care device uploads the daily health information to the daily care record module of the server; wherein, when the daily care record module receives the daily health information, the daily care record module identifies whether the daily health information is abnormal, and when the daily health information is abnormal, the daily care record module sends an alert message to the user terminal.

7. The health management application integration system as described in claim 6, wherein, The server further includes: a custom check reminder module; wherein, when the user generates a check reminder message, the user uploads the check reminder message to the custom check reminder module of the server; wherein, when the custom check reminder module receives the check reminder message, the custom check reminder module transmits a check reminder to the domestic helper care device.

8. The health management application integration system as described in claim 1, wherein, The server further includes: a digital check-in module; wherein, when the user generates a check-in message, the user uploads the check-in message to the digital check-in module of the server; wherein, when the digital check-in module receives the check-in message, the digital check-in module transmits the check-in message to the clinic's electronic device.

Images