Component package debugging method and device for medical platform software, equipment and medium

Abstract

The invention discloses a component package debugging method and device for medical platform software, equipment and a medium, relates to the technical field of computers, is applied to a storage space, and comprises the following steps: receiving a component package acquisition request sent by a target medical project in target medical platform software, and generating a corresponding component package storage address; sending the component package storage address to the target medical project, and establishing a soft link in the target medical project based on the component package storage address; and monitoring a target component package corresponding to the component package acquisition request in the storage space, and when the target component package is updated, updating a component package storage address contained in a soft link in the target medical project based on the updated component package, and executing a component package debugging operation based on the updated storage address. According to the method, all the component packages are put into the global component package warehouse, and the component packages are obtained in a soft and hard link mode, so that all the used medical projects are automatically and synchronously updated when the component packages are updated, and the stability and the production efficiency of medical platform-level software development are improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device, equipment and medium for debugging component packages of medical platform software. Background Art

[0002] In the complex environment of medical software development, medical platform software often contains many sub-component packages to meet the diverse needs of different medical projects. Various businesses and methods are often extracted into various components or packages to solve the same part of the business and logic in different projects. For example, a comprehensive medical information management platform may cover multiple sub-projects such as medical image processing, medical record management, and drug development simulation. Each sub-project (target medical project) may send a component package acquisition request. Taking the medical image processing sub-project as an example, it may require a specific image processing component package to achieve accurate analysis and processing functions for images such as X-rays and CT (Computed Tomography). However, component packages are created, developed and debugged. Each update and release will re-acquire the corresponding component package. For example, 10 projects use the same component package. This component package is updated and upgraded once, and 10 projects will manually update the component package 10 times. This is a repetitive assembly line work with low production efficiency. With the increasing amount of medical software development, the local development and debugging automation of component packages has become a major pain point. Summary of the invention

[0003] In view of this, the purpose of the present invention is to provide a component package debugging method, device, equipment and storage medium, which can automate development and debugging and improve production efficiency. The specific scheme is as follows:

[0004] In a first aspect, the present invention discloses a component package debugging method, which is applied to a storage space and includes:

[0005] Receiving a component package acquisition request sent by a target medical project in a target medical platform software, so as to generate a corresponding component package storage address based on the component package acquisition request;

[0006] Sending the component package storage address to the target medical project, and establishing a soft link in the target medical project based on the component package storage address;

[0007] Monitor the target component package corresponding to the component package acquisition request in the storage space, and when the target component package is updated, update the component package storage address contained in the soft link in the target medical project based on the updated component package, and perform component package debugging operations based on the updated storage address.

[0008] Optionally, before the receiving of the component package acquisition request sent by the target medical project in the target medical platform software so as to generate the corresponding component package storage address based on the component package acquisition request, the method further includes:

[0009] Create a global warehouse, obtain the component package created by the developer, and store the component package in the corresponding storage folder in the global warehouse;

[0010] A version control tool is used to manage all the component packages in the global repository.

[0011] Optionally, storing the component package in a corresponding storage folder in the global warehouse includes:

[0012] The code files, configuration files and instruction documents corresponding to each component package are stored in the corresponding and unique storage folder in the global warehouse; wherein the instruction document includes the functional usage and precautions of the component package.

[0013] Optionally, obtaining the component package created by the developer includes:

[0014] Creating a current component package, and naming the current component package based on a preset naming method to obtain an initial version number;

[0015] Determine whether the developer modifies the current component package;

[0016] If the developer has modified the current component package, determining a modified version number corresponding to the modified component package based on the modification information and the version number update rule;

[0017] Accordingly, obtaining the component package created by the developer and storing the component package in a corresponding storage folder in the global warehouse includes:

[0018] The modified component package created by the developer is obtained, and the modified component package is stored in the corresponding new storage folder in the global warehouse.

[0019] Optionally, if the developer has modified the current component package, before determining the modified version number corresponding to the modified component package based on the modification information and the version number update rule, the method further includes:

[0020] A component package modification command in the temporary storage area is obtained, and the current component package is modified based on the modification description information contained in the component package modification command to obtain the modified component package.

[0021] Optionally, before monitoring the target component package corresponding to the component package acquisition request in the storage space, the method further includes:

[0022] A corresponding hard link is set for each component package in the global warehouse; the hard link contains a reference address of a file storage unit corresponding to the component package;

[0023] When any one of the component packages in the global warehouse changes, the reference address in the corresponding hard link is automatically modified based on the changed storage address of the changed component package in the global warehouse.

[0024] In a second aspect, the present invention discloses a component package debugging device, which is applied to a storage space and includes:

[0025] When the target component package is updated, obtaining an updated component package storage address corresponding to the updated component package; wherein the updated component package storage address is generated based on the latest reference address;

[0026] The component package storage address in the soft link of the target medical project is replaced with the updated component package storage address, so that the updated component package is accessed based on the updated component package storage address when a component package access operation is triggered.

[0027] In a third aspect, the present invention discloses an electronic device, comprising:

[0028] Memory, used to store computer programs;

[0029] The processor is used to execute the computer program to implement the steps of the component package debugging method disclosed above.

[0030] In a fourth aspect, the present invention discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the component package debugging method disclosed above is implemented.

[0031] It can be seen that the present invention provides a component package debugging method, including: receiving a component package acquisition request sent by a target medical project in a target medical platform software, so as to generate a corresponding component package storage address based on the component package acquisition request; sending the component package storage address to the target medical project, and establishing a soft link in the target medical project based on the component package storage address; monitoring the target component package corresponding to the component package acquisition request in the storage space, and when the target component package is updated, updating the component package storage address contained in the soft link in the target medical project based on the updated component package, and performing component package debugging operations based on the updated storage address. It can be seen that the present invention establishes a global component package warehouse, puts all component packages into the global warehouse and obtains component packages by means of soft and hard links, ensuring the consistency of the component packages, and when the component package is updated, all projects using the component package are automatically updated synchronously, so that development and debugging are automated, the workload of manual operations is reduced, and production efficiency is improved. The code in the global component package warehouse can be directly used through the soft and hard link project without copying or downloading, which accelerates local development, debugging and testing. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0033] Figure 1 A flowchart of a component package debugging method disclosed in the present invention;

[0034] Figure 2 A schematic diagram of a soft and hard link disclosed in the present invention;

[0035] Figure 3 A schematic diagram of a debugging process disclosed in the present invention;

[0036] Figure 4 A schematic diagram of a process of placing a component package disclosed in the present invention into a global component package warehouse;

[0037] Figure 5 A flowchart of a specific component package debugging method disclosed in the present invention;

[0038] Figure 6 It is a structural schematic diagram of a component package debugging device disclosed in the present invention;

[0039] Figure 7 The present invention is a structural diagram of an electronic device disclosed in the present invention. DETAILED DESCRIPTION

[0040] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0041] At present, in the process of software development, various businesses and methods are often extracted into various components or packages, which are used to solve the same part of business and logic in different projects. However, component packages are created, developed and debugged, and each update and release corresponding to the use of the component package will be re-acquired. For example, 10 projects use the same component package, and this component package is updated and upgraded once. 10 projects will manually update the component package 10 times, which belongs to repetitive assembly line work and has low production efficiency. With the increasing number of software development projects, the local development and debugging automation of component packages has become a major pain point. To this end, the present invention provides a component package debugging method, which can automate development and debugging and improve production efficiency.

[0042] The embodiment of the present invention discloses a component package debugging method, see Figure 1 As shown, applied to a storage space, the method includes:

[0043] Step S11: receiving a component package acquisition request sent by a target medical project in a target medical platform software, so as to generate a corresponding component package storage address based on the component package acquisition request.

[0044] In this embodiment, a component package acquisition request sent by a target medical project in the target medical platform software is received so as to generate a corresponding component package storage address based on the component package acquisition request. The developer establishes a global component package warehouse on the local machine and uses a version control tool (such as Git) to manage the component packages in the warehouse. The developer puts the developed component package into the global warehouse, and each component package should have its own folder, which contains the component code, configuration files and documents, etc. When storing the component package in the warehouse, it is implemented by the following code: git remote add origin <warehouse URL>, git push -u origin master, where <warehouse URL (Uniform Resource Locator)> is the address of the global component package warehouse. Therefore, after receiving the component package acquisition request sent by the target medical project, the target component package corresponding to the component package acquisition request is determined, the location of the target component package is determined from the component package warehouse and the corresponding component package storage address is generated. Select a version control tool, such as Git, to track and manage changes in component packages. In the selected version control tool, create a new warehouse for storing component packages. For example, use the following command on the command line to complete: git init package-table, create a new warehouse named package-table in the current directory. When uploading a component package, copy the component package files (code, configuration files, documents, etc.) to the corresponding folder of the warehouse, ensure that each component package has an independent folder and is named according to consistent naming rules. When changes need to be made to the component package, use the following command to submit the changes in the staging area to the warehouse and add a message describing the submission content, for example: gitcommit -m "Add initial version of package-table". It should be noted that the storage address generated based on the component package acquisition request is crucial for the development of medical platform software. Just as medical data requires a specific storage location in the hospital information system, the storage address of the component package ensures that each sub-component package can be accurately obtained and used in the medical platform software. Reasonable storage address planning helps maintain the stability and efficiency of the imaging cloud platform and avoid component package acquisition errors or system failures caused by storage confusion.

[0045] Step S12: Sending the component package storage address to the target medical project, and establishing a soft link in the target medical project based on the component package storage address.

[0046] In this embodiment, a component package acquisition request sent by a target medical project in the target medical platform software is received, so that after the corresponding component package storage address is generated based on the component package acquisition request, the component package storage address is sent to the target medical project, and a soft link is established in the target medical project based on the component package storage address. Soft link (soft link, also called symbolic link Symbolic link), symbolic link is a special type of file; (can be understood as a shortcut) contains a reference to other files or directories in the form of an absolute path or a relative path. The soft link establishment module plays a vital role in medical system integration. Soft link is similar to establishing a seamless connection channel between various medical subsystems under the development of medical platform software. For example, a soft link is established between the electronic medical record system, pharmacy management system and medical equipment management system of a hospital, so that these systems can share information in real time, just like establishing a soft link in the target project through the soft link establishment module to obtain the component package. This seamless connection can greatly improve the efficiency and quality of medical services and reduce delays and errors in information transmission. At the same time, the use of soft links avoids the repeated storage of data and saves space.

[0047] Step S13: Monitor the target component package corresponding to the component package acquisition request in the storage space, and when the target component package is updated, update the component package storage address contained in the soft link in the target medical project based on the updated component package, and perform component package debugging operations based on the updated storage address.

[0048] In this embodiment, before monitoring the target component package corresponding to the component package acquisition request in the storage space, a corresponding hard link is set for each component package in the global warehouse; the hard link contains the reference address of the file storage unit corresponding to the component package; when any component package in the global warehouse changes, the reference address in the corresponding hard link is automatically modified based on the changed storage address of the changed component package in the global warehouse. In the development of medical platform software, monitoring the update of sub-component packages is of great significance. With the continuous progress of medical research and the continuous development of clinical practice, sub-component packages in medical software need to be updated in time to adapt to new needs. For example, an algorithm component package for disease diagnosis may be continuously optimized with new medical research results. When this component package is updated, the part of the medical project using the component package can be automatically and synchronously updated by the method of the present invention to ensure the accuracy and advancement of medical diagnosis. Real-time updating of sub-component packages can keep medical software in the best performance state at all times and provide patients with better medical services.

[0049] Furthermore, the component package storage address is sent to the target medical project, and after a soft link is established in the target medical project based on the component package storage address, the target component package corresponding to the component package acquisition request in the storage space is monitored, and when the target component package is updated, the component package storage address contained in the soft link in the target medical project is updated based on the updated component package, and the component package debugging operation is performed based on the updated storage address. Specifically, when the target component package is updated, the updated component package storage address corresponding to the updated component package is obtained; wherein the updated component package storage address is generated based on the latest reference address; and the component package storage address in the soft link of the target medical project is replaced with the updated component package storage address, so that the updated component package is accessed based on the updated component package storage address when the component package access operation is triggered.

[0050] It can be understood that a hard link is a file storage unit that is shared equally by multiple files in a computer file system. The characteristic of a hard link is that when the content in file a is modified, the content in the corresponding hard link file b is also automatically synchronized with the modified content, thereby achieving automatic update of local development and debugging. At the same time, multiple files sharing the same file storage unit equally will also greatly save disk space. Figure 2 As shown, hard links are connected to storage space, while soft links are connected to hard links. For projects that need to use component packages, you can obtain component packages in the global component package repository through soft and hard links.

[0051] like Figure 3 As shown, when the component package code changes, the updated component package is submitted to the global component package repository, such as Figure 4 As shown, create a package and name it, add the component package file with version number containing code files, instructions and other information to the global component package repository. Then, as mentioned above Figure 3 As shown, the project obtains the component package from the global component package warehouse for preview use. After the component package is debugged, the corresponding component package is obtained from the global component package warehouse for production and launch.

[0052] During the creation, development and debugging stages of component packages, the present invention establishes a global component package warehouse on the developer's local computer, puts all component packages into the global warehouse, and projects that need to use the component packages obtain the component packages through soft and hard linking. When the component packages are updated, they are replaced and stored in the corresponding global warehouse, so that after the component packages are updated in the development and debugging stages, all projects that use the component packages are automatically updated synchronously, making the local development and debugging of the component packages automated, so that software developers can focus on the development of core business logic without spending a lot of energy on repeated component package development and debugging.

[0053] It can be seen that the present invention provides a component package debugging method, including: receiving a component package acquisition request sent by a target medical project in a target medical platform software, so as to generate a corresponding component package storage address based on the component package acquisition request; sending the component package storage address to the target medical project, and establishing a soft link in the target medical project based on the component package storage address; monitoring the target component package corresponding to the component package acquisition request in the storage space, and when the target component package is updated, updating the component package storage address contained in the soft link in the target medical project based on the updated component package, and performing component package debugging operations based on the updated storage address. It can be seen that the present invention establishes a global component package warehouse, puts all component packages into the global warehouse and obtains component packages by means of soft and hard links, ensuring the consistency of the component packages, and when the component package is updated, all projects using the component package are automatically updated synchronously, so that development and debugging are automated, the workload of manual operations is reduced, and production efficiency is improved. The code in the global component package warehouse can be directly used through the soft and hard link project without copying or downloading, which accelerates local development, debugging and testing.

[0054] See also Figure 5 As shown, an embodiment of the present invention discloses a component package debugging method, which is applied to a storage space. Compared with the previous embodiment, this embodiment further illustrates and optimizes the technical solution.

[0055] Step S21: Create a global warehouse, obtain the component package created by the developer, and store the component package in a corresponding storage folder in the global warehouse.

[0056] In this embodiment, a global warehouse is created, component packages created by developers are obtained, and the component packages are stored in corresponding storage folders in the global warehouse. Specifically, the code files, configuration files, and instruction documents corresponding to each component package are stored in the corresponding and unique storage folder in the global warehouse; wherein the instruction document contains the functional usage and precautions of the component package. All the component packages in the global warehouse are managed using version control tools.

[0057] It can be understood that, a current component package is created, and the current component package is named based on a preset naming method to obtain an initial version number; it is determined whether the developer has modified the current component package; if the developer has modified the current component package, the modified version number corresponding to the modified component package is determined based on the modification information and the version number update rule; accordingly, obtaining the component package created by the developer and storing the component package in the corresponding storage folder in the global warehouse includes: obtaining the modified component package created by the developer, and storing the modified component package in the corresponding new storage folder in the global warehouse.

[0058] If the developer has modified the current component package, before determining the modified version number corresponding to the modified component package based on the modification information and the version number update rule, obtain the component package change command in the temporary storage area, and modify the current component package based on the modification description information contained in the component package change command to obtain the modified component package.

[0059] The naming rules of component packages are as follows: The naming of component packages should be descriptive, easy to understand and follow certain naming rules so that developers can easily identify and use them, such as using an agreed naming prefix or suffix. The version number is a naming method used to identify the uniqueness of the current version. The naming conventions of component package version numbers are as follows: The standard version number uses the format of VX.YZ, such as V5.3.2; where V (version number) represents the version number; X, Y, and Z are non-negative integers, X is the major version number, Y is the minor version number, and Z is the revision number. The first released version is named V1.0.0, and each time a version is updated, the version number is +1. The update rules of the version number are as follows: when fixing bugs and optimizing functions, the third digit is modified and superimposed, i.e. Z+1, and the rest remain unchanged, such as V1.0.0-V1.0.1; when adding a small function, the second digit is modified and superimposed, i.e. Y+1, and the rest remain unchanged, such as V1.0.0-V1.1.0; when adding a big function or making a big change to the original function, the first digit is modified and superimposed, i.e. X+1, and the rest remain unchanged, such as V1.0.0-V2.0.0. After the previous digits are superimposed, the following digits are counted from zero.

[0060] Step S22: receiving a component package acquisition request sent by a target medical project in the target medical platform software, so as to generate a corresponding component package storage address based on the component package acquisition request.

[0061] Step S23: Sending the component package storage address to the target medical project, and establishing a soft link in the target medical project based on the component package storage address.

[0062] Step S24: monitor the target component package corresponding to the component package acquisition request in the storage space, and when the target component package is updated, update the component package storage address contained in the soft link in the target medical project based on the updated component package, and perform component package debugging operations based on the updated storage address.

[0063] In a specific implementation, the actual application code of the soft and hard link is as follows:

[0064] ****Locally developed software A****

[0065] |_ A -> .packages / A@1.0.0 / node_modules / A

[0066] |_ B -> .packages / B@1.0.0 / node_modules / B

[0067] |_ .packages

[0068] |_ A@1.0.0

[0069] |_ node_modules

[0070] |_ A =>Global component package repository / A

[0071] |_ C -> .. / .. / C@1.0.0 / node_modules / C

[0072] |_ B@1.0.0

[0073] |_ node_modules

[0074] |_ B =>Global component package repository / B

[0075] |_ C -> .. / .. / C@2.0.0 / node_modules / C

[0076] |_ C@1.0.0

[0077] |_ node_modules

[0078] |_ C =>Global component package repository / C

[0079] |_ C@2.0.0

[0080] |_ node_modules

[0081] |_ C =>Global component package repository / C

[0082] ****Locally developed software B****

[0083] |_ A -> .packages / A@1.0.0 / node_modules / A

[0084] |_ B -> .packages / B@1.0.0 / node_modules / B

[0085] |_ .packages

[0086] |_ A@1.0.0

[0087] |_ node_modules

[0088] |_ A =>Global component package repository / A

[0089] |_ C -> .. / .. / C@1.0.0 / node_modules / C

[0090] |_ B@1.0.0

[0091] |_ node_modules

[0092] |_ B =>Global component package repository / B

[0093] |_ C -> .. / .. / C@2.0.0 / node_modules / C

[0094] |_ C@1.0.0

[0095] |_ node_modules

[0096] |_ C =>Global component package repository / C

[0097] |_ C@2.0.0

[0098] |_ node_modules

[0099] |_ C => global component package repository / C;

[0100] In actual software development, for example, there are two softwares under development, namely local development software A and local development software B. In local development software A and local development software B, there are three files A, B, and .packages. The reference of A and B files is a soft link, representing component A and component B respectively. These two files contain a reference to other global component package repositories in the form of absolute paths. The content pointed to by the inode of the soft link actually saves an absolute path. A and B files are only a few KB in size, where the path of A file is .packages / A@1.0.0 / node_modules / A, and the path of B file is .packages / B@1.0.0 / node_modules / B. The reference of .packages file is a hard link, which means that multiple files in the computer file system share the same file storage unit equally, which means that local development software A and local development software B share the same file storage unit equally. The component package content referenced by A and B files comes from the .packages file, and the .packages file content is obtained from the global component package repository through hard links. The .packages file content includes A@1.0.0, B@1.0.0, C@1.0.0, C@2.0.0 in the global component package repository. Through the characteristics of hard links, when the content of the global component package repository is updated, the content in the corresponding hard link b file is also automatically synchronized with the relevant modified content, thereby achieving automatic update of local development and debugging.

[0101] The present invention manages component packages in a global component package warehouse so that all projects will use the same component package, thereby ensuring the consistency of the component packages. The version control tool can track and manage different versions of the component package so as to roll back or update when necessary. When the component packages in the global component package warehouse are updated, all projects using these component packages can be automatically and synchronously updated, thereby reducing the workload of manual operations and improving development efficiency. Developers no longer need to manually update component packages for each project, thereby saving time and energy and being able to focus more on the development of core business logic. Using soft and hard links, multiple projects share the file content of the same component package, thereby saving disk space and avoiding multiple copies of the same data. Through soft and hard links, projects can directly use the code in the global component package warehouse without copying or downloading, thereby accelerating the process of local development, debugging and testing. Automated updates reduce the possibility of manual operations, thereby reducing the risk of version inconsistencies or errors. By centralizing all component packages in a global warehouse, management and maintenance become simpler, and there is no need to maintain component packages of different versions in multiple projects. Developers can start working faster and only need to configure the global component package repository once, rather than configuring component packages project by project, which significantly improves development efficiency, reduces repetitive work, and reduces the risk of errors.

[0102] For the specific contents of the above steps S22 to S24, reference may be made to the corresponding contents disclosed in the above embodiments, which will not be repeated here.

[0103] It can be seen that the embodiment of the present application creates a global warehouse, obtains the component package created by the developer, and stores the component package in the corresponding storage folder in the global warehouse; receives a component package acquisition request sent by the target medical project in the target medical platform software, so as to generate a corresponding component package storage address based on the component package acquisition request; sends the component package storage address to the target medical project, and establishes a soft link in the target medical project based on the component package storage address; monitors the target component package corresponding to the component package acquisition request in the storage space, and when the target component package is updated, updates the component package storage address contained in the soft link in the target medical project based on the updated component package, and performs component package debugging operations based on the updated storage address, so as to automate development and debugging and improve production efficiency.

[0104] See also Figure 6 As shown, the embodiment of the present invention also discloses a component package debugging device, which is applied to the storage space and includes:

[0105] The storage address generation module 11 is used to receive a component package acquisition request sent by a target medical project in the target medical platform software, so as to generate a corresponding component package storage address based on the component package acquisition request;

[0106] A soft link establishing module 12, used for sending the component package storage address to the target medical project, and establishing a soft link in the target medical project based on the component package storage address;

[0107] A component package monitoring module 13, used to monitor the target component package corresponding to the component package acquisition request in the storage space;

[0108] The storage address updating module 14 is used to update the storage address of the component package contained in the soft link in the target medical project based on the updated component package when the target component package is updated, and perform component package debugging operations based on the updated storage address.

[0109] It can be seen that the present invention includes: receiving a component package acquisition request sent by a target medical project in the target medical platform software, so as to generate a corresponding component package storage address based on the component package acquisition request; sending the component package storage address to the target medical project, and establishing a soft link in the target medical project based on the component package storage address; monitoring the target component package corresponding to the component package acquisition request in the storage space, and when the target component package is updated, updating the component package storage address contained in the soft link in the target medical project based on the updated component package, and performing component package debugging operations based on the updated storage address. It can be seen that the present invention establishes a global component package warehouse, puts all component packages into the global warehouse and obtains component packages through soft and hard links, ensuring the consistency of the component packages. When the component package is updated, all projects that use the component package are automatically updated synchronously, making development and debugging automated, reducing the workload of manual operations, and improving production efficiency. The code in the global component package warehouse can be directly used through the soft and hard link project without copying or downloading, which accelerates local development, debugging and testing.

[0110] In some specific embodiments, the storage address generation module 11 specifically includes:

[0111] Warehouse creation unit, used to create a global warehouse;

[0112] A component package creation unit is used to create the current component package;

[0113] An initial version number obtaining unit, used for naming the current component package based on a preset naming method to obtain an initial version number;

[0114] A modification judgment unit, used to judge whether the developer has modified the current component package;

[0115] A component package change command acquisition unit, used to acquire a component package change command in a temporary storage area;

[0116] A component package modification unit, configured to modify the current component package based on the modification description information contained in the component package modification command to obtain the modified component package;

[0117] A modified version number determining unit, configured to determine a modified version number corresponding to the modified component package based on the modification information and the version number updating rule if the developer has modified the current component package;

[0118] An information storage unit, used to store the code files, configuration files and instruction documents corresponding to each component package in the corresponding and unique storage folder in the global warehouse; wherein the instruction document includes the functional usage and precautions of the component package;

[0119] The component package management unit is used to manage all the component packages in the global repository using a version control tool.

[0120] In some specific embodiments, the storage address generation module 11 specifically includes:

[0121] A component package storage address generating unit, configured to receive a component package acquisition request sent by a target medical project in a target medical platform software, so as to generate a corresponding component package storage address based on the component package acquisition request;

[0122] A modified component package acquisition unit, used to acquire the modified component package created by the developer;

[0123] The modified component package storage unit is used to store the modified component package in the corresponding new storage folder in the global warehouse.

[0124] In some specific embodiments, the soft link establishment module 12 specifically includes:

[0125] The soft link establishing unit is used to send the component package storage address to the target medical project and establish a soft link in the target medical project based on the component package storage address.

[0126] In some specific embodiments, before the component package monitoring module 13, it specifically also includes:

[0127] A hard link setting unit, used to set a corresponding hard link for each component package in the global warehouse; the hard link contains a reference address of a file storage unit corresponding to the component package;

[0128] The reference address modification unit is used to automatically modify the reference address in the corresponding hard link based on the changed storage address of the changed component package in the global warehouse when any one of the component packages in the global warehouse changes.

[0129] In some specific embodiments, the component package monitoring module 13 specifically includes:

[0130] The target component package monitoring unit is used to monitor the target component package corresponding to the component package acquisition request in the storage space.

[0131] In some specific embodiments, the storage address updating module 14 specifically includes:

[0132] An updated component package storage address acquisition unit, used for acquiring an updated component package storage address corresponding to the updated component package when the target component package is updated; wherein the updated component package storage address is generated based on the latest reference address;

[0133] A storage address replacement unit is used to replace the component package storage address in the soft link of the target medical project with the updated component package storage address, so as to access the updated component package based on the updated component package storage address when the component package access operation is triggered.

[0134] Furthermore, an embodiment of the present invention also provides an electronic device. Figure 7 This is a structural diagram of an electronic device 20 according to an exemplary embodiment, and the content in the diagram cannot be regarded as any limitation on the scope of application of the present invention.

[0135] Figure 7 The present invention provides a schematic diagram of the structure of an electronic device 20 provided in an embodiment of the present invention. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 is used to store a computer program, and the computer program is loaded and executed by the processor 21 to implement the relevant steps in the component package debugging method disclosed in any of the aforementioned embodiments. In addition, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0136] In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and the external device, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present invention, and is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs and is not specifically limited here.

[0137] In addition, the memory 22, as a carrier for storing resources, can be a read-only memory, a random access memory, a disk or an optical disk, etc. The resources stored thereon can include an operating system 221, a computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0138] The operating system 221 is used to manage and control the hardware devices and computer program 222 on the electronic device 20, which can be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program that can be used to complete the component package debugging method executed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 222 can further include a computer program that can be used to complete other specific tasks.

[0139] Furthermore, an embodiment of the present invention also discloses a computer-readable storage medium, in which a computer program is stored. When the computer program is loaded and executed by a processor, the steps of the component package debugging method disclosed in any of the aforementioned embodiments are implemented.

