CN115695570B - Method, device, equipment and storage medium for converting medical image scanning protocol - Google Patents
Method, device, equipment and storage medium for converting medical image scanning protocol Download PDFInfo
- Publication number
- CN115695570B CN115695570B CN202211318487.9A CN202211318487A CN115695570B CN 115695570 B CN115695570 B CN 115695570B CN 202211318487 A CN202211318487 A CN 202211318487A CN 115695570 B CN115695570 B CN 115695570B
- Authority
- CN
- China
- Prior art keywords
- version
- protocol
- conversion
- medical image
- path
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000006243 chemical reaction Methods 0.000 claims abstract description 494
- 238000004590 computer program Methods 0.000 claims description 22
- 238000005481 NMR spectroscopy Methods 0.000 description 5
- 230000008859 change Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 238000004519 manufacturing process Methods 0.000 description 3
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Landscapes
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The application provides a method, a device, equipment and a storage medium for converting a medical image scanning protocol, which can enable the protocol version of the medical image scanning protocol on a medical image scanning application and a medical image scanning platform to be consistent. According to the method, each version conversion unit of protocol conversion file description is obtained, and according to a source protocol version and a target protocol version included in each version conversion unit, a protocol version which is required to be subjected to conversion between a first protocol version and a second protocol version by a medical image scanning protocol is determined, so that a version conversion path is obtained; determining a target version conversion unit in each version conversion unit according to two adjacent protocol versions in the version conversion path; and converting the medical image scanning protocol between the first protocol version and the second protocol version according to the sequence of each target version conversion unit on the version conversion path.
Description
Technical Field
The present application relates to the field of medical image scanning protocol processing technology, and in particular, to a method, an apparatus, a computer device, a storage medium, and a computer program product for converting a medical image scanning protocol.
Background
The medical image scanning application operates on the basis of a medical image scanning platform, and a protocol used when the medical image scanning application interacts with the medical image scanning platform may be referred to as a medical image scanning protocol.
Over time, the medical image scanning protocol may change, and accordingly, multiple protocol versions may exist. If the protocol versions of the medical image scanning protocol are not consistent across the medical image scanning application and the medical image scanning platform, interactions between the medical image scanning application and the medical image scanning platform may be erroneous.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a method, apparatus, computer device, storage medium, and computer program product for converting a medical image scanning protocol.
The application provides a conversion method of a medical image scanning protocol, which comprises the following steps:
Taking the medical image scanning protocol version on the medical image scanning application as a first protocol version, and taking the medical image scanning protocol version on the medical image scanning platform as a second protocol version;
Each version conversion unit of the protocol conversion file description is obtained, and a protocol version which needs to be passed through by the medical image scanning protocol for conversion between the first protocol version and the second protocol version is determined according to a source protocol version and a target protocol version which are included by each version conversion unit, so that a version conversion path is obtained;
determining a target version conversion unit in each version conversion unit according to two adjacent protocol versions in the version conversion path;
and converting the medical image scanning protocol between the first protocol version and the second protocol version according to the sequence of each target version conversion unit on the version conversion path.
The application provides a conversion device of a medical image scanning protocol, which comprises:
The protocol version determining module is used for taking the medical image scanning protocol version on the medical image scanning application as a first protocol version and taking the medical image scanning protocol version on the medical image scanning platform as a second protocol version;
The path acquisition module is used for acquiring each version conversion unit described by the protocol conversion file, and determining a protocol version which needs to be passed by the medical image scanning protocol for conversion between the first protocol version and the second protocol version according to a source protocol version and a target protocol version which are included by each version conversion unit to obtain a version conversion path;
The target unit determining module is used for determining a target version conversion unit in each version conversion unit according to two adjacent protocol versions in the version conversion path;
the conversion module is used for converting the medical image scanning protocol between the first protocol version and the second protocol version according to the sequence of each target version conversion unit on the version conversion path. The present application provides a computer device comprising a memory storing a computer program and a processor executing the method described above.
The present application provides a computer readable storage medium having stored thereon a computer program for execution by a processor of the above method.
The present application provides a computer program product having a computer program stored thereon, the computer program being executed by a processor to perform the above method.
In the method, the device, the computer equipment, the storage medium and the computer program product for converting the medical image scanning protocol, the medical image scanning protocol version on the medical image scanning application is used as a first protocol version, and the medical image scanning protocol version on the medical image scanning platform is used as a second protocol version; determining a protocol version which needs to be passed by a medical image scanning protocol for conversion between a first protocol version and a second protocol version according to a source protocol version and a target protocol version which are included in each version conversion unit described by a protocol conversion file, and obtaining a version conversion path; determining a target version conversion unit in each version conversion unit according to two adjacent protocol versions in the version conversion path; according to the sequence of each target version conversion unit on the version conversion path, converting the medical image scanning protocol between the first protocol version and the second protocol version, so that the protocol versions of the medical image scanning protocol on the medical image scanning application and the medical image scanning platform are consistent, and interaction errors between the medical image scanning application and the medical image scanning platform are avoided; in addition, even if the protocol version of the medical image scanning protocol on the medical image scanning platform changes, a developer is not required to manufacture the medical image scanning protocol of the corresponding protocol version for the medical image scanning application, and the computer equipment can automatically form a version conversion path according to the version conversion units described by the protocol conversion file and the unit conversion contents corresponding to the version conversion units, automatically determine the unit conversion contents required by the conversion of the medical image scanning protocol between the first protocol version and the second protocol version, and realize the automatic conversion of the medical image scanning protocol without personnel intervention.
Drawings
FIG. 1 is a diagram of parent-child relationships between software versions and protocol versions in one embodiment;
FIG. 2 is a flow chart of a method for converting a medical image scanning protocol according to an embodiment;
FIG. 3 is a schematic diagram of a protocol conversion file in one embodiment;
FIG. 4 is a flow chart of a method for converting a medical image scanning protocol according to an embodiment;
FIG. 5 is a block diagram showing a structure of a conversion device of a medical image scanning protocol according to an embodiment;
fig. 6 is an internal structural diagram of a computer device in one embodiment.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the described embodiments of the application may be combined with other embodiments.
The medical image scanning software comprises a medical image scanning platform and a medical image scanning application, and the medical image scanning application runs by depending on the medical image scanning platform; the mode used for scanning the medical image can be nuclear magnetic resonance or CT. The medical image scanning software may be updated iteratively or regressively, in which case the software version may be used as a representation that clearly distinguishes each release in order to distinguish each release of medical image scanning software.
In order to represent the evolution history of the medical image scanning software, the software version may be named in a parent-child relationship, as shown in fig. 1, MAIN represents the software version number of the MAIN branch, VA1 is a child software version of MAIN, VA1_1 is a child software version of VA1, and VA1_1_1sp1 is a child software version of VA 1_1.
The protocol used when the medical image scanning application and the medical image scanning platform interact may be referred to as a medical image scanning protocol. When the medical image scanning is based on a nuclear magnetic resonance mode, the medical image scanning protocol can be called as a nuclear magnetic resonance protocol, and the nuclear magnetic resonance protocol can comprise a magnetic resonance parameter set used for configuring sequence scanning and post-reconstruction processing and is organized in a certain data format; the nmr protocol mainly specifies the type, value range and search mode of common parameters of all sequences, for example, specifies that TR (Repetition Time) data type is long and unit is ms.
With time change, the medical image scanning protocol may change, specifically, a "protocol version" may be introduced to indicate the evolution history of the medical image scanning protocol, where the protocol version may be named in a parent-child relationship manner, as shown in fig. 1, when the software version is VA1, the protocol version of the corresponding medical image scanning protocol is named as < ver >1.1, when the software version VA1 pulls out a new branch, the corresponding software version is named as VA1_1, and when the medical image scanning protocol is updated, the protocol version naming may be < ver >1.1.1, i.e. one bit is added on the basis of the parent branch protocol version of < ver >1.1, and the last bit of the protocol version represents the difference between different child branches of the same parent branch, i.e. the subordinate and iterative relationship of different branch protocols may be represented by the protocol version.
In the evolution process of the medical image scanning protocol, the protocol version with the longer time can be called as a low protocol version, and the protocol version with the shorter time can be called as a high protocol version. When the medical image scanning protocol changes from a low protocol version to a high protocol version, it may be referred to as a forward conversion of the medical image scanning protocol; when the medical image scanning protocol changes from a high protocol version to a low protocol version, it may be referred to as a reverse conversion of the medical image scanning protocol.
The conversion method of the medical image scanning protocol can be applied to a forward conversion scene, a reverse conversion scene or a scene in which the forward conversion and the reverse conversion exist simultaneously of the medical image scanning protocol. The method may be performed by a computer device and may include the steps shown in fig. 2:
step S201, the medical image scanning protocol version on the medical image scanning application is used as the first protocol version, and the medical image scanning protocol version on the medical image scanning platform is used as the second protocol version.
The protocol version of the medical image scanning protocol on the medical image scanning application may be referred to as a first protocol version and the protocol version of the medical image scanning protocol on the medical image scanning platform may be referred to as a second protocol version; the first protocol version and the second protocol version may or may not be identical. In the event of inconsistencies, a translation is required to reconcile the protocol version of the medical image scan on the medical image scanning application with the protocol version on the medical image scanning platform. When the first protocol version and the second protocol version are not identical, step S202 may be performed.
Step S202, each version conversion unit described by the protocol conversion file is obtained, and a protocol version which needs to be passed through by the medical image scanning protocol for conversion between a first protocol version and a second protocol version is determined according to a source protocol version and a target protocol version which are included by each version conversion unit, so that a version conversion path is obtained;
In a scenario that the medical image scanning application adapts to the medical image scanning platform, the first protocol version can be used as a first protocol version, the second protocol version can be used as a tail protocol version, and then a version conversion path for converting the medical image scanning protocol from the first protocol version to the second protocol version is obtained.
In a scenario that the medical image scanning platform is adapted to the medical image scanning application, the second protocol version may be used as a first protocol version, and the first protocol version may be used as a tail protocol version, so as to obtain a version conversion path for converting the medical image scanning protocol from the second protocol version to the first protocol version.
The protocol conversion file can be pre-generated, and can be preset on the medical image scanning platform or an application package of the medical image scanning application. The evolution history of the medical image scanning protocol can be determined through the protocol version, how to carry out version conversion on the medical image scanning protocol is determined, and a corresponding forward protocol conversion file and a corresponding reverse protocol conversion file are arranged between adjacent father and son branches, as shown in fig. 3, a medical image scanning platform platform_A+a medical image scanning application app_A is updated to a medical image scanning platform platform_B+a medical image scanning application app_B through the platform; the Protocol packet (hereinafter referred to as Protocol packet_a) carried by the application packet of the medical image scanning application app_a is manufactured based on the medical image scanning platform platform_a or the medical image scanning application app_a, and the Protocol version of the medical image scanning Protocol obtained by using the Protocol packet_a is consistent with the medical image scanning platform platform_a/the medical image scanning application app_a without Protocol conversion; similarly, a Protocol packet (hereinafter referred to as Protocol packet_b) carried by an application packet of the medical image scanning application app_b is made based on the medical image scanning platform plane_b or the medical image scanning application app_b, and a Protocol version of a medical image scanning Protocol obtained by using the Protocol packet_b is consistent with the medical image scanning platform plane_b/the medical image scanning application app_b without Protocol conversion.
If the Protocol packet_a is used to install the medical image scanning application app_a to the medical image scanning platform platform_b, a Protocol conversion is required to change the Protocol version on the medical image scanning application app_a to the Protocol version on the medical image scanning platform platform_b to be consistent, and if the Protocol version on the medical image scanning application app_a is lower and the Protocol version on the medical image scanning platform platform_b is higher, the Protocol conversion is a forward Protocol conversion. Similarly, if the Protocol packet_b is used to install the medical image scanning application app_b on the medical image scanning platform platform_a, a Protocol conversion is required to change the Protocol version on the medical image scanning application app_b into the Protocol version on the medical image scanning platform platform_a to be consistent, and if the Protocol version on the medical image scanning application app_b is higher and the Protocol version on the medical image scanning platform platform_a is lower, the Protocol conversion is reverse.
The protocol conversion file may describe one or more version conversion units, each version conversion unit including: a source protocol version, a target protocol version, and conversion contents required for converting the source protocol version into a protocol version as the target protocol version; that is, each version conversion unit describes which protocol version is the source protocol version, which protocol version is the target protocol version, and the conversion contents required for converting from the protocol version which is the source protocol version to the protocol version which is the target protocol version.
The description is presented in terms of the protocol conversion file as shown above:
When describing a version-conversion unit, a < item > may be used as a start identifier and a </item > may be used as an end identifier. In the start identifier < item >, a protocol version as a source protocol version and a protocol version as a target protocol version can be written. Between the start identifier and the end identifier, conversion contents required for converting from the source protocol version to the target protocol version, which may be referred to as unit conversion contents, may be written.
In the above protocol conversion file, from corresponds To the source protocol version, to corresponds To the target protocol version, "Add" indicates addition, "Remove" indicates deletion, and "Reset" indicates modification.
For example, the number of the cells to be processed,In a version conversion unit, in a start identifier < item from= "1" to= "1.1" >, the start identifier writes protocol version 1 as a source protocol version, protocol version 1.1 as a target protocol version, and < remove tag= "root.a.b.c" > "to < remove >" located between the start identifier and the end identifier, a conversion content required for conversion from protocol version 1 to 1.1 is written, the conversion content indicating: to convert the medical image scanning protocol from the protocol version 1 to 1.1, the tag= "root.a.b.c" needs to be deleted in the protocol version 1, and the protocol version 1.1 is obtained after deletion.
In this embodiment, according to version conversion units described by the protocol conversion file, a source protocol version and a target protocol version included in each version conversion unit may be determined, and further, according to the source protocol version and the target protocol version corresponding to the version conversion unit, a protocol version required to be passed by the medical image scanning protocol to convert between the first protocol version and the second protocol version is determined, so as to obtain a version conversion path.
Taking the first protocol version of 1.2.2 and the second protocol version of 1.1.1 as examples: the start identifiers of the version conversion units of the protocol conversion file description are shown in table 1:
TABLE 1
According to the respective initial identifiers of the version conversion units, the source protocol version and the target protocol version included by each version conversion unit can be determined; then, according to the source protocol version and the target protocol version corresponding to each version conversion unit, the protocol versions required to be passed between the protocol version 1.2.2 and the protocol version 1.1.1 are determined to be 1.2.2, 1.2, 1, 1.1 and 1.1.1, and the protocol versions required to be passed are taken as nodes to obtain a version conversion path 1.2.2- >1.2- >1.1- >1.1.1.
In step S203, a target version conversion unit is determined from the two adjacent protocol versions in the version conversion path.
Two adjacent protocol versions in the version conversion path are a source protocol version and a target protocol version included in a certain version conversion unit of the protocol conversion file description, for example, protocol versions 1.2.2 and 1.2 are adjacent protocol versions in the version conversion path 1.2.2- >1.2- >1.1- >1.1.1, the two protocol versions are a source protocol version and a target protocol version included in the version conversion unit ①, and for example, protocol versions 1 and 1.1 are adjacent protocol versions in the version conversion path 1.2.2- >1.2- >1.1, and the two protocol versions are a source protocol version and a target protocol version included in the version conversion unit ④.
After determining the version conversion path between the first protocol version and the second protocol version, since two adjacent protocol versions in the version conversion path are matched with the source protocol version and the target protocol version included in a certain version conversion unit, the target version conversion unit can be determined in each version conversion unit described in the protocol conversion file.
Illustratively, a version conversion path between the protocol version 1.2.2 and the protocol version 1.1.1 is 1.2- >1.1- >1.1.1, and there are two adjacent protocol versions 1.2.2 and 1.2 in the version conversion path, and in each version conversion unit described in the protocol conversion file, the version conversion unit of the source protocol version and the target protocol version included in the version conversion unit of the two adjacent protocol versions 1.2.2 and 1.2 are ①, and therefore, ① may be regarded as a target version conversion unit, and in this manner, it may be determined that the version conversion unit ③④⑥ is also a target version conversion unit.
Step S204, the medical image scanning protocol is converted between the first protocol version and the second protocol version according to the sequence of each target version conversion unit on the version conversion path.
Two adjacent protocol versions in the version conversion path are a source protocol version and a target protocol version included in a certain version conversion unit, so that each target version conversion unit has a corresponding sequence on the version conversion path, for example, a version conversion path between a protocol version 1.2.2 and a protocol version 1.1.1: in 1.2.2- >1.2- >1- >1.1- >1.1.1, the version switch units ①、③、④ and ⑥ are in the following order on the version switch path: ①③④⑥.
Then, firstly converting the medical image scanning protocol of the protocol version 1.2.2 by using unit conversion content corresponding to the version conversion unit ① to obtain the medical image scanning protocol of the protocol version 1.2; then, converting the medical image scanning protocol of the protocol version 1.2 by utilizing unit conversion content corresponding to the version conversion unit ③ to obtain the medical image scanning protocol of the protocol version 1; converting the medical image scanning protocol of the protocol version 1 by using unit conversion content corresponding to the version conversion unit ④ to obtain the medical image scanning protocol of the protocol version 1.1; and finally, converting the medical image scanning protocol of the protocol version 1.1 by utilizing unit conversion content corresponding to the version conversion unit ⑥ to obtain the medical image scanning protocol of the protocol version 1.1.1. Furthermore, the medical image scanning application uses the medical image scanning protocol with the protocol version of 1.1.1, so that the medical image scanning application and the medical image scanning platform interact based on the medical image scanning protocol with the consistent protocol version.
In the above method for converting a medical image scanning protocol, a medical image scanning protocol version on a medical image scanning application is used as a first protocol version, and a medical image scanning protocol version on a medical image scanning platform is used as a second protocol version; determining a protocol version which needs to be passed by a medical image scanning protocol for conversion between a first protocol version and a second protocol version according to a source protocol version and a target protocol version which are included in each version conversion unit described by a protocol conversion file, and obtaining a version conversion path; determining a target version conversion unit in each version conversion unit according to two adjacent protocol versions in the version conversion path; according to the sequence of each target version conversion unit on the version conversion path, converting the medical image scanning protocol between the first protocol version and the second protocol version, so that the protocol versions of the medical image scanning protocol on the medical image scanning application and the medical image scanning platform are consistent, and interaction errors between the medical image scanning application and the medical image scanning platform are avoided; in addition, even if the protocol version of the medical image scanning protocol on the medical image scanning platform changes, a developer is not required to manufacture the medical image scanning protocol of the corresponding protocol version for the medical image scanning application, and the computer equipment can automatically form a version conversion path according to the version conversion units described by the protocol conversion file and the unit conversion contents corresponding to the version conversion units, automatically determine the unit conversion contents required by the conversion of the medical image scanning protocol between the first protocol version and the second protocol version, and realize the automatic conversion of the medical image scanning protocol without personnel intervention.
In one embodiment, step S202 may specifically include: according to a source protocol version and a target protocol version which are included in each version conversion unit, determining a protocol version which a medical image scanning protocol needs to pass through for conversion between a first protocol version and a second protocol version, and determining a plurality of feasible version conversion paths; and determining the version conversion path with the shortest path in the plurality of feasible version conversion paths to obtain the version conversion path.
Taking the conversion of the medical image scanning protocol from the protocol version 1.2.2 to 1.1.1 as an example, the following description will be given:
If the version conversion unit described by the protocol conversion file is used, a plurality of feasible version conversion paths are formed, for example: route (1): 1.2.2- >1.2- >1- >1.1- >1.1.1;
Path (2): 1.2.2- >1.2- >1.2.1- >1.2- >1- >1.1- >1.1.1.
Among the paths (1) and (2), the version conversion path whose path is shortest is determined to be the path (1), and thus the version conversion path for converting from the protocol version 1.2.2 to 1.1.1 is 1.2- >1- >1.1- >1.1.1.
In the above embodiment, among the plurality of feasible version conversion paths, the version conversion path with the shortest path is determined, so that the protocol conversion efficiency can be improved.
Further, determining the version switch path with the shortest path among the plurality of feasible version switch paths may specifically include: and determining the version conversion path with the least number of protocol versions used for constructing the path from the plurality of feasible version conversion paths to obtain the version conversion path with the shortest path.
Among these, the number of protocol versions used for constructing the path (1) is 5, and the number of protocol versions used for constructing the path (2) is 7, so that it is possible to determine that the version conversion path with the shortest path among the two possible version conversion paths is (1); next, the path (1) is set as a version conversion path for converting from the protocol version 1.2.2 to 1.1.1.
In the above embodiment, the version conversion path whose path is shortest can be accurately determined according to the number of protocol versions used to construct the path.
In some scenarios, in order to seek more reasonable conversion, the protocol conversion is reversely converted and rolled back to a parent level common to two protocol versions, and then forward conversion is upgraded from the parent level to the child level, so as to obtain a version conversion path.
Based on this, step S202 includes: determining a protocol version which needs to be passed by a medical image scanning protocol from a first protocol version or a second protocol version to a common father-level protocol version according to a source protocol version and a target protocol version which are included in each version conversion unit, and obtaining a version conversion first sub-path; under the condition that the version conversion first sub-path corresponds to a first protocol version and a common parent protocol version, determining a protocol version which needs to be passed by a medical image scanning protocol from the common parent protocol version to a second protocol version according to a source protocol version and a target protocol version which are included by each version conversion unit, and obtaining a version conversion second sub-path; under the condition that the version conversion first sub-path corresponds to the second protocol version and the common parent protocol version, determining a protocol version which needs to be passed by the medical image scanning protocol from the common parent protocol version to the first protocol version according to the source protocol version and the target protocol version which are included by each version conversion unit, and obtaining the version conversion second sub-path; and obtaining a version conversion path according to the version conversion first sub-path and the version conversion second sub-path.
Wherein the common parent protocol version is a common parent protocol version of the first protocol version and the second protocol version.
Taking the first protocol version as 1.2.2 and the second protocol version as 1.1.1, and converting from the first protocol version to the common parent protocol version and converting from the common parent protocol version to the second protocol version as an example, the following description will be given:
The common parent protocol version of the protocol version 1.2.2 and the protocol version 1.1.1 is 1, if the version conversion path from the protocol version 1.2.2 to the protocol version 1 is determined to be 1.2- >1 according to the source protocol version and the target protocol version included by each version conversion unit, the version conversion path can be called as a version conversion first sub-path; if the version conversion path from the protocol version 1 to the protocol version 1.1.1 is determined to be 1- >1.1- >1.1.1 according to the source protocol version and the target protocol version included in each version conversion unit, the version conversion path may be referred to as a version conversion second sub-path.
The computer device may then splice the version-conversion first sub-path and the version-conversion second sub-path to obtain a version-conversion path 1.2.2- >1.2- >1- >1.1- >1.1.1 converted from protocol version 1.2.2 to protocol version 1.1.1.
It can be appreciated that reverse conversion is first rolled back to a parent level common to two protocol versions, and then forward conversion is upgraded from the parent level to the child level, so that a plurality of feasible version conversion paths can be obtained.
In one embodiment, step S204 may specifically include: sequentially adding corresponding unit conversion contents into the container according to the sequence of each target version conversion unit on the version conversion path; and converting the medical image scanning protocol between the first protocol version and the second protocol version according to the sequentially arranged units in the container.
After each target version unit is determined, the corresponding unit conversion content is added into the container in sequence according to the sequence of each target version conversion unit on the version conversion path. For example, a version transition path between protocol version 1.2.2 and protocol version 1.1.1: in 1.2.2- >1.2- >1- >1.1- >1.1.1, the version switch units ①、③、④ and ⑥ are in the following order on the version switch path: ①③④⑥. Then, according to the sequence, the unit conversion contents corresponding to the version conversion units ①③④⑥ are added into the container in sequence.
At this time, the unit conversion contents corresponding to the units of each target version are sequentially arranged in the container, and then the medical image scanning protocol is converted from the protocol version 1.2.2 to the protocol version 1.1.1 according to the unit conversion contents sequentially ordered in the container.
In the above embodiment, according to the sequence of the target version conversion units on the version conversion path, the corresponding unit conversion contents are sequentially added into the container, and the medical image scanning protocol is converted according to the sequentially ordered unit conversion contents in the container, so as to avoid conversion errors.
In one embodiment, step S203 may specifically include: the source protocol version and the target protocol version which are included in the version conversion unit are used as a protocol version pair of the version conversion unit; according to the consistency of the protocol version pair of each version conversion unit and two adjacent protocol versions in the version conversion path, determining a candidate version conversion unit in each version conversion unit to obtain a candidate version conversion unit set; in the candidate version conversion unit set, a target version conversion unit is determined.
The protocol version pair of the version conversion unit may be formed by a source protocol version and a target protocol version included in the version conversion unit. The two adjacent protocol versions in the version switch path are in sequence, i.e. the two adjacent protocol versions of the version switch path comprise a preceding protocol version and a following protocol version.
If the source protocol version of a certain protocol version pair is consistent with the previous protocol version and the target protocol version of the protocol version pair is consistent with the subsequent protocol version, determining that the protocol version pair of the version conversion unit has consistency with the two adjacent protocol versions of the version conversion path.
Taking the version conversion unit described by the protocol conversion file including ① to ⑥ shown in table 1 as an example introduction:
From the start identifier of each version conversion unit, the source protocol version and the target protocol version of each version conversion unit can be determined, for example, from the start identifier < item from= "1.2.2" to= "1.2" >, the source protocol version of version conversion unit ① can be determined to be 1.2.2, and the target protocol version to be 1.2, whereby the protocol version pair of version conversion unit ① is 1.2.2 and 1.2. Likewise, it is possible to determine that the protocol version pair of the version conversion unit ② is 1.2.2 and 1.2.1, the protocol version pair of the protocol conversion unit ③ is 1.2 and 1, the protocol version pair of the protocol conversion unit ④ is 1 and 1.1, the protocol version pair of the protocol conversion unit ⑤ is 1.2.1 and 1.2, and the protocol version pair of the protocol conversion unit ⑥ is 1.1 and 1.1.1.
In the case where the version conversion path between the protocol version 1.2.2 and the protocol version 1.1.1 is 1.2- >1.1, two adjacent protocol versions in the version conversion path are 1.2.2- >1.2, 1.2- >1, 1- >1.1 and 1.1- >1.1.1.
Taking two adjacent protocol versions 1.2.2- >1.2 as an example, according to the protocol version pairs of each version conversion unit, it can be determined that the protocol version pair of the version conversion unit ① is consistent with the two adjacent protocol versions 1.2.2- >1.2, and thus, the version conversion unit ① can be used as a candidate version conversion unit.
Taking two adjacent protocol versions 1.2- >1 as an example, according to the protocol version pairs of each version conversion unit, it can be determined that the protocol version pair of the version conversion unit ③ is consistent with the two adjacent protocol versions 1.2- >1, so that the version conversion unit ③ can be used as a candidate version conversion unit.
In the above manner, it may be determined that the version conversion unit as the candidate version conversion unit in table 1 includes ①③④⑥, thereby forming the candidate version conversion unit set.
In the case where the start identifier of each version conversion unit shown in table 1 only identifies the source protocol version and the target protocol version, each candidate version conversion unit in the candidate version conversion unit set may be directly converted as the target version.
In the above embodiment, according to the consistency between the protocol version pair of the version conversion unit and two adjacent protocol versions in the version conversion path, in each version conversion unit, the candidate version conversion unit is determined, so as to obtain the target version conversion unit, thereby avoiding error of the version conversion path and ensuring correct conversion of the medical image scanning protocol.
In one embodiment, determining the target version-conversion unit from the set of candidate version-conversion units comprises: under the condition that the candidate version conversion units in the candidate version conversion unit set do not carry the software parameters and the corresponding software parameter values, taking the candidate version conversion units as target version conversion units; under the condition that the candidate version conversion units in the candidate version conversion unit set carry software parameters and corresponding software parameter values, when the candidate version conversion units are determined to be suitable for medical image scanning application or medical image scanning platform according to the carried software parameters and corresponding software parameter values, the candidate version conversion units are taken as target version conversion units.
In some scenarios, the start identifier of the version switch unit may not only specify the source protocol version and the target protocol version, but also the software parameters and corresponding software parameter values. For example, in the scenario where the medical image scanning protocol is a nuclear magnetic resonance protocol, as shown in table 2, the start identifier of the version conversion unit ⑦ not only writes the source protocol version and the target protocol version, but also writes the software parameters and corresponding software parameter values: field= "3.0" model= "mr_val_2"; wherein field represents the magnetic field strength and model represents the software version number; likewise, the version conversion unit ⑧ also writes not only the source protocol version and the target protocol version, but also the software parameters and the corresponding software parameter values field= "1.5".
TABLE 2
The version conversion unit described in the protocol conversion file includes ⑦ to ⑦ shown in table 2Introduction to the example:
In the case where the version conversion path between protocol version 1.2.2 and protocol version 1.1.1 is 1.2- >1- >1.1- >1.1.1, according to the agreement between the protocol version pair of each version conversion unit and the adjacent two protocol versions in the version conversion path shown in table 2, it is possible to determine that the candidate version conversion unit set includes: ⑦⑧⑨⑩ 。
Version conversion units ⑦ and ⑧ shown in table 2, which describe a source protocol version and a target protocol version that are identical, but the software parameters and corresponding values carried by the two version conversion units are different, the software parameters and corresponding software parameter values carried by the version conversion unit ⑦ are field= "3.0", the model= "mr_val_2", and the software parameters and corresponding software parameter values carried by the version conversion unit ⑧ are field= "1.5".
According to the software parameters and corresponding software parameter values carried by the version conversion units ⑦ and ⑧, determining that the version conversion unit ⑦ is applicable to the medical image scanning application or the medical image scanning platform, and the version conversion unit ⑧ is not applicable to the medical image scanning application or the medical image scanning platform, wherein the version conversion unit ⑦ can be used as a target version conversion unit, and the version conversion unit ⑧ is not used as a target version conversion unit;
as to the inclusion of the candidate version-conversion unit set ⑨⑩ Since the several version conversion units do not carry software parameters and corresponding software parameter values, ⑨⑩/>, can be directly implementedAs a target version conversion unit.
In the above embodiment, when the candidate version conversion unit set determines the target version conversion unit, in combination with the software parameter carried by the version conversion unit and the corresponding software parameter value, it is determined whether the version conversion unit is suitable for the medical image scanning application or the medical image scanning platform, so as to avoid selecting the version conversion unit unsuitable for the medical image scanning application or the medical image scanning platform, which leads to the conversion error of the medical image scanning protocol.
In order to better understand the above method, an application example of the conversion method of the medical image scanning protocol of the present application is described in detail below with reference to fig. 4.
Steps S401 to S403 use the protocol version 1.2.2 of the medical image scanning protocol on the medical image scanning application as the first protocol version and the protocol version 1.1.1 of the medical image scanning protocol on the medical image scanning platform as the last protocol version.
Step S404, determining whether a plurality of feasible version conversion paths can be obtained according to the protocol conversion file stored in the medical image scanning platform; if not, the process proceeds to step S405, where a plurality of feasible version conversion paths are obtained according to the protocol conversion file stored in the medical image scanning application.
The step of obtaining a plurality of feasible version conversion paths according to the protocol conversion file stored in the medical image scanning platform or the protocol conversion file stored in the medical image scanning application comprises the following steps:
And acquiring each version conversion unit of the protocol conversion file description, and determining a protocol version which needs to be passed by the medical image scanning protocol from the protocol version 1.2.2 to the protocol version 1.1.1 according to the source protocol version and the target protocol version included in each version conversion unit to obtain a plurality of feasible version conversion paths.
Step S406, after obtaining a plurality of feasible version conversion paths, determining the version conversion path with the least number of protocol versions used for forming the path, obtaining the version conversion path with the shortest path, and converting the version conversion path with the shortest path from the protocol version 1.2.2 to the version conversion path with the protocol version 1.1.1 as the medical image scanning protocol.
After determining the version switch path, a target version switch unit may be determined, the determining the target version switch unit specifically including the steps of:
The source protocol version and the target protocol version which are included in the version conversion unit are used as a protocol version pair of the version conversion unit; according to the consistency of the protocol version pair of each version conversion unit and two adjacent protocol versions in the version conversion path, determining a candidate version conversion unit in each version conversion unit to obtain a candidate version conversion unit set; under the condition that the candidate version conversion units in the candidate version conversion unit set do not carry the software parameters and the corresponding software parameter values, taking the candidate version conversion units as target version conversion units; under the condition that the candidate version conversion units in the candidate version conversion unit set carry software parameters and corresponding software parameter values, when the candidate version conversion units are determined to be suitable for medical image scanning application or medical image scanning platform according to the carried software parameters and corresponding software parameter values, the candidate version conversion units are taken as target version conversion units.
Step S407, sequentially adding unit conversion contents corresponding to the target version conversion units into the container according to the sequence of the target version conversion units on the version conversion path; according to the unit conversion contents sequentially arranged in the container, the medical image scanning protocol is converted from the protocol version 1.2.2 to the protocol version 1.1.1, so that the protocol versions of the medical image scanning protocol on the medical image scanning application and the medical image scanning platform are consistent, and the medical image scanning application is successfully installed on the medical image scanning platform (step S408).
In this embodiment, a medical image scanning protocol version on a medical image scanning application is used as a first protocol version, and a medical image scanning protocol version on a medical image scanning platform is used as a second protocol version; determining a protocol version which needs to be passed by a medical image scanning protocol for conversion between a first protocol version and a second protocol version according to a source protocol version and a target protocol version which are included in each version conversion unit described by a protocol conversion file, and obtaining a version conversion path; determining a target version conversion unit in each version conversion unit according to two adjacent protocol versions in the version conversion path; according to the sequence of each target version conversion unit on the version conversion path, converting the medical image scanning protocol between the first protocol version and the second protocol version, so that the protocol versions of the medical image scanning protocol on the medical image scanning application and the medical image scanning platform are consistent, and interaction errors between the medical image scanning application and the medical image scanning platform are avoided; in addition, even if the protocol version of the medical image scanning protocol on the medical image scanning platform changes, a developer is not required to manufacture the medical image scanning protocol of the corresponding protocol version for the medical image scanning application, and the computer equipment can automatically form a version conversion path according to the version conversion units described by the protocol conversion file and the unit conversion contents corresponding to the version conversion units, automatically determine the unit conversion contents required by the conversion of the medical image scanning protocol between the first protocol version and the second protocol version, and realize the automatic conversion of the medical image scanning protocol without personnel intervention.
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.
In one embodiment, as shown in fig. 5, there is provided a conversion device of a medical image scanning protocol, including:
The protocol version determining module 501 is configured to take a medical image scanning protocol version on a medical image scanning application as a first protocol version and take a medical image scanning protocol version on a medical image scanning platform as a second protocol version;
The path obtaining module 502 is configured to obtain each version conversion unit described by the protocol conversion file, determine a protocol version that needs to be passed by the medical image scanning protocol for conversion between the first protocol version and the second protocol version according to a source protocol version and a target protocol version included by each version conversion unit, and obtain a version conversion path;
A target unit determining module 503, configured to determine a target version conversion unit in each version conversion unit according to two adjacent protocol versions in the version conversion path;
A conversion module 504, configured to convert the medical image scanning protocol between the first protocol version and the second protocol version according to the order of each of the target version conversion units on the version conversion path.
In one embodiment, the path obtaining module 502 is further configured to determine, according to a source protocol version and a target protocol version included in each version conversion unit, a protocol version that the medical image scanning protocol needs to undergo for conversion between the first protocol version and the second protocol version, and determine a plurality of feasible version conversion paths; and determining the version conversion path with the shortest path in the plurality of feasible version conversion paths to obtain the version conversion path.
In one embodiment, the path obtaining module 502 is further configured to determine, from the plurality of possible version conversion paths, a version conversion path with the least number of protocol versions used for forming the path, and obtain a version conversion path with the shortest path.
In one embodiment, the path obtaining module 502 is further configured to determine, according to a source protocol version and a target protocol version included in each version conversion unit, a protocol version that needs to be passed by the medical image scanning protocol to be converted from the first protocol version or the second protocol version to a common parent protocol version, so as to obtain a version-converted first sub-path; the common parent protocol version is a common parent protocol version of the first protocol version and the second protocol version; under the condition that the version conversion first sub-path corresponds to the first protocol version and the common parent protocol version, determining a protocol version which the medical image scanning protocol needs to pass through when the medical image scanning protocol is converted from the common parent protocol version to the second protocol version according to a source protocol version and a target protocol version which are included by each version conversion unit, and obtaining a version conversion second sub-path; under the condition that the version conversion first sub-path corresponds to the second protocol version and the common parent protocol version, determining a protocol version which needs to be passed by the medical image scanning protocol from the common parent protocol version to the first protocol version according to a source protocol version and a target protocol version which are included by each version conversion unit, and obtaining a version conversion second sub-path; and converting the first sub-path and the second sub-path according to the version to obtain a version conversion path.
In one embodiment, the conversion module 504 is configured to sequentially add the corresponding unit conversion content to the container according to the order of each of the target version conversion units on the version conversion path; and converting the medical image scanning protocol between the first protocol version and the second protocol version according to the sequentially arranged units in the container to convert the content.
In one embodiment, the target unit determining module 503 is further configured to use the source protocol version and the target protocol version included in the version conversion unit as a protocol version pair of the version conversion unit; according to the consistency of the protocol version pair of each version conversion unit and two adjacent protocol versions in the version conversion path, determining a candidate version conversion unit in each version conversion unit to obtain a candidate version conversion unit set; and determining a target version conversion unit in the candidate version conversion unit set.
In one embodiment, the target unit determining module 503 is further configured to, in a case where the candidate version conversion units in the candidate version conversion unit set do not carry the software parameter and the corresponding software parameter value, take the candidate version conversion unit as the target version conversion unit; in the case that the candidate version conversion units in the candidate version conversion unit set carry software parameters and corresponding software parameter values, when the candidate version conversion units are determined to be suitable for the medical image scanning application or the medical image scanning platform according to the carried software parameters and corresponding software parameter values, the candidate version conversion units are taken as target version conversion units.
For specific limitations of the conversion device of the medical image scanning protocol, reference may be made to the above limitation of the conversion method of the medical image scanning protocol, and no further description is given here. The modules in the conversion device of the medical image scanning protocol can be realized in whole or in part by software, hardware and a 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, the internal structure of which may be as shown in FIG. 6. The computer device includes a processor, a memory, and a network interface connected by a system bus. 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 the conversion data of the medical image scanning protocol. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer equipment also comprises an input/output interface, wherein the input/output interface is a connecting circuit for exchanging information between the processor and the external equipment, and the input/output interface is connected with the processor through a bus and is called as an I/O interface for short. The computer program is executed by a processor to implement a method of converting a medical image scanning protocol.
It will be appreciated by those skilled in the art that the structure shown in FIG. 6 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory storing a computer program and a processor implementing the steps of the method embodiments described above when the processor executes the computer program.
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 respective method embodiments described above.
In one embodiment, a computer program product is provided, on which a computer program is stored, which computer program is executed by a processor for performing the steps of the various method embodiments described above.
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, storage, database, or other medium used in 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, or the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory. By way of illustration, and not limitation, RAM can be in various forms such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), etc.
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 foregoing examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.
Claims (10)
1. A method for converting a medical image scanning protocol, the method comprising:
Taking the medical image scanning protocol version on the medical image scanning application as a first protocol version, and taking the medical image scanning protocol version on the medical image scanning platform as a second protocol version;
Each version conversion unit of the protocol conversion file description is obtained, and according to a source protocol version and a target protocol version included in each version conversion unit, a protocol version required to be passed by a medical image scanning protocol for conversion between the first protocol version and the second protocol version is determined, so that a version conversion path is obtained, and the method comprises the following steps: determining that the medical image scanning protocol is converted from one protocol version of the first protocol version and the second protocol version to a protocol version needing to be passed through by a common father-level protocol version to obtain a version conversion first sub-path, and determining that the medical image scanning protocol is converted from the common father-level protocol version to another protocol version to obtain a version conversion second sub-path; according to the version conversion first sub-path and the version conversion second sub-path, a version conversion path is obtained; the common parent protocol version is a common parent protocol version of the first protocol version and the second protocol version;
determining a target version conversion unit in each version conversion unit according to two adjacent protocol versions in the version conversion path;
and converting the medical image scanning protocol between the first protocol version and the second protocol version according to the sequence of each target version conversion unit on the version conversion path.
2. The method of claim 1, wherein said converting the first sub-path and said converting the second sub-path according to the version to obtain a version-converted path comprises:
according to the version conversion first sub-path and the version conversion second sub-path, a feasible version conversion path is obtained;
And after the plurality of feasible version conversion paths are obtained, determining the version conversion path with the shortest path in the plurality of feasible version conversion paths to obtain the version conversion path.
3. The method of claim 2, wherein determining a shortest one of the plurality of possible version switch paths comprises:
And determining the version conversion path with the least number of protocol versions used for forming the path from the plurality of feasible version conversion paths to obtain the version conversion path with the shortest path.
4. The method of claim 1, wherein the version-conversion second sub-path corresponds to the second protocol version if the version-conversion first sub-path corresponds to the first protocol version; in the case that the version-conversion first sub-path corresponds to the second protocol version, the version-conversion second sub-path corresponds to the first protocol version.
5. The method of claim 1, wherein said converting the medical image scan protocol between the first protocol version and the second protocol version in the order of each of the target version conversion units on the version conversion path comprises:
sequentially adding corresponding unit conversion contents into a container according to the sequence of each target version conversion unit on the version conversion path;
and converting the medical image scanning protocol between the first protocol version and the second protocol version according to the sequentially arranged units in the container to convert the content.
6. The method according to any one of claims 1 to 5, wherein determining a target version conversion unit from two adjacent protocol versions in the version conversion path in each of the version conversion units includes:
The method comprises the steps that a source protocol version and a target protocol version which are included in a version conversion unit are used as a protocol version pair of the version conversion unit;
according to the consistency of the protocol version pair of each version conversion unit and two adjacent protocol versions in the version conversion path, determining a candidate version conversion unit in each version conversion unit to obtain a candidate version conversion unit set;
And determining a target version conversion unit in the candidate version conversion unit set.
7. The method of claim 6, wherein the determining a target version-conversion unit from the set of candidate version-conversion units comprises:
Under the condition that the candidate version conversion units in the candidate version conversion unit set do not carry software parameters and corresponding software parameter values, taking the candidate version conversion units as target version conversion units;
in the case that the candidate version conversion units in the candidate version conversion unit set carry software parameters and corresponding software parameter values, when the candidate version conversion units are determined to be suitable for the medical image scanning application or the medical image scanning platform according to the carried software parameters and corresponding software parameter values, the candidate version conversion units are taken as target version conversion units.
8. A device for converting a medical image scanning protocol, the device comprising:
The protocol version determining module is used for taking the medical image scanning protocol version on the medical image scanning application as a first protocol version and taking the medical image scanning protocol version on the medical image scanning platform as a second protocol version;
the path obtaining module is configured to obtain each version conversion unit described by the protocol conversion file, determine a protocol version that needs to be passed by the medical image scanning protocol for conversion between the first protocol version and the second protocol version according to a source protocol version and a target protocol version included by each version conversion unit, and obtain a version conversion path, where the path obtaining module includes: determining that the medical image scanning protocol is converted from one protocol version of the first protocol version and the second protocol version to a protocol version needing to be passed through by a common father-level protocol version to obtain a version conversion first sub-path, and determining that the medical image scanning protocol is converted from the common father-level protocol version to another protocol version to obtain a version conversion second sub-path; according to the version conversion first sub-path and the version conversion second sub-path, a version conversion path is obtained; the common parent protocol version is a common parent protocol version of the first protocol version and the second protocol version;
The target unit determining module is used for determining a target version conversion unit in each version conversion unit according to two adjacent protocol versions in the version conversion path;
the conversion module is used for converting the medical image scanning protocol between the first protocol version and the second protocol version according to the sequence of each target version conversion unit on the version conversion path.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the method of any one of claims 1 to 7 when executing the computer program.
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 method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211318487.9A CN115695570B (en) | 2022-10-26 | 2022-10-26 | Method, device, equipment and storage medium for converting medical image scanning protocol |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211318487.9A CN115695570B (en) | 2022-10-26 | 2022-10-26 | Method, device, equipment and storage medium for converting medical image scanning protocol |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115695570A CN115695570A (en) | 2023-02-03 |
| CN115695570B true CN115695570B (en) | 2024-05-24 |
Family
ID=85099597
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211318487.9A Active CN115695570B (en) | 2022-10-26 | 2022-10-26 | Method, device, equipment and storage medium for converting medical image scanning protocol |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115695570B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110570483A (en) * | 2019-08-08 | 2019-12-13 | 上海联影智能医疗科技有限公司 | scanning method, scanning device, computer equipment and storage medium |
| WO2020108183A1 (en) * | 2018-11-30 | 2020-06-04 | 中兴通讯股份有限公司 | Method, apparatus and device for generating differential upgrade package |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9917928B2 (en) * | 2014-11-24 | 2018-03-13 | Fortinet, Inc. | Network address translation |
| EP3396572A1 (en) * | 2017-04-24 | 2018-10-31 | Siemens Healthcare GmbH | Method for operating an image recording device, image recording device, computer program and electronically readable data carrier |
| EP3800480B1 (en) * | 2019-10-01 | 2023-11-29 | Siemens Healthcare GmbH | Mr measurement protocol conversion |
-
2022
- 2022-10-26 CN CN202211318487.9A patent/CN115695570B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020108183A1 (en) * | 2018-11-30 | 2020-06-04 | 中兴通讯股份有限公司 | Method, apparatus and device for generating differential upgrade package |
| CN110570483A (en) * | 2019-08-08 | 2019-12-13 | 上海联影智能医疗科技有限公司 | scanning method, scanning device, computer equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| CT Thorax lavdose - En sammenligning av et organdosemodulerings program X-CARE og vismut beskyttelse;Mikael Oseberg等;《Radiography Open》;20171231;全文 * |
| 基于特征关键字的多协议数据流转换方法;林霞;蔡声镇;吴允平;卢宇;关健;吴燕;陈锦凯;;计算机工程;20110305(第05期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115695570A (en) | 2023-02-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111428462B (en) | Communication protocol template construction method and terminal equipment | |
| CN108829584B (en) | Service logic interface mock test method and system | |
| CN110046091B (en) | Automatic test method and device | |
| CN110554958A (en) | Graph database testing method, system, device and storage medium | |
| CN111324577B (en) | Yml file reading and writing method and device | |
| CN110968509B (en) | Method and system for batch customizing of variables | |
| CN110543427B (en) | Test case storage method and device, electronic equipment and storage medium | |
| CN113608692A (en) | Method, system, equipment and medium for verifying data consistency of storage system | |
| US11422917B2 (en) | Deriving software application dependency trees for white-box testing | |
| CN113420520B (en) | Integrated circuit device design simulation method, device, apparatus and readable storage medium | |
| CN114546432A (en) | Multi-application deployment method, device, equipment and readable storage medium | |
| CN111209188A (en) | Testing method and device for distributed storage system | |
| CA3138761A1 (en) | Method, device, computer equipment and storage medium for verifying inter-system data admission | |
| CN115695570B (en) | Method, device, equipment and storage medium for converting medical image scanning protocol | |
| CN114238085A (en) | Interface testing method and device, computer equipment and storage medium | |
| CN112511341B (en) | Network automation fault positioning method, terminal and storage medium | |
| CN116629015A (en) | Digital twin task processing method, device, equipment and storage medium | |
| CN110147313A (en) | A kind of log-output method and device | |
| CN116932358A (en) | Test data construction method and device and computer equipment | |
| CN115080444A (en) | Test case conversion method and device, electronic equipment and storage medium | |
| CN111736848A (en) | Packet conflict positioning method and device, electronic equipment and readable storage medium | |
| CN115840715B (en) | Software test management method, device and storage medium | |
| CN110795297B (en) | Electronic equipment testing method and device | |
| CN110711389B (en) | Data processing method, device, equipment and computer readable medium | |
| CN110825631B (en) | Test method, test device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |