Emergency medical information management method and system

Abstract

The present invention relates to an emergency medical information management method and system, including: when a device reports the first emergency information, the system calls a corresponding function according to the reporting method and creates an identification and storage process. The identification process parses the medical information in the emergency information to determine whether it is a new emergency event. If it is a new event, the original virtual machine and shared storage space are created through the storage process, and the emergency medical information is stored. Based on the emergency information and the reporting method, the system generates emergency event response suggestions and returns them to the device. At the same time, based on the emergency type, the target template is called from the medical record template library, the emergency medical information is written to generate an emergency medical record, and it is sent to the medical terminal. This process realizes the rapid identification, storage and provision of response suggestions for emergency information, as well as the automatic generation and sending of emergency medical records.

Description

Technical Field

[0001] The present disclosure relates to the field of emergency medicine technology, and in particular to an emergency medicine information management method and system. Background Art

[0002] In existing medical emergency systems, the device side (such as wearable medical devices, mobile medical terminals, etc.) is usually used to monitor the patient's physiological parameters in real time and report emergency information when abnormal conditions are detected. However, the traditional emergency information processing process has many shortcomings. For example, when the device side reports emergency information, it is often unable to flexibly call the corresponding processing function according to the reporting method, resulting in low processing efficiency. In addition, the lack of an effective emergency information identification and storage mechanism makes it difficult to quickly and accurately determine the uniqueness of emergency events and achieve effective management and storage of emergency information. Summary of the invention

[0003] The purpose of the present invention is to provide an emergency medical information management method and system, which aims to solve the problem that the corresponding processing function cannot be flexibly called according to the reporting method in the relevant scenario, resulting in low processing efficiency. In addition, the lack of an effective emergency information identification and storage mechanism makes it difficult to quickly and accurately determine the uniqueness of emergency events and achieve effective management and storage of emergency information.

[0004] In order to achieve the above-mentioned purpose, a first aspect of an embodiment of the present disclosure provides an emergency medical information management method, which is applied to a medical cloud edge server, and the method includes:

[0005] In response to receiving the first emergency information reported by the device, according to the reporting method of the first emergency information reported by the device, calling a first function corresponding to the reporting method, creating an identification process corresponding to the first emergency information, and calling a second function to create a storage process corresponding to the first emergency information;

[0006] Calling the identification process corresponding to the first emergency information, identifying the medical information carried by the first emergency information, obtaining the emergency medical information of the first emergency event corresponding to the first emergency information, and determining whether there is a second emergency event in the shared memory that is the same emergency event as the first emergency event based on the emergency medical information corresponding to the first emergency information;

[0007] In the case that the second emergency event that is the same as the first emergency event does not exist in the shared memory, calling the storage process corresponding to the first emergency information to create an original virtual machine, and creating a shared storage space in the shared memory through the original virtual machine;

[0008] Calling the storage process corresponding to the first emergency information, storing the emergency medical information corresponding to the first emergency information in the created shared storage space, and generating and returning emergency event response suggestions for the emergency event to the device end according to the emergency medical information of the first emergency event and the reporting method, so as to provide the emergency event response suggestions on the device end;

[0009] According to the emergency type of the first emergency event, the target medical record template is called from the preset medical record template library of the medical cloud edge server, and the emergency medical information is written into the target medical record template to generate an emergency medical record, and the emergency medical record is sent to the medical terminal.

[0010] A second aspect of the present disclosure provides an emergency medical information management method, which is applied to a device, and the method includes:

[0011] In response to the first emergency information corresponding to the received emergency event, the first emergency information is reported to the medical cloud edge server, so that the medical cloud edge server calls the first function corresponding to the reporting method according to the reporting method of the first emergency information reported by the device end, creates an identification process corresponding to the first emergency information, and calls the second function to create a storage process corresponding to the first emergency information, and calls the identification process corresponding to the first emergency information to identify the medical information carried by the first emergency information to obtain the emergency medical information of the first emergency event corresponding to the first emergency information, and determines whether there is a second emergency event that is the same emergency event as the first emergency event in the shared memory according to the emergency medical information corresponding to the first emergency information, and if there is no second emergency event that is the same emergency event as the first emergency event in the shared memory, calls the storage process corresponding to the first emergency information to create an original virtual machine, and creates a shared storage space in the shared memory through the original virtual machine, and calls the storage process corresponding to the first emergency information to store the emergency medical information corresponding to the first emergency information in the created shared storage space;

[0012] Receive emergency event response suggestions from the medical cloud edge server for the emergency event corresponding to the first emergency information, and provide the emergency event response suggestions on the device side, wherein the emergency event response suggestions are generated and returned based on the emergency medical information of the first emergency event and the reporting method of the device side sending the first emergency information to the medical cloud edge server.

[0013] The third aspect of the embodiments of the present disclosure provides an emergency medical information management system, comprising: the medical cloud edge server and medical terminal described in any one of the first aspects, and any number of device terminals described in any one of the second aspects, wherein the device terminals are communicatively connected to the medical cloud edge server via any wireless communication method.

[0014] The present invention provides an emergency medical information management method and system. Compared with the prior art, it has the following beneficial effects:

[0015] By intelligently identifying the reporting method of emergency information reported by the device, and calling the corresponding function to create the identification and storage process, the rapid classification and processing of emergency information is realized. In the identification process, the medical information in the emergency information can be accurately parsed, and then it can be determined whether there are the same emergency events in the shared memory, avoiding repeated processing of information, improving processing efficiency and ensuring the uniqueness of emergency events.

[0016] When encountering a new emergency event, the original virtual machine and shared storage space can be quickly created to ensure the safe and efficient storage of emergency information, and to achieve effective management and storage of emergency information. At the same time, based on the medical information of the emergency event, emergency response suggestions can be automatically generated and returned to the device end, providing immediate and professional first aid guidance.

[0017] In addition, according to the type of emergency event, the target medical record template is automatically called from the medical record template library of the medical cloud edge server, and the emergency medical information is written to generate the emergency medical record, which is sent to the medical terminal in a timely manner. This not only improves the automation level of medical record generation, but also ensures the accuracy and completeness of medical record information, providing strong support for subsequent medical treatment.

[0018] To sum up, the intelligent and automated emergency information processing process has effectively improved the response speed and accuracy of medical emergency response, providing strong guarantees for the timely treatment of patients.

[0019] Other features and advantages of the present disclosure will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings are used to provide a further understanding of the present disclosure and constitute a part of the specification. Together with the following specific embodiments, they are used to explain the present disclosure but do not constitute a limitation of the present disclosure. In the accompanying drawings:

[0021] Figure 1 It is a flowchart of an emergency medical information management method on a medical cloud edge server side according to an embodiment of the specification.

[0022] Figure 2It is a flowchart of an emergency medical information management method on a device side according to an embodiment of the specification.

[0023] Figure 3 It is a block diagram of a medical cloud edge server according to an embodiment of the specification. DETAILED DESCRIPTION

[0024] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0025] The specific implementation of the present disclosure is described in detail below in conjunction with the accompanying drawings. It should be understood that the specific implementation described herein is only used to illustrate and explain the present disclosure, and is not used to limit the present disclosure.

[0026] The present invention provides an emergency medical information management method. Figure 1 1 is a flow chart of an emergency medical information management method according to an embodiment. The method can be applied to a medical cloud edge server, and the method includes:

[0027] In step S101, in response to receiving the first emergency information reported by the device, according to the reporting method of the first emergency information reported by the device, a first function corresponding to the reporting method is called to create an identification process corresponding to the first emergency information, and a second function is called to create a storage process corresponding to the first emergency information;

[0028] Among them, the reporting method is the specific communication protocol or data format used by the device to send emergency information to the medical cloud edge server. The first function is a function predefined according to the reporting method, which is used to create an identification process. The second function is a function used to create a storage process. The identification process can be a process specifically used to parse and process emergency information. The storage process can be responsible for storing the processed emergency information in a specified location.

[0029] In the disclosed embodiment, the medical cloud edge server receives the first emergency information reported by the device end by monitoring a specific port or interface. The medical cloud edge server parses the header or metadata of the emergency information and identifies the reporting method used by the device end.

[0030] Then, according to the identified reporting method, the corresponding first function and second function are called to create an identification process, which will be responsible for parsing the medical information in the emergency information, and to create a storage process, which will be responsible for storing the parsed emergency information in the system.

[0031] For example, if the device reports emergency information via HTTP POST request, the system first parses the HTTP request header and identifies that the reporting method is "HTTP POST". Then, the medical cloud edge server calls the predefined "HTTP_POST_recognition function" to create a recognition process, and "HTTP_POST_storage function" to create a storage process. The recognition process begins to parse the emergency information in the POST request body, and the storage process prepares to store the parsed information in the database or shared memory.

[0032] In step S102, the identification process corresponding to the first emergency information is called to identify the medical information carried by the first emergency information to obtain the emergency medical information of the first emergency event corresponding to the first emergency information, and based on the emergency medical information corresponding to the first emergency information, it is determined whether there is a second emergency event in the shared memory that is the same emergency event as the first emergency event;

[0033] Among them, emergency medical information is medical data or description directly related to the emergency event extracted from the emergency information. Shared memory is a memory area in the medical cloud edge server that can be accessed by multiple processes and is used to store temporary data. The second emergency event is another emergency event that is the same or similar to the first emergency event in medical characteristics.

[0034] In the disclosed embodiment, the recognition process parses the emergency information, extracts the emergency medical information therein, such as patient symptoms, vital signs, etc., and then uses the extracted emergency medical information to search in the shared memory whether there is a second emergency event that is the same emergency event as the first emergency event. For example, this can be achieved by comparing specific fields of the emergency medical information (such as symptom description, diagnosis code, etc.).

[0035] Furthermore, if the second emergency event is found, it means that the emergency event has been processed, and the medical cloud edge server can choose to ignore the current first emergency information or merge it. If the second emergency event is not found, it means that this is a new emergency event, and the medical cloud edge server will continue to execute subsequent steps (such as creating storage space, storing information, etc.).

[0036] For example, suppose the recognition process extracts the patient's symptoms as "chest pain, difficulty breathing" and the address is AAA from the emergency information, and searches the shared memory for other emergency events with the same symptoms and the address is also AAA. The medical cloud edge server determines that it is a duplicate event and can choose to merge the current first emergency information.

[0037] If no record of the same symptoms is found, the medical cloud edge server continues to execute subsequent steps, such as creating storage space for the current emergency event and storing relevant information.

[0038] In step S103, when the second emergency event that is the same emergency event as the first emergency event does not exist in the shared memory, the storage process corresponding to the first emergency information is called to create an original virtual machine, and a shared storage space is created in the shared memory through the original virtual machine;

[0039] The original virtual machine is a lightweight, isolated execution environment that is used to create and manage independent storage space in shared memory. The shared storage space is a memory area created inside the original virtual machine to store specific data, which is visible to the virtual machine instance.

[0040] In the disclosed embodiment, when there is no second emergency event identical to the first emergency event in the shared memory, the medical cloud edge server performs this step. First, the storage process is called to create an original virtual machine instance using virtualization technology. This virtual machine instance will serve as an isolated execution environment for protecting and managing the storage of emergency information. Furthermore, within the original virtual machine, a shared storage space is allocated to store the emergency medical information of the first emergency event. This space is visible to the storage process and possible other authorized processes, but remains isolated from the outside world to ensure data security.

[0041] For example, suppose that the medical cloud edge server has determined that the first emergency event currently received is a new, unprocessed event. Then, the storage process is called to create an original virtual machine instance using virtualization technologies such as Docker or KVM. Inside this virtual machine instance, a shared storage space can be allocated to store the emergency medical information extracted from the first emergency information. This shared storage space is visible to the storage process and is also configured to be visible to other authorized processes that may access this information (such as doctor workstations or medical data analysis systems).

[0042] In step S104, the storage process corresponding to the first emergency information is called, the emergency medical information corresponding to the first emergency information is stored in the created shared storage space, and based on the emergency medical information of the first emergency event and the reporting method, an emergency event response suggestion for the emergency event is generated and returned to the device end, so as to provide the emergency event response suggestion on the device end;

[0043] Among them, emergency response recommendations are a series of response measures or suggestions for emergency events generated by the medical cloud edge server based on emergency medical information.

[0044] In the disclosed embodiment, emergency medical information is stored: the storage process stores the emergency medical information of the first emergency event in the shared storage space created previously. The medical cloud edge server generates response suggestions for the current emergency event based on the stored emergency medical information and the preset emergency processing rules or algorithms. The medical cloud edge server returns the generated response suggestions to the device side through the reporting method previously used by the device side (such as HTTP response, Web Socket message, etc.). After receiving the response suggestions, the device side displays them to the user (such as emergency personnel) through its user interface to guide them to take the next step.

[0045] For example, assume that the medical cloud edge server has successfully stored the emergency medical information of the first emergency event in the shared storage space. Based on this information and the preset emergency treatment rules (such as providing different first aid measures based on symptom classification), the medical cloud edge server generates response suggestions for the current emergency event. For example, if the emergency medical information indicates that the patient has symptoms of cardiac arrest, the medical cloud edge server may generate a response suggestion of "immediately perform cardiopulmonary resuscitation" and may provide cardiopulmonary resuscitation operation methods. The medical cloud edge server returns this response suggestion to the device end (such as a mobile medical device) through an HTTP response. After receiving the response suggestion, the device end displays the suggestion through its screen or sound prompts to guide emergency treatment.

[0046] In step S105, according to the emergency type of the first emergency event, the target medical record template is called from the preset medical record template library of the medical cloud edge server, and the emergency medical information is written into the target medical record template to generate an emergency medical record, and the emergency medical record is sent to the medical terminal.

[0047] Among them, the emergency type can be classified according to the nature, symptoms, severity, etc. of the emergency event, and is used to distinguish different types of emergency events. For example, it can be divided into the following emergency types:

[0048] Cardiovascular disease emergencies, such as acute myocardial infarction: manifested by sudden chest pain, dyspnea, palpitations and other symptoms, requiring immediate electrocardiogram and myocardial enzyme testing to confirm the diagnosis and initiate emergency treatment. Acute heart failure: patients may experience dyspnea, orthopnea, coughing up pink foamy sputum and other symptoms, requiring emergency diuresis, vasodilation, cardiotonic treatment and other treatments.

[0049] Emergency treatment for neurological diseases, such as stroke: including cerebral hemorrhage and cerebral infarction, manifested by sudden limb paralysis, slurred speech, impaired consciousness and other symptoms, requiring immediate head CT or MRI examination, and initiation of emergency treatment such as thrombolysis and antiplatelet therapy. Status epilepticus: patients with continuous epileptic seizures for more than 5 minutes, or repeated seizures in a short period of time, require emergency administration of anti-epileptic drugs to control symptoms.

[0050] Respiratory system emergency, for example, acute respiratory failure: patients' respiratory function is severely impaired due to various reasons, and they have severe hypoxemia and hypercapnia, and they need to be treated immediately with oxygen therapy, mechanical ventilation, etc. Acute asthma attack: patients suddenly have severe wheezing, dyspnea and other symptoms, and they need to be urgently given bronchodilators, glucocorticoids and other drugs to control the symptoms.

[0051] Digestive system disease emergencies, such as acute gastrointestinal bleeding: patients suddenly experience symptoms such as vomiting blood and black stools, and need to immediately stop bleeding, rehydrate, and find out the cause of bleeding. Acute pancreatitis: patients experience sudden abdominal pain, nausea, vomiting, and other symptoms, and need to urgently undergo pancreatic imaging examinations and blood amylase tests to confirm the diagnosis and start treatment.

[0052] Trauma emergencies, for example, severe trauma: multiple fractures and organ damage caused by car accidents and falls, etc., require immediate vital sign monitoring, hemostasis, bandaging, fixation, etc., and transfer to the hospital for comprehensive treatment as soon as possible. Burns: Skin or mucous membrane injuries caused by fire, chemicals, etc. require emergency wound cleaning, disinfection, bandaging, etc., and assessment of the degree of burns and whether further treatment is needed.

[0053] Among them, the medical record template library is a database stored in the medical cloud edge server, which contains a variety of medical record templates. These templates are preset according to the disease type, treatment process, etc., and are used to quickly generate medical records. The target medical record template is a medical record template selected from the medical record template library according to the emergency type, and is used to generate emergency medical records for specific emergency events. Emergency medical records can be formal medical documents that record patient information, symptoms, diagnosis, treatment, etc. of emergency events.

[0054] Among them, the medical terminal can be a computer system or equipment used within a medical institution for medical information management, patient diagnosis and treatment, and other functions.

[0055] In the disclosed embodiment, the medical cloud edge server first selects a suitable target medical record template from a preset medical record template library according to the emergency type of the first emergency event, and then writes the emergency medical information of the first emergency event (such as patient basic information, symptom description, examination results, etc.) into the target medical record template to generate a complete emergency medical record. Finally, the generated emergency medical record is sent to a designated medical terminal (such as a hospital's information system, a doctor's mobile device, etc.) through a secure communication protocol (such as HTTPS, FTP, etc.) for medical personnel to view and process.

[0056] For example, suppose the first emergency event is diagnosed as "acute myocardial infarction". The medical cloud edge server selects the "acute myocardial infarction" medical record template from the medical record template library as the target medical record template. Then, the patient's name, age, gender, symptom description (such as chest pain, dyspnea, etc.), electrocardiogram test results and other emergency medical information are written into the target medical record template to generate a complete emergency medical record. Finally, this emergency medical record is sent to the hospital's information system via the HTTPS protocol for doctors to review and conduct follow-up treatment.

[0057] The above technical solution realizes the rapid classification and processing of emergency information by intelligently identifying the reporting method of emergency information reported by the device end, and calling the corresponding function to create the identification and storage process accordingly. In the identification process, the medical information in the emergency information can be accurately parsed, and then it can be determined whether there is the same emergency event in the shared memory, avoiding repeated processing of information, improving processing efficiency and ensuring the uniqueness of the emergency event.

[0058] When encountering a new emergency event, the original virtual machine and shared storage space can be quickly created to ensure the safe and efficient storage of emergency information, and to achieve effective management and storage of emergency information. At the same time, based on the medical information of the emergency event, emergency response suggestions can be automatically generated and returned to the device end, providing immediate and professional first aid guidance.

[0059] In addition, according to the type of emergency event, the target medical record template is automatically called from the medical record template library of the medical cloud edge server, and the emergency medical information is written to generate the emergency medical record, which is sent to the medical terminal in a timely manner. This not only improves the automation level of medical record generation, but also ensures the accuracy and completeness of medical record information, providing strong support for subsequent medical treatment.

[0060] To sum up, the intelligent and automated emergency information processing process has effectively improved the response speed and accuracy of medical emergency response, providing strong guarantees for the timely treatment of patients.

[0061] In one possible implementation, the method further includes:

[0062] In step S106, when the second emergency event that is the same emergency event as the first emergency event exists in the shared memory, the emergency medical information of the second emergency event on the emergency event is obtained;

[0063] In the disclosed embodiment, the medical cloud edge server first checks whether there is a second emergency event in the shared memory that is the same emergency event as the first emergency event. If there is a second emergency event, the emergency medical information of the event will be read from the shared memory. This information may include some of the same information as the first emergency event, or it may contain new and supplementary information. The emergency medical information of the second emergency event can be integrated into the information of the first emergency event as needed to form a more comprehensive and accurate description of the emergency event.

[0064] Among them, the second emergency event can include multiple. For example, suppose the first emergency event is an event in which a patient suddenly falls into a coma, which is reported by a device on an ambulance. However, someone else also reported an emergency event of a patient falling into a coma by phone (as a second emergency event). Later, after the same patient was sent to the hospital, the device in the hospital also reported an emergency event about the patient (as a second emergency event). When checking the shared memory, it was found that the two emergency events were actually the same event. Therefore, the emergency medical information of the second emergency event (such as the examination results, preliminary diagnosis, etc. in the hospital) was read from the shared memory and integrated into the information of the first emergency event. In this way, a more comprehensive and accurate description of the emergency event can be formed, providing more sufficient information support for subsequent medical decisions.

[0065] In step S107, supplementary emergency medical information for the emergency event is determined based on the emergency medical information of the second emergency event and the emergency medical information corresponding to the first emergency information;

[0066] Among them, the supplementary emergency medical information is based on the comparison of the emergency medical information provided by the second emergency event with the first emergency information, and the new or updated patient information, examination results, diagnosis conclusions, etc. are determined to complete the emergency medical record or guide subsequent treatment.

[0067] In the disclosed embodiment, the emergency medical information provided by the second emergency event is first compared with the first emergency information. This includes various aspects such as the patient's basic information, symptom description, test results, preliminary diagnosis, etc. By comparison, the differences between the two are identified, and these differences may include newly added symptoms, more accurate test results, revised diagnostic conclusions, etc. Based on the identified differences, the system determines the supplementary emergency medical information for this emergency event. This information may be a supplement, correction or update to the original information.

[0068] For example, suppose that in the second emergency information, the patient was initially diagnosed with "suspected acute myocardial infarction" and reported basic information such as chest pain and abnormal electrocardiogram. The first emergency event provided more detailed examination results, such as a significant increase in myocardial enzymes and cardiac ultrasound showing the specific location and range of myocardial infarction. After comparing the two sets of information, it was identified that the second emergency event provided a more accurate diagnostic basis and more detailed myocardial infarction. Therefore, supplementary emergency medical information was determined, including the specific values ​​of the myocardial enzymes, the results of cardiac ultrasound, etc.

[0069] For another example, suppose the second emergency event reports a patient who suddenly fainted, which was reported by a phone call, including "nausea and vomiting, and cold sweats", and then a device on an ambulance reported "suspected acute myocardial infarction". Later, after the same patient was sent to the hospital, the equipment in the hospital also reported the patient's emergency events, including "weakened heart function, insufficient pumping, and decreased heart pumping function, resulting in systemic tissue hypoxia". In this way, different information reported by different devices can be integrated.

[0070] In step S108, the storage process corresponding to the first emergency medical information is called to create a clone virtual machine, and the supplementary emergency medical information is stored in the shared storage space through the clone virtual machine;

[0071] Among them, the clone virtual machine is one or more replica virtual machines created based on the original virtual machine (or called the parent virtual machine). It has the same configuration and initial state as the parent virtual machine, but can run in an independent environment to isolate and store specific data or applications.

[0072] In the disclosed embodiment, the medical cloud edge server calls the storage process corresponding to the first emergency information and creates a clone virtual machine based on the previously created original virtual machine. This clone virtual machine will be used to isolate and store supplementary emergency medical information. Inside the clone virtual machine, the supplementary emergency medical information is stored through the storage space shared with the original virtual machine. This information may include newly added examination results, revised diagnosis conclusions, etc. In this way, data synchronization between the original virtual machine and the cloned virtual machine is ensured so that the latest emergency medical information can be accessed when needed. At the same time, the emergency medical record is updated to include the supplementary emergency medical information.

[0073] For example, assuming that the medical cloud edge server has determined supplementary emergency medical information based on the second emergency event, including the specific values ​​of the myocardial enzyme spectrum and the results of the cardiac ultrasound examination, the storage process is called to create a clone virtual machine based on the original virtual machine. This cloned virtual machine has the same configuration and initial state as the original virtual machine, but will be used to store supplementary emergency medical information. In this way, both the original virtual machine and the cloned virtual machine can access the latest emergency medical information, providing comprehensive and accurate patient information support for medical personnel. At the same time, by creating a cloned virtual machine to store supplementary information, data isolation and security are also achieved.

[0074] In step S109, the supplementary emergency medical information and the emergency medical information of the second emergency event on the emergency event are used as the emergency medical information of the first emergency event, and emergency event response suggestions for the emergency event are regenerated and sent to the device end, so that the emergency event response suggestions are displayed on the device end;

[0075] In the disclosed embodiment, supplementary emergency medical information (such as new test results, changes in patient symptoms, etc.) and relevant information of the second emergency event (which may be the emergence of a new symptom or the aggravation of existing symptoms) are first integrated. Then, the system combines this information with the original emergency medical information of the first emergency event to form a more comprehensive and accurate description of the condition. Next, the system reruns the emergency event response suggestion generation algorithm based on the updated description of the condition to generate new emergency event response suggestions. Finally, the system sends the new response suggestions to the device for medical staff to refer to and execute.

[0076] For example: Suppose a patient visits a doctor for chest pain and is initially diagnosed with suspected acute myocardial infarction (the first emergency event). Before step S19, preliminary emergency event response recommendations have been generated, such as performing an electrocardiogram and myocardial enzyme testing. Subsequently, the patient's electrocardiogram results showed abnormalities, and myocardial enzyme levels were significantly elevated (supplementary emergency medical information), and the patient experienced difficulty breathing (the second emergency event). After integrating this new information, the condition is reassessed and new emergency event response recommendations are generated, such as immediate cardiac intervention and enhanced vital sign monitoring. The new recommendations are then sent to the device.

[0077] In step S110, the supplementary emergency medical information is written into the emergency medical record corresponding to the second emergency event, a new emergency medical record for the emergency event is generated, and the new emergency medical record for the emergency event is sent to the medical terminal.

[0078] In the disclosed embodiment, the original emergency medical record is first updated based on the supplementary emergency medical information (such as new diagnosis results, treatment process, etc.) and the relevant information of the second emergency event. The updated content may include a description of the disease progression, a new diagnosis conclusion, the treatment measures taken and their effects, etc. Then, the system generates a new emergency medical record, which comprehensively reflects all important medical information of the patient from the time of consultation to the present moment. Finally, the system sends the new emergency medical record to the medical terminal for medical staff to review, analyze and further diagnose and treat.

[0079] Continuing with the above example, the patient's symptoms were relieved after receiving cardiac interventional treatment, and the subsequent electrocardiogram and myocardial enzyme tests showed normal results (supplemental emergency medical information). Based on this information, the system updated the original emergency medical record, adding content such as the treatment process, treatment effect, and follow-up observation plan. Then, the system generated a new emergency medical record and sent it to the medical terminal. Medical staff can understand the patient's complete diagnosis and treatment process by consulting the new emergency medical record, and provide guidance for subsequent rehabilitation treatment and follow-up.

[0080] In a possible implementation, in step S107, determining the supplementary emergency medical information for the emergency event based on the emergency medical information of the second emergency event and the emergency medical information corresponding to the first emergency information includes:

[0081] In step S1071, based on each emergency medical description in the emergency medical information of the emergency event, a first description vector corresponding to each emergency medical description is constructed;

[0082] Among them, the description vector is a high-dimensional vector that converts text descriptions (such as emergency medicine descriptions) into numerical form, which is used for computer processing and comparison of similarities between texts.

[0083] In the disclosed embodiment, natural language processing (NLP) technology, such as word embedding or sentence embedding, can be used to convert each emergency medical description in the emergency medical information into a vector representation in a high-dimensional space. These vectors can capture the semantic information in the description, so that similar descriptions are close in the vector space.

[0084] For example, suppose there is a description in emergency medical information that says "the patient suddenly had chest pain, accompanied by difficulty breathing." Through NLP technology, this description may be converted into a vector containing hundreds of numerical values, each of which represents the strength or existence of a feature or concept in the description.

[0085] In step S1072, according to each emergency medical description in the emergency medical information of the emergency event, a second description vector corresponding to each emergency medical description is constructed;

[0086] Similarly, for the description of emergency medical information in the second emergency event, natural language processing (NLP) technology, such as word embedding or sentence embedding methods, can be used to convert each emergency medical description in the emergency medical information into a vector representation in a high-dimensional space. The purpose is to convert each emergency medical description in the second emergency event into a vector form so as to compare it with the description vector of the first emergency event.

[0087] For example, if a description in the second emergency event is "the patient's chest pain worsens, cold sweat and confusion occur", similarly, this description will also be converted into a vector, which is consistent with the vector obtained in step S1071 in dimension and structure, but the specific value will vary depending on the description content.

[0088] In step S1073, a first description vector corresponding to each of the emergency medical descriptions corresponding to the first emergency event is matched with a second description vector corresponding to each of the emergency medical descriptions corresponding to the second emergency event to obtain a matching value;

[0089] Among them, the matching value is a numerical indicator that can measure the similarity or matching degree between two description vectors, which is usually obtained by calculating the distance between the vectors (such as cosine distance, Euclidean distance, etc.) or their similarity score (such as cosine similarity).

[0090] In the disclosed embodiment, the matching degree between the first emergency event and the second emergency event is evaluated by calculating the similarity or distance between the corresponding description vectors in the first emergency event and the second emergency event. Commonly used methods include cosine similarity (measuring the similarity of two vector directions), Euclidean distance (measuring the straight-line distance between two vectors in space), etc. The higher the matching value (or the smaller the distance), the more similar the two descriptions are.

[0091] For example: Assume that the two description vectors obtained in steps S1071 and S1072 are A and B. By calculating the cosine similarity between A and B, a value between 0 and 1 (such as 0.85) is obtained, which is the matching value. It shows that the two descriptions "the patient suddenly had chest pain, accompanied by dyspnea" and "the patient's chest pain worsened, cold sweat and confusion" have a high semantic similarity, which may point to similar disease states or require similar emergency measures.

[0092] In step S1074, a blank matrix is ​​constructed according to the number of the first description vectors and the number of the second description vectors;

[0093] Among them, a blank matrix is ​​a matrix initialized to zero or empty values, which is used to fill data later to form a specific data structure, such as a matching matrix.

[0094] In the disclosed embodiment, the construction of the blank matrix is ​​based on the number of first description vectors and second description vectors. Assuming that the first emergency event has M emergency medical descriptions (i.e., M first description vectors) and the second emergency event has N emergency medical descriptions (i.e., N second description vectors), a blank matrix with M rows and N columns is constructed. Each element of this matrix represents a potential matching position, and these positions are initially empty or filled with default values ​​(such as 0).

[0095] For example: if the first emergency event has 3 descriptions and the second emergency event has 4 descriptions, then the constructed blank matrix is ​​a 3x4 matrix.

[0096] In step S1075, the matching values ​​of the first description vector corresponding to each of the emergency medical descriptions corresponding to the first emergency event and the second description vector corresponding to each of the emergency medical descriptions corresponding to the second emergency event are filled into the blank matrix to construct a matching matrix;

[0097] The matching matrix is ​​a matrix filled with matching values ​​between description vectors, which is used to represent the similarity or matching degree between different description vectors.

[0098] In the disclosed embodiment, the calculated matching values ​​of each pair of description vectors (the first description vector and the second description vector) are filled into the constructed blank matrix. In this way, the blank matrix is ​​converted into a matching matrix, in which each element represents the matching value of the two description vectors at the corresponding position.

[0099] Continuing with the above example, if the matching value between the first description vector of the first emergency event and the second description vector of the second emergency event is 0.75, then 0.75 is entered in the first row and second column of the matching matrix. This process is repeated until all matching values ​​are entered into the matching matrix.

[0100] In step S1076, according to the Hungarian algorithm and the matching matrix, the best matching vector of the first description vector corresponding to each of the emergency medical descriptions corresponding to the first emergency event is searched from the second description vector;

[0101] Among them, the Hungarian algorithm is a combinatorial optimization algorithm used to solve the maximum weight matching problem of bipartite graphs, and is also often used to solve problems such as task allocation and resource allocation. The optimal matching vector is another description vector with the highest matching degree (or the largest matching value) found by the Hungarian algorithm in the matching matrix.

[0102] In the embodiment of the present disclosure, the Hungarian algorithm is applied to the constructed matching matrix to find the best match (i.e., the vector with the largest matching value) for each vector in the first description vector set in the second description vector set. The Hungarian algorithm gradually constructs a maximum weight matching (or optimal matching) solution by finding augmenting paths, updating matching, etc.

[0103] For example, in the matching matrix, for the first description vector of the first emergency event, the Hungarian algorithm will find the description vector of the second emergency event with the largest matching value as the optimal matching vector. This process will be repeated until the optimal matching vector is found for all description vectors of the first emergency event.

[0104] In step S1077, according to a preset matching threshold and a matching value between the first description vector corresponding to each of the emergency medical descriptions and the corresponding optimal matching vector, it is determined whether each emergency medical description in the emergency medical information of the first emergency event and the emergency medical description corresponding to the corresponding optimal matching vector in the second emergency event are the same medical description;

