Detailed Description
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only examples or embodiments of the invention, from which it is possible for a person skilled in the art, without inventive effort, to apply the invention also in other similar contexts. Unless otherwise apparent from the context, or otherwise indicated, like reference numbers in the figures refer to the same structure or operation.
As used in this disclosure and in the claims, the terms "a," "an," "the," and/or "the" are not intended to be inclusive in the singular, but rather are inclusive in the plural, unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that steps and elements are included which are explicitly identified, that the steps and elements do not form an exclusive list, and that a method or apparatus may include other steps or elements. The term "and/or" as used in this document includes any and all combinations of one or more of the associated listed items.
Flow charts are used in the present invention to illustrate the operations performed by a system according to embodiments of the present invention. It should be understood that the preceding or following operations are not necessarily performed in the exact order in which they are performed. Rather, various steps may be processed in reverse order or simultaneously. Meanwhile, other operations are added to or removed from these processes.
The invention provides a random and dispensing execution method of a random and dispensing system. Fig. 1 is a flow chart illustrating a method for performing randomization and dispensing of a randomization and medication system according to an embodiment of the present invention. As shown in fig. 1, the random and dispensing execution method of the random and dispensing system according to the embodiment of the present invention includes the following steps:
step 101, receiving operation based on a preposed standard operation flow;
step 102, before starting the random process, verifying whether one or more predetermined steps of the pre-standard operation flow have been executed;
103, when one or more predetermined steps are executed, initiating a random process, otherwise, not initiating the random process;
104, determining to enter a medicine dispensing process according to the result of the random process;
step 105, before starting the dispensing process, verifying whether one or more predetermined steps have been performed; and
step 106, when one or more predetermined steps have been performed, initiating a dispensing process, otherwise not.
The various steps in the randomization and dispensing execution method of the randomization and medication system are described in further detail below:
in step 101, an operation based on a pre-standard operation flow is received.
Before the random and drug delivery process of the random and drug system, the prepositive standard operation flow needs to be completed. The Standard Operation Procedure (SOP) may not be strictly implemented for various reasons (e.g., human factors), thereby posing a risk to the business. Operations based on the pre-standard operation flow are received, which may be used in other steps to verify the completion status of the pre-standard operation flow.
The pre-standard operational flow may include a number of predetermined steps. The predetermined step may refer to a core step in the pre-standard operation flow, which is a step that cannot be omitted or skipped in the whole project flow. The predetermined step may also refer to a step of the pre-standard operation flow that is of interest to the user. After all the preset steps in the pre-standard operation flow are completed, the subsequent random and medicine sending processes can be started, so that the pre-standard operation flow can be strictly implemented to reduce the overall risk of the project.
Optionally, the method may further comprise receiving a pre-configuration of the predetermined step. The predetermined steps may be configured in the system in advance according to actual business requirements. The predetermined steps may be system set or user set.
Optionally, the pre-standard operation flow may further include one or more non-predetermined steps. The non-predetermined step is a non-core step in the pre-standard operation flow and can be omitted or skipped. Failure to complete all of the non-predetermined steps does not affect the initiation of the randomization and dispensing process.
Optionally, the pre-standard operation flow may include a plurality of steps, and the step of receiving an operation based on the pre-standard operation flow includes: receiving the operation of the first step; and verifying whether the first step has been executed, and if so, allowing the operation of the second step following the first step.
The various steps in the pre-standard operation flow may need to be performed in a specific order in turn, thus requiring a guarantee that the previous step has been completed before proceeding to the next step. The operation of the first step is received and it is then verified whether the first step has been performed according to the operation. If the first step has been executed, allowing the operation of the second step following the first step; if the first step is not executed, the operation of the second step next to the first step is not allowed to be performed. Since the second step is performed immediately after the first step, i.e., the second step must be performed after the first step, the first step may be any other step except the last step in the pre-standard operation flow.
The pre-standard operation flow is further specifically described below with reference to a real service scenario. Fig. 2 is a schematic diagram illustrating a pre-standard operation flow according to an embodiment of the present invention. As shown in fig. 2, in this actual business scenario, the pre-standard operation flow may include steps 1-14. The following table 1 details the steps of fig. 2:
table 1
The steps 1-11 are steps before an IWRS System (Interactive Web Response System, Interactive network Response System) is on-line, and belong to predetermined steps in a preset standard operation flow, that is, the predetermined steps 1-11 need to be completed before the stochastic and drug delivery processes of the stochastic and drug System. The steps 12-14 are steps after the IWRS system is on-line, and do not belong to the predetermined steps in the pre-standard operation flow, i.e. the predetermined steps 12-14 may not be completed before the random and drug delivery process is performed by the random and drug system. Steps 1-14 may be performed by different persons, respectively, or may be performed by the same person.
Steps 1-14 are arranged in a specific order, and it is possible to set that the next step can be entered only after the previous step is completed. The next step can be assured that it has been completed before proceeding to it by: receiving the operation of step 1, and verifying whether step 1 is executed according to the operation of step 1. If step 1 has been performed, then the operation following step 2 is allowed to proceed; if step 1 is not performed, the operation following step 2 is not allowed to be performed. The steps 2-14 are received and verified by analogy, and the description is omitted here.
Optionally, the step of receiving the operation based on the pre-standard operation flow may further include: receiving another operation of the first step; and according to another operation, creating another prepositive standard operation flow from the first step to the second step.
In an actual business scenario, it may happen that there are two different operations in one step. For the case where there is another operation for the first step, another operation for the first step may be received, and then another pre-standard operation flow from the first step to the second step may be created according to the another operation. The other pre-standard operation flow may include any subsequent steps in addition to the first step and the second step.
The steps of creating another pre-standard operational flow according to another operation of the first step are described in further detail below in conjunction with fig. 3. Fig. 3 is a flowchart illustrating a process flow of creating another pre-standard according to an embodiment of the present invention. The pre-standard operation flow of fig. 3 includes five steps A, B, C, D, E. Only one operation 1 is executed in steps a to B, and only one operation 2 is executed in steps B to C, so that both operations 1 and 2 belong to the same pre-standard operation flow (i.e. SOP task 1 in fig. 3). In steps C to D, two operations 3 and 4 are performed. Thus, after receiving another operation 4 of step C, another pre-standard operational flow from step C to step D (i.e. SOP task 2 in fig. 3) is created according to another operation 4. In the subsequent steps D to E, the two preposed standard operation flows respectively and independently continue to the step 5 and the step 6, and the two preposed standard operation flows do not influence each other.
In step 102, it is verified whether one or more predetermined steps of the pre-standard operation flow have been performed before starting the random process.
In order to ensure that one or more predetermined steps in the pre-standard operation flow have been performed before the random process is started, it is necessary to verify whether one or more predetermined steps of the pre-standard operation flow have been performed.
Alternatively, it may be verified whether one or more predetermined steps of the pre-standard operational flow have been performed by querying a completion status switch associated with the pre-standard operational flow.
The manner of verifying whether one or more predetermined steps of the pre-standard operation flow have been performed may be by querying a completion status switch associated with the pre-standard operation flow. When one or more predetermined steps in the pre-standard operation flow are not executed, the completion status switch related to the predetermined steps can be set to an off state representing 'not executed'; after one or more predetermined steps in the pre-standard operational flow are executed, the completion status switch associated therewith may be set to an on state indicating "executed". By inquiring the completion state switch, the quick and accurate verification is realized. Completion status switches may be global, thereby facilitating cross-process queries.
In one example, the completion status switch may determine the switch status through the associated file in table 1. For example, after step 3 is executed, the "project requirement table" is saved as the related file of step 3. The status of the completion status switch associated with step 3 can thus be determined by detecting whether a "project requirement table" file exists. When the 'project requirement table' file is detected, the completion state switch related to the step 3 is in an open state; when the "project requirement table" file cannot be detected, the completion status switch associated with step 3 is in the off state.
There may be one or more completion status switches associated with the pre-standard operation flow, and each completion status switch may correspond to one or more predetermined steps, which is not limited in this embodiment of the present invention.
In step 103, a random procedure is initiated when one or more predetermined steps have been performed, otherwise the random procedure is not initiated.
The random process may be initiated when it is verified that one or more predetermined steps have been performed, the condition for initiating the random process is satisfied. If it is not verified that one or more predetermined steps have been performed, the conditions for initiating the random process are not met and the random process is not initiated. By setting the condition for initiating the random process, the random process can be started after one or more preset steps in the preposed standard operation flow are executed, so that the risk caused by the fact that the preset steps are not executed is avoided, and the overall reliability of the project is improved.
In step 104, the dispensing process is determined based on the result of the randomization process.
And obtaining the result of the random process after the random process is completed. The dispensing process can be started after the random process is performed, and thus the dispensing process is decided to be entered according to the result of the random process.
In step 105, it is verified whether one or more predetermined steps have been performed before starting the dispensing process.
In order to ensure that one or more predetermined steps in the pre-standard operation flow have been performed before the dispensing process is started, it is necessary to verify whether one or more predetermined steps of the pre-standard operation flow have been performed.
Alternatively, it may be verified whether one or more predetermined steps of the pre-standard operational flow have been performed by querying a completion status switch associated with the pre-standard operational flow. For details, reference may be made to step 102, which is not described herein again.
In step 106, the dispensing process may be initiated when one or more predetermined steps have been performed, otherwise the dispensing process may not be initiated.
When it is verified that one or more predetermined steps have been performed, the conditions for initiating the dispensing process are met, and the dispensing process may be initiated. If it is not verified that one or more predetermined steps have been performed, the conditions for initiating the dispensing process are not met and the dispensing process is not initiated. By setting the condition for initiating the dispensing process, the dispensing process can be started after one or more predetermined steps in the preposed standard operation flow are executed, so that the risk caused by the fact that the predetermined steps are not executed is avoided, and the overall reliability of the project is improved.
In summary, the random and dispensing execution method of the random and dispensing system according to the embodiment of the present invention manages the random and dispensing execution process by combining the execution status of the pre-standard operation flow in the random and dispensing system, and can ensure that the pre-standard operation flow is implemented strictly, thereby greatly reducing the risk of the whole project.
The random and medicine distribution execution method of the random and medicine system of the embodiment of the invention can further reduce the risk of the business and improve the overall safety by adding risk control.
Optionally, the method may further include: setting one or more risk points in the preposed standard operation flow, wherein at least part of the risk points are associated with the predetermined steps; assigning a risk weight value to one or more risk points; and determining a risk value according to the execution condition of the preposed standard operation flow.
One or more risk points may be set in the pre-standard operation flow, wherein at least some of the risk points are associated with one or more predetermined steps in the pre-standard operation flow. And respectively assigning corresponding risk weight values to one or more risk points.
For example, the risk weight value in the pre-standard operation flow shown in fig. 2 may be 1, 2, 3, or 4, wherein a smaller value represents a lower risk, and a higher value represents a higher risk. Since step 3 (writing and validating the random demand table) is very important for the overall project, the risk points associated with it may be assigned a risk weight value of 3. Whereas step 8 (external test validation) is of slightly lower importance for the overall project, the risk point associated therewith may be assigned a risk weight value of 2.
And determining a corresponding risk value according to the execution condition of the preposed standard operation flow. When determining the risk values, a weighted calculation may be performed according to the risk weight values of the respective risk points. The risk point with a high risk weight value has a large influence on the risk value, and the risk point with a low risk weight value has a small influence on the risk value, so that risk assessment can be more accurately performed according to the execution condition of the preposed standard operation flow.
Optionally, the method may further include: presenting a risk value; or presenting the risk value when the risk value is above a threshold.
After the risk value is determined, the risk value can be directly presented to the user, so that the user can intuitively know the overall risk condition of the project. Or after the risk value is determined, the risk value can be presented for reminding only when the risk value is higher than a preset threshold value.
Optionally, the method may further include: before starting the random process, inquiring a risk value; and/or further comprising querying the risk value before starting the dispensing process.
The risk value can intuitively let the user know and judge the risk condition of the current project. Before the random process is started, the risk value can be inquired, so that the user can know the risk condition and then make a decision. Similarly, before the process of dispensing the medicine is started, the risk value can be inquired first, so that the user can make a decision after knowing the risk condition.
The present invention also provides a randomization and medication system, comprising: a memory for storing instructions executable by the processor; and a processor for executing the instructions to implement the method as described above.
Fig. 4 is a system block diagram illustrating a randomization and drug system in accordance with an embodiment of the present invention. Random and drug system 400 may include internal communication bus 401, Processor (Processor)402, Read Only Memory (ROM)403, Random Access Memory (RAM)404, communication port 405, and hard disk 407. The internal communication bus 401 may enable data communication between the random and drug system 400 components. The processor 402 may make the determination and issue the prompt. In some embodiments, processor 402 may be comprised of one or more processors. The communication port 405 may enable data communication of the random and drug system 400 with the outside. In some embodiments, the random and drug system 400 may send and receive information and data from the network through the communication port 405. The random and drug system 400 may also include various forms of program storage units and data storage units, such as a hard disk 407, Read Only Memory (ROM)403 and Random Access Memory (RAM)404, capable of storing various data files for computer processing and/or communication use, as well as possibly program instructions for execution by the processor 402. The processor executes these instructions to implement the main parts of the method. The processor executes these instructions to implement the main parts of the method. The results processed by the processor are communicated to the user device through the communication port and displayed on the user interface.
The invention also provides a computer readable medium having stored thereon computer program code which, when executed by a processor, implements a method as described above.
The random and dispensing execution method of the random and dispensing system described above may be implemented as a computer program, stored in the hard disk 407, and recorded to the processor 402 for execution to implement the method of the present invention.
The random and dispensing execution methods, when implemented as a computer program, may also be stored as an article of manufacture in a computer readable storage medium. For example, computer-readable storage media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD)), smart cards, and flash memory devices (e.g., electrically Erasable Programmable Read Only Memory (EPROM), card, stick, key drive). In addition, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" can include, without being limited to, wireless channels and various other media (and/or storage media) capable of storing, containing, and/or carrying code and/or instructions and/or data.
It should be understood that the above-described embodiments are illustrative only. The embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the processing units may be implemented within one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, and/or other electronic units designed to perform the functions described herein, or a combination thereof.
Having thus described the basic concept, it will be apparent to those skilled in the art that the foregoing disclosure is only illustrative and not limiting of the invention. Various modifications, improvements and adaptations of the present invention may occur to those skilled in the art, although not explicitly described herein. Such modifications, improvements and adaptations are proposed within the present invention and are therefore within the spirit and scope of the exemplary embodiments of this invention.
Also, the present invention has been described using specific terms to describe embodiments of the invention. Such as "one embodiment," "an embodiment," and/or "some embodiments" means a feature, structure, or characteristic described in connection with at least one embodiment of the invention. Therefore, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, some of the features, structures, or characteristics of one or more embodiments of the present invention may be combined as suitable.
Aspects of the present invention may be embodied entirely in hardware, entirely in software (including firmware, resident software, micro-code, etc.) or in a combination of hardware and software. The above hardware or software may be referred to as "data block," module, "" engine, "" unit, "" component, "or" system. The processor may be one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), digital signal processing devices (DAPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or a combination thereof. Furthermore, aspects of the present invention may be represented as a computer product, including computer readable program code, embodied in one or more computer readable media. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips … …), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD) … …), smart cards, and flash memory devices (e.g., card, stick, key drive … …).
Similarly, it should be noted that in the preceding description of embodiments of the invention, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the embodiments. This method of disclosure, however, is not intended to suggest that the claimed subject matter requires more features than are expressly recited in the claims. Indeed, the embodiments may be characterized as having less than all of the features of a single embodiment disclosed above.
Although the present invention has been described with reference to the present specific embodiments, it will be appreciated by those skilled in the art that the above embodiments are merely illustrative of the present invention and various equivalent changes and substitutions may be made without departing from the spirit of the invention, and therefore, it is intended that all changes and modifications to the above embodiments, which fall within the true spirit of the invention, fall within the scope of the claims of the present invention.