Management method applied to inspection table of medicine enterprise

Abstract

The invention relates to the technical field of check table management, and discloses a management method applied to a check table of a medicine enterprise, which comprises the following steps of: 1, designing a check table framework diagram, and designing and constructing the check table according to the designed check table framework diagram; when the check table is designed, various contents in the structure in the check table are constructed in an object mode; step 2, according to the check table constructed in the step 1, carrying out influence evaluation on the check table; 3, testing the performance of the check table; when the test result does not meet the preset requirement, the check table design content is modified and adjusted according to the test result; 4, designing a service interface and an API (Application Program Interface), and accessing the check table to a client through the designed interface; and step 5, maintaining the structure and the function of the check table constructed in the step 1, and evaluating and testing the maintained check table in the step 2 and the step 3. The method has the beneficial effect that the check table is convenient to maintain.

Description

Technical Field

[0001] The present invention relates to the technical field of checklist management, and in particular to a management method applied to checklists of pharmaceutical companies. Background Art

[0002] Checklist, also known as questionnaire, is a pre-designed form for the convenience of observing, recording, collecting and organizing data. Checklist is the simplest and most commonly used method in quality management. Checklist can systematically collect data, accumulate information, confirm facts, and roughly organize and analyze data. It can also be used as a tool for daily management and analysis and improvement. In pharmaceutical companies, there are usually many production or management projects involved. In the process of these projects, in order to ensure that the projects can be carried out efficiently and orderly, checklists are usually used to record and manage the data during the process of these projects, so as to provide effective and accurate data analysis results.

[0003] For example, the patent document with the announcement number CN111597172B discloses a multi-dimensional big data analysis and display system based on the checklist, including: a data cleaning module, which is used to clean the original data of the database and perform ETL operations on the data; a checklist module, which is used to maintain the checklist data, the checklist is a law enforcement checklist or a management checklist, and the checklist consists of multiple check items; a dimension table module, which is used to maintain the dimension table data, and the dimension table consists of multiple data dimension items; a data analysis and processing module, which performs data analysis on the data in the data cleaning module, the checklist module, and the dimension table module, extracts valid data from the data generated by the data cleaning module, and provides data support to the data display module; and updates the data in the checklist module and the dimension table module; a data display module, which is used to display the analyzed and processed data. This technical solution can perform analysis and display based on the multi-dimensional big data of the checklist, which can effectively improve the work efficiency of the supervision work.

[0004] Although the above technical scheme can improve the work efficiency of supervision work through checklists, in the actual work process, as the work content continues to progress and the project is promoted, the overall specific content of the checklist also needs to be modified as the work and project content changes to ensure that the checklist can match the actual needs. In the above technical scheme, when analyzing data through the checklist, the design content of the checklist cannot maintain the functions and parameters of the checklist according to actual needs during use, resulting in the need to rebuild the checklist when the functions and parameters of the checklist cannot meet the actual needs during the actual work process, resulting in reduced efficiency in checklist management; and in the work process, data is counted through multiple checklists, resulting in complicated related data within the work life cycle, which is not conducive to data statistics and analysis. Summary of the invention

[0005] The present invention aims to provide a management method for checklists of pharmaceutical companies to solve the technical problem that the design content of the checklist in the prior art cannot maintain the functions and parameters of the checklist according to actual needs during use, resulting in reduced efficiency of checklist management and being unfavorable for data statistics and analysis.

[0006] To achieve the above object, the present invention adopts the following technical solution: a management method applied to a pharmaceutical company checklist, comprising the following steps: Step 1: Design a checklist architecture diagram, and design and construct the checklist according to the designed checklist architecture diagram; In step 1, when designing the checklist, each item in the structure of the checklist is constructed in an object manner; Step 2: Based on the checklist constructed in step 1, conduct an impact assessment on the checklist; Step 3: Test the performance of the checklist designed in step 1; if the test results do not meet the preset requirements, modify and adjust the checklist design content according to the test results; Step 4: Design the interface of the checklist constructed in step 1, and connect the checklist to the client through the designed interface; Step 5: Maintain the structure and function of the checklist constructed in step 1, and evaluate and test the maintained checklist in steps 2 and 3.

[0007] In this solution, the checklist is designed and managed in the following steps: design, construction, evaluation, and testing. This ensures that the accuracy of the checklist design content and the rationality of the logical relationship of the designed checklist are guaranteed during the design and management of the checklist. At the same time, after the checklist is designed, the checklist is evaluated and tested to ensure that the performance and functions of the checklist can meet actual needs, thereby avoiding defects in the structure and functions of the checklist, which would increase the difficulty of subsequent use and maintenance of the checklist.

[0008] And when constructing the checklist, by constructing the checklist and its contents into one object, when maintaining and configuring the checklist, the maintenance of the checklist can be completed by configuring and modifying each object, thereby improving the convenience of checklist maintenance.

[0009] After the checklist is built, the checklist is connected to the user front end by designing a checklist interface, so that the front and back ends of the checklist can be separated during use, which facilitates the checklist to be able to run remotely on multiple platforms. When the functions of the checklist are maintained, the checklist can be configured and maintained from the back end of the checklist, so that the checklist can maintain various parameters when it is started, thereby improving the convenience of checklist maintenance.

[0010] Preferably, as an improvement, in step 1, when designing the checklist, the table structure of the checklist is first designed; and the entity relationship diagram of the checklist and the field table in the table structure are designed. This allows the checklist to clearly display the relationship between the structures when designing and building, making it easier to sort out the relationship between multiple structures in the checklist when designing; and the fields in the checklist are described through the field table, making it easier to check the structures and fields of the checklist after design, thereby improving the convenience of designing and building the checklist.

[0011] Preferably, as an improvement, in step one, when designing and constructing the checklist, the functions of the checklist are classified according to the design content of the checklist.

[0012] Preferably, as an improvement, in step 5, when the checklist is maintained, the checklist is also classified and maintained according to the classified contents of the checklist in step 1. By classifying and dividing the multiple contents in the checklist, when the checklist is maintained, the contents that need to be maintained and debugged can be quickly located through the classification information, and similar or related functions can be quickly maintained and debugged during the maintenance process, thereby improving the efficiency of the maintenance operation. In addition, by classifying and maintaining the functions of the checklist, the total similar or related functions of the checklist can be maintained and modified at the same time, ensuring the integrity of the checklist content coverage during maintenance, avoiding omissions in the checklist during maintenance, and affecting the normal use of related functions in the checklist.

[0013] Preferably, as an improvement, in step 1, when designing and constructing the checklist, the environment variables of the checklist are also designed; the environment variables are used to save the environment configuration information of the checklist. When the checklist is maintained later, the operation and maintenance personnel can correctly obtain the configuration of the checklist according to the environment variable information; the accuracy of the checklist configuration is ensured when the checklist is maintained, and errors in obtaining the configuration content of the checklist during operation and maintenance are avoided, resulting in damage to the checklist after maintenance.

[0014] Preferably, as an improvement, in step 2, when there is an impact on the function in the affected evaluation result, a reference solution is given to the affected function according to the evaluation content, so that the restricted functions in the checklist can be modified quickly, ensuring that the functions in the checklist can operate normally.

[0015] Preferably, as an improvement, in step three, the resource utilization test, stability, capacity planning and scalability of the checklist are also tested. When the test results do not meet the preset requirements, the design content of the checklist is modified and adjusted according to the test results. By testing the resource utilization and stability of the checklist, it is ensured that the constructed checklist can run normally for a long time, and it is avoided that insufficient resources or poor stability during the operation of the checklist cause the checklist to run stuck or crash, affecting the normal use of the checklist. And it is ensured that after the checklist is used for a long time, the design content of the checklist can meet the growth of actual needs, avoid the checklist after use. After the need for maintenance such as expansion, etc., reduce the maintenance workload of the checklist. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 This is a flowchart of a single-object migration configuration method for pharmaceutical company data in an embodiment of the present invention. DETAILED DESCRIPTION