[0105] The preset matching threshold is a pre-set value used to determine whether the matching value between two description vectors is high enough to be considered to represent the same medical description. The same medical description means that two or more description vectors are semantically highly similar, so that they can be considered to describe the same medical condition or symptom.

[0106] In the disclosed embodiment, for each first description vector and its corresponding optimal matching vector found, their matching values ​​are compared with a preset matching threshold. If the matching value is greater than or equal to the preset matching threshold, it is considered that the two description vectors represent the same medical description; otherwise, it is considered that they are not the same medical description.

[0107] For example: assuming that the preset matching threshold is 0.8, for a first description vector and its corresponding optimal matching vector, if their matching value is 0.85, they are judged to be the same medical description; if the matching value is 0.75, they are judged to be not the same medical description.

[0108] In step S1078, based on the determination result of whether it is the same medical description, the supplementary emergency medical information for the emergency event is determined.

[0109] According to the determination result of step S1077, for the first description vector and the second description vector that are determined to be the same medical description, if the second description vector contains additional information not in the first description vector (such as a more detailed symptom description, additional diagnostic information or treatment recommendations), the additional information is added to the emergency medical information of the first emergency event as supplementary emergency medical information. For cases where the medical description is not the same, if the description information in the second emergency event has an important supplementary or corrective effect on the emergency treatment, it can also be considered to be included in the supplementary emergency medical information, but more detailed evaluation and judgment are required.

[0110] For example: suppose that a certain emergency medical description of the first emergency event is "the patient has chest pain", and the corresponding best matching vector in the second emergency event describes "the patient has chest pain, accompanied by abnormal electrocardiogram". If it is determined to be the same medical description, the additional information of "accompanied by abnormal electrocardiogram" can be added to the emergency medical information of the first emergency event to provide a more comprehensive description of the patient's condition. If the second emergency event also contains specific suggestions on the treatment of chest pain (such as immediate administration of nitroglycerin), and these suggestions do not conflict with the information in the first emergency event, they can also be considered for inclusion in the supplementary emergency medical information.

[0111] The above technical solution supplements and improves the original emergency medical information based on the information of the second emergency event, so as to provide more accurate and comprehensive emergency medical guidance, and then based on the matching matrix and the Hungarian algorithm, finds the vector that best matches the description vector of the first emergency event from the description vector of the second emergency event, and based on the determination results of the matching threshold and the optimal matching vector, effectively supplements and improves the emergency medical information, so as to provide more accurate and comprehensive guidance for emergency medical care.

[0112] In a possible implementation, in step S109, generating and sending to the device an emergency event response suggestion for the emergency event based on the emergency medical information of the first emergency event includes:

[0113] In step S1091, a root node of a decision tree for the first emergency event is constructed according to the characteristic emergency medical description in the emergency medical information of the first emergency event, wherein the root node includes all characteristic emergency medical descriptions in the emergency medical information of the first emergency event;

[0114] Among them, the characteristic emergency medical description is a medical description in the emergency medical information that has key diagnostic or therapeutic significance for emergency events, such as specific symptoms, signs, examination results, etc. The decision tree root node is the top-level node of the decision tree. As the starting point of the entire decision-making process, it usually contains the most extensive or important characteristic information and is used to guide the subsequent decision path.

[0115] In the disclosed embodiment, when constructing the root node of the decision tree, all characteristic emergency medical descriptions in the emergency medical information of the first emergency event are first extracted. These characteristic descriptions are the basis for constructing the decision tree because they contain key information of the emergency event and can affect the subsequent decision path. Then, these characteristic descriptions are integrated into the root node of the decision tree as the starting point of the entire decision process.

[0116] For example, suppose the first emergency event is "acute myocardial infarction", and its emergency medical information contains multiple characteristic emergency medical descriptions, such as "chest pain", "ST segment elevation on electrocardiogram", "elevated myocardial enzymes", etc. When constructing the root node of the decision tree, these characteristic descriptions will be integrated as the basis for guiding the subsequent decision path.

[0117] In step S1092, according to the characteristic information of each characteristic emergency medical description, an initial weight of each characteristic emergency medical description in the emergency medical information is determined;

[0118] Among them, feature information is the specific information used to describe the characteristics of emergency events in emergency medical information, such as the severity of symptoms, the obviousness of signs, the abnormality of examination results, etc. The initial weight is the initial importance value assigned to each feature emergency medical description during the decision tree construction process, which is used to measure the influence of the feature in the decision process.

[0119] In the disclosed embodiment, when determining the initial weight of the feature emergency medical description, it is necessary to consider the feature information of each feature in the emergency medical information. This feature information may include the severity of symptoms, the obviousness of signs, the abnormality of examination results, etc. Based on this feature information, the importance of each feature in the diagnosis or treatment decision of the emergency event can be evaluated, and the corresponding initial weight can be assigned accordingly. The setting of the initial weight is usually based on expert experience, statistical data, or the results of a machine learning algorithm.

[0120] Continuing with the above example, for the emergency medicine information of "acute myocardial infarction", the feature emergency medicine description "electrocardiogram ST segment elevation" may have a higher initial weight because it has a high specificity in the diagnosis of acute myocardial infarction. While the feature description "chest pain" is also an important symptom, its specificity may be lower, so the initial weight may be relatively low. By assigning different initial weights, the decision tree can be guided to pay more attention to those features with higher importance during the subsequent construction process.

[0121] In step S1093, according to the initial weight of each characteristic emergency medicine description in the emergency medicine information, a preset first number of multiple characteristic emergency medicine descriptions are combined from large to small to obtain a preset second number of branch child nodes;

[0122] Among them, the branch subnode is a node composed of a specific feature set when building a decision tree or similar model. It is first sorted according to the initial weight of the feature emergency medicine description in the emergency medicine information. Feature emergency medicine descriptions with high weights are considered to have a higher influence on the judgment or classification of emergency events. Subsequently, the first N (N is the preset first number) feature emergency medicine descriptions with the highest weights are selected and combined to form the first branch subnode. Repeat this process until a preset second number of branch subnodes are generated, each of which contains a different combination of feature emergency medicine descriptions sorted by weight.

[0123] For example: suppose there are 5 features emergency medicine description A, B, C, D, E, and their initial weights are 0.8, 0.7, 0.6, 0.5, and 0.4 respectively. The first number is preset to 3, and the second number is preset to 2. First, the top 3 features with the highest weights (A, B, C) are selected to form the first branch subnode. Then, the next highest 3 features (A, B, D) or other qualified combinations may be selected to form the second branch subnode.

[0124] In step S1094, the following steps are executed in a loop: randomly removing one of the characteristic emergency medicine descriptions from each of the branch sub-nodes to obtain a branch sub-node of the branch sub-node, until the sum of the initial weights of the characteristic emergency medicine descriptions in the obtained branch sub-nodes is less than a preset threshold, thereby obtaining a minimum branch sub-node;

[0125] Among them, random elimination is the process of randomly selecting an element from the set and removing it. The minimum branch child node is the branch child node whose sum of the initial weights of the remaining feature emergency medicine descriptions is less than a preset threshold after the elimination operation.

[0126] In the disclosed embodiment, a loop elimination operation is performed on each branch subnode. In each loop, a feature emergency medicine description is randomly eliminated from the current branch subnode to form a new branch subnode. This process continues until the sum of the initial weights of all feature emergency medicine descriptions in the newly generated branch subnode is less than a preset threshold, at which point the node is considered to be the minimum branch subnode. This process is intended to simplify the model by reducing the number of features while maintaining sufficient recognition capabilities for emergency events.

[0127] Continuing with the above example, assuming that the preset threshold is 1.5, for a branch subnode containing A, B, and C, if C is randomly removed, the sum of the weights of A and B (0.8+0.7=1.5) is exactly equal to the threshold, but if either A or B is removed, the sum of the weights of the remaining features will be less than 1.5, and the minimum branch subnode is obtained.

[0128] In step S1095, based on the characteristic emergency medical description in each of the minimum branch subnodes, emergency event response suggestions for the emergency event are generated and sent to the device end.

[0129] Among them, emergency response recommendations are specific treatment or recommended measures for emergency events based on the characteristic emergency medicine description in the smallest branch sub-node.

