Image cloud interconnection and intercommunication method, device, equipment and medium

Abstract

The invention relates to an image cloud interconnection method and device, equipment and a medium, and belongs to the technical field of medical image information transmission, storage and management. The method comprises the steps that clinician image examination request information is acquired, and clinician image examination request resources are created through an FHIR server; obtaining clinician image examination information and creating clinician image examination resources through the FHIR server; obtaining clinician image data, receiving the clinician image data through a DICOM gateway, and storing the clinician image data in a clinician VDC image file library; obtaining clinician image examination and diagnosis report information and creating clinician image examination and diagnosis report resources through an FHIR server; according to data in the clinician VDC image file library, uploading the data to a cloud at a set time for filing and backup; image-related information interfaces of different manufacturers are uniformly converted into an FHIR standard through a low-code interface adapter, and cross-medical institution information query and image retrieval of a client are realized through an application server, so that optimal configuration and utilization of medical resources are promoted.

Description

Technical Field

[0001] The present invention belongs to the technical field of medical image information transmission, storage and management, and in particular relates to an image cloud interconnection method, device, equipment and medium. Background Art

[0002] With the country attaching great importance to medical imaging information data, the widespread application of image digitization and cloud data storage and management technology has promoted the development of medical imaging cloud. However, the existing medical imaging cloud is mostly limited to the system provided by the same manufacturer, resulting in certain defects and limitations in the interconnection and interoperability across medical institutions. Due to the inconsistency of the image management information data model and interface standards adopted by different manufacturers, imaging clouds involving multiple manufacturers, especially in multi-level systems, are prone to interface adaptation difficulties and increased development and expansion complexity, which not only affects the progress of the project, but also increases the workload and difficulty of subsequent maintenance. Summary of the invention

[0003] In order to solve the above-mentioned problems existing in the prior art, the present invention proposes an image cloud interconnection method, which adopts new international medical information field standards to effectively manage medical image data, realizes a flexible and efficient medical image transmission and storage mechanism across medical institutions, and conveniently retains the image retrieval methods of the original systems of each manufacturer, ensures seamless connection and information sharing between systems, improves the utilization efficiency of medical image resources, and promotes the in-depth development of medical informatization.

[0004] The purpose of the present invention can be achieved through the following technical solutions:

[0005] An image cloud interconnection method, comprising:

[0006] Acquire clinical physician imaging request information, and create clinical physician imaging request resources through the FHIR server according to the clinical physician imaging request information, wherein the clinical physician imaging request resources include clinical physician imaging application resources and clinical physician imaging reservation resources, and the FHIR server provides an FHIR standard information API to manage information storage, query, and call;

[0007] Acquire clinical physician imaging examination information, and create clinical physician imaging examination resources through the FHIR server according to the clinical physician imaging examination information;

[0008] Acquire clinical doctor image data, and receive and save the clinical doctor image data to the clinical doctor VDC image file library through the DICOM gateway according to the clinical doctor image data, wherein the clinical doctor image data includes clinical doctor DICOM image data and clinical doctor non-DICOM image data;

[0009] Obtaining clinical physician imaging diagnosis report information, and creating a clinical physician imaging diagnosis report resource through the FHIR server according to the clinical physician imaging diagnosis report information;

[0010] Upload the clinician's imaging examination information, the clinician's imaging data, and the clinician's imaging examination diagnosis report information to the cloud for archiving and backup at a set time;

[0011] According to the image-related information interfaces of different manufacturers, the low-code interface adapter is used to uniformly convert the image-related information standard interfaces of each manufacturer;

[0012] According to the clinician's VDC image file library, the server is connected through the standard interface of the image-related information of each manufacturer to perform client cross-medical institution information query and client image review.

[0013] Preferably, the acquiring of the clinical doctor image data, receiving and saving the clinical doctor image data to the clinical doctor VDC image file library through a DICOM gateway includes:

[0014] Acquire DICOM image data of clinicians through PACS and examination equipment, and when the DICOM image data of clinicians is not compressed, losslessly compress the DICOM image data of clinicians through Deflate algorithm;

[0015] Acquire non-DICOM imaging data of clinicians through a medical information system, wherein the medical information system is an internal information system of each hospital;

[0016] The clinician DICOM image data and the clinician non-DICOM image data are saved to the clinician VDC image file library through the DICOMstore and the Q / R clinician image data transmission interface.

