CN111145857A - Method for managing doctor advice execution of patient leaving hospital - Google Patents
Method for managing doctor advice execution of patient leaving hospital Download PDFInfo
- Publication number
- CN111145857A CN111145857A CN201911365846.4A CN201911365846A CN111145857A CN 111145857 A CN111145857 A CN 111145857A CN 201911365846 A CN201911365846 A CN 201911365846A CN 111145857 A CN111145857 A CN 111145857A
- Authority
- CN
- China
- Prior art keywords
- patient
- hospital
- doctor
- order
- client
- 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
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
- G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
-
- 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)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Chemical & Material Sciences (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Medicinal Chemistry (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The invention relates to a method for managing hospital leaving patient advice execution, which is characterized in that a doctor client uploads a hospital leaving advice to a hospital leaving patient advice management server, the patient client can download the advice from the hospital leaving patient advice management server after passing authentication and execute the advice, the hospital leaving patient advice management server collects and monitors the condition that a patient completes the advice, the doctor is automatically notified after abnormality is found, and the hospital leaving patient advice management server automatically adjusts the advice after the doctor issues an instruction. The method is convenient for the patient to obtain and complete the hospital leaving advice, and the advice can be adjusted in time according to the abnormal condition of the patient.
Description
Technical Field
The invention belongs to the field of medical informatization, and particularly relates to a method for managing medical advice execution of a patient in a hospital.
Background
The medical orders are medical orders given by physicians during medical activities, and patients need to perform prescribed actions in the aspects of diet, medication, examination, and the like according to the medical orders. The medical orders are classified into long-term medical orders and temporary medical orders according to timeliness of the medical orders, and can be classified into hospital medical orders and hospital discharge medical orders (i.e., hospital discharge medical orders) according to whether the patient is in a hospital stay or after the patient is discharged. The invention mainly provides a management system and an implementation method aiming at long-term medical advice of a patient in a hospital.
The leaving medical advice is usually the continuation of the in-hospital medical advice, and for chronic diseases or special diseases which need long-term treatment, paper medical advice similar to an instruction manual which embodies the treatment experience of the disease is usually provided, the medical advice defines the action actions of taking medicine, checking, and the like of the patient in the whole treatment process, and the key elements are time and action, namely, the plan for executing the medical actions of taking medicine, checking, and the like is made according to the time.
The patient is assisted and supervised by a medical professional such as a nurse during hospitalization, and the related orders are completely executed by the patient (including a guardian) by self-help after discharge. For the taking behavior, the patient takes or injects a prescribed dose of a single or multiple prescribed drugs at a prescribed time according to the order; for the examination, the patient performs corresponding examination or examination at the institution meeting the conditions at the designated time according to the medical advice to obtain corresponding physical indexes, judges the reasonability of the current medication according to the physical indexes, adjusts the dosage and frequency if necessary, and even suspends or resumes the medication.
However, it is generally difficult for a patient to remember the order of the hospital leaving, and therefore, it is common in the prior art to provide a paper order to the patient leaving the hospital. However, the paper medical advice cannot deal with the sudden abnormal situation of the patient after leaving the hospital, and various problems are easy to occur in the paper medical advice.
Disclosure of Invention
In order to solve the problems in the prior art, the invention provides a method for managing the execution of medical orders of patients leaving hospital.
The technical scheme adopted by the invention is as follows:
a method for managing the execution of orders of hospital patients comprises the following steps:
step 100: when the patient is out of the hospital, the patient uses his patient client to establish near field communication with the doctor client;
step 200: the patient client and the doctor client are connected through near field communication, and a medical order identifier ID1 is negotiated;
step 300: a doctor sets a corresponding hospital leaving advice of the patient on a doctor client, generates an advice data packet, and sends the advice data packet to a hospital leaving patient advice management server; wherein the order data package comprises the order identifier ID1, a doctor identifier ID2, a patient identifier ID3, and the hospital discharge order;
step 400: after receiving the order data packet, the hospital leaving patient order management server stores the order identifier ID1, the doctor identifier ID2, the patient identifier ID3 and the hospital leaving order in a database in an associated manner;
step 500: after a patient logs in at a patient client, the patient client generates an advice request message and sends the advice request message to the hospital-leaving patient advice management server; the order request message includes the doctor identifier ID2 and the patient identifier ID 3;
step 600: after receiving the order request message, the order management server of the patient leaving the hospital queries a database according to the order request message to obtain a corresponding order identifier ID 1;
step 700: the hospital patient medical advice management server randomly generates an authentication code C, sends the authentication code C to the patient client, encrypts the authentication code C by using the medical advice identifier ID1 as a secret key to obtain an encryption Result, and sends the encryption Result to the hospital patient medical advice management server;
step 800: the hospital-leaving patient medical order management server decrypts the encrypted Result based on the medical order identifier ID1, if the authentication code C can be decrypted, the subsequent steps are continuously executed, otherwise, the patient client side medical order request is refused;
step 900: the hospital patient order management server sends the hospital order associated with ID1, ID2, ID3 to the patient client.
Further, the method also comprises the following steps:
step 1000: after completing an advice operation, a patient makes a corresponding completion mark on a patient client, and the patient client sends completion information to the hospital-leaving patient advice management server;
step 1100: and the hospital-leaving patient order management server monitors the condition that the patient completes the order, and if the condition is abnormal, the order is adjusted according to a preset rule, or the corresponding doctor is informed according to the doctor identifier ID2 and is adjusted by the doctor.
Further, each of the orders of the hospital discharge orders is divided into a key activity or a general routine activity, and in step 1100, the order management server adjusts the orders according to a predetermined rule based on the key activity and the general routine activity defined in advance by the doctor.
Further, in step 1100, if the abnormal condition exceeds the condition considered by the predetermined rule, the order management server of the patient who is out of hospital notifies the doctor, and the doctor makes a corresponding adjustment.
Further, the patient client is a smart phone, and the doctor client is a PC, or a smart phone with a near field communication module, a PDA, or a tablet computer.
Further, the patient client and the doctor client are both provided with near field communication modules, and the near field communication modules are NFC modules or Bluetooth modules.
Further, the step 200 includes that a patient client generates a random number R1, and a doctor client generates a random number R2, then the patient client sends R1 to the doctor client and the doctor client also sends R2 to the patient client through the near field communication, and then the two clients simultaneously calculate ID 1-R1 ⊕ R2.
Further, the random numbers R1 and R2 have at least 1024 bits.
Further, the patient identifier ID3 is used to uniquely identify the patient, and the patient identifier ID3 is the patient's identification number or health care number.
Further, the doctor identifier ID2 is used to uniquely identify the doctor, and the doctor identifier ID2 is the doctor's identification number.
The invention has the beneficial effects that: the patient can conveniently obtain and finish the hospital leaving medical advice, and the medical advice can be adjusted in time according to the abnormal condition of the patient.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, and are not to be considered limiting of the invention, in which:
FIG. 1 is a block diagram of a system to which the method of the present invention is applied.
Detailed Description
The present invention will now be described in detail with reference to the drawings and specific embodiments, wherein the exemplary embodiments and descriptions are provided only for the purpose of illustrating the present invention and are not to be construed as limiting the present invention.
Referring to fig. 1, a system architecture for implementing the method of the present invention is shown, the system comprising a patient client, a doctor client, an order management server for a patient in a hospital, and a database.
The patient client side is held by the patient, and the patient leaving the hospital receives a hospital leaving order made by the doctor for the patient through the patient client side, and feeds back an execution result, other health events of the patient and the like. The patient client can be implemented in a mode including but not limited to a webpage, client software running on a PC, a mobile smartphone, and a tablet computer, or supported by various implementations.
The doctor client is held by a doctor, and the doctor can complete modeling of a treatment scheme aiming at the disease species at the doctor client, namely a corresponding doctor advice template is generated; treatment plans can be assigned to the patient and advice can be issued to the patient; the doctor's advice execution record and other condition feedback fed back by the patient in the treatment process can be received and viewed; the order of the patient can be modified or suspended and the execution of the order can be resumed; the modified order may be further issued to the patient.
And the hospital leaving patient doctor advice management server is responsible for communicating with the patient client and the doctor client. The hospital leaving patient advice management server sends the hospital leaving patient advice to the patient client through the network, receives the doctor advice execution records and various health conditions fed back by the patient through the patient client, and writes the doctor advice execution records and various health conditions into a database for storage; the hospital leaving patient advice management server is connected with the doctor client through a network, receives a treatment scheme compiled by a doctor and stores the treatment scheme in the database, receives the treatment scheme distributed by the doctor to the hospital leaving patient, generates a hospital leaving patient advice, stores the hospital leaving patient advice, sends the hospital leaving patient advice to the hospital leaving patient client, simultaneously processes a request for inquiring the hospital leaving patient advice execution record and the health condition information sent by the doctor through the doctor client and returns a result, processes an instruction for modifying, suspending and recovering the doctor advice execution through the doctor client, informs the patient through the patient client, and records operation logs in the process in the database.
The database is used for storing treatment schemes, orders for the individual patients who are out of hospital, records executed by the patients who are out of hospital, relevant conditions (including but not limited to abnormal physical conditions and the like) fed back by the patients who are out of hospital during the execution of the orders (namely, during the treatment process), and all records of the adjustment operation of doctors on the orders.
Based on the above system configuration, the method of the present invention is explained in detail below.
Step 100: when the patient is out of the hospital, the patient uses his patient client to establish near field communication with the doctor client.
According to an embodiment of the present invention, the patient client may be a smartphone used by the patient, and the doctor client may be a PC used by the doctor, or a smartphone, PDA or tablet computer with a near field communication module, both of which have a near field communication module, typically an NFC module or a bluetooth module, etc. Generally, the smart phone is provided with a near field communication module, and the PC can be provided with a corresponding near field communication module.
The patient may establish a near field communication connection with his patient client by bringing the patient client closer to the doctor client. In specific implementation, corresponding software programs (for example, APPs of smart phones) can be installed in both the patient client and the doctor client, and the software programs of the two parties respectively start the near field communication modules to establish connection.
Step 200: the patient client and the doctor client negotiate an order identifier ID1 via a near field communication connection.
By near field communication, the negotiated order identifier is not revealed to others, and thus is reliable and secure.
According to an embodiment of the present invention, a random number R1 may be generated by the patient client, and a random number R2 may be generated by the doctor client, and then the patient client sends R1 to the doctor client and the doctor client also sends R2 to the patient client through the near field communication, so that the two clients may simultaneously calculate ID1 — R1 ⊕ R2.
During this negotiation, the patient client may obtain the order identifier ID1 and the corresponding doctor identifier ID2 from the doctor client.
Step 300: a doctor sets a corresponding hospital leaving advice of the patient on a doctor client, generates an advice data packet, and sends the advice data packet to a hospital leaving patient advice management server; wherein the order data package includes the order identifier ID1, a doctor identifier ID2, a patient identifier ID3, and the hospital discharge order.
Specifically, the doctor identifier ID2 is used to uniquely identify the doctor, and the patient identifier ID3 is used to uniquely identify the patient, both of which are set in advance. For example, an identification number may be used as the identifier, or a medical insurance number may be used as the patient identifier, or unique identifiers of doctors and patients may be randomly generated in advance, and the specific generation method of the identifier is not limited in the present invention.
Thus, based on the order Advice set by the doctor and the three identifiers, generation is performed
The order data packet is { ID1, ID2, ID3, Advice },
therefore, the doctor client can send the doctor order data packet to the hospital leaving patient order management server.
Step 400: after receiving the order data packet, the departured patient order management server stores the order identifier ID1, doctor identifier ID2, patient identifier ID3, and the departured order in association in a database.
Specifically, as shown in fig. 1, the hospital patient order management server is connected to a database, and the database is used for storing relevant information of the hospital order for subsequent query or modification.
Step 500: after a patient logs in at a patient client, the patient client generates an advice request message and sends the advice request message to the hospital-leaving patient advice management server; the order request message includes the doctor identifier ID2 and the patient identifier ID 3.
Specifically, the patient may log into the patient client using his patient identifier ID3, such as into the order management APP on a smartphone, and the patient client may send a request message to the departmental patient order management server using the patient identifier ID3 and the doctor identifier ID2 obtained in step 200.
Step 600: and after receiving the order request message, the order management server of the patient leaving the hospital queries a database according to the order request message to obtain a corresponding order identifier ID 1.
Specifically, in step 400, since the database stores the order identifier ID1, the doctor identifier ID2, and the patient identifier ID3 in association with each other, the order management server for the patient who leaves the hospital may perform a joint query in the database based on ID2 and ID3 to obtain the corresponding order identifier ID1 and the order for the patient who leaves the hospital.
Step 700: the hospital patient medical advice management server randomly generates an authentication code C, sends the authentication code C to the patient client, encrypts the authentication code C by using the medical advice identifier ID1 as a secret key to obtain an encryption Result, and sends the encryption Result to the hospital patient medical advice management server.
Specifically, Result is E (ID1, C), where E is an encryption algorithm that uses ID1 as a key. The encryption algorithm may be any one of existing encryption algorithms in the art, and may be a symmetric encryption algorithm, such as DES, AES, etc., or an asymmetric encryption algorithm, such as RSA, etc.
Step 800: and the hospital-leaving patient medical order management server decrypts the encrypted Result based on the medical order identifier ID1, if the authentication code C can be decrypted, the subsequent steps are continuously executed, and otherwise, the patient client side medical order request is refused.
Through this step, if the patient client can decrypt the authentication code, the patient order management server can confirm that the patient client holds the correct triplet ID1, ID2, and ID3, and thus the patient client can be authenticated by the patient order management server.
During the authentication process of step 500-800 described above, only IDs 2 and ID3 are transmitted over the network, but order identifier ID1 is not transmitted, and thus order identifier ID1 is still not compromised and known to others.
Step 900: the hospital patient order management server sends the hospital order associated with ID1, ID2, ID3 to the patient client.
Specifically, the hospital leaving patient medical order management server may query in the foregoing step 600 to obtain a corresponding database record, extract the hospital leaving order from the database record after the authentication is passed in step 800, and send the hospital leaving order to the patient client.
It should be noted that a patient may see a plurality of visits, and thus there may be multiple records in the database regarding patient identifier ID3, i.e., multiple hospital orders, but different hospital orders may be distinguished by order identifier ID 1.
After receiving the hospital leaving order, the patient client can display the hospital leaving order for the patient to browse, and the patient performs corresponding operations according to the order, such as medicine taking, injection and the like. The following table is a specific hospital order table:
step 1000: after a patient finishes an order operation, making a corresponding completion mark on a patient client, and sending completion information to the hospital leaving patient order management server by the patient client.
Specifically, the APP on the patient client may provide a corresponding marking interface, and the patient completes one order operation, for example, if the patient takes 500mg of c-drug orally on day 1 of week 1, the corresponding completion mark is marked on the order in the marking interface (for example, a check is made in a check box). The APP can send the completion information of the patient to the hospital patient advice management server for storage.
Step 1100: and the hospital leaving patient order management server monitors the condition that the patient completes the order, automatically generates an alarm if abnormality is found, and informs a corresponding doctor according to the doctor identifier ID2 to be adjusted by the doctor.
In the actual process of executing the medical orders, some abnormal events may cause some medical orders not to be executed, and the influence generated after the abnormal situation occurs is exemplified by taking the medical order execution plan shown in the table as an example.
Abnormal case 1: if a patient develops fever symptoms by 12/1/2019, intravenous injection and oral medication associated with 12/2/2019 must be suspended for a delay. Since the 12/2 day iv chemotherapy medication cannot be executed, all subsequent orders will be deferred from execution, i.e., the entire order is left to wait for the patient to recover from the fever. If the patient returns to normal on day 3/12, and is conditioned for chemotherapy, the patient may execute the order prescribed on day 2/12 on day 3/12. All previous orders are performed sequentially for 1 day, e.g., a second chemotherapy is initiated on day 9 at 12 months, and deferred until day 10 at 12 months. Obviously, after an abnormality occurs, the conventional system needs to modify the order execution plan item by item for the whole order and then sends the order execution plan to the patient who is out of hospital to follow the execution.
Abnormal case 2: if the patient normally executes the order according to the plan until the day of 12 months and 4 days, the patient suddenly pulls the stomach and vomits, and the like, the medicine c can not be orally taken in the case, but the medicine x can be continuously taken, in the case, the order execution plan only needs to suspend the medicine c to be orally taken, and the medicine x to be orally taken is continuously executed according to the order plan. The oral administration of the c-drug is only auxiliary administration, so that the overall objective of the whole medical scheme execution is not influenced, and after the patient resumes the 12 th and 5 th days, the corresponding order instructions can be continuously executed according to the orders of the 12 th and 5 th days, namely, the instructions for oral administration of the c-drug in the 12 th and 4 th days are simply skipped, so that the oral administration of the c-drug is suspended in the 12 th and 4 th days, and the oral administration of the c-drug is resumed in the 12 th and 5 th days.
An abnormal condition 3; if the patient has a fever on day 8/12 for up to 10/12, all intravenous and oral medications must be suspended for a delay. In this case, the order instructions of the oral c-drug and the oral x-drug on day 8 of 12 months are ignored, the order of the intravenous a-drug and the oral d-drug and the oral x-drug on day 9 of 12 months and all the order execution plans after day 9 of 12 months are deferred until the patient recovers from fever symptoms on day 11 of 12 months, namely, the order instructions on day 9 of 12 months are executed from day 11 of 12 months, and the order instructions on day 12, day 12 and the following days are executed and the like.
Therefore, for the medical orders, a classification design is required:
the first one is called key activity instruction, namely, the instruction is equivalent to milestone-like activity in the whole treatment process, each milestone is a necessary action for completing the treatment process, such as chemotherapy by injecting a-drug, the whole treatment process has two milestone activities, namely chemotherapy by injecting a-drug twice, the treatment target in the whole treatment process is two times of chemotherapy, and the rest of the drugs are auxiliary drugs, so that the patient is helped to reduce side effects caused by the chemotherapy. The key activities may be the same activities or activities of different contents, but there is a dependency and precedence relationship between the key activities, for example, the second time of intravenous injection of a-medication is performed 7 days after the first time of intravenous injection of a-medication, or it can be understood that the second time of intravenous injection of a-medication must be performed 7 days after the first time of intravenous injection of a-medication is completed, and the second time of intravenous injection of a-medication cannot be performed if the first time of intravenous injection of a-medication is not completed or is not completed for more than 7 days. Another feature of the critical activity instruction is that intravenous drug a is not allowed after a condition affecting the execution occurs, such as a patient fever, in which case a deferred action is taken as the critical activity instruction, i.e., the critical activity instruction cannot be skipped, and intravenous drug a is executed when the patient's body resumes meeting the conditions for intravenous drug a. The design of the key activities comprises the previous activities, if the previous activities do exist, the previous activities need to be defined during scheme modeling, so that any change occurs in the previous activities, and the subsequent activities can automatically make corresponding changes according to the change of the previous activities.
Secondly, we refer to ordinary routine activities, that is, ordinary activities which are executed according to a certain frequency in the whole treatment process, when abnormal conditions which affect the execution of the ordinary activities occur, such as the patient pulls the stomach and vomits, the oral c-drug administration must be suspended, and the c-drug administration according to the medical advice can be immediately resumed after the patient's symptoms are recovered. For oral administration of c-drug, which is a routine action to be performed every morning and afternoon of the first week, the patient does not need to influence the whole treatment process because of suspending the oral administration of c-drug, i.e. if two times of chemotherapy do not influence the process by straining to vomit, if c-drug is taken two less times during the process, the whole treatment process is not influenced at all. Common routines, when defined, include information about the time period, frequency, etc. of execution.
Therefore, based on the key activities and common routine activities defined by the doctor in advance, the order management server of the patient away from the hospital can judge whether the order is executed according to the plan according to the execution feedback of the patient, if the order is not executed according to the plan, an alarm can be generated to remind the doctor, the doctor can check or inquire the condition of the patient to judge whether the order needs to be modified, if the order needs to be modified, the doctor sends an order for adjusting the order at the doctor client side, and after the order of the doctor is received, the order management server automatically adjusts the order according to a preset rule. .
After the medical advice is adjusted, the hospital leaving patient medical advice management server can push the adjusted medical advice to the patient client, or the patient client can also regularly update and download the hospital leaving advice every day. From this, guaranteed that the sudden abnormal conditions that the doctor's advice of leaving the hospital can deal with patient, improved the reliability of doctor's advice of leaving the hospital.
The above description is only a preferred embodiment of the present invention, and all equivalent changes or modifications of the structure, characteristics and principles described in the present invention are included in the scope of the present invention.
Claims (10)
1. A method for managing the execution of orders of hospital patients is characterized by comprising the following steps:
step 100: when the patient is out of the hospital, the patient uses his patient client to establish near field communication with the doctor client;
step 200: the patient client and the doctor client are connected through near field communication, and a medical order identifier ID1 is negotiated;
step 300: a doctor sets a corresponding hospital leaving advice of the patient on a doctor client, generates an advice data packet, and sends the advice data packet to a hospital leaving patient advice management server; wherein the order data package comprises the order identifier ID1, a doctor identifier ID2, a patient identifier ID3, and the hospital discharge order;
step 400: after receiving the order data packet, the hospital leaving patient order management server stores the order identifier ID1, the doctor identifier ID2, the patient identifier ID3 and the hospital leaving order in a database in an associated manner;
step 500: after a patient logs in at a patient client, the patient client generates an advice request message and sends the advice request message to the hospital-leaving patient advice management server; the order request message includes the doctor identifier ID2 and the patient identifier ID 3;
step 600: after receiving the order request message, the order management server of the patient leaving the hospital queries a database according to the order request message to obtain a corresponding order identifier ID 1;
step 700: the hospital patient medical advice management server randomly generates an authentication code C, sends the authentication code C to the patient client, encrypts the authentication code C by using the medical advice identifier ID1 as a secret key to obtain an encryption Result, and sends the encryption Result to the hospital patient medical advice management server;
step 800: the hospital-leaving patient medical order management server decrypts the encrypted Result based on the medical order identifier ID1, if the authentication code C can be decrypted, the subsequent steps are continuously executed, otherwise, the patient client side medical order request is refused;
step 900: the hospital patient order management server sends the hospital order associated with ID1, ID2, ID3 to the patient client.
2. The method of claim 1, further comprising the steps of:
step 1000: after completing an advice operation, a patient makes a corresponding completion mark on a patient client, and the patient client sends completion information to the hospital-leaving patient advice management server;
step 1100: and the hospital-leaving patient order management server monitors the condition that the patient completes the order, and if the condition is abnormal, the order is adjusted according to a preset rule, or the corresponding doctor is informed according to the doctor identifier ID2 and is adjusted by the doctor.
3. The method of claim 2, wherein each of the order of the hospital discharge orders is divided into a critical activity or a general routine activity, and in step 1100, the hospital discharge patient order management server adjusts the order according to a predetermined rule based on the critical activity and the general routine activity previously defined by the doctor.
4. The method of claim 2, wherein in step 1100, if the abnormal condition exceeds the condition considered by the predetermined rule, the order management server of the patient from the hospital notifies the doctor, and the doctor makes the corresponding adjustment.
5. The method according to any one of claims 1-4, wherein the patient client is a smartphone and the doctor client is a PC, or a smartphone with a near field communication module, a PDA or a tablet computer.
6. The method of any one of claims 1-5, wherein the patient client and the doctor client both have near field communication modules, and wherein the near field communication modules are NFC modules or Bluetooth modules.
7. The method as claimed in any one of claims 1 to 6, wherein the step 200 comprises generating a random number R1 by the patient client and a random number R2 by the doctor client, and then transmitting R1 to the doctor client and R2 to the patient client by the doctor client through the near field communication, and then calculating the ID 1-R1 ⊕ R2 by the two clients at the same time.
8. The method of claim 7, wherein the random numbers R1 and R2 have at least 1024 bits.
9. The method of any of claims 1-8, wherein the patient identifier ID3 is used to uniquely identify the patient, and wherein the patient identifier ID3 is a patient's identification number or health care number.
10. The method of any one of claims 1-9, wherein the doctor identifier ID2 is used to uniquely identify the doctor, and wherein the doctor identifier ID2 is a doctor's identification number.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911365846.4A CN111145857A (en) | 2019-12-26 | 2019-12-26 | Method for managing doctor advice execution of patient leaving hospital |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911365846.4A CN111145857A (en) | 2019-12-26 | 2019-12-26 | Method for managing doctor advice execution of patient leaving hospital |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111145857A true CN111145857A (en) | 2020-05-12 |
Family
ID=70520467
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911365846.4A Pending CN111145857A (en) | 2019-12-26 | 2019-12-26 | Method for managing doctor advice execution of patient leaving hospital |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111145857A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113241161A (en) * | 2021-05-10 | 2021-08-10 | 酉阳土家族苗族自治县人民医院 | ERAS medical advice management platform |
| CN113380362A (en) * | 2021-06-18 | 2021-09-10 | 安徽科大讯飞医疗信息技术有限公司 | Chronic disease supervision method, platform, system, electronic equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109166610A (en) * | 2018-08-30 | 2019-01-08 | 成都宇亨智能设备科技有限公司 | A kind of intelligent medical order management system and method based on prescription information |
| CN109461483A (en) * | 2018-10-26 | 2019-03-12 | 深圳市全息医疗科技有限公司 | A kind of intelligence doctor's advice executes method, apparatus, system and storage medium |
| CN109887568A (en) * | 2019-03-02 | 2019-06-14 | 深圳市宝安区人民医院 | Based on the health management system arranged of doctor's advice |
-
2019
- 2019-12-26 CN CN201911365846.4A patent/CN111145857A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109166610A (en) * | 2018-08-30 | 2019-01-08 | 成都宇亨智能设备科技有限公司 | A kind of intelligent medical order management system and method based on prescription information |
| CN109461483A (en) * | 2018-10-26 | 2019-03-12 | 深圳市全息医疗科技有限公司 | A kind of intelligence doctor's advice executes method, apparatus, system and storage medium |
| CN109887568A (en) * | 2019-03-02 | 2019-06-14 | 深圳市宝安区人民医院 | Based on the health management system arranged of doctor's advice |
Non-Patent Citations (1)
| Title |
|---|
| 张仕斌 等: "《卓越工程师计划 应用密码学》", 西安：西安电子科技大学出版社, pages: 360 - 361 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113241161A (en) * | 2021-05-10 | 2021-08-10 | 酉阳土家族苗族自治县人民医院 | ERAS medical advice management platform |
| CN113380362A (en) * | 2021-06-18 | 2021-09-10 | 安徽科大讯飞医疗信息技术有限公司 | Chronic disease supervision method, platform, system, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11907397B2 (en) | Records access and management | |
| JP7190238B2 (en) | Delivery and data sharing of clinical data in equipment management | |
| Ramzan et al. | Healthcare applications using blockchain technology: Motivations and challenges | |
| US11244059B2 (en) | Blockchain for managing access to medical data | |
| Aileni et al. | IoMT: A blockchain perspective | |
| JP5085561B2 (en) | Remote programming of patient medical devices | |
| EP2036299B1 (en) | Advanced access control for medical ad hoc body sensor networks | |
| US8977572B2 (en) | Systems and methods for patient-controlled, encrypted, consolidated medical records | |
| US20130191162A1 (en) | System and Method for Facilitating Outcome-Based Health Care | |
| WO2004025530A1 (en) | Medical information management system | |
| JP2010536111A (en) | Medical device control method | |
| US20150254423A1 (en) | Computer-based prescription system for medicaments | |
| US12062458B2 (en) | System and method for secure, private, and trusted medical information monitoring and semi-autonomous prescription management | |
| AU2016269572A1 (en) | User device platform for interacting with cloud-based platform | |
| CN111145857A (en) | Method for managing doctor advice execution of patient leaving hospital | |
| KR102279377B1 (en) | Medical information providing system with enhanced personal authority using blockchain | |
| US20240348455A1 (en) | Blockchain-based supervision method for electronic immunity passport | |
| CN113764060A (en) | Medical data management system based on double block chains and patient authorized medical record sharing method | |
| Yongjoh et al. | Development of an internet-of-healthcare system using blockchain | |
| Alsudani et al. | Blockchain-based e-medical record and data security service management based on IoMT resource | |
| KR102557971B1 (en) | System and method for connecting clinical trial using blockchain network | |
| US20230047795A1 (en) | Automatic medical device patient registration | |
| Rubio et al. | A robust and simple security extension for the medical standard SCP-ECG | |
| US20210326903A1 (en) | Method for registering a user in a medical software application | |
| WO2023076467A1 (en) | Encrypting data generated from medical devices |
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 |