Medical examination data management method and device, electronic equipment and storage medium

Through the dual password verification mechanism, the problem of security risks in the transmission of medical test data between multiple institutions is solved, ensuring that only authorized hospital terminals and doctors can access the data, achieving data security and compliance.

CN119011202APending Publication Date: 2024-11-22HEFEI JINYU MEDICAL INSPECTION OFFICE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410966686.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-18
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

There are security risks in the transmission of medical test data between multiple institutions, resulting in data leakage and illegal access.

Method used

Using a dual password verification mechanism, through communication between the server and the hospital terminal and the laboratory terminal, ensure that only the hospital terminals within the institution and the doctors bound to the inspection project can access the corresponding medical test data, and prevent other institutions and unauthorized personnel. visit.

Benefits of technology

It effectively improves the security of medical test data, prevents data leakage and unauthorized access, and ensures that the data is only viewed by doctors within their responsibilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119011202A_ABST
    Figure CN119011202A_ABST
Patent Text Reader

Abstract

The embodiment of the invention relates to a medical examination data management method and device, electronic equipment and a storage medium, and the method comprises the steps: receiving an examination data viewing request sent by a target hospital terminal, the inspection data viewing request comprises a target inspection item corresponding to the medical inspection data to be accessed and doctor identity information corresponding to the target hospital terminal; acquiring a first input password uploaded by the target hospital terminal; if the first input password is matched with a first preset password corresponding to a mechanism to which the target hospital terminal belongs, acquiring a second input password uploaded by the target hospital terminal, and acquiring a second preset password bound with the doctor identity information and the target inspection item; and if the second input password is matched with the second preset password, sending medical examination data corresponding to the target examination item to the target hospital terminal. According to the medical examination data management method and device, the electronic equipment and the storage medium, the security of the medical examination data can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and specifically to a medical test data management method, device, electronic device and storage medium. Background Art

[0002] With the widespread application of medical tests in daily life, such as gene tests, blood hormone tests, etc., various medical institutions send samples corresponding to multiple test items to laboratories for testing, and medical test data related to each test item will be generated in this process. Since the same laboratory can test the test items of multiple medical institutions, and can also test multiple test items of the same medical structure, when doctors obtain medical test data, they can easily obtain medical test data from other medical institutions, and can easily obtain medical test data of other test items, resulting in the leakage of medical test data and the inability to ensure data security. Summary of the invention

[0003] The embodiments of the present application disclose a medical test data management method, device, electronic device and storage medium, which can improve the security of medical test data.

[0004] In a first aspect, an embodiment of the present application discloses a medical test data management method, which is applied to a server, and the server is communicatively connected to at least one hospital terminal; the method comprises:

[0005] Receiving a test data viewing request sent by a target hospital terminal, the test data viewing request including a target test item corresponding to the medical test data to be accessed and the doctor identity information corresponding to the target hospital terminal; the target hospital terminal is any of the hospital terminals;

[0006] Obtaining the first input password uploaded by the target hospital terminal;

[0007] If the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, then obtaining the second input password uploaded by the target hospital terminal, and obtaining the second preset password bound to the doctor's identity information and the target inspection item;

[0008] If the second input password matches the second preset password, the medical test data corresponding to the target test item is sent to the target hospital terminal.

[0009] As an optional implementation, in the first aspect of the embodiment of the present application, the server is also communicatively connected to at least one laboratory terminal, and the method also includes: if the second input password does not match the second preset password, sending a review request to the target laboratory terminal corresponding to the target inspection item, the review request including the target inspection item and the doctor's identity information, so that the target laboratory terminal can review whether the target hospital terminal can access the medical inspection data corresponding to the target inspection item; if the review approval information sent by the target laboratory terminal is received, the medical inspection data corresponding to the target inspection item is sent to the target hospital terminal; if the review approval information sent by the target laboratory terminal is not received within the preset time period, or the review failure information sent by the target laboratory terminal is received, the medical inspection data corresponding to the target inspection item is not sent to the target hospital terminal.

[0010] As an optional implementation, in the first aspect of the embodiment of the present application, the inspection data viewing request also includes at least one data type corresponding to the medical inspection data to be accessed; after obtaining the first input password uploaded by the target hospital terminal, the method also includes: if the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, then determining the confidentiality level corresponding to each of the data types, and the confidentiality level includes public or non-public; if the inspection data viewing request includes a data type with a public confidentiality level, then sending the medical inspection data corresponding to the data type with a public confidentiality level to the target hospital terminal.

[0011] As an optional implementation, in the first aspect of the embodiment of the present application, the obtaining of the second input password uploaded by the target hospital terminal and the obtaining of the second preset password bound to the doctor's identity information and the target inspection item include: if the inspection data viewing request includes a data type with a confidentiality level of non-public, obtaining the second input password uploaded by the target hospital terminal, and obtaining the second preset password bound to the doctor's identity information and the target inspection item; if the second input password matches the second preset password, sending the medical inspection data corresponding to the target inspection item to the target hospital terminal, includes: if the second input password matches the second preset password, sending the medical inspection data corresponding to the data type with a confidentiality level of non-public to the target hospital terminal.

[0012] As an optional implementation, in the first aspect of the embodiment of the present application, the method also includes: determining the data access permission corresponding to the target hospital terminal based on the doctor's identity information; if the data access permission is the first permission, obtaining a third preset password bound to the first permission; if the second input password matches the third preset password, sending all medical test data of the institution to which the target hospital terminal belongs to the target hospital terminal; obtaining the second preset password bound to the doctor's identity information and the target inspection item includes: if the data access permission is the second permission, obtaining the second preset password bound to the doctor's identity information and the target inspection item; the first permission is greater than the second permission, and the first permission refers to the permission to access all medical test data of the institution to which the target hospital terminal belongs; the second permission refers to the permission to access the medical test data corresponding to the inspection item bound to the doctor's identity information.

[0013] As an optional implementation, in the first aspect of the embodiment of the present application, the server is also communicatively connected to at least one laboratory terminal, and the method also includes: obtaining multiple historical access records corresponding to the historical hospital terminal, the historical access records including the historical doctor identity information corresponding to the historical hospital terminal, and at least one historical data type corresponding to the medical test data corresponding to the historical hospital terminal; dividing the at least one historical data type by importance and determining the importance corresponding to each historical data type; determining a target historical data type whose importance is greater than a preset threshold; generating a historical type list corresponding to the historical doctor identity information based on the target historical data type, and sending the historical type list to the at least one laboratory terminal, so that the at least one laboratory terminal searches for medical test data corresponding to each target historical data type contained in the historical type list from the medical test data corresponding to the test item bound to the historical doctor identity information, and uploads it to the server.

[0014] As an optional implementation, in the first aspect of the embodiment of the present application, the inspection data viewing request also includes at least one data type corresponding to the target inspection item; after obtaining the first input password uploaded by the target hospital terminal, the method also includes: if the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, obtaining the historical type list corresponding to the doctor's identity information; if the at least one data type is included in the historical type list corresponding to the doctor's identity information, sending medical inspection data corresponding to the at least one target inspection data type to the target hospital terminal; if the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, obtaining the second input password uploaded by the target hospital terminal, and obtaining the second preset password bound to the doctor's identity information and the target inspection item, including: if there is any data type that does not match the historical inspection data type included in the target historical type list, obtaining the second input password uploaded by the target hospital terminal, and obtaining the second preset password bound to the doctor's identity information and the target inspection item.

[0015] In a second aspect, an embodiment of the present application discloses a medical test data management device, which is applied to a server, and the server is communicatively connected to at least one hospital terminal; the device comprises:

[0016] A receiving module, configured to receive a test data viewing request sent by a target hospital terminal, wherein the test data viewing request includes a target test item corresponding to the medical test data to be accessed and the doctor identity information corresponding to the target hospital terminal; the target hospital terminal is any of the hospital terminals;

[0017] An acquisition module, used for acquiring the first input password uploaded by the target hospital terminal;

[0018] The acquisition module is further configured to acquire, if the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, a second input password uploaded by the target hospital terminal, and acquire a second preset password bound to the doctor's identity information and the target inspection item;