[0140] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0141] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0142] The above is a detailed introduction to a component package debugging method, device, equipment and storage medium provided by the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A component package debugging method for medical platform software, characterized in that: Applicable to storage space, including: Receiving a component package acquisition request sent by a target medical project in a target medical platform software, so as to generate a corresponding component package storage address based on the component package acquisition request; Sending the component package storage address to the target medical project, and establishing a soft link in the target medical project based on the component package storage address; Monitor the target component package corresponding to the component package acquisition request in the storage space, and when the target component package is updated, update the component package storage address contained in the soft link in the target medical project based on the updated component package, and perform component package debugging operations based on the updated storage address.

2. The component package debugging method according to claim 1, characterized in that: Before the receiving of the component package acquisition request sent by the target medical project in the target medical platform software so as to generate the corresponding component package storage address based on the component package acquisition request, the method further includes: Create a global warehouse, obtain the component package created by the developer, and store the component package in the corresponding storage folder in the global warehouse; A version control tool is used to manage all the component packages in the global repository.

3. The component package debugging method according to claim 2, characterized in that: The storing of the component package to a corresponding storage folder in the global warehouse includes: The code files, configuration files and instruction documents corresponding to each component package are stored in the corresponding and unique storage folder in the global warehouse; wherein the instruction document includes the functional usage and precautions of the component package.

4. The component package debugging method according to claim 2, characterized in that: The obtaining of the component package created by the developer includes: Creating a current component package, and naming the current component package based on a preset naming method to obtain an initial version number; Determine whether the developer modifies the current component package; If the developer has modified the current component package, determining a modified version number corresponding to the modified component package based on the modification information and the version number update rule; Accordingly, obtaining the component package created by the developer and storing the component package in a corresponding storage folder in the global warehouse includes: The modified component package created by the developer is obtained, and the modified component package is stored in the corresponding new storage folder in the global warehouse.

5. The component package debugging method according to claim 4, characterized in that: If the developer has modified the current component package, before determining the modified version number corresponding to the modified component package based on the modification information and the version number update rule, the method further includes: A component package modification command in the temporary storage area is obtained, and the current component package is modified based on the modification description information contained in the component package modification command to obtain the modified component package.

6. The component package debugging method according to any one of claims 2 to 5, characterized in that: Before monitoring the target component package corresponding to the component package acquisition request in the storage space, the method further includes: A corresponding hard link is set for each component package in the global warehouse; the hard link contains a reference address of a file storage unit corresponding to the component package; When any one of the component packages in the global warehouse changes, the reference address in the corresponding hard link is automatically modified based on the changed storage address of the changed component package in the global warehouse.

7. The component package debugging method according to claim 6, characterized in that: When the target component package is updated, updating the component package storage address contained in the soft link in the target medical project based on the updated component package includes: When the target component package is updated, obtaining an updated component package storage address corresponding to the updated component package; wherein the updated component package storage address is generated based on the latest reference address; The component package storage address in the soft link of the target medical project is replaced with the updated component package storage address, so that the updated component package is accessed based on the updated component package storage address when a component package access operation is triggered.

8. A component package debugging device, characterized in that: Applicable to storage space, including: A storage address generation module, used to receive a component package acquisition request sent by a target medical project in a target medical platform software, so as to generate a corresponding component package storage address based on the component package acquisition request; A soft link establishment module, used for sending the component package storage address to the target medical project, and establishing a soft link in the target medical project based on the component package storage address; A component package monitoring module, used for monitoring a target component package in the storage space corresponding to the component package acquisition request; The storage address updating module is used to update the storage address of the component package contained in the soft link in the target medical project based on the updated component package when the target component package is updated, and perform component package debugging operations based on the updated storage address.

9. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, configured to execute the computer program to implement the steps of the component package debugging method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: Used to store computer programs; wherein, when the computer program is executed by a processor, the component package debugging method according to any one of claims 1 to 7 is implemented.

Images