Test bill of lading method for medical devices, computer equipment and storage media

Abstract

The present application relates to a test bill of lading method, computer equipment and storage medium. The method obtains a bill of lading instruction, generates a problem document template according to the bill of lading instruction, and collects test data within a preset time period. Finally, the information related to the problem in the test data is added to the problem document template to generate a problem document, and the problem document is fed back to the document management device. The above method can automatically collect test data and automatically generate a problem document based on the test data according to the problem document template through a bill of lading instruction, realizing a "one-click bill of lading" test bill of lading method, so that any user can easily and quickly feedback the problem as long as they find a problem on the medical device. While improving the bill of lading efficiency, it also expands the scope of testing, which is beneficial to the quality of medical equipment and the improvement of user experience.

Description

Technical Field

[0001] The present application relates to the technical field of medical equipment, and in particular to a test bill method for medical equipment, a computer device, and a storage medium. Background Art

[0002] As society and people increasingly prioritize health, ultrasound examinations are becoming increasingly important in medical diagnosis due to their non-invasive, repeatable, and radiation-free nature. Ultrasound can examine a wide range of conditions, including the abdomen, superficial structures, heart, blood vessels, and fetuses. The corresponding ultrasound software is large in scale and complex in functionality. Comprehensive and efficient testing and feedback on all software functions on ultrasound equipment significantly impacts its performance.

[0003] Existing test billing methods mainly include several methods. The first is that the tester operates the ultrasound equipment. After discovering a problem, he will manually collect some information, create a new document in the test document management system, fill in various information, and then feedback the completed problem document to the developer or maintenance personnel to solve the problem on the ultrasound equipment; the second method is semi-automated test billing, that is, by running an automated test script on the ultrasound equipment, when a problem occurs, the tester creates a new document in the test document management system, fills in various information, and then feedback the completed problem document to the developer or maintenance personnel to solve the problem on the ultrasound equipment; the third method is that the clinician uses the ultrasound equipment. After discovering the problem, the feedback is given to the on-site tracking technician, the technician records it and feeds it back to the tester, who then manually fills in the problem document and feeds it back to the developer or maintenance personnel to solve the problem on the ultrasound equipment; the fourth method is that in the actual use scenario of a hospital or physical examination center, if the doctor finds a problem, he will feedback the problem to the manufacturer's personnel during the communication process when the ultrasound manufacturer visits afterwards, and the manufacturer's personnel will improve and enhance the quality of the ultrasound product.

[0004] However, the above-mentioned method for testing bills of lading has the problem of low testing efficiency. Summary of the Invention

[0005] Based on this, it is necessary to provide a test bill of lading method, computer equipment and storage medium for medical equipment that can improve bill of lading efficiency in response to the above technical problems.

[0006] In a first aspect, a test bill of lading method for medical equipment comprises:

[0007] Obtain bill of lading instructions;

[0008] generating a problem document template according to the bill of lading instruction;

[0009] Collect test data within a preset time period;

[0010] The problem-related information in the test data is added to the problem document template to generate a problem document, and is fed back to the document management device to instruct the document management device to process the problem in the problem document and return the processing result.

[0011] In one embodiment, the method further comprises:

[0012] Receive the processing result returned by the document management device after processing the problem in the problem document.

[0013] In one embodiment, if the bill of lading instruction is a one-key triggered instruction, the method further includes:

[0014] Collecting voice annotation data input by the user;

[0015] The step of adding the problem-related information in the test data to a problem ticket template to generate a problem ticket includes:

[0016] locating information related to the question in the test data using the voice annotation data;

[0017] Adding information related to the problem to the problem ticket template generates a problem ticket.

[0018] In one embodiment, if the bill of lading instruction is an instruction generated after the medical device undergoes various functional tests, the method further includes:

[0019] When receiving the start test instruction input by the user, run the test script to test each software function;

[0020] If the test fails, the bill of lading instruction is generated;

[0021] The step of adding the problem-related information in the test data to a problem ticket template to generate a problem ticket includes:

[0022] Determining information related to the problem in the test data according to test information; the test information is information generated when running the test script to test each software function;

[0023] Adding information related to the problem to the problem ticket template generates a problem ticket.

[0024] In one embodiment, the test data includes at least one of status data, log data, parameter data, image data, and test result data.

[0025] In one embodiment, the problem document includes a problem number, a problem title, a problem description, a module to which the problem belongs, a test environment, operation steps, expected results, actual results, a bill-issuing person, and attachment information.

[0026] In a second aspect, a method for processing medical device documents is provided, the method comprising:

[0027] Receiving a problem document sent by the medical device; the problem document is a document generated by the medical device adding information related to the problem in the collected test data to a problem document template generated according to the bill of lading instruction;

[0028] Processing the problem in the problem document and obtaining a processing result;

[0029] The processing result is fed back to the medical device.

[0030] In one embodiment, processing the problem in the problem document to obtain a processing result includes:

[0031] Analyze the problem types in the problem documents;

[0032] If the problem type is a general problem, generating a software update package for the software corresponding to the problem;

[0033] If the problem type is not a general problem, a software patch package for the software corresponding to the problem is generated.

[0034] In a third aspect, a test bill device for medical equipment comprises:

[0035] Acquisition module, used to obtain bill of lading instructions;

[0036] A first generating module, configured to generate a problem document template according to the bill of lading instruction;

[0037] A collection module, used to collect test data within a preset time period;

[0038] The second generating module is used to add the information related to the problem in the test data to the problem document template to generate a problem document, and feed it back to the document management device.

[0039] In a fourth aspect, a document processing device for medical equipment is provided, the device comprising:

[0040] a receiving module for receiving a problem document sent by a medical device; the problem document is a document generated by the medical device adding information related to the problem in the collected test data to a problem document template generated according to the bill of lading instruction;

[0041] A processing module, used to process the problem in the problem document and obtain a processing result;

[0042] A feedback module is used to feed back the processing result to the medical device.

[0043] In a fifth aspect, a computer device includes a memory and a processor, wherein the memory stores a computer program, and the processor implements the method described in the first aspect when executing the computer program.

[0044] In a sixth aspect, a computer-readable storage medium stores a computer program, which implements the method described in the first aspect when executed by a processor.

[0045] The above-mentioned medical device test billing method, computer device, and storage medium obtain billing instructions, generate a problem document template based on the billing instructions, collect test data within a preset time period, and finally add problem-related information in the test data to the problem document template to generate a problem document, which is then fed back to the document management device. The above-mentioned method can automatically collect test data and automatically generate a problem document based on the test data according to the problem document template with just one billing instruction, realizing a "one-click billing" test billing method. Any user who discovers a problem on the medical device can conveniently and quickly report the problem. While improving billing efficiency, it also expands the scope of testing, which is beneficial to improving the quality of medical devices and user experience. Moreover, the above-mentioned method also extends the testing cycle. Medical devices, as terminals, can collect first-hand problems during use at any time and any place, which can continuously improve the quality of medical devices and extend the service life of medical devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 A diagram of an application environment of a test bill of lading method for medical equipment in one embodiment;

[0047] Figure 2 A schematic flow chart of a method for preparing a test bill of lading for medical equipment according to an embodiment;

[0048] Figure 2A A schematic diagram of a problem document template in one embodiment;

[0049] Figure 2B A schematic diagram of a problem document in one embodiment;

[0050] Figure 3 A schematic flow chart of a method for preparing a test bill of lading for medical equipment according to an embodiment;

[0051] Figure 4A schematic flow chart of a method for preparing a test bill of lading for medical equipment according to an embodiment;

[0052] Figure 5 A schematic flow chart of a method for preparing a test bill of lading for medical equipment according to an embodiment;

[0053] Figure 6 for Figure 5 A flow chart of an implementation method of S104 in the embodiment;

[0054] Figure 7 1. A flowchart of a method for processing medical device documents in one embodiment;

[0055] Figure 8 for Figure 7 A flowchart of an implementation method of S202 in the embodiment;

[0056] Figure 9 A schematic flow chart of a method for preparing a test bill of lading for medical equipment according to an embodiment;

[0057] Figure 10 A schematic diagram of a bill of lading test system in one embodiment;

[0058] Figure 11 The figure is a schematic diagram of the ultrasonic software testing process of one-click bill of lading in one embodiment.

[0059] Figure 12 A structural block diagram of a test bill of lading device for medical equipment in one embodiment;

[0060] Figure 13 A structural block diagram of a test billing device for medical equipment in one embodiment

[0061] Figure 14 A structural block diagram of a test bill of lading device for medical equipment in one embodiment;

[0062] Figure 15 A structural block diagram of a test bill of lading device for medical equipment in one embodiment;

[0063] Figure 16 A structural block diagram of a document processing device for medical equipment in one embodiment;

[0064] Figure 17 A structural block diagram of a document processing device for medical equipment in one embodiment;

[0065] Figure 18 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0066] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0067] The test bill of lading method for medical equipment provided in this application can be applied to Figure 1 In the application environment shown, medical device 102 communicates with document management device 104 via a network. Medical device 102 generates a problem document based on the bill of lading instruction and feeds the problem document back to document management device 104. Document management device 104 processes the problem document and feeds back the processing results to medical device 102. Medical device 102 may be, but is not limited to, various personal computers, laptops, smartphones, tablet computers, and portable wearable devices. Document management device 104 may be a server, and may be implemented as a standalone server or a server cluster consisting of multiple servers.

[0068] Those skilled in the art will understand that Figure 1 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the application environment to which the solution of the present application is applied. The specific application environment may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0069] Existing methods for testing bills of lading generally include:

