WO2026003587A2 - Disater medicial assistance system - Google Patents

Abstract

Provided is a disaster medical assistance system, which allows the management terminal to establish disaster information and add a disaster site via a control interface generated by a cloud control platform. Then, an advance team is dispatched to the disaster site, and disaster site assessment information is generated and transmitted by using a user interface of a mobile terminal. Subsequently, as needed, the management terminal continues to dispatch a medical team to the disaster site. The medical team generates and transmits information such as triage, medical treatment, and/or evacuation of the injured individuals, and collects and analyzes such information by using the user interface of the mobile terminal to assist the commander in understanding the disaster site status and supporting subsequent decision-making.

Description

DISATER MEDICIAL ASSISTANCE SYSTEM

BACKGROUND

Technical Field

The present disclosure relates to the technical field of disaster medical assistance, and more particularly, to a disaster medical assistance system that provides real-time response upon the occurrence of a disaster event (such as a natural disaster or a manmade accident).

Description of Related Art

Whenever a large-scale disaster occurs, the relevant disaster response units typically establish an emergency response center and coordinate with official or civilian medical rescue teams to carry out disaster relief, with the aim of quickly locating injured individuals at the disaster site and providing triage, medical treatment, or evacuation services.

In the past, communication between the emergency response center and the medical rescue teams has mostly relied on mobile phones or instant messaging software, which fails to achieve synchronous and effective information transmission. On-site members of the medical rescue team must perform triage or treatment procedures for injured individuals, and at the same time, record related treatment information. However, for triage and medical treatment information, paper-based recording methods are still commonly used. This not only consumes the time and effort of rescuers but also introduces greater difficulty and complexity in subsequent data compilation and statistical analysis related to the disaster, thereby preventing real-time reflection of the rescue status at the disaster site.

Therefore, how to design a disaster medical assistance system that can effectively improve upon the aforementioned issues is a problem urgently in need of resolution. SUMMARY

The present disclosure provides a disaster medical assistance system, which may utilize a cloud control platform as a medium, allowing remote data transmission or communication between a commander and on-site personnel to enable real-time understanding of the disaster site situation.

According to at least one embodiment of the disaster medical assistance system provided by the present disclosure, all information related to the occurrence and handling of the disaster may be digitized and consolidated, replacing the inconvenience of recording and transmitting such information using traditional paper-based methods.

According to at least one embodiment of the disaster medical assistance system provided by the present disclosure, the commander may establish independent disaster events via a control interface provided by the cloud control platform and assign on-site personnel as needed, granting them corresponding execution tasks.

According to at least one embodiment of the disaster medical assistance system provided by the present disclosure, on-site personnel may utilize a user interface on a mobile electronic device (e.g., a mobile phone) to perform tasks such as personnel check-in, disaster site assessment, triage, and medical treatment of the injured individuals, and transmit related information back to the cloud control platform.

According to at least one embodiment, the disaster medical assistance system provided by the present disclosure may further be integrated with a hospital terminal, whereby after transferring an injured individual to a suitable hospital, relevant medical information of the injured individual may be provided to the hospital terminal for continued treatment or management.

In at least one embodiment of the present disclosure, the disaster medical assistance system comprises a cloud control platform and a plurality of mobile terminals. In at least one embodiment of the present disclosure, the cloud control platform is configured to allow a management terminal to be assessed via a network connection to generate a control interface. In at least one embodiment of the present disclosure, the cloud control platform comprises a disaster event management module, an advance team management module, and a medical team management module. In at least one embodiment of the present disclosure, the disaster event management module is configured to receive an event establishment command via the control interface to establish a disaster event and add a disaster site. The advance team management module is configured to receive an advance team assignment command via the control interface to select a plurality of advance team members to form an advance team and notify the advance team to proceed to the disaster site. The advance team management module is configured to also receive first return information from any of the advance team members in real time via the user interface, wherein the first return information includes at least one of first check-in information, first disaster site assessment information, first triage information, first medical treatment information, and first evacuation information. The medical team management module is configured to receive a medical team assignment command via the control interface to select a plurality of medical team members to form a medical team and notify the medical team to proceed to the disaster site. The medical team management module is also configured to receive second return information from any of the medical team members in real time via the user interface, wherein the second return information includes at least one of second check-in information, second disaster site assessment information, second triage information, second medical treatment information, and second evacuation information. In at least one embodiment of the present disclosure, each of the mobile terminals is operated by one of the advance team members or the medical team members and configured to connect to the cloud control platform via the network to generate the user interface. Each of the mobile terminals includes a disaster site assessment module, a triage module, a medical treatment module, and an evacuation module. In at least one embodiment of the present disclosure, the disaster site assessment module is configured to generate a disaster site assessment form on the user interface and receive environmental assessment content for the disaster site through the disaster site assessment form to generate at least one of the first disaster site assessment information and the second disaster site assessment information. The triage module is configured to scan an identification code of a patient via the user interface to generate a triage form and receive triage content through the triage form to generate at least one of the first triage information and the second triage information. The medical treatment module is configured to scan the identification code of the patient via the user interface to generate a medical treatment form and receive medical treatment content of the patient through the medical treatment form to generate at least one of the first medical treatment information and the second medical treatment information. The evacuation management module is configured to scan the identification code of the patient via the user interface to generate an evacuation form and receive evacuation content of the patient through the evacuation form to generate at least one of the first evacuation information and the second evacuation information.

In some embodiments of the present disclosure, the advance team management module is configured to receive the advance team assignment command after a disaster site is established, and the medical team management module is configured to receive the medical team assignment command via the control interface after the advance team is formed.

In some embodiments of the present disclosure, the cloud control platform further comprises a data collection module. The data collection module collects and analyzes at least one of the first return information and the second return information and generates a visual chart-based data analysis result.

In some embodiments of the present disclosure, the cloud control platform further comprises a personnel database that stores a plurality of personnel records, and the advance team management module is configured to select a plurality of advance team members from the personnel database to form the advance team.

In some embodiments of the present disclosure, prior to forming the medical team, the advance team management module is configured to disband the advance team, and the medical team management module is configured to select the medical team members from the personnel database to form the medical team.

In some embodiments of the present disclosure, prior to forming the medical team, the advance team management module is configured to disband the advance team, and the medical team management module is configured to directly convert at least one advance team member into a medical team member and omit the check-in procedure for the converted medical team member.

In some embodiments of the present disclosure, the advance team management module comprises an advance team check-in unit. After forming the advance team, the advance team check-in unit is configured to display the advance team check-in menu on the corresponding user interface of the mobile terminal operated by each of the advance team members. After the advance team check-in unit receives the first checkin information generated from the advance team check-in menu transmitted by any of the advance team members, the advance team check-in unit is configured to hide the advance team check-in menu displayed on the corresponding user interface of the mobile terminal operated by each of the advance team members and display at least one of the disaster site assessment form, the triage form, the medical treatment form, and the evacuation form.

In some embodiments of the present disclosure, the medical team management module comprises a medical team check-in unit. The medical team members are divided into at least one administrative group member and a plurality of non- administrative group members. After forming the medical team, the medical team check-in unit is configured to display the medical team check-in menu on the corresponding user interface of the mobile terminal operated by each of the administrative group members. After the medical team check-in unit receives the second check-in information transmitted by any of the administrative group members via the medical team check-in menu, the medical team check-in unit is configured to display a check-in identification code on the corresponding user interface of the mobile terminal of each of the administrative group members, and display a check-in scanning menu on the corresponding user interface of the mobile terminal operated by each of the non-administrative group members. After the medical team check-in unit receives the second check-in information transmitted by any of the non-administrative group members via scanning the check-in identification code on the corresponding user interface, the medical team check-in unit is configured to hide the check-in scanning menu and display at least one of the disaster site assessment form, the triage form, the medical treatment form, and the evacuation form.

In some embodiments of the present disclosure, the cloud control platform further comprises a medical institution database, and the evacuation management module is configured to select a destination medical institution for the patient based on the medical institution database.

In some embodiments of the present disclosure, the disaster medical assistance system further comprises a plurality of hospital terminals. Each of the hospital terminals is connected to the cloud control platform via the network to generate a patient control interface, and each of the hospital terminals comprises a patient receiving module configured to scan the identification code of the patient and confirm the identification code in accordance with the first evacuation information or the second evacuation information to receive the patient.

In some embodiments of the present disclosure, the medical team management module is configured to present a specific function menu of a task group on the corresponding user interface according to the task group assigned to each of the medical team members.

In some embodiments of the present disclosure, the cloud control platform is configured to prevent another medical treatment module on another mobile terminal from generating another medical treatment form for a same patient before the medical treatment form generated from the medical treatment module of the mobile terminal for the same patient is closed.

In some embodiments of the present disclosure, at least one of the first medical treatment information and the second medical treatment information includes subjective and objective diagnostic content for the patient, and the medical treatment module is configured to display a summarized version of the subjective and objective diagnostic content on the user interface.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure can be more fully understood by reading the following detailed descriptions of the embodiments, with reference made to the accompanying drawings.

FIG. 1 is a schematic diagram of the disaster medical assistance system of the present disclosure.

FIG. 2 is another schematic diagram of the disaster medical assistance system of the present disclosure.

FIG. 3 is a schematic diagram illustrating the establishment of a disaster event via the control interface in the disaster medical assistance system of the present disclosure.

FIG. 4 is a schematic diagram showing the state before and after check-in is completed via the user interface in the disaster medical assistance system of the present disclosure.

FIG. 5 is a schematic diagram showing the display of a check-in identification code and the state before and after check-in is completed via the user interface in the disaster medical assistance system of the present disclosure.

FIG. 6 is a schematic diagram showing the display of data analysis results on the control interface in the disaster medical assistance system of the present disclosure.

FIG. 7 is a flowchart illustrating the overall system operation of the disaster medical assistance system of the present disclosure.

FIG. 8 is a schematic diagram showing the display of a disaster site assessment form on the user interface in the disaster medical assistance system of the present disclosure.

FIG. 9 is a schematic diagram showing the display of a triage form on the user interface in the disaster medical assistance system of the present disclosure.

FIG. 10 is a schematic diagram showing the display of a medical treatment form on the user interface in the disaster medical assistance system of the present disclosure.

FIG. 11 is a schematic diagram showing the display of an evacuation form on the user interface in the disaster medical assistance system of the present disclosure.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Since various embodiments and examples are merely illustrative and not limiting, after reading this specification, one of ordinary skill in the art could also conceive other embodiments or examples within the scope of the disclosure without deviating from the scope of the present disclosure. The characteristics and advantages of these embodiments can be further illustrated by the following detailed description and claims.