[0017] Preferably, the step of saving the clinician DICOM image data and the clinician non-DICOM image data to the clinician VDC image file library through the DICOM store and the Q / R clinician image data transmission interface comprises:

[0018] According to the clinician's DICOM image data and DICOM related regulations, the clinician's DICOM image data key identifier is verified by VDC to obtain a clinician's DICOM image data VDC verification result;

[0019] Obtaining a matching result of the clinician's DICOM image data by record matching according to the clinician's DICOM image data VDC verification result and the clinician's image examination resource;

[0020] Obtaining the clinical doctor's non-DICOM image data association result through a file name matching mechanism according to the clinical doctor's non-DICOM image data, the clinical doctor's other image file data, and the clinical doctor's image examination resources, wherein the clinical doctor's other image file data includes a patient informed consent form and a patient report form;

[0021] The clinician's VDC image file library is updated according to the clinician's DICOM image data matching result and the clinician's non-DICOM image data association result.

[0022] Preferably, the obtaining of the VDC verification result of the clinician's DICOM image data by verifying the clinician's DICOM image data key identifier through VDC according to the clinician's DICOM image data and DICOM related regulations includes:

[0023] The clinician DICOM image data key identifier includes the clinician DICOM image data examination instance unique identifier, the clinician DICOM image data patient admission number, and the clinician DICOM image data patient ID number;

[0024] According to the relevant DICOM regulations, determine whether the key identifier of the clinical doctor's DICOM image data meets the mandatory and validity requirements. If yes, the VDC verification result of the clinical doctor's DICOM image data is a successful verification; if not, the VDC verification result of the clinical doctor's DICOM image data is a failed verification, and the clinical doctor's DICOM image data enters the acquisition failure queue and outputs an acquisition failure prompt.

[0025] Preferably, obtaining the matching result of the clinician's DICOM image data by record matching based on the clinician's DICOM image data VDC verification result and the clinician's image examination resource includes:

[0026] When the VDC verification result of the clinician's DICOM image data is successful, the clinician's DICOM image data file header information is extracted through the DICOM parser, and the clinician's DICOM image data file header information includes a key identifier and other related metadata;

[0027] Determine whether the clinical doctor's DICOM image data file header information matches the clinical doctor's image examination resources. If yes, the matching result of the clinical doctor's DICOM image data is a successful match; if not, the matching result of the clinical doctor's DICOM image data is a failed match, and the clinical doctor's DICOM image data enters the failed match queue, and outputs a failed match prompt.

[0028] Preferably, the obtaining of the clinical physician non-DICOM image data association result through a file name matching mechanism based on the clinical physician non-DICOM image data, other clinical physician image file data, and the clinical physician image examination resource includes:

[0029] Extract the clinician's non-DICOM image data file name and the clinician's other image file data file name through an automated file name extraction tool according to the clinician's non-DICOM image data and the clinician's other image file data;

[0030] According to the file name of the clinician's non-DICOM image data and the file name of the clinician's other image file data, determine whether there is a consistent file name with the clinician's image examination resource. If so, the association result of the clinician's non-DICOM image data is a successful association; if not, the association result of the clinician's non-DICOM image data is a failed association, and the clinician's non-DICOM image data and the clinician's other image file data enter the failed association queue, and an association failure prompt is output.

[0031] Preferably, updating the clinician's VDC image file library according to the clinician's DICOM image data matching result and the clinician's non-DICOM image data association result comprises:

[0032] When the matching result of the clinician's DICOM image data is successful, the reference address of the clinician's DICOM image data in the clinician's VDC image file library is updated through the DICOM store and the Q / R clinician image data transmission interface;

[0033] When the association result of the clinician's non-DICOM image data is successful, the reference address of the clinician's non-DICOM image data and other file data of the clinician's images in the clinician's VDC image file library is updated through the DICOM store and the Q / R clinician image data transmission interface.

[0034] An image cloud interconnection system using the above-mentioned image cloud interconnection method includes an examination application module, an examination registration module, a clinician VDC image file library update module, a cloud backup module, a conversion interface adapter module, and an application server module;

[0035] The examination application module is used for a clinician to issue an imaging examination application, and creates a clinician imaging examination request resource through the FHIR server according to the clinician imaging examination request information;

[0036] The examination registration module is used to obtain clinical physician imaging examination information, and create clinical physician imaging examination resources through the FHIR server according to the clinical physician imaging examination information;

[0037] The clinician VDC image file library update module is used to update the clinician image examination information, the clinician image data, and the clinician image examination diagnosis report information;

[0038] The cloud backup module is used to back up the data in the clinician's VDC image file library;

[0039] The conversion interface adapter module is used to convert the image-related information interfaces of different manufacturers into the FHIR standard through a low-code interface adapter, and manage and maintain the interface information;

[0040] The application server module is used to provide the client with cross-medical institution information query and image retrieval functions.

[0041] An electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned image cloud interconnection method when executing the program.

[0042] A storage medium containing computer executable instructions, which are used to perform the above-mentioned image cloud interconnection method when executed by a computer processor.

[0043] The beneficial effects of the present invention are:

[0044] (1) Receiving and saving clinician imaging data through the DICOM gateway and creating clinician imaging examination resources through the FHIR server achieves standardized data management and improves data interoperability and accessibility.

[0045] (2) The image-related information interfaces of different manufacturers are uniformly converted to the FHIR standard through a low-code interface adapter, which improves the compatibility and maintainability of the system.

[0046] (3) By verifying the key identifiers of the clinician's DICOM image data through VDC, the accuracy and integrity of the clinician's DICOM image data are ensured, thereby improving the quality control level of the clinician's DICOM image data.

[0047] (4) Through the record matching and file name matching mechanisms, the clinician's DICOM image data, clinician's non-DICOM image data and clinician's imaging examination resources are matched and associated, realizing multi-dimensional data integration and providing more comprehensive information support for clinicians.

[0048] (5) The application server provides clients with cross-medical institution information query and image retrieval functions, thus realizing cross-medical institution information sharing and promoting the optimal allocation and utilization of medical resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to facilitate understanding by those skilled in the art, the present invention is further described below with reference to the accompanying drawings.

[0050] Figure 1 The figure is a flow chart of an image cloud interconnection method of the present invention. DETAILED DESCRIPTION

[0051] In order to further explain the technical means and effects adopted by the present invention to achieve the predetermined invention purpose, the specific implementation methods, structures, features and effects of the present invention are described in detail below in conjunction with the accompanying drawings and preferred embodiments.

[0052] See also Figure 1 , an image cloud interconnection method, comprising:

[0053] S1: Acquire clinician imaging request information, and create clinician imaging request resources through the FHIR server according to the clinician imaging request information. The clinician imaging request resources include clinician imaging application resources and clinician imaging reservation resources. The FHIR server provides FHIR standard information API to manage information storage, query and call;

[0054] S2: Acquire the clinician imaging examination information, and create the clinician imaging examination resource through the FHIR server according to the clinician imaging examination information;

[0055] S3: Acquire the clinician's image data, and receive and save the clinician's image data to the clinician's VDC image file library through the DICOM gateway, wherein the clinician's image data includes the clinician's DICOM image data and the clinician's non-DICOM image data;

[0056] S4: Acquire the clinician's imaging diagnosis report information, and create a clinician's imaging diagnosis report resource through the FHIR server according to the clinician's imaging diagnosis report information;

[0057] S5: uploading the clinician's imaging examination information, the clinician's imaging data, and the clinician's imaging examination diagnosis report information to the cloud for archiving and backup at a set time;

[0058] S6: The image-related information interfaces of different manufacturers are uniformly converted through low-code interface adapters to obtain the image-related information standard interfaces of each manufacturer;

[0059] S7: Connecting to the server through the standard interface of the image-related information of each manufacturer according to the clinician VDC image file library to perform client cross-medical institution information query and client image retrieval.

[0060] In step S3, the acquisition of clinical doctor image data, receiving the clinical doctor image data through the DICOM gateway and saving it to the clinical doctor VDC image file library specifically includes the following steps:

[0061] S301: Acquire DICOM image data of clinicians through PACS and examination equipment, where the PACS is a hospital clinical image archiving and communication system, and the examination equipment includes a CT machine, an MRI machine, and an X-ray machine;

[0062] When the clinician's DICOM image data is not compressed, the clinician's DICOM image data is losslessly compressed using a Deflate algorithm to save storage space and improve transmission efficiency;

[0063] S302: Acquire non-DICOM image data of clinicians through a medical information system, where the medical information system is an internal information system of each hospital;

