Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms referred to in this application are explained first:
DICOM file: the DICOM image file is characterized in that the content of the DICOM image file consists of two parts: a Header (Header) including parameter information and picture point Data (Pixel Data). Each DICOM file must include the file header. The header begins with the file preamble, which consists of 128 bytes 00H, followed by the DICOM prefix, which is a 4-byte string "DICM" that can be used to determine whether a file is a DICOM file. The header also includes other useful information such as the transmission format of the file, the application that generated the file, etc. The point data describes the luminance value of each point of the image. The DICOM file contains 4 content levels: patient; study (check); series (Series); image (Image). The contents of the previous layers are the same in many images, but they are present in each image file. An image is composed of a plurality of Information entities (Information entities); the information entity is subdivided into modules (modules); the smallest unit inside each Module is called an Attribute (Attribute) or a data Element (Element). In the DICOM file, the position of each data element is stored in a fixed position, so that the corresponding data element can be found according to the offset of the storage position as long as the first address of the storage of the file in the memory is known.
File: in this application, a file refers to an independent unit that is continuously stored in a disk at a high probability and can be read and written in a continuous reading and writing manner. Such as a DICOM file, an interim result data file, an interim result index file, a priority flag file, etc., are all viewed in a separate perspective.
DICOM image data information: a DICOM image data information refers to image data information extracted from a DICOM file, each piece of DICOM image data information includes general information and individual information, wherein the general information may include a serial number, a patient name or a patient identifier, a thickness, and the like, and the individual information may include an image identifier (such as an example number size of an image) and specific image data. The example number size of the image represents the order before and after scan generation.
Furthermore, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. In the description of the following examples, "plurality" means two or more unless specifically limited otherwise.
The network architecture-based medical image processing method provided by the application is suitable for the following network architecture-based medical image processing system: including a terminal (i.e., client), a proxy server (i.e., front-end), a switch, a first application server, and a second application server.
The software environment of the first application server and the software environment of the second application server are the same as the website program, the difference is that the second application server also serves as a file storage function, and since the first application server and the second application server both need to access data on the second application server, the disk capacity of the second application server can be set to be large, for example, a 250G solid state disk running operating system and a mechanical hard disk array are included to store file data), and the disk capacity of the first application server is set to be small, for example, a 250G solid state disk running operating system and a mechanical hard disk array are included to back up temporary data.
The physical architecture of the system is as follows:
the client, the front-end processor, the first application server and the second application server are connected to the switch through network cables to form a local area network in a hospital. The first application server and the second application server are connected in a disk sharing mode, and are generally realized in a Samba or nfs mode and the like. The system operation flow comprises the following steps:
the client is foreground equipment, a user inputs ip or a domain name of the front-end processor through a browser to access the front-end processor, the front-end processor dispatches a foreground request according to a load balancing algorithm, the request is reversely proxied to a background application server, the front-end processor is equivalent to a virtual client at the moment, the request of a real client is sent to an application server, the application server processes the response request and sends response data to the front-end processor, and the front-end processor replies the response data replied by the background server to the front-end processor. The Http request response process is completed once.
If the front-end processor is proxied to the second application server, the second application server directly accesses data from the local hard disk. And if the front-end processor acts on the first application server, the first application server reads and writes the local hard disk of the second application server through the disk sharing mode.
In order to realize the interaction between the first application server and the second application server, the first application server and the second application server need to be configured, and the configuration can comprise a role of informing the opposite party who is used as the file server and a role of responding to the application server.
Optionally, both the first application server and the second application server may respond to the request of the terminal. Only the role of the file server is played by one application server, and the other application server needs to read and write data through a disk sharing mode. For the sake of convenience in distinguishing the embodiments of the present application, an application server that plays the role of a file server is referred to as a second application server, and another application server is referred to as a first application server.
The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present invention will be described below with reference to the accompanying drawings.
The embodiment of the application provides a medical image processing method based on a network architecture, which is used for correspondingly processing a medical image. The execution subject of the embodiment is a server, and is referred to as a first application server for convenience of differentiation.
As shown in fig. 1, a flow chart of a method for processing a medical image based on a network architecture provided in this embodiment is schematically illustrated, where the method includes:
step 101, a first application server receives DICOM file data to be processed sent by a terminal, wherein the DICOM file data comprises a plurality of DICOM files.
Specifically, when a patient is examined once, a doctor needs to upload DICOM file data of the patient for the examination to the first application server, and the doctor can upload the DICOM file data through the terminal. For example, a doctor can log in the PACS through a terminal, upload DICOM file data to be processed on an upload interface, trigger an upload request and send the DICOM file data to be processed to the first application server. The first application server can receive to-be-processed DICOM file data sent by the terminal, wherein the DICOM file data comprises a plurality of DICOM files, and the specific DICOM file data can comprise all DICOM files of the patient for the current examination.
Optionally, the first application server may put the DICOM file data to be processed into the memory after receiving the DICOM file data.
Step 102, the first application server generates staging result data information according to the DICOM file data, wherein the staging result data information comprises one or more pieces of staging data.
Specifically, after receiving to-be-processed DICOM file data sent by the terminal, the first application server generates staging result data information according to the DICOM file data, wherein the staging result data information includes one or more pieces of staging data.
Illustratively, the first application server extracts DICOM image data information corresponding to each DICOM file from each DICOM file, performs staging processing on each DICOM image data information according to a preconfigured staging rule, and generates staging result data information, wherein each staging data in the staging result data information comprises at least two DICOM image data information.
In some embodiments, the staging result data information may optionally be generated in accordance with a pre-configured custom series data structure. Illustratively, the custom series file data structure is: each series number is stored using 4-byte characters, each length of DICOM image data information is stored using 4-byte characters, and each length of DICOM image data information is stored using byte characters corresponding to the length of the DICOM image data information. Here, the specific structure may be set according to actual requirements, and the embodiment is not limited. Specifically, after the server extracts DICOM image data information corresponding to each DICOM file from each DICOM file, the server generates staging result data information according to a custom series file data structure and stores the staging result data information in a memory.
And 103, writing each staging data in the staging result data information into a corresponding staging result data file by the first application server, and sending the staging result data file to the second application server so that the second application server stores the staging result data file locally.
Specifically, after generating the staging result data information, the first application server writes each piece of staging data in the staging result data information into a corresponding staging result data file, and sends the staging result data file to the second application server, so that the second application server stores the staging result data file locally.
In some embodiments, optionally, each piece of staging data in the staging result data information may be written into a different staging result data file, for example, the first piece of staging data is written into the first staging result data file, the second piece of staging data is written into the second staging result data file, and so on. That is, each staging data corresponds to different staging result data files.
In some embodiments, optionally, each of the staging data in the staging result data may be written into the same staging result data file, for example, there are two staging data, and the two staging data are written into the same staging result data file sequentially. That is, each staging data corresponds to the same staging result data file.
In some embodiments, optionally, if the generated staging result data information is stored in the memory, the first application server obtains the staging result data information from the memory, and writes the staging result data information into the corresponding staging result data file according to a pre-configured image custom data file format.
Illustratively, the image custom data file format is: each DICOM image data has a length of 534965 and hexadecimal 0x000829B 5. The series number 1 is stored in the first 4 bytes, the length of the first DICOM image data information in the series is stored in the 5 th to 8 th bytes, the first DICOM image data information is stored in the 9 th to 534973 th bytes, the length of the second DICOM image data information is stored in the 534974 th to 534977 th bytes, the second DICOM image data information is stored in the 534978 th to 1069942 th bytes, and so on.
Optionally, the staging result data file may also be cached in the first application server, and a preset caching duration may be cached.
In the medical image processing method based on the network architecture, the first application server generates the staging result data information from the plurality of DICOM files sent by the terminal, and each staging data is rewritten into the corresponding staging result data file and sent to the second application server for storage, so that the plurality of DICOM files are rewritten into a large file for storage, thereby effectively reducing the network transmission time and the disk read-write time.
The method provided by the first embodiment of the present application is further described.
As shown in fig. 2, a flow chart of a medical image processing method based on a network architecture is provided in this embodiment.
As a practical manner, on the basis of the first embodiment, optionally after the step 101, the method may further include:
in step 2011, the first application server generates the index information of the staging result according to the DICOM file data, where the index information of the staging result includes the index information of the data information of the staging result.
Specifically, after receiving the to-be-processed DICOM file data, the first application server generates staging result data information and staging result index information according to the DICOM file data, wherein the staging result index information includes index information of the staging result data information. The staging result index information may specifically include attribute information and a storage path corresponding to each DICOM image data information, where the attribute information may include patient information, such as a patient name, a thickness, a serial number, and the like.
Step 2012, the first application server writes the staging result index information into the staging result index file and sends the staging result index file to the second application server, so that the second application server stores the staging result index file locally.
Specifically, the first application server may write the staging result index information corresponding to each staging data into the same staging result index file. For example, the staging result data includes 3 pieces of staging data, each piece of staging data has corresponding staging result index information, and because the staging result index information is text data and is relatively small, the staging result index information corresponding to the 3 pieces of staging data can be sequentially written into the same staging result index file. And the first application server sends the staging result index file to the second application server so that the second application server stores the staging result index file locally.
Optionally, the staging result index file may also be stored in the first application server.
In some embodiments, optionally, the first application server may generate the staging result index information according to a pre-configured custom staging data structure. Illustratively, the custom staging data structure is: the three series are sequentially arranged according to the series division regions, such as an artery stage, a vein stage and a balance stage, and each series comprises a Patientname (patient name), a thickness, a seriesnum (series number), an image path and the like. The method comprises the steps of storing the image path by using a special character ^ through a Patientname, storing the image path by using a 32-byte character, storing the image path by using a four-byte single-precision type by using a thickness, shaping and storing the image path by using 4 bytes, storing the image path by using an unfixed byte character string and distinguishing by using a special character ^ through a special character. Here, the specific structure may be set according to actual requirements, and the embodiment is not limited.
Optionally, the first application server may write the staging result index information into the staging result index file according to a preconfigured staging custom data file format.
The staging custom data file format corresponds to the custom staging data structure. The staging custom data file format is embodied by the specific format of the staging data structure after the file is written. The first application server generates stage result index information according to DICOM image data information extracted from each DICOM file and a custom stage data structure and stores the stage result index information in a memory, and when the file needs to be written, the corresponding stage result index information is obtained from the memory and written into the stage result index file according to a stage custom data file format.
Illustratively, the format of the staging custom data file in which the staging result index information is written into the staging result index file is as follows: zhangsan is stored in the first 32 bytes, 0.6 is stored from the 5 th byte to the 8 th byte, 10 is stored in the 9 th to 12 th bytes, D:/image/1 is stored in the 13 th byte to the 23 th byte, is stored in the 24 th character, D:/image/2 is stored in the 25 th to 35 th characters, and so on.
Similarly, when the staging result index information needs to be read from the staging result index file, the read staging result index information is still stored in the memory according to the custom staging data structure.
In the above embodiment, the image custom data file format and the custom series file data structure are the same as or corresponding to the case of the staging custom data file format and the custom staging data structure, the staging result data information is stored in the memory according to the custom series file data structure, when the file is written in, the corresponding staging result data file is written in according to the image custom data file format, and when the staging result data file is read, the read staging result data information is stored in the memory according to the custom series file data structure. Therefore, the staging is completed in the uploading stage, the real-time staging is not needed during the film reading, the speed of responding the user request is improved, and the user experience is improved.
In some embodiments, optionally, the first application server may further write the staging result index information into the staging result data file before the staging result data information.
Specifically, the first application server may precede the staging result data information with the staging result index information, and write the staging result index information and the staging result data information corresponding to each piece of staging data into the staging result data file corresponding to the piece of staging data.
Illustratively, if the session result data file includes two session data, for each session data, taking the first session data as an example, the session result index information corresponding to the first session data is first written into the corresponding first session result data file, and then the first session data is written into the first session result data file, that is, the session result index information corresponding to the first session data and the first session data are spliced and written into the first session result data file.
Optionally, the first application server writes the staging result index information into the staging result data file before the staging result data information, and the writing may specifically include:
if each piece of staging data corresponds to different staging result data files respectively, for each piece of staging data, writing the staging result index information corresponding to the staging data into the staging result data file corresponding to the staging data before the staging data; if each piece of staging data corresponds to the same staging result data file, the staging data files are sequentially arranged according to the serial numbers, and the staging result index information corresponding to each serial number is sequentially written into the staging result data files before the staging result data information.
Specifically, if each piece of staging data corresponds to different staging result data files, for each piece of staging data, the staging result index information corresponding to the piece of staging data is written into the corresponding staging result data file, and then the pieces of staging data are spliced and written into the staging result data file, that is, the staging result index information corresponding to the piece of staging data and the piece of staging data are sequentially written into the same staging result data file for storage.
If each staging data corresponds to the same staging result data file, the staging result index information corresponding to the staging data is firstly written into the staging result data file, and then the staging data is sequentially written into the staging result data file, namely, the staging result index information corresponding to the staging data and the staging data are both written into the same staging result data file. Wherein, all the staging result index information is written into the beginning part of the staging result data file, and the specific staging data is written into the back of all the staging result index information.
Optionally, each piece of staging data may correspond to different staging result data files, or may correspond to the same staging result data file, which is not limited in this embodiment.
In some embodiments, optionally, the generating, by the first application server, the staging result index information according to the DICOM file data may specifically include: the first application server extracts DICOM image data information corresponding to each DICOM file from the DICOM file data, wherein the DICOM image data information comprises general information and individual information; the first application server carries out stage processing on each DICOM image data information according to a pre-configured stage rule to generate stage result data information and stage result index information, wherein each stage data in the stage result data information comprises at least two DICOM image data information.
Specifically, after receiving the DICOM file data sent by the terminal, the first application server may extract DICOM image data information corresponding to each DICOM file from each DICOM file, perform a staging process on each DICOM image data information according to a preconfigured staging rule, and generate staging result data information and staging result index information, where each staging data in the staging result data information includes at least two pieces of DICOM image data information. For example, the DICOM file data includes 100 DICOM files, which may be divided into 6 installments according to a serial number, the serial number may be used as an installment identifier of each installment, or a corresponding installment identifier may be generated for each installment, so as to identify each installment data. The server may also be preconfigured with a corresponding relationship between the serial number and a common stage, such as three common stages of an artery stage, a vein stage, and a balance stage, and may also include other stages, which may be specifically set according to actual requirements. The server can associate each stage identifier with each stage name (artery stage, vein stage, balance stage, etc.), and each stage data includes its stage identifier, so that when a user clicks and displays an option of "artery stage" on an interface during subsequent reading, the corresponding stage data can be found according to its corresponding stage identifier. The staging result index information can also be associated with the staging result data information through the staging identifier.
Optionally, when uploading the DICOM file data, the doctor may also pre-screen and divide each DICOM file obtained by the examination at the terminal to screen out valid data, improve the validity of the data, and save the storage space, for example, divide according to a serial number, screen out the DICOM files to which the three series of the common artery period, vein period, and balance period respectively belong, send the screened DICOM file data to the first application server, after receiving the DICOM file data sent by the terminal, the first application server may extract the DICOM image data information corresponding to each DICOM file from the DICOM file data, and perform the staging processing according to the pre-configured staging rule. For example, the generated staging result data information includes staging data corresponding to three stages, namely an artery stage, a vein stage and a balance stage, and staging result index information corresponding to each staging data.
Optionally, the staging result index information includes attribute information and a storage path corresponding to each DICOM image data information. The attribute information may include, among other things, patient information such as patient name, thickness, serial number, etc.
Alternatively, the pre-configured staging rules may be staged in series, i.e. a series of images is the same staging. The writing, by the first application server, the staging result index information into the staging result index file may specifically include: the first application server is sequentially arranged according to the staging identifications, and the staging result index information corresponding to each staging identification is sequentially written into the staging result index file. The stage identifier may be a serial number or a newly generated stage identifier. Specifically, the staging result index information may be written into the staging result index file according to the staging customized data file format, which is not described herein again.
Optionally, the pre-configuring the staging rule is to stage according to a series, the general information is a serial number, and the first application server writes the staging result index information into the staging result data file before the staging result data information, which may specifically include:
if each piece of stage data corresponds to different stage result data files respectively, sequentially writing each piece of stage data according to each piece of DICOM image data information, wherein for each piece of DICOM image data information, one corresponding stage result data file is sequentially written according to the sequence of general information, data length and individual information, and the data length is the data length of the individual information (exemplarily, ((serial number 1, data length 534965, individual information 1) (serial number 1, data length 534965, individual information 2) (serial number 1, data length 534965, individual information 3)); or, for each piece of staging data, firstly writing the general information corresponding to the staging data into the staging result data file, and then sequentially writing the data length and the individual information corresponding to each piece of DICOM image data information into the staging result data file. Exemplarily, ((serial No. 1) (data length 534965, individual information 1) (data length 534965, individual information 2) (data length 534965, individual information 3)). It should be noted that, the writing order is only illustrated by way of example, and the format is not limited.
If each staging data corresponds to the same staging result data file, sequencing each staging data in sequence according to the staging identifier, for each stage data, sequentially arranging and writing the stage data according to the DICOM image data information, wherein, for each DICOM image data information, the staging result data file is written in the order of the general information, data length, individual information, exemplarily, ((serial No. 1, data length 534965, individual information 1) (serial No. 1, data length 534965, individual information 2) (serial No. 1, data length 534965, individual information 3) (serial No. 2, data length 534965, individual information 4) (serial No. 2, data length 534965, individual information 5) (serial No. 2, data length 534965, individual information 6) (serial No. 3, data length 534965, individual information 7) (serial No. 3, data length 534965, individual information 8)); alternatively, the respective pieces of staging data are sorted in order according to the staging identifier, and for each piece of staging data, the general information corresponding to the piece of staging data is written into the staging result data file, and the data length and the individual information corresponding to the piece of DICOM image data information are written into the staging result data file in order ((serial No. 1) (data length 534965, individual information 1) (data length 534965, individual information 2) (data length 534965, individual information 3) (serial No. 2) (data length 534965, individual information 4) (data length 534965, individual information 5) (data length 534965, individual information 6) (serial No. 3) (data length 534965, individual information 7) (data length 534965, individual information 8)). It should be noted that, the writing order is only illustrated by way of example, and the format is not limited.
In some embodiments, after the first application server extracts DICOM image data information corresponding to each DICOM file from the DICOM file data, the method may further include:
the first application server carries out pixel analysis on image data parts of individual information in each DICOM image data information to obtain analyzed image data information, wherein the analyzed image data information comprises general information and individual information with pixel data; correspondingly, the first application server performs staging processing on each DICOM image data information according to the preconfigured staging rule to generate staging result data information and staging result index information, and the staging result data information and the staging result index information comprise:
the first application server carries out stage processing on each analyzed image data information according to a pre-configured stage rule to generate stage result data information and stage result index information, wherein each stage data in the stage result data information comprises at least two analyzed image data information.
Specifically, the first application server can also complete pixel analysis of the image data part in a staging process, so that each staging data in the stored staging result data information includes the analyzed image data information, and thus, during subsequent film reading, the pixel analysis is not required to be performed in real time, the staging result data information is directly obtained and returned to the terminal, the terminal can be used for displaying, the response rate of subsequent film reading is further improved, and the user experience is improved.
Optionally, the first application server stores the staging result index file locally, and caches the staging result data file locally for a preset caching duration.
Fig. 3 is a schematic flow chart of another medical image processing method based on a network architecture according to this embodiment.
As another implementable manner, on the basis of the first embodiment, optionally, the method may further include:
step 2021, the first application server receives the user operation behavior information sent by the terminal, where the user operation behavior information includes target object information of the operation and a corresponding user operation, and the target object information includes at least one of a serial number, an issue number, and an image number.
Step 2022, the first application server generates priority label information according to the user operation behavior information, where the priority label information includes a priority identifier and one or more pieces of target object information corresponding to the priority identifier, and the priority identifier is identifier information of a preset priority to which the user operation belongs.
Step 2023, the first application server sequentially writes the priority label information into the priority label file according to the priority label and the sequence of the target object information corresponding to the priority label, and sends the priority label file to the second application server, so that the second application server stores the priority label file locally.
The priority mark file is associated with the staging result index file and the staging result data file through serial numbers. The priority marking file can be one or more.
Specifically, when a user (such as a doctor) needs to check after uploading a checking result of a patient to a first application server of the PACS system, the user can log in the PACS system through a terminal, enter a first interface, select or input a medical record identifier to be read of the patient to be checked, such as a medical record number, or select or input a patient name, and select the medical record identifier to be read from medical record identifiers corresponding to the patient name. The specific manner is not limited. Each doctor can correspond to a plurality of patients, each patient can have one or more examinations, and each examination corresponds to one medical record identifier. When a user determines a medical record identifier to be read, a two-dimensional reading request can be sent to a first application server, the two-dimensional reading request comprises the medical record identifier to be read, the first application server returns reading interface data corresponding to the medical record identifier to a terminal, so that the terminal can display a reading interface to a doctor, and the reading interface can comprise viewing buttons or options corresponding to each piece of date or each piece of date identifier, and an image display area. For example, three options of "arterial phase", "venous phase" and "balance phase" are displayed on the reading interface, and the user can view images of stages by clicking on the options. The specific display style of the first interface and the reading interface is not limited in this embodiment, and any practicable style can be adopted for display according to actual requirements.
When a user selects a certain stage, for example, clicking 'artery stage', an image searching request is sent to a first application server, the image searching request comprises a target stage identifier of an image to be read, for example, a stage identifier corresponding to the artery stage, and the server returns stage data corresponding to the artery stage, so that the terminal displays one or more images corresponding to the artery stage in a display area of a reading interface for a doctor to view.
When the user views the images, the user may perform operations on the images, such as performing image calibration on the interested staged images, including organ length measurement, lesion volume measurement, and the like, or may simply browse the images without performing calibration, or may directly ignore the images, and the like. The terminal can acquire the operation behavior information of the user and send the operation behavior information to the first application server for processing, the first application server receives the operation behavior information of the user sent by the terminal, and can generate priority marking information according to the operation behavior information of the user, the priority marking information is sequentially written into a priority marking file according to the priority identification and the sequence of the target object information corresponding to the priority identification and is sent to the second application server for storage, and the second application server can associate the priority marking file with the staging result index file and the staging result data file through serial numbers or through the staging identification.
Alternatively, the first application server may write the priority label information of all patients of one doctor to the same priority label file.
Optionally, the first application server may also store the priority marking file locally.
Optionally, when the user reads the medical record, after sending the two-dimensional reading request to the server, the first application server may first determine whether the medical record identifier to be read included in the two-dimensional reading request has the corresponding priority markup file, if the medical record identifier to be read corresponds to the priority markup file, the corresponding staging result file may be pre-read from the second application server according to a sequence from high priority to low priority in the priority markup file, the staging result data information is obtained and stored in the memory, and if the image searching request subsequently sent by the user is the pre-read staging, the corresponding staging data may be quickly obtained from the memory and returned to the terminal for display, so that the response speed is increased, the user can quickly check the image without waiting, and the user experience is improved.
Optionally, if a target staging identifier included in an image lookup request subsequently sent by the user does not correspond to a pre-read staging result data file, the first application server stops pre-reading according to the priority, and switches to read the staging result data file corresponding to the target staging identifier so as to respond to the image lookup request of the user, returns staging result data information corresponding to the target staging identifier, and displays the staging result data information on the terminal for the user to view.
In some embodiments, if the staging result index information and the staging result data information corresponding to each staging identifier are written into the same staging result data file, and the medical image file is the staging result data file, pre-reading the medical image file according to the order of the priorities in the priority label file from high to low includes:
step 2031, one or more staging identifiers corresponding to the first priority identifier are obtained from the priority label file, and the first priority identifier is the priority identifier corresponding to the highest priority.
Step 2032, according to each staging identifier corresponding to the first priority identifier, obtaining staging result index information corresponding to each staging identifier from the staging result data file.
Step 2033, according to the staging result index information, obtaining the staging result data information corresponding to each staging identifier from the staging result data file.
Optionally, after the pre-reading of the staging result data files corresponding to the one or more staging identifiers corresponding to the first priority identifier is completed, the pre-reading of the staging result files corresponding to the one or more staging identifiers corresponding to the second priority identifier may be continued according to the priority, and the obtained staging result index information and the staging result data information are stored in the memory.
In some embodiments, if the staging result index information is written into the same staging result index file for storage, and each piece of staging data in the staging result data information is written into a corresponding staging result data file for storage, the medical image file includes the staging result index file and the staging result data file. Correspondingly, the medical image files are pre-read according to the sequence of the priority in the priority mark files from high to low, and the method comprises the following steps:
step 2041, one or more staging identifiers corresponding to the first priority identifier are obtained from the priority label file, and the first priority identifier is the priority identifier corresponding to the highest priority.
Step 2042, according to each staging identifier corresponding to the first priority identifier, obtaining staging result index information corresponding to each staging identifier from the staging result index file.
Step 2043, according to the staging result index information, obtaining staging result data information corresponding to each staging identification from the staging result data file.
In some embodiments, the method may further comprise: if the staging result data information comprises DICOM image data information, performing pixel analysis on image data parts in each DICOM image data information included in the staging result data information to obtain analyzed image data information corresponding to each DICOM image data information, pushing the analyzed image data information to the terminal so that the terminal can display one or more images corresponding to the first priority identification in an image display area of the scoring interface, wherein the image data parts in the analyzed image data information are in a pixel data format.
Optionally, if each piece of staging data in the staging result data information includes DICOM image data information, it is further required to perform pixel analysis on the piece of staging result data information to obtain corresponding analyzed image data information, so that the terminal can display the image data information. The specific pixel resolution process may be the prior art, and is not described herein again.
Optionally, for the first application server reading various files (staging result index file, staging result data file, priority label file) from the second application server to the local (such as hard disk) and reading various information (staging result index information, staging result data information, priority label information) from these files to the internal memory, after the terminal request is responded (such as the user logs out or does not receive the terminal request within a certain time), the first application server may delete the files and information from the local or internal memory. And when the terminal requests again, reading from the second application server.
It should be noted that the implementable modes and the alternative modes in the present embodiment may be implemented individually, or may be implemented in combination in any combination without conflict, and are not limited in the present application.
Based on the foregoing embodiment, in the medical image processing method based on the network architecture, the first application server may further generate the staging result index information to write in the staging result index file or write in the same corresponding staging result data file as the staging result data information, so that the first application server can find corresponding staging data faster according to the staging result index information corresponding to each piece of staging data, thereby improving the data processing rate. And pixel analysis can be realized in the uploading process, and the request response rate can be improved during subsequent film reading, so that the film reading experience of a user is improved. In addition, the first application server can also generate a priority mark file according to the user operation behavior information of the user in the film reading process, and send the priority mark file to the second application server, so that the priority mark file is stored in association with the staging result data file and the staging result index file.
The third embodiment of the present application provides a medical image processing method based on a network architecture, which is used for processing a medical image, and an execution subject of the method may be a server, and is referred to as a first application server for convenience of differentiation.
As shown in fig. 4, a flow chart of a method for processing a medical image based on a network architecture provided in this embodiment is schematically shown, where the method includes:
step 301, a first application server receives an image viewing request sent by a terminal, where the image viewing request includes a target stage identifier of an image to be viewed.
Step 302, the first application server reads the pre-stored staging result file corresponding to the target staging identifier from the second application server according to the target staging identifier, and obtains staging result index information corresponding to the target staging identifier.
Step 303, the first application server reads the staging result file corresponding to the target staging identifier from the second application server according to the staging result index information corresponding to the target staging identifier, and obtains the analyzed image data information corresponding to the target staging identifier, wherein the analyzed image data information includes general information and individual information with pixel data.
And 304, the first application server sends the analyzed image data information corresponding to the target staging identifier to the terminal so as to enable the terminal to perform display processing.
The staging result file corresponding to the target staging identifier comprises a staging result data file, and the staging result data file comprises staging result index information and staging result data information corresponding to the target staging identifier; or,
the staging result file corresponding to the target staging identifier comprises a staging result data file and a staging result index file, the staging result data file comprises staging result data information corresponding to the target staging identifier, and the staging result index file comprises staging result index information corresponding to the target staging identifier.
Specifically, after a doctor uploads DICOM file data of a patient examination result to a server, if the doctor wants to check the patient examination result subsequently, the doctor needs to log in a PACS system for checking, illustratively, a user sends a login request to a first application server through a terminal, the login request at least comprises a user identifier and verification information such as a verification code, and after the first application server passes the verification, the first application server returns first interface data corresponding to the user identifier, so that the doctor enters the first interface, a patient selection item, a medical record identifier selection item and the like can be arranged in the first interface, the doctor can select or input a medical record identifier to be read of the patient to be checked, such as a medical record number, or select or input a patient name, and the medical record identifier to be read is selected from the medical record identifiers corresponding to the patient name. The specific manner is not limited. Each doctor can correspond to a plurality of patients, each patient can have one or more examinations, and each examination corresponds to one medical record identifier. When a user determines a medical record identifier to be read, a two-dimensional reading request can be sent to a first application server, the two-dimensional reading request comprises the medical record identifier to be read, the first application server returns reading interface data corresponding to the medical record identifier to a terminal, so that the terminal can display a reading interface to a doctor, and the reading interface can comprise viewing buttons or options corresponding to each piece of date or each piece of date identifier, and an image display area. For example, three options of "arterial phase", "venous phase" and "balance phase" are displayed on the reading interface, and the user can view images of stages by clicking on the options. The specific display style of the first interface and the reading interface is not limited in this embodiment, and any practicable style can be adopted for display according to actual requirements. After a doctor clicks a certain option of a stage, an image lookup request is sent to a server, the image lookup request comprises a target stage identification of an image to be read, after the first application server receives the image lookup request, a prestored stage result file can be read from a second application server according to the target stage identification, stage result index information corresponding to the target stage identification is obtained, further, a stage result file corresponding to the target stage identification is read according to the stage result index information corresponding to the target stage identification, analyzed image data information corresponding to the target stage identification is obtained, and the analyzed image data information comprises general information and individual information with pixel data. After the server obtains the analyzed image data information corresponding to the target staging identifier, the server sends the analyzed image data information corresponding to the target staging identifier to the terminal so as to enable the terminal to perform display processing.
Optionally, the staging result file corresponding to the target staging identifier may include a staging result data file, and the staging result data file includes staging result index information and staging result data information corresponding to the target staging identifier. That is, the staging result index information corresponding to each staging data and the staging data are written into the same staging result data file during staging. The specific staging process and the process of writing files are described in detail in the first embodiment or the second embodiment, and are not described again here.
Optionally, the staging result file corresponding to the target staging identifier includes a staging result data file and a staging result index file, the staging result data file includes staging result data information corresponding to the target staging identifier, and the staging result index file includes staging result index information corresponding to the target staging identifier. That is, in the staging process, the staging result index information is written into the staging result index file, and each staging data in the staging result data information is written into a corresponding staging result data file. Wherein the staging result index file can be one file or can comprise a plurality of files. The specific staging process and the process of writing files are described in detail in the first embodiment or the second embodiment, and are not described again here.
According to the medical image processing method based on the network architecture, when a doctor reads and views images, the first application server reads the staging result file corresponding to the target staging identification, and the staging result file is a large file rewritten by a DICOM (digital imaging and communications in medicine) file during staging processing, so that network transmission time and disk reading and writing time are effectively reduced, fluency of viewing images in the process of reading the images by a user is improved, and user experience of reading the images is improved.
The fourth embodiment of the present application provides a further supplementary description of the method provided in the third embodiment.
As shown in fig. 5, a flow chart of a medical image processing method based on a network architecture is provided in this embodiment.
As a practical way, on the basis of the above embodiment, optionally, the staging result file can be obtained through the following process:
step 4011, the first application server generates staging result data information and staging result index information according to the DICOM file data sent by the terminal.
Specifically, the process of generating the staging result data information and the staging result index information by the first application server according to the DICOM file data sent by the terminal is consistent with the process in the first embodiment or the second embodiment, and is not described herein again.
Step 4012, the first application server writes the staging result index information into the staging result index file, writes each staging data in the staging result data information into a corresponding staging result data file, and sends the staging result index file and the staging result data file to the second application server, so that the second application server stores the staging result index file and the staging result data file locally.
The data information of the staging result comprises one or more pieces of staging data, the index information of the staging result comprises the index information of the data information of the staging result, and the DICOM file data comprises a plurality of DICOM files.
Optionally, for each piece of staging data, the first application server may further sequentially write the piece of staging result index information corresponding to the piece of staging data and the piece of staging data into a corresponding piece of staging result data file according to the staging result index information corresponding to the piece of staging data and the order of the piece of staging data, and send the staging result data file to the second application server, so that the second application server stores the staging result data file locally, where each piece of staging data corresponds to a different piece of staging result data file.
Optionally, the first application server sequentially writes the staging result index information and the staging result data information into a staging result data file according to the sequence of the staging result index information and the staging result data information, and sends the staging result data file to the second application server, so that the second application server stores the staging result data file locally.
The specific process of writing the staging result index information and the staging result data information into the file may be the same as the writing process in the first embodiment or the second embodiment, and details are not repeated here.
Optionally, after the doctor logs in the PACS system and sends the two-dimensional reading request to the first application server, the first application server may first determine whether the medical record identifier to be read included in the two-dimensional reading request has a corresponding priority markup file, if the medical record identifier to be read corresponds to the priority markup file, the corresponding stage result file may be pre-read from the second application server according to a sequence from high priority to low priority in the priority markup file, the obtained stage result data information is stored in the memory, and if the image searching request subsequently sent by the user is just a pre-read stage, the corresponding stage data may be quickly obtained from the memory and returned to the terminal for display, so that the response speed is increased, the user can quickly check the image without waiting, and the user experience is improved.
Optionally, if a target staging identifier included in an image lookup request subsequently sent by the user does not correspond to a pre-read staging result data file, the first application server stops pre-reading according to the priority, and switches to read the staging result data file corresponding to the target staging identifier so as to respond to the image lookup request of the user, returns staging result data information corresponding to the target staging identifier, and displays the staging result data information on the terminal for the user to view.
As another implementable manner, on the basis of the foregoing embodiment, optionally, if the staging result data information includes at least two pieces of DICOM image data information, the first application server reads the staging result file corresponding to the target staging identifier from the second application server according to the staging result index information corresponding to the target staging identifier, and obtains the parsed image data information corresponding to the target staging identifier, including: the first application server reads and obtains staging result data information corresponding to the target staging identification from the staging result file; and the first application server carries out pixel analysis on the staging result data information corresponding to the target staging identifier to obtain the analyzed image data information corresponding to the target staging identifier.
Specifically, if no pixel analysis is performed during staging processing, the image data portion in the staging result data information corresponding to the target staging identifier, which is obtained when the staging result file corresponding to the target staging identifier is read, is still information in the DICOM format. Illustratively, the image data in DICOM format stores CT values, which are 16-bit data, and are converted into 16-bit gray values and then 8-bit pixel values according to an algorithm, so that the terminal can display the CT values. The specific pixel analysis process may be any implementable manner in the prior art, and this embodiment is not limited.
Optionally, if the staging result data information includes at least two pieces of analyzed image data information, the first application server directly reads the analyzed image data information corresponding to the target staging identifier from the staging result file.
Optionally, when the first application server reads the staging result file, the first application server may also store the staging result index information obtained by reading in the memory according to the custom staging data structure in the second embodiment, and store the staging result data information in the memory according to the custom series file data structure in the first embodiment. The staging result index file is written according to the staging custom data file format in the second embodiment, and the staging result data file is written according to the image custom data file format in the first embodiment.
The medical image processing method based on the network architecture provided by the embodiment can also realize pixel analysis in the uploading process on the basis of the embodiment, and can quickly return the analyzed image data information corresponding to the target staging identifier to the terminal when reading the film, so that the terminal can quickly display the image data information, the request response rate can be improved, and the film reading experience of a user can be improved. In addition, the priority marking file, the staging result data file and the staging result index file can be generated and stored in a correlation mode according to the user operation behavior information of the user in the film reading process, and during the film reading process, the staging data with higher priority can be pushed or read for the user according to the historical operation habits of the user, so that the response speed during the film reading process is further improved, and the film reading experience of the user is improved.
The fifth embodiment of the present application provides a medical image processing method based on a network architecture, which is used for processing a medical image, and an execution subject of the method is an application server, and is referred to as a second application server for convenience of distinction.
As shown in fig. 6, a flow chart of a method for processing a medical image based on a network architecture provided in this embodiment is schematically shown, where the method includes:
step 501, the second application server receives an staging result data file sent by the first application server, wherein the staging result data file comprises staging result data information, the staging result data information comprises one or more pieces of staging data, and the staging result data information is generated according to a plurality of DICOM files.
Step 502, the second application server stores the staging result data file locally.
Specifically, when a patient is examined once, a doctor needs to upload DICOM file data of the patient for the examination to the first application server, and the doctor can upload the DICOM file data through the terminal. For example, a doctor can log in the PACS through a terminal, upload DICOM file data to be processed on an upload interface, trigger an upload request and send the DICOM file data to be processed to the first application server. The first application server can receive to-be-processed DICOM file data sent by the terminal, wherein the DICOM file data comprises a plurality of DICOM files, and the specific DICOM file data can comprise all DICOM files of the patient for the current examination.
After receiving DICOM file data to be processed sent by the terminal, the first application server generates staging result data information according to the DICOM file data, wherein the staging result data information comprises one or more pieces of staging data.
After generating the staging result data information, the first application server writes each staging data in the staging result data information into a corresponding staging result data file and sends the staging result data file to the second application server, and after receiving the staging result data file sent by the first application server, the second application server locally stores the staging result data file.
Optionally, the second application server may store the staging result data file in a local disk.
It should be noted that, in this embodiment, specific operations performed by the first application server have been described in detail in the foregoing embodiments, and are not described herein again.
In the medical image processing method based on the network architecture, the first application server generates the staging result data information from the plurality of DICOM files sent by the terminal, and each staging data is rewritten into the corresponding staging result data file and sent to the second application server for storage, so that the plurality of DICOM files are rewritten into a large file for storage, thereby effectively reducing the network transmission time and the disk read-write time.
In some embodiments, optionally, the method further comprises:
the second application server receives an staging result index file sent by the first application server, wherein the staging result index file comprises staging result index information, and the staging result index information comprises index information of staging result data information; and the second application server stores the staging result index file and the staging result data file in a local association manner.
Specifically, after receiving the to-be-processed DICOM file data, the first application server generates staging result data information and staging result index information according to the DICOM file data, wherein the staging result index information includes index information of the staging result data information. The staging result index information may specifically include attribute information and a storage path corresponding to each DICOM image data information, where the attribute information may include patient information, such as a patient name, a thickness, a serial number, and the like.
The first application server may write the staging result index information corresponding to each staging data into the same staging result index file. For example, the staging result data includes 3 pieces of staging data, each piece of staging data has corresponding staging result index information, and because the staging result index information is text data and is relatively small, the staging result index information corresponding to the 3 pieces of staging data can be sequentially written into the staging result index file. And the first application server sends the staging result index file to the second application server.
And after receiving the staging result index file sent by the first application server, the second application server stores the staging result index file locally.
In some embodiments, optionally, the method further comprises:
the second application server receives a priority marking file sent by the first application server, wherein the priority marking file comprises priority marking information, the priority marking information comprises a priority identification and one or more pieces of target object information corresponding to the priority identification, the priority identification is identification information of a preset priority to which user operation belongs, the priority marking information is generated according to user operation behavior information, the user operation behavior information comprises operation target object information and corresponding user operation, and the target object information comprises at least one of a staging identification and an image number; and the second application server stores the priority marking file locally, and the priority marking file is associated with the staging result index file and the staging result data file through serial numbers.
In some embodiments, optionally, the method further comprises:
the second application server receives DICOM file data to be processed sent by the terminal, wherein the DICOM file data comprises a plurality of DICOM files; the second application server generates staging result data information according to the DICOM file data, wherein the staging result data information comprises one or more pieces of staging data; and the second application server writes each staging data in the staging result data information into a corresponding staging result data file and stores the staging result data file locally.
Optionally, the second application server may execute the method provided in the foregoing embodiment one or embodiment two, and the specific execution process is not described herein again. The difference is that the second application server does not need to send the various files, but stores them locally. That is, the second application server may respond to the request of the terminal and perform operations such as staging, like the first application server, or may assume the role of a file server.
In the medical image processing method based on the network architecture, based on the above embodiment, the second application server may further store an indexing file of the staging result, so that the second application server can find corresponding staging data faster according to indexing information of the staging result corresponding to each piece of staging data, thereby improving data processing rate. The priority mark file, the staging result data file and the staging result index file can be stored in an associated mode, and during subsequent film reading, the staging data with higher priority can be pushed or read for the user according to the historical operation habits of the user, so that the response speed during film reading is further improved, and the film reading experience of the user is improved.
The sixth embodiment of the present application provides a medical image processing method based on a network architecture, which is used for processing a medical image, and an execution subject of the method is an application server, and is referred to as a second application server for convenience of distinction.
The method comprises the following steps:
step 601, when the first application server needs to read the staging result file corresponding to the target staging identifier, the second application server locally reads the staging result file corresponding to the target staging identifier and sends the staging result file to the first application server, so that the first application server obtains the analyzed image data information corresponding to the target staging identifier, and the analyzed image data information includes general information and individual information with pixel data.
The staging result file corresponding to the target staging identifier comprises a staging result data file, and the staging result data file comprises staging result index information and staging result data information corresponding to the target staging identifier; or,
the staging result file corresponding to the target staging identifier comprises a staging result data file and a staging result index file, the staging result data file comprises staging result data information corresponding to the target staging identifier, and the staging result index file comprises staging result index information corresponding to the target staging identifier.
In some embodiments, optionally, the method further comprises:
the second application server generates staging result data information and staging result index information according to DICOM file data sent by the terminal; the second application server writes the indexing information of the staging results into an indexing file of the staging results, writes each piece of staging data in the data information of the staging results into a corresponding data file of the staging results, and stores the indexing file of the staging results and the data file of the staging results locally, wherein the data information of the staging results comprises one or more pieces of staging data, the indexing information of the staging results comprises the indexing information of the data information of the staging results, and the data of the DICOM file comprises a plurality of DICOM files; or,
the second application server writes the staging result index information corresponding to the staging data and the staging data into a corresponding staging result data file in sequence according to the staging result index information and the staging data sequence corresponding to the staging data for each piece of staging data, and stores the staging result data file locally, wherein each piece of staging data corresponds to different staging result data files; or,
and the second application server writes the staging result index information and the staging result data information into a staging result data file in sequence according to the sequence of the staging result index information and the staging result data information, and stores the staging result data file locally.
In some embodiments, optionally, the method further comprises:
a second application server receives a login request sent by a terminal, wherein the login request at least comprises a user identifier; the second application server returns the first interface data corresponding to the user identification so that the terminal displays the first interface corresponding to the user identification; the second application server receives a two-dimensional reading request sent by the terminal, wherein the two-dimensional reading request comprises a medical record identifier to be read; if the priority marking file corresponding to the user identifier is stored, the second application server returns the reading interface data corresponding to the medical record identifier to be read according to the two-dimensional reading request, and pre-reads the medical image file from the local to the memory according to the sequence from high to low of the priority in the priority marking file, wherein the priority marking file is generated according to the user operation behavior information and marks the priority corresponding to each target object information.
That is, the second application server may respond to various requests from the terminal and perform operations such as staging, like the first application server, or may assume the role of a file server. The specific execution operation is the same as the specific operation of the first application server in the third embodiment or the fourth embodiment, and details are not described in this embodiment.
According to the medical image processing method based on the network architecture, when a doctor reads and views images, the first application server reads the staging result file corresponding to the target staging identification, and the staging result file is a large file rewritten by a DICOM (digital imaging and communications in medicine) file during staging processing, so that network transmission time and disk reading and writing time are effectively reduced, fluency of viewing images in the process of reading the images by a user is improved, and user experience of reading the images is improved.
A seventh embodiment of the present application provides a first application server, configured to execute the method provided in any one of the first to fourth embodiments.
Fig. 7 is a schematic structural diagram of the first application server provided in this embodiment. The first application server 70 includes: at least one processor 71 and a memory 72.
The memory stores a computer program; at least one processor executes the computer program stored in the memory to implement the method provided in any of the first to fourth embodiments.
According to the first application server of the embodiment, the first application server generates the staging result data information from the plurality of DICOM files sent by the terminal, each staging data is rewritten into the corresponding staging result data file, and the staging result data file is sent to the second application server for storage, so that the plurality of DICOM files are rewritten into a large file for storage, the network transmission time and the disk reading and writing time can be effectively reduced, the second application server is adopted to play the role of the file server, a special file server does not need to be configured, and the cost of the file server is effectively reduced because the cost of the file server is high. When a doctor reads and views images, the first application server reads the stage result file corresponding to the target stage identification, and the stage result file is a large file rewritten from the DICOM file during stage processing, so that network transmission time and disk reading and writing time are effectively reduced, fluency of the user in the process of viewing the images is improved, and user experience in reading the images is improved.
An eighth embodiment of the present application provides a second application server, configured to execute the method provided in the fifth embodiment or the sixth embodiment.
As shown in fig. 8, a schematic structural diagram of the second application server provided in this embodiment is shown. The second application server 80 includes: at least one processor 81 and a memory 82.
The memory stores a computer program; at least one processor executes the computer program stored in the memory to implement the method provided in the fifth embodiment or the sixth embodiment.
According to the second application server of the embodiment, the second application server stores the staging result data file, so that a plurality of DICOM files are rewritten into a large file for storage, the network transmission time and the disk read-write time can be effectively reduced, and the second application server plays the role of a file server, so that a special file server does not need to be configured, and the cost of the file server is effectively reduced because the cost of the file server is high. The second application server can also store the staging result index file, so that the second application server can find corresponding staging data more quickly according to the staging result index information corresponding to each staging data, and the data processing speed is improved. The priority mark file, the staging result data file and the staging result index file can be stored in an associated mode, and during subsequent film reading, the staging data with higher priority can be pushed or read for the user according to the historical operation habits of the user, so that the response speed during film reading is further improved, and the film reading experience of the user is improved.
The ninth embodiment of the application provides a medical image processing system based on a network architecture. The method for processing the medical image based on the network architecture is provided by any one of the embodiments.
In some embodiments, as shown in fig. 9, a schematic structural diagram of a medical image processing system based on a network architecture is provided for this embodiment. The network architecture-based medical image processing system may include: a terminal (i.e., a client), a proxy server (i.e., a front-end), a switch, a first application server, and a second application server.
The software environment of the first application server and the software environment of the second application server are the same as the website program, the difference is that the second application server also serves as a file storage function, and since the first application server and the second application server both need to access data on the second application server, the disk capacity of the second application server can be set to be large, for example, a 250G solid state disk running operating system and a mechanical hard disk array are included to store file data), and the disk capacity of the first application server is set to be small, for example, a 250G solid state disk running operating system and a mechanical hard disk array are included to back up temporary data.
The physical architecture of the system is as follows:
the client, the front-end processor, the first application server and the second application server are connected to the switch through network cables to form a local area network in a hospital. The first application server and the second application server are connected in a disk sharing mode, and are generally realized in a Samba or nfs mode and the like. The system operation flow comprises the following steps:
the client is foreground equipment, a user inputs ip or a domain name of the front-end processor through a browser to access the front-end processor, the front-end processor dispatches a foreground request according to a load balancing algorithm and reversely proxies the request to a background server, the front-end processor is equivalent to a virtual client at the moment, the request of a real client is sent to a certain server, the server processes the response request and sends response data to the front-end processor, and the front-end processor replies the response data replied by the background server to the front-end processor. The Http request response process is completed once.
If the front-end processor is proxied to the second application server, the second application server directly accesses data from the local hard disk. And if the front-end processor acts on the first application server, the first application server reads and writes the local hard disk of the second application server through the disk sharing mode.
In order to realize the interaction between the first application server and the second application server, the first application server and the second application server need to be configured, and the configuration can comprise a role of informing the opposite party who is used as the file server and a role of responding to the application server.
Optionally, both the first application server and the second application server may execute the method provided in any of the above embodiments. Only the role of the file server is played by one application server, and the other application server needs to read and write data through a disk sharing mode.
The DICOM image uploading process based on the system comprises the following steps:
the staging result file of the local disk of the first application server is stored in the file system format of the operating system, is converted into a network file system format through operations such as layer-by-layer packaging and the like, is transmitted to the second application server through a network after processes such as negotiation, authentication and the like, receives data, converts the network file system format into the file of the operating system according to the system format through layer-by-layer unpacking and stores the file.
Optionally, after receiving the DICOM file data sent by the terminal, the first application server may first store the DICOM file in a file system format of an operating system, convert the DICOM file into a network file system format through operations such as layer-by-layer packaging, perform network transmission to the second application server through processes such as negotiation and authentication, receive the data by the second application server, and convert the network file system format into a file of the operating system according to the system format through layer-by-layer unpacking and store the file. Then the first application server carries out the staging process:
the first application server needs to read each DICOM file from the shared disk in turn. The second application server reads DICOM files from a local disk, converts the DICOM files into a network file system format through operations such as layer-by-layer packaging and the like, performs processes such as negotiation and authentication, performs network transmission to the first application server, receives data, converts the network file system format into files of an operation system according to the system format through layer-by-layer unpacking, stores the files into a memory of the first application server, performs staging processing after reading all the files, obtains staging result index information and staging result data information after staging is completed, writes the staging result index information and the staging result data information into corresponding staging result files (which can comprise the staging result data files or comprise the staging result data files and the staging result index files), and stores the staging result files in the second application server.
Optionally, the first application server may also assume the role of a file server, and the second application server may also assume the role of a response request.
Optionally, the first application server and the second application server may both play a role of responding to the request, and are configured to execute the method provided in any of the above embodiments, where the front-end processor distributes the request according to the load balancing mode, and the first application server or the second application server plays a role of a file server.
Optionally, when the second application server assumes the role of a file server, the priority markup file may be stored in the second application server together with the staging result file, but since the priority markup file needs to be updated frequently, the priority markup file is used to distinguish the user attention degrees of the staging result data files of different stages and accelerate the response of data, and thus, preferably, the priority markup file may be stored in the first application server, so that the first application server may request to read the staging result data file with higher user attention degree from the second application server according to the priority markup file, and the second application server returns via a network and preferentially displays in the user interface. The data loading of the first application server can be more accurate, and the data response speed is improved.
Optionally, when the second application server assumes the role of a file server and stores the staging result file in the second application server, the first application server may also synchronize the staging result index file in the long-term storage staging result file, cache the staging result data file in the staging result file, and cache a certain cache period.
Optionally, the first application server may also be increased to a storage capacity of the same capacity as the second application server, so that both the first application server and the second application server simultaneously function as file servers, and function as response requests. In this case, the two parties can back up each other to implement data synchronization, that is, when the first application server executes the method provided in any of the above embodiments, the obtained staging result file and the priority label file need to be sent to the second application server for backup storage while being locally stored, and when the second application server executes the method provided in any of the above embodiments, the obtained staging result file and the priority label file need to be sent to the second application server for backup storage while being locally stored, thereby implementing mutual backup and data synchronization between the two application servers. Therefore, when the film is read subsequently, no matter which application server the request is proxied to, the request can be obtained from the local storage, and the request does not need to be read to another application server, so that the network transmission time is shortened, and the corresponding speed is improved.
An embodiment tenth of the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the method provided in any one of the first to fourth embodiments is implemented.
An eleventh embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the method provided in the fifth embodiment or the sixth embodiment is implemented.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
It is obvious to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to perform all or part of the above described functions. For the specific working process of the device described above, reference may be made to the corresponding process in the foregoing method embodiment, which is not described herein again.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.