Life cycle-based medical file multi-node storage method, device and system

Abstract

The application provides a life cycle-based medical file multi-node storage method, device and system, the method comprising: acquiring a generation node and a life length of a medical file to determine a life cycle of the medical file; and storing the medical file in a hot period in a first storage medium and storing the medical file in a warm period only in a second storage medium according to the life cycle. Based on the fast response capability of the first storage medium, a large amount of data can be retrieved from the first storage medium at the same time, the speed of extracting data when the system processes the medical file is improved, and the problem of system lag is avoided; the medical file in the warm period is stored only in the network storage, which not only reduces the storage pressure of the first storage medium, but also guarantees the integrity and availability of the medical file, realizes the classified storage of the medical file, and avoids the problem of lag in the data processing process due to improper storage location of the medical file.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of file storage, in particular to a medical file multi-node storage method, device and system based on life cycle. BACKGROUND

[0002] With the wide application of computer technology, it is necessary to store and process massive data files, especially in the medical field. The update frequency of medical file data is relatively high. However, due to the limited ability of the system to process data at a time, when the amount of data stored in the system is too large, the processing speed of the system will be reduced.

[0003] Currently, in order to reduce the load of the system in data storage and improve the processing speed of the system, a special storage medium is mainly set to store the data of the system, so that the system only needs to retrieve the data in the storage medium when processing data. However, by the above-mentioned way of retrieving data, a large amount of data is retrieved from the storage medium at the same time, and due to the limited ability of the system to process data at a time, there is a problem of lag in obtaining medical files.

[0004] Therefore, in the prior art, when processing medical files, there is a problem of lag in obtaining a large amount of medical files due to unreasonable storage location of medical files. SUMMARY

[0005] Therefore, it is necessary to provide a medical file multi-node storage method, device and system based on life cycle, to solve the problem of lag in processing medical files due to improper storage of files in the prior art.

[0006] In order to solve the above-mentioned problem, the present application provides a medical file multi-node storage method based on life cycle, comprising:

[0007] obtaining the generation node and the life length of the medical file;

[0008] determining the life cycle of the medical file according to the generation node and the life length, wherein the life cycle includes a hot period and a warm period;

[0009] According to the life cycle, the medical file is stored in multiple nodes according to a preset storage strategy, wherein the medical file in the hot period is stored in at least a first storage medium, and the medical file in the warm period is stored in only a second storage medium, and the response speed of the first storage medium is faster than that of the second storage medium.

[0010] Further, according to the generation node and the life length, the life cycle of the medical file is determined,

[0011] comprising:

[0012] determining whether the current date is included in the life cycle;

[0013] if yes, determining that the medical file is in the hot period;

[0014] if no, determining that the medical file is in the warm period.

[0015] 5Further, the preset storage strategy includes a classification storage strategy, a state switching storage strategy, and a scheduling storage strategy.

[0016] Further, the medical file is stored in multiple nodes according to the classification storage strategy, including:

[0017] determining whether the medical file is in the hot period;

[0018] if yes, storing the storage path of the corresponding medical file to the first storage medium and the second storage medium respectively; if no, storing the storage path of the corresponding medical file to the second storage medium only.

[0019] Further, the medical file is stored in multiple nodes according to the state switching storage strategy, including:

[0020] real-time acquisition of the state to be switched medical file which is about to end the hot period;

[0021] 5confirming the storage path of the state to be switched medical file in the second storage medium;

[0022] in a preset idle time, triggering an instruction to delete the storage path of the state to be switched medical file in the first storage medium.

[0023] Further, the medical file is stored in multiple nodes according to the scheduling storage strategy, including:

[0024] real-time acquisition of the calling instruction of the medical file;

[0025] determining the update generation node of the to-be-called medical file according to the calling instruction;

[0026] determining the update life cycle of the to-be-called medical file according to the update generation node and the life length;

[0027] correspondingly adjusting the storage location of the to-be-called medical file according to the update life cycle.

[0028] Further, the calling instruction includes a positive calling instruction and a negative calling instruction; determining the update generation node of the to-be-called medical file according to the calling instruction, including:

[0029] determining whether the to-be-called medical file is in the hot period;

[0030] If yes, it is judged whether the calling instruction is a forward calling instruction; if yes, the generation node of the to-be-called medical file is updated to the current node; if no, the life length of the to-be-called medical file is adjusted to zero.

[0031] If no, the generation node of the to-be-called medical file is updated to the current node.

[0032] Further, according to the update life cycle, the storage location of the to-be-called medical file is adjusted correspondingly, including:

[0033] It is judged whether the update life cycle is in a hot period.

[0034] If yes, the storage path of the to-be-called medical file is stored to the first storage medium and the second storage medium.

[0035] If no, the storage path of the to-be-called medical file is only stored to the second storage medium.

[0036] In order to solve the above problems, the application further provides a medical file multi-node storage device based on a life cycle, comprising:

[0037] A life length acquisition module is configured to acquire the generation node and the life length of the medical file.

[0038] A life cycle determination module is configured to determine the life cycle of the medical file according to the generation node and the life length, wherein the life cycle comprises a hot period and a warm period.

[0039] A multi-node storage module is configured to store the medical file in multiple nodes according to the life cycle and a preset storage strategy, wherein the medical file in the hot period is stored in at least the first storage medium, the medical file in the warm period is stored in only the second storage medium, and the response speed of the first storage medium is faster than that of the second storage medium.

[0040] In order to solve the above problems, the application further provides a medical file multi-node storage system based on a life cycle, comprising a first storage medium, a second storage medium and a medical file multi-node storage device based on a life cycle as described above.

[0041] The beneficial effects of the above technical scheme are: the application provides a medical file multi-node storage method, device and system based on a life cycle, which comprises the following steps: first, obtaining the generation node and life length of a medical file to determine the life cycle of the medical file; then, according to the life cycle, storing the medical file in a hot period in at least a first storage medium and storing the medical file in a warm period in only a second storage medium. Based on the fast response capability of the first storage medium to the system, a large amount of data can be retrieved from the first storage medium at the same time, the speed of extracting data when the system processes the medical file is improved, and the problem of system lag is avoided; the medical file in the warm period is only stored in the network storage, which not only reduces the storage pressure of the first storage medium, but also guarantees the integrity and usability of the medical file, realizes the classified storage of the medical file, and avoids the problem of lag in the data processing process due to improper storage location of the medical file. BRIEF DESCRIPTION OF DRAWINGS

[0042] Figure 1 A flowchart of an embodiment of the medical file multi-node storage method based on a life cycle provided by the application is shown.

[0043] Figure 2 A flowchart of an embodiment of the medical file storage location adjustment provided by the application is shown.

[0044] Figure 3 A flowchart of an embodiment of the update generation node of the medical file to be called provided by the application is shown.

[0045] Figure 4 A flowchart of an embodiment of the storage location adjustment of the medical file to be called provided by the application is shown.

[0046] Figure 5 A structural diagram of an embodiment of the medical file multi-node storage device based on a life cycle provided by the application is shown. DETAILED DESCRIPTION

[0047] The preferred embodiments of the application will be specifically described below with reference to the accompanying drawings, which form a part of this application, and are used to explain the principles of the application together with the embodiments of the application, but are not used to limit the scope of the application.

[0048] Before the embodiments are described, the network storage, solid state disk, PACS server and IO are described:

[0049] Network storage (NAS storage) is simply connected to the network in the literal sense, with data storage function device, so also known as "network storage". It is a dedicated data storage server, data-centric, completely separate storage devices and servers, centralized management of data, thereby releasing bandwidth, improving performance, reducing total cost of ownership, protecting investment, its data storage in the network, through the network and system connection, when needed, through the network bandwidth to obtain.

[0050] Solid state disk (Solid State Disk or Solid State Drive, SSD), also known as solid state drive, is made of solid state electronic storage chip array, which can be directly connected with the system. Since it is a chip storage, when the data in the chip needs to be extracted, it can be directly extracted according to the instruction of the system, and a small batch of files can be processed at the same time.

[0051] PACS server refers to image archiving and communication system, which is a multimedia DBMS system involving radiology, image medicine, digital image technology (collection and processing), computer and communication, C / S architecture, software engineering, graphics image synthesis and post-processing and other technologies. Its main application direction is: device cluster use, image collection from various image devices or digital devices, sharing and selection of various output devices such as printing, image transmission and distribution, rapid transmission of image data between various departments in the hospital, remote transmission of image and diagnosis report, etc.

[0052] IO, (Input / Output, input / output), divided into IO device and IO interface two parts, refers to the process of system input and output to storage device, usually represents the read-write ability of host to storage.

[0053] At present, the PACS server usually collects and processes medical files. In order to alleviate the running pressure of the PACS server, a special storage medium is usually set as the position of the system storage data. However, when processing data, a large amount of data needs to be retrieved from the storage medium at the same time, and due to the limited ability of the system to process data at a time, the problem of lag in obtaining medical files exists.

[0054] Therefore, the prior art has the problem that due to the unreasonable storage position of medical files, the lag problem occurs in the process of obtaining a large amount of medical files.

[0055] In order to solve the above problems, the present application provides a medical file multi-node storage method, device and system based on life cycle, which are described in detail below.

[0056] As Figure 1 shown, Figure 1 The flowchart of an embodiment of the life cycle-based medical file multi-node storage method provided by the present application is shown in the figure, which includes:

[0057] Step S101: Obtain the generation node and life length of the medical file.

[0058] Step S102: Determine the life cycle of the medical file according to the generation node and life length, wherein the life cycle includes a hot period and a warm period.

[0059] Step S103: According to the life cycle, store the medical file in multiple nodes according to the preset storage strategy, wherein the medical file in the hot period is stored in at least the first storage medium, and the medical file in the warm period is stored only in the second storage medium, and the response speed of the first storage medium is faster than that of the second storage medium.

[0060] In this embodiment, first, the generation node and life length of the medical file are obtained to determine the life cycle of the medical file, wherein the life cycle includes a hot period and a warm period; then, according to the life cycle of the medical file, the medical file in the hot period is stored in at least the first storage medium, and the medical file in the warm period is stored only in the second storage medium, realizing the classified storage of the medical file, and at the same time, since the response speed of the first storage medium is faster than that of the second storage medium, a large amount of data can be retrieved from the first storage medium at the same time, improving the response speed of the system in obtaining data and avoiding lag.

[0061] In this embodiment, by storing the medical file in the hot period in at least the first storage medium, the speed of extracting medical file data by the system is improved based on the fast response capability of the first storage medium to the system, avoiding the problem of system lag; since the response speed of the first storage medium is faster than that of the second storage medium, the medical file in the warm period is only stored in the second storage medium, which not only reduces the storage pressure of the first storage medium, but also guarantees the integrity and availability of the medical file, realizes the classified storage of the medical file, and avoids the problem of lag in the data processing process due to improper storage location of the medical file.

[0062] As a preferred embodiment, in step S101, the medical file is uniformly processed by a PACS server, wherein the first storage medium is matched with the PACS server, and the first storage medium can quickly respond to the instructions of the system; the second storage medium is specially used to store medical files, and since the storage capacity of the second storage medium is strong but the speed of responding to the system is general, the second storage medium is used as the location for uniformly storing medical files to ensure the integrity of the medical files.

[0063] Further, in order to alleviate the pressure of a single PACS server, multiple PACS servers are arranged to collect medical files of different types and from different devices; in addition, each PACS server is configured with a first storage medium corresponding thereto for storing the medical files acquired thereby.

[0064] In a specific embodiment, in order to improve the pertinence of the PACS server, DR1 and DR2 are arranged to send images to the first PACS server, CT1 and CT2 are arranged to send images to the second PACS server, and so on; that is, each PACS server only accepts medical files of a single type.

[0065] In other embodiments, the number and arrangement of the PACS servers can also be adjusted as needed to meet the needs of receiving medical files in different situations.

[0066] Further, the generation node of the medical file is the time point at which the medical file is initially collected by the PACS server, and the life length of the medical file refers to the time during which the medical file is generally used.

[0067] In a specific embodiment, the life length of the medical image file is 0-3 days, and the life length of the review report file is completed within 0-15 days. In order to facilitate operation, the life length of the medical file is generally set to 30 days.

[0068] In a specific embodiment, in order to facilitate data processing, the life length of the medical files processed by the same PACS server is set to the same value.

[0069] In other embodiments, the time length of the life length can also be set according to actual needs.

[0070] As a preferred embodiment, in step S102, in order to determine the life cycle of the medical file, the generation node and the life length are summed to determine the life cycle of the medical file, that is, the generation node is taken as the starting point, and the life length is taken as the length to determine the time length of the life cycle of the medical file.

[0071] As a preferred embodiment, in order to determine whether the medical file is in the hot period, it is necessary to determine whether the current date is included in the life cycle, that is, to determine whether the life cycle of the medical file has been completely consumed, so as to determine whether the medical file is in the hot period; as long as the current date is included in the life cycle, it is determined that the medical file is in the hot period; otherwise, it is determined that the medical file is in the warm period.

[0072] In a specific embodiment, in order to expand the range of the hot period, implement the early reservation of the medical file, the current date can also be replaced by a future date, that is, as long as the life cycle of the medical file includes a period of time that has not occurred, it is determined that the corresponding medical file is in the hot period.

[0073] As a preferred embodiment, in step S103, after determining the life cycle of the medical file, it is also necessary to store the medical file according to a preset storage strategy, wherein the preset storage strategy includes a classification storage strategy, a state switching storage strategy, and a scheduling storage strategy.

[0074] In a specific embodiment, the classification storage strategy includes: first, determining whether the medical file is in the hot period; when it is determined that the medical file is in the hot period, the storage path of the corresponding medical file is stored in the first storage medium and the second storage medium respectively, that is, in order to obtain the medical file in time, while avoiding increasing the storage pressure of the first storage medium and the second storage medium, the storage path of the medical file is stored in the first storage medium and the second storage medium, when the medical file is needed, only the corresponding storage path needs to be searched; when it is determined that the hot period of the medical file ends, that is, in the warm period, the storage path of the corresponding medical file is only stored in the second storage medium, which not only avoids adding too much storage pressure to the second storage medium, but also ensures that the medical file is obtained.

[0075] As a preferred embodiment, the first storage medium is a solid state disk, and the second storage medium is a network storage. Generally, the solid state disk is an M.2 interface or a SATA3 interface, which is directly connected with the system through the PCI-E bus of the host board, and the response speed is much better than that of the local mechanical hard disk.

[0076] In a specific embodiment, the state switching storage strategy includes: first, real-time obtaining of the state switching medical file whose hot period is about to end, that is, real-time monitoring of the medical file in the hot period, so as to timely comb the medical file whose life cycle state is about to switch; then, confirming the storage path of the state switching medical file in the second storage medium, so as to ensure that the storage path of the state switching medical file exists in the second storage medium, and the state switching medical file can be found in time in the future; finally, triggering an instruction to delete the storage path of the state switching medical file in the first storage medium at a preset idle time, that is, for the medical file whose hot period ends, the corresponding storage path cannot be directly found in the first storage medium in the future.

[0077] In the embodiment, in order to ensure the completeness of the medical files in the life cycle, since the medical files and the storage path thereof are only stored in the first storage medium by default when the medical files are initially acquired, the medical files in the hot period also need to be stored to the second storage medium, so that when the life cycle of the medical files in the hot period ends and the first storage medium deletes the related medical files, the completeness of the medical files can also be ensured.

[0078] In a specific embodiment, the medical files in the hot period are copied from the first storage medium to the second storage medium when the system is idle.

[0079] In a specific embodiment, after the PACS server receives the medical files, the PACS server not only immediately stores the medical files to the first storage medium, but also establishes a task of storing the medical files to the second storage medium in the background. When the system is idle, the background task is performed according to the order of the set time, so as to realize the storage of the medical files to the second storage medium. In other words, for the newly received medical files, not only are the medical files stored in the first storage medium with higher response capability, but also the medical files are completely copied and stored to the second storage medium, that is, the second storage medium is used as a unified storage location of the medical files, so as to ensure the completeness of the medical files.

[0080] In a specific embodiment, for the medical files whose life cycle ends, the medical files are sorted according to the time of the generation node, and the corresponding medical files are removed in the night, so as to reduce the task amount of the system in the working time and reduce the working pressure of the system.

[0081] In other embodiments, the deletion time can also be set according to the generation node, and the deletion task is performed immediately when the life cycle of the medical files ends.

[0082] As a preferred embodiment, after the medical files are classified and stored in step S103, the storage location of the medical files needs to be adjusted in response to the scheduling instruction, for example, Figure 2 As shown in Figure 2 The flowchart of an embodiment of the application for adjusting the storage location of the medical files is shown in the figure, which comprises:

[0083] Step S131: Real-time acquisition of the calling instruction of the medical files.

[0084] Step S132: Determination of the update generation node of the medical files to be called according to the calling instruction.

[0085] Step S133: Determination of the update life cycle of the medical files to be called according to the update generation node and the life length.

[0086] Step S134: According to the update life cycle, the storage location of the to-be-called medical file is adjusted correspondingly.

[0087] In this embodiment, first, the calling instruction of the medical file is acquired in real time, and the update generation node of the to-be-called medical file is determined according to the calling instruction; then, the update life cycle of the to-be-called medical file is determined according to the update generation node and the life length; finally, the storage location of the to-be-called medical file is adjusted correspondingly according to the update life cycle.

[0088] In this embodiment, the update generation node of the to-be-called medical file is determined through the calling instruction, which can flexibly control the position of the update generation node of the to-be-called medical file, thereby flexibly determining the update life cycle of the to-be-called medical file and adjusting the storage location of the to-be-called medical file; by flexibly controlling the update life cycle of the to-be-called medical file, the storage location of the medical file can be flexibly adjusted, the storage pressure of the first storage medium can be reduced, the response speed of the system can be improved, and the problem of lag in the data processing process can be avoided.

[0089] As a preferred embodiment, in step S132, in order to determine the update generation node of the to-be-called medical file, as shown in Figure 3 , the update generation node of the to-be-called medical file is determined according to the calling instruction and the life length of the to-be-called medical file. Figure 3 The flowchart of an embodiment for determining the update generation node of the to-be-called medical file provided by the present application includes:

[0090] Step S1321: It is judged whether the to-be-called medical file is in the hot period.

[0091] Step S1322: If yes, it is judged whether the calling instruction is a positive calling instruction; if yes, the generation node of the to-be-called medical file is updated to the current node; if no, the life length of the to-be-called medical file is updated to zero.

[0092] Step S1323: If no, the generation node of the to-be-called medical file is updated to the current node.

[0093] In this embodiment, it is first judged whether the to-be-called medical file is in the hot period; when it is judged that the to-be-called medical file is in the hot period, it is further judged whether the calling instruction is a positive calling instruction; if yes, the generation node of the to-be-called medical file is updated to the current node; if no, the life length of the to-be-called medical file is updated to zero; when it is judged that the to-be-called medical file is in the warm period, the generation node of the to-be-called medical file is updated to the current node.

[0094] In this embodiment, whether the to-be-called medical file is in the hot period is determined, so as to determine the storage location where the to-be-called medical file is currently located. If the to-be-called medical file is in the hot period, it indicates that the to-be-called medical file is at least stored in the first storage medium, that is, the to-be-called medical file is the current commonly used medical file data of the system. Therefore, it is further needed to determine whether the calling instruction is a positive calling instruction. If yes, it indicates that the demand for the to-be-called medical file is improved, and the life cycle of the to-be-called medical file needs to be prolonged. The generation node of the to-be-called medical file is updated to the current node, so as to prolong the life cycle of the to-be-called medical file. If no, it indicates that the data of the to-be-called medical file is no longer needed by the current system, and the life cycle of the to-be-called medical file needs to be shortened. The life length of the to-be-called medical file is adjusted to zero, so as to directly end the life cycle of the to-be-called medical file. If the to-be-called medical file is in the warm period, it indicates that the to-be-called medical file is only stored in the second storage medium, that is, the to-be-called medical file needs to be converted from the current low demand state to the high demand state, that is, the to-be-called medical file needs to be copied to the first storage medium. In this embodiment, the generation node of the to-be-called medical file is converted to the current node, so as to adjust the life cycle of the to-be-called medical file.

[0095] In this embodiment, whether the to-be-called medical file is in the hot period is determined, so as to determine the storage location where the to-be-called medical file is currently located. If the to-be-called medical file is in the hot period, it indicates that the to-be-called medical file is at least stored in the first storage medium, that is, the to-be-called medical file is the current commonly used medical file data of the system. Therefore, it is further needed to determine whether the calling instruction is a positive calling instruction. If yes, it indicates that the demand for the to-be-called medical file is improved, and the life cycle of the to-be-called medical file needs to be prolonged. The generation node of the to-be-called medical file is updated to the current node, so as to prolong the life cycle of the to-be-called medical file. If no, it indicates that the data of the to-be-called medical file is no longer needed by the current system, and the life cycle of the to-be-called medical file needs to be shortened. The life length of the to-be-called medical file is adjusted to zero, so as to directly end the life cycle of the to-be-called medical file. If the to-be-called medical file is in the warm period, it indicates that the to-be-called medical file is only stored in the second storage medium, that is, the to-be-called medical file needs to be converted from the current low demand state to the high demand state, that is, the to-be-called medical file needs to be copied to the first storage medium. In this embodiment, the generation node of the to-be-called medical file is converted to the current node, so as to adjust the life cycle of the to-be-called medical file.

[0096] As a preferred embodiment, the calling instruction is triggered based on identity verification, coding verification and disease verification.

[0097] In a specific embodiment, when the calling instruction is an ID card number or a patient ID, it indicates that the corresponding patient is re-admitted for review or inpatient. At this time, in order to improve the detection efficiency and avoid allergic reactions, the calling instruction is defined as a positive calling instruction. The medical file corresponding to the ID card number or the patient ID is obtained in the second storage medium, and the generation node of the medical file is updated to the current node, so as to adjust the update life cycle of the medical file. Correspondingly, the medical file is copied from the second storage medium to the first storage medium, so as to facilitate the system to improve the response speed of the medical file in the subsequent data processing process and avoid lag.

[0098] In a specific embodiment, when the calling instruction is a patient state and the patient state is discharged, it indicates that the corresponding medical file is no longer needed for data processing, and therefore, the calling instruction is defined as a negative calling instruction, the medical file corresponding to the patient state is obtained from the first storage medium, the generation node of the medical file is updated to infinitesimal, so as to adjust the medical file from the hot period to the warm period, and then the medical file is directly deleted from the first storage medium, thereby reducing the data storage amount of the first storage medium and reducing the load of the system.

[0099] As a preferred embodiment, in step S134, in order to adjust the storage location of the medical file to be called, as shown in Figure 4 Figure 4 The flowchart of an embodiment of adjusting the storage location of the medical file to be called provided by the present application comprises:

[0100] Step S1341: determining whether the update life cycle is in the hot period.

[0101] Step S1342: if yes, storing the storage path of the medical file to be called to the first storage medium and the second storage medium.

[0102] Step S1343: if no, storing the storage path of the medical file to be called to only the second storage medium.

[0103] In the embodiment, by controlling the update life cycle of the medical file to be called, the storage path of the medical file to be called is managed, so that the storage location of the storage path of the medical file is updated in real time, which not only meets the requirements of the calling instruction, but also avoids the redundancy that may occur in the storage process of the first storage medium and the second storage medium.

[0104] In the above manner, first, the generation node and the life length of the medical file are obtained to determine the life cycle of the medical file, wherein the life cycle comprises a hot period and a warm period; then, according to the life cycle of the medical file, the medical file in the hot period is stored in the first storage medium, and the medical file in the warm period is stored only in the second storage medium, so as to realize the classified storage of the medical file and improve the response speed of the system to the medical file; finally, the update generation node of the medical file to be called is adjusted according to the calling instruction, and the storage location of the medical file to be called is updated according to the update generation node, so as to realize the multi-node adjustment of the medical file, thereby timely adjusting the storage location of the medical file to be called and avoiding the problem of lag in the data processing process caused by improper storage of the medical file.

[0105] In order to solve the above problems, the present application further provides a medical file multi-node storage device based on a life cycle, as shown in Figure 5 ​​Figure 5 A structure schematic diagram of an embodiment of the life cycle based medical file multi-node storage device provided by the present application is shown in the figure, the life cycle based medical file multi-node storage device 500 comprises:

[0106] A life length acquisition module 501 is configured to acquire the generation node and the life length of the medical file.

[0107] A life cycle determination module 502 is configured to determine the life cycle of the medical file according to the generation node and the life length, wherein the life cycle comprises a hot period and a warm period.

[0108] A multi-node storage module 503 is configured to perform multi-node storage of the medical file according to the life cycle and a preset storage strategy, wherein the medical file in the hot period is stored in at least the first storage medium, the medical file in the warm period is stored only in the second storage medium, and the response speed of the first storage medium is faster than that of the second storage medium.

[0109] Further, the life cycle determination module 502 comprises a life cycle control unit configured to control the life cycle of the medical file, to determine whether the medical file is currently in the hot period in real time, and to input the determination result to the multi-node storage module 503.

[0110] Further, the multi-node storage module 503 further comprises a preset storage strategy control module, specifically comprising a classification storage strategy control unit, a state switching storage strategy control unit and a scheduling storage strategy control unit, respectively configured to execute the classification storage strategy, the state switching storage strategy and the scheduling storage strategy as described above.

[0111] In order to solve the above problems, the present application further provides a life cycle based medical file multi-node storage system, comprising a first storage medium, a second storage medium and a life cycle based medical file multi-node storage device as described above.

[0112] The present application further provides a computer readable storage medium having a life cycle based medical file multi-node storage program stored thereon, and the computer program is executed by a processor to implement the life cycle based medical file multi-node storage method as described in any of the above technical solutions.

[0113] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when executed, can include the processes of the above-mentioned embodiment methods. Any reference to memory, storage, database, or other medium used in the embodiments provided by the present application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration but not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0114] The above descriptions are only the preferred embodiments of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed by the present application, which should be covered within the protection scope of the present application.

Claims

1. A lifecycle-based multi-node storage method for medical files, characterized in that, include: Obtain the generation node and lifespan of medical documents; The lifecycle of the medical document is determined based on the generated node and the lifespan, wherein the lifecycle includes a hot period and a warm period; According to the life cycle, the medical files are stored in multiple nodes according to a preset storage strategy. The medical files in the hot phase are stored at least in the first storage medium, and the medical files in the warm phase are stored only in the second storage medium. The response speed of the first storage medium is faster than that of the second storage medium. The preset storage strategy includes a classification storage strategy, a state switching storage strategy, and a scheduling storage strategy; The medical files are stored on multiple nodes according to the aforementioned scheduling and storage strategy, including: Real-time acquisition of the medical file access instructions; Based on the invocation instruction, determine the update generation node of the medical file to be invoked; The update lifecycle of the medical file to be invoked is determined based on the update generation node and the lifespan. Based on the update lifecycle, the storage location of the medical file to be invoked is adjusted accordingly; The invocation instructions include positive invocation instructions and negative invocation instructions; determining the update generation node of the medical file to be invoked based on the invocation instructions includes: Determine whether the medical file to be retrieved is in the hot period; If yes, determine whether the calling instruction is a forward calling instruction; if yes, update the generation node of the medical file to be called to the current node; if no, adjust the lifespan of the medical file to be called to zero. If not, update the generated node of the medical file to be invoked to the current node.

2. The lifecycle-based multi-node storage method for medical files according to claim 1, characterized in that, Determining the lifecycle of the medical document based on the generation node and the lifespan includes: Determine whether the current date is included in the lifecycle; If so, then the medical document is determined to be in the hot period; If not, then the medical document is determined to be in the stated warm period.

3. The lifecycle-based multi-node storage method for medical files according to claim 1, characterized in that, The medical files are stored in a multi-node manner according to the aforementioned classification and storage strategy, including: Determine whether the medical document is in the hot period; If yes, the storage path of the corresponding medical file is stored in both the first storage medium and the second storage medium; otherwise, the storage path of the corresponding medical file is stored only in the second storage medium.

4. The lifecycle-based multi-node storage method for medical files according to claim 1, characterized in that, The medical files are stored in a multi-node manner according to the state switching storage strategy, including: Real-time acquisition of medical files awaiting switching as the heat cycle is about to end; Confirm the storage path of the medical file whose status needs to be switched in the second storage medium; During a preset idle time, an instruction is triggered to delete the storage path of the medical file whose status is to be switched in the first storage medium.

5. The lifecycle-based multi-node storage method for medical files according to claim 1, characterized in that, The step of adjusting the storage location of the medical file to be invoked according to the update lifecycle includes: Determine whether the update lifecycle is in the hot period; If so, the storage path of the medical file to be invoked is stored in the first storage medium and the second storage medium; If not, the storage path of the medical file to be invoked will be stored only in the second storage medium.

6. A lifecycle-based multi-node storage device for medical files, characterized in that, include: The lifespan acquisition module is used to obtain the generation node and lifespan of medical files; A lifecycle determination module is used to determine the lifecycle of the medical document based on the generation node and the lifespan, wherein the lifecycle includes a hot period and a warm period; A multi-node storage module is used to store the medical files in multiple nodes according to the life cycle and a preset storage strategy, wherein medical files in the hot phase are stored at least in the first storage medium, and medical files in the warm phase are stored only in the second storage medium, and the response speed of the first storage medium is faster than that of the second storage medium. The preset storage strategy includes a classification storage strategy, a state switching storage strategy, and a scheduling storage strategy; The medical files are stored on multiple nodes according to the aforementioned scheduling and storage strategy, including: Real-time acquisition of the medical file access instructions; Based on the invocation instruction, determine the update generation node of the medical file to be invoked; The update lifecycle of the medical file to be invoked is determined based on the update generation node and the lifespan. Based on the update lifecycle, the storage location of the medical file to be invoked is adjusted accordingly; The invocation instructions include positive invocation instructions and negative invocation instructions; determining the update generation node of the medical file to be invoked based on the invocation instructions includes: Determine whether the medical file to be retrieved is in the hot period; If yes, determine whether the calling instruction is a forward calling instruction; if yes, update the generation node of the medical file to be called to the current node; if no, adjust the lifespan of the medical file to be called to zero. If not, update the generated node of the medical file to be invoked to the current node.

7. A lifecycle-based multi-node storage system for medical documents, characterized in that, It includes a first storage medium, a second storage medium, and a lifecycle-based multi-node storage device for medical documents as described in claim 6.

Images