[0064] S303: saving the clinician's DICOM image data and the clinician's non-DICOM image data to the clinician's VDC image file library through the DICOM store and the Q / R clinician image data transmission interface;

[0065] In this embodiment, the clinical doctor image file library generally only retains clinical doctor image data within three to six months, and images that exceed the time limit will be automatically deleted, and the corresponding address nodes will be deleted.

[0066] The step S303 described in which the clinician DICOM image data and the clinician non-DICOM image data are saved to the clinician VDC image file library through the DICOM store and the Q / R clinician image data transmission interface specifically includes the following steps:

[0067] S303-1: Verify the key identifier of the clinician's DICOM image data through VDC according to the clinician's DICOM image data and DICOM related regulations to obtain a VDC verification result of the clinician's DICOM image data;

[0068] The clinician DICOM image data key identifier includes the clinician DICOM image data examination instance unique identifier, the clinician DICOM image data patient admission number, and the clinician DICOM image data patient ID number;

[0069] The DICOM-related regulations are standards developed by the American College of Radiology and the American Electrical Manufacturers Association specifically for the storage and transmission of medical images;

[0070] According to the DICOM related regulations, it is determined whether the key identifier of the clinician's DICOM image data meets the mandatory and validity requirements. If yes, the VDC verification result of the clinician's DICOM image data is a successful verification; if no, the VDC verification result of the clinician's DICOM image data is a failed verification, and the clinician's DICOM image data enters the acquisition failure queue, and an acquisition failure prompt is output;

[0071] S303-2: Obtaining a matching result of the clinical doctor's DICOM image data by record matching according to the clinical doctor's DICOM image data VDC verification result and the clinical doctor's image examination resource;

[0072] When the VDC verification result of the clinician's DICOM image data is successful, the clinician's DICOM image data file header information is extracted through the DICOM parser, and the clinician's DICOM image data file header information includes a key identifier and other related metadata;

[0073] Determine whether the clinical doctor's DICOM image data file header information matches the clinical doctor's image examination resources. If yes, the matching result of the clinical doctor's DICOM image data is a successful match; if not, the matching result of the clinical doctor's DICOM image data is a failed match, and the clinical doctor's DICOM image data enters the failed match queue, and outputs a failed match prompt.

[0074] S303-3: Obtaining a clinical doctor's non-DICOM image data association result through a file name matching mechanism according to the clinical doctor's non-DICOM image data, other clinical doctor image file data, and the clinical doctor image examination resources, wherein the other clinical doctor image file data includes a patient informed consent form and a patient report form;

[0075] Extract the clinician's non-DICOM image data file name and the clinician's other image file data file name through an automated file name extraction tool according to the clinician's non-DICOM image data and the clinician's other image file data;

[0076] According to the file name of the clinician's non-DICOM image data and the file name of the clinician's other image file data, determine whether there is a consistent file name with the clinician's image examination resource. If so, the association result of the clinician's non-DICOM image data is a successful association; if not, the association result of the clinician's non-DICOM image data is a failed association, and the clinician's non-DICOM image data and the clinician's other image file data enter the failed association queue, and an association failure prompt is output.

[0077] S303-4: updating the clinician's VDC image file library according to the clinician's DICOM image data matching result and the clinician's non-DICOM image data association result;

[0078] When the matching result of the clinician's DICOM image data is successful, the reference address of the clinician's DICOM image data in the clinician's VDC image file library is updated through the DICOM store and the Q / R clinician image data transmission interface;

[0079] When the association result of the clinician's non-DICOM image data is successful, the reference address of the clinician's non-DICOM image data and other file data of the clinician's images in the clinician's VDC image file library is updated through the DICOM store and the Q / R clinician image data transmission interface.

[0080] An image cloud interconnection system includes an examination application module, an examination registration module, a clinician VDC image file library update module, a cloud backup module, a conversion interface adapter module, and an application server module;

[0081] The examination application module is used for a clinician to issue an imaging examination application, and creates a clinician imaging examination request resource through the FHIR server according to the clinician imaging examination request information;

[0082] The examination registration module is used to obtain clinical physician imaging examination information, and create clinical physician imaging examination resources through the FHIR server according to the clinical physician imaging examination information;

[0083] The clinician VDC image file library update module is used to update the clinician image examination information, the clinician image data, and the clinician image examination diagnosis report information;

