CN113764083A - Prescription event auditing method, device and storage medium - Google Patents
Prescription event auditing method, device and storage medium Download PDFInfo
- Publication number
- CN113764083A CN113764083A CN202110363833.4A CN202110363833A CN113764083A CN 113764083 A CN113764083 A CN 113764083A CN 202110363833 A CN202110363833 A CN 202110363833A CN 113764083 A CN113764083 A CN 113764083A
- Authority
- CN
- China
- Prior art keywords
- prescription
- event
- intelligent
- audited
- auditing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 73
- 238000012550 audit Methods 0.000 claims description 198
- 238000012545 processing Methods 0.000 claims description 65
- 239000003814 drug Substances 0.000 claims description 44
- 201000010099 disease Diseases 0.000 claims description 7
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 claims description 7
- 238000012552 review Methods 0.000 description 8
- 229940079593 drug Drugs 0.000 description 7
- 230000008569 process Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 239000000284 extract Substances 0.000 description 6
- 230000008859 change Effects 0.000 description 5
- 230000003111 delayed effect Effects 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000004590 computer program Methods 0.000 description 2
- 238000005265 energy consumption Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
Landscapes
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Health & Medical Sciences (AREA)
- Engineering & Computer Science (AREA)
- Biomedical Technology (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The invention provides a prescription event auditing method, a device and a storage medium; the method comprises the following steps: receiving at least one prescription event to be audited; when a target prescription event to be audited meeting the intelligent auditing condition exists in at least one prescription event to be audited, waiting the target prescription event to be audited for a preset time period; if the intelligent checking prescription event is received, storing the intelligent checking prescription event to an intelligent checking pool; the intelligent prescription checking event is a prescription event which passes intelligent checking in at least one prescription event to be checked; and when the preset time period is reached, if the target prescription event to be audited does not belong to the intelligent prescription auditing event, storing the target prescription event to be audited in a common auditing pool. The invention can improve the auditing efficiency.
Description
Technical Field
The present invention relates to information processing technologies, and in particular, to a method and an apparatus for auditing prescription events, and a storage medium.
Background
In internet hospitals, intelligent auditing technologies have gradually been popularized and used. Before manual review is performed on the prescription, intelligent review is performed first, and then the intelligent review result is used as a reference for the manual review, so that the manual review burden can be reduced, and the review efficiency can be improved. However, in practical applications, the intelligent audit requires a certain time, and the manual audit cannot be performed after the intelligent audit is completed.
In the prior art, the method is mainly marked by a database or the sending of the event to be audited is delayed. The database marking can bring the problem of repeated marking, so that the same to-be-audited data is processed for multiple times; delaying the sending of the event to be audited causes the intelligent audit to be delayed. These methods all cause a problem of reduction in auditing efficiency.
Disclosure of Invention
The embodiment of the invention provides a prescription event auditing method, a device and a storage medium, which can improve auditing efficiency.
The technical scheme of the invention is realized as follows:
the embodiment of the invention provides a prescription event auditing method, which comprises the following steps:
receiving at least one prescription event to be audited;
when a target prescription event to be audited meeting the intelligent auditing condition exists in the at least one prescription event to be audited, waiting the target prescription event to be audited for a preset time period;
if an intelligent checking prescription event is received, storing the intelligent checking prescription event to an intelligent checking pool; the intelligent prescription auditing event is a prescription event which passes intelligent auditing in the at least one prescription event to be audited;
and when the preset time period is up, if the target prescription event to be audited does not belong to the intelligent prescription auditing event, storing the target prescription event to be audited in a common auditing pool.
In the foregoing solution, when there is a target to-be-audited prescription event that meets an intelligent audit condition in the at least one to-be-audited prescription event, the method further includes, after waiting for a preset time period for the target to-be-audited prescription event, that is, after the target to-be-audited prescription event is met, the method further includes:
and when the preset time period is up, if the intelligent checking prescription event is not received, storing the target prescription event to be checked into the common checking pool.
In the above solution, after receiving at least one event of a prescription to be reviewed, the method further includes:
if any one piece of medicine information and/or patient information matched with the intelligent auditing condition exists in at least one piece of medicine information and/or at least one piece of patient information in the at least one prescription event to be audited, the target prescription event to be audited meeting the intelligent auditing condition exists in the at least one prescription event to be audited;
and if at least one piece of medicine information and/or patient information which is not matched with the intelligent auditing condition exists in at least one piece of medicine information and/or at least one piece of patient information in the at least one prescription event to be audited, a non-target prescription event to be audited which does not meet the intelligent auditing condition exists in the at least one prescription event to be audited.
In the above solution, after receiving at least one event of a prescription to be reviewed, the method further includes:
and when the non-target prescription event to be audited which does not meet the intelligent auditing condition exists in the at least one prescription event to be audited, storing the non-target prescription event to be audited to the common auditing pool.
In the foregoing solution, the storing the intelligent audit prescription event to an intelligent audit pool includes:
extracting a first prescription number from the intelligent audit prescription event;
inquiring the first processing state identification from a prescription library according to the first prescription number;
and if the first processing state identifier indicates that the first prescription number is not stored in the intelligent audit pool or the common audit pool, storing the first prescription number in the intelligent audit pool.
In the above scheme, the storing the target prescription event to be reviewed to a common review pool includes:
extracting a second prescription number from the target prescription event to be audited;
inquiring the second processing state identification from a prescription library according to the second prescription number;
and if the second processing state identifier indicates that the second prescription number is not stored in the intelligent audit pool or the common audit pool, storing the second prescription number in the common audit pool.
In the above solution, after querying the first processing state identifier from the recipe library according to the first recipe number, the method further includes:
and if the first processing state identifier indicates that the first prescription number has been stored in the intelligent audit pool or the common audit pool, discarding the intelligent audit prescription event.
In the above solution, after querying the second processing state identifier from the prescription library according to the second prescription number, the method further includes:
and if the second processing state identifier indicates that the second prescription number has been stored in the intelligent audit pool or the common audit pool, discarding the target prescription event to be audited.
In the foregoing solution, after the intelligent audit prescription event is stored in an intelligent audit pool, the method further includes:
and changing the first processing state identifier corresponding to the intelligent audit prescription event in the prescription library into the one stored in the intelligent audit pool.
In the above scheme, after the target prescription event to be reviewed is stored in a common review pool, the method further includes:
and changing the second processing state identifier corresponding to the target prescription event to be audited in the prescription library into the second processing state identifier stored in the common audit pool.
In the above scheme, when there is a target to-be-audited prescription event that satisfies an intelligent audit condition in the at least one to-be-audited prescription event, the method includes:
performing intelligent audit on the at least one prescription event to be audited;
and if the at least one prescription event to be audited has an intelligent audit prescription event which passes the intelligent audit, sending the intelligent audit prescription event.
In the above scheme, the performing intelligent audit on the at least one prescription event to be audited includes:
and intelligently auditing at least one item of disease information, patient information, medicine information and doctor information corresponding to the at least one prescription event to be audited.
An embodiment of the present invention further provides a prescription event auditing apparatus, including:
the receiving unit is used for receiving at least one prescription event to be audited;
the waiting unit is used for waiting for the target prescription event to be audited for a preset time period when the target prescription event to be audited meeting the intelligent auditing condition exists in the at least one prescription event to be audited;
the storage unit is used for storing the intelligent checking prescription event to an intelligent checking pool if the intelligent checking prescription event is received; the intelligent prescription auditing event is a prescription event which passes intelligent auditing in the at least one prescription event to be audited; or, when the preset time period is reached, if the target prescription event to be audited does not belong to the intelligent prescription auditing event, storing the target prescription event to be audited in a common auditing pool.
An embodiment of the present invention further provides a prescription event auditing apparatus, including:
a memory for storing executable instructions;
and the processor is used for realizing the prescription event auditing method in the scheme when executing the executable instructions stored in the memory.
The embodiment of the invention also provides a storage medium, which stores executable instructions and is used for causing a processor to execute the method for auditing the prescription event in the scheme.
Therefore, the embodiment of the invention provides a prescription event auditing method, a device and a storage medium, which can receive at least one prescription event to be audited; and when a target prescription event to be audited meeting the intelligent auditing condition exists in at least one prescription event to be audited, waiting the target prescription event to be audited for a preset time period. Then, if the intelligent checking prescription event is received, the intelligent checking prescription event is stored in an intelligent checking pool; in addition, when the preset time period is reached, if the target prescription event to be audited does not belong to the intelligent prescription auditing event, the target prescription event to be audited is stored in the common auditing pool. Therefore, the intelligent checking prescription event which passes the intelligent checking can be preferentially received and processed in the preset time period, the utilization rate of the intelligent checking is improved, and meanwhile, the normal checking prescription process is not influenced, so that the checking efficiency is improved.
Drawings
Fig. 1 is a schematic system architecture diagram of a prescription event auditing method according to an embodiment of the present invention;
FIG. 2 is a first flowchart of a prescription event auditing method according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating a recipe event auditing method according to an embodiment of the present invention;
fig. 4 is a flowchart of a recipe event auditing method according to an embodiment of the present invention;
FIG. 5 is a fourth flowchart of a prescription event auditing method according to an embodiment of the present invention;
fig. 6 is a flowchart of a recipe event auditing method according to an embodiment of the present invention;
FIG. 7 is a sixth flowchart of a prescription event auditing method according to an embodiment of the present invention;
fig. 8 is a seventh flowchart of a prescription event auditing method according to an embodiment of the present invention;
fig. 9 is a flowchart eight of a prescription event auditing method according to an embodiment of the present invention;
FIG. 10 is a first schematic structural diagram of a prescription event auditing apparatus according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram of a prescription event auditing apparatus according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions of the present invention are further described in detail with reference to the drawings and the embodiments, the described embodiments should not be construed as limiting the present invention, and all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.
In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict.
To the extent that similar descriptions of "first/second" appear in this patent document, the description below will be added, where reference is made to the term "first \ second \ third" merely to distinguish between similar objects and not to imply a particular ordering with respect to the objects, it being understood that "first \ second \ third" may be interchanged either in a particular order or in a sequential order as permitted, to enable embodiments of the invention described herein to be practiced in other than the order illustrated or described herein.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used herein is for the purpose of describing embodiments of the invention only and is not intended to be limiting of the invention.
Fig. 1 is a schematic diagram of an optional system architecture of a prescription event auditing method according to an embodiment of the present invention, and as shown in fig. 1, a prescription event auditing apparatus 800 includes: a dispatching system 501 and an intelligent auditor system 502, wherein:
the prescription event auditing device 800 sends at least one to-be-audited prescription event to the sending system 501 and the intelligent auditor system 502 after receiving the at least one to-be-audited prescription event sent by the prescription system 503. The intelligent auditor system 502 calculates audit suggestions according to the prescription information, generates corresponding intelligent audit prescription events for the to-be-audited prescription events passing through the intelligent audit, and sends the intelligent audit prescription events to the dispatcher system 501. The dispatching system 501 monitors prescription events to be audited and intelligent audit prescription events at the same time, and integrates the results of the two events and puts the results into a corresponding audit pool in the prescription library 504; and if the intelligent checking prescription event corresponding to a certain prescription event to be checked is not received, the default is that the prescription event to be checked does not pass the intelligent checking. It can be understood that it takes a certain time for the intelligent auditor system 502 to intelligently audit the to-be-audited prescription events, and therefore, the to-be-audited prescription events can more easily reach the dispatcher system 501 before the corresponding intelligent auditor prescription events. Therefore, if the dispatcher system 501 directly dispatches the first to-be-audited prescription event to the audit pool, the intelligent audit result may be wasted; if the dispatcher system 501 does not process the first arriving event of the prescription to be audited, the dispatcher time will be delayed, and both cases will cause the auditing efficiency to be reduced.
In the related art, the order of the to-be-audited prescription event and the intelligent audit prescription event is not clear, so that the processing time is redundant. Meanwhile, the intelligent recipe audit event is usually used as a reference for manually auditing recipes, and the normal recipe audit flow cannot be influenced by the reduced availability of the intelligent auditor system 502. In addition, the related art has difficulty in solving the problem that events corresponding to the same recipe are dispatched by the dispatch system 501 multiple times.
Fig. 2 is an alternative flow chart of a recipe event auditing method according to an embodiment of the present invention, which will be described with reference to the steps shown in fig. 2.
S101, receiving at least one prescription event to be audited.
In an embodiment of the invention, the prescription event auditing device receives at least one to-be-audited prescription event sent by the prescription system. After receiving at least one prescription prescribed by a doctor, the prescription system establishes a corresponding prescription file for each prescription in a prescription library, wherein each prescription file comprises a unique prescription number; then, the prescription system generates a to-be-audited prescription event corresponding to each prescription, so as to obtain at least one to-be-audited prescription event. Each prescription event to be audited comprises patient information, medicine information and a prescription number of a corresponding prescription, and the prescription event auditing device can inquire a corresponding prescription file in a prescription library according to the prescription number.
It can be understood that the corresponding prescription file is established for each prescription, and the corresponding prescription event to be audited is generated, so that each prescription can be queried and processed more accurately, and the auditing efficiency is improved.
S102, when a target prescription event to be audited meeting the intelligent auditing condition exists in at least one prescription event to be audited, waiting the target prescription event to be audited for a preset time period.
In the embodiment of the invention, if the prescription event auditing device determines that a target prescription event to be audited meeting the intelligent auditing condition exists in at least one prescription event to be audited, the target prescription event to be audited is waited for a preset time period. The intelligent auditing condition is stored in the prescription event auditing device, is a preset judging condition and is used for judging whether each prescription event to be audited can refer to the intelligent auditing result. The to-be-audited prescription events meeting the intelligent auditing conditions can refer to the intelligent auditing results, and the to-be-audited prescription events not meeting the intelligent auditing conditions can not refer to the intelligent auditing results.
In the embodiment of the present invention, the intelligent audit condition may be set from dimensions such as drug information and patient information, and includes at least one matching condition, for example: setting a plurality of medicines as common medicines, and detecting whether all medicine information contained in each prescription event to be checked is matched with the common medicines; and/or setting an information range of applicable patients for each medicine from the aspects of age, sex, weight, disease history and the like of the patients, and detecting whether the patient information contained in each prescription event to be checked is matched with the information ranges of the applicable patients corresponding to all the medicine information contained in the prescription event to be checked. If one to-be-audited prescription event meets all matching conditions in the intelligent auditing conditions, the to-be-audited prescription event is considered to meet the intelligent auditing conditions; otherwise, the to-be-audited prescription event is considered to not meet the intelligent auditing condition.
In the embodiment of the invention, the prescription event auditing device extracts medicine information and patient information corresponding to each received prescription event to be audited in at least one received prescription event to be audited, and then matches the extracted at least one medicine information and at least one patient information with the intelligent auditing conditions one by one. If any one piece of medicine information and/or patient information matched with the intelligent auditing condition exists in the at least one piece of medicine information and/or the at least one piece of patient information, the prescription event auditing device considers that a target prescription event to be audited meeting the intelligent auditing condition exists in the at least one prescription event to be audited. And if the medicine information and/or the patient information which are not matched with the intelligent auditing condition exist in the at least one piece of medicine information and/or the at least one piece of patient information, the prescription event auditing device considers that a non-target prescription event to be audited which does not meet the intelligent auditing condition exists in the at least one prescription event to be audited.
In the embodiment of the invention, the preset time period is the time for waiting for the prescription event to be checked by the prescription event checking device. In a preset time period, the prescription event auditing device does not distribute an auditing pool to the target prescription event to be audited until the preset time period is over or the prescription event auditing device receives the intelligent prescription auditing event. The intelligent prescription checking event is a prescription event which passes intelligent checking in at least one prescription event to be checked. Because the normal use of one intelligent audit is usually in millisecond level, and the maximum time is not more than 10 seconds, the preset time period can be set to 30 seconds, and if the intelligent audit prescription event arrives within 30 seconds, the intelligent audit prescription event is dispatched to the intelligent audit pool; and if the intelligent checking prescription event does not arrive at the end of 30 seconds, allocating a target prescription event to be checked to the common checking pool.
It can be understood that the target to-be-audited prescription event meeting the intelligent auditing condition waits for the preset time period to wait for the generation and sending of the intelligent auditing result, so that the utilization rate of the intelligent auditing can be effectively improved, the intelligent auditing result can be obtained as far as possible, and the auditing efficiency is improved.
S103, if the intelligent checking prescription event is received, storing the intelligent checking prescription event to an intelligent checking pool; the intelligent prescription checking event is a prescription event which passes intelligent checking in at least one prescription event to be checked.
In the embodiment of the invention, before a preset time period for waiting for a target prescription event to be audited comes, if an intelligent audit prescription event corresponding to the target prescription event to be audited is received, the prescription event audit device stores the intelligent audit prescription event into an intelligent audit pool. The intelligent audit pool is a storage unit used for storing intelligent audit prescription events which pass the intelligent audit; the prescription file corresponding to the intelligent audit prescription event stored in the intelligent audit pool can take the result of passing the intelligent audit as reference in the follow-up audit so as to reduce the burden of manual audit.
In the embodiment of the invention, after the prescription event auditing device receives the intelligent auditing prescription event in the preset time period, the corresponding first prescription number can be extracted from the received intelligent auditing prescription event, and then the first prescription number is stored in the intelligent auditing pool. Then, the prescription event auditing device can change the processing state identifier on the prescription file corresponding to the first prescription number in the prescription library to be stored in the intelligent auditing pool so as to prevent the prescription number from being assigned for multiple times.
In the embodiment of the invention, if the prescription event auditing device still does not receive the intelligent auditing prescription event corresponding to the to-be-audited prescription event when the preset time period for waiting the to-be-audited prescription event arrives, the inquiry is initiated; and if the intelligent audit prescription event cannot be inquired, the intelligent audit of the prescription event to be audited is considered to be failed.
It can be understood that in the preset time period of waiting for the prescription event to be audited, if an intelligent audit prescription event which represents that the intelligent audit of the prescription event to be audited passes is received, the prescription event to be audited is directly stored in the intelligent audit pool. Therefore, the intelligent audit event is preferentially processed, the intelligent audit result is preferentially considered, namely, the intelligent audit result is adopted as much as possible, and the utilization rate of the intelligent audit is effectively improved.
And S104, when the preset time period is up, if the target prescription event to be audited does not belong to the intelligent prescription auditing event, storing the target prescription event to be audited in a common auditing pool.
In the embodiment of the invention, when the prescription event auditing device reaches the preset time period, if the target prescription event to be audited does not belong to the intelligent prescription auditing event, namely the intelligent auditing of the target prescription event to be audited does not pass, the target prescription event to be audited is stored in the common auditing pool. The common audit pool is a storage unit used for storing the to-be-audited prescription events which do not belong to the intelligent audit pass; and storing the prescription file corresponding to the to-be-audited prescription event in the common audit pool, wherein the result that the intelligent audit is not passed in the subsequent audit is used as a reference, and the manual audit is required to be completely carried out.
In the embodiment of the invention, when the prescription event auditing device arrives at the preset time period, if the target prescription event to be audited does not belong to the intelligent prescription auditing event, the corresponding second prescription number can be extracted from the target prescription event to be audited, and then the second prescription number is stored in the common auditing pool. Then, the prescription event auditing device can change the processing state identifier on the prescription file corresponding to the second prescription number in the prescription library to be stored in the common auditing pool so as to prevent the same prescription number from being assigned for multiple times.
It can be understood that the target to-be-audited prescription event which does not pass the intelligent audit is stored in the common audit pool and is completely audited manually. Therefore, all prescription events can be reasonably allocated, and the follow-up auditing can be performed in a targeted manner according to the allocation result of the prescription events, so that the auditing efficiency is improved. Through tests, by adopting the prescription event auditing method provided by the embodiment of the invention, 100% of intelligent prescription event auditing can be preferentially processed, and the auditing efficiency can be improved by 18-20%.
In some embodiments of the present invention, S105 shown in fig. 3 is further included after S102 shown in fig. 2, and will be described in conjunction with each step.
And S105, when the preset time period is reached, if the intelligent checking prescription event is not received, storing the target prescription event to be checked into a common checking pool.
In the embodiment of the invention, when a preset time period for waiting a target prescription event to be audited is reached, if an intelligent audit prescription event corresponding to the target prescription event to be audited is not received, the prescription event auditing device stores the target prescription event to be audited to a common audit pool.
In the embodiment of the invention, when a preset time period for waiting a target prescription event to be checked is reached, if an intelligent checking prescription event corresponding to the target prescription event to be checked is not received, a prescription event checking device can send a query request to an intelligent checking party system so as to query an intelligent checking result of the target prescription event to be checked; and if the target prescription event to be audited does not have the intelligent audit result or the intelligent audit is not passed through, storing the target prescription event to be audited in a common audit pool.
It can be understood that the intelligent auditor system may not issue an intelligent audit prescription event representing that the intelligent audit is passed for all received prescription events to be audited because the intelligent audit is not passed, the system is delayed, and the like. If the prescription event auditing device waits for the intelligent auditing of the prescription event to arrive, the auditing can be delayed. Therefore, when the preset time period is reached, the to-be-audited prescription event which does not receive the corresponding intelligent audit prescription event is regarded as that the intelligent audit is not passed, and the to-be-audited prescription event is stored in the common audit pool and is completely subjected to manual audit. Therefore, all prescription numbers can be guaranteed to be assigned in time, and timely completion of auditing is guaranteed.
In some embodiments of the present invention, S106-S107 shown in fig. 4 is further included after S101 shown in fig. 2, and will be described in conjunction with each step.
S106, if any one piece of medicine information and/or patient information matched with the intelligent auditing condition exists in at least one piece of medicine information and/or at least one piece of patient information in at least one prescription event to be audited, a target prescription event to be audited meeting the intelligent auditing condition exists in at least one prescription event to be audited.
In the embodiment of the invention, the prescription event auditing device extracts medicine information and patient information corresponding to each received prescription event to be audited in at least one received prescription event to be audited, and then matches the extracted at least one medicine information and at least one patient information with the intelligent auditing conditions one by one. If any one piece of medicine information and/or patient information matched with the intelligent auditing condition exists in the at least one piece of medicine information and/or the at least one piece of patient information, the prescription event auditing device considers that a target prescription event to be audited meeting the intelligent auditing condition exists in the at least one prescription event to be audited. And if the medicine information and/or the patient information which are not matched with the intelligent auditing condition exist in the at least one piece of medicine information and/or the at least one piece of patient information, the prescription event auditing device considers that a non-target prescription event to be audited which does not meet the intelligent auditing condition exists in the at least one prescription event to be audited.
S107, if at least one piece of medicine information and/or patient information in at least one prescription event to be audited does not match with the intelligent auditing condition, a non-target prescription event to be audited which does not meet the intelligent auditing condition exists in the at least one prescription event to be audited.
In the embodiment of the invention, the prescription event auditing device extracts medicine information and patient information corresponding to each received prescription event to be audited in at least one received prescription event to be audited, and then matches the extracted at least one medicine information and at least one patient information with the intelligent auditing conditions one by one. And if the medicine information and/or the patient information which are not matched with the intelligent auditing condition exist in the at least one piece of medicine information and/or the at least one piece of patient information, the prescription event auditing device considers that a non-target prescription event to be audited which does not meet the intelligent auditing condition exists in the at least one prescription event to be audited.
In some embodiments of the present invention, S108 shown in fig. 4 is further included after S101 shown in fig. 2, and will be described in conjunction with each step.
And S108, when the non-target prescription event to be audited which does not meet the intelligent auditing condition exists in the at least one prescription event to be audited, storing the non-target prescription event to be audited to a common auditing pool.
In the embodiment of the invention, if the prescription event auditing device determines that a non-target prescription event to be audited which does not meet the intelligent auditing condition exists in at least one prescription event to be audited, the non-target prescription event to be audited is stored in a common auditing pool.
In some embodiments of the present invention, S103 shown in fig. 2 may be implemented by S1031 to S1033 shown in fig. 5, which will be described in conjunction with the steps.
And S1031, extracting the first prescription number from the intelligent prescription checking event.
In the embodiment of the invention, after the prescription event auditing device receives the intelligent prescription auditing event in the preset time period, the corresponding first prescription number can be extracted from the received intelligent prescription auditing event.
S1032, inquiring the first processing state identification from the prescription library according to the first prescription number.
In the embodiment of the invention, after the prescription event auditing device extracts the first prescription number, the corresponding first prescription file can be inquired from the prescription library according to the first prescription number, and then the first processing state identifier in the first prescription file is confirmed. Wherein the first processing state identifier is used to characterize a processing state of the first recipe profile.
And S1033, if the first processing state identifier indicates that the first prescription number is not stored in the intelligent audit pool or the common audit pool, storing the first prescription number in the intelligent audit pool.
In the embodiment of the present invention, the processing state identifier represents the processing state of the corresponding prescription file, and is divided into: stored to the intelligent audit pool, stored to the common audit pool and unprocessed. When the processing state identifier is stored in the intelligent audit pool, the prescription number representing the prescription file is stored in the intelligent audit pool; when the processing state identifier is stored in the common audit pool, the prescription number representing the prescription file is stored in the common audit pool; and when the processing state is identified as unprocessed, the prescription number representing the prescription file is not stored in the intelligent audit pool or the common audit pool.
In the embodiment of the invention, if the prescription event auditing device inquires that the first processing state identifier is unprocessed, that is, the first prescription number is not stored in any one of the intelligent auditing pool or the common auditing pool, which indicates that the first prescription number can be processed at present, the prescription event auditing device stores the first prescription number in the intelligent auditing pool.
It can be understood that, before assigning the prescription number, the prescription event auditing device performs an idempotent check to confirm whether the prescription number has been assigned; while no duplicate assignment is made to prescription numbers that have already been assigned. Therefore, the idempotent of the prescription number assignment is ensured, the result confusion caused by repeated assignment is avoided, and the processing energy consumption of the system is also saved.
In some embodiments of the present invention, S104 shown in fig. 2 may be implemented by S1041-S1043 shown in fig. 6, which will be described in conjunction with various steps.
And S1041, extracting a second prescription number from the target prescription event to be checked.
In the embodiment of the invention, when the prescription event auditing device arrives at the preset time period, if the target prescription event to be audited does not belong to the intelligent prescription auditing event, namely the intelligent auditing of the target prescription event to be audited is not passed, the corresponding second prescription number can be extracted from the target prescription event to be audited.
S1042, according to the second prescription number, inquiring a second processing state identification from the prescription library.
In the embodiment of the present invention, after the prescription event auditing device extracts the second prescription number, the corresponding second prescription file may be queried from the prescription library according to the second prescription number, and then the second processing state identifier in the second prescription file is confirmed. Wherein the second processing state identifier is used to characterize a processing state of the second recipe profile.
And S1043, if the second processing state identifier indicates that the second prescription number is not stored in any one of the intelligent audit pool or the common audit pool, storing the second prescription number in the common audit pool.
In the embodiment of the invention, if the prescription event auditing device inquires that the second processing state identifier is unprocessed, that is, the second prescription number is not stored in any one of the intelligent auditing pool or the common auditing pool, which indicates that the second prescription number can be processed currently, the prescription event auditing device stores the second prescription number in the common auditing pool.
It can be understood that, before assigning the prescription number, the prescription event auditing device performs an idempotent check to confirm whether the prescription number has been assigned; while no duplicate assignment is made to prescription numbers that have already been assigned. Therefore, the idempotent of the prescription number assignment is ensured, the result confusion caused by repeated assignment is avoided, and the processing energy consumption of the system is also saved.
In some embodiments of the present invention, S1034 is further included after S1032 shown in fig. 5, and will be described with reference to each step.
S1034, if the first processing state identifier indicates that the first prescription number is stored in the intelligent audit pool or the common audit pool, discarding the intelligent audit prescription event.
In the embodiment of the invention, if the prescription event auditing device inquires that the first processing state identifier is stored in the intelligent auditing pool or the common auditing pool, the first prescription number is represented to be dispatched, the intelligent auditing prescription event is discarded, and the first prescription number is not dispatched again.
It can be understood that, for the first prescription number that has been assigned, the corresponding intelligent audit prescription event is discarded in time, so that the occupation of the system storage space can be reduced.
In some embodiments of the present invention, S1044 is further included after S1042 shown in fig. 6, which will be described in conjunction with the steps.
And S1044, if the second processing state identifier indicates that the second prescription number has been stored in any one of the intelligent audit pool or the common audit pool, discarding the target prescription event to be audited.
In the embodiment of the invention, if the prescription event auditing device inquires that the second processing state identifier is stored in the intelligent auditing pool or the common auditing pool, the prescription event auditing device indicates that the second prescription number is assigned, and discards the target prescription event to be audited without assigning the second prescription number again.
It can be understood that, for the second prescription number that has been assigned, the corresponding target prescription event to be reviewed is discarded in time, which can reduce the occupation of the system memory space.
In some embodiments of the present invention, S109 shown in fig. 7 is further included after S103 shown in fig. 2, and will be described with reference to each step.
And S109, changing the first processing state identifier corresponding to the intelligent audit prescription event in the database into the first processing state identifier stored in the intelligent audit pool.
In the embodiment of the invention, after the prescription event auditing device stores the intelligent auditing prescription event into the intelligent auditing pool, the first processing state identifier corresponding to the intelligent auditing prescription event in the database is changed into the one stored into the intelligent auditing pool.
It can be understood that, after the prescription number assignment is completed, the prescription event auditing device changes the corresponding processing state identifier, so that the subsequent prescription number assignment process can be prompted, and the repeated assignment of the same prescription number is avoided.
In some embodiments of the present invention, S110 shown in fig. 7 is further included after S104 shown in fig. 2, and will be described in conjunction with various steps.
And S110, changing the second processing state identifier corresponding to the target prescription event to be audited in the database into the second processing state identifier stored in the common audit pool.
In the embodiment of the invention, after the prescription event auditing device stores the target prescription event to be audited into the common auditing pool, the second processing state identifier corresponding to the target prescription event to be audited in the database is changed into the one stored into the common auditing pool.
It can be understood that, after the prescription number assignment is completed, the prescription event auditing device changes the corresponding processing state identifier, so that the subsequent prescription number assignment process can be prompted, and the repeated assignment of the same prescription number is avoided.
In some embodiments of the present invention, S111-S112 shown in fig. 8 is further included after S102 shown in fig. 2, and will be described in conjunction with each step.
And S111, intelligently auditing at least one prescription event to be audited.
In the embodiment of the invention, the prescription event auditing device intelligently audits at least one item of disease information, patient information, medicine information and doctor information corresponding to the prescription event to be audited.
And S112, if the intelligent checking prescription event which passes the intelligent checking exists in the at least one to-be-checked prescription event, sending the intelligent checking prescription event.
In the embodiment of the invention, after the prescription event auditing device finishes intelligent auditing, if an intelligent auditing prescription event which passes the intelligent auditing exists in at least one prescription event to be audited, the intelligent auditing prescription event is sent.
In some embodiments of the present invention, S112 shown in fig. 8 may be implemented through S1121, which will be described in conjunction with various steps.
S1121, intelligently auditing at least one item of disease information, patient information, medicine information and doctor information corresponding to at least one prescription event to be audited.
In the embodiment of the invention, the prescription event auditing device intelligently audits at least one item of disease information, patient information, medicine information and doctor information corresponding to the prescription event to be audited, and determines whether the prescription is intelligently audited to pass.
In the embodiment of the invention, the judgment rule for intelligent audit in the prescription event audit device and the intelligent audit condition for judging whether the intelligent audit can be performed are partially overlapped in content, but the judgment rule for intelligent audit is more detailed, and more time is needed for intelligent audit.
Fig. 9 is an alternative flow chart of a recipe event auditing method according to an embodiment of the present invention, which will be described with reference to the steps shown in fig. 9.
S301, the intelligent auditor system receives the prescription event to be audited.
In the embodiment of the present invention, the intelligent auditor system 502 receives at least one to-be-audited prescription event sent by the prescription system 503.
S302, the intelligent auditor system intelligently audits the prescription event to be audited to obtain an intelligent audit prescription event.
In the embodiment of the present invention, the intelligent auditor system 502 performs intelligent audit on the received at least one prescription event to be audited, so as to obtain an intelligent audit prescription event that passes the intelligent audit in the at least one prescription event to be audited.
S303, the intelligent auditor system sends the intelligent audit prescription event.
In the embodiment of the present invention, the intelligent auditor system 502 dispatches the intelligent audit prescription event that passes the intelligent audit to the dispatcher system 501.
S304, the dispatching system receives the prescription event to be checked.
In the embodiment of the present invention, the dispatcher system 501 receives at least one to-be-audited prescription event sent by the prescription system 503.
S305, the dispatcher system judges whether the prescription event to be audited meets the intelligent auditing condition.
In the embodiment of the present invention, the dispatching system 501 determines whether each received prescription event to be audited meets the intelligent audit condition. If the dispatcher system 501 determines that the received prescription event to be audited is a target prescription event to be audited meeting the intelligent auditing condition, the target prescription event to be audited is waited for a preset time period; otherwise, storing the prescription event to be audited in the common audit pool.
S306, the dispatcher system waits for a preset time period for the target prescription event to be audited meeting the intelligent auditing condition.
In the embodiment of the present invention, if it is determined that the received prescription event to be audited is the target prescription event to be audited that satisfies the intelligent audit condition, the dispatcher system 501 waits for the target prescription event to be audited for a preset time period.
And S307, the party system inquires the intelligent checking result when the preset time period is reached.
In the embodiment of the present invention, when the preset time period is reached, if the intelligent audit prescription event corresponding to the target prescription event to be audited is not received, the dispatcher system 501 queries the intelligent audit result corresponding to the target prescription event to be audited from the intelligent auditor system 502.
And S308, the dispatcher system determines whether the intelligent checking result passes or not.
In the embodiment of the present invention, the dispatcher system 501 determines whether the intelligent audit result passes. Before the preset time period is reached, if an intelligent checking prescription event corresponding to the target prescription event to be checked is received, the dispatch system 501 determines that the intelligent checking result of the target prescription event to be checked passes. When the preset time period is reached, if the intelligent audit prescription event corresponding to the target prescription event to be audited is not received and the intelligent audit result of the target prescription event to be audited is not inquired to be passed, the dispatch system 501 considers that the intelligent audit result of the target prescription event to be audited is not passed. If the dispatching system 501 judges that the intelligent audit result of the target prescription event to be audited passes, that is, receives an intelligent audit prescription event corresponding to the target prescription event to be audited, then extracts the corresponding prescription number from the intelligent audit prescription event, and stores the prescription number corresponding to the intelligent audit prescription event into an intelligent audit pool; if the dispatch system 501 determines that the intelligent audit result of the target to-be-audited prescription event does not pass or the intelligent audit result is not obtained, the corresponding prescription number is extracted from the target intelligent audit prescription event, and the prescription number corresponding to the target to-be-audited prescription event is stored in a common audit pool.
S309, the dispatching system updates the information of whether the intelligent checking result passes the prescription file.
In the embodiment of the present invention, the dispatching system 501 updates the information on whether the intelligent audit result of the target to-be-audited prescription event passes the intelligent audit result in the corresponding prescription file in the prescription library 504.
Fig. 10 is an alternative structural schematic diagram of a prescription event auditing apparatus according to an embodiment of the present invention. As shown in fig. 10, an embodiment of the present invention further provides a prescription event auditing apparatus 800, including: a receiving unit 804, a waiting unit 805, and a storing unit 806, wherein:
a receiving unit 804, configured to receive at least one prescription event to be reviewed;
a waiting unit 805, configured to wait for a preset time period for a target prescription event to be audited when the target prescription event to be audited that meets the intelligent audit condition exists in the at least one prescription event to be audited;
a storage unit 806, configured to store the intelligent audit prescription event to an intelligent audit pool if the intelligent audit prescription event is received; the intelligent prescription checking event is a prescription event which passes intelligent checking in at least one prescription event to be checked; or when the preset time period is up, if the target prescription event to be audited does not belong to the intelligent prescription auditing event, storing the target prescription event to be audited in the common auditing pool.
In some embodiments of the present invention, the storage unit 806 is further configured to, when a preset time period is reached, store the target to-be-checked prescription event to the common checking pool if the intelligent checking prescription event is not received.
In some embodiments of the present invention, the prescription event auditing apparatus 800 further includes: a matching judgment unit 807 in which:
a matching judgment unit 807, configured to, if at least one piece of drug information and/or at least one piece of patient information in at least one prescription event to be audited includes any piece of drug information and/or patient information that matches the intelligent audit condition, determine that a target prescription event to be audited that meets the intelligent audit condition exists in the at least one prescription event to be audited; or if at least one piece of medicine information and/or patient information in at least one prescription event to be audited does not match the intelligent auditing condition, a non-target prescription event to be audited which does not meet the intelligent auditing condition exists in at least one prescription event to be audited.
In some embodiments of the present invention, the storage unit 806 is further configured to store the non-target to-be-audited prescription event to the common audit pool when there is a non-target to-be-audited prescription event that does not satisfy the intelligent audit condition in the at least one to-be-audited prescription event.
In some embodiments of the present invention, the prescription event auditing apparatus 800 further includes: an extracting unit 808 and a querying unit 809, wherein:
an extracting unit 808, configured to extract the first prescription number from the intelligent audit prescription event.
The query unit 809 is configured to query the first processing state identifier from the recipe library according to the first recipe number.
The storage unit 806 is further configured to store the first prescription number in the intelligent audit pool if the first processing state identifier indicates that the first prescription number is not stored in any one of the intelligent audit pool and the common audit pool.
In some embodiments of the present invention, the extracting unit 808 is further configured to extract the second prescription number from the target to-be-audited prescription event.
The query unit 809 is further configured to query the second processing state identifier from the recipe library according to the second recipe number.
The storage unit 806 is further configured to store the second prescription number in the general audit pool if the second processing state identifier indicates that the second prescription number is not stored in any of the intelligent audit pool or the general audit pool.
In some embodiments of the present invention, the prescription event auditing apparatus 800 further includes: a discard unit 810, wherein:
a discarding unit 810, configured to discard the intelligent audit prescription event if the first processing state identifier indicates that the first prescription number has been stored in the intelligent audit pool or the common audit pool.
In some embodiments of the present invention, the discarding unit 810 is further configured to discard the target to-be-audited prescription event if the second processing state identifier indicates that the second prescription number has been stored in the intelligent audit pool or the general audit pool.
In some embodiments of the present invention, the prescription event auditing apparatus 800 further includes: an identity change unit 811, wherein:
the identifier changing unit 811 is configured to change the identifier of the first processing state corresponding to the intelligent audit prescription event in the prescription library to be stored in the intelligent audit pool.
In some embodiments of the present invention, the identifier changing unit 811 is further configured to change the identifier of the second processing state corresponding to the target to-be-audited prescription event in the prescription library to be stored in the common audit pool.
In some embodiments of the present invention, the prescription event auditing apparatus 800 further includes: an intelligent auditing unit 812, a dispatch unit 813, where:
an intelligent auditing unit 812, configured to perform intelligent auditing on at least one prescription event to be audited;
the dispatch unit 813 is configured to dispatch the intelligent audit prescription event if there is an intelligent audit prescription event that passes the intelligent audit in the at least one to-be-audited prescription event.
In some embodiments of the present invention, the intelligent auditing unit 812 is further configured to perform intelligent auditing on at least one of disease information, patient information, drug information, and doctor information corresponding to at least one prescription event to be audited.
It should be noted that fig. 11 is an optional structural schematic diagram of the prescription event auditing apparatus according to the embodiment of the present invention, and as shown in fig. 11, the hardware entities of the prescription event auditing apparatus 800 include: a processor 801, a communication interface 802, and a memory 803, wherein:
the processor 801 generally controls the overall operation of the prescription event auditing apparatus 800.
The communication interface 802 may enable the prescription event auditing apparatus 800 to communicate with other apparatuses or devices over a network.
The Memory 803 is configured to store instructions and applications executable by the processor 801, and may also buffer data (e.g., image data, audio data, voice communication data, and video communication data) to be processed or already processed by each module in the pending event auditing apparatus 801 and the prescription event auditing apparatus 800, and may be implemented by a FLASH Memory (FLASH) or a Random Access Memory (RAM).
It should be noted that, in the embodiment of the present invention, if the method for detecting malicious behavior is implemented in the form of a software functional module, and is sold or used as a standalone product, it may also be stored in a computer-readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling the risk detection apparatus 800 (which may be a personal computer, a server, or a network device) to execute all or part of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, or an optical disk. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.
Correspondingly, the embodiment of the present invention provides a first computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps in the method corresponding to the prescription event auditing apparatus.
Here, it should be noted that: the above description of the storage medium and device embodiments is similar to the description of the method embodiments above, with similar advantageous effects as the method embodiments. For technical details not disclosed in the embodiments of the storage medium and the apparatus according to the invention, reference is made to the description of the embodiments of the method according to the invention.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units; can be located in one place or distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, all the functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The above description is only an embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the present invention, and all such changes or substitutions are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (15)
1. A prescription event auditing method, comprising:
receiving at least one prescription event to be audited;
when a target prescription event to be audited meeting the intelligent auditing condition exists in the at least one prescription event to be audited, waiting the target prescription event to be audited for a preset time period;
if an intelligent checking prescription event is received, storing the intelligent checking prescription event to an intelligent checking pool; the intelligent prescription auditing event is a prescription event which passes intelligent auditing in the at least one prescription event to be audited;
and when the preset time period is up, if the target prescription event to be audited does not belong to the intelligent prescription auditing event, storing the target prescription event to be audited in a common auditing pool.
2. The prescription event auditing method according to claim 1, wherein when there is a target prescription event to be audited that meets an intelligent auditing condition in the at least one prescription event to be audited, the method further comprises, after waiting for a preset time period for the target prescription event to be audited:
and when the preset time period is up, if the intelligent checking prescription event is not received, storing the target prescription event to be checked into the common checking pool.
3. Prescription event auditing method according to claim 1 or 2, characterized in that after receiving at least one prescription event to be audited, the method further comprises:
if any one piece of medicine information and/or patient information matched with the intelligent auditing condition exists in at least one piece of medicine information and/or at least one piece of patient information in the at least one prescription event to be audited, the target prescription event to be audited meeting the intelligent auditing condition exists in the at least one prescription event to be audited;
and if at least one piece of medicine information and/or patient information which is not matched with the intelligent auditing condition exists in at least one piece of medicine information and/or at least one piece of patient information in the at least one prescription event to be audited, a non-target prescription event to be audited which does not meet the intelligent auditing condition exists in the at least one prescription event to be audited.
4. The prescription event auditing method according to claim 3, wherein after receiving at least one prescription event to be audited, the method further comprises:
and when the non-target prescription event to be audited which does not meet the intelligent auditing condition exists in the at least one prescription event to be audited, storing the non-target prescription event to be audited to the common auditing pool.
5. The prescription event auditing method according to any one of claims 1-4, where storing the intelligent audit prescription event to an intelligent audit pool includes:
extracting a first prescription number from the intelligent audit prescription event;
inquiring the first processing state identification from a prescription library according to the first prescription number;
and if the first processing state identifier indicates that the first prescription number is not stored in the intelligent audit pool or the common audit pool, storing the first prescription number in the intelligent audit pool.
6. The prescription event auditing method according to any one of claims 1-4, where storing the target to-be-audited prescription event to a common audit pool includes:
extracting a second prescription number from the target prescription event to be audited;
inquiring the second processing state identification from a prescription library according to the second prescription number;
and if the second processing state identifier indicates that the second prescription number is not stored in the intelligent audit pool or the common audit pool, storing the second prescription number in the common audit pool.
7. The prescription event auditing method according to claim 5, after said querying the first processing state identification from a prescription library according to the first prescription number, the method further comprises:
and if the first processing state identifier indicates that the first prescription number has been stored in the intelligent audit pool or the common audit pool, discarding the intelligent audit prescription event.
8. The prescription event auditing method according to claim 6, after said querying the second processing state identification from a prescription library according to the second prescription number, the method further comprises:
and if the second processing state identifier indicates that the second prescription number has been stored in the intelligent audit pool or the common audit pool, discarding the target prescription event to be audited.
9. The prescription event auditing method according to claim 1, wherein after storing the intelligent audit prescription event to an intelligent audit pool, the method further comprises:
and changing the first processing state identifier corresponding to the intelligent audit prescription event in the prescription library into the one stored in the intelligent audit pool.
10. The prescription event auditing method according to claim 1, wherein after storing the target prescription event to be audited to a common audit pool, the method further comprises:
and changing the second processing state identifier corresponding to the target prescription event to be audited in the prescription library into the second processing state identifier stored in the common audit pool.
11. The prescription event auditing method according to claims 1-10, wherein when there is a target to-be-audited prescription event that satisfies the intelligent auditing condition among the at least one to-be-audited prescription event, after waiting the target to-be-audited prescription event for a preset time period, the method further comprises:
performing intelligent audit on the at least one prescription event to be audited;
and if the at least one prescription event to be audited has an intelligent audit prescription event which passes the intelligent audit, sending the intelligent audit prescription event.
12. The prescription event auditing method according to claim 11, wherein the intelligently auditing the at least one prescription event to be audited includes:
and intelligently auditing at least one item of disease information, patient information, medicine information and doctor information corresponding to the at least one prescription event to be audited.
13. A prescription event auditing apparatus, comprising:
the receiving unit is used for receiving at least one prescription event to be audited;
the waiting unit is used for waiting for the target prescription event to be audited for a preset time period when the target prescription event to be audited meeting the intelligent auditing condition exists in the at least one prescription event to be audited;
the storage unit is used for storing the intelligent checking prescription event to an intelligent checking pool if the intelligent checking prescription event is received; the intelligent prescription auditing event is a prescription event which passes intelligent auditing in the at least one prescription event to be audited; or, when the preset time period is reached, if the target prescription event to be audited does not belong to the intelligent prescription auditing event, storing the target prescription event to be audited in a common auditing pool.
14. A first prescription event auditing apparatus, comprising:
a memory for storing executable instructions;
a processor for implementing the method of any one of claims 1 to 12 when executing executable instructions stored in the memory.
15. A storage medium having stored thereon executable instructions for causing a processor to perform the method of any one of claims 1 to 12 when executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110363833.4A CN113764083A (en) | 2021-04-02 | 2021-04-02 | Prescription event auditing method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110363833.4A CN113764083A (en) | 2021-04-02 | 2021-04-02 | Prescription event auditing method, device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113764083A true CN113764083A (en) | 2021-12-07 |
Family
ID=78786880
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110363833.4A Pending CN113764083A (en) | 2021-04-02 | 2021-04-02 | Prescription event auditing method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113764083A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107785060A (en) * | 2017-03-03 | 2018-03-09 | 平安医疗健康管理股份有限公司 | Medicine prescription checking method and device |
| CN107918907A (en) * | 2017-12-13 | 2018-04-17 | 深圳市易达云科技有限公司 | A kind of order checking method and system |
| CN109255747A (en) * | 2018-09-12 | 2019-01-22 | 福建南威软件有限公司 | A kind of intelligent checks method that information is declared |
| CN110729040A (en) * | 2019-10-23 | 2020-01-24 | 泰康保险集团股份有限公司 | Prescription auditing method and device, storage medium and electronic equipment |
| CN111813966A (en) * | 2020-07-13 | 2020-10-23 | 湖南快乐阳光互动娱乐传媒有限公司 | Data auditing method and device |
-
2021
- 2021-04-02 CN CN202110363833.4A patent/CN113764083A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107785060A (en) * | 2017-03-03 | 2018-03-09 | 平安医疗健康管理股份有限公司 | Medicine prescription checking method and device |
| CN107918907A (en) * | 2017-12-13 | 2018-04-17 | 深圳市易达云科技有限公司 | A kind of order checking method and system |
| CN109255747A (en) * | 2018-09-12 | 2019-01-22 | 福建南威软件有限公司 | A kind of intelligent checks method that information is declared |
| CN110729040A (en) * | 2019-10-23 | 2020-01-24 | 泰康保险集团股份有限公司 | Prescription auditing method and device, storage medium and electronic equipment |
| CN111813966A (en) * | 2020-07-13 | 2020-10-23 | 湖南快乐阳光互动娱乐传媒有限公司 | Data auditing method and device |
Non-Patent Citations (2)
| Title |
|---|
| 孔旭东等: "医院前置审方系统的现状及问题分析", 《中国数字医学》, vol. 16, no. 3, 31 March 2021 (2021-03-31), pages 18 - 22 * |
| 陈喆等: "大型综合医院前置审方系统的设计与应用", 《中国临床药学杂志》, vol. 29, no. 3, 31 December 2020 (2020-12-31), pages 193 - 198 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108694657B (en) | Client identification apparatus, method and computer-readable storage medium | |
| WO2019192103A1 (en) | Concurrent access control method and apparatus, terminal device, and medium | |
| US11068964B2 (en) | Method and device for processing service request | |
| US20240195905A1 (en) | Methods and systems for automatic discovery of fraudulent calls using speaker recognition | |
| US8818940B2 (en) | Systems and methods for performing record actions in a multi-tenant database and application system | |
| US8214492B2 (en) | Method and system for adapting a session timeout period | |
| CN109614238B (en) | Target object identification method, device and system and readable storage medium | |
| WO2019091025A1 (en) | A user report processing method, device electronic device and medium | |
| US20070106669A1 (en) | Ensuring Timely Servicing of Desired Transactions in a Database Server | |
| WO2019041912A1 (en) | Method and apparatus for assigning claim settlement case, computer device, and storage medium | |
| CN109360325B (en) | Cash adding method and device for financial equipment, terminal and computer readable storage medium | |
| CN104980402B (en) | Method and device for identifying malicious operation | |
| WO2020062952A1 (en) | Room check-in method and apparatus, server and storage medium | |
| CN111583023A (en) | Service processing method, device and computer system | |
| CN115113997A (en) | Task scheduling method and device, electronic equipment and storage medium | |
| CN114244961A (en) | Robot intelligent outbound method and device, computer equipment and storage medium | |
| CN113764083A (en) | Prescription event auditing method, device and storage medium | |
| JP5216299B2 (en) | Order system | |
| CN107463371B (en) | Code management and control method and system | |
| US8918406B2 (en) | Intelligent analysis queue construction | |
| CN112286662B (en) | Task pushing method, device and equipment based on shared resources and storage medium | |
| CN110704501B (en) | User account correlation method and device | |
| CN106874336B (en) | Data matching method, data query method and device | |
| CN111724788B (en) | Service processing method, device and equipment | |
| CN114217875A (en) | Method, device and equipment for processing order and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |