A form-based drug information approval management method, system and storage medium

Abstract

The application discloses a form-based drug information examination and approval management method and system and a storage medium. After obtaining the chemical formula information of a drug without record, a first business examination and approval flow is generated, and other business examination and approval flows without examination and approval initiated from the same starting point are obtained. Whether to be combined and updated into a new business examination and approval flow is confirmed according to the correlation of the examination and approval path data of the first business examination and approval flow and the other business examination and approval flows, so that the number of single to-be-approved flow sheets is greatly reduced, the processing pressure of each examination and approval node is effectively reduced, and the examination and approval time is saved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of information technology, in particular to a form-based drug information approval management method and system and a storage medium. BACKGROUND

[0002] In the process of medical research and development, experimenters use templates to record basic test reports, and in this process, the templates used and the test reports recorded often need to be approved, including the calculation formulas and chemical formulas involved in the reports, which also need to be approved before use. In the traditional approval process, the process and the business are highly coupled, and the separation of business and process is not achieved, and once the approval process changes, the modification workload is large. In addition, in the existing process management, the approval process and the transaction are becoming more and more complicated, and in a relatively short period of time, each approval node will receive a large number of approval process transactions initiated by the same starting point or different starting points, and the opening and processing of each approval sheet will occupy a large amount of working time. SUMMARY

[0003] The present application provides a form-based drug information approval management method to overcome the shortcomings of the prior art, which comprises the following steps:

[0004] S1, obtaining unrecorded drug chemical formula information, generating an approval form according to the drug chemical formula information, the approval form including a first cell group for associating the drug chemical formula information and a second cell group for entering editable information, screening an approval process template according to fixed approval information in the first cell group, the approval process template including starting point data and approval path data;

[0005] S2, analyzing the approval path data in the approval process template, the approval path data including judgment data attributes, switching condition groups and / or intermediate nodes, the switching condition groups including a plurality of preset screening indicators and their respective corresponding different intermediate nodes;

[0006] S3, obtaining the corresponding intermediate node as the transfer point data after comparing the entered approval information in the second cell group with the preset screening indicators, updating the starting point data in the approval process template according to the fixed approval information, and adding the transfer point data to the approval process template to generate a first business approval flow;

[0007] S4, obtaining other unapproved business approval flows initiated by the same starting point, and confirming whether to merge and update as a new business approval flow according to the relevance of the approval path data of the first business approval flow and the other business approval flows.

[0008] Preferably, the second cell group includes but is not limited to a name cell, a CAS number cell, and a structural formula cell.

[0009] Preferably, the step S3 comprises:

[0010] According to the judgment data attribute in the first cell group and the second cell group of the approval form to retrieve the corresponding attribute cells, compare the entered approval information in the cell with a plurality of preset screening indicators to obtain the corresponding preset screening indicators, and take the intermediate node associated with the preset screening indicators as the transfer point data.

[0011] Preferably, the step S4 specifically comprises:

[0012] Obtain a second business approval flow that has the same starting point and has not received intermediate node feedback signals, wherein the intermediate node feedback signals are information fed back by the intermediate node to the starting point after modifying or updating the business approval flow data.

[0013] Determine whether the first business approval flow and the second business approval flow are the same approval process template.

[0014] If they are the same approval process template, compare the approval account levels corresponding to the intermediate nodes at each level in turn, add the higher-level approval account at each level and the starting point data to the approval process template, merge the entered approval information in the first and second business approval flows and add them to the approval process template to generate a third business approval flow for replacing the second business approval flow.

[0015] Preferably, the step S4 can further specifically comprise:

[0016] Obtain a second business approval flow that has the same starting point and has not received all intermediate node feedback signals, wherein the intermediate node feedback signals are information fed back by the intermediate node to the starting point after modifying or updating the business approval flow data.

[0017] When the first business approval flow and the second business approval flow are the same approval process template, obtain the remaining intermediate nodes in the second business approval flow that have not been fed back, and compare the approval account levels of the corresponding intermediate nodes at the same level in the first business approval flow.

[0018] Replace the approval account corresponding to the remaining intermediate nodes in the original second business approval flow with the higher-level approval account, and send the updated second business approval flow to the remaining intermediate nodes.

[0019] The application further discloses a form-based drug information approval management system, which specifically comprises a process template acquisition module, which is used for acquiring unrecorded drug chemical formula information, generating an approval form according to the drug chemical formula information, and including a first cell group for associating the drug chemical formula information and a second cell group for inputting editable information in the approval form; filtering an approval process template according to fixed approval information in the first cell group, wherein the approval process template comprises start point data and approval path data; an analysis module, which is used for analyzing the approval path data in the approval process template, wherein the approval path data comprises judgment data attributes, switching condition groups and / or intermediate nodes, and the switching condition groups comprise a plurality of preset filtering indexes and respective corresponding different intermediate nodes; a transfer point acquisition module, which is used for acquiring corresponding intermediate nodes as transfer point data after comparing the input approval information in the second cell group with the preset filtering indexes, updating the start point data in the approval process template according to the fixed approval information, and adding the transfer point data to the approval process template to generate a first business approval flow; and a process merging module, which is used for acquiring other unapproved business approval flows initiated by the same start point, and confirming whether to merge and update as a new business approval flow according to the relevance of the approval path data of the first business approval flow and the other business approval flows.

[0020] Preferably, the second cell group comprises but is not limited to a name cell, a CAS number cell and a structural formula cell.

[0021] Preferably, the transfer point acquisition module is further configured to retrieve corresponding attribute cells in the first cell group and the second cell group of the approval form according to the judgment data attributes, compare the input approval information in the cells with a plurality of preset filtering indexes to acquire corresponding preset filtering indexes, and acquire intermediate nodes associated with the preset filtering indexes as transfer point data.

[0022] The application further discloses a form-based drug information approval management device, which comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, and the processor implements the steps of the above method when executing the computer program.

[0023] The application further discloses a computer readable storage medium, which stores a computer program, and the computer program implements the steps of the above method when executed by a processor.

[0024] The form-based drug information approval management method and system discloses the application, through in the new generation business approval flow to query whether there is no approval other business approval flow, if there is, according to the approval path data relevance of business approval flow to carry out reasonable merging, thereby greatly reducing the number of separate to-be-approved process, effectively reduce the processing pressure of each approval node, save the approval time.

[0025] Additional aspects and advantages of the application will be described in the description that follows, and in part will become apparent from the description, or will be learned by practice of the application. BRIEF DESCRIPTION OF DRAWINGS

[0026] The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application. In the drawings:

[0027] Figure 1 The flowchart of the form-based drug information approval management method disclosed for an embodiment.

[0028] Figure 2 The specific flowchart of step S3 disclosed for an embodiment.

[0029] Figure 3 The specific flowchart of step S32 disclosed for an embodiment.

[0030] Figure 4 The specific flowchart of step S4 disclosed for an embodiment.

[0031] Figure 5 Another specific flowchart of step S4 disclosed for an embodiment.

[0032] Figure 6 Another specific flowchart of step S4 disclosed for an embodiment. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solutions and advantages of the embodiments of the application clearer, the technical solutions of the embodiments of the application will be described clearly and completely below with reference to the drawings of the embodiments of the application. Obviously, the described embodiments are part of the embodiments of the application, rather than all the embodiments of the application. Based on the described embodiments of the application, all other embodiments obtained by those skilled in the art without creative labor fall within the protection scope of the application.

[0034] In the description of the present application, it needs to be understood that the terms "center", "longitudinal", "transverse", "length", "width", "thickness", "upper", "lower", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise" and the like indicate the orientation or positional relationship shown in the drawings, which are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the devices or elements referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore cannot be understood as limiting the present application.

[0035] In addition, the terms "first", "second" are only for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the technical features indicated. Therefore, the features defined with "first", "second" can explicitly or implicitly include one or more of the features. In the description of the present application, the meaning of "multiple" is two or more, unless otherwise specifically limited.

[0036] In the present application, unless otherwise specifically defined and limited, the terms "mounting", "connecting", "connecting", "fixing" and the like should be understood broadly, for example, it can be fixedly connected, or it can be detachably connected, or integrally connected; it can be mechanically connected, or it can be electrically connected; it can be directly connected, or it can be indirectly connected through an intermediate medium, or it can be the communication between two elements. For those skilled in the art, the specific meaning of the above terms in the present application can be understood according to the specific circumstances.

[0037] In the present application, unless otherwise specifically defined and limited, the first feature "above" or "below" the second feature can include the first and second features in direct contact, or the first and second features not in direct contact but in contact through another feature between them. Moreover, the first feature "above", "above" and "above" the second feature includes the first feature directly above and obliquely above the second feature, or only indicates that the horizontal height of the first feature is higher than that of the second feature. The first feature "below", "below" and "below" the second feature includes the first feature directly below and obliquely below the second feature, or only indicates that the horizontal height of the first feature is less than that of the second feature.

[0038] Unless otherwise defined, the technical terms or scientific terms used herein should be understood as the usual meaning understood by those skilled in the art to which the present application belongs. The use of "first", "second" and similar words in the patent application description and claims of the present application does not indicate any order, quantity or importance, but is only used to distinguish different components. Similarly, "one" or "a" and similar words do not indicate a quantity limit, but indicate the existence of at least one.

