Software version maintenance method and system for anesthesia depth monitor
By comparing and verifying the version information files of the anesthesia depth monitor, using the MD5 algorithm to extract file information, obtain software replacement files and perform version updates, the problem of poor accuracy in identifying brands, models and versions when the device is upgraded offline, and the update is achieved Safe and reliable software updates.
Patent Information
- Application Number
- CN202410992395.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-22
- Publication Date
- 2024-12-03
AI Technical Summary
When the software system is offline upgraded, the existing anesthesia depth monitor has poor accuracy in identifying the brand, model and version, resulting in insufficient safety and reliability and high risk of misoperation.
By comparing the original version information file with the version information check file, using the MD5 information summary algorithm to extract file information, calculate the percentage of data difference, obtain the software replacement file and update the version, check the verification information file again after restarting the device, and display the upgrade results in an image. .
Ensure the accuracy and reliability of the software update of the anesthesia depth monitor, reduce the risk of misoperation, and improve the safety and reliability of the equipment.
Smart Images

Figure CN119065701A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of medical monitoring equipment, and in particular to a software version maintenance method and system for an anesthesia depth monitor. Background Art
[0002] In order to eliminate surgical pain and ensure patient safety during clinical surgery, patients need to be deeply anesthetized. However, there is still a risk of various complications after anesthesia, so it is necessary to monitor the depth of anesthesia of patients. The anesthesia depth monitor is used to monitor the depth of anesthesia during whole-body anesthesia surgery. It detects auditory evoked potentials to monitor the depth of anesthesia of surgical patients in real time and prevent the occurrence of anesthesia complications. In the actual application of anesthesia depth monitors, medical institutions will purchase multiple anesthesia depth monitors in different batches. Sometimes, the purchased anesthesia depth monitors are not only of different models, but also of different manufacturers. Therefore, when upgrading the software system of the anesthesia depth monitor offline, it is very important to distinguish the differences in brand, model and version of the anesthesia depth monitor. The manual judgment method has poor accuracy and high probability of misoperation, which seriously endangers the safety and reliability of the use of anesthesia depth monitors. Summary of the invention
[0003] The main technical problem solved by the present invention is how to ensure the safety and reliability of offline upgrading of the software system of an anesthesia depth monitor.
[0004] According to the first aspect, an embodiment provides a software version maintenance method for an anesthesia depth monitor, which is used to perform version maintenance on a software file of the anesthesia depth monitor in an offline manner, and the software version maintenance method includes: Compare the original version information file with the version information verification file to obtain a consistency comparison result; the original version information file is obtained based on the software file of the anesthesia depth monitor to be maintained, and the version information verification file is obtained by reading from a mobile storage device connected to an external interface in response to a version update instruction; the consistency comparison result is used to identify the degree of data difference between the original version information file and the version information verification file, and is expressed in percentage; Reading a software replacement file corresponding to the consistency comparison result from the mobile storage device according to the consistency comparison result, and storing it in the anesthesia depth monitor; Updating the software file of the anesthesia depth monitor by using the software replacement file; After the version update is completed, the anesthesia depth monitor is restarted.
[0005] In one embodiment, the software version maintenance method further includes: Comparing the verification information file and the upgrade information verification file to obtain a verification comparison result; the verification information file is obtained based on the software file of the anesthesia depth monitor restarted after the version update; the upgrade information verification file is read from the mobile storage device; The upgrade result information is graphically displayed according to the verification and comparison result; the upgrade result information includes upgrade success, upgrade failure and / or upgrade completion.
[0006] In one embodiment, the original version information file is obtained based on the software file of the anesthesia depth monitor to be maintained, including: A first information digest algorithm is applied to extract information from the software file of the anesthesia depth monitor to obtain the original version information file; the first information digest algorithm includes an MD5 information digest algorithm.
[0007] In one embodiment, the verification information file is obtained based on the software file of the anesthesia depth monitor that is restarted after the version update, and includes: A second information digest algorithm is applied to extract information from the software file of the anesthesia depth monitor that is restarted after the version update to obtain the verification information file; the second information digest algorithm includes an MD5 information digest algorithm.
[0008] In one embodiment, the updating of the software file of the anesthesia depth monitor by using the software replacement file includes: Check the file information in the software replacement file to determine that the software replacement file meets the requirements of the version upgrade; the file information includes file type, file name and / or version number information; If the file information is verified to be correct, the version update is executed; otherwise, the version update is stopped and an update failure message is displayed.
[0009] According to the second aspect, an embodiment provides a software version maintenance system for an anesthesia depth monitor, which is used to apply the software version maintenance method as described in the first aspect, and the software version maintenance system includes: An information checking unit is used to compare an original version information file with a version information checking file to obtain a consistency comparison result; the original version information file is obtained based on a software file of an anesthesia depth monitor to be maintained, and the version information checking file is obtained by reading from a mobile storage device connected to an external interface in response to a version update instruction; the consistency comparison result is used to identify the degree of data difference between the original version information file and the version information checking file, and is expressed in percentage; A replacement file acquisition unit, configured to read a software replacement file corresponding to the consistency comparison result from the mobile storage device according to the consistency comparison result, and store the replacement file in the anesthesia depth monitor; The update execution unit is used to update the software file of the anesthesia depth monitor through the software replacement file, and restart the anesthesia depth monitor after the version update is completed.
[0010] In one embodiment, the software version maintenance system further includes: An update verification unit is used to compare the verification information file and the upgrade information verification file to obtain a verification comparison result; the verification information file is obtained based on the software file of the anesthesia depth monitor restarted after the version update; the upgrade information verification file is read from the mobile storage device; The update information display unit is used to graphically display the upgrade result information according to the verification and comparison result; the upgrade result information includes upgrade success, upgrade failure and / or upgrade completion.
[0011] In one embodiment, the external interface includes a wireless communication interface and / or a wired communication interface, and the wired communication interface includes a USB interface; the mobile storage device includes a USB flash drive, a mobile hard disk, or a mobile hard disk box.
[0012] According to the third aspect, an embodiment provides a computer program product, including a computer program and / or instructions, which, when executed by a processor, implement the software version maintenance system method as described in the first aspect.
[0013] According to a fourth aspect, an embodiment provides a computer-readable storage medium, on which a computer program is stored. The computer program can be executed by a processor to implement the software version maintenance system method as described in the first aspect.
[0014] According to the software version maintenance method of the above embodiment, since the original version information file is obtained based on the software file of the anesthesia depth monitor to be maintained during the original version information verification process, the accuracy of the software replacement file of the verified anesthesia depth monitor pre-version update is guaranteed, making the software update of the anesthesia depth monitor more accurate and reliable. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Figure 1 A flowchart of a software version maintenance method in an embodiment; Figure 2 It is a structural block diagram of a software version maintenance system in one embodiment. DETAILED DESCRIPTION
[0016] The present invention is further described in detail below by specific embodiments in conjunction with the accompanying drawings. Wherein similar elements in different embodiments adopt associated similar element numbers. In the following embodiments, many detailed descriptions are for making the present application better understood. However, those skilled in the art can easily recognize that some features can be omitted in different situations, or can be replaced by other elements, materials, methods. In some cases, some operations related to the present application are not shown or described in the specification, this is to avoid the core part of the present application being overwhelmed by too much description, and for those skilled in the art, it is not necessary to describe these related operations in detail, and they can fully understand the related operations according to the description in the specification and the general technical knowledge in the art.
[0017] In addition, the features, operations or characteristics described in the specification can be combined in any appropriate manner to form various implementations. At the same time, the steps or actions in the method description can also be interchanged or adjusted in a manner that is obvious to those skilled in the art. Therefore, the various sequences in the specification and the drawings are only for the purpose of clearly describing a certain embodiment and are not meant to be a required sequence, unless otherwise specified that a certain sequence must be followed.
[0018] The serial numbers assigned to the components herein, such as "first", "second", etc., are only used to distinguish the objects described and do not have any order or technical meaning. The "connection" and "coupling" mentioned in this application, unless otherwise specified, include direct and indirect connections (couplings).
[0019] Anesthesia depth monitors are considered bedside monitoring devices, and are mostly modular in design. The functional modules of the product can be added or subtracted according to actual needs, and the software files of the anesthesia depth monitor need to be updated and maintained accordingly. Since it is a portable device, it is necessary to be able to perform version maintenance in an offline manner. After the customer obtains the new software replacement file, it is necessary to judge the hardware or software information of multiple anesthesia depth monitors of different models or manufacturers, which increases the difficulty of upgrading the anesthesia depth monitor.
[0020] In an embodiment of the present application, an information verification step is set during offline upgrading, and the original version information file obtained based on the software file of the anesthesia depth monitor to be maintained with the software version is used as the verification basis, thereby ensuring the accuracy of the software replacement file of the pre-version update of the anesthesia depth monitor being verified.
[0021] Embodiment 1: Please refer to Figure 1, is a flowchart of a software version maintenance method in an embodiment, the software version maintenance method is used to perform version maintenance on a software file of an anesthesia depth monitor in an offline manner, including: Step 101, check the upgrade information.
[0022] Compare the original version information file with the version information verification file to obtain a consistency comparison result. The original version information file is obtained based on the software file of the anesthesia depth monitor to be maintained, and the version information verification file is obtained by reading from a mobile storage device connected to an external interface in response to a version update instruction. The consistency comparison result is used to identify the degree of data difference between the original version information file and the version information verification file, and is expressed in percentage.
[0023] In one embodiment, a first information digest algorithm is applied to extract information from a software file of an anesthesia depth monitor to obtain an original version information file. In one embodiment, the first information digest algorithm includes an MD5 information digest algorithm. In one embodiment, a version information verification file is an information extraction file of a software file of an anesthesia depth monitor for testing using the first information digest algorithm to obtain a version information verification file. Since the first information digest algorithm is used to extract information files, as long as the software file of the anesthesia depth monitor for testing is consistent with the software file of the anesthesia depth monitor to be maintained for software version, the similarity between the original version information file obtained for comparison and the version information verification file is 100%.
[0024] Step 102, obtaining a software replacement file.
[0025] The software replacement file corresponding to the consistency comparison result is read from the mobile storage device according to the consistency comparison result, and is stored in the anesthesia depth monitor. In one embodiment, different software replacement files are selected according to different values of the consistency comparison result, and each value corresponds to a software replacement file, so that software replacement files corresponding to different values can be selected according to different consistency comparison results, that is, different software replacement files are placed together, and different software replacement files are selected according to different values of the consistency comparison result.
[0026] Step 103, version update.
[0027] The software file of the anesthesia depth monitor is updated through the software replacement file. In one embodiment, before the software file of the anesthesia depth monitor is updated, the file information in the software replacement file is checked to determine whether the software replacement file meets the requirements of the version upgrade, wherein the file information includes the file type, file name and / or version number information. When the file information is checked correctly, the version update is executed, otherwise the version update is stopped and the update failure information is displayed.
[0028] Step 104, hardware restart.
[0029] After the version update is complete, restart the anesthesia depth monitor.
[0030] Step 105, check the information again.
[0031] The verification information file and the upgrade information verification file are compared to obtain the verification comparison result, wherein the verification information file is obtained based on the software file of the anesthesia depth monitor restarted after the version update, and the upgrade information verification file is read from the mobile storage device.
[0032] In one embodiment, a second information digest algorithm is applied to extract information from a software file of an anesthesia depth monitor that is restarted after a version update to obtain a verification information file. In one embodiment, the second information digest algorithm includes an MD5 information digest algorithm. In one embodiment, a second information digest algorithm is applied to extract information from a software file of an anesthesia depth monitor under test to obtain an upgrade information verification file. As long as the software file of the anesthesia depth monitor used for the test is consistent with the software file of the anesthesia depth monitor that is restarted after a version update, the similarity between the corresponding comparison verification information file and the upgrade information verification file is 100%.
[0033] In one embodiment, the version number after the version update is set to be greater than the version number before the update, otherwise the upgrade file is considered to be wrong, which is used as a judgment condition to prevent the program from being upgraded to the previous version program.
[0034] Step 106, display the result.
[0035] The upgrade result information is graphically displayed according to the verification and comparison result, and the upgrade result information includes upgrade success, upgrade failure and / or upgrade completion.
[0036] Please refer to Figure 2, is a structural block diagram of a software version maintenance system in an embodiment, the software version maintenance system is used to apply the software version maintenance method as described above, and specifically includes an information checking unit 10, a replacement file acquisition unit 20, an update execution unit 30, an update verification unit 40 and an update information display unit 50. The information checking unit 10 is used to compare the original version information file with the version information verification file to obtain a consistency comparison result, wherein the original version information file is obtained based on the software file of the anesthesia depth monitor to be maintained, and the version information verification file is obtained by reading from a mobile storage device connected to an external interface in response to a version update instruction. The consistency comparison result is used to identify the degree of data difference between the original version information file and the version information verification file, and is expressed in percentage. The replacement file acquisition unit 20 is used to read the software replacement file corresponding to the consistency comparison result from the mobile storage device according to the consistency comparison result, and save it in the anesthesia depth monitor. The update execution unit 30 is used to update the software file of the anesthesia depth monitor through the software replacement file, and restart the anesthesia depth monitor after the version update is completed. The update verification unit 40 is used to compare the verification information file and the upgrade information verification file to obtain the verification comparison result, wherein the verification information file is obtained based on the software file of the anesthesia depth monitor that is restarted after the version update, and the upgrade information verification file is read from the mobile storage device. The update information display unit 50 is used to graphically display the upgrade result information based on the verification comparison result, wherein the upgrade result information includes upgrade success, upgrade failure and / or upgrade completion. In one embodiment, the external interface of the anesthesia depth monitor includes a wireless communication interface and / or a wired communication interface, the wired communication interface includes a USB interface, and the wireless communication interface includes a Bluetooth interface and a WIFI interface. In one embodiment, the mobile storage device includes a USB flash drive, a mobile hard disk, or a mobile hard disk box.
[0037] The software version maintenance method disclosed in the embodiment of the present application is used to perform version maintenance on the software files of the anesthesia depth monitor in an offline manner. The software version maintenance method includes: firstly comparing the original version information file with the version information verification file to obtain a consistency comparison result; then reading the software replacement file corresponding to the consistency comparison result from the mobile storage device according to the consistency comparison result; then updating the version of the software file of the anesthesia depth monitor through the software replacement file; and finally restarting the anesthesia depth monitor. Since the original version information file is obtained based on the software file of the anesthesia depth monitor to be maintained by the software version, and the version information verification file is read from the mobile storage device, the verification of the software version information is more accurate and reliable, thereby ensuring the safe use of the anesthesia depth monitor.
[0038] Those skilled in the art will appreciate that all or part of the functions of the various methods in the above-mentioned embodiments can be implemented by hardware or by computer programs. When all or part of the functions in the above-mentioned embodiments are implemented by computer programs, the program can be stored in a computer-readable storage medium, and the storage medium can include: read-only memory, random access memory, disk, optical disk, hard disk, etc., and the program is executed by a computer to implement the above-mentioned functions. For example, the program is stored in the memory of the device, and when the program in the memory is executed by the processor, all or part of the above-mentioned functions can be implemented. In addition, when all or part of the functions in the above-mentioned embodiments are implemented by computer programs, the program can also be stored in a storage medium such as a server, another computer, disk, optical disk, flash disk or mobile hard disk, and can be downloaded or copied and saved in the memory of the local device, or the system of the local device is updated, and when the program in the memory is executed by the processor, all or part of the functions in the above-mentioned embodiments can be implemented.
[0039] The above specific examples are used to illustrate the present invention, which is only used to help understand the present invention and is not intended to limit the present invention. For those skilled in the art, according to the concept of the present invention, some simple deductions, modifications or substitutions can be made.
Claims
1. A software version maintenance method for an anesthesia depth monitor, characterized in that: The method is used to perform version maintenance on the software file of the anesthesia depth monitor in an offline manner, and the software version maintenance method includes: Compare the original version information file with the version information verification file to obtain a consistency comparison result; the original version information file is obtained based on the software file of the anesthesia depth monitor to be maintained, and the version information verification file is obtained by reading from a mobile storage device connected to an external interface in response to a version update instruction; the consistency comparison result is used to identify the degree of data difference between the original version information file and the version information verification file, and is expressed in percentage; Reading a software replacement file corresponding to the consistency comparison result from the mobile storage device according to the consistency comparison result, and storing it in the anesthesia depth monitor; Updating the software file of the anesthesia depth monitor by using the software replacement file; After the version update is completed, the anesthesia depth monitor is restarted.
2. The software version maintenance method according to claim 1, characterized in that: Also includes: Compare the verification information file and the upgrade information verification file to obtain the verification comparison result; The verification information file is obtained based on the software file of the anesthesia depth monitor that is restarted after the version update; The upgrade information verification file is read from the mobile storage device; Graphically displaying the upgrade result information according to the verification and comparison result; The upgrade result information includes upgrade success, upgrade failure and / or upgrade completion.
3. The software version maintenance method according to claim 2, characterized in that: The original version information file is obtained based on the software file of the anesthesia depth monitor to be maintained, including: A first information digest algorithm is applied to extract information from the software file of the anesthesia depth monitor to obtain the original version information file; the first information digest algorithm includes an MD5 information digest algorithm.
4. The software version maintenance method according to claim 2, characterized in that: The verification information file is obtained based on the software file of the anesthesia depth monitor that is restarted after the version update, and includes: A second information digest algorithm is applied to extract information from the software file of the anesthesia depth monitor that is restarted after the version update to obtain the verification information file; the second information digest algorithm includes an MD5 information digest algorithm.
5. The software version maintenance method according to claim 2, characterized in that: The updating of the software file of the anesthesia depth monitor by using the software replacement file includes: Check the file information in the software replacement file to determine that the software replacement file meets the requirements of the version upgrade; the file information includes file type, file name and / or version number information; If the file information is verified to be correct, the version update is executed; otherwise, the version update is stopped and an update failure message is displayed.
6. A software version maintenance system for an anesthesia depth monitor, characterized in that: Used to apply the software version maintenance method according to any one of claims 1 to 5, the software version maintenance system comprises: An information checking unit is used to compare an original version information file with a version information checking file to obtain a consistency comparison result; the original version information file is obtained based on a software file of an anesthesia depth monitor to be maintained, and the version information checking file is obtained by reading from a mobile storage device connected to an external interface in response to a version update instruction; the consistency comparison result is used to identify the degree of data difference between the original version information file and the version information checking file, and is expressed in percentage; A replacement file acquisition unit, configured to read a software replacement file corresponding to the consistency comparison result from the mobile storage device according to the consistency comparison result, and store the replacement file in the anesthesia depth monitor; The update execution unit is used to update the software file of the anesthesia depth monitor through the software replacement file, and restart the anesthesia depth monitor after the version update is completed.
7. The software version maintenance system according to claim 6, characterized in that: Also includes: An update verification unit is used to compare the verification information file with the upgrade information verification file to obtain a verification comparison result; The verification information file is obtained based on the software file of the anesthesia depth monitor that is restarted after the version update; The upgrade information verification file is read from the mobile storage device; An update information display unit, used for graphically displaying the update result information according to the verification and comparison result; The upgrade result information includes upgrade success, upgrade failure and / or upgrade completion.
8. The software version maintenance system according to claim 6, characterized in that: The external interface includes a wireless communication interface and / or a wired communication interface, and the wired communication interface includes a USB interface; the mobile storage device includes a USB flash drive, a mobile hard disk or a mobile hard disk box.
9. A computer program product comprising a computer program and / or instructions, characterized in that: When the computer program and / or instructions are executed by a processor, the software version maintenance system method according to any one of claims 1 to 5 is implemented.
10. A computer-readable storage medium, characterized in that: The medium stores a computer program, which can be executed by a processor to implement the software version maintenance system method according to any one of claims 1 to 5.