In this disclosure, the terms “a” or “an” are used to describe elements and components described herein. This is merely for convenience of explanation and should be understood to have a general meaning within the scope of this disclosure. Therefore, unless explicitly stated otherwise, such descriptions should be understood to include one or at least one, and singular terms also include plural. In this disclosure, the terms such as “comprise,” “include,” “have,” or other similar terms are intended to cover non-exclusive inclusions. For example, components or structures containing multiple elements are not limited to those elements listed herein but can also include other elements that are typically inherent to that component or structure, even if not explicitly listed.

Please refer to FIGs. 1 and 2, where FIG. 1 shows a schematic diagram of the disaster medical assistance system 1 of the present disclosure, and FIG. 2 shows another schematic diagram of the disaster medical assistance system 1 of the present disclosure. As shown in FIGs. 1 and 2, the disaster medical assistance system 1 of the present disclosure primarily includes a cloud control platform 10. In at least one embodiment of the present disclosure, the cloud control platform 10 can be formed by using one or more servers, where storage devices within the servers may store relevant software programs and databases (e.g., personnel database and medical institution database). The processor within the server can execute the software programs to generate an operation interface and allow different users to access via a network connection to apply the operation interface and perform corresponding functions.

In at least one embodiment of the present disclosure, the cloud control platform 10 can generate different functional interfaces based on the user’s access permissions. For example, the cloud control platform 10 can allow to be accessed by the management terminal 20 via a network connection and generate a control interface that will be displayed on the management terminal 20. In at least one embodiment of the present disclosure, the management terminal 20 can be an electronic device such as a computer, a tablet, or a mobile phone, so that the operator of the management terminal 20 (e.g., a commander or a manager) can use the control interface to establish or manage disaster events and further perform related control functions and settings.

In at least one embodiment, the disaster medical assistance system 1 of the present disclosure can further incorporate a plurality of mobile terminals 30. In the disaster medical assistance system 1 of the present disclosure, the cloud control platform 10 or other network platforms can also pre-install or store emergency rescue applications (APP). For example, each mobile terminal 30 can pre-download and perform the emergency rescue application to access and exchange information with the cloud control platform 10 via a network connection.

In at least one embodiment of the present disclosure, the cloud control platform 10 can allow any mobile terminal 30 to access via a network connection and generate a user interface, which will be displayed on the mobile terminal 30. In at least one embodiment of the present disclosure, the mobile terminal 30 can be a portable electronic device such as a tablet or a mobile phone, so that the operator of the mobile terminal 30 (e.g., the advance team members or the medical team members as described below) can perform assigned tasks or functions via the user interface. In other words, the operator of the management terminal 20 and each mobile terminal 30 can use the cloud control platform 10 as a medium to exchange digital disaster assistance information over the network connection, enabling the operator of the management terminal 20 to monitor the real-time status of disaster events and carry out corresponding commands and coordination, so as to facilitate the operator of the mobile terminal 30 to complete the rescue operations.

Please also refer to FIGs. 2 and 3, where FIG. 3 shows a schematic diagram of the disaster medical assistance system 1 of the present disclosure for establishing a disaster event using the control interface. As shown in FIGs. 2 and 3, in at least one embodiment of the present disclosure, the cloud control platform 10 includes a disaster event management module 11, an advance team management module 12, and a medical team management module 13, and these modules are electrically connected to each other.

In at least one embodiment of the present disclosure, the disaster event management module 11 is configured to provide disaster event management functions and receive an event establishment command via the control interface to establish a disaster event and add a disaster site. In at least one embodiment of the present disclosure, the disaster event management module 11 can display a disaster event management menu on the control interface, so that the operator of the management terminal 20 can input a command through the disaster event management menu of the control interface to establish or terminate a disaster event. In at least one embodiment of the present disclosure, during the process of establishing a disaster event, the operator of the management terminal 20 needs to input disaster-related information (such as the disaster name and whether it is an official disaster, etc.) via the control interface. After the disaster event is established, the disaster event management module 11 will record the establishment time and the establisher of the disaster event.

In at least one embodiment of the present disclosure, once the disaster event is established, the operator of the management terminal 20 can input a command via the control interface to add or delete a disaster site. In at least one embodiment of the present disclosure, once a disaster site is added, the disaster event management module 11 will display relevant information of the disaster site (such as the disaster name, address, current processing status, etc.) and available options of a disaster site management menu on the control interface, allowing the operator of the management terminal 20 to assign relevant personnel to provide medical assistance for that disaster site. The disaster site can be deleted after medical assistance operations are completed at that disaster site. In some embodiments of the present disclosure, one or more disaster sites can be added for the same disaster event, and the control interface may be set to only allow the disaster event to be terminated once all disaster sites in that disaster event are deleted. In some embodiments of the present disclosure, the disaster event management module 11 may record the creation time and the creator of a disaster site after the disaster site is added and record the deletion time and the person who deleted the disaster site after the disaster site is removed. In at least one embodiment of the present disclosure, the advance team management module 12 is configured to provide advance team management functions. The advance team management module 12 is configured to receive the advance team assignment command via the control interface and select a plurality of advance team members to form an advance team, which is then assigned to the disaster site for assessment. In some embodiments of the present disclosure, the advance team management module 12 may display an advance team assignment menu on the control interface, enabling the operator of the management terminal 20 to input a command through the advance team assignment menu of the control interface. The advance team management module 12 may automatically select a plurality of advance team members to form the advance team, or the operator of the management terminal 20 may manually select a plurality of advance team members from the personnel database built into the cloud control platform 10 to form the advance team. In some embodiments of the present disclosure, the advance team management module 12 only allows to receive the advance team assignment command after the disaster site has been established; that is to say, the advance team management module 12 will provide the advance team assignment function via the control interface only after the disaster site has been established.