[0039] In the process of pharmaceutical research and development, experimenters record basic test reports using templates, and both the templates and the recorded test reports need to be approved, including the calculation formulas and drug chemical formulas involved in the reports, which also need to be approved before use. In the traditional approval process, the process is highly coupled with the business, and the separation of business and process is not achieved, and the modification workload caused by changes in the approval process is large. The business approval process involved in the drug information approval management method based on forms disclosed in the embodiment adopts the method of process customization and form customization, and the separation of process and business, which well solves the problem that the user may need to change the process. The process and the approval form defined by the user can better meet the actual business process requirements and have better scalability and maintainability. Most of the existing workflows on the market are fixed processes and form information, or the process cannot be associated with the actual business. Therefore, the scalability is not high, the modification and maintenance are difficult, and the actual business cannot be contacted, so the usability is not high. To solve the above problems, the embodiment discloses a drug information approval management method based on forms, as shown in the accompanying Figure 1 The drug information approval management method based on forms specifically includes the following contents.

[0040] Step S1, obtaining unrecorded drug chemical formula information, generating an approval form according to the drug chemical formula information, the approval form including a first cell group for associating the drug chemical formula information and a second cell group for entering editable information, screening an approval process template according to fixed approval information in the first cell group, and the approval process template including start point data and approval path data.

[0041] The approval form is pre-bound to different approval forms for different types of drug chemical formulas, and the approval form can include multiple cells with information. The cells can be divided into a first cell group and a second cell group according to the information source. The information in the first cell group can be directly obtained from the drug chemical formula to be approved and input into the first cell group after automatic identification. The first cell group data includes approval initiation account identity information, drug chemical formula type, chemical formula version, creation time, etc. The second cell group can include editable information input by the approval initiator. In the embodiment, the second cell group includes but is not limited to a name cell, a CAS number cell, and a structural formula cell.

[0042] In some embodiments, various report templates, test reports, calculation formulas and chemical formulas that need to be approved before use can be bound to different approval forms, so that when using such materials, the approval instruction can be initiated directly by clicking the approval option, and the corresponding approval form of the material needing approval can be obtained. In specific embodiments, the customizable approval form can be generated by adding form elements to generate a form through drag-and-drop operation in a graphical interface according to the actual business process requirements. Each business process is paired with an initial form, and users can design and customize the required form elements according to business requirements. The form definition table is created by MariaDB to store form name, version, creation time, etc. The form field table is created to store element information and element position of the form.

[0043] Step S2, analyzing the approval path data in the approval process template, the approval path data including judgment data attributes, switching condition groups and / or intermediate nodes, the switching condition group including a plurality of preset screening indicators and respective corresponding different intermediate nodes.

[0044] Specifically, each node of the process represents a link in the actual business process twist. When designing the process, the approval handler of the node can be set by clicking the user node. The handler can select a system role, a project role, specify a specific person, or freely select, such as selecting from all personnel in the system. The twist conditions between nodes are set by clicking the connection between nodes. The condition setting of the process connection comes from the preset field selection in the second cell group in the approval form. The twist conditions that can be set include equal to, not equal to, contain, etc. For example, the setting element in the approval form is the judgment data attribute "quantity", and the preset screening indicators in the switching condition group can be "greater than 10", "less than or equal to 10", etc. Among them, the intermediate node approval account corresponding to "greater than 10" is A, and the intermediate node approval account corresponding to "less than or equal to 10" is B.

[0045] Step S3, comparing the entered approval information in the second cell group with the preset screening indicators to obtain the corresponding intermediate node as the transfer point data, updating the start point data in the approval process template according to the fixed approval information, and adding the transfer point data to the approval process template to generate the first business approval flow.

[0046] In this embodiment, step S3 further includes retrieving the corresponding attribute cells in the first cell group and the second cell group of the approval form according to the judgment data attribute, comparing the entered approval information in the cell with the plurality of preset screening indicators to obtain the corresponding preset screening indicators, and taking the intermediate node associated with the preset screening indicators as the transfer point data.

[0047] Specifically, as shown in FIG. 6, the approval form includes a judgment data attribute "quantity", a switching condition group "greater than 10" and a switching condition group "less than or equal to 10". The intermediate node corresponding to the switching condition group "greater than 10" is A, and the intermediate node corresponding to the switching condition group "less than or equal to 10" is B. Figure 2As shown, the step S3 can further include:

[0048] In step S31, the corresponding first judging data is retrieved according to the judging data attribute in the record, and it is judged whether there is a preset screening index that matches the first judging data in the switching condition group.

[0049] In step S32, if there is, the first intermediate node corresponding to the preset screening index that matches the first judging data is taken as the transfer point data, otherwise, the approval instruction identity information is obtained, and the starting account level of the approval initiation is obtained according to the approval instruction identity information.

[0050] In this embodiment, as shown in the accompanying drawings Figure 3 As shown, the step S32 can specifically include:

[0051] In step S321, if there is a first preset screening index that matches the first judging data, the first account level in the first intermediate node corresponding to the first screening index is obtained.

[0052] In step S322, the approval instruction identity information is obtained, and the starting account level of the approval initiation is obtained according to the approval instruction identity information.

[0053] In step S323, if the first account level is higher than the starting account level, the first intermediate node is taken as the transfer point data, otherwise, the account levels of the intermediate nodes corresponding to all preset screening indexes are traversed, and an intermediate node with a corresponding preset screening index higher than the first preset screening index and higher than the starting account level is taken as the transfer point data.

[0054] The step S323 further includes:

[0055] In step S3231, if the first account level is higher than the starting account level, the first intermediate node is taken as the transfer point data, otherwise, the account levels of the intermediate nodes corresponding to all preset screening indexes are traversed.

[0056] In step S3232, a plurality of candidate intermediate nodes with a corresponding preset screening index higher than the first preset screening index and higher than the starting account level are obtained.

[0057] In step S3233, the intermediate node with the lowest corresponding preset screening index in the plurality of candidate intermediate nodes is taken as the transfer point data.

[0058] That is, when the approval initiation instruction account level is higher than the account level of the intermediate node corresponding to the preset screening index given after judgment, it will cause the starting account level to be higher than the approval account level, which is an error. At this time, the account levels of all intermediate nodes corresponding to the preset screening index in the switching condition group in the approval form are obtained, and the intermediate node closest to the starting account level but higher than the starting account level is obtained as the transfer point data in order from low to high. Thus, in the case where the starting account level is higher than the approval account level, the closest intermediate node to the starting account level is arranged as the transfer point data from the switching condition group.

[0059] Step S33, if the starting account level is greater than the approval account level in at least one intermediate node, the second intermediate node with the highest of the plurality of preset screening indexes is taken as the transfer point data, and the preset screening index corresponding to the second intermediate node in the approval path data is updated according to the first judgment data.

[0060] When there is no preset screening index that meets the first judgment data, in principle, the approval process is wrong, which does not meet the preset approval conditions of the approval form, and the system cannot generate corresponding transfer point data, which will report an error or remind that the approval form input data is incorrect. If you still want to approve, you need to re-initialize the condition settings of the approval form. However, when the approval initiation account level is high enough, the second intermediate node specified as the transfer point data corresponding to the first judgment data is selected again, and the first judgment data is taken as the new preset screening index content to update the preset screening index corresponding to the second intermediate node in the approval path data. Thus, the switching condition group in the approval form is quickly updated, avoiding re-initializing the condition settings of the approval form.

[0061] The above steps can adjust the intermediate nodes according to the data in the experiment record when generating the business approval flow data, solving the problem that most of the existing workflows are fixed in the early stage and the form information, which cannot adjust the intermediate approval path and each approval node of the business approval process data in real time according to the actual business situation, resulting in low adaptability of such approval process method to complex business.

[0062] In another embodiment, the above step S3 further specifically includes: verifying the data approval flow relationship of each level of intermediate node, and adding to the approval process template to generate the first business approval flow if the verification is passed, otherwise adjusting the problem node that fails the verification and then adding to the approval process template to generate the business approval flow. Specifically, the approval accounts of each intermediate node can be adjusted according to the level relationship between the approval accounts of each level of intermediate node and the approval instruction initiation account, and the adjusted each intermediate node is added to the approval process template to generate the first business approval flow.

[0063] Specifically, in the management software, the business approval flowchart is checked by the background when publishing whether the flowchart conforms to the actual business meaning, for example, the flowchart only allows one start node, the flow must have an end node, and only one connection line can be stored between nodes. By parsing the XML of the flowchart, it is judged whether the flow meets the requirements, for example, a usable flow has a single start node, multiple connection lines, user nodes and end nodes. If the flowchart does not meet the requirements, the user will be informed that the flow does not meet the requirements. The flow is designed to identify errors when designing complex workflows and automatically calibrate. Error identification, such as selecting a flow connection line when drawing a flowchart, the start and end points of the connection line cannot be the same connection line, and the gateway must have a conditional exit. This correction step can automatically prompt you to the next possible process element that meets the flow design requirements when you draw a connection line, and provides a quick selection button to allow the user to quickly and easily design an accurate flowchart.

[0064] In some embodiments, the step can specifically include the following contents:

[0065] Step S101, obtaining the starting point account of sending the approval instruction, comparing the level of the starting point account with the approval account level corresponding to the first level intermediate node.

[0066] Step S102, if the starting point account level is lower than the approval account level of the first level intermediate node, the first level intermediate node is not changed, otherwise, the switching condition group to which the first level intermediate node belongs and the corresponding first preset screening index are obtained, the account level of each intermediate node corresponding to the preset screening index in the switching condition group is traversed, and an intermediate node higher than the starting point account level and corresponding to the preset screening index higher than the first preset screening index is obtained to replace the first level intermediate node.

[0067] The above embodiments can be used to check the level of the starting point account in the flowchart and the first level intermediate node account connected with the starting point, avoiding the problem that the starting point account level initiating the approval flow is higher than the intermediate node account approving it, thereby preventing the flow confusion problem of assigning low-level accounts to approve the process initiated by high-level accounts, and realizing automatic verification and adjustment of the account level of the nodes before and after the approval flow in the flow design stage.