[0017] The following is further described in detail through specific implementation methods: As attached Figure 1 As shown, a management method applied to a pharmaceutical company checklist includes the following steps: Step 1: Design the checklist architecture diagram, and design and construct the checklist based on the designed checklist architecture diagram; specifically, when designing the checklist framework diagram, divide the chapters of the content and data that need to be counted and investigated in the checklist according to the actual needs of the checklist, and set a number of survey questions in each chapter. The checklist architecture diagram can arrange the hierarchical relationships such as checklists, chapters, questions, and answers according to the tree structure. In the process of designing the checklist, the overall architecture of the checklist can be clearly displayed, which is convenient for a clear understanding of the checklist architecture when designing and constructing the checklist later, and improves the convenience of designing and constructing the checklist.

[0018] In step 1, when designing the checklist, the table structure of the checklist is first designed; and according to the checklist architecture diagram and the functional requirements of the checklist, the entity relationship diagram of the checklist and the field table in the table structure are designed, wherein the entity relationship diagram is used to display the output relationship diagram between the structures in the checklist, and the field table is used to display and explain the configuration parameters such as the name and type of each field in the checklist. When designing and building the checklist, the relationship between the structures can be clearly displayed, which is convenient for sorting out the relationship between multiple structures in the checklist during design; and each field in the checklist is explained through the field table, which is convenient for checking the structures and fields of the checklist after design, thereby improving the convenience of designing and building the checklist.

[0019] After the table structure design of the checklist is completed, the display page of the checklist is designed according to the designed checklist structure. When designing the display page of the checklist, each field in the checklist is added and the added fields are sorted. The specific content of designing the display page of the checklist is prior art and will not be repeated here.

[0020] In step 1, when designing the checklist, each structure in the checklist is constructed in an object manner. Specifically, in this embodiment, when constructing the checklist in step 1, each checklist is constructed as an object, and each chapter in each checklist, a number of questions in each chapter, and the answers corresponding to each question and other hierarchical contents are constructed as a number of objects. The hierarchical structures and contents in each structure in the constructed checklist are carried out as a single object, which improves the mutual independence between the contents in the checklist, facilitates the individual modification and debugging of each content during maintenance, and improves the convenience of checklist maintenance.

[0021] In step 1, when designing and constructing the checklist, the functions of the checklist are classified according to the design content of the checklist, and similar or related functions in the checklist are added to the same category. By categorizing the multiple contents in the checklist, when maintaining the checklist, the content that needs maintenance and debugging can be quickly located through the classification information, and similar or related functions can be quickly maintained and debugged during the maintenance process, thereby improving the efficiency of maintenance operations.

[0022] In step one, when designing and constructing the checklist, the environment variables of the checklist are also designed according to the actual needs of the checklist. Specifically, the environment configuration information required for the checklist operation is saved in the checklist through environment variables. When the checklist is maintained at a later stage, the operation and maintenance personnel can correctly obtain the configuration of the checklist based on the environment variable information; ensure the accuracy of the checklist configuration when the checklist is maintained, and avoid errors in obtaining the configuration content of the checklist during operation and maintenance, which may cause damage to the checklist after maintenance.

[0023] Step 2: According to the checklist constructed in step 1, conduct an impact assessment on the checklist; specifically, after the checklist is constructed, the impact of the checklist on related operations of the checklist in the actual work process is evaluated according to the specific functional information of the constructed checklist. Specifically, according to the specific design content of the checklist, the impact of operations such as configuration migration, multi-language translation, and updating test cases of the checklist is evaluated. The specific method of conducting an impact assessment on the checklist can be verified by testing and other methods. The specific content is the existing technology and will not be repeated here. By evaluating the functions of the checklist, it is possible to avoid some functions in the checklist being restricted, which will affect the subsequent use of the checklist.

[0024] In step 2, when some functions are affected in the affected assessment results, reference solutions are given to the affected functions based on the assessment content; for example, when the checklist design and construction is completed, when some functions in the checklist will affect the configuration migration function of the checklist, solutions to the affected configuration migration function of the checklist are given based on the specific content of the assessment (such as adding a migration table, etc.), and relevant staff adjust the functions of the checklist based on the assessment results to ensure the integrity of the various functions of the checklist. This allows the restricted functions in the checklist to be quickly modified to ensure that the various functions in the checklist can operate normally.

[0025] Step 3: Test the performance of the checklist designed in step 1; when testing the checklist, perform a load test on the performance of the checklist according to the design performance requirements of the checklist; the performance requirements of the checklist include response time, throughput and concurrency, where the response time indicates the checklist's ability to respond quickly to requests (i.e., the time it takes for the checklist to return results when the user clicks the corresponding function button); throughput indicates the number of requests that the checklist can process simultaneously per unit time (seconds); concurrency indicates the number of concurrent requests that the checklist can process simultaneously (i.e., the number of users that the checklist supports to be online at the same time); when load testing the checklist, test the response performance of the checklist under different load conditions according to the performance requirements of the checklist. By testing the performance of the checklist after the design and construction is completed, it is ensured that the various performance parameters of the checklist can meet the preset requirements, and it is avoided that some performance defects of the constructed checklist exist, which affects the normal use of the checklist and increases the difficulty of later maintenance of the checklist.

[0026] In step three, the resource utilization and stability tests of the checklist are also performed, wherein the resource utilization test is used to test the resource consumption of the checklist during operation, wherein the resource utilization test includes the occupancy of resources such as CPU, memory, and bandwidth, to ensure that the resource occupancy of the checklist during operation is within a preset range. The stability test is used to test the stability of the checklist under long-term and high-load operation to ensure that the checklist does not need to be restarted or crashed during operation. By testing the resource utilization and stability of the checklist, it is ensured that the constructed checklist can run normally for a long time, avoiding insufficient resources or poor stability during the operation of the checklist, which may cause the checklist to run stuck or crash, affecting the normal use of the checklist.

[0027] In step three, the capacity planning and scalability of the checklist are also tested. Capacity planning means that in the case of future demand growth, the planned hardware resources and system configuration can meet the annual growth of users and data volume of the checklist to ensure that the checklist can meet the actual capacity requirements. Scalability means that the checklist can be effectively expanded when the load increases. For example, the system can respond to the increase in users by adding server nodes according to the actual operation situation to ensure the smooth operation of the checklist under high load. After the checklist is used for a long time, the design content of the checklist can meet the growth of actual demand, avoiding the need for maintenance such as re-expansion of the checklist after use, and reducing the maintenance workload of the checklist.

[0028] In step three, when the test results do not meet the preset requirements, the checklist design content is modified and adjusted according to the test results to ensure the stability of the checklist during actual use. This allows defects in the checklist to be repaired in a timely manner, ensuring the completeness of the delivered checklist functions and the stability of the architecture.

[0029] Step 4. According to the function and structure of the checklist designed in step 1, design the service interface and API interface of the checklist, and connect the checklist to the client through the designed service interface and API interface to collect data; connect the checklist to the user front end by designing the checklist service interface and API interface, so that the front and back ends of the checklist can be separated during use, which makes it easier for the checklist to run remotely on multiple platforms. When maintaining the functions of the checklist, the checklist can be configured and maintained from the back end of the checklist, so that the checklist can maintain various parameters when it is started, thereby improving the convenience of checklist maintenance.

[0030] Step 5: Maintain the structure and function of the checklist constructed in step 1, and evaluate and test the maintained checklist in steps 2 and 3. In step 5, when maintaining the checklist, modify the function or configuration of the checklist according to business and project requirements. When maintaining the checklist, maintain the function of the checklist by modifying and configuring each object in the checklist constructed in step 1. After the checklist is maintained, the modified checklist is evaluated and tested again to ensure that the modified content in the checklist meets the design requirements of the checklist, avoiding functional restrictions or performance degradation in the checklist during maintenance, which affects the normal operation and use of the checklist.

