CN109524082B - Medicine dispensing method, server and system - Google Patents
Medicine dispensing method, server and system Download PDFInfo
- Publication number
- CN109524082B CN109524082B CN201811266372.3A CN201811266372A CN109524082B CN 109524082 B CN109524082 B CN 109524082B CN 201811266372 A CN201811266372 A CN 201811266372A CN 109524082 B CN109524082 B CN 109524082B
- Authority
- CN
- China
- Prior art keywords
- prescription
- medicine
- target
- server
- acquisition request
- 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.)
- Active
Links
- 239000003814 drug Substances 0.000 title claims abstract description 293
- 229940079593 drug Drugs 0.000 title claims abstract description 98
- 238000000034 method Methods 0.000 title claims abstract description 49
- 238000005516 engineering process Methods 0.000 claims description 19
- 238000012015 optical character recognition Methods 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 7
- 230000003287 optical effect Effects 0.000 claims description 4
- 239000000825 pharmaceutical preparation Substances 0.000 claims description 2
- 229940127557 pharmaceutical product Drugs 0.000 claims description 2
- 238000004458 analytical method Methods 0.000 abstract description 2
- 238000004891 communication Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 5
- 206010020772 Hypertension Diseases 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000012377 drug delivery Methods 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000001514 detection method Methods 0.000 description 3
- 230000001815 facial effect Effects 0.000 description 3
- 238000003745 diagnosis Methods 0.000 description 2
- 201000010099 disease Diseases 0.000 description 2
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 description 2
- 230000003203 everyday effect Effects 0.000 description 2
- 230000001631 hypertensive effect Effects 0.000 description 2
- 230000000474 nursing effect Effects 0.000 description 2
- 208000024891 symptom Diseases 0.000 description 2
- 239000005541 ACE inhibitor Substances 0.000 description 1
- 102000008873 Angiotensin II receptor Human genes 0.000 description 1
- 108050000824 Angiotensin II receptor Proteins 0.000 description 1
- 229940127291 Calcium channel antagonist Drugs 0.000 description 1
- 206010019233 Headaches Diseases 0.000 description 1
- 206010033557 Palpitations Diseases 0.000 description 1
- 229940044094 angiotensin-converting-enzyme inhibitor Drugs 0.000 description 1
- 239000002220 antihypertensive agent Substances 0.000 description 1
- 229940127088 antihypertensive drug Drugs 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 239000000480 calcium channel blocker Substances 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 230000002354 daily effect Effects 0.000 description 1
- 239000002934 diuretic Substances 0.000 description 1
- 229940030606 diuretics Drugs 0.000 description 1
- 208000002173 dizziness Diseases 0.000 description 1
- 238000002651 drug therapy Methods 0.000 description 1
- 230000002526 effect on cardiovascular system Effects 0.000 description 1
- 206010016256 fatigue Diseases 0.000 description 1
- 231100000869 headache Toxicity 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 208000034783 hypoesthesia Diseases 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 210000004936 left thumb Anatomy 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 206010029446 nocturia Diseases 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000002195 synergetic effect Effects 0.000 description 1
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
- G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
- G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
Landscapes
- Health & Medical Sciences (AREA)
- Engineering & Computer Science (AREA)
- Chemical & Material Sciences (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Medicinal Chemistry (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 application discloses a medicine dispensing method, a server and a system, which relate to analysis and processing of medical information, wherein the method comprises the following steps: the method comprises the steps that a server receives a medicine acquisition request sent by a medicine acquisition request terminal, wherein the medicine acquisition request carries identity information of a target patient; the medicine acquisition request terminal is deployed at a medicine acquisition requester; the server judges whether a target prescription containing identity information of the target patient exists in a database storing a plurality of prescriptions; if a target prescription containing the identity information of the target patient exists in the database, the server judges whether a medicine exists in the target prescription; if a drug is present in the target prescription, the server distributes the drug to the drug acquisition requester. By adopting the application, the medicine dispensing accuracy and the medicine dispensing efficiency can be improved.
Description
Technical Field
The present application relates to the field of medical information technologies, and in particular, to a method, a server, and a system for drug delivery.
Background
The number of patients who are treated every day in each big hospital is increased sharply, so that the number of patients who are queued for taking medicines in the hospital pharmacy every day is not counted; in addition, in order to prevent some lawbreakers from taking medicine through the virtual fake medicine list and masquerading as patients in the medicine taking window, pharmacy staff needs to check the medicine list information repeatedly manually, on one hand, the workload of the pharmacy staff is increased, and on the other hand, the patients need to spend a large amount of time queuing for taking medicine.
Disclosure of Invention
The application provides a medicine dispensing method, a server and a system, which can improve the medicine dispensing accuracy and the medicine dispensing efficiency of patients.
In a first aspect, the present application provides a method of drug delivery involving analysis and processing of medical information, the method comprising:
The method comprises the steps that a server receives a medicine acquisition request sent by a medicine acquisition request terminal, wherein the medicine acquisition request carries identity information of a target patient; the medicine acquisition request terminal is deployed at a medicine acquisition requester;
the server judges whether a target prescription containing identity information of the target patient exists in a database storing a plurality of prescriptions;
if a target prescription containing the identity information of the target patient exists in the database, the server judges whether a medicine exists in the target prescription;
if a drug is present in the target prescription, the server distributes the drug to the drug acquisition requester.
With reference to the first aspect, in some possible embodiments,
The server judging whether a target prescription containing identity information of the target patient exists in a database storing a plurality of prescriptions, comprising:
the server performs character recognition on the prescriptions through an optical character recognition technology so as to recognize the identity information of the patient in each prescription in the prescriptions;
The server compares the identity information of the target patient with the identified identity information of the patient in each prescription to determine whether a target prescription containing the identity information of the target patient exists in the database storing the plurality of prescriptions.
With reference to the first aspect, in some possible embodiments,
After the server judges whether a target prescription containing the identity information of the target patient exists in the database, the method further comprises the following steps:
If the target prescription containing the identity information of the target patient does not exist in the database, the server sends a first indication to the medicine acquisition request terminal, wherein the first indication is used for indicating that the target prescription containing the identity information of the target patient does not exist.
With reference to the first aspect, in some possible embodiments,
If a target prescription containing the identity information of the target patient exists in the database, the server judges whether medicines exist in the target prescription or not, and the method comprises the following steps:
If a target prescription containing the identity information of the target patient exists in the database, the server carries out character recognition on the target prescription through an optical character recognition technology so as to judge whether medicines exist in the target prescription.
With reference to the first aspect, in some possible embodiments,
After the server judges whether the target prescription contains the medicine, the method further comprises the following steps:
And if the target prescription does not contain the medicine, the server sends a second instruction to the medicine acquisition request terminal, wherein the second instruction is used for indicating that no medicine in the target prescription is advisable.
With reference to the first aspect, in some possible embodiments,
Before the server receives the medicine acquisition request sent by the medicine acquisition request terminal, the method further comprises the following steps:
The server receives registration information of the medicine acquisition requester transmitted by the medicine acquisition request terminal.
In a second aspect, the present application provides a server comprising:
the receiving unit is used for receiving a medicine acquisition request sent by the medicine acquisition request terminal, wherein the medicine acquisition request carries the identity information of a target patient; the medicine acquisition request terminal is deployed at a medicine acquisition requester;
a first judgment unit configured to judge whether or not a target prescription containing identity information of the target patient exists in a database storing a plurality of prescriptions;
A second judging unit configured to judge whether a medicine exists in a target prescription including identity information of the target patient if the target prescription exists in the database;
And the sending unit is used for distributing the medicine to the medicine acquisition requester if the medicine exists in the target prescription.
With reference to the second aspect, in some possible embodiments,
A first judging unit for
Performing character recognition on the prescriptions through an optical character recognition technology to recognize the identity information of the patient in each prescription;
Comparing the identity information of the target patient with the identified identity information of the patient in each prescription to determine whether a target prescription containing the identity information of the target patient exists in the database storing the plurality of prescriptions.
A second judging unit for
If a target prescription containing the identity information of the target patient exists in the database, performing character recognition on the target prescription through an optical character recognition technology so as to judge whether medicines exist in the target prescription.
With reference to the second aspect, in some possible embodiments,
Further comprises: a transmitting unit configured to:
after the first judging unit judges whether a target prescription containing the identity information of the target patient exists in the database, if the target prescription containing the identity information of the target patient does not exist in the database, a first indication is sent to the medicine acquisition request terminal, wherein the first indication is used for indicating that the target prescription containing the identity information of the target patient does not exist.
The sending unit is further used for:
After the second judging unit judges whether the medicine exists in the target prescription, if the medicine does not exist in the target prescription, a second instruction is sent to the medicine acquisition request terminal, wherein the second instruction is used for indicating that no medicine is advisable in the target prescription.
With reference to the second aspect, in some possible embodiments,
Further comprises: a receiving unit configured to: and receiving registration information of the medicine acquisition requesting party sent by the medicine acquisition requesting terminal.
In a third aspect, the present application provides a server comprising: the device comprises a transceiver, a memory and a processor coupled with the memory, wherein the transceiver, the memory and the processor coupled with the memory are mutually connected, the transceiver is used for executing receiving or sending actions, the memory is used for storing the implementation code of the medicine dispensing method, and the processor is used for calling the implementation code stored in the memory, namely executing the medicine dispensing method of the first aspect.
In a fourth aspect, the present application provides a pharmaceutical dispensing system comprising: the system comprises a server, a medicine acquisition request terminal and a prescription providing terminal; the server is used for distributing medicines according to the medicine distribution method of the first aspect, the medicine acquisition request terminal is used for sending medicine acquisition requests to the server, and the prescription providing terminal is used for sending prescriptions to the server.
In a fifth aspect, the present application provides a computer readable storage medium having instructions stored thereon which, when executed by a processor, cause the processor to perform the method of drug dispensing provided by the first aspect and any of its various possible implementations.
In a sixth aspect, the present application provides a computer program product which, when executed by a processor, causes the processor to perform the method of drug dispensing provided by the first aspect and any of its various possible implementations.
The application provides a medicine dispensing method, a server and a system. The server receives a medicine acquisition request sent by a medicine acquisition request terminal, wherein the medicine acquisition request carries identity information of a target patient; the medicine acquisition request terminal is deployed at a medicine acquisition request party; the server judges whether a target prescription containing identity information of a target patient exists in a database storing a plurality of prescriptions; if the target prescription containing the identity information of the target patient exists in the database, the server judges whether the medicine exists in the target prescription; if a drug is present in the target prescription, the server dispenses the drug to the drug acquisition requester. By adopting the application, the medicine dispensing accuracy and the medicine dispensing efficiency of the patient can be improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a drug dispensing system provided by the present application;
FIG. 2 is a schematic flow chart of a method of dispensing a pharmaceutical product provided by the present application;
FIG. 3 is a schematic block diagram of a server provided by the present application;
fig. 4 is a schematic block diagram of another server provided by the present application.
Detailed Description
The following description of the embodiments of the present application will be made more apparent and fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the application are shown. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
It should be understood that the terms "comprises" and "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".
In particular implementations, the terminals described in this disclosure include, but are not limited to, other portable devices such as mobile phones, laptop computers, or tablet computers having a touch-sensitive surface (e.g., a touch screen display and/or a touch pad). It should also be appreciated that in some embodiments, the device is not a portable communication device, but a desktop computer having a touch-sensitive surface (e.g., a touch screen display and/or a touch pad).
In the following discussion, a terminal including a display and a touch sensitive surface is described. However, it should be understood that the terminal may include one or more other physical user interface devices such as a physical keyboard, mouse, and/or joystick.
The terminal supports various applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, website creation applications, disk burning applications, spreadsheet applications, gaming applications, telephony applications, video conferencing applications, email applications, instant messaging applications, workout support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music player applications, and/or digital video player applications.
Various applications that may be executed on the terminal may use at least one common physical user interface device such as a touch sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the terminal may be adjusted and/or changed between applications and/or within the corresponding applications. In this way, the common physical architecture (e.g., touch-sensitive surface) of the terminal may support various applications with user interfaces that are intuitive and transparent to the user.
Referring to fig. 1, which is a schematic diagram of a drug dispensing system according to the present application, as shown in fig. 1, the drug dispensing system may include: server, medicine acquisition request terminal and prescription providing terminal.
The drug acquisition request terminal and the prescription providing terminal may be terminals in a drug dispensing system, and the terminals may refer to access terminals, user Equipment (UE), subscriber units, subscriber stations, mobile stations, remote terminals, mobile terminals, user terminals, wireless communication devices, user agents, or user apparatuses. An access terminal may be a cellular telephone, a cordless telephone, a conference initiation protocol telephone, a wireless local loop station, a personal digital assistant, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a wearable device, or a terminal device in a future-evolving public land mobile network.
In a drug dispensing system, may include: a medicine acquisition requester, a prescription provider and a medicine dispenser. In the embodiment of the application, taking the example that a medicine acquisition request terminal is deployed at a medicine acquisition request party, a prescription providing terminal is deployed at a prescription provider, and a server is deployed at a medicine distribution party.
In the embodiment of the application, a doctor of a medical institution can log in a prescription providing client to input registration information into a prescription providing terminal arranged on a prescription provider (such as the medical institution), the prescription providing terminal sends the registration information to a server, and the server further obtains a private key which is set by the doctor of the medical institution and used for logging in the prescription providing client and stores the private key.
The drug acquisition request party staff (such as pharmacy staff) can log in the drug acquisition request client to input registration information into a drug acquisition request terminal deployed at the drug request party (such as pharmacy or pharmacy of a medical institution), and the drug acquisition request terminal sends the registration information to a server deployed at the drug dispenser, so that the server obtains a private key for logging in the drug acquisition request client and stores the private key.
Furthermore, after different users are registered in the server through the medicine acquisition request terminal or the prescription providing terminal respectively, a worker of the medicine acquisition request party can log in the medicine acquisition request client to input a medicine acquisition request to the medicine acquisition request terminal; a doctor of a multi-institute medical facility can input prescriptions of patients to prescription providing terminals disposed at prescription providers, respectively, through prescription providing clients.
It should be noted that a medical facility may include: hospitals, women and child care homes, community health service centers, rural (town) care homes, nursing homes, outpatient departments (such as the department of Chinese medicine outpatient, the department of Chinese and Western medicine combined with the outpatient department), village care rooms, emergency treatment centers, clinical examination centers, dedicated disease control homes or nursing homes, and the like.
The drug retrieval requester may be a pharmacy, pharmacy of a medical facility, or the like.
It should be noted that the client may include: locally running applications, functions running on a Web browser (also known as Web apps), applets embedded in email, applets embedded in client software for instant messaging (e.g., weChat (WeChat)), and functions embedded in other applications (e.g., weChat) (e.g., weChat public numbers), etc. For clients, a corresponding server program needs to be run on the server to provide corresponding services, such as database services, data calculation, decision execution, and the like.
In the embodiment of the application, the server can also be called a background server, a component server, a medicine distribution server and the like, and the server can be in communication connection with a medicine acquisition request terminal capable of sending a medicine acquisition request and a prescription providing terminal for sending a prescription through the internet and can respond to the received medicine acquisition request.
It should be noted that, the server receives the medicine acquisition request sent by the medicine acquisition request terminal, and the medicine acquisition request carries the identity information of the target patient; the medicine acquisition request terminal is deployed at a medicine acquisition request party; the server judges whether a target prescription containing identity information of a target patient exists in a database storing a plurality of prescriptions; if the target prescription containing the identity information of the target patient exists in the database, the server judges whether the medicine exists in the target prescription; if a drug is present in the target prescription, the server dispenses the drug to the drug acquisition requester. By adopting the embodiment of the application, the medicine dispensing accuracy and the medicine dispensing efficiency of patients can be improved.
Referring to fig. 2, fig. 2 is a schematic flow chart of a drug dispensing method according to an embodiment of the present application.
As shown in fig. 2, the following describes in detail a drug dispensing method provided by a drug dispensing system, which may at least include the following steps:
s201, the server receives a medicine acquisition request sent by the medicine acquisition request terminal.
In the embodiment of the application, the medicine acquisition request carries the identity information of the target patient; the medicine acquisition request terminal is deployed at a medicine acquisition request party;
the server may store the drug retrieval request in two ways, including but not limited to.
The first way is: the drug retrieval request is stored in an internal memory of the server.
The second way is: and storing the medicine acquisition request in a cloud database connected with the server.
The drug acquisition request carries identity information of the target patient, wherein the identity information of the target patient may include, but is not limited to: identification card number of target patient (such as 430903 xxxxxxxx 3915), social security card number, fingerprint feature (such as left thumb fingerprint feature), facial feature or iris feature (such as left eye iris feature), etc.
It should be noted that the drug acquisition request terminal may acquire the identity information of the target patient in various manners.
Specifically, the drug acquisition request terminal can identify the second-generation identification card or the social security card of the target patient through a near field Communication (NEAR FIELD Communication) technology so as to acquire the identification information of the target patient.
The medicine acquisition request terminal can also scan the second-generation identity card of the target patient through the information identification interface so as to acquire the identity information of the patient.
The medicine acquisition request terminal can scan the target patient through the biological sign recognition interface to recognize sign information (facial features, iris features or fingerprint features of the patient, etc.) of the target patient
It should be noted that, before the server receives the medicine acquisition request sent by the medicine acquisition request terminal, the method further includes the following steps:
Step 1: the server receives registration information (including a registration account number and a login password for logging in the registration account number) of the medicine acquisition request party sent by the medicine acquisition request terminal, wherein the registration information of the medicine acquisition request party is input to the medicine acquisition request terminal by staff of the medicine acquisition request party (such as pharmacy staff of a medical institution and pharmacy staff).
In addition, the server may also receive registration information of the prescription provider transmitted from the prescription providing terminal, wherein the registration information of the prescription provider is input to the prescription providing terminal by a prescription provider staff member (e.g., a staff member of a medical institution).
Step 2: after different users (drug acquisition request staff or prescription provider staff) are respectively registered in the server through the drug acquisition request terminal or the prescription providing terminal, the server can respectively receive the drug acquisition request carrying the identity information of the target patient and the prescriptions of the patients sent by the prescription providing terminal. The medicine acquisition request carrying the identity information of the target patient is input to the medicine acquisition request terminal by a medicine acquisition requester staff based on the medicine acquisition client. The prescription of the plurality of patients is a prescription input to the prescription providing terminal by a prescription provider staff based on the prescription providing client.
S202, the server judges whether a target prescription containing identity information of a target patient exists in a database storing a plurality of prescriptions.
In an embodiment of the present application, the database includes prescriptions for a plurality of patients. Wherein the patient's prescription includes, but is not limited to: patient identity information (such as patient ID card number, social security card number), clinical manifestation symptoms, diagnosis results, treatment means or medicines, etc.
Taking the prescription of a hypertensive patient as an example, the prescription of a hypertensive patient may include, but is not limited to, the following: social security card number, name, age, sex, contact means and clinical manifestation symptoms of hypertension patients are: dizziness, headache, fatigue, palpitation, inattention, numbness of limbs, nocturia, and the like, and the diagnosis results are as follows: patients with slow-going hypertension, the treatment means are as follows: antihypertensive drug therapy (drug which can control twenty-four hours of disease to reach standard after once daily administration) improves living behavior and synergistic control of multiple cardiovascular risk factors. The medicine comprises: diuretics, calcium channel blockers, angiotensin converting enzyme inhibitors, angiotensin II receptor blockers, and the like.
The server determines whether a target prescription containing identity information of a target patient exists in a database storing a plurality of prescriptions, and specifically includes, but is not limited to, the following steps:
Step 1: the plurality of prescriptions in the database are respectively subjected to character recognition by an optical character recognition technology (Optical Character Recognition, OCR) so as to recognize the identity information of the patient in each prescription in the plurality of prescriptions.
Step 2: and comparing the identity information of the target patient with the identity information of the patient in each identified prescription to judge whether a target prescription containing the identity information of the target patient exists in a database storing a plurality of prescriptions.
Taking the identity information of the patient as the identity card number of the patient as an example, the server can respectively perform character recognition on the prescriptions in the database through an optical character recognition technology so as to recognize the identity card number of the patient in each prescription in the prescriptions.
Comparing the identification card number of the target patient with the identification card number of the patient in each identified prescription to judge whether a target prescription containing the identification card number of the target patient exists in a database storing a plurality of prescriptions.
Taking the identity information of the patient as the social security card number of the patient as an example, the server can respectively perform text recognition on the prescriptions in the database through an optical text recognition technology so as to recognize the social security card number of the patient in each prescription in the prescriptions.
And comparing the social security card number of the target patient with the social security card number of the patient in each prescription so as to judge whether a target prescription containing the social security card number of the target patient exists in a database storing a plurality of prescriptions.
It should be noted that after the server determines whether there is a target prescription containing the identity information of the target patient in the database, the method further includes the following steps:
If the target prescription containing the identity information of the target patient does not exist in the database, the server sends a first indication to the medicine acquisition request terminal, wherein the first indication is used for indicating that the target prescription containing the identity information of the target patient does not exist. Furthermore, after the medicine acquisition request party receives the first instruction through the medicine acquisition request terminal, the medicine acquisition request party can determine that any medicine is not required to be distributed, and the accuracy of medicine distribution is improved.
S203, if a prescription containing the identity information of the target patient exists in the database, the server judges whether a medicine exists in the target prescription.
Specifically, if a target prescription containing the identity information of the target patient exists in the database, the server performs text recognition on the target prescription through an optical character recognition technology to judge whether a medicine exists in the target prescription.
It should be noted that, after the server determines whether the target prescription contains the medicine, the method further includes the following steps:
If the target prescription does not contain the medicine, the server sends a second instruction to the medicine acquisition request terminal, wherein the second instruction is used for indicating that the target prescription does not contain the medicine. Furthermore, after the medicine acquisition request party receives the second instruction through the medicine acquisition request terminal, the medicine acquisition request party can determine that any medicine is not required to be distributed, and the accuracy of medicine distribution is improved.
S204, if the target prescription contains the medicine, the server distributes the medicine to the medicine acquisition requesting party.
Specifically, if the server determines that the target prescription contains a drug, the server may send a drug delivery instruction to an application terminal (e.g., a robot), where the drug delivery instruction is used to notify the application terminal to dispense the drug listed in the target prescription to the drug requester.
The server distributes the drug to the drug acquisition requester, which may include, but is not limited to, the following three ways:
The first way is: the server directly distributes the drug to the drug requester.
The second way is: the server sends a third instruction to the first terminal of the drug taker, the third instruction being for notifying the drug taker to dispense the drug to the drug requester.
Third mode: the server sends a fourth indication to the application terminal (e.g., the robot) for informing the application terminal to dispense the drug to the drug requester.
It should be noted that, the server receives the medicine acquisition request sent by the medicine acquisition request terminal, and the medicine acquisition request carries the identity information of the target patient; the medicine acquisition request terminal is deployed at a medicine acquisition request party; the server judges whether a target prescription containing identity information of a target patient exists in a database storing a plurality of prescriptions; if the target prescription containing the identity information of the target patient exists in the database, the server judges whether the medicine exists in the target prescription; if a drug is present in the target prescription, the server dispenses the drug to the drug acquisition requester. By adopting the embodiment of the application, the medicine dispensing accuracy and the medicine dispensing efficiency of patients can be improved.
Referring to fig. 3, a server provided by the present application may be the server in fig. 2. As shown in fig. 3, the server 30 includes: a receiving unit 301, a first judging unit 302, a second judging unit 303, and a distributing unit 304. Wherein:
A receiving unit 301, configured to receive a drug acquisition request sent by a drug acquisition request terminal, where the drug acquisition request carries identity information of a target patient; the medicine acquisition request terminal is deployed at a medicine acquisition request party;
A first judging unit 302 for judging whether or not there is a target prescription containing the identity information of the target patient in a database storing a plurality of prescriptions.
A second judging unit 303 for judging whether or not a medicine is present in the target prescription if the target prescription containing the identity information of the target patient is present in the database.
A dispensing unit 304 for dispensing the medicine to the medicine acquisition requester if the medicine exists in the target prescription.
With reference to the second aspect, in some possible embodiments,
A first judging unit 302, specifically for
And respectively carrying out character recognition on the prescriptions through an optical character recognition technology so as to recognize the identity information of the patient in each prescription in the prescriptions.
Comparing the identity information of the target patient with the identity information of the patient in each identified prescription to judge whether a target prescription containing the identity information of the target patient exists in the database storing a plurality of prescriptions.
A second judging unit 303, specifically for
If the target prescription containing the identity information of the target patient exists in the database, the target prescription is subjected to character recognition through an optical character recognition technology so as to judge whether the medicine exists in the target prescription.
The server 30 includes: the receiving unit 301, the first judging unit 302, the second judging unit 303, and the distributing unit 304 further include: and a transmitting unit.
A transmitting unit configured to:
After the first judging unit 302 judges whether or not there is a target prescription containing the identity information of the target patient in the database, if there is no target prescription containing the identity information of the target patient in the database, a first instruction for indicating that the target prescription containing the identity information of the target patient is not present is sent to the medicine acquisition request terminal.
The sending unit is further used for:
After the second judging unit 303 judges whether or not there is a medicine in the target prescription, if there is no medicine in the target prescription, a second instruction for indicating that no medicine in the target prescription is advisable is sent to the medicine acquisition request terminal.
It should be understood that server 30 is merely one example provided for embodiments of the present application, and that server 30 may have more or fewer components than shown, may combine two or more components, or may have different configuration implementations of the components.
It will be appreciated that, regarding the specific implementation of the functional blocks included in the server 30 of fig. 3, reference may be made to the foregoing method embodiment described in fig. 2, and no further description is given here.
In summary, the receiving unit 301 receives the medicine acquisition request sent by the medicine acquisition request terminal, where the medicine acquisition request carries the identity information of the target patient; the medicine acquisition request terminal is deployed at a medicine acquisition request party; the first judgment unit 302 judges whether or not there is a target prescription containing the identity information of the target patient in a database storing a plurality of prescriptions; if there is a target prescription containing the identity information of the target patient in the database, the second judging unit 303 judges whether or not there is a medicine in the target prescription; if there is a drug in the target prescription, the dispensing unit 304 dispenses the drug to the drug acquisition requester. By adopting the embodiment of the application, the medicine dispensing accuracy and the medicine dispensing efficiency of patients can be improved.
The present application provides another server, which may be the server in fig. 2. As shown in fig. 4, the server 40 may include: a processor 401, a memory 402 (one or more computer-readable storage media), and a transceiver 403. These components may communicate over one or more communication buses 404.
The processor 401 may be a central processor (Central Processing Unit, CPU), a network processor (Network Processor, NP) or a combination of CPU and NP.
The processor 401 may further include a hardware chip. The hardware chip may be an Application-specific integrated Circuit (ASIC), a programmable logic device (Programmable Logic Device, PLD), or a combination thereof. The PLD may be a complex programmable Logic device (Complex Programmable Logic Device, CPLD), a Field-programmable gate array (Field-programmable GATE ARRAY, FPGA), general-purpose array Logic (GENERIC ARRAY Logic, GAL), or any combination thereof.
As can be appreciated, the processor 401 may be configured to determine whether a target prescription containing identity information of a target patient exists in a database storing a plurality of prescriptions; if a target prescription containing the identity information of the target patient exists in the database, judging whether a medicine exists in the target prescription; if a drug is present in the target prescription, the drug is dispensed to the drug acquisition requester.
The processor 401 is specifically configured to: and respectively carrying out character recognition on the prescriptions through an optical character recognition technology so as to recognize the identity information of the patient in each prescription in the prescriptions.
And comparing the identity information of the target patient with the identity information of the patient in each identified prescription to judge whether a target prescription containing the identity information of the target patient exists in a database storing a plurality of prescriptions.
The processor 401 is specifically further configured to:
If the target prescription containing the identity information of the target patient exists in the database, the target prescription is subjected to character recognition through an optical character recognition technology so as to judge whether the medicine exists in the target prescription.
Memory 402 is coupled to processor 401 and may be used to store various software programs and/or sets of instructions. In particular implementations, memory 402 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 402 may store an operating system (hereinafter referred to as a system), such as ANDROID, IOS, WINDOWS, or an embedded operating system, such as LINUX. Memory 402 may also store network communication programs that may be used to communicate with one or more additional devices, one or more terminal devices, and one or more network devices. The memory 402 may also store a user interface program that can vividly display the content image of the application program through a graphical operation interface, and receive control operations of the application program by a user through input controls such as menus, dialog boxes, buttons, and the like.
As can be appreciated, the memory 402 may also be configured to store a medicine acquisition request sent by the medicine acquisition request terminal and a prescription issued by a doctor of the medical institution sent by the prescription providing terminal, where the medicine acquisition request carries identity information of the target patient; the identity information of the target patient may include, but is not limited to: the drug acquisition request terminal is deployed at a drug acquisition requester, such as an identification card number, a social security card number, fingerprint characteristics, facial characteristics or iris characteristics of a target patient.
The transceiver 403 may also be used to receive a drug acquisition request sent by the drug acquisition request terminal and a prescription issued by a doctor of the medical institution sent by the prescription providing terminal.
The transceiver 403 may be further configured to send a first indication to the drug acquisition request terminal after the processor 401 determines whether the target prescription including the identity information of the target patient is present in the database, if the target prescription including the identity information of the target patient is not present in the database, the first indication being used to indicate that the target prescription including the identity information of the target patient is not present.
Transceiver 403 may be further configured to send a second indication to the medication intake request terminal after processor 401 determines whether there is a medication in the target prescription, if there is no medication in the target prescription, the second indication indicating that no medication is advisable in the target prescription.
The transceiver 403 may be further configured to receive registration information of a medicine acquisition requester transmitted by the medicine acquisition request terminal before receiving the medicine acquisition request transmitted by the medicine acquisition request terminal.
It should be understood that server 40 is merely one example provided for embodiments of the present application, and that server 40 may have more or fewer components than shown, may combine two or more components, or may have different configuration implementations of the components.
It will be appreciated that, regarding the specific implementation of the functional blocks included in the server 40 of fig. 4, reference may be made to the foregoing method embodiment described in fig. 2, and a detailed description is omitted here.
In summary, the transceiver 403 receives the medicine acquisition request sent by the medicine acquisition request terminal, where the medicine acquisition request carries the identity information of the target patient; the medicine acquisition request terminal is deployed at a medicine acquisition request party; the processor 401 determines whether there is a target prescription containing identity information of a target patient in a database storing a plurality of prescriptions; if there is a target prescription in the database that contains identity information of the target patient, the second processor 401 determines whether there is a drug in the target prescription; if a drug is present in the target prescription, the processor 401 dispenses the drug to the drug acquisition requester. By adopting the embodiment of the application, the medicine dispensing accuracy and the medicine dispensing efficiency of patients can be improved.
The present application provides a computer readable storage medium storing a computer program which is implemented when executed by a processor.
The computer readable storage medium may be an internal storage unit of the terminal according to any of the foregoing embodiments, for example, a hard disk or a memory of the terminal. The computer readable storage medium may also be an external storage device of the terminal, such as a plug-in hard disk, a smart memory card (SMART MEDIA CARD, SMC), a Secure Digital (SD) card, a flash memory card (FLASH CARD), etc. that are provided on the terminal. Further, the computer readable storage medium may also include both an internal storage unit of the terminal and an external storage device. The computer-readable storage medium is used to store a computer program and other programs and data required by the terminal. The computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.
The present application also provides a computer program product comprising a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform part or all of the steps of any one of the methods described in the method embodiments above. The computer program product may be a software installation package, the computer comprising the electronic device.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein may be embodied in electronic hardware, in computer software, or in a combination of the two, and that the elements and steps of the examples have been generally described in terms of function in the foregoing description to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working procedures of the terminal and the unit described above may refer to the corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In several embodiments provided by the present application, it should be understood that the disclosed terminal and method may be implemented in other manners. For example, the compositions and steps of the examples are described. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The above-described terminal embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and there may be other manners of division in actual implementation, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, terminals or units, or may be an electrical, mechanical or other form of connection.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment of the present application.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application is essentially or a part contributing to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
While the application has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the application. Therefore, the protection scope of the application is subject to the protection scope of the claims.
Claims (9)
1. A method of dispensing a pharmaceutical product, comprising:
The method comprises the steps that a server receives registration information of a doctor of a medical institution sent by a prescription providing terminal, obtains a private key used for logging in the prescription providing terminal and set by the doctor of the medical institution, and stores the private key used for logging in the prescription providing terminal;
the server receives a medicine acquisition request sent by a medicine acquisition request terminal, wherein the medicine acquisition request carries identity information of a target patient; the medicine acquisition request terminal is deployed at a medicine acquisition requester;
the server registers a prescription providing terminal arranged in each medical institution through private keys set by doctors of a plurality of medical institutions and used for registering the prescription providing terminal, receives prescriptions of patients input by the doctors of each medical institution through the prescription providing terminal of each medical institution and stores the prescriptions of the patients input by the doctors of each medical institution into a database;
the server respectively carries out character recognition on the prescriptions stored in the database through an optical character recognition technology so as to recognize the identity information of the patient in each prescription in the prescriptions;
The server compares the identity information of the target patient with the identified identity information of the patient in each prescription, and judges whether a target prescription containing the identity information of the target patient exists in the database storing the prescriptions;
if a target prescription containing the identity information of the target patient exists in the database, the server identifies the prescription through an optical character identification technology to judge whether medicines exist in the target prescription;
if a drug is present in the target prescription, the server distributes the drug to the drug acquisition requester.
2. The method of claim 1, wherein,
After the server judges whether a target prescription containing the identity information of the target patient exists in the database, the method further comprises the following steps:
If the target prescription containing the identity information of the target patient does not exist in the database, the server sends a first indication to the medicine acquisition request terminal, wherein the first indication is used for indicating that the target prescription containing the identity information of the target patient does not exist.
3. The method of claim 1, wherein,
If a target prescription containing the identity information of the target patient exists in the database, the server judges whether medicines exist in the target prescription or not, and the method comprises the following steps:
If a target prescription containing the identity information of the target patient exists in the database, the server carries out character recognition on the target prescription through an optical character recognition technology so as to judge whether medicines exist in the target prescription.
4. The method of claim 1, wherein,
After the server judges whether the target prescription contains the medicine, the method further comprises the following steps:
And if the target prescription does not contain the medicine, the server sends a second instruction to the medicine acquisition request terminal, wherein the second instruction is used for indicating that no medicine in the target prescription is advisable.
5. The method of claim 1, wherein,
Before the server receives the medicine acquisition request sent by the medicine acquisition request terminal, the method further comprises the following steps:
The server receives registration information of the medicine acquisition requester transmitted by the medicine acquisition request terminal.
6. A server, comprising:
the receiving unit is used for receiving registration information of a doctor of a medical institution sent by the prescription providing terminal, obtaining a private key used for logging in the prescription providing terminal and set by the doctor of the medical institution and storing the private key used for logging in the prescription providing terminal;
The receiving unit is further used for receiving a medicine acquisition request sent by the medicine acquisition request terminal, wherein the medicine acquisition request carries identity information of a target patient; the medicine acquisition request terminal is deployed at a medicine acquisition requester;
A first judgment unit configured to register, via private keys set by doctors of a plurality of medical institutions, prescription providing terminals disposed in respective medical institutions, receive prescriptions of patients input by the doctors of the respective medical institutions via the prescription providing terminals of the respective medical institutions, and store the prescriptions of the patients input by the doctors of the respective medical institutions into a database;
The first judging unit is further configured to perform text recognition on the multiple prescriptions stored in the database through an optical text recognition technology, so as to recognize identity information of a patient in each of the multiple prescriptions, and compare the identity information of the target patient with the recognized identity information of the patient in each prescription, so as to judge whether a target prescription containing the identity information of the target patient exists in the database storing the multiple prescriptions;
a second judging unit for, if a target prescription containing the identity information of the target patient exists in the database, identifying the prescription by an optical character recognition technology to judge whether a medicine exists in the target prescription;
And the dispensing unit is used for dispensing the medicine to the medicine acquisition requester if the medicine exists in the target prescription.
7. A server, comprising: a transceiver, a memory and a processor coupled to the memory, the transceiver, the memory and the processor coupled to the memory being interconnected, wherein the transceiver is configured to perform a receiving or transmitting action, the memory is configured to store implementation code of a drug dispensing method, and the processor is configured to invoke the implementation code stored in the memory, i.e. to perform the drug dispensing method of any of claims 1-5.
8. A computer readable storage medium, characterized in that the computer storage medium stores a computer program comprising program instructions which, when executed by a processor, cause the processor to perform the pharmaceutical dispensing method according to any of claims 1-5.
9. A drug dispensing system, comprising: the system comprises a server, a medicine acquisition request terminal and a prescription providing terminal; wherein the server is configured to perform the drug dispensing method of any one of claims 1 to 5, the drug acquisition request terminal is configured to send a drug acquisition request to the server, and the prescription providing terminal is configured to send a prescription to the server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811266372.3A CN109524082B (en) | 2018-10-27 | 2018-10-27 | Medicine dispensing method, server and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811266372.3A CN109524082B (en) | 2018-10-27 | 2018-10-27 | Medicine dispensing method, server and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109524082A CN109524082A (en) | 2019-03-26 |
| CN109524082B true CN109524082B (en) | 2024-07-09 |
Family
ID=65772467
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811266372.3A Active CN109524082B (en) | 2018-10-27 | 2018-10-27 | Medicine dispensing method, server and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109524082B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101923606A (en) * | 2010-08-20 | 2010-12-22 | 无锡北邮感知技术产业研究院有限公司 | System and method for drug placement, distribution and source tracing based on digital tags |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7426475B1 (en) * | 2000-03-21 | 2008-09-16 | Mahesh Tangellapally | Secure electronic healthcare information management process and system |
| US7426476B2 (en) * | 2000-03-27 | 2008-09-16 | Whittier Group Inc. | System and method for automated prescription management |
| KR100338321B1 (en) * | 2000-04-17 | 2002-05-27 | 김영태 | A patient oriented medical prescription transmitting system and medical prescription transmitting method |
| EP2811273A1 (en) * | 2007-04-03 | 2014-12-10 | Mutoh Industries Ltd. | Spectrophotometer and method |
| CN101650225B (en) * | 2009-09-16 | 2011-08-17 | 中国科学院安徽光学精密机械研究所 | Absolute spectral radiance luminance responsivity calibrating system utilizing wide tunable laser |
| CN101881662B (en) * | 2010-06-30 | 2011-12-14 | 中国科学院安徽光学精密机械研究所 | Full-automatic visible short infrared subdivided spectral irradiance meter |
| WO2018060758A1 (en) * | 2016-09-30 | 2018-04-05 | Lubezky Americus Arie | Method for controlling medical prescriptions, issuing medical prescriptions, validating the identity and authority of involved parties and ensuring the correct filling of prescriptions |
| CN106872030B (en) * | 2017-03-16 | 2018-07-06 | 中国科学院合肥物质科学研究院 | Visible-short-wave infrared ultraphotic spectrum irradiance instrument available for long-term automatic Observation |
-
2018
- 2018-10-27 CN CN201811266372.3A patent/CN109524082B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101923606A (en) * | 2010-08-20 | 2010-12-22 | 无锡北邮感知技术产业研究院有限公司 | System and method for drug placement, distribution and source tracing based on digital tags |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109524082A (en) | 2019-03-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109559792B (en) | Medicine dispensing method, block chain link point equipment and system | |
| CN109509527B (en) | Medicine dispensing method, block chain link point equipment and system | |
| US20220172806A1 (en) | Electronic health record system | |
| US12086227B2 (en) | Verification system | |
| JP7519670B2 (en) | Doctor and user matching system | |
| WO2020082808A1 (en) | Pharmacy selection method, server, computer readable storage medium, and system | |
| CN109509104B (en) | Identity authentication method, device, server and medium based on face recognition | |
| CN106991292A (en) | A kind of health guidance method and system | |
| CN109522743B (en) | Medical insurance bill auditing method, block chain link point equipment and system | |
| KR20180041925A (en) | System and method for managing taking medicine | |
| CN109522817B (en) | Patient hospitalization auditing method, block chain link point equipment and system | |
| US20200185071A1 (en) | Facilitating sexually transmitted infection services | |
| CN111324468B (en) | Message transmission method, device, system and computing equipment | |
| CN109509532B (en) | Medicine dispensing method, server and system | |
| CN109545314A (en) | A kind of risk control method of prescriptions, server and system | |
| CN109545337A (en) | A kind of processing method of medical resource, server and system | |
| CN109524082B (en) | Medicine dispensing method, server and system | |
| CN109584085B (en) | Medical insurance bill auditing method, block chain link point equipment and system | |
| US20160070924A1 (en) | Virtual-Account-Initiated Communication of Protected Information | |
| CN109509105B (en) | Medicine taking certificate auditing method, server and system | |
| CN104994099A (en) | Data processing method, equipment and system based on network hospital | |
| CN109542991A (en) | A kind of pharmacy selection method, server and system | |
| Aldughayfiq et al. | A system to lower the risk of dispensing medication errors at pharmacies using NFC | |
| US20240013879A1 (en) | Medical system and computer program | |
| KR102636838B1 (en) | DTx PLATFORM SYSTEM AND METHOD SUPPORTING CONTINUOUS PRESCRIPTION AND MULTI-HOSPITAL CONTINUOUS PRESCRIPTION |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |