CN116483721A

CN116483721A - Medical equipment software testing method and device, computer equipment and storage medium

Info

Publication number: CN116483721A
Application number: CN202310462238.5A
Authority: CN
Inventors: 孙永泉
Original assignee: Shenzhen United Imaging Research Institute of Innovative Medical Equipment
Current assignee: Shenzhen United Imaging Research Institute of Innovative Medical Equipment
Priority date: 2023-04-20
Filing date: 2023-04-20
Publication date: 2023-07-25

Abstract

The application relates to a method, a device, a computer device and a storage medium for testing medical device software. The method comprises the following steps: acquiring a business process associated with virtual medical equipment matched with the medical equipment; the business process is matched with business operation logic corresponding to the medical equipment; under the condition that the attribute operation triggering event is monitored, determining a target business process matched with the attribute operation triggering event in the business processes; the attribute operation trigger event is a trigger condition for executing attribute operation for the virtual medical device; according to the association relation between the minimum business process units in the target business process, executing attribute operation in each minimum business process unit to obtain attribute change information related to the virtual medical equipment; the attribute change information is used to test the medical device software. The method can improve the software testing efficiency.

Description

Medical equipment software testing method and device, computer equipment and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for testing medical device software, a computer device, and a storage medium.

Background

In current medical device systems, there is a significant amount of software testing effort interacting with hardware devices, and in many cases, the actual device components are connected for testing. In various pressure testing processes for software, equipment components often have difficulty meeting testing requirements. Therefore, it is necessary to realize the pressure test by simulating the software by the simulation device.

In the related art, the development modes of the device component virtualization simulation technology are developed for a certain device, and special development is required for different devices. Moreover, after the simulation software is developed, the code can only be modified again if necessary to adjust the operating logic. In a medical equipment system, the number of equipment is large, the test requirement of medical equipment software is high, a large number of test requirements are met, and a program developer cannot deal with complex and changeable test logic in the development mode, so that the software test efficiency of the medical equipment software is low.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a medical device software testing method, apparatus, computer device, computer-readable storage medium, and computer program product that can improve the software testing efficiency of medical device software.

In a first aspect, the present application provides a method of testing medical device software. The method comprises the following steps:

acquiring a business process associated with virtual medical equipment matched with the medical equipment; the business process is matched with business operation logic corresponding to the medical equipment;

under the condition that an attribute operation triggering event is monitored, determining a target business process matched with the attribute operation triggering event in the business processes; the attribute operation triggering event is a triggering condition for executing attribute operation on the virtual medical equipment;

executing attribute operation in each minimum business process unit according to the association relation between minimum business process units in the target business process to obtain attribute change information related to the virtual medical equipment; the attribute change information is used to test medical device software.

In one embodiment, the virtual medical device has at least one associated business process; and under the condition that the attribute operation triggering event is monitored, determining a target business process matched with the attribute operation triggering event in the business processes, wherein the target business process comprises the following steps:

Matching the initial attribute operation trigger event of each business process with the attribute operation trigger event;

and using the business process of matching the corresponding initial attribute operation triggering event with the attribute operation triggering event as the target business process.

In one embodiment, the adjacent business process minimum units with association relationship are associated with the next business process minimum unit through attribute operation of the previous business process minimum unit; the business process minimum unit of the target business process comprises a current business process minimum unit; executing attribute operation in each business process minimum unit according to the association relation between the business process minimum units in the target business process, including:

acquiring an attribute operation queue of the minimum unit of the current business process to obtain a current attribute operation queue;

sequentially executing attribute operations in the current attribute operation queue; the attribute operation comprises reading or writing an attribute value corresponding to an attribute associated with the attribute operation; the attribute operation is associated with at most one minimum unit of the next business process;

and executing the attribute operation in the attribute operation queue of the associated next business process minimum unit according to the arrangement sequence of the attribute operation in the current attribute operation queue under the condition that the attribute operation has the associated next business process minimum unit in the target business process until the attribute operation in all business process minimum units of the target business process is executed.

In one embodiment, the attribute operations in the current attribute operation queue include current attribute operations; and executing the attribute operation in the attribute operation queue of the associated next business process minimum unit according to the arrangement order of the attribute operation in the current attribute operation queue under the condition that the attribute operation has the associated next business process minimum unit in the target business process, until the attribute operation in all business process minimum units of the target business process is executed, wherein the method comprises the following steps:

when the current attribute operation has an associated next business process minimum unit in the target business process, taking the next business process minimum unit associated with the current attribute operation as the current business process minimum unit, and returning to the step of acquiring the attribute operation queue of the current business process minimum unit until all attribute operations in the attribute operation queue of the associated next business process minimum unit are executed;

and under the condition that the current attribute operation exists in the current attribute operation queue, taking the next attribute operation as the current attribute operation, returning to the step under the condition that the current attribute operation exists in the associated next business process minimum unit in the target business process until the attribute operation in all business process minimum units of the target business process is executed.

In one embodiment, the attribute operation trigger event comprises an attribute change event; the method further comprises the steps of:

monitoring the change of the attribute value corresponding to the internal attribute of the virtual medical equipment;

and generating the attribute change event after the changed attribute value corresponding to the virtual medical equipment meets a preset event generation condition.

In one embodiment, the attribute operation triggering event comprises a timer event; the method further comprises the steps of:

detecting a current time point;

and generating the timer event when the current time point meets a preset time condition.

In one embodiment, the acquiring the business process associated with the virtual medical device matched with the medical device includes:

responding to event configuration operation and attribute configuration operation matched with the business operation logic aiming at the virtual medical equipment, and determining a business flow minimum unit corresponding to the virtual medical equipment and an association relation between the business flow minimum units; the event configuration operation is used for configuring an attribute operation trigger event of the minimum unit of the business process; the attribute configuration operation is used for configuring the attribute of the virtual medical equipment;

And determining the business process associated with the virtual medical equipment according to the association relation between the business process minimum units.

In a second aspect, the present application further provides a test device for medical equipment software. The device comprises:

the acquisition module is used for acquiring the business process associated with the virtual medical equipment matched with the medical equipment; the business process is matched with business operation logic corresponding to the medical equipment;

the determining module is used for determining a target business process matched with the attribute operation trigger event in the business processes under the condition that the attribute operation trigger event is monitored; the attribute operation triggering event is a triggering condition for executing attribute operation on the virtual medical equipment;

the execution module is used for executing attribute operation in each minimum business process unit according to the association relation between the minimum business process units in the target business process to obtain attribute change information related to the virtual medical equipment; the attribute change information is used to test medical device software.

In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor which when executing the computer program performs the steps of:

In a fourth aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:

In a fifth aspect, the present application also provides a computer program product. The computer program product comprises a computer program which, when executed by a processor, implements the steps of:

The test method, the test device, the computer equipment, the storage medium and the computer program product of the medical equipment software are realized by acquiring the business process associated with the virtual medical equipment matched with the medical equipment; the business process is matched with business operation logic corresponding to the medical equipment; under the condition that the attribute operation triggering event is monitored, determining a target business process matched with the attribute operation triggering event in the business processes; the attribute operation triggering event is a triggering condition for executing attribute operation on the virtual medical equipment; according to the association relation between the minimum business process units in the target business process, executing attribute operation in each minimum business process unit to obtain attribute change information related to the virtual medical equipment; the attribute change information is used to test the medical device software.

In this way, as the business processes associated with the virtual medical equipment are matched with the business operation logic corresponding to the matched medical equipment, the attribute operation in the business process minimum unit is executed according to the association relation between the business process minimum units in the target business process matched with the attribute operation triggering event, so that the change logic of the real internal attribute of the medical equipment can be simulated by the internal attribute change of the virtual medical equipment, the attribute change information related to the virtual medical equipment is obtained, and the medical equipment software is fully and accurately tested by the attribute change information; and by executing different business processes, different business operation logics of the medical equipment can be simulated, when the business operation logics are changed, program codes are not required to be modified, only the corresponding business process is selected for software testing, program development work is reduced, and software testing efficiency is improved.

Drawings

FIG. 1 is a flow chart of a method of testing medical device software in one embodiment;

FIG. 2 is a schematic diagram of a minimum unit of a business process according to an embodiment;

FIG. 3 is a schematic diagram of an association relationship between minimum units of a business process in an embodiment;

FIG. 4 is a flow diagram of one embodiment of performing an attribute operation;

FIG. 5 is a schematic diagram illustrating the operation of a target business process in one embodiment;

FIG. 6 is a schematic diagram of a process for generating an attribute operation trigger event and triggering a business process in one embodiment;

FIG. 7 is a schematic diagram of a scenario for simulating a business operational logic change of a real medical device based on a business process framework in one embodiment;

FIG. 8 is a flow chart of a method of testing medical device software according to another embodiment;

FIG. 9 is a block diagram of a test device for medical device software in one embodiment;

fig. 10 is an internal structural view of a computer device in one embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.

In one embodiment, as shown in fig. 1, a method for testing medical device software is provided, and this embodiment is applied to a computer device for illustration, where it is understood that the computer device may be a terminal, a server, or a server cluster formed by a plurality of servers. In this embodiment, the method includes the steps of:

step S110, obtaining a business process associated with a virtual medical device matched with the medical device.

The business process is matched with business operation logic corresponding to the medical equipment.

The business process is used for describing the internal attribute of the medical equipment and the change control of the equipment parts. For example, the business processes may include processes of temperature change control processes, power change control processes, equipment component control processes, and the like. The device components may include, but are not limited to, components such as cooling fans, cooling water tanks, and the like in medical devices.

Wherein the virtual medical device may be associated with several business processes.

The medical equipment is hardware equipment which interacts with the medical equipment software in the process of testing the medical equipment software.

The virtual medical equipment is virtual equipment used for simulating the medical equipment in simulation equipment simulation software.

The simulation device simulation software is installed in the computer device.

The business operation logic is operation logic of the medical equipment, and the business process is a method for simulating the operation logic of the medical equipment by simulation equipment simulation software.

In a specific implementation, aiming at the virtual medical equipment matched with the medical equipment in the simulation equipment simulation software, the computer equipment can acquire the business flow associated with the virtual medical equipment, and the business flow associated with the virtual medical equipment is obtained by configuration and determination according to the business operation logic of the corresponding medical equipment, so that the business flow associated with the virtual medical equipment is matched with the business operation logic corresponding to the corresponding medical equipment.

In step S120, in the case of monitoring the attribute operation trigger event, a target business process matching the attribute operation trigger event is determined from the business processes.

The attribute operation triggering event is a triggering condition for executing attribute operation on the virtual medical equipment.

Wherein the attribute operation is an operation performed on an attribute value of the virtual medical device.

The attribute value of the virtual medical equipment is an attribute value corresponding to the internal attribute of the virtual medical equipment.

Internal attributes may include, but are not limited to, temperature, power, operating state, etc.

In a specific implementation, the computer device may monitor the attribute operation trigger event through the event processor, and after the attribute operation trigger event is monitored, the business process matched with the monitored attribute operation trigger event may be determined as the target business process through a business process manager storing the business process associated with the virtual medical device.

The business process manager is responsible for loading all business processes associated with the virtual medical equipment when the virtual medical equipment is initialized, and is responsible for matching corresponding business processes after monitoring the attribute operation triggering event, so as to determine a target business process.

Step S130, executing attribute operation in each minimum unit of the business process according to the association relation between the minimum units of the business process in the target business process, and obtaining attribute change information related to the virtual medical equipment.

The attribute change information is used for performing software testing on medical equipment software, and the medical equipment software can be installed in computer equipment.

The attribute change information may include a changed attribute value corresponding to the virtual medical device.

One Business process consists of one or more associated Business process minimum Business elements (BSEs).

The service flow minimum unit (BSE) is composed of an attribute operation trigger event and an attribute, wherein the attribute operation trigger event is a trigger condition of the BSE to perform an attribute operation, and the attribute includes an operation performed on an attribute value (i.e., an attribute operation), a rule for generating the attribute value, and an associated next BSE. As shown in fig. 2, a schematic composition of a business process minimum element (BSE) is provided. In practical application, the attribute operation triggering event may be simply referred to as an "event".

In a specific implementation, the computer device may execute attribute operations for the virtual medical device in the minimum business process units according to the association relationship between the minimum business process units in the target business process, so as to obtain attribute change information related to the virtual medical device, where the attribute change information may be used to test medical device software.

Specifically, the medical equipment software can actively acquire attribute change information related to the virtual medical equipment, and the virtual medical equipment can also actively report the attribute change information to the medical equipment software so that the medical equipment software can acquire the attribute change information.

In the test method of the medical equipment software, the business process associated with the virtual medical equipment matched with the medical equipment is obtained; the business process is matched with business operation logic corresponding to the medical equipment; under the condition that the attribute operation triggering event is monitored, determining a target business process matched with the attribute operation triggering event in the business processes; the attribute operation triggering event is a triggering condition for executing attribute operation on the virtual medical equipment; according to the association relation between the minimum business process units in the target business process, executing attribute operation in each minimum business process unit to obtain attribute change information related to the virtual medical equipment; the attribute change information is used to test the medical device software.

In one embodiment, in the event that the attribute operation trigger event is monitored, determining a target business process matching the attribute operation trigger event from among the business processes includes: matching the initial attribute operation trigger event and the attribute operation trigger event of each business process; and taking the business process of matching the corresponding initial attribute operation trigger event and the attribute operation trigger event as a target business process.

Wherein the virtual medical device has at least one associated business process.

Wherein, a plurality of business processes can be operated in the same virtual device at the same time.

The initial attribute operation trigger event is an attribute operation trigger event for triggering and executing a minimum unit of the initial business process in the corresponding business process.

The initial business process minimum unit is the first business process minimum unit in the corresponding business processes.

In a specific implementation, in the process that the computer device determines the target business process matched with the attribute operation trigger event in the business processes under the condition that the attribute operation trigger event is monitored, because the business process is executed from the triggered of the minimum unit of the first business process, the computer device can match the initial attribute operation trigger event of each business process related to the virtual medical device with the monitored attribute operation trigger event through the business process manager, so that the business process of which the initial attribute operation trigger event is matched with the attribute operation trigger event can be used as the target business process of the virtual medical device.

According to the technical scheme of the embodiment, as the business processes are executed from the triggering of the minimum unit of the first business process, the initial attribute operation triggering event of each business process is matched with the attribute operation triggering event; and taking the corresponding business process of which the initial attribute operation trigger event is matched with the attribute operation trigger event as a target business process, so that the business process matched with the attribute operation trigger event can be accurately determined in at least one business process associated with the virtual medical equipment as the target business process to be executed currently under the condition of monitoring the attribute operation trigger event.

In one embodiment, the adjacent business process minimum units with association relationship are associated with the next business process minimum unit through attribute operation of the previous business process minimum unit; the business process minimum unit of the target business process comprises a current business process minimum unit.

Wherein, according to the association relation between the minimum units of the business processes in the target business process, executing the attribute operation in the minimum units of the business processes, comprising: acquiring an attribute operation queue of a minimum unit of a current service flow to obtain a current attribute operation queue; sequentially executing attribute operations in the current attribute operation queue; the attribute operation comprises the step of performing a read operation or a write operation on an attribute value corresponding to the attribute associated with the attribute operation; attribute operation is associated with a minimum unit of the next business process at most; and under the condition that the attribute operation has the associated next business process minimum unit in the target business process, executing the attribute operation in the attribute operation queue of the associated next business process minimum unit according to the arrangement sequence of the attribute operation in the current attribute operation queue until the attribute operation in all business process minimum units of the target business process is executed.

Wherein, a minimum unit of business flow can include at least one attribute operation, the attribute operations in the minimum unit of business flow are arranged according to the execution sequence, form the attribute operation queue of the minimum unit of business flow.

The current business process minimum unit is a business process minimum unit currently executed in the corresponding business process.

Wherein, one business process is composed of N (N > =1) BSEs, each attribute operation (ACT) in a BSE can be associated to the next BSE, that is, the adjacent business process minimum unit with an association relationship is associated with the next business process minimum unit through the attribute operation of the previous business process minimum unit. As shown in fig. 3, a schematic diagram of the association between minimum units of a service flow is provided, and the arrow between BSEs in fig. 3 indicates the association. Each ACT can be associated with at most one BSE, and different ACTs can be associated with the same BSE.

Wherein, the BSE performing a read operation on the attribute value may be an operation of transferring the read attribute value to an associated next BSE.

The BSE may perform a write operation on the attribute value, which may be an operation of modifying the attribute value according to a generation rule of the attribute value.

In the specific implementation, in the process of executing attribute operation in each minimum unit of a business process according to the association relationship between minimum units of the business process in the target business process, the computer equipment starts to execute from the first minimum unit of the business process, and for the minimum unit of the current business process of the target business process, the computer equipment can use the attribute operation queue of the minimum unit of the current business process as the current attribute operation queue; then, the computer device may sequentially execute the attribute operations in the current attribute operation queue according to the arrangement order of the attribute operations in the current attribute operation queue, so as to perform a read operation or a write operation on an attribute value corresponding to an internal attribute associated with the attribute operation in the virtual medical device.

Meanwhile, under the condition that the attribute operation in the current attribute operation queue exists in the associated next business process minimum unit in the target business process, according to the arrangement sequence of the attribute operation in the current attribute operation queue, under the condition that the associated next business process minimum unit meets the trigger condition, executing the attribute operation in the attribute operation queue of the associated next business process minimum unit until the attribute operation in all business process minimum units of the target business process is executed.

Specifically, each attribute operation may be associated with a next BSE, if the currently executed attribute operation is associated with the next BSE, after the execution of the currently executed attribute operation is ended, the attribute operation triggering event of the associated next BSE is triggered, and when the attribute operation triggering event of the next BSE is successfully triggered, that is, the associated next business process minimum unit meets the triggering condition, the attribute operation in the attribute operation queue of the associated next business process minimum unit is executed until all the attribute operations in the business process minimum unit of the target business process are executed. For ease of understanding by those skilled in the art, FIG. 4 provides a schematic flow diagram of an execution attribute operation.

In this way, by performing a read operation or a write operation on the attribute value corresponding to the attribute associated with the attribute operation, so as to modify the attribute value of the virtual medical device, associating the next business process unit with the attribute operation, and after the execution of the attribute operation is finished, triggering the associated attribute operation triggering event of the next BSE until the attribute operation in the minimum unit of all business processes of the target business process is executed, the attribute change generating event and the event-driven attribute change are realized, thereby realizing the automatic operation of the business process.

According to the technical scheme, the attribute operation queue of the minimum unit of the current business process is obtained, so that the current attribute operation queue is obtained; sequentially executing attribute operations in the current attribute operation queue; the attribute operation comprises reading or writing an attribute value corresponding to the attribute associated with the attribute operation so as to modify the attribute value of the virtual medical equipment; attribute operation is associated with a minimum unit of the next business process at most; under the condition that the attribute operation has the associated minimum unit of the next business process in the target business process, executing the attribute operation in the attribute operation queue of the associated minimum unit of the next business process according to the arrangement sequence of the attribute operation in the current attribute operation queue until the attribute operation in the minimum unit of all business processes of the target business process is executed; therefore, the business process can be automatically operated, so that the change logic of the internal attribute of the real medical equipment can be simulated more effectively and truly.