[0019] A sending module is used to send the medical test data corresponding to the target test item to the target hospital terminal if the second input password matches the second preset password.

[0020] In a third aspect, an embodiment of the present application discloses an electronic device, including a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor implements the method described in any of the above embodiments.

[0021] In a fourth aspect, an embodiment of the present application discloses a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described in any of the above embodiments is implemented.

[0022] The medical test data management method, device, electronic device and storage medium disclosed in the embodiments of the present application, the server receives a test data viewing request sent by a target hospital terminal, the test data viewing request includes a target test item corresponding to the medical test data to be accessed and the doctor's identity information corresponding to the target hospital terminal; the target hospital terminal is any hospital terminal; a first input password uploaded by the target hospital terminal is obtained; if the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, the second input password uploaded by the target hospital terminal is obtained, and the second preset password bound to the doctor's identity information and the target test item is obtained; if the second input password matches the second preset password, the medical test data corresponding to the target test item is sent to the target hospital terminal. In an embodiment of the present application, a first preset password associated with the institution to which the hospital terminal belongs is matched with a first input password uploaded by the target hospital terminal, thereby ensuring that only hospital terminals within the institution can further view the medical test data of the institution, effectively preventing illegal access by other institutions; and a second preset password that is doubly bound to the doctor's identity information and the target test item is matched with the second input password, thereby ensuring that only the doctor bound to the target test item can use the target hospital terminal to view the medical test data corresponding to the target test item, thereby avoiding doctors from viewing medical test data corresponding to test items that are not within their scope of responsibility or are not authorized to access, and adopting a double password verification method to effectively improve the security of medical test data. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0024] Figure 1 This is an application scenario diagram of a medical test data management method in an embodiment;

[0025] Figure 2 is a flow chart of a medical test data management method in one embodiment;

[0026] Figure 3 is a flow chart of a medical test data management method in another embodiment;

[0027] Figure 4is a flow chart of a medical test data management method in another embodiment;

[0028] Figure 5 is a flow chart of a medical test data management method in another embodiment;

[0029] Figure 6 is a flow chart of a medical test data management method in another embodiment;

[0030] Figure 7 is a block diagram of a medical test data management device in one embodiment;

[0031] Figure 8 FIG. 4 is a structural block diagram of an electronic device in an embodiment. DETAILED DESCRIPTION

[0032] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0033] It should be noted that the terms "including" and "having" and any variations thereof in the embodiments of the present application and the accompanying drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device including a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products or devices.

[0034] It is understood that the terms "first", "second", etc. used in this application can be used in this article to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish a first element from another element. For example, without departing from the scope of this application, the first input password can be referred to as the second input password, and similarly, the second input password can be referred to as the first input password. Both the first input password and the second input password are input passwords, but they can be the same input password or different input passwords.

[0035] The embodiments of the present application disclose a medical test data management method, device, electronic device and storage medium, which can prevent the leakage of medical test data between different institutions and prevent doctors from viewing medical test data corresponding to other unbound test items, thereby further improving the security of medical test data.

[0036] Figure 1FIG. 1 is an application scenario diagram of a medical test data management method in an embodiment. Figure 1 As shown, the medical test data management method can be applied to the server 110. The server 110 can establish a communication connection with at least one hospital terminal 120, and can also establish a communication connection with at least one laboratory terminal 130. Among them, the server 110 may include but is not limited to a single server, a server cluster, etc. The hospital terminal 120 and the laboratory terminal 130 may include but are not limited to various personal computers, smart wearable devices, tablet computers, PCs (Personal Computers), laptops, smart phones, and portable wearable devices, etc., which are not limited in the embodiments of the present application.

[0037] Optionally, available communication connection methods include but are not limited to data line connection, wireless local area network (Wireless Local Area Network, WLAN) connection, WiFi connection and other wired or wireless connection methods.

[0038] Optionally, when there are multiple hospital terminals 120 , the multiple hospital terminals 120 may belong to the same institution or different institutions, such as different hospitals.

[0039] In some embodiments, when the institution to which the hospital terminal 120 belongs needs to conduct an inspection project, the delivery personnel may deliver the specimen to be inspected to the laboratory to which the laboratory terminal 130 belongs, and upload the project information related to the inspection project to the server 110, wherein the project information includes one or more of the project name corresponding to the inspection project, the department to which the project belongs, the doctor's identity information corresponding to the project, and the patient's identity information. The laboratory terminal 130 may obtain the project information related to the inspection project from the server 110, and inspect the specimen to be inspected based on the project information related to the inspection project to obtain the corresponding medical inspection data, and upload the medical inspection data corresponding to the inspection project to the server 110. The server 110 generates a first preset password associated with the institution to which the hospital terminal 120 belongs, and generates a second preset password bound to each inspection project and the corresponding doctor's identity information, and informs the institution to which the hospital terminal 120 belongs of the first preset password, and informs the doctor of the doctor's identity information corresponding to each inspection project of the second preset password.

[0040] In some embodiments, the server 110 may randomly generate a string of characters as the first preset password associated with the organization to which the hospital terminal 120 belongs. The server 110 may also generate the first preset password associated with the organization to which the hospital terminal 120 belongs based on the project information and medical test data related to the test project.

[0041] When the doctor needs to obtain the medical test data corresponding to the target test item, the target hospital terminal 120 is used to send a test data viewing request to the server 110, and the test data viewing request includes the target test item and the doctor's identity information corresponding to the medical test data to be accessed. The doctor can also enter a first input password in the target hospital terminal 120, and the target hospital terminal 120 can upload the first input password to the server. After receiving the test data viewing request sent by the target hospital terminal 120, the server 110 obtains the first input password uploaded by the target hospital terminal 120. The server 110 matches the first input password with the first preset password corresponding to the institution to which the target hospital terminal 120 belongs. The doctor can also enter a second input password in the target hospital terminal 120, and the target hospital terminal 120 can upload the second input password to the server. If the server 110 detects that the first input password matches the first preset password, the server 110 obtains the second input password uploaded by the target hospital terminal 120, and obtains the second preset password bound to the doctor's identity information and the target inspection item; the server 110 matches the second input password with the second preset password. If the second input password matches the second preset password, the server 110 sends the medical inspection data corresponding to the target inspection item to the target hospital terminal 120, so that the doctor can obtain the medical inspection data corresponding to the target inspection item.

[0042] like Figure 2 As shown, in one embodiment, a medical test data management method is provided, which can be applied to the above server. The method may include the following steps 210 to 240.

[0043] Step 210: receiving a request for viewing test data sent by a target hospital terminal.

[0044] After the institution to which the target hospital terminal belongs sends the samples to be tested corresponding to each test item to the laboratory, the laboratory tests the samples to be tested and uploads the medical test data corresponding to the test item to the server. Therefore, when the target hospital terminal wants to obtain the medical test data corresponding to the target test item, the target hospital terminal can send a test data viewing request to the server to obtain the stored medical test data corresponding to the target test item from the server.

[0045] A hospital terminal refers to a terminal device used by doctors in their respective institutions that can communicate with the server; the target hospital terminal can be any hospital terminal. Optionally, a hospital terminal can correspond to a doctor's identity information one by one. A hospital terminal can also correspond to multiple doctor's identity information, that is, multiple doctors use the same hospital terminal. For example, if multiple doctors are bound to the same test item, and one item corresponds to one hospital terminal, then these multiple doctors can use the same hospital terminal to request medical test data from the server.

[0046] The request for viewing test data includes the target test item corresponding to the medical test data to be accessed and the doctor's identity information corresponding to the target hospital terminal; the target hospital terminal is any hospital terminal. The medical test data to be accessed refers to the medical test data that the target hospital terminal requests to obtain from the server. The medical test data may include at least part of the data generated by the laboratory during the test process of the target test item, as well as the test results of the target test item. The doctor's identity information corresponding to the target hospital terminal refers to the personal information corresponding to the doctor who holds or uses the target hospital terminal, which may include one or more of the doctor's name, work number in the institution to which he belongs, ID number, department to which he belongs, doctor's grade, etc., but is not limited to this.

[0047] Optionally, in addition to requesting the complete medical test data corresponding to the target test item from the server, the target hospital terminal can also obtain partial medical test data. Therefore, the test data viewing request also includes at least one data type corresponding to the medical test data to be accessed. Data type refers to the type attribute of each data contained in the medical test data. For example, the medical test data corresponding to the target test item may include data types such as project name, methodology, detection reagents, equipment, quality control, inter-laboratory quality assessment, and reagent instructions; when the target hospital terminal sends a request for data to the server, it can selectively obtain data of some data types, for example, only obtain the data of the project name, quality control, inter-laboratory quality assessment, and reagent instructions of the target test item.

[0048] Step 220, obtaining the first input password uploaded by the target hospital terminal.

[0049] Since the medical test data stored in the server may belong to different institutions, in order to avoid the leakage of medical test data between different institutions, each institution may have a first preset password corresponding to the institution. The first preset password is generated by the server, and the first preset password is associated with each institution. The first preset passwords corresponding to different institutions are different. Optionally, the server may send the first preset password associated with the target institution to any hospital terminal in the target institution, and the doctor at the hospital terminal that receives the first preset password will inform other doctors of the target institution of the first preset password, so that all doctors of the institution know the first preset password corresponding to the institution. Optionally, the server may also send the first preset password associated with the target institution to all hospital terminals belonging to the target institution recorded in the server, so that all doctors of the institution know the first preset password corresponding to the institution.

[0050] When the doctor of the institution needs to obtain the medical test data corresponding to the target test item, he / she enters the first input password in the target hospital terminal according to the first preset password known to him / her, and the target hospital terminal uploads the first input password to the server. The server can determine whether the institution to which the target hospital terminal actually belongs is the institution to which the target hospital terminal is preset as recorded in the server according to the first input password uploaded by the target hospital terminal, so as to ensure that the target hospital terminal can only access the medical test data corresponding to the test items of the institution to which the target hospital terminal belongs, and prevent hospital terminals of other institutions from obtaining the medical test data of the target institution.

[0051] Optionally, after receiving the inspection data viewing request, the server may send a first password prompt to the target hospital terminal, so that the target hospital terminal uploads the first input password according to the first password prompt. The first password prompt is used to prompt the target hospital terminal to enter the password corresponding to the actual institution to which it belongs. Optionally, after receiving the first password prompt sent by the server, the target hospital terminal may display a password input interface according to the first password prompt; the password input interface may include a prompt area and an input area, the prompt area may display "Please enter the password of the institution to which the hospital terminal belongs", and the input area is an input box. After receiving the first input password entered by the doctor, the target hospital terminal sends the first input password to the server, so that the server obtains the first input password uploaded by the target hospital terminal.

[0052] Optionally, the first input password uploaded by the target hospital terminal may be carried in the inspection data viewing request, and the server may directly parse the first input password from the inspection data viewing request sent by the target hospital terminal.

[0053] Step 230, if the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, obtain the second input password uploaded by the target hospital terminal, and obtain the second preset password bound to the doctor's identity information and the target test item.

[0054] After the server obtains the first input password, the first input password can be matched with the first preset password corresponding to the institution to which the target hospital terminal belongs, so as to determine whether the institution to which the target hospital terminal actually belongs is the preset institution to which the target hospital terminal belongs stored in the server, to ensure that the target hospital terminal can only obtain the medical examination data corresponding to the institution to which the target hospital terminal belongs.

[0055] In some embodiments, the first input password and the first preset password can match, indicating that the organization to which the target hospital terminal actually belongs is the same as the preset organization stored in the server, which can ensure that the target inspection items requested to be accessed by the target hospital terminal are inspection items of the organization to which the target hospital terminal belongs, thereby preventing hospital terminals of other institutions from obtaining the medical inspection data of the target organization, thereby preventing the leakage of medical inspection data between different institutions.

[0056] Different doctors in the same institution have second preset passwords bound to the doctor's identity information and the test items; the second preset password is generated by the server, and the second preset password is doubly bound to the doctor's identity information and the test items, and the server informs the doctor of the doctor's identity information corresponding to each test item. The second preset passwords known to different doctors are different, the second preset passwords corresponding to different test items of the same doctor are also different, and the second preset passwords known to different doctors for the same test item are also different, that is, the second preset password is unique among doctors with different test items and different doctor identity information, which can ensure that doctors in the same institution who are not bound to the target test item will not be able to view the medical test data corresponding to the target test item due to the same second preset password.

[0057] Optionally, after generating the second preset password, the server may send the second preset password to the hospital terminal recorded in the server and corresponding to the doctor identity information bound to the second preset password, based on the doctor identity information bound to the second preset password, and inform the hospital terminal of the test items bound to the second preset password, so that the doctor with the doctor identity information knows the second preset password bound to the doctor identity information and the test items.

[0058] The doctor can input the second input password in the target hospital terminal according to the second preset password known to him, and the target hospital terminal uploads the second input password to the server. The server can further obtain the second input password uploaded by the target hospital terminal, the second preset password bound to the doctor's identity information and the target test item, so that the server can further judge the identity information of the doctor currently using the target hospital terminal, determine whether he can access the medical test data corresponding to the target test item, and ensure that only the doctor bound to the target test item can view the medical test data corresponding to the target test item using the target hospital terminal, thereby further improving the security of the medical test data.

[0059] Optionally, the description of the server obtaining the second input password uploaded by the target hospital terminal may be similar to the description of the server obtaining the first input password described in the above step 220, which will not be repeated here.

[0060] In some embodiments, the first preset password is different from the second preset password. The first preset password is bound to the organization to which the hospital terminal belongs, and the second preset password is doubly bound to the test item and the doctor's identity information. That is, the server can obtain the first preset password by looking up the preset organization to which the target hospital terminal belongs stored in the server, and the server uses the preset password whose test item is the target test item and whose doctor's identity information is the same as the doctor's identity information corresponding to the target hospital terminal as the second preset password.

[0061] Optionally, the second preset passwords corresponding to the same test item but different doctor identity information may be different; the second preset passwords corresponding to the same doctor identity information but different test items may not be used. Thus, the doctor can only access the medical test data corresponding to his own doctor identity information. In the case that the second preset password of the doctor is illegally stolen, the illegal user can only obtain the medical test data of the test item corresponding to the second preset password when illegally using the hospital terminal and the doctor's identity information, but cannot obtain the medical test data of other test items of the doctor. Through independent access between each test item, the security of each medical test data can be guaranteed to the greatest extent.

[0062] In some embodiments, if the server detects that the first input password does not match the first preset password, it means that the institution actually described by the target hospital terminal is different from the preset institution stored in the server, which means that other institutions are more likely to access the medical examination data of the preset institution. Therefore, the medical examination data corresponding to the target examination item is not sent to the target hospital terminal to avoid the leakage of the medical examination data of the preset institution.

[0063] In some embodiments, if the server detects that the first input password does not match the first preset password, the server may send a first input password error prompt to the target hospital terminal, so that the target hospital terminal re-uploads a new first input password. Optionally, after receiving the first input password error prompt sent by the server, the target hospital terminal may display the password input interface again; at this time, the prompt area in the password input interface may display "Wrong password, please re-enter the password of the institution to which the hospital terminal belongs" to obtain the new first input password entered by the doctor. The target hospital terminal sends the new first input password to the server, so that the server obtains the new first input password uploaded by the target hospital terminal, and matches the new first input password with the first preset password. Provide the target hospital terminal with an opportunity for trial and error to avoid the inability to obtain medical test data due to errors such as incorrect input by doctors.

[0064] In some embodiments, the server may specify that within a preset input time period, if the number of times the first input password does not match the first preset password is greater than a number threshold, the server may refuse to obtain the first input password uploaded by the target hospital terminal until a preset interval time period has passed, and then obtain the first input password uploaded by the target hospital terminal. Optionally, within a preset interval time period, the server may send a lock prompt to the target hospital terminal to prompt the target hospital terminal that the number of incorrect first input passwords is greater than a number threshold and the first input password is not obtained temporarily, and prompt the target hospital terminal to upload the first input password again after a preset interval time period. Optionally, the preset interval time period may increase as the number of server rejections increases. By setting a number threshold, it is possible to effectively prevent illegal users from obtaining the correct first input password through brute force cracking (exhaustive method, etc.), thereby improving its security, and effectively reducing the resource usage of the server caused by continuous matching.

[0065] Step 240: If the second input password matches the second preset password, the medical test data corresponding to the target test item is sent to the target hospital terminal.

[0066] After obtaining the second input password and the second preset password, the server can match the second input password with the second preset password to determine whether the actual doctor currently using the target hospital terminal is the preset doctor stored in the server who is doubly bound to the target test item and doctor's identity information, so as to prevent doctors of other test items from accessing the medical test data corresponding to the target test item.

[0067] In some embodiments, if the second input password matches the second preset password, it means that the actual doctor currently using the target hospital terminal is the preset doctor stored in the server who can access the medical test data corresponding to the target test item. Therefore, the server can send the medical test data corresponding to the target test item to the target hospital terminal to ensure that only the doctor bound to the target test item can view the medical test data corresponding to the target test item using the target hospital terminal, thereby avoiding doctors in the same institution viewing medical test data corresponding to test items that are not within their scope of responsibility or are not authorized to access.

[0068] In some embodiments, if the server detects that the second input password does not match the second preset password, the server does not send the medical test data corresponding to the target test item to the target hospital terminal. Specifically, the description of the server determining that the second input password does not match the second preset password can refer to the relevant description of the server determining that the first input password does not match the private preset password in step 230 above, which will not be repeated here.

[0069] In an embodiment of the present application, the server uses a first preset password associated with the institution to which the hospital terminal belongs to match the first input password uploaded by the target hospital terminal, thereby ensuring that only hospital terminals within the institution can further view the medical test data of the institution, effectively preventing access by other institutions; and, using a second preset password that is doubly bound to the doctor's identity information and the target test item to match the second input password, thereby ensuring that only the doctor bound to the target test item can use the target hospital terminal to access the medical test data corresponding to the target test item, thereby avoiding doctors from viewing medical test data corresponding to test items that are not within their scope of responsibility or are not authorized to access, and adopting a double password verification method to effectively improve the security of medical test data.

[0070] like Figure 3 As shown, in another embodiment, a medical test data management method is provided, which can be applied to the above server. The method may include the following steps 302 to 310.

[0071] Step 302, determine whether the second input password matches the second preset password. If they match, execute step 304; if they do not match, execute step 306.

[0072] After receiving the test data viewing request sent by the target doctor terminal and obtaining the first input password uploaded by the target hospital terminal, the server detects that the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, then obtains the second input password uploaded by the target hospital terminal, and obtains the second preset password bound to the doctor's identity information and the target test item; the server can determine whether the second input password matches the second preset password, thereby determining whether the target hospital terminal can obtain the medical test data corresponding to the target test item.

[0073] Step 304: Send the medical test data corresponding to the target test item to the target hospital terminal.

[0074] The description of step 304 may refer to the relevant description of step 240 in the above embodiment, which will not be repeated here.

[0075] Step 306: Send a review request to the target laboratory terminal corresponding to the target inspection item.

[0076] In some embodiments, if the second input password does not match the second preset password, it means that the actual doctor currently using the target hospital terminal is different from the preset doctor stored in the server and allowed to access the medical test data corresponding to the target project, but due to other factors, the server may not bind the doctor's identity information corresponding to the target hospital terminal with the target test project and generate the corresponding second preset password, or the actual binding of the doctor's identity information corresponding to the target hospital terminal and the target test project has been modified but not synchronized to the server. In order to avoid the above situation, when the server detects that the second input password does not match the second preset password, the server will send a review request to the target laboratory terminal corresponding to the test project, so that the target laboratory determines the server to make a judgment and determine whether the medical test data corresponding to the target test project can be sent to the target hospital terminal.

[0077] Optionally, the review request includes the target test item and the doctor's identity information, so that the target laboratory terminal can review whether the target hospital terminal can access the medical test data corresponding to the target test item.

[0078] In some embodiments, after the target laboratory terminal receives the review request sent by the server, it can obtain multiple preset doctor identity information corresponding to the target inspection item stored in the target laboratory terminal; perform similarity detection on the doctor identity information in the review request and the multiple preset doctor identity information; if the average similarity between the doctor identity information and the multiple preset doctor identity information is greater than the similarity threshold, it is considered that the target hospital terminal corresponding to the doctor identity information in the review request can access the medical inspection data corresponding to the target inspection item, and send the review approval information to the server; if the similarity average is not greater than the similarity threshold, it is considered that the target hospital terminal corresponding to the doctor identity information in the review request cannot access the medical inspection data corresponding to the target inspection item, and then no review approval information is sent to the server or a review failure information is sent to the server.

[0079] In some embodiments, after the target laboratory terminal receives the review request sent by the server, it can also display a review interface based on the target test item and doctor identity information in the review request; the review interface may include an information area and a selection area, and the information area can be used to display specific data of the target test data and doctor identity information. Specifically, it can display "Please review whether doctor A can obtain the medical test data corresponding to test item B. Doctor A belongs to department C and the corresponding doctor level is D"; the selection area may include option buttons, such as a "pass" button and a "fail" button; if the holder of the target laboratory terminal clicks the "pass" button, the target laboratory terminal sends a review pass message to the server; if the holder of the target laboratory terminal clicks the "fail" button, the target laboratory terminal does not send a review pass message to the server or sends a review fail message to the server.

[0080] Step 308: If the approval information sent by the target laboratory terminal is received, the medical test data corresponding to the target test item is sent to the target hospital terminal.

[0081] In some embodiments, the server receives the approval information sent by the target laboratory terminal, indicating that the target laboratory terminal believes that the target hospital terminal can access the medical test data corresponding to the target test item, and then the server sends the medical test data corresponding to the target test item to the target hospital terminal.

[0082] Step 310: If the approval information sent by the target laboratory terminal is not received within the preset time period, or the rejection information sent by the target laboratory terminal is received, the medical test data corresponding to the target test item will not be sent to the target hospital terminal.

[0083] In some embodiments, if the server does not receive the review approval information sent by the target laboratory terminal within a preset time period, or receives the review failure information sent by the target laboratory terminal, it means that the target laboratory terminal believes that the target hospital terminal cannot access the medical test data corresponding to the target test item. In this case, the server does not send the medical test data corresponding to the target test item to the target hospital terminal to avoid leakage of the medical test data.

[0084] In an embodiment of the present application, when it is detected that the second input password does not match the second preset password, the server indicates that access to the target hospital terminal is directly rejected, but a method of sending an audit prompt to the laboratory terminal is added to decide whether to allow the target hospital terminal to access the medical test data corresponding to the target test item through the laboratory terminal audit. This can avoid the inconvenience that may be caused by a one-size-fits-all rejection strategy, flexibly handle requests for viewing empirical data, and improve the fault tolerance of the server while ensuring the security of medical test data.

[0085] like Figure 4 As shown, in another embodiment, a medical test data management method is provided, which can be applied to the above server. The method may include the following steps 402 to 418.

[0086] Step 402: Receive a request for viewing test data sent by a target hospital terminal.

[0087] Step 404, obtaining the first input password uploaded by the target hospital terminal.

[0088] Step 406, determine whether the first input password matches the first preset password corresponding to the organization to which the target hospital terminal belongs. If they do not match, execute step 408; if they match, execute step 410.

[0089] The description of steps 402 to 406 may refer to the relevant description of steps 210 to 230 in the above embodiment, and will not be repeated here.

[0090] Step 408: Send an error prompt to the target hospital terminal.

[0091] In some embodiments, when the server detects that the first input password does not match the first preset password corresponding to the institution to which the target hospital terminal belongs, it sends an error prompt to the target hospital terminal, wherein the error prompt is used to prompt the doctor currently using the target hospital terminal that the input password is wrong.

[0092] Step 410: Determine the confidentiality level corresponding to each data type.