[0070] 1) Manual test receipt: When a tester operates the ultrasonic equipment and finds a problem, he or she will create a new document in the test document management system and fill in various information, including a description of the problem and the test environment. He or she will also manually collect some logs and image data for reference. The completed test document is the problem document.

[0071] 2) Automated test bill of lading: By running the automated test script on the ultrasonic equipment, when a problem occurs, the tester manually collects the operation log of the automated test and uses the above method (1) to carry out bill of lading to obtain the problem bill.

[0072] 3) Internal and external clinical trial bill of lading: When a clinician uses ultrasound equipment and finds a problem, he or she will feedback it to the on-site tracking technician. The technician will record it and feedback it to the tester. The tester will use the above method (1) to make a bill of lading and obtain the problem document.

[0073] 4) Ultrasound Physician Inquiry: In actual use scenarios at hospitals or physical examination centers, if a doctor discovers a problem, there is no appropriate way to report it to the ultrasound manufacturer. While the issue may be discussed during a visit with the manufacturer, it may be incomplete or omitted. These issues are often crucial to improving ultrasound product quality and enhancing user experience.

[0074] Existing ultrasound equipment test billing solutions suffer from the following problems: the billing process is cumbersome, requiring extensive data collection, prone to omissions or inaccuracies in manual collection, requiring extensive manual intervention, prone to omissions of ultrasound physicians' specialized test problem sheets, low billing efficiency, and individual variations in the quality of problem sheets. To address these issues, the present application provides a method for automatically billing problem sheets when problems are discovered during the use of medical equipment. This method can automatically bill problem sheets without the intervention of physicians or testers, resulting in extremely high billing efficiency. The following examples specifically illustrate the medical equipment test billing method described in this application.

[0075] In one embodiment, Figure 2 As shown, a test bill method for medical equipment is provided, which is applied to Figure 1 Taking the medical device in the example as an example, the following steps are included:

[0076] S101, obtain bill of lading instructions.

[0077] The bill of lading instruction is used to instruct the medical device to automatically obtain test data and generate a problem document based on the test data. In this embodiment, when a user discovers a problem while using the medical device, they can trigger the bill of lading instruction by pressing the "one-click bill of lading" function button. The medical device will generate the bill of lading instruction upon receiving the user's key operation. Optionally, the user can also activate the automatic testing function of the medical device. After the test, the medical device will automatically trigger and generate the bill of lading instruction based on the test results. It should be noted that the above-mentioned method of triggering the bill of lading instruction by function button is not limited, and the bill of lading instruction can also be triggered by voice input, etc.

[0078] S102, generating a problem document template according to the bill of lading instruction.

[0079] The problem document template is a blank template, which includes several header information, for example, Figure 2A As shown, the problem document template specifically includes header information such as problem number, problem title, problem description, problem module, test environment, operation steps, expected results, actual results, bill of lading personnel and attachment information.

[0080] In this embodiment, when the medical device obtains the bill of lading instruction, it can further obtain the problem document template from the storage template database, or automatically generate the problem document template based on the header information, so that the problem document template can be used to generate a problem document later.

[0081] S103: Collect test data within a preset time period.

[0082] The test data includes at least one of status data, log data, parameter data, image data, and test result data. Status data represents all status information of the current medical device, including the collectible hardware operating status, software operating status, network status, current mode of the medical device, etc. Log data includes user operation logs, system kernel logs, software logs, monitoring logs, etc. Parameter data includes all front-end and back-end parameter information of the current medical device image mode. Image data includes intermediate image data of the medical device at each stage of use, the final image data presented to the user, and a cross-sectional view of the main interface UE. Test result data includes measurement and calculation results of the medical device, as well as annotations and body marks when in the measurement or annotation state. The preset time period can be determined in advance by the medical device based on the bill of lading requirements. For example, the preset time period can be different time periods such as 5 minutes, 10 minutes, and 20 minutes before the user's bill of lading.

[0083] In this embodiment, after the medical device generates a problem document template, since the problem document template is a blank template, relevant information needs to be filled in. Therefore, the medical device can collect the test data required by the problem document template within a preset time period, such as collecting some log information (kernel, operation, software, etc.), parameters (probe, preset, front and back ends, etc.), pictures (screenshots, process diagrams, display diagrams, etc.), videos (videos in the playback area on the medical device, etc.), status (probe, mode, etc.), measurements and other results.

[0084] S104: Add the problem-related information in the test data to the problem document template to generate a problem document, and feed it back to the document management device.

[0085] The problem document includes the content corresponding to the header information, such as the problem number, problem title, problem description, module to which the problem belongs, test environment, operation steps, expected results, actual results, bill of lading personnel and attachment information.

[0086] Since the test data includes relevant information when the medical device is operating normally, and also includes relevant information when a problem occurs with the medical device, when the medical device collects test data within a preset time period, it can further filter out relevant information when a problem occurs with the medical device, that is, problem-related information, and then add the problem-related information to the corresponding area in the problem document template. The problem document template after adding the information is the problem document finally generated by the medical device. The problem document can reflect some problems that occur during the use of the medical device. Therefore, after the medical device generates a problem document, it can feed the problem document back to the document management device so that the administrator of the document management device can view the problem document and then handle the problem in the problem document, or the administrator can feed the problem in the problem document back to the maintenance personnel for processing; optionally, the document management device can also automatically handle the problem in the problem document. It should be noted that the information related to the problem corresponds to the corresponding header in the problem document template, for example, Figure 2B As shown, the information related to the problem includes the problem number, problem title, problem description, module to which the problem belongs, test environment, operation steps, expected results, actual results, bill of lading personnel and the content corresponding to the header of the attachment information (indicated by XXXX in the figure).

[0087] The above-mentioned test billing method for medical devices obtains billing instructions, generates a problem document template based on the billing instructions, collects test data within a preset time period, and finally adds problem-related information in the test data to the problem document template to generate a problem document, which is then fed back to the document management device. The above-mentioned method can automatically collect test data and automatically generate problem documents based on the test data according to the problem document template with just one billing instruction, realizing a "one-click billing" test billing method. This allows any user to easily and quickly report problems as soon as they discover a problem on the medical device. While improving billing efficiency, it also expands the scope of testing, which is beneficial to improving the quality of medical devices and user experience. Moreover, the above-mentioned method also extends the testing cycle. Medical devices, as terminals, can collect first-hand problems during use at any time and any place, which can continuously improve the quality of medical devices and increase the service life of medical devices.

[0088] In actual applications, after the medical device passes the problem document to the document management device, the document management device can also automatically process the problem in the problem document and then return the processing result to the medical device. Figure 2 Based on the method described in the embodiment, the present application also provides a test bill method for medical equipment, such as Figure 3 As shown, Figure 2 The method of the embodiment further includes:

[0089] S105, receiving the processing result returned by the document management device after processing the problem in the problem document.

[0090] The processing result includes the repair data or repair method of the problem in the problem document.

[0091] In this embodiment, when the document management device receives a problem document fed back by a medical device, it can analyze the problem type in the problem document and handle the corresponding problem in a corresponding manner according to the problem type to obtain a processing result. The processing result is then returned to the medical device via network push or other means. The medical device can then receive the processing result returned by the document management device. The medical device can then remind the user of the relevant problem, or automatically repair the problem based on the processing result, or instruct the user to perform repair operations on the medical device according to the instructions of the processing result. The above method can realize the automatic repair of problems in the use process of medical equipment without waiting for maintenance personnel to provide on-site service, thereby improving the efficiency of repairing problems in problem documents, saving related human resources, and correspondingly improving the versatility of medical equipment.

[0092] Optionally, in some application scenarios, the above-mentioned bill of lading instruction may be an instruction triggered by one button. In some application scenarios, the above-mentioned bill of lading instruction may be an instruction generated by the medical device after performing various functional tests. This application provides a test bill of lading method for medical devices in these two application scenarios, which are described in the following embodiments respectively:

[0093] The first application scenario is when the bill of lading instruction is a one-click trigger instruction, such as Figure 4 As shown, Figure 2 The test bill of lading method described in the embodiment also includes:

[0094] S106: Collect the voice annotation data input by the user.

[0095] The voice annotation data is used to locate information related to the question in the test data. The voice annotation data includes the voice description of the bill of lading input by the user on the medical device. The voice description content may include keywords related to the question in the test data.

[0096] In this embodiment, when a problem occurs on the medical device, the medical device can prompt the user to give a brief voice description of the problem. The user can input voice annotation data on the medical device through voice input. The medical device can automatically convert the voice annotation data into text to assist in explaining the problem that occurred on the medical device, helping the medical device to quickly locate information related to the problem in the test data later.

[0097] Correspondingly, the above-mentioned S104 "adding information related to the problem in the test data to the problem document template to generate a problem document" includes the following steps:

[0098] S1041, using the voice annotation data to locate information related to the question in the test data.

[0099] When the medical device collects voice annotation data input by the user, it can extract keywords describing the problem from the voice annotation data, and then locate information related to the problem from the test data of the medical device collected previously based on these keywords. During specific positioning, the test data can be marked to a certain extent according to the keywords, so that the medical device can determine information related to the problem based on the marked test data.

[0100] S1042: Add information related to the problem to the problem document template to generate a problem document.

[0101] This step is consistent with the aforementioned step S104. For detailed instructions, please refer to the aforementioned content and will not be repeated here.

[0102] The test bill of lading method in the above application scenario can quickly locate information related to the problem in the test data through voice annotation data, thereby improving the efficiency of medical equipment bill of lading.

[0103] The second application scenario is when the bill of lading instructions are automatically generated after the medical device undergoes various functional tests, such as Figure 5 As shown, Figure 2 The test bill of lading method described in the embodiment also includes:

[0104] S107: When receiving the test start instruction input by the user, the test script is run to perform various software function tests.

[0105] The start test instruction is used to instruct the medical device to perform automatic testing.

[0106] In this embodiment, the tester can pre-edit a test script on the medical device, and the medical device can also pre-access the test script based on the relevant instructions of the medical device. When the medical device needs to be tested, the user can input a start test command on the medical device through any means. Upon receiving the start test command, the medical device can automatically run the test script to test various software functions on the medical device and obtain a test result. If the test result is successful, it means that there is no problem with the medical device and no billing operation for the problem document is required. If the test result fails, it means that there is a problem with the medical device and it needs to be submitted to the problem maintenance personnel or the problem needs to be resolved.

[0107] S108: If the test fails, generate a bill of lading instruction.

[0108] This embodiment relates to the case where the test result is a test failure. In this case, the medical device can generate a bill of lading instruction and then Figure 2 Example or Figure 3 The method described in the embodiment generates a problem ticket or handles a problem in a problem ticket.

[0109] Correspondingly, the above S104 "adds the information related to the problem in the test data to the problem document template to generate a problem document", such as Figure 6 As shown, the steps include:

[0110] S1043: Determine information related to the problem in the test data according to the test information.

[0111] The test information is the information generated when running the test script to test various software functions.

[0112] In this embodiment, after the medical device automatically performs a test based on the aforementioned step S107, it can obtain the test results and the test information of each test step in the test process. When the test result is a test failure, the medical device can also extract information related to the problem from the test information of each test step.

[0113] S1044, adding information related to the problem to the problem document template to generate a problem document.

[0114] This step is consistent with the aforementioned step S104. For detailed instructions, please refer to the aforementioned content and will not be repeated here.

[0115] The test billing method in this application scenario can quickly locate information related to the problem in the test data using test information during the test process, thereby improving the efficiency of medical device billing. Moreover, the above method realizes the full automation of medical device testing and billing operations, improving the intelligence of medical devices.

[0116] above Figure 2-Figure 6 The embodiment is a test bill method for medical equipment on the medical equipment side. This application also provides a document processing method on the document management device side. Figure 7-Figure 8 The embodiment will specifically illustrate the document processing method on the document management device side.

[0117] Figure 7 The embodiment is a method for processing medical device documents, such as Figure 7 As shown, this method is applied to Figure 1 Taking the document management device in [1] as an example, the method includes:

[0118] S201, receiving a problem document sent by a medical device.

[0119] The problem document is a document generated by adding problem-related information in the collected test data to the problem document template.

[0120] In this embodiment, the medical device can be based on the above Figure 2-Figure 6 The method described in any embodiment of the embodiment generates a problem document, and sends the problem document to the document management device through the network or other means, and the document management device can receive the problem document. Figure 2-Figure 6 The methods described in the embodiments are described above and will not be repeated here.

[0121] S202: Process the problem in the problem document and obtain the processing result.

[0122] When the document management device receives a problem document, it can extract the issue that needs to be addressed from the document and then automatically handle the issue using the appropriate method to obtain the result. Alternatively, it can feed the issue back to the relevant maintenance personnel, instructing them to handle the issue and obtaining the result of their handling. It should be noted that the relevant maintenance personnel can handle the issue offline and then upload the result to the document management device; alternatively, the relevant maintenance personnel can handle the issue directly on the document management device and obtain the result.

[0123] S203: Feedback the processing result to the medical device.

[0124] Once the document management device receives the processing results, it can send them to the medical device via a network or other means, prompting the medical device to automatically repair any issues based on the processing results, or instructing the user of the medical device to perform repair operations on the medical device according to the processing results. This step corresponds to S105 above, and details can be found in the previous description and will not be repeated here.

[0125] In the aforementioned test billing method for medical devices, the document management device receives a problem document from the medical device, processes the problem document, obtains a processing result, and then feeds the processing result back to the medical device. This method enables the document management device to automatically feed back the problem processing result to the medical device after the medical device submits the bill to the document management device. This fully automates the entire process from problem occurrence, problem document generation, to problem resolution, significantly improving the efficiency of medical device billing and document processing.

[0126] Furthermore, the above S202 "processes the problem in the problem document and obtains the processing result", such as Figure 8 Shown, including:

[0127] S2021, analyze the problem type in the problem document. If the problem type is a general problem, execute step S2022; if the problem type is not a general problem, execute step S2023.

[0128] In actual applications, problems that occur on medical devices may be universal problems or non-universal problems. Universal problems refer to problems that are likely to occur on various medical devices, and may be problems that occur on most medical devices of this type due to device defects; non-universal problems refer to problems that occur on a certain medical device, that is, problems that occur with a low probability, and may be problems that occur on individual medical devices due to usage problems.

[0129] In this embodiment, when the document management device obtains a problem document sent by a medical device, it can further analyze the problem type in the problem document and determine whether the problem type is a general problem or a non-general problem, and then select different processing methods to handle the problem according to different problem types.

[0130] S2022: Generate a software update package for the software corresponding to the problem.

[0131] The problem-corresponding software is the software corresponding to the problem that occurs on the medical device. For example, if there is a problem with the image display software on the ultrasound device, the image display software is the software corresponding to the problem.

[0132] This embodiment involves an application scenario in which the problem type is a universal problem. Since the problem type is a universal problem, this type of problem may be a problem that occurs in most medical devices. It may be that the software on the medical device that has the problem is not the latest version and needs to be updated, or there is a problem with a plug-in and needs to be updated. In this case, the document management device obtains the software update package of the software corresponding to the problem from the relevant software database based on the problem in the problem document, and returns the software update package to the medical device as a processing result. After receiving the software update package, the medical device can automatically install the software update package to perform the corresponding software update, thereby realizing automatic problem repair of the medical device.

[0133] S2023: Generate a software patch package for the software corresponding to the problem.

[0134] This embodiment involves an application scenario where the problem type is a non-universal problem. Since the problem type is a non-universal problem, this type of problem may be a problem that occurs in individual medical devices. It may be that the software corresponding to the problem on the medical device has a problem and needs to be repaired. In this case, the document management device obtains the software patch package of the software corresponding to the problem from the relevant software database based on the problem in the problem document, and returns the software patch package to the medical device as a processing result. After receiving the software patch package, the medical device can automatically install the software patch package to perform corresponding software repairs, thereby realizing automatic problem repair of the medical device.

[0135] In summary of all the above embodiments, the present application also provides a test bill method for medical equipment, such as Figure 9 As shown, the method includes:

[0136] S301, medical equipment obtains bill of lading instructions.

[0137] S302: The medical device collects voice annotation data input by the user.

[0138] S303, when the medical device receives the start test instruction input by the user, it runs the test script to test each software function. If the test fails, a bill of lading instruction is generated.

[0139] S304, the medical device generates a problem document template according to the bill of lading instruction.

[0140] S305, the medical device collects test data within a preset time period.

[0141] S306 , the medical device uses the voice annotation data to locate information related to the problem in the test data.

[0142] S307: Determine information related to the problem in the test data according to the test information.

[0143] S308, the medical device adds information related to the problem to the problem document template to generate a problem document, and feeds it back to the document management device.

[0144] S309: The document management device receives the problem document sent by the medical device.

[0145] S310, analyzing the problem type in the problem document. If the problem type is a general problem, execute step S311; if the problem type is not a general problem, execute step S312.

[0146] S311: Generate a software update package for the software corresponding to the problem, and return the software update package to the medical device.

[0147] S312: Generate a software patch package for the software corresponding to the problem, and return the new software patch package to the medical device.

[0148] Each of the above steps has been explained above. Please refer to the above explanation for details and will not be repeated here. It should be noted that when the problem type is a universal problem, since this type of problem is a problem that exists in most medical devices, when the document management device obtains a software update package that solves the universal problem, it can send the software update package to the medical device that raised the problem, and can also send the software update package to other medical devices of the same type, so that other medical devices can update or upgrade their own related software versions according to the software update package. When the problem type is a non-universal problem, since this type of problem is a problem that exists in individual medical devices, when the document management device obtains a software patch package that solves the non-universal problem, it will only send the software patch package to the medical device that raised the problem.

[0149] In one embodiment, a test bill of lading system is also provided, such as Figure 10 As shown, the test bill of lading system includes: an ultrasonic device and a document management device, which are connected via a network. The ultrasonic device includes a one-key bill of lading module, a test data acquisition module, a voice annotation module, and a data integration and transmission module; the document management device includes a document data receiving module, a document data processing module, and a document data feedback module.

[0150] Among them, the one-click bill of lading module is used to respond to the user's bill of lading requirements and generate a standard problem document template based on the bill of lading instructions entered by the user; the test data acquisition module is used to collect test data of the ultrasound equipment; the voice annotation module is used to remind the user to give a voice description of the problems that occurred on the ultrasound equipment, and to collect voice annotation data, as well as extract keywords from it, and mark the test data to a certain extent according to the keywords to assist the ultrasound equipment in locating problems in the test data; the data integration and transmission module is used to generate problem documents based on the voice annotation data and test data, and is responsible for sending the problem documents to the document management device, and is responsible for receiving the processing results and message prompts sent by the test management system.

[0151] The document data receiving module is used to receive problem documents of the ultrasonic equipment; the document data processing module is used to process the problems in the problem documents and obtain the processing results; the document data feedback module is used to feed back the processing results to the ultrasonic equipment.

[0152] Accordingly, the present application also provides a method for applying the above Figure 10 The ultrasonic software testing process of a one-key bill of lading system shown in the figure is as follows: Figure 11 As shown, the process includes:

[0153] S401: When the ultrasound equipment is in use, the user finds a problem and presses the "one-click order" button.

[0154] S402, the one-click bill of lading module automatically generates a problem document template.

[0155] S403: The test data collection module starts collecting test data.

[0156] S404: The voice annotation module collects the user's voice annotation content.

[0157] S405, the data integration and transmission module is used to integrate the test data and the voice annotation content into the problem document, and transmit the problem document to the document management device.

[0158] S406, the document data receiving module receives the problem document from the ultrasonic equipment and enters the problem document.

[0159] S407, notify the data processing module to process the problem document.

[0160] S408: The document processing module sends the problem document to the testers and developers.

[0161] S409: Process the problem in the problem document and obtain the processing result.

[0162] S410, the document data feedback module notifies the ultrasonic device of the processing result.

[0163] S411: After receiving the feedback processing result, the data integration and transmission module issues a notification on the ultrasound device.

[0164] The above steps have been explained above. Please refer to the above instructions for details and will not be repeated here.

[0165] It should be understood that although Figure 2-11 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. In addition, Figure 2-11 At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The order of execution of these steps or stages is not necessarily one by one, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

[0166] In one embodiment, Figure 12 As shown, a test bill device for medical equipment is provided, comprising:

[0167] An acquisition module 11 is used to acquire bill of lading instructions;

[0168] A first generating module 12, configured to generate a problem document template according to the bill of lading instruction;

[0169] The acquisition module 13 is used to collect test data within a preset time period;

[0170] The second generating module 14 is configured to add the problem-related information in the test data to a problem document template to generate a problem document, and feed the result back to the document management device.

[0171] In one embodiment, Figure 13 As shown, the above device also includes:

[0172] The receiving module 15 is used to receive the processing result returned by the document management device after processing the problem in the problem document.

[0173] In one embodiment, Figure 14 As shown, the above device also includes:

[0174] The voice collection module 16 is used to collect the voice annotation data input by the user;

[0175] Correspondingly, the second generating module 14 includes:

[0176] a first locating unit 141, configured to locate information related to the question in the test data using the voice annotation data;

[0177] The first adding unit 142 is configured to add information related to the problem to the problem document template to generate a problem document.

[0178] In one embodiment, Figure 15 As shown, the above device also includes:

[0179] A testing module 17 is configured to receive a processing result returned by the document management device after processing the problem in the problem document;

[0180] The second generating module 18 is used to generate the bill of lading instruction when the test fails.

[0181] Correspondingly, the second generating module 14 includes:

[0182] A determining unit 143 is configured to determine information related to the problem in the test data based on test information; the test information is information generated when the test script is run to test various software functions;

[0183] The second adding unit 144 is configured to add information related to the problem to the problem document template to generate a problem document.

[0184] In one embodiment, the test data includes at least one of status data, log data, parameter data, image data, and test result data.

[0185] In one embodiment, the problem document includes the problem number, problem title, problem description, the module to which the problem belongs, the test environment, the operation steps, the expected result, the actual result, the person who filed the bill and the attachment information.

[0186] The specific definitions of the medical device test ordering device can be found in the definitions of the medical device test ordering method described above and will not be further elaborated here. Each module within the aforementioned medical device test ordering device can be implemented in whole or in part via software, hardware, or a combination thereof. Each of these modules can be embedded in or independent of a processor within a computer device in hardware form, or stored in a computer device memory in software form, allowing the processor to call and execute the corresponding operations of each module.

[0187] In one embodiment, Figure 16 As shown, a document processing device for medical equipment is provided, comprising:

[0188] A receiving module 21 is configured to receive a problem document sent by a medical device; the problem document is generated by the medical device adding information related to the problem in the collected test data to a problem document template generated according to the bill of lading instruction;

[0189] A processing module 22 is used to process the problem in the problem document and obtain a processing result;

[0190] The feedback module 23 is configured to feed back the processing result to the medical device.

[0191] In one embodiment, the processing module 22, such as Figure 17 Shown, including:

[0192] An analyzing unit 221 is used to analyze the problem type in the problem document;

[0193] A first generating unit 222 is configured to generate a software update package for software corresponding to the problem if the problem type is a general problem;

[0194] The second generating unit 223 is configured to generate a software patch package for software corresponding to the problem if the problem type is not a general problem.

[0195] The specific definition of the medical device's document processing device can be found in the definition of the medical device's document processing method above and will not be repeated here. Each module in the aforementioned medical device's document processing device can be implemented in whole or in part through software, hardware, or a combination thereof. Each of these modules can be embedded in or independent of a processor in a computer device in hardware form, or stored in a computer device's memory in software form, so that the processor can call and execute the corresponding operations of each module.

[0196] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 18 As shown. The computer device includes a processor, a memory and a network interface connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store test data. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a test billing method for a medical device is implemented.

[0197] Those skilled in the art will understand that Figure 18 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0198] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0199] Obtain bill of lading instructions;

[0200] generating a problem document template according to the bill of lading instruction;

[0201] Collect test data within a preset time period;

[0202] The information related to the problem in the test data is added to the problem document template to generate a problem document, and the problem document is fed back to the document management device.

[0203] The computer device provided in the above embodiment has an implementation principle and technical effects similar to those of the above method embodiment, and will not be described in detail here.

[0204] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0205] Receiving a problem document sent by the medical device; the problem document is a document generated by the medical device adding information related to the problem in the collected test data to a problem document template generated according to the bill of lading instruction;

[0206] Processing the problem in the problem document and obtaining a processing result;

[0207] The processing result is fed back to the medical device.

[0208] The computer device provided in the above embodiment has an implementation principle and technical effects similar to those of the above method embodiment, and will not be described in detail here.

[0209] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0210] Obtain bill of lading instructions;

[0211] generating a problem document template according to the bill of lading instruction;

[0212] Collect test data within a preset time period;

[0213] The information related to the problem in the test data is added to the problem document template to generate a problem document, and the problem document is fed back to the document management device.

[0214] The above embodiment provides a computer-readable storage medium, whose implementation principle and technical effects are similar to those of the above method embodiment, and will not be repeated here.

[0215] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0216] Receiving a problem document sent by the medical device; the problem document is a document generated by the medical device adding information related to the problem in the collected test data to a problem document template generated according to the bill of lading instruction;

[0217] Processing the problem in the problem document and obtaining a processing result;

[0218] The processing result is fed back to the medical device.

[0219] The above embodiment provides a computer-readable storage medium, whose implementation principle and technical effects are similar to those of the above method embodiment, and will not be repeated here.

[0220] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0221] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0222] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. A test bill of lading method for medical equipment, characterized in that: The method comprises: The medical device generates a bill of lading instruction when receiving a key operation from the user; or, after performing various function tests, the medical device triggers and generates the bill of lading instruction according to the test results; Obtaining a problem document template from a stored template database according to the bill of lading instruction, or generating a problem document template according to the bill of lading instruction and header information; Collect test data within a preset time period according to the bill of lading instructions; Based on the voice annotation data and / or test information, information related to the problem when the medical device has a problem is filtered out from the test data, the information related to the problem in the test data is added to the problem document template to generate a problem document, and the problem document is fed back to the document management device; the problem document is used to indicate problems that occur during the use of the medical device.

2. The method according to claim 1, characterized in that The method further comprises: Receive the processing result returned by the document management device after processing the problem in the problem document.

3. The method according to claim 1 or 2, characterized in that If the bill of lading instruction is a one-key triggered instruction, the method further includes: Collecting voice annotation data input by the user; The step of adding the problem-related information in the test data to a problem ticket template to generate a problem ticket includes: locating information related to the question in the test data using the voice annotation data; Adding information related to the problem to the problem ticket template generates a problem ticket.

4. The method according to claim 1 or 2, characterized in that If the bill of lading instruction is an instruction generated after the medical device undergoes various functional tests, the method further includes: When receiving the start test instruction input by the user, run the test script to test each software function; If the test fails, the bill of lading instruction is generated.

5. The method according to claim 4, characterized in that The step of adding the problem-related information in the test data to a problem ticket template to generate a problem ticket includes: Determining information related to the problem in the test data according to test information; the test information is information generated when running the test script to test each software function; Adding information related to the problem to the problem ticket template generates a problem ticket.

6. The method according to claim 1 or 2, characterized in that The test data includes at least one of status data, log data, parameter data, image data, and test result data.

7. A method for processing medical equipment documents, characterized in that: The method comprises: Receive a problem document sent by a medical device; the problem document is a document generated by the medical device based on voice annotation data and / or test information, filtering out information related to the problem when the medical device has a problem from test data collected according to a bill of lading instruction, and adding the problem-related information in the test data to a problem document template generated according to the bill of lading instruction; the problem document template is obtained from a storage template database according to the bill of lading instruction, or generated according to the bill of lading instruction and header information; the problem document is used to indicate a problem that occurs during use of the medical device; the bill of lading instruction is generated by the medical device when receiving a user's key operation, or is triggered and generated by the medical device according to the test results after performing various functional tests; Processing the problem in the problem document and obtaining a processing result; The processing result is fed back to the medical device.

8. The method according to claim 7, characterized in that The processing of the problem in the problem document to obtain a processing result includes: Analyze the problem types in the problem documents; If the problem type is a general problem, generating a software update package for the software corresponding to the problem; If the problem type is not a general problem, a software patch package for the software corresponding to the problem is generated.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 8 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images