An intelligent medical fault processing system and method based on medical data transmission
Through the interaction between wearable devices and smart medical devices, the location information is analyzed to confirm the device status, the problem of confirming the status of smart medical devices is solved, the normal transmission of medical data and the accuracy of the timing health database is ensured, and the research value of the database is enhanced.
Patent Information
- Application Number
- CN202210201012.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-02
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2042-03-02
AI Technical Summary
Existing intelligent medical fault handling technology cannot effectively confirm whether the smart medical equipment is in normal working state, resulting in abnormal data transmission of user medical treatment data, affecting the accuracy and research value of timing health databases.
Through the interaction between wearable devices and smart medical devices, the first location information and the second location information are obtained and analyzed to confirm whether the smart medical device is in a normal working state. If logically related, the user's medical data is transmitted to the cloud server to ensure the normal data is Sexual and timing health database accuracy.
Ensure that the medical treatment data received by the cloud server is normal data, avoid the time series health database containing invalid or abnormal data, and improve the database's correct characterization of user health and the research reference value of other doctors.
Smart Images

Figure CN114582480B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of intelligent medical technology, and in particular to an intelligent medical fault processing system and method based on medical data transmission. Background Art
[0002] The increasing maturity of current intelligent medical technology and related intelligent medical equipment has provided many conveniences for users to seek medical treatment. For example, on the one hand, it can greatly reduce the time users have to wait for medical treatment, and on the other hand, it can effectively reduce the workload of medical workers. Some large hospitals are usually equipped with a large number of intelligent medical equipment to process users' medical data. When these intelligent medical devices fail, some technical solutions need to be adopted to identify the normal and faulty devices from the above-mentioned intelligent medical devices and export the normal medical data of the user from the normal operating intelligent medical device or bypass the faulty intelligent medical device and pass the user's medical data to another intelligent medical device in normal working condition. At the same time, the ownership and control of the medical data related to user visits / examinations generated by the intelligent medical devices of various medical institutions still mainly belong to the above-mentioned medical institutions. In short, the medical data related to user visits / examinations can only be stored in the institution corresponding to the intelligent medical device that generates the medical data, and is controlled and used by the above-mentioned institution. Therefore, users cannot use the cloud server of their own choice to collect their own medical data from the smart medical devices of medical institutions to form the user's longitudinal (such as along the time direction) and transverse (such as the subdivision categories of various health data) time series health database.
[0003] For example, a Chinese patent document with a publication number of CN111489816B discloses a method and a cloud server for intelligent medical fault handling based on the transmission of medical data. The cloud server of the invention generates a fault trajectory map based on the fault prompt information when the fault prompt information is detected. Afterwards, the first identity information is determined from the received medical data and the second identity information is determined from the fault prompt information. Then, when the first identity information and the second identity information are the same, the medical data determined as the review data is transmitted based on the fault trajectory map to realize the online review of the intelligent medical device with a fault, and when the first identity information and the second identity information are different, the transmission direction information other than the fault trajectory map is determined and the medical data determined as normal data is transmitted based on the transmission direction information to ensure that the patient's medical data will not be received when the intelligent medical device is in a fault detection state. In short, the invention has been able to realize the transmission of the medical data determined as normal data in the intelligent medical device between other intelligent medical devices in normal working state based on the transmission direction information when the intelligent medical device performs fault detection, so as to ensure that the patient's medical data will not be received when the intelligent medical device is in a fault detection state.
[0004] However, the above invention still has the following technical deficiencies: although the technical solution of the above invention can transmit the medical data determined as normal data in the smart medical device between other smart medical devices in normal working state based on the transmission direction information, so as to ensure that the patient's medical data will not be received when the smart medical device is in a fault detection state, when the smart medical device is not in a fault detection state, the transmission direction information of the invention cannot confirm whether a smart medical device that receives the medical data is in a normal working state or in a fault state; more importantly, when it is desired to continuously collect the medical data of the user in the smart medical device through the cloud server to form a time series corresponding to the user In the case of a health database, if the cloud server or other devices cannot judge the working status of the smart medical device (for example, identify whether the smart medical device is in a faulty state), even if the cloud server can continuously collect the user's medical data in the smart medical device, the collected medical data itself will not be normal data or the smart medical device cannot send the user's normal medical data to the cloud server due to a fault, resulting in the time series health database established by the cloud server containing a lot of invalid or noise data or abnormal data that cannot correctly characterize the user's health, thereby affecting the actual research / reference value of the time series health database for other doctors or medical institutions.
[0005] In addition, on the one hand, there are differences in understanding among those skilled in the art; on the other hand, the applicant studied a large number of documents and patents when making the present invention, but due to space limitations, not all details and contents are listed in detail. However, this does not mean that the present invention does not have the characteristics of these prior arts. On the contrary, the present invention already has all the characteristics of the prior art, and the applicant reserves the right to add relevant prior art to the background technology. Summary of the invention
[0006] Although the existing intelligent medical fault handling technology can transfer the medical data determined as normal data in the intelligent medical device between other intelligent medical devices in normal working state based on the transmission direction information, so as to ensure that the patient's medical data will not be received when the intelligent medical device is in a fault detection state, when the intelligent medical device is not in a fault detection state, the transmission direction information of the invention cannot confirm whether a certain intelligent medical device that receives the medical data is in a normal working state or in a fault state; more importantly, when it is desired to continuously collect the medical data of users in the intelligent medical devices through the cloud server to form a time series health database corresponding to the user In this case, if the cloud server or other devices cannot judge the status of the smart medical device (for example, whether the smart medical device is in a faulty state), even if the cloud server can continuously collect the user's medical data in the smart medical device, the collected medical data itself is not normal data or the smart medical device cannot send the user's normal medical data to the cloud server due to a fault, resulting in the time series health database established by the cloud server containing a lot of invalid or noise data or abnormal data that cannot correctly characterize the user's health, thereby affecting the actual research / reference value of the time series health database for other doctors or medical institutions.
[0007] In view of the shortcomings of the prior art, the present invention provides an intelligent medical fault processing system and method based on medical data transmission. The intelligent medical fault processing system at least includes an intelligent medical device, a wearable device and a cloud server.
[0008] The smart medical device is configured to generate or obtain the user's medical data. A plurality of the smart medical devices can form a smart medical device cluster. The medical data can be transmitted between a plurality of the smart medical device clusters or smart medical devices.
[0009] The cloud server can communicate with the smart medical devices so that the medical data can be transmitted between the multiple smart medical devices under the control of the cloud server.
[0010] Since the user cannot predict or judge whether the smart medical device he is using is really in normal working state (for example, the smart medical device can open the boot interface normally but cannot correctly process the medical data it receives), when the user wants to process the medical data in the smart medical device he is using (for example, transmit it to the cloud server to form his personal health database), the smart medical device is likely to send abnormal medical data to the cloud server due to being in a faulty state. Therefore, the cloud server of the present invention uses the following technical solution to confirm whether the smart medical devices in the smart medical device cluster are in normal working state.
[0011] The wearable device interacts with the smart medical device so that the smart medical device can obtain the first location information of the wearable device. The wearable device can send the second location information of the wearable device to the cloud server.
[0012] When the cloud server is able to confirm whether the smart medical device that obtains the first location information is in normal working condition by analyzing the first location information and the second location information, the cloud server is configured to regulate the smart medical device that corresponds to the first location information and is in normal working condition to send the medical data of the user corresponding to the wearable device to the cloud server, so that the cloud server can obtain the medical data of the user corresponding to the wearable device from the smart medical device that corresponds to the first location information and is in normal working condition in a time series manner to establish a time series health database of the user.
[0013] Particularly preferably, the method in which the cloud server can confirm whether the smart medical device that obtains the first location information is in a normal working state by analyzing the first location information and the second location information is:
[0014] The cloud server can request medical information containing the first location information of the wearable device from at least one smart medical device used by the user wearing the wearable device;
[0015] The cloud server obtains the second location information sent by the wearable device;
[0016] The cloud server analyzes and compares the first location information in the medical information containing the first location information of the wearable device with the second location information sent by the wearable device, and the smart medical device that obtains the first location information is in normal working condition when and only when the first location information has a logical association with the second location information.
[0017] When the first location information of the smart medical device requested by the cloud server has no logical association with the second location information sent by the wearable device, the cloud server determines that the smart medical device corresponding to the first location information is in a fault state.
[0018] The condition that the first location information and the second location information are logically associated is that the location information in the first location information is consistent or substantially consistent with the location information in the second location information, and the timestamp in the first location information is consistent or substantially consistent with the timestamp in the second location information.
[0019] Through this configuration, the user can send a storage path instruction for establishing a medical data transmission path between the cloud server and the smart medical device whose first location information is confirmed by the cloud server to be logically associated with the second location information through a wearable device, thereby enabling the smart medical device to send the user's normal (i.e., the content of the medical data is not different from its initial state due to reasons such as medical device failure) medical data to the cloud server to ensure that the medical data related to the user received by the cloud server are all normal medical data, and establish a time series health database for the user in a time series manner based on the above normal medical data, so as to avoid the time series health database established by the cloud server containing many invalid noise data or abnormal data that cannot correctly characterize the user's health, thereby affecting the actual research / reference value of the time series health database to other doctors or medical institutions.
[0020] According to a preferred embodiment, the wearable device whose second location information is logically associated with the first location information can send a storage path instruction to the cloud server for establishing a medical data transmission path between the cloud server and the smart medical device whose first location information is logically associated with the second location information, so that the cloud server can obtain the medical data of the user corresponding to the wearable device whose second location information is logically associated with the first location information from the smart medical device whose first location information is logically associated with the second location information.
[0021] The medical data transmission path is a data channel between smart medical devices and cloud servers for transmitting medical data.
[0022] Preferably, the medical data transmission path can be directed from the smart medical device to the cloud server. Preferably, the medical data transmission path can also be directed from the cloud server to the smart medical device.
[0023] After the cloud server receives a storage path instruction for establishing a medical data transmission path between the cloud server and the smart medical device whose first location information can be logically associated with the second location information, the cloud server can send the storage path instruction to the above-mentioned smart medical device.
[0024] Normal medical consultation data is defined as medical consultation data whose data content is not different from its initial state content due to medical device failure.
[0025] According to a preferred embodiment, the storage path instruction for establishing a medical data transmission path between the cloud server and the smart medical device having a logical association with the acquired first location information and the second location information includes at least: a data stream type, a user identifier and sub-block data content, the data stream type is used to indicate the transmission direction of the medical data on the medical data transmission path, the user identifier is used to indicate the user's identity information, and the sub-block data content is the user's medical data.
[0026] According to a preferred embodiment, the wearable device whose second location information is confirmed by the cloud server to have a logical association with the first location information can obtain the network address of the smart medical device whose first location information is confirmed by the cloud server to have a logical association with the second location information, and define it as the data source address of the medical data of the user corresponding to the wearable device whose second location information is confirmed to have a logical association with the first location information or the data destination address of the medical data that the cloud server needs to transmit at that time.
[0027] According to a preferred embodiment, when the first location information is confirmed by the cloud server that the smart medical device that has a logical association with the second location information has obtained the storage path instruction, the smart medical device that has a logical association with the first location information can send the network address of the smart medical device to the wearable device that has a logical association with the second location information.
[0028] Through this configuration, the user can use the wearable device to send the user's medical data in the smart medical device whose first location information is confirmed by the cloud server to be logically associated with the second location information to the cloud server corresponding to the data destination address in the storage path instruction.
[0029] According to a preferred embodiment, the user can authorize, through the wearable device he wears, the smart medical device whose first location information is confirmed by the cloud server to have a logical association with the second location information to send the user's medical data to the cloud server.
[0030] According to a preferred embodiment, the cloud server is able to issue a data request to the smart medical device corresponding to the data source address based on the data source address in the storage path instruction, so as to obtain the relevant medical data of the user corresponding to the user identifier in the storage path instruction in the smart medical device whose first location information is confirmed by the cloud server to have a logical association with the second location information.
[0031] According to a preferred embodiment, the cloud server is able to obtain the timestamp of the user's medical data, and based on the timestamp, store the medical data in a time-series manner into a time-series health database corresponding to the user in the cloud server.
[0032] The timestamp of the medical consultation data is the time when the smart medical device generates the medical consultation data.
[0033] Preferably, the cloud server can include multiple time series health databases. Preferably, one time series health database can only correspond to one user one by one.
[0034] According to a preferred embodiment, the cloud server connected to the data of the smart medical device and the wearable device can only send the medical data corresponding to the level of authorization to the smart medical device of other individuals or institutions authorized by the wearable device based on the authorization of the user corresponding to the wearable device. BRIEF DESCRIPTION OF THE DRAWINGS
[0035] Figure 1 It is a simplified schematic diagram of module connection relationships of a preferred implementation mode provided by the present invention.
[0036] Reference numerals list
[0037] 1: Smart medical devices; 2: Wearable devices; 3: Cloud servers. DETAILED DESCRIPTION
[0038] The following is a detailed description with reference to the accompanying drawings.
[0039] like Figure 1 An intelligent medical fault processing system based on the transmission of medical data is shown. The intelligent medical fault processing system at least includes an intelligent medical device 1, a wearable device 2 and a cloud server 3.
[0040] The intelligent medical device 1 is configured to generate or obtain the user's medical treatment data.
[0041] A plurality of the intelligent medical devices 1 can form a cluster of intelligent medical devices 1. The medical consultation data can be transmitted between a plurality of clusters of the intelligent medical devices 1 or between intelligent medical devices 1.
[0042] The cloud server 3 can be in a cascade relationship with multiple smart medical device 1 clusters.
[0043] For example, the cloud server 3 communicates with smart medical device 1 cluster A, smart medical device 1 cluster A communicates with smart medical device 1 cluster B, smart medical device 1 cluster C communicates with smart medical device 1 cluster D, and so on.
[0044] Furthermore, each smart medical device 1 cluster includes at least one smart medical device 1, and the smart medical devices 1 in the smart medical device 1 clusters at different levels communicate in sequence to form a complete medical treatment process.
[0045] The cloud server 3 can communicate with the smart medical devices 1 so that the medical data can be transmitted between the multiple smart medical devices 1 under the control of the cloud server 3 .
[0046] Medical data includes but is not limited to: personal basic information data, medical information, user medical record data, laboratory test report data, imaging examination report data, hospitalization medical record data, outpatient treatment data, personal electronic medical record data, electronic physical examination data, etc.
[0047] Preferably, the smart medical device 1 may include but is not limited to: self-service equipment in the hospital, inspection and testing equipment in various departments of the hospital, etc. Preferably, the wearable device 2 may include but is not limited to: smart bracelets, VR glasses, AR glasses, smart phones, etc. Preferably, different users can choose the same or different cloud servers 3 as storage devices for their medical data.
[0048] The cloud server 3 can be selected by the user. Preferably, the cloud server 3 and the smart medical device 1 communicate so that the medical data can be transmitted between the multiple smart medical devices 1 under the control of the cloud server 3. The existing technology can be directly used. For example, the cloud server 3 can use the smart medical fault handling method based on medical data transmission and the cloud server disclosed in the Chinese patent document with publication number CN111489816B to transmit the medical data, so it will not be repeated here.
[0049] Since the user cannot predict or judge whether the smart medical device 1 he is using is really in a normal working state (for example, the smart medical device 1 can open the boot interface normally but cannot correctly process the medical data it receives), when the user wants to process the medical data in the smart medical device 1 he is using (for example, transmit it to the cloud server 3 to form his personal health database), the smart medical device 1 is likely to send abnormal medical data to the cloud server 3 due to being in a fault state. Therefore, the cloud server 3 of the present invention uses the following technical solution to confirm whether the smart medical devices 1 in the smart medical device 1 cluster are in a normal working state.
[0050] The wearable device 2 interacts with the smart medical device 1 so that the smart medical device 1 can obtain the first location information of the wearable device 2. The wearable device 2 can send the second location information of the wearable device 2 to the cloud server 3.
[0051] Preferably, when the user needs to authorize the smart medical device 1 to send the user's related medical data to the cloud server 3 and / or the cloud server 3 to the smart medical device 1, the user can interact with the smart medical device 1 through the wearable device 2 so that the smart medical device 1 can obtain the first location information of the wearable device 2.
[0052] Preferably, when the user needs to authorize the smart medical device 1 to send the user's related medical data to the cloud server 3 and / or the cloud server 3 to the smart medical device 1, the user can send the second location information of the wearable device 2 to the cloud server 3 through the wearable device 2.
[0053] The first location information at least includes: the location information of the wearable device 2 acquired by the smart medical device 1, and the timestamp when the smart medical device 1 acquires the location information. The location information may be three-dimensional coordinate information.
[0054] Preferably, the wearable device 2 can send the second location information of the wearable device 2 to the cloud server 3 when the distance between the wearable device 2 and the smart medical device 1 is lower than a first threshold distance.
[0055] The second location information at least includes: the location information when the wearable device 2 obtains itself, and the timestamp when the wearable device 2 obtains the location information.
[0056] When the cloud server 3 is able to confirm whether the smart medical device 1 that obtains the first location information is in normal working condition by analyzing the first location information and the second location information, the cloud server 3 is configured to be able to regulate the smart medical device 1 that corresponds to the first location information and is in normal working condition to send the medical data of the user corresponding to the wearable device 2 to the cloud server 3, so that the cloud server 3 can obtain the medical data of the user corresponding to the wearable device 2 from the smart medical device 1 that corresponds to the first location information and is in normal working condition in a time series manner to establish a time series health database of the user.
[0057] The cloud server 3 can request medical information containing the first location information of the wearable device 2 from at least one smart medical device 1 used by the user wearing the wearable device 2 .
[0058] Preferably, the medical consultation information sent by the smart medical device 1 to the cloud server 3 can include the first location information.
[0059] The smart medical device 1 can only obtain the first location information of the wearable device 2 when the distance between the smart medical device 1 and the wearable device 2 is lower than the first threshold distance.
[0060] The first threshold distance may be set according to actual application scenarios, for example, the first threshold distance may be twenty centimeters.
[0061] The user can obtain the network address of the cloud server 3 selected by the user through the wearable device 2.
[0062] The user can establish a data connection with the cloud server 3 selected by the user through the wearable device 2 worn by the user based on the network address of the cloud server 3 selected by the user.
[0063] According to a preferred embodiment, the cloud server 3 can analyze the first location information and the second location information to confirm whether the smart medical device 1 that obtains the first location information is in a normal working state by:
[0064] The cloud server 3 can request medical information containing the first location information of the wearable device 2 from at least one smart medical device 1 used by the user wearing the wearable device 2;
[0065] The cloud server 3 obtains the second location information sent by the wearable device 2;
[0066] The cloud server 3 analyzes and compares the first location information in the medical information containing the first location information of the wearable device 2 with the second location information sent by the wearable device 2, and the smart medical device 1 that obtains the first location information is in normal working condition when and only when the first location information has a logical association with the second location information.
[0067] When the first location information of the smart medical device 1 requested by the cloud server 3 has no logical association with the second location information sent by the wearable device 2, the cloud server 3 determines that the smart medical device 1 corresponding to the first location information is in a fault state.
[0068] The condition that the first location information and the second location information are logically associated is that the location information in the first location information is consistent or substantially consistent with the location information in the second location information and the timestamp in the first location information is consistent or substantially consistent with the timestamp in the second location information.
[0069] For example, when the location information in the first location information is consistent with the location actually expressed by the location information in the second location information (such as the two-dimensional coordinates on the two-dimensional map of the hospital), if the specific format adopted by the location information in the first location information and the location information in the second location information (such as using the same coordinate system) is consistent or approximately consistent, and the time expression format adopted by the timestamp in the first location information and the timestamp in the second location information (such as the same time format as "YY-MM-DD") is consistent or approximately consistent, the cloud server 3 determines that the location information in the first location information is consistent or approximately consistent with the location information in the second location information.
[0070] Since the smart medical device 1 in a faulty state cannot correctly obtain the real-time location and location expression format of the wearable device 2 of the user who is using the smart medical device 1, on the one hand, it cannot also obtain the correct time and its format in real time or correctly transmit the time to the cloud server 3 (for example, the smart medical device 1 in a faulty state can only send garbled time information to the cloud server 3 but cannot correctly send the time when it obtains the real-time location of the user's wearable device 2).
[0071] Through this configuration, the user can send a storage path instruction for establishing a medical data transmission path between the cloud server 3 and the smart medical device 1 whose first location information is confirmed by the cloud server 3 to be logically associated with the second location information through the wearable device 2, thereby enabling the smart medical device 1 to send the normal medical data of the user (that is, the content of the medical data is not different from the content in its initial generation state due to medical device failure) to the cloud server 3 to ensure that the medical data related to the user received by the cloud server 3 are all normal medical data, and establish a time series health database for the user in a time series manner based on the above normal medical data, so as to avoid the time series health database established by the cloud server 3 containing many invalid noise data or abnormal data that cannot correctly represent the user's health, thereby affecting the actual research / reference value of the time series health database for other doctors or medical institutions.
[0072] According to a preferred embodiment, the wearable device 2 whose second location information is logically associated with the first location information can send a storage path instruction to the cloud server 3 for establishing a medical data transmission path between the cloud server 3 and the smart medical device 1 whose first location information is logically associated with the second location information, so that the cloud server 3 can obtain the medical data of the user corresponding to the wearable device 2 whose second location information is logically associated with the first location information from the smart medical device 1 whose first location information is logically associated with the second location information.
[0073] The medical data transmission path is a data channel between the smart medical device 1 and the cloud server 3 for transmitting medical data.
[0074] Preferably, the medical consultation data transmission path can be directed from the smart medical device 1 to the cloud server 3. Preferably, the medical consultation data transmission path can also be directed from the cloud server 3 to the smart medical device 1.
[0075] After the cloud server 3 receives a storage path instruction for establishing a medical data transmission path between the cloud server 3 and the smart medical device 1 whose first location information can be logically associated with the second location information, the cloud server 3 can send the storage path instruction to the above-mentioned smart medical device 1.
[0076] Preferably, the wearable device 2 worn by the user can issue storage path instructions to the medical device and the cloud server 3 respectively. Preferably, the storage path instruction is used to establish a data connection between the smart medical device 1 that has obtained the storage path instruction and the cloud server 3 that has obtained the storage path instruction.
[0077] According to a preferred embodiment, the storage path instruction for establishing a medical data transmission path between the cloud server 3 and the smart medical device 1 having a logical association with the acquired first location information and second location information includes at least: a data stream type, a user identifier, and sub-block data content. The data stream type is used to indicate the transmission direction of the medical data on the medical data transmission path. The user identifier is used to indicate the identity information of the user. The sub-block data content is the medical data of the user.
[0078] Preferably, the transmission direction may be the direction from the smart medical device 1 used by the user to the cloud server 3 .
[0079] Preferably, the transmission direction may also be the direction from the cloud server 3 to the smart medical device 1 used by the user.
[0080] Preferably, the data flow type consists of at least a data source address and a data destination address.
[0081] Preferably, the user identifier may be the user's ID number or medical insurance card number, etc.
[0082] Preferably, the sub-block data content is the user's medical treatment data. For example, the sub-block data content may include but is not limited to: physical examination sub-data, medical imaging sub-data, hospitalization sub-data, vaccination sub-data, wearable device 2 monitoring sub-data, etc.
[0083] According to a preferred embodiment, the wearable device 2 whose second location information is confirmed by the cloud server 3 to have a logical association with the first location information can obtain the network address of the smart medical device 1 whose first location information is confirmed by the cloud server 3 to have a logical association with the second location information, and define it as the data source address of the medical data of the user corresponding to the wearable device 2 whose second location information is confirmed to have a logical association with the first location information or the data destination address of the medical data that the cloud server 3 needs to transmit at that time.
[0084] Preferably, the network address of the cloud server 3 selected by the user can be used as the data destination address of the current consultation data.
[0085] Preferably, the wearable device 2 data-connected to the cloud server 3 can obtain the network address of the smart medical device 1 whose first location information is confirmed by the cloud server 3 as having a logical association with the second location information after obtaining the authorization of the user.
[0086] The data destination address of the medical data may be the network address of the cloud server 3 selected by the user.
[0087] The data destination address of the medical data may also be other smart medical devices 1 authorized by the user.
[0088] According to a preferred embodiment, when the first location information is confirmed by the cloud server 3 that the smart medical device 1 that is logically associated with the second location information has obtained the storage path instruction, the smart medical device 1 that is logically associated with the first location information and the second location information can send the network address of the smart medical device 1 to the wearable device 2 that is logically associated with the second location information and the first location information.
[0089] After obtaining the storage path instruction, the smart medical device 1 sends the network address of the smart medical device 1 to the wearable device 2. The data source address of the data stream type in the storage path instruction initially received by the smart medical device 1 is empty. Preferably, after receiving the network address of the smart medical device 1, the wearable device 2 can add the network address of the smart medical device 1 into the data source address of the data stream type in the storage path instruction, and send the storage path instruction to the corresponding cloud server 3 and / or smart medical device 1.
[0090] Preferably, the user can send the user's medical data in the smart medical device 1 whose first location information is confirmed by the cloud server 3 to be logically associated with the second location information to the cloud server 3 corresponding to the data destination address in the storage path instruction through the wearable device 2.
[0091] For example, if the data flow type in the storage path instruction is IP1+IP2, IP1 is the network address of the relevant smart medical device 1 of the medical and health institution, and IP2 is the network address of the cloud server 3 specified / authorized by the user through the wearable device 2, then the above data flow type indicates that the relevant smart medical device 1 of the medical and health institution with the network address IP1 sends the user's medical data of the current visit / examination to the cloud server 3 with the network address IP2 specified / authorized by the user; conversely, if the data flow type in the storage path instruction is IP3+IP4, IP3 is the network address of the cloud server 3 specified / authorized by the user through the wearable device 2, and IP4 is the network address of the relevant smart medical device 1 of the medical and health institution, then the above data flow type indicates that the cloud server 3 with the network address IP3 specified / authorized by the user needs to send the user's medical data corresponding to the user identifier in the current storage path instruction to the smart medical device 1 of the medical and health institution with the network address IP4 authorized by the user's wearable device 2.
[0092] Through this configuration, the user can send the user's medical data in the smart medical device 1 whose first location information is confirmed by the cloud server 3 to be logically associated with the second location information to the cloud server 3 corresponding to the data destination address in the storage path instruction through the wearable device 2.
[0093] According to a preferred embodiment, the user can authorize the smart medical device 1 whose first location information is confirmed by the cloud server 3 to have a logical association with the second location information to send the user's medical data to the cloud server 3 through the wearable device 2 worn by the user.
[0094] According to a preferred embodiment, the cloud server 3 is able to issue a data request to the smart medical device 1 corresponding to the data source address based on the data source address in the storage path instruction, so as to obtain the relevant medical data of the user corresponding to the user identifier in the storage path instruction in the smart medical device 1 whose first location information is confirmed by the cloud server 3 to have a logical association with the second location information.
[0095] The cloud server 3 establishes a data connection with the smart medical device 1 corresponding to the data source address in the storage path instruction based on the storage path instruction, and obtains the user's medical data corresponding to the user identifier in the storage path instruction from the smart medical device 1.
[0096] According to a preferred embodiment, the cloud server 3 is able to obtain the timestamp of the user's medical data, and based on the timestamp, store the medical data in a time series manner into a time series health database corresponding to the user in the cloud server 3.
[0097] The timestamp of the medical consultation data is the time when the smart medical device 1 generates the medical consultation data.
[0098] Preferably, the cloud server 3 can include multiple time series health databases. Preferably, one time series health database can only correspond to one user one by one.
[0099] According to a preferred embodiment, the cloud server 3 which is data-connected to the smart medical device 1 and the wearable device 2 can only send the medical data corresponding to the level of authorization to the smart medical device 1 of other individuals or institutions authorized by the wearable device 2 based on the authorization of the user corresponding to the wearable device 2.
[0100] For example, after authorization by the user, the doctor can obtain the user's medical data from the cloud server 3 (or virtual server), such as searching for chest CT data required by the doctor from the medical data / examination data within the time threshold. Preferably, the time threshold can be set according to the doctor's professional knowledge and experience. For example, the time threshold of chest CT can be half a month, that is, if there is a valid chest CT examination report within the time threshold in the user's health book, the above doctor can directly use the chest CT examination report, and there is no need to repeat the chest CT examination in this visit.
[0101] Preferably, any other individual or organization that needs to access the user's health data needs to obtain the user's authorization, and the user's medical data in the cloud server 3 can be shared with other individuals or organizations.
[0102] Particularly preferably, the user's medical data in the cloud server 3 can be transmitted and / or shared with other individuals or institutions only under the user's corresponding level of authorization.
[0103] Preferably, the cloud server 3 acquires and stores the medical treatment data of the user corresponding to the user identifier in the current storage path instruction sent by the smart medical device 1 in a time-sequential manner.
[0104] For example, when a user receives a vaccine provided by a medical institution, the vaccination information is initially generated in the relevant smart medical device 1 of the medical institution. After the user completes the vaccination, the wearable device 2 used by the user (for example, the user presses the corresponding button of the wearable device 2, etc.) can establish a data connection with the relevant smart medical device 1 of the above-mentioned medical institution and send a storage path instruction to the relevant smart medical device 1 of the medical institution. After the relevant smart medical device 1 of the medical institution obtains the storage path instruction, the relevant smart medical device 1 of the medical institution sends the user's medical data (i.e., the user's vaccination information at that time) to the cloud server 3 corresponding to the data destination address in the storage path instruction.
[0105] Through this configuration, in addition to being able to retain the user's medical data, the relevant smart medical device 1 of the medical institution can also be authorized by the user through the wearable device 2 used by the user, so that the user's medical information can be sent to the cloud server 3 designated / authorized by the user through the smart medical device 1, thereby enabling the cloud server 3 to establish a time-series health database related to the user based on the medical data.
[0106] Preferably, the wearable device 2 can authorize according to the type and / or time range of the user's medical data. For example, the user only authorizes the user's electronic physical examination data within a certain year to be transmitted / shared to other individuals or institutions through the wearable device 2. The sub-block data type in the storage path instruction can be the category of medical data that needs to be authorized. Preferably, the sub-block data type of the storage path instruction can also be set by the wearable device 2 to allow the authorized time period.
[0107] In short, this setting method can prevent the user's data from being taken over by other institutions, and can also ensure that the cloud server 3 can send the medical data corresponding to the authorization level to the smart medical device 1 of the authorized individual or institution only after the user's authorization.
[0108] Through the above configuration, 1) the user-related medical data generated by the smart medical device 1 is stored in a time series manner through the cloud server 3 authorized or trusted by the user, and the user can also retrieve the medical data related to the user through the wearable device 2 to fully and clearly understand his or her health status; 2) the medical data authorized by the user through the wearable device 2 is sent to the smart medical device 1 used by relevant institutions and individuals (such as doctors) through the cloud server 3 to help doctors and medical workers better understand the user's previous health and disease conditions, thereby avoiding misdiagnosis, missed diagnosis, and reducing repeated laboratory tests, imaging examinations and unnecessary medical consultations; 3) the time-series health database established by the cloud server 3 can realize the organization of past information of the user's medical data, so as to facilitate communication and exchange with relevant personnel (such as doctors) and obtain useful information; 4) If a user's identity is diagnosed as a rare disease at a later time, the medical data accumulated in the early stage of the time-series health database established by the cloud server 3 will also have a higher research value accordingly.
[0109] The embodiment of the present invention also provides a cloud server, comprising: a processor, and a memory and a network interface connected to the processor, wherein the network interface is connected to a non-volatile memory in the cloud server. When the processor is running, it retrieves a computer program from the non-volatile memory through the network interface, and runs the computer program through the memory to execute the above method.
[0110] Furthermore, a computer-readable storage medium is provided, wherein the computer-readable storage medium is burned with a computer program, and the computer program implements the above method when running in the memory of the cloud server.
[0111] It should be noted that the above-mentioned specific embodiments are exemplary, and those skilled in the art can come up with various solutions inspired by the disclosure of the present invention, and these solutions also belong to the disclosure scope of the present invention and fall within the protection scope of the present invention. Those skilled in the art should understand that the present invention specification and its drawings are illustrative and do not constitute a limitation on the claims. The scope of protection of the present invention is defined by the claims and their equivalents. The present invention specification contains multiple inventive concepts, such as "preferably", "according to a preferred embodiment" or "optionally", all of which indicate that the corresponding paragraph discloses an independent concept, and the applicant reserves the right to file a divisional application based on each inventive concept.
Claims
1. An intelligent medical fault handling system based on medical data transmission, comprising at least: An intelligent medical device (1), wherein the intelligent medical device (1) is configured to generate or obtain a user's medical treatment data; A cloud server (3) capable of communicating with the intelligent medical device (1) so that the medical data can be transmitted between a plurality of the intelligent medical devices (1) under the control of the cloud server (3); It is characterized by further comprising: The wearable device (2) is capable of interacting with the intelligent medical device (1) so that the intelligent medical device (1) can obtain the first location information of the wearable device (2), and the wearable device (2) can send the second location information of the wearable device (2) to the cloud server (3); The cloud server (3) is configured as follows: regulating the intelligent medical device (1) to send the first location information of the wearable device (2) to the cloud server (3) and to obtain the second location information of the wearable device (2); determining whether the intelligent medical device (1) is in a normal working state based on the first location information and the second location information; The smart medical device (1) for acquiring the first location information is in a normal working state if and only if the first location information and the second location information have a logical association condition that the location information and the timestamp in the first location information and the second location information are consistent or approximately consistent; The intelligent medical device (1) in a normal working state is used to obtain the medical treatment data of the user corresponding to the wearable device (2) in a time series manner to establish a time series health database of the user.
2. The system according to claim 1, characterized in that The method by which the cloud server (3) can confirm whether the intelligent medical device (1) that obtains the first location information is in a normal working state by analyzing the first location information and the second location information is: The cloud server (3) is capable of requesting medical information containing first location information of the wearable device (2) from at least one smart medical device (1) used by a user wearing the wearable device (2); The cloud server (3) obtains the second location information sent by the wearable device (2); The cloud server (3) analyzes and compares the first location information in the medical consultation information containing the first location information of the wearable device (2) with the second location information sent by the wearable device (2).
3. The system according to claim 2, characterized in that The wearable device (2) whose second location information is logically associated with the first location information and is sent to the cloud server (3) can send a storage path instruction to the cloud server (3) for establishing a medical data transmission path between the cloud server (3) and the smart medical device (1) whose first location information is logically associated with the second location information, so that the cloud server (3) can obtain the medical data of the user corresponding to the wearable device (2) whose second location information is logically associated with the first location information from the smart medical device (1) whose first location information is logically associated with the second location information.
4. The system according to claim 3, characterized in that The storage path instruction for establishing a medical data transmission path between the cloud server (3) and the smart medical device (1) having a logical association with the acquired first location information and second location information includes at least: a data stream type, a user identifier and sub-block data content, wherein the data stream type is used to indicate the transmission direction of the medical data on the medical data transmission path, the user identifier is used to indicate the identity information of the user, and the sub-block data content is the medical data of the user.
5. The system according to claim 4, characterized in that The wearable device (2) whose second location information is confirmed by the cloud server (3) to be logically associated with the first location information can obtain the network address of the smart medical device (1) whose first location information is confirmed by the cloud server (3) to be logically associated with the second location information, and define it as the data source address of the medical data of the user corresponding to the wearable device (2) whose second location information is logically associated with the first location information or the data destination address of the medical data that the cloud server (3) needs to transmit.
6. The system according to claim 5, characterized in that When the first location information is confirmed by the cloud server (3) that the smart medical device (1) that is logically associated with the second location information has obtained the storage path instruction, the smart medical device (1) that is logically associated with the first location information can send the network address of the smart medical device (1) to the wearable device (2) that is logically associated with the second location information.
7. The system according to claim 6, characterized in that The user can authorize, through the wearable device (2) worn by the user, the smart medical device (1) whose first location information is confirmed by the cloud server (3) to have a logical association with the second location information to send the user's medical data to the cloud server (3).
8. The system according to claim 7, characterized in that The cloud server (3) is capable of issuing a data request to the smart medical device (1) corresponding to the data source address based on the data source address in the storage path instruction, so as to obtain relevant medical data of the user corresponding to the user identifier in the storage path instruction in the smart medical device (1) whose first location information is confirmed by the cloud server (3) to have a logical association with the second location information.
9. The system according to claim 8, characterized in that The cloud server (3) is capable of obtaining the timestamp of the user's medical data, and based on the timestamp, storing the medical data in a time-series manner into a time-series health database corresponding to the user in the cloud server (3).
10. The system according to claim 9, characterized in that The cloud server (3) connected to the data of the smart medical device (1) and the wearable device (2) can only send the medical data corresponding to the level of authorization to the smart medical device (1) of other individuals or institutions authorized by the wearable device (2) based on the authorization of the user corresponding to the wearable device (2).