[0093] Since the target hospital terminal can request access to partial medical test data in addition to the complete medical test data corresponding to the target test item from the server, the test data viewing request sent by the target hospital terminal may also include at least one data type corresponding to the medical test data to be accessed.

[0094] Optionally, the confidentiality level is used to indicate whether the medical test data corresponding to the data type needs to be kept confidential. The confidentiality level includes public or private. The data type with a confidentiality level of private can be further divided into N private levels, where N is an integer greater than 1, that is, the medical test data corresponding to the data type of the first private level has the lowest confidentiality level, and the higher the private level, the higher the confidentiality level of the medical test data corresponding to the data type.

[0095] In some embodiments, the server can obtain the confidentiality levels corresponding to all data types contained in the medical test data uploaded by the target laboratory terminal; when the server detects that the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, it can find the confidentiality level corresponding to at least one data type contained in the test data viewing request from the confidentiality levels corresponding to all data types.

[0096] In some embodiments, the confidentiality level corresponding to the same data type in different inspection items can be the same or different, depending on the actual situation. For example, in inspection items a and b, the confidentiality level corresponding to data type A is public; but in inspection item c, the confidentiality level corresponding to data type A can be non-public.

[0097] Specifically, the data types included in the hypothesis test data viewing request include: project name, methodology, test reagents, equipment, quality control, external quality assessment, and reagent instructions. Among them, the confidentiality level corresponding to the project name and equipment can be set to public, and the confidentiality level corresponding to the methodology, test reagents, quality control, external quality assessment, and reagent instructions can be set to non-public.

[0098] Step 412: If the test data viewing request includes a data type with a public confidentiality level, the medical test data corresponding to the data type with a public confidentiality level is sent to the target hospital terminal.

[0099] In some embodiments, medical test data corresponding to a data type with a confidentiality level that is public indicates that these medical test data may be data that is frequently accessed by doctors or does not need to be highly confidential. Therefore, when the server detects that the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, the server can send the medical test data corresponding to the data type with a confidentiality level that is public to the target hospital terminal, thereby reducing the resource consumption of the server for secondary matching of the second input password and the second preset password.

[0100] Step 414: If the inspection data viewing request includes data types with a confidentiality level of non-public, the second input password uploaded by the target hospital terminal is obtained, and the second preset password bound to the doctor's identity information and the target inspection item is obtained.

[0101] In some embodiments, medical test data corresponding to data types with a confidentiality level of non-public indicate that these medical test data are more sensitive and need to be kept confidential than medical test data corresponding to data types with a confidentiality level of public. Therefore, when the server detects that the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, it still needs to perform further verification on the target hospital terminal to ensure the security of the medical test data corresponding to data types with a confidentiality level of non-public.

[0102] In some embodiments, in addition to being bound to the doctor's identity information and the target test item, the second preset password can also be bound to the non-disclosure level of the data type. Different second preset passwords correspond to data types with different non-disclosure levels, so as to achieve hierarchical confidentiality of medical test data based on the non-disclosure level of the data type, which can effectively improve the confidentiality of data with high non-disclosure levels in the medical test data.

[0103] Step 416, determine whether the second input password matches the second preset password. If they match, execute step 416; if not, execute step 408.

[0104] The description of step 416 may refer to the relevant description of step 302 in the above embodiment, which will not be repeated here.

[0105] Step 418: Send the medical test data corresponding to the data type with a confidentiality level of non-public to the target hospital terminal.

[0106] The description of sending the medical test data corresponding to the data type with a confidentiality level of non-public in step 418 can refer to the relevant description of sending the medical test data corresponding to the data type with a confidentiality level of public in step 412 in the above embodiment, which will not be repeated here.

[0107] In some embodiments, at least one data type corresponding to the medical test data to be accessed contained in the test data viewing request may include data types with public confidentiality levels and data types with non-public confidentiality levels. In this case, the server may directly send the medical test data corresponding to the data type with public confidentiality levels to the target hospital terminal when it is determined that the first input password uploaded by the target hospital terminal matches the first preset password belonging to the target hospital terminal. The server then obtains the second input password uploaded by the target hospital terminal, and only sends the medical test data corresponding to the data type with non-public confidentiality levels to the target hospital terminal when it is determined that the second input password matches the second preset password, so as to ensure the security of the medical test data corresponding to the data type with non-public confidentiality levels.

[0108] In some embodiments, when the second input password matches the second preset password, if the server detects that there is an unuploaded data type among the data types with a confidentiality level of non-public (the unuploaded data type means that the data type has no corresponding medical test data stored or recorded in the server), an upload prompt is generated according to the unuploaded data type, and the upload prompt is sent to the target laboratory terminal corresponding to the target test item, so that the target laboratory terminal uploads the medical test data corresponding to the unuploaded data type to the server according to the upload prompt. After receiving the medical test data corresponding to the unuploaded data type uploaded by the target laboratory terminal, the server sends the medical test data corresponding to the data type with a confidentiality level of non-public to the target hospital terminal.

[0109] In an embodiment of the present application, medical test data are divided into public and non-public based on the confidentiality level corresponding to the data type, and different medical test data management methods are implemented according to different confidentiality levels, so that data management is more flexible and precise; in addition, when the first input password matches the first preset password, the server directly sends the basic data (medical test data corresponding to the data type with a public confidentiality level) to the target hospital terminal; when the target hospital terminal needs to access more sensitive data (medical test data corresponding to the data type with a non-public confidentiality level), the server further matches the second input password with the second preset password to prevent the leakage of more sensitive data, which not only ensures the convenience of the target hospital terminal to quickly obtain basic data, but also ensures access control of more sensitive data.

[0110] like Figure 5 As shown, in another embodiment, a medical test data management method is provided, which can be applied to the above server. The method may include the following steps 502 to 512.

[0111] Step 502: Determine the data access permission corresponding to the target hospital terminal according to the doctor's identity information.

[0112] Due to the different levels of doctors in the same institution, in actual situations, different doctor identities need to obtain different numbers of test items in the same institution, and different amounts of medical test data that can be accessed (for example, some doctors need to be able to access the medical test data corresponding to all the test items of the institution; some doctors only need to access the medical test data corresponding to the test items they are bound to), so the data access permissions corresponding to the hospital terminals used by different doctors need to be different. Therefore, after the server determines that the first input password uploaded by the target hospital terminal matches the first preset password corresponding to the institution to which the target hospital terminal belongs, after obtaining the second input password uploaded by the target hospital terminal, it first determines the data access permission corresponding to the target hospital terminal based on the doctor's identity information, so as to send the corresponding medical test data to the target hospital terminal based on different data access permissions.

[0113] In some embodiments, different data access permissions represent permissions for medical test data corresponding to different test items that the hospital terminal can access as recorded in the server. The data access permissions may include a first permission and a second permission, wherein the first permission is greater than the second permission, and the first permission refers to the permission to access all medical test data of the institution to which the target hospital terminal belongs; the second permission refers to the permission to access the medical test data corresponding to the test item bound to the doctor's identity information.

[0114] In some embodiments, the data access rights may also include a third right, which is less than the first right and greater than the second right. The third right refers to the right to access the medical test data corresponding to the test items bound to the doctor's identity information of the same department. Specifically, the target hospital terminal corresponding to the first right may be a hospital terminal held by the head of the institution, the target hospital terminal corresponding to the second right may be a hospital terminal held by the doctor directly involved in the test project A, and the target hospital terminal corresponding to the third right may be a hospital terminal held by the head of department B. Through further division of data access rights, the server can more flexibly manage medical test data according to different data access rights.

[0115] Step 504: If the data access permission is the first permission, obtain a third preset password bound to the first permission.

[0116] In some embodiments, the data access permission is the first permission, indicating that the current target hospital terminal has the permission to access all medical test data of the institution to which the target hospital terminal belongs. However, in order to ensure the security of all medical test data, the server can obtain a third preset password bound to the first permission to verify whether all medical test data of the institution can be sent to the target hospital terminal when the target hospital terminal has the permission to access all medical test data of the institution.

[0117] In some embodiments, even if the data access rights are all the first authority, but the doctor identity information is different, the corresponding third preset passwords can be the same or different.