In one embodiment, the attribute operations in the current attribute operation queue include current attribute operations; under the condition that the attribute operation has the associated next business process minimum unit in the target business process, executing the attribute operation in the attribute operation queue of the associated next business process minimum unit according to the arrangement sequence of the attribute operation in the current attribute operation queue until the attribute operation in all business process minimum units of the target business process is executed, wherein the method comprises the following steps:

Under the condition that the current attribute operation has the associated next service flow minimum unit in the target service flow, taking the next service flow minimum unit associated with the current attribute operation as the current service flow minimum unit, and returning to the step of acquiring the attribute operation queue of the current service flow minimum unit until all attribute operations in the attribute operation queue of the associated next service flow minimum unit are executed; and under the condition that the current attribute operation exists in the current attribute operation queue, taking the next attribute operation as the current attribute operation, returning to the step under the condition that the current attribute operation exists in the associated next business process minimum unit in the target business process until the attribute operation in all business process minimum units of the target business process is executed.

Wherein the current attribute operation is a currently executed attribute operation.

In a specific implementation, under the condition that an associated next business process minimum unit exists in a target business process by attribute operation, executing attribute operation in an attribute operation queue of the associated next business process minimum unit according to the arrangement sequence of the attribute operation in a current attribute operation queue, until the attribute operation in all business process minimum units of the target business process is executed, the computer equipment can judge whether the associated next business process minimum unit exists in the target business process by judging whether the current attribute operation has the associated next business process minimum unit or not through whether the current attribute operation records the unit identification corresponding to the associated next business process minimum unit or not, under the condition that the associated next business process minimum unit exists, after the execution of the current attribute operation is finished, and under the condition that the associated next business process minimum unit meets a trigger condition, taking the next business process minimum unit associated with the current attribute operation as the current business process minimum unit, and returning to the step of acquiring the attribute operation queue of the current business process minimum unit until all attribute operations in the attribute operation queue of the associated next business process minimum unit are executed.

Then, the computer device determines whether the current attribute operation exists in the current attribute operation queue, and when the current attribute operation exists, the computer device returns the next attribute operation as the current attribute operation to the step when the current attribute operation exists in the associated next minimum business process unit in the target business process until the attribute operation in all minimum business process units of the target business process is executed.

Under the condition that the next attribute operation does not exist, the computer equipment judges whether the current business process minimum unit exists or not according to whether the unit identifier corresponding to the last business process minimum unit is recorded in the current business process minimum unit, and under the condition that the last business process minimum unit exists, the computer equipment returns to the last business process minimum unit of the current business process minimum unit, and continues to sequentially execute the attribute operation in the attribute operation queue of the last business process minimum unit until all the attribute operations in the business process minimum units of the target business process are executed.

And if the condition that the last minimum business flow unit does not exist is judged, finishing the execution of the attribute operation in all the minimum business flow units of the target business flow.

For example, when the current business process minimum unit is the first business process minimum unit in the target business process, for the current attribute operation queue (including attribute operations of A1, A2, A3 …, etc.), the execution starts from the first attribute operation A1, the execution of A1 is completed, if A1 is associated with the next BSE, and the next BSE satisfies the trigger condition, the attribute operations in the next BSE are sequentially executed (at this time, the attribute operations of A2, A3, etc. are not executed yet), and when the execution of the subsequent BSE triggered by A1 is completed, the first business process minimum unit is returned to execute the attribute operations of A2, A3, etc. until all the attribute operations in the business process minimum units of the target business process are executed.

For ease of understanding by those skilled in the art, FIG. 5 provides a schematic diagram of the operation of a target business process. And after the execution is finished, continuing to wait for the next attribute operation triggering event to trigger the service flow to be re-executed. Wherein, a plurality of business processes can be operated simultaneously in the same virtual medical equipment.

According to the technical scheme of the embodiment, under the condition that the current attribute operation has the associated next service flow minimum unit in the target service flow, the next service flow minimum unit associated with the current attribute operation is taken as the current service flow minimum unit, and the step of acquiring the attribute operation queue of the current service flow minimum unit is returned until all attribute operations in the attribute operation queue of the associated next service flow minimum unit are executed; under the condition that the current attribute operation exists in the current attribute operation queue, taking the next attribute operation as the current attribute operation, returning to the step under the condition that the current attribute operation exists in the associated next business process minimum unit in the target business process until the attribute operation in all business process minimum units of the target business process is executed; therefore, all minimum units of the target business processes can be sequentially executed, and automatic operation of the target business processes matched with the attribute operation triggering event is realized.

In one embodiment, the attribute operation trigger event comprises an attribute change event; the method further comprises the steps of: monitoring a change in an attribute value corresponding to an internal attribute of the virtual medical device; and generating an attribute change event when the changed attribute value corresponding to the virtual medical equipment meets the preset event generation condition.

In a specific implementation, when the attribute value of the virtual medical device changes and a certain condition (namely a preset event generation condition) is met, an attribute change event is generated, so that the event processor receives the attribute change event. Wherein a change in the attribute value refers to a modification of the attribute value. Whether a change in the attribute value results in an attribute change event is determined by the user configuration. The attribute change event comprises three conditions, namely, one attribute value is changed; 2. the attribute value is equal to, greater than or equal to, less than or equal to a user configured threshold value; 3. the attribute value is read and written.

Wherein table 1 is an attribute change condition type and description of an attribute change event generated by a change in an attribute value.

Table 1 condition type and description of attribute change generating event

One attribute change event can be composed of a plurality of attribute change conditions, and each attribute change condition is combined through an OR relationship and an AND relationship, namely if the relationship of the two attribute change conditions is the OR relationship, one of the attribute change conditions can be judged to meet the preset event generation condition so as to generate the attribute change event; if the relation is AND, two attribute changes are required to be simultaneously met, and then the condition for generating the preset event can be judged to be met, and the attribute change event is generated.

According to the technical scheme, the change of the attribute value corresponding to the internal attribute of the virtual medical equipment is monitored; when the changed attribute value corresponding to the virtual medical equipment is monitored to meet the preset event generation condition, the monitored attribute change event can be accurately judged, so that the execution target business process can be triggered and executed according to the attribute change event, and the change logic of the internal attribute of the medical equipment can be simulated according to the internal attribute change of the virtual medical equipment.

In one embodiment, the attribute operation trigger event comprises a timer event; the method further comprises the steps of: detecting a current time point; and generating a timer event when the current time point meets a preset time condition.

The timer event may be triggered one or more times at a certain time, or may be triggered one or more times at regular intervals.

In a specific implementation, by detecting the current time point, when the current time point meets a preset time condition, a timer event is generated, so that the event processor receives the timer event. Specifically, when the current time point reaches a preset time point, one or more timer events can be triggered, and when the current time point and the time point of last triggering the timer event meet a preset time interval, one or more timer events can be triggered.

Thus, in some embodiments, the attribute operation trigger event may include an attribute change event and a timer event, one BSE may be composed of a plurality of different attribute operation trigger events, and the attribute operation trigger events may be "or" and "combined, i.e., if the relationship of the two attribute operation trigger events is" or "then either attribute operation trigger event generation may trigger BSE execution; if the and relationship is present, then only if two attribute operation trigger events are generated simultaneously will BSE execution be triggered.

Therefore, when the event processor monitors at least one attribute operation triggering event, the monitored at least one attribute operation triggering event can be matched with each initial attribute operation triggering event for triggering and executing each service flow of the virtual medical device through the service flow manager, a matched target service flow is determined, so that the target service flow is triggered, and the target service flow is executed. In the service flow, other BSEs except the first BSE are directly triggered by the last BSE. The attribute operation trigger event generation and trigger business process is shown in fig. 6.

According to the technical scheme, the current time point is detected; when the current time point meets the preset time condition, a timer event is generated, so that the timer event can be triggered according to the preset time to execute the business process of the virtual medical equipment, the business process of the virtual medical equipment can be automatically operated, and the business operation logic of the real medical equipment can be effectively simulated.

In one embodiment, obtaining a business process associated with a virtual medical device that matches a medical device includes: responding to event configuration operation and attribute configuration operation matched with service operation logic aiming at the virtual medical equipment, and determining a minimum unit of a service flow corresponding to the virtual medical equipment and an association relation among the minimum units of the service flow; and determining the business process associated with the virtual medical equipment according to the association relation between the business process minimum units.

The event configuration operation is used for configuring attribute operation triggering events of the minimum unit of the business process.

Wherein the attribute configuration operation is used to configure attributes of the virtual medical device.

In a specific implementation, in the process of acquiring a business process associated with a virtual medical device matched with a medical device, the computer device can provide a business process framework for the virtual medical device matched with the medical device, the framework provides a set of configurable business process operation scheme, and by configuring a business process in the business process framework, the change logic of the internal attribute (such as temperature, power, working state and the like) of the real medical device can be simulated by the internal attribute change of the virtual medical device; but also can be configured into any business process, and the business process can be changed according to the situation that real medical equipment is almost impossible to occur.

Specifically, the user may perform event configuration operation and attribute configuration operation on the virtual medical device according to service operation logic of the corresponding medical device in the service flow framework, so that the computer device may determine an attribute operation triggering event in response to the event configuration operation on the virtual medical device, determine an attribute of the virtual medical device in response to the attribute configuration operation on the virtual medical device, and the attribute of the virtual medical device includes a read or write operation (i.e., attribute operation) performed on the attribute value, a rule for generating the attribute value, and an associated next minimum unit of the service flow, so that, by responding to the event configuration operation and the attribute configuration operation on the virtual medical device, a minimum unit of the service flow composed of the attribute operation triggering event and the attribute, and an association relationship between the minimum units of the service flow may be determined, so that a service flow associated with the virtual medical device may be determined according to the association relationship between the minimum units of the service flow.

The attribute value generation rule is designed aiming at an attribute value, is a change logic of an attribute, and can be edited and configured by a user in a formula form.

Wherein, the attribute value generation rule formula comprises: 1. attributes, values, basic mathematical operators, etc. 2, basic functions, such as sqrt (), pow (), rand (), abs (), trigonometric functions, etc. Wherein the attributes are represented in the formula in the manner of "[ attribute name ]". An attribute change rule configuration writing format example is shown in table 2:

table 2 attribute change rule configuration write format examples

/>

Therefore, by providing the attribute generation rule configuration and writing the generation rule, the attribute of the virtual medical equipment can be changed according to the mode wanted by the user, so that the software testing requirement of the user is met, and the man-machine interaction intelligence is improved.

In addition, aiming at the configured minimum units of various service flows, the user can also recombine the association relations among the minimum units of various service flows to form various new service flows so as to simulate service operation logic of different medical equipment.

In addition, if the user needs to modify the operation logic of the virtual medical equipment, the corresponding business flow configuration can be modified, program modification or development is not needed, program development work is reduced, and software testing efficiency is improved. Specifically, the association relation between the minimum units of the service flow of the virtual medical equipment can be modified, the virtual medical equipment can be recombined, the attribute operation sequence in the attribute operation queue can be modified, and the attribute value generation rule formula can be modified.

Therefore, the business process framework can realize business scenes needed by the interactive test of most medical equipment software and hardware equipment only by configuring the business process. For different medical equipment, only different business processes are required to be configured, so that the matched virtual medical equipment can operate according to the situation wanted by a user, program modification or development is not required, and program development work is reduced. The business process framework enables testers of medical equipment software to configure required business processes according to different testing requirements so as to realize full testing of the medical equipment software, thereby ensuring the safety of the equipment and improving the software development speed. Fig. 7 provides a schematic diagram of a scenario for simulating a business operational logic change of a real medical device based on a business process framework. As shown in fig. 7, the virtual medical device simulates the change logic of the internal attribute of the real medical device by executing each business process, so as to obtain the related attribute change information, and the medical device software accesses the virtual medical device to obtain the attribute change information for software testing.

In another embodiment, as shown in fig. 8, a method for testing medical equipment software is provided, and the method is applied to computer equipment for illustration, and includes the following steps:

Step S810, determining a minimum unit of a business process corresponding to the virtual medical device and an association relationship between the minimum units of the business processes in response to the event configuration operation and the attribute configuration operation matched with the business operation logic for the virtual medical device.

Step S820, determining the business process associated with the virtual medical equipment according to the association relation between the minimum units of the business processes.

In step S830, the initial attribute operation trigger event and the attribute operation trigger event of each business process are matched under the condition that the attribute operation trigger event is monitored.

In step S840, the business process of matching the corresponding initial attribute operation trigger event and the attribute operation trigger event is used as the target business process.

Step S850, obtaining the attribute operation queue of the minimum unit of the current business process, and obtaining the current attribute operation queue.

Step S860, the attribute operations in the current attribute operation queue are sequentially executed.

In step S870, when the attribute operation has the associated next-business-flow minimum unit in the target business flow, the attribute operation in the attribute operation queue of the associated next-business-flow minimum unit is executed according to the arrangement order of the attribute operation in the current attribute operation queue until the attribute operation in all the business-flow minimum units of the target business flow is executed, thereby obtaining the attribute change information related to the virtual medical device.

It should be noted that, the specific limitation of the above steps may be referred to the specific limitation of the test method of the medical device software.

It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides a testing device of the medical equipment software for realizing the testing method of the medical equipment software. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in the embodiments of the test device for one or more medical device software provided below may refer to the limitation of the test method for one medical device software hereinabove, and will not be repeated herein.

In one embodiment, as shown in fig. 9, there is provided a test apparatus of medical device software, comprising: an acquisition module 910, a determination module 920, and an execution module 930, wherein:

an obtaining module 910, configured to obtain a business process associated with a virtual medical device that matches a medical device; and the business process is matched with business operation logic corresponding to the medical equipment.

A determining module 920, configured to determine, in the case of monitoring an attribute operation trigger event, a target business process that matches the attribute operation trigger event from the business processes; the attribute operation trigger event is a trigger condition for executing an attribute operation with respect to the virtual medical device.

An execution module 930, configured to execute attribute operations in the minimum business process units according to the association relationship between the minimum business process units in the target business process, to obtain attribute change information related to the virtual medical device; the attribute change information is used to test medical device software.

In one embodiment, the virtual medical device has at least one associated business process; the determining module 920 is specifically configured to match a start attribute operation trigger event of each business process with the attribute operation trigger event; and using the business process of matching the corresponding initial attribute operation triggering event with the attribute operation triggering event as the target business process.

In one embodiment, the adjacent business process minimum units with association relationship are associated with the next business process minimum unit through attribute operation of the previous business process minimum unit; the business process minimum unit of the target business process comprises a current business process minimum unit; the execution module 930 is specifically configured to obtain an attribute operation queue of the minimum unit of the current service flow, to obtain a current attribute operation queue; sequentially executing attribute operations in the current attribute operation queue; the attribute operation comprises reading or writing an attribute value corresponding to an attribute associated with the attribute operation; the attribute operation is associated with at most one minimum unit of the next business process; and executing the attribute operation in the attribute operation queue of the associated next business process minimum unit according to the arrangement sequence of the attribute operation in the current attribute operation queue under the condition that the attribute operation has the associated next business process minimum unit in the target business process until the attribute operation in all business process minimum units of the target business process is executed.

In one embodiment, the attribute operations in the current attribute operation queue include current attribute operations; the executing module 930 is specifically configured to, when the current attribute operation has an associated next business process minimum unit in the target business process, return the next business process minimum unit associated with the current attribute operation to the step of obtaining the attribute operation queue of the current business process minimum unit, until all attribute operations in the attribute operation queue of the associated next business process minimum unit are executed; and under the condition that the current attribute operation exists in the current attribute operation queue, taking the next attribute operation as the current attribute operation, returning to the step under the condition that the current attribute operation exists in the associated next business process minimum unit in the target business process until the attribute operation in all business process minimum units of the target business process is executed.

In one embodiment, the attribute operation trigger event comprises an attribute change event; the determining module 920 is further configured to monitor a change in an attribute value corresponding to an internal attribute of the virtual medical device; and generating the attribute change event after the changed attribute value corresponding to the virtual medical equipment meets a preset event generation condition.

In one embodiment, the attribute operation triggering event comprises a timer event; the determining module 920 is further configured to detect a current time point; and generating the timer event when the current time point meets a preset time condition.

In one embodiment, the obtaining module 910 is specifically configured to determine a minimum unit of a business process corresponding to the virtual medical device and an association relationship between the minimum units of the business process in response to an event configuration operation and an attribute configuration operation that are matched with the business operation logic for the virtual medical device; the event configuration operation is used for configuring an attribute operation trigger event of the minimum unit of the business process; the attribute configuration operation is used for configuring the attribute of the virtual medical equipment; and determining the business process associated with the virtual medical equipment according to the association relation between the business process minimum units.

The modules in the test device of the medical equipment software can be realized by all or part of software, hardware and combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a server, and the internal structure of which may be as shown in fig. 10. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured 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, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for storing minimum unit data of the business process. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements a method of testing medical device software.

It will be appreciated by those skilled in the art that the structure shown in fig. 10 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.

In an embodiment, there is also provided a computer device comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, carries out the steps of the method embodiments described above.

In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.

It should be noted that, the user information (including, but not limited to, user equipment information, user personal information, etc.) and the data (including, but not limited to, data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data are required to comply with the related laws and regulations and standards of the related countries and regions.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the various embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the various embodiments provided herein may include at least one of relational databases and non-relational databases. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic units, quantum computing-based data processing logic units, etc., without being limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to the appended claims.

Claims

1. A method of testing medical device software, the method comprising:

2. The method of claim 1, wherein the virtual medical device has at least one associated business process; and under the condition that the attribute operation triggering event is monitored, determining a target business process matched with the attribute operation triggering event in the business processes, wherein the target business process comprises the following steps:

3. The method according to claim 1, wherein adjacent business process minimum units having an association relationship are associated with the next business process minimum unit through attribute operation of the previous business process minimum unit; the business process minimum unit of the target business process comprises a current business process minimum unit; executing attribute operation in each business process minimum unit according to the association relation between the business process minimum units in the target business process, including:

4. A method according to claim 3, wherein the attribute operations in the current attribute operation queue comprise current attribute operations; and executing the attribute operation in the attribute operation queue of the associated next business process minimum unit according to the arrangement order of the attribute operation in the current attribute operation queue under the condition that the attribute operation has the associated next business process minimum unit in the target business process, until the attribute operation in all business process minimum units of the target business process is executed, wherein the method comprises the following steps:

5. The method of claim 1, wherein the attribute operation trigger event comprises an attribute change event; the method further comprises the steps of:

6. The method of claim 1, wherein the attribute operation trigger event comprises a timer event; the method further comprises the steps of:

detecting a current time point;

7. The method of claim 1, wherein the obtaining the business process associated with the virtual medical device that matches the medical device comprises:

8. A test apparatus for medical device software, the apparatus comprising:

9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 7 when the computer program is executed.

10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 7.