[0068] Step S201, obtaining the approval account level corresponding to each level intermediate node, and sequentially judging whether the account level of each level intermediate node is lower than or equal to the account level of the intermediate node of the previous level.

[0069] Step S202, if the intermediate node account level is lower than or equal to the previous level, the switching condition group to which the intermediate node belongs and the corresponding first preset screening index are obtained, each preset screening index corresponding to the intermediate node account level in the switching condition group is traversed, and an intermediate node with an account level higher than the previous level and a preset screening index higher than the first preset screening index is obtained to replace the intermediate node at this level.

[0070] The above embodiments can be used to check the level of each level of intermediate node account in the flowchart, avoid the problem that the node approval account level before the approval flow is higher than the node approval account level after the approval flow, thereby preventing the problem that the node before the approval flow has been approved by a higher level account and then flows to a lower level account for re-approval, resulting in a chaotic approval node setting of the entire approval flow and failing to achieve step-by-step approval. The above steps achieve automatic checking and adjustment of the node account level before and after the approval flow in the process design stage.

[0071] Step S301, obtaining an approval instruction sending timestamp, calculating a deadline according to the approval time limit in the fixed approval information and the sending timestamp.

[0072] Step S302, determining whether the deadline is in a first period, if so, taking the deadline as the form closing time of the first business approval flow, if not, multiplying the deadline by a preset proportion to obtain the form closing time of the first business approval flow, and if in other periods, adding the interval of the period to obtain the form closing time of the first business approval flow.

[0073] In the fixed approval information of the first cell group of the approval form, there is a corresponding approval time limit generated according to the type and attribute of the drug chemical formula, and the latest deadline in the business approval flow, i.e., the form closing time, is included in the approval processing of the drug chemical formula by the intermediate nodes at each level of approval. However, in real approval work, the approval processing time is often affected by the work period, such as the daytime work period, the possible overtime period at night, and the off-work period, etc. Therefore, the form closing time is not directly corresponding to the above-mentioned deadline, but needs to be adjusted according to the period in which the final deadline is located, so as to meet the actual work scenario. For example, the first period can be from 8 am to 5 pm, and the second period can be from 8 pm to 12 am. When the deadline is in the second period, the time in the second period can be multiplied by a weight value, for example, multiplied by 2, i.e., the deadline is appropriately extended, and finally integrated into the final form closing time. Thus, the problem that the form processing period set in the existing approval form cannot be flexibly adjusted according to the specific work period is solved, and the adaptability of the approval method to various work scenarios is provided.

[0074] Step S4, obtaining other unapproved business approval flows initiated by the same starting point, and determining whether to merge and update into a new business approval flow according to the relevance of the approval path data of the first business approval flow and the other business approval flows.

[0075] In the existing process management, the approval process and transaction are more and more complicated, and in a short period of time, each approval node often receives a large number of approval process transactions to be approved initiated by the same starting point or different starting points. The opening and processing of each approval sheet occupies a large amount of working time. In the embodiment, by querying whether there is other unapproved business approval flow when a new business approval flow is generated, if there is, the business approval flow is reasonably merged according to the relevance of the approval path data, thereby greatly reducing the number of separate to-be-approved process sheets, effectively reducing the processing pressure of each approval node, and saving the approval time.

[0076] In the embodiment, as shown in the accompanying drawings, Figure 4 The step S4 specifically includes:

[0077] Step S401, obtaining a second business approval flow existing the same starting point and not receiving an intermediate node feedback signal, the intermediate node feedback signal being information fed back to the starting point after the intermediate node modifies or updates the business approval flow data. Each account as an intermediate node will feed back a signal to the starting point account and the server to show that the business approval has been processed when performing various processing actions such as auditing, reviewing or rejecting the data.

[0078] Step S402, determining whether the first business approval flow and the second business approval flow are the same approval process template. Specifically, obtaining the approval process template id adopted by the first business approval flow and the approval process template id adopted by the second business approval flow, and determining whether the first business approval flow and the second business approval flow are the same approval process template according to whether the two approval process template ids are the same.

[0079] Step S403, if they are the same approval process template, then the approval accounts corresponding to the levels of the intermediate nodes are compared in turn, and the higher level approval accounts and the starting point data are added to the approval process template, the entered approval information in the first and second business approval flows is merged and added to the approval process template to generate a third business approval flow for replacing the second business approval flow.

[0080] In the embodiment, if the first business approval flow and the second business approval flow are based on different approval process templates, the approval flows are not merged. If the first business approval flow and the second business approval flow are based on the same approval process template, the approval account levels of the same level intermediate nodes are compared, and the intermediate node with the higher level is taken as the intermediate node of the same level of the merged business approval flow. Then, the modified data can be used to generate a third business approval flow incremental update package, which is sent to each node to perform incremental update on the second business approval flow data received by the original intermediate node, so as to change the second business approval flow data into new approval data, or the second business approval flow data on the server is directly updated to change into the third business approval flow data.

[0081] In another embodiment, as shown in FIG. 4, the step S4 can specifically include: Figure 5

[0082] In step S501, a second business approval flow with the same starting point and without receiving feedback signals of all intermediate nodes is obtained. The feedback signal of the intermediate node is information fed back by the intermediate node to the starting point after the intermediate node modifies or updates the business approval flow data.

[0083] In step S502, when the first business approval flow and the second business approval flow are based on the same approval process template, the remaining intermediate nodes in the second business approval flow without feedback are obtained, and the approval account levels of the remaining intermediate nodes are compared with the approval account levels of the intermediate nodes of the same level in the first business approval flow.

[0084] In step S503, the approval account with the higher level is obtained to replace the approval account corresponding to the remaining intermediate nodes in the original second business approval flow, and the updated second business approval flow is sent to the remaining intermediate nodes.

[0085] In the embodiment, if the first business approval flow and the second business approval flow are based on different approval process templates, the approval flows are not merged. If the first business approval flow and the second business approval flow are based on the same approval process template, the approval account levels of the remaining intermediate nodes without approval are compared, and the intermediate node with the higher level is taken as the intermediate node of the same level of the merged business approval flow. Then, the modified data can be used to generate a third business approval flow incremental update package, which is sent to the remaining intermediate nodes without performing approval processing on the second business approval flow, each remaining node performs incremental update on the second business approval flow data received by the original intermediate node, so as to change the second business approval flow data into new approval data, or the second business approval flow data on the server is directly updated to change into the third business approval flow data.

[0086] In another embodiment, as shown in FIG. 4, the step S4 can specifically include: Figure 6

[0087] ​​Step S601, a second business approval flow with the same starting point and without receiving intermediate node feedback signals is obtained, the intermediate node feedback signal being information fed back by an intermediate node to the starting point after modifying or updating the business approval flow data.

[0088] Step S602, it is judged whether the first business approval flow and the second business approval flow are the same approval process template.

[0089] Step S603, if the first business approval flow and the second business approval flow are the same approval process template, two input approval information of the first business approval flow and the second business approval flow are obtained respectively, and it is judged whether the size of the first input approval information in the first business approval flow is greater than the second input approval information in the second business approval flow.

[0090] Step S604, if the first input approval information in the first business approval flow is less than or equal to the second input approval information in the second business approval flow, the first input approval information and the second input approval information in the first and second business approval flows are merged to replace the first input approval information in the original second business approval flow, and the updated second business approval flow is sent to the remaining intermediate nodes.

[0091] Step S605, if the first input approval information is greater than the second input approval information, the intermediate node approval account associated with the preset screening index corresponding to the first input approval information is obtained, the approval account corresponding to the remaining intermediate node in the original second business approval flow is replaced, the input approval information in the first and second business approval flows is merged to replace the second input approval information in the original second business approval flow, and the updated second business approval flow is sent to the remaining intermediate nodes.

[0092] In this embodiment, the size of the first input approval information in the two business approval flows using the same template is judged to adjust the way of merging the approval flow data, thereby effectively merging the unapproved business flows, thereby effectively reducing the number of business approvals of each audit node.

[0093] The above-mentioned embodiments disclose a form-based drug information approval management method, which queries whether there is other unapproved business approval flow when a new business approval flow is generated, and if there is, the business approval flow is reasonably merged according to the approval path data relevance, thereby greatly reducing the number of separate to-be-approved process sheets, effectively reducing the processing pressure of each approval node, and saving the approval time.

[0094] In some embodiments, a form-based drug information approval management system is also disclosed, which specifically includes: a process template acquisition module configured to acquire unrecorded drug chemical formula information, generate an approval form according to the drug chemical formula information, the approval form including a first cell group for associating the drug chemical formula information and a second cell group for entering editable information, and filter an approval process template according to fixed approval information in the first cell group, the approval process template including start point data and approval path data; an analysis module configured to analyze the approval path data in the approval process template, the approval path data including judgment data attributes, switching condition groups, and / or intermediate nodes, and the switching condition groups including a plurality of preset screening indicators and respective corresponding different intermediate nodes; a transfer point acquisition module configured to acquire corresponding intermediate nodes as transfer point data after comparing the entered approval information in the second cell group with the preset screening indicators, update the start point data in the approval process template according to the fixed approval information, and add the transfer point data to the approval process template to generate a first business approval flow; and a process merging module configured to acquire other unapproved business approval flows initiated by the same start point, and confirm whether to merge and update as a new business approval flow according to the relevance of the approval path data of the first business approval flow and the other business approval flows. The second cell group includes, but is not limited to, a name cell, a CAS number cell, and a structural formula cell.

[0095] In this embodiment, the transfer point acquisition module is further configured to retrieve corresponding attribute cells in the first cell group and the second cell group of the approval form according to the judgment data attributes, compare the entered approval information in the cells with a plurality of preset screening indicators to acquire corresponding preset screening indicators, and acquire the intermediate nodes associated with the preset screening indicators as the transfer point data.

[0096] In this embodiment, the process merging module can specifically include: a first approval flow acquisition module configured to acquire a second business approval flow having the same start point and not receiving an intermediate node feedback signal, the intermediate node feedback signal being information fed back by an intermediate node to a start point after modifying or updating business approval flow data; a template judgment module configured to judge whether the first business approval flow and the second business approval flow are the same approval process template; a first merging module configured to, when the first business approval flow and the second business approval flow are the same approval process template, sequentially compare the approval account levels corresponding to the intermediate nodes at each level, acquire higher-level approval accounts at each level and the start point data added to the approval process template, merge the entered approval information in the first and second business approval flows and add them to the approval process template to generate a third business approval flow for replacing the second business approval flow.

[0097] In another embodiment, the process merging module can specifically include: a second approval flow obtaining module, configured to obtain a second business approval flow that has the same starting point and has not received all intermediate node feedback signals, the intermediate node feedback signal being information fed back by an intermediate node to the starting point after modifying or updating the business approval flow data. A remaining node judging module, configured to, when the first business approval flow and the second business approval flow are the same approval process template, obtain the remaining intermediate nodes in the second business approval flow that have not been fed back and compare them with the approval account levels of the corresponding same-level intermediate nodes in the first business approval flow. A second merging module, configured to replace the approval account corresponding to the remaining intermediate nodes in the original second business approval flow with the approval account of a higher level, and send the updated second business approval flow to the remaining intermediate nodes.

[0098] In another embodiment, the process merging module can specifically include: a third approval flow obtaining module, configured to obtain a second business approval flow that has the same starting point and has not received intermediate node feedback signals, the intermediate node feedback signal being information fed back by an intermediate node to the starting point after modifying or updating the business approval flow data. A template judging module, configured to judge whether the first business approval flow and the second business approval flow are the same approval process template. A third merging module, configured to, when the template judging module judges that they are the same approval process template, respectively obtain two entry approval information of the first business approval flow and the second business approval flow, and if the entry approval information in the first business approval flow is less than or equal to the entry approval information in the second business approval flow, merge the entry approval information in the first and second business approval flows and add them to the approval process template to generate a third business approval flow for replacing the second business approval flow.

[0099] It should be noted that the embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts of each embodiment can be referred to each other. For the form-based drug information approval management system disclosed in the embodiments, since it corresponds to the form-based drug information approval management method disclosed in the embodiments, the description is relatively simple, and the relevant parts are described in the method part.

[0100] In some other embodiments, a form-based drug information approval management apparatus is also provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements each step of the form-based drug information approval management method described in the above embodiments when executing the computer program.

[0101] The form-based drug information approval management device can include, but is not limited to, a processor and a memory. Those skilled in the art can understand that the schematic diagram is only an example of the form-based drug information approval management device, and does not constitute a limitation on the form-based drug information approval management device, and can include more or fewer components than the schematic diagram, or combine certain components, or different components.

[0102] The processor can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic components, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc. The processor is the control center of the form-based drug information approval management device, and connects various parts of the form-based drug information approval management device through various interfaces and lines.

[0103] The memory can be used to store the computer programs and / or modules, and the processor realizes various functions of the form-based drug information approval management device by running or executing the computer programs and / or modules stored in the memory, and calling the data stored in the memory. The memory can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, at least one application required for a function, etc. In addition, the memory can include a high-speed random access memory, and can also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, at least one disk storage device, a flash memory device, or other volatile solid-state storage device.

[0104] If the form-based drug information approval management device is implemented in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the above-mentioned embodiment methods can also be completed by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium. When the processor executes the computer program, the steps of each form-based drug information approval management method embodiment described above can be implemented. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or some intermediate forms, etc. The computer-readable medium can include any entity or device that can carry the computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium, etc. It should be noted that the content included in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.

[0105] Finally, it should be noted that: the above examples are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the foregoing examples, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing examples, or make equivalent substitutions for some technical features; and these modifications or substitutions do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

[0106] In summary, the above is only a preferred embodiment of the present application, and any equivalent changes and modifications made within the scope of the patent application of the present application shall be included in the scope of the present application.

Claims

1. A form-based drug information approval management method, characterized by, The method comprises the following steps: S1, obtaining unrecorded drug chemical formula information, generating an approval form according to the drug chemical formula information, the approval form comprising a first cell group for associating the drug chemical formula information and a second cell group for inputting editable information, screening an approval process template according to fixed approval information in the first cell group, the approval process template comprising start point data and approval path data; S2, analyzing the approval path data in the approval process template, the approval path data comprising judgment data attributes, switching condition groups and / or intermediate nodes, the switching condition groups comprising a plurality of preset screening indicators and respective corresponding different intermediate nodes; S3, obtaining corresponding intermediate nodes as transfer point data after comparing the input approval information in the second cell group with the preset screening indicators, updating the start point data in the approval process template according to the fixed approval information, and adding the transfer point data to the approval process template to generate a first business approval flow; S4, obtaining other unapproved business approval flows initiated by the same start point, and determining whether to merge and update into a new business approval flow according to the relevance of the approval path data of the first business approval flow and the other business approval flows; obtaining a second business approval flow that has the same start point and has not received all intermediate node feedback signals, the intermediate node feedback signal being information fed back to the start point after the intermediate node modifies or updates the business approval flow data; when the first business approval flow and the second business approval flow are the same approval process template, obtaining the remaining intermediate nodes in the second business approval flow that have not been fed back, and comparing the approval account levels of the corresponding intermediate nodes of the same level in the first business approval flow; obtaining an approval account with a higher level to replace the approval account corresponding to the remaining intermediate nodes in the original second business approval flow, and sending the updated second business approval flow to the remaining intermediate nodes.

2. The form-based drug information review management method of claim 1, wherein: The second cell group comprises a name cell, a CAS number cell, and a structural formula cell.

3. The form-based drug information review management method of claim 2, wherein, The step S3 comprises: According to the judgment data attributes, the corresponding attribute cells are retrieved and obtained in the first cell group and the second cell group of the approval form, the input approval information in the cells is compared with the plurality of preset screening indicators to obtain the corresponding preset screening indicators, and the intermediate nodes associated with the preset screening indicators are taken as the transfer point data.

4. The form-based drug information review management method of claim 3, wherein, The step S4 specifically comprises: obtaining a second business approval flow that has the same start point and has not received an intermediate node feedback signal, the intermediate node feedback signal being information fed back to the start point after the intermediate node modifies or updates the business approval flow data; determining whether the first business approval flow and the second business approval flow are the same approval process template; if they are the same approval process template, then the approval account levels of the intermediate nodes of the same level are compared in sequence, an approval account with a higher level of each level is obtained, the start point data is added to the approval process template, the input approval information in the first and second business approval flows is merged and added to the approval process template to generate a third business approval flow for replacing the second business approval flow.

5. A form-based drug information approval management system, characterized by, Specifically, The process template acquisition module is configured to acquire unrecorded drug chemical formula information, generate an approval form according to the drug chemical formula information, the approval form including a first cell group for associating the drug chemical formula information and a second cell group for inputting editable information, and filter an approval process template according to fixed approval information in the first cell group, the approval process template including start point data and approval path data; The analysis module is configured to analyze the approval path data in the approval process template, the approval path data including judgment data attributes, switching condition groups, and / or intermediate nodes, and the switching condition groups including multiple preset filtering indexes and respective corresponding different intermediate nodes; The transfer point acquisition module is configured to acquire corresponding intermediate nodes as transfer point data after comparing the input approval information in the second cell group with the preset filtering indexes, update the start point data in the approval process template according to the fixed approval information, and add the transfer point data to the approval process template to generate a first business approval flow; The process merging module is configured to acquire other unapproved business approval flows initiated by the same start point, and determine whether to merge and update into a new business approval flow according to the relevance of the approval path data of the first business approval flow and the other business approval flows. The second business approval flow with the same start point and without receiving all intermediate node feedback signals is acquired, the intermediate node feedback signal being information fed back by the intermediate node to the start point after modifying or updating the business approval flow data; when the first business approval flow and the second business approval flow are the same approval process template, the remaining intermediate nodes in the second business approval flow without feedback are acquired, and the approval account levels of the corresponding same-level intermediate nodes in the first business approval flow are compared; the approval account with a higher level is acquired to replace the approval account corresponding to the remaining intermediate nodes in the original second business approval flow, and the updated second business approval flow is sent to the remaining intermediate nodes.

6. The form-based drug information review management system according to claim 5, wherein, The second cell group includes a name cell, a CAS number cell, and a structural formula cell.

7. The form-based drug information review management system according to claim 6, characterized by, The transfer point acquisition module is further configured to retrieve corresponding attribute cells in the first cell group and the second cell group of the approval form according to the judgment data attributes, compare the input approval information in the cells with multiple preset filtering indexes to acquire corresponding preset filtering indexes, and acquire intermediate nodes associated with the preset filtering indexes as transfer point data. 8.A form-based drug information review and approval management apparatus, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: The processor executes the computer program to implement the steps of the method of any one of claims 1-4.

9. A computer readable storage medium, the computer readable storage medium storing a computer program, characterized in that: The computer program is executed by the processor to implement the steps of the method of any one of claims 1-4.

Images