In some embodiments of the present disclosure, the control interface can prescreen qualified members from the personnel database according to the composition and number of the advance team members (e.g., one doctor, two nurses, one Emergency Operation Center (EOC) member, one public health department member, etc.) recommended by the disaster medical assistance system 1. Alternatively, the operator of the management terminal 20 can manually select and edit the composition and number of the qualified members to form the advance team to be assigned to the disaster site. In some embodiments of the present disclosure, if any person in the personnel database has already been assigned to another task (e.g., already working at another disaster site), such person will not be eligible to be selected as the advance team member. In some embodiments of the present disclosure, once the advance team has been successfully formed and assigned to the disaster site, the relevant information of the disaster site displayed on the control interface will be updated to reflect the status that the advance team has been assigned.

In at least one embodiment of the present disclosure, the advance team management module 12 is configured to receive the first return information in real time from any of the advance team members via the mobile terminal 30 and reflect it on the control interface. In some embodiments of the present disclosure, the first return information may include at least one of the first check-in information of the advance team member, the first disaster site assessment information, the first triage information, the first medical treatment information, and the first evacuation information. In at least one embodiment of the present disclosure, the primary task of the advance team is to assess the current status of the disaster site and, after conducting the environment assessment of the disaster site, return the relevant information to the cloud control platform 10. Therefore, the disaster medical assistance system 1 of the present disclosure requires receiving the first check-in information from the advance team members to confirm the arrival of the advance team at the disaster site. Based on the received assessment information of the disaster site, the operator of the management terminal 20 can determine whether to assign a medical team to the disaster site. Additionally, in some embodiments of the present disclosure, the advance team can also assist in subsequent medical rescues and provide triage information, medical treatment information, and evacuation information of the injured individuals as part of the first return information.

Please also refer to FIGs. 2 and 4. FIG. 4 is a schematic diagram showing the disaster medical assistance system 1 before and after check-in on the user interface. As shown in FIGs. 2 and 4, in some embodiments of the present disclosure, the advance team management module 12 includes an advance team check-in unit 121. In some embodiments of the present disclosure, after the advance team is formed, the advance team check-in unit 121 is configured to restrict the corresponding user interface of the mobile terminal 30 operated by each of the advance team members to display only the advance team check-in menu, without other function menus available. When the advance team management module 12 receives the first check-in information generated from the advance team check-in menu transmitted by any of the advance team members, the advance team check-in unit 121 is configured to hide the advance team check-in menu displayed on the corresponding user interface of the mobile terminal 30 operated by each of the advance team members, and display at least one of the disaster site assessment form, the triage form, the medical treatment form, and the evacuation form. Thus, once any of the advance team members returns the first check-in information to the advance team management module 12, the disaster medical assistance system 1 of the present disclosure will recognize that the advance team has arrived at the disaster site, facilitating the subsequent environmental assessment tasks of the disaster site.

In some embodiments of the present disclosure, the advance team management module 12 can receive the assessment information of the disaster site transmitted in real time by the advance team members. The operator of the management terminal 20 can then select the “View Assessment Form” option in the disaster site column on the control interface. The related assessment information of the disaster site will be displayed on the control interface to assist the operator of the management terminal 20 in determining the required manpower and tasks for the medical team. In some embodiments of the present disclosure, the control interface may arrange the received assessment information of the disaster site according to the update time, enabling the operator of the management terminal 20 to grasp the latest assessment content.

In at least one embodiment of the present disclosure, the medical team management module 13 is configured to provide medical team management functions. The medical team management module 13 is configured to receive a medical team assignment command via the control interface to select a plurality of medical team members, thereby forming a medical team and assigning the medical team to proceed to the disaster site for medical rescue. In at least one embodiment of the present disclosure, the medical team management module 13 is configured to display a medical team assignment menu on the control interface, allowing the operator of the management terminal 20 to input a command through the medical team assignment menu of the control interface. The medical team management module 13 can then automatically select a plurality of medical team members to form a medical team, or the operator of the management terminal 20 can manually select a plurality of medical team members from the personnel database built into the cloud control platform 10 to form the medical team.

In some embodiments of the present disclosure, the plurality of medical team members can be divided into at least one administrative group member and a plurality of non-administrative group members. In some embodiments of the present disclosure, each of the non-administrative group members can further be categorized into a planning group member, an execution group member, or a logistics group member according to the assigned tasks, allowing the plurality of medical team members to perform different tasks and support each other at the disaster site. In some embodiments of the present disclosure, the medical team management module 13 only allows to receive a medical team assignment command via the control interface after the advance team is formed. In other words, the medical team management module 13 provides the medical team assignment function via the control interface only after the advance team is formed, so as to avoid prematurely sending a medical team to the disaster site before the advance team clarifies the situation at the disaster site.

In some embodiments of the present disclosure, after the medical team management module 13 receives the medical team assignment command via the control interface, the advance team management module 12 can disband the originally formed advance team, allowing the medical team management module 13 or the operator of the management terminal 20 to select any of the advance team members of the original advance team to become a medical team member. In some embodiments of the present disclosure, after the medical team management module 13 receives the medical team assignment command via the control interface, the advance team management module 12 can disband the originally formed advance team, and the medical team management module 13 then converts at least one advance team member into a medical team member, omitting the check-in procedure for the converted medical team member. In some embodiments of the present disclosure, the control interface can prevent any member who has been selected as a medical team member for one disaster site from being selected again as a medical team member for another disaster site. In some embodiments of the present disclosure, after a medical team is successfully formed and assigned to a disaster site, the disaster site-related information displayed on the control interface is also updated to indicate the status that the medical team has been assigned.