[0118] Step 506, determine whether the second input password matches the third preset password. If they match, execute step 508; if they do not match, execute step 510.

[0119] The description of matching the second input password with the third preset password in step 506 may refer to the relevant description of matching the second input password with the second preset password in step 302 in the above embodiment, which will not be repeated here.

[0120] Step 508: Send all medical examination data of the institution to which the target hospital terminal belongs to the target hospital terminal.

[0121] In some embodiments, if the second input password matches the third preset password, it means that the target hospital terminal has the authority to access all medical examination data of the institution and can pass the password verification, then all medical examination data of the institution to which the target hospital terminal belongs will be sent to the target hospital terminal.

[0122] The description of sending all medical test data of the institution to which the target hospital terminal belongs in step 508 can refer to the relevant description of sending medical test data corresponding to the target test items in step 240 in the above embodiment, which will not be repeated here.

[0123] Step 510: Send an error prompt to the target hospital terminal.

[0124] In some embodiments, if the second input password does not match the third preset password, it means that the target hospital terminal cannot pass the password verification. Even if the target hospital terminal has the authority to access all medical test data of the institution, the server will still not send all medical test data of the institution to which the target hospital terminal belongs to the target hospital terminal, but will send an error prompt to notify the target hospital terminal that the password is wrong.

[0125] The description in step 510 may refer to the relevant description in step 408 in the above embodiment, which will not be repeated here.

[0126] Step 512: If the data access permission is the second permission, obtain a second preset password bound to the doctor's identity information and the target inspection item.

[0127] In some embodiments, the data access permission is the second permission, indicating that the current target hospital terminal has the permission to access the medical test data corresponding to the test item bound to the doctor's identity information, and in order to ensure the security of the medical test data corresponding to the target test item, the server can obtain a third preset password bound to the doctor's identity information and the target test item, so as to verify whether the medical test data corresponding to the target test item can be sent to the target hospital terminal through the second preset password when the target hospital terminal has the second permission.

[0128] In an embodiment of the present application, the server allows hospital terminals with data access rights of the first authority to access all medical test data of the institution to which they belong, and also restricts hospital terminals with data access rights of the second authority from accessing medical test data corresponding to test items other than the test items bound to the doctor's identity information, thereby achieving hierarchical management of data access rights corresponding to hospital terminals, so that the server can meet the actual access needs of different doctor identity information and hospital terminals while ensuring the security of medical test data in each institution.

[0129] like Figure 6 As shown, in another embodiment, a medical test data management method is provided, which can be applied to the above server. The method may include the following steps 602 to 626.

[0130] Step 602: Acquire multiple historical access records corresponding to historical hospital terminals.

[0131] In some embodiments, the server may record historical hospital terminals that requested access to medical test data within a preset historical time period, historical doctor identity information corresponding to the historical hospital terminals, corresponding historical test items, and corresponding at least one historical data type.

[0132] In some embodiments, the server may obtain multiple historical access records corresponding to the historical hospital terminal from the storage module. The historical hospital terminal refers to the hospital terminal that has previously sent an experience data viewing request to the server; the historical access record includes the historical doctor identity information corresponding to the historical hospital terminal, and at least one historical data type corresponding to the medical test data corresponding to the historical hospital terminal. The server determines the access habits of each historical hospital terminal based on the multiple historical access records, thereby optimizing the efficiency of the historical hospital terminal's current access to the medical test data based on the access habits.

[0133] Step 604: classify the importance of at least one historical data type and determine the importance corresponding to each historical data type.

[0134] In some embodiments, the importance of the historical data type is used to indicate the possibility that the historical data type is a data type frequently accessed by the historical hospital terminal. That is, the higher the importance, the greater the possibility that the corresponding historical data type is a data type frequently accessed by the historical hospital terminal; conversely, the lower the importance, the smaller the possibility that the corresponding historical data type is a data type frequently accessed by the historical hospital terminal.

[0135] In some embodiments, the server may calculate the number of times a first historical data type appears in multiple historical access records corresponding to a first historical hospital terminal, and obtain a first order number corresponding to the first historical data type, where the first historical data type is any historical data type corresponding to medical test data corresponding to the first historical hospital terminal, and the first historical hospital terminal is any historical hospital terminal; and determine the importance corresponding to each historical data type according to the first order number corresponding to each historical data type, wherein the more first order numbers there are, the higher the corresponding importance.

[0136] In some embodiments, the server may use multiple historical access records corresponding to the historical hospital terminal as a training set to construct a probability prediction model; the probability prediction model is used to predict the probability of each historical data type appearing in the inspection data viewing request sent by the historical hospital terminal to the server.

[0137] Step 606: Determine the target historical data type whose importance is greater than a preset threshold.

[0138] In some embodiments, a target historical data type whose importance is greater than a preset threshold value indicates that the target historical data type may be a data type frequently accessed by the historical hospital terminal. When the historical hospital terminal sends a request to view inspection data to the server again, the server can quickly send the inspection data to be accessed to the historical hospital terminal based on the target historical data type.

[0139] Step 608, generates a history type list corresponding to the historical doctor identity information according to the target historical data type, and sends the history type list to at least one laboratory terminal, so that at least one laboratory terminal can search for medical test data corresponding to each target historical data type contained in the history type list from the medical test data corresponding to the test items bound to the historical doctor identity information, and upload it to the server.

[0140] The history type list includes the history doctor identity information and each target history data type.

[0141] In some embodiments, after the server sends the history type list to at least one laboratory terminal. The first laboratory terminal receives the history type list sent by the server, and the first laboratory terminal is any at least one laboratory terminal; according to the historical doctor identity information in the history type list, the test items bound to the historical doctor identity information are found; and from the medical test data corresponding to the test items bound to the historical doctor identity information, the medical test data corresponding to each target historical data type included in the history type list are searched and uploaded to the server. The server receives the medical test data corresponding to the historical doctor identity information sent by at least one laboratory terminal, and stores it first; through the history type list, the server first obtains from at least one laboratory terminal the medical test data that the historical hospital terminal is very likely to request to access next time, so as to reduce the waiting time for the historical hospital terminal to request access to the medical test data from the server next time.

[0142] Step 610: Receive a request for viewing test data sent by a target hospital terminal.

[0143] Step 612, obtaining the first input password uploaded by the target hospital terminal.

[0144] Step 614, determine whether the first input password matches the first preset password corresponding to the organization to which the target hospital terminal belongs. If they do not match, execute step 616; if they match, execute step 618.

[0145] Step 616, sending an error prompt to the target hospital terminal.

[0146] The description of steps 610 to 616 may refer to the relevant description of steps 402 to 408 in the above embodiment, and will not be repeated here.

[0147] Step 618, obtaining a list of history types corresponding to the doctor's identity information.

[0148] In some embodiments, when the server determines that the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, the server matches the doctor identity information corresponding to the target hospital terminal with the historical doctor identity information recorded by the server, thereby finding a historical type list corresponding to the doctor identity information. If the server cannot find the historical doctor identity information that matches the doctor identity information corresponding to the target hospital terminal, indicating that the target hospital terminal is requesting access to medical test data from the server for the first time, the server obtains the second input password uploaded by the target hospital terminal, and obtains the second preset password bound to the doctor identity information and the target test item to verify whether the medical test data corresponding to the target test item can be sent to the target hospital terminal; at the same time, the server can record the target hospital terminal and generate a historical type list corresponding to the target hospital terminal based on this request.

[0149] Step 620: If the history type list corresponding to the doctor's identity information contains at least one data type, medical test data corresponding to at least one target test data type is sent to the target hospital terminal.

[0150] In some embodiments, the historical type list corresponding to the doctor's identity information includes at least one data type, indicating that at least one data type corresponding to the medical test data to be accessed requested by the target hospital terminal this time is a data type frequently accessed by doctors of the target hospital terminal. Therefore, when the server determines that the first input password matches the first preset password, it can directly send at least one medical test data corresponding to the target test data type to the target hospital terminal to reduce the matching process of the second input password and the second preset password, simplify the process of the target doctor terminal accessing the medical test data from the server, and enable the doctor to obtain the required medical test data more quickly.

[0151] Step 622, if there is any data type that does not belong to the historical type list corresponding to the doctor's identity information, obtain the second input password uploaded by the target hospital terminal, and obtain the second preset password bound to the doctor's identity information and the target inspection item.

[0152] In some embodiments, there is any data type that does not belong to the historical type list corresponding to the doctor's identity information, indicating that at least one data type corresponding to the medical test data to be accessed requested by the target hospital terminal is not a frequently accessed data type. In order to ensure the security of the data, the server needs to perform further password matching on the target hospital terminal to verify whether the target hospital terminal can obtain the medical test data corresponding to the target test item.

[0153] In some embodiments, if the server detects that there is any data type that does not belong to the historical type list corresponding to the doctor's identity information, the server needs to successfully match the second input password with the second preset password before it can send the medical test data corresponding to each data type requested by the target hospital terminal to the target hospital terminal. Optionally, if the server detects that there is any data type that does not belong to the historical type list corresponding to the doctor's identity information, the server may send the medical test data corresponding to the data type that belongs to the historical type list to the target hospital terminal; after the second input password successfully matches the second preset password, the medical test data corresponding to the data type that does not belong to the historical type list is sent to the target hospital terminal.

[0154] Step 624, determine whether the second input password matches the second preset password. If they match, execute step 626; if not, execute step 616.

[0155] Step 626, the medical test data corresponding to the target test item is sent to the target hospital terminal.

[0156] The description of steps 624 to 626 may refer to the relevant description of step 204 in the above embodiment, and will not be repeated here.

[0157] In an embodiment of the present application, the server obtains data types (or a list of historical types) of high importance by analyzing the historical access records of the historical hospital terminal. When the historical hospital terminal requests to access the medical test data again, the server can quickly identify these data types of high importance and send them directly to the target hospital terminal, thereby reducing the time the target hospital terminal waits for the server to process the medical test data and improving access efficiency. In addition, the server also sends the list of historical types to the laboratory terminal so that the laboratory terminal can prepare and upload the medical test data corresponding to the data types that may be frequently accessed in advance, so that the server can be prepared earlier to process the request of the target hospital terminal faster, making the resource allocation of the server more reasonable. Moreover, the server processes each link of the test data viewing request of the target hospital terminal, verifies the target hospital terminal through password matching, and always ensures the security of the medical test data.

[0158] like Figure 7 As shown, in one embodiment, a medical test data management device 700 is provided, which can be applied to the above electronic device. The medical test data management device 700 can include a receiving module 710 , an acquiring module 720 and a sending module 730 .

[0159] The receiving module 710 is used to receive a test data viewing request sent by a target hospital terminal, the test data viewing request includes a target test item corresponding to the medical test data to be accessed and the doctor identity information corresponding to the target hospital terminal; the target hospital terminal is any hospital terminal.

[0160] The acquisition module 720 is used to acquire the first input password uploaded by the target hospital terminal.

[0161] Optionally, the acquisition module 720 is also used to obtain the second input password uploaded by the target hospital terminal if the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, and obtain the second preset password bound to the doctor's identity information and the target inspection item.

[0162] The sending module 730 is used to send the medical test data corresponding to the target test item to the target hospital terminal if the second input password matches the second preset password.

[0163] Optionally, the server is communicatively connected to at least one hospital terminal; the server is also communicatively connected to at least one laboratory terminal.

[0164] In some embodiments, the medical examination data management device 700 may further include an audit module.

[0165] The audit module is used to send an audit request to the target laboratory terminal corresponding to the target inspection item if the second input password does not match the second preset password. The audit request includes the target inspection item and the doctor's identity information, so that the target laboratory terminal can audit whether the target hospital terminal can access the medical inspection data corresponding to the target inspection item.

[0166] Optionally, the sending module 730 is further used to send the medical test data corresponding to the target test item to the target hospital terminal if the review approval information sent by the target laboratory terminal is received.

[0167] Optionally, the receiving module 710 is also used to not send the medical test data corresponding to the target test item to the target hospital terminal if no review approval information is received from the target laboratory terminal within a preset time period, or if review failure information is received from the target laboratory terminal.

[0168] Optionally, the test data viewing request also includes at least one data type corresponding to the medical test data to be accessed.

[0169] In some embodiments, the acquisition module 720 further includes determining the confidentiality level corresponding to each data type if the first input password matches the first preset password corresponding to the organization to which the target hospital terminal belongs, and the confidentiality level includes public or non-public.

[0170] The sending module 730 is further configured to send the medical test data corresponding to the data type with a public confidentiality level to the target hospital terminal if the test data viewing request includes the data type with a public confidentiality level.

[0171] In some embodiments, the acquisition module 720 is also used to obtain the second input password uploaded by the target hospital terminal if the inspection data viewing request includes a data type with a confidentiality level of non-public, and obtain the second preset password bound to the doctor's identity information and the target inspection item.

[0172] In some embodiments, the sending module 730 is further used to send the medical test data corresponding to the data type with a confidentiality level of non-public to the target hospital terminal if the second input password matches the second preset password.

[0173] Optionally, the acquisition module 720 is further used to determine the data access permission corresponding to the target hospital terminal according to the doctor's identity information; if the data access permission is the first permission, obtain the third preset password bound to the first permission.

[0174] Optionally, the sending module 730 is further configured to send all medical test data of the institution to which the target hospital terminal belongs to the target hospital terminal if the second input password matches the third preset password.

[0175] In some embodiments, the acquisition module 720 is further used to obtain a second preset password bound to the doctor's identity information and the target inspection item if the data access permission is the second permission.

[0176] Optionally, the first authority is greater than the second authority, the first authority refers to the authority to access all medical test data of the institution to which the target hospital terminal belongs; the second authority refers to the authority to access the medical test data corresponding to the test items bound to the doctor's identity information.

[0177] In some embodiments, the medical test data management device 700 may further include a list generation module. The list generation module is used to obtain multiple historical access records corresponding to the historical hospital terminal, the historical access records include historical doctor identity information corresponding to the historical hospital terminal, and at least one historical data type corresponding to the medical test data corresponding to the historical hospital terminal; divide the at least one historical data type into importance levels, determine the importance levels corresponding to each historical data type; determine the target historical data type whose importance level is greater than a preset threshold; generate a historical type list corresponding to the historical doctor identity information according to the target historical data type, and send the historical type list to at least one laboratory terminal, so that at least one laboratory terminal searches for medical test data corresponding to each target historical data type included in the historical type list from the medical test data corresponding to the test items bound to the historical doctor identity information, and uploads the medical test data to the server.

[0178] Optionally, the acquisition module 720 is further used to obtain a history type list corresponding to the doctor's identity information if the first input password matches a first preset password corresponding to the institution to which the target hospital terminal belongs.

[0179] Optionally, the sending module 730 is further used to send medical test data corresponding to at least one target test data type to the target hospital terminal if at least one data type is included in the historical type list corresponding to the doctor's identity information.

[0180] In some embodiments, the acquisition module 720 is also used to obtain a second input password uploaded by the target hospital terminal if there is any data type that does not match the historical inspection data type included in the target historical type list, and obtain a second preset password bound to the doctor's identity information and the target inspection item.

[0181] In an embodiment of the present application, the server uses a first preset password associated with the institution to which the hospital terminal belongs to match the first input password uploaded by the target hospital terminal, thereby ensuring that only hospital terminals within the institution can further view the medical test data of the institution, effectively preventing access by other institutions; and, using a second preset password that is doubly bound to the doctor's identity information and the target test item to match the second input password, thereby ensuring that only the doctor bound to the target test item can use the target hospital terminal to view the medical test data corresponding to the target test item, thereby avoiding doctors from viewing medical test data corresponding to test items that are not within their scope of responsibility or are not authorized to access, and adopting a double password verification method to effectively improve the security of medical test data.

[0182] Figure 8 FIG. 1 is a block diagram of an electronic device in an embodiment. The electronic device may be a mobile phone, a tablet computer, a smart wearable device, etc. Figure 8 As shown, the electronic device 800 may include one or more of the following components: a processor 810, and a memory 820 coupled to the processor 810, wherein the memory 820 may store one or more computer programs, and the one or more computer programs may be configured to implement the methods described in the above embodiments when executed by one or more processors 810.