[0031] In step 5, when the checklist is maintained, the checklist is also classified and maintained according to the classified contents of the checklist in step 1. By classifying and maintaining the functions of the checklist, the overall similar or related functions of the checklist can be maintained and modified at the same time, ensuring the integrity of the checklist content during maintenance, avoiding omissions in the checklist during maintenance, and affecting the normal use of related functions in the checklist.

[0032] Compared with the prior art, the present invention sequentially designs and manages the checklist through the steps of design, construction, evaluation, and testing, so that when the checklist is designed and managed, the accuracy of the design content of the checklist can be guaranteed, and the rationality of the logical relationship of the designed checklist can be guaranteed; at the same time, after the checklist is designed, the checklist is evaluated and tested to ensure that the performance and function of the checklist can meet the actual needs, and to avoid defects in the structure and function of the checklist, which increases the difficulty of subsequent use and maintenance of the checklist; at the same time, when the checklist is constructed, the checklist and the contents in the checklist are constructed into an object, so that When the checklist is maintained and configured, the maintenance of the checklist can be completed by configuring and modifying each object, thereby improving the convenience of checklist maintenance; and after the checklist is constructed, the checklist is connected to the user front end by designing a checklist service interface and an API interface, so that the checklist can be separated from the front and back ends during use, so that the checklist can be run remotely on multiple platforms, and when the functions of the checklist are maintained, the checklist can be configured and maintained from the back end of the checklist, so that the checklist can maintain various parameters when it is started, thereby improving the convenience of checklist maintenance.

[0033] It should be pointed out that for those skilled in the art, several modifications and improvements can be made without departing from the technical solution of the present invention, which should also be regarded as the protection scope of the present invention, and these will not affect the effect of the implementation of the present invention and the practicality of the patent. The protection scope required by this application shall be based on the content of its claims, and the specific implementation methods and other records in the specification can be used to interpret the content of the claims.

Claims

1. A management method for a pharmaceutical company checklist, characterized in that: The following steps are involved: Step 1: Design a checklist architecture diagram, and design and construct the checklist according to the designed checklist architecture diagram; In step 1, when designing the checklist, each item in the structure of the checklist is constructed in an object manner; Step 2: Based on the checklist constructed in step 1, conduct an impact assessment on the checklist; Step 3: Test the performance of the checklist designed in step 1; if the test results do not meet the preset requirements, modify and adjust the checklist design content according to the test results; Step 4: Design the interface of the checklist constructed in step 1, and connect the checklist to the client through the designed interface; Step 5: Maintain the structure and function of the checklist constructed in step 1, and evaluate and test the maintained checklist in steps 2 and 3.

2. A management method for pharmaceutical company checklists according to claim 1, characterized in that: In step one, when designing the check table, firstly design the table structure of the check table; and then design the entity relationship diagram of the check table and the field table in the table structure.

3. A management method for pharmaceutical company checklists according to claim 1, characterized in that: In step one, when designing and constructing the checklist, the functions of the checklist are classified according to the design content of the checklist.

4. A management method for pharmaceutical company checklists according to claim 3, characterized in that: In step five, when the checklist is maintained, the checklist is also classified and maintained according to the classification content of the checklist in step one.

5. The management method for pharmaceutical company checklist according to claim 1, characterized in that: In step one, when designing and constructing the checklist, the environment variables of the checklist are also designed; the environment variables are used to store the environment configuration information of the checklist.

6. A management method for pharmaceutical company checklists according to claim 1, characterized in that: In step 2, when there is an impact on the function in the affected assessment results, a reference solution is given to the affected function based on the assessment content.

7. The management method for pharmaceutical company checklist according to claim 1, characterized in that: In step three, the resource utilization test, stability, capacity planning and scalability of the checklist are also tested. When the test results do not meet the preset requirements, the checklist design content is modified and adjusted according to the test results.

Images