In at least one embodiment of the present disclosure, the medical team management module 13 is configured to receive second return information transmitted by any of the medical team members via a mobile terminal 30 in real time and reflect it on the control interface. In some embodiments of the present disclosure, the second return information includes at least one of the second check-in information of the medical team member, the second triage information, the second medical treatment information, and the second evacuation information. In some embodiments of the present disclosure, the primary task of the medical team is to conduct triage, medical treatment, and evacuation of the injured individuals at the disaster site, and to transmit related information to the cloud control platform 10 to facilitate subsequent patient treatment and statistical analysis. Therefore, the disaster medical assistance system 1 of the present disclosure requires receiving the second check-in information from the medical team member to confirm the arrival of the medical team at the disaster site and to count the number of personnel. Additionally, the received triage information, medical treatment information, and evacuation information help the operator of the management terminal 20 determine subsequent medical treatment and resource allocation. Furthermore, in some embodiments of the present disclosure, the medical team can assist in performing the disaster site assessment, which is as part of the second return information.

Please also refer to FIGs. 2 and 5, where FIG. 5 illustrates a schematic diagram of the disaster medical assistance system 1 of the present disclosure showing the check-in identification code and the schematic diagram before and after check-in. As shown in FIGs. 2 and 5, in some embodiments of the present disclosure, the medical team management module 13 includes a medical team check-in unit 131. In some embodiments of the present disclosure, after the medical team is formed, the medical team check-in unit 131 is configured to only display the medical team check-in menu on the corresponding user interface of the mobile terminal 30 operated by each of the administrative group members of the medical team. After the medical team check-in unit 131 receives the second check-in information transmitted by any of the administrative group members through the medical team check-in menu, the medical team check-in unit 131 is then configured to display the check-in identification code (e.g., a one-dimensional barcode or a two-dimensional code) on the corresponding user interface of the mobile terminal operated by each of the administrative group members, and also display the check-in scanning menu on the corresponding user interface operated by each of the non-administrative group members. In some embodiments of the present disclosure, when the medical team check-in unit 131 receives the second check-in information transmitted by any of the non-administrative members, the medical team check-in unit 131 can simultaneously hide the check-in scanning menu and display at least one of the disaster site assessment form, the triage form, the medical treatment form, and the evacuation form. Accordingly, only after any of the administrative group members of the medical team has transmitted the second checkin information to the medical team management module 13, the disaster medical assistance system 1 of the present disclosure will gradually allow other non- administrative group members of the medical team to scan and check in through any of the administrative group members, enabling the administrative group member of the medical team to keep track of the actual number of arrivals and to allocate manpower and resources.

As previously described, in some embodiments of the present disclosure, when the medical team management module 13 directly converts at least one advance team member at the same disaster site into a medical team member, the medical team checkin unit 131 can omit the check-in scanning process for the converted medical team member, as the advance team member has already been present and performing tasks at the disaster site. Accordingly, the medical team check-in unit 131 may directly display at least one of the disaster site assessment form, the triage form, the medical treatment form, and the evacuation form, allowing the converted medical team member to continue performing patient treatment operations.

Please also refer to FIGs. 2 and 6, where FIG. 6 is a schematic diagram showing the data analysis results displayed on the control interface of the disaster medical assistance system 1 of the present disclosure. As shown in FIGs. 2 and 6, in at least one embodiment of the present disclosure, the cloud control platform 10 further comprises a data collection module 14, which is electrically connected to the disaster event management module 11, the advance team management module 12, and the medical team management module 13.

In at least one embodiment of the present disclosure, the data collection module 14 is configured to compile and analyze the first return information (e.g., all disaster site assessment information) received by the advance team management module 12 and/or the second return information (e.g., all patient treatment-related information) received by the medical team management module 13, and then generate visual chartbased data analysis results and display them on the control interface. In some embodiments of the present disclosure, the operator of the management terminal 20 can use the control interface to query and confirm information related to the current disaster event, such as the analytical statistic results regarding the status at the disaster site, the number of patients, the patient status, and the medical treatment, enabling the operator of the management terminal 20 to grasp the ongoing response of the disaster event and assist in subsequent decision-making. These analytical results are presented in visual chart-based formats for intuitive comprehension of the current data analysis for the operator of the management terminal 20.

Please also refer to FIG. 7, which is a flowchart illustrating the general operation process of the disaster medical assistance system 1 of the present disclosure. To efficiently and properly respond to disaster events, the present disclosure integrates the concepts of an advance team and a medical team into the cloud control platform 10. In at least one embodiment of the present disclosure, once a disaster event has been established and a disaster site has been added, the operator of the management terminal 20 may first assign an advance team to check in at the disaster site via the cloud control platform 10 and then assess the current environment and report back. Based on the assessment report, the operator of the management terminal 20 can determine whether to assign a medical team to check in at the disaster site and perform patient treatment. The disaster event ends once all necessary medical operations at the disaster site are completed. In some embodiments of the present disclosure, the management functions at the disaster site shown in the disaster site column of the control interface may vary depending on the current handling status. For example, when no advance team has been assigned, the “Activate Medical Team” function will be hidden. Once an advance team has been assigned, the “Activate Medical Team” function will appear, while the “Assign Advance Team” function will be hidden.

In some embodiments of the present disclosure, each of the mobile terminals 30 is operated by any of the advance team members and the medical team members. Each of the mobile terminals 30 connects to and accesses the cloud control platform 10 via a network to generate a user interface displayed on the mobile terminal 30. In at least one embodiment of the present disclosure, each of the mobile terminals 30 includes a disaster site assessment module 31, a triage module 32, a medical treatment module 33, and an evacuation management module 34, and all these modules are electrically connected to each other.

Please also refer to FIGs. 2 and 8, where FIG. 8 is a schematic diagram showing the disaster site assessment form displayed on the user interface of the disaster medical assistance system 1 of the present disclosure. As shown in FIGs. 2 and 8, the disaster site assessment module 31 is configured to provide disaster site assessment functions and generate a disaster assessment form on the user interface. The disaster assessment form receives current environmental assessment content for a disaster site and generates corresponding disaster assessment information. In at least one embodiment of the present disclosure, the operator of each of the mobile terminals 30 may select the “Fill Out Disaster Assessment Form” function on the user interface. After activation, the user interface will provide and display the disaster assessment form containing various assessment items, allowing the operator of the mobile terminal 30 to select the corresponding assessment items and complete the relevant content of the items based on the current conditions of the disaster site. Upon completion, the disaster assessment form is transmitted and uploaded to the cloud control platform 10.

In some embodiments of the present disclosure, the assessment items may generally include search and rescue needs, medical needs, infrastructure, traffic conditions, basic necessities, safety, others, and assessment status. Each of the assessment items may further include a plurality of sub-items for the operator of the mobile terminal 30 to select. In some embodiments of the present disclosure, when any of the assessment items is completed by the operator of the mobile terminal 30, the user interface will mark the assessment item (e.g., with a color or symbol) to indicate to the operator of the mobile terminal 30 or subsequent personnel that the assessment item has been completed. Moreover, after each disaster assessment form is completed and uploaded to the cloud control platform 10, the disaster assessment-related information will be displayed in real time on the control interface of the management terminal 20.

Please also refer to FIGs. 2 and 9, where FIG. 9 is a schematic diagram showing the triage form on the user interface of the disaster medical assistance system 1 of the present disclosure. As shown in FIGs. 2 and 9, the triage module 32 is configured to provide triage functions for patients, allowing the user interface to scan the identification code (e.g., a one-dimensional barcode or a two-dimensional code) of the patient to generate a triage form for the patient. Then, the triage form receives current triage content of any of the patients to generate the triage information. In some embodiments of the present disclosure, the operator of each of the mobile terminals 30 may select the “Triage” function from the user interface. In some embodiments of the present disclosure, upon activation, the operator of each of the mobile terminals 30 can scan the identification code (e.g., a two-dimensional code (QR code)) on the patient’s wristband by the user interface. Then, the user interface will show a plurality of triage level options for selection, and the operator of the mobile terminal 30 will select a corresponding triage level based on the patient’s current condition. Once selected, the patient’s triage result will be transmitted and uploaded to the cloud control platform 10.

In some embodiments of the present disclosure, the triage levels may generally include minor, moderate, severe, and awaiting treatment. Each assessment item may further include a plurality of assessment sub-items for the operator of the mobile terminal 30 to select. In some embodiments of the present disclosure, upon the operator of the mobile terminal 30 completes any of the assessment items, the user interface will mark the assessment item (e.g., with a color or symbol) to indicate to the operator of the mobile terminal 30 or subsequent personnel that the assessment item has been completed. In some embodiments of the present disclosure, after completing the triage of the patient, the operator of the mobile terminal 30 may select the “Rescan” option on the user interface to scan the identification code (e.g., a two-dimensional code (QR code)) of the next patient’ s wristband to perform a new triage operation.

Please also refer to FIGs. 2 and 10, where FIG. 10 is a schematic diagram of the medical treatment form displayed on the user interface of the disaster medical assistance system 1 of the present disclosure. As shown in FIGs. 2 and 10, the medical treatment module 33 is configured to provide medical treatment functions for patients. The patient’s identification code is scanned via the user interface to generate a medical treatment form, which then receives the current medical treatment content of the patient and generates medical treatment information. In some embodiments of the present disclosure, the operator of the mobile terminal 30 may select the “Medical Treatment” function from the user interface. In some embodiments of the present disclosure, upon activation, the user interface will provide and display a menu with various medical treatment items for the operator of the mobile terminal 30 to select a corresponding medical treatment item based on the patient’s condition and fill out the related item content. After completion, the medical treatment form is transmitted to the cloud control platform 10.

In some embodiments of the present disclosure, the medical treatment items may generally be divided into: (1) personal information (e.g., demographic form); (2) subjective/objective information (e.g., chief complaint); and (3) treatment. The personal information may optionally include patient’s name, ID number, birth date, gender, current address, breastfeeding status, medication history, past medical history, and drug allergies. The subjective and objective information may feature a graphical human body interface on the user interface for optionally selecting patient’s vital signs (e.g., body temperature, blood pressure, respiration, heart rate, etc.), trauma locations and types, or non-trauma-related information and types, and other subjective and objective data, with support for single or multiple choices. The treatment section may include options for currently implemented treatment measures for the patient, such as wound dressing, cold compress, medication administration, etc., with support for single or multiple choices.

In some embodiments of the present disclosure, the medical treatment module 33 is configured to summarize the patient’s subjective and objective information as a concise overview on the user interface. That is to say, once the operator of the mobile terminal 30 completes the subjective and objective items for the patient, a summary of the entered or selected information will appear on the user interface for quick reference of the summarized content, facilitating the operator of the mobile terminal 30 or subsequent personnel to intuitively confirm the patient’s conditions. In some embodiments of the present disclosure, when the operator of the mobile terminal 30 completes the entry of any medical treatment items, the user interface will mark the completed medical treatment item (e.g., with a color or symbol) to indicate to the operator of the mobile terminal 30 or subsequent personnel that the medical treatment item has been completed.

In some embodiments of the present disclosure, before a medical treatment form for a patient generated from a medical treatment module 33 of any mobile terminal 30 is closed, the cloud control platform 10 is configured to restrict another medical treatment module 33 of another mobile terminal 30 from generating another medical treatment form for the same patient. In other words, when an operator of any mobile terminal 30 is in the process of filling out a medical treatment form for a patient via the user interface (i.e., the medical treatment form has been opened), operators of other mobile terminals 30 will be unable to simultaneously fill out a medical treatment form for the same patient via their respective user interfaces, unless the mobile terminal 30 that initially began the medical treatment input process for the patient has completed the entry (i.e. , the medical treatment form has been closed). Accordingly, this prevents data conflicts or confusion that may arise from multiple operators on different mobile terminals 30 simultaneously inputting medical treatment information for the same patient.

In some embodiments of the present disclosure, either before or after completing the medical treatment entries for a given patient, the operator of the mobile terminal 30 may enter the patient’s condition status by selecting a “Patient Status” item within the form function corresponding to different medical treatment items. The medical treatment form for the patient is only considered complete after the patient status entry is filled out, and only then can the medical treatment form be transmitted to the cloud control platform 10. In some embodiments of the present disclosure, the patient status item may optionally include the current condition of the patient, such as self-departed, recommendation for further treatment, transferred to hospital, deceased, etc. In some embodiments of the present disclosure, if the patient is not in a deceased state, the mobile terminal 30 is configured such that the operator must at least complete the subjective and objective information (e.g., chief complaint) in the medical treatment form for the patient before proceeding to fill out the patient status. However, if the patient is deceased, the operator of the mobile terminal 30 may skip the subjective and objective information (e.g., chief complaint) entries and directly complete the “Patient Status” section.

Please also refer to FIGs. 2 and 11 , where FIG. 11 is a schematic diagram showing the evacuation form on the user interface of the disaster medical assistance system 1 of the present disclosure. As shown in FIGs. 2 and 11 , the evacuation management module 34 is configured to provide evacuation management function for patients. A user interface is used to scan the patient’s identification code (e.g., a two-dimensional code), thereby generating an evacuation form via the user interface and receiving the current evacuation content of the patient via the evacuation form to generate the evacuation information. In some embodiments of the present disclosure, the operator of the mobile terminal 30 may select the “Evacuation” function on the user interface. In some embodiments of the present disclosure, upon activation, the user interface will present one or more candidate hospital options, allowing the operator of the mobile terminal 30 to select an appropriate hospital based on the patient’s current condition or the proximity of the hospital, thereby facilitating subsequent medical treatment for the patient. In some embodiments of the present disclosure, once a candidate hospital is selected by the operator of the mobile terminal 30, the user interface will mark the selected hospital (e.g., by a color or symbol) to indicate to the operator of the mobile terminal 30 that the hospital selection has been completed.

Furthermore, in at least one embodiment, the disaster medical assistance system 1 of the present disclosure may be further integrated with a hospital terminal 40. For example, the cloud control platform 10 may allow the hospital terminal 40 to access via a network connection to generate a patient management interface. In at least one embodiment of the present disclosure, the hospital terminal 40 may be an electronic device such as a computer, a tablet, or a mobile phone, enabling the operator of the hospital terminal 40 (e.g., a doctor, a nurse, or other medical personnel) to use the patient management interface to understand the current status of the patient and subsequently perform appropriate treatment or medical procedures for the patient. In some embodiments of the present disclosure, each of the hospital terminals 40 includes a patient receiving module 41. In some embodiments of the present disclosure, the patient receiving module 41 is configured to scan the identification code (e.g., a two- dimensional code) on the patient’s wristband by using the patient management interface, and receive the patient upon confirming that the patient’s identification code corresponds to either the first evacuation information or the second evacuation information. Accordingly, the disaster medical assistance system of the present disclosure, through coordination between the cloud control platform, the management terminal, and the mobile terminal, can digitize and consolidate all relevant information concerning the occurrence of the disaster and the treatment of patients. This significantly reduces the time required for data processing and transmission and enables the management terminal to clearly understand the situation of the disaster and the realtime progress of rescue operations, thereby facilitating decision-making and the appropriate allocation of manpower and resources.

The above embodiments are provided for illustrative purposes only and are not intended to limit the subject matter of this disclosure or the applications or uses of the embodiments. Furthermore, although at least one exemplary embodiment has been presented in the foregoing description, it should be understood that numerous variations may still be possible within the scope of this disclosure. It should also be understood that the embodiments described herein are not intended to limit the scope, applications, or forms of the claimed subject matter in any way. Rather, the foregoing embodiments are intended to provide those skilled in the art with a convenient guide for implementing one or more embodiments described herein. Moreover, various modifications in function and arrangement of the components may be made without departing from the scope defined by the claims, which encompass known equivalents and foreseeable equivalents available at the time of filing this patent application.

Claims

CLAIMS What is claimed is:

1. A disaster medical assistance system, comprising: a cloud control platform configured to be accessed by a management terminal via a network connection to generate a control interface, the cloud control platform comprising: a disaster event management module configured to receive, via the control interface, an event establishment command to establish a disaster event and add a disaster site; an advance team management module configured to receive, via the control interface, an advance team assignment command to select a plurality of advance team members to form an advance team and notify the advance team to proceed to the disaster site, the advance team management module further configured to receive first return information transmitted in real time by any of the advance team members via a user interface, wherein the first return information includes at least one of first check-in information, first disaster site assessment information, first triage information, first medical treatment information, and first evacuation information; and a medical team management module configured to receive, via the control interface, a medical team assignment command to select a plurality of medical team members to form a medical team and notify the medical team to proceed to the disaster site, the medical team management module further configured to receive second return information transmitted in real time by any of the medical team members via the user interface, wherein the second return information includes at least one of second check-in information, second disaster site assessment information, second triage information, second medical treatment information, and second evacuation information; and a plurality of mobile terminals each operated by one of the advance team members or the medical team members and configured to connect to the cloud control platform via the network to generate the user interface, each of the mobile terminals comprising: a disaster site assessment module configured to generate a disaster site assessment form via the user interface and receive environment assessment content of the disaster site through the disaster site assessment form to generate at least one of the first disaster site assessment information and the second disaster site assessment information; a triage module configured to scan an identification code of a patient via the user interface to generate a triage form of the patient and receive triage content of the patient through the triage form to generate at least one of the first triage information and the second triage information; a medical treatment module configured to scan the identification code of the patient via the user interface to generate a medical treatment form and receive medical treatment content of the patient through the medical treatment form to generate at least one of the first medical treatment information and the second medical treatment information; and an evacuation management module configured to scan the identification code of the patient via the user interface to generate an evacuation form and receive evacuation content of the patient through the evacuation form to generate at least one of the first evacuation information and the second evacuation information.

2. The disaster medical assistance system of claim 1, wherein the advance team management module is configured to receive the advance team assignment command after the disaster site is established, and the medical team management module is configured to receive the medical team assignment command via the control interface after the advance team is formed.

3. The disaster medical assistance system of claim 1, wherein the cloud control platform further comprises a data collection module configured to collect and analyze at least one of the first return information and the second return information and generate a visual chart-based data analysis result.

4. The disaster medical assistance system of claim 1, wherein the cloud control platform further comprises a personnel database storing a plurality of personnel records, and the advance team management module is configured to select the advance team members from the personnel database to form the advance team.

5. The disaster medical assistance system of claim 4, wherein: prior to the formation of the medical team, the advance team management module is configured to disband the advance team, and the medical team management module is configured to select the medical team members from the personnel database to form the medical team; or prior to the formation of the medical team, the advance team management module is configured to disband the advance team, and the medical team management module is configured to directly convert at least one of the advance team members into a medical team member and omit a check-in procedure for the converted medical team member.

6. The disaster medical assistance system of claim 1, wherein the advance team management module comprises an advance team check-in unit configured to display an advance team check-in menu on a corresponding user interface of the mobile terminal operated by each of the advance team members after the advance team is formed, and wherein the advance team check-in unit is configured to hide the advance team check- in menu displayed on the corresponding user interface of the mobile terminal operated by each of the advance team members and display at least one of the disaster site assessment form, the triage form, the medical treatment form, and the evacuation form after the advance team check-in unit receives the first check-in information generated from the advance team check-in menu transmitted by any of the advance team members.

7. The disaster medical assistance system of claim 6, wherein the medical team management module comprises a medical team check-in unit, and the medical team members are divided into at least one administrative group member and a plurality of non-administrative group members, and wherein the medical team check-in unit is configured to: display a medical team check-in menu on a corresponding user interface of the mobile terminal operated by each of the administrative group members after the medical team is formed; display a check-in identification code on the corresponding user interface of the mobile terminal operated by each of the administrative group members after the medical team check-in menu receives the second check-in information transmitted by any of the administrative group members; display a check-in scanning menu on a corresponding user interface of the mobile terminal operated by each of the non-administrative group members; and hide the check-in scanning menu and display at least one of the disaster site assessment form, the triage form, the medical treatment form, and the evacuation form after the medical team check-in unit receives the second check-in information transmitted by any of the non-administrative group members via scanning the check-in identification code on the corresponding user interface.

8. The disaster medical assistance system of claim 1, wherein the cloud control platform further comprises a medical institution database, and the evacuation management module is configured to select a destination medical institution for the patient based on the medical institution database.

9. The disaster medical assistance system of claim 1, further comprising a plurality of hospital terminals each connected to the cloud control platform via the network to generate a patient management interface, wherein each of the hospital terminals comprises a patient receiving module configured to scan the identification code of the patient by using the patient management interface and confirm the identification code of the patient in accordance with at least one of the first evacuation information and the second evacuation information to receive the patient.

10. The disaster medical assistance system of claim 1, wherein the medical team management module is configured to present a specific function menu of a task group on the corresponding user interface according to the task group assigned to each of the medical team members.

11. The disaster medical assistance system of claim 1, wherein the cloud control platform is configured to prevent the medical treatment module on another mobile terminal from generating another medical treatment form for a same patient before the medical treatment form generated from the medical treatment module of the mobile terminal for the same patient is closed.

12. The disaster medical assistance system of claim 1, wherein at least one of the first medical treatment information and the second medical treatment information includes subjective and objective diagnostic content for the patient, and the medical treatment module is configured to display a summarized version of the subjective and objective diagnostic content on the user interface.