CN115691768B - DICOM RT file automatic transmission method and system based on cloud platform - Google Patents
DICOM RT file automatic transmission method and system based on cloud platform Download PDFInfo
- Publication number
- CN115691768B CN115691768B CN202310012060.4A CN202310012060A CN115691768B CN 115691768 B CN115691768 B CN 115691768B CN 202310012060 A CN202310012060 A CN 202310012060A CN 115691768 B CN115691768 B CN 115691768B
- Authority
- CN
- China
- Prior art keywords
- dicom
- file
- information
- equipment
- service
- 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
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The invention discloses a DICOM RT file automatic transmission method and a DICOM RT file automatic transmission system based on a cloud platform, wherein hospital equipment and a cloud platform TPS are configured according to user needs, automatic sending configuration is supported, after the equipment is configured, a doctor can automatically upload CT or DICOM target area files in a hospital to the TPS of the cloud platform, meanwhile, the single DICOM target area file is supported to be transmitted in a supplementing way, multiple TPSs are adapted, the cloud platform also supports the DICOM plan files made by a physicist to be automatically sent to a hospital accelerator workstation or a radiotherapy informatization system, the TPS plan screenshot is supported to be sent to a hospital front-end processor and supported to be directly downloaded in the cloud platform, the purpose of reducing the workload of the doctor and the physicist is achieved, and safe, reliable, convenient and fast experience is brought to the user.
Description
Technical Field
The invention belongs to the technical field of medical communication, and particularly relates to a DICOM RT file automatic transmission method and system based on a cloud platform.
Background
DICOM is one of the most widespread medical information standards, serving doctors and patients, and more so, the standard for medical imaging to work effectively. The DICOM file is the most primitive image data, and contains the most comprehensive, detailed and abundant information. Not only can adjust the window width, the window level, the layer thickness and the position, but also can measure the size of the focus. The radiation diagnosis and treatment device is widely applied to radiation medical treatment and radiation diagnosis and treatment equipment at present.
DICOM files scanned by equipment such as CT, nuclear magnetism and the like are uploaded to a server, and a doctor or a physicist draws a target area or makes a plan on a TPS planning system at any time. After the operation on the TPS planning system, the DICOM planning file is transmitted back to a hospital accelerator workstation or a radiotherapy information management system (OIS) to drive an accelerator to treat the patient.
The existing DICOM RT file is mainly transmitted in the following ways: the most original form is through the transfer of the U disk or the recording of the optical disk; with the construction of the network in the hospital, a form of sharing folders is adopted; after the DICOM protocol links the devices, a manual pushing mode is adopted;
doctors or physicists need to read the films at any time on the workstation, the previous scheme cannot bring safe, reliable, convenient and quick experience to users, especially the risks of incomplete transmission and information leakage can occur, and the clinical requirements of rigidness, standardization, safety and high efficiency cannot be met. Therefore, the conventional method for transmitting DICOM RT files has the following problems:
1. the transmission is unsafe, and the risk of patient information leakage is easily caused;
2. the transmission is not strict, the file copy is incomplete, and the node is selected by manual pushing, so that the risk of loss is caused;
3. the transmission is not efficient, the operation of doctors or physicists is complicated, and redundant workload is increased;
4. the transmission is not standard, and if the device does not support the USB port or the optical disc drive, the transmission cannot be performed.
Disclosure of Invention
In order to overcome the defects of the prior art, the application provides a DICOM RT file automatic transmission method and system based on a cloud platform.
The application of the first aspect provides a DICOM RT file automatic transmission method based on a cloud platform, which is characterized in that: the method comprises the following steps:
step 1: maintaining equipment database information;
step 2: DICOM information acquisition and automatic equipment sending configuration are carried out through a DICOM matching processor based on the equipment database information;
and 3, step 3: processing the DICOM file through a multi-TPS adaptive processor;
and 4, step 4: constructing DICOM file transmission service;
and 5: building DICOM file analysis service;
and 6: and automatically transmitting the DICOM file, wherein a corresponding analysis step is triggered after the DICOM file is monitored through the DICOM file analysis service in the step 5, then a DICOM matching processor in the step 2 is called to analyze node information of both interaction sides and equipment is automatically sent and configured, a multi-TPS adaptation processor in the step 3 is called to carry out TPS adaptation, and finally, the DICOM file transmission service in the step 4 is called to select a corresponding file transmission service to carry out automatic DICOM file transmission.
In some optional implementations of some embodiments, the step 1 includes:
establishing an in-hospital equipment basic information table, a cloud platform TPS information table and a common file information table in a database;
and (3) developing the base service of the devices in the hospital and the TPS information service of the cloud platform, and performing input and configuration according to the devices in the hospital.
In some optional implementations of some embodiments, the step 2 includes a DICOM node information obtaining step of the device and a device automatic sending configuration step;
the equipment DICOM information acquisition step is as follows: transmitting a parameter AE Title, analyzing the parameter AE Title based on a DICOM matching processor, matching according to the equipment database information, and acquiring DICOM node information of corresponding equipment;
the automatic sending configuration step of the equipment comprises the following steps: acquiring hospital information of corresponding equipment, acquiring DICOM node information of all equipment in the hospital according to hospital codes, and judging whether the equipment can automatically transmit according to the automatic transmission information.
In some optional implementations of some embodiments, the step 3 includes:
analyzing UID (user identification) under a sequence corresponding to a target area field in a DICOM target area file exported by TPS (TPS), and generating a change relation table according to the TPS exported target area file;
and converting the type of the TPS according to the change relation table, and processing the DICOM file.
In some optional implementations of some embodiments, the step 4 includes an image sending service dcmstoresscu, an image querying service dcmfondscu, an image forwarding service DcmMoveSCU, an image obtaining service dcmmegetscu;
the image sending service DcmStoreSCU encapsulates the StoreSCU, and the bottom layer calls a C-STORE protocol;
the image query service DcmFindSCU packages the FindSCU, and the bottom layer calls a C-FIND protocol;
the image forwarding service DcmMoveSCU encapsulates the MoveSCU, and the bottom layer calls a C-MOVE protocol;
the image acquisition service DcmGetSCU encapsulates the GetSCU, and the bottom layer calls a C-GET protocol.
In some optional implementation manners of some embodiments, the step 5 includes a DICOM mutual party information parsing step, a DICOM file type information parsing step, and a file monitoring parsing step;
the file monitoring and analyzing steps are as follows: when the DICOM file is monitored by the DICOM file monitor, triggering and executing a DICOM mutual party information analysis step/a DICOM file type information analysis step;
the DICOM interactive two-party information analysis step is as follows: determining information of two service interaction parties by analyzing an initiator and a receiver of a protocol data unit in a DICOM upper layer protocol;
the DICOM file type information analysis step is as follows: determining the DICOM file type by analyzing Tag in the DICOM file, wherein the DICOM file type comprises CT, MR, RTSTRUCT, RTPLAN, RTDOSE, RTIMAGE and the like.
In some optional implementations of some embodiments, the step 6 includes a DICOM target area file automatic transmission step, where the DICOM target area file automatic transmission step is:
when the DICOM file listener of the DICOM file parsing service in the step 5 monitors the DICOM file, AE Title of the equipment of the two interacting parties is obtained by parsing the information of the two interacting parties of the DICOM, and then the DICOM information obtaining step in the step 2 is called to obtain DICOM node information of the equipment of the two interacting parties;
and if the AE Title of the equipment in the hospital is analyzed, calling an equipment automatic sending configuration step in the step 2, and acquiring DICOM information and automatic sending information of a cloud platform TPS corresponding to the hospital:
if the AE Title of the cloud platform equipment is analyzed, the equipment automatic sending configuration step in the step 2 is called to obtain DICOM node information and automatic sending information of corresponding in-hospital equipment;
after the automatic transmission equipment information is analyzed, the DICOM file type information analyzing step in the step 5 is required to be called to analyze the file type, and when the file type is RTSTRUCT, a TPS type conversion method of a multi-TPS adaptation processor in the step 3 is required to be called to carry out TPS adaptation;
and finally, calling an image forwarding service DcmMoveSCU of the DICOM file transmission service in the step 4, acquiring DICOM node information of the two interactive devices according to the step 5, and automatically transmitting the DICOM target area file to the in-hospital device/cloud platform TPS.
In some optional implementations of some embodiments, the step 6 further includes a DICOM plan file automatic transmission step, where the DICOM plan file automatic transmission step is:
calling AE Title of the TPS of the cloud platform analyzed in the step 5, then calling an equipment automatic sending configuration step in the step 2, and acquiring DICOM node information and automatic sending information of corresponding in-hospital equipment;
after the automatically transmitted equipment information is analyzed, the DICOM file type information analyzing step in step 5 is also required to be called to analyze the file type. And when the file type is RTPLAN, calling the image forwarding service DcmMoveSCU in the step 4, and automatically transmitting the DICOM plan file to the in-hospital equipment according to the DICOM node information of the interactive two-party equipment obtained in the step 5.
In some optional implementation manners of some embodiments, the method further includes setting up a common file transmission service, where the common file transmission service includes a cloud platform TPS file monitoring service, a file transmission center service, a cloud platform file receiving service, and a front-end processor file receiving service.
The application of the second aspect provides a DICOM RT file automatic transmission system based on a cloud platform, which comprises a data information maintenance module, a data transmission module and a data transmission module, wherein the data information maintenance module is used for maintaining equipment database information;
the DICOM matching processing module is used for performing DICOM information acquisition and automatic equipment sending configuration on the basis of the equipment database information through a DICOM matching processor;
the multi-TPS adaptation module is used for processing the DICOM file through the multi-TPS adaptation processor;
the DICOM file transmission service module is used for constructing a DICOM file transmission service;
the DICOM file analysis service module is used for building DICOM file analysis service;
and the DICOM file automatic transmission module is used for automatically transmitting the DICOM file, monitoring that the DICOM file triggers a corresponding analysis step through a DICOM file analysis service in the DICOM file analysis service module, calling a DICOM matching processor of the DICOM matching processing module to analyze node information of two interactive parties and automatically transmit and configure equipment, calling a multi-TPS adaptation processor of the multi-TPS adaptation module to carry out TPS adaptation, and finally calling the DICOM file transmission service in the DICOM file transmission service module to select a corresponding file transmission service to carry out DICOM file automatic transmission.
In a third aspect of the embodiments of the present invention, an electronic device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the method when executing the computer program.
In a fourth aspect of the embodiments of the present invention, a computer-readable storage medium is provided, which stores a computer program, which when executed by a processor implements the steps of the method.
The invention has the beneficial effects that:
1. and establishing a private network by using the VPN, getting through the outside of the hospital and the online and offline, and carrying out DICOM RT file encryption transmission.
2. And developing a device management function, and maintaining the devices which support the DICOM protocol in and out of the hospital to a cloud platform. Meanwhile, a switch for automatically sending or not is configured to control the automatic sending of the DICOM file of the equipment.
3. And (4) directly uploading CT files in the support hospital to TPS of the cloud platform, and drawing a target area and making a plan outside the support hospital.
4. And supporting in-hospital drawing, uploading the CT and DICOM target area files to the TPS of the cloud platform together, performing out-of-hospital planning, and if the target area files do not meet the standard, similarly supporting re-uploading the DICOM target area files.
5. Different types of TPS are supported to upload CT and DICOM target area files, if the TPS in a hospital is inconsistent with the TPS of a cloud platform, matching rules can be made for the different types of TPS, and automatic association of the DICOM target area files and the CT is achieved.
6. The DICOM RT file which supports the TPS of the cloud platform to do is automatically sent to a hospital accelerator workstation or a radiotherapy information management system, and an accelerator is driven to treat the patient.
7. The non-DICOM file generated by the TPS supported on the cloud platform is automatically sent to a hospital front-end processor or displayed on the cloud platform for a doctor or a physicist to download.
Drawings
FIG. 1 is a general flow diagram of the present invention.
Fig. 2 is a DICOM file transfer service encapsulation relation diagram.
Fig. 3 is a DICOM file parsing service relationship diagram.
Fig. 4 is a flow chart of DICOM RT file transfer.
Fig. 5 is a flowchart of a general file transfer.
Fig. 6 is a schematic block diagram of the system of the present invention.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be embodied in various forms and should not be limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
In a first aspect, the application provides a DICOM RT file automatic transmission method based on a cloud platform, as shown in fig. 1: comprises the following steps of 1-6:
step 1: maintaining equipment database information;
in some optional implementations of some embodiments, the step 1 includes:
establishing an in-hospital equipment basic information table, a cloud platform TPS information table and a common file information table in a database;
and (3) developing the base service of the devices in the hospital and the TPS information service of the cloud platform, and performing input and configuration according to the devices in the hospital.
The device information is mainly divided into a hospital device and a cloud platform TPS.
The in-hospital equipment comprises equipment supporting DICOM protocol, such as a positioning CT machine, an accelerator workstation, a radiotherapy informatization system, a front-end processor and the like, wherein an IP address, a port number and AE Title are required to be filled, as the IP address, the port number and the AE Title are important identifiers of the in-hospital equipment, and DICOM RT files are transmitted according to the three items. And whether the identification is automatically sent or not is judged, and the user can set the identification according to the requirement. Besides, the relevant configurations such as the model of the equipment, the hospital, etc. are provided, as shown in the following table 1:
table 1: in-hospital device information
Cloud platform TPS includes Pinnacle3, eclipse, monaco, etc. Where IP address, port number, AE Title are mandatory to fill out as this is an important identity for TPS. Besides, there are version numbers, the hospitals, and other related configurations, as shown in table 2 below:
table 2: cloud platform TPS information
Further, maintaining the device database information specifically includes: establishing an in-hospital device basic information table device _ base _ info, a cloud platform TPS information table device _ TPS _ info and a common file information table device _ TPS _ file in a database, developing an in-hospital device basic service device and a cloud platform TPS information service device tpsService, and performing entry and configuration according to existing hospital devices.
And 2, step: the DICOM information acquisition and automatic equipment sending configuration are carried out through a DICOM matching processor based on the equipment database information;
in some optional implementations of some embodiments, the step 2 includes a DICOM node information obtaining step of the device and a device automatic sending configuration step;
the method for acquiring the DICOM information comprises the following steps: transmitting a parameter AE Title, analyzing the parameter AE Title based on a DICOM matching processor, matching according to the information of the equipment database, and acquiring DICOM node information of corresponding equipment;
the automatic sending configuration step of the equipment comprises the following steps: acquiring hospital information of corresponding equipment, acquiring DICOM node information of all equipment in the hospital according to hospital codes, and judging whether the equipment can automatically transmit according to the automatic transmission information.
Wherein, the DICOM matching processor is HosDeviceHandler, the equipment DICOM information acquisition step is GetDeviceDcmInfo, and the equipment automatically sends and configures as AutoSendDmToNode;
further, when the DICOM information obtaining step is executed, a parameter AE Title may also be introduced, and the DICOM matching processor HosDeviceHandler may analyze the parameter and perform matching according to dcm _ aet (see table 2) from the database, so as to obtain DICOM node information (IP address, port number, AE Title) of the corresponding device.
Further, when the device automatic sending configuration step is executed, the parameter AE Title can be transmitted, the DICOM matching processor HosDeviceHandler analyzes the parameter and matches the parameter from the database according to dcm _ aet (see table 2), hospital information (hospital code and hospital name) of the corresponding device is firstly obtained, DICOM node information (IP address, port number and AE Title) of all devices in the hospital is obtained according to the hospital code, and whether the device can automatically send is judged according to auto _ send information.
And step 3: processing the DICOM file through a multi-TPS adaptive processor;
in some optional implementations of some embodiments, the step 3 includes:
analyzing UIDs under sequences corresponding to target area fields in DICOM target area files exported by TPS, and generating a change relation table according to the TPS exported target area files;
and converting the type of the TPS according to the change relation table, and processing the DICOM file.
Wherein, the multi-TPS adaptive processor is a MultiTpsHandler, and TPS which is mainstream in the market is Pinnacle, eclipse and Monaco. The cloud platform TPS adopts Pinnaacle as a default, and if the TPS in the hospital is Monaco or Pinnaacle, the processor does not need to process the file. If the TPS in the hospital is Eclipse, a method ConvertTpsType for converting the TPS type needs to be called, firstly, the related DICOM data of the database are cleared, and then the data are stored again.
Specifically, the multi-TPS adaptive processor provides a method ParseReferencedSeries for analyzing related DICOM target area files, and the method can analyze Series Instance UIDs under RT Referenced Series sequences, reflected SOP Instance UIDs under content Image Sequence and Series Instance UIDs under RT Series in the DICOM target area files generated and loaded by mainstream TPS equipment (Pinnarcle 3, eclipse and Monaco) on the market. And exporting a target area file once every time the main flow TPS is generated, and then generating a field change relation table.
Table 3: TPS derived target area file field change relation table
Specifically, the multi-TPS adaptation processor provides a TPS type conversion method ConvertetTpsType, and the method processes the DICOM file according to a field change relation table returned by a TPS derived target area file analysis method ParseReferencedSeries.
If the Pinnacle3 and the Monaco are directly converted into each other, the files do not need to be processed, and only new DICOM target area data need to be added into the database. If Pinnacle3, monaco and Eclipse are converted, data collision can be caused because the Series input UID under RT Series is not changed and is a unique identifier. Therefore, old DICOM target data in the database needs to be deleted, and new DICOM target data needs to be added into the database.
In the case of other types of TPS (e.g. XiO), special treatment is required. All the three items of data XiO will change, and for this situation, all the old DICOM data in the database will be deleted, and then the new DICOM data will be added into the database.
And 4, step 4: building DICOM file transmission service;
in some optional implementations of some embodiments, the step 4 includes an image sending service dcmstoreSCU, an image querying service dcmfondSCU, an image forwarding service dcmmoveSCU, an image obtaining service dcmcgetSCU;
the image sending service DcmStoreSCU encapsulates a StoreSCU, and a C-STORE protocol is called at the bottom layer;
the image query service DcmFindSCU packages the FindSCU, and the bottom layer calls a C-FIND protocol;
the image forwarding service DcmMoveSCU encapsulates the MoveSCU, and the bottom layer calls the C-MOVE protocol;
the image acquisition service DcmGetSCU encapsulates the GetSCU, and the bottom layer calls a C-GET protocol.
Further, the specific packaging relationship of the image sending service dcmstoresccu, the image querying service DcmFindSCU, the image forwarding service DcmMoveSCU, and the image acquiring service dcmcgetscu is shown in fig. 2.
And 5: building DICOM file analysis service;
in some optional implementation manners of some embodiments, the step 5 includes a DICOM mutual party information parsing step, a DICOM file type information parsing step, and a file monitoring parsing step;
the file monitoring and analyzing steps are as follows: when the DICOM file is monitored by the DICOM file monitor, triggering and executing a DICOM mutual party information analysis step/a DICOM file type information analysis step;
the DICOM interactive two-party information analysis step is as follows: determining information of both service interaction parties by analyzing an initiator and a receiver of a protocol data unit in a DICOM upper layer protocol;
the DICOM file type information analysis step is as follows: and determining the DICOM file type by analyzing Tag in the DICOM file, wherein the DICOM file type comprises CT, MR, RTSTRUCT, RTPLAN, RTDOSE, RTIMAGE and the like.
Further, as shown in fig. 3, the DICOM file parsing service parses DICOM interaction party information parsedmsendandreceive, which is information that determines two parties of service interaction by parsing an initiator Calling AE Title and a receiver Called AE Title of a protocol data unit a-ASSOCIATE-RQ PDU in a DICOM upper protocol a-ASSOCIATE. For example, the Calling AE Title is pinst 831FIR (AE Title of the premises equipment), and the Called AE Title is JDS _ STR _ SCP (AE Title of the cloud platform DICOM file parsing service storeparsedcfilescp). And then, calling a GetDeviceDcmInfo method of the hospital equipment and the DICOM matching processor HosDeviceHandler in the step 2 to acquire DICOM node information (IP address, port number and AE Title) of the equipment of the two interactive parties.
Specifically, the DICOM file type information parsing step parsedcmmodulity is to determine the DICOM file type for modulity by parsing Tag in the DICOM file, and the type is classified into CT, MR, RTSTRUCT, RTPLAN, RTDOSE, RTIMAGE and the like.
Step 6: and (3) automatically transmitting the DICOM file, wherein the DICOM file is monitored through the DICOM file analysis service in the step (5), then the corresponding analysis step is triggered, then the DICOM matching processor in the step (2) is called to analyze the node information of the two interactive parties and carry out equipment automatic sending configuration, the multi-TPS matching processor in the step (3) is called to carry out TPS matching, and finally the DICOM file transmission service in the step (4) is called to select the corresponding file transmission service to carry out the automatic transmission of the DICOM file.
In some optional implementations of some embodiments, the step 6 includes a DICOM target volume file automatic transmission step, where the DICOM target volume file automatic transmission step is:
as shown in fig. 4, when the DICOM file listener of the DICOM file parsing service in step 5 monitors a DICOM file, AE Title of the interactive both-party device is obtained by parsing the DICOM interactive both-party information, and then the DICOM information obtaining step in step 2 is invoked to obtain DICOM node information of the interactive both-party device;
and if the AE Title of the equipment in the hospital is analyzed, calling an equipment automatic sending configuration step in the step 2, and acquiring DICOM information and automatic sending information of a cloud platform TPS corresponding to the hospital:
if the AE Title of the cloud platform equipment is analyzed, calling an equipment automatic sending configuration step in the step 2, and acquiring DICOM node information and automatic sending information of corresponding in-hospital equipment;
after the automatic transmission equipment information is analyzed, the DICOM file type information analyzing step in the step 5 is required to be called to analyze the file type, and when the file type is RTSTRUCT, a TPS type conversion method of a multi-TPS adaptation processor in the step 3 is required to be called to carry out TPS adaptation;
and finally, calling an image forwarding service DcmMoveSCU of the DICOM file transmission service in the step 4, acquiring DICOM node information of the two interactive devices according to the step 5, and automatically transmitting the DICOM target area file to the in-hospital device/cloud platform TPS.
Specifically, when the DICOM file listener DcmSendListener of the DICOM file parsing service StoreParseDcmFileSCP in the step 5 monitors the DICOM file, the AE Title of the interactive both-party device is obtained by parsing the DICOM interactive both-party information parsedmsendreceivemethod, and then the getdevicedcmlnfo method of the hospital device and the DICOM matching processor HosDeviceHandler in the step 2 is called to obtain the DICOM node information (IP address, port number, AE Title) of the interactive both-party device.
And if the analyzed Call AE Title is the AE Title of the equipment in the hospital, calling the automatic sending configuration method AutoSendDcmToNode of the hospital equipment and the equipment of the DICOM matching processor HosDeviceHandler in the step 2, and acquiring DICOM information of the cloud platform TPS corresponding to the hospital and whether the information is automatically sent. Namely, the intra-hospital DICOM target area file needs to be automatically transmitted to the TPS of the cloud platform.
And if the parsed Call AE Title is the AE Title of the cloud platform device, calling the automatic transmission configuration method AutoSendDcmToNode of the hospital device and the equipment of the DICOM matching processor HosDeviceHandler in the step 2, and acquiring DICOM information of corresponding hospital equipment and whether the information is automatically transmitted. Namely, the DICOM target area file generated by the TPS of the cloud platform needs to be automatically transmitted to the in-hospital device.
After the automatically transmitted equipment information is analyzed, a DICOM file type information analyzing step ParsedCmModality in step 5 needs to be called to analyze the DICOM Modality type. When the DICOM modification type is rtstrruct, the TPS adaptation is performed by calling the converted TPS type method convertttpsdype of the multiple TPS adaptation processor multitpsbhandler in step 3.
And finally, calling an image forwarding service DcmMoveSCU of a DICOM file transmission service DcmQureyRetrieveSCU in the step 4, acquiring DICOM node information (IP address, port number and AE Title) of the equipment of the two interactive parties according to the step 5, and automatically transmitting the DICOM target file to hospital equipment or a cloud platform TPS.
The emphasis of automatically transmitting DICOM target volume files is to adapt the type of TPS. Because TPS manufacturers vary, the logic for handling DICOM files also varies.
In some optional implementations of some embodiments, the step 6 further includes a DICOM plan file automatic transmission step, where the DICOM plan file automatic transmission step is:
the AE Title of the cloud platform TPS analyzed in the step 5 is called, then the automatic equipment sending configuration step in the step 2 is called, and DICOM node information and automatic sending information of corresponding in-hospital equipment are obtained;
after the automatically transmitted equipment information is analyzed, the DICOM file type information analyzing step in step 5 is also required to be called to analyze the file type. And when the file type is RTPLAN, calling the image forwarding service DcmMoveSCU in the step 4, and automatically transmitting the DICOM plan file to the in-hospital equipment according to the DICOM node information of the interactive two-party equipment obtained in the step 5.
When the DICOM file is monitored by the DICOM file monitor DcmendLister of the DICOM file parsing service StoreParseDcmFileSCP in the step 5, AE Title of the interactive two-party equipment is obtained by a method for parsing information ParseDcmendAndReceive of the two interactive parties, and then the GetDeviceDcmInfo method of the hospital equipment and the DICOM matching processor HosDeviceHandler in the step 2 is called to obtain DICOM node information (IP address, port number and AE Title) of the interactive two-party equipment.
In general, a user uploads a DICOM CT image and a DICOM target area file to the TPS of the cloud platform to delineate a target area or make a plan. After completion, the related DICOM planning file needs to be transmitted back to the hospital accelerator workstation or the radiotherapy information management system, and the accelerator is driven to treat the patient.
Therefore, the parsed Calling AE Title in the step 5 is the AE Title of the TPS of the cloud platform, and then the automatic transmission configuration method AutoSendDcmToNode of the hospital equipment and the equipment of the DICOM matching processor HosDeviceHandler in the step 2 is called to acquire DICOM information of the corresponding hospital equipment and whether the information is automatically transmitted or not. Namely, the DICOM target file generated by the TPS of the cloud platform needs to be automatically transmitted to the in-hospital device.
After the automatically transmitted equipment information is analyzed, a DICOM file type information analyzing step ParsedCmModality in step 5 needs to be called to analyze the DICOM Modality type. And when the DICOM Module type is RTPLAN, calling an image forwarding service DcmMoveSCU of a DICOM file transfer service DcmQureyRetrieveSCU in the step 4, and automatically transmitting a DICOM target area file to hospital equipment according to DICOM node information (IP address, port number and AE Title) of the equipment of the two interactive parties obtained in the step 5.
The key point of automatic transmission of DICOM planning files is to send the files safely and accurately to the hospital accelerator workstation or radiotherapy information management system, and drive the accelerator to treat patients.
In some optional implementation manners of some embodiments, the method further includes setting up a common file transmission service, where the common file transmission service includes a cloud platform TPS file monitoring service, a file transmission center service, a cloud platform file receiving service, and a front-end processor file receiving service.
The common file types include PDF, planerdose, and the like. Wherein, monitor _ ip and accept _ ip are mandatory items in the data, and the two items determine the monitor end and the receiving end. The associated cloud platform TPS is not needed, because the monitoring end IP is unique, the file operation types are creation, modification and deletion, and the following table 4 shows that:
table 4: general file information
As shown in fig. 5, further, a cloud platform TPS file monitoring service filemonitoreservice is deployed in each TPS of the cloud platform, configures a monitoring directory and a receiving IP, and is responsible for recording file information created, modified, and deleted in the TPS into data.
The file transfer center service fileDeliverCenterService is a file stream transfer service and does not perform any operation on files. The purpose is in order to get through the institute in-hospital and out-of-hospital network, guarantees the safe transmission of file. And meanwhile, a file transmission failure retry mechanism FailedRetryTimes is added, a failure task is created after the first transmission failure of the file, and the task actively pulls the file and retransmits the file until the file transmission is finished.
The cloud platform file receiving service CloudFileReceiveService is deployed in a cloud platform, reads data in a database, loads file streams according to matching rules, and simultaneously safely stores files in a file server. Besides, the file name and the file header information can be analyzed and matched with the patient information and the treatment information in the database, and the file is connected and mounted to a file management center of the patient treatment information, so that a doctor and a physicist can conveniently use and download the file.
The front-end processor file receiving service FrontFileReceiveService is deployed in a cloud platform, reads data in a database, loads file streams according to matching rules, and simultaneously safely stores files in the front-end processor, so that doctors and physicists can use the files conveniently.
In a second aspect, the present application provides a DICOM RT file automatic transmission system based on a cloud platform, as shown in fig. 6, including a data information maintenance module, configured to maintain device database information;
the DICOM matching processing module is used for performing DICOM information acquisition and automatic equipment sending configuration on the basis of the equipment database information through a DICOM matching processor;
the multi-TPS adaptation module is used for processing the DICOM file through the multi-TPS adaptation processor;
the DICOM file transmission service module is used for building DICOM file transmission service;
the DICOM file analysis service module is used for building DICOM file analysis service;
the DICOM file automatic transmission module is used for automatically transmitting the DICOM file, wherein the DICOM file analysis service in the DICOM file analysis service module monitors that the DICOM file triggers a corresponding analysis step, then a DICOM matching processor of the DICOM matching processing module is called to analyze node information of two interactive parties and carry out automatic transmission configuration of equipment, a multi-TPS adaptation processor of the multi-TPS adaptation module is called to carry out TPS adaptation, and finally the DICOM file transmission service in the DICOM file transmission service module is called to select a corresponding file transmission service to carry out automatic transmission of the DICOM file.
In a third aspect of the embodiments of the present invention, an electronic device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the method when executing the computer program.
In a fourth aspect of the embodiments of the present invention, a computer-readable storage medium is provided, which stores a computer program, which when executed by a processor implements the steps of the method.
The above are only preferred embodiments of the present invention, and it should be noted that several modifications and improvements made by those skilled in the art without departing from the technical solution should also be considered as falling within the scope of the claims.
Claims (8)
1. The DICOM RT file automatic transmission method based on the cloud platform is characterized in that: the method comprises the following steps:
step 1: maintaining equipment database information;
and 2, step: the DICOM information acquisition and automatic equipment sending configuration are carried out through a DICOM matching processor based on the equipment database information, wherein the step 2 comprises a DICOM node information acquisition step and an automatic equipment sending configuration step of equipment; the equipment DICOM information acquisition step is as follows: transmitting a parameter AE Title, analyzing the parameter AE Title based on a DICOM matching processor, matching according to the information of the equipment database, and acquiring DICOM node information of corresponding equipment; the automatic sending configuration step of the equipment comprises the following steps: acquiring hospital information of corresponding equipment, acquiring DICOM node information of all equipment in the hospital according to hospital codes, and judging whether the equipment can automatically transmit according to automatic transmission information;
and step 3: processing the DICOM file through a multi-TPS adaptive processor, wherein the UID under the sequence corresponding to the target area field in the DICOM target area file exported by TPS is analyzed, and a change relation table is generated according to the TPS exported target area file; converting the type of the TPS according to the change relation table, and processing the DICOM file;
and 4, step 4: building DICOM file transmission service;
and 5: building DICOM file analysis service;
step 6: and automatically transmitting the DICOM file, wherein a corresponding analysis step is triggered after the DICOM file is monitored through the DICOM file analysis service in the step 5, then a DICOM matching processor in the step 2 is called to analyze node information of both interaction sides and equipment is automatically sent and configured, a multi-TPS adaptation processor in the step 3 is called to carry out TPS adaptation, and finally, the DICOM file transmission service in the step 4 is called to select a corresponding file transmission service to carry out automatic DICOM file transmission.
2. The method of claim 1, wherein: the step 1 comprises the following steps:
establishing an in-hospital equipment basic information table, a cloud platform TPS information table and a common file information table in a database;
and (3) developing the base service of the devices in the hospital and the TPS information service of the cloud platform, and performing input and configuration according to the devices in the hospital.
3. The method of claim 2, wherein: the step 4 comprises an image sending service DcmStoeSCU, an image query service DcmFindSCU, an image forwarding service DcmMoveSCU and an image acquiring service DcmGetSCU;
the image sending service DcmStoreSCU encapsulates the StoreSCU, and the bottom layer calls a C-STORE protocol;
the image query service DcmFindSCU packages the FindSCU, and the bottom layer calls a C-FIND protocol;
the image forwarding service DcmMoveSCU encapsulates the MoveSCU, and the bottom layer calls the C-MOVE protocol;
the image acquisition service DcmGetSCU encapsulates the GetSCU, and the bottom layer calls a C-GET protocol.
4. The method of claim 3, wherein: the step 5 comprises a DICOM mutual party information analysis step, a DICOM file type information analysis step and a file monitoring analysis step;
the file monitoring and analyzing steps are as follows: when the DICOM file is monitored by the DICOM file monitor, triggering and executing a DICOM mutual party information analysis step/a DICOM file type information analysis step;
the DICOM interactive two-party information analysis step is as follows: determining information of two service interaction parties by analyzing an initiator and a receiver of a protocol data unit in a DICOM upper layer protocol;
the DICOM file type information analyzing step comprises the following steps: determining the DICOM file type by analyzing Tag in the DICOM file, wherein the DICOM file type comprises CT, MR, RTSTRUCT, RTPLAN, RTDOSE and RTIMAGE.
5. The method of claim 4, wherein: the step 6 comprises the automatic transmission step of the DICOM target area file, and the automatic transmission step of the DICOM target area file comprises the following steps:
when the DICOM file listener of the DICOM file parsing service monitors the DICOM file in the step 5, obtaining AE Title of the interactive both-party equipment by parsing the DICOM interactive both-party information, and then calling the DICOM information obtaining step in the step 2 to obtain DICOM node information of the interactive both-party equipment;
and if the AE Title of the equipment in the hospital is analyzed, calling an equipment automatic sending configuration step in the step 2, and acquiring DICOM information and automatic sending information of a cloud platform TPS corresponding to the hospital:
if the AE Title of the cloud platform equipment is analyzed, the equipment automatic sending configuration step in the step 2 is called to obtain DICOM node information and automatic sending information of corresponding in-hospital equipment;
after the automatic transmission equipment information is analyzed, the DICOM file type information analyzing step in the step 5 is required to be called to analyze the file type, and when the file type is RTSTRUCT, a TPS type conversion method of a multi-TPS adaptation processor in the step 3 is required to be called to carry out TPS adaptation;
and finally, calling an image forwarding service DcmMoveSCU of the DICOM file transmission service in the step 4, acquiring DICOM node information of the two interactive devices according to the step 5, and automatically transmitting the DICOM target area file to the in-hospital device/cloud platform TPS.
6. The method of claim 1, wherein: the step 6 also comprises a DICOM plan file automatic transmission step, wherein the DICOM plan file automatic transmission step comprises the following steps:
the AE Title of the cloud platform TPS analyzed in the step 5 is called, then the automatic equipment sending configuration step in the step 2 is called, and DICOM node information and automatic sending information of corresponding in-hospital equipment are obtained;
after the automatically transmitted equipment information is analyzed, the DICOM file type information analyzing step in the step 5 is also required to be called to analyze the file type; and when the file type is RTPLAN, calling the image forwarding service DcmMoveSCU in the step 4, and automatically transmitting the DICOM plan file to the in-hospital equipment according to the DICOM node information of the interactive two-party equipment obtained in the step 5.
7. The method of claim 1, wherein: and establishing common file transmission services, wherein the common file transmission services comprise a cloud platform TPS file monitoring service, a file transmission center service, a cloud platform file receiving service and a front-end processor file receiving service.
8. DICOM RT file automatic transmission system based on cloud platform, its characterized in that: the system comprises a data information maintenance module, a data information management module and a data information management module, wherein the data information maintenance module is used for maintaining equipment database information;
the DICOM matching processing module is used for carrying out DICOM information acquisition and automatic equipment sending configuration on the basis of the equipment database information through a DICOM matching processor, wherein the DICOM matching processing module comprises a DICOM node information acquisition step and an automatic equipment sending configuration step of equipment; the equipment DICOM information acquisition step is as follows: transmitting a parameter AE Title, analyzing the parameter AE Title based on a DICOM matching processor, matching according to the information of the equipment database, and acquiring DICOM node information of corresponding equipment; the automatic sending configuration step of the equipment comprises the following steps: acquiring hospital information of corresponding equipment, acquiring DICOM node information of all equipment in the hospital according to hospital codes, and judging whether the equipment can automatically transmit according to automatic transmission information;
the multi-TPS adaptation module is used for processing the DICOM file through the multi-TPS adaptation processor, analyzing the UID under the sequence corresponding to the target area field in the DICOM target area file exported by the TPS, and generating a change relation table according to the TPS exported target area file; converting the type of the TPS according to the change relation table, and processing the DICOM file;
the DICOM file transmission service module is used for constructing a DICOM file transmission service;
the DICOM file analysis service module is used for building a DICOM file analysis service;
the DICOM file automatic transmission module is used for automatically transmitting the DICOM file, wherein the corresponding analysis step is triggered after the DICOM file is monitored through a DICOM file analysis service in the DICOM file analysis service module, then a DICOM matching processor of the DICOM matching processing module is called to analyze node information of two interactive parties and carry out automatic transmission configuration of equipment, a multi-TPS adaptation processor of the multi-TPS adaptation module is called to carry out TPS adaptation, and finally the DICOM file transmission service in the DICOM file transmission service module is called to select the corresponding file transmission service to carry out DICOM file automatic transmission.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310012060.4A CN115691768B (en) | 2023-01-05 | 2023-01-05 | DICOM RT file automatic transmission method and system based on cloud platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310012060.4A CN115691768B (en) | 2023-01-05 | 2023-01-05 | DICOM RT file automatic transmission method and system based on cloud platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115691768A CN115691768A (en) | 2023-02-03 |
| CN115691768B true CN115691768B (en) | 2023-03-31 |
Family
ID=85057248
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310012060.4A Active CN115691768B (en) | 2023-01-05 | 2023-01-05 | DICOM RT file automatic transmission method and system based on cloud platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115691768B (en) |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8775199B2 (en) * | 2007-09-25 | 2014-07-08 | The Board Of Trustees Of The University Of Arkansas | Method and system for image pumping |
| US8065166B2 (en) * | 2007-10-30 | 2011-11-22 | Onemednet Corporation | Methods, systems, and devices for managing medical images and records |
| CN105743978A (en) * | 2016-01-29 | 2016-07-06 | 武汉联影医疗科技有限公司 | Data transmitting method |
| CN106934245A (en) * | 2017-03-21 | 2017-07-07 | 上海辉明软件有限公司 | A kind of DICOM image display methods, device and system |
| CN109637652A (en) * | 2018-11-21 | 2019-04-16 | 北京全域医疗技术有限公司 | A kind of remote collaboration hook Target process and system based on cloud |
| CN111161850B (en) * | 2019-12-22 | 2022-06-14 | 武汉儿童医院 | Image uploading matching system and method based on non-real-time additional recording and later-transmitting mode |
| CN112382372B (en) * | 2020-10-16 | 2024-04-19 | 北京全域医疗技术集团有限公司 | System, method and equipment for viewing DICOM file based on network page |
-
2023
- 2023-01-05 CN CN202310012060.4A patent/CN115691768B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN115691768A (en) | 2023-02-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4712962B2 (en) | Image-based artifact troubleshooting for medical systems | |
| US20160162637A1 (en) | Cloud-based Medical Imaging Viewer and Methods for Establishing A Cloud-based Medical Consultation Session | |
| CN1969265B (en) | Medical diagnostic apparatus, medical network system, and method of controlling medical diagnostic apparatus | |
| US20040082845A1 (en) | Medical image diagnostic system, and information providing server and information providing method employed in medical image diagnostic system | |
| RU2409858C2 (en) | Connections control system based on messaging | |
| CN106650211B (en) | Storage server | |
| CN107292117B (en) | Processing method and device for quality guarantee of mass shared medical images | |
| US20110145373A1 (en) | Systems and methods for configuring communication between medical devices | |
| CN101002207A (en) | Generalized approach to structured medical reporting | |
| US20120323606A1 (en) | Method and a mobile device for reviewing patient information | |
| US20090006483A1 (en) | System and method for collecting data from data sources and using data collection tools | |
| EP3249565A2 (en) | Automated application selection for medical devices | |
| US20110238442A1 (en) | System And Method For Customizing Workflow Using Standard Formats For Information Transfer | |
| CA3131986A1 (en) | Universal web service for dicom objects | |
| CN112489770B (en) | DICOM file transmission system, DICOM file transmission method and DICOM file transmission device | |
| CN115691768B (en) | DICOM RT file automatic transmission method and system based on cloud platform | |
| CN106529153B (en) | The character set matching process and device of Digital imaging in medicine and communication file | |
| RU2604983C2 (en) | Service parsing method flexibly adapted to ims system service tag | |
| Abrardo et al. | Embedded Java in a web-based teleradiology system | |
| US20040103169A1 (en) | Medical system architecture and method for exchanging messages | |
| US20150058042A1 (en) | Consolidated patient information exchange | |
| US20100145727A1 (en) | Interaction between healthcare software products | |
| Yiu et al. | Network management for picture archiving and communication systems | |
| US20220198576A1 (en) | Systems and method to treat complex revenue cycle management transactions with machine learning in a standards-based electronic data interchange | |
| Liu et al. | An edge device centric e-health interconnection architecture |
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 |