[0130] In the disclosed embodiment, according to the characteristic emergency medical description contained in each minimum branch subnode, combined with the preset response strategy library, corresponding emergency event response suggestions are generated. These suggestions may include emergency treatment measures, further examination suggestions, possible diagnostic directions, etc. Subsequently, the system sends these suggestions to the designated device end through the network so that medical staff can obtain them in time and take corresponding actions.

[0131] For example, if the smallest branch subnode contains the features "chest pain" and "abnormal electrocardiogram", the system may retrieve relevant suggestions from the response strategy library, such as "immediately conduct myocardial infarction screening", "give the patient oxygen support", etc.

[0132] After completing the construction of the decision tree root node and determining the initial weights of the characteristic emergency medicine description, the above technical solution will involve gradually constructing the branches and leaf nodes of the decision tree based on these weights and characteristic information, and finally generating emergency event response recommendations for the first emergency event to ensure that the generated response recommendations are both accurate and practical.

[0133] In a possible implementation, in step S101, according to the reporting method of the first emergency information reported by the device, calling a first function corresponding to the reporting method, and creating an identification process corresponding to the first emergency information includes:

[0134] In step S1011, according to the reporting identifier carried by the first emergency information reported by the device, a reporting method for the device to report the first emergency information is determined;

[0135] Among them, the identification process is a process used to process and analyze emergency information. This process is responsible for receiving emergency information, extracting key data, and executing corresponding processing logic based on this data, such as sending information to doctors in the emergency department, or performing further condition analysis and classification. The reporting method is the way the device reports emergency information, which may include different communication protocols, data formats, or transmission mechanisms. The reporting identifier is a mark or code used to identify the method used by the device to report emergency information.

[0136] In the disclosed embodiment, according to the reporting method of the emergency information reported by the device, the system can select the most appropriate processing method. Different reporting methods may require different processing logic and functions to be implemented. By calling the function corresponding to the reporting method, an identification process can be created, which will specifically process the emergency information.

[0137] For example: Suppose there are two reporting methods: Method A transmits data in XML format through the TCP protocol, and Method B transmits data in JSON format through the HTTP protocol. When receiving an emergency information reported through Method A, it will determine that this is Method A based on the reporting identifier. Then, the function corresponding to Method A is searched in the function mapping table (assuming it is processXML Data). Next, the extracted patient information is passed as a parameter to the process XML Data function. Finally, by calling a copy of the parent process of the process XML Data function (that is, using the fork function), an identification process is created, which will process this emergency information.

[0138] By checking the reporting identifier, it is possible to determine which processing logic and function should be used to process the emergency information. For example, assuming that the reporting identifier is "A001", it means that this is emergency information reported through method A.

[0139] In step S1012, according to a preset function mapping table, a first function corresponding to the reporting method is searched, wherein different reporting methods correspond to a function in the function mapping table one by one;

[0140] The function mapping table is a data structure used to map different reporting methods to corresponding processing functions.

[0141] In the disclosed embodiment, the function mapping table allows the system to quickly find the function corresponding to the reporting method. By traversing or looking up the table, the function matching the reporting identifier can be found. For example, in the function mapping table, the reporting method "A001" corresponds to the process XML Data function.

[0142] In step S1013, the extracted patient information is passed as a parameter to the first function;

[0143] Parameter passing is the process of passing necessary data or information as parameters to a function when the function is called. In the disclosed embodiment, before calling the processing function, the extracted patient information is passed to the function as a parameter. In this way, the function can use this information to process emergency information. For example, assume that the extracted patient information includes name, age, and description of the condition. This information will be passed as a parameter to the process XML Data function.

[0144] In step S1014, an identification process corresponding to the first emergency information is created by calling a copy of the parent process of the first function.

[0145] Among them, the copy of the parent process is in Unix and Unix-like operating systems. The child process created by the fork function is a copy of the parent process. The child process inherits many properties of the parent process, but is independent in the memory address space.

[0146] In the disclosed embodiment, in Unix and Unix-like operating systems, the fork function is used to create a new process (child process). This child process is a copy of the parent process that calls the fork function. By calling the copy of the parent process of the function corresponding to the reporting method, the system can create an identification process specifically for processing emergency information.

[0147] For example, when the process XML Data function is called, its parent process (which may be the main process or another processing process) will create a copy (the child process). This child process will serve as the identification process to process emergency information.

[0148] In one possible implementation, the reporting method includes any one of a text message reporting method, a voice reporting method, a mini-program reporting method, an application reporting method, and a telephone reporting method.

[0149] Among them, the SMS reporting method refers to sending the relevant information of the emergency event to the designated recipient in text form through the SMS (Short Message Service). This method is usually suitable for fast and brief information transmission and can be sent without a network connection. For example: If a patient is found to be suspected of cardiac arrest, a brief description of the patient (such as age, gender, and main symptoms) can be sent via mobile phone text message.

[0150] Among them, voice reporting refers to the verbal transmission of relevant information about the emergency incident to the recipient through voice calls or voice messaging services (such as VoIP, Voice over Internet Protocol or voice memos). This method is suitable for emergency situations where medical staff need to describe the patient's condition quickly and in detail. For example: At the scene of a traffic accident, an emergency worker finds multiple injured people. He can call the hospital's emergency number through his mobile phone and use voice to describe the injury and location of each injured person in detail.

[0151] Among them, the mini program reporting method refers to filling in and submitting relevant information about emergency events through mini program applications installed on smartphones (usually based on platforms such as WeChat and Alipay). This method combines the portability of mobile devices and the interactivity of applications, making it easy to enter and submit information quickly and accurately. For example: A hospital has developed an emergency reporting mini program, which can be entered by scanning the mini program code or searching for the mini program name. In the application, you can select the corresponding emergency type, fill in patient information, describe symptoms, and upload on-site photos or videos as auxiliary information. Finally, click the Submit button to send the information.

[0152] Among them, the application reporting method refers to reporting relevant information of emergency events through a dedicated application (APP) installed on a smartphone or tablet. This method usually provides richer functions and more personalized interface design to meet the specific needs of different hospitals or medical institutions. For example: A large medical institution has developed an emergency medical information system APP, which can be used to quickly report emergency events. The APP provides a variety of reporting templates, and you can select the corresponding template and fill in the relevant information according to the actual situation. In addition, the APP also supports functions such as real-time location sharing and voice input, which is convenient for a more comprehensive description of the emergency scene.

[0153] Among them, the telephone reporting method refers to the oral communication of the relevant information of the emergency incident to the recipient through telephone communication (including landline and mobile phone). This method is one of the traditional ways of information transmission, which is instant and direct. For example: in remote areas or when there is no network coverage, you can report an emergency incident by calling the hospital's emergency number. You can use verbal language to describe the patient's condition and location information in detail.

[0154] The present disclosure also provides an emergency medical information management method, which is applied to a device. Figure 2 As shown, the method includes:

[0155] In step S201, in response to the first emergency information corresponding to the received emergency event, the first emergency information is reported to the medical cloud edge server, so that the medical cloud edge server calls the first function corresponding to the reporting method according to the reporting method of the first emergency information reported by the device end, creates an identification process corresponding to the first emergency information, and calls the second function to create a storage process corresponding to the first emergency information, and calls the identification process corresponding to the first emergency information to identify the medical information carried by the first emergency information to obtain the emergency medical information of the first emergency event corresponding to the first emergency information, and determines whether there is a second emergency event that is the same emergency event as the first emergency event in the shared memory according to the emergency medical information corresponding to the first emergency information, and if there is no second emergency event that is the same emergency event as the first emergency event in the shared memory, calls the storage process corresponding to the first emergency information to create an original virtual machine, and creates a shared storage space in the shared memory through the original virtual machine, and calls the storage process corresponding to the first emergency information to store the emergency medical information corresponding to the first emergency information in the created shared storage space;

[0156] In the disclosed embodiment, when the device end (such as a smart medical device, a mobile medical application, etc.) receives the first emergency information of an emergency event, it will report this information to the medical cloud edge server.

[0157] The reporting process may involve steps such as data encapsulation, encryption, and the selection of transmission protocols to ensure the integrity and security of the data. After receiving this information, the medical cloud edge server will parse and store it, and may trigger further medical analysis and processing processes.

[0158] For example: suppose a smart bracelet detects that the user's heart rate suddenly rises to a dangerous level and automatically determines it as an emergency event. The bracelet will report the first emergency information containing the user's basic information, heart rate data, timestamp, etc. to the medical cloud edge server. After receiving this information, the server will immediately process it and execute the emergency medical information management method executed by the medical cloud edge server in the aforementioned embodiment of the present disclosure.

[0159] In step S202, the medical cloud edge server receives emergency event response suggestions for the emergency event corresponding to the first emergency information, and provides the emergency event response suggestions on the device side, wherein the emergency event response suggestions are generated and returned based on the emergency medical information of the first emergency event and the reporting method of the device side sending the first emergency information to the medical cloud edge server.

[0160] In the disclosed embodiment, after receiving the first emergency information, the medical cloud edge server will perform real-time medical analysis and processing, including condition assessment, first aid measure recommendation, etc. Based on the analysis results, the server will generate emergency event response suggestions and transmit them to the device end through the network. After receiving these suggestions, the device end will parse and display them so that users or medical personnel can quickly understand and take corresponding response measures.

[0161] For example, suppose that after receiving the emergency information reported by the smart bracelet, the medical cloud edge server determines that the user may be experiencing tachycardia after analysis. The server will generate emergency response suggestions, such as "stop the activity immediately, stay calm, and call the emergency number." These suggestions will be transmitted to the smart bracelet through the network, and the bracelet will display these suggestions on the screen, and may also remind the user through vibration or sound.

[0162] Through these two steps, the medical cloud edge server can achieve real-time information interaction and provide medical advice with the device side, thereby helping users or medical personnel better respond to emergency events.

[0163] In a possible implementation, in step S202, providing the emergency event response suggestion on the device side includes:

[0164] In step S2021, the speaker usage information of the device end is obtained, and when the speaker usage information indicates that the speaker of the device end is not occupied, the emergency event response suggestion is played through the speaker of the device end;

[0165] The speaker usage information may be information recorded by the device about the current state of the speaker, including whether it is occupied, volume setting, etc. The speaker is in an unoccupied state: it means that the speaker is not currently used by other applications or services and is in an idle state.

[0166] In the disclosed embodiment, after the device receives the emergency response suggestions sent by the medical cloud edge server, it will first check the speaker usage information. If the speaker is not occupied, the device will use the speaker function to play the emergency response suggestions in voice form. During the playback process, the device may adjust the volume to ensure that the user can clearly hear the suggestions.

[0167] For example, let's say a user is using a smartwatch and the watch receives emergency response advice for tachycardia. The watch first checks if the speaker is idle, and if so, it plays the message "Stop moving immediately, stay calm, and call emergency services." The user doesn't need to look at the screen, they can hear the advice.

[0168] In step S2022, when the speaker on the device end is occupied according to the speaker usage information table, a text response suggestion description is generated based on the emergency event response suggestion, and the text response suggestion description is displayed on the device end.

[0169] The text response suggestion description is to convert the emergency response suggestion into text form so as to be displayed on the device screen. The speaker is in the occupied state, which means that the speaker is currently being used by other applications or services and cannot be used to play voice messages.

[0170] In the disclosed embodiment, if the speaker is in use, the device cannot play voice suggestions, and a text description of the response suggestions will be generated instead. The text description will be based on the content of the emergency response suggestions to ensure the accuracy and completeness of the information. The device will display these text descriptions on the screen, and the user can obtain the response suggestions visually.

[0171] For example, suppose a user's smartphone is playing music on the speaker and receives emergency response advice about a fall. Since the speaker is occupied, the phone will display the message "Stay calm, check yourself for injuries, and call emergency services if necessary." The user can read the text description on the phone screen to understand the response advice.

[0172] Through these two sub-steps, the device can flexibly play voice suggestions when the speaker is idle and display text suggestions when the speaker is occupied, thereby ensuring that users can obtain timely response suggestions for emergency events no matter what the circumstances.

[0173] In one possible implementation, the reporting method includes any one of a text message reporting method, a voice reporting method, a mini-program reporting method, an application reporting method, and a telephone reporting method.

[0174] The disclosed embodiments also provide an emergency medical information management system, comprising: a medical cloud edge server and a medical terminal as described in any one of the aforementioned embodiments, and any number of device terminals as described in any one of the aforementioned embodiments, wherein the device terminals are communicatively connected to the medical cloud edge server via any wireless communication method.

[0175] Figure 3The emergency medical information management method device 100 shown includes: a processor 1001 and a memory 1003. Among them, the processor 1001 and the memory 1003 are connected, such as through a bus 1002. Optionally, the emergency medical information management method device 100 may also include a communication component 1004, and the communication component 1004 can be used for data interaction between the device 100 and other devices, such as data sending and / or data receiving. It should be noted that in actual scheduling, the communication component 1004 is not limited to one, and the structure of the emergency medical information management method device 100 does not constitute a limitation on the embodiments of the present application.

[0176] Processor 1001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 1001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0177] The bus 1002 may include a path to transmit information between the above components. The bus 1002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 1002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0178] The memory 1003 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), magnetic disk storage medium, other magnetic storage devices, or any other medium that can be used to carry or store program code and can be read by a computer, without limitation herein.

[0179] The memory 1003 is used to store program codes for executing the embodiments of the present disclosure, and the execution is controlled by the processor 1001. The processor 1001 is used to execute the program codes stored in the memory 1003 to implement the steps shown in the embodiment of the emergency medical information management method.

[0180] The embodiment of the present disclosure also provides a computer-readable storage medium having program code stored thereon. When the program code is executed by a processor, the steps and corresponding contents of the aforementioned emergency medical information management method embodiment can be implemented.

[0181] The preferred embodiments of the present disclosure are described in detail above in conjunction with the accompanying drawings; however, the present disclosure is not limited to the specific details in the above embodiments; within the technical concept of the present disclosure, various changes, modifications, substitutions and variations may be made to these embodiments, and these changes, modifications, substitutions and variations all fall within the protection scope of the present disclosure.

[0182] It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any appropriate manner without contradiction, and they should also be regarded as the contents disclosed in this disclosure. In order to avoid unnecessary repetition, this disclosure will not further describe various possible combinations. The technical scope of this application is not limited to the contents in the specification, and its technical scope must be determined according to the scope of the claims.

Claims

1. An emergency medical information management method, characterized in that: Applied to a medical cloud edge server, the method includes: In response to receiving the first emergency information reported by the device, according to the reporting method of the first emergency information reported by the device, calling a first function corresponding to the reporting method, creating an identification process corresponding to the first emergency information, and calling a second function to create a storage process corresponding to the first emergency information; Calling the identification process corresponding to the first emergency information, identifying the medical information carried by the first emergency information, obtaining the emergency medical information of the first emergency event corresponding to the first emergency information, and determining whether there is a second emergency event in the shared memory that is the same emergency event as the first emergency event based on the emergency medical information corresponding to the first emergency information; In the case that the second emergency event that is the same as the first emergency event does not exist in the shared memory, calling the storage process corresponding to the first emergency information to create an original virtual machine, and creating a shared storage space in the shared memory through the original virtual machine; Calling the storage process corresponding to the first emergency information, storing the emergency medical information corresponding to the first emergency information in the created shared storage space, and generating and returning emergency event response suggestions for the emergency event to the device end according to the emergency medical information of the first emergency event and the reporting method, so as to provide the emergency event response suggestions on the device end; According to the emergency type of the first emergency event, a target medical record template is called from a preset medical record template library of the medical cloud edge server, and the emergency medical information is written into the target medical record template to generate an emergency medical record, and the emergency medical record is sent to the medical terminal; In the case where the second emergency event that is the same emergency event as the first emergency event exists in the shared memory, acquiring emergency medical information of the second emergency event with respect to the emergency event; Determine supplementary emergency medical information for the emergency event this time according to the emergency medical information of the second emergency event to the emergency event and the emergency medical information corresponding to the first emergency information; Calling the storage process corresponding to the first emergency medical information to create a cloned virtual machine, and storing the supplementary emergency medical information in the shared storage space through the cloned virtual machine; Wherein, determining the supplementary emergency medical information for the emergency event based on the emergency medical information of the second emergency event and the emergency medical information corresponding to the first emergency information includes: According to the first emergency event, for each emergency medical description in the emergency medical information of the emergency event, construct a first description vector corresponding to each emergency medical description; According to each emergency medical description in the emergency medical information of the emergency event, the second emergency event constructs a second description vector corresponding to each emergency medical description; Matching a first description vector corresponding to each of the emergency medical descriptions corresponding to the first emergency event with a second description vector corresponding to each of the emergency medical descriptions corresponding to the second emergency event to obtain a matching value; constructing a blank matrix according to the number of the first description vectors and the number of the second description vectors; Fill the matching values ​​of the first description vector corresponding to each of the emergency medical descriptions corresponding to the first emergency event and the second description vector corresponding to each of the emergency medical descriptions corresponding to the second emergency event into the blank matrix to construct a matching matrix; According to the Hungarian algorithm and the matching matrix, searching the second description vector for the best matching vector of the first description vector corresponding to each of the emergency medical descriptions corresponding to the first emergency event; Determine, based on a preset matching threshold and a matching value between a first description vector corresponding to each of the emergency medical descriptions and the corresponding optimal matching vector, whether each emergency medical description in the emergency medical information of the first emergency event and the emergency medical description corresponding to the corresponding optimal matching vector in the second emergency event are the same medical description; Based on the determination result of whether it is the same medical description, the supplementary emergency medical information for the emergency event is determined.

2. The emergency medical information management method according to claim 1, characterized in that: The method further comprises: Using the supplementary emergency medical information and the emergency medical information of the second emergency event on the emergency event as the emergency medical information of the first emergency event, regenerating and sending emergency event response suggestions for the emergency event to the device end, so as to display the emergency event response suggestions on the device end; The supplementary emergency medical information is written into the emergency medical record corresponding to the second emergency event, a new emergency medical record for the emergency event is generated, and the new emergency medical record for the emergency event is sent to the medical terminal.

3. The emergency medical information management method according to claim 1, characterized in that: The generating, based on the emergency medical information of the first emergency event, and sending to the device an emergency event response suggestion for the emergency event, comprises: According to the characteristic emergency medical description in the emergency medical information of the first emergency event, construct a root node of a decision tree for the first emergency event, wherein the root node includes all characteristic emergency medical descriptions in the emergency medical information of the first emergency event; Determining, according to the characteristic information of each characteristic emergency medical description, an initial weight of each characteristic emergency medical description in the emergency medical information; According to the initial weight of each of the characteristic emergency medicine descriptions in the emergency medicine information, combining a preset first number of multiple characteristic emergency medicine descriptions from large to small to obtain a preset second number of branch child nodes; The following steps are executed in a loop: randomly removing one of the characteristic emergency medicine descriptions from each of the branch sub-nodes to obtain a branch sub-node of the branch sub-node, until the sum of the initial weights of the characteristic emergency medicine descriptions in the obtained branch sub-nodes is less than a preset threshold, thereby obtaining a minimum branch sub-node; According to the characteristic emergency medical description in each of the minimum branch subnodes, emergency event response suggestions for the emergency event are generated and sent to the device end.

4. The emergency medical information management method according to claim 1, characterized in that: The step of calling a first function corresponding to the reporting method according to the reporting method of the first emergency information by the device end, and creating an identification process corresponding to the first emergency information includes: Determining a reporting method for reporting the first emergency information by the device end according to a reporting identifier carried by the first emergency information reported by the device end; According to a preset function mapping table, query the first function corresponding to the reporting method, wherein different reporting methods correspond to a function in the function mapping table one by one; Passing the extracted patient information as a parameter to the first function; An identification process corresponding to the first emergency information is created by calling a copy of the parent process of the first function.

5. The emergency medical information management method according to any one of claims 1 to 4, characterized in that: The reporting method includes any one of a text message reporting method, a voice reporting method, a mini-program reporting method, an application reporting method, and a telephone reporting method.

6. An emergency medical information management method, characterized in that: Applied to the device side, the method includes: In response to the first emergency information corresponding to the received emergency event, the first emergency information is reported to the medical cloud edge server, so that the medical cloud edge server calls the first function corresponding to the reporting method according to the reporting method of the first emergency information reported by the device end, creates an identification process corresponding to the first emergency information, and calls the second function to create a storage process corresponding to the first emergency information, and calls the identification process corresponding to the first emergency information to identify the medical information carried by the first emergency information to obtain the emergency medical information of the first emergency event corresponding to the first emergency information, and determines whether there is a second emergency event that is the same emergency event as the first emergency event in the shared memory according to the emergency medical information corresponding to the first emergency information, and if there is no second emergency event that is the same emergency event as the first emergency event in the shared memory, calls the storage process corresponding to the first emergency information to create an original virtual machine, and creates a shared storage space in the shared memory through the original virtual machine, and calls the storage process corresponding to the first emergency information to store the emergency medical information corresponding to the first emergency information in the created shared storage space;In the case where the second emergency event that is the same emergency event as the first emergency event exists in the shared memory, the emergency medical information of the second emergency event on the emergency event is obtained, and the supplementary emergency medical information for the emergency event is determined based on the emergency medical information of the second emergency event on the emergency event and the emergency medical information corresponding to the first emergency information, the storage process corresponding to the first emergency information is called to create a cloned virtual machine, and the supplementary emergency medical information is stored in the shared storage space through the cloned virtual machine, wherein the supplementary emergency medical information for the emergency event is determined based on the emergency medical information of the second emergency event on the emergency event and the emergency medical information corresponding to the first emergency information, including: according to each emergency medical description in the emergency medical information of the emergency event by the first emergency event, a first description vector corresponding to each emergency medical description is constructed, according to each emergency medical description in the emergency medical information of the emergency event by the second emergency event, a second description vector corresponding to each emergency medical description is constructed, and each emergency medical description corresponding to the first emergency event is constructed. Match the first description vector corresponding to the emergency medical description of the first emergency event with the second description vector corresponding to each of the emergency medical descriptions corresponding to the second emergency event to obtain a matching value, construct a blank matrix according to the number of the first description vectors and the number of the second description vectors, fill the matching values ​​of the first description vector corresponding to each of the emergency medical descriptions corresponding to the first emergency event and the second description vector corresponding to each of the emergency medical descriptions corresponding to the second emergency event into the blank matrix to construct a matching matrix, query the optimal matching vector of the first description vector corresponding to each of the emergency medical descriptions corresponding to the first emergency event from the second description vector according to the Hungarian algorithm and the matching matrix, determine whether the emergency medical description corresponding to each of the emergency medical descriptions in the emergency medical information of the first emergency event and the emergency medical description corresponding to the optimal matching vector in the second emergency event are the same medical description according to a preset matching threshold and the matching value of the first description vector corresponding to each of the emergency medical descriptions and the corresponding optimal matching vector in the second emergency event are the same medical description, and determine the supplementary emergency medical information for the emergency event according to the determination result of whether they are the same medical description; Receive emergency event response suggestions from the medical cloud edge server for the emergency event corresponding to the first emergency information, and provide the emergency event response suggestions on the device side, wherein the emergency event response suggestions are generated and returned based on the emergency medical information of the first emergency event and the reporting method of the device side sending the first emergency information to the medical cloud edge server.

7. The emergency medical information management method according to claim 6, characterized in that: Providing the emergency event response suggestion on the device side includes: Acquire speaker usage information of the device end, and play the emergency event response suggestion through the speaker of the device end when the speaker usage information indicates that the speaker of the device end is not occupied; When the speaker on the device end is occupied in the speaker usage information table, a text response suggestion description is generated according to the emergency event response suggestion, and the text response suggestion description is displayed on the device end.

8. The emergency medical information management method according to claim 6 or 7, characterized in that: The reporting method includes any one of a text message reporting method, a voice reporting method, a mini-program reporting method, an application reporting method, and a telephone reporting method.

9. An emergency medical information management system, characterized in that: include: The medical cloud edge server and medical terminal described in any one of claims 1-5, and any number of device terminals described in any one of claims 6-8, wherein the device terminals are communicatively connected to the medical cloud edge server via any wireless communication method.

Images