[0183] The processor 810 may include one or more processing cores. The processor 810 uses various interfaces and lines to connect various parts of the entire electronic device 800, and executes various functions and processes data of the electronic device 800 by running or executing instructions, programs, code sets or instruction sets stored in the memory 820, and calling data stored in the memory 820. Optionally, the processor 810 can be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 810 can integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing display content; and the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 810, but may be implemented separately through a communication chip.

[0184] The memory 820 may include a random access memory (RAM) or a read-only memory (ROM). The memory 820 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 820 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc. The data storage area may also store data created by the electronic device 800 during use, etc.

[0185] It can be understood that the electronic device 800 may include more or fewer structural elements than those in the above structural block diagram, for example, including a power supply, input buttons, cameras, speakers, screens, RF (Radio Frequency) circuits, Wi-Fi (Wireless Fidelity) modules, Bluetooth modules, sensors, etc., and no limitation is made here.

[0186] An embodiment of the present application discloses a computer-readable storage medium storing a computer program, wherein the computer program implements the methods described in the above embodiments when executed by a processor.

[0187] The embodiments of the present application disclose a computer program product, including a computer program, and the computer program can be executed by a processor to implement the methods described in the above embodiments.

[0188] A person skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a non-volatile computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only memory (ROM), etc.

[0189] As used herein, any reference to memory, storage, database, or other medium may include nonvolatile and / or volatile memory. Suitable nonvolatile memory may include ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically Erasable PROM (EEPROM), or Flash memory. Volatile memory may include random access memory (RAM), which is used as an external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), memory bus direct RAM (RDRAM), and direct memory bus dynamic RAM (DRDRAM).

[0190] It should be understood that the "one embodiment" or "an embodiment" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. Those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required for the present application.

[0191] In the various embodiments of the present application, it should be understood that the size of the serial numbers of the above-mentioned processes does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0192] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0193] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0194] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0195] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-accessible memory. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a memory and includes several requests for a computer device (which can be a personal computer, a server or a network device, etc., specifically a processor in a computer device) to perform some or all of the steps of the above-mentioned methods of various embodiments of the present application.

[0196] The above is a detailed introduction to a medical test data management method, device, electronic device and storage medium disclosed in the embodiments of the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and core idea of ​​the present application. At the same time, for those of ordinary skill in the art, according to the idea of ​​the present application, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A medical test data management method, characterized in that: Applied to a server, the server is communicatively connected to at least one hospital terminal; the method comprises: Receiving a test data viewing request sent by a target hospital terminal, the test data viewing request including a target test item corresponding to the medical test data to be accessed and the doctor identity information corresponding to the target hospital terminal; the target hospital terminal is any of the hospital terminals; Obtaining the first input password uploaded by the target hospital terminal; If the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, then obtaining the second input password uploaded by the target hospital terminal, and obtaining the second preset password bound to the doctor's identity information and the target inspection item; If the second input password matches the second preset password, the medical test data corresponding to the target test item is sent to the target hospital terminal.

2. The method according to claim 1, characterized in that The server is also in communication connection with at least one laboratory terminal, and the method further comprises: If the second input password does not match the second preset password, a review request is sent to the target laboratory terminal corresponding to the target inspection item, the review request including the target inspection item and the doctor's identity information, so that the target laboratory terminal can review whether the target hospital terminal can access the medical inspection data corresponding to the target inspection item; If the approval information sent by the target laboratory terminal is received, the medical test data corresponding to the target test item is sent to the target hospital terminal; If the approval information sent by the target laboratory terminal is not received within the preset time period, or the rejection information sent by the target laboratory terminal is received, the medical test data corresponding to the target test item will not be sent to the target hospital terminal.

3. The method according to claim 1, characterized in that The test data viewing request also includes at least one data type corresponding to the medical test data to be accessed; After obtaining the first input password uploaded by the target hospital terminal, the method further includes: If the first input password matches the first preset password corresponding to the organization to which the target hospital terminal belongs, determining the confidentiality level corresponding to each of the data types, the confidentiality level including public or non-public; If the inspection data viewing request includes a data type with a public confidentiality level, the medical inspection data corresponding to the data type with a public confidentiality level is sent to the target hospital terminal.

4. The method according to claim 3, characterized in that The step of obtaining the second input password uploaded by the target hospital terminal and obtaining the second preset password bound to the doctor's identity information and the target inspection item includes: If the inspection data viewing request includes data types with a confidentiality level of non-public, obtaining a second input password uploaded by the target hospital terminal, and obtaining a second preset password bound to the doctor's identity information and the target inspection item; If the second input password matches the second preset password, sending the medical test data corresponding to the target test item to the target hospital terminal includes: If the second input password matches the second preset password, the medical test data corresponding to the data type with a confidentiality level of non-public is sent to the target hospital terminal.

5. According to claim 1, it is characterized in that: The method further comprises: Determine the data access permission corresponding to the target hospital terminal according to the doctor's identity information; If the data access permission is the first permission, obtaining a third preset password bound to the first permission; If the second input password matches the third preset password, all medical test data of the institution to which the target hospital terminal belongs are sent to the target hospital terminal; The obtaining of a second preset password bound to the doctor's identity information and the target inspection item includes: If the data access permission is the second permission, obtaining a second preset password bound to the doctor's identity information and the target inspection item; The first authority is greater than the second authority. The first authority refers to the authority to access all medical test data of the institution to which the target hospital terminal belongs; the second authority refers to the authority to access the medical test data corresponding to the test items bound to the doctor's identity information.

6. The method according to claim 1, characterized in that The server is also in communication connection with at least one laboratory terminal, and the method further comprises: Acquire a plurality of historical access records corresponding to the historical hospital terminal, wherein the historical access records include historical doctor identity information corresponding to the historical hospital terminal and at least one historical data type corresponding to medical test data corresponding to the historical hospital terminal; Classifying the at least one historical data type by importance, and determining the importance corresponding to each historical data type; Determine the target historical data type whose importance is greater than a preset threshold; According to the target historical data type, a historical type list corresponding to the historical doctor identity information is generated, and the historical type list is sent to the at least one laboratory terminal, so that the at least one laboratory terminal can search for medical test data corresponding to each target historical data type contained in the historical type list from the medical test data corresponding to the test items bound to the historical doctor identity information, and upload it to the server.

7. The method according to claim 6, characterized in that The inspection data viewing request also includes at least one data type corresponding to the medical inspection data to be accessed; after obtaining the first input password uploaded by the target hospital terminal, the method further includes: If the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, obtaining a history type list corresponding to the doctor's identity information; If the historical type list corresponding to the doctor's identity information includes the at least one data type, sending medical test data corresponding to the at least one target test data type to the target hospital terminal; If the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, obtaining the second input password uploaded by the target hospital terminal, and obtaining the second preset password bound to the doctor's identity information and the target inspection item, including: If there is any data type that does not belong to the historical type list corresponding to the doctor's identity information, the second input password uploaded by the target hospital terminal is obtained, and the second preset password bound to the doctor's identity information and the target inspection item is obtained.

8. A medical test data management device, characterized in that: Applied to a server, the server is communicatively connected to at least one hospital terminal; the device comprises: A receiving module, configured to receive a test data viewing request sent by a target hospital terminal, wherein the test data viewing request includes a target test item corresponding to the medical test data to be accessed and the doctor identity information corresponding to the target hospital terminal; the target hospital terminal is any of the hospital terminals; An acquisition module, used for acquiring the first input password uploaded by the target hospital terminal; The acquisition module is further configured to acquire, if the first input password matches the first preset password corresponding to the institution to which the target hospital terminal belongs, a second input password uploaded by the target hospital terminal, and acquire a second preset password bound to the doctor's identity information and the target inspection item; A sending module is used to send the medical test data corresponding to the target test item to the target hospital terminal if the second input password matches the second preset password.

9. An electronic device, characterized in that: The method comprises a memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the processor implements the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.