[0084] The cloud backup module is used to back up the data in the clinician's VDC image file library;

[0085] The conversion interface adapter module is used to convert the image-related information interfaces of different manufacturers into the FHIR standard through a low-code interface adapter, and manage and maintain the interface information;

[0086] The application server module is used to provide the client with cross-medical institution information query and image retrieval functions.

[0087] The computer storage medium of the embodiment of the present invention may adopt any combination of one or more computer-readable media. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device.

[0088] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0089] The program code included on the computer readable medium can be transmitted with any appropriate medium, including but not limited to wireless, electric wire, optical cable, RF, etc., or any suitable combination of the above. The computer program code for performing the operation of the present invention can be written in one or more programming languages ​​or their combinations, and the programming language includes object-oriented programming languages-such as Java, Smalltalk, C++, and also includes conventional procedural programming languages-such as "C" language or similar programming languages. The program code can be executed completely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on the remote computer, or completely on the remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).

[0090] The above description is only a preferred embodiment of the present invention and does not limit the present invention in any form. Although the present invention has been disclosed as a preferred embodiment as above, it is not used to limit the present invention. Any technical personnel in this field can make some changes or modify the technical contents disclosed above into equivalent embodiments without departing from the scope of the technical solution of the present invention. However, any simple modification, equivalent change and modification made to the above embodiments according to the technical essence of the present invention without departing from the content of the technical solution of the present invention still fall within the scope of the technical solution of the present invention.

Claims

1. An image cloud interconnection method, characterized in that: include: Acquire clinical physician imaging request information, and create clinical physician imaging request resources through the FHIR server according to the clinical physician imaging request information, wherein the clinical physician imaging request resources include clinical physician imaging application resources and clinical physician imaging reservation resources, and the FHIR server provides an FHIR standard information API to manage information storage, query, and call; Acquire clinical physician imaging examination information, and create clinical physician imaging examination resources through the FHIR server according to the clinical physician imaging examination information; Acquire clinical doctor image data, and receive and save the clinical doctor image data to the clinical doctor VDC image file library through the DICOM gateway according to the clinical doctor image data, wherein the clinical doctor image data includes clinical doctor DICOM image data and clinical doctor non-DICOM image data; Obtaining clinical physician imaging diagnosis report information, and creating a clinical physician imaging diagnosis report resource through the FHIR server according to the clinical physician imaging diagnosis report information; Upload the clinician's imaging examination information, the clinician's imaging data, and the clinician's imaging examination diagnosis report information to the cloud for archiving and backup at a set time; According to the image-related information interfaces of different manufacturers, the low-code interface adapter is used to uniformly convert the image-related information standard interfaces of each manufacturer; According to the clinician's VDC image file library, the server is connected through the standard interface of the image-related information of each manufacturer to perform client cross-medical institution information query and client image review.

2. The image cloud interconnection method according to claim 1, characterized in that: The obtaining of clinical doctor image data, receiving and saving the clinical doctor image data to the clinical doctor VDC image file library through the DICOM gateway, comprises: Acquire DICOM image data of clinicians through PACS and examination equipment, and when the DICOM image data of clinicians is not compressed, losslessly compress the DICOM image data of clinicians through Deflate algorithm; Acquire non-DICOM imaging data of clinicians through a medical information system, wherein the medical information system is an internal information system of each hospital; The clinician DICOM image data and the clinician non-DICOM image data are saved in the clinician VDC image file library through the DICOM store and the Q / R clinician image data transmission interface.

3. The image cloud interconnection method according to claim 2, characterized in that: The step of storing the clinician's DICOM image data and the clinician's non-DICOM image data in the clinician's VDC image file library through the DICOM store and the Q / R clinician image data transmission interface includes: According to the clinician's DICOM image data and DICOM related regulations, the clinician's DICOM image data key identifier is verified by VDC to obtain a clinician's DICOM image data VDC verification result; Obtaining a matching result of the clinician's DICOM image data by record matching according to the clinician's DICOM image data VDC verification result and the clinician's image examination resource; Obtaining the clinical doctor's non-DICOM image data association result through a file name matching mechanism according to the clinical doctor's non-DICOM image data, the clinical doctor's other image file data, and the clinical doctor's image examination resources, wherein the clinical doctor's other image file data includes a patient informed consent form and a patient report form; The clinician's VDC image file library is updated according to the clinician's DICOM image data matching result and the clinician's non-DICOM image data association result.

4. The image cloud interconnection method according to claim 3, characterized in that: The obtaining of the VDC verification result of the clinician's DICOM image data by verifying the clinician's DICOM image data key identifier through VDC according to the clinician's DICOM image data and DICOM related regulations includes: The clinician DICOM image data key identifier includes the clinician DICOM image data examination instance unique identifier, the clinician DICOM image data patient admission number, and the clinician DICOM image data patient ID number; According to the relevant DICOM regulations, determine whether the key identifier of the clinical doctor's DICOM image data meets the mandatory and validity requirements. If yes, the VDC verification result of the clinical doctor's DICOM image data is a successful verification; if not, the VDC verification result of the clinical doctor's DICOM image data is a failed verification, and the clinical doctor's DICOM image data enters the acquisition failure queue and outputs an acquisition failure prompt.

5. The image cloud interconnection method according to claim 3, characterized in that: The obtaining of the matching result of the clinician's DICOM image data by record matching based on the VDC verification result of the clinician's DICOM image data and the clinician's image examination resource includes: When the VDC verification result of the clinician's DICOM image data is successful, the clinician's DICOM image data file header information is extracted through the DICOM parser, and the clinician's DICOM image data file header information includes a key identifier and other related metadata; Determine whether the clinical doctor's DICOM image data file header information matches the clinical doctor's image examination resources. If yes, the matching result of the clinical doctor's DICOM image data is a successful match; if not, the matching result of the clinical doctor's DICOM image data is a failed match, and the clinical doctor's DICOM image data enters the failed match queue, and outputs a failed match prompt.

6. The image cloud interconnection method according to claim 3, characterized in that: The clinical doctor non-DICOM image data association result obtained by the file name matching mechanism according to the clinical doctor non-DICOM image data, the clinical doctor image other file data, and the clinical doctor image examination resource includes: Extract the clinician's non-DICOM image data file name and the clinician's other image file data file name through an automated file name extraction tool according to the clinician's non-DICOM image data and the clinician's other image file data; According to the file name of the clinician's non-DICOM image data and the file name of the clinician's other image file data, determine whether there is a consistent file name with the clinician's image examination resource. If so, the association result of the clinician's non-DICOM image data is a successful association; if not, the association result of the clinician's non-DICOM image data is a failed association, and the clinician's non-DICOM image data and the clinician's other image file data enter the failed association queue, and an association failure prompt is output.

7. The image cloud interconnection method according to claim 3, characterized in that: The updating of the clinician's VDC image file library according to the clinician's DICOM image data matching result and the clinician's non-DICOM image data association result comprises: When the matching result of the clinician's DICOM image data is successful, the reference address of the clinician's DICOM image data in the clinician's VDC image file library is updated through the DICOM store and the Q / R clinician image data transmission interface; When the association result of the clinician's non-DICOM image data is successful, the reference address of the clinician's non-DICOM image data and other file data of the clinician's images in the clinician's VDC image file library is updated through the DICOM store and the Q / R clinician image data transmission interface.

8. An image cloud interconnection system using the image cloud interconnection method of claim 1, comprising an examination application module, an examination registration module, a clinician VDC image file library update module, a cloud backup module, a conversion interface adapter module, and an application server module, characterized in that: The examination application module is used for a clinician to issue an imaging examination application, and creates a clinician imaging examination request resource through the FHIR server according to the clinician imaging examination request information; The examination registration module is used to obtain clinical physician imaging examination information, and create clinical physician imaging examination resources through the FHIR server according to the clinical physician imaging examination information; The clinician VDC image file library update module is used to update the clinician image examination information, the clinician image data, and the clinician image examination diagnosis report information; The cloud backup module is used to back up the data in the clinician's VDC image file library; The conversion interface adapter module is used to convert the image-related information interfaces of different manufacturers into the FHIR standard through a low-code interface adapter, and manage and maintain the interface information; The application server module is used to provide the client with cross-medical institution information query and image retrieval functions.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the image cloud interconnection method as described in any one of claims 1-7 is implemented.

10. A storage medium containing computer executable instructions, characterized in that: The computer executable instructions, when executed by a computer processor, are used to execute the image cloud interconnection method as described in any one of claims 